Service guarantee method and device, related equipment, storage medium and program product

Abstract

The invention provides a service guarantee method and device, related equipment, a storage medium and a program product, which are applied to the technical field of communication, and the method comprises the following steps: generating a target data packet detection rule PDR parameter adapted to a wireless network; and sending a target PDR parameter and a target quality of service (QoS) profile parameter to a second network element of the core network, the target PDR parameter not including a related field for performing data transmission by using the core network. In the method, the first network element of the core network generates the target PDR parameter adapted to the wireless network, and the target PDR parameter does not comprise related fields for data transmission by using the core network, so that the whole process from the data generation starting point to the data receiving end point is completed in the wireless network without depending on the intervention of the core network, and the data transmission efficiency is improved. Therefore, the wireless network can guarantee the service quality in the whole data transmission process.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a service assurance method, apparatus, related equipment, storage medium, and program product. Background Technology

[0002] In existing mobile communication systems, taking the New Radio (NR) technology of Fifth Generation Mobile Communications (5G) as an example, the Quality of Service (QoS) assurance scheme is as follows: The Session Management Function (SMF) sends Packet Detection Rules (PDR), QoS profiles, and QoS rules to the User Plane Function (UPF), base station, and User Equipment (UE) to complete end-to-end QoS configuration. Taking the downlink direction as an example, the service assurance scheme is as follows: The UPF completes the mapping from downlink Internet Protocol (IP) flow to QoS flow based on the PDR; the Service Data Adaptation Protocol (SDAP) layer of the base station completes the mapping from QoS flow to radio bearer based on the QoS profile; and the UE completes the mapping from radio bearer to IP flow based on the QoS rules.

[0003] However, future wireless networks will inherently support computing, data analysis, and sensing capabilities. Wireless networks will function as computing power closer to users, providing them with computing and other services. In this scenario, the wireless network needs to act as both the starting and ending point for data transmission related to computing services, ensuring the quality of the data stream during transmission. Current solutions only provide a partial link in data transmission QoS assurance and cannot achieve full QoS control and assurance throughout the entire computing service process. Summary of the Invention

[0004] This application provides a service assurance method and apparatus to solve the problem that existing wireless networks cannot complete QoS control and assurance for the entire computing service process.

[0005] To solve the above-mentioned technical problems, this application is implemented as follows:

[0006] In a first aspect, embodiments of this application provide a service assurance method, executed by a first network element of the core network, the method comprising:

[0007] Generate Target Packet Detection (PDR) parameters to adapt to the wireless network;

[0008] Send target PDR parameters and target QoS profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0009] Optionally, the target PDR parameters include at least one of the following fields:

[0010] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0011] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0012] Data identifier field.

[0013] Optionally, sending the target PDR parameters and the target QoS profile parameters to the second network element of the core network includes:

[0014] Send a service-oriented interface message or an N11 interface message carrying the target PDR parameters and target QoS profile parameters to the second network element of the core network.

[0015] Secondly, embodiments of this application provide a service assurance method, executed by a second network element of the core network, the method comprising:

[0016] The system receives target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0017] The target PDR parameters and the target QoS profile parameters are sent to the target base station.

[0018] Optionally, sending the target PDR parameters and the target QoS profile parameters to the target base station includes:

[0019] Send a service interface message or an N2 interface message carrying the target PDR parameters and the target QoS profile parameters to the target base station, wherein the service interface message or N2 interface message is any one of the following:

[0020] PDU session resource modification request;

[0021] PDU session resource establishment request;

[0022] Compute session resource modification requests;

[0023] Calculate the session resource establishment request;

[0024] Session resource modification request;

[0025] Session resource establishment request.

[0026] Optionally, the target PDR parameters include at least one of the following fields:

[0027] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0028] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0029] Data identifier field.

[0030] Thirdly, embodiments of this application provide a service assurance method, executed by a target base station, the method comprising:

[0031] The system receives target PDR parameters and target QoS profile parameters sent by a second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0032] Based on the target PDR parameters, the data stream is mapped to the Quality of Service (QoS) stream;

[0033] Based on the target QoS profile parameters, the QoS flow is mapped to the radio bearer.

[0034] Optionally, the target base station includes a first base station and a second base station, and the receiving of the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes:

[0035] The first base station and the second base station receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network;

[0036] The step of mapping the data stream to the QoS stream based on the target PDR parameters includes:

[0037] The first base station and the second base station map the data stream to the QoS stream according to the target PDR parameters;

[0038] The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes:

[0039] The first base station and the second base station map the QoS flow to the radio bearer according to the target QoS profile parameters.

[0040] Optionally, the target base station includes a first base station and a second base station, and the receiving of the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes:

[0041] The first base station receives the target PDR parameters and target QoS profile parameters sent by the second network element of the core network;

[0042] The step of mapping the data stream to the Quality of Service (QoS) stream based on the target PDR parameters includes:

[0043] The first base station sends the target PDR parameters and the target QoS profile parameters to the second base station;

[0044] The second base station maps the data stream to a QoS stream based on the target PDR parameters;

[0045] The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes:

[0046] The second base station maps the QoS flow to the radio bearer according to the target QoS profile parameters.

[0047] Optionally, the target base station includes a first base station and a second base station, and the receiving of the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes:

[0048] The first base station receives the target PDR parameters and target QoS profile parameters sent by the second network element of the core network;

[0049] The step of mapping the data stream to the Quality of Service (QoS) stream based on the target PDR parameters includes:

[0050] The first base station sends the target PDR parameters and the target QoS profile parameters to the second base station;

[0051] The first base station and the second base station map the data stream to a QoS stream according to the target PDR parameters;

[0052] The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes:

[0053] The first base station and the second base station map the QoS flow to the radio bearer according to the target QoS profile parameters.

[0054] Optionally, the first base station sends the target PDR parameters and the target QoS profile parameters to the second base station, including:

[0055] The first base station sends a preset interface message carrying the target PDR parameters and the target QoS profile parameters to the second base station. The preset interface message is a message defining the interface between the first base station and the second base station.

[0056] The preset interface message can be any of the following:

[0057] PDU session resource modification request;

[0058] PDU session resource establishment request;

[0059] Compute session resource modification requests;

[0060] Calculate the session resource establishment request;

[0061] Session resource modification request;

[0062] Session resource establishment request;

[0063] QoS flow control;

[0064] Xn / F1 / E1 Session establishment request;

[0065] Xn / F1 / E1 Session Modification Request.

[0066] Optionally, the target PDR parameters include at least one of the following fields:

[0067] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0068] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0069] Data identifier field.

[0070] Fourthly, embodiments of this application provide a service assurance system, which includes a first network element of the core network, a second network element of the core network, and a target base station;

[0071] The first network element is used to generate target PDR parameters for the adapted wireless network and send the target PDR parameters and target QoS profile parameters to the second network element.

[0072] The second network element is used to receive the target PDR parameters and the target QoS profile parameters sent by the first network element, and to send the target PDR parameters and the target QoS profile parameters to the target base station;

[0073] The target base station is used to receive the target PDR parameters and the target QoS profile parameters sent by the second network element, and to map the data stream to the QoS stream according to the target PDR parameters, and to map the QoS stream to the radio bearer according to the target QoS profile parameters.

[0074] The target PDR parameters do not include fields related to data transmission using the core network.

[0075] Fifthly, embodiments of this application provide a service assurance device applied to a first network element of a core network, the device comprising:

[0076] The first generation module is used to generate target packet detection rule (PDR) parameters adapted to wireless networks.

[0077] The first sending module is used to send target PDR parameters and target QoS profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0078] Sixthly, embodiments of this application provide a service assurance device applied to a second network element of a core network, the device comprising:

[0079] The first receiving module is used to receive the target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network;

[0080] The second sending module is used to send the target PDR parameters and the target QoS profile parameters to the target base station.

[0081] Seventhly, embodiments of this application provide a service assurance device applied to a target base station, the device comprising:

[0082] The second receiving module is used to receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network;

[0083] The first mapping module is used to map the data stream to the Quality of Service (QoS) stream according to the target PDR parameters.

[0084] The second mapping module is used to map QoS flows to radio bearers according to the target QoS profile parameters.

[0085] Eighthly, embodiments of this application provide a first network element of a core network, including a transceiver and a processor, wherein the processor is used for:

[0086] Generate Target Packet Detection (PDR) parameters to adapt to the wireless network;

[0087] The transceiver is used for:

[0088] Send target PDR parameters and target QoS profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0089] Ninthly, embodiments of this application provide a second network element for a core network, including a transceiver and a processor, wherein the transceiver is used for:

[0090] The system receives target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0091] The target PDR parameters and the target QoS profile parameters are sent to the target base station.

[0092] In a tenth aspect, embodiments of this application provide a target base station, including a transceiver and a processor, wherein the transceiver is used for:

[0093] The system receives target PDR parameters and target QoS profile parameters sent by the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0094] The processor is used for:

[0095] Based on the target PDR parameters, the data stream is mapped to the Quality of Service (QoS) stream;

[0096] Based on the target QoS profile parameters, the QoS flow is mapped to the radio bearer.

[0097] Eleventhly, embodiments of this application also provide an electronic device, including a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the above-described service assurance method.

[0098] In a twelfth aspect, embodiments of this application also provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the service assurance method described above.

[0099] In a thirteenth aspect, a computer program product is provided, including computer instructions that, when executed by a processor, implement the steps of the service assurance method described above.

[0100] The service assurance method of this application embodiment includes generating target packet detection rule (PDR) parameters adapted to the wireless network; sending the target PDR parameters and target quality of service (QoS) profile parameters to a second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network. In this method, the first network element of the core network generates the target PDR parameters adapted to the wireless network. Since the target PDR parameters do not include fields related to data transmission using the core network, the entire process from data generation to data reception is completed within the wireless network without relying on the intervention of the core network, thereby enabling the wireless network to ensure quality of service throughout the entire data transmission process. Attached Figure Description

[0101] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the 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.

[0102] Figure 1 This is one of the flowcharts of the service assurance method provided in the embodiments of this application;

[0103] Figure 2 This is a flowchart of data transmission provided in an embodiment of this application;

[0104] Figure 3 This is the second flowchart of the service assurance method provided in the embodiments of this application;

[0105] Figure 4 This is the third flowchart of the service assurance method provided in the embodiments of this application;

[0106] Figure 5 This is one of the schematic diagrams of the first base station and the second base station provided in the embodiments of this application;

[0107] Figure 6 This is a second schematic diagram of the first and second base stations provided in the embodiments of this application;

[0108] Figure 7 This is the fourth flowchart of the service assurance method provided in the embodiments of this application;

[0109] Figure 8 This is the fifth flowchart of the service assurance method provided in the embodiments of this application;

[0110] Figure 9 This is one of the structural diagrams of a service guarantee device provided in an embodiment of this application;

[0111] Figure 10 This is a second structural diagram of a service guarantee device provided in an embodiment of this application;

[0112] Figure 11 This is the third structural diagram of a service guarantee device provided in one embodiment of this application;

[0113] Figure 12 This is a structural diagram of a network device provided in an embodiment of this application. Detailed Implementation

[0114] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0115] This application provides a service assurance method, executed by a first network element in the core network. See also... Figure 1 , Figure 1This is a flowchart of the service assurance method provided in the embodiments of this application, such as... Figure 1 As shown, it includes the following steps:

[0116] Step 101: Generate Target Data Packet Detection Rule (PDR) parameters for the adapted wireless network;

[0117] In existing service assurance methods, base stations can only map data streams to appropriate radio bearer channels based on the QoS profiles issued by the core network. These QoS profiles determine the quality of service (e.g., priority, bandwidth requirements) that different types of data streams should enjoy. However, this service assurance method cannot complete QoS assurance and mapping in closed-loop wireless network data scenarios (i.e., data transmission occurs within the wireless network, with data flowing from user equipment to user equipment or from the base station to user equipment without passing through the core network or other intermediate nodes).

[0118] See Figure 2 The data transmission process described in this application involves the User Equipment (UE) sending the dataset requiring computation and processing, along with related algorithm files (i.e., the code or model used to process this data), to the wireless network. Upon receiving the dataset and algorithm files, the wireless network performs the actual computation and analysis internally or with the aid of edge computing nodes (such as servers near base stations). The data transmission process originates at the UE and terminates at the wireless network, respectively, without traversing the core network. PDR parameters play a crucial role in service assurance, defining how network data flows are processed and managed to ensure the performance requirements of various applications and services are met.

[0119] Therefore, in this step, the first network element of the core network, in order to generate QoS PDR parameters adapted to the wireless network, needs to delete or modify the fields related to data transmission using the core network in the original PDR parameters to obtain the target PDR parameters. The aforementioned first network element of the core network can be a Session Management Function (SMF).

[0120] Step 102: Send the target PDR parameters and the target QoS profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0121] In this network architecture, different core network functional nodes are responsible for specific tasks. In this mode, after the first network element of the core network generates the target PDR parameters, it needs to send the target PDR parameters and target QoS profile parameters to the second network element of the core network. Then, the second network element of the core network is responsible for transmitting the target PDR parameters and target QoS profile parameters to the base station. The second network element of the core network can be the Access and Mobility Management Function (AMF).

[0122] The aforementioned target QoS profile parameters are QoS parameters relevant to converged services or wireless network data closed-loop scenarios. Before the second network element in the core network is responsible for transmitting the target PDR parameters and target QoS profile parameters to the base station, the base station can send a QoS parameter retrieval request to the core network.

[0123] In one implementation, the first network element of the core network generates target PDR parameters adapted to the wireless network. These target PDR parameters do not include fields related to data transmission using the core network. Therefore, the entire process from the start of data generation to the end of data reception is completed within the wireless network without relying on the intervention of the core network. This enables the wireless network to guarantee service quality throughout the entire data transmission process.

[0124] Optionally, the target PDR parameters include at least one of the following fields:

[0125] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0126] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0127] Data identifier field.

[0128] In one implementation, the target PDR parameters generated by the first network element of the core network are modified from the original PDR parameters as follows, as shown in Table 1:

[0129] Table 1

[0130]

[0131]

[0132]

[0133] In traditional network architectures, the N4 interface is used for control plane communication between the first network element (which can be an SMF) and the UPF in the core network. However, when data processing is moved from the core network to the edge nodes of the wireless network (such as base stations), the N4 session identifier field needs to be modified accordingly. Furthermore, since the existing data transmission process does not require traversing the core network, the core network-related fields in the PDI packet detection information field also need to be removed.

[0134] In this embodiment, the target PDR parameters generated by the first network element of the core network do not include fields related to data transmission using the core network. Therefore, the entire process from the start of data generation to the end of data reception is completed within the wireless network without relying on the intervention of the core network, thereby enabling the wireless network to ensure service quality throughout the entire data transmission process.

[0135] Optionally, sending the target PDR parameters and the target QoS profile parameters to the second network element of the core network includes:

[0136] Send a service-oriented interface message or an N11 interface message carrying the target PDR parameters and target QoS profile parameters to the second network element of the core network.

[0137] In one implementation, the first network element of the core network sends target PDR parameters and target QoS profile parameters to the second network element of the core network through service-oriented interface messages or N11 interface messages, which conforms to the 3GPP standard definition and can ensure interoperability and compatibility between different vendors and systems.

[0138] This application provides a service assurance method, executed by a second network element in the core network. See also... Figure 3 , Figure 3 This is a flowchart of the service assurance method provided in the embodiments of this application, such as... Figure 3 As shown, it includes the following steps:

[0139] Step 301: Receive the target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network;

[0140] Step 302: Send the target PDR parameters and the target QoS profile parameters to the target base station.

[0141] In one implementation, after receiving the target PDR parameters and target QoS profile parameters sent by the first network element of the core network, the second network element of the core network then sends the target PDR parameters and target QoS profile parameters to the target base station in the wireless network architecture.

[0142] In this implementation, the second network element of the core network receives the target PDR parameters and target QoS profile parameters sent by the first network element of the core network, and then forwards the target PDR parameters and target QoS profile parameters to the target base station in the wireless network architecture. The target PDR parameters do not include fields related to data transmission using the core network; therefore, the entire process from data generation to data reception is completed within the wireless network without relying on the core network, enabling the wireless network to guarantee service quality throughout the entire data transmission process.

[0143] Optionally, sending the target PDR parameters and the target QoS profile parameters to the target base station includes:

[0144] Send a service interface message or an N2 interface message carrying the target PDR parameters and the target QoS profile parameters to the target base station, wherein the service interface message or N2 interface message is any one of the following:

[0145] PDU session resource modification request;

[0146] PDU session resource establishment request;

[0147] Compute session resource modification requests;

[0148] Calculate the session resource establishment request;

[0149] Session resource modification request;

[0150] Session resource establishment request.

[0151] In one implementation, the second network element of the core network sends target PDR parameters and target QoS profile parameters to the target base station through a service interface message or an N2 interface message. The N2 message can be a PDU session resource modify request, a PDU session resource setup request, a computation session resource modify request, a computation session resource setup request, a session resource modification request, or a session resource setup request.

[0152] In this implementation, the service interface or N2 interface is part of the 3GPP standardization organization. The second network element of the core network uses this interface to send target PDR parameters and target QoS profile parameters to the target base station, which can ensure compatibility and interoperability, thereby ensuring the stable operation of the existing network.

[0153] Optionally, the target PDR parameters include at least one of the following fields:

[0154] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0155] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0156] Data identifier field.

[0157] This embodiment can be referred to in the specific description of the foregoing embodiments, and will not be repeated here.

[0158] This application provides a service assurance method, executed by the target base station. See also... Figure 4 , Figure 4 This is a flowchart of the service assurance method provided in the embodiments of this application, such as... Figure 6 As shown, it includes the following steps:

[0159] Step 401: Receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network;

[0160] Step 402: Map the data stream to the Quality of Service (QoS) stream according to the target PDR parameters;

[0161] Step 403: Map the QoS flow to the radio bearer according to the target QoS profile parameters.

[0162] In one implementation, the target base station receives target PDR parameters and target QoS profile parameters sent by a second network element of the core network. Based on the target PDR parameters, it classifies these data flows into different QoS flows. This means that data with similar quality of service requirements are grouped together for the application of a unified QoS policy. Each QoS flow has an associated QoS profile, which includes quality of service requirements such as bandwidth, latency, and priority. The base station maps the QoS flows to appropriate radio bearers based on the QoS profile parameters. Radio bearers are logical channels used to transmit data between terminals and the network. This mapping ensures that each type of data flow receives the necessary network resources and priority processing to meet its quality of service requirements. In this implementation, the target base station can optimize resource allocation and scheduling decisions using this mapping relationship, thereby achieving efficient use of network resources. Furthermore, the target PDR parameters do not include fields related to data transmission using the core network. Therefore, the entire process from data generation to data reception is completed within the wireless network without relying on the core network, enabling the wireless network to guarantee quality of service throughout the entire data transmission process.

[0163] Optionally, the target base station includes a first base station and a second base station, and the receiving of the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes:

[0164] The first base station and the second base station receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network;

[0165] The step of mapping the data stream to the QoS stream based on the target PDR parameters includes:

[0166] The first base station and the second base station map the data stream to the QoS stream according to the target PDR parameters;

[0167] The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes:

[0168] The first base station and the second base station map the QoS flow to the radio bearer according to the target QoS profile parameters.

[0169] In one implementation, see Figure 5The first base station here can be understood as the main base station for Sixth Generation (6G) mobile communication technology. In addition to the existing communication connection control plane and user plane functions, the 6G main base station adds centralized (e.g., mobility management, paging management, QoS management on the core network side) and distributed (e.g., radio bearer management, paging, mobility management on the base station side) connection control functions for converged services (sensing, computing, AI, etc.), data transmission functions for converged services, and connectionless control functions such as computing control and data control, as well as connectionless execution functions such as computing execution and data execution. The second base station can be understood as the 6G slave base station. In addition to the existing communication connection control plane and user plane functions, the 6G slave base station adds distributed connection control functions for converged services, data transmission functions, and connectionless execution functions such as data execution and computing execution.

[0170] In this implementation, the first and second base stations utilize this mapping relationship to optimize resource allocation and scheduling decisions, thereby achieving effective use of network resources. Furthermore, the target PDR parameters do not include fields related to data transmission via the core network; therefore, the entire process from data generation to data reception is completed within the wireless network without relying on the core network, thus enabling the wireless network to guarantee service quality throughout the entire data transmission process.

[0171] Optionally, the target base station includes a first base station and a second base station, and the receiving of the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes:

[0172] The first base station receives the target PDR parameters and target QoS profile parameters sent by the second network element of the core network;

[0173] The step of mapping the data stream to the Quality of Service (QoS) stream based on the target PDR parameters includes:

[0174] The first base station sends the target PDR parameters and the target QoS profile parameters to the second base station;

[0175] The second base station maps the data stream to a QoS stream based on the target PDR parameters;

[0176] The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes:

[0177] The second base station maps the QoS flow to the radio bearer according to the target QoS profile parameters.

[0178] In one implementation, see Figure 6 The first base station can be understood as a centralized control base station, and the second base station as a distributed data base station. The centralized control base station provides all connection control functions, non-connection control functions such as computing control and data control, and non-connection execution functions such as computing execution and data execution. The distributed data base station provides user plane connection functions, as well as non-connection execution functions such as computing execution and data execution. Computation control includes computing node selection, multi-base station computing resource orchestration, and multi-task (sensing, AI, etc.) computing resource orchestration. Data control includes multi-base station data acquisition control, data transmission control, data processing control, and data storage management. Data execution functions include data storage, data transmission, data acquisition, and data processing. Computation execution functions include high-performance computing, mobile computing, personalized computing, AI model training, AI model inference, sensor data association, and deduplication.

[0179] In this implementation, the second base station utilizes this mapping relationship to optimize resource allocation and scheduling decisions, thereby achieving effective use of network resources. Furthermore, the target PDR parameters do not include fields related to data transmission via the core network; therefore, the entire process from data generation to data reception is completed within the wireless network without relying on the core network, thus enabling the wireless network to guarantee service quality throughout the entire data transmission process.

[0180] Optionally, the target base station includes a first base station and a second base station, and the receiving of the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes:

[0181] The first base station receives the target PDR parameters and target QoS profile parameters sent by the second network element of the core network;

[0182] The step of mapping the data stream to the Quality of Service (QoS) stream based on the target PDR parameters includes:

[0183] The first base station sends the target PDR parameters and the target QoS profile parameters to the second base station;

[0184] The first base station and the second base station map the data stream to a QoS stream according to the target PDR parameters;

[0185] The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes:

[0186] The first base station and the second base station map the QoS flow to the radio bearer according to the target QoS profile parameters.

[0187] In one implementation, the first base station can be understood as the primary base station, and the second base station as the secondary base station. The first base station receives the target PDR parameters and target QoS profile parameters sent by the second network element of the core network, and then sends the target PDR parameters and target QoS profile parameters to the second base station. Subsequently, the first and second base stations map the data stream to the QoS stream according to the target PDR parameters, and map the QoS stream to the radio bearer according to the target QoS profile parameters.

[0188] In this implementation, the first and second base stations utilize this mapping relationship to optimize resource allocation and scheduling decisions, thereby achieving effective use of network resources. Furthermore, the target PDR parameters do not include fields related to data transmission via the core network; therefore, the entire process from data generation to data reception is completed within the wireless network without relying on the core network, thus enabling the wireless network to guarantee service quality throughout the entire data transmission process.

[0189] Optionally, the first base station sends the target PDR parameters and the target QoS profile parameters to the second base station, including:

[0190] The first base station sends a preset interface message carrying the target PDR parameters and the target QoS profile parameters to the second base station. The preset interface message is a message defining the interface between the first base station and the second base station.

[0191] The preset interface message can be any of the following:

[0192] PDU session resource modification request;

[0193] PDU session resource establishment request;

[0194] Compute session resource modification requests;

[0195] Calculate the session resource establishment request;

[0196] Session resource modification request;

[0197] Session resource establishment request;

[0198] QoS flow control;

[0199] Xn / F1 / E1 Session establishment request;

[0200] Xn / F1 / E1 Session Modification Request.

[0201] In one implementation, the first base station can send target PDR parameters to the second base station via a preset interface message. The preset interface message can be any one of the following: PDU session resource modify request, PDU session resource setup request, QoS flow control, Xn / F1 / E1 session establishment request, Xn / F1 / E1 session modification request, computational session resource modification request, computational session resource setup request, session resource modification request, and session resource setup request. Specifically, the target base station can send the target PDR parameters to the second base station via the QoS flow level QoS parameter information element (QosFlowLevelQosParameters IE) field in the preset interface message.

[0202] In this implementation, the preset interface is part of the 3GPP standardization organization. The target base station uses this standard interface to send the target PDR parameters to the second base station, which can ensure compatibility and interoperability, thereby ensuring the stable operation of the existing network.

[0203] Optionally, the target PDR parameters include at least one of the following fields:

[0204] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0205] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0206] Data identifier field.

[0207] This embodiment can be referred to in the specific description of the foregoing embodiments, and will not be repeated here.

[0208] This application embodiment also provides a quality of service assurance system, which includes a first network element of the core network, a second network element of the core network, and a target base station;

[0209] The first network element is used to generate target PDR parameters for the adapted wireless network and send the target PDR parameters and target QoS profile parameters to the second network element.

[0210] The second network element is used to receive the target PDR parameters and the target QoS profile parameters sent by the first network element, and to send the target PDR parameters and the target QoS profile parameters to the target base station;

[0211] The target base station is used to receive the target PDR parameters and the target QoS profile parameters sent by the second network element, and to map the data stream to the QoS stream according to the target PDR parameters, and to map the QoS stream to the radio bearer according to the target QoS profile parameters.

[0212] The target PDR parameters do not include fields related to data transmission using the core network.

[0213] See Figure 7 , Figure 7 One of the flowcharts for executing a service assurance method for a service assurance system includes a first base station and a second base station as target base stations. When the first base station is a centralized control base station and the second base station is a distributed data base station, the specific flow of the service assurance method is as follows:

[0214] (1) The SMF generates target PDR parameters adapted to the wireless network and sends them to the second network element of the core network through a service interface message or an N11 interface message. In addition, when a base station providing converged services such as computing power and sensing sends a QoS parameter request to the core network, the SMF can send the target PDR parameters to the AMF through a service interface message or an N11 interface message, and at the same time, send the target QoS Profile parameters to the AMF.

[0215] (2) AMF pass-through: The target PDR parameters and target QoS Profile parameters are sent to the target base station through the N2 interface message.

[0216] (3) The first base station sends the target PDR parameters and target QoS Profile parameters to the second base station through the message defined by the interface between the first base station and the second base station. The second base station calculates the mapping of the relevant data stream to the QoS stream based on the target PDR parameters, and completes the mapping of the QoS stream to the Data Radio Bearer (DRB) based on the target QoS Profile parameters.

[0217] See Figure 8 , Figure 8The second flowchart for executing the service assurance method for the service assurance system, where the target base stations include a first base station and a second base station, and the first base station is the master base station and the second base station is the slave base station, is as follows:

[0218] (1) The SMF generates target PDR parameters adapted to the wireless network and sends them to the AMF via a service interface message or an N11 interface message. In addition, when a base station providing converged services such as computing power and sensing sends a QoS parameter request to the core network, the SMF can send the target PDR parameters to the second network element of the core network via a service interface message or an N11 interface message, and at the same time, send the target QoS Profile parameters to the AMF.

[0219] (2) AMF pass-through: PDR parameters and QoS parameters are sent to the first base station and the second base station through N2 interface messages.

[0220] (3) The first base station and the second base station complete the mapping of relevant data streams to QoS streams based on the target PDR parameters, and complete the mapping of QoS streams to data radio bearers (DRBs) based on the target QoS Profile parameters.

[0221] See Figure 9 , Figure 9 This is a structural diagram of a service assurance device provided in an embodiment of this application, which is applied to a first network element of the core network. Figure 9 As shown, the service support device 900 includes:

[0222] The first generation module 901 is used to generate target data packet detection rule (PDR) parameters adapted to wireless networks.

[0223] The first sending module 902 is used to send target PDR parameters and target quality of service (QoS) profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0224] Optionally, the target PDR parameters include at least one of the following fields:

[0225] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0226] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0227] Data identifier field.

[0228] Optionally, the first transmitting module includes:

[0229] The first sending unit is used to send a service interface message or N11 interface message carrying target PDR parameters and target QoS profile parameters to the second network element of the core network.

[0230] It should be noted that this embodiment is used as a reference for... Figure 1 For a detailed implementation of the corresponding device-side embodiment, please refer to [link / reference]. Figure 1 The related descriptions of the embodiments shown in the figure will not be repeated in this embodiment to avoid repetition, and the same beneficial effects can be achieved.

[0231] See Figure 10 , Figure 10 This is a structural diagram of a service assurance device provided in an embodiment of this application, which is applied to a second network element of the core network. Figure 10 As shown, the service support device 1000 includes:

[0232] The first receiving module 1001 is used to receive the target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network;

[0233] The second sending module 1002 is used to send the target PDR parameters and the target QoS profile parameters to the target base station.

[0234] Optionally, the second transmitting module includes:

[0235] The second sending unit is configured to send a service interface message or an N2 interface message carrying the target PDR parameters and the target QoS profile parameters to the target base station, wherein the service interface message or N2 interface message is any one of the following:

[0236] PDU session resource modification request;

[0237] PDU session resource establishment request;

[0238] Compute session resource modification requests;

[0239] Calculate the session resource establishment request;

[0240] Session resource modification request;

[0241] Session resource establishment request.

[0242] Optionally, the target PDR parameters include at least one of the following fields:

[0243] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0244] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0245] Data identifier field.

[0246] It should be noted that this embodiment is used as a reference for... Figure 3 For a detailed implementation of the corresponding device-side embodiment, please refer to [link / reference]. Figure 3 The related descriptions of the embodiments shown in the figure will not be repeated in this embodiment to avoid repetition, and the same beneficial effects can be achieved.

[0247] See Figure 11 , Figure 11 This is a structural diagram of a service assurance device provided in an embodiment of this application, which is applied to a target base station. Figure 11 As shown, the service support device 1100 includes:

[0248] The second receiving module 1101 is used to receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0249] The first mapping module 1102 is used to map the data stream to the Quality of Service (QoS) stream according to the target PDR parameters.

[0250] The second mapping module 1103 is used to map QoS flows to radio bearers according to the target QoS profile parameters.

[0251] Optionally, the target base station includes a first base station and a second base station, and the second receiving module includes:

[0252] The first receiving unit is used for the first base station and the second base station to receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network.

[0253] The first mapping module includes:

[0254] The first mapping unit is used by the first base station and the second base station to map the data stream to the QoS stream according to the target PDR parameters;

[0255] The second mapping module includes:

[0256] The second mapping unit is used by the first base station and the second base station to map QoS flows to radio bearers according to the target QoS profile parameters.

[0257] Optionally, the target base station includes a first base station and a second base station, and the second receiving module includes:

[0258] The second receiving unit is used for the first base station to receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network.

[0259] The first mapping module includes:

[0260] The third transmitting unit is used for the first base station to send the target PDR parameters and the target QoS profile parameters to the second base station;

[0261] The third mapping unit is used by the second base station to map the data stream to a QoS stream according to the target PDR parameters;

[0262] The second mapping module includes:

[0263] The fourth mapping unit is used by the second base station to map the QoS flow to the radio bearer according to the target QoS profile parameters.

[0264] Optionally, the second mapping unit is specifically used for:

[0265] The first base station sends a preset interface message carrying the target PDR parameters and the target QoS profile parameters to the second base station. The preset interface message is a message defining the interface between the first base station and the second base station.

[0266] The preset interface message can be any of the following:

[0267] PDU session resource modification request;

[0268] PDU session resource establishment request;

[0269] Compute session resource modification requests;

[0270] Calculate the session resource establishment request;

[0271] Session resource modification request;

[0272] Session resource establishment request;

[0273] QoS flow control;

[0274] Xn / F1 / E1 Session establishment request;

[0275] Xn / F1 / E1 Session Modification Request.

[0276] Optionally, the target PDR parameters include at least one of the following fields:

[0277] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0278] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0279] Data identifier field.

[0280] It should be noted that this embodiment is used as a reference for... Figure 4 For a detailed implementation of the corresponding device-side embodiment, please refer to [link / reference]. Figure 4 The related descriptions of the embodiments shown in the figure will not be repeated in this embodiment to avoid repetition, and the same beneficial effects can be achieved.

[0281] This application also provides a network device. Since the principle by which the network device solves the problem is similar to the service assurance method in this application, the implementation of this network device can refer to the implementation of the method, and repeated details will not be elaborated further. Figure 12 As shown, when the network device is the first network element of the core network, the first network element of the core network in this embodiment of the application includes: a processor 1200, used to read the program in the memory 1220 and execute the following processes:

[0282] Generate Target Packet Detection (PDR) parameters to adapt to the wireless network;

[0283] The processor 1200 is used to read the program in the memory 1220 and execute the following process: via transceiver 1210:

[0284] Send target PDR parameters and target QoS profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0285] Among them, Figure 12 In this context, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 1200) and memory (memory 1220). The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. A bus interface provides an interface. Transceiver 1210 may be multiple elements, including transmitters and transceivers, providing a unit for communicating with various other devices over a transmission medium. Processor 1200 is responsible for managing the bus architecture and general processing, and memory 1220 may store data used by processor 1200 during operation.

[0286] Optionally, the target PDR parameters include at least one of the following fields:

[0287] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0288] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0289] Data identifier field.

[0290] Optionally, the processor 1200 is configured to read the program from the memory 1220 and execute the following process via the transceiver 1210:

[0291] Send a service-oriented interface message or an N11 interface message carrying the target PDR parameters and target QoS profile parameters to the second network element of the core network.

[0292] In the case where the network device is the second network element of the core network, the second network element of the core network in this embodiment of the application includes: a processor 1200, configured to read a program from the memory 1220 and execute the following processes:

[0293] Processor 1200 is used to read the program from memory 1220 and execute the following procedures via transceiver 1210:

[0294] The system receives target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0295] The target PDR parameters and the target QoS profile parameters are sent to the target base station.

[0296] Optionally, the processor 1200 is configured to read the program from the memory 1220 and execute the following process via the transceiver 1210:

[0297] Send a service interface message or an N2 interface message carrying the target PDR parameters and the target QoS profile parameters to the target base station, wherein the service interface message or N2 interface message is any one of the following:

[0298] PDU session resource modification request;

[0299] PDU session resource establishment request;

[0300] Compute session resource modification requests;

[0301] Calculate the session resource establishment request;

[0302] Session resource modification request;

[0303] Session resource establishment request.

[0304] Optionally, the target PDR parameters include at least one of the following fields:

[0305] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0306] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0307] Data identifier field.

[0308] When the network device is the target base station, the target base station in this embodiment of the application includes: a processor 1200, configured to read a program from the memory 1220 and execute the following process: via transceiver 1210:

[0309] The system receives target PDR parameters and target QoS profile parameters sent by a second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

[0310] Processor 1200 is used to read the program from memory 1220 and execute the following procedures:

[0311] Based on the target PDR parameters, the data stream is mapped to the Quality of Service (QoS) stream;

[0312] Based on the target QoS profile parameters, the QoS flow is mapped to the radio bearer.

[0313] Optionally, the target base station includes a first base station and a second base station, and the processor 1200 is used to read the program in the memory 1220 and execute the following process: via transceiver 1210:

[0314] The first base station and the second base station receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network;

[0315] The processor 1200 is used to read the program in the memory 1220 and execute the following processes:

[0316] The first base station and the second base station map the data stream to the QoS stream according to the target PDR parameters;

[0317] The first base station and the second base station map the QoS flow to the radio bearer according to the target QoS profile parameters.

[0318] Optionally, the target base station includes a first base station and a second base station, and the processor 1200 is used to read the program in the memory 1220 and execute the following process: via transceiver 1210:

[0319] The first base station receives the target PDR parameters and target QoS profile parameters sent by the second network element of the core network;

[0320] The processor 1200 is used to read the program in the memory 1220 and execute the following processes:

[0321] The first base station sends the target PDR parameters and the target QoS profile parameters to the second base station;

[0322] The second base station maps the data stream to a QoS stream based on the target PDR parameters;

[0323] The second base station maps the QoS flow to the radio bearer according to the target QoS profile parameters.

[0324] Optionally, the processor 1200 is configured to read the program from the memory 1220 and execute the following process via the transceiver 1210:

[0325] The first base station sends a preset interface message carrying the target PDR parameters and the target QoS profile parameters to the second base station. The preset interface message is a message defining the interface between the first base station and the second base station.

[0326] The preset interface message can be any of the following:

[0327] PDU session resource modification request;

[0328] PDU session resource establishment request;

[0329] Compute session resource modification requests;

[0330] Calculate the session resource establishment request;

[0331] Session resource modification request;

[0332] Session resource establishment request;

[0333] QoS flow control;

[0334] Xn / F1 / E1 Session establishment request;

[0335] Xn / F1 / E1 Session Modification Request.

[0336] Optionally, the target PDR parameters include at least one of the following fields:

[0337] The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR;

[0338] The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field.

[0339] Data identifier field.

[0340] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the above-described service assurance method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0341] This application also provides a computer program product, including computer instructions, which, when executed by a processor, implement the above-described... Figure 1 , Figure 3 , Figure 4 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0342] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0343] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0344] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A service assurance method, characterized in that, The method, executed by the first network element of the core network, includes: Generate Target Packet Detection (PDR) parameters to adapt to the wireless network; Send target PDR parameters and target QoS profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

2. The method according to claim 1, characterized in that, The target PDR parameters include at least one of the following fields: The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR; The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field. Data identifier field.

3. The method according to claim 1, characterized in that, Sending the target PDR parameters and target QoS profile parameters to the second network element of the core network includes: Send a service-oriented interface message or an N11 interface message carrying the target PDR parameters and target QoS profile parameters to the second network element of the core network.

4. A service assurance method, characterized in that, The method, executed by a second network element of the core network, includes: The system receives target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network. The target PDR parameters and the target QoS profile parameters are sent to the target base station.

5. The method according to claim 4, characterized in that, Sending the target PDR parameters and the target QoS profile parameters to the target base station includes: Send a service interface message or an N2 interface message carrying the target PDR parameters and the target QoS profile parameters to the target base station, wherein the service interface message or N2 interface message is any one of the following: PDU session resource modification request; PDU session resource establishment request; Compute session resource modification requests; Calculate the session resource establishment request; Session resource modification request; Session resource establishment request.

6. The service assurance method according to claim 4, characterized in that, The target PDR parameters include at least one of the following fields: The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR; The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field. Data identifier field.

7. A service assurance method, characterized in that, Performed by the target base station, the method includes: The system receives target PDR parameters and target QoS profile parameters sent by a second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network. Based on the target PDR parameters, the data stream is mapped to the Quality of Service (QoS) stream; Based on the target QoS profile parameters, the QoS flow is mapped to the radio bearer.

8. The service assurance method according to claim 7, characterized in that, The target base station includes a first base station and a second base station. The process of receiving the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes: The first base station and the second base station receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network; The step of mapping the data stream to the QoS stream based on the target PDR parameters includes: The first base station and the second base station map the data stream to the QoS stream according to the target PDR parameters; The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes: The first base station and the second base station map the QoS flow to the radio bearer according to the target QoS profile parameters.

9. The service assurance method according to claim 7, characterized in that, The target base station includes a first base station and a second base station. The process of receiving the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes: The first base station receives the target PDR parameters and target QoS profile parameters sent by the second network element of the core network; The step of mapping the data stream to the Quality of Service (QoS) stream based on the target PDR parameters includes: The first base station sends the target PDR parameters and the target QoS profile parameters to the second base station; The second base station maps the data stream to a QoS stream based on the target PDR parameters; The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes: The second base station maps the QoS flow to the radio bearer according to the target QoS profile parameters.

10. The service assurance method according to claim 7, characterized in that, The target base station includes a first base station and a second base station. The process of receiving the target PDR parameters and target QoS profile parameters sent by the second network element of the core network includes: The first base station receives the target PDR parameters and target QoS profile parameters sent by the second network element of the core network; The step of mapping the data stream to the Quality of Service (QoS) stream based on the target PDR parameters includes: The first base station sends the target PDR parameters and the target QoS profile parameters to the second base station; The first base station and the second base station map the data stream to a QoS stream according to the target PDR parameters; The step of mapping QoS flows to radio bearers based on the target QoS profile parameters includes: The first base station and the second base station map the QoS flow to the radio bearer according to the target QoS profile parameters.

11. The method according to claim 9, characterized in that, The first base station sends the target PDR parameters and the target QoS profile parameters to the second base station, including: The first base station sends a preset interface message carrying the target PDR parameters and the target QoS profile parameters to the second base station. The preset interface message is a message defining the interface between the first base station and the second base station. The preset interface message can be any of the following: PDU session resource modification request; PDU session resource establishment request; Compute session resource modification requests; Calculate the session resource establishment request; Session resource modification request; Session resource establishment request; QoS flow control; Xn / F1 / E1 Session establishment request; Xn / F1 / E1 Session Modification Request.

12. The method according to claim 7, characterized in that, The target PDR parameters include at least one of the following fields: The session identifier field or radio bearer identifier field is used to identify the session or radio bearer associated with the PDR; The PDI packet detection information field includes at least one of the following: source interface field, user equipment (UE) Internet Protocol IP address, packet filter set, application identifier ID, and QoS flow identifier ID. The source interface field is used to identify uplink or downlink data, and the PDI packet detection information field does not include network instance field, core network tunnel information field, and Ethernet protocol data unit (PDU) session information field. Data identifier field.

13. A service assurance system, characterized in that, The service assurance system includes a first network element of the core network, a second network element of the core network, and a target base station; The first network element is used to generate target PDR parameters for the adapted wireless network and send the target PDR parameters and target QoS profile parameters to the second network element. The second network element is used to receive the target PDR parameters and the target QoS profile parameters sent by the first network element, and to send the target PDR parameters and the target QoS profile parameters to the target base station; The target base station is used to receive the target PDR parameters and the target QoS profile parameters sent by the second network element, and to map the data stream to the QoS stream according to the target PDR parameters, and to map the QoS stream to the radio bearer according to the target QoS profile parameters. The target PDR parameters do not include fields related to data transmission using the core network.

14. A service support device, characterized in that, The device, applied to the first network element of the core network, includes: The first generation module is used to generate target packet detection rule (PDR) parameters adapted to wireless networks. The first sending module is used to send target PDR parameters and target QoS profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

15. A service support device, characterized in that, The device, used as a second network element in the core network, includes: The first receiving module is used to receive the target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network; The second sending module is used to send the target PDR parameters and the target QoS profile parameters to the target base station.

16. A service support device, characterized in that, Applied to a target base station, the device includes: The second receiving module is used to receive the target PDR parameters and target QoS profile parameters sent by the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network; The first mapping module is used to map the data stream to the Quality of Service (QoS) stream according to the target PDR parameters. The second mapping module is used to map QoS flows to radio bearers according to the target QoS profile parameters.

17. A first network element of a core network, characterized in that, Includes transceivers and processors, among which, The processor is used to generate Target Packet Detection Rule (PDR) parameters adapted to wireless networks; The transceiver is used to send target PDR parameters and target QoS profile parameters to the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network.

18. A second network element of a core network, characterized in that, Includes a transceiver and a processor, the transceiver being used for: The system receives target PDR parameters and target QoS profile parameters sent by the first network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network. The target PDR parameters and the target QoS profile parameters are sent to the target base station.

19. A target base station, characterized in that, Includes a transceiver and a processor, the transceiver being used for: The system receives target PDR parameters and target QoS profile parameters sent by the second network element of the core network, wherein the target PDR parameters do not include fields related to data transmission using the core network. The processor is used for: Based on the target PDR parameters, the data stream is mapped to the Quality of Service (QoS) stream; Based on the target QoS profile parameters, the QoS flow is mapped to the radio bearer.

20. A network device, characterized in that, The method includes a processor, a memory, and a computer program stored in the memory and executable on the processor, wherein when executed by the processor, the computer program implements the steps of the service assurance method as described in any one of claims 1 to 3, or when executed by the processor, the computer program implements the steps of the service assurance method as described in any one of claims 4 to 6, or when executed by the processor, the computer program implements the steps of the service assurance method as described in any one of claims 7 to 12.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the service assurance method as described in any one of claims 1 to 3, or when executed by the processor, implements the steps of the service assurance method as described in any one of claims 4 to 6, or when executed by the processor, implements the steps of the service assurance method as described in any one of claims 7 to 12.

22. A computer program product, characterized in that, The method includes computer instructions that, when executed by a processor, implement the steps of the service assurance method as described in any one of claims 1 to 3, or when executed by the processor, implement the steps of the service assurance method as described in any one of claims 4 to 6, or when executed by the processor, implement the steps of the service assurance method as described in any one of claims 7 to 12.

Images