MEC Questions Answers - Revision history

Velez at 07:08, 16 April 2024

2024-04-16T07:08:08Z

Velez at 16:04, 12 April 2024

2024-04-12T16:04:08Z

← Older revision		Revision as of 17:04, 12 April 2024
Line 55:		Line 55:

	'''A7:''' ETSI MEC has defined procedures to ensure service continuity when the application instance is relocated from an external cloud environment to the MEC system. The procedure describes how to relocate the application instance to the target MEC host. This procedure is based on using the information provided by the 5G network as an example, i.e., UPF and DN connected to the ETSI MEC host, in order to identify the target ETSI MEC host.		'''A7:''' ETSI MEC has defined procedures to ensure service continuity when the application instance is relocated from an external cloud environment to the MEC system. The procedure describes how to relocate the application instance to the target MEC host. This procedure is based on using the information provided by the 5G network as an example, i.e., UPF and DN connected to the ETSI MEC host, in order to identify the target ETSI MEC host.
	~~----[[MEC Questions Answers#%20msoanchor%201\|[AL1]]]As indicated in other specs, these services are all optional. So I have changed the wording a bit to avoid confusion.~~

			= '''Architecture questions''' =
	== Q8: How can the ETSI MEC system be deployed? ==		== Q8: How can the ETSI MEC system be deployed? ==

Line 67:		Line 69:

	4. MEC collocated with the Core Network functions (i.e. in the same data center)		4. MEC collocated with the Core Network functions (i.e. in the same data center)

			[[File:QA_Picture1.png\|800px\|center\|class=img-responsive]]


Line 72:		Line 76:

	'''A9''': The following is the generic architecture for ETSI MEC:		'''A9''': The following is the generic architecture for ETSI MEC:
			[[File:QA_Picture2.png\|800px\|center\|class=img-responsive]]

	The multi-access edge system consists of the MEC hosts and the MEC management necessary to run MEC applications within an operator network or a subset of an operator network.		The multi-access edge system consists of the MEC hosts and the MEC management necessary to run MEC applications within an operator network or a subset of an operator network.

Velez at 15:50, 12 April 2024

2024-04-12T15:50:26Z

← Older revision		Revision as of 16:50, 12 April 2024
Line 156:		Line 156:


	== Q17: Is MEC system designed in difference for different vertical application domains, such as automotive, AR/XR, vs. AI custom services, etc.? For example, if certain MEC applications require the GPU accelerators, how do they know if the MEC platform can support it or not? ==		== Q17: Is MEC system designed in difference for different vertical application domains, such as automotive, AR/XR, vs. AI custom services, etc.? ==
			For example, if certain MEC applications require the GPU accelerators, how do they know if the MEC platform can support it or not?

	'''A17:''' ETSI GS MEC 010-2 specifies application Descriptor (AppD), which describes application requirements and rules required by application provider. For example, among the AppD attributes MCIO (Managed Container Infrastructure Object) constraint parameters describes constraints expected to be assigned to MCIOs realizing this application, and GPU is one of the additional capabilities required. Applications would get such info through MEC management. For example, the MEC Orchestrator (MEO) may return with a failure, if the MEC system cannot find any MEC hosts supporting GPU in this case.		'''A17:''' ETSI GS MEC 010-2 specifies application Descriptor (AppD), which describes application requirements and rules required by application provider. For example, among the AppD attributes MCIO (Managed Container Infrastructure Object) constraint parameters describes constraints expected to be assigned to MCIOs realizing this application, and GPU is one of the additional capabilities required. Applications would get such info through MEC management. For example, the MEC Orchestrator (MEO) may return with a failure, if the MEC system cannot find any MEC hosts supporting GPU in this case.

Velez at 15:49, 12 April 2024

2024-04-12T15:49:13Z

Velez at 15:45, 12 April 2024

2024-04-12T15:45:46Z

Velez at 15:42, 12 April 2024

2024-04-12T15:42:50Z

← Older revision		Revision as of 16:42, 12 April 2024
Line 5:		Line 5:
	= General questions =		= General questions =

	== Q1: What does MEC acronym stand for? ==		=== Q1: What does MEC acronym stand for? ===
	'''A1''': At the initial creation of Industry Specification Group (ISG) MEC in 2014, the acronym meant Mobile Edge Computing. Since MEC Phase 2 work (2017 onwards) this was expanded to Multi-access Edge Computing, to include not only cellular networks but also other access networks (e.g., WLAN, fixed access networks). MEC is access network agnostic and can be deployed on various networks for which specific supports may be needed for the full exploitation of these access networks.		'''A1''': At the initial creation of Industry Specification Group (ISG) MEC in 2014, the acronym meant Mobile Edge Computing. Since MEC Phase 2 work (2017 onwards) this was expanded to Multi-access Edge Computing, to include not only cellular networks but also other access networks (e.g., WLAN, fixed access networks). MEC is access network agnostic and can be deployed on various networks for which specific supports may be needed for the full exploitation of these access networks.

	== Q2: What makes ETSI MEC unique? ==		=== Q2: What makes ETSI MEC unique? ===
	'''A2''': ETSI MEC focuses on the standardization of the necessary APIs to enable application and service providers to utilize computing capabilities present at the edge of the network (e.g. 3GPP 3G/4G/5G networks, WLAN, fixed access networks), thus bringing edge computing as close as possible to the end users without it being in the user devices. This is critical in establishing a unified and truly scalable and inter-operable edge computing eco-system. ETSI MEC specifies the essential elements that are required to enable applications to be hosted in a multi-vendor multi-access edge computing environment, ensuring service continuity and assisting seamless application layer mobility, both intra- and inter-MEC.		'''A2''': ETSI MEC focuses on the standardization of the necessary APIs to enable application and service providers to utilize computing capabilities present at the edge of the network (e.g. 3GPP 3G/4G/5G networks, WLAN, fixed access networks), thus bringing edge computing as close as possible to the end users without it being in the user devices. This is critical in establishing a unified and truly scalable and inter-operable edge computing eco-system. ETSI MEC specifies the essential elements that are required to enable applications to be hosted in a multi-vendor multi-access edge computing environment, ensuring service continuity and assisting seamless application layer mobility, both intra- and inter-MEC.

	== Q3: What are the main use cases targeted by ETSI MEC? ==		=== Q3: What are the main use cases targeted by ETSI MEC? ===
	'''A3''': ETSI MEC targets several main categories of use cases, including but not limited to:		'''A3''': ETSI MEC targets several main categories of use cases, including but not limited to:

Line 23:		Line 23:


	~~'''~~Q4:''' Where can I find the official list of common terms used in ETSI MEC?		== Q4:''' Where can I find the official list of common terms used in ETSI MEC? ==

	'''A4:''' Common terms and abbreviations are defined in ETSI GR MEC 001.		'''A4:''' Common terms and abbreviations are defined in ETSI GR MEC 001.

Velez at 15:41, 12 April 2024

2024-04-12T15:41:29Z

Show changes

Velez at 15:37, 12 April 2024

2024-04-12T15:37:34Z

← Older revision		Revision as of 16:37, 12 April 2024
Line 6:		Line 6:

	== Q1: What does MEC acronym stand for? ==		== Q1: What does MEC acronym stand for? ==
	A1: At the initial creation of Industry Specification Group (ISG) MEC in 2014, the acronym meant Mobile Edge Computing. Since MEC Phase 2 work (2017 onwards) this was expanded to Multi-access Edge Computing, to include not only cellular networks but also other access networks (e.g., WLAN, fixed access networks). MEC is access network agnostic and can be deployed on various networks for which specific supports may be needed for the full exploitation of these access networks.		'''A1''': At the initial creation of Industry Specification Group (ISG) MEC in 2014, the acronym meant Mobile Edge Computing. Since MEC Phase 2 work (2017 onwards) this was expanded to Multi-access Edge Computing, to include not only cellular networks but also other access networks (e.g., WLAN, fixed access networks). MEC is access network agnostic and can be deployed on various networks for which specific supports may be needed for the full exploitation of these access networks.

	== Q2: What makes ETSI MEC unique? ==		== Q2: What makes ETSI MEC unique? ==
	A2: ETSI MEC focuses on the standardization of the necessary APIs to enable application and service providers to utilize computing capabilities present at the edge of the network (e.g. 3GPP 3G/4G/5G networks, WLAN, fixed access networks), thus bringing edge computing as close as possible to the end users without it being in the user devices. This is critical in establishing a unified and truly scalable and inter-operable edge computing eco-system. ETSI MEC specifies the essential elements that are required to enable applications to be hosted in a multi-vendor multi-access edge computing environment, ensuring service continuity and assisting seamless application layer mobility, both intra- and inter-MEC.		'''A2''': ETSI MEC focuses on the standardization of the necessary APIs to enable application and service providers to utilize computing capabilities present at the edge of the network (e.g. 3GPP 3G/4G/5G networks, WLAN, fixed access networks), thus bringing edge computing as close as possible to the end users without it being in the user devices. This is critical in establishing a unified and truly scalable and inter-operable edge computing eco-system. ETSI MEC specifies the essential elements that are required to enable applications to be hosted in a multi-vendor multi-access edge computing environment, ensuring service continuity and assisting seamless application layer mobility, both intra- and inter-MEC.

			== Q3: What are the main use cases targeted by ETSI MEC? ==
			'''A3''': ETSI MEC targets several main categories of use cases, including but not limited to:

Velez at 15:35, 12 April 2024

2024-04-12T15:35:56Z

← Older revision		Revision as of 16:35, 12 April 2024
Line 1:		Line 1:
			__TOC__

	{{DISPLAYTITLE:MEC Questions & Answers }}		{{DISPLAYTITLE:MEC Questions & Answers }}

			= General questions =

			== Q1: What does MEC acronym stand for? ==
			A1: At the initial creation of Industry Specification Group (ISG) MEC in 2014, the acronym meant Mobile Edge Computing. Since MEC Phase 2 work (2017 onwards) this was expanded to Multi-access Edge Computing, to include not only cellular networks but also other access networks (e.g., WLAN, fixed access networks). MEC is access network agnostic and can be deployed on various networks for which specific supports may be needed for the full exploitation of these access networks.

			== Q2: What makes ETSI MEC unique? ==
			A2: ETSI MEC focuses on the standardization of the necessary APIs to enable application and service providers to utilize computing capabilities present at the edge of the network (e.g. 3GPP 3G/4G/5G networks, WLAN, fixed access networks), thus bringing edge computing as close as possible to the end users without it being in the user devices. This is critical in establishing a unified and truly scalable and inter-operable edge computing eco-system. ETSI MEC specifies the essential elements that are required to enable applications to be hosted in a multi-vendor multi-access edge computing environment, ensuring service continuity and assisting seamless application layer mobility, both intra- and inter-MEC.

Velez at 15:33, 12 April 2024

2024-04-12T15:33:08Z

← Older revision		Revision as of 16:33, 12 April 2024
Line 1:		Line 1:
	{{DISPLAYTITLE:MEC Questions ~~and Anwsers~~ }}		{{DISPLAYTITLE:MEC Questions & Answers }}

← Older revision		Revision as of 16:49, 12 April 2024
Line 3:		Line 3:
	{{DISPLAYTITLE:MEC Questions & Answers }}		{{DISPLAYTITLE:MEC Questions & Answers }}

	= General questions =		= '''General questions''' =

	== Q1: What does MEC acronym stand for? ==		== Q1: What does MEC acronym stand for? ==
Line 117:		Line 117:


	~~'''~~Q12:~~'''~~ What is the application lifecycle management in ETSI MEC?		== Q12: What is the application lifecycle management in ETSI MEC? ==

	'''A12:''' The MEC Orchestrator is the core functionality in MEC system level management, which is responsible for the following application lifecycle management related functions:		'''A12:''' The MEC Orchestrator is the core functionality in MEC system level management, which is responsible for the following application lifecycle management related functions:
Line 134:		Line 134:


	~~'''~~Q13:~~'''~~ How is it ensured that the MEC application is running at the optimal/best location?		== Q13: How is it ensured that the MEC application is running at the optimal/best location? ==

	'''A13:''' As defined in ETSI GS MEC 010-2, MEC Orchestrator (MEO) / Mobile Edge Application Orchestrator (MEAO) can choose a good (if not the best) location to host an application, considering the requirements of computation, networking and deployment policies. When the current location no longer meets the requirements, the mobility services may be used. ETSI GS MEC 021 specifies application mobility service APIs in support of service continuity via relocation of a MEC application instance from one MEC host to a different host. More in detail, “Application mobility is a unique feature of MEC system, which supports relocation of user context and/or application instance from one MEC host to another, or between a MEC host and a Cloud, especially when the MEC host is attached to mobile operator’s networks. As a mobile device connected to a mobile network moves around within the network, it can result in the device connecting to the network entity associated to a different MEC host from the serving host. Consequently, there is necessity of relocating the application instance and/or user context associated to the device to a new MEC host to continue offering the best performance of service.”		'''A13:''' As defined in ETSI GS MEC 010-2, MEC Orchestrator (MEO) / Mobile Edge Application Orchestrator (MEAO) can choose a good (if not the best) location to host an application, considering the requirements of computation, networking and deployment policies. When the current location no longer meets the requirements, the mobility services may be used. ETSI GS MEC 021 specifies application mobility service APIs in support of service continuity via relocation of a MEC application instance from one MEC host to a different host. More in detail, “Application mobility is a unique feature of MEC system, which supports relocation of user context and/or application instance from one MEC host to another, or between a MEC host and a Cloud, especially when the MEC host is attached to mobile operator’s networks. As a mobile device connected to a mobile network moves around within the network, it can result in the device connecting to the network entity associated to a different MEC host from the serving host. Consequently, there is necessity of relocating the application instance and/or user context associated to the device to a new MEC host to continue offering the best performance of service.”

	== '''Implementation related questions''' ==		= '''Implementation related questions''' =

	~~'''~~Q14:~~'''~~ Is there any open source or reference implementation of MEC systems available including MEC orchestrations, OSS, MEC platforms, MEC host?		== Q14: Is there any open source or reference implementation of MEC systems available including MEC orchestrations, OSS, MEC platforms, MEC host? ==


	'''A14:''' All ETSI MEC specified APIs are illustrated in JSON or YAML format with OpenAPI and online available here: <nowiki>https://forge.etsi.org/rep/mec/</nowiki>. There is a list of available open source MEC solutions including MEC platforms, MEC Platform Manager and MEC orchestrator on the MEC wiki (see [[MEC Ecosystem\|MEC ecosystem]]). These solutions are not necessarily ISG MEC compliant but are recognized by MEC ISG MEC.		'''A14:''' All ETSI MEC specified APIs are illustrated in JSON or YAML format with OpenAPI and online available here: <nowiki>https://forge.etsi.org/rep/mec/</nowiki>. There is a list of available open source MEC solutions including MEC platforms, MEC Platform Manager and MEC orchestrator on the MEC wiki (see [[MEC Ecosystem\|MEC ecosystem]]). These solutions are not necessarily ISG MEC compliant but are recognized by MEC ISG MEC.

	~~'''~~Q15:~~'''~~ What is the ETSI MEC Sandbox? How we can utilize it for development?		== Q15: What is the ETSI MEC Sandbox? How we can utilize it for development? ==


	'''A15:''' ETSI MEC Sandbox is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardized RESTful APIs are targeted towards MEC application developers to expose the value-added services offered by MEC, including real time access to network and context information, as well as location awareness. MEC Sandbox provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behavior and capabilities of the Location (MEC013), Radio Network Information (MEC012), Traffic Management APIs (MEC015), Application Mobility (MEC021), WLAN Information (MEC028) and V2X Information API (MEC030) service APIs. Such contextual information can offer significant differential performance for edge based MEC applications. MEC Sandbox also provides the support of capabilities described by Edge Platform Application Enablement (MEC011) and Device Application Interface (MEC016).		'''A15:''' ETSI MEC Sandbox is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardized RESTful APIs are targeted towards MEC application developers to expose the value-added services offered by MEC, including real time access to network and context information, as well as location awareness. MEC Sandbox provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behavior and capabilities of the Location (MEC013), Radio Network Information (MEC012), Traffic Management APIs (MEC015), Application Mobility (MEC021), WLAN Information (MEC028) and V2X Information API (MEC030) service APIs. Such contextual information can offer significant differential performance for edge based MEC applications. MEC Sandbox also provides the support of capabilities described by Edge Platform Application Enablement (MEC011) and Device Application Interface (MEC016).

	~~'''~~Q16:~~'''~~ Does MEC specify the minimum required computing/storage/network resources to run or deploy MEC host?		== Q16: Does MEC specify the minimum required computing/storage/network resources to run or deploy MEC host? ==


Line 156:		Line 156:


	~~'''~~Q17:~~'''~~ Is MEC system designed in difference for different vertical application domains, such as automotive, AR/XR, vs. AI custom services, etc.? For example, if certain MEC applications require the GPU accelerators, how do they know if the MEC platform can support it or not?		== Q17: Is MEC system designed in difference for different vertical application domains, such as automotive, AR/XR, vs. AI custom services, etc.? For example, if certain MEC applications require the GPU accelerators, how do they know if the MEC platform can support it or not? ==

	'''A17:''' ETSI GS MEC 010-2 specifies application Descriptor (AppD), which describes application requirements and rules required by application provider. For example, among the AppD attributes MCIO (Managed Container Infrastructure Object) constraint parameters describes constraints expected to be assigned to MCIOs realizing this application, and GPU is one of the additional capabilities required. Applications would get such info through MEC management. For example, the MEC Orchestrator (MEO) may return with a failure, if the MEC system cannot find any MEC hosts supporting GPU in this case.		'''A17:''' ETSI GS MEC 010-2 specifies application Descriptor (AppD), which describes application requirements and rules required by application provider. For example, among the AppD attributes MCIO (Managed Container Infrastructure Object) constraint parameters describes constraints expected to be assigned to MCIOs realizing this application, and GPU is one of the additional capabilities required. Applications would get such info through MEC management. For example, the MEC Orchestrator (MEO) may return with a failure, if the MEC system cannot find any MEC hosts supporting GPU in this case.

← Older revision		Revision as of 16:45, 12 April 2024
Line 5:		Line 5:
	= General questions =		= General questions =

	=== Q1: What does MEC acronym stand for? ===		== Q1: What does MEC acronym stand for? ==
	'''A1''': At the initial creation of Industry Specification Group (ISG) MEC in 2014, the acronym meant Mobile Edge Computing. Since MEC Phase 2 work (2017 onwards) this was expanded to Multi-access Edge Computing, to include not only cellular networks but also other access networks (e.g., WLAN, fixed access networks). MEC is access network agnostic and can be deployed on various networks for which specific supports may be needed for the full exploitation of these access networks.		'''A1''': At the initial creation of Industry Specification Group (ISG) MEC in 2014, the acronym meant Mobile Edge Computing. Since MEC Phase 2 work (2017 onwards) this was expanded to Multi-access Edge Computing, to include not only cellular networks but also other access networks (e.g., WLAN, fixed access networks). MEC is access network agnostic and can be deployed on various networks for which specific supports may be needed for the full exploitation of these access networks.

	=== Q2: What makes ETSI MEC unique? ===		== Q2: What makes ETSI MEC unique? ==
	'''A2''': ETSI MEC focuses on the standardization of the necessary APIs to enable application and service providers to utilize computing capabilities present at the edge of the network (e.g. 3GPP 3G/4G/5G networks, WLAN, fixed access networks), thus bringing edge computing as close as possible to the end users without it being in the user devices. This is critical in establishing a unified and truly scalable and inter-operable edge computing eco-system. ETSI MEC specifies the essential elements that are required to enable applications to be hosted in a multi-vendor multi-access edge computing environment, ensuring service continuity and assisting seamless application layer mobility, both intra- and inter-MEC.		'''A2''': ETSI MEC focuses on the standardization of the necessary APIs to enable application and service providers to utilize computing capabilities present at the edge of the network (e.g. 3GPP 3G/4G/5G networks, WLAN, fixed access networks), thus bringing edge computing as close as possible to the end users without it being in the user devices. This is critical in establishing a unified and truly scalable and inter-operable edge computing eco-system. ETSI MEC specifies the essential elements that are required to enable applications to be hosted in a multi-vendor multi-access edge computing environment, ensuring service continuity and assisting seamless application layer mobility, both intra- and inter-MEC.

	=== Q3: What are the main use cases targeted by ETSI MEC? ===		== Q3: What are the main use cases targeted by ETSI MEC? ==
	'''A3''': ETSI MEC targets several main categories of use cases, including but not limited to:		'''A3''': ETSI MEC targets several main categories of use cases, including but not limited to:

Line 23:		Line 23:


	== Q4:~~'''~~ Where can I find the official list of common terms used in ETSI MEC? ==		== Q4: Where can I find the official list of common terms used in ETSI MEC? ==

	'''A4:''' Common terms and abbreviations are defined in ETSI GR MEC 001.		'''A4:''' Common terms and abbreviations are defined in ETSI GR MEC 001.


	~~'''~~Q5:~~'''~~ What are the MEC requirements defined in ETSI MEC?		== Q5: What are the MEC requirements defined in ETSI MEC? ==

	'''A5:''' ETSI GS MEC 002 specified the requirements for MEC with the aim of promoting interoperability and deployments, including		'''A5:''' ETSI GS MEC 002 specified the requirements for MEC with the aim of promoting interoperability and deployments, including
Line 41:		Line 41:


	~~'''~~Q6:~~'''~~ What is ETSI MEC service and which services are required to fulfill the given requirements?		== Q6: What is ETSI MEC service and which services are required to fulfill the given requirements? ==

	'''A6:''' ETSI MEC service is a service provided via the MEC platform either by the MEC platform itself or by a MEC application. There are several MEC services specified in ETSI MEC, including:[[MEC Questions Answers#%20msocom%201\|[AL1]]]		'''A6:''' ETSI MEC service is a service provided via the MEC platform either by the MEC platform itself or by a MEC application. There are several MEC services specified in ETSI MEC, including:[[MEC Questions Answers#%20msocom%201\|[AL1]]]
Line 52:		Line 52:


	~~'''~~Q7:~~'''~~ Is it possible to ensure service continuity between applications running in the mobile edge and an external cloud environment?		== Q7: Is it possible to ensure service continuity between applications running in the mobile edge and an external cloud environment? ==

	'''A7:''' ETSI MEC has defined procedures to ensure service continuity when the application instance is relocated from an external cloud environment to the MEC system. The procedure describes how to relocate the application instance to the target MEC host. This procedure is based on using the information provided by the 5G network as an example, i.e., UPF and DN connected to the ETSI MEC host, in order to identify the target ETSI MEC host.		'''A7:''' ETSI MEC has defined procedures to ensure service continuity when the application instance is relocated from an external cloud environment to the MEC system. The procedure describes how to relocate the application instance to the target MEC host. This procedure is based on using the information provided by the 5G network as an example, i.e., UPF and DN connected to the ETSI MEC host, in order to identify the target ETSI MEC host.
	----[[MEC Questions Answers#%20msoanchor%201\|[AL1]]]As indicated in other specs, these services are all optional. So I have changed the wording a bit to avoid confusion.		----[[MEC Questions Answers#%20msoanchor%201\|[AL1]]]As indicated in other specs, these services are all optional. So I have changed the wording a bit to avoid confusion.
			== Q8: How can the ETSI MEC system be deployed? ==
	~~'''~~Q8~~'''~~: How can the ETSI MEC system be deployed?

	'''A8''': Logically ETSI MEC hosts are deployed in the edge or central data network and it is the User Plane Function (UPF) that takes care of steering the user plane traffic towards the targeted MEC applications in the data network. The locations of the data networks and the UPF are a choice of the network operator and the network operator may choose to place the physical computing resources based on technical and business considerations such as available site facilities, supported applications and their requirements, measured or estimated user load etc. The MEC management system, orchestrating the operation of MEC hosts and applications, may decide dynamically where to deploy the MEC applications. In terms of physical deployment of MEC hosts, there are multiple options available based on various operational, performance or security related requirements. The figure below illustrates examples of the physical deployment of MEC in a 5G network. For more detailed information, one can refer to ETSI WP “MEC in 5G networks (June 2018)”, ETSI WP “MEC Deployments in 4G and Evolution Towards 5G (February 2018)”.		'''A8''': Logically ETSI MEC hosts are deployed in the edge or central data network and it is the User Plane Function (UPF) that takes care of steering the user plane traffic towards the targeted MEC applications in the data network. The locations of the data networks and the UPF are a choice of the network operator and the network operator may choose to place the physical computing resources based on technical and business considerations such as available site facilities, supported applications and their requirements, measured or estimated user load etc. The MEC management system, orchestrating the operation of MEC hosts and applications, may decide dynamically where to deploy the MEC applications. In terms of physical deployment of MEC hosts, there are multiple options available based on various operational, performance or security related requirements. The figure below illustrates examples of the physical deployment of MEC in a 5G network. For more detailed information, one can refer to ETSI WP “MEC in 5G networks (June 2018)”, ETSI WP “MEC Deployments in 4G and Evolution Towards 5G (February 2018)”.
Line 70:		Line 69:


	~~'''~~Q9~~'''~~: Is there a reference architecture for ETSI MEC?		== Q9: Is there a reference architecture for ETSI MEC? ==

	'''A9''': The following is the generic architecture for ETSI MEC:		'''A9''': The following is the generic architecture for ETSI MEC:
Line 93:		Line 92:


	~~'''~~Q10:~~'''~~ What features that ETSI MEC may support?		== Q10: What features that ETSI MEC may support? ==

	'''A10''': ETSI MEC may support the following optional features:		'''A10''': ETSI MEC may support the following optional features:
Line 111:		Line 110:
	More features can be found in ETSI GS MEC 002.		More features can be found in ETSI GS MEC 002.

	== '''API related questions''' ==		= '''API related questions''' =

	~~'''~~Q11:~~'''~~ Is MEC Application registration supported in ETSI MEC?		== Q11: Is MEC Application registration supported in ETSI MEC? ==

	'''A11:''' Yes, MEC application registration related procedures are specified in ETSI GS MEC 011. This set of procedures is optional, and it is up to application developer to decide if registration is necessary. The application registration procedure allows an authorized MEC application instance to provide its information to the MEC platform. For the application instance that is not instantiated by the MEC Management, the registration can ensure the application instance is discoverable. If there is a change in the requirements or to the information of an MEC application instance, the authorized MEC application instance uses the application registration update procedure to update the MEC platform.		'''A11:''' Yes, MEC application registration related procedures are specified in ETSI GS MEC 011. This set of procedures is optional, and it is up to application developer to decide if registration is necessary. The application registration procedure allows an authorized MEC application instance to provide its information to the MEC platform. For the application instance that is not instantiated by the MEC Management, the registration can ensure the application instance is discoverable. If there is a change in the requirements or to the information of an MEC application instance, the authorized MEC application instance uses the application registration update procedure to update the MEC platform.