Message sending method, device and equipment based on switching process, and medium

Abstract

The application is a divisional application of 202110215380.0. The application discloses a message sending method and device based on a switching process, equipment and a storage medium, and belongs to the Internet field. The method comprises the following steps: in the switching process, a source access network sends control parameters of a QNC of a non-GBR bearer flow to a target access network, so that the target access network sends a notification message to an application entity through a core network entity when a change in the parameter value of the QNC of the non-GBR bearer flow after the switching is completed meets the reporting condition; wherein the control parameters of the QNC are used to indicate the parameters of the QNC of the non-GBR bearer flow and the reporting condition. The application can optimize the QoS notification mechanism for using the non-GBR bearer flow.

Description

[0001] This application is a divisional application. The parent application has the application number 202110215380.0, the application date is February 25, 2021, and the invention title is "Message Transmission Method, Apparatus, Device and Medium Based on Handover Process". Technical Field

[0002] This application relates to the field of mobile communications, and in particular to a message sending method, apparatus, device, and medium based on a handover process. Background Technology

[0003] In 5G mobile communication technology, QoS control is performed based on the Quality of Service Flow (QoS Flow).

[0004] Based on the bearer type, QoS flows are divided into two types: Guaranteed Bit Rate (GBR) and Non-Guaranteed Bit Rate (Non-GBR). For GBR QoS flows, the corresponding bit rate can be guaranteed even when network resources are scarce; for Non-GBR QoS flows, a rate reduction is required when network resources are scarce.

[0005] Currently, over 90% of service traffic is non-GBR QoS streaming, such as common audio and video calls and online conferencing. Changes in wireless network status frequently cause stuttering in these audio and video communications. Summary of the Invention

[0006] This application provides a message sending method, apparatus, device, and storage medium based on the handover process, which can optimize the QoS notification mechanism for non-GBR bearer streams. The technical solution is as follows:

[0007] According to one aspect of this application, a message sending method based on a handover process is provided, the method comprising:

[0008] During the handover process, the source access network sends the QoS Notification Control (QNC) control parameters of the non-GBR bearer flow to the target access network, so that when the change of the QNC parameter value of the non-GBR bearer flow after the handover is completed meets the reporting conditions, the target access network sends a notification message to the application entity through the core network entity.

[0009] The control parameters of the QNC are used to indicate the parameters of the QNC and the reporting conditions of the non-GBR bearer stream.

[0010] According to another aspect of this application, a message sending method based on a handover process is provided, the method comprising:

[0011] During the handover process, the target access network receives control parameters of the QNC, which are used to indicate the parameters of the QNC and the reporting conditions of the non-GBR bearer stream.

[0012] After the handover is completed, when the change in the parameter value of the QNC of the non-GBR bearer flow meets the reporting conditions, the target access network sends a notification message to the application entity through the core network entity.

[0013] The control parameters of the QNC are used to indicate the parameters of the QNC and the reporting conditions of the non-GBR bearer stream.

[0014] According to another aspect of this application, a message sending apparatus during a handover process is provided, the apparatus comprising:

[0015] The sending module is used to send the control parameters of the QNC of the non-GBR bearer flow to the target access network during the handover process, so that when the change of the QNC parameter value of the non-GBR bearer flow after the handover is completed meets the reporting conditions, the target access network sends a notification message to the application entity through the core network entity.

[0016] The control parameters of the QNC are used to indicate the parameters of the QNC and the reporting conditions of the non-GBR bearer stream.

[0017] According to another aspect of this application, a message sending apparatus during a handover process is provided, the apparatus comprising:

[0018] The receiving module is used to receive control parameters of the QNC during the handover process. The control parameters of the QNC are used to indicate the parameters of the QNC of the non-GBR bearer stream and the reporting conditions.

[0019] The sending module is used to send a notification message to the application entity through the core network entity after the handover is completed, when the change in the parameter value of the QNC of the non-GBR bearer stream meets the reporting conditions.

[0020] According to one aspect of this application, an access network element is provided, the access network element comprising: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the message sending method based on the handover process as described above.

[0021] According to another aspect of this application, a computer-readable storage medium is provided, the storage medium storing a computer program that is loaded and executed by a processor to implement the message sending method based on the switching process as described above.

[0022] According to another aspect of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and executes the computer instructions, causing the computer device to perform the message sending method based on a switching process provided above.

[0023] The beneficial effects of the technical solutions provided in this application include at least the following:

[0024] Since the handover process is the most likely to cause rapid changes in the wireless network state, by sending the QNC control parameters of the non-GBR bearer flow from the source access network to the target access network, the target access network can send a notification message to the application entity through the core network entity when the increase / decrease of the QNC parameters of the non-GBR bearer flow meets the reporting conditions. This allows the application entity to adjust its internal application to adapt to the parameter changes when the relevant parameters of the non-GBR bearer flow deteriorate or recover from poor to good, thereby optimizing the operation of the application. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This application shows a structural block diagram of a communication system provided in an exemplary embodiment.

[0027] Figure 2 A structural block diagram of a communication system provided in another exemplary embodiment of this application is shown;

[0028] Figure 3 A flowchart illustrating a message sending method based on a handover process provided in an exemplary embodiment of this application is shown.

[0029] Figure 4 A flowchart of a message sending method based on a handover process provided in another exemplary embodiment of this application is shown;

[0030] Figure 5 A flowchart illustrating a configuration method for QNC provided in an exemplary embodiment of this application is shown;

[0031] Figure 6 A flowchart illustrating a QNC configuration method provided in another exemplary embodiment of this application is shown;

[0032] Figure 7 A flowchart illustrating a QNC configuration method provided in another exemplary embodiment of this application is shown;

[0033] Figure 8 A flowchart illustrating an exemplary embodiment of the QNC optimization method provided in this application is shown.

[0034] Figure 9 A flowchart illustrating an optimization method for QNC provided in another exemplary embodiment of this application is shown;

[0035] Figure 10 A flowchart illustrating a method for notifying QNC parameter values ​​provided in an exemplary embodiment of this application is shown;

[0036] Figure 11 A flowchart illustrating a message sending method based on a handover process provided in an exemplary embodiment of this application is shown.

[0037] Figure 12 A flowchart of a message sending method based on a handover process provided in another exemplary embodiment of this application is shown;

[0038] Figure 13 This illustration shows a schematic diagram of a UE or network-requested PDU session modification (for non-roaming and local decentralization roaming) process provided in an exemplary embodiment of this application;

[0039] Figure 14 This illustration shows a schematic diagram of an exemplary embodiment of the SM policy association modification process provided in this application;

[0040] Figure 15 This illustration shows a schematic diagram of an Xn-based inter-NG-RAN handover process without UPF reallocation provided in an exemplary embodiment of this application;

[0041] Figure 16 This illustration shows a schematic diagram of the message structure of an N2 path switching request provided in an exemplary embodiment of this application;

[0042] Figure 17 A schematic diagram of an N2 handover process based on an NG-RAN node provided in an exemplary embodiment of this application is shown;

[0043] Figure 18This illustration shows a schematic diagram of a UE-requested PDU session establishment process provided in an exemplary embodiment of this application;

[0044] Figure 19 This application illustrates a flowchart of a PDU session establishment process for a UE request in a home-roaming scenario, provided by an exemplary embodiment of this application.

[0045] Figure 20 This illustration shows a schematic diagram of the AF request transfer to the relevant PCF process for a single UE address provided in an illustrative embodiment of this application;

[0046] Figure 21 This illustration shows a schematic diagram of a PDU session modification process for non-roaming and locally diverted roaming UEs or networks, provided by an exemplary embodiment of this application.

[0047] Figure 22 This illustration shows a schematic diagram of a PDU session modification process for a UE or network requesting home route roaming, provided by an exemplary embodiment of this application.

[0048] Figure 23 A schematic diagram of a handover procedure within a base station provided in an exemplary embodiment of this application is shown;

[0049] Figure 24 This illustration shows a schematic diagram of an Xn-based inter-NG-RAN handover process without UPF reallocation provided by another exemplary embodiment of this application;

[0050] Figure 25 This application shows a message structure diagram of a switching command provided in an exemplary embodiment.

[0051] Figure 26 A schematic diagram of a handover process based on XG-RAN node N2 provided in another exemplary embodiment of this application is shown;

[0052] Figure 27 This application illustrates a message structure diagram of a handover request provided in an exemplary embodiment.

[0053] Figure 28 This invention provides a message structure diagram of a switching command provided in another exemplary embodiment of the present application.

[0054] Figure 29 This illustration shows a schematic diagram of a handover process (non-roaming and locally routed roaming) from an untrusted non-3GPP to a 3GPP access PDU session provided by an exemplary embodiment of this application;

[0055] Figure 30This illustration shows a switching diagram from EPC / ePDG to 5GS provided in an exemplary embodiment of this application;

[0056] Figure 31 This illustration shows a schematic diagram of the preparation phase for interoperability based on a single registration in the EPS to 5GS process provided by an exemplary embodiment of this application;

[0057] Figure 32 This invention provides a block diagram of a message sending apparatus based on a handover process during a handover process, according to an exemplary embodiment of this application.

[0058] Figure 33 This invention provides a block diagram of a message sending apparatus based on a handover process during a handover process, according to an exemplary embodiment of this application.

[0059] Figure 34 A block diagram of a network element device provided in an exemplary embodiment of this application is shown. Detailed Implementation

[0060] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0061] It should be understood that "several" in this article refers to one or more, and "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0062] Figure 1 A schematic diagram of the architecture of a communication system provided in an exemplary embodiment of this application is shown. Figure 1 As shown, the system architecture 100 may include: User Equipment (UE), Radio Access Network (RAN), Core, and Data Network (DN). Among these, UE, RAN, and Core are the main components of the architecture, logically divided into user plane and control plane. The control plane is responsible for mobile network management, while the user plane is responsible for service data transmission. Figure 1In this context, 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, and the NG6 reference point is located between the Core user plane and the data network.

[0063] UE (User Equipment): This is the entry point for mobile users to interact with the network. It provides basic computing and storage capabilities, displays service windows to the user, and accepts user input. The UE will use next-generation air interface technology to establish signal and data connections with the RAN (Radio Network Array), thereby transmitting control signals and service data to the mobile network.

[0064] RAN: Similar to a base station in a traditional network, it is deployed close to the UE (User Equipment) to provide network access for authorized users within the cell coverage area. It can transmit user data using transmission tunnels of different quality levels based on user level and service requirements. The RAN manages its own resources, utilizes them efficiently, and provides access services to the UE on demand, forwarding control signals and user data between the UE and the core network.

[0065] Core: Responsible for maintaining the subscription data of the mobile network, managing the network elements of the mobile network, and providing UE with functions such as session management, mobility management, policy management, and security authentication. When the UE attaches, it provides network access authentication; when the UE has a service request, it allocates network resources for the UE; when the UE moves, it updates network resources for the UE; when the UE is idle, it provides a fast recovery mechanism for the UE; when the UE detaches, it releases network resources for the UE; when the UE has service data, it provides data routing functions, such as forwarding uplink data to the DN; or receiving downlink data from the UE from the DN, forwarding it to the RAN, and then sending it to the UE.

[0066] DN: This is the data network that provides services to users. Generally, the client is located at the UE (User Equipment), and the server is located in the data network. The data network can be a private network, such as a local area network (LAN), an external network not controlled by the operator, such as the Internet, or a dedicated network jointly deployed by the operator, such as for configuring IP Multimedia Core Network Subsystem (IMS) services.

[0067] Figure 2 Is Figure 1The detailed architecture determined based on this is as follows: the core network user plane includes the User Plane Function (UPF); the core network control plane includes the Authentication Server Function (AUSF), Access and Mobility Management Function (AMF), Session Management Function (SMF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Function Repository Function (NRF), Unified Data Management (UDM), Policy Control Function (PCF), and Application Function (AF). The functions of these entities are as follows:

[0068] UPF: Performs user packet forwarding according to the routing rules of SMF;

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

[0070] AMF: UE Access and Mobility Management;

[0071] SMF: UE Session Management;

[0072] NSSF: Select network slices for the UE;

[0073] NEF: To expose network functions to third parties via API interfaces;

[0074] NRF: Provides storage and selection functions for network function entity information for other network elements;

[0075] UDM: User Subscription Context Management;

[0076] PCF: User Policy Management;

[0077] AF: User Application Management.

[0078] exist Figure 2In the architecture shown, the N1 interface serves as the reference point between the UE and the AMF; the N2 interface serves as the reference point between the RAN and the AMF, used for sending NAS messages, etc.; the N3 interface serves as the reference point between the RAN and the UPF, used for transmitting user plane data, etc.; the N4 interface serves as the reference point between the SMF and the UPF, used for transmitting information such as tunnel identification information for N3 connections, data buffer indication information, and downlink data notification messages, etc.; the N6 interface serves as the reference point between the UPF and the DN, used for transmitting user plane data, etc. NG interface: The interface between the radio access network and the 5G core network.

[0079] It should be noted that, Figure 1 and Figure 2 The interface names between the various network elements are just examples. In the actual implementation, the interface names may be other names. This application does not specifically limit this. Figure 1 and Figure 2 The names of the various network elements included (such as SMF, AF, UPF, etc.) are merely examples and do not limit the functions of the network elements themselves. In 5GS and other future networks, the aforementioned network elements may also have other names, and this application embodiment does not specifically limit them. For example, in 6G networks, some or all of the aforementioned network elements may use the terminology from 5G, or may use other names, etc. This is explained uniformly here and will not be repeated below. Furthermore, it should be understood that the names of the messages (or signaling) transmitted between the aforementioned network elements are merely examples and do not limit the functions of the messages themselves.

[0080] In this embodiment, a QuickChange QoS Notification Control (QCQNC) mechanism is defined for non-GBR QoS flows. QCQNC is a type of QoS Notification Control (QNC) and can be abbreviated as QNC. In the QCQNC mechanism provided in this embodiment, when the access network detects a rapid change in at least one QoS parameter of a non-GBR QoS flow, it sends a quick change notification to the SMF. The SMF sends the quick change notification to the PCF, AF, and UE. After receiving the quick change notification, the AF and UE adjust their internal applications to adapt to the change, preventing stuttering and other issues that affect the Quality of Experience (QoE).

[0081] QoS flows represent the smallest QoS distinction within a PDU session. In 5G systems, QoS flow IDs (QFIs) are used to differentiate QoS flows. QoS flows are controlled by the SMF and can be pre-configured, established during the PDU session establishment process, or modified during the PDU session modification process.

[0082] In this embodiment of the application, the following QoS characteristics are defined for non-GBR QoS flows:

[0083] • 5G QoS Identifier (5QI), Allocation and Retention Priority (ARP), and Reflective QoS Attribute (RQA).

[0084] Furthermore, for 5QI corresponding to non-GBR QoS flows, only the following QoS characteristics are defined:

[0085] • Resource Type;

[0086] It is divided into: GBR, latency-critical GBR, or non-GBR.

[0087] Priority Level;

[0088] • Packet Delay Budget (PDB);

[0089] Packet data latency (budget), including core network packet latency.

[0090] • Packet Error Rate (PER);

[0091] Of these four QoS features, 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.

[0092] In this embodiment, the proposed QoS QNC profile consists of three parameters related to the Non-GBR QoS Flow (NGBF): PDB, PER, and Current Bit Rate (CBR). When the RAN detects that any one of these three parameters increases or decreases by a rate of change (or increases or decreases by a value) exceeding a specified threshold (since the nature of different parameters is different, the corresponding rate of change or value is different for each parameter), it sends a notification message to the SMF, informing it of the rate of change or value of change for all parameters. The SMF sends a notification message to the PCF, the PCF sends a notification message to the AF, and the application corresponding to the AF makes corresponding adjustments. Simultaneously, the SMF sends a notification message to the UE via NAS messages, and the application corresponding to the UE can also make corresponding adjustments. This achieves interaction between the network and the application, optimizes service transmission, resolves lag when the network is congested, or addresses situations where, even after network conditions improve, the application still uses a very low transmission rate, failing to fully utilize network resources and thus failing to improve the user experience.

[0093] In one embodiment, the parameter variation can be defined in two ways:

[0094] 1. Change value;

[0095] When the parameter value changes from A to B, BA is defined as the changed value. It should be noted that, assuming the change value when the parameter value changes from A to B is the first changed value, and the change value when it changes back from B to A is the second changed value, then the magnitudes of the first and second changed values ​​are the same (regardless of whether they are positive or negative).

[0096] 2. Rate of change.

[0097] In one possible design, when the parameter value changes from A to B, (BA) / A is defined as the change value. It should be noted that, assuming the rate of change when the parameter value changes from A to B is the first rate of change (BA) / A, and the rate of change when changing back 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 (regardless of whether they are positive or negative).

[0098] That is, the magnitude of (BA) / A is not equal to the magnitude of (AB) / B (assuming B>A>0). Therefore, in the above definition, after parameter value A rises by 30% to parameter value B, and then parameter value B falls by 30%, it does not return to parameter value A.

[0099] In another possible design, to ensure that a parameter value that first increases by 30% and then decreases by 30% represents a return to the original parameter value, the rate of change is uniformly defined as (larger value – smaller value) / smaller value before and after the change, or (larger value – smaller value) / larger value before and after the change, or (larger value – smaller value) / a fixed value before and after the change. Here, the larger value is the parameter value with the larger absolute value before and after the change, the smaller value is the parameter value with the smaller absolute value before and after the change, and the fixed value is a pre-determined, unchanging value. In this way, when parameter value A first increases by 30% and then decreases by 30%, it returns to the original parameter value A.

[0100] In one embodiment, the following communication protocol is provided:

[0101] QoS configuration

[0102] Whether a QoS flow is GBR or non-GBR is determined by its QoS configuration. The QoS configuration of a QoS flow is sent to (R)AN and includes the following QoS parameters (details of the QoS parameters are defined in section 5.7.2 of standard TS23.501).

[0103] - For each QoS flow, the QoS configuration should include the QoS parameters;

[0104] -5QI; and,

[0105] -ARP;

[0106] - For each non-GBR QoS flow, the QoS configuration can also include QoS parameters:

[0107] -QCQNC;

[0108] -RQA;

[0109] - For each GBR QoS stream only, the QoS configuration can also include QoS parameters:

[0110] -Guaranteed Flow Bit Rate (GFBR) - Uplink and downlink, and,

[0111] -Maximum Flow Bit Rate (MFBR) -Uplink and downlink; and,

[0112] - For GBR QoS flows only, the QoS configuration may also include one or more QoS parameters;

[0113] -Notification control;

[0114] -Maximum packet loss rate-Uplink and downlink.

[0115] In one embodiment, a QoS Quick ChangeNotification control profile is provided.

[0116] The QoS Rapid Change Notification Control (QCDC) configuration is provided for non-GBR QoS flows that have QCDC enabled. If the corresponding PCC rule contains relevant information (as described in TS23.503), the SMF should provide the QCDC configuration to the NG-RAN in addition to the QoS profile. If the SMF provides the QCDC configuration to the NG-RAN (if the corresponding Policy and Charging Control (PCC) rule information has changed), the NG-RAN will replace the previously stored configuration with it.

[0117] The Rapid Change Notification Control (RDC) configuration indicates rapid changes in any QoS parameters, including PDB, PER, and detected CBR (Current Bit Rate). This helps applications control application traffic based on the changed QoS parameters. The RDC configuration indicates rapid changes (increases or decreases) in (PDR, PER, CBR) over a short period (20%, 10%, 30%), and that the new values ​​are maintained consistently. This rapid change is not due to short, rapid spikes caused by sudden surges or interference.

[0118] Note: The rapid change notification control configuration can be any combination of changes to PDB, PER, and CBR. For example, the rapid change notification control configuration can set the increase (or decrease) PDR to 20%; it can also set the increase (or decrease) PDR and PER to 20% and the increase (or decrease) CBR to 10%; or it can set the increase (or decrease) CBR to 30%.

[0119] When NG-RAN sends a rapid change notification to SMF that satisfies the QCQNC configuration, NG-RAN should also include the current QoS parameters (PDB, PER) and CBR in the notification message.

[0120] The QNC mechanism for non-GBR bearer streams includes the following processes:

[0121] 1. QNC control during the switching process;

[0122] 2. QNC configuration process;

[0123] 3. The optimization process of QNC;

[0124] 4. QNC notification process (for AF);

[0125] 5. Notification process for the changed QNC parameter values ​​(for UE).

[0126] The above processes are described in detail below.

[0127] 1. QNC control during the switching process;

[0128] The handover process is the most common factor causing rapid changes in QNC parameters, so it is necessary to introduce a QNC mechanism for non-GBR bearer streams during the handover process.

[0129] Figure 3 This is a flowchart of a message sending method based on a handover process provided in an exemplary embodiment of this application. This embodiment applies this method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0130] Step 320: During the handover process, the source access network sends the control parameters of the QNC for the non-GBR bearer stream to the target access network;

[0131] Non-GBR bearer flows refer to bearer flows that are not of the GBR type. Non-GBR bearer flows include: non-GBR QoS flows, or non-GBR EPS bearers. For example, in a 5G system, a non-GBR bearer flow is a non-GBR type QoS flow; in a 4G system, a non-GBR bearer flow is a non-GBR type EPS bearer.

[0132] Among them, the control parameters of QNC are used to indicate the parameters of QNC for non-GBR bearer streams and the reporting conditions.

[0133] For example, the parameters of QNC (or QCQNC) include at least one of the following: PDB, PER, and CBR. When QNC includes at least two parameters, there are at least two parameters with the same reporting conditions; and / or, there are at least two parameters with different reporting conditions.

[0134] For example, the reporting conditions (or change thresholds, change reporting thresholds) include at least one of the following:

[0135] • The change in the parameters of QNC within the first time period is greater than the first threshold;

[0136] The first threshold is a decimal greater than 0 and less than 1. For example, the first threshold is 20%, 30%, and 40%. The first duration is the period or duration used to calculate the change value, such as 1 second or 2 seconds.

[0137] • The rate of change of the QNC parameters during the second time period is greater than the second threshold;

[0138] The second threshold is a decimal greater than 0 and less than 1. For example, the second threshold could be 20%, 30%, or 40%. The second duration is the period or duration used to calculate the rate of change, such as 1 second or 2 seconds.

[0139] • The change value of the QNC parameter within the first time period is greater than the first threshold, and it remains at the third threshold.

[0140] The third threshold is a threshold used to measure the duration of a change in value, such as 2 seconds.

[0141] • The rate of change of the QNC parameter during the second time period is greater than the second threshold and remains at the fourth threshold.

[0142] The fourth threshold is the threshold used to measure the duration of the rate of change, such as 2 seconds.

[0143] Step 340: During the handover process, the target access network receives control parameters from the QNC;

[0144] The target access network enables or initiates the QNC for non-GBR bearer flows based on the control parameters of the QNC.

[0145] Step 360: After the handover is completed, when the change in the parameter value of the QNC of the non-GBR bearer flow in the target access network meets the reporting conditions, a notification message is sent to the application entity through the core network entity.

[0146] Changes in QNC parameter values ​​include at least one of the following two:

[0147] 1. The change from the first parameter value to the second parameter value;

[0148] The first parameter value is the QNC parameter value before the handover, which is the current parameter value in the source access network; the second parameter value is the QNC parameter value after the handover, which is the current parameter value in the target access network.

[0149] 2. The change from the second parameter value to the third parameter value.

[0150] The second and third parameter values ​​are both QNC parameters after the switch, with the third parameter value being acquired later than the second parameter value.

[0151] In summary, since the handover process is the most likely to cause rapid changes in the wireless network state, the method provided in this embodiment sends the control parameters of the QNC of the non-GBR bearer flow from the source access network to the target access network. This enables the target access network to send notification messages to the application entity and the terminal through the core network entity when the increase / decrease of the QNC parameters of the non-GBR bearer flow meets the reporting conditions. This allows the application entity to adjust its internal application to adapt to the parameter changes when the relevant parameters of the non-GBR bearer flow deteriorate or recover from poor to good, thereby optimizing the operation of the application and the terminal.

[0152] For example, during the handover process, the source access network sends QNC control parameters for non-GBR bearer flows to the target access network through core network entities. The type, number, and division of core network entities may differ in different communication systems. Taking a 5G system as an example, the core network entities include: a first core network entity (AMF) and a second core network entity (SMF). The process of the source access network sending QNC control parameters for non-GBR bearer flows to the target access network through core network entities may optionally include the following steps:

[0153] 1. During the handover process, the source access network sends a handover request (HandoverRequire) to the source first core network entity AMF. The handover request carries the control parameters of QNC.

[0154] 2. The source first core network entity AMF sends a UE context creation request (Namf_Communication_CreateUEContext) to the target first core network entity AMF. The UE context creation request carries the control parameters of QNC.

[0155] 3. The target first core network entity AMF sends an update session context request (Nsmf_PDUSession_UpdateSMContext) to the second core network entity SMF. The update session context request carries the control parameters of QNC.

[0156] 4. The second core network entity SMF sends an update session context response (Nsmf_PDUSession_UpdateSMContext response) to the target first core network entity AMF. The update session context response carries the control parameters of QNC.

[0157] 5. The target primary core network entity (AMF) sends a handover request to the target access network, which carries the control parameters of the QNC.

[0158] QNC control parameters can be carried in a source-to-end pass-through container. This source-to-end pass-through container contains fields passed through in handover requests, UE context creation requests, session context update requests, session context update responses, and handover commands.

[0159] Figure 4 This is a flowchart of a message sending method based on a handover process provided in an exemplary embodiment of this application. This embodiment applies this method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0160] Step 322: During the handover process, the source access network sends the control parameters of the QNC for the non-GBR bearer stream and the first parameter value to the target access network;

[0161] and Figure 3 Compared to the previous embodiment, the source access network not only sends the control parameters of the QNC to the target access network, but also sends the first parameter value to the target access network at the same time. The first parameter value is the parameter value of the QNC before the handover.

[0162] The control parameters and the first parameter value of QNC can be sent in the same message or in different messages. This application uses the example of sending the control parameters and the first parameter value of QNC in the same message to illustrate this.

[0163] For example, during the handover process, the source access network sends the QNC control parameters and the first parameter value of the non-GBR bearer flow to the target access network through core network entities. In different communication systems, the type, number, and division of core network entities may differ. Taking a 5G system as an example, the core network entities include: a first core network entity (AMF) and a second core network entity (SMF). The process of the source access network sending the QNC control parameters and the first parameter value of the non-GBR bearer flow to the target access network through core network entities may optionally include the following steps:

[0164] 1. During the handover process, the source access network sends a handover request to the source first core network entity (AMF), and the handover request carries the control parameters of the QNC;

[0165] 2. The source first core network entity AMF sends a UE context creation request to the target first core network entity AMF. The UE context creation request carries the control parameters of QNC and the first parameter value.

[0166] 3. The target first core network entity AMF sends an update session context request to the second core network entity SMF. The update session context request carries the control parameters of QNC and the value of the first parameter.

[0167] 4. The second core network entity SMF sends an update session context response to the target first core network entity AMF. The update session context response carries the control parameters of QNC and the value of the first parameter.

[0168] 5. The target first core network entity AMF sends a handover command to the target access network. The handover command carries the control parameters of QNC and the first parameter value.

[0169] Optionally, the QNC control parameters and the first parameter value are carried in the source-to-end transparent transmission container. The source-to-end transparent transmission container contains fields transparently transmitted in handover requests, UE context creation requests, session context update requests, session context update responses, and handover commands.

[0170] Step 342: During the handover process, the target access network receives the control parameters of the QNC and the value of the first parameter;

[0171] For example, in addition to the QNC control parameters sent by the source access network to the target access network, the handover command may also carry the QNC control parameters sent by the second core network entity SMF to the target access network.

[0172] The control parameters of the two sets of QNCs are carried in different fields of the handover command. For example, the control parameters of the QNC sent by the source access network to the target access network are carried in the source-to-end transparent container field of the handover command; the control parameters of the QNC sent by the second core network entity SMF to the target access network are carried in the QoS establishment request field of the handover command.

[0173] Normally, the control parameters of the two sets of QNCs are consistent. However, if there is a discrepancy between the control parameters of the two sets of QNCs, the target access network will preferentially use the control parameters of the QNC sent to the target access network by the second core network entity SMF.

[0174] Step 362: After the handover is completed, when the change from the first parameter value to the second parameter value of the target access network meets the reporting conditions, the core network entity sends a notification message to the application entity.

[0175] The first parameter value is the QNC parameter value before the switch, and the second parameter value is the QNC parameter value after the switch.

[0176] In summary, the method provided in this embodiment, by sending the first parameter value of the non-GBR bearer flow from the source access network to the target access network, enables the target access network to monitor the increase / decrease of the QNC parameters of the non-GBR bearer flow before and after handover. If the change of the QNC parameters before and after handover meets the reporting conditions, the target access network sends a notification message to the application entity and the terminal through the core network entity. This allows the application entity to adjust its internal application to adapt to the parameter change when the relevant parameters of the non-GBR bearer flow deteriorate or recover from poor to good, thereby optimizing the operation of the application and the terminal.

[0177] It should be noted that in some cases, the source access network or a device within the source access network may not support QNC for non-GBR bearer flows, while the target access network does support QNC for non-GBR bearer flows. This application also provides the following embodiments, such as... Figure 5 As shown:

[0178] Step 330: During the handover process, the core network entity sends the control parameters of the QNC for the non-GBR bearer flow to the target access network;

[0179] After receiving a handover request from the source access network, if the handover process involves the handover of non-GBR bearer flows, the core network entity can add QNC control parameters to the handover command.

[0180] For example, the SMF adds QNC control parameters to the QoS establishment request entry of the handover command. These QNC control parameters include: whether QNC is enabled, QNC parameters, and reporting conditions.

[0181] Step 342: During the handover process, the target access network receives control parameters from the QNC;

[0182] The target access network enables or initiates the QNC for non-GBR bearer flows based on the control parameters of the QNC.

[0183] Step 362: After the handover is completed, when the change between the second and third parameter values ​​of the target access network meets the reporting conditions, the core network entity sends a notification message to the application entity.

[0184] The second and third parameter values ​​are both QNC parameters after the switch, with the third parameter value being acquired later than the second parameter value.

[0185] In summary, the method provided in this embodiment, by sending QNC control parameters of non-GBR bearer flows from the core network entity to the target access network, can trigger the target access network to perform QNC control on non-GBR bearer flows even when the source access network does not support QNC for non-GBR bearer flows. Therefore, QNC control on non-GBR bearer flows can be introduced in handover scenarios where QNC parameters are most likely to change rapidly, thereby enhancing the control of applications and enabling applications to better adapt to network changes.

[0186] 2. QNC configuration process;

[0187] During the establishment or modification of non-GBR bearer flows, the core network entity performs QNC configuration to the (source) access network. That is, the core network entity sends QNC configuration to the (source) access network. The QNC configuration is used to configure the QNC parameters and reporting conditions (or change threshold, rapid change threshold, change reporting threshold, and rapid change reporting threshold).

[0188] Figure 6 This is a flowchart of a QNC configuration method provided in an exemplary embodiment of this application. This embodiment applies this method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0189] Step 420: The third core network entity PCF sends the QNC parameters and reporting conditions to the second core network entity SMF;

[0190] The third core network entity is the entity responsible for policy management within the core network.

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

[0192] For example, during the establishment or modification of a non-GBR bearer flow, the third core network entity PCF sends the QNC parameters and reporting conditions to the second core network entity SMF.

[0193] For example, during the establishment of a PDU session, a first QoS flow is established, which is called a QoS Flow with Default QoS Rules. Generally, this QoS flow is not of the GBR type, and the third core network entity can provide the QNC parameters and reporting conditions to the second core network entity.

[0194] For example, the parameters and reporting conditions of the QNC are determined by the third core network entity PCF itself; or, the parameters and reporting conditions of the QNC 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 UE's subscription data.

[0195] Step 440: The second core network entity SMF receives the PCC rules sent by the third core network entity PCF;

[0196] Step 460: The second core network entity sends a QNC profile to the access network. The QNC profile is used to configure the parameters and reporting conditions of the QNC to the access network.

[0197] In summary, the method provided in this embodiment can trigger the second core network entity to configure QNC parameters and reporting conditions for non-GBR bearer flows by sending QNC parameters and reporting conditions from the third core network entity to the second core network entity, thereby completing the QNC configuration process.

[0198] In one design, the application entity provides service flow information to the third core network entity. This service flow information carries the QNC parameters required (or suggested) by the application entity, as well as reporting conditions, such as... Figure 7 As shown. In another design, the third core network entity determines the parameters and reporting conditions of the QNC based on the QNC contract data, such as... Figure 8 As shown.

[0199] Figure 7 This is a flowchart of a QNC configuration method provided in another exemplary embodiment of this application. This embodiment applies this method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0200] Step 412: The application entity AF sends service flow information to the third core network entity PCF. The service flow information carries the control parameters of QNC.

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

[0202] Step 420: The third core network entity PCF sends PCC rules to the second core network entity SMF. The PCC rules carry the control parameters of QNC.

[0203] Step 440: The second core network entity SMF receives the PCC rules sent by the third core network entity PCF;

[0204] Step 460: The second core network entity sends QNC configuration to the access network. The QNC configuration is used to configure the control parameters of QNC to the access network.

[0205] In summary, the method provided in this embodiment enables active interaction between the application entity and the core network entity by providing QNC control parameters to the third core network entity. The application entity drives the radio access network (such as the RAN of 5G and 4G) to report rapid changes in non-GBR bearer flows, thereby opening up its network capabilities to the application entity and providing a new approach for the innovation of Internet applications.

[0206] Figure 8 This is a flowchart of a QNC configuration method provided in another exemplary embodiment of this application. This embodiment applies this method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0207] Step 414: The fourth core network entity UDM sends QNC subscription data to the third core network entity PCF. The QNC subscription data carries the control parameters of QNC.

[0208] If the default 5QI is of type NGBR, then QNC subscription data is added. 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.

[0209] Step 420: The third core network entity PCF sends the default QoS rule to the second core network entity SMF. The default QoS rule carries the control parameters of QNC.

[0210] Step 440: The second core network entity SMF receives the PCC rules sent by the third core network entity PCF;

[0211] Step 460: The second core network entity sends QNC configuration to the access network. The QNC configuration is used to configure the control parameters of QNC to the access network.

[0212] In summary, the method provided in this embodiment determines the control parameters of QNC based on the UE's subscription data by a third core network entity, which enables the 5G network to report rapid changes in non-GBR bearer flows to the AF and / or UE based on the UE's subscription data.

[0213] 3. The optimization process of QNC;

[0214] When the third core network entity PCF or application entity AF detects that QNC notification messages are too frequent, causing a large signaling load on the system, the PCF or AF should modify the QNC reporting conditions, such as increasing the change threshold.

[0215] Figure 9 This is a flowchart of an exemplary embodiment of the QNC optimization method provided in this application. This embodiment applies the method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0216] Step 520: When the reporting frequency of notification messages is greater than or less than the frequency threshold, the third core network entity PCF sends the updated control parameters of QNC to the second core network entity SMF.

[0217] The updated QNC control parameters include at least one of the following: whether QNC is enabled, the updated QNC parameters, and the updated change threshold. In other words, the updated QNC control parameters can update at least one of the following: enabling QNC, QNC parameters, and change threshold.

[0218] For example, when the reporting frequency of notification messages exceeds the frequency threshold, the third core network entity PCF sends an instruction to the second core network entity SMF to disable QNC; another example is that when the reporting frequency of notification messages exceeds the frequency threshold, the third core network entity PCF sends the reduced QNC parameters to the second core network entity SMF; yet another example is that when the reporting frequency of notification messages exceeds the frequency threshold, the third core network entity PCF sends the increased threshold to the second core network entity SMF.

[0219] Step 540: The second core network entity SMF sends the QNC configuration to the (target) access network. The QNC configuration carries the updated control parameters of the QNC.

[0220] In summary, the method provided in this embodiment can avoid causing significant signaling overhead to the system by sending updated QNC control parameters to the second core network entity SMF and the access network when the reporting frequency of notification messages is greater than or less than the frequency threshold, or by making reasonable use of the QNC notification mechanism.

[0221] Figure 10 This is a flowchart of a QNC optimization method provided in another exemplary embodiment of this application. This embodiment applies this method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0222] Step 510: When the reporting frequency of notification messages is greater than or less than the frequency threshold, the application entity sends the updated QNC control parameters to the third core network entity PCF.

[0223] The updated QNC control parameters include at least one of the following: whether QNC is enabled, the updated QNC parameters, and the updated change threshold. In other words, the updated QNC control parameters can update at least one of the following: enabling QNC, QNC parameters, and change threshold.

[0224] For example, when the reporting frequency of notification messages exceeds the frequency threshold, the AF sends an instruction to the third core network entity PCF to disable QNC; or, when the reporting frequency of notification messages exceeds the frequency threshold, the AF sends the reduced QNC parameters to the third core network entity PCF; or, when the reporting frequency of notification messages exceeds the frequency threshold, the AF sends an increased threshold to the third core network entity PCF.

[0225] Step 520: The third core network entity PCF sends the updated control parameters of QNC to the second core network entity SMF;

[0226] Step 540: The second core network entity SMF sends the QNC configuration to the access network. The QNC configuration carries the updated control parameters of the QNC.

[0227] In summary, the method provided in this embodiment can avoid causing significant signaling overhead to the system by having the PCF trigger the AF to send updated QNC control parameters to the second core network entity SMF and the access network when the reporting frequency of the notification message is greater than or less than the frequency threshold, or by making reasonable use of the QNC notification mechanism.

[0228] 4. QNC notification process (for AF):

[0229] Figure 11 This is a flowchart of a message sending method based on a handover process provided in an exemplary embodiment of this application. This embodiment applies this method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0230] Step 620: When the changes in the parameters of the QNC of the non-GBR bearer flow meet the reporting conditions, the (target) access network sends a notification message to the application entity through the core network entity.

[0231] For example, the notification message also carries the changed parameter values ​​of the QNC. That is, the current parameter values ​​of the QNC after a rapid change in the QNC parameters. This "current" is a relative concept, not an absolute one. For instance, the current parameter value is the value at the time the reporting condition is triggered, and may not be equal to the real-time parameter value after the notification message is sent.

[0232] There may be one or more core network entities. When a notification message involves multiple core network entities located between the RAN and AF, the multiple core network entities transmit the notification message sequentially. Different core network entities may use different types of messages to carry the notification message. For example, if the core network entities include: Mobility Management Entity (MME), Serving Gateway (SGW), PDN Gateway (PGW), and PCF, then the transmission path of the notification message will at least include RAN→MME→SGW / PGW→PCF→AF; or, for example, if the core network entities include: First Core Network Entity AMF, Second Core Network Entity SMF, and Third Core Network Entity PCF, then the transmission path of the notification message will at least include RAN→AMF→SMF→PCF→AF.

[0233] For example, a core network entity sends an event report to an application entity, which carries a notification message.

[0234] Step 640: The application entity controls the application based on the notification message.

[0235] This notification message (or rapid change notification, rapid change report, notification report) is used to indicate that changes in the parameters of the QoS Notification Control (QNC) for non-GBR bearer flows meet the reporting conditions.

[0236] The application entity controls at least one of the application's computation and traffic strategies based on notification messages to enable the application to adapt to rapid changes in relevant parameters of non-GBR bearer streams.

[0237] The first possible implementation:

[0238] In response to a notification message indicating a deterioration in the parameter value of QNC, the control application executes according to the first calculation strategy;

[0239] In response to a notification message indicating that the parameter value of QNC has improved, the control application executes according to the second calculation strategy;

[0240] Among them, the computation time of the same computational task under the first computational strategy is less than that under the second computational strategy.

[0241] Computation strategies are those related to the computational execution of an application. Computation strategies include, but are not limited to, at least one of the following: encoding / decoding method selection strategy, encoding / decoding model selection strategy, encoding / decoding level selection strategy, compression level selection strategy, and neural network model selection strategy.

[0242] Taking the selection of encoding / decoding methods as an example, in response to a notification message indicating a deterioration in the parameter value of the QNC, the application is controlled to use a first encoding / decoding method; in response to a notification message indicating an improvement in the parameter value of the QNC, the application is controlled to use a second encoding / decoding method. Here, "encoding / decoding" refers to at least one of encoding and decoding.

[0243] Among them, the computation time of the same encoding and decoding task under the first encoding and decoding strategy is less than that under the second encoding and decoding strategy.

[0244] For example, when PDR increases, although network latency increases, the application can compensate for the deterioration of network latency by reducing internal computation time, and can still ensure that the overall transmission latency remains unchanged or changes very little.

[0245] The second possible implementation:

[0246] In response to a notification message indicating a deterioration in the parameter value of QNC, the control application executes according to the first traffic policy;

[0247] In response to a notification message indicating that the parameter value of QNC has changed, the control application executes according to the second traffic strategy;

[0248] Wherein, the traffic of the first traffic strategy is less than the traffic of the second traffic strategy.

[0249] For example, application traffic includes voice packets and video packets;

[0250] In response to a notification message indicating a deterioration in QNC parameter values, maintain the first traffic for voice data packets and reduce the second traffic for video data packets; in response to a notification message indicating an improvement in QNC parameter values, maintain the first traffic for voice data packets and increase the second traffic for video data packets.

[0251] This is because cloud-based applications (video conferencing, voice conferencing, distance learning) typically require two-way interaction of video and audio. There are certain requirements for network transmission latency (usually one-way transmission latency <150ms). However, in actual use, due to changes in the wireless network status, the transmission latency of the wireless network may suddenly worsen or the transmission rate may suddenly decrease within a certain period (such as a 5-second interval), causing audio and video stuttering.

[0252] Related research shows that users are very sensitive to audio stuttering, but not so sensitive to changes in video quality (such as changes in resolution or clarity) (and temporarily turning off the video is acceptable as long as the audio is preserved). Audio generally doesn't stutter as frequently due to its smaller data transmission rate. However, if audio does stutter, the user experience is very poor. Furthermore, even if audio quality is reduced from CD quality to very low transmission rates (such as 2G voice transmission quality), as long as there is no stuttering, the user experience is still very good.

[0253] In summary, the method provided in this embodiment allows the application entity to adjust the application based on the changed QNC parameter values. This enables the application entity to adjust its internal application to adapt to the parameter changes when the relevant parameters of the non-GBR bearer stream deteriorate or recover from poor to good, thereby optimizing the operation of the application.

[0254] The method provided in this embodiment also compensates for the deterioration of network latency by changing the application's calculation strategy when the relevant parameters of the non-GBR bearer stream deteriorate, thereby reducing the computation time within the application and still ensuring that the overall transmission latency remains unchanged or changes very little.

[0255] The method provided in this embodiment also improves the user experience when the relevant parameters of the non-GBR bearer stream deteriorate by changing the application's traffic strategy, such as maintaining the traffic of voice data packets and reducing the traffic of video data packets. This avoids audio stuttering that has a significant impact on user experience.

[0256] 5. The QNC parameter value notification process (for UE);

[0257] Figure 12 This is a flowchart of a method for notifying the parameter value of QNC provided in an exemplary embodiment of this application. This embodiment applies this method to... Figure 1 or Figure 2 The following example illustrates the method using a communication system as shown.

[0258] Step 620: The core network entity receives a notification message from the access network. The notification message is used to indicate that the change of the QNC parameter of the non-GBR bearer flow meets the reporting conditions. The notification message carries the changed QNC parameter value.

[0259] Step 640: The core network entity sends the changed QNC parameter values ​​to the terminal;

[0260] Taking the core network entity SMF as an example, after receiving the notification message from the access network, the SMF sends the changed QNC parameter values ​​to the UE.

[0261] As an illustration, if the SMF does not receive a new PCC rule from the PCF within a predetermined time after receiving the notification message, it sends the changed QNC parameter value to the terminal.

[0262] Indicatively, if the SMF receives a new PCC rule from the PCF within a predetermined time after receiving the notification message, and the new PCC rule does not modify the QoS configuration, it sends the changed QNC parameter values ​​to the terminal.

[0263] The modified QCQNC parameter values ​​are transparently transmitted from the core network entity to the terminal via the RAN. Optionally, the core network entity sends a NAS message to the UE, and the terminal receives the NAS message sent by the core network entity, which carries the modified QCQNC parameter values. Optionally, the core network entity sends a PDU session modification command to the terminal, and the terminal receives the PDU session modification command sent by the core network entity, which carries the modified QCQNC parameter values.

[0264] Step 660: The terminal controls the application based on the changed QNC parameter values.

[0265] The UE controls at least one of the application's calculation strategy and traffic strategy based on the changed QNC parameter values, so that the application can adapt to the rapid changes in the relevant parameters of the non-GBR bearer flow.

[0266] The first possible implementation:

[0267] In response to the deterioration of the changed QNC parameter value, the control application executes according to the first calculation strategy;

[0268] In response to the improved parameter value of the changed QNC, the control application executes according to the second calculation strategy;

[0269] Among them, the computation time of the same computational task under the first computational strategy is less than that under the second computational strategy.

[0270] Computation strategies are those related to the computational execution of an application. Computation strategies include, but are not limited to, at least one of the following: encoding / decoding method selection strategy, encoding / decoding model selection strategy, encoding / decoding level selection strategy, compression level selection strategy, and neural network model selection strategy.

[0271] Taking the selection of encoding / decoding methods as an example, in response to a deterioration in the parameter value of the changed QNC, the control application uses a first encoding / decoding method; in response to an improvement in the parameter value of the changed QNC, the control application uses a second encoding / decoding method. Here, "encoding / decoding" refers to at least one of encoding and decoding.

[0272] Among them, the computation time of the same encoding and decoding task under the first encoding and decoding strategy is less than that under the second encoding and decoding strategy.

[0273] For example, when PDR increases, although network latency increases, the application can compensate for the deterioration of network latency by reducing internal computation time, and can still ensure that the overall transmission latency remains unchanged or changes very little.

[0274] The second possible implementation:

[0275] In response to the deterioration of the changed QNC parameter value, the control application executes according to the first flow strategy;

[0276] In response to the improved parameter values ​​of the changed QNC, the control application executes according to the second traffic strategy;

[0277] Wherein, the traffic of the first traffic strategy is less than the traffic of the second traffic strategy.

[0278] For example, application traffic includes voice packets and video packets;

[0279] In response to a worsening of the changed QNC parameter values, the first traffic corresponding to voice data packets is maintained, while the second traffic corresponding to video data packets is reduced; in response to a betterning of the changed QNC parameter values, the first traffic corresponding to voice data packets is maintained, while the second traffic corresponding to video data packets is increased.

[0280] This is because cloud-based applications (video conferencing, voice conferencing, distance learning) typically require two-way interaction of video and audio. There are certain requirements for network transmission latency (usually one-way transmission latency <150ms). However, in actual use, due to changes in the wireless network status, the transmission latency of the wireless network may suddenly worsen or the transmission rate may suddenly decrease within a certain period (such as a 5-second interval), causing audio and video stuttering.

[0281] Related research shows that users are very sensitive to audio stuttering, but not so sensitive to changes in video quality (such as changes in resolution or clarity) (and temporarily turning off the video is acceptable as long as the audio is preserved). Audio generally doesn't stutter as frequently due to its smaller data transmission rate. However, if audio does stutter, the user experience is very poor. Furthermore, even if audio quality is reduced from CD quality to very low transmission rates (such as 2G voice transmission quality), as long as there is no stuttering, the user experience is still very good.

[0282] In summary, the method provided in this embodiment allows the UE to adjust its application based on the changed QNC parameter values. This enables the UE to adapt its internal application to the parameter changes when the relevant parameters of the non-GBR bearer flow deteriorate or recover from poor to good, thereby optimizing the operation of the application.

[0283] The method provided in this embodiment also compensates for the deterioration of network latency by changing the application's calculation strategy when the relevant parameters of the non-GBR bearer stream deteriorate, thereby reducing the computation time within the application and still ensuring that the overall transmission latency remains unchanged or changes very little.

[0284] The method provided in this embodiment also improves the user experience when the relevant parameters of the non-GBR bearer stream deteriorate by changing the application's traffic strategy, such as maintaining the traffic of voice data packets and reducing the traffic of video data packets. This avoids audio stuttering that has a significant impact on user experience.

[0285] The above process will be explained in more detail below using the communication protocol (TS23.502) of the Third Generation Partnership Project (3GPP). For detailed information on network element names, steps, and descriptions in the following diagrams, please refer to TS23.502.

[0286] The relevant descriptions can be found in (https: / / www.3gpp.org / ftp / Specs / archive / 23_series / 23.502). Due to space limitations, this article focuses on the differences between the embodiments of this application and the TS23.502 protocol.

[0287] 1. QNC notification process:

[0288] When the network where the UE is located changes, i.e., the base station detects a rapid change in radio resources (improvement or deterioration), the RAN triggers the QNC notification process when this change reaches the change threshold defined by the QNC, sending a notification message to the AF. Optionally, this notification message carries the parameter values ​​of the changed QNC parameters (current parameter values). The base station first sends the notification message to the SMF, then the SMF sends the notification message to the PCF, and the PCF then sends the notification message to the AF.

[0289] 1.1 Non-roaming and local roaming scenarios:

[0290] Figure 13 This illustration shows a schematic diagram of a UE or network-requested PDU session modification (for non-roaming and local roaming) process provided in an exemplary embodiment of this application.

[0291] In 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.

[0292] When the parameters of the QNC in a non-GBR bearer stream meet the reporting conditions, these two messages carry a notification message. Optionally, the notification message also carries the transformed parameter values ​​of the QNC.

[0293] In step 2, the SM initiates the SM policy association modification process and sends notification messages to the PCF and AF.

[0294] In step 5, the SM sends a PDU session modification command to the UE, sending the changed QNC parameter values ​​to the UE.

[0295] For example, after the SM receives the notification message for a period of time, if the SMF does not receive a new PCC Rule from the PCF or the PCC Rule received does not modify the QoS aspect of the PCC Rule for the SDF corresponding to the QNC, the SMF initiates a PDU session modification command to the UE, notifying the UE of the parameter values ​​(PDB, PER, CBR) of the current QCQNC of the QFI corresponding to the current QNC.

[0296] In step 9, the UE responds with a PDU session modification confirmation.

[0297] Among them, the PDU session modification command and PDU session modification confirmation are transparently transmitted between the UE and SMF through the RAN.

[0298] The SM policy association modification process shown in step 2 above is as follows: Figure 14 Definition. For example... Figure 14 As shown:

[0299] In step 1, the SMF sends an Npcf_SMPolicyControl_Update request to the PCF, which carries a notification message.

[0300] In step 2, the PCF sends an event report Npcf_PolicyAuthorizationNotify request to the AF, which carries a notification message.

[0301] 1.2 NG-RAN handover scenario based on Xn interface:

[0302] Figure 15 This illustration shows a schematic diagram of an Xn-based inter-NG-RAN handover process without UPF reallocation provided by an exemplary embodiment of this application.

[0303] During the handover process, the source NG-RAN sends the control parameters of the QNC on the source side of the non-GBR bearer stream and the first parameter value of the QNC to the target NG-RAN, which is the current parameter value of the QNC before the handover.

[0304] In step 1, the target NG-RAN sends an N2 path handover request to the AMF. This request carries a notification message, which may optionally carry the parameter value (second parameter value) of the QNC after the handover.

[0305] After a UE successfully hands over to the target NG-RAN, since the resource status of the target NG-RAN is necessarily different from that of the source NG-RAN, the target NG-RAN determines whether a notification message needs to be reported. If reporting is required, the parameter values ​​of the QNC on the target NG-RAN after the change can be included in the QoSFlowAcceptedItem field of the N2 path handover request. The message structure of the N2 path handover request is as follows: Figure 16 As shown.

[0306] In step 2, the AMF sends an Nsmf_PDUSession_UpdateSMContext request to the SMF. This request carries a notification message, which may optionally carry the parameter value of the switched QNC (the second parameter value).

[0307] Subsequently, based on SMF Figure 13 and Figure 14 The process shown will report the notification message to both the PCF and the AF.

[0308] 1.3 N2 handover scenario based on NG-RAN nodes:

[0309] Figure 17This illustration shows an N2 handover process based on an NG-RAN node provided in an exemplary embodiment of this application.

[0310] In step 5, the target NG-RAN sends a handover notification to the target AMF. The handover notification carries a notification message, which may optionally carry the parameter value (second parameter value) of the QNC on the target NG-RAN after the handover.

[0311] When a UE successfully hands over to the target NG-RAN, since the resource status of the target NG-RAN is necessarily different from that of the source NG-RAN, the target NG-RAN determines whether a notification message needs to be reported. If reporting is required, the notification message can be included in the handover notification.

[0312] In step 7, the AMF sends an Nsmf_PDUSession_UpdateSMContext request to the SMF. This request carries a notification message, which may optionally carry the parameter value (second parameter value) of the switched QNC.

[0313] Subsequently, based on SMF Figure 13 and Figure 14 The process shown will report the notification message to both the PCF and the AF.

[0314] 2. QNC configuration process;

[0315] 2.1 PDU session establishment scenarios for non-roaming and local roaming:

[0316] Figure 18 This illustration shows a schematic diagram of a UE-requested PDU session establishment process provided in an exemplary embodiment of this application.

[0317] In steps 7b and 9, the PCF sends an SM policy association establishment response message to the SMF, or a response message regarding the SMF initiating an SM policy association modification, which carries the control parameters of the QNC.

[0318] During the establishment of a PDU session, a QoS flow (usually the first one) is created. This QoS flow is called a QoS flow based on the default QoS rules (no longer similar to the default bearer in 4G; 5G no longer uses the default QoS flow for naming).

[0319] Generally, if the default QoS rule is not of the GBR type, then the PCF can include QNC control parameters in the PCC rule. Figure 18 In step 7b or 9, if the 5QI in the Default QoS Rule provided by the PCF is of type NGBR, the PCF can provide the SMF with the control parameters of QCQNC.

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

[0321] Optionally, the UE's subscription data includes default 5QI and default ARP. If the default 5QI is of type NGBR, then QNC subscription data is added.

[0322] In steps 4, 7b, and 9, the UDM provides a message containing QNC subscription data to the SMF, the SMF then provides the QNC subscription data to the PCF, and the PCF then provides the default QoS rules containing the control parameters for QNC.

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

[0324] It should be noted that there may be multiple non-GBR QoS flows being processed here.

[0325] It should be noted that the SM-related parameters in the N2 message of step 12 are included in step 11, therefore the QNC control parameters are included in step 11.

[0326] 2.2 Home Roaming Scenarios:

[0327] Figure 19 A flowchart illustrating a PDU session establishment process for a UE request in a home-roaming scenario, provided by an exemplary embodiment of this application, is shown.

[0328] During the establishment of a PDU session, a QoS flow (usually the first one) is created. This QoS flow is called a QoS flow based on the default QoS rules (no longer similar to the default bearer in 4G; 5G no longer uses the default QoS flow for naming).

[0329] Generally, if the default QoS rule is not of the GBR type, then the PCF can include QNC control parameters in the PCC rule. Figure 19 In message 9b or 11, if the 5QI in the default QoS rule is not of type GBR, the PCF can provide QNC control parameters. Then, in messages 13, 14, and 15, QNC configuration is added.

[0330] Optionally, the UE's subscription data includes default 5QI and default ARP. If the default 5QI is of type NGBR, then QNC subscription data is added.

[0331] In steps 7, 9b, 11, the UDM provides the QNC subscription data to the SMF, 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.

[0332] 2.3 QoS flow establishment process triggered by AF, in non-roaming and local roaming scenarios:

[0333] Figure 20 This illustration shows a schematic diagram of the transfer of an AF request to a related PCF process for a single UE address, provided by an illustrative embodiment of this application. Figure 21 This illustration shows a schematic diagram of a PDU session modification process for non-roaming and locally diverted roaming UEs or networks, provided by an exemplary embodiment of this application.

[0334] exist Figure 20 Step 4: The AF sends an Npcf_PolicyAuthorization_Create / Update message to the PCF. This message includes QNC control parameters in the information of one or more media components. As mentioned earlier, if the media component contains QNC control parameters, it requests that the media be transmitted on NGBF; if the media component does not contain QCQNC parameters, it indicates that the media can be transmitted on either NGBF or GBF (GBR QoS Flow).

[0335] exist Figure 21 In step 1b, the PCF sends an Npcf_SMPolicyControlUpdateNotify request message. In this request message, QNC control parameters are added to the PCC rules of one or more SDFs (Service Data Flows, where one SDF corresponds to a media stream provided by the AF).

[0336] Correspondingly, in Figure 21 The messages in steps 3b and 4 carry control parameters including QNC.

[0337] 2.4 QoS flow establishment process triggered by AF, home route roaming scenario:

[0338] Figure 22 This illustration shows a schematic diagram of a PDU session modification process for a UE or network requesting home route roaming, provided by an exemplary embodiment of this application.

[0339] exist Figure 22 Steps 1b, 3, 4b, and 5 involve adding one or more QNC control parameters (i.e., for each possible service flow, SDF, QoS Flow).

[0340] exist Figure 22 Step 3 is relative to Figure 21 The new step in the scenario is to add QNC control parameters to the QoS parameters of one or more QoS flows.

[0341] 3. QoS notification during handover:

[0342] 3.1 Switching scenarios for the Xn interface:

[0343] Figure 23 A schematic diagram of a handover procedure within a base station provided in an exemplary embodiment of this application is shown. Figure 24 A schematic diagram of the Xn-based inter-NG-RAN handover process without UPF reallocation provided in this application is shown.

[0344] exist Figure 23 Step 1 involves adding QNC control parameters for non-GBR bearer flows. Since multiple QoS flows may exist within the same UE, for any QoS flow that has QNC control parameters at the source gNB, the QNC control parameters need to be provided to the target gNB.

[0345] The first parameter value is carried in the switching request, such as... Figure 25 The QoSFlowsToBeSetup-Item field shown is shown.

[0346] In addition, to support the subsequent QNC notification process, the source gNB also needs to report the parameter values ​​corresponding to each parameter of the current source-side QNC, i.e., the first parameter value. Thus, when the UE successfully hands over to the target gNB, the resource status of the target gNB may be much better or much worse than that of the source gNB. Therefore, after the UE successfully hands over to the target gNB, the target gNB can determine whether it can report the notification message.

[0347] 3.2 Handover preparation scenario based on XG-RAN node N2:

[0348] exist Figure 26 In steps 1, 3, 4, 7, and 9, QNC control parameters are added. Since there are multiple QFs, these parameters need to be provided for any QoS flow that has QNC control parameters at the source gNB. In fact, this process simply involves transmitting the QNC control parameters of all QoS flows on the source NG-RAN to the target NG-RAN through multiple steps.

[0349] Similarly, to support the subsequent QNC notification process, the source gNB also needs to report the values ​​of the current QNC parameters on the source side, i.e., the first parameter value. Thus, when the UE successfully hands over to the target gNB, the resource status of the target gNB is significantly better or worse than that of the source gNB. Therefore, after the UE successfully hands over to the target gNB, the target gNB can determine whether it can report the notification message. Therefore, steps 1, 3, 4, 7, and 9 in the left diagram add the current values ​​of the QNC parameters for all QoS flows on the source NG-RAN.

[0350] in, Figure 27 The message structure diagram of the source-to-end transparent container in the switching response is shown, and the first parameter value is carried in the source-to-end transparent container; Figure 28 The QoSFlowSetupRequestItem field in the switching request is shown; QNC control parameters can be carried in this request field.

[0351] 3.3 Switching from non-3GPP to 3GPP scenarios:

[0352] Figure 29 A schematic diagram is shown illustrating the handover process (non-roaming and local roaming) from an untrusted non-3GPP to a 3GPP access PDU session. Figure 30 A schematic diagram of the switch from EPC / ePDG to 5GS is shown.

[0353] from Figure 29 As can be seen, both the 5G non-3GPP and 4G non-3GPP handover to 5GS use the PDU session establishment process, which is defined in the above embodiments. Therefore, QNC processing during the non-3GPP to 3GPP handover can be implemented simply by reusing the above embodiments.

[0354] Figure 31 This illustrates the preparation phase for interoperability based on a single registration from EPS to 5GS.

[0355] The processing method in this embodiment is similar. Figure 26 Simply modify steps 2 and 3 to the response message in the 5G system. That is, when switching from 4G to 5GS, if 4G also supports QCQNC, some updates to the 4G protocol are required.

[0356] The method proposed in this application can also be applied to 4G systems. When applied to 4G systems, NR-gNB is replaced by eNB. The interaction between PCF and AF remains unchanged. The interaction between SMF and PCF is modified to be the interaction between PGW and PCF. 5G's QoSFlow is replaced by 4G's EPS Bearer. 5G's 5QI 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.

[0357] Figure 32 A block diagram of a message sending apparatus based on a handover process, provided in an exemplary embodiment of this application, is shown. The apparatus includes:

[0358] The sending module 820 is used to send the control parameters of the QNC of the non-GBR bearer flow to the target access network during the handover process, so that when the change of the parameter value of the QNC of the non-GBR bearer flow after the handover is completed meets the reporting conditions, the target access network sends a notification message to the application entity through the core network entity.

[0359] The control parameters of the QNC are used to indicate the parameters of the QNC and the reporting conditions of the non-GBR bearer stream.

[0360] In one possible design of this embodiment, the sending module 820 is used to send the control parameters of the QNC of the non-GBR bearer stream to the target access network through the core network entity during the handover process.

[0361] In one possible design of this embodiment, the sending module 820 is used to send a handover request to the core network entity during the handover process, the handover request carrying the control parameters of the QNC.

[0362] In one possible design of this embodiment, the control parameters of the QNC carry the source-to-end pass-through container field in the switching request.

[0363] In one possible design of this embodiment, the sending module 820 is used to send a first parameter value to the target access network during the handover process; so that when the change from the first parameter value to the second parameter value meets the reporting condition, the target access network sends a notification message to the application entity through the core network entity.

[0364] Wherein, the first parameter value is the parameter value of the QNC before the switch, and the second parameter value is the parameter value of the QNC after the switch.

[0365] In one possible design of this embodiment, the first parameter value carries the source-to-end pass-through container field in the switching request.

[0366] In one possible design of this embodiment, the parameters of the QNC include at least one of the following:

[0367] Packet Data Delay (PDR);

[0368] Packet error rate (PER)

[0369] Current bit rate (CBR).

[0370] In one possible design of this embodiment, the reporting conditions include at least one of the following:

[0371] The change in the parameter value of QNC within the first time period is greater than the first threshold.

[0372] The rate of change of the parameter value of QNC within the second time period is greater than the second threshold.

[0373] The parameter value of QNC changes by more than the first threshold during the first time period and remains at the third threshold.

[0374] The rate of change of the parameter value of QNC within the second time period is greater than the second threshold, and it remains at the fourth threshold.

[0375] Figure 33 A block diagram of a message sending apparatus based on a handover process, provided in an exemplary embodiment of this application, is shown. The apparatus includes:

[0376] The receiving module 920 is used to receive control parameters of the QNC of the non-GBR bearer stream during the handover process. The control parameters of the QNC are used to indicate the parameters of the QNC and the reporting conditions.

[0377] The sending module 940 is used to send a notification message to the application entity through the core network entity after the handover is completed, when the change in the parameter value of the QNC of the non-GBR bearer stream meets the reporting conditions.

[0378] In one possible design of this embodiment, the receiving module 920 is configured to receive control parameters of the QNC from the source access network during the handover process; and / or, during the handover process, receive control parameters of the QNC from the core network entity.

[0379] In one possible design of this embodiment, the receiving module 920 is used to receive a handover command sent by the core network device during the handover process, the handover command carrying control parameters of the QNC from the source access network.

[0380] In one possible design of this embodiment, the control parameters of the QNC from the source access network carry the source-to-end transparent container field in the handover command.

[0381] In one possible design of this embodiment, the receiving module 920 is used to receive a handover command sent by the core network device during the handover process, the handover command carrying control parameters of the QNC from the core network entity.

[0382] In one possible design of this embodiment, the control parameters of the QNC from the core network entity carry the QoS establishment request field in the handover command.

[0383] In one possible design of this embodiment, the method further includes:

[0384] In the event that the control parameters of the QNC from the source access network and the control parameters of the QNC from the core network entity are inconsistent, the control parameters of the QNC from the core network entity shall be used preferentially.

[0385] In one possible design of this embodiment, the receiving module 920 is used to receive a first parameter value of the source access network during the handover process;

[0386] The sending module 940 is used to send a notification message to the application entity through the core network entity after the handover is completed, when the change from the first parameter value to the second parameter value meets the reporting condition.

[0387] Wherein, the first parameter value is the parameter value of the QNC before the switch, and the second parameter value is the parameter value of the QNC after the switch.

[0388] In one possible design of this embodiment, the receiving module 920 is used to receive a first parameter value sent by the source access network during the handover process;

[0389] The sending module 940 is used to send a notification message to the application entity through the core network entity after the handover is completed, when the change from the first parameter value to the second parameter value of the target access network meets the reporting condition.

[0390] Wherein, the first parameter value is the parameter value of the QNC before the switch, and the second parameter value is the parameter value of the QNC after the switch.

[0391] Figure 34A schematic diagram of a network element device provided in one embodiment of this application is shown. For example, this network element device can be used to execute the control method of the above-described application program. Specifically, the network element device 3400 may include: a processor 3401, a receiver 3402, a transmitter 3403, a memory 3404, and a bus 3405.

[0392] The processor 3401 includes one or more processing cores, and the processor 3401 executes various functional applications and information processing by running software programs and modules.

[0393] The receiver 3402 and the transmitter 3403 can be implemented as a transceiver 3406, which can be a communication chip.

[0394] The memory 3404 is connected to the processor 3401 via the bus 3405.

[0395] The memory 3404 can be used to store computer programs, and the processor 3401 is used to execute the computer programs to implement the various steps performed by the network element device, access network entity, core network element or core network entity in the above method embodiments.

[0396] The transmitter 3403 is used to perform the transmission-related steps in the above embodiments; the receiver 3402 is used to perform the reception-related steps in the above embodiments; and the processor 3401 is used to perform other steps in the above embodiments besides the transmission and reception steps.

[0397] Furthermore, the memory 3404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices.

[0398] In an exemplary embodiment, a network element device is also provided, the network element device including: a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the message sending method based on the handover process as described above.

[0399] This application also provides a computer-readable storage medium storing at least one instruction, at least one program, code set, or instruction set, wherein the at least one instruction, the at least one program, the code set, or the instruction set is loaded and executed by a processor to implement the message sending method based on the switching process provided in the above method embodiments.

[0400] Optionally, this application also provides a computer program product comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the message sending method based on the switching process provided above.

[0401] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0402] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0403] The above description is merely an optional embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A message sending method based on a handover process, characterized in that, The method includes: During the handover process, the source access network sends the control parameters of the QNC of the non-GBR bearer flow to the target access network, so that when the change of the QNC parameter value of the non-GBR bearer flow after the handover is completed meets the reporting conditions, the target access network sends a notification message to the application entity through the core network entity. The control parameters of the QNC are used to indicate the parameters of the QNC for the non-GBR bearer stream and the reporting conditions.

2. The method according to claim 1, characterized in that, During the handover process, the source access network sends QNC control parameters for the non-GBR bearer flow to the target access network, including: During the handover process, the source access network sends the QNC control parameters of the non-GBR bearer flow to the target access network through the core network entity.

3. The method according to claim 2, characterized in that, During the handover process, the source access network sends the QNC control parameters of the non-GBR bearer flow to the target access network through the core network entity, including: During the handover process, the source access network sends a handover request to the core network entity, and the handover request carries the control parameters of the QNC.

4. The method according to claim 3, characterized in that, The control parameters of the QNC are carried in the source-to-end pass-through container field of the switching request.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: During the handover process, the source access network sends a first parameter value to the target access network; so that when the change from the first parameter value to the second parameter value meets the reporting condition, the target access network sends the notification message to the application entity through the core network entity. Wherein, the first parameter value is the parameter value of the QNC before the switch, and the second parameter value is the parameter value of the QNC after the switch.

6. The method according to claim 5, characterized in that, The first parameter value is carried in the source-to-end pass-through container field of the switching request.

7. The method according to any one of claims 1 to 6, characterized in that, The parameters of the QNC include at least one of the following: Packet Data Delay (PDR); Packet error rate (PER) Current bit rate (CBR).

8. The method according to any one of claims 1 to 6, characterized in that, The reporting conditions include at least one of the following: The change in the parameter value of QNC within the first time period is greater than the first threshold. The rate of change of the parameter value of QNC within the second time period is greater than the second threshold. The parameter value of QNC changes by more than the first threshold during the first time period and remains at the third threshold. The rate of change of the parameter value of QNC within the second time period is greater than the second threshold, and it remains at the fourth threshold.

9. A message sending method based on a handover process, characterized in that, The method includes: During the handover process, the target access network receives control parameters of the QNC for the non-GBR bearer stream. The control parameters of the QNC are used to indicate the parameters of the QNC and the reporting conditions. After the handover is completed, when the change in the parameter value of the QNC of the non-GBR bearer flow meets the reporting conditions, the target access network sends a notification message to the application entity through the core network entity.

10. The method according to claim 9, characterized in that, During the handover process, the target access network receives control parameters for the QNC of the non-GBR bearer stream, including: During the handover process, the target access network receives control parameters from the QNC of the source access network; And / or, during the handover process, the target access network receives control parameters of the QNC from the core network entity.

11. The method according to claim 10, characterized in that, During the handover process, the target access network receives control parameters from the source access network's QNC, including: During the handover process, the target access network receives a handover command sent by the core network equipment, the handover command carrying the control parameters of the QNC from the source access network.

12. A message sending device based on a handover process, characterized in that, The device includes: The sending module is used to send the control parameters of the QNC of the non-GBR bearer flow to the target access network during the handover process, so that when the change of the parameter value of the QNC of the non-GBR bearer flow after the handover is completed meets the reporting conditions, the target access network sends a notification message to the application entity through the core network entity. The control parameters of the QNC are used to indicate the parameters of the QNC for the non-GBR bearer stream and the reporting conditions.

13. A message sending device for a switching process, characterized in that, The device includes: The receiving module is used to receive control parameters of the QNC during the handover process. The control parameters of the QNC are used to indicate the parameters and reporting conditions of the QNC for non-GBR bearer streams. The sending module is used to send a notification message to the application entity through the core network entity after the handover is completed, when the change in the parameter value of the QNC of the non-GBR bearer stream meets the reporting conditions.

14. A network element device, characterized in that, The network element device includes a processor and a memory, the memory storing a computer program, the computer program being loaded and executed by the processor to implement the message sending method based on the handover process as described in any one of claims 1 to 11.

15. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that is loaded and executed by a processor to implement the message sending method based on a handover process as described in any one of claims 1 to 11.

Images