Apparatus and method for mobile computing network control and management

Abstract

A user equipment (UE) (110) for communicating with an edge data network in a mobile network (100), in particular a 3GPP 5G or 6G network (100) is disclosed. The UE (110) is configured to operate in a UE mode and a mobile computing node (MCN) mode, the UE (110) comprises a mobile edge application server (111) configured to cause the UE (110) to operate in the MCN mode to act as an edge data network node of the mobile network (100), e.g. as an edge application server. Thus, in the MCN mode, the UE (110) can contribute its computing and / or communication resources to the edge data network.

Description

Technical Field

[0001] This invention relates to wireless communication. More specifically, this invention relates to apparatus and methods for controlling and managing mobile computing networks. Background Technology

[0002] Technologies such as mobile edge computing, multi-access edge computing, and fog computing enable cloud computing and IT service environments to operate at or near the edge of cellular networks (i.e., mobile networks). The fundamental idea behind these technologies is that by running applications and performing related processing tasks closer to cellular network customers, network congestion can be reduced, resulting in better application performance. Typically, these technologies are designed to be implemented at base stations or other edge nodes in the mobile network's access network, enabling customers to flexibly and quickly deploy new applications and services, such as in autonomous driving, V2X communications, and robotics applications. Summary of the Invention

[0003] The aim is to provide improved devices and methods for controlling and managing mobile computing networks.

[0004] The foregoing and other objectives are achieved through the subject matter claimed in the independent claims. Other implementations are apparent from the dependent claims, the specification, and the drawings.

[0005] According to a first aspect, a user equipment (UE) is provided for communicating with an edge data network in a mobile network. The mobile network may be a 3GPP network with an edge data network, specifically a 5G or 6G network. The UE according to the first aspect is used to operate in UE mode and mobile computing node (MCN) mode, where the UE mode is a normal UE operating mode in which the UE behaves like a normal UE. The UE according to the first aspect includes a mobile edge application server for enabling the UE to operate in the MCN mode to act as an edge data network node of the edge data network of the mobile network, specifically acting as an edge application server. Therefore, in MCN mode, the UE according to the first aspect can contribute its computing and communication resources to the edge data network.

[0006] In this document, one or more of the following abbreviations and / or acronyms may be used above and below: V2X vehicle-to-everything (V2X) MaaS (Mobile as a Service) uRLLC ultra-high reliability and ultra-low latency communication KPIs (Key Performance Indicators) FOG Fog Calculation MEC Multi-Access Edge Computing V2I (Vehicle-to-Infrastructure) MCN Mobile Computing Nodes EDN Edge Data Network MEAS Mobile Edge Application Server MEES Mobile Edge Enabler Server MECS Mobile Edge Configuration Server CMC Connection Management Client CMS Connection Management Server MECSP Mobile Edge Computing Service Provider ECSP Edge Computing Service Provider PLMN Public Land Mobile Network In another possible implementation, the UE according to the first aspect further includes: a mobile edge enabling server for enabling other entities (specifically other UEs) to discover the mobile edge application server of the UE in the edge data network of the mobile network. This enables the UE, acting as an MCN (i.e., in MCN mode), to be efficiently discovered in the EDN of the mobile network.

[0007] In another possible implementation, the UE according to the first aspect further includes: a mobile edge configuration server for providing configuration information to corresponding edge-enabled clients of one or more other UEs for connecting to the mobile edge application server of the UE. This enables one or more other UEs in the mobile network to efficiently connect to the UE used as an MCN (i.e., in MCN mode).

[0008] In another possible implementation, the UE according to the first aspect further includes: a connection management client for receiving control data from the connection management server of the edge data network of the mobile network. This enables the EDN to efficiently control the UE used as an MCN (i.e., in MCN mode).

[0009] In another possible implementation, the connection management client of the UE according to the first aspect is used to operate as a gateway for the core network of the mobile network. This allows the UE, acting as an MCN (i.e., in MCN mode), to provide additional computing and communication resources to the mobile network.

[0010] In another possible implementation, the connection management client of the UE according to the first aspect is used to interact directly with the edge data network of the mobile network. This supports efficient and fast communication between the UE, which is used as an MCN (i.e., in MCN mode), and the EDN.

[0011] In another possible implementation, the connection management client is specifically configured to report the IP address of the UE as described in the first aspect to the connection management server of the edge data network of the mobile network in response to a corresponding request from the connection management server. This enables the EDN to efficiently control the UE used as an MCN (i.e., in MCN mode).

[0012] In another possible implementation, the connection management client of the UE according to the first aspect is used to send a unique UE identifier, specifically a universally unique identifier (UUID), to the connection management server of the edge data network of the mobile network to register with the connection management server. This enables the EDN to efficiently control the UE used as an MCN (i.e., in MCN mode).

[0013] In another possible implementation, in response to sending the unique UE identifier, specifically a UUID, to the connection management server of the edge data network of the mobile network, the connection management client of the UE according to the first aspect receives an MCN identifier from the connection management server. This enables the EDN to efficiently control the UE used as an MCN (i.e., in MCN mode).

[0014] In another possible implementation, in response to receiving a message, specifically an SMS message, from the connection management server of the edge data network of the mobile network, including the address of the connection management server, the connection management client of the UE according to the first aspect is used to reconnect with the connection management server. This provides an efficient mechanism for maintaining a communication connection between the UE and the EDN, which is used as an MCN (i.e., in MCN mode).

[0015] In another possible implementation, the UE according to the first aspect further includes a mobile edge computing service provider (MECSP), wherein the MECSP interacts with the PLMN management system of the mobile network to manage the UE for operation in the MCN mode, thereby enabling the UE to act as an edge data network node of the mobile network, specifically an edge application server. This supports the seamless integration of the UE used as an MCN (i.e., in MCN mode) into existing and / or standardized mobile network architectures.

[0016] According to a second aspect, a method is provided for operating user equipment (UE) for communicating with an edge data network in a mobile network (specifically a 3GPP network), the UE being used to operate in UE mode and mobile computing node (MCN) mode. The method according to the second aspect includes the step of: enabling the UE to operate in the MCN mode to act as an edge data network node of the mobile network, specifically an edge application server.

[0017] The method according to the second aspect can be executed by the UE according to the first aspect. Furthermore, other features of the method according to the second aspect are directly derived from the functionality of the UE described in the first aspect and its various implementations described above and below.

[0018] According to a third aspect, an edge data network node is provided for communicating with multiple user equipment (UEs) in a mobile network (specifically a 3GPP network). The edge data network node according to the third aspect includes: a connection management server for interacting with a connection management client of one of the plurality of UEs to manage the UE to operate in a mobile computing node (MCN) mode, wherein in the MCN mode, the UE acts as an edge data network node of the mobile network, specifically an edge application server. Therefore, the EDN node according to the third aspect supports enabling UEs to contribute their computing and communication resources to the edge data network.

[0019] In another possible implementation, the connection management server of the edge data network node according to the third aspect is used to send control data to the connection management client of the UE to enable the UE to operate in the MCN mode. This allows the EDN node to efficiently control (e.g., configure) the UE used as an MCN (i.e., in MCN mode).

[0020] In another possible implementation, the connection management server requests the UE's IP address from the connection management client and receives the UE's IP address from the connection management client. This enables the EDN node to efficiently control the UE used as an MCN (i.e., in MCN mode).

[0021] In another possible implementation, the connection management server registers the UE in response to a registration request from the connection management client, wherein the registration request includes the UE's unique UE identifier, specifically a UUID. This enables the EDN node to efficiently control the UE used as an MCN (i.e., in MCN mode).

[0022] In another possible implementation, in response to receiving the registration request from the connection management client, the connection management server sends an MCN identifier to the connection management client. This enables the EDN node to efficiently control the UE used as an MCN (i.e., in MCN mode).

[0023] In another possible implementation, the connection management server sends a message, specifically an SMS message, to the connection management client, including the address of the connection management server, to reconnect the connection management client to the connection management server. This provides an efficient mechanism for maintaining the communication connection between the UE and the EDN, which is used as an MCN (i.e., in MCN mode).

[0024] According to a fourth aspect, a method is provided for operating an edge data network node for communicating with multiple user equipment (UEs) in a mobile network (specifically a 3GPP network), the edge data network node including a connection management server. The method according to the fourth aspect includes the steps of: interacting between the connection management server and a connection management client of one of the plurality of UEs to manage the UE to operate in a mobile computing node (MCN) mode, wherein in the MCN mode, the UE acts as an edge data network node of the mobile network, specifically an edge application server.

[0025] The method described according to the fourth aspect can be executed by the edge data network node described according to the third aspect. Furthermore, other features of the method described according to the fourth aspect directly derive from the functionality of the edge data network node described in the third aspect and its various implementations described above and below.

[0026] According to a fifth aspect, a computer program product is provided, including a computer-readable storage medium for storing program code, which, when executed by a computer or processor, causes the computer or processor to perform the method according to the second aspect and the method according to the fourth aspect.

[0027] One or more embodiments will be described in detail in the accompanying drawings and the following description. Other features, objects, and advantages will be apparent from the specification, drawings, and claims. Attached Figure Description

[0028] The embodiments of the present invention will be described in detail below with reference to the accompanying drawings. In the drawings: Figure 1aA schematic diagram of a mobile network is shown, which includes a user equipment provided in one embodiment and an edge data network node provided in another embodiment; Figure 1b It shows the result of Figure 1a A schematic diagram of the general architecture for mobile network implementation; Figure 2 It shows Figure 1a A schematic diagram of another embodiment of a mobile network; Figure 3 It shows Figure 1a A schematic diagram of another embodiment of a mobile network; Figure 4 A signaling diagram illustrating the interaction between a user equipment provided in one embodiment and an edge data network node provided in another embodiment is shown. Figure 5 A signaling diagram illustrating the interaction between a user equipment provided in another embodiment and an edge data network node provided in another embodiment is shown. Figure 6 A signaling diagram illustrating the interaction between a user equipment provided in another embodiment and an edge data network node provided in another embodiment is shown. Figure 7 A schematic diagram illustrating several implementation examples of a user equipment in the form of a vehicle provided in one embodiment is shown; Figure 8 A signaling diagram illustrating the interaction between a user equipment in the form of a vehicle, provided in another embodiment, and an edge data network node, provided in another embodiment, is shown. Figure 9 A flowchart of a method for operating a user equipment according to an embodiment is shown; Figure 10 A flowchart of a method for operating an edge data network node according to an embodiment is shown.

[0029] In the following text, the same reference numerals refer to the same or at least functionally equivalent features. Detailed Implementation

[0030] In the following description, reference is made to the accompanying drawings, which form part of this invention, illustrating by way of description specific aspects of embodiments of the invention or specific aspects in which embodiments of the invention may be used. It should be understood that embodiments of the invention can be used in other aspects and include structural or logical variations not depicted in the drawings. Therefore, the following detailed description should not be construed as limiting, and the scope of the invention is defined by the appended claims.

[0031] For example, it should be understood that the disclosure relating to the described method also applies to the corresponding device or system used to perform the method, and vice versa. For example, if one or more specific method steps are described, the corresponding device may include one or more units (e.g., functional units) to perform the described one or more method steps (e.g., one unit performs one or more steps, or multiple units perform one or more of multiple steps respectively), even if such one or more units are not explicitly described or illustrated in the drawings. Furthermore, if a specific apparatus is described based on one or more units such as functional units, the corresponding method may include a step to perform the function of one or more units (e.g., one step performs the function of one or more units, or multiple steps perform the function of one or more of multiple units respectively), even if such one or more units are not explicitly described or illustrated in the drawings. Moreover, it is understood that, unless otherwise explicitly stated, features of the various exemplary embodiments and / or aspects described herein can be combined with each other.

[0032] Figure 1a A schematic diagram of a mobile network 100 is shown, which includes a user equipment (UE) 110 provided in one embodiment and an edge data network with edge data network nodes 120 provided in another embodiment; Figure 1a In the illustrated embodiment, the mobile network 100 also includes a core network 105, which is implemented as a 3GPP network, such as a 3GPP 5G or 6G network.

[0033] UE 110 is designed to operate in both UE mode and mobile computing node (MCN) mode. UE mode is the standard UE operating mode, in which UE 110 behaves like a normal UE. This will be described in more detail below. Figure 1a As shown, UE 110 includes a mobile edge application server 111, which enables UE 110 to operate in MCN mode to act as an edge data network node of the edge data network of mobile network 110, specifically acting as an edge application server. In other words, in MCN mode, UE 110 contributes its computing and / or communication resources to the edge data network, so that for other UEs (operating in normal UE mode), UE 110 appears as a component of the edge data network.

[0034] The edge data network includes an edge data network node 120, which includes or is implemented as a connection management server 122. As will be described in more detail below, the connection management server 122 interacts with the connection management client 115 of the UE 110 to manage the UE 110 for operation in MCN mode. As described above, in MCN mode, the UE acts as an edge data network node of the mobile network 100, specifically an edge application server.

[0035] Further reference Figure 1b It will be understood that the diagram illustrates the... Figure 1a This diagram illustrates a general architecture for a mobile network 100 and its components, providing MCN enablement, MCN management, and MCN connectivity according to embodiments disclosed herein. MCN enablement can be implemented as part of an edge enablement layer 202 located below the application layer 201, defining the overall functionality provided by the MCN enablement entity to support consumer applications. MCN management can be implemented as part of an edge management layer 205 associated with an edge hosting environment 203, providing management of the MCN edge system (including the network, the MCN enablement layer, and applications). MCN connectivity can be implemented as part of a 3GPP transport layer 204 to support consumer applications and the MCN edge enablement entity. MCN connectivity can be used to monitor MCN status, handle MCN mobility, and / or ensure MCN connectivity QoS. Figure 1b The general architecture shown can be based on an architecture that conforms to 3GPP and / or ETSI standards.

[0036] return Figure 1a In order to achieve Figure 1b The MCN is enabled, and the control connection between the MCN and EDN is executed through the connection management client 115 of UE 110 and the connection management server 122 of EDN. In one embodiment, the connection management client 115 and the connection management server 122 are used to exchange control data through the 3GPP network using the EDGE-8M and EDGE-9MS interfaces. This operation can be based on the EDGE-9 connection principle between multiple ECSs and different EDNs. The MCN can be regarded as a "separate EDN". Based on the same principle, the EDGE-2M interface can realize the interaction between MEES and 3GPP core network functions and APIs to retrieve network capability information, and the EDGE-7M reference point can realize the interaction between EAS and 3GPP core network functions and APIs to retrieve network capability information. In one embodiment, the mobile edge enabling layer is responsible for one or more of the following functions and / or services: service provisioning; registration; MEAS discovery; capability exposure to EAS; support for service continuity; security; dynamic MEAS instantiation triggering; and / or MCN billing.

[0037] Figure 2 It shows the method of providing Figure 1b The MCN management shown Figure 1a A schematic diagram of another embodiment of a mobile network. More specifically, in Figure 2 In the illustrated embodiment, UE 110 also includes a mobile edge computing service provider (MECSP) management system 117 (or simply MECSP 117), wherein MECSP 117 is responsible for the lifecycle management of MCN services, such as the instantiation, termination, modification, and querying of MCN services and components. In one embodiment, MECSP 117 can be used to: synchronize with an edge computing service provider (ECSP) management system 150 (or simply ECSP 150); interact with a PLMN management system 140; and / or cooperate with 3GPP-defined management services to enable consumers (e.g., ASPs, ECSPs) to orchestrate and manage MCNs.

[0038] Figure 3 It shows the method of providing Figure 1b The MCN connectivity shown Figure 1a This is a schematic diagram of another embodiment of the mobile network. As described above in the context of Figure 1, the connection management client 115 and connection management server 122 of UE 110 are entities that support connectivity issues. Since the MCN may belong to different networks, in one embodiment, the MCN connection management client 115 and server 122 can be further used to provide bridging between an untrusted non-3GPP MCN and the 5G core. This may be based on a 3GPP-compliant architecture managed by edge computing.

[0039] According to one embodiment, MCN connectivity can have two types of implementations: one for untrusted MCNs and one for trusted MCNs.

[0040] In the case of an untrusted MCN, the connection management client 115 can act as a gateway to the 5GCN, supporting EDGE-10MC and EDGE-2M interfaces toward the 5GCN. At the EDN, using the EDGE-9MS interface, the RAN can redirect untrusted signaling to the connection management server 122. This process can be similar to the N3IWF proposed in 3GPP.

[0041] In the case of a trusted MCN, the MCN can interact directly with the EDN through the UPF. In this scenario, the UPF has a direct connection to the edge application server 121.

[0042] In many use cases, numerous distributed computing architectures may be required to send data to the UE 110. However, due to mobility and network functions such as NAT / NAPT and firewalls, it can be challenging for the mobile service provider server to effectively reach the MCN. Possible scenarios include: changes in IP anchors due to changes in the MSP edge server; timers for network functions such as NAT / NAPT potentially expiring; service interruptions occurring when the vehicle carrying the UE moves to an area without network coverage; and / or handover between different access networks.

[0043] Figure 4 A signaling diagram is shown for providing direct open interaction between a UE 110 provided in one embodiment and an edge data network node provided in another embodiment. Network open functions (such as SCEF defined in 3GPP TS 23.682 and NEF defined in 3GPP TS 29.522) specify various network APIs for third parties. According to one embodiment, MCN 110 (specifically, connection management client 115) can be triggered through these open functions to report its IP address to the MSP server. More specifically, in Figure 4 In step 401, the connection management server 122 registers the MCN 110 ID with the mobile network 100 (specifically its core network 105). Any IP changes within the mobile network 100 (see...) Figure 4 (403) can notify the MCN connection management client 115 in step 405, and in Figure 4 Step 407 notifies the EDN connection management server 122. Figure 4 The process shown ensures seamless synchronization between MCN 110 and EDN 120 in the event of network changes in mobile network 100.

[0044] Figure 5 A signaling diagram illustrating the interaction between a UE 110 provided in another embodiment and an edge data network node implementing a notification scheme provided in another embodiment is shown. Figure 5 In the illustrated embodiment, push notifications are messages automatically "pushed" from the MCN connection management server 122 to remote clients. Each MCN management client application needs to register with the MCN management server using a unique key or UUID. More specifically, in Figure 5 In step 501, the connection management client 115 of UE 110 sends a UUID registration to the connection management server 122. Due to an unexpected connection failure and / or problem between entities 115 and 122 (see...), Figure 5 (503), the MCN connection management server 122 sends a push notification with a unique MCN application ID to the MCN connection management client 115, such as Figure 5Step 505 is shown. Figure 5 The process shown ensures resynchronization and authentication between entities 115 and 122 without involving / triggering mobile network 100.

[0045] Figure 6 A signaling diagram illustrating the interaction between a UE 110 provided in another embodiment and an edge data network node provided in another embodiment for providing an incoming SMS call is shown. Push SMS is an SMS "incoming call" trigger message in current over-the-air (OTA) software delivery systems. According to one embodiment, the trigger message can be sent by an EDN connection management server 122 to the target MCN. The application can maintain a link to a database operated by the OEM, which includes the IMEI number of each MCN client in the queue. More specifically, in Figure 6 In step 601, the connection between the connection management server 122 and the connection management client 115 may be lost. In this extreme case, such as Figure 6 As shown in step 603, the EDN connection management server 122 contacts / triggers a reconnection process with the MCN connection management client 115 using an SMS push notification. The SMS includes the management server's IP address. Figure 6 In step 605, the MCN connection management client 115 reconnects with the EDN connection management client 112 using the new IP information. Although the mobile network 100 and the EDN connection management server 112 cannot connect, this process ensures active synchronization and communication medium between entities 115 and 122.

[0046] Figure 7 This diagram illustrates the operational flow of the activation phase of the MCN mode for a UE 110 (implemented as a vehicle or its component, i.e., for a V2X use case) provided in one embodiment for four different scenarios. In the first scenario 1a, the MCN application client 112 of the MCN UE 110 requests in-vehicle MCN processing. In the second scenario 1b, the EDN node 120 requests the MCN UE 110 to perform in-vehicle MCN processing. In the third scenario 1c, another UE 130 communicating with the EDN requests service from the MCN UE 110. In the fourth scenario 1d, the MCN edge enabling server 113 of the MCN UE 110 detaches from the EDN and performs in-vehicle MCN processing.

[0047] Figure 8A signaling diagram illustrating the interaction between a UE 110, provided as a vehicle or a component thereof, and an edge data network node 120, provided as in another embodiment, is shown. In this example, two UEs (one without MCN capability 130, and one with MCN capability 110) are connected to the same EDN 120. EDN 120 intends to direct / redirect traffic from UE 130 to UE-MCN 110. Figure 8 In the first step 801, the V2X enabling server 123 of EDN node 120 sends a registration request to the mobile V2X enabling server 113 of UE 110 within UE 110. In step 803, the mobile V2X enabling server 113 and the mobile V2X configuration server 116 perform a feasibility check to assess whether the current UE-MCN 110 system capabilities and service load are sufficient to guarantee optimal UE 130 service performance without harming other potential users currently being served. In this example, the request from step 801 is accepted, and an acknowledgment is sent to the EDN in step 805. In parallel, in step 807, entity 113 sends a notification request with an MCN connection request to the VAE server 132 of UE 130. In step 809, the VAE server 132 and the mobile V2X enabling server 113 perform a handshake process to register / authenticate UE 130 to UE-MCN 110. Following this process, VAE server 132 no longer redirects its data to V2X enabling server 123, but instead redirects it directly to mobile V2X enabling server 113. In step 811, the process is acknowledged from VAE server 132 to mobile V2X enabling server 113. Since multiple VAE clients 134 can be instantiated on the same UE 130, the expected VAE client 134 should register with mobile V2X application server 111 after step 813. Once the application registration process is complete, the mobile V2X configuration server 116 of UE-MCN 110 detaches from EDN 120 after step 815.

[0048] Figure 9 A flowchart of a method 900 for operating a UE (e.g., UE 110) to communicate with an edge data network in a mobile network (e.g., mobile network 100 described above) is shown. As described above, UE 110 is used to operate in UE mode and mobile computing node (MCN) mode, i.e., as an MCN UE 110. Method 900 includes step 901: enabling UE 110 to operate in MCN mode to act as an edge data network node of mobile network 100.

[0049] Figure 10A flowchart is shown of a method 1000 for operating an edge data network node (e.g., the aforementioned EDN node 120) to communicate with multiple user equipment (UEs) (including UE 110) in a mobile network (e.g., mobile network 100 described above). As described above, the edge data network node 120 includes a connection management server 122. The method 1000 includes step 1001: interacting between the connection management server 122 and a connection management client 115 of UE 110 to manage UE 110 to operate in mobile computing node (MCN) mode, wherein, in MCN mode, UE 110 acts as an edge data network node of mobile network 100.

[0050] For example, the embodiments disclosed herein can be implemented in use cases involving multiple mobile robots, in low-latency robotics and / or V2X applications, or in traditional low-coverage infrastructure. Based on the embodiments disclosed herein, vehicle / robot OEMs can provide not only mobility services but also computing resources and services. By flexibly deploying edge / fog computing capabilities, dedicated investments in computing infrastructure (server rooms, fiber optics, roadside units) can be reduced. Vehicle owners / operators can benefit from sharing unused computing resources. Complex scenarios and low-coverage conditions are no longer limitations on low-latency and high-reliability communication.

[0051] As will be understood, the embodiments disclosed herein provide an improved architecture and enhanced functionality capable of accurately representing network KPIs through models, thereby ensuring limited overhead and high privacy. Transmitting models instead of data significantly reduces the amount of information exchanged between network nodes and the central node responsible for optimization. Furthermore, data remains local, storing only useful data. Additionally, according to the embodiments disclosed herein, the ML model can be updated based on different centralized or local triggers. This is because the embodiments disclosed herein utilize available data to detect network changes and modeling performance degradation, and update the model accordingly. The network model can remain up-to-date while limiting communication overhead and energy consumption. The management framework / system 130 can push model updates based on, for example, optimized network performance or models received by different RAN nodes 120a to 120n. The embodiments disclosed herein utilize the ML / AI capabilities available in network nodes 120a to 120n. Therefore, available local processing power can be utilized efficiently, i.e., training models during nighttime when traffic load is low. Furthermore, the embodiments disclosed herein support coordination between nodes in different domains. For example, the management framework / system 130 can leverage distributed learning and expert knowledge to define the features needed to build each model, select model hyperparameters, create a global model from local models, and / or identify new model architectures. Models can be shared to represent KPIs that are typically not shared through standardized interfaces.

[0052] Those skilled in the art will understand that “blocks” (“units”) in the various figures (methods and apparatuses) represent or describe the functionality of embodiments of the invention (and are not necessarily independent “units” in hardware or software), thereby equally describing the functionality or features (unit = step) of apparatus embodiments and method embodiments.

[0053] Several embodiments are provided in this application; it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the described embodiments of the apparatus are merely exemplary. For example, the unit division is only a logical functional division, and other division methods may be used in actual implementation. For example, multiple units or components may be merged or integrated into another system, or some features may be ignored or not performed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed can be implemented through some interface. Indirect coupling or communication connection between devices or units can be implemented electronically, mechanically, or otherwise.

[0054] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of the embodiment solution according to actual needs.

[0055] In addition, the functional units in the embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

Claims

1. A user equipment (UE) (110) for communicating with an edge data network in a mobile network (100), characterized in that, The UE (110) is used to operate in UE mode and mobile computing node MCN mode, and the UE (110) includes a mobile edge application server (111) for enabling the UE (110) to operate in the MCN mode to act as an edge data network node of the mobile network (100).

2. The UE (110) according to claim 1, characterized in that, The UE (110) further includes a mobile edge enabling server (113) for enabling the discovery of the mobile edge application server (111) of the UE (110) in the edge data network of the mobile network (100).

3. The UE (110) according to claim 1 or 2, characterized in that, The UE (110) further includes a mobile edge configuration server (116) for providing configuration information to the corresponding edge-enabled clients (114) of one or more other UEs (130) for connecting to the mobile edge application server (111) of the UE (110).

4. The UE (110) according to any one of the preceding claims, characterized in that, The UE (110) further includes a connection management client (115) for receiving control data from the connection management server (122) of the edge data network of the mobile network (100).

5. The UE (110) according to claim 4, characterized in that, The connection management client (115) is used to operate as a gateway of the core network (105) of the mobile network (100).

6. The UE (110) according to claim 5, characterized in that, The connection management client (115) is used to interact directly with the edge data network of the mobile network (100).

7. The UE (110) according to claim 4, characterized in that, The connection management client (115) is used to report the IP address of the UE (110) to the connection management server (122) of the edge data network of the mobile network (100).

8. The UE (110) according to claim 4, characterized in that, The connection management client (115) is used to send a unique UE identifier to the connection management server (122) of the edge data network of the mobile network (100) to register with the connection management server (122).

9. The UE (110) according to claim 8, characterized in that, In response to sending the unique UE identifier to the connection management server (122) of the edge data network of the mobile network (100), the connection management client (115) is used to receive the MCN identifier from the connection management server (122).

10. The UE (110) according to claim 4, characterized in that, In response to receiving a message including the address of the connection management server (122) of the edge data network of the mobile network (100), the connection management client (115) is used to reconnect with the connection management server (122).

11. The UE (110) according to any one of the preceding claims, characterized in that, The UE (110) also includes a Mobile Edge Computing Service Provider (MECSP) (117), wherein the MECSP (117) is used to interact with the PLMN management system (140) of the mobile network (100) to manage the operation of the UE (110), thereby enabling the UE (110) to act as an edge data network node of the mobile network (100).

12. A method (900) for operating a user equipment (UE) (110) for communicating with an edge data network in a mobile network (100), characterized in that, The UE (110) is used to operate in UE mode and mobile computing node MCN mode, and the method (900) includes enabling the UE (110) to operate in the MCN mode (901) to act as an edge data network node of the mobile network (100).

13. An edge data network node (120) for communicating with multiple user equipment (UE) devices in a mobile network (100), characterized in that, The edge data network node (120) includes a connection management server (122), wherein the connection management server (122) is used to interact with a connection management client (115) of one of the plurality of UEs (110) to manage the UE (110) to operate in a mobile computing node MCN mode, wherein in the MCN mode, the UE (110) acts as an edge data network node of the mobile network (100).

14. The edge data network node (120) according to claim 13, characterized in that, The connection management server (122) is used to send control data to the connection management client (115) so that the UE (110) can run in the MCN mode.

15. The edge data network node (120) according to claim 13 or 14, characterized in that, The connection management server (122) is used to request the IP address of the UE (110) from the connection management client (115) and receive the IP address of the UE (110) from the connection management client (115).

16. The edge data network node (120) according to any one of claims 13 to 15, characterized in that, The connection management server (122) is used to register the UE (110) in response to a registration request from the connection management client (115), wherein the registration request includes a unique UE identifier of the UE (110).

17. The edge data network node (120) according to claim 16, characterized in that, In response to receiving the registration request from the connection management client (115), the connection management server (122) sends an MCN identifier to the connection management client (115).

18. The edge data network node (120) according to any one of claims 13 to 17, characterized in that, The connection management server (122) is used to send a message to the connection management client (115), wherein the message includes the address of the connection management server (122) so that the connection management client (115) can reconnect with the connection management server (122).

19. A method (1000) for operating an edge data network node (120) for communicating with a plurality of user equipment (UE) in a mobile network (100), characterized in that, The edge data network node (120) includes a connection management server (122), and the method (1000) includes interacting (1001) between the connection management server (122) and a connection management client (115) of one of the plurality of UEs (110, 130) to manage the UE (110) to operate in a mobile computing node MCN mode, wherein, in the MCN mode, the UE (110) acts as an edge data network node of the mobile network (100).

20. A computer program product, characterized in that, Includes a computer-readable storage medium for storing program code, which, when executed by a computer or processor, causes the computer or processor to perform the method (900) according to claim 12 or the method (1000) according to claim 19.

Images