CN115515191A

CN115515191A - Private service quality management method, device, system and storage medium

Info

Publication number: CN115515191A
Application number: CN202110632576.XA
Authority: CN
Inventors: 孙干
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2021-06-07
Filing date: 2021-06-07
Publication date: 2022-12-23
Also published as: WO2022257379A1

Abstract

The embodiment of the application discloses a method, equipment, a system and a storage medium for managing the private service quality, which solve the technical problem that the existing standard QoS protocol cannot effectively meet the use requirement of a private network or a campus network. In this application, the private qos management method is applied to a multi-access edge computing MEC device, and includes: receiving Protocol Data Unit (PDU) session data and bearer control signaling data of user equipment transmitted by a base station, wherein the bearer control signaling data at least carries an initial quality of service (QoS) configuration file; determining the current network performance of the user equipment according to the PDU session data; and carrying out private QoS management on the user equipment according to the network performance and the initial QoS configuration file carried in the bearer control signaling data.

Description

Private service quality management method, device, system and storage medium

Technical Field

The embodiment of the application relates To the field of 5G enterprise oriented (ToB) scene communication, in particular To a private quality of service management method, device, system and storage medium.

Background

At present, the country actively promotes the 5G network construction, and the 5G life has arrived quietly. Due To the characteristics of large bandwidth, high reliability, low time delay and massive access of 5G, better experience is brought To traditional individual (To Customer, toC) oriented users, and the 5G intelligent ToB industry such as intelligent factories and intelligent parks is rapidly developed.

In order to adapt to the communication characteristics of the smart campus, the smart campus deploys its own private network (which may also be referred to as an intranet) in combination with a Multi-Access Edge Computing (MEC) technology in addition to accessing a public network. The MEC technology migrates the cloud computing platform from the interior of the mobile core network to the edge of the mobile access network, realizes the elastic utilization of computing and storage resources, and exploits the inherent capability of the wireless network to the maximum extent. The MEC service of the smart campus is focused on the connection and calculation capability, and is generally deployed between a core Network (5G core, 5gc) and a base station in a Radio Access Network (RAN) form, and serves as an entrance of a data "first hop" at a place closest to the campus, so that a good way is provided for creating a communication system special for the smart campus.

However, with the development of the ToB ecology of smart factories, smart docks, smart mines, and the like, various customized communication requirements make the Quality of Service (QoS) management in the current standard protocol unable to meet the requirements of user services, such as the critical station visual Quality inspection in a smart factory, requiring continuous uplink high definition video backhaul, and requiring extreme delay and packet loss rate, taking a smart grid as an example, requiring millisecond-level network delay, and having different and specific network requirements according to different services. These requirements, according to the mapping characteristics of QoS, generate a plurality of different QoS profiles (QoS profiles), which cannot be satisfied by the conventional network, not only because the current protocol does not have a suitable QoS Profile, but also because QoS is more a policy on the core network side, and the complex QoS parameters are deployed in the core network, which causes confusion of the public network.

Therefore, how to solve the problem that the standard QoS protocol cannot effectively meet the use requirement of the private network or the campus network becomes a technical problem which needs to be solved urgently.

Disclosure of Invention

An embodiment of the present application aims to provide a method, a device, a system, and a storage medium for managing private quality of service, which aim to solve the above technical problems.

In order to solve the foregoing technical problem, an embodiment of the present application provides a private quality of service management method, which is applied to a multi-access edge computing MEC device, where the private quality of service management method includes: receiving Protocol Data Unit (PDU) session data and bearer control signaling data of User Equipment (UE) transmitted by a base station, wherein the bearer control signaling data at least carries an initial quality of service (QoS) configuration file; determining the current network performance of the user equipment according to the PDU session data; and carrying out private QoS management on the user equipment according to the network performance and the initial QoS configuration file carried in the bearer control signaling data.

In order to solve the above technical problem, an embodiment of the present application further provides a private qos management method applied to a base station, where the private qos management method includes: acquiring Protocol Data Unit (PDU) session data and bearer control signaling data of user equipment, wherein the bearer control signaling data at least carries an initial quality of service (QoS) configuration file; determining whether the user equipment needs to perform private QoS management according to the identification information corresponding to the user equipment; if necessary, transmitting the PDU session data and the bearer control signaling data to a multi-access edge computing MEC device, so that the MEC device can perform private QoS management on the user equipment according to the initial QoS configuration file carried in the PDU session data and the bearer control signaling; otherwise, transmitting the PDU conversation data and the bearing control signaling to a public network.

To achieve the foregoing object, an embodiment of the present application further provides a private quality of service management device, including: a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform a private quality of service management method as described above for an MEC device or a private quality of service management method for a base station.

To achieve the above object, an embodiment of the present application further provides a private quality of service management system, including: a multi-access edge computing MEC device and a base station; the MEC equipment is used for executing the private quality of service management method applied to the MEC equipment; the base station is used for executing the private service quality management method applied to the base station.

In order to achieve the above object, an embodiment of the present application further provides a computer-readable storage medium storing a computer program. The computer program, when executed by a processor, implements a private quality of service management method as described above, applied to an MEC device, or a private quality of service management method applied to a base station.

According to the private QoS management method, the equipment, the system and the storage medium, the MEC equipment is deployed in a ToB service park, the MEC equipment is set to determine the network performance according to PDU session data of the user equipment received from the base station, and then the private QoS management is carried out on the user equipment according to the current network performance of the user equipment and an initial QoS configuration file in load control signaling data of the user equipment received from the base station. Since the MEC device is deployed in the campus, the private QoS management of the user device is performed in the campus, that is, the private service management scheme provided by the present application does not require to deploy complicated QoS parameters on the core network side, so that the private QoS management of the user device does not cause confusion of the public network.

In addition, the MEC equipment in the campus manages the private QoS of the user equipment according to the current network performance of the user equipment and the initial QoS configuration file in the bearer control signaling data of the user equipment received from the base station, so that the private QoS management of the user equipment can better conform to the private network corresponding to the campus, and the QoS of the user equipment is better guaranteed.

Drawings

One or more embodiments are illustrated by the corresponding figures in the drawings, which are not meant to be limiting.

Fig. 1 is a schematic structural diagram of a private quality of service management system provided in an embodiment of the present application;

fig. 2 is a schematic diagram of the interaction of MEC equipment, base stations and user equipment in the private quality of service relationship system shown in fig. 1;

fig. 3 is a schematic flowchart of a private service management method applied to an MEC device according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram of a specific flow for implementing private QoS management on user equipment according to an initial QoS configuration file carried in network performance and bearer control signaling data in the private service management method applied to the MEC device according to the embodiment of the present application;

fig. 5 is a schematic flowchart illustrating a private QoS guarantee preprocessing operation introduced in a private service management method applied to an MEC device according to an embodiment of the present disclosure;

fig. 6 is a flowchart illustrating a private service management method applied to a base station according to an embodiment of the present application;

fig. 7 is a schematic flowchart of private QoS management for a mobile device and a fixed device for a user equipment in a private service management method applied to a base station according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a private service management device according to an embodiment of the present application.

Detailed Description

In the embodiment of the present application, the term "and/or" describes an association relationship of associated objects, and means that there may be three relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In the embodiments of the present application, the term "plurality" means two or more, and other terms are similar thereto.

To make the objects, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. However, it will be appreciated by those of ordinary skill in the art that in the examples of the present application, numerous technical details are set forth in order to provide a better understanding of the present application. However, the technical solutions claimed in the present application can be implemented without these technical details and various changes and modifications based on the following embodiments. The following embodiments are divided for convenience of description, and should not constitute any limitation to the specific implementation manner of the present application, and the embodiments may be mutually incorporated and referred to without contradiction.

Referring to fig. 1, fig. 1 is a schematic structural diagram of a private service management system provided in an embodiment of the present application.

As shown in fig. 1, the private service management system provided in this embodiment includes: a base station 100 and MEC equipment 200.

For the base station 100, when implementing private quality of service management, the base station is specifically configured to obtain Protocol Data Unit (PDU) session Data and bearer control signaling Data of a user equipment, where the bearer control signaling Data at least carries an initial quality of service QoS configuration file; and determining whether the user equipment needs to perform private QoS management or not according to the identification information corresponding to the user equipment.

Correspondingly, if necessary, the base station 100 is further configured to transmit PDU session data and bearer control signaling data to the MEC device 200, so that the MEC device 200 performs private QoS management on the user equipment according to the initial QoS configuration file carried in the PDU session data and the bearer control signaling; otherwise, transmitting the PDU session data and the bearing control signaling to the public network.

For the MEC device 200, when implementing private QoS management, the MEC device is specifically configured to receive PDU session data and bearer control signaling data of a user equipment transmitted by the base station 100, where the bearer control signaling data at least carries an initial QoS configuration file; determining the current network performance of the user equipment according to the PDU session data; and carrying out private QoS management on the user equipment according to the network performance and the initial QoS configuration file carried in the bearer control signaling data.

In order to better understand how the base station 100 and the MEC device 200 in the private QoS management system provided in this embodiment cooperate to implement private QoS management on a user equipment, the following description is made in detail with reference to fig. 2:

(1) Private QoS profiles are designed in advance according to network requirements of each user equipment 300 of the ToB user, and are deployed to the base station 100 and the MEC equipment 200, so that the base station 100 and the MEC equipment 200 can complete protocol handshaking based on the same deployed private QoS profiles, that is, under the condition of establishing communication connection, the private QoS management on the user equipment 300 can be ensured to be normally performed.

Specifically, in an example, in order to deploy the pre-designed private QoS Profile to the base station 100 and the MEC device 200, a QoS Profile storage table may be deployed or newly created in respective storage areas of the base station 100 and the MEC device 200, and then the pre-designed private QoS Profile is added to the QoS Profile storage tables in the base station 100 and the MEC device 200, respectively.

For example, the QoS profile storage table in the MEC200 is referred to as a first QoS profile storage table, and the QoS profile storage table in the base station 100 is referred to as a second QoS profile storage table.

Accordingly, the QoS Profile stored in the first QoS Profile storage table may be referred to as a first QoS Profile, and the QoSProfile stored in the second QoS Profile storage table may be referred to as a second QoS Profile.

In addition, it is worth mentioning that in order to meet diversified service scenarios of the user equipment 300, network requirements of different service scenarios need to be considered as much as possible when designing a private QoS Profile, and then a plurality of QoS profiles are generated. That is, at least one first QoS Profile needs to be stored in the first QoS Profile storage table.

Accordingly, a second QoS Profile identical to the first QoS Profile needs to be stored in the second QoS Profile storage table.

In addition, in an example, the user equipment 300 may be a fixed device, such as a camera for a key station visual quality inspection in an intelligent factory, or a transceiver device disposed in a certain fixed area in a garden, which is not illustrated here, and the embodiment is not limited thereto.

In another example, the user device may also be a mobile device, such as a robot moving in a campus, an AGV cart implemented based on an Automated Guided Vehicle (AGV), and the like, which are not listed here, and the embodiment is not limited thereto.

In addition, in order to ensure that the private qos management scheme provided in this embodiment can be performed normally, each ue 300 in the campus needs to access a network, specifically, a 5G network in advance, and establish a bearer in a 5G core network (5G core, 5gc).

(2) After the ue 300 accesses the network, the base station 100 may obtain PDU session data and bearer control signaling data of the ue 300.

In this embodiment, the bearer control signaling data carries at least QoS Profile.

It is understood that, in one example, the QoS Profile includes a series of QoS characteristics and QoS parameters, such as Packet Error Rate (PER), priority (Priority Level), packet Delay Budget (PDB), and QoS parameters such as Allocation and Retention Priority (ARP), maximum Packet Loss Rate (Maximum Packet Loss Rate), 5G QoS Class Identifier (5G QoS Class Identifier, hereinafter referred to as 5 QI).

Furthermore, it is understood that The above-mentioned 5QI is specifically a scalar for indexing a 5G QoS feature, and The Third Generation Partnership Project (3 GPP) specifies 5QI values such as 5QI1 to 5QI9, 5QI65 to 5QI67, 5QI69, 5QI70, 5QI75, and 5QI79 to 5QI85 in Release 15, R15 protocol, and provides resource types of Guaranteed Bit Rate (GBR) and Non-Guaranteed Bit Rate (NGBR).

In an example, the GBR resource types include traffic scenarios such as remote control and augmented reality, and the NGBR resource types include traffic scenarios such as voice, conversational video, and game.

(3) The base station 100 determines whether the user equipment 300 needs to perform private QoS management according to the identification information corresponding to the user equipment 300.

Specifically, in this embodiment, the determining whether the user equipment 300 needs to perform private QoS management specifically means that, on the base station 100 side, the base station 100 identifies whether the currently acquired PDU session data and bearer control signaling data of the user equipment 300 are to be directly sent to a public network (also referred to as an external network) or a private network (also referred to as an enterprise network or an internal network) in a campus.

It should be noted that, in an example, the identification information for determining whether the user equipment needs to perform the private QoS management includes, but is not limited to, any one of a local network number, a network slice, an IP five-tuple, and a Domain Name System (DNS).

In addition, it can be preset which user equipments 300 need to perform private QoS management, for example, if the local network number of a certain number segment is set to need to perform private QoS management, the user equipments 300 accessing using these local network numbers need to perform private QoS management.

Further, as can be seen from the above description of (1), the user equipment 300 may be a fixed device or a mobile device. For the mobile device, when implementing the corresponding service, not only the network requirement of the mobile device is present, but also the network resource of other user equipment cannot be occupied when the external network environment changes, which requires that the MEC device not only consider the PDU session data and the initial QoS Profile of the mobile device, but also consider the current location information of the mobile device when performing the private QoS management on the mobile device.

Therefore, after identifying the user equipment 300 that needs to perform the private QoS management, the base station 100 needs to further identify whether the user equipment 300 is a mobile equipment.

Regarding how to identify that the ue 300 is a mobile device, taking the identification information corresponding to the ue as a local network number as an example, the ue 300 corresponding to the local network number of a certain number segment may be predefined as a mobile device.

When determining that the user equipment 300 currently needing the private QoS management is a mobile equipment, the base station 100 needs to locate the current location information of the mobile equipment based on a preset base station location technology, such as a time difference of arrival technology, and add the determined location information to the bearer control signaling data.

(4) The base station 100 transmits PDU session data and bearer control signaling data of the user equipment 300 that does not need to perform private QoS management to the public network, and transmits PDU session data and bearer control signaling data of the user equipment 300 that needs to perform private QoS management to the MEC equipment 200 deployed in the campus.

As can be seen from the above description, for the case that the user equipment 300 to be subjected to private QoS management is a mobile device, when the PDU session data and the bearer control signaling data are transmitted to the MEC device 200 deployed in the campus, the current location information of the user equipment 300 is also carried in the sent bearer control signaling data.

In addition, it should be noted that, when the base station 100 sends the PDU session data and the bearer control signaling data of the user equipment 300 to the public network, specifically, the PDU session data and the bearer control signaling data are sent to the 5GC through the transmission network, and then the 5GC sends the PDU session data and the bearer control signaling data to the Internet (Internet), that is, the PDU session data and the bearer control signaling data of the user equipment 300 interfacing the public network are sent to the public network according to the transmission path of the base station 100- > transmission network- >5GC- > Internet.

For PDU session data and bearer control signaling data of the user equipment 300 that needs to perform private QoS management, the base station 100 transmits directly to the MEC apparatus 200 deployed in the campus through the transport network.

(5) After receiving the PDU session data and the bearer control signaling data of the user equipment 300 transmitted by the base station 100, the MEC device 200 analyzes the PDU session data, and further determines the current network performance of the user equipment 300 according to the analysis result; the bearer control signaling data is analyzed, and then the initial QoS Profile carried in the bearer control signaling data and the current location information of the user equipment 300 are extracted (the user equipment can be analyzed if the user equipment is a mobile device).

(6) The MEC device 200 performs private QoS management on the user device 300 according to the determined network performance and the extracted initial QoS Profile and the current location information of the user device 300.

It should be noted that, in this embodiment, the private QoS management performed on the user equipment 300 is divided into two cases, i.e., adjusting the initial QoS Profile and not adjusting the initial QoS Profile.

Specifically, the MEC device 200 does not need to adjust the initial QoS Profile, if the network performance meets the preset threshold, that is, the initial QoS Profile is kept unchanged, and the PDU session data and the bearer control signaling data of the user equipment 300 are directly transmitted to the private network.

For the QoS Profile that needs to be adjusted, if the network performance does not meet the preset threshold, the MEC device 200 adjusts the initial QoS Profile as needed to obtain a target QoS Profile, and sends the target QoS Profile to the base station 100.

(7) The base station 100 receives a target QoS Profile issued by the MEC device 200, and guarantees the service of the user equipment 300 according to the target QoS Profile.

It should be noted that, in an example, PDU session data and bearer control signaling data that need to be guaranteed finally flow into the private network after passing through the above-mentioned guarantee procedure.

Furthermore, it is worth mentioning that, in order to implement the private QoS guarantee preprocessing for the continuous uplink or downlink service scenario (a certain user equipment in the campus is only used as an information sender or receiver, and can perform subsequent work without feedback from other user equipments during work), the MEC device 200 may determine the current service scenario of the user equipment 300 according to the received PDU session data of the user equipment 300 before adjusting the initial QoS Profile, then perform the private QoS guarantee preprocessing operation when determining that the current service scenario of the user equipment 300 is the continuous uplink or downlink service, and then perform the operation of adjusting the initial QoS configuration file after performing the private QoS guarantee preprocessing operation; on the contrary, if the current service scenario of the ue 300 is not the continuous uplink or downlink service, the operation of adjusting the initial QoS profile is directly performed.

The private QoS guarantee preprocessing operation described above specifically includes:

first, the MEC apparatus 200 generates scheduling indication information according to the current service scenario of the user equipment 300.

Specifically, the scheduling indication information in this embodiment carries parameters such as an index (which may be the above-mentioned identification information or a device number) of the ue 300, an uplink or downlink scheduling flag, a scheduling cycle time, and a scheduling packet size, which are not listed here one by one, and this embodiment is not limited thereto.

Then, the MEC apparatus 200 issues the scheduling indication information to the base station 100.

Then, the base station 100 negotiates with the user equipment 300 according to the scheduling indication information.

Specifically, after receiving the scheduling indication information, the base station 100 negotiates with the user equipment 300 according to the scheduling indication suggested by the MEC device 200, that is, according to the scheduling indication information, so as to remove a resource scheduling request flow of PDU session data and bearer control quality data generated in an uplink or downlink service after successful negotiation, and directly performs communication interaction with the base station 100 according to negotiated preset scheduling parameters, such as a preset period and a preset size of a data packet, thereby saving network resources to a great extent and using all network resources for effective data scheduling.

Next, the base station 100 reports the negotiation result to the MEC apparatus 200.

Specifically, if the negotiation result is that the negotiation is successful, the MEC device 200 starts to perform the above operation of adjusting the initial QoS Profile; otherwise, the scheduling indication information is sent to the base station 100 again, i.e. the above operation is executed again.

Therefore, in the private QoS management system provided in this embodiment, the MEC device is deployed in the park of the ToB service, and the MEC device is set to determine the network performance according to the PDU session data of the user equipment received from the base station, so as to perform private QoS management on the user equipment according to the current network performance of the user equipment and the initial QoS configuration file in the bearer control signaling data of the user equipment received from the base station. Since the MEC device is deployed in the campus, the private QoS management for the user device is performed in the campus, that is, the private service management scheme provided by the application does not need to deploy complex QoS parameters on the core network side, so that the private QoS management for the user device does not cause confusion of a public network.

In addition, the MEC equipment in the park manages the private QoS of the user equipment according to the current network performance of the user equipment and the initial QoS configuration file in the bearer control signaling data of the user equipment received from the base station, so that the private QoS management of the user equipment can better accord with the private network corresponding to the park, and the QoS of the user equipment is better guaranteed.

In addition, the MEC data distribution technology and the campus base station positioning technology are combined, the private QoS guarantee pretreatment is added to continuous uplink or downlink services, and customized private QoS management is provided for user equipment in a campus, so that the extreme requirements of different user equipment in the campus on network performances such as large flow bandwidth, network delay, false alarm rate and the like under different service scenes can be better met, and the method plays a promoting role in enterprise-based application of the 5G technology.

Referring to fig. 3, fig. 3 is a flowchart of a private quality of service management method provided in an embodiment of the present application, and in this embodiment, the method is mainly applied to an MEC device.

In addition, it should be noted that the MEC equipment described in this embodiment is specifically deployed in a campus.

As for the MEC device, it has a local off flow Function (TOF). Therefore, the MEC equipment can shunt the local business data to the private network based on the characteristic, so that the private data is prevented from leaving the campus, and the enterprise information leakage is avoided.

Meanwhile, the MEC equipment can calculate local service data, namely service data (PDU session data and bearer control signaling data) of user equipment in the campus do not need to be forwarded to a public network for calculation, but are processed at the enterprise edge, so that the end-to-end time delay of network transmission can be effectively reduced.

Based on these characteristics of the MEC device, the private quality of service management method provided by this embodiment is specifically described below with reference to fig. 3.

As shown in fig. 3, the private qos management method provided in this embodiment includes the following steps:

step 301, receiving protocol data unit PDU session data and bearer control signaling data of the ue transmitted by the base station.

Specifically, the 5G system mainly includes a user plane and a control plane. For the user plane, the data to be distributed is mainly PDU session data of the user equipment, that is, the user equipment specific transmission data. For the control plane, the data to be shunted is mainly bearer control signaling data for the user equipment to establish the PDU session.

It should be noted that the bearer control signaling data usually carries multiple information, but this embodiment focuses on the QoS configuration file carried in the bearer control signaling data when the PDU session is established. Therefore, at least the QoS configuration file needs to be carried in the bearer control signaling data of the user equipment received by the MEC device from the base station.

For convenience of description, in this embodiment, a QoS profile carried in bearer control signaling data acquired from the user equipment side is referred to as an initial QoS profile.

In an example, the initial QoS profile is specifically a QoS profile corresponding to a standard QoS protocol according to which the user equipment accesses the 5 GC.

Step 302, determining the current network performance of the user equipment according to the PDU session data.

In an example, the MEC device may determine the current network performance of the user equipment according to parameters such as a time delay between the analyzed data and the analyzed data, and/or an error rate between packets, and/or a maximum packet loss rate by analyzing the received PDU session data.

Step 303, according to the network performance and the initial QoS configuration file carried in the bearer control signaling data, performing private QoS management on the user equipment.

Specifically, if the network performance is good, or the index values meet a preset threshold, performing private QoS management on the user equipment, substantially keeping an initial QoS configuration file unchanged, and directly transmitting PDU session data and bearer control signaling data to the private network; if the network performance is abnormal or the index values do not meet the preset threshold value, the initial QoS configuration file is adjusted according to the private QoS management of the user equipment to obtain a target QoS configuration file, and the target QoS configuration file is issued to the base station so that the base station can guarantee the service of the user equipment according to the target QoS configuration file.

Furthermore, it can be understood that, since the user equipment may be a mobile device, for the case that the bearer control signaling data is from the mobile device, the MEC device may further consider the current location information of the user equipment carried in the bearer control signaling data when performing private QoS management on the user equipment according to the network performance and the initial QoS profile carried in the bearer control signaling data.

That is, for the user equipment being fixed equipment, the private QoS management can be performed on the user equipment only according to the initial QoS configuration file in the PDU session data and the bearer control signaling data; for the user equipment to be mobile, the user equipment needs to be privately QoS managed according to the initial QoS profile and the location information in the PDU session data, bearer control signaling data.

It is easy to find out through the above description that the private QoS management method provided in this embodiment deploys the MEC device in the ToB service park, sets the MEC device to determine the network performance according to the PDU session data of the user equipment received from the base station, and further performs private QoS management on the user equipment according to the current network performance of the user equipment and the initial QoS configuration file in the bearer control signaling data of the user equipment received from the base station. Since the MEC device is deployed in the campus, the private QoS management of the user device is performed in the campus, that is, the private service management scheme provided by the present application does not require to deploy complicated QoS parameters on the core network side, so that the private QoS management of the user device does not cause confusion of the public network.

Referring to fig. 4, fig. 4 is a flowchart of a private quality of service management method provided in an embodiment of the present application, and in this embodiment, the method is mainly applied to MEC equipment deployed in a campus.

As shown in fig. 4, the private qos management method provided in this embodiment includes the following steps:

step 401, receiving protocol data unit PDU session data and bearer control signaling data of the ue transmitted by the base station.

Step 402, determining the current network performance of the user equipment according to the PDU session data.

It is to be understood that

steps

401 and 402 in this embodiment are substantially the same as

steps

301 and 302 in the embodiment shown in fig. 3, and are not described herein again.

In step 403, it is determined whether the network performance satisfies a predetermined threshold.

Specifically, in this embodiment, the step of determining whether the network performance meets the preset threshold is to determine whether the user equipment needs to perform private QoS guarantee.

If the current network performance of the user equipment is determined not to meet the preset threshold value through judgment, executing a step 404; otherwise, step 405 is performed.

Step 404, determining a target QoS configuration file according to the initial QoS configuration file, and issuing the target QoS configuration file to the base station, so that the base station guarantees the service of the user equipment according to the target QoS configuration file.

Regarding the implementation of step 404, in one example, specifically:

first, before step 404 is executed, a first QoS configuration file storage table needs to be deployed in the MEC device in advance, and at least one first QoS configuration file is stored in the first QoS configuration file storage table; also, a second QoS profile storage table is deployed in the base station, and a second QoS profile identical to the first QoS profile is stored in the second QoS profile storage table.

It should be noted that, in this embodiment, the first QoS profile and the second QoS profile are predetermined according to the network requirement of the user equipment.

The manner of determining the first QoS profile and the second QoS profile may be determined by a skilled person through manual design, or may be determined based on a network model obtained through training of a preset machine learning algorithm.

Then, when step 404 is executed, according to the determined network performance, a 5QI corresponding to the first QoS profile is selected from the first QoS profile storage table, and the selected 5QI is used as the target QoS profile.

And finally, the target QoS configuration file is issued to the base station, so that the base station can position a second QoS configuration file corresponding to the 5QI from a second QoS configuration file storage table according to the QoS configuration file, and the service of the user equipment is guaranteed according to the second QoS configuration file.

For such an adjustment policy, since the first QoS profile stored in the first QoS profile storage table is not associated with the location information, the adjustment policy is suitable for the case where the user equipment is a fixed device.

That is, for the fixed device, first, a private QoS Profile, that is, the above-mentioned first QoS Profile and second QoS Profile, is pre-designed for different fixed devices according to their specific network requirements, for example, a 5QI value, such as 5QI100, which is not within the 3GPP protocol range is customized for the wireless video backhaul service, and under this new 5QI index value, according to the requirements of the fixed device for the video backhaul service, qoS characteristics, such as a targeted resource type (such as NGBR), a default priority (such as 19), a packet delay budget (PDB, such as 10 ms), a packet error rate (PER, such as 10-4), a maximum data burst (such as 1354 bytes), and the like, and corresponding QoS parameters are designed in a matching manner; and then deploying the designed private QoS profiles to a first QoS Profile of the MEC equipment and a second QoS Profile of the base station respectively. And then, after the fixed equipment is accessed to the network, transmitting the current initial QoS Profile to the base station through the bearer control signaling data, simultaneously transmitting the current PDU session data to the base station, transmitting the obtained PDU session data and the bearer control signaling data at least carrying the initial QoS Profile to the MEC equipment by the base station, and carrying out private QoS management on the user equipment by the MEC equipment according to the adjustment strategy when the current network state of the user equipment is determined not to meet the preset threshold value through analysis.

Regarding the implementation of step 404, in another example, specifically:

first, the QoS parameters to be changed are determined according to the PDU session data.

And then, adjusting the initial QoS configuration file according to the determined QoS parameters to obtain a target QoS configuration file.

And finally, issuing the target QoS configuration file to the base station, so that the base station can guarantee the service of the user equipment according to the target QoS configuration file.

Specifically, because the QoS Profile includes QoS characteristics and QoS parameters, and the QoS parameters include, but are not limited to, ARP, MPLR, 5QI, etc., if it is determined that the QoS parameter to be changed is ARP according to the PDU session data, the parameter value corresponding to the ARP in the initial QoS Profile is adjusted to the currently determined parameter value, so that the adjusted initial QoS Profile can be regarded as the target QoS Profile.

In addition, it should be noted that, in the adjustment policy given above, the adjustment of the initial QoS Profile is completed on the MEC device side, but in practical application, the operation of changing a certain QoS parameter in the initial QoS Profile may be performed on the base station side, so that the MEC device may issue QoS parameters to the base station after determining the QoS parameter to be changed, and the base station may adjust the initial QoS Profile according to the received QoS parameter.

For such adjustment policy, since the overall replacement of the initial QoS Profile is not involved, but only adjustment is performed on several QoS parameters in the initial QoS Profile, the adjustment policy does not limit the specific type of the user equipment, that is, the adjustment policy can be used for private QoS management by both the mobile device and the fixed device.

Compared with the mode that 5QI in the private QoS Profile is still designed in advance as an index, the QoS Profile is newly added or switched, and the adjustment strategy only changes a certain QoS parameter value in the initial QoS Profile, so that the base station can guarantee the user equipment more finely according to the obtained target QoS Profile.

For example, monitoring of a certain location in the campus is very important in a future period of time, the MEC device may issue an indication of modification of a certain QoS parameter in the initial QoS Profile of the device, taking QoS parameter ARP as an example, which defines the importance of a user equipment resource request, when system resources are limited, the ARP parameter determines whether a new QoS flow is accepted or rejected, and to ensure monitoring of important workstations, the MEC device may decide to modify the ARP parameter from a default value to the highest priority value of 1.

Regarding the implementation of step 404, in another example, specifically:

first, before step 404 is executed, a first QoS configuration file storage table needs to be deployed in the MEC device in advance, at least one first QoS configuration file is stored in the first QoS configuration file storage table, and a location information corresponding to each first QoS configuration file is set at the same time, that is, a corresponding relationship between each first QoS configuration file and each location information is established; also, a second QoS profile storage table is deployed in the base station, and a second QoS profile identical to the first QoS profile is stored in the second QoS profile storage table.

Then, when step 404 is executed, according to the location information of the user equipment carried in the bearer control signaling data, a first QoS configuration file corresponding to the location information of the user equipment is determined from the first QoS configuration file table, and a target QoS configuration file is obtained.

Next, a switching instruction is generated according to the target QoS profile.

And finally, issuing the switching instruction to the base station, so that the base station switches the QoS configuration file corresponding to the user equipment from the initial QoS configuration file to a second QoS configuration file corresponding to the first QoS configuration file according to the switching instruction, and guarantees the service of the user equipment according to the second QoS configuration file.

For such an adjustment policy, since the first QoS profile stored in the first QoS profile storage table is associated with the location information, the adjustment policy is more suitable for the case that the user equipment is a mobile device.

That is, for the mobile device, first, a private QoS Profile is pre-designed for different mobile devices according to their specific network requirements and network conditions around different location information, that is, the above-mentioned first QoS Profile and second QoS Profile, for example, for the wireless video backhaul service, a 5QI value that is not within the 3GPP protocol range, such as 5QI100, is customized, and under this new 5QI index value, according to the requirements of the mobile device for the video backhaul service, qoS characteristics such as a targeted resource type (such as NGBR), a default priority (such as 19), a packet delay budget (PDB, such as 10 ms), a packet error rate (PER, such as 10-4), a maximum data burst amount (such as 1354 bytes), and corresponding QoS parameters are designed in a matching manner; then, the designed private QoS profiles are respectively deployed to a first QoS configuration file of the MEC device and a second QoS configuration file of the base station, and when the first QoS configuration file is deployed to a first QoS configuration file storage table of the MEC device, a corresponding relationship between each first QoS configuration file and each location information needs to be established. After the mobile device is accessed to the network, transmitting the current initial QoS Profile to the base station through the bearer control signaling data, and simultaneously transmitting the current PDU session data to the base station, wherein the base station transmits the acquired PDU session data and the bearer control signaling data carrying the initial QoS Profile and the current position information of the mobile device to the MEC device, and the MEC device can perform private QoS management on the user device according to the adjustment strategy when determining that the current network state of the user device does not meet the preset threshold value through analysis.

For example, for a service scene in which the mobile device is an inspection robot, when the inspection robot reaches a device area, the MEC device issues a GBR-type QoS guarantee, and when the inspection robot enters a personnel area, the MEC device issues an NGBR-type QoS guarantee, that is, appropriate private QoS management is performed for the location where the inspection robot is located.

It should be understood that the above examples are only examples for better understanding of the technical solution of the present embodiment, and are not to be taken as the only limitation to the present embodiment.

In addition, it should be noted that, in an example, regardless of which adjustment policy is adopted, PDU session data and bearer control signaling data that need to be guaranteed finally flow into the private network after passing through the above-mentioned guarantee flow.

Step 405, keeping the initial QoS configuration file unchanged, and transmitting PDU session data and bearer control signaling data to the private network.

Therefore, the private QoS management method provided in this embodiment is based on the MEC TOF technology and combined with the campus base station positioning technology, so as to implement private QoS management on the user equipment in the campus, and when the private QoS management is performed on the user equipment, different adjustment strategies are respectively provided for the situations that the user equipment is mobile equipment and fixed equipment, so that the private QoS management performed on the user equipment can better conform to the actual use situation of the user equipment, and further, the service quality is ensured.

Referring to fig. 5, fig. 5 is a flowchart of a private quality of service management method provided in an embodiment of the present application, and in this embodiment, the method is mainly applied to MEC equipment deployed in a campus.

As shown in fig. 5, the private qos management method provided in this embodiment includes the following steps:

step 501, receiving protocol data unit PDU session data and bearer control signaling data of the ue transmitted by the base station.

Step 502, determining the current network performance of the user equipment according to the PDU session data.

It is to be understood that step 501 and step 502 in this embodiment are substantially the same as step 401 and step 402 in the embodiment shown in fig. 4, and are not described herein again.

Step 503, determine whether the network performance meets a preset threshold.

If the current network performance of the user equipment meets the preset threshold value through judgment, executing step 504; otherwise, step 505 is performed.

Step 504, transmitting the PDU session data and bearer control signaling data to the private network.

It can be understood that, for the case that the current network performance of the user equipment meets the preset threshold, the initial QoS Profile is also kept unchanged, and then the PDU session data and the bearer control signaling data are transmitted to the private network.

Step 505, determining whether the current service scenario of the user equipment is a continuous uplink or downlink service.

Step 506, perform private QoS guarantee pre-processing operations.

firstly, the MEC equipment generates scheduling indication information according to the current service scene of the user equipment.

Specifically, the scheduling indication information in this embodiment carries parameters such as an index (which may be the above-mentioned identification information, or a device number) of the ue, an uplink or downlink scheduling flag, a scheduling cycle time, and a scheduling packet size, which are not listed one by one here, and this embodiment is not limited thereto.

And then, the MEC equipment transmits the scheduling indication information to the base station.

And then, the base station negotiates with the user equipment according to the scheduling indication information.

Specifically, after receiving the scheduling indication information, the base station negotiates with the user equipment according to the scheduling indication suggested by the MEC device, that is, according to the scheduling indication information, so as to remove a resource scheduling request flow of PDU session data and bearer control quality data generated in an uplink or downlink service after successful negotiation, and directly performs communication interaction with the base station according to negotiated preset scheduling parameters, such as a preset period and a preset size of a data packet, thereby saving network resources to a great extent and using all network resources for effective data scheduling.

And then, the MEC equipment receives the negotiation result reported by the base station.

Specifically, if the negotiation result is that the negotiation is successful, the MEC apparatus starts to perform the operation of step 507; otherwise, the scheduling indication information is sent to the base station again.

Step 507, determining a target QoS configuration file according to the initial QoS configuration file, and issuing the target QoS configuration file to the base station, so that the base station can guarantee the service of the user equipment according to the target QoS configuration file.

It is to be understood that step 507 in this embodiment is substantially the same as step 404 in the embodiment shown in fig. 4, and this embodiment is not described again.

Therefore, according to the private QoS management method provided in this embodiment, for a service in which a service scene in a campus is continuous uplink or downlink transmission of a large amount of data, a private QoS guarantee preprocessing function is added in the MEC device, and before performing private QoS management on the user equipment, the private QoS guarantee preprocessing is performed first, that is, the MEC device issues scheduling indication information for the uplink or downlink service, so as to indicate the base station to perform authorization-free scheduling on uplink or downlink data of the user equipment that needs to perform private QoS guarantee, thereby implementing optimal management of resources.

In addition, by combining the private QoS guarantee preprocessing flow and the subsequent private QoS management, the extremely network requirements of the continuous uplink or downlink transmission scene can be met.

Referring to fig. 6, fig. 6 is a flowchart of a private quality of service management method provided in an embodiment of the present application, and in this embodiment, the method is mainly applied to a base station.

As shown in fig. 6, the private qos management method provided in this embodiment includes the following steps:

step 601, acquiring protocol data unit PDU session data and bearer control signaling data of user equipment, wherein the bearer control signaling data at least carries an initial QoS configuration file.

Step 602, determining whether the user equipment needs to perform private QoS management according to the identification information corresponding to the user equipment.

In addition, it can be preset which user equipments need to perform private QoS management, for example, if the local network number of a certain number segment is set to be required to perform private QoS management, the user equipments accessed by using these local network numbers need to perform private QoS management.

Step 603, transmitting the PDU session data and the bearer control signaling data to the multi-access edge computing MEC equipment, so that the MEC equipment can perform private QoS management on the user equipment according to the initial QoS configuration file carried in the PDU session data and the bearer control signaling.

In addition, in an example, if the current service scenario of the user equipment is a continuous uplink or downlink service, the base station may further receive scheduling indication information issued by the MEC equipment after transmitting PDU session data of the user equipment and bearer control signaling data carrying initial QoS Profile to the MEC equipment, negotiate with the user equipment according to the scheduling indication information, and notify the MEC equipment of a negotiation result, so that the MEC equipment performs private QoS management on the user equipment according to the negotiation result, the PDU session data, and the initial QoS configuration file carried in the bearer control signaling.

Since the base station provided in this embodiment needs to cooperate with the MEC device in the embodiments shown in fig. 1 to fig. 5 when implementing the private QoS management, for how the MEC device performs the private QoS management on the user equipment according to the PDU session data and the bearer control signaling data of the user equipment uploaded by the base station, the content described in the above embodiment is referred to in detail, and details of this embodiment are not repeated.

Step 604, transmitting the PDU session data and bearer control signaling to the public network.

That is, the user equipment is not subjected to private QoS management, and PDU session data and bearer control signaling data do not need to go to a private network but directly enter a public network.

Therefore, according to the private QoS management method provided in this embodiment, the base station performs data offloading processing with the MEC device deployed in the campus where the ToB service is implemented according to the above manner, and transmits PDU session data of the user equipment that needs to perform private QoS management and bearer control signaling data that carries the initial QoS configuration file to the MEC device deployed in the campus, and the MEC device in the campus performs private QoS management on the user equipment according to the current network performance of the user equipment and the initial QoS configuration file in the bearer control signaling data of the user equipment received from the base station, so that the private QoS management performed on the user equipment better conforms to the private network corresponding to the campus, and further, the service quality of the service executed by the user equipment is better guaranteed.

In addition, as can be seen from the above description, the private QoS management method provided in this embodiment does not need to deploy complicated QoS parameters on the core network side, and thus the private QoS management for the user equipment does not cause confusion of the public network.

Referring to fig. 7, fig. 7 is a flowchart of a private quality of service management method provided in an embodiment of the present application, and in this embodiment, the method is mainly applied to a base station.

As shown in fig. 7, the private qos management method provided in this embodiment includes the following steps:

step 701, acquiring protocol data unit PDU session data and bearer control signaling data of the user equipment, where the bearer control signaling data at least carries an initial QoS configuration file.

Step 702, determining whether the user equipment needs to perform private QoS management according to the identification information corresponding to the user equipment.

Step 703, transmitting the PDU session data and the bearer control signaling to the public network.

It is to be understood that steps 701 to 703 in this embodiment are substantially the same as

steps

601, 602, and 604 in the embodiment shown in fig. 6, and are described herein.

Step 704, determining whether the user equipment is a mobile equipment according to the identification information.

Understandably, since the user equipment may be a fixed device, it may also be a mobile device. Because the surrounding environment of the fixed equipment basically does not change greatly, the communication interference caused by environmental factors does not fluctuate greatly, and the adaptive QoS service can meet the requirements for a long time without frequent change or switching. However, for the mobile device, when implementing the corresponding service, there is not only its own network requirement, but also the network resource of other user equipment cannot be occupied when its external network environment changes, which requires that the MEC device not only consider the PDU session data and the initial QoS Profile of the mobile device, but also consider the current location information of the mobile device when performing private QoS management on the mobile device.

Taking the mobile device as an example of a patrol robot in a campus, the patrol robot may frequently enter and exit from an equipment area or a personnel area, or may work in a "busy cell" or an "idle cell" in a communication environment, so that the position information of the mobile device is needed, and the patrol robot not only plays the roles of campus navigation and asset tracking, but also can be supplemented as a premise for private QoS guarantee.

Therefore, after identifying the user equipment that needs to perform private QoS management, the base station further needs to identify whether the user equipment is a mobile device.

Regarding how to identify that the ue is a mobile device, taking the identification information corresponding to the ue as a local network number as an example, it may be predefined that the ue corresponding to the local network number of a certain number segment is a mobile device.

Correspondingly, if the current user equipment is determined to be the mobile equipment, step 705 is executed; otherwise, step 706 is performed.

Step 705, transmitting the PDU session data and the bearer control signaling data to the multi-access edge computing MEC device, so that the MEC device performs private QoS management on the user equipment according to the initial QoS configuration file carried in the PDU session data and the bearer control signaling.

It is easy to find that step 705 in this embodiment is substantially the same as step 603 in the embodiment shown in fig. 6, and the steps are described herein.

Step 706, determining the location information of the user equipment based on the preset base station positioning technology, and adding the location information to the bearer control signaling data.

The predetermined base station location technology may be Time Difference of Arrival (TDOA) technology. Taking the determined service as an Uplink service as an example, the selected TDOA technique is specifically an Uplink Time Difference of Arrival (UTDOA) technique.

Specifically, when determining the Location information of the ue based on the UTDOA technique, the base station (specifically, a Location Measurement Unit (LMU) in the base station) measures the time difference of arrival of the uplink Measurement signal transmitted by the mobile device, and then may calculate the current Location information of the mobile terminal according to a geometric principle.

For ease of understanding, the following is specifically illustrated with reference to examples:

assuming that a mobile device accesses a 5G base station, and its uplink Reference Signal (SRS) can be received by multiple peripheral base stations, here, 4 base stations are used to Receive the measurement Signal of the mobile device, forming 4 Transmission and Reception Points (TRP) for performing SRS demodulation at the same time, and calculating the uplink delay of each TRP according to formula (1).

Wherein, rxtd ₁ 、rxtd ₂ 、rxtd ₃ 、rxtd ₄ The measured uplink arrival time of base station 1, base station 2, base station 3 and base station 4, c is constant, x ₁ 、y ₁ 、z ₁ Is the coordinate position, x, of the base station 1 ₂ 、y ₂ 、z ₂ Is the coordinate position, x, of the base station 2 ₃ 、y ₃ 、z ₃ Is the coordinate position, x, of the base station 3 ₄ 、y ₄ 、z ₄ Is the coordinate position of the base station 4. According to rxtd ₁ 、rxtd ₂ 、rxtd ₃ 、rxtd ₄ And 4 equations are established for the coordinate positions of the 4 base stations, so that the coordinate positions x, y, z and DeltaT (common error of multi-station timing) of the mobile equipment can be calculated.

Step 707, transmitting the PDU session data and the bearer control signaling data added with the location information to the multi-access edge computing MEC device, so that the MEC device performs private QoS management on the user equipment according to the PDU session data, the initial QoS configuration file and the location information carried in the bearer control signaling.

Therefore, according to the private QoS management method provided in this embodiment, for the case that the user equipment is a mobile device, the base station determines the current location information of the mobile device based on the preset base station positioning technology, and adds the determined location information to the bearer control signaling data, so that when the MEC device performs private QoS management on the mobile device, the MEC device can comprehensively consider the current location information of the mobile device, and thus the private QoS management performed on the mobile device better conforms to a private network corresponding to a campus, and further the service quality of a service executed by the mobile device is better guaranteed.

In addition, it should be understood that the above steps of the various methods are divided for clarity, and the implementation may be combined into one step or split into some steps, and the steps are divided into multiple steps, so long as the same logical relationship is included in the protection scope of the present patent; it is within the scope of the patent to add insignificant modifications to the algorithms or processes or to introduce insignificant design changes to the core design without changing the algorithms or processes.

In addition, as can be seen from the above description, no matter the private qos management method related to the private qos management system, the private qos management method applied to the MEC device, or the private qos management method applied to the base station are mutually matched in the specific implementation, so the related technical details mentioned in any of the above embodiments are still valid in other embodiments.

Referring to fig. 8, fig. 8 is a schematic structural diagram of a private service management device according to an embodiment of the present application.

As shown in fig. 8, the private service management apparatus provided in this embodiment includes: includes at least one processor 801; and a memory 802 communicatively coupled to the at least one processor.

The memory 802 stores instructions executable by the at least one processor 801, and the instructions are executed by the at least one processor 801, so that the at least one processor 801 can execute the private quality of service management method applied to the MEC device or the private quality of service management method applied to the base station, as described in the above method embodiments.

As can be seen from the above description, the processor 801 in the private service management apparatus can execute the private quality of service management method applied to the MEC apparatus or the private quality of service management method applied to the base station, which is described in the above method embodiments. Thus, in one example, if the processor 801 executes a private quality of service management method applied to an MEC device, then the private quality of service management device is specifically an MEC device; the private service managing apparatus is in particular a base station if the processor 801 executes a private quality of service managing method applied to the base station.

Further, it is noted that in one example, the memory 802 and the processor 801 are coupled by a bus, which may include any number of interconnecting buses and bridges that couple one or more of the various circuits of the processor 801 and the memory 802 together. The bus may also connect various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface provides an interface between the bus and the transceiver. The transceiver may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 801 is transmitted over a wireless medium through an antenna, which receives the data and transmits the data to the processor 801.

Further, it will be appreciated that the processor 801, in addition to being responsible for managing the bus and general processing, may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 802 may also be used for storing data used by processor 801 in performing operations.

The embodiment of the application also relates to a computer readable storage medium which stores a computer program. The computer program, when executed by the processor, implements the private quality of service management method applied to the MEC device or the private quality of service management method applied to the base station described in the above method embodiments.

That is, as can be understood by those skilled in the art, all or part of the steps in the method for implementing the embodiments described above may be implemented by a program instructing related hardware, where the program is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the method described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It will be understood by those of ordinary skill in the art that the foregoing embodiments are specific examples for carrying out the present application, and that various changes in form and details may be made therein without departing from the spirit and scope of the present application in practice.

Claims

1. A private quality of service management method is applied to a multi-access edge computing (MEC) device, and comprises the following steps:

receiving Protocol Data Unit (PDU) session data and bearer control signaling data of User Equipment (UE) transmitted by a base station, wherein the bearer control signaling data at least carries an initial quality of service (QoS) configuration file;

determining the current network performance of the user equipment according to the PDU session data;

and carrying out private QoS management on the user equipment according to the network performance and the initial QoS configuration file carried in the bearer control signaling data.

2. The private QoS management method of claim 1, wherein said performing private QoS management for the ue according to the network performance and the initial QoS profile carried in the bearer control signaling data comprises:

judging whether the network performance meets a preset threshold value or not;

if not, determining a target QoS configuration file according to the initial QoS configuration file, and issuing the target QoS configuration file to the base station, so that the base station can guarantee the service of the user equipment according to the target QoS configuration file;

otherwise, keeping the initial QoS configuration file unchanged, and transmitting the PDU session data and the bearing control signaling data to a private network.

3. The private quality of service management method of claim 2, wherein prior to said determining a target QoS profile from the initial QoS profile, the method further comprises:

determining the current service scene of the user equipment according to the PDU session data;

if the current service scene of the user equipment is a continuous uplink or downlink service, executing private QoS guarantee preprocessing operation, and after the private QoS guarantee preprocessing operation is executed, executing the step of determining a target QoS configuration file according to the initial QoS configuration file;

otherwise, executing the step of determining the target QoS configuration file according to the initial QoS configuration file.

4. The private QoS management method according to claim 3, wherein said performing a private QoS guarantee pre-processing operation if the current service scenario of the ue is a persistent uplink or downlink service, comprises:

if the current service scene of the user equipment is a continuous uplink or downlink service, generating scheduling indication information according to the current service scene of the user equipment;

the scheduling indication information is sent to the base station, so that the base station can negotiate with the user equipment according to the scheduling indication information;

receiving a negotiation result reported by the base station;

if the negotiation is successful, determining that the private QoS guarantee preprocessing operation is completed;

otherwise, the scheduling indication information is sent to the base station again.

5. The private quality of service management method of claim 2, wherein a first QoS profile storage table is deployed in the MEC device, the first QoS profile storage table storing at least one first QoS profile; a second QoS configuration file storage table is deployed in the base station, and a second QoS configuration file which is the same as the first QoS configuration file is stored in the second QoS configuration file storage table; the first QoS profile and the second QoS profile are determined according to network requirements of the user equipment;

the determining a target QoS configuration file according to the initial QoS configuration file, and issuing the target QoS configuration file to the base station, so that the base station guarantees the service of the user equipment according to the target QoS configuration file, includes:

according to the network performance, selecting a 5G QoS grade identification 5QI corresponding to the first QoS configuration file from the first QoS configuration file storage table, and taking the selected 5QI as the target QoS configuration file;

and issuing the target QoS configuration file to the base station, so that the base station positions a second QoS configuration file corresponding to the 5QI from the second QoS configuration file storage table according to the QoS configuration file, and guarantees the service of the user equipment according to the second QoS configuration file.

6. The private QoS management method of claim 2, wherein the determining a target QoS profile according to the initial QoS profile and sending the target QoS profile to the base station for the base station to guarantee the service of the ue according to the target QoS profile comprises:

determining a QoS parameter to be changed according to the PDU session data;

adjusting the initial QoS configuration file according to the determined QoS parameters to obtain the target QoS configuration file;

and sending the target QoS configuration file to the base station, so that the base station can guarantee the service of the user equipment according to the target QoS configuration file.

7. The private quality of service management method of claim 2, wherein a first QoS profile storage table is deployed in the MEC device, the first QoS profile storage table storing at least one first QoS profile, each of the first QoS profiles corresponding to a location information; a second QoS configuration file storage table is deployed in the base station, and a second QoS configuration file which is the same as the first QoS configuration file is stored in the second QoS configuration file storage table; the first QoS profile and the second QoS profile are determined according to network requirements of the user equipment; the bearer control signaling data also carries position information of the user equipment, and the position information is determined by the base station based on a preset base station positioning technology;

the determining a target QoS configuration file for the initial QoS configuration file and sending the target QoS configuration file to the base station, so that the base station can guarantee the service of the user equipment according to the target QoS configuration file includes:

determining a first QoS configuration file corresponding to the position information of the user equipment from the first QoS configuration file table according to the position information of the user equipment carried in the bearer control signaling data to obtain the target QoS configuration file;

generating a switching instruction according to the target QoS configuration file;

and issuing the switching instruction to the base station, so that the base station switches the QoS configuration file corresponding to the user equipment from the initial QoS configuration file to the second QoS configuration file corresponding to the first QoS configuration file according to the switching instruction, and guarantees the service of the user equipment according to the second QoS configuration file.

8. A private QoS management method is applied to a base station, and comprises the following steps:

acquiring Protocol Data Unit (PDU) session data and bearer control signaling data of user equipment, wherein the bearer control signaling data at least carries an initial quality of service (QoS) configuration file;

determining whether the user equipment needs to perform private QoS management according to the identification information corresponding to the user equipment;

if necessary, transmitting the PDU session data and the bearer control signaling data to a multi-access edge computing MEC (Multi-access edge) device, so that the MEC device can perform private QoS (quality of service) management on the user equipment according to the initial QoS configuration file carried in the PDU session data and the bearer control signaling;

otherwise, transmitting the PDU session data and the bearing control signaling to a public network.

9. The private quality of service management method of claim 8, wherein said transmitting the PDU session data and the bearer control signaling data to a multi-access edge computing MEC device for the MEC device to perform private QoS management on the user equipment according to the initial QoS profile carried in the PDU session data and the bearer control signaling comprises:

determining whether the user equipment is mobile equipment or not according to the identification information;

if so, determining the position information of the user equipment based on a preset base station positioning technology, and adding the position information into the bearer control signaling data;

transmitting the PDU session data and the bearer control signaling data added with the position information to a multi-access edge computing MEC (media access control) device, so that the MEC device can perform private QoS management on the user equipment according to the PDU session data, the initial QoS configuration file and the position information carried in the bearer control signaling;

otherwise, transmitting the PDU session data and the bearer control signaling data to a multi-access edge computing MEC device, so that the MEC device performs private QoS management on the user equipment according to the initial QoS configuration file carried in the PDU session data and the bearer control signaling.

10. The private quality of service management method of claim 8, wherein the current service scenario of the user equipment is a persistent uplink or downlink service;

the transmitting the PDU session data and the bearer control signaling data to a multi-access edge computing MEC device, so that the MEC device performs private QoS management on the user equipment according to the initial QoS configuration file carried in the PDU session data and the bearer control signaling, comprising:

transmitting the PDU session data and the bearer control signaling data to the MEC device;

receiving scheduling indication information issued by the MEC equipment;

and negotiating with the user equipment according to the scheduling indication information, and informing the MEC equipment of a negotiation result, so that the MEC equipment performs private QoS management on the user equipment according to the negotiation result, the PDU session data and the initial QoS configuration file carried in the bearer control signaling.

11. A private quality of service management device, comprising:

at least one processor; and the number of the first and second groups,

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the private quality of service management method of any one of claims 1 to 7 or the private quality of service management method of any one of claims 8 to 10.

12. A private quality of service management system, comprising: a multi-access edge computing MEC device and a base station;

the MEC device for performing the private quality of service management method of any one of claims 1 to 7;

the base station for performing the private quality of service management method of any of claims 8 to 10.

13. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the private quality of service management method of any one of claims 1 to 7 or the private quality of service management method of any one of claims 8 to 10.