Method and apparatus for provisioning edge services in joint deployment of wireless communication network

Abstract

There is provided a management system in a mobile network, the management system comprising one or more processors arranged to: receive a request to provide an edge service, the request indicating a region in which the edge service is to be provided; identifying at least one edge data network (EDN) for providing the requested edge service based on at least a portion of the indicated region; and requesting to deploy an edge application server (EAS) in the identified EDN to provide the requested edge service in the specified region.

Description

Technical Field

[0001] The subject matter disclosed herein relates generally to the field of implementing methods and apparatus for provisioning edge services in a joint deployment of wireless communication networks.This document defines a management system in a mobile network and methods performed by a management system of a mobile network. Background Art

[0002] In 3GPP EDGEAPP (3GPP TS23.558v17.4.0), the application layer functional model of the edge enablement layer has been specified. In this architecture, the main functions specified are related to the edge enablement server (EES), edge configuration server (ECS) and EDGE-x interface.

[0003] In addition, in SA5 (TS28.538 v17.7.1), an overall management framework is described. In the overall management framework, an edge computing management framework is provided, which includes a public land mobile network (PLMN) management system and an edge computing service provider (ECSP) management system. The ECSP management system (as a producer) provides management services to enable application service providers (ASPs) and ECSP consumers to orchestrate and manage edge data network (EDN) network functions (NFs), such as EAS, EES, and ECS. The PLMN management system (as a producer) provides management services to enable the ECSP management system to interconnect EDN NFs with 5GC NFs (e.g., PCF, UPF, NEF). Both the ECSP management system and the PLMN management system communicate with ETSI Network Function Virtualization Management and Orchestration (NFV MANO) to perform lifecycle management functions. Summary of the invention

[0004] Disclosed herein is a process for provisioning edge services in a joint deployment of wireless communication networks. The above process may be implemented by a management system of a mobile network.

[0005] In one aspect, a management system in a mobile network is provided, the management system comprising one or more processors, the one or more processors being arranged to: receive a request to provide an edge service, the request indicating a region in which the edge service is to be provided; identify at least one edge data network EDN for providing the requested edge service based on at least a portion of the indicated region; and request to deploy or configure an edge application server EAS in the identified EDN to provide the requested edge service in the specified region.

[0006] On the other hand, a method performed by a management system of a mobile network is provided, the method comprising: receiving a request to provide an edge service, the request indicating a region in which the edge service will be provided; identifying at least one edge data network EDN for providing the requested edge service based on the indicated region; and requesting to deploy or configure an edge application server EAS in the identified EDN to provide the requested edge service in the specified region.

[0007] On the other hand, a device in a mobile network is provided, the device comprising one or more processors, the one or more processors being arranged to: receive a request to provide an edge service, the request indicating a region in which the edge service is to be provided; and identify at least one edge data network (EDN) for providing the requested edge service based on at least a portion of the indicated region. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the present disclosure is described by reference to certain devices and methods shown in the accompanying drawings. Each of these drawings depicts only certain aspects of the present disclosure and should not be considered as limiting the scope thereof. For the sake of clarity, the drawings may have been simplified and are not necessarily drawn to scale.

[0009] A method and apparatus for provisioning edge services in a joint deployment of wireless communication networks will now be described, by way of example only, with reference to the accompanying drawings, in which:

[0010] Figure 1 depicts a wireless communication system (not to scale) in which the methods and apparatus disclosed herein may be implemented;

[0011] Figure 2 Describes the application layer functional model of the edge enablement layer outlined in 3GPP TS23.558v17.4.0;

[0012] Figure 3 Describes the edge computing management framework outlined in 3GPP TS28.538 v17.7.1;

[0013] Figure 4 depicts the relationships involved in edge computing services during federation and roaming;

[0014] Figure 5 Describes edge application servers deployed by different edge computing service providers as described in 3GPP TR 23.700-98 v.1.1.1;

[0015] Figure 6 Describes the edge node sharing scenario between the first operator platform and the second operator platform;

[0016] Figure 7 depicts a user equipment device that may be used to implement the methods described herein;

[0017] Figure 8 depicts a network node that can be used to implement the methods described herein;

[0018] Fig. 9 Describes a process for configuring / selecting and provisioning edge services in a wireless network; and

[0019] Fig.10 is a process flow diagram depicting the steps of a method performed by a management system for configuring / selecting and provisioning edge services in a wireless network. DETAILED DESCRIPTION

[0020] Those skilled in the art will appreciate that aspects of the present disclosure may be embodied as systems, devices, methods or program products. Therefore, the arrangements described herein may be implemented in full hardware form, full software form (including firmware, resident software, microcode, etc.), or in a combination of software and hardware aspects.

[0021] For example, the disclosed methods and apparatus may be implemented as hardware circuits, including custom very large scale integrated (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed methods and apparatus may also be implemented in programmable hardware devices, such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code, which may be organized, for example, as objects, procedures, or functions.

[0022] In addition, the method and apparatus may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transmitting. The storage device may not embody a signal. In some arrangements, the storage device uses only a signal for accessing the code.

[0023] Any combination of one or more computer readable media may be used. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, device or apparatus, or any suitable combination of the above.

[0024] More specific examples of storage devices (a non-exhaustive list) include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0025] In this specification, references to examples or similar language of a particular method or device indicate that the specific features, structures or characteristics described in conjunction with the example are included in at least one implementation of the methods and devices described herein. Therefore, unless otherwise expressly provided, references to examples or similar language features of a particular method or device may, but do not necessarily, all refer to the same example, but to "one or more but not all examples". Unless otherwise expressly provided, the terms "including", "comprising", "having" and their variations mean "including but not limited to". Unless otherwise expressly provided, a list of items listed does not mean that any or all items are mutually exclusive. Unless otherwise expressly provided, the terms "a", "an" and "the" also mean "one or more".

[0026] As used herein, a list with the conjunction "and / or" includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one or more of ..." includes any single item in the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one of ..." includes one and only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and does not include a combination of A, B, and C. As used herein, "a member selected from A, B, and C" includes one and only one of A, B, or C, and does not include a combination of A, B, and C. As used herein, "a member selected from A, B and C and combinations thereof" includes only A, only B, only C, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B and C.

[0027] In addition, the features, structures or characteristics described herein may be combined in any suitable manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a comprehensive understanding of the present disclosure. However, those skilled in the relevant art will recognize that the disclosed methods and apparatus may be practiced without one or more of the specific details, or may be practiced using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid confusing aspects of the present disclosure.

[0028] The following is a description of various aspects of the disclosed method and apparatus with reference to schematic flow charts and / or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flow charts and / or schematic block diagrams and the combination of blocks in the schematic flow charts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by a processor of a computer or other programmable data processing device can create a component for implementing the function / action specified in the schematic flow charts and / or schematic block diagrams.

[0029] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus, or other device to work in a specific manner so that the instructions stored in the storage device produce an article of manufacture that includes instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0030] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are executed on the computer, other programmable apparatus, or other device, thereby producing a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0031] The schematic flow charts and / or schematic block diagrams in the figure illustrate the possible implementation architectures, functions and operations of the device, system, method and program product. In this regard, each block in the schematic flow chart and / or schematic block diagram can represent a code module, segment or portion, which includes one or more executable instructions for implementing the code of (multiple) specified logical functions.

[0032] It should also be noted that in some alternative implementations, the functions shown in the blocks may not appear in the order shown in the figures. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods are contemplated that are equivalent in function, logic or effect to one or more blocks or portions thereof of the illustrated figures.

[0033] The description of the elements in each figure can refer to the elements in the subsequent figures. The same numbers represent the same elements in all figures.

[0034] Figure 1 A wireless communication system 100 is depicted in which the methods and apparatus disclosed herein may be implemented. The wireless communication system 100 includes a remote unit 102 and a network unit 104. Figure 1 Although a specific number of remote units 102 and network units 104 are depicted in the figure, those skilled in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100. The wireless communication system 100 may also include Figure 1 Additional entities not shown in the figure, such as edge computing entities, such as but not limited to one or more EDNs, one or more ECSPs, and one or more EASs. The functions of such additional entities will be described in more detail below.

[0035] In one example, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (PDA), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle computer, a network device (e.g., a router, a switch, a modem), an aircraft, a drone, etc. In some examples, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 102 may be referred to as a subscriber unit, a mobile station, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 102 may communicate directly with one or more of the network units 104 via UL communication signals. The remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0036] The network elements 104 may be distributed over a geographic area. In some examples, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, node Bs, eNBs, gNBs, home node Bs, relay nodes, devices, core networks, air servers, radio access nodes, APs, NRs, network entities, access and mobility management functions (AMFs), unified data management functions (UDMs), unified data repositories (UDRs), UDM / UDRs, policy control functions (PCFs), radio access networks (RANs), network slice selection functions (NSSFs), or other terms used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers that are communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks that may be coupled to other networks, such as the Internet and a public switched telephone network, among others. These and other elements of the radio access network and the core network are not shown, but are generally well known to those of ordinary skill in the art.

[0037] In one implementation, the wireless communication system 100 complies with the New Radio (NR) protocol standardized in 3GPP, wherein the network unit 104 transmits on the downlink (DL) using an orthogonal frequency division multiple access (OFDM) modulation scheme, and the remote unit 102 transmits on the uplink (UL) using a single carrier frequency division multiple access (SC-FDMA) scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfoxx, etc. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0038] The network unit 104 can serve a number of remote units 102 within a service area (eg, a cell or cell sector) via wireless communication links. The network unit 104 sends DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0039] Figure 2 The application layer functional model of the edge enablement layer outlined in 3GPP TS 23.558 v17.4.0, in particular the EDGE APP architecture 200 is depicted.

[0040] Figure 3 An edge computing management framework 300 as outlined in 3GPP TS 28.538 v17.7.1 is depicted.

[0041] Based on 3GPP TR 23.700-98v1.1.1, the relationships involved in edge computing services are as follows: Figure 4 shown.

[0042] Figure 4 Depicts the relationships involved in edge computing services during federation and roaming.

[0043] End user 400 is a consumer of an application provided by ASP 402. End user 400:

[0044] · may have an ASP service agreement 404 with one or more ASPs 402;

[0045] • Having a PLMN subscription arrangement 406 with a PLMN operator 408 (e.g., a Home Public Land Mobile Network (HPLMN)). The user equipment device used by the end user may

[0046] to register on the HPLMN network and its roaming partners’ networks; and

[0047] May have access to one or more ECSP 410 edge services.

[0048] ASP 402 consumes edge management services (eg, infrastructure and / or platform services) provided by ECSP 410 or PLMN management service producer 408. ASP 402 may have an edge computing service provider service agreement 412 with one or more ECSPs 410.

[0049] PLMN operator 408 provides connectivity between end-user 402 and edge services provided by ECSP 410. PLMN operator 408:

[0050] may have a PLMN operator service agreement 414 with one or more ECSPs 410; and

[0051] May have roaming service agreements, including edge computing service agreements and / or joint agreements with single or multiple PLMN operators.

[0052] One or more ECSPs 410 provide edge services and:

[0053] May have service agreements 414 with one or more PLMN operators 408 to

[0054] Providing edge computing support; and

[0055] May have a federation partnership / agreement 416 to share edge services with one or more ECSPs 410.

[0056] The ECSP(s) 410 and the PLMN operator(s) 408 belong to the same organization.

[0057] Multi-access edge computing (MEC) federation is discussed in ETSI GR MEC035, which covers the coordination between MEC systems and can be defined as a federation model of MEC systems that enables the shared use of MEC services and applications.

[0058] In 3GPP, federation corresponds to the shared use of EES and / or EAS services and resources. This federation in MEC and EDGEAPP scenarios covers the coordination required between edge / cloud platforms in the following cases:

[0059] Edge node sharing;

[0060] The same edge service deployed in two or more platforms; and

[0061] Different edge services / applications deployed in different platforms but with “partner” or “dependency” relationships.

[0062] In some federation scenarios, changes in user equipment devices mapped to different edge / cloud service areas may result in service roaming (i.e., changes in application servers or EAS or MEC services) and / or network roaming (i.e., changes in the underlying network). The present disclosure relates to service roaming aspects. With respect to edge services, the following aspects of federation are discussed.

[0063] In the first case, a federated EAS service (using a partner EAS in an EDN of another ECSP) is described: In order for EAS to collaborate with other EAS to provide services (weather, traffic, maps, etc.), EAS context handling and federated EAS support may be required at the edge compatibility layer. When application context relocation (ACR) occurs due to user equipment device mobility, a method for re-arranging the federated EAS context may be required to provide continuous service of the federated EAS. In addition, a method for finding an EAS providing a federated EAS service within an EDN to which the user equipment device has moved may be required.

[0064] In the second case, edge services spanning multiple ECSPs are described. According to 3GPP TR 23.700-98 v.1.1.1, edge services or EAS (e.g., V2X servers) can be provided via different EDNs deployed by different ECSPs. Due to financial, regulatory, and operational constraints, each ECSP may not have the infrastructure required to install an EAS in each EDN. It is assumed that user equipment devices can access the same edge services provided by corresponding different EASs, which are registered to corresponding different EESs and deployed by corresponding different ECSPs with service level agreements for shared edge services. These ECSPs can deploy EESs to provide services for different PLMNs or different coverage areas of a given PLMN. 3GPP TR 23.700-98 v.1.1.1 Figure 4 A typical example of this scenario is depicted in .6-1.

[0065] Figure 5 According to the second case, EAS deployed by different ECSPs is depicted, as described in 3GPP TR 23.700-98 v.1.1.1.

[0066] The first EAS 500 residing in the first EDN 502 and the second EDN 504 provides the same service. The user equipment device 506 may be configured with the first ECS configuration information 508 (for example, if the user equipment device 506 is a subscriber of the first ECSP 510). When the user equipment device 506 is not within the service area of ​​the second EAS 500 in the first ECSP 510 and cannot find a suitable EES within the first ECSP 510 to discover and connect to the first EAS 500, the second ECS configuration information 512 deployed by the second ECSP 514 (a partner of the first ECSP 510) may also need to be supplied to the user equipment device 506. The same problem also exists when the first EAS 500 is unavailable due to other reasons (for example, overload), or when the first ECSP 510 does not deploy the first EAS 500 at all, but relies on the partner second ECSP 514 to provide edge services. In addition, the user equipment device 506 may have accessed the first EAS 500 in the first EDN 502 and is obtaining services from the first EAS 500. In this case, when the user equipment device moves out of the service area of ​​the first EAS 500 in the first EDN 502 and transfers to (e.g., goes to) the service area of ​​the first EAS 500 in the second EDN 504, it is necessary to support service continuity due to the mobility of the user equipment device.

[0067] In the third case, edge node sharing across ECSPs is described. The edge node sharing scenario has been identified in GSMA OPG.02CR1 001 Operator Platform Telecom Edge Requirements, clause 3.3.5, in accordance with (ie, based on) OPG.02CR1001 Operator Platform Telecom Edge Requirements.

[0068] Figure 6 This edge node sharing scenario is depicted between a first operator platform (OP) 600 and a second OP 602. In this example, OP may refer to an ECSP or other operator platform.

[0069] The first OP 600 deploys an application in the second OP 602 (ie, partner OP). The first OP 600 wishes to extend its services to the area covered by the second OP 604 by using the edge infrastructure of the second OP 602.

[0070] In this example, the user (and user equipment device 604 ) belongs to a first OP 600 .

[0071] If the first OP 600 finds that the second OP 602 (partner OP) has an application available that is most suitable for providing services to the user, the first OP 600 requests the second OP 602 for edge computing services.

[0072] In view of these considered scenarios, a user equipment device may wish to access edge services when roaming near another ECSP that can provide similar services. For example, it may be beneficial for the user equipment device to connect to a nearby ECSP in terms of cost or performance. However, it is currently unclear how a user equipment device is configured to connect to or use such services.

[0073] A commonality of the above scenarios is that application services are extended to multiple ECSPs. This means that a management system in or from an ASP, ECSP or PLMN must be able to manage (e.g., deploy and configure) user equipment devices so that similar or equivalent applications can be used in another ECSP.

[0074] This application proposes a solution to this problem.

[0075] Figure 7A user equipment device (UE) 700 is depicted that can be used to implement the methods described herein. UE 700 is used to implement one or more of the solutions described herein. UE 700 is consistent with one or more UEs described in the embodiments herein. Specifically, UE 700 is consistent with the above-mentioned UE 506, 604, and therefore, reference numeral 700 is used hereinafter to indicate a UE consistent with UE 506, 604. UE 700 includes a processor 705, a memory 710, an input device 715, an output device 720, and a transceiver 725.

[0076] The input device 715 and the output device 720 may be combined into a single device, such as a touch screen. In some implementations, the user equipment apparatus 700 does not include any input device 715 and / or output device 720. The user equipment apparatus 700 may include one or more of a processor 705, a memory 710, and a transceiver 725, and may not include an input device 715 and / or an output device 720.

[0077] As shown, the transceiver 725 includes at least one transmitter 730 and at least one receiver 735. The transceiver 725 can communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 725 can be operable on an unlicensed spectrum. In addition, the transceiver 725 can include multiple UE panels supporting one or more beams. In addition, the transceiver 725 can support at least one network interface 740 and / or application interface 745. (Multiple) application interface 745 can support one or more APIs. (Multiple) network interface 740 can support 3GPP reference points, such as Uu, N1, PC5, etc. As understood by those of ordinary skill in the art, other network interfaces 740 can be supported.

[0078] The processor 705 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 705 may be a microcontroller, a microprocessor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processing unit, a field programmable gate array (FPGA), or a similar programmable controller. The processor 705 may execute instructions stored in the memory 710 to perform the methods and routines described herein. The processor 705 is communicatively coupled to the memory 710, the input device 715, the output device 720, and the transceiver 725.

[0079] Processor 705 may control user equipment device 700 to implement user equipment device behaviors described herein. Processor 705 may include an application processor (also referred to as a main processor) that manages application domain and operating system (OS) functions and a baseband processor (also referred to as a baseband radio processor) that manages radio functions.

[0080] The memory 710 may be a computer-readable storage medium. The memory 710 may include a volatile computer storage medium. For example, the memory 710 may include a RAM, including a dynamic RAM (DRAM), a synchronous dynamic RAM (SDRAM), and / or a static RAM (SRAM). The memory 710 may include a non-volatile computer storage medium. For example, the memory 710 may include a hard drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 710 may include both volatile and non-volatile computer storage media.

[0081] The memory 710 may store data related to implementing the traffic class field as described herein. The memory 710 may also store program code and related data, such as an operating system or other controller algorithms operating on the device 700.

[0082] Input device 715 may include any known computer input device, including a touch pad, buttons, keyboard, stylus, microphone, etc. Input device 715 may be integrated with output device 720, for example, as a touch screen or similar touch-sensitive display. Input device 715 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 715 may include two or more different devices, such as a keyboard and a touch pad.

[0083] The output device 720 may be designed to output visual, auditory and / or tactile signals. The output device 720 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 720 may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display, an organic LED (OLED) display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 720 may include a wearable display that is separate from the rest of the user device apparatus 700 but communicatively coupled, such as a smart watch, smart glasses, a head-up display, etc. In addition, the output device 720 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0084] Output device 720 may include one or more speakers for producing sound. For example, output device 720 may produce an audible alarm or notification (e.g., a beep or buzzer). Output device 720 may include one or more tactile devices for producing vibration, motion, or other tactile feedback. All or part of output device 720 may be integrated with input device 715. For example, input device 715 and output device 720 may form a touch screen or similar touch-sensitive display. Output device 720 may be located near input device 715.

[0085] The transceiver 725 communicates with one or more network functions of the mobile communication network via one or more access networks. The transceiver 725 operates under the control of the processor 705 to send messages, data and other signals, and also receives messages, data and other signals. For example, the processor 705 can selectively activate the transceiver 725 (or part thereof) at a specific time to send and receive messages.

[0086] The transceiver 725 includes at least one transmitter 730 and at least one receiver 735. One or more transmitters 730 can be used to provide uplink communication signals to a base unit of a wireless communication network. Similarly, one or more receivers 735 can be used to receive downlink communication signals from the base unit. Although only one transmitter 730 and one receiver 735 are shown, the user equipment device 700 can have any suitable number of transmitters 730 and receivers 735. In addition, (multiple) transmitters 730 and (multiple) receivers 735 can be any suitable type of transmitter and receiver. The transceiver 725 may include a first transmitter / receiver pair for communicating with a mobile communication network through an authorized radio spectrum, and a second transmitter / receiver pair for communicating with a mobile communication network through an unauthorized radio spectrum.

[0087] A first transmitter / receiver pair that can be used to communicate with a mobile communication network via an authorized radio spectrum and a second transmitter / receiver pair that can be used to communicate with a mobile communication network via an unlicensed radio spectrum can be combined into a single transceiver unit, such as a single chip that performs functions for use with both the authorized and unlicensed radio spectrums. The first transmitter / receiver pair and the second transmitter / receiver pair can share one or more hardware components. For example, some of the transceivers 725, transmitters 730, and receivers 735 can be implemented as physically separate components that access shared hardware resources and / or software resources, such as a network interface 740.

[0088] One or more transmitters 730 and / or one or more receivers 735 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system on chip, an application specific integrated circuit (ASIC), or other types of hardware components. One or more transmitters 730 and / or one or more receivers 735 may be implemented and / or integrated into a multi-chip module. Other components such as a network interface 740 or other hardware components / circuits may be integrated into a single chip with any number of transmitters 730 and / or receivers 735. The transmitter 730 and receiver 735 may be logically arranged as a transceiver 725 using one or more common control signals, or may be arranged as modular transmitters 730 and receivers 735 implemented in the same hardware chip or multi-chip module.

[0089] Figure 8 The details of a network node 800 that can be used to implement the methods described herein are depicted. The network node 800 can be an implementation of an entity in a wireless communication network, such as one or more of the networks described herein. The network node 800 can be, for example, the UE 700 described above, or a NF or application function (AF), or another entity of one or more of the networks of the embodiments described herein. The network node 800 includes a processor 805, a memory 810, an input device 815, an output device 820, and a transceiver 825.

[0090] The input device 815 and the output device 820 may be combined into a single device, such as a touch screen. In some implementations, the network node 800 does not include any input device 815 and / or output device 820. The network node 800 may include one or more of a processor 805, a memory 810, and a transceiver 825, and may not include an input device 815 and / or an output device 820.

[0091] As shown, the transceiver 825 includes at least one transmitter 830 and at least one receiver 835. Here, the transceiver 825 communicates with one or more remote units 200. In addition, the transceiver 825 can support at least one network interface 840 and / or application interface 845. (Multiple) application interface 845 can support one or more APIs. (Multiple) network interface 840 can support 3GPP reference points such as Uu, N1, N2 and N3. As understood by those of ordinary skill in the art, other network interfaces 840 can be supported.

[0092] The processor 805 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 805 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, or a similar programmable controller. The processor 805 may execute instructions stored in the memory 810 to perform the methods and routines described herein. The processor 805 is communicatively coupled to the memory 810, the input device 815, the output device 820, and the transceiver 825.

[0093] The memory 810 may be a computer-readable storage medium. The memory 810 may include a volatile computer storage medium. For example, the memory 810 may include a RAM, including a dynamic RAM (DRAM), a synchronous dynamic RAM (SDRAM), and / or a static RAM (SRAM). The memory 810 may include a non-volatile computer storage medium. For example, the memory 810 may include a hard drive, a flash memory, or any other suitable non-volatile computer storage device. The memory 810 may include both volatile and non-volatile computer storage media.

[0094] The memory 810 may store data related to establishing a multipath unicast link and / or mobile operation. For example, as described herein, the memory 810 may store parameters, configurations, resource allocations, policies, etc. The memory 810 may also store program codes and related data, such as an operating system or other controller algorithms operating on the network node 800.

[0095] Input device 815 may include any known computer input device, including a touch pad, buttons, keyboard, stylus, microphone, etc. Input device 815 may be integrated with output device 820, for example, as a touch screen or similar touch-sensitive display. Input device 815 may include a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. Input device 815 may include two or more different devices, such as a keyboard and a touch pad.

[0096] The output device 820 may be designed to output visual, auditory and / or tactile signals. The output device 820 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 820 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, the output device 820 may include a wearable display, such as a smart watch, smart glasses, a head-up display, etc., that is separated from the rest of the network node 800 but is communicatively coupled. In addition, the output device 820 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0097] The output device 820 may include one or more speakers for producing sound. For example, the output device 820 may produce an audible alarm or notification (e.g., a beep or buzzer). The output device 820 may include one or more tactile devices for producing vibration, motion, or other tactile feedback. All or part of the output device 820 may be integrated with the input device 815. For example, the input device 815 and the output device 820 may form a touch screen or similar touch-sensitive display. The output device 820 may be located near the input device 815.

[0098] The transceiver 825 includes at least one transmitter 830 and at least one receiver 835. One or more transmitters 830 can be used to communicate with the UE, as described herein. Similarly, one or more receivers 835 can be used to communicate with network functions in the PLMN and / or RAN, as described herein. Although only one transmitter 830 and one receiver 835 are shown, the network node 800 can have any suitable number of transmitters 830 and receivers 835. In addition, the (multiple) transmitters 830 and (multiple) receivers 835 can be any suitable type of transmitters and receivers.

[0099] Fig. 9 Depicted is a process 900 for configuring / selecting and provisioning edge services for users in a wireless network. The architecture for performing process 900 includes ASP 902, 3GPP management system 904 (e.g., PLMN or ECSP), additional ECSP management system 906, PLMN lookup NF 908, and charging function (CHF) 910.

[0100] In the existing SA2 arrangement described in 3GPP TS23.558v17.4.0, there is no mention of how the core network supports the provisioning of edge services to users.

[0101] In 3GPP, the UE can provide application layer information about its location. This information can be used to select the EAS at the application level. In an embodiment of the present invention, the selection of the EAS can be performed at the network level, where the EAS is selected based on the network level information of the UE. (In the context of the present disclosure, "network level" or "network plane" can refer to the user plane, control plane, or management plane). For example, this can be achieved when the application layer information is not provided. For example, if the application layer request does not include UE location information, the first ECS can interact with the 3GPP core network to retrieve the UE location (as described in more detail in TR23.700-98).

[0102] The PLMN Lookup NF 908 can be any NF in the control plane, such as an Application Management Function (AMF), a Session Management Function (SMF), or a Policy Control Function (PCF). A UE used by a user in a corresponding network has two options. First, at registration, the Lookup NF 908 can be instructed to use the correct EAS in the correct EDN. Alternatively, in the case where an EAS is requested but no geographic area information is provided, the Lookup NF 908 can redirect the request to the EAS in the correct EDN.

[0103] At step s900, ASP 902 requests 3GPP management system 904 (eg, in PLMN or ECSP) to provide EAS support for one or more services in certain given regions. This may include requesting 3GPP management system 904 to indicate whether EAS is supported in a given region.

[0104] At step s902, a management service in the management system 904 decides or determines which EDNs to use based on a given (requested) territory (ie, geographical coverage).

[0105] At step s904, the 3GPP management system 904 contacts the management system(s) 906 of the corresponding ECSP(s) to request an indication of the feasibility of providing one or more services (e.g., by deploying applications) in its EDN. Optionally, a reservation may be requested for these feasibility requests. For example, the 3GPP management system 904 may provide a timeout value to the management system(s) 906 of the corresponding other ECSP(s) that specifies the time that the requested resources (needed to make the provision of the one or more services feasible) should be reserved.

[0106] At step s906, the 3GPP management system 904 receives responses from the other management system(s) 906 indicating whether the requested service provision is feasible, and whether resource reservation (if requested) is successful / possible.

[0107] Optionally, at step s908 , the 3GPP management system 904 may request pricing / billing details for resource reservations for one or more services in each ECSP with the management system(s) 906 .

[0108] Optionally, at step s910, the 3GPP management system 904 may receive corresponding pricing details from the management system(s) 906. These details may later be used to configure the charging system in the PLMN / ECSP.

[0109] Optionally, at step s912, a response indicating a successful feasibility check and corresponding pricing details may be provided by the 3GPP management system 904 to the ASP 902.

[0110] Optionally, at step s914, ASP 902 may indicate whether it accepts or agrees to the indicated feasibility and the received pricing model.

[0111] At step s916, the EAS is deployed in the corresponding EDN of the corresponding ECSP using the createMoi management service (as described in 3GPP TS28.532v16.4.0). Internally, the Managed Network Service (MnS) producer can use a virtualization system (NFV or container-based) to deploy the EAS.

[0112] At step s918, a response indicating the success or failure of the EAS deployment is returned by the management system(s) 906 to the 3GPP management system 904. In the case of success, a list of EASs and their corresponding geographic proximity to various known points in the network (e.g., their latency, and / or geographic area coordinates, and / or service reliability, and / or bandwidth information) may be provided.

[0113] Based on the deployed EAS, at step s920, the mapping system is supplied by the 3GPP management system 904 to the relevant 3GPP NF, namely the PLMN lookup NF 908. The mapping system maps a given UE edge service request to a given EAS. For example, this can be achieved by mapping UE access to the next generation NodeB (gNB) to certain EAS in the system and / or by mapping UE applications to the EAS of the appropriate EDN based on the received proximity (e.g., any geographic area, latency, reliability, or bandwidth information). When performing such mapping, the mapping system may also take into account the gNB to EAS latency and load balancing between EASs. The lookup NF 908 in which such a mapping system can be supplied can be any control or user plane or management plane function defined by 3GPP, such as AMF, SMF, UPF, MDAF or PCF.

[0114] At step s922 , a response indicating the success (or failure) of the configuration at s920 is returned to the 3GPP management system 904 .

[0115] Based on the mapping and the pricing model agreed upon at steps s912-s914 (or, if steps s912-s914 are not performed, based on, for example, a predetermined charging plan), at step s924, the CHF 910 in the PLMN / ECSP (the PLMN / ESCP to which the 3GPP management system 904 belongs) is configured accordingly.

[0116] At step s926, a response is returned by the CHF 910 to the 3GPP management system 904 indicating the success (or failure) of the configuration of the CHF 910 at step s924.

[0117] Optionally, at step s928, a response may be returned (eg, forwarded) to ASP 902 indicating the success (or failure) of the configuration of CHF 910 at step s924.

[0118] Thus, a process 900 for configuring / selecting and provisioning edge services for (eg, roaming) users in a wireless network is provided.

[0119] In one embodiment, a management system in a mobile network is provided. The management system can be used with reference to Fig. 9 The management system 904 described in more detail is consistent. The management system includes one or more processors, which are arranged to receive a request to provide an edge service, for example from an ASP 902. The request indicates the region in which the edge service will be provided. Any suitable manner of indicating, identifying and / or defining the region can be implemented, including but not limited to the manner covered or described by any 3GPP standard specification or ETSI standard specification. The one or more processors of the management system are also arranged to identify at least one edge data network EDN for providing the requested edge service based on at least a portion of the indicated region; and request or cause (for example, to a remote ECSP or a management system of the remote ECSP) to deploy an edge application server EAS in the identified EDN to provide the requested edge service in the specified region.

[0120] One or more processors may be arranged to send (e.g., to a remote edge computing service provider, ECSP, associated with the EDN) a request for the feasibility of deploying an EAS in the EDN in response to identifying the EDN. One or more processors may be arranged to receive (e.g., from a remote ECSP) a response indicating the feasibility of deploying an EAS in the EDN. Optionally, one or more processors may be arranged to send (e.g., to an ASP / entity from which a request to provide edge services was received) an indication as to whether deployment of the EAS in the EDN is feasible. The request for deployment or configuration of the EAS in the identified EDN may be made in response to receiving an indication that deployment of the EAS in the EDN is feasible. For example, in some embodiments, a request for such deployment or configuration is sent only if such deployment or configuration is feasible. In some embodiments, if the received indication indicates that deployment of the EAS in the EDN is not feasible, a request for deployment or configuration of the EAS in the identified EDN is not made (or caused).

[0121] The one or more processors may be arranged to send (e.g., to a remote edge computing service provider, ECSP, associated with the EDN) a request to reserve resources for deploying the EAS in the EDN in response to identifying the EDN. The one or more processors may be arranged to receive (e.g., from the remote ECSP) a response indicating whether the requested resources have been reserved. The one or more processors may be arranged to receive (e.g., from the remote ESCP) a timeout value specifying a time for which the requested resources should be reserved.

[0122] One or more processors may be arranged to send (e.g., to a remote edge computing service provider, ECSP, associated with the EDN) a request for pricing details for deploying the EAS in the EDN in response to identifying the EDN. One or more processors may be arranged to receive (e.g., from a remote ECSP) the requested pricing details for deploying the EAS in the EDN. One or more processors may be arranged to send (e.g., to an ASP / entity from which the request to provide edge services was received). One or more processors may be arranged to receive (e.g., from an ASP / entity from which the request to provide edge services was received) an indication of whether the pricing details were accepted.

[0123] One or more processors may be arranged to use the createMOI operation defined in TS28.532 to request or cause the deployment or configuration of the EAS in the identified EDN to provide the requested edge service in the indicated region. One or more processors may be arranged to use a virtualization system, network function virtualization NFV or container library to request the deployment of the EAS in the identified EDN to provide the requested edge service in the indicated region.

[0124] The one or more processors may be arranged to receive an indication (e.g., from a remote edge computing service provider ECSP associated with the EDN) as to whether the deployment of the EAS in the EDN was successful. The one or more processors may be arranged to: if the deployment of the EAS in the EDN was successful, receive (e.g., from a remote ECSP) an indication (such as a list including the EAS and the geographic proximity) of the EAS and one or more known points associated with the EAS in the mobile network. This may indicate geographic proximity to one or more known points in the EDN / network (e.g., with other / neighboring EASs or EDNs) in terms of geographic area (e.g., geographic area coordinates) and / or RTT delay and / or jitter and / or connection reliability.

[0125] One or more processors may be arranged to provision a mapping system in a network function NF of a mobile network, the mapping system mapping a user equipment to an EAS. The mapping system may be provisioned in response to a successful deployment of an EAS in an EDN. The mapping system may map a UE request to an EAS in an EDN based on the geographic location of the user equipment (e.g., satisfying one or more criteria for edge services). The NF may be any control or user plane or management plane function defined by 3GPP example AMF, SMF, PCF.

[0126] The one or more processors may be arranged to provision a mapping system that maps user equipment and / or its applications to the EDN.

[0127] The mapping can be performed by one or more of the following:

[0128] - Mapping the gNB used by the user equipment to the EDN; and / or

[0129] - Mapping geographic or latency or reliability or bandwidth information associated with the UE to the EDN; and / or

[0130] - Map any other characteristics of the UE to the EDN that optimizes the performance of edge services.

[0131] The mapping system may perform the (multiple) mappings taking into account the gNB (i.e., the UE's access gNB) to EAS latency and / or load balancing between EASs.

[0132] The management system may be an edge computing service provider ECSP or a management system of a public land mobile network PLMN.

[0133] The request to provide edge services may be received from an application service provider ASP in the mobile network.

[0134] The indicated regions may define one or more regions or service areas in a mobile network. The indicated regions may define one or more of: one or more geographic regions; one or more topological regions, which may be defined by a cell list; one or more edge service regions; one or more cloud service regions; one or more tracking regions; one or more identifiers indicating a geographic region; and / or one or more or sub-regions of one or more edge or cloud service regions. Sub-regions may be defined by edge platform coverage or edge service regions.

[0135] The EAS deployed in the EDN can be selected based on its compatibility with the software in the EDN. Therefore, given a geographic area, the management system can select an EDN combination so that the geographic area is covered. In addition, the management system can map other characteristics used to select EDNs, such as but not limited to software compatibility and / or reliability.

[0136] The EAS may be deployed on one or more (eg, multiple) ECSPs, one or more (eg, multiple) edge platforms, one or more (eg, multiple) cloud platforms, or any combination thereof.

[0137] EAS can be an edge enabling service, or a multi-access edge computing MEC service, or a MEC application.

[0138] In one embodiment, a method performed by a management system of a mobile network is provided. Fig.10 is a process flow chart showing certain steps of this embodiment. The method includes the following steps.

[0139] At s1002, a management system in a mobile network receives a request to provide an edge service, the request indicating a region in which the edge service is to be provided. Fig. 9 The management system 904 is described in more detail.

[0140] At s1004 , the management system identifies at least one edge data network EDN for providing the requested edge service based on the indicated territory.

[0141] At s1006 , the management system requests or causes the edge application server EAS to be deployed in the identified EDN to provide the requested edge service in the specified region.

[0142] The management system may be an edge computing service provider ECSP or a management system of a public land mobile network PLMN. The request to provide edge services may be received from an application service provider ASP in the mobile network. The request for deployment of the EAS may be sent to a remote edge computing service provider ECSP associated with the EDN.

[0143] The specified or indicated region may define one or more of the following:

[0144] One or more geographic areas; one or more topological areas, which may be defined by a cell list; one or more edge service areas; one or more cloud service areas; one or more tracking areas; one or more identifiers indicating geographic areas; and / or one or more or sub-areas of one or more edge or cloud service areas. A sub-area may be defined by edge platform coverage or edge service areas.

[0145] In another embodiment, a device in a mobile network is provided, the device comprising one or more processors, the one or more processors being arranged to: receive a request to provide an edge service, the request indicating a territory in which the edge service is to be provided; and identify at least one edge data network EDN for providing or supporting the requested edge service based on (i.e., within or covering) at least a portion of the indicated territory.

[0146] The apparatus may compile a list of one or more EDNs identified for providing or supporting edge services in the indicated region. The selection or identification of one or more EDNs may also be based on software compatibility, reliability, and / or one or more other selection criteria.

[0147] A novel aspect of the methods and apparatus disclosed herein is the ability of an ASP to support edge services in a given territory. In addition, only a portion of the territory indicated / specified by the ASP in the request may be covered by the PLMN / ECSP receiving the ASP request, i.e., covered by the PLMN / ECSP having the management system 904 in the above embodiment.

[0148] According to the methods and apparatus disclosed herein, a mapping system is provided for configuring a UE to select a desired EAS corresponding to an appropriate / optimal ECSP. Advantageously, this tends to provide a solution to the problem of how to configure a UE to optimally use edge services or to optimally serve a UE's request for edge services in a cost and performance efficient manner.

[0149] Furthermore, in the methods and apparatus disclosed herein, the mapping of gNB to ECSP is configured in the control plane. Advantageously, the need for the UE to provide geographic information at the application level to receive the best latency edge service is avoided.

[0150] Advantageously, embodiments described herein tend to provide internal management of load balancing between EASs, for example, by dynamically mapping UE requests to the load of an EAS.

[0151] Advantageously, the embodiments described herein support dynamics. More specifically, the gNB to ECSP mapping may be reconfigured, for example, in case any performance parameter of the EAS changes. The UE may not be aware of any failure in a specific case of the EAS.

[0152] In one embodiment, a method is provided for supporting edge service provisioning based on a request to support multiple regions or service areas, wherein the multiple regions or service areas include geographic areas or topological areas (e.g., cell lists, tracking areas, etc.), or edge / cloud service areas or sub-areas (defined by edge platform coverage or edge service areas).

[0153] Whether the EAS in each EDN is suitable for service provisioning may depend on various factors, such as compatibility with the EDN software.

[0154] EAS can be deployed across multiple ECSPs, multiple edge platforms or cloud platforms, or any combination thereof.

[0155] EAS can be an edge-enabled service, a MEC service, or a MEC application.

[0156] The method may include performing a feasibility check across multiple ECSPs to deploy the EAS on certain EDNs.

[0157] The method may include configuring, in a control plane NF, a mapping between (eg, from) a UE (or an application in the UE) and (eg, to) an EAS.

[0158] It should be noted that the above methods and apparatus illustrate rather than limit the invention, and that those skilled in the art will be able to design many alternative arrangements without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of other elements or steps than those listed in a claim, "a" or "an" does not exclude a plurality, and a single processor or other unit may perform the functions of several units described in a claim. Any reference signs in a claim should not be construed as limiting its scope.

[0159] Furthermore, although examples have been given in the context of specific communication standards, these examples are not intended to limit the communication standards to which the disclosed methods and apparatus may be applied. For example, although specific examples have been given in the context of 3GPP, the principles disclosed herein may also be applied to another wireless communication system, and indeed to any communication system that uses routing rules.

[0160] The method may also be embodied in a set of instructions stored on a computer-readable medium, which when loaded into a computer processor, a digital signal processor (DSP), etc., causes the processor to perform the above-described method.

[0161] The described methods and apparatus may be practiced in other specific forms. The described methods and apparatus are considered in all respects to be illustrative only and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes within the meaning and equivalent range of the claims should be included within their scope.

[0162] The following abbreviations are used herein and / or are known terms useful to those skilled in the art in understanding the methods and apparatus disclosed herein:

[0163] 3GPP: Third Generation Partnership Project

[0164] ICT: Information and Communications Technology

[0165] ASP: Application Service Provider

[0166] HPLMN: Home Public Land Mobile Network

[0167] ECSP: Edge Computing Service Provider

[0168] ACR: Application Context Relocation

[0169] EAS: Edge Application Server

[0170] EDN: Edge Data Network

[0171] EES: Edge Enablement Server

[0172] ECS: Edge Configuration Server

[0173] OP: Operator Platform

[0174] CSP: Cloud Service Provider

[0175] CEF: Charging Enablement Function

[0176] CHF: Billing function

[0177] CDR: Charging Data Record

[0178] CDF: Charging Data Function

[0179] CGF: Charging Gateway Function

[0180] BD: Billing domain

[0181] CTF: Charging Trigger Function

[0182] FCCSP: Joint Billing Coordinated Service Producer

[0183] LCM: Life Cycle Management

[0184] FCCSC: Joint billing coordination serves consumers

[0185] S or T-EES: Source or target EES

[0186] DNN: Data Network Name

[0187] DNAI: Data Network Access Identifier

Claims

1. A management system in a mobile network, the management system comprising one or more processors, the one or more processors being arranged to: receiving a request to provide an edge service, the request indicating a region in which the edge service is to be provided; Based on the indicated at least a portion of the territory, identifying at least one edge data network EDN for providing the requested edge service; as well as A request is made to deploy or configure at least one edge application server EAS in the at least one EDN to provide the requested edge service in the specified region.

2. The management system of claim 1, wherein the one or more processors are further arranged to: In response to identifying the EDN, sending a request for feasibility of deploying the EAS in the EDN; as well as receiving a response indicating the feasibility of deploying the EAS in the EDN; Optionally, sending an indication of whether deploying or configuring the EAS in the EDN is feasible; in The request to deploy or configure is made in response to receiving an indication that deployment of the EAS in the EDN is feasible.

3. A management system according to claim 1 or 2, wherein the one or more processors are further arranged to: In response to identifying the EDN, sending a request to reserve resources for deploying the EAS in the EDN; and Optionally, a response is received indicating whether the requested resource has been reserved.

4. The management system according to any one of claims 1 to 3, wherein the one or more processors are further arranged to: In response to identifying the EDN, sending a request for pricing details for deploying the EAS in the EDN; and The requested pricing details for deploying the EAS in the EDN are received.

5. The management system of claim 4, wherein the one or more processors are further arranged to: transmitting the received pricing details; and Optionally, an indication is received as to whether the pricing details are accepted.

6. A management system according to any one of claims 1 to 5, wherein the one or more processors are arranged to: Using the createMOI operation defined in TS28.532, requesting to deploy or configure the EAS in the identified EDN to provide the requested edge service in the indicated region; or Using a virtualization system, network function virtualization NFV, or a container library, request to deploy or configure the EAS in the identified EDN to provide the requested edge service in the indicated region.

7. The management system according to any one of claims 1 to 6, wherein the one or more processors are further arranged to: receiving an indication of whether the deploying of the EAS in the EDN was successful; and If the deploying of the EAS in the EDN is successful, then optionally receiving an indication of the EAS and geographic proximity relative to one or more known points in the mobile network associated with the EAS.

8. A management system according to any one of claims 1 to 7, wherein the one or more processors are further arranged to: A mapping system is provisioned in a network function NF of the mobile network, the mapping system mapping a user equipment to the EAS.

9. A management system according to claim 8, wherein the one or more processors are arranged to provision the mapping system that maps the user equipment to the EDN by one or more of: mapping a gNB used by the user equipment to the EDN; or Mapping geographic or latency or reliability or bandwidth information associated with the UE to the EDN.

10. The management system according to any one of claims 1 to 9, wherein the management system is a management system of an edge computing service provider (ECSP) or a public land mobile network (PLMN).

11. The management system according to any one of claims 1 to 10, wherein the request to provide edge service is received from an application service provider ASP in the mobile network.

12. A management system according to any one of claims 1 to 11, wherein the indicated regions define one or more regions or service areas in the mobile network.

13. The management system of claim 12, wherein the indicated region defines one or more of the following: one or more geographic regions; one or more topological regions; One or more edge service regions; One or more cloud service regions; one or more tracking areas; or one or more identifiers indicating a geographic area; or One or more sub-regions within one or more edge or cloud service regions.

14. The management system according to any one of claims 1 to 13, wherein the EAS deployed in the EDN is selected based on its compatibility with software in the EDN.

15. The management system of any one of claims 1 to 14, wherein the EAS is deployed across one or more ECSPs, one or more edge platforms, one or more cloud platforms, or any combination thereof.

16. The management system according to any one of claims 1 to 15, wherein the EAS is an edge enabling service, or a multi-access edge computing MEC service, or a MEC application.

17. A method performed by a management system of a mobile network, the method comprising: receiving a request to provide an edge service, the request indicating a region in which the edge service is to be provided; Based on the indicated region, identifying at least one edge data network EDN for providing the requested edge service; as well as Request to deploy or configure an edge application server EAS in the identified EDN to provide the requested edge service in the specified region.

18. The method of claim 17, wherein: The management system is a management system of an edge computing service provider ECSP or a public land mobile network PLMN; The request to provide the edge service is received from an application service provider ASP in the mobile network; as well as The request to deploy or configure the EAS is sent to a remote edge computing service provider ECSP associated with the EDN.

19. The method according to claim 17 or 18, wherein the specified region defines one or more of the following: one or more geographic regions; one or more topological regions; One or more edge service regions; One or more cloud service regions; or One or more sub-regions of one or more edge or cloud service regions.

20. An apparatus in a mobile network, the apparatus comprising one or more processors, the one or more processors being arranged to: receiving a request to provide an edge service, the request indicating a region in which the edge service is to be provided; and At least one edge data network (EDN) for providing the requested edge service is identified based on the indicated at least a portion of the territory.

Images