Quality of Service (QoS) configuration method, device, equipment, and medium

Abstract

Embodiments of the present invention provide a method, apparatus, device, and medium for configuring quality of service (QoS). The method for configuring quality of service (QoS) includes: sending quality of service (QoS) management information to a base station, which is a base station connected to a mobile edge computing (MEC) device; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information, wherein one cell identifier in the cell identifier list corresponds to one base station, and the QoS management information is used to instruct the base station to create at least one virtual bearer between the user equipment (UE) connected to it. Embodiments of the present invention can reduce the maintenance complexity and cost of network transformation and construction, and solve the latency problem of QoS guarantee.

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a method, device, equipment and medium for configuring quality of service (QoS). Background Art

[0002] With the development of communication technology, the configuration management, configuration distribution, and guaranteed execution of the Quality of Service (QoS) of end-to-end services all rely on numerous core network elements. For example, in the Long Term Evolution (LTE) network, the Home Subscriber Server (HSS), Policy and Charging Rule Function (PCRF) / Subscription Profile Repository (SPR), Policy and Charging Enforcement Function (PCEF), and Service Capability Exposure Framework (SCEF) in the core network are responsible for the configuration management and configuration distribution of end-to-end services. The PDN Gateway (P-GW), Serving GateWay (S-GW), evolved Node B (eNB), and User Equipment (UE) in the core network are responsible for the QoS guarantee execution of end-to-end services. For example, differentiated QoS guarantee execution is based on different user information, different service information, and different location information, based on the PCRF. The two control anchors of the Rx interface (Diameter protocol) or the SCEF northbound interface (generally RESTful HTTP API) establish corresponding dedicated bearers.

[0003] Currently, in some mobile edge computing (MEC) scenarios, it is necessary to manage QoS configuration, issue configurations, and ensure execution of user information, service information, and location information. Figure 1 The figure shows a MEC scenario. Figure 1 There are several problems in this: (1) The introduction of PCC and SCEF increases the maintenance complexity and cost of network transformation and construction; (2) Since the relevant policy gateway is on the core network side, the QoS guarantee with high latency requirements is not effective. Summary of the Invention

[0004] The embodiments of the present invention provide a method, apparatus, device and medium for configuring quality of service (QoS), the purpose of which is to reduce the maintenance complexity and cost of network reconstruction and construction, and to solve the delay problem existing in QoS guarantee.

[0005] In a first aspect, an embodiment of the present invention provides a method for configuring Quality of Service (QoS), which is applied to a server and includes:

[0006] Sending quality of service (QoS) management information to a base station, which is a base station connected to a mobile edge computing (MEC) device. The QoS management information includes a cell identifier list, user information, QoS parameters, and service information. Each cell identifier in the cell identifier list corresponds to a base station. The QoS management information is used to instruct the base station to create at least one virtual bearer between the user equipment (UE) connected to it.

[0007] In a second aspect, an embodiment of the present invention provides a method for configuring quality of service (QoS), which is applied to a base station connected to a mobile edge computing (MEC) device. The method includes:

[0008] Receive quality of service (QoS) management information sent by the server; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information, where each cell identifier in the cell identifier list corresponds to one base station;

[0009] At least one virtual bearer is created between the user equipment UE connected thereto according to the QoS management information.

[0010] In a third aspect, an embodiment of the present invention provides a device for configuring quality of service (QoS), which is applied to a server and includes:

[0011] The sending module is used to send service quality QoS management information to the base station, which is a base station connected to the mobile edge computing MEC device; wherein the QoS management information includes a cell identifier list, user information, QoS parameters and service information. A cell identifier in the cell identifier list corresponds to a base station, and the QoS management information is used to instruct the base station to create at least one virtual bearer between the user equipment UE connected to it.

[0012] In a fourth aspect, an embodiment of the present invention provides a device for configuring quality of service (QoS), which is applied to a base station connected to a mobile edge computing (MEC) device. The device includes:

[0013] a receiving module, configured to receive quality of service (QoS) management information sent by a server; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information, wherein each cell identifier in the cell identifier list corresponds to one base station;

[0014] The creation module is configured to create at least one virtual bearer between the user equipment UE connected thereto according to the QoS management information.

[0015] In the fifth aspect, an embodiment of the present invention provides a quality of service (QoS) configuration device, comprising: at least one processor, at least one memory, and computer program instructions stored in the memory. When the computer program instructions are executed by the processor, the method of the first aspect in the above-mentioned embodiment is implemented.

[0016] In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium having computer program instructions stored thereon, which implements the method of the first aspect in the above-mentioned embodiment when the computer program instructions are executed by a processor.

[0017] The embodiments of the present invention provide a quality of service (QoS) configuration method, apparatus, device, and medium, in which a server sends quality of service (QoS) management information to a base station connected to a mobile edge computing (MEC) device; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information; a cell identifier in the cell identifier list corresponds to a base station; and the QoS management information is used to instruct the base station to create at least one virtual bearer between the user equipment (UE) connected to it; on the one hand, the embodiments of the present invention do not require the introduction of PCC and SCEF, thereby reducing the maintenance complexity and cost of network transformation and construction; on the other hand, the relevant policy gateway is not on the core network side, but close to the user side, thereby solving the problem of high latency requirements for QoS assurance. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0019] Figure 1 Shows the prior art;

[0020] Figure 2 A flowchart of a method for configuring quality of service (QoS) according to some embodiments of the present invention is shown;

[0021] Figure 3 A schematic diagram of an MEC scenario provided according to some embodiments of the present invention is shown;

[0022] Figure 4 A schematic diagram showing downlink QoS provided according to some embodiments of the present invention is shown;

[0023] Figure 5 A schematic diagram of uplink QoS provided according to some embodiments of the present invention is shown;

[0024] Figure 6 A schematic diagram of a device for configuring quality of service (QoS) according to some embodiments of the present invention is shown;

[0025] Figure 7 A schematic diagram of a device for configuring quality of service (QoS) according to some embodiments of the present invention is shown;

[0026] Figure 8 A schematic diagram of a server provided according to some embodiments of the present invention is shown;

[0027] Figure 9 A schematic diagram of a base station provided according to some embodiments of the present invention is shown. DETAILED DESCRIPTION

[0028] The features and exemplary embodiments of various aspects of the present invention will be described in detail below. In order to make the objects, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below in conjunction with the accompanying drawings and Examples. It should be understood that the specific embodiments described herein are only configured to explain the present invention and are not configured to limit the present invention. For those skilled in the art, the present invention can be implemented without the need for some of these specific details. The following description of the embodiments is merely to provide a better understanding of the present invention by illustrating examples of the present invention.

[0029] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, the elements defined by the phrase "comprising..." do not exclude the presence of other identical elements in the process, method, article, or device comprising the elements.

[0030] Figure 2 The flowchart of the QoS configuration method provided by some embodiments of the present invention is shown. Figure 2Only the 4G architecture is used as an example. If the core network is replaced with a 5G architecture, the technical effects of the present invention can also be achieved, so we will not go into details here.

[0031] exist Figure 2 and Figure 3 The QoS configuration method includes:

[0032] Step 201: The server sends quality of service (QoS) management information to a base station, which is a base station connected to a mobile edge computing (MEC) device. The QoS management information includes a cell identifier list, user information, QoS parameters, and service information. Each cell identifier in the cell identifier list corresponds to a base station. The QoS management information is used to instruct the base station to create at least one virtual bearer between the base station and the user equipment (UE) connected to the base station.

[0033] Step 202: The base station receives quality of service (QoS) management information sent by the server. The QoS management information includes a cell identifier list, user information, QoS parameters, and service information. Each cell identifier in the cell identifier list corresponds to one base station.

[0034] Step 203: The base station creates at least one virtual bearer between the base station and the user equipment UE connected thereto according to the QoS management information.

[0035] The quality of service (QoS) configuration method provided by an embodiment of the present invention is that a server sends quality of service (QoS) management information to a base station connected to a mobile edge computing (MEC) device; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information. A cell identifier in the cell identifier list corresponds to a base station, and the QoS management information is used to instruct the base station to create at least one virtual bearer between the user equipment (UE) connected to it; on the one hand, the embodiment of the present invention does not require the introduction of PCC and SCEF, thereby reducing the maintenance complexity and cost of network transformation and construction; on the other hand, the relevant policy gateway is not on the core network side, but close to the user side, thereby solving the problem of high latency requirements for QoS assurance.

[0036] In some embodiments of the present invention, the server sending the quality of service (QoS) management information to the base station in step 201 includes:

[0037] The server periodically sends QoS management information;

[0038] Alternatively, the cell of the base station requests the server to send QoS management information;

[0039] Alternatively, the cell of the base station (i.e., the cell included in the cell identifier list) requests the server to send service quality QoS management information. The server determines whether the QoS management information of the cell has changed. If so, the QoS management information is sent to the base station.

[0040] In some embodiments of the present invention, the QoS management information in step 201 is further used to instruct the base station to update QoS parameters that have a mapping relationship with the default bearer of the UE.

[0041] In one example, QoS management information is located in a server. The QoS management information is used to add, delete, query, and modify mobile user service data flows (SDFs) and their corresponding QoS parameters, and synchronize them to all or part of the evolved Node B (eNodeB) cells of the MEC network as needed. The QoS management information includes at least:

[0042] User information: A user list consisting of one or more tags from the user device's Internet Protocol version 4 (IPv4) address, Internet Protocol version 6 (IPv6) address, Mobile Subscriber International Integrated Service Digital Network (MSISDN), or International Mobile Subscriber Identity (IMSI);

[0043] In the embodiment of the present invention, the IPv4 address, IPv6 address, MSISDN and IMSI are global IDs, and the global ID will not change.

[0044] It should be noted that if the user information is not a global ID, that is, a temporary ID, the base station can determine the global ID corresponding to the temporary ID through a mapping relationship between the temporary ID and the global ID.

[0045] Service information: also known as SDF, is defined by the Internet Protocol (IP) five-tuple (source IP, source port, destination IP, destination port, transport layer protocol) filter;

[0046] Location information: Use the E-UTRAN cell global identifier (ECGI) list to define the target cell where user information, service information, and QoS parameters are to be configured.

[0047] QoS parameters: QCI, Address Resolution Protocol (ARP), Guaranteed Bit Rate (GBR), Master Boot Record (MBR), User Equipment-Aggregated Maximum Bit Rate (UE-AMBR), Access Point Name-Aggregated Maximum Bit Rate (APN-AMBR);

[0048] The implementation of the IP quintuple filter may refer to the mode design of the LTE uplink-traffic filter template (Uplink-Traffic Filter Template, UL-TFT) or the downlink-traffic filter template (Downlink-Traffic Filter Template, DL-TFT).

[0049] In some embodiments of the present invention, the QoS management information described in step 201 also includes: a five-tuple filtering policy; wherein the five-tuple filtering policy is used to instruct the base station to parse the downlink data packet according to the TCP / IP message when receiving the downlink data packet, and map the parsed downlink data packet to a virtual bearer in at least one virtual bearer corresponding to the parsed downlink data packet.

[0050] In one example, message parsing refers to the eNodeB's support for parsing user data messages above the Packet Data Convergence Protocol (PDCP) layer in a specified cell. For example, this includes parsing at the network and transport layers to obtain the IP 5-tuple. Message filtering refers to the eNodeB's support for configuring UL-TFT and DL-TFT based on IP 5-tuple matching rules in a specified cell.

[0051] In some embodiments of the present invention, the type of the virtual bearer may include a GBR bearer or a non-GBR bearer type.

[0052] In one example, the QoS guarantee requirement may be configured as GBR (guaranteed bit rate) and Non-GBR (non-guaranteed bit rate) types.

[0053] GBR types: Address Resolution Protocol (ARP), QoS Class Identifier (QCI), Guaranteed Bit Rate-Uplink (GBR-UL), Guaranteed Bit Rate-Downlink (GBR-DL), Master Boot Record-Uplink (MBR-UL), Master Boot Record-Downlink (MBR-DL);

[0054] Non-GBR type: ARP, QCI, User Equipment Aggregated Maximum Bit Rate Uplink (UE-AMBR-UL), User Equipment Aggregated Maximum Bit Rate Downlink (UE-AMBR-DL), Access Point Name Aggregated Maximum Bit Rate Uplink (APN-AMBR-UL), and Access Point Name Aggregated Maximum Bit Rate Downlink (APN-AMBR-DL).

[0055] The binding relationship of the above information determines the QoS guarantee level and the requirements of users, services and locations.

[0056] In one example, virtual bearer creation and bearer aggregation are implemented in the eNodeB. In this implementation, the concept of virtual bearer creation means that when a UE has only one default bearer, the eNodeB creates one or more virtual radio bearers with different QoS guarantees for its various downlink services. These bearers are identified by a virtual ring buffer-identity document (vRB-ID), which uses the same encoding format as the ring buffer-identity document (RB-ID) to maximize the reuse of the LTE scheduler implementation based on bearer-guaranteed QoS. Virtual bearer aggregation means that the eNodeB manages the mapping between the RB-ID and the vRB-ID (virtual RB-ID) for each user equipment (UE). For the UE, the eNodeB still only exposes the RB-ID of the default bearer over the air interface. For the S1 interface, the eNodeB also exposes only the S1-TEID corresponding to this RB-ID to the S-GW. The default bearer is the mapping between the 3GPP standard and the EPS bearer for a single user.

[0057] In some other embodiments of the present invention, after step 203, the quality of service (QoS) configuration method further includes:

[0058] The base station updates the QoS parameters that have a mapping relationship with the default bearer of the UE.

[0059] In some other embodiments of the present invention, after step 203, the quality of service (QoS) configuration method further includes:

[0060] The base station receives the downlink data packet sent by the server;

[0061] The base station parses the downlink data packet according to the TCP / IP message;

[0062] The base station maps the parsed downlink data packet to a dummy bearer corresponding to the parsed downlink data packet in the at least one dummy bearer.

[0063] The following is an example of downlink QoS protection. Figure 4 Midstream and downlink QoS assurance includes the following steps:

[0064] Step 1: Configure QoS management information on the server;

[0065] User information configuration: A list of users that require a certain QoS guarantee. The type of the list can be one of IPv4 address, IPv6 address, MSISDN, or IMSI.

[0066] Configuration of service information: The characteristics that need to be met by services that require certain QoS guarantees are defined by IP five-tuple (source IP, source port, destination IP, destination port, transport layer protocol) filters, such as using regular expressions to express the corresponding filtering rules.

[0067] Configuration of location information: The network location requirements that require certain QoS guarantees are described by the ECGI list.

[0068] Configuration of QoS parameters: Guaranteed QoS requirements can be configured as GBR (guaranteed bit rate) and Non-GBR (non-guaranteed bit rate) types.

[0069] GBR type: ARP, QCI, GBR-UL, GBR-DL, MBR-UL, MBR-DL;

[0070] Non-GBR type: ARP, QCI, UE-AMBR-UL, UE-AMBR-DL, APN-AMBR-UL, APN-AMBR-DL;

[0071] The binding relationship of the above information determines the QoS guarantee level and the requirements of users, services and locations.

[0072] Step 2: The server sends the configuration to the eNodeB.

[0073] The server selects the corresponding eNodeB based on the ECGI in the location information in the first step and sends the corresponding configuration to the eNodeB.

[0074] Step 3: The eNodeB generates a downlink vRB-ID and its QoS configuration based on the configuration sent.

[0075] The eNodeB sends the corresponding configuration to the corresponding cell functional entity based on the ECGI in the location information in the first step. The cell uses the user information in the first step to create a virtual bearer (vRB-ID) for these users. The virtual bearer is bound to the service feature filter and QoS parameters described in the service information in the first step.

[0076] Step 4: The downlink data of S1-u will be transmitted to the downlink scheduler based on the relationship between RB-ID and vRB-ID;

[0077] When the eNodeB cell receives downlink data from S1-u, it initiates TCP / IP data packet parsing above the PDCP layer for the 3rd Generation Partnership Project (3GPP) standard bearer of the user specified in the user information in the first step. It then directs the data packets that meet the filtering rules described in the service information of the virtual bearer in the third step to the corresponding virtual bearer and then passes them to the scheduler for scheduling.

[0078] Step 5: The eNodeB provides QoS assurance for downlink differentiated service bearers.

[0079] The scheduling results of all vRB-IDs of the same user in the eNodeB cell are reflected on the air interface as the RB-ID of the default bearer.

[0080] Among them, the first to fifth steps correspond to Figure 4 Circles 1 to 5 in the.

[0081] The following is an example of uplink QoS protection. Figure 5 In the upstream QoS, the following steps are included:

[0082] Step 1: Configure QoS management information on the server;

[0083] User information configuration: A list of users that require certain QoS guarantees. The type of the list can be one of IPv4 addresses, IPv6 addresses, Serving-Temporary Mobile Subscriber Identity (S-TMSI), or IMSI.

[0084] Configuration of service information: The characteristics that need to be met by services that require certain QoS guarantees are defined by IP five-tuple (source IP, source port, destination IP, destination port, transport layer protocol) filters, such as using regular expressions to express the corresponding filtering rules.

[0085] Configuration of location information: The network location requirements that require certain QoS guarantees are described by the ECGI list.

[0086] Configuration of QoS parameters: Guaranteed QoS requirements can be configured as GBR (guaranteed bit rate) and Non-GBR (non-guaranteed bit rate) types.

[0087] GBR type: ARP, QCI, GBR-UL, GBR-DL, MBR-UL, MBR-DL;

[0088] Non-GBR type: ARP, QCI, UE-AMBR-UL, UE-AMBR-DL, APN-AMBR-UL, APN-AMBR-DL;

[0089] The binding relationship of the above information determines the QoS guarantee level and the requirements of users, services and locations.

[0090] Step 2: The server sends the configuration to the eNodeB.

[0091] The server selects the corresponding eNodeB based on the ECGI in the location information in step 1 and sends the corresponding configuration to the eNodeB.

[0092] Step 3: The eNodeB updates the QoS configuration for the uplink RB-ID based on the configuration sent.

[0093] The eNodeB sends the corresponding configuration to the corresponding cell functional entity based on the ECGI in the location information in step 1. The cell uses the user information in step 1 to update the QoS parameters of the uplink default bearer of these users and apply them to the scheduler.

[0094] Step 4: The eNodeB provides uplink single-bearer QoS assurance regardless of service.

[0095] Uplink service data flows enter the uplink default bearer and obtain bearer-level QoS guarantees.

[0096] Among them, the first to fifth steps correspond to Figure 5 Circles 1 to 4 in the.

[0097] Figure 6 FIG. 1 shows a schematic diagram of a device for configuring quality of service (QoS) according to some embodiments of the present invention. Figure 6 As shown, the quality of service QoS configuration device 600 includes:

[0098] The sending module 601 is used to send service quality QoS management information to the base station, which is a base station connected to the mobile edge computing MEC; wherein the QoS management information includes a cell identifier list, user information, QoS parameters and service information. One cell identifier in the cell identifier list corresponds to one base station, and the QoS management information is used to instruct the base station to create at least one virtual bearer between the user equipment UE connected to it.

[0099] Optionally, the QoS management information is further used to instruct the base station to update QoS parameters that have a mapping relationship with the default bearer of the UE.

[0100] Optionally, the QoS management information also includes: a five-tuple filtering policy; wherein the five-tuple filtering policy is used to instruct the base station to parse the downlink data packet according to the TCP / IP message when receiving the downlink data packet, and map the parsed downlink data packet to a virtual bearer in at least one virtual bearer corresponding to the parsed downlink data packet.

[0101] Optionally, the type of the virtual bearer includes a GBR bearer or a non-GBR bearer type.

[0102] Figure 7 FIG. 1 is a schematic diagram showing another device for configuring quality of service (QoS) according to some embodiments of the present invention. Figure 7 As shown, the quality of service QoS configuration device 700 includes:

[0103] Receiving module 701, configured to receive quality of service (QoS) management information sent by a server; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information, wherein each cell identifier in the cell identifier list corresponds to one base station;

[0104] The creation module 702 is configured to create at least one virtual bearer between the user equipment UE connected thereto according to the QoS management information.

[0105] Optionally, the quality of service (QoS) configuration device 700 further includes:

[0106] An updating module is used to update the QoS parameters having a mapping relationship with the default bearer of the UE according to the QoS management information.

[0107] Optionally, the quality of service (QoS) configuration device 700 further includes:

[0108] Receiving module, used to receive downlink data packets sent by the server;

[0109] Parsing module, used for parsing downlink data packets according to TCP / IP messages;

[0110] The mapping module is configured to map the parsed downlink data packet to a virtual bearer corresponding to the parsed downlink data packet in at least one virtual bearer.

[0111] Optionally, the type of the virtual bearer includes a GBR bearer or a non-GBR bearer.

[0112] Figure 8 A schematic diagram of the hardware structure of a server provided in an embodiment of the present invention is shown.

[0113] The server may include a processor 801 and a memory 802 storing computer program instructions.

[0114] Specifically, the processor 801 may include a central processing unit (CPU) or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiment of the present invention.

[0115] The memory 802 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 802 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory 802 may include a removable or non-removable (or fixed) medium. Where appropriate, the memory 802 may be inside or outside the data processing device. In a specific embodiment, the memory 802 is a non-volatile solid-state memory. In a specific embodiment, the memory 802 includes a read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), an electrically alterable read-only memory (EAROM) or a flash memory or a combination of two or more of these.

[0116] The processor 801 reads and executes computer program instructions stored in the memory 802 to implement any one of the quality of service (QoS) configuration methods in the above embodiments.

[0117] In one example, the server may further include a communication interface 803 and a bus 810. Figure 8 As shown, the processor 801, the memory 802, and the communication interface 803 are connected via a bus 810 and communicate with each other.

[0118] The communication interface 803 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiment of the present invention.

[0119] The bus 810 includes hardware, software, or both that couples the components of the server to each other. By way of example and not limitation, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an InfiniBand interconnect, a Low Pin Count Bus (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a Peripheral Component Interconnect Express (PCI-Express) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VESA Local Bus, VLB), or other suitable buses, or a combination of two or more of these. Where appropriate, the bus 810 may include one or more buses. Although embodiments of the present invention describe and illustrate a particular bus, the present invention contemplates any suitable bus or interconnect.

[0120] In addition, in conjunction with the QoS configuration method in the above embodiments, embodiments of the present invention may provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any of the QoS configuration methods in the above embodiments is implemented.

[0121] Figure 9 A schematic diagram of the hardware structure of a base station provided by an embodiment of the present invention is shown.

[0122] The base station may include a processor 901 and a memory 902 storing computer program instructions.

[0123] Specifically, the processor 901 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiment of the present invention.

[0124] The memory 902 may include a large capacity memory for data or instructions. By way of example and not limitation, the memory 902 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory 902 may include a removable or non-removable (or fixed) medium. Where appropriate, the memory 902 may be inside or outside the data processing device. In a specific embodiment, the memory 902 is a non-volatile solid-state memory. In a specific embodiment, the memory 902 includes a read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or a flash memory, or a combination of two or more of these.

[0125] The processor 901 reads and executes computer program instructions stored in the memory 902 to implement any one of the quality of service (QoS) configuration methods in the above embodiments.

[0126] In one example, the base station may further include a communication interface 903 and a bus 910. Figure 9 As shown, the processor 901 , the memory 902 , and the communication interface 903 are connected via a bus 910 and communicate with each other.

[0127] The communication interface 903 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiment of the present invention.

[0128] Bus 910 comprises hardware, software or both, and the parts of base station are coupled together.For example, and not limitation, bus can comprise accelerated graphics port (AGP) or other graphics bus, enhanced industry standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industry standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations.In suitable cases, bus 910 can comprise one or more buses.Although the embodiment of the present invention describes and shows specific bus, the present invention considers any suitable bus or interconnection.

[0129] In addition, in conjunction with the QoS configuration method in the above embodiments, embodiments of the present invention may provide a computer-readable storage medium for implementation. The computer-readable storage medium stores computer program instructions; when the computer program instructions are executed by a processor, any of the QoS configuration methods in the above embodiments is implemented.

[0130] It should be understood that the present invention is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, a detailed description of known methods is omitted. In the above embodiments, several specific steps are described and illustrated as examples. However, the method of the present invention is not limited to the specific steps described and illustrated. Those skilled in the art may make various changes, modifications, and additions, or change the order of the steps after understanding the spirit of the present invention.

[0131] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of the present invention are programs or code segments that are used to perform the required tasks. The programs or code segments can be stored in a machine-readable medium, or transmitted on a transmission medium or communication link via a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memories (ROMs), flash memories, erasable ROMs (EROMs), floppy disks, compact disc read-only memories (CD-ROMs), optical discs, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0132] It should also be noted that the exemplary embodiments described herein describe methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the steps described above. In other words, the steps may be performed in the order described in the embodiments, or in a different order, or several steps may be performed simultaneously.

[0133] The above description is only a specific embodiment of the present invention. Those skilled in the art will clearly understand that for the convenience and brevity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the protection scope of the present invention is not limited to this. Any person skilled in the art can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention.

Claims

1. A method for configuring quality of service (QoS), characterized in that: Applied to a server, the method includes: Sending quality of service (QoS) management information to a base station, where the base station is a base station connected to a mobile edge computing (MEC) device; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information, where one cell identifier in the cell identifier list corresponds to one base station, and the QoS management information is used to instruct the base station to create at least one virtual bearer between a user equipment (UE) connected thereto; the QoS management information also includes: a five-tuple filtering policy; wherein the five-tuple filtering policy is used to instruct the base station, upon receiving a downlink data packet, to parse the downlink data packet according to a TCP / IP message, and to map the parsed downlink data packet to a virtual bearer corresponding to the parsed downlink data packet in the at least one virtual bearer; A downlink data packet is sent to the base station so that the base station maps a virtual bearer corresponding to the downlink data packet.

2. The method according to claim 1, characterized in that The QoS management information is further used to instruct the base station to update a QoS parameter that has a mapping relationship with the default bearer of the UE.

3. The method according to claim 1, characterized in that The type of the virtual bearer includes a guaranteed bit rate (GBR) bearer or a non-GBR bearer.

4. A method for configuring quality of service (QoS), characterized in that: Applied to a base station connected to a mobile edge computing (MEC) device, the method includes: Receive quality of service (QoS) management information sent by a server; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information, wherein each cell identifier in the cell identifier list corresponds to one of the base stations, and the QoS management information further includes: a five-tuple filtering policy; wherein the five-tuple filtering policy is used to instruct the base station, upon receiving a downlink data packet, to parse the downlink data packet according to a TCP / IP message, and to map the parsed downlink data packet to a virtual bearer corresponding to the parsed downlink data packet in at least one virtual bearer; creating the at least one virtual bearer between the user equipment UE connected thereto according to the QoS management information; The method further comprises: Receiving a downlink data packet sent by the server; Parsing the downlink data packet according to the TCP / IP message; The parsed downlink data packet is mapped to a dummy bearer corresponding to the parsed downlink data packet in at least one dummy bearer.

5. The method according to claim 4, characterized in that The method further comprises: A QoS parameter having a mapping relationship with a default bearer of the UE is updated according to the QoS management information.

6. The method according to claim 4, characterized in that The type of the at least one virtual bearer includes a GBR bearer or a non-GBR bearer.

7. A device for configuring quality of service (QoS), characterized in that: Applied to a server, the device includes: A sending module, configured to send quality of service (QoS) management information to a base station, wherein the base station is a base station connected to a mobile edge computing (MEC) device; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information, wherein one cell identifier in the cell identifier list corresponds to one base station, and the QoS management information is used to instruct the base station to create at least one virtual bearer between a user equipment (UE) connected thereto; the QoS management information further includes: a five-tuple filtering policy; wherein the five-tuple filtering policy is used to instruct the base station, upon receiving a downlink data packet, to parse the downlink data packet according to a TCP / IP message, and to map the parsed downlink data packet to a virtual bearer corresponding to the parsed downlink data packet in the at least one virtual bearer; The sending module is further configured to send a downlink data packet to the base station so that the base station can map a virtual bearer corresponding to the downlink data packet.

8. A device for configuring quality of service (QoS), characterized in that: Applied to a base station, the base station is connected to a mobile edge computing MEC device, and the device includes: a receiving module, configured to receive quality of service (QoS) management information issued by a server; wherein the QoS management information includes a cell identifier list, user information, QoS parameters, and service information, wherein each cell identifier in the cell identifier list corresponds to one of the base stations; and wherein the QoS management information further includes: a five-tuple filtering policy; wherein the five-tuple filtering policy is configured to instruct the base station, upon receiving a downlink data packet, to parse the downlink data packet according to a TCP / IP message and map the parsed downlink data packet to a virtual bearer corresponding to the parsed downlink data packet in at least one virtual bearer; a creating module, configured to create at least one virtual bearer between a user equipment UE connected thereto according to the QoS management information; The receiving module is further configured to receive downlink data packets sent by the server; A parsing module, configured to parse the downlink data packet according to the TCP / IP message; The mapping module is configured to map the parsed downlink data packet to a virtual bearer corresponding to the parsed downlink data packet in the at least one virtual bearer.

9. A QoS configuration device, characterized in that: include: At least one processor, at least one memory, and computer program instructions stored in the memory, which implement the method according to any one of claims 1 to 3 or 4 to 6 when the computer program instructions are executed by the processor.

10. A computer-readable storage medium having computer program instructions stored thereon, characterized in that: When the computer program instructions are executed by a processor, the method according to any one of claims 1 to 3 or 4 to 6 is implemented.

Images