WO2019126931A1 - Quality of service (qos) control in mobile edge computing (mec) - Google Patents
Quality of service (qos) control in mobile edge computing (mec) Download PDFInfo
- Publication number
- WO2019126931A1 WO2019126931A1 PCT/CN2017/118269 CN2017118269W WO2019126931A1 WO 2019126931 A1 WO2019126931 A1 WO 2019126931A1 CN 2017118269 W CN2017118269 W CN 2017118269W WO 2019126931 A1 WO2019126931 A1 WO 2019126931A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- qos
- qos profile
- mobile device
- mec
- network
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
-
- 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]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
- H04W72/543—Allocation or scheduling criteria for wireless resources based on quality criteria based on requested quality, e.g. QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/76—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
- H04L47/762—Admission control; Resource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions triggered by the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0215—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices
- H04W28/0221—Traffic management, e.g. flow control or congestion control based on user or device properties, e.g. MTC-capable devices power availability or consumption
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Systems, methods, and software for controlling Quality of Service (QoS) selection in Mobile Edge Computing (MEC) services. In one embodiment, a MEC server is at a Radio Access Network (RAN), and implements edge applications that provide the MEC services. The MEC server queries a core network for a QoS policy for a mobile device that indicates QoS profile options for the mobile device, and receives the QoS policy from the core network. The MEC server monitors for a triggering event that triggers selection of a QoS profile, selects the QoS profile from the QoS profile options for a user plane connection established for a MEC service between the mobile device and an edge application in response to the triggering event, and provides a QoS profile identifier for the QoS profile to a base station in the RAN to enforce the QoS profile on the user plane connection.
Description
The invention is related to the field of communication systems and, in particular, to Mobile Edge Computing (MEC) .
MEC is a technology that enables Information Technology (IT) services and cloud computing services at the edge of a mobile network (i.e., within the Radio Access Network (RAN) ) and in close proximity to mobile subscribers. MEC is considered a key emerging technology for Fifth Generation (5G) networks, as processing capability at the edge of the network (e.g., inside or adjacent to a base station, a WiFi hotspot server, etc. ) allows for lower latency and efficient service delivery. A MEC platform is typically a virtualized platform that hosts one or more MEC applications. The MEC applications may operate on downstream data from a core network, and/or on upstream data from mobile devices.
The growth of mobile traffic and pressure on costs are driving a need to implement several changes in order to maintain quality of experience, to generate revenue, and optimize network operations and resource utilization.
Summary
Embodiments described herein provide mechanisms for controlling Quality of Service (QoS) for MEC services provided to mobile devices serviced by a RAN. A MEC server of a RAN implements one or more edge applications that provide MEC services to mobile devices in the RAN. MEC is deployed within the RAN to improve the user experience and more effectively handle latency-sensitive services instead of relying on a core network to provide the services. Providing the MEC services in the RAN allows for service delivery to be adapted according to the load on the RAN, and can reduce the need for long distance backhaul to the core network. A MEC server, as described herein, acquires a QoS policy from the core network for a mobile device. Based on the QoS policy, the MEC server is able to select QoS profiles for MEC services accessed by the mobile device. Thus, QoS profile selection is performed in the RAN instead of relying on the core network to select the QoS profile for each individual MEC service accessed by a mobile device. QoS profile selection in the RAN is advantageous because the MEC server is privy to load conditions in the RAN, an identity of edge applications that provide the MEC services, costs/rates of the MEC services, battery level or other conditions regarding the mobile devices, etc.
One embodiment comprises a MEC server implemented at a RAN of a mobile network that includes a base station. The MEC server includes a memory, and a controller configured to implement one or more edge applications configured to provide MEC services to a mobile device in range of the base station. The controller is configured to implement a policy manager configured to query a core network of the mobile network for a QoS policy for the mobile device that indicates a plurality of QoS profile options for the mobile device, to receive the QoS policy from the core network, and to store the QoS policy in the memory. The controller is also configured to implement a QoS selector configured to monitor for a triggering event that triggers selection of a QoS profile, to select the QoS profile from the QoS profile options for a user plane connection established for a MEC service between the mobile device and an edge application in response to the triggering event, and to provide a QoS profile identifier for the QoS profile to the base station to enforce the QoS profile on the user plane connection.
In another embodiment, the QoS selector is configured to assign a validity timer to the QoS profile.
In another embodiment, the triggering event comprises expiration of the validity timer for a previously-selected QoS profile.
In another embodiment, the triggering event comprises a change in network conditions within the RAN.
In another embodiment, the triggering event comprises a determination in the QoS selector that a battery level in the mobile device drops below a threshold.
In another embodiment, the QoS selector is configured to send a notification to the mobile device indicating the QoS profile identifier.
In another embodiment, the QoS selector is configured to send a notification to the mobile device indicating the QoS profile options, to receive a response from the mobile device selecting one of the QoS profile options, and to select the QoS profile based on the one of the QoS profile options selected by the mobile device.
Another embodiment comprises a method operable in a MEC server. The method comprises querying a core network of the mobile network for a QoS policy for the mobile device that indicates a plurality of QoS profile options for the mobile device, receiving the QoS policy from the core network, storing the QoS policy in the memory, monitoring for a triggering event that triggers selection of a QoS profile, selecting the QoS profile from the QoS profile options for a user plane connection established for a MEC service between the mobile device and an edge application in response to the triggering event, and providing a QoS profile identifier for the QoS profile to the base station to enforce the QoS profile on the user plane connection.
In another embodiment, the method further comprises assigning a validity timer to the QoS profile.
In another embodiment, the method further comprises sending a notification to the mobile device indicating the QoS profile identifier.
In another embodiment, the step of selecting the QoS profile comprises sending a notification to the mobile device indicating the QoS profile options, receiving a response from the mobile device selecting one of the QoS profile options, and selecting the QoS profile based on the one of the QoS profile options selected by the mobile device.
Another embodiment comprises a non-transitory computer readable medium embodying programmed instructions executed by one or more processors, wherein the instructions direct the processors to implement a MEC server implemented at a RAN of a mobile network that includes a base station. The MEC server implements one or more edge applications configured to provide MEC services to a mobile device in range of the base station. The MEC server queries a core network of the mobile network for a QoS policy for the mobile device that indicates a plurality of QoS profile options for the mobile device, receives the QoS policy from the core network, and stores the QoS policy in the memory. The MEC server monitors for a triggering event that triggers selection ofa QoS profile, selects the QoS profile from the QoS profile options for a user plane connection established for a MEC service between the mobile device and an edge application in response to the triggering event, and provides a QoS profile identifier for the QoS profile to the base station to enforce the QoS profile on the user plane connection.
Another embodiment comprises a MEC server implemented at a RAN of a mobile network that includes a base station. The MEC server includes a means for implementing one or more edge applications configured to provide MEC services to a mobile device in range of the base station. The MEC server includes a means for querying a core network of the mobile network for a QoS policy for the mobile device that indicates a plurality of QoS profile options for the mobile device, a means for receiving the QoS policy from the core network, and a means for storing the QoS policy in the memory. The MEC server also includes a means for monitoring for a triggering event that triggers selection of a QoS profile, a means for selecting the QoS profile from the QoS profile options for a user plane connection established for a MEC service between the mobile device and an edge application in response to the triggering event, and a means for providing a QoS profile identifier for the QoS profile to the base station to enforce the QoS profile on the user plane connection.
The above summary provides a basic understanding of some aspects of the specification. This summary is not an extensive overview of the specification. It is intended to neither identify key or critical elements of the specification nor delineate any scope of the particular embodiments of the specification, or any scope of the claims. Its sole purpose is to present some concepts of the specification in a simplified form as a prelude to the more detailed description that is presented later.
Description of the Drawings
Some embodiments of the invention are now described, by way of example only, and with reference to the accompanying drawings. The same reference number represents the same element or the same type of element on all drawings.
FIG. 1 illustrates a mobile network in an illustrative embodiment.
FIG. 2 is a block diagram of a MEC server in an illustrative embodiment.
FIG. 3 is a flow chart illustrating a method of acquiring a QoS policy for a mobile device in an illustrative embodiment.
FIG. 4 illustrates a QoS policy in an illustrative embodiment.
FIG. 5 is a flow chart illustrating a method of selecting a QoS profile for a user plane connection established for a MEC service for a mobile device in an illustrative embodiment.
FIG. 6 is a flow chart illustrating additional steps of selecting a QoS profile in an illustrative embodiment.
FIG. 7 illustrates a non-roaming architecture of a next generation network in an illustrative embodiment.
FIG. 8 is a signaling diagram illustrating MEC QoS control in an illustrative embodiment.
FIG. 9 illustrates a network architecture in an illustrative embodiment.
Description of Embodiments
The figures and the following description illustrate specific exemplary embodiments. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the embodiments and are included within the scope of the embodiments. Furthermore, any examples described herein are intended to aid in understanding the principles of the embodiments, and are to be construed as being without limitation to such specifically recited examples and conditions. As a result, the inventive concept (s) is not limited to the specific embodiments or examples described below, but by the claims and their equivalents.
FIG. 1 illustrates a mobile network 100 in an illustrative embodiment. Mobile network 100, which may also be referred to as a cellular network, is a type of communication network where the last link to end user devices is wireless. Mobile network 100 may represent a next generation network, such as a 5G network. In this embodiment, mobile network 100 includes a core network 110 and a Radio Access Network (RAN) 120. Core network 110 is the central part of mobile network 100 that provides various services to subscribers who connect to core network 110 via RAN 120. Core network 110 may include a Session Management Function (SMF) , a User Plane Function (UPF) , etc., in a next generation example. In this embodiment, core network 110 includes a policy control element 112 and a subscriber server 114. Policy control element 112 comprises a network device, physical node, or virtual function configured to provide policy control for mobile network 100. One example of policy control element 112 is a Policy Control Function (PCF) of a next generation network. Subscriber server 114 comprises a network device, physical node, or virtual function configured to store service plans for end users. One example of subscriber server 114 is a Home Subscriber Server (HSS) and/or a Unified Data Management (UDM) element of a next generation network. Core network 110 is shown as connecting to one or more external data networks 130 also referred to as Packet Data Networks (PDN) . External data networks 130 may include an operator external public or private data network, or an intra-operator data network (e.g., for IMS services) .
In this embodiment, MEC is implemented in RAN 120. MEC is a technology that enables the deployment of services (e.g., IT services and cloud services) within RAN 120 to more effectively provide latency-sensitive services and improve user experience. To implement MEC, compute capabilities are implemented at one or more base stations 122 of RAN 120. For instance, a MEC server 124 is implemented at base station 122 of RAN 120, and is configured to provide MEC services to mobile devices (e.g., mobile device 140) in range of base station 122. When referred to as being implemented “at” base station 122, MEC server 124 maybe part of base station 122 (i.e., part of the controller of base station 122) or may be an external server deployed between base station 122 and core network 110, such as on the S 1 interface. MEC server 124 hosts, executes, or runs one or more edge applications (APP) 126-128. An edge application is an application that provides a MEC service to one or more mobile devices in range of base station 122 as opposed to core network 110 providing the MEC service. Thus, mobile device 140 may be in communication with one or more of edge applications 126-128 in MEC server 124 when receiving a MEC service from mobile network 100, and the MEC service does not have to be provided by a network element within core network 110. This allows for MEC services to be provided with lower latency as the MEC services are provided by RAN 120 as opposed to core network 110.
Communications between mobile device 140 and MEC server 124 may be divided into control plane transmissions and user plane transmissions. The control plane is a network plane that carries signaling traffic, and the user plane (also referred to as the data plane, forwarding plane, or bearer plane) is the network plane that carries user data traffic, such as voice and data traffic. User data traffic (downlink (DL) and/or uplink (UL) ) is carried on data radio bearers (DRB) of the user plane between base station 122 and mobile device 140. A DRB is a virtual connection between two endpoints for transporting traffic based on a set of attributes over the air interface.
As an overview of the embodiments described herein, mobile device 140 attaches to RAN 120 and registers with core network 110. A session may be established between mobile device 140 and core network 110, such as a Packet Data Unit (PDU) session. The session may be initiated by mobile device 140, or a network may initiate the session via a device trigger message. An example of session establishment procedures in next generation networks may be found in 3GPP TS 23.502 (version 1.3.0) , which is incorporated by reference as if fully included herein. Within a session, mobile device 140 may initiate service request procedures to request a MEC service, such as to send uplink data. A service request procedure for next generation networks is used to activate/establish a user plane connection for a session. When MEC is implemented as in the present embodiment, the user plane connection for a MEC service is between mobile device 140 and an edge application 126-128 of MEC server 124 instead of between mobile device 140 and a UPF of a core network (e.g., core network 110) . MEC server 124 may also initiate service request procedures to request a MEC service, such as to send DL data to mobile device 140. Either way, a user plane connection is established between mobile device 140 and an edge application 126-128 in response to a service request procedure. And, multiple service request procedures may be performed during a session to establish multiple user plane connections between mobile device 140 and one or more edge applications 126-128 in MEC server 124.
In the embodiments described herein, MEC server 124 selects a QoS for the user plane connections established for mobile device 140 (and other mobile devices served by RAN 120) for MEC services. MEC server 124 obtains a QoS policy from core network 110, and selects the QoS for user plane connections based on the QoS policy. Thus, the QoS for individual user plane connections in RAN 120 is actually selected within RAN 120 (i.e., by MEC server 124) instead of being selected by core network 110.
FIG. 2 is a block diagram of MEC server 124 in an illustrative embodiment. MEC server 124 is implemented on a MEC platform 200. MEC platform 200 refers to a pool of physical resources in RAN 120 that are used to implement MEC server 124 and possibly other MEC servers within RAN 120. MEC platform 200 may include the physical resources of compute resources, storage resources, and network resources.
In this embodiment, MEC server 124 is an apparatus that includes a network interface component 202, a controller 204, and a memory 206. Network interface component 202 is a component (e.g., hardware) configured to communicate with base station 122 (and other base stations of RAN 120) and core network 110. Network interface component 202 may be able to interpret a variety of protocols. Controller 204 represents a component that provides the functions of MEC server 124 through one or more processors or other physical resources. Controller 204 is able to communicate with base station 122 and core network 110 through network interface component 202. Memory 206 is a local computer readable storage medium (e.g., ROM or flash memory) for data, instructions, applications, etc., and is accessible by controller 204. MEC server 124 may include various other components not specifically illustrated in FIG. 2.
FIG. 3 is a flow chart illustrating a method 300 of acquiring a QoS policy for mobile device 140 in an illustrative embodiment. The steps of method 300 will be described with reference to MEC server 124 in FIGS. 1-2, but those skilled in the art will appreciate that method 300 may be performed in other devices. The steps of the flow charts described herein are not all inclusive and may include other steps not shown, and the steps may be performed in an alternative order.
Responsive to a determination to acquire a QoS policy for mobile device 140, policy manager 210 queries core network 110 for the QoS policy for mobile device 140 (step 306) . A QoS policy is a set of information determined by core network 110 which allows MEC server 124 to select a QoS profile for a user plane connection established for a MEC service. In this embodiment, the QoS policy includes a plurality of QoS profile options for mobile device 140. Policy manager 210 receives the QoS policy from core network 110 (step 308) , and stores the QoS policy 220 in memory 206 (step 310) . Ifa previous QoS policy 220 is stored in memory 206, then policy manager 210 may delete the previous QoS policy 220 when storing the newly-received QoS policy 220. Core network 110 or policy manager 210 may assign a validity timer to QoS policy 220, which may be stored in memory 206 along with QoS policy 220. Method 300 then returns to step 304. Thus, policy manager 210 keeps an updated copy of the QoS policy 220 for mobile device 140 in memory 206, which may be used to select QoS profiles for MEC services that are initiated for mobile device 140.
FIG. 4 illustrates a QoS policy 220 in an illustrative embodiment. QoS policy 220 may include a mobile device ID for mobile device 140. QoS policy 220 also includes a plurality of QoS profile options 401-404. Each QoS profile option 401-404 is associated with a QoS profile, and may include the following parameters: selection criteria 410, a QoS profile identifier (ID) 411, a charging plan 412, and additional QoS information 413. These parameters indicate one possible example, and QoS profile options 401-404 may include different or additional parameters in other embodiments. The selection criteria 410 are rules, conditions, information, etc., used to select a QoS profile. For example, the selection criteria 410 may include a location of a mobile device, time-of-day/day-of-week, an edge application ID, a MEC service type, network conditions (e.g., MEC server load, RAN usage, etc. ) , any device information that can be detected by RAN 120 such as UE battery level, etc. The QoS profile ID 411 is mapped to, points to, or is used to indicate a particular QoS profile. The charging plan 412 indicates the charging rate for a QoS profile, and may be static or dynamic. A dynamic charging rate may be based on the selection criteria 410 or other criteria. The additional QoS information 413 may include a special bit rate, notification control parameters, etc.
A QoS profile contains QoS parameters that define the QoS for a user plane connection, such as a QoS ID (e.g., 5QI) , an Allocation and Retention Priority (ARP) , Guaranteed Flow Bit Rate (GFBR) and Maximum Flow Bit Rate (MFBR) for UL and DL traffic for a Guaranteed Bit Rate (GBR) flow, a Reflective QoS Attribute (RQA) for a non-GBR flow, notification control, etc. The QoS ID references QoS characteristics that describe the packet forwarding treatment for a QoS flow between a mobile device and a MEC server, such as resource type (GBR, delay critical GBR, or Non-GBR) , priority level, packet delay budget, packet error rate, and averaging window.
FIG. 5 is a flow chart illustrating a method 500 of selecting a QoS profile for a user plane connection established for a MEC service for mobile device 140 in an illustrative embodiment. The steps of method 500 will be described with reference to MEC server 124 in FIGS. 1-2, but those skilled in the art will appreciate that method 500 may be performed in other devices.
In response to detecting a triggering event, QoS selector 212 selects a QoS profile for a user plane connection established for the MEC service between mobile device 140 and an edge application 126-128 from QoS profile options 401-404 in QoS policy 220 (step 504) . The QoS profile specifies the QoS parameters to enforce for the user plane connection established for the MEC service. QoS selector 212 processes the selection criteria 410 for the QoS profile options 401-404 to select the QoS profile associated with one of the QoS profile options 401-404. For example, QoS selector 212 may consider the location of mobile device 140, the edge application ID of the edge application 126-128 set to provide the MEC service, the service type of the MEC service (e.g., a video service, an AR service, etc. ) , load conditions within RAN 120, another other criteria in selecting the QoS profile. QoS selector 212 may also consider the charging plans associated with each of the QoS profile options 401-404 when selecting the QoS profile. QoS selector 212 may also assign a validity timer to the selected QoS profile.
In one embodiment, QoS selector 212 may interact with mobile device 140 when selecting the QoS profile for a MEC service. FIG. 6 is a flow chart illustrating additional steps of selecting a QoS profile in an illustrative embodiment. The steps shown in FIG. 6 may be performed before or concurrent with step 504 in FIG. 5. QoS selector 212 sends a notification to mobile device 140 indicating the QoS profile options 401-404 (step 602) . In response to the notification, mobile device 140 may interact with its end user to select one of the QoS profile options 401-404. QoS selector 212 receives a response from mobile device 140 selecting one of the QoS profile options 401-404 (step 604) . QoS selector 212 may then select the QoS profile for the user plane connection established for the MEC service between mobile device 140 and an edge application 126-128 based on the QoS profile option selected by mobile device 140 (step 504) . QoS selector 212 is in charge of making the final selection of the QoS profile, but may consider the input from mobile device 140 and its end user when making the final selection.
FIG. 7 illustrates a non-roaming architecture 700 of a next generation network in an illustrative embodiment. The architecture in FIG. 7 is a reference point representation, as is further described in 3GPP TS 23.501 (version 1.5.0) , which is incorporated by reference as if fully included herein. The control plane of architecture 700 includes Authentication Server Function (AUSF) 710, a Unified Data Management (UDM) element 712, a Network Slice Selection Function (NSSF) 713, an Access and Mobility Management Function (AMF) 714, a Session Management Function (SMF) 716, a Policy Control Function (PCF) 718, and an Application Function (AF) 720. The user plane of architecture 700 includes a User Plane Function (UPF) 724 that communicates with a Data Network (DN) 726. A (Radio) Access Network ( (R) AN) 730 and User Equipment (UE) 732 are able to access the control plane and the user plane.
In this embodiment, MEC services are provided within architecture 700. For the MEC services, a MEC server 740 is implemented at (R) AN 730, a MEC QoS Management Function (MQMF) 746 is implemented at SMF 716, and a MEC QoS Policy Function (MQPF) 748 is implemented at PCF 718. MEC server 740 provides MEC services through edge applications running on MEC server 740. MEC server 740 is also in charge of selecting QoS profiles for MEC services/edge applications that are serving UE 732. MQPF 748 is introduced on PCF 718, and is configured to generate a MEC QoS policy for UE 732. The MEC QoS policy includes QoS profile options for UE 732, and each QoS profile option may include a MEC QoS Flow ID (QFI) , conditions of applying this QFI, a charging plan for the QFI, etc. MQPF 748 may be triggered by SMF 716 in a scenario such as PDU session establishment/modification, location change of UE 732, MEC service update, etc. MQPF 748 provides the MEC QoS policy to MQMF 746.
FIG. 8 is a signaling diagram illustrating MEC QoS control in an illustrative embodiment. The scenario shown in FIG. 8 is for PDU session establishment. However, similar signaling may occur for scenarios, such as MEC session establishment/modification procedures, UE attach procedures, etc. In order to establish a new PDU session, UE 732 generates a new PDU session ID. UE 732 initiates the UE-requested PDU session establishment procedure by the transmission of a NAS message containing a PDU Session Establishment Request within the N1 SM container. The Request Type indicates “Initial request” if the PDU Session Establishment is a request to establish a new PDU session and indicates “Existing PDU Session” if the request refers to an existing PDU session between 3GPP access and non-3GPP access or to an existing PDN connection in EPC. The NAS message sent by UE 732 is encapsulated by (R) AN 730 in a N2 message towards AMF 714 that should include User location information and Access Technology Type Information.
With the MEC QoS policy, MEC server 740 monitors for a triggering event that triggers selection of a QoS profile for a MEC service, such as a service request for a MEC service initiated by UE 732 or an edge application in MEC server 740. In response to detecting a triggering event, MEC server 740 selects a QoS profile for a user plane connection established for the MEC service between UE 732 and an edge application on MEC server 740 based on the MEC QoS policy. For example, MEC server 740 may consider the location of UE 732, the edge application ID of the edge application set to provide the MEC service, the service type of the MEC service (e.g., a video service, an AR service, etc. ) , load conditions within (R) AN 730, charging plans associated with each QoS profile, etc. MEC server 740 then enforces the selected QoS profile by providing the QFI that is mapped to the selected QoS profile to a base station in (R) AN 730. MEC server 740 may optionally send the QoS profile ID (or the QoS profile itself) to UE 732.
In one embodiment, the MEC platform (e.g., MEC platform 200) for a MEC server (e.g., MEC server 124) may be implemented with a virtualized architecture. FIG. 9 illustrates a network architecture 900 in an illustrative embodiment. Network architecture 900 uses Network Functions Virtualization (NFV) , which is a concept that virtualizes classes of network node functions into building blocks that may connect or chain together to create communication services, which are MEC services in this embodiment. Architecture 900 includes an NFV infrastructure 910, which includes hardware resources 911, such as compute resources 912, storage resources 913, and network resources 914. NFV infrastructure 910 also includes a virtualization layer 915, which is able to create virtual compute resources 916, virtual storage resources 917, and virtual network resources 918.
Any of the various elements or modules shown in the figures or described herein may be implemented as hardware, software, firmware, or some combination of these. For example, an element may be implemented as dedicated hardware. Dedicated hardware elements may be referred to as “processors” , “controllers” , or some similar terminology. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term “processor” or “controller” should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, a network processor, application specific integrated circuit (ASIC) or other circuitry, field programmable gate array (FPGA) , read only memory (ROM) for storing software, random access memory (RAM) , non-volatile storage, logic, or some other physical hardware component or module.
Also, an element may be implemented as instructions executable by a processor or a computer to perform the functions of the element. Some examples of instructions are software, program code, and firmware. The instructions are operational when executed by the processor to direct the processor to perform the functions of the element. The instructions may be stored on storage devices that are readable by the processor. Some examples of the storage devices are digital or solid-state memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media.
Although specific embodiments were described herein, the scope of the disclosure is not limited to those specific embodiments. The scope of the disclosure is defined by the following claims and any equivalents thereof.
Claims (20)
- A system comprising:a Mobile Edge Computing (MEC) server implemented at a Radio Access Network (RAN) of a mobile network that includes a base station, the MEC server comprising:a memory; anda controller configured to implement at least one edge application configured to provide MEC services to a mobile device in range of the base station;the controller is configured to implement a policy manager configured to query a core network of the mobile network for a Quality of Service (QoS) policy for the mobile device that indicates a plurality of QoS profile options for the mobile device, to receive the QoS policy from the core network, and to store the QoS policy in the memory;the controller is configured to implement a QoS selector configured to monitor for a triggering event that triggers selection of a QoS profile, to select the QoS profile from the QoS profile options for a user plane connection established for a MEC service between the mobile device and the at least one edge application in response to the triggering event, and to provide a QoS profile identifier for the QoS profile to the base station to enforce the QoS profile on the user plane connection.
- The system of claim 1 wherein:the QoS selector is configured to assign a validity timer to the QoS profile.
- The system of claim 2 wherein:the triggering event comprises expiration of the validity timer for a previously-selected QoS profile.
- The system of claim 1 wherein:the triggering event comprises a change in network conditions within the RAN.
- The system of claim 1 wherein:the triggering event comprises a determination in the QoS selector that a battery level in the mobile device drops below a threshold.
- The system of claim 1 wherein:the QoS selector is configured to send a notification to the mobile device indicating the QoS profile identifier.
- The system of claim 1 wherein:the QoS selector is configured to send a notification to the mobile device indicating the QoS profile options, to receive a response from the mobile device selecting one of the QoS profile options, and to select the QoS profile based on the one of the QoS profile options selected by the mobile device.
- A method operable in a Mobile Edge Computing (MEC) server implemented at a Radio Access Network (RAN) of a mobile network that includes a base station, wherein the MEC server implements at least one edge application configured to provide MEC services to a mobile device in range of the base station, the method comprising:querying a core network of the mobile network for a Quality of Service (QoS) policy for the mobile device that indicates a plurality of QoS profile options for the mobile device;receiving the QoS policy from the core network;storing the QoS policy in the memory;monitoring for a triggering event that triggers selection of a QoS profile;selecting the QoS profile from the QoS profile options for a user plane connection established for a MEC service between the mobile device and the at least one edge application in response to the triggering event; andproviding a QoS profile identifier for the QoS profile to the base station to enforce the QoS profile on the user plane connection.
- The method of claim 8 further comprising:assigning a validity timer to the QoS profile.
- The method of claim 9 wherein:the triggering event comprises expiration of the validity timer for a previously-selected QoS profile.
- The method of claim 8 wherein:the triggering event comprises a change in network conditions within the RAN.
- The method of claim 8 wherein:the triggering event comprises a determination that a battery level in the mobile device drops below a threshold.
- The method of claim 8 further comprising:sending a notification to the mobile device indicating the QoS profile identifier.
- The method of claim 8 wherein selecting the QoS profile comprises:sending a notification to the mobile device indicating the QoS profile options;receiving a response from the mobile device selecting one of the QoS profile options; andselecting the QoS profile based on the one of the QoS profile options selected by the mobile device.
- A non-transitory computer readable medium embodying programmed instructions executed by one or more processors, wherein the instructions direct the processors to implement:a Mobile Edge Computing (MEC) server implemented at a Radio Access Network (RAN) of a mobile network that includes a base station;the MEC server implements at least one edge application configured to provide MEC services to a mobile device in range of the base station;the MEC server queries a core network of the mobile network for a Quality of Service (QoS) policy for the mobile device that indicates a plurality of QoS profile options for the mobile device, receives the QoS policy from the core network, and stores the QoS policy in the memory;the MEC server monitors for a triggering event that triggers selection of a QoS profile, selects the QoS profile from the QoS profile options for a user plane connection established for a MEC service between the mobile device and the at least one edge application in response to the triggering event, and provides a QoS profile identifier for the QoS profile to the base station to enforce the QoS profile on the user plane connection.
- The computer readable medium of claim 15 wherein:the MEC server assigns a validity timer to the QoS profile.
- The computer readable medium of claim 16 wherein:the triggering event comprises expiration of the validity timer for a previously-selected QoS profile.
- The computer readable medium of claim 15 wherein:the triggering event comprises a change in network conditions within the RAN.
- The computer readable medium of claim 15 wherein:the triggering event comprises a determination that a battery level in the mobile device drops below a threshold.
- The computer readable medium of claim 15 wherein:the MEC server sends a notification to the mobile device indicating the QoS profile options, receives a response from the mobile device selecting one of the QoS profile options, and selects the QoS profile based on the one of the QoS profile options selected by the mobile device.
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201780098251.XA CN111684774B (en) | 2017-12-25 | 2017-12-25 | Quality of service (QOS) control method and system in Mobile Edge Computing (MEC) |
PCT/CN2017/118269 WO2019126931A1 (en) | 2017-12-25 | 2017-12-25 | Quality of service (qos) control in mobile edge computing (mec) |
EP17936033.4A EP3732846B1 (en) | 2017-12-25 | 2017-12-25 | Quality of service (qos) control in mobile edge computing (mec) |
US16/956,236 US11134410B2 (en) | 2017-12-25 | 2017-12-25 | Quality of service (QoS) control in mobile edge computing (MEC) |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2017/118269 WO2019126931A1 (en) | 2017-12-25 | 2017-12-25 | Quality of service (qos) control in mobile edge computing (mec) |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2019126931A1 true WO2019126931A1 (en) | 2019-07-04 |
Family
ID=67062784
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/118269 WO2019126931A1 (en) | 2017-12-25 | 2017-12-25 | Quality of service (qos) control in mobile edge computing (mec) |
Country Status (4)
Country | Link |
---|---|
US (1) | US11134410B2 (en) |
EP (1) | EP3732846B1 (en) |
CN (1) | CN111684774B (en) |
WO (1) | WO2019126931A1 (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2021093158A1 (en) | 2020-01-13 | 2021-05-20 | Zte Corporation | A method for adaptively configuring transmission of data flows |
CN113473446A (en) * | 2020-03-31 | 2021-10-01 | 中国电信股份有限公司 | User plane changing method, system and mobile edge computing network element |
WO2021207586A1 (en) * | 2020-04-09 | 2021-10-14 | Dish Wireless L.L.C. | Cellular network capacity slicing systems and methods |
CN113873582A (en) * | 2020-06-30 | 2021-12-31 | 华为技术有限公司 | Mobile edge calculation processing method and related equipment |
WO2022027505A1 (en) * | 2020-08-06 | 2022-02-10 | Apple Inc. | User equipment authentication and authorization procedure for edge data network |
CN114302428A (en) * | 2021-12-24 | 2022-04-08 | 中国联合网络通信集团有限公司 | Method and device for determining MEC node |
WO2022089713A1 (en) * | 2020-10-26 | 2022-05-05 | Nokia Technologies Oy | Apparatus, method, and computer program for providing service level for extended reality application |
EP4013124A4 (en) * | 2019-08-21 | 2022-09-14 | Huawei Technologies Co., Ltd. | Method for notifying quality of service information, device, and system |
EP4132049A4 (en) * | 2020-05-14 | 2023-09-06 | Huawei Technologies Co., Ltd. | Communication system, server, and communication method and apparatus |
WO2023215918A1 (en) * | 2022-05-06 | 2023-11-09 | Google Llc | Communicating pdu sets in a wireless communication system |
US11968530B2 (en) | 2020-08-06 | 2024-04-23 | Apple Inc. | Network authentication for user equipment access to an edge data network |
Families Citing this family (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110167191B (en) * | 2018-02-14 | 2021-04-09 | 华为技术有限公司 | Communication method and device |
US10986528B2 (en) * | 2018-02-15 | 2021-04-20 | Huawei Technologies Co., Ltd. | Tracking QoS violated events |
CN110300143B (en) * | 2018-03-23 | 2021-10-15 | 华为技术有限公司 | Service switching processing method, related device and computer storage medium |
EP3721642A4 (en) * | 2018-04-05 | 2020-10-28 | Samsung Electronics Co., Ltd. | Method and apparatus for providing local area data network service based on non-subscription model in wireless communication system |
CN110519802B (en) * | 2018-05-21 | 2022-05-10 | 华为技术有限公司 | Data processing method, data sending method and data sending device |
US11595456B2 (en) * | 2018-05-31 | 2023-02-28 | Microsoft Technology Licensing, Llc | Modifying content streaming based on device parameters |
US10779155B2 (en) * | 2018-07-17 | 2020-09-15 | At&T Intellectual Property I, L.P. | Customizable and low-latency architecture for cellular core networks |
US10609546B2 (en) * | 2018-08-08 | 2020-03-31 | Verizon Patent And Licensing Inc. | Unified radio access network (RAN)/multi-access edge computing (MEC) platform |
CN110933711B (en) * | 2018-09-19 | 2023-06-02 | 华为技术有限公司 | Policy control method, device and system |
WO2020104021A1 (en) * | 2018-11-20 | 2020-05-28 | Huawei Technologies Co., Ltd. | Devices and methods for time sensitive communication in a communication network |
US10841766B2 (en) * | 2018-11-28 | 2020-11-17 | Verizon Patent And Licensing Inc. | Method and system for service provisioning based on multi-tiered networks and resource utilization |
US11412052B2 (en) * | 2018-12-28 | 2022-08-09 | Intel Corporation | Quality of service (QoS) management in edge computing environments |
KR20200086149A (en) * | 2019-01-08 | 2020-07-16 | 삼성전자주식회사 | A method and apparatus for power saving of a terminal in a wireless communication system |
KR20210126691A (en) * | 2019-02-13 | 2021-10-20 | 콘비다 와이어리스, 엘엘씨 | Apparatus, system, method and computer readable medium for connection-oriented vehicle-to-X (VTX) communication in 5G |
US11533669B2 (en) * | 2019-04-26 | 2022-12-20 | Cisco Technology, Inc. | Enterprise network fabric extension across mobile networks |
CN110198363B (en) * | 2019-05-10 | 2021-05-18 | 深圳市腾讯计算机系统有限公司 | Method, device and system for selecting mobile edge computing node |
CN114884612A (en) * | 2019-06-24 | 2022-08-09 | 华为技术有限公司 | Method and device for transmitting service message |
US11818576B2 (en) * | 2019-10-03 | 2023-11-14 | Verizon Patent And Licensing Inc. | Systems and methods for low latency cloud computing for mobile applications |
US11115872B2 (en) * | 2019-12-02 | 2021-09-07 | At&T Intellectual Property I, L.P. | Hierarchical and intelligent distributed controllers for an access network |
US11582066B2 (en) | 2019-12-19 | 2023-02-14 | Cisco Technology, Inc. | Techniques for extending a cellular quality of service bearer through an enterprise fabric |
CN112333107A (en) * | 2020-11-12 | 2021-02-05 | 中国联合网络通信集团有限公司 | Method, device and storage medium for determining strategy for sending downlink data |
EP4297352A4 (en) * | 2021-02-23 | 2024-04-03 | Huawei Tech Co Ltd | Data transmission method and apparatus |
CN113163409B (en) * | 2021-03-16 | 2022-09-20 | 重庆邮电大学 | Mobile edge computing service placement method based on artificial intelligence |
CN113099387B (en) * | 2021-03-22 | 2022-02-22 | 河海大学 | Method for constructing service quality data set in real edge environment |
US11570674B1 (en) | 2021-04-01 | 2023-01-31 | T-Mobile Usa, Inc. | Dynamic management of telecommunication services at user equipment |
US11452122B1 (en) * | 2021-04-06 | 2022-09-20 | Verizon Patent And Licensing Inc. | Systems and methods for regional assignment of multi-access edge computing resources |
US11665097B2 (en) * | 2021-04-27 | 2023-05-30 | Verizon Patent And Licensing Inc. | Methods and systems for differentiating MEC flows using IP header signaling |
CN115515191A (en) * | 2021-06-07 | 2022-12-23 | 中兴通讯股份有限公司 | Private service quality management method, device, system and storage medium |
CN115734282A (en) * | 2021-08-31 | 2023-03-03 | 华为技术有限公司 | Method and device for processing service quality and communication system |
KR20230065806A (en) * | 2021-11-05 | 2023-05-12 | 삼성전자주식회사 | Method and apparatus for providing split computing in wireless communications systems |
CN116133059A (en) * | 2021-11-12 | 2023-05-16 | 索尼集团公司 | Electronic device, method and storage medium for communication system |
CN117083897A (en) * | 2022-01-28 | 2023-11-17 | 北京小米移动软件有限公司 | Policy processing method and device, communication equipment and storage medium |
CN115004744B (en) * | 2022-02-17 | 2024-04-26 | 香港应用科技研究院有限公司 | Method for establishing connection between edge sites of 5G communication network |
US11968566B2 (en) * | 2022-05-09 | 2024-04-23 | Verizon Patent And Licensing Inc. | Systems and methods for inter-entity system configuration management using distributed ledger system |
WO2023225890A1 (en) * | 2022-05-25 | 2023-11-30 | Qualcomm Incorporated | Quality of service (qos) differentiation in user-plane procedures |
WO2024020756A1 (en) * | 2022-07-25 | 2024-02-01 | 北京小米移动软件有限公司 | Wireless communication method and apparatus, communication device and storage medium |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107018534A (en) * | 2016-01-28 | 2017-08-04 | 中兴通讯股份有限公司 | A kind of method for realizing mobile edge calculations service, apparatus and system |
WO2017211377A1 (en) * | 2016-06-06 | 2017-12-14 | Nokia Solutions And Networks Oy | Method, apparatus and system for mobile edge computing |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6661780B2 (en) * | 2001-12-07 | 2003-12-09 | Nokia Corporation | Mechanisms for policy based UMTS QoS and IP QoS management in mobile IP networks |
US8331375B2 (en) * | 2004-08-06 | 2012-12-11 | Qualcomm Incorporated | Technology agnostic QoS support in a multi-mode environment |
US7852849B2 (en) * | 2008-03-04 | 2010-12-14 | Bridgewater Systems Corp. | Providing dynamic quality of service for virtual private networks |
US8339954B2 (en) * | 2008-05-16 | 2012-12-25 | Cisco Technology, Inc. | Providing trigger based traffic management |
US20140160990A1 (en) * | 2012-09-20 | 2014-06-12 | Telecommunication Systems, Inc. | Mechanisms for Quality of Service to Over the Top Applications for Use in Commercial Wireless Networks |
US9301191B2 (en) * | 2013-09-20 | 2016-03-29 | Telecommunication Systems, Inc. | Quality of service to over the top applications used with VPN |
WO2012015902A1 (en) * | 2010-07-30 | 2012-02-02 | Interdigital Patent Holdings, Inc. | Method and apparatus for managing and processing policy profile restrictions |
EP2509254A1 (en) * | 2011-04-06 | 2012-10-10 | Telefonaktiebolaget L M Ericsson (publ) | Method and apparatus for controlling service traffic in a communication network |
US20130007286A1 (en) * | 2011-06-29 | 2013-01-03 | Juniper Networks, Inc. | User session routing between mobile network gateways |
US8913494B1 (en) * | 2013-01-22 | 2014-12-16 | Sprint Spectrum L.P. | Dynamic allocation of backhaul bearer services based on loading conditions |
WO2016199515A1 (en) * | 2015-06-12 | 2016-12-15 | ソニー株式会社 | Device, method and program |
US10122547B2 (en) * | 2015-08-14 | 2018-11-06 | Nec Corporation | Enabling high-bandwidth, responsive mobile applications in LTE networks |
US10004019B2 (en) * | 2015-09-08 | 2018-06-19 | Parallel Wireless, Inc. | RAN for multimedia delivery |
US10348517B2 (en) * | 2015-10-09 | 2019-07-09 | Openet Telecom Ltd. | System and method for enabling service lifecycle based policy, licensing, and charging in a network function virtualization ecosystem |
EP3456000A1 (en) | 2016-05-09 | 2019-03-20 | Nokia Solutions and Networks Oy | Policy control with mobile edge computing |
CN106231607A (en) * | 2016-09-21 | 2016-12-14 | 北京佰才邦技术有限公司 | The method of a kind of resource distribution and base station |
US10849186B2 (en) * | 2017-01-09 | 2020-11-24 | Huawei Technologies Co., Ltd. | System and methods for session management |
CN107466482B (en) * | 2017-06-07 | 2021-07-06 | 香港应用科技研究院有限公司 | Method and system for joint determination of computational offload and content pre-fetching in a cellular communication system |
US11082881B2 (en) * | 2018-04-05 | 2021-08-03 | At&T Intellectual Property I, L.P. | Dynamic quality of service setting system |
-
2017
- 2017-12-25 CN CN201780098251.XA patent/CN111684774B/en active Active
- 2017-12-25 EP EP17936033.4A patent/EP3732846B1/en active Active
- 2017-12-25 US US16/956,236 patent/US11134410B2/en active Active
- 2017-12-25 WO PCT/CN2017/118269 patent/WO2019126931A1/en unknown
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107018534A (en) * | 2016-01-28 | 2017-08-04 | 中兴通讯股份有限公司 | A kind of method for realizing mobile edge calculations service, apparatus and system |
WO2017211377A1 (en) * | 2016-06-06 | 2017-12-14 | Nokia Solutions And Networks Oy | Method, apparatus and system for mobile edge computing |
Non-Patent Citations (4)
Title |
---|
3GPP: "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System - Phase 1; CT WG4 Aspects (Release 15", 3GPP TR 29.891 V0.4.0, 31 August 2017 (2017-08-31), XP051327846 * |
NOKIA ET AL.: "Role of the common UP-GW in case of multi-homed (IPv6) PDU Session", SA WG2 MEETING #116 S2-164251, 15 July 2016 (2016-07-15), XP051121874 * |
PENCHEVA, EVELINA ET AL.: "Mobile Edge Computing Services for Dynamic Quality of Service Control", PROCEEDING OF THE 20 TH CONFERENCE OF FRUCT ASSOCIATION, 19 October 2017 (2017-10-19), pages 365370, XP033226559 * |
See also references of EP3732846A4 * |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP4013124A4 (en) * | 2019-08-21 | 2022-09-14 | Huawei Technologies Co., Ltd. | Method for notifying quality of service information, device, and system |
WO2021093158A1 (en) | 2020-01-13 | 2021-05-20 | Zte Corporation | A method for adaptively configuring transmission of data flows |
EP4074120A4 (en) * | 2020-01-13 | 2023-07-12 | ZTE Corporation | A method for adaptively configuring transmission of data flows |
CN113473446A (en) * | 2020-03-31 | 2021-10-01 | 中国电信股份有限公司 | User plane changing method, system and mobile edge computing network element |
US11375409B2 (en) | 2020-04-09 | 2022-06-28 | Dish Wireless L.L.C. | Cellular network capacity slicing systems and methods |
WO2021207586A1 (en) * | 2020-04-09 | 2021-10-14 | Dish Wireless L.L.C. | Cellular network capacity slicing systems and methods |
EP4132049A4 (en) * | 2020-05-14 | 2023-09-06 | Huawei Technologies Co., Ltd. | Communication system, server, and communication method and apparatus |
WO2022001738A1 (en) * | 2020-06-30 | 2022-01-06 | 华为技术有限公司 | Mobile edge computing processing method, and related device |
CN113873582A (en) * | 2020-06-30 | 2021-12-31 | 华为技术有限公司 | Mobile edge calculation processing method and related equipment |
EP4156778A4 (en) * | 2020-06-30 | 2023-12-27 | Huawei Technologies Co., Ltd. | Mobile edge computing processing method, and related device |
WO2022027505A1 (en) * | 2020-08-06 | 2022-02-10 | Apple Inc. | User equipment authentication and authorization procedure for edge data network |
US11968530B2 (en) | 2020-08-06 | 2024-04-23 | Apple Inc. | Network authentication for user equipment access to an edge data network |
WO2022089713A1 (en) * | 2020-10-26 | 2022-05-05 | Nokia Technologies Oy | Apparatus, method, and computer program for providing service level for extended reality application |
CN114302428A (en) * | 2021-12-24 | 2022-04-08 | 中国联合网络通信集团有限公司 | Method and device for determining MEC node |
CN114302428B (en) * | 2021-12-24 | 2023-06-23 | 中国联合网络通信集团有限公司 | MEC node determination method and device |
WO2023215918A1 (en) * | 2022-05-06 | 2023-11-09 | Google Llc | Communicating pdu sets in a wireless communication system |
Also Published As
Publication number | Publication date |
---|---|
US11134410B2 (en) | 2021-09-28 |
US20210076250A1 (en) | 2021-03-11 |
EP3732846B1 (en) | 2022-11-30 |
CN111684774A (en) | 2020-09-18 |
EP3732846A1 (en) | 2020-11-04 |
CN111684774B (en) | 2022-08-19 |
EP3732846A4 (en) | 2021-08-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3732846B1 (en) | Quality of service (qos) control in mobile edge computing (mec) | |
US11711858B2 (en) | Shared PDU session establishment and binding | |
US11968750B2 (en) | System and method for session relocation at edge networks | |
US10462828B2 (en) | Policy and billing services in a cloud-based access solution for enterprise deployments | |
KR102387239B1 (en) | Mobile Network Interaction Proxy | |
EP3780682B1 (en) | Method and device for subscribing to service | |
CN110662308B (en) | Communication method and device | |
US11463935B2 (en) | Methods and functions for handling local breakout | |
CN115462174A (en) | Session management for handling offload | |
WO2018233451A1 (en) | Communication method, apparatus, and system | |
CN116058000A (en) | Mechanism for coordinating seamless service continuity to edge application servers at relocation | |
CN113727401A (en) | Method in access node of mobile network | |
CN114514764A (en) | Apparatus, method and computer program | |
US20150281967A1 (en) | Application aware communication system | |
CN116546564A (en) | Communication method and device |
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: 17936033 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2017936033 Country of ref document: EP Effective date: 20200727 |