Mechanism for determining edge computing and network resources for application
Patent Information
- Application Number
- PCT/CN2023/096932
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-29
- Publication Date
- 2024-12-05
Smart Images

Figure CN2023096932_05122024_PF_FP_ABST
Abstract
Description
MECHANISM FOR DETERMINING EDGE COMPUTING AND NETWORK RESOURCES FOR APPLICATIONTECHNICAL FIELD
[0001] Various example embodiments described in the subject disclosure generally relate to the field of telecommunication. In particular, some example embodiments relate to methods, devices, apparatuses and computer readable storage medium for determining edge computing and network resources.BACKGROUND
[0002] Mobile augmented reality (AR) / virtual reality (VR) , industrial control, and vehicle to everything (V2X) are viable scenarios for mobile edge computing. These applications have the capacity to impact a network with respect to latency, bandwidth and even mobility. These applications can also exert a sizable compute demand for certain use cases, when –for instance –artificial intelligence (AI) / machine learning (ML) algorithms and data analytics are applied and implemented with various demands on an infrastructure under specific timing constraint (s) . Hence, networking and edge cloud may be considered parts of a whole end-to-end (E2E) solution.SUMMARY
[0003] Some example embodiments of the subject disclosure will be described with respect to certain aspects. These aspects are not intended to indicate key or essential features of the various example embodiments of the subject disclosure, nor are they intended to be used to limit the scope thereof. Other features, aspects and elements will be readily apparent to a person skilled in the art in view of the subject disclosure.
[0004] In a first aspect, there is provided a first device. The first device comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first device to: receive, from a second device, an application identity associated with an application; and determine an edge computing resource and a network resource for the application based on the application identity, edge computing resource information, and network status information.
[0005] In a second aspect, there is provided a second device. The second device comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second device to: transmit, to a first device, an application identity associated with an application; and receive, from the first device, access information regarding a sever of the application on a third device, and wherein access information is determined based on the application identity, edge computing resource information, and network status.
[0006] In a third aspect, there is provided a method. The method comprises: receiving, at a first device and from a second device, an application identity associated with an application; and determining an edge computing resource and a network resource for the application based on the application identity, edge computing resource information, and network status information.
[0007] In a fourth aspect, there is provided a method. The method comprises: transmitting, at a second device and to a first device, an application identity associated with an application; and receiving, from the first device, access information regarding a sever of the application on a third device, and wherein access information is determined based on the application identity, edge computing resource information, and network status.
[0008] In a fifth aspect, there is provided a first apparatus. The first apparatus comprises means for receiving, from a second apparatus, an application identity associated with an application; and means for determining an edge computing resource and a network resource for the application based on the application identity, edge computing resource information, and network status information.
[0009] In a sixth aspect, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a first apparatus, an application identity associated with an application; and means for receiving, from the first apparatus, access information regarding a sever of the application on a third apparatus, and wherein access information is determined based on the application identity, edge computing resource information, and network status.
[0010] In a seventh aspect, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the third aspect.
[0011] In an eighth aspect, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.BRIEF DESCRIPTION OF THE DRAWINGS
[0012] Some example embodiments will now be described with reference to the accompanying drawings, where:
[0013] FIG. 1 illustrates an example communication environment in which example embodiments can be implemented;
[0014] FIG. 2 illustrates a signaling chart for determining the edge computing resource and the network resource according to some example embodiments;
[0015] FIG. 3 illustrates an example of the communication environment shown in FIG. 1 according to some example embodiments;
[0016] FIG. 4 illustrates a signaling chart for determining the edge computing resource and the network resource during an initiation procedure according to some example embodiments;
[0017] FIG. 5 illustrates a signaling chart for determining the edge computing resource and the network resource during a handover procedure according to some example embodiments;
[0018] FIG. 6 illustrates a flowchart of a method implemented at a first device according to some example embodiments;
[0019] FIG. 7 illustrates a flowchart of a method implemented at a second device according to some example embodiments;
[0020] FIG. 8 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments; and
[0021] FIG. 9 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments.
[0022] Throughout the drawings, the same or similar reference numerals are intended to represent the same or similar element.DETAILED DESCRIPTION
[0023] Various example embodiments of the subject disclosure are further described. It is to be understood that these example embodiments are described only for the purpose of illustration and to aid those skilled in the art to understand and implement the subject disclosure, without suggesting any specific limitation as to the scope of the subject disclosure. Example embodiments described herein can be implemented in various manners other than the ones described below.
[0024] The terminology used herein is generally provided the purpose of describing particular example embodiments only and is not intended to be limiting. In the following description and claims, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this subject disclosure pertains, unless otherwise defined.
[0025] References in the subject disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” “some example embodiments, ” “certain example embodiments, ” “various example embodiments” and the like indicate that the referenced embodiment (s) described may include particular feature (s) , structure (s) , or characteristic (s) , but it is not necessary that every embodiment or example embodiment described herein includes the particular feature (s) , structure (s) , or characteristic (s) . Moreover, such phrases are not necessarily referring to the same embodiment or same example embodiment. Further, when particular feature (s) , structure (s) , or characteristic (s) are described in connection with an embodiment or example embodiment, it is submitted that it is within the knowledge of one skilled in the art to combine such feature (s) , structure (s) , or characteristic (s) in connection with any other embodiments or example embodiments described herein whether or not such combination is explicitly described.
[0026] It shall be understood that although the terms “first, ” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
[0027] As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.
[0028] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.
[0029] As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and / or “including” , when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.
[0030] As used herein, the term “circuitry” may refer to one or more or all of the following example embodiments:
[0031] (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and
[0032] (b) combinations of hardware circuits and software, such as (as applicable) :
[0033] (i) a combination of analog and / or digital hardware circuit (s) with software / firmware and
[0034] (ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and
[0035] (c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.
[0036] This definition of circuitry applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
[0037] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and / or any other protocols either currently known or to be developed in the future. Example embodiments may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the subject disclosure may be embodied. It should not be seen as limiting the scope to only the aforementioned communication technologies and systems.
[0038] As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.
[0039] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) . As used herein, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.
[0040] As used herein, the term “resource, ” “transmission resource, ” “resource block, ” “physical resource block” (PRB) , “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. A resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments. It is noted that example embodiments are equally applicable to other resources in other domains.
[0041] As used herein, the term “edge computing” used herein may refer to a distributed computing framework that brings enterprise applications closer to data sources such as internet of thing (IoT) devices or local edge servers. The term “edging computing resource” used herein may refer to any resource closer to where data is generated that can be used to process, analyze, and store the data to enable rapid, near real-time analysis and response. The term “edging computing unit” used herein may refer to a device or an entity that can be used in the edge computing.
[0042] As used herein, the term “network resource” used herein may refer to any resource that can be used to route or forward data in a network. For example, the network resource may be a device or an entity that can route or forward the data.
[0043] As used herein, the term “application” or the term “app” used herein may refer to a program that performs a particular task or set of tasks or provide a service for a user. The term “server” used herein may refer to a device designed to process requests and deliver data to another device over an internet or a local network. The terms “server” and “application server” can be used interchangeable hereinafter.
[0044] As mentioned above, networking and edge cloud may be considered parts of a whole E2E solution. Generally, a communication resource can be scheduled in a network domain, whereas a computing resource can also be allocated in a cloud domain. However, in a mobile case with a low latency requirement where relocations of resources happen in both the network and computing domains, these two parts are proposed in some example embodiments to be coordinated and jointly scheduled. For certain use cases, this can result in an enhanced E2E performance, although it may be suboptimal for one or two of the domains. In some example embodiments, there has been edge application server (EAS) (Re-) discovery procedures defined for a session setup to support edge computing. 5G core network (5GC) supports three connectivity models to enable the edge computing, including a distributed anchor connectivity model, a multiple protocol data unit (PDU) sessions connectivity model, and a session breakout connectivity model. A domain name server (DNS) query sent by UE may be handled by an edge application server discovery function (EASDF) or by a local or central DNS resolver / server. For a case when EASDF will be used for terminals initial DNS query for edge application discovery, a local platform security architecture (PSA) may be inserted based on query results. It can be supposed to be a sequential manner since edge computing resources for an application are determined first according to the DNS query, which follows by the network resources by inserting local PSA.
[0045] In addition to EASDF mechanism to locate an application server, some solutions also support to edge relocation procedures supporting EAS changes and / or PSA user plane function (UPF) relocation in scenarios of UE mobility, load balance and maintenance of an EAS. For the PSA UPF relocation, it may be triggered or by the network itself (e.g., due to a UE mobility) or by an application function (AF) request (e.g., due to a load balance between EAS instances) . Besides, the PSA UPF relocation can trigger Application Context Relocation (ACR) , and a decision maker of ACR can be an edge enabler client (EEC) , an edge enabler server (EES) or an EAS. In addition, the ACR can also trigger the PSA relocation by means of application function influence on traffic routing. This kind of coordination is supposed to be a peer-to-peer collaboration, sequentially instead of jointly. The above procedures of edge discovery and relocation can in terms of the E2E performance and even induce more latency if more iterations are required in some use cases. Therefore, some example embodiments for determining edge computing and network resources are herein proposed.
[0046] Example Environment
[0047] FIG. 1 illustrates an example communication environment 100 in which example embodiments can be implemented. The communication environment 100 includes a first device 110, a second device 120, a third device 130, and a fourth device 140. It is noted that even though FIG. 1 only shows one first device, one second device, one third device and one fourth device, the communication environment 100 may include any suitable number of devices.
[0048] In an example embodiment, the first device 110 may be a network control plane unit in a control plane 101. For example, the first device 110 may include: an access and mobility management function (AMF) , a session management function (SMF) , a unified data repository (UDR) , a network exposure function (NEF) , and / or a policy control function (PCF) . The first device 110 may include a control plane function in a radio access network (RAN) (such as, RAN-central unit control plane (CU-CP) ) . Alternatively, the first device 110 can also include an entity that can implement a new defined function specifically to realize embodiments described herein. In addition, the second device 120 may be a terminal device. In some example embodiments, the third device 130 may be an edge computing unit that can provide an edging computing resource. The fourth device 140 may be a network user plane unit in a user plane 102. For example, the fourth device 140 may be a user plane function (UPF) . Alternatively, the fourth device 140 may be a user plane function in the RAN, such as, RAN-central unit user plane (CU-UP) . Alternatively, the fourth device 140 can also include an entity that can implement a new defined function specifically to realize embodiments described herein. In some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device. The second device 120 can communicate with the first device 110 in the control plane 101 and the fourth device 140 in the user plane 102. Further, the first device 110 and the fourth device 140 can communicate with each other, and the fourth device 140 and the third device 130 can communicate with each other. In addition, the second device 120 and the fourth device 140 can also communicate with each other, and the first device 110 and the third device 130 can communicate with each other.
[0049] In some example embodiments, a link from a network device to a terminal device is referred to as a downlink (DL) , and a link from the terminal device to the network device is referred to as an uplink (UL) . In DL, the network device is a transmitting (TX) device (or a transmitter) , and the terminal device is a receiving (RX) device (or a receiver) . In UL, the terminal device is a TX device (or a transmitter) , and the network device is a RX device (or a receiver) .
[0050] Communications in the communication environment 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) , the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.
[0051] An edge application may include a user-side application client and an edge application server. For example, the user-side application client may be at the second device 120 and the edge application server may be at the third device 130. The edge application may have many requirements to the network and edge computing unit in terms of latency, bandwidth, hardware acceleration and so forth. In addition, user mobility requires that both the network and the edge computing unit to support service continuity. In such a case, the determination of network and computing resources may combine many factors, such as a user’s location, network status, a computing power of the edge computing unit, and a load status of the application server to select an appropriate user plane transmission path and an edge computing unit to satisfy application requirements.
[0052] Example Signaling for Communication
[0053] According to some example embodiments, there is provided an enhancement for determining edge computing and network resources. The second device transmits an application identity associated with an application to the first device. The first device determines the edge computing resource and the network resource based on the application identity, location information of the second device, edge computing resource information, and network status information. The second device receives access information regarding a server of the application. For certain uses cases, it is conductive to overall management of network and computing resources and an enhanced allocation of resources.
[0054] Reference is now made to FIG. 2, which shows a signaling chart 200 for communication according to some example embodiments of the subject disclosure. As shown in FIG. 2, the signaling chart 200 involves the first device 110, the second device 120, the third device 130 and the fourth device 140.
[0055] In some example embodiments, before a user initiates a service request to a network, the application client may transmit an application identity to the user. For example, the application client may inform the application identity to the second device 120.
[0056] The second device 120 transmits (2005) an application identity of the application to the first device 110. The first device 110 receives the application identity from the second device 120. In some example embodiments, the application identity may be an application client identity (ACID) associated with the application. Alternatively, the application identity may be an application server identity (ASID) associated with the application. In some embodiments, the ACID may be a string or a number. Alternatively, or in addition, the ASID may be a string or a number.
[0057] In an example embodiment, the second device 120 may transmit a service request that includes the application identity to the first device 110. By way of example, information reported during user’s service request process may include the application identity. For example, if the second device 120 initiates a service request, the application identity may be included in the service request sent to the first device 110. In some example embodiments, the service request may also include a network slice identity associated with the application. The network slice identity may indicate a network slice that can support a service of the application. For example, the network slice identity may be single network slice selection assistance information (S-NSSAI) that is used to uniquely identify a network slice. The S-NSSAI may include a slice / service type which refers to an expected network slice behavior in terms of features and services and a slice differentiator which is optional information that complements the slice / service type to differentiate among multiple network slices of the same slice / service type. Alternatively, or in addition, the service request may include a data network name (DNN) associated with the application.
[0058] In another example embodiment, if the second device 120 moves from a source cell to a target cell, the second device 120 may transmit a measurement report of the target cell as well as the application identity to the first device 110. During a change of serving fourth device, the application identity may be transmitted from the second device 120 to the first device 110. In some example embodiments, the measurement report may include a cell identity of the target cell. The measurement report may include any proper measurement metric, for example, reference signal received power (RSRP) . In some embodiments, the measurement report and the application identity may be transmitted separately. Alternatively, the application identity and the measurement report may be transmitted together.
[0059] In some example embodiments, the first device 110 may obtain network status information. For example, the first device 110 may receive the network status information from another first device (e.g., a different network control plane unit) . Alternatively, or in addition, the fourth device 140 may transmit (2010) the network status information to the first device 110. The first device 110 may receive the network status information from the fourth device 140. In an example embodiment, the network status information may include a location area served by the fourth device 140. For example, the network status information may include a cell identity associated with the location area served by the fourth device 140. Alternatively, the network status information may include a tracking area identity (TAI) . In some example embodiments, the network status information may include latitude and longitude information of the location area served by the fourth device 140. The network status information may include topology information of the fourth device 140. In some embodiments, the above-mentioned network status information may be provided by the different network control plane unit. In some example embodiments, the network status information may include latency and bandwidth information between fourth devices. Alternatively, or in addition, the network status information may include latency and bandwidth information between the fourth device 140 and the third device 130. In some example embodiments, the network status information may include routing information from the fourth device 140 to the third device 130. For example, the routing information may include a data network access identifier (DNAI) of the third device 130.
[0060] The third device 130 may transmit (2015) edge computing resource information to the first device 110. The first device 110 may receive the edge computing resource information from the third device 130. It is noted that order of the steps 2010 and 2015 shown in FIG. 2 is only an example not a limitation. It is noted that the edge computing resource information may be received / transmitted before a reception or transmission of the network status information.
[0061] In an example embodiment, the edge computing resource information may include information (referred to as “first information” ) regarding a server of the application located on the third device 130. For example, the first information may include an identity of the server (such as, ASID) . Alternatively, or in addition, the first information may include a load status of the server. For example, the load status of the server may indicate the amount or percentage of computing power of the server which is consumed. By way of example, the load status of the server may include one of “idle” , “busy” or “overloaded. ”
[0062] In some example embodiments, the first information may include link or routing information of the server. For example, the link or routing information may include and internet protocol (IP) address of the server. Alternatively, or in addition, the link or routing information may include a fully qualified domain name (FQDN) of the server. The term “FQDN” used herein may refer to a domain name that is written with a hostname and a domain name, including a top-level domain, in that order: [hostname] . [domain] . [tId] .
[0063] In some example embodiments, the first information may include service area and service continuity information of the server. For example, the service area and service continuity information may indicate an area where the server can provide services, such as, a cell. It is noted that the first information may also include other information related to the server on third device 130.
[0064] Alternatively, or in addition, the edge computing resource information may include information (referred to as “second information” ) regarding the third device 130. For example, the second information may include routing information to the third device 130. Alternatively, or in addition, the second information may include a supported service area of the third device 130 (e.g., an area covered by a cell) . The second information may also include resource utilization information of the third device 130. For example, the resource utilization information may indicate the amount or percentage of computing power of the third device 130 which are utilized. In some example embodiments, the second information may include platform information (e.g., a hardware acceleration capability of the third device 130) . The hardware acceleration capability may include one or more of: a graph processing unit (GPU) , a field programmable gate array (FPGA) , or an application specific integrated circuit (ASIC) . It is noted that the second information may also include other information related to the third device 130.
[0065] The second device 120 may transmit (2020) preference information of the application to the first device 110. The preference information may filter out an application server instance expected by the application client on the second device 120. For example, the preference information may include application provider information. Alternatively, or in addition, the preference information may include edge computing service provider information. In some example embodiments, the preference information may include a preferred vendor.
[0066] The first device 110 may obtain location information of the second device 120. Alternatively, the second device 120 may report its current location information during the service request process for the application. In an example embodiment, the location information may be geographic latitude and longitude information of the second device 120. In another example embodiment, the location information may include indirect location information of the second device 120. For example, the location information may include a TAI of an area where the second device 120 locates. As another example, the location information may include a cell identity of a cell where the second device 120 locates.
[0067] In some example embodiments, the first device 110 may be configured to determine (2025) an edge computing resource and a network resource for the application either sequentially or jointly. The first device 110 determines (2025) the edge computing resource and the network resource for the application based on the application identity, the edge computing resource information, and the network status information. In some example embodiments, the first device 110 may be configured to trigger a joint determination based on the application identity. However, even with the application identity, the first device 110 could instead perform a sequential determination for certain use cases. The first device 110 may be configured to determine one or more optimization criteria with reduced iteration, based on the application identity (e.g., targeted computing resource (s) , targeted QoS (s) , etc. ) . A joint determination by the first device 110 may include the selection of a pair (e.g., a node, an attribute value pair (AVP) , a solution vector, and so forth) that includes both a computing resource and a network resource. In more detail, the selected pair may, for example, be selected by the first device 110 from a search space that includes plurality of pair candidates, where each pair candidate includes a respective candidate computing resource and a respective candidate network resource. With the application identity, the edge computing resource information, and the network status information, it is possible to jointly determine a computing resource and a network resource with enhanced performance over a sequential determination. Thus, the first device 110 may perform an overall management of network and computing resources. In some example embodiments, the first device 110 can organically integrate a discovery of an application server at the edge computing unit and an establishment process of network connection. Accordingly, an enhanced allocation of resources can be achieved.
[0068] In some example embodiments, the first device 110 may determine a data transmission path of the application. For example, the data transmission path may include one or more fourth devices. Alternatively, or in addition, the first device 110 may determine access information to access the sever of the application. The access information may indicate how to access the server of the application. For example, the access information may include an identity of the server (such as, ASID) . Alternatively, or in addition, the access information may include address information (such as IP, FQDN, etc. ) , a domain name system (DNS) server of the server. In some example embodiments, the first device 110 may also determine information of the third device 130 where the server of the application is located.
[0069] The first device 110 may transmit (2030) one or more of: a user context of the second device 120 or routing information to the third device 130 to the fourth device 140. For example, the user context of the second device 120 may transmitted to the fourth device 140 to establish a data transmission path. In an example embodiment, the user context may include name-value pairs that describe a client connected to the server. It is noted that the user context may include any relevant information that can be used to characterize a situation of the second device 120.
[0070] The first device 110 may transmit (2035) access information regarding the server to the second device 120. For example, the access information may include the identity of the server. Alternatively, or in addition, the access information may include address information (such as IP, FQDN, etc. ) , and / or the DNS server of the server. In some example embodiments, the access information may also include other information of the sever. The second device 120 can thus realize the application client’s access to the server.
[0071] In some example embodiments, after the application on the second device 120 completes an interaction with the server on the third device 130, the application may indicate that the service is over. In some example embodiments, the second device 120 may transmit (2040) a resource release request to the first device 110. Alternatively, the third device 130 may transmit (2042) the resource release request to the first device 110. The resource release request may include the application identity of the application.
[0072] As mentioned above, if the second device 120 moves from a source cell to a target cell, the second device 120 may transmit the application identity to the first device 110. In this case, the first device 110 may determine (2045) a further data transmission path of the application. For example, the further data transmission path may include a further fourth device. Alternatively, or in addition, the further data transmission path may include a further third device associated with the target cell. In some other example embodiments, the further data transmission path may also include a further server of the application on the further third device.
[0073] The first device 110 may transmit (2050) a reconfiguration information to the fourth device 140. Alternatively, or in addition, the first device 110 may transmit the reconfiguration information to the further fourth device. In some example embodiments, the reconfiguration information may include one or more of: the user context of the second device and further routing information to the further third device. In an example embodiment, the user context may include name-value pairs that describe a client connected to the server. It is noted that the user context may include any relevant information that can be used to characterize a situation of the second device 120.
[0074] The first device 110 may transmit (2055) a context relocation message to the server on the third device 130. In some example embodiments, the context relocation message may include one or more of link or routing information to the further server, routing information to the further third device, a DNS server of the further server, or service area and service continuity information of the further server.
[0075] The first device 110 may transmit (2060) further access information to the second device 120. The further access information may include one or more of: an identity of the further server, address information of the further server, or the DNS server of the further server. The identity of the further server may be an ASID of the further sever. In some example embodiments, the access information may also include other information of the further sever. In some example embodiments, the second device 120 can thus realize the application client’s access to the further server.
[0076] The first device 110 may store (2065) the edge computing resource information and the network status information. In some example embodiments, the edge computing resource information and the network status information may be partially stored. Alternatively, the edge computing resource information and the network status information may be fully stored. The edge computing resource information and the network status information may be stored in the control plane in a separate data unit, for example, UDR, or other control plane units. It is noted that storing (2065) the edge computing resource information and the network status information may be performed in a proper order that may be different from that shown in FIG. 2. For example, the edge computing resource information and the network status information may be stored before receiving the preference information from the second device 120.
[0077] According to example embodiments described with the reference to FIG. 2, it can organically integrate the discovery of the application server at the edge computing unit and the establishment process of network connection. It is conducive to the overall management of network and computing resources and the enhanced allocation of resources. Either mobility or load balancing of application servers may trigger a joint reconfiguration of the network user plane and the edge computing unit. Especially when both the data transmission path reconfiguration and application context relocation are triggered, example embodiments are conducive to reduce the delay of the whole reconfiguration process, and in some use cases to avoid the iterative process to treat data transmission path reconfiguration and application context relocation sequentially.
[0078] As discussed above, initiating a service request and / or user's mobility may trigger the reconfiguration of user plane data path and the application context relocation of application server at edge computing unit. Example embodiments of the above cases will be described in detail below with reference to the accompanying drawings.
[0079] FIG. 3 illustrates an example of the communication environment 100 shown in FIG. 1 according to some example embodiments. As shown in FIG. 3, a communication environment 300 may include a network control plane unit 310. The network control plane unit 310 may be an example the first device 110 shown in FIG. 1. The network control plane unit 310 may include one or more of: AMF 3101, SMF 3102, RAN-CU-CP 3103, PCF 3104, UDR 3105, NEF 3106, or new defined specific network control functions. The communication environment 100 may also include a terminal device 320 on which an APP X is installed.
[0080] The communication environment 300 may include one or more network user plane units, for example, a network user plane unit 340-1, a network user plane unit 340-2, a network user plane unit 340-3 and a network user plane unit 340-4. The network user plane unit may be an example of the fourth device 140 in FIG. 1. The network user plane unit may be one of: a UPF or a RAN CU-UP.
[0081] As shown in FIG. 3, the communication environment 300 may also include one or more edge computing units (e.g., an edge computing unit 330-1 and an edge computing unit 330-2) . The edge computing unit may be an example of the third device 130 as shown in FIG. 1. There may be a server 350-1 of the APP X on the edge computing unit 330-1 and a server 350-2 of the APP X on the edge computing unit 330-2.
[0082] Further, the communication environment 300 may include one or more network device, for example, a network device 370-1 that provides a cell 360-1 and a network device 370-2 that provides a cell 360-2. By way of example, a service area of the edge computing unit 330-1 may be the cell 360-1 and a service area of the edge computing unit 330-2 may be the cell 360-2. The communication environment 300 may also include a DNN server 380. It is noted that the number of devices / units shown in FIG. 3 is only an example not limitations.
[0083] FIG. 4 illustrates a signaling chart 400 for determining the edge computing resource and the network resource during an initiation procedure according to some example embodiments. The signaling chart 400 is described with reference to FIG. 3. As shown in FIG. 4, the signaling chart 400 may involve a device 410, a device 420, a device 430, a device 440, a device 450 and a device 460. The device 410 may be the terminal device 320 shown in FIG. 3. The device 420 may include: the RAN CU-CP 3103, the SMF 3102, the PCF 3104, the AMF 3101, and / or a newly defined specific network control functions. The device 430 may include: the UDR 3105 and / or the UDM. The device 440 may be the network user plane unit, for example, may include: the network user plane unit 340-1, the network user plane unit 340-2, the network user plane unit 340-3 and / or the network user plane unit 340-4. The device 450 may be the NEF 3106. The device 460 may be the edge computing unit (e.g., the edge computing unit 330-1 or the edge computing unit 330-2) .
[0084] As shown in FIG. 4, after the edge computing unit 460 (e.g., the edge computing unit 330-1 or 330-2) goes live, information of the edge computing unit 460 may be updated (4001) to a network side through the device 450. The information may include one or more of: routing information to the edge computing unit 460 (e.g., the DNAI of the server 350-1 or the DNAI of the server 350-2) , resource utilization information of the edge computing unit 460, or a platform capability of the edge computing unit 460. The platform capability may be a hardware acceleration capability (such as, GPU, FPGA, or ASIC) .
[0085] After the server (e.g., the server 350-1 or the server 350-2) identified by its application identity is instantiated and deployed in the edge computing unit 460, related information of a server may be updated (4002) to the network side through the device 450. For example, the related information includes the identity of the server, its load status, its address information (such as IP, FQDN, etc. ) , its service area supported and / or service continuity information (and the like) .
[0086] In some example embodiments, the information of the edge computing unit 460 and the related information of the server may be periodically updated (4003) to the network side. Alternatively, the information of the edge computing unit 460 and the related information of the server may be updated (4003) to the network side on demand.
[0087] The device 440 may transmit (4004) the network status information to the device 420. For example, the device 420 may check the network status information. The network status information may include one or more of: a location area (e.g., CellID, TAI, or latitude and longitude information) served by the device 440, network topology information of the device 440, the latency and bandwidth information between the network user plane units (e.g., between any two of: the network user plane unit 340-1, the network user plane unit 340-2, the network user plane unit 340-3 or the network user plane unit 340-4) , and the latency and bandwidth information between the device 440 and the device and the device 460, or the routing information to the device 460 (e.g., DNAI1, DNAI2) . The device 450 may transmit (4005) the information related to the edge computing unit 460 and the server to the device 430 for storage.
[0088] If there is a request for APP X to access the server 350-1, the application client on the device 410 may deliver (4006) the ACID or ASID to the device 410. The device 410 may transmit (4007) the ACID or ASID to the device 420. The device 410 may also report its current location information to the network during the service request process, which can be based on geographic latitude and longitude information or can be indirect location information, such as network location identification (e.g., TAI, Cell ID, and the like) . In addition to the current location information, the device 410 can also report basic logical network information. The device 410 can also transmit other information including slice identification (S-NSSAI) , DNN, some preferences to the device 420. The preferences can be information on application provider or edge computing service provider to filters out the server instances expected by the client.
[0089] The device 420 may query (4008) the user’s subscription information, and the relevant status information of the server 350-1 and its host edge computing unit 330-1 to the device 430. The device 430 may transmit (4009) a query response that includes the user’s subscription information, and the relevant status information of the server 350-1 and its host edge computing unit 330-1.
[0090] Based on the queried (4008) information, S-NSSAI, DNN, user position, App X’s requirements in latency, bandwidth, mobility, and service continuity, and the network status information, the device 420 can determine (4010) a network transmission path (e.g., the network user plane unit 340-1 the network user plane unit 340-2 the edge computing unit 330-1 the server 350-1) .
[0091] The device 420 may transmit (4011) the user's context to the device 440 that may be the network user plane unit 340-1 and / or the network user plane unit 340-2 in the determined data transmission path to establish a data transmission channel, and also transmit (4011) the routing information DNAI1 of the edge computing unit edge 330-1 containing the server 350-1 to the device 440. The device 440 may transmit (4012) a configuration response to the device 420.
[0092] The device 420 may transmit (4013) the application identity of the server 350-1, the address information of the server 350-1 (such as IP, FQDN, and the like) , a DNS server of the server 350-1 and other information to the device 410. The device 410 may reply (4014) to the device 420 to confirm that the entire process is completed. A data transmission path including the device 410, the device 440 and the device 460 may be established (4015) . APP X on the device 410 can thus, in some example embodiments, access the server 350-1.
[0093] If the APP X completes the interaction with the server instance in the device 460, the APP X may indicate to the device 410 that the service is over. The device 410 may transmit (4016) a resource release request to the device 420, and the request information may carry the ASID or ACID.
[0094] Alternatively, if the APP X completes the interaction with the server instance in the device 460, the server on the device 460 may transmit (4017) a resource release request towards the device 420 and the request information may carry the ASID or ACID. The device 420 may instruct (4018) related node such as the device 440 and the device 460 to release resources.
[0095] FIG. 5 illustrates a signaling chart 500 for determining the edge computing resource and the network resource during a handover procedure according to some example embodiments. The signaling chart 500 is described with reference to FIG. 3. As shown in FIG. 5, the signaling chart 500 may involve a device 510, a device 520, a device 530, a device 540, a device 550, a device 560, a device 570 and a device 580. The device 510 may be the terminal device 320 shown in FIG. 3. The device 520 may include: the RAN CU-CP 3103, the SMF 3102, the PCF 3104 the AMF 3101, and / or new defined specific network control functions. The device 530 may include: the UDR 3105 and / or the UDM. The device 540 may be the network user plane unit (e.g., the network user plane unit 340-2) . The device 550 may be another network user plane unit (e.g., the network user plane unit 340-3) . The device 560 may be the NEF 3106. The device 570 may be the edge computing unit (e.g., the edge computing unit 330-1) . The device 580 may be another edge computing unit (e.g., the edge computing unit 330-2) .
[0096] The data transmission path including the device 510, the device 540 and the device 570 may be established (5001) . The status information of the devices 570 and 580 and servers on the devices 570 and 580 may be updated (5002) (e.g., periodically updated) . The status information of the devices 540 and 550 may be updated (5003) (e.g., periodically updated) .
[0097] When the App X is still communicating with the server 350-1 in the device 570, the device 510 may move from the current cell 360-1 with Cell ID 1 to the adjacent cell 360-2 with Cell ID2. During this move, the device 510 may transmit (5004) at least one of: a measurement report of wireless signal from the adjacent cell 360-2 with Cell ID2, the cell identity of cell ID2, or the application identity (ACID or ASID) to the device 520.
[0098] The device 520 may query (5005) relevant status information of App X server according to ACID or ASID, and the devices 570 and 580 to the device 530. The device 530 may transmit (5006) a query response that includes the relevant status information.
[0099] Based on the relevant status information, S-NSSAI, DNN, user position, App X’s requirements in latency, bandwidth, mobility, and service continuity, and network status information, the device 520 can determine (5007) a data transmission path including the network user plane unit 340-1 the network user plane unit 340-3 the edge computing unit 330-2 App X Server. The device 550 (e.g., the network user plane unit 340-3) may be a target user plane unit to be inserted, the device 580 (e.g., the edge computing unit 330-2) may be a target edge computing unit to host the target application App X server instance.
[0100] According to the determined data transmission path, the device 520 may transmit (5008) reconfiguration information to the device 540 and the device 550. The reconfiguration information may include user-related context information and routing information to the device 580.
[0101] According to the determined data transmission path, the device 520 may transmit (5010) an application context relocation command to the server 350-1 in the device 570. The application context relocation command may include link or routing information to the server 350-2 in the device 580 (such as IP, FQDN, etc. ) , its DNAI, DNS server, and service continuity information.
[0102] The device 520 may forward (5012) a handover acknowledgement command to the device 510. The handover acknowledgement command may include information on the server 350-2 instance in the device 580 including the server identity, the address information (such as IP address, FQDN, etc. ) , DNS server and etc. The device 510 may reply (5013) to the device 520 to confirm that the handover process is completed. A data transmission path including the device 510, the device 5500 and the device 580 may be established (5014) .
[0103] Example Methods
[0104] FIG. 6 shows a flowchart of an example method 600 implemented at a first device in accordance with some example embodiments. For the purpose of discussion, the method 600 will be described from the perspective of the first device 110 in FIG. 1.
[0105] At block 610, the first device 110 receives from the second device 120, an application identity associated with an application. In some example embodiments, the application identity may be an application client identity (ACID) associated with the application. Alternatively, the application identity may be an application server identity (ASID) associated with the application.
[0106] At block 620, the first device 110 determines an edge computing resource and a network resource for the application based on the application identity, edge computing resource information, and network status information. In some example embodiments, the first device 110 may receive from a third device 130, the edge computing resource information. The first device 110 may also receive from a fourth device 140, the network status information.
[0107] In some example embodiments, the edge computing resource information comprises at least one of: first information regarding a server of the application located on the third device; or second information regarding the third device.
[0108] In some example embodiments, the first information comprises at least one of: an identity of the server, a load status of the server, link or routing information to the server, or service area and service continuity information of the server. In some example embodiments, the second information comprises: routing information to the third device, a supported service area of the third device, resource utilization of the third device, or a hardware acceleration capability of the third device.
[0109] In some example embodiments, the network status information comprises at least one of: a location area served by the fourth device, topology information of the fourth device, latency and bandwidth information between fourth devices, further latency and bandwidth information between the fourth device and the third device, or routing information from the fourth device to the third device.
[0110] In some example embodiments, the first device 110 may receive from the second device 120, preference information of the application. In some example embodiments, the preference information comprises at least one of: application provider information of the application, or edge computing service provider information of the application.
[0111] In some example embodiments, the first device 110 may determine at least one of: a data transmission path of the application, or access information to access the server of the application.
[0112] In some example embodiments, the first device 110 may transmit to the fourth device 140, at least one of: a user context of the second device and the routing information to the third device to establish the data transmission path. In some example embodiments, the first device 110 may transmit to the second device 120, access information of the server on the third device. The access information may include at least one of: the identity of the server, address information of the server, or a domain name system server.
[0113] In some example embodiments, the first device 110 may receive from the second device 120, a service request comprising the application identity. The service request may further include at least one of: a network slice identity associated with the application, or a data network name associated with the application.
[0114] In some example embodiments, the first device 110 may receive from the second device 120, a resource release request that comprises the application identity. Alternatively, the first device 110 may receive from the third device 130, the resource release request that comprises the application identity.
[0115] In some example embodiments, the first device 110 may receive from the second device, the application identity during a change of serving fourth device.
[0116] In some example embodiments, the instructions, the first device 110 may determine a further data transmission path of the application. The further data transmission path may at least include: a further fourth device, a further third device associated with the target cell, or a further sever of the application on the further third device.
[0117] In some example embodiments, the first device 110 may transmit to the fourth device 140, reconfiguration information. The first device 110 may transmit to the further fourth device, the reconfiguration information. The reconfiguration information may include at least one of: a user context of the second device and further routing information to the further third device.
[0118] In some example embodiments, the first device 110 may transmit to the server on the third device 130, a context relocation message. The context relocation message may include at least one of: link or routing information to the further server, routing information to the further third device, a domain name system server of the further server, or service area and service continuity information of the further server. In some example embodiments, the first device 110 may transmit to the second device 120, at least one of: an identity of the further server, address information of the further server, or the domain name system server of the further server. In some example embodiments, the first device 110 may store the edge computing resource information and the network status information.
[0119] In some example embodiments, the first device comprises a network control plane unit, the second device comprises a terminal device, the third device comprises an edge computing unit, the fourth device comprises a network user plane unit.
[0120] In some example embodiments, the network control plane unit may include: a core network control plane unit, an access network control plane unit, and / or an entity that implements a control plane function. In some example embodiments, the network user plane unit may include: a core network user plane unit, an access network user plane unit, and / or an entity that implements a user plane function.
[0121] FIG. 7 shows a flowchart of an example method 700 implemented at a second device in accordance with some example embodiments. For the purpose of discussion, the method 700 will be described from the perspective of the second device 120 in FIG. 1.
[0122] At block 710, the second device 120 transmits to a first device 110, an application identity associated with an application. In some example embodiments, the application identity may be an application client identity (ACID) associated with the application. Alternatively, the application identity may be an application server identity (ASID) associated with the application.
[0123] At block 720, the second device 120 receives from the first device 110, access information of a sever of the application on a third device. The access information is determined based on the application identity, edge computing resource information, and network status. In some example embodiments, the edge computing resource information comprises at least one of: first information regarding a server of the application located on a third device, or second information regarding the third device.
[0124] In some example embodiments, the first information comprises at least one of: an identity of the server, a load status of the server, link or routing information to the server, or service area and service continuity information of the server. In some example embodiments, the second information comprises: routing information to the third device, a supported service area of the third device, resource utilization of the third device, or a hardware acceleration capability of the third device. In some example embodiments, the network status information comprises at least one of: a location area served by a fourth device, topology information of the fourth device, latency and bandwidth information between fourth devices, further latency and bandwidth information between the fourth device and the third device, or routing information from the fourth device to the third device.
[0125] In some example embodiments, the second device 120 may transmit to the first device 110, preference information of the application. In some example embodiments, the preference information comprises at least one of: application provider information of the application, or edge computing service provider information of the application.
[0126] In some example embodiments, the access information comprises at least one of: an identity of the server located on the third device, address information of the server, or a domain name system server of the server.
[0127] In some example embodiments, the second device 120 may transmit to the first device 110, a service request comprising the application identity. The service request may further include at least one of: a network slice identity associated with the application, or a data network name associated with the application. In some example embodiments, the second device 120 may transmit to the first device 110, a resource release request that comprises the application identity.
[0128] In some example embodiments, the second device 120 may transmit to the first device 110, the application identity during a change of serving fourth device.
[0129] In some example embodiments, the second device 120 may receive from the first device 110, at least one of: an identity of a further server on a further third device, address information of the further server, or a domain name system server of the further server.
[0130] In some example embodiments, the first device comprises a network control plane unit, the second device comprises a terminal device, the third device comprises an edge computing unit, the fourth device comprises a network user plane unit. In some example embodiments, the network control plane unit is one of: a core network control plane unit, an access network control plane unit, or an entity that implements a control plane function. In some example embodiments, the network user plane unit is one of: a core network user plane unit, an access network user plane unit, or an entity that implements a user plane function.
[0131] Example Apparatus, Device and Medium
[0132] In some example embodiments, a first apparatus capable of performing (e.g., configured to perform) any of the method 600 (e.g., the first device 110 in FIG. 1) may comprise means for performing the respective operations of the method 600. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first device 110 in FIG. 1.
[0133] In some example embodiments, the first apparatus comprises means for receiving, from a second device, an application identity associated with an application; and means for determining an edge computing resource and a network resource for the application based on the application identity, location information of the second device, edge computing resource information, and network status information.
[0134] In some example embodiments, the first apparatus comprises means for receiving, from a third device, the edge computing resource information; and means for receiving, from a fourth device, the network status information.
[0135] In some example embodiments, the edge computing resource information comprises at least one of: first information regarding a server of the application located on the third device; or second information regarding the third device.
[0136] In some example embodiments, the first information comprises at least one of: an identity of the server, a load status of the server, link or routing information to the server, or service area and service continuity information of the server, and wherein the second information comprises: means for routing information to the third device, a supported service area of the third device, resource utilization of the third device, or a hardware acceleration capability of the third device.
[0137] In some example embodiments, the network status information comprises at least one of: a location area served by the fourth device, topology information of the fourth device, latency and bandwidth information between fourth devices, further latency and bandwidth information between the fourth device and the third device or routing information from the fourth device to the third device.
[0138] In some example embodiments, the first apparatus means for receiving, from the second device, preference information of the application.
[0139] In some example embodiments, the preference information comprises at least one of: application provider information of the application, or edge computing service provider information of the application.
[0140] In some example embodiments, the first apparatus means for determining at least one of: a data transmission path of the application, access information to access the server of the application, or third information of the third device where the server of the application locates.
[0141] In some example embodiments, the first apparatus means for transmitting, to the fourth device, at least one of: a user context of the second device and the routing information to the third device to establish the data transmission path.
[0142] In some example embodiments, the first apparatus means for transmitting, to the second device, access information of the server on the third device, wherein the access information comprises at least one of: the identity of the server, the address information of the server, or a domain name system server.
[0143] In some example embodiments, the first apparatus means for receiving, from the second device, a service request comprising the application identity, and wherein the service request further comprises at least one of: a network slice identity associated with the application, or a data network name associated with the application.
[0144] In some example embodiments, the first apparatus means for receiving, from the second device, a resource release request that comprises the application identity; or means for receiving, from the third device, the resource release request that comprises the application identity.
[0145] In some example embodiments, the first apparatus means for receiving, from the second device, a measurement report of a target cell comprising the application identity, and wherein the measurement report further comprises a cell identity of the target cell.
[0146] In some example embodiments, the first apparatus means for determining a further data transmission path of the application, wherein the further data transmission path at least comprises: a further fourth device, a further third device associated with the target cell, or a further sever of the application on the further third device.
[0147] In some example embodiments, the first apparatus means for transmitting, to the fourth device, reconfiguration information; and means for transmitting, to the further fourth device, the reconfiguration information, and wherein the reconfiguration information comprises at least one of: a user context of the second device and further routing information to the further third device.
[0148] In some example embodiments, the first apparatus means for transmitting, to the server on the third device, a context relocation message, and wherein the context relocation message comprises at least one of: link or routing information to the further server, routing information to the further third device, a domain name system server of the further server, or service area and service continuity information of the further server.
[0149] In some example embodiments, the first apparatus means for transmitting, to the second device, at least one of: an identity of the further server, address information of the further server, or the domain name system server of the further server.
[0150] In some example embodiments, the first apparatus means for storing the edge computing resource information and the network status information.
[0151] In some example embodiments, the first device comprises a network control plane unit, the second device comprises a terminal device, the third device comprises an edge computing unit, the fourth device comprises a network user plane unit.
[0152] In some example embodiments, the first apparatus further comprises means for performing other operations in some example embodiments of the method 600 or the first device 110. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the first apparatus.
[0153] In some example embodiments, a second apparatus capable of performing (e.g., configured to perform) any of the method 700 (e.g., the second device 120 in FIG. 1) may comprise means for performing the respective operations of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second device 120 in FIG. 1.
[0154] In some example embodiments, the second apparatus comprises means for transmitting, to a first device, an application identity associated with an application; and means for receiving, from the first device, access information of a sever of the application on a third device, and wherein access information is determined based on the application identity, location information of the second device, edge computing resource information, and network status.
[0155] In some example embodiments, the edge computing resource information comprises at least one of: first information regarding a server of the application located on a third device; or second information regarding the third device.
[0156] In some example embodiments, the first information comprises at least one of: an identity of the server, a load status of the server, link or routing information to the server, or service area and service continuity information of the server, and wherein the second information comprises: means for routing information to the third device, a supported service area of the third device, resource utilization of the third device, or a hardware acceleration capability of the third device.
[0157] In some example embodiments, the network status information comprises at least one of: a location area served by a fourth device, topology information of the fourth device, latency and bandwidth information between fourth devisees, further latency and bandwidth information between the fourth device and the third device or routing information from the fourth device to the third device.
[0158] In some example embodiments, the second apparatus comprises means for transmitting, to the first device, preference information of the application.
[0159] In some example embodiments, the preference information comprises at least one of: application provider information of the application, or edge computing service provider information of the application.
[0160] In some example embodiments, the access information comprises at least one of: an identity of the server located on the third device, address information of the server, or a domain name system server of the server.
[0161] In some example embodiments, the second apparatus comprises means for transmitting, to the first device, a service request comprising the application identity, and wherein the service request further comprises at least one of: a network slice identity associated with the application, or a data network name associated with the application.
[0162] In some example embodiments, the second apparatus comprises means for transmitting, to the first device, a resource release request that comprises the application identity.
[0163] In some example embodiments, the second apparatus comprises means for transmitting, to the first device, a measurement report of a target cell comprising the application identity, and wherein the measurement report further comprises a cell identity of the target cell.
[0164] In some example embodiments, the second apparatus comprises means for receiving, from the first device, at least one of: an identity of a further server on a further third device, address information of the further server, or a domain name system server of the further server.
[0165] In some example embodiments, the first device comprises a network control plane unit, the second device comprises a terminal device, the third device comprises an edge computing unit, the fourth device comprises a network user plane unit.
[0166] In some example embodiments, the second apparatus further comprises means for performing other operations in some example embodiments of the method 700 or the second device 120. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the second apparatus.
[0167] FIG. 8 is a simplified block diagram of a device 800 that may implement one or more example embodiments described herein. The device 800 may be provided to implement a communication device, for example, the first device 110 or the second device 120 as shown in FIG. 1. As shown, the device 800 includes one or more processors 810, one or more memories 820 coupled to the processor 810, and one or more communication modules 840 coupled to the processor 810.
[0168] The communication module 840 is for bidirectional communications. The communication module 840 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is utilized for communication with other network elements. In some example embodiments, the communication module 840 may include at least one antenna.
[0169] The processor 810 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
[0170] The memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 824, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a random-access memory (RAM) 822 and other volatile memories that will not last in the power-down duration.
[0171] A computer program 830 includes computer executable instructions that are executed by the associated processor 810. The instructions of the program 830 may include instructions for performing operations / acts of some example embodiments. The program 830 may be stored in the memory, e.g., the ROM 824. The processor 810 may perform any suitable actions and processing by loading the program 830 into the RAM 822.
[0172] The example embodiments may be implemented by means of the program 830 so that the device 800 may perform any process of the disclosure as discussed with reference to FIG. 2 to FIG. 7. The example embodiments may also be implemented by hardware or by a combination of software and hardware.
[0173] In some example embodiments, the program 830 may be tangibly contained in a computer readable medium which may be included in the device 800 (such as in the memory 820) or other storage devices that are accessible by the device 800. The device 800 may load the program 830 from the computer readable medium to the RAM 822 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
[0174] FIG. 9 shows an example of the computer readable medium 900 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 900 has the program 830 stored thereon.
[0175] Various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Even though various aspects of embodiments are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
[0176] Some example embodiments also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Program modules may include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
[0177] Program code for carrying out methods may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
[0178] In the context, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.
[0179] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0180] Further, even though operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, even though several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope, but rather as descriptions of features that may be specific to particular example embodiments. Unless explicitly stated, certain features that are described in the context of separate example embodiments may also be implemented in combination in a single example embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single example embodiment may also be implemented in a plurality of example embodiments separately or in any suitable sub-combination.
[0181] Although various example embodiments of the subject disclosure has been described in language specific to structural features and / or methodological acts, it is to be understood that the various example embodiments of the subject disclosure is not limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the various example embodiments of the subject disclosure.
Claims
1.A first device comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the first device to:receive, from a second device, an application identity associated with an application; anddetermine an edge computing resource and a network resource for the application based on the application identity, edge computing resource information, and network status information.2.The first device of claim 1, wherein the instructions, when executed by the at least one processor, cause the first device to:receive, from a third device, the edge computing resource information; andreceive, from a fourth device, the network status information.3.The first device of claim 1 or 2, wherein the edge computing resource information comprises at least one of:first information regarding a server of the application located on the third device; orsecond information regarding the third device.4.The first device of claim 3, wherein the first information comprises at least one of:an identity of the server,a load status of the server,link or routing information to the server, orservice area and service continuity information of the server, andwherein the second information comprises:routing information to the third device,a supported service area of the third device,resource utilization of the third device, ora hardware acceleration capability of the third device.5.The first device of any of claims 1-4, wherein the network status information comprises at least one of:a location area served by the fourth device,topology information of the fourth device,latency and bandwidth information between fourth devices,further latency and bandwidth information between the fourth device and the third device, orrouting information from the fourth device to the third device.6.The first device of any of claims 1-5, wherein the instructions, when executed by the at least one processor, cause the first device to:receive, from the second device, preference information of the application.7.The first device of claim 6, wherein the preference information comprises at least one of:application provider information of the application, oredge computing service provider information of the application.8.The first device of any of claims 1-7, wherein the instructions, when executed by the at least one processor, cause the first device to:determine at least one of:a data transmission path of the application, oraccess information to access the server of the application.9.The first device of any of claims 1-8, wherein the instructions, when executed by the at least one processor, cause the first device to:transmit, to the fourth device, at least one of: a user context of the second device and the routing information to the third device to establish the data transmission path.10.The first device of any of claims 1-9, wherein the instructions, when executed by the at least one processor, cause the first device to:transmit, to the second device, access information of the server on the third device, wherein the access information comprises at least one of: the identity of the server, an address of the server, or a domain name system server.11.The first device of any of claims 1-10, wherein the instructions, when executed by the at least one processor, cause the first device to:receive, from the second device, a service request comprising the application identity, and wherein the service request further comprises at least one of: a network slice identity associated with the application, or a data network name associated with the application.12.The first device of any of claims 1-11, wherein the instructions, when executed by the at least one processor, cause the first device to:receive, from the second device, a resource release request that comprises the application identity; orreceive, from the third device, the resource release request that comprises the application identity.13.The first device of any of claims 1-10, wherein the instructions, when executed by the at least one processor, cause the first device to:receive, from the second device, the application identity during a change of serving fourth device.14.The first device of claim 13, wherein the instructions, when executed by the at least one processor, cause the first device to:determine a further data transmission path of the application, wherein the further data transmission path at least comprises: a further fourth device, a further third device associated with the target cell, or a further sever of the application on the further third device.15.The first device of claim 13 or 14, wherein the instructions, when executed by the at least one processor, cause the first device to:transmit, to the fourth device, reconfiguration information; andtransmit, to the further fourth device, the reconfiguration information, and wherein the reconfiguration information comprises at least one of: a user context of the second device and further routing information to the further third device.16.The first device of any of claims 13-15, wherein the instructions, when executed by the at least one processor, cause the first device to:transmit, to the server on the third device, a context relocation message, and wherein the context relocation message comprises at least one of: link or routing information to the further server, routing information to the further third device, a domain name system server of the further server, or service area and service continuity information of the further server.17.The first device of any of claims 13-16, wherein the instructions, when executed by the at least one processor, cause the first device to:transmit, to the second device, further access information that comprises at least one of: an identity of the further server, an address of the further server, or the domain name system server of the further server.18.The first device of any of claims 1-17, wherein the instructions, when executed by the at least one processor, cause the first device to:store the edge computing resource information and the network status information.19.The first device of any of claims 1-18, wherein the first device comprises a network control plane unit, the second device comprises a terminal device, the third device comprises an edge computing unit, the fourth device comprises a network user plane unit.20.The first device of claim 19, wherein the network control plane unit is one of: a core network control plane unit, an access network control plane unit, or an entity that implements a control plane function, andwherein the network user plane unit is one of: a core network user plane unit, an access network user plane unit, or an entity that implements a user plane function.21.A second device comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the second device to:transmit, to a first device, an application identity associated with an application; andreceive, from the first device, access information regarding a sever of the application on a third device, and wherein access information is determined based on the application identity edge computing resource information, and network status.22.The second device of claim 20, wherein the edge computing resource information comprises at least one of:first information regarding a server of the application located on a third device; orsecond information regarding the third device.23.The second device of claim 21, wherein the first information comprises at least one of:an identity of the server,a load status of the server,access information to the server, orservice area and service continuity information of the server, andwherein the second information comprises:routing information to the third device,a supported service area of the third device,resource utilization of the third device, ora hardware acceleration capability of the third device.24.The second device of any of claims 20-22, wherein the network status information comprises at least one of:a location area served by a fourth device,topology information of the fourth device,latency and bandwidth information between fourth devices,further latency and bandwidth information between the fourth device and the third device, orrouting information from the fourth device to the third device.25.The second device of any of claims 20-23, wherein the instructions, when executed by the at least one processor, cause the second device to:transmit, to the first device, preference information of the application.26.The second device of claim 24, wherein the preference information comprises at least one of:application provider information of the application, oredge computing service provider information of the application.27.The second device of any of claims 20-25, wherein the access information comprises at least one of: an identity of the server located on the third device, address information of the server, or a domain name system server of the server.28.The second device of any of claims 20-26, wherein the instructions, when executed by the at least one processor, cause the second device to:transmit, to the first device, a service request comprising the application identity, and wherein the service request further comprises at least one of: a network slice identity associated with the application, or a data network name associated with the application.29.The second device of any of claims 20-27, wherein the instructions, when executed by the at least one processor, cause the second device to:transmit, to the first device, a resource release request that comprises the application identity.30.The second device of any of claims 20-28, wherein the instructions, when executed by the at least one processor, cause the second device to:send to the first device, the application identity during a change of serving fourth device.31.The second device of claim 29, wherein the instructions, when executed by the at least one processor, cause the second device to:receive, from the first device, at least one of: an identity of a further server on a further third device, address information of the further server, or a domain name system server of the further server.32.The second device of any of claims 20-30, wherein the first device comprises a network control plane unit, the second device comprises a terminal device, the third device comprises an edge computing unit, the fourth device comprises a network user plane unit.33.The second device of claim 32, wherein the network control plane unit is one of: a core network control plane unit, an access network control plane unit, or an entity that implements a control plane function, andwherein the network user plane unit is one of: a core network user plane unit, an access network user plane unit, or an entity that implements a user plane function.34.A method comprising:receiving, at a first device and from a second device, an application identity associated with an application; anddetermining an edge computing resource and a network resource for the application based on the application identity, edge computing resource information, and network status information.35.A method comprising:transmitting, at a second device and to a first device, an application identity associated with an application; andreceiving, from the first device, access information of a sever of the application on a third device, and wherein access information is determined based on the application identity, edge computing resource information, and network status.36.A first apparatus comprising:means for receiving, from a second apparatus, an application identity associated with an application; andmeans for determining an edge computing resource and a network resource for the application based on the application identity, edge computing resource information, and network status information.37.A second apparatus comprising:means for transmitting, to a first apparatus, an application identity associated with an application; andmeans for receiving from the first apparatus, access information of a sever of the application on a third device, and wherein access information is determined based on the application identity, edge computing resource information, and network status.38.A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of claim 34 or claim 35.
Citation Information
Patent Citations
Switching processing method and device and communication equipment
CN114598741A
Method and device for determining function and information provision of user plane, and medium
EP4145882A1
Method and device for determining edge application, apparatus and storage medium
US20220239623A1
Method, device and apparatus for address acquisition of application example and storage medium
WO2021004528A1
