WO2022257379A1 - 私有服务质量管理方法、设备、系统及存储介质 - Google Patents

私有服务质量管理方法、设备、系统及存储介质 Download PDF

Info

Publication number
WO2022257379A1
WO2022257379A1 PCT/CN2021/134844 CN2021134844W WO2022257379A1 WO 2022257379 A1 WO2022257379 A1 WO 2022257379A1 CN 2021134844 W CN2021134844 W CN 2021134844W WO 2022257379 A1 WO2022257379 A1 WO 2022257379A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration file
qos
user equipment
private
qos configuration
Prior art date
Application number
PCT/CN2021/134844
Other languages
English (en)
French (fr)
Inventor
孙干
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2022257379A1 publication Critical patent/WO2022257379A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]

Definitions

  • the embodiment of the present application relates to the field of 5G enterprise-oriented (To Business, ToB) scenario communication, and in particular to a private quality of service management method, device, system and storage medium.
  • 5G enterprise-oriented (To Business, ToB) scenario communication and in particular to a private quality of service management method, device, system and storage medium.
  • the smart park In order to adapt to the communication characteristics of the smart park, in addition to accessing the public network, the smart park also deploys its own private network (also called the campus network) in combination with Multi-Access Edge Computing (MEC) technology.
  • MEC technology migrates the cloud computing platform from the inside of the mobile core network to the edge of the mobile access network, realizes flexible utilization of computing and storage resources, and maximizes the inherent capabilities of wireless networks.
  • the MEC service of the smart campus focuses on connection and computing capabilities. It is usually deployed between the base station in the form of the core network (5G Core, 5GC) and the radio access network (Radio Access Network, RAN). The entrance of the "first hop" of data provides a good way to tailor the proprietary communication system of the smart park.
  • 5G Core 5GC
  • Radio Access Network Radio Access Network
  • QoS Profiles QoS profiles
  • the current protocol does not have a suitable Qos Profile
  • QoS is more of a core network Policies on the side, and complicated QoS parameters deployed on the core network will cause confusion on the public network.
  • 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.
  • the private service quality management method includes: receiving the protocol data unit PDU session data and bearer control of the user equipment transmitted by the base station signaling data, the bearer control signaling data carries at least an initial quality of service QoS configuration file; according to the PDU session data, determine the current network performance of the user equipment; according to the network performance and the bearer control signaling
  • the initial QoS configuration file carried in the data performs private QoS management on the user equipment.
  • the embodiment of the present application also provides a private quality of service management method, which is applied to a base station.
  • the private quality of service management method includes: obtaining protocol data unit PDU session data and bearer control signaling data of user equipment, and the bearer control
  • the signaling data carries at least an initial quality of service QoS configuration file; according to the identification information corresponding to the user equipment, it is determined whether the user equipment needs to perform private QoS management; if necessary, the PDU session data and the bearer control signal transmit the 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 PDU session data and the initial QoS configuration file carried in the bearer control signaling; otherwise, transmitting the PDU session data and the bearer control signaling to a public network.
  • the embodiment of the present application also provides a private quality of service management device, including: a memory connected in communication with the at least one processor; wherein, the memory stores instructions executable by the at least one processor, the The instructions are executed by the at least one processor, so that the at least one processor can execute the above-mentioned private quality of service management method applied to the MEC device, or the private service quality management method applied to the base station.
  • a private quality of service management device including: a memory connected in communication with the at least one processor; wherein, the memory stores instructions executable by the at least one processor, the The instructions are executed by the at least one processor, so that the at least one processor can execute the above-mentioned private quality of service management method applied to the MEC device, or the private service quality management method applied to the base station.
  • the embodiment of the present application also provides a private quality of service management system, including: a multi-access edge computing MEC device and a base station; the MEC device is configured to execute the above-mentioned private service quality management method applied to the MEC device; The base station is configured to execute the above-mentioned private QoS management method applied to the base station.
  • a private quality of service management system including: a multi-access edge computing MEC device and a base station; the MEC device is configured to execute the above-mentioned private service quality management method applied to the MEC device;
  • the base station is configured to execute the above-mentioned private QoS management method applied to the base station.
  • the embodiment of the present application also provides a computer-readable storage medium storing a computer program.
  • the computer program is executed by the processor, the above-mentioned private quality of service management method applied to the MEC device, or the private service quality management method applied to the base station is implemented.
  • Fig. 1 is a schematic structural diagram of a private service quality management system provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of the interaction between the MEC device, the base station, and the 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 MEC equipment provided by an embodiment of the present application
  • FIG. 4 is a schematic diagram of a specific flow diagram for implementing private QoS management on user equipment according to the network performance and the initial QoS configuration file carried in the bearer control signaling data in the private service management method applied to the MEC device provided by the embodiment of the present application;
  • FIG. 5 is a schematic flowchart of introducing a private QoS guarantee preprocessing operation into a private service management method applied to an MEC device provided by an embodiment of the present application;
  • FIG. 6 is a schematic flowchart of a private service management method applied to a base station provided by an embodiment of the present application
  • FIG. 7 is a schematic flowchart of private QoS management for mobile equipment and fixed equipment for user equipment in the private service management method applied to the base station provided by the embodiment of the present application;
  • FIG. 8 is a schematic structural diagram of a private service management device provided by an embodiment of the present application.
  • the purpose of the embodiments of the present application is to provide a private service quality management method, device, system and storage medium, aiming at solving the above technical problems.
  • the private service quality management method, equipment, system and storage medium proposed in this application deploy MEC equipment in the ToB business park, and set the MEC equipment to determine network performance according to the PDU session data received from the user equipment from the base station, and then 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 perform private QoS management on the user equipment. Since the MEC equipment is deployed in the park, the private QoS management for the user equipment is carried out in the park, that is, the private service management solution provided by this application does not need to deploy complicated QoS parameters on the core network side, so the Private QoS management of user equipment without cluttering public networks.
  • the private QoS management of the user equipment by the MEC equipment in the campus 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 can make the user equipment
  • the private QoS management performed by the device is more in line with the corresponding private network of the campus, so as to better guarantee the QoS of the user equipment.
  • FIG. 1 is a schematic structural diagram of a private service management system provided by an embodiment of the present application.
  • the private service management system includes: a base station 100 and an MEC device 200 .
  • the base station 100 when implementing private quality of service management, it is specifically used to obtain the protocol data unit (Protocol Data Unit, PDU) session data and bearer control signaling data of the user equipment, and the bearer control signaling data carries at least the initial quality of service QoS configuration file; according to the identification information corresponding to the user equipment, determine whether the user equipment needs to perform private QoS management.
  • PDU Protocol Data Unit
  • the base station 100 is also configured to transmit the PDU session data and bearer control signaling data to the MEC device 200, for the MEC device 200 to provide the user equipment with the initial QoS configuration file carried in the PDU session data and bearer control signaling. Perform private QoS management; otherwise, transmit PDU session data and bearer control signaling to the public network.
  • the MEC device 200 when implementing private quality of service management, it is specifically used to receive the PDU session data and bearer control signaling data of the user equipment transmitted by the base station 100, and the bearer control signaling data at least carries the initial quality of service QoS configuration file; according to PDU session data to determine the current network performance of the user equipment; perform 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.
  • the private QoS Profile of the private QoS Profile completes the protocol handshake, that is, when the communication connection is established, it can also ensure that the private QoS management performed on the user equipment 300 can be performed normally.
  • a QoS profile storage table can be deployed or newly created in the respective storage areas of the base station 100 and the MEC device 200, and then Add the preset private QoS Profile to the QoS profile storage tables in the base station 100 and the MEC device 200 respectively.
  • the QoS configuration file storage table in the MEC 200 is called a first QoS configuration file storage table
  • the QoS configuration file storage table in the base station 100 is called a second QoS configuration file storage table.
  • the QoS Profile stored in the first QoS profile storage table can be called the first QoS Profile
  • the QoS Profile stored in the second QoS profile storage table can be called the second QoS Profile
  • the second QoS Profile identical to the first QoS Profile needs to be stored in the second QoS profile storage table.
  • the user device 300 may be a fixed device, such as a camera for visual quality inspection at a key station in a smart factory, or a transceiver device installed in a fixed area in the park, etc., which will not be listed here. This embodiment does not limit this either.
  • the user equipment may also be a mobile device, such as a robot moving in the park, an AGV car based on the automatic guided vehicle navigation technology (Automated Guided Vehicle, AGV), etc., which will not be listed here , which is not limited in this embodiment.
  • a mobile device such as a robot moving in the park, an AGV car based on the automatic guided vehicle navigation technology (Automated Guided Vehicle, AGV), etc., which will not be listed here , which is not limited in this embodiment.
  • each user equipment 300 in the park needs to access the network in advance, which can be specifically a 5G network, and establish a bearer on the 5G core network (5G Core, 5GC) .
  • 5G Core 5G Core
  • the base station 100 can obtain the PDU session data and bearer control signaling data of the user equipment 300 .
  • the bearer control signaling data carries at least a QoS Profile.
  • the QoS Profile includes a series of QoS characteristics and QoS parameters, such as packet error rate (Packet Error Rate, PER), priority (Priority Level), packet delay budget (Packet Delay Budget, PDB ), and QoS parameters such as Allocation and Retention Priority (ARP), Maximum Packet Loss Rate (Maximum Packet Loss Rate), and 5G QoS Class Identifier (hereinafter referred to as 5QI).
  • Packet Error Rate PER
  • priority Priority Level
  • PDB Packet Delay Budget
  • QoS parameters such as Allocation and Retention Priority (ARP), Maximum Packet Loss Rate (Maximum Packet Loss Rate), and 5G QoS Class Identifier (hereinafter referred to as 5QI).
  • ARP Allocation and Retention Priority
  • Maximum Packet Loss Rate Maximum Packet Loss Rate
  • 5QI 5G QoS Class Identifier
  • the 5QI mentioned above is specifically a scalar, which is used to index a 5G QoS feature.
  • 5QI values such as 5QI1 to 5QI9, 5QI65 to 5QI67, 5QI69, 5QI70, 5QI75, 5QI79 to 5QI85 are stipulated in 5QI, and it provides guaranteed traffic bit rate (Guaranteed Bit Rate, GBR) and non-guaranteed traffic bit rate (Non-Guaranteed Bit Rate). Rate, NGBR) resource type.
  • the resource types of GBR mentioned above include business scenarios such as remote control and augmented reality, while the resource types of NGBR include business scenarios such as voice, conversational video, and games.
  • 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 .
  • the determination of whether the user equipment 300 needs to perform private QoS management mentioned in this embodiment, on the side of the base station 100 specifically means that the base station 100 needs to identify the currently acquired PDU session data and bearer control information of the user equipment 300. Whether the data should be sent directly to the public network (also called extranet) or the private network in the park (also called enterprise network, or intranet).
  • the public network also called extranet
  • the private network in the park also called enterprise network, or intranet
  • the identification information used to determine whether the user equipment needs to perform private QoS management includes but is not limited to local network numbers, network slices, IP quintuples, domain name system (Domain Name System, DNS) any of the
  • which user equipment 300 needs to perform private QoS management can be pre-set. For example, if the local network numbers of a certain number segment are set to require private QoS management, as long as the users who use these local network numbers to access The device 300 needs to perform private QoS management.
  • the user equipment 300 may be a fixed equipment or a mobile equipment.
  • mobile devices when implementing corresponding services, they not only have their own network requirements, but also cannot occupy the network resources of other user devices when the external network environment changes. This requires MEC devices to perform private QoS on mobile devices.
  • MEC devices When managing, not only the PDU session data and initial QoS Profile of the mobile device must be considered, but also the current location information of the mobile device.
  • the base station 100 identifies the user equipment 300 that needs to perform private QoS management, it needs to further identify whether the user equipment 300 is a mobile device.
  • the identification information corresponding to the user equipment as a local network number it may be predetermined that the user equipment 300 corresponding to a local network number in a certain number range is a mobile device.
  • the base station 100 When determining that the user equipment 300 currently requiring private QoS management is a mobile device, the base station 100 needs to locate the current location information of the mobile device based on a preset base station positioning technology, such as time difference of arrival technology, and add the determined location information to the bearer In the control signaling data.
  • a preset base station positioning technology such as time difference of arrival technology
  • the base station 100 transmits the 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 the PDU session data and bearer control signaling data of the user equipment 300 that requires private QoS management The data is transmitted to the MEC device 200 deployed in the campus.
  • the bearer control signaling data sent also carries the current location information of the user equipment 300.
  • the base station 100 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, it specifically first sends the PDU session data and the bearer control signaling data to the 5GC through the transmission network, 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 connected to the public network are based on the base station 100—>transmission network—>5GC —>The transmission path of the Internet is sent to the public network.
  • Internet Internet
  • the base station 100 For the PDU session data and bearer control signaling data of the user equipment 300 requiring private QoS management, the base station 100 directly transmits them to the MEC device 200 deployed in the campus through the transmission network.
  • the MEC device 200 After receiving the PDU session data and 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 then determines the current network performance of the user equipment 300 according to the analysis result; The 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 (only when the user equipment is a mobile device).
  • the MEC device 200 performs private QoS management on the user equipment 300 according to the determined network performance, the extracted initial QoS Profile and the current location information of the user equipment 300.
  • the private QoS management performed on the user equipment 300 is divided into two cases: adjusting the initial QoS Profile and not adjusting the initial QoS Profile.
  • the MEC device 200 will not adjust the initial QoS Profile, that is, keep the initial QoS Profile unchanged, and directly transfer the PDU session data and bearer control information of the user equipment 300 Just let the data be transmitted to the private network.
  • the MEC device 200 adjusts the initial QoS Profile as needed, and then obtains the target QoS Profile, and sends the target QoS Profile to the base station 100.
  • the base station 100 receives the target QoS Profile issued by the MEC device 200, and guarantees the service of the user equipment 300 according to the target QoS Profile.
  • PDU session data and bearer control signaling data that need to be guaranteed will eventually flow into the private network after going through the above guarantee process.
  • the MEC device 200 can first determine the current service scenario of the user equipment 300 according to the received PDU session data of the user equipment 300, and then determine the current service scenario of the user equipment 300.
  • the MEC device 200 generates scheduling indication information according to the current service scenario of the user equipment 300 .
  • the scheduling indication information mentioned in this embodiment will carry the index of the user equipment 300 (which may be the identification information mentioned above, or the device number), the uplink or downlink scheduling flag, the scheduling cycle time, the scheduling packet size and other parameters, It is not listed here one by one, and this embodiment does not limit it.
  • the MEC device 200 sends the scheduling indication information to the base station 100 .
  • the base station 100 negotiates with the user equipment 300 according to the scheduling indication information.
  • the base station 100 after receiving the scheduling indication information, the base station 100 will follow the scheduling indication suggested by the MEC device 200, that is, negotiate with the user equipment 300 according to the scheduling indication information, aiming to eliminate the need for uplink or downlink services after the negotiation is successful.
  • the generated PDU session data and the resource scheduling request flow of the bearing control quality data directly communicate with the base station 100 according to the negotiated preset scheduling parameters, such as the preset period and the preset size of the data packet, thereby greatly saving Network resources, use all network resources for efficient data scheduling.
  • the base station 100 reports the negotiation result to the MEC device 200 .
  • the MEC device 200 starts to perform the above operation of adjusting the initial QoS Profile; otherwise, re-sends the scheduling instruction information to the base station 100, that is, re-performs the above operation.
  • the private quality of service management system deploys MEC equipment in the ToB service campus, and configures the MEC equipment to determine network performance based on the PDU session data of the user equipment received from the base station, and then according to the current Private QoS management of the user equipment is performed on the 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 equipment is deployed in the park, the private QoS management for the user equipment is carried out in the park, that is, the private service management solution provided by this application does not need to deploy complicated QoS parameters on the core network side, so the Private QoS management of user equipment without cluttering public networks.
  • the private QoS management of the user equipment by the MEC equipment in the campus 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, it is possible to make the user equipment Private QoS management is more in line with the private network corresponding to the campus, so as to better guarantee the QoS of user equipment.
  • the MEC data distribution technology with the park base station positioning technology, and adding private QoS guarantee pre-processing to the continuous uplink or downlink business, it provides customized private QoS management for user equipment in the park, so as to better It meets the extreme requirements of network performance such as large traffic bandwidth, network delay, and false alarm rate for different user equipment in different business scenarios in the park, and plays a role in promoting the enterprise application of 5G technology.
  • FIG. 3 is a flowchart of a private service quality management method provided in an embodiment of the present application.
  • the method is mainly applied to MEC equipment.
  • the MEC device mentioned in this embodiment is specifically deployed in a campus.
  • MEC equipment has a local data offload function (Traffic Offload Function, TOF). Therefore, based on this feature, MEC equipment can offload local business data to the private network, thereby ensuring that private data does not leave the campus, and avoiding enterprise information leakage.
  • TOF Traffic Offload Function
  • MEC devices can calculate local service data, that is, the service data (PDU session data and bearer control signaling data) of user equipment in the campus does not need to be forwarded to the public network for calculation, but is processed at the edge of the enterprise, so that Effectively reduce the end-to-end delay of network transmission.
  • the service data PDU session data and bearer control signaling data
  • the private QoS management method provided by this embodiment will be specifically described below with reference to FIG. 3 .
  • the private service quality management method provided by this embodiment includes the following steps:
  • Step 301 receiving protocol data unit PDU session data and bearer control signaling data of the user equipment transmitted by the base station.
  • the 5G system mainly includes a user plane and a control plane.
  • the data that needs to be offloaded is mainly the PDU session data of the device, that is, the specific transmission data of the user device.
  • the data that needs to be offloaded is mainly bearer control signaling data for the user equipment to establish a PDU session.
  • the bearer control signaling data usually carries a variety of information, but this embodiment focuses on the QoS configuration file carried in the bearer control signaling data when the PDU session is established. Therefore, the bearer control signaling data of the user equipment received by the MEC device from the base station needs to carry at least the QoS configuration file.
  • the QoS configuration file carried in the bearer control signaling data acquired from the user equipment side is referred to as an initial QoS configuration file.
  • the initial QoS configuration file is specifically a QoS configuration file corresponding to the standard QoS protocol used when the user equipment accesses the 5GC.
  • Step 302 according to the PDU session data, determine the current network performance of the user equipment.
  • the MEC device can parse the received PDU session data, and then according to the time delay between the parsed data, and/or the bit error rate between packets, and/or the maximum The packet loss rate and other parameters are used to determine the current network performance of the user equipment.
  • Step 303 Perform 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.
  • the private QoS management performed on the user equipment essentially keeps the initial QoS configuration file unchanged, and directly transfers the PDU session data and bearer control signaling The data is transmitted to the private network; if the network performance is abnormal, or the above-mentioned index values do not meet the preset thresholds, according to the private QoS management of the user equipment, the initial QoS configuration file is adjusted to obtain the target QoS configuration file, and the The target QoS configuration file is delivered to the base station, so that the base station can guarantee the service of the user equipment according to the target QoS configuration file.
  • the MEC device will provide the user with When the device performs private QoS management, it also considers the current location information of the user equipment carried in the bearer control signaling data.
  • private QoS management can be performed on the user equipment only according to the initial QoS configuration file in the PDU session data and bearer control signaling data; Only according to the initial QoS configuration file and location information in the PDU session data and bearer control signaling data can private QoS management be performed on the user equipment.
  • the private service quality management method provided in this embodiment deploys MEC equipment in the ToB business park, and sets the MEC equipment to determine network performance according to the PDU session data received from the user equipment from the base station, and then 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 equipment is deployed in the park, the private QoS management for the user equipment is carried out in the park, that is, the private service management solution provided by this application does not need to deploy complicated QoS parameters on the core network side, so the Private QoS management of user equipment without cluttering public networks.
  • the private QoS management of the user equipment by the MEC equipment in the campus 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, it is possible to make the user equipment Private QoS management is more in line with the private network corresponding to the campus, so as to better guarantee the QoS of user equipment.
  • FIG. 4 is a flowchart of a private service quality management method provided in an embodiment of the present application.
  • the method is mainly applied to MEC devices deployed in a campus.
  • the private service quality management method provided by this embodiment includes the following steps:
  • Step 401 receiving protocol data unit PDU session data and bearer control signaling data of user equipment transmitted by the base station.
  • Step 402 according to the PDU session data, determine the current network performance of the user equipment.
  • step 401 and step 402 in this embodiment are substantially the same as step 301 and step 302 in the embodiment shown in FIG. 3 , and will not be repeated here.
  • Step 403 judging whether the network performance meets a preset threshold.
  • the essence of judging whether the network performance meets the preset threshold in this embodiment is to determine whether the user equipment needs private QoS guarantee.
  • step 404 is performed; otherwise, step 405 is performed.
  • Step 404 determine the target QoS configuration file according to the initial QoS configuration file, and send 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.
  • step 404 in an example, it is specifically:
  • the first QoS configuration file storage table needs to be pre-deployed in the MEC device, and at least one first QoS configuration file is stored in the first QoS configuration file storage table;
  • the second QoS configuration file storage table stores the same second QoS configuration file as the first QoS configuration file in the second QoS configuration file storage table.
  • the first QoS configuration file and the second QoS configuration file are predetermined according to network requirements of the user equipment.
  • the manner of determining the first QoS configuration file and the second QoS configuration file it may be determined manually by a technician, or may be determined based on a network model obtained by training a preset machine learning algorithm.
  • step 404 select a 5QI corresponding to the first QoS configuration file from the first QoS configuration file storage table, and use the selected 5QI as the target QoS configuration file.
  • the target QoS configuration file is sent to the base station, so that the base station can locate the second QoS configuration file corresponding to the 5QI from the second QoS configuration file storage table according to the QoS configuration file, and ensure the security of the user equipment according to the second QoS configuration file. business.
  • this adjustment strategy since the first QoS configuration file stored in the first QoS configuration file storage table is not associated with location information, this adjustment strategy is more suitable for the case where the user equipment is a fixed device.
  • a private QoS Profile is pre-designed, that is, the first QoS profile and the second QoS profile mentioned above, for example, for the wireless video backhaul service , customize the 5QI value that is not within the scope of the 3GPP agreement, such as 5QI100, under this new 5QI index value, according to the requirements of the fixed equipment for the video backhaul service, match and design the targeted resource type (such as NGBR), the default priority QoS features such as level (such as 19), packet delay budget (PDB, such as 10ms), packet error rate (PER, such as 10-4), maximum data burst size (such as 1354 bytes), and corresponding QoS parameters; Then deploy these designed private QoS profiles to the first QoS profile of the MEC device and the second QoS profile of the base station respectively.
  • the targeted resource type such as NGBR
  • the default priority QoS features such as level (such as 19), packet delay budget (PDB, such as 10ms), packet error rate (PER, such as
  • the fixed device accesses the network, it transmits the current initial QoS Profile to the base station through bearer control signaling data, and at the same time transmits the current PDU session data to the base station, and the base station transmits the obtained PDU session data and at least The bearer control signaling data carrying the initial QoS Profile is transmitted to the MEC equipment.
  • the MEC equipment analyzes and determines that the current network status of the user equipment does not meet the preset threshold, it can perform private QoS management on the user equipment according to the above adjustment strategy.
  • step 404 in another example, it is specifically:
  • the initial QoS configuration file is adjusted to obtain the target QoS configuration file.
  • the target QoS configuration file is sent to the base station, so that the base station can guarantee the service of the user equipment according to the target QoS configuration file.
  • the QoS Profile includes QoS features and QoS parameters, and the QoS parameters include but are not limited to ARP, MPLR, 5QI, etc.
  • the initial QoS Profile If it is determined that the QoS parameter that needs to be changed is ARP according to the PDU session data, then the initial QoS Profile If the parameter value corresponding to the ARP is adjusted to the currently determined parameter value, the adjusted initial QoS Profile can be regarded as the target QoS Profile.
  • the adjustment of the initial QoS Profile is completed on the MEC device side, but in practical applications, the operation of changing a certain QoS parameter in the initial QoS Profile can be done in the It is performed on the base station side. Therefore, after the MEC device determines the QoS parameters that need to be changed, it can send the QoS parameters to the base station, and the base station can adjust the initial QoS Profile according to the received QoS parameters.
  • this adjustment strategy since it does not involve the overall replacement of the initial QoS Profile, but only adjusts several QoS parameters in the initial QoS Profile, this adjustment strategy does not limit the specific type of user equipment, that is, whether it is a mobile Both equipment and fixed equipment can use this adjustment strategy for private QoS management.
  • this adjustment strategy of only changing a certain QoS parameter value in the initial QoS Profile enables the base station to obtain The target QoS Profile provides a more refined guarantee for user equipment.
  • the MEC device can issue a modification instruction for a certain QoS parameter in the current initial QoS Profile of the device.
  • the QoS parameter ARP defines The importance of user equipment resource requests.
  • the ARP parameter determines whether a new QoS flow is accepted or rejected.
  • the MEC device can decide to modify the ARP parameter from the default value is the highest priority value of 1.
  • step 404 in another example, it is specifically:
  • the first QoS configuration file storage table needs to be pre-deployed in the MEC device, and at least one first QoS configuration file is stored in the first QoS configuration file storage table, and each first QoS configuration file is set at the same time.
  • the QoS configuration file corresponds to a location information, that is, the corresponding relationship between each first QoS configuration file and each location information is established; similarly, the second QoS configuration file storage table is deployed in the base station, and in the second QoS configuration file storage table A second QoS profile identical to the first QoS profile is stored.
  • step 404 when step 404 is executed, according to the location information of the user equipment carried in the bearer control signaling data, the first QoS configuration file corresponding to the location information of the user equipment is determined from the first QoS configuration file table, and the target QoS configuration file is obtained. .
  • the handover instruction is sent to the base station, so that the base station can switch 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 handover instruction, and follow the second QoS configuration file.
  • the file guarantees the service of the user equipment.
  • this adjustment strategy since the first QoS configuration file stored in the first QoS configuration file storage table is associated with location information, this adjustment strategy is more suitable for the case where the user equipment is a mobile device.
  • a private QoS Profile is pre-designed for different mobile devices, that is, the first QoS profile and the second QoS configuration mentioned above
  • a 5QI value that is not within the scope of the 3GPP agreement, such as 5QI100.
  • match and design targeted Resource type such as NGBR
  • default priority such as 19
  • packet delay budget such as 10ms
  • PER packet error rate
  • maximum data burst size such as 1354 bytes
  • the mobile device accesses the network, it transmits the current initial QoS Profile to the base station through the bearer control signaling data, and at the same time transmits the current PDU session data to the base station, and the base station will obtain the PDU session data and carry
  • the initial QoS Profile and the bearer control signaling data of the mobile device's current location information are transmitted to the MEC device.
  • the MEC device analyzes and determines that the current network status of the user device does not meet the preset threshold, it can follow the above adjustment strategy for the user.
  • the device performs private QoS management.
  • the MEC device when the inspection robot arrives in the equipment area, the MEC device delivers the GBR-type QoS guarantee, and when the inspection robot enters the personnel area, the MEC device issues the NGBR-type QoS guarantee. That is, suitable private QoS management is performed for the location of the inspection robot.
  • Step 405 keep the initial QoS configuration file unchanged, and transmit the PDU session data and bearer control signaling data to the private network.
  • the private QoS management method provided in this embodiment is based on the MEC TOF technology, combined with the base station positioning technology in the park, realizes the private QoS management of the user equipment in the park, and when the private QoS management is performed on the user equipment, Different adjustment strategies are provided for the case where the user equipment is a mobile device and a fixed device, so that the private QoS management of the user equipment can better fit the actual use of the user equipment, thereby ensuring the quality of service.
  • FIG. 5 is a flowchart of a private service quality management method provided in an embodiment of the present application.
  • the method is mainly applied to MEC devices deployed in a campus.
  • the private service quality management method provided by this embodiment includes the following steps:
  • Step 501 Receive protocol data unit PDU session data and bearer control signaling data of user equipment transmitted by the base station.
  • Step 502 according to the PDU session data, determine the current network performance of the user equipment.
  • 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 will not be repeated here.
  • Step 503 judging whether the network performance meets a preset threshold.
  • step 504 If it is determined that the current network performance of the user equipment meets the preset threshold, step 504 is performed; otherwise, step 505 is performed.
  • Step 504 transmit the PDU session data and bearer control signaling data to the private network.
  • the initial QoS Profile is also kept unchanged, and then the PDU session data and bearer control signaling data are transmitted to the private network.
  • Step 505 determine whether the current service scenario of the user equipment is continuous uplink or downlink service.
  • Step 506 execute private QoS guarantee preprocessing operation.
  • the MEC device generates scheduling indication information according to the current service scenario of the user equipment.
  • the scheduling instruction information mentioned in this embodiment will carry the index of the user equipment (which can be the above-mentioned identification information, or the equipment number), uplink or downlink scheduling flag, scheduling cycle time, scheduling packet size and other parameters are not listed here, and are not limited in this embodiment.
  • the MEC device sends the scheduling indication information to the base station.
  • the base station negotiates with the user equipment according to the scheduling indication information.
  • the base station after receiving the scheduling indication information, the base station will follow the scheduling indication suggested by the MEC equipment, that is, negotiate with the user equipment according to the scheduling indication information, aiming to avoid the PDU session generated in the uplink or downlink services after the negotiation is successful
  • the resource scheduling request process for data and bearer control quality data directly communicates with the base station according to the negotiated preset scheduling parameters, such as the preset period and the preset size of the data packet, thereby greatly saving network resources and all of network resources are used for efficient data scheduling.
  • the MEC device receives the negotiation result reported by the base station.
  • the MEC device starts to perform the operation of step 507; otherwise, it sends the scheduling indication information to the base station again.
  • Step 507 Determine the target QoS configuration file according to the initial QoS configuration file, and send 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.
  • step 507 in this embodiment is substantially the same as step 404 in the embodiment shown in FIG. 4 , which will not be repeated in this embodiment.
  • the private QoS management method provided in this embodiment is aimed at the continuous uplink or downlink transmission of a large amount of data in the business scenario in the campus, by adding a private QoS guarantee preprocessing function in the MEC device, and performing Before private QoS management, private QoS guarantee preprocessing is performed first, that is, the MEC device issues scheduling instruction information for uplink or downlink services, thereby instructing the base station to perform authorization-free scheduling of uplink or downlink data of user equipment that needs private QoS guarantee. This enables optimal management of resources.
  • FIG. 6 is a flowchart of a private service quality management method provided by an embodiment of the present application.
  • the method is mainly applied to a base station.
  • the private service quality management method provided in this embodiment includes the following steps:
  • Step 601 acquire protocol data unit PDU session data and bearer control signaling data of the user equipment, the bearer control signaling data at least carries the initial quality of service QoS configuration file.
  • Step 602 Determine whether the user equipment needs to perform private QoS management according to the identification information corresponding to the user equipment.
  • the identification information used to determine whether the user equipment needs to perform private QoS management includes but is not limited to local network numbers, network slices, IP quintuples, domain name system (Domain Name System, DNS) any of the
  • which user equipment needs to be managed by private QoS can be pre-set. For example, if the local network number of a certain number segment is set to be managed by private QoS, as long as the user equipment that uses these local network numbers to access It is the need for private QoS management.
  • step 603 the PDU session data and bearer control signaling data are transmitted to the multi-access edge computing MEC device for the MEC device to perform private QoS management on the user equipment according to the initial QoS configuration file carried in the PDU session data and bearer control signaling.
  • the base station transmits the PDU session data of the user equipment and the bearer control signaling data carrying the initial QoS Profile to the MEC device, It will also receive the scheduling instruction information issued by the MEC device, and then negotiate with the user equipment according to the scheduling instruction information, and inform the MEC device of the negotiation result, so that the MEC device can use the initial information carried in the negotiation result, PDU session data, and bearer control signaling.
  • the QoS profile performs private QoS management on user equipment.
  • Step 604 transmit the PDU session data and bearer control signaling to the public network.
  • PDU session data and bearer control signaling data do not need to be smuggled into the private network, but directly enter the public network.
  • the base station performs data offloading processing with the MEC device deployed in the campus implementing the ToB service in the above-mentioned manner, and transfers the PDU session data and
  • the bearer control signaling data carrying the initial QoS configuration file is transmitted to the MEC device deployed in the campus, and the MEC device in the park bases on the current network performance of the user equipment and the bearer control signaling data of the user equipment received from the base station
  • the initial QoS configuration file performs private QoS management on the user equipment, so that the private QoS management on the user equipment is more in line with the corresponding private network in the campus, and thus better guarantees the service quality of the services executed by the user equipment.
  • the private QoS management method provided by this embodiment does not need to deploy complex QoS parameters on the core network side, so the private QoS management of user equipment will not cause confusion on the public network.
  • FIG. 7 is a flowchart of a private service quality management method provided by an embodiment of the present application.
  • the method is mainly applied to a base station.
  • the private service quality management method provided in this embodiment includes the following steps:
  • Step 701 acquire protocol data unit PDU session data and bearer control signaling data of the user equipment, the bearer control signaling data at least carries the initial quality of service QoS configuration file.
  • Step 702 Determine whether the user equipment needs to perform private QoS management according to the identification information corresponding to the user equipment.
  • Step 703 transmit the PDU session data and bearer control signaling to the public network.
  • step 701 to step 703 in this embodiment are approximately the same as step 601, step 602 and step 604 in the embodiment shown in FIG. 6 respectively, and the steps are described here.
  • Step 704 determine whether the user equipment is a mobile equipment.
  • the user equipment since the user equipment may be a fixed equipment, it may also be a mobile equipment. Since the surrounding environment of fixed equipment does not change much, the communication interference caused by environmental factors does not fluctuate much, and the adapted QoS service can meet the requirements for a long period of time without frequent changes or switching.
  • mobile devices when implementing corresponding services, they not only have their own network requirements, but also cannot occupy the network resources of other user equipment when the external network environment changes. This requires MEC devices to perform private QoS on mobile devices. When managing, not only the PDU session data and initial QoS Profile of the mobile device must be considered, but also the current location information of the mobile device.
  • the mobile device may frequently enter and exit the equipment area or personnel area, or may work in a "busy cell” or “idle cell” in the communication environment, so the location information of the mobile device is required.
  • the location information of the mobile device is required.
  • it can also be used as a prerequisite for private QoS protection.
  • the base station identifies the user equipment that needs to perform private QoS management, it needs to further identify whether the user equipment is a mobile device.
  • the identification information corresponding to the user equipment as a local network number it may be predetermined that the user equipment corresponding to a local network number in a certain number segment is a mobile device.
  • step 705 if it is determined that the current user equipment is a mobile device, perform step 705; otherwise, perform step 706.
  • Step 705 transmit the PDU session data and bearer control signaling data to the multi-access edge computing MEC device for the MEC device to perform private QoS management on the user equipment according to the initial QoS configuration file carried in the PDU session data and bearer control signaling.
  • step 705 in this embodiment is substantially the same as step 603 in the embodiment shown in FIG. 6 , and the steps are repeated here.
  • Step 706 based on the preset base station positioning technology, determine the location information of the user equipment, and add the location information to the bearer control signaling data.
  • the preset base station positioning technology may be a time difference of arrival (Time Difference of Arrival, TDOA) technology.
  • TDOA Time Difference of Arrival
  • UTDOA Uplink Time Difference of Arrival
  • the base station when determining the location information of the user equipment based on the UTDOA technology, the base station (specifically, it may be a location measurement unit (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 The current location information of the mobile terminal can be calculated according to the geometric principle.
  • LMU Location Measurement Unit
  • a mobile device accesses a 5G base station
  • its uplink reference signal Sounding Reference Signal, SRS
  • SRS Sounding Reference Signal
  • four base stations are used to receive the measurement signal of the mobile device, forming four transmitting and receiving points (Transmit and Receive Point (TRP) simultaneously perform SRS demodulation, and the uplink delay of each TRP can be calculated according to formula (1).
  • TRP Transmit and Receive Point
  • rxtd 1 , rxtd 2 , rxtd 3 , and rxtd 4 are the uplink arrival times measured by base station 1, base station 2, base station 3, and base station 4 respectively
  • c is a constant
  • x 1 , y 1 , z 1 are the coordinate positions of base station 1
  • x 2 , y 2 , z 2 are the coordinates of base station 2
  • x 3 , y 3 , z 3 are the coordinates of base station 3
  • x 4 , y 4 , z 4 are the coordinates of base station 4.
  • Step 707 transmit the PDU session data and the bearer control signaling data added with location information to the MEC device for multi-access edge computing, for the MEC device to pair the PDU session data, the initial QoS configuration file and the location information carried in the bearer control signaling User equipment performs private QoS management.
  • the base station determines the current location information of the mobile device based on the preset base station positioning technology for the case where the user equipment is a mobile device, and adds the determined location information to the bearer control
  • the MEC device can comprehensively consider the current location information of the mobile device when performing private QoS management on the mobile device, so that the private QoS management on the mobile device is more in line with the private network corresponding to the campus, and thus better The quality of service of the business performed by the mobile device is guaranteed.
  • FIG. 8 is a schematic structural diagram of a private service management device provided by an embodiment of the present application.
  • the private service management device includes: at least one processor 801 ; and a memory 802 communicatively connected to the at least one processor.
  • the memory 802 stores instructions that can be executed by at least one processor 801, and the instructions are executed by at least one processor 801, so that at least one processor 801 can execute the private quality of service applied to the MEC device described in the above method embodiment management method, or a private QoS management method applied to the base station.
  • the processor 801 in the private service management device can execute the private QoS management method applied to the MEC device or the private QoS management method applied to the base station described in the above method embodiments. Therefore, in an example, if the processor 801 executes a private quality of service management method applied to an MEC device, then the private service management device is specifically an MEC device; if the processor 801 executes a private quality of service management method applied to a base station method, then the private service management device is specifically a base station.
  • the memory 802 and the processor 801 are connected by a bus, and the bus may include any number of interconnected buses and bridges.
  • the bus connects one or more processors 801 and the memory 802 The circuits are connected together.
  • the bus may also connect together various other circuits such as peripherals, voltage regulators, and power management circuits, all of which are well known in the art and therefore will not be further described herein.
  • the bus interface provides an interface between the bus and the transceivers.
  • a transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing means for communicating with various other devices over a transmission medium.
  • the data processed by the processor 801 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 801 .
  • the processor 801 can also provide various functions, including timing, peripheral interface, voltage regulation, power management and other control functions, in addition to being responsible for bus management and general processing.
  • the memory 802 can also be used to store data used by the processor 801 when performing operations.
  • the embodiment of the present application also relates to a computer-readable storage medium storing a computer program.
  • the computer program is executed by the processor, the private QoS management method applied to the MEC device or the private QoS management method applied to the base station described in the above method embodiments is implemented.
  • a storage medium includes several instructions to make a device ( It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc., which can store program codes. .

Landscapes

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

Abstract

一种私有服务质量管理方法、设备、系统及存储介质，私有服务质量管理方法应用于多接入边缘计算MEC设备，包括：接收基站传输的用户设备的协议数据单元PDU会话数据和承载控制信令数据，承载控制信令数据至少携带了初始服务质量QoS配置文件；根据PDU会话数据，确定用户设备当前的网络性能；根据网络性能和承载控制信令数据中携带的初始QoS配置文件，对用户设备进行私有QoS管理。

Description

私有服务质量管理方法、设备、系统及存储介质
相关申请的交叉引用
本申请基于申请号为“202110632576.X”、申请日为2021年6月7日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此以引入方式并入本申请。
技术领域
本申请实施例涉及5G面向企业(To Business，ToB)场景通信领域，特别涉及一种私有服务质量管理方法、设备、系统及存储介质。
背景技术
目前国家积极推进5G网络建设，5G生活已悄然到来。由于5G大带宽、高可靠、低时延、海量接入的特点，不仅给传统的面向个人(To Customer，ToC)用户带来更好的体验，而且也使得智能工厂、智慧园区等5G智能化ToB产业得以快速发展。
为适应智慧园区的通信特点，智慧园区除接入公共网络外，还结合多接入边缘计算(Multi-Access Edge Computing，MEC)技术部署了自己的私有网络(也可以称为园内网)。MEC技术将云计算平台从移动核心网络内部迁移到移动接入网边缘，实现计算及存储资源的弹性利用，最大程度发掘无线网络的内在能力。智慧园区的MEC服务重在联接和计算的能力，其通常部署在核心网(5G Core，5GC)和无线接入网络(Radio Access Network，RAN)形式的基站之间，在最靠近园区的地方作为数据“第一跳”的入口，为量身打造智慧园区专有通信系统提供了很好的途径。
但是随着智能工厂、智能码头、智慧矿场等ToB生态的发展，各种自定义通信需求使得目前标准协议中的服务质量(Quality of Service，QoS)管理无法满足用户业务的需要，例如智能工厂中的关键工位视觉质检，要求持续的上行高清视频回传，且要求极致的时延以及丢包率，以智能电网为例，要求毫秒级的网络时延，同时根据不同的业务，又有不同的且具体的网络要求。这些要求按照QoS的映射特点，就会产生多种不同的QoS配置文件(QoS Profile)，是传统的网络无法满足的，不仅因为当前协议没有合适的Qos Profile，而且因为QoS更多的是核心网侧的策略，而繁杂的QoS参数部署在核心网将会引起公共网络的混乱。
因此，如何解决标准QoS协议无法有效满足私网或园区网使用需求成为了一个亟需解决的技术问题。
发明内容
本申请的实施例提供了一种私有服务质量管理方法，应用于多接入边缘计算MEC设备，所述私有服务质量管理方法包括：接收基站传输的用户设备的协议数据单元PDU会话数据和承载控制信令数据，所述承载控制信令数据至少携带了初始服务质量QoS配置文件；根据所述PDU会话数据，确定所述用户设备当前的网络性能；根据所述网络性能和所述承载控制信 令数据中携带的所述初始QoS配置文件，对所述用户设备进行私有QoS管理。
本申请的实施例还提供了一种私有服务质量管理方法，应用于基站，所述私有服务质量管理方法包括：获取用户设备的协议数据单元PDU会话数据和承载控制信令数据，所述承载控制信令数据至少携带了初始服务质量QoS配置文件；根据所述用户设备对应的标识信息，确定所述用户设备是否需要进行私有QoS管理；若需要，将所述PDU会话数据和所述承载控制信令数据传输至多接入边缘计算MEC设备，供所述MEC设备根据所述PDU会话数据和所述承载控制信令中携带的所述初始QoS配置文件对所述用户设备进行私有QoS管理；否则，将所述PDU会话数据和所述承载控制信令传输至公共网络。
本申请实施例还提供了一种私有服务质量管理设备，包括：与所述至少一个处理器通信连接的存储器；其中，所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如上所述的应用于MEC设备的私有服务质量管理方法，或者应用于基站的私有服务质量管理方法。
本申请实施例还提供了一种私有服务质量管理系统，包括：多接入边缘计算MEC设备和基站；所述MEC设备，用于执行如上所述的应用于MEC设备的私有服务质量管理方法；所述基站，用于执行如上所述的应用于基站的私有服务质量管理方法。
本申请实施例还提供了一种计算机可读存储介质，存储有计算机程序。所述计算机程序被处理器执行时实现如上所述的应用于MEC设备的私有服务质量管理方法，或者应用于基站的私有服务质量管理方法。
附图说明
一个或多个实施例通过与之对应的附图中的图片进行示例性说明，这些示例性说明并不构成对实施例的限定。
图1是本申请实施例提供的私有服务质量管理系统的结构示意图；
图2是图1所示的私有服务质量关系系统中MEC设备、基站与用户设备的交互的示意图；
图3是本申请实施例提供的应用于MEC设备的私有服务管理方法的流程示意图；
图4是本申请实施例提供的应用于MEC设备的私有服务管理方法中实现根据网络性能和承载控制信令数据中携带的初始QoS配置文件，对用户设备进行私有QoS管理的具体流程示意图；
图5是本申请实施例提供的应用于MEC设备的私有服务管理方法中引入私有QoS保障预处理操作的流程示意图；
图6是本申请实施例提供的应用于基站的私有服务管理方法的流程示意图；
图7是本申请实施例提供的应用于基站的私有服务管理方法中针对用户设备为移动设备和固定设备进行私有QoS管理的流程示意图；
图8是本申请实施例提供的私有服务管理设备的结构示意图。
具体实施方式
本申请实施例中术语“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本申请实施例中术语“多个”是指两个或两个以上，其它量词与之类似。
为使本申请实施例的目的、技术方案和优点更加清楚，下面将结合附图对本申请的各实施例进行详细的阐述。然而，本领域的普通技术人员可以理解，在本申请各实施例中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施例的种种变化和修改，也可以实现本申请所要求保护的技术方案。以下各个实施例的划分是为了描述方便，不应对本申请的具体实现方式构成任何限定，各个实施例在不矛盾的前提下可以相互结合相互引用。
本申请实施例的目的在于提供一种私有服务质量管理方法、设备、系统及存储介质，旨在解决上述技术问题。
本申请提出的私有服务质量管理方法、设备、系统及存储介质，通过在ToB业务的园区部署MEC设备，并设置MEC设备根据从基站接收到的用户设备的PDU会话数据来确定网络性能，进而根据用户设备当前的网络性能和从基站接收的用户设备的承载控制信令数据中的初始QoS配置文件对用户设备进行私有QoS管理。由于MEC设备是部署在园区内的，因此对用户设备进行的私有QoS管理是在园区内的进行的，即本申请提供的私有服务管理方案，无需在核心网侧部署繁杂的QoS参数，因此对用户设备的私有QoS管理不会造成公共网络的混乱。
除此之外，通过由园区内的MEC设备根据用户设备当前的网络性能和从基站接收的用户设备的承载控制信令数据中的初始QoS配置文件对用户设备进行私有QoS管理，可以使得对用户设备进行的私有QoS管理更加符合园区对应的私有网络，从而更好的保障用户设备的QoS。
参见图1，图1是本申请实施例提供的私有服务管理系统的结构示意图。
如图1所示，本实施例提供的私有服务管理系统包括：基站100和MEC设备200。
对于基站100，在实现私有服务质量管理时，具体用于获取用户设备的协议数据单元(Protocol Data Unit，PDU)会话数据和承载控制信令数据，承载控制信令数据至少携带了初始服务质量QoS配置文件；根据用户设备对应的标识信息，确定用户设备是否需要进行私有QoS管理。
相应地，若需要，基站100还用于将PDU会话数据和承载控制信令数据传输至MEC设备200，供MEC设备200根据PDU会话数据和承载控制信令中携带的初始QoS配置文件对用户设备进行私有QoS管理；否则，将PDU会话数据和承载控制信令传输至公共网络。
对于MEC设备200，在实现私有服务质量管理时，具体用于接收基站100传输的用户设备的PDU会话数据和承载控制信令数据，承载控制信令数据至少携带了初始服务质量QoS配置文件；根据PDU会话数据，确定用户设备当前的网络性能；根据网络性能和承载控制信令数据中携带的初始QoS配置文件，对用户设备进行私有QoS管理。
为了更好了理解本实施例提供的私有服务质量管理系统中的基站100和MEC设备200是如何配合实现对用户设备的私有QoS管理，以下结合图2进行具体说明：
(1)按照ToB用户的各用户设备300的网络需求，预先设计私有QoS Profile，并将这些私有QoS Profile部署到基站100和MEC设备200中，在保证基站100与MEC设备200能够基于部署的相同的私有QoS Profile完成协议握手，即建立通信连接的情况下，也能够保证对用户设备300进行的私有QoS管理能够正常进行。
具体的，在一个例子中，为了将预先设计的私有QoS Profile部署到基站100和MEC设备200中，可以在基站100和MEC设备200各自的存储区域中部署或新建一个QoS配置文件存储表，然后将预设设计的私有QoS Profile分别添加到基站100和MEC设备200中的QoS配置文件存储表中。
比如，将MEC200中的QoS配置文件存储表称为第一QoS配置文件存储表，将基站100中的QoS配置文件存储表称为第二QoS配置文件存储表。
相应地，存储在第一QoS配置文件存储表的QoS Profile可以称为第一QoS Profile，存储在第二QoS配置文件存储表的QoSProfile可以称为第二QoS Profile。
此外，值得一提的是，为了满足用户设备300多样化的业务场景，在设计私有QoS Profile时需要尽可能的考虑不同业务场景的网络需求，进而生成多个QoS Profile。即，第一QoS配置文件存储表中需要存储至少一种第一QoS Profile。
相应地，第二QoS配置文件存储表中需要存储与第一QoS Profile相同的第二QoS Profile。
此外，在一个例子中，用户设备300可能为固定设备，如智能工厂中关键工位视觉质检的摄像头，或者园区内设置在某一固定区域的收发装置等，此处不再一一列举，本实施例对此也不做限制。
此外，在另一个例子中，用户设备也可能为移动设备，如园区内移动的机器人、基于自动导引车导航技术(Automated Guided Vehicle，AGV)实现的AGV小车等，此处不再一一列举，本实施例对此也不做限制。
此外，为了保障本实施例提供的私有服务质量管理方案能够正常进行，园区内的各用户设备300需要预先接入网络，具体可以是5G网络，并在5G核心网(5G Core，5GC)建立承载。
(2)用户设备300接入网络后，基站100便可以获取用户设备300的PDU会话数据和承载控制信令数据。
在本实施例中，承载控制信令数据至少携带了QoS Profile。
可理解的，在一个例子中，QoS Profile包括一系列的QoS特性和QoS参数，例如误包率(Packet Error Rate，PER)、优先级(Priority Level)、包时延预算(Packet Delay Budget，PDB)等QoS特性，和分配保留优先级(Allocation and Retention Priority，ARP)、最大丢包率(Maximum Packet Loss Rate)、5G QoS等级标识(5G QoS Class Identifier，后文简称5QI)等QoS参数。
此外，可理解的，上述所说的5QI具体是一个标量，用于索引一个5G QoS特性，第三代合作伙伴计划(The Third Generation Partnership Project，3GPP)在第15版(Release 15，R15)协议中规定了5QI1至5QI9、5QI65至5QI67、5QI69、5QI70、5QI75、5QI79至5QI85等5QI值，提供了需要保证流量比特率(Guaranteed Bit Rate，GBR)和不需要保证流量比特率(Non-Guaranteed Bit Rate，NGBR)的资源类型。
需要说明的是，在一个例子中，上述所说的GBR的资源类型有遥控、增强现实等业务场景，而NGBR的资源类型有语音、会话视频、游戏等业务场景。
(3)基站100根据用户设备300对应的标识信息，确定用户设备300是否需要进行私有QoS管理。
本实施例中，本实施例中所说的判断用户设备300是否需要进行私有QoS管理，在基站100侧，具体是指基站100要识别当前获取到的用户设备300的PDU会话数据和承载控制信令数据是要直接发往公共网络(也可以称为外网)，还是园区内的私有网络(也可以称为企业网，或内网)。
需要说明的是，在一个例子中，用于确定用户设备是否需要进行私有QoS管理的标识信息包括但不限于本地网号、网络切片、IP五元组、域名系统(Domain Name System，DNS)中的任意一种。
此外，对于哪些用户设备300是需要进行私有QoS管理的，可以预先设置，如将某一号段的本地网号设置为需要进行私有QoS管理的，则只要是使用这些本地网号接入的用户设备300就是需要进行私有QoS管理的。
此外，通过上述(1)的描述可知，用户设备300可能是固定设备，也可能是移动设备。而对于移动设备，在实现对应的业务时，不仅有自己的网络需求，当其外界网络环境发生变化时，也不能挤占其他用户设备的网络资源，这就需要MEC设备在对移动设备进行私有QoS管理时，不仅要考虑移动设备的PDU会话数据和初始QoS Profile，还需要考虑移动设备当前的位置信息。
因此，基站100在识别出需要进行私有QoS管理的用户设备300后，还需要进一步识别该用户设备300是否是移动设备。
关于如何识别用户设备300是移动设备的方式，以用户设备对应的标识信息为本地网号为例，则可以预先规定某一号段的本地网号对应的用户设备300为移动设备。
在确定当前需要进行私有QoS管理的用户设备300为移动设备时，基站100需要基于预设的基站定位技术，如到达时间差技术来定位移动设备当前的位置信息，并将确定的位置信息添加到承载控制信令数据中。
(4)基站100将不需要进行私有QoS管理的用户设备300的PDU会话数据和承载控制信令数据传输给公共网络，将需要进行私有QoS管理的用户设备300的PDU会话数据和承载控制信令数据传输给部署在园区内的MEC设备200。
通过上述描述可知，对于要进行私有QoS管理的用户设备300是移动设备的情况，在PDU会话数据和承载控制信令数据传输给部署在园区内的MEC设备200时，发送的承载控制信令数据中还携带了用户设备300当前的位置信息。
此外，需要说明的是，基站100在将用户设备300的PDU会话数据和承载控制信令数据发送至公共网络时，具体是先通过传输网络将PDU会话数据和承载控制信令数据发送至5GC，然后再由5GC将PDU会话数据和承载控制信令数据发送至因特网(Internet)，即对接公共网络的用户设备300的PDU会话数据和承载控制信令数据是按照基站100—>传输网络—>5GC—>Internet的传输路径发送到公共网络的。
对于需要进行私有QoS管理的用户设备300的PDU会话数据和承载控制信令数据，基站100是直接通过传输网络传输至部署在园区内的MEC设备200的。
(5)MEC设备200在接收到基站100传输的用户设备300的PDU会话数据和承载控制信令数据后，对PDU会话数据进行解析，进而根据解析结果确定用户设备300当前的网络性能；对承载控制信令数据进行解析，进而提取出承载控制信令数据中携带的初始QoS Profile和用户设备300的当前的位置信息(对于用户设备是移动设备的才能解析出)。
(6)MEC设备200根据确定的网络性能和提取出的初始QoS Profile和用户设备300的当前的位置信息，对用户设备300进行私有QoS管理。
需要说明的，在本实施例中，对用户设备300进行的私有QoS管理分为调整初始QoS Profile和不调整初始QoS Profile两种情况。
具体的，不需要调整初始QoS Profile的，如网络性能满足预设阈值，MEC设备200对初始QoS Profile不作调整，即保存初始QoS Profile不变，直接将用户设备300的PDU会话数据和承载控制信令数据传输至私有网络即可。
对于需要调整初始QoS Profile的，如网络性能不满足预设阈值，MEC设备200便根据需要对初始QoS Profile进行调整，进而得到目标QoS Profile，并将目标QoS Profile下发至基站100。
(7)基站100接收MEC设备200下发的目标QoS Profile，按照目标QoS Profile保障用户设备300的业务。
需要说明的，在一个例子中，需要保证的PDU会话数据和承载控制信令数据经过上述保障流程后，最终也会流入到私有网络。
此外，值得一提是，为了实现对持续上行或下行的业务场景(园区内的某一用户设备仅作为信息发送方或接收方，工作期间不需要根据其他用户设备的反馈才能进行后续工作)的私有QoS保障预处理，MEC设备200在对初始QoS Profile进行调整之前，可以先根据接收到的用户设备300的PDU会话数据确定用户设备300当前的业务场景，然后在确定用户设备300当前的业务场景是持续的上行或下行业务时，先执行私有QoS保障预处理操作，在执行完私有QoS保障预处理操作后，再执行对初始QoS配置文件进行调整的操作；反之，如果用户设备300当前的业务场景不是持续的上行或下行业务，则直接执行对初始QoS配置文件进行调整的操作。
关于上述说的私有QoS保障预处理操作，具体为：
首先，MEC设备200根据用户设备300当前的业务场景生成调度指示信息。
本实施例中所说的调度指示信息会携带用户设备300的索引(可以是上述提到的标识信息，也可以是设备号)、上行或下行调度标志、调度周期时间、调度包大小等参数，此处不再一一列举，本实施例对此也不做限制。
然后，MEC设备200将调度指示信息下发至基站100。
接着，基站100根据调度指示信息与用户设备300进行协商。
本实施例中，基站100接收到调度指示信息后，会按照MEC设备200建议的调度指示，即按照调度指示信息和用户设备300进行协商，旨在协商成功后，能够免去上行或下行业务中产生的PDU会话数据和承载控制质量数据的资源调度请求流程，直接按照协商好的预设调度参数，如预设周期和数据包的预设大小与基站100进行通信交互，从而极大程度的节省网络资源，将所有的网络资源用于有效数据调度。
接着，基站100将协商结果上报给MEC设备200。
本实施例中，如果协商结果是协商成功，则MEC设备200开始执行上述对初始QoS Profile进行调整的操作；否则，重新向基站100下发调度指示信息，即重新执行上述操作。
由此，本实施例提供的私有服务质量管理系统，通过在ToB业务的园区部署MEC设备，并设置MEC设备根据从基站接收到的用户设备的PDU会话数据来确定网络性能，进而根据用户设备当前的网络性能和从基站接收的用户设备的承载控制信令数据中的初始QoS配置文件对用户设备进行私有QoS管理。由于MEC设备是部署在园区内的，因此对用户设备进行的私有QoS管理是在园区内的进行的，即本申请提供的私有服务管理方案，无需在核心网侧部署繁杂的QoS参数，因此对用户设备的私有QoS管理不会造成公共网络的混乱。
此外，通过由园区内的MEC设备根据用户设备当前的网络性能和从基站接收的用户设备的承载控制信令数据中的初始QoS配置文件对用户设备进行私有QoS管理，可以使得对用户设备进行的私有QoS管理更加符合园区对应的私有网络，从而更好的保障用户设备的QoS。
此外，通过将MEC数据分流技术和园区基站定位技术相结合，并对持续上行或下行的业务增加私有QoS保障预处理，对园区内的用户设备提供定制化的私有QoS管理，从而能够更好的满足园区内不同用户设备在不同业务场景下，对大流量带宽、网络时延、误报率等网络性能的极致要求，为5G技术的企业化落地应用起到了促进作用。
参见图3，图3是本申请实施例提供的私有服务质量管理方法的流程图，在本实施例中，该方法主要应用于MEC设备。
此外，需要说明的是，本实施例中所说的MEC设备具体是部署在园区内的。
关于MEC设备，其具有本地数据分流功能(Traffic Offload Function，TOF)。因此，基于这一特性MEC设备能够将本地业务数据分流到私有网络，从而保证私有数据不出园区，以避免企业信息泄露。
同时MEC设备能够对本地业务数据进行计算，即园区内用户设备的业务数据(PDU会话数据和承载控制信令数据)无需转发到公共网络进行计算，而是在企业边缘就进行了处理，从而可以有效的降低网络传输的端到端时延。
基于MEC设备的这些特性，以下结合图3对本实施例提供的私有服务质量管理方法进行具体说明。
如图3所示，本实施例提供的私有服务质量管理方法，包括以下步骤：
步骤301，接收基站传输的用户设备的协议数据单元PDU会话数据和承载控制信令数据。
本实施例中，5G系统主要包括用户面和控制面。对于用户面，需要分流的数据主要是用设备的PDU会话数据，即用户设备具体的传输数据。对于控制面，需要分流的数据主要是用户设备建立PDU会话的承载控制信令数据。
需要说明的，承载控制信令数据通常会携带多种信息，但本实施例重点关注PDU会话建立时，承载控制信令数据中携带的QoS配置文件。因此，MEC设备从基站接收到的用户设备的承载控制信令数据中至少需携带QoS配置文件。
为了便于说明，本实施例将从用户设备侧获取的承载控制信令数据中携带的QoS配置文件称为初始QoS配置文件。
在一个例子中，初始QoS配置文件具体是用户设备接入5GC时所依据的标准QoS协议对应的QoS配置文件。
步骤302，根据PDU会话数据，确定用户设备当前的网络性能。
在一个例子中，MEC设备可以通过对接收到的PDU会话数据进行解析，进而根据解析出的数据与数据之间的时延，和/或包与包之间的误码率，和/或最大丢包率等参数来确定用户设备当前的网络性能。
步骤303，根据网络性能和承载控制信令数据中携带的初始QoS配置文件，对用户设备进行私有QoS管理。
本实施例中，如果网络性能良好，或者说上述各项指标值满足预设阈值，对用户设备进行的私有QoS管理，实质保持初始QoS配置文件不变，直接将PDU会话数据和承载控制信令数据传输至私有网络；如果网络性能出现异常，或者说上述各项指标值不满足预设阈值，根据用户设备进行的私有QoS管理，对初始QoS配置文件进行调整，得到目标QoS配置文件，并将目标QoS配置文件下发至基站，供基站按照目标QoS配置文件保障用户设备的业务。
此外，可理解的，由于用户设备可能是移动设备，因而对于承载控制信令数据是来自移动设备的情况，MEC设备在根据网络性能和承载控制信令数据中携带的初始QoS配置文件，对用户设备进行私有QoS管理时，还会考虑承载控制信令数据中携带的用户设备当前的位置信息。
也就是说，对于用户设备是固定设备的，只需根据PDU会话数据和承载控制信令数据中的初始QoS配置文件，便可以对用户设备进行私有QoS管理；对于用户设备是移动设备的，需要根据根据PDU会话数据、承载控制信令数据中的初始QoS配置文件和位置信息才可以对用户设备进行私有QoS管理。
通过上述描述不难发现，本实施例提供的私有服务质量管理方法，通过在ToB业务的园区部署MEC设备，并设置MEC设备根据从基站接收到的用户设备的PDU会话数据来确定网络性能，进而根据用户设备当前的网络性能和从基站接收的用户设备的承载控制信令数据中的初始QoS配置文件对用户设备进行私有QoS管理。由于MEC设备是部署在园区内的，因此对用户设备进行的私有QoS管理是在园区内的进行的，即本申请提供的私有服务管理方案，无需在核心网侧部署繁杂的QoS参数，因此对用户设备的私有QoS管理不会造成公共网络的混乱。
此外，通过由园区内的MEC设备根据用户设备当前的网络性能和从基站接收的用户设备的承载控制信令数据中的初始QoS配置文件对用户设备进行私有QoS管理，可以使得对用户设备进行的私有QoS管理更加符合园区对应的私有网络，从而更好的保障用户设备的QoS。
参见图4，图4是本申请实施例提供的私有服务质量管理方法的流程图，在本实施例中，该方法主要应用于部署在园区内的MEC设备。
如图4所示，本实施例提供的私有服务质量管理方法，包括以下步骤：
步骤401，接收基站传输的用户设备的协议数据单元PDU会话数据和承载控制信令数据。
步骤402，根据PDU会话数据，确定用户设备当前的网络性能。
不难发现，本实施例中的步骤401和步骤402与图3所示的实施例中的301和步骤302大致相同，在此就不再赘述。
步骤403，判断网络性能是否满足预设阈值。
本实施例中所说的判断网络性能是否满足预设阈值，实质就是确定用户设备是否需要进行私有QoS保障。
若通过判断，确定用户设备当前的网络性能不满足预设阈值，则执行步骤404；否则， 执行步骤405。
步骤404，根据初始QoS配置文件确定目标QoS配置文件，并将目标QoS配置文件下发至基站，供基站按照目标QoS配置文件保障用户设备的业务。
关于步骤404的实现，在一个例子中具体为：
首先，在执行步骤404之前，需要预先在MEC设备中部署第一QoS配置文件存储表，并设置第一QoS配置文件存储表中存储有至少一种第一QoS配置文件；同样，在基站中部署第二QoS配置文件存储表，并在第二QoS配置文件存储表中存储与第一QoS配置文件相同的第二QoS配置文件。
需要说明的是，本实施例中，第一QoS配置文件和第二QoS配置文件为根据用户设备的网络需求预先确定的。
关于确定第一QoS配置文件和第二QoS配置文件的方式，可以是由技术人员人为设计确定的，也可以是基于预设的机器学习算法训练获得的网络模型确定的。
然后，在执行步骤404时根据确定的网络性能，从第一QoS配置文件存储表中选取一个第一QoS配置文件对应的5QI，将选取的5QI作为目标QoS配置文件。
最后，将目标QoS配置文件下发至基站，便可以供基站根据QoS配置文件从第二QoS配置文件存储表中定位5QI对应的第二QoS配置文件，并按照第二QoS配置文件保障用户设备的业务。
对于这种调整策略，由于第一QoS配置文件存储表存储的第一QoS配置文件没有与位置信息建立关联，因而这种调整策略比较适合用户设备为固定设备的情况。
即，对于固定设备，首先对不同的固定设备根据其具体的网络需求，预先设计私有的QoS Profile，即上述所说的第一QoS配置文件和第二QoS配置文件，例如针对无线视频回传业务，自定义不在3GPP协议范围内的5QI值，比如5QI100，在这个新的5QI索引值下，根据固定设备对该视频回传业务的要求，匹配设计针对性的资源类型(比如NGBR)、默认优先级(比如19)、包时延预算(PDB，比如10ms)、误包率(PER，比如10-4)、最大数据突发量(比如1354字节)等QoS特性，和相应的QoS参数；然后将这些设计好的私有QoS Profile分别部署到MEC设备的第一QoS配置文件和基站的第二QoS配置文件。之后，该固定设备在接入网络后，将当前的初始QoS Profile通过承载控制信令数据传输给基站，同时将当前的PDU会话数据也传输给基站，由基站将获取到的PDU会话数据和至少携带了初始QoS Profile的承载控制信令数据传输给MEC设备，MEC设备通过分析，在确定用户设备的当前网络状态不满足预设阈值时，便可以按照上述调整策略对用户设备进行私有QoS管理。
关于步骤404的实现，在另一个例子中具体为：
首先，根据PDU会话数据，确定需要更改的QoS参数。
然后，根据确定的QoS参数，对初始QoS配置文件进行调整，得到目标QoS配置文件。
最后，将目标QoS配置文件下发至基站，供基站按照目标QoS配置文件保障用户设备的业务。
本实施例中，由于QoS Profile包括QoS特征和QoS参数，而QoS参数包括但不限于ARP、MPLR、5QI等，因此如果根据PDU会话数据确定需要更改的QoS参数是ARP，则将初始QoS Profile中的ARP对应的参数值调整为当前确定的参数值，便可以将调整后的初始QoS Profile看作是目标QoS Profile。
此外，需要说明的是，上述给出的调整策略中，对初始QoS Profile的调整是在MEC设备侧完成的，但在实际应用中，更改初始QoS Profile中的某一QoS参数的操作可以是在基站侧进行的，故而MEC设备在确定需要更改的QoS参数后，可以将QoS参数之间下发至基站，由基站根据接收到的QoS参数对初始QoS Profile进行调整即可。
对于这种调整策略，由于不涉及对初始QoS Profile的整体替换，而是仅仅针对初始QoS Profile中的几个QoS参数进行调整，因此这种调整策略不限定用户设备的具体类型，即无论是移动设备，还是固定设备均可采用这种调整策略进行私有QoS管理。
相较于上述依旧预先设计的私有QoS Profile中的5QI为索引的方式，新增或切换QoS Profile，这种仅更改初始QoS Profile中的某个QoS参数值的调整策略，使得基站能够根据得到的目标QoS Profile对用户设备更加精细化的保障。
比如，园区内某个位置的监控在将来一段时间内是非常重要的，MEC设备就可以下发目前该设备初始QoS Profile中某个QoS参数的修改指示，以QoS参数ARP为例，其定义了用户设备资源请求的重要性，在系统资源受限时，ARP参数决定了一个新的QoS流是被接受还是被拒绝，为保障重要工位的监控，MEC设备可决策将ARP参数从默认值修改为最高优先值1。
关于步骤404的实现，在另一个例子中具体为：
首先，在执行步骤404之前，需要预先在MEC设备中部署第一QoS配置文件存储表，并设置第一QoS配置文件存储表中存储有至少一种第一QoS配置文件，同时设置每一第一QoS配置文件对应一位置信息，即建立各第一QoS配置文件与各位置信息之间的对应关系；同样，在基站中部署第二QoS配置文件存储表，并在第二QoS配置文件存储表中存储与第一QoS配置文件相同的第二QoS配置文件。
然后，在执行步骤404时根据承载控制信令数据中携带的用户设备的位置信息，从第一QoS配置文件表中确定与用户设备的位置信息对应的第一QoS配置文件，得到目标QoS配置文。
接着，根据目标QoS配置文件生成切换指令。
最后，将切换指令下发至基站，供基站根据切换指令将用户设备对应的QoS配置文件从初始QoS配置文件切换到与第一QoS配置文件对应的第二QoS配置文件，并按照第二QoS配置文件保障用户设备的业务。
对于这种调整策略，由于第一QoS配置文件存储表存储的第一QoS配置文件与位置信息建立关联，因而这种调整策略比较适合用户设备为移动设备的情况。
即，对于移动设备，首先对不同的移动设备根据其具体的网络需求，以及不同位置信息周围的网络情况，预先设计私有的QoS Profile，即上述所说的第一QoS配置文件和第二QoS配置文件，例如针对无线视频回传业务，自定义不在3GPP协议范围内的5QI值，比如5QI100，在这个新的5QI索引值下，根据移动设备对该视频回传业务的要求，匹配设计针对性的资源类型(比如NGBR)、默认优先级(比如19)、包时延预算(PDB，比如10ms)、误包率(PER，比如10-4)、最大数据突发量(比如1354字节)等QoS特性，和相应的QoS参数；然后将这些设计好的私有QoS Profile分别部署到MEC设备的第一QoS配置文件和基站的第二QoS配置文件，同时在将第一QoS配置文件部署到MEC设备的第一QoS配置文件存储表时，需要建立各第一QoS配置文件与各位置信息之间的对应关系。之后，该移动设备在接入网络后， 将当前的初始QoS Profile通过承载控制信令数据传输给基站，同时将当前的PDU会话数据也传输给基站，由基站将获取到的PDU会话数据和携带了初始QoS Profile、移动设备当前的位置信息的承载控制信令数据传输给MEC设备，MEC设备通过分析，在确定用户设备的当前网络状态不满足预设阈值时，便可以按照上述调整策略对用户设备进行私有QoS管理。
比如，对于移动设备为巡检机器人的业务场景，当巡检机器人到达设备区时，MEC设备下发GBR类型的QoS保障，当巡检机器人进入人员区，MEC设备下发NGBR类型的QoS保障，即针对巡检机器人所处的位置，进行适合的私有QoS管理。
应当理解的是，上述示例仅是为了更好的理解本实施例的技术方案而列举的示例，不作为对本实施例的唯一限制。
此外，需要说明的，在一个例子中，不论是采用上述哪种调整策略，需要保证的PDU会话数据和承载控制信令数据经过上述保障流程后，最终均会流入到私有网络。
步骤405，保持初始QoS配置文件不变，将PDU会话数据和承载控制信令数据传输至私有网络。
由此，本实施例提供的私有服务质量管理方法，基于MEC TOF技术，并结合园区基站定位技术，实现了对园区内的用户设备进行私有QoS管理，并且在对用户设备进行私有QoS管理时，针对用户设备为移动设备和固定设备的情况，分别给出的不同的调整策略，从而使得对用户设备进行的私有QoS管理能够更好的贴合用户设备的实际使用情况，进而保障了服务质量。
参见图5，图5是本申请实施例提供的私有服务质量管理方法的流程图，在本实施例中，该方法主要应用于部署在园区内的MEC设备。
如图5所示，本实施例提供的私有服务质量管理方法，包括以下步骤：
步骤501，接收基站传输的用户设备的协议数据单元PDU会话数据和承载控制信令数据。
步骤502，根据PDU会话数据，确定用户设备当前的网络性能。
不难发现，本实施例中的步骤501和步骤502与图4所示的实施例中的401和步骤402大致相同，在此就不再赘述。
步骤503，判断网络性能是否满足预设阈值。
若通过判断，确定用户设备当前的网络性能满足预设阈值，则执行步骤504；否则，执行步骤505。
步骤504，将PDU会话数据和承载控制信令数据传输至私有网络。
可理解的，对于用户设备当前的网络性能满足预设阈值的情况，同样是保持初始QoS Profile不变，然后将PDU会话数据和承载控制信令数据传输至私有网络。
步骤505，确定用户设备当前的业务场景是否为持续的上行或下行业务。
步骤506，执行私有QoS保障预处理操作。
关于上述说的私有QoS保障预处理操作，具体为：
首先，MEC设备根据用户设备当前的业务场景生成调度指示信息。
具体的说，本实施例中所说的调度指示信息会携带用户设备的索引(可以是上述提到的标识信息，也可以是设备号)、上行或下行调度标志、调度周期时间、调度包大小等参数，此处不再一一列举，本实施例对此也不做限制。
然后，MEC设备将调度指示信息下发至基站。
接着，基站根据调度指示信息与用户设备进行协商。
具体的说，基站接收到调度指示信息后，会按照MEC设备建议的调度指示，即按照调度指示信息和用户设备进行协商，旨在协商成功后，能够免去上行或下行业务中产生的PDU会话数据和承载控制质量数据的资源调度请求流程，直接按照协商好的预设调度参数，如预设周期和数据包的预设大小与基站进行通信交互，从而极大程度的节省网络资源，将所有的网络资源用于有效数据调度。
接着，MEC设备接收基站上报的协商结果。
具体的说，如果协商结果是协商成功，则MEC设备开始执行步骤507的操作；否则，重新向基站下发调度指示信息。
步骤507，根据初始QoS配置文件确定目标QoS配置文件，并将目标QoS配置文件下发至基站，供基站按照目标QoS配置文件保障用户设备的业务。
不难发现，本实施例中的步骤507与图4所示的实施例中的步骤404大致相同，本实施例对此不再赘述。
由此，本实施例提供的私有服务质量管理方法，针对园区内业务场景是大量数据的持续上行或下行传输的业务，通过在MEC设备中增设私有QoS保障预处理功能，并在对用户设备进行私有QoS管理之前，先进行私有QoS保障预处理，即MEC设备下发针对上行或下行业务的调度指示信息，从而指示基站对需要进行私有QoS保障的用户设备的上行或下行数据进行免授权调度，从而实现了资源的最优管理。
此外，通过将私有QoS保障预处理流程和后续的私有QoS管理相结合，从而能够满足这种持续上行或下行传输场景的极致网络需求。
参见图6，图6是本申请实施例提供的私有服务质量管理方法的流程图，在本实施例中，该方法主要应用于基站。
如图6所示，本实施例提供的私有服务质量管理方法，包括以下步骤：
步骤601，获取用户设备的协议数据单元PDU会话数据和承载控制信令数据，承载控制信令数据至少携带了初始服务质量QoS配置文件。
步骤602，根据用户设备对应的标识信息，确定用户设备是否需要进行私有QoS管理。
需要说明的是，在一个例子中，用于确定用户设备是否需要进行私有QoS管理的标识信息包括但不限于本地网号、网络切片、IP五元组、域名系统(Domain Name System，DNS)中的任意一种。
此外，对于哪些用户设备是需要进行私有QoS管理的，可以预先设置，如将某一号段的本地网号设置为需要进行私有QoS管理的，则只要是使用这些本地网号接入的用户设备就是需要进行私有QoS管理的。
步骤603，将PDU会话数据和承载控制信令数据传输至多接入边缘计算MEC设备，供MEC设备根据PDU会话数据和承载控制信令中携带的初始QoS配置文件对用户设备进行私有QoS管理。
此外，在一个例子中，如果用户设备当前的业务场景为持续的上行或下行业务，则基站在将用户设备的PDU会话数据和携带了初始QoS Profile的承载控制信令数据传输至MEC设备后，还会接收MEC设备下发的调度指示信息，然后根据调度指示信息与用户设备进行协商，并将协商结果告知MEC设备，供MEC设备根据协商结果、PDU会话数据和承载控制信 令中携带的初始QoS配置文件对用户设备进行私有QoS管理。
由于本实施例提供的基站在实现私有服务质量管理时，需要与图1至图5所示的实施例中涉及的MEC设备相互配合，因此关于MEC设备如何根据基站上传的用户设备的PDU会话数据和承载控制信令数据对用户设备进行私有QoS管理，详见上述实施例记载的内容即可，本实施例对此不再赘述。
步骤604，将PDU会话数据和承载控制信令传输至公共网络。
即，不对用户设备进行私有QoS管理，PDU会话数据和承载控制信令数据不需要要走私有网络，而是直接进入公共网络。
由此，本实施例提供的私有服务质量管理方法，基站通过与部署在实现ToB业务的园区内的MEC设备按照上述方式进行数据分流处理，将需要进行私有QoS管理的用户设备的PDU会话数据和携带了初始QoS配置文件的承载控制信令数据传输给部署在园区内的MEC设备，由园区内的MEC设备根据用户设备当前的网络性能和从基站接收的用户设备的承载控制信令数据中的初始QoS配置文件对用户设备进行私有QoS管理，从而使得对用户设备进行的私有QoS管理更加符合园区对应的私有网络，进而更好的保障了用户设备的执行的业务的服务质量。
此外，通过上述描述可知，本实施例提供的私有服务质量管理方法，无需在核心网侧部署繁杂的QoS参数，因此对用户设备的私有QoS管理不会造成公共网络的混乱。
参见图7，图7是本申请实施例提供的私有服务质量管理方法的流程图，在本实施例中，该方法主要应用于基站。
如图7所示，本实施例提供的私有服务质量管理方法，包括以下步骤：
步骤701，获取用户设备的协议数据单元PDU会话数据和承载控制信令数据，承载控制信令数据至少携带了初始服务质量QoS配置文件。
步骤702，根据用户设备对应的标识信息，确定用户设备是否需要进行私有QoS管理。
步骤703，将PDU会话数据和承载控制信令传输至公共网络。
不难发现，本实施例中的步骤701至步骤703分别与图6所示的实施例中的步骤601、步骤602和步骤604大致相同，此处步骤赘述。
步骤704，根据标识信息，确定用户设备是否为移动设备。
可理解的，由于用户设备可能是固定设备，也可能是移动设备。由于固定设备的周围环境基本变化不大，由环境因素导致的通信干扰浮动不大，适配的QoS服务可以较长一段时间满足要求，不需要频繁更改或切换。但对于移动设备，在实现对应的业务时，不仅有自己的网络需求，当其外界网络环境发生变化时，也不能挤占其他用户设备的网络资源，这就需要MEC设备在对移动设备进行私有QoS管理时，不仅要考虑移动设备的PDU会话数据和初始QoS Profile，还需要考虑移动设备当前的位置信息。
以移动设备为园区内的巡检机器人为例，其可能在设备区或人员区频繁进出，或可能在通信环境中的“忙小区”或“闲小区”工作，所以需要移动设备的位置信息，除了起到园区导航、资产跟踪的目的以外，还能作为私有QoS保障的前提补充。
因此，基站在识别出需要进行私有QoS管理的用户设备后，还需要进一步识别该用户设备是否是移动设备。
关于如何识别用户设备是移动设备的方式，以用户设备对应的标识信息为本地网号为例，则可以预先规定某一号段的本地网号对应的用户设备为移动设备。
相应地，若确定当前用户设备是移动设备，则执行步骤705；否则，执行步骤706。
步骤705，将PDU会话数据和承载控制信令数据传输至多接入边缘计算MEC设备，供MEC设备根据PDU会话数据和承载控制信令中携带的初始QoS配置文件对用户设备进行私有QoS管理。
不难发现，本实施例中的步骤705与图6所示的实施例中的步骤603大致相同，此处步骤赘述。
步骤706，基于预设的基站定位技术，确定用户设备的位置信息，并将位置信息添加到承载控制信令数据中。
关于预设的基站定位技术，具体可以是达到时间差(Time Difference of Arrival，TDOA)技术。以确定的业务为上行业务为例，选取的TDOA技术具体为上行链路到达时间差(Uplink Time Difference of Arrival，UTDOA)技术。
具体的说，在基于UTDOA技术，确定用户设备的位置信息时，基站(具体可以是基站内的定位测量单元(Location Measurement Unit，LMU))通过测量移动设备发射的上行测量信号的到达时间差，然后根据几何原理便可以计算得到移动终端当前的位置信息。
为了便于理解，以下结合实例进行具体说明：
假设移动设备接入一个5G基站，其上行参考信号(Sounding Reference Signal，SRS)能够被周边多个基站收到，这里采用4个基站接收移动设备的测量信号，形成4个发射与接收点(Transmit and Receive Point，TRP)同时进行SRS解调，根据公式(1)便可以计算出各TRP的上行时延。
Figure PCTCN2021134844-appb-000001
其中，rxtd 1、rxtd 2、rxtd 3、rxtd 4分别为基站1、基站2、基站3、基站4测量的上行到达时间，c为常数，x 1、y 1、z 1为基站1的坐标位置，x 2、y 2、z 2为基站2的坐标位置，x 3、y 3、z 3为基站3的坐标位置，x 4、y 4、z 4为基站4的坐标位置。根据rxtd 1、rxtd 2、rxtd 3、rxtd 4和上4个基站的坐标位置建立4个方程，便可以计算出移动设备的坐标位置x、y、z和DeltaT(多站定时的公共误差)。
应当理解的是，上述示例仅是为了更好的理解本实施例的技术方案而列举的示例，不作为对本实施例的唯一限制。
步骤707，将PDU会话数据和添加了位置信息的承载控制信令数据传输至多接入边缘计算MEC设备，供MEC设备根据PDU会话数据、承载控制信令中携带的初始QoS配置文件和位置信息对用户设备进行私有QoS管理。
由此，本实施例提供的私有服务质量管理方法，基站针对用户设备为移动设备的情况，通过基于预设的基站定位技术确定移动设备当前的位置信息，并将确定的位置信息添加到承载控制信令数据中，从而使得MEC设备在对移动设备进行私有QoS管理时，能够综合考虑移动设备当前的位置信息，从而使得对移动设备进行的私有QoS管理更加符合园区对应的私有网络，进而更好的保障了移动设备的执行的业务的服务质量。
此外，应当理解的是，上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
此外，通过上述描述可知，不论是私有服务质量管理系统涉及的私有服务质量管理方法，还是应用于MEC设备的私有服务质量管理方法，还是应用于基站的私有服务质量管理方法，在具体实现中是相互配合的，因此上述任一实施例中提到的相关技术细节，在其他实施例中依然有效。
参见图8，图8是本申请实施例提供的私有服务管理设备的结构示意图。
如图8所示，本实施例提供的私有服务管理设备包括：包括至少一个处理器801；以及，与至少一个处理器通信连接的存储器802。
其中，存储器802存储有可被至少一个处理器801执行的指令，指令被至少一个处理器801执行，以使至少一个处理器801能够执行上述方法实施例所描述的应用于MEC设备的私有服务质量管理方法，或者应用于基站的私有服务质量管理方法。
通过上述描述可知，私有服务管理设备中的处理器801能够执行上述方法实施例所描述的应用于MEC设备的私有服务质量管理方法，或者应用于基站的私有服务质量管理方法。因此，在一个例子中，如果处理器801执行的是应用于MEC设备的私有服务质量管理方法，那么私有服务管理设备具体是MEC设备；如果处理器801执行的是应用于基站的私有服务质量管理方法，那么私有服务管理设备具体是基站。
此外，值得一提的是，在一个例子中，存储器802和处理器801采用总线方式连接，总线可以包括任意数量的互联的总线和桥，总线将一个或多个处理器801和存储器802的各种电路连接在一起。总线还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路连接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。总线接口在总线和收发机之间提供接口。收发机可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经处理器801处理的数据通过天线在无线介质上进行传输，进一步，天线还接收数据并将数据传送给处理器801。
此外，可理解的，处理器801除了负责管理总线和通常的处理，还可以提供各种功能，包括定时，外围接口，电压调节、电源管理以及其他控制功能。而存储器802还可以被用于存储处理器801在执行操作时所使用的数据。
本申请实施例还涉及一种计算机可读存储介质，存储有计算机程序。计算机程序被处理器执行时实现上述方法实施例所描述的应用于MEC设备的私有服务质量管理方法，或者应用于基站的私有服务质量管理方法。
即，本领域技术人员可以理解，实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设 备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施例是实现本申请的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本申请的精神和范围。

Claims (13)

  1. 一种私有服务质量管理方法，应用于多接入边缘计算MEC设备，所述私有服务质量管理方法包括：
    接收基站传输的用户设备的协议数据单元PDU会话数据和承载控制信令数据，所述承载控制信令数据至少携带了初始服务质量QoS配置文件；
    根据所述PDU会话数据，确定所述用户设备当前的网络性能；
    根据所述网络性能和所述承载控制信令数据中携带的所述初始QoS配置文件，对所述用户设备进行私有QoS管理。
  2. 如权利要求1所述的私有服务质量管理方法，其中，所述根据所述网络性能和所述承载控制信令数据中携带的所述初始QoS配置文件，对所述用户设备进行私有QoS管理，包括：
    判断所述网络性能是否满足预设阈值；
    若不满足，根据所述初始QoS配置文件确定目标QoS配置文件，并将所述目标QoS配置文件下发至所述基站，供所述基站按照所述目标QoS配置文件保障所述用户设备的业务；
    否则，保持所述初始QoS配置文件不变，将所述PDU会话数据和所述承载控制信令数据传输至私有网络。
  3. 如权利要求2所述的私有服务质量管理方法，其中，在所述根据所述初始QoS配置文件确定目标QoS配置文件之前，所述方法还包括：
    根据所述PDU会话数据，确定所述用户设备当前的业务场景；
    如果所述用户设备当前的业务场景为持续的上行或下行业务，执行私有QoS保障预处理操作，并在执行完所述私有QoS保障预处理操作后，执行所述根据所述初始QoS配置文件确定目标QoS配置文件的步骤；
    否则，执行所述根据所述初始QoS配置文件确定目标QoS配置文件的步骤。
  4. 如权利要求3所述的私有服务质量管理方法，其中，所述如果所述用户设备当前的业务场景为持续的上行或下行业务，执行私有QoS保障预处理操作，包括：
    如果所述用户设备当前的业务场景为持续的上行或下行业务，根据所述用户设备当前的业务场景生成调度指示信息；
    将所述调度指示信息下发至所述基站，供所述基站根据所述调度指示信息与所述用户设备进行协商；
    接收所述基站上报的协商结果；
    如果协商成功，确定所述私有QoS保障预处理操作完成；
    否则，重新向所述基站下发所述调度指示信息。
  5. 如权利要求2所述的私有服务质量管理方法，其中，所述MEC设备中部署有第一QoS配置文件存储表，所述第一QoS配置文件存储表中存储有至少一种第一QoS配置文件；所述基站中部署有第二QoS配置文件存储表，所述第二QoS配置文件存储表中存储有与所述第一QoS配置文件相同的第二QoS配置文件；所述第一QoS配置文件和所述第二QoS配置文件根据所述用户设备的网络需求确定；
    所述根据所述初始QoS配置文件确定目标QoS配置文件，并将所述目标QoS配置文件下发至所述基站，供所述基站按照所述目标QoS配置文件保障所述用户设备的业务，包括：
    根据所述网络性能，从所述第一QoS配置文件存储表中选取一个所述第一QoS配置文件 对应的5G QoS等级标识5QI，将选取的所述5QI作为所述目标QoS配置文件；
    将所述目标QoS配置文件下发至所述基站，供所述基站根据所述QoS配置文件从所述第二QoS配置文件存储表中定位所述5QI对应的第二QoS配置文件，并按照所述第二QoS配置文件保障所述用户设备的业务。
  6. 如权利要求2所述的私有服务质量管理方法，其中，所述根据所述初始QoS配置文件确定目标QoS配置文件，并将所述目标QoS配置文件下发至所述基站，供所述基站按照所述目标QoS配置文件保障所述用户设备的业务，包括：
    根据所述PDU会话数据，确定需要更改的QoS参数；
    根据确定的所述QoS参数，对所述初始QoS配置文件进行调整，得到所述目标QoS配置文件；
    将所述目标QoS配置文件下发至所述基站，供所述基站按照所述目标QoS配置文件保障所述用户设备的业务。
  7. 如权利要求2所述的私有服务质量管理方法，其中，所述MEC设备中部署有第一QoS配置文件存储表，所述第一QoS配置文件存储表中存储有至少一种第一QoS配置文件，每一所述第一QoS配置文件对应一位置信息；所述基站中部署有第二QoS配置文件存储表，所述第二QoS配置文件存储表中存储有与所述第一QoS配置文件相同的第二QoS配置文件；所述第一QoS配置文件和所述第二QoS配置文件根据所述用户设备的网络需求确定；所述承载控制信令数据中还行携带有所述用户设备的位置信息，所述位置信息由所述基站基于预设的基站定位技术确定；
    所述对所述初始QoS配置文件确定目标QoS配置文件，并将所述目标QoS配置文件下发至所述基站，供所述基站按照所述目标QoS配置文件保障所述用户设备的业务，包括：
    根据所述承载控制信令数据中携带的所述用户设备的位置信息，从所述第一QoS配置文件表中确定与所述用户设备的位置信息对应的第一QoS配置文件，得到所述目标QoS配置文件；
    根据所述目标QoS配置文件生成切换指令；
    将所述切换指令下发至所述基站，供所述基站根据所述切换指令将所述用户设备对应的QoS配置文件从所述初始QoS配置文件切换到与所述第一QoS配置文件对应的所述第二QoS配置文件，并按照所述第二QoS配置文件保障所述用户设备的业务。
  8. 一种私有服务质量管理方法，应用于基站，所述私有服务质量管理方法包括：
    获取用户设备的协议数据单元PDU会话数据和承载控制信令数据，所述承载控制信令数据至少携带了初始服务质量QoS配置文件；
    根据所述用户设备对应的标识信息，确定所述用户设备是否需要进行私有QoS管理；
    若需要，将所述PDU会话数据和所述承载控制信令数据传输至多接入边缘计算MEC设备，供所述MEC设备根据所述PDU会话数据和所述承载控制信令中携带的所述初始QoS配置文件对所述用户设备进行私有QoS管理；
    否则，将所述PDU会话数据和所述承载控制信令传输至公共网络。
  9. 如权利要求8所述的私有服务质量管理方法，其中，所述将所述PDU会话数据和所述承载控制信令数据传输至多接入边缘计算MEC设备，供所述MEC设备根据所述PDU会话数据和所述承载控制信令中携带的所述初始QoS配置文件对所述用户设备进行私有QoS管 理，包括：
    根据所述标识信息，确定所述用户设备是否为移动设备；
    若是，基于预设的基站定位技术，确定所述用户设备的位置信息，并将所述位置信息添加到所述承载控制信令数据中；
    将所述PDU会话数据和添加了所述位置信息的所述承载控制信令数据传输至多接入边缘计算MEC设备，供所述MEC设备根据所述PDU会话数据、所述承载控制信令中携带的所述初始QoS配置文件和所述位置信息对所述用户设备进行私有QoS管理；
    否则，将所述PDU会话数据和所述承载控制信令数据传输至多接入边缘计算MEC设备，供所述MEC设备根据所述PDU会话数据和所述承载控制信令中携带的所述初始QoS配置文件对所述用户设备进行私有QoS管理。
  10. 如权利要求8至9中任一项所述的私有服务质量管理方法，其中，所述用户设备当前的业务场景为持续的上行或下行业务；
    所述将所述PDU会话数据和所述承载控制信令数据传输至多接入边缘计算MEC设备，供所述MEC设备根据所述PDU会话数据和所述承载控制信令中携带的所述初始QoS配置文件对所述用户设备进行私有QoS管理，包括：
    将所述PDU会话数据和所述承载控制信令数据传输至所述MEC设备；
    接收所述MEC设备下发的调度指示信息；
    根据所述调度指示信息与所述用户设备进行协商，并将协商结果告知所述MEC设备，供所述MEC设备根据所述协商结果、所述PDU会话数据和所述承载控制信令中携带的所述初始QoS配置文件对所述用户设备进行私有QoS管理。
  11. 一种私有服务质量管理设备，包括：
    至少一个处理器；以及，
    与所述至少一个处理器通信连接的存储器；其中，
    所述存储器存储有可被所述至少一个处理器执行的指令，所述指令被所述至少一个处理器执行，以使所述至少一个处理器能够执行如权利要求1至7任一所述的私有服务质量管理方法，或者如权利要求8至10任一项所述的私有服务质量管理方法。
  12. 一种私有服务质量管理系统，包括：多接入边缘计算MEC设备和基站；
    所述MEC设备，用于执行如权利要求1至7任一项所述的私有服务质量管理方法；
    所述基站，用于执行如权利要求8至10任一项所述的私有服务质量管理方法。
  13. 一种计算机可读存储介质，存储有计算机程序，其特征在于，所述计算机程序被处理器执行时实现权利要求1至7中任一项所述的私有服务质量管理方法，或者如权利要求8至10任一项所述的私有服务质量管理方法。
PCT/CN2021/134844 2021-06-07 2021-12-01 私有服务质量管理方法、设备、系统及存储介质 WO2022257379A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110632576.X 2021-06-07
CN202110632576.XA CN115515191A (zh) 2021-06-07 2021-06-07 私有服务质量管理方法、设备、系统及存储介质

Publications (1)

Publication Number Publication Date
WO2022257379A1 true WO2022257379A1 (zh) 2022-12-15

Family

ID=84424721

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/134844 WO2022257379A1 (zh) 2021-06-07 2021-12-01 私有服务质量管理方法、设备、系统及存储介质

Country Status (2)

Country Link
CN (1) CN115515191A (zh)
WO (1) WO2022257379A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117440446A (zh) * 2023-12-20 2024-01-23 商飞智能技术有限公司 一种基于数据分发服务的数据传输方法和装置
CN117440446B (zh) * 2023-12-20 2024-05-31 商飞智能技术有限公司 一种基于数据分发服务的数据传输方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107018534A (zh) * 2016-01-28 2017-08-04 中兴通讯股份有限公司 一种实现移动边缘计算服务的方法、装置及系统
CN111684774A (zh) * 2017-12-25 2020-09-18 诺基亚通信公司 移动边缘计算(mec)中的服务质量(qos)控制
WO2021053006A1 (en) * 2019-09-20 2021-03-25 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. QUALITY OF SERVICE PROFILE CHANGE FOR A MULTI-QoS PROFILE SESSION

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107018534A (zh) * 2016-01-28 2017-08-04 中兴通讯股份有限公司 一种实现移动边缘计算服务的方法、装置及系统
CN111684774A (zh) * 2017-12-25 2020-09-18 诺基亚通信公司 移动边缘计算(mec)中的服务质量(qos)控制
WO2021053006A1 (en) * 2019-09-20 2021-03-25 Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V. QUALITY OF SERVICE PROFILE CHANGE FOR A MULTI-QoS PROFILE SESSION

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117440446A (zh) * 2023-12-20 2024-01-23 商飞智能技术有限公司 一种基于数据分发服务的数据传输方法和装置
CN117440446B (zh) * 2023-12-20 2024-05-31 商飞智能技术有限公司 一种基于数据分发服务的数据传输方法和装置

Also Published As

Publication number Publication date
CN115515191A (zh) 2022-12-23

Similar Documents

Publication Publication Date Title
US10939333B2 (en) Communication method and communications apparatus to implement a network slice based service in a central unit (CU)-distributed unit (DU) architecture
US10798702B2 (en) Periodic frames for control plane data to manage multi-band wireless networking system
US11576073B2 (en) Capacity management methods and apparatus for use in a wireless network
CN110731092B (zh) 实现关于相邻小区中无线电帧配置的信息的交换
WO2020207229A1 (zh) 数据传输方法及相关装置
WO2019158102A1 (zh) 一种确定QoS描述信息的方法和装置
WO2022089002A1 (zh) 多链路低时延通信方法、装置、存储介质和电子装置
JP2015526051A (ja) 端末アクセス方法、システム及び端末
EP2996396A1 (en) Method and device for interworking between access technology networks
EP2922336A1 (en) Method, apparatus, and system for radio bearer control
CN112203330B (zh) QoS流的控制方法及通信装置
CN110519807A (zh) 一种通信方法及装置
US20230379747A1 (en) Method and apparatus to synchronize radio bearers
JP2021530153A (ja) 通信システム
WO2022257379A1 (zh) 私有服务质量管理方法、设备、系统及存储介质
WO2017156789A1 (zh) 基于设备到设备的通信方法和终端
WO2019238050A1 (zh) 一种通信方法及装置
WO2016070701A1 (zh) 无线资源分配方法、通信节点和存储介质
EP4307763A1 (en) Traffic flow processing method, apparatus and system
EP3854127A1 (en) Cellular telecommunications network
CN111432458B (zh) 一种基于双连接的通信方法及装置
WO2019158034A1 (zh) 一种资源分配方法和装置
US20160323780A1 (en) Method and apparatus for using call admission control for client balancing
US10206124B1 (en) Method and apparatus for bidirectional modem
CN113141658B (zh) 一种基于5g nsa语音通话的载波配置方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21944875

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE