Method and apparatus for communication service
By transmitting edge-related information in the edge computing system and coordinating the connection of user equipment, the service continuity problem during edge node switching is solved, effective communication and service management of paired user equipment is realized, and applications such as remote operation and driving are optimized. Delay and stability.
Patent Information
- Application Number
- CN202280095162.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-20
- Publication Date
- 2024-12-03
AI Technical Summary
Existing edge computing systems have difficulty maintaining service continuity between vehicles and control stations, especially when edge nodes of vehicles are switched, resulting in the inability to effectively maintain communication services between paired user equipment.
By transmitting edge-related information between user equipment and edge application servers, coordinating the connection between user equipment and edge platform, ensuring service continuity is maintained during edge node switching, and a central application server is used for paired user equipment registration and connection management.
It realizes service discovery and service continuity of paired user equipment in an edge computing environment, optimizes communication delay and stability of applications such as remote operation and driving, and ensures the smooth exchange of information between the vehicle and the control station.
Smart Images

Figure CN119072953A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates generally to communication networks, and more particularly to methods and apparatus for communication services. Background Art
[0002] This section introduces some aspects that help to better understand the present disclosure. Accordingly, the statements in this section should be understood in this light and should not be understood as an admission of what does or does not exist in the prior art.
[0003] Communication service providers and network operators have been facing the challenge of providing value and convenience to consumers through, for example, attractive network services and performance. With the rapid development of data communication and equipment manufacturing technology, a variety of communication devices have been designed and used to support diverse services. In recent years, remote control technology has been widely used in modern society and has become increasingly popular and widespread in civil and industrial applications. One application case of remote control technology is teleoperated driving (ToD), in which the driving of a vehicle can be remotely controlled by an operator through a communication network. Similar application cases may include remote drone control, digital twins, etc. These application cases may require a pair of user equipment (UE), such as a remotely operated vehicle and a control station, to achieve non-line-of-sight communication between each other. Considering the diversity of communication environments and application scenarios, the support and maintenance of paired UE communications may become more challenging. Summary of the invention
[0004] This summary is intended to introduce some concepts in a simplified form, which will be further explained in the detailed description below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
[0005] In order to meet the rapidly growing communication needs, an interesting option for the development of network technology is to support edge computing. Edge computing, as an evolutionary form of cloud computing, can decentralize application hosting from centralized data centers to the edge of the network, closer to consumers and the data generated by applications, especially in consideration of latency and bandwidth efficiency. In a vehicle system based on edge computing, due to the mobility of the vehicle, a vehicle served by an edge node may switch from the edge node to another edge node. For a pair of UEs, such as a vehicle and a control station participating in ToD, it may need to communicate with the same edge application server (EAS, Edge Application Server) to exchange information, such as video data captured by the vehicle, driving commands by the control station, etc. However, the current edge computing system can only support service discovery and service continuity for a single UE. In this case, the communication service between the paired UEs may not be maintained because the control station may not be able to connect to the appropriate EAS that is providing services to the vehicle, especially when the vehicle's EAS that provides services changes during the edge node switching. Therefore, it may be desirable to enhance service discovery and / or service continuity for paired UEs in the edge computing system.
[0006] Various exemplary embodiments of the present disclosure propose solutions for communication services, which enable edge discovery and / or service continuity for communications between paired UEs (e.g., primary UE, secondary UE, etc., where the primary UE is, for example, a remotely operated vehicle, and the secondary UE is, for example, a control station) that utilize edge computing technology.
[0007] According to a first aspect of the present disclosure, a method performed by a UE (e.g., a secondary UE) is proposed. The method includes: receiving edge related information sent by a server. The edge related information may indicate an EAS that is serving or is to serve another UE (e.g., a primary UE) paired with the UE. According to an exemplary embodiment, the method also includes: creating a connection with the EAS indicated by the edge related information.
[0008] According to an exemplary embodiment, the edge-related information may also indicate an edge platform (EP) associated with the EAS.
[0009] According to an exemplary embodiment, the UE may be a control station and the other UE may be a remotely operated vehicle.
[0010] According to an exemplary embodiment, the server may be a Central Application Server (CAS).
[0011] According to an exemplary embodiment, the method according to the first aspect of the present disclosure may further include: sending a request for edge related information to the CAS. The request may indicate another UE.
[0012] According to an exemplary embodiment, the edge-related information may also indicate another UE.
[0013] According to an exemplary embodiment, the method according to the first aspect of the present disclosure may further include: sending a message to the CAS. The message may indicate that the edge related information is received by the UE.
[0014] According to an exemplary embodiment, the server may be a source EAS for the UE and another UE, and the EAS indicated by the edge-related information may be a target EAS to which the UE and the other UE are to switch from the source EAS.
[0015] According to an exemplary embodiment, the method according to the first aspect of the present disclosure may further include: receiving a notification sent by the source EAS. The notification may indicate a status of Application Context Relocation (ACR) between the UE and another UE.
[0016] According to an exemplary embodiment, the method according to the first aspect of the present disclosure may further include: when the notification indicates that the ACR of the UE and the other UE is completed, communicating with the other UE using the created connection with the target EAS.
[0017] According to a second aspect of the present disclosure, a device that can be implemented as a UE is proposed. The device may include one or more processors and one or more memories storing computer program codes. The one or more memories and the computer program codes may be configured to, through one or more processors, cause the device to at least perform any step of the method according to the first aspect of the present disclosure.
[0018] According to a third aspect of the present disclosure, a computer-readable medium is provided, on which a computer program code is carried. When the computer program code is executed on a computer, the computer executes any step of the method according to the first aspect of the present disclosure.
[0019] According to a fourth aspect of the present disclosure, a device that can be implemented as a UE is proposed. The device may include a receiving unit and a creating unit. According to some exemplary embodiments, the receiving unit may be operated to at least perform the receiving step of the method according to the first aspect of the present disclosure. The creating unit may be operated to at least perform the creating step of the method according to the first aspect of the present disclosure.
[0020] According to a fifth aspect of the present disclosure, a method performed by a CAS is proposed. The method includes: receiving edge-related information from an EAS. The edge-related information may indicate that the EAS is serving or is to serve a UE (e.g., a primary UE). According to an exemplary example, the method also includes: maintaining registration information of the UE based on the edge-related information. The registration information of the UE may indicate the serving EAS of the UE.
[0021] According to an exemplary embodiment, the edge-related information may also indicate an EP associated with the EAS.
[0022] According to an exemplary embodiment, maintaining the registration information of the UE according to the edge-related information may include: generating the registration information of the UE according to the edge-related information. The registration information may include a registration identifier (ID) of the UE.
[0023] According to an exemplary embodiment, the method according to the fifth aspect of the present disclosure may further include: sending the registration ID of the UE to the EAS.
[0024] According to an exemplary embodiment, the method according to the fifth aspect of the present disclosure may further include: pairing the UE with another UE (eg, a secondary UE).
[0025] According to an exemplary embodiment, the method according to the fifth aspect of the present disclosure may further include: sending pairing information to the EAS. The pairing information may indicate the UE and another UE.
[0026] According to an exemplary embodiment, the method according to the fifth aspect of the present disclosure may further include: sending edge-related information to another UE paired with the UE.
[0027] According to an exemplary embodiment, the method according to the fifth aspect of the present disclosure may further include: receiving a request for edge-related information from the other UE. The request may indicate the UE.
[0028] According to an exemplary embodiment, when the other UE is authorized by CAS, edge related information may be sent to the other UE.
[0029] According to an exemplary embodiment, the edge-related information may also indicate the UE.
[0030] According to an exemplary embodiment, the method according to the fifth aspect of the present disclosure may further include: receiving a message from another UE. The message may indicate that the edge-related information is received by another UE.
[0031] According to an exemplary embodiment, the EAS may be a target EAS to which the UE is to switch from a source EAS, and the edge-related information received by the CAS may include a registration ID of the UE.
[0032] According to an exemplary embodiment, maintaining the registration information of the UE according to the edge-related information may include updating the registration information of the UE by changing a serving EAS of the UE from a source EAS to a target EAS according to a registration identifier of the UE.
[0033] According to an exemplary embodiment, the method according to the fifth aspect of the present disclosure may further include: notifying the EAS of an update of the registration information of the UE.
[0034] According to a sixth aspect of the present disclosure, a device that can be implemented as a CAS is proposed. The device may include one or more processors and one or more memories storing computer program codes. The one or more memories and the computer program codes may be configured to, through one or more processors, cause the device to at least perform any step of the method according to the fifth aspect of the present disclosure.
[0035] According to a seventh aspect of the present disclosure, a computer-readable medium is provided, on which a computer program code is carried. When the computer program code is executed on a computer, the computer executes any step of the method according to the fifth aspect of the present disclosure.
[0036] According to an eighth aspect of the present disclosure, a device that can be implemented as a CAS is proposed. The device may include a receiving unit and a maintaining unit. According to some exemplary embodiments, the receiving unit may be operated to at least perform the receiving step of the method according to the fifth aspect of the present disclosure. The maintaining unit may be operated to at least perform the maintaining step of the method according to the fifth aspect of the present disclosure.
[0037] According to a ninth aspect of the present disclosure, a method performed by an EAS is proposed. The method includes: sending edge related information to a CAS. The edge related information may indicate that the EAS is serving or is about to serve a UE (e.g., a primary UE). According to an exemplary embodiment, the method also includes: receiving information related to UE registration from the CAS.
[0038] According to an exemplary embodiment, the edge-related information may also indicate an EP associated with the EAS.
[0039] According to an exemplary embodiment, the information related to the UE registration may include a registration ID of the UE.
[0040] According to an exemplary embodiment, the method according to the ninth aspect of the present disclosure may further include: receiving pairing information from the CAS. The pairing information may indicate the UE and another UE (eg, secondary UE) paired with the UE.
[0041] According to an exemplary embodiment, the EAS may be a target EAS to which the UE is to switch from a source EAS, and the edge-related information transmitted to the CAS may include a registration ID of the UE.
[0042] According to an exemplary embodiment, the method according to the ninth aspect of the present disclosure may also include: receiving an application context of the UE and another UE (e.g., a secondary UE) paired with the UE from a source EAS. The application context may include a registration ID of the UE and / or pairing information indicating the UE and the other UE.
[0043] According to an exemplary embodiment, the information related to the UE registration may indicate that the registration information of the UE at the CAS is updated by changing the serving EAS of the UE to the target EAS.
[0044] According to an exemplary embodiment, the method according to the ninth aspect of the present disclosure may further include: creating a connection with another UE so as to support communication between the UE and the other UE.
[0045] According to the tenth aspect of the present disclosure, a device that can be implemented as an EAS is proposed. The device may include one or more processors and one or more memories storing computer program codes. The one or more memories and the computer program codes may be configured to, through one or more processors, enable the device to at least perform any step of the method according to the ninth aspect of the present disclosure.
[0046] According to an eleventh aspect of the present disclosure, a computer-readable medium is provided, on which a computer program code is carried. When the computer program code is executed on a computer, the computer executes any step of the method according to the ninth aspect of the present disclosure.
[0047] According to a twelfth aspect of the present disclosure, a device that can be implemented as an EAS is provided. The device may include a sending unit and a receiving unit. According to some exemplary embodiments, the sending unit may be operated to at least perform the sending step of the method according to the ninth aspect of the present disclosure. The receiving unit may be operated to at least perform the receiving step of the method according to the ninth aspect of the present disclosure.
[0048] According to the thirteenth aspect of the present disclosure, a method performed by an EAS is proposed. The method includes: when another UE (e.g., a primary UE) paired with the UE switches from the EAS to another EAS, edge-related information is sent to the UE (e.g., a secondary UE). The edge-related information may indicate that the other EAS is serving or is to serve the other UE. According to an exemplary embodiment, the method also includes: transmitting the application context of the UE and the other UE to another EAS. The application context may include: a registration ID of the other UE, and / or, pairing information indicating the UE and the other UE.
[0049] According to an exemplary embodiment, the edge-related information may also indicate an EP associated with another EAS.
[0050] According to an exemplary embodiment, when another UE is registered to the CAS, the registration ID of the other UE may be provided by the CAS.
[0051] According to an exemplary embodiment, the method according to the thirteenth aspect of the present disclosure may further include: sending a notification to the UE. The notification may indicate the status of the ACR of the UE and another UE.
[0052] According to the fourteenth aspect of the present disclosure, a device that can be implemented as an EAS is proposed. The device may include one or more processors and one or more memories storing computer program codes. The one or more memories and the computer program codes may be configured to, through one or more processors, enable the device to at least perform any step of the method according to the thirteenth aspect of the present disclosure.
[0053] According to a fifteenth aspect of the present disclosure, a computer-readable medium is provided, on which a computer program code is carried. When the computer program code is executed on a computer, the computer executes any step of the method according to the thirteenth aspect of the present disclosure.
[0054] According to a sixteenth aspect of the present disclosure, a device that can be implemented as an EAS is provided. The device may include a sending unit and a transmission unit. According to some exemplary embodiments, the sending unit may be operated to at least perform the sending step of the method according to the thirteenth aspect of the present disclosure. The transmission unit may be operated to at least perform the transmission step of the method according to the thirteenth aspect of the present disclosure.
[0055] According to various exemplary embodiments, in some application cases (such as ToD, remote drone control, and digital twins, etc.), a pair of UEs that need to cooperate with each other may select a common EAS so that the communication service between the pair of UEs can be maintained with optimized end-to-end delay. BRIEF DESCRIPTION OF THE DRAWINGS
[0056] The present disclosure itself, as well as preferred modes of use and further objects, may be better understood by reference to the following detailed description of embodiments when read in conjunction with the accompanying drawings, in which:
[0057] Figure 1 is a diagram showing a ToD example according to an embodiment of the present disclosure;
[0058] Figure 2A is a schematic diagram showing an exemplary architecture of an edge computing system according to an embodiment of the present disclosure;
[0059] Figure 2B is a schematic diagram showing an exemplary architecture of UE communication using edge pairing according to an embodiment of the present disclosure;
[0060] Figure 3 is a schematic diagram showing an exemplary edge discovery process according to an embodiment of the present disclosure;
[0061] Figure 4 is a schematic diagram showing an exemplary ACR process according to an embodiment of the present disclosure;
[0062] Figures 5A to 5D is a flowchart illustrating various methods according to embodiments of the present disclosure;
[0063] Figure 6 is a block diagram showing an apparatus according to an embodiment of the present disclosure; and
[0064] Figures 7A to 7D is a block diagram showing various devices according to an embodiment of the present disclosure. DETAILED DESCRIPTION
[0065] Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed for the purpose of enabling those skilled in the art to better understand and thus implement the present disclosure, rather than to impose any limitation on the scope of the present disclosure. Features, advantages or similar expressions mentioned throughout this specification do not mean that all features and advantages that can be implemented by the present disclosure should be or exist in any single embodiment of the present disclosure. On the contrary, the language referring to features and advantages is understood as specific features, advantages or characteristics related to the embodiment being included in at least one embodiment of the present disclosure. In addition, the features, advantages and characteristics described in the present disclosure can be combined in any suitable manner into one or more embodiments. It will be appreciated by those skilled in the relevant art that the present disclosure can be implemented without one or more specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments, and these features and advantages may not be present in all embodiments of the present disclosure.
[0066] As used herein, the terms "first", "second", etc. are used to refer to different elements. The singular forms "a" and "an" are intended to include the plural forms, unless the context clearly indicates otherwise. The terms "include", "comprise", "have", "contain", "include" and / or "comprising" as used herein indicate the presence of the described features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof. The term "based on" should be understood as "based at least in part on". The terms "one embodiment" and "embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Other definitions, whether explicit or implicit, may be included below.
[0067] In recent years, vehicles have become increasingly intelligent and can communicate with any other entity that can provide consumers with rich features (such as multimedia experience, safer experience, smarter navigation experience, etc.). The development of vehicle technology has made it possible to control vehicles in a variety of novel ways. Teleoperated driving (ToD) refers to the driving of a vehicle remotely controlled by an operator from outside the line of sight.
[0068] Figure 1 is a schematic diagram showing a ToD example according to an embodiment of the present disclosure. Basically, ToD may require some components, such as a high-definition (HD) camera, an on-board control unit in a vehicle, and a control center where an operator can control the vehicle. The on-board unit in the vehicle can provide functions such as braking, acceleration, and steering, and the operator can access these functions through a control station in the control center. In turn, the on-board unit can provide the operator with data about the current visual impression of the road conditions, so that the operator can react appropriately. In order to generate this current impression, the vehicle may require video streams from at least four HD cameras. These data streams can be transmitted to the control center via a mobile communication network, for example, on a monitor or virtual reality (VR) glasses. Based on the video stream and / or sensor data from the vehicle, the operator can, for example, send one or more control commands to the vehicle via a mobile communication network. A stable, low-latency, and high-bandwidth mobile connection may be one of the important factors in achieving ToD.
[0069] Edge computing may play an important role in the transformation of telecommunications services, where telecommunications networks are being transformed into multi-functional service platforms for industrial and other specific customer groups. Edge computing can support this transformation because it opens the network edge to applications and services, including those from third parties. Due to the connection requirements for stability, latency and bandwidth, edge computing may be the perfect technology to achieve ToD.
[0070] Mobility is a characteristic of vehicles. When a vehicle UE moves in a mobile communication network, the mobile edge node that provides services for the vehicle UE may change. The switching of mobile edge nodes (which may include application relocation and context transfer) is important to ensure the service continuity and security of ToD.
[0071] Current edge computing systems can provide service discovery and service continuity support for a single UE. For example, in an edge computing-based connected vehicle / autonomous driving vehicle system, the edge computing system can provide corresponding services to support vehicle UE switching edge nodes, such as those described in the European Telecommunications Standards Institute (ETSI) Multi-Access Edge Computing (MEC) "Application Mobility Service (AMS)" or the 3rd Generation Partnership Project (3GPP) EDGEAPP "Service Continuity Support".
[0072] However, in a ToD system, two types of UEs are usually involved: a vehicle (as a primary UE) and a control station (as a secondary UE). These two UEs may need to communicate with the same EAS to exchange information. During edge node switching, the edge computing system may need to coordinate the two UEs to ensure service continuity. Currently, edge computing systems cannot provide such service continuity support.
[0073] Various exemplary embodiments of the present disclosure propose a solution of coordinating a pair of UEs to select a common EAS for communication. For some application cases (such as ToD, drone remote control, and digital twins), it may be important to select a common EAS for a pair of UEs in order to avoid synchronization between EASs and reduce end-to-end latency. According to an exemplary embodiment, CAS may provide edge discovery capabilities for secondary UEs (such as control stations, etc.) to discover a common EAS. According to another exemplary embodiment, EAS may provide ACR support to coordinate primary UEs (such as remotely operated vehicles, etc.) and secondary UEs (such as control stations, etc.).
[0074] It will be appreciated that while some exemplary embodiments are described in the context of ToD, the same principles may be applied to other use cases, such as remote drone control and digital twins, to enable selection of a common EAS for paired UEs, thereby avoiding complex inter-EAS synchronization when two UEs are connected to different EASs, and reducing end-to-end latency for paired UE communications via EAS.
[0075] Figure 2A is a schematic diagram showing an exemplary architecture of an edge computing system according to an embodiment of the present disclosure. In a general reference architecture of an edge computing system, there may be one or more edge nodes (also referred to as edge sites), such as Figure 2AThe edge nodes #A and edge nodes #B shown in the figure each provide services for a corresponding geographical area. Each edge node can be connected to a central node (also called a central site) via a wired or wireless connection. In the edge node, a set of software and hardware can be deployed to provide services to UEs within a specific geographical area. Typically, an edge node may include an EP that provides a range of services and a virtualized infrastructure that provides computing, storage, and network resources for EAS. The EP can provide a range of services to facilitate EAS and UE, such as EAS discovery, network capabilities, and service continuity support. In one embodiment, the EP can be mapped to the edge enabler server (EES) in 3GPP SA6 EDGEAPP (for example, as described in 3GPP TS23.558 V17.3.0, Technical Specification Group Services and System Aspects; Architecture for Enabling Edge Applications), or mapped to the MEC platform in the ETSI MEC reference architecture (for example, as described in ETSI GS MEC 003 V2.2.1, Multi-Access Edge Computing; Framework and Reference Architecture).
[0076] According to an exemplary embodiment, EAS can be an application server developed by an application service provider (ASP, Application Service Provider) to implement specific business logic. EAS can be deployed in an edge node and can be accessed by a UE through an edge data network (EDN, Edge Data Network). In one embodiment, EAS can be mapped to EAS in 3GPP SA6 EDGEAPP (for example, as described in 3GPP TS23.558V17.3.0, Technical Specification Group Services and System Aspects; Architecture for Enabling Edge Applications), or mapped to MEC applications in the ETSI MEC reference architecture (for example, as described in ETSI GSMEC 003V2.2.1, Multi-Access Edge Computing; Framework and Reference Architecture).
[0077] According to an exemplary embodiment, at a central site, a discovery server may be deployed as a centralized server to provide services to UEs to discover edge nodes / edge sites / edge platforms based on the context of the UE. In one embodiment, the discovery server may be mapped to an edge configuration server (ECS) in 3GPP SA6 EDGEAPP (e.g., as described in 3GPP TS23.558 V17.3.0, Technical Specification Group Services and System Aspects; Architecture for Enabling Edge Applications).
[0078] Figure 2B1 is a schematic diagram showing an exemplary architecture of UE communication using edge pairing according to an embodiment of the present disclosure. Various entities applicable to edge computing systems can be deployed in the architecture of UE communication using edge pairing. Figure 2B As shown in , CAS that is not deployed at the edge but at the central cloud can collaborate with EAS. CAS can also be developed by ASP. A pair of UEs including a primary UE (e.g., a remotely operated vehicle, etc.) and a secondary UE (e.g., a control station, etc.) can be served by an edge computing system and can communicate with each other via EAS. According to an exemplary embodiment, the primary UE can use the services provided by the edge computing system to discover EP / EAS, and EP / EAS can be selected based on the context of the primary UE (e.g., location, etc.). The secondary UE can use CAS to discover EP / EAS, and EP / EAS can be selected based on the paired primary UE. In one embodiment, the primary UE and the secondary UE can exchange application data through the same EAS instead of direct communication. Using EAS to relay paired UE communications can have several advantages, such as data enrichment, security / privacy protection, etc.
[0079] Understandably, Figure 2A and Figure 2B The system structure and various nodes / entities shown in are merely examples. According to an embodiment of the present disclosure, more or fewer alternative nodes / entities and corresponding interfaces with different structures may be included in the edge computing system to support paired UE communications.
[0080] Figure 3 is a schematic diagram showing an exemplary edge discovery process according to an embodiment of the present disclosure. The edge discovery process may be performed for a pair of UEs, such as a primary UE (e.g., a remotely operated vehicle, etc.) and a secondary UE (e.g., a control station, etc.), so as to discover a common EAS to connect to when they begin to access services provided by the EAS. According to an exemplary embodiment, when performing edge discovery for paired UEs, the primary UE may use services provided by the edge computing system to discover the EAS, and the secondary UE may use the CAS to discover the EAS that provides services to the primary UE. It is understandable that Figure 3 The network elements and signaling messages shown in are merely examples, and according to various embodiments of the present disclosure, more or fewer alternative network elements and signaling messages may be involved in the edge discovery process. Figure 3 As shown, the edge discovery process may include the following operations: 301: The master UE may discover the EAS through the edge computing system. For example, the master UE may discover the EP through the discovery server, and discover / select the EAS through the EP. 302: The primary UE may create a connection to the discovered / selected EAS. 303: EAS may send a "primary UE registration" request to CAS. The "primary UE registration" request may include the primary UE ID and information about the EP / EAS to which the primary UE is currently connected. The EP / EAS information may include at least ID and endpoint information. 304: CAS may send a “Primary UE Registration” response with the registration ID to EAS. 305: CAS may pair the primary UE and the secondary UE as required. 306: The CAS may send a "provide pairing" request to the EAS to which the primary UE is currently connected. The "provide pairing" request may include the primary UE ID and the secondary UE ID. 307: EAS may send an "offer pairing" response back to CAS. 308: CAS may provide EP / EAS information to the secondary UE. There may be two alternatives for extracting / pushing EP / EAS information from CAS to the secondary UE: -Alternative 1 (ALT 1: Extract EP / EAS information) 308a: If the secondary UE knows the UE ID of the primary UE, the secondary UE may discover EAS through CAS. For example, the secondary UE may send a "discover EAS" request to the CAS. The "discover EAS" request may include the primary UE ID. 308b: For security and privacy purposes, CAS may perform authorization based on the pairing information of the primary UE and the secondary UE. 308c: The CAS may send a "Discover EAS" response to the secondary UE, which includes EP / EAS information indicating the EP / EAS to which the primary UE is currently connected. The EP / EAS information may include at least an ID and endpoint information. -Alternative 2 (ALT 2: Push EP / EAS information) 308d: The CAS may push the EP / EAS information to the secondary UE, for example, by sending an "EAS Notification" request. The "EAS Notification" request may include the primary UE ID and the EP / EAS information. 308e: The secondary UE may send an "EAS Notification" response back to the CAS. 309: The secondary UE may create a connection to the same EAS to which the primary UE is currently connected. 310: The secondary UE may communicate with the primary UE via the EAS.
[0081] Figure 4is a schematic diagram showing an exemplary ACR process according to an embodiment of the present disclosure. The ACR process may be triggered by the movement of the primary UE. When the primary UE switches its service edge node, the source EAS (S-EAS) may need to transfer the application context of the paired UEs (primary UE and secondary UE) to the target EAS (T-EAS) to ensure that the T-EAS can provide services to the paired UEs without interrupting the service, which is also referred to as service continuity support. According to an exemplary embodiment, in order to support service continuity, the ACR status may be notified to the secondary UE so that the secondary UE can connect to the same T-EAS as the primary UE. It will be understood that Figure 4 The network elements and signaling messages shown in are merely examples, and according to various embodiments of the present disclosure, more or fewer alternative network elements and signaling messages may be involved in the ACR process. Figure 4 As shown, the ACR process may include the following operations: 401: S-EAS may detect that the master UE needs to switch edge nodes (eg, by monitoring the location of the master UE). Then, S-EAS may decide to trigger ACR. 402: S-EAS may discover T-EP and T-EAS according to the context of the primary UE (e.g., its current location, etc.) by using services provided by the edge computing system. For example, S-EAS may discover T-EP through a discovery server, and discover T-EAS through T-EP. 403: S-EAS may notify the master UE of T-EP / T-EAS information. In one embodiment, the S-EAS may send an "ACR Information Notification" request to the S-EP. The "ACR Information Notification" request sent to the S-EP may include the master UE ID and T-EP / T-EAS information. The T-EP / T-EAS information may include at least the ID and endpoint information. Then, the S-EP may send an "ACR Information Notification" request to the master UE. The "ACR Information Notification" request sent to the master UE may include T-EP / T-EAS information. The T-EP / T-EAS information may include at least the ID and endpoint information. Optionally, the master UE may send an "ACR Information Notification" response back to the S-EP, and the S-EP may send an "ACR Information Notification" response back to the S-EAS. 404: The primary UE may create a secondary connection to the T-EAS. 405: Based on the pairing information of the primary UE and the secondary UE, the S-EAS may also notify the secondary UE of the T-EP / T-EAS information. In one embodiment, the S-EAS may send an "ACR information notification" request to the S-EP. The "ACR information notification" request sent to the S-EP may include the secondary UE ID and the T-EP / T-EAS information. The T-EP / T-EAS information may include at least the ID and the endpoint information. Then, the S-EP may send an "ACR information notification" request to the secondary UE. The "ACR information notification" request sent to the secondary UE may include the T-EP / T-EAS information. The T-EP / T-EAS information may include at least the ID and the endpoint information. Optionally, the secondary UE may send an "ACR information notification" response back to the S-EP, and the S-EP may send an "ACR information notification" response back to the S-EAS. 406: The secondary UE may establish a secondary connection to the T-EAS. 407: S-EAS may start transferring the application context of the primary UE and the secondary UE to T-EAS. In one embodiment, the registration information (e.g., including the registration ID) and the pairing information (e.g., including the primary UE ID and the secondary UE ID) of the primary UE may be part of the application context, so that the registration information and the pairing information of the primary UE may also be transferred from S-EAS to T-EAS. 408: Once the transfer of the application context is completed, the S-EAS may notify the master UE of the completion status, for example by sending another "ACR Information Notification" request. For example, the S-EAS may send an "ACR Information Notification" request to the S-EP. The "ACR Information Notification" request sent to the S-EP may include the master UE ID and the completion status. The S-EP may send the "ACR Information Notification" request to the master UE. The "ACR Information Notification" sent to the master UE may include the completion status. Optionally, the master UE may send an "ACR Information Notification" response back to the S-EP, and the S-EP may send an "ACR Information Notification" response back to the S-EAS. 409: The primary UE may start using the secondary connection to the T-TAS. 410: T-EAS may send an "Update Primary UE Registration" request to CAS. The "Update Primary UE Registration" request may include the registration ID of the primary UE and T-EP / T-EAS information. 411: CAS may send an "Update Primary UE Registration" response back to T-EAS, for example when the registration information of the primary UE is updated on CAS. 412: Based on the pairing information, the S-EAS may also notify the secondary UE of the completion status. In one embodiment, the S-EAS may send an "ACR Information Notification" request to the S-EP. The "ACR Information Notification" request sent to the S-EP may include the secondary UE ID and the completion status. The S-EP may send an "ACR Information Notification" request to the secondary UE. The "ACR Information Notification" request sent to the secondary UE may include the completion status. Optionally, the secondary UE may send an "ACR Information Notification" response back to the S-EP, and the S-EP may send an "ACR Information Notification" response back to the S-EAS. 413: The secondary UE may start using the secondary connection to the T-EAS. 414: The secondary UE may communicate with the primary UE via T-EAS.
[0082] Understandably, Figure 3 and Figure 4 The names, parameters and routes of the various messages / signals shown in are merely examples. In the implementation of the recommended solutions according to the embodiments of the present disclosure, other alternative names, parameters and routes as well as related configurations and settings of different messages / signals may also be applied.
[0083] Figure 5A is a flow chart illustrating a method 510 according to some embodiments of the present disclosure. Figure 5A The illustrated method 510 may be performed by a UE (e.g., a secondary UE, such as a control station, etc.) or a device communicatively coupled to the UE. According to an exemplary embodiment, the UE may be configured to obtain various services provided by an application server (e.g., EAS, CAS, etc.) and communicate with another UE (e.g., a primary UE, such as a remotely operated vehicle, etc.) in an edge computing system.
[0084] according to Figure 5A In the exemplary method 510 shown, the UE may receive edge-related information sent by the server, as shown in block 512. The edge-related information may indicate an EAS that is serving or is to serve another UE paired with the UE. According to an exemplary embodiment, the UE may establish a connection with the EAS indicated by the edge-related information, as shown in block 514.
[0085] According to an exemplary embodiment, the edge-related information may also indicate an EP associated with the EAS.
[0086] According to an exemplary embodiment, the server may be a CAS.
[0087] According to an exemplary embodiment, the UE may send a request for edge-related information (eg Figure 3 The "Discover EAS" request in the UEID is sent to the CAS. The request may indicate another UE (for example, by including the ID of the other UE).
[0088] According to an exemplary embodiment, the edge related information may also indicate another UE (for example, by including the ID of another UE in Figure 3 in the "EAS Notification" request).
[0089] According to an exemplary embodiment, the UE may send a message (eg Figure 3 The message may indicate that edge related information is received by the UE.
[0090] According to an exemplary embodiment, the server may be a source EAS (eg, Figure 4 The S-EAS in FIG. 1 , and the EAS indicated by the edge-related information may be a target EAS (eg, Figure 4 The UE and another UE need to switch from the source EAS to the target EAS.
[0091] According to an exemplary embodiment, the UE may receive a notification (eg, Figure 4 The notification may indicate the status of the ACR of the UE and another UE.
[0092] According to an exemplary embodiment, when a notification (e.g. Figure 4 When the "ACR Information Notification" request in the UE indicates that the ACR between the UE and another UE is completed, the UE can use the created connection with the target EAS to communicate with the other UE.
[0093] Figure 5B is a flow chart illustrating a method 520 according to some embodiments of the present disclosure. Figure 5B The method 520 shown in the figure may be performed by a CAS or by a device coupled to the CAS in communication. According to an exemplary embodiment, the CAS may be configured to support or provide various services to one or more UEs. According to another exemplary embodiment, the CAS may be configured to communicate with one or more other servers (e.g., one or more EASs, etc.) to implement application provision and / or management of one or more UEs.
[0094] according to Figure 5B In the exemplary method 520 shown, the CAS may receive edge-related information from the EAS, as shown in box 522. The edge-related information may indicate that the EAS is serving or is to serve the UE (e.g., the master UE of the paired UE). According to an exemplary embodiment, the CAS may maintain the registration information of the UE based on the edge-related information, as shown in box 524. The registration information of the UE may indicate the serving EAS of the UE.
[0095] According to an exemplary embodiment, the edge-related information may also indicate an EP associated with the EAS.
[0096] According to an exemplary embodiment, the CAS may maintain the registration information of the UE by generating registration information according to the edge-related information. The registration information may include the registration ID of the UE. In one embodiment, the CAS may send the registration ID of the UE to the EAS (e.g., in the form of a Figure 3 "Primary UE Registration" response in UEID.
[0097] According to an exemplary embodiment, the CAS may pair the UE with another UE (e.g., a secondary UE of the paired UE). In one embodiment, the CAS may send the pairing information to the EAS (e.g., Figure 3 The pairing information may indicate the UE and another UE.
[0098] According to an exemplary embodiment, the CAS may send edge related information to another UE paired with the UE (e.g., Figure 3 'EAS Discovery' response and / or 'EAS Notification' request in the .
[0099] According to an exemplary embodiment, the CAS may receive a request for edge-related information from another UE (eg, Figure 3 The request may indicate the UE (e.g., by including the ID of the UE). In one embodiment, when the other UE is authorized by CAS, edge related information may be sent to the other UE.
[0100] According to an exemplary embodiment, the edge related information may also indicate to the UE (e.g., by Figure 3 In one embodiment, the CAS may receive a message from another UE (e.g. Figure 3 The message may indicate that edge-related information is received by another UE.
[0101] According to an exemplary embodiment, the EAS may be a target EAS (eg, Figure 4 T-EAS in the UE, the UE needs to receive the T-EAS from the source EAS (e.g. Figure 4 The UE switches to the target EAS through the S-EAS in the CAS, and the edge-related information received by the CAS may include the registration ID of the UE.
[0102] According to an exemplary embodiment, the CAS may update the registration information of the UE by changing the serving EAS of the UE from the source EAS to the target EAS according to the registration identifier of the UE based on the edge related information, thereby maintaining the registration information of the UE. In one embodiment, the CAS may notify the EAS of the update of the registration information of the UE (e.g., in the form of Figure 4 Update Primary UE Registration response in UEID.
[0103] Figure 5C is a flow chart illustrating a method 530 according to some embodiments of the present disclosure. Figure 5C The method 530 shown in FIG. 5 may be performed by an EAS (eg, Figure 3 The EAS shown in Figure 4 According to an exemplary embodiment, the EAS may be configured to support or provide various services to one or more UEs. According to another exemplary embodiment, the EAS may be configured to communicate with one or more other servers (e.g., one or more other EASs, CASs, etc.) to implement application provision and / or management of one or more UEs.
[0104] According to Figure 5C In the exemplary method 530 shown in FIG. 5 , the EAS may send edge-related information to the CAS, as shown in block 532. The edge-related information may indicate that the EAS is providing or is about to provide services to a UE (e.g., a primary UE in a paired UE). According to an exemplary embodiment, the EAS may receive information related to UE registration from the CAS, as shown in block 534.
[0105] According to an exemplary embodiment, the edge-related information may also indicate an EP associated with the EAS.
[0106] According to an exemplary embodiment, the information related to the UE registration received by the EAS may include the registration ID of the UE (e.g., Figure 3 "Primary UE Registration" response in UEID.
[0107] According to an exemplary embodiment, the EAS may receive pairing information (e.g., in the form of Figure 3 The pairing information may indicate the UE and another UE (eg, a secondary UE) that is paired with the UE.
[0108] According to an exemplary embodiment, the EAS may be a target EAS (eg, Figure 4 T-EAS in the UE, the UE needs to receive the T-EAS from the source EAS (e.g. Figure 4 The UE switches to the target EAS through the S-EAS in the UE, and the edge-related information sent by the EAS to the CAS may include the registration ID of the UE.
[0109] According to an exemplary embodiment, the EAS may receive an application context of a UE and another UE (eg, a secondary UE) paired with the UE from a source EAS. The application context may include a registration ID of the UE and / or pairing information indicating the UE and the other UE.
[0110] According to an exemplary embodiment, the information related to the UE registration received by the EAS from the CAS may indicate that the registration information of the UE at the CAS is updated by changing the serving EAS of the UE to the target EAS.
[0111] According to an exemplary embodiment, the EAS may create a connection with another UE, thereby supporting communication between the UE and the other UE.
[0112] Figure 5D is a flow chart illustrating a method 540 according to some embodiments of the present disclosure. Figure 5D The method 540 shown in FIG. 5 may be performed by an EAS (eg, Figure 4 According to an exemplary embodiment, the EAS may be configured to support or provide various services to one or more UEs. According to another exemplary embodiment, the EAS may be configured to communicate with one or more other servers (e.g., one or more other EASs, CASs, etc.) to implement application provision and / or management of one or more UEs.
[0113] according to Figure 5D In the exemplary method 540 shown in FIG. 5 , when another UE (e.g., a primary UE) paired with a UE switches from an EAS to another EAS, the EAS may send edge-related information to the UE (e.g., a secondary UE in the paired UE), as shown in box 542. The edge-related information may indicate that another EAS is serving or is to serve another UE. According to an exemplary embodiment, the EAS may transmit the application context of the UE and another UE to another EAS, as shown in box 544. The application context may include: a registration ID of another UE, and / or, pairing information indicating the UE and another UE.
[0114] According to an exemplary embodiment, the edge-related information may also indicate an EP associated with another EAS.
[0115] According to an exemplary embodiment, when another UE is registered with the CAS, the registration ID of the other UE may be provided by the CAS (e.g., in the form of Figure 3 "Primary UE Registration" response in UEID.
[0116] According to an exemplary embodiment, the EAS may send a notification to the UE (e.g., Figure 4 The notification may indicate the status of the ACR of the UE and another UE.
[0117] Figures 5A to 5D The various blocks shown in the figure may be viewed as method steps, and / or as operations produced by the operation of a computer program code, and / or as a plurality of coupled logic circuit elements configured to perform the relevant functions. Figure 1 Generally referred to as a logical flow chart. Therefore, the depicted order and labeled steps indicate a specific embodiment of the presented method. Other steps and methods can be envisioned, which are equivalent in function, logic or effect to one or more steps of the illustrated method or some parts thereof. In addition, the order in which a particular method occurs may or may not strictly follow the order of the steps shown.
[0118] Figure 6 6 is a block diagram showing an apparatus 600 according to various embodiments of the present disclosure. Figure 6 As shown, the apparatus 600 may include: one or more processors, such as processor 601; and one or more memories, such as memory 602 storing computer program code 603. The memory 602 may be a non-transitory machine / processor / computer readable storage medium. According to some exemplary embodiments, the apparatus 600 may be implemented as an integrated circuit chip or module, which can be inserted or installed into a computer according to the present invention. Figure 5A UE as described, or as described according to Figure 5B CAS as described, or as per Figure 5C EAS as described, or as provided in Figure 5D In these cases, the apparatus 600 may be implemented as described in accordance with Figure 5A UE as described, or as described according to Figure 5B CAS as described, or as per Figure 5C EAS as described, or as provided in Figure 5D EAS as described.
[0119] In some implementations, the one or more memories 602 and the computer program code 603 may be configured to, with the aid of the one or more processors 601, cause the apparatus 600 to at least perform the following steps in conjunction with Figure 5A In other implementations, the one or more memories 602 and the computer program code 603 may be configured to, with the aid of the one or more processors 601, cause the apparatus 600 to at least perform the following steps in conjunction with Figure 5B In other implementations, the one or more memories 602 and the computer program code 603 may be configured to, with the aid of the one or more processors 601, cause the apparatus 600 to at least perform the following steps in conjunction with Figure 5C In other implementations, the one or more memories 602 and the computer program code 603 may be configured to, with the aid of the one or more processors 601, cause the apparatus 600 to at least perform the following steps in conjunction with Figure 5DAlternatively or additionally, the one or more memories 602 and the computer program code 603 may be configured to, with the aid of the one or more processors 601, enable the apparatus 600 to at least perform more or fewer operations to implement the method suggested according to the exemplary embodiments of the present disclosure.
[0120] Fig. 7A 7 is a block diagram illustrating an apparatus 710 according to some embodiments of the present disclosure. Fig. 7A As shown, the device 710 may include a receiving unit 711 and a creating unit 712. In an exemplary embodiment, the device 710 may be implemented in a UE. The receiving unit 711 may be operated to perform the operations in block 512, and the creating unit 712 may be operated to perform the operations in block 514. Optionally, the receiving unit 711 and / or the creating unit 712 may be operated to perform more or less operations to implement the method suggested according to the exemplary embodiments of the present disclosure. In one embodiment, the device 710 may include a sending unit ( Fig. 7A ), which is used to send various information from device 710 to other devices (e.g., UE, EAS, CAS, etc.).
[0121] Figure 7B 7 is a block diagram illustrating an apparatus 720 according to some embodiments of the present disclosure. Figure 7B As shown, the device 720 may include a receiving unit 721 and a maintenance unit 722. In an exemplary embodiment, the device 720 may be implemented in a CAS. The receiving unit 721 may be operated to perform the operations in block 522, and the maintenance unit 722 may be operated to perform the operations in block 524. Optionally, the receiving unit 721 and / or the maintenance unit 722 may be operated to perform more or less operations to implement the method suggested according to the exemplary embodiments of the present disclosure. In one embodiment, the device 720 may include a sending unit ( Figure 7B ), which is used to send various information from device 720 to other devices (e.g., UE, EAS, etc.).
[0122] Figure 7C 7 is a block diagram illustrating an apparatus 730 according to some embodiments of the present disclosure. Figure 7C As shown, the device 730 may include a sending unit 731 and a receiving unit 732. In an exemplary embodiment, the device 730 may be implemented in an EAS. The sending unit 731 may be operated to perform the operations in block 532, and the receiving unit 732 may be operated to perform the operations in block 534. Optionally, the sending unit 731 and / or the receiving unit 732 may be operated to perform more or less operations to implement the method suggested according to the exemplary embodiments of the present disclosure.
[0123] Fig.7D 7 is a block diagram illustrating an apparatus 740 according to some embodiments of the present disclosure. Fig.7D As shown, the device 740 may include a sending unit 741 and a transmission unit 742. In an exemplary embodiment, the device 740 may be implemented in an EAS. The sending unit 741 may be operated to perform the operations in block 542, and the transmission unit 742 may be operated to perform the operations in block 544. Optionally, the sending unit 741 and / or the transmission unit 742 may be operated to perform more or less operations to implement the method suggested according to the exemplary embodiments of the present disclosure. In one embodiment, the device 740 may include a receiving unit ( Fig.7D ), for receiving various information from other devices (eg, UE, EAS, CAS, etc.) to apparatus 740.
[0124] In general, each exemplary embodiment can be implemented in hardware or dedicated chips, circuits, software, logic units, or any combination thereof. For example, some aspects can be implemented in hardware, while other aspects can be implemented in firmware or software, which can be executed by a controller, microprocessor, or other computing device, but the present disclosure is not limited thereto. Although each exemplary embodiment of the present disclosure can be illustrated and described with block diagrams, flow charts, or other graphical representations, it should be understood that the boxes, devices, systems, techniques, or methods described herein can be implemented with hardware, software, firmware, dedicated circuits or logic circuits, general hardware or controllers or other computing devices, or some combination thereof as non-limiting examples.
[0125] Therefore, it should be understood that at least some aspects of the exemplary embodiments of the present disclosure can be implemented in various components, such as integrated circuit chips and modules. Therefore, it should be understood that the exemplary embodiments of the present disclosure can be implemented in an apparatus, which is implemented as an integrated circuit, wherein the integrated circuit may include circuits (and possible firmware) for implementing at least one or more data processors, digital signal processors, baseband circuits, and radio frequency circuits, which circuits can be configured to operate in accordance with the exemplary embodiments of the present disclosure.
[0126] It should be understood that at least some aspects of the exemplary embodiments of the present disclosure can be implemented with computer executable instructions executed by one or more computers or other devices, such as one or more program modules. Typically, a program module includes routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types when run by a processor in a computer or other device. Computer executable instructions may be stored on a computer-readable medium, such as a hard disk, an optical disk, a removable storage medium, a solid-state memory, a random access memory (RAM), etc. Those skilled in the art will appreciate that the functions of the program modules may be combined or distributed in various embodiments as needed. In addition, the functions may be implemented in whole or in part with firmware or hardware equivalents (such as integrated circuits, field programmable gate arrays (FPGAs), etc.).
[0127] The present disclosure includes any novel feature or feature combination explicitly disclosed herein or any summary thereof. Those skilled in the art may make various modifications and adaptations to the aforementioned exemplary embodiments of the present disclosure when reading the above description and in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-restrictive and exemplary embodiments of the present disclosure.
Claims
1. A method (510) performed by a user equipment UE, comprising: receiving (512) edge related information sent by a server, wherein the edge related information indicates an edge application server EAS, and the EAS is serving or is to serve another UE paired with the UE; as well as A connection is created (514) with the EAS indicated by the edge-related information. 2 . The method according to claim 1 , wherein the edge-related information further indicates an edge platform EP associated with the EAS.
3. The method according to claim 1 or 2, wherein the server is a Central Application Server (CAS).
4. The method according to claim 3, further comprising: A request for the edge-related information is sent to the CAS, wherein the request indicates the other UE. The method according to claim 3 , wherein the edge-related information further indicates the other UE.
6. The method according to claim 5, further comprising: A message is sent to the CAS, wherein the message indicates that the edge-related information is received by the UE.
7. The method according to claim 1 or 2, wherein the server is a source EAS for the UE and another UE, and the EAS indicated by the edge-related information is a target EAS, and the UE and another UE are to switch from the source EAS to the target EAS.
8. The method according to claim 7, further comprising: A notification sent by the source EAS is received, wherein the notification indicates a status of an application context relocation (ACR) of the UE and another UE.
9. The method according to claim 8, further comprising: When the notification indicates that the ACR of the UE and the other UE is completed, communication with the other UE is performed using the created connection with the target EAS.
10. The method according to any one of claims 1 to 9, wherein the UE is a control station and the other UE is a remotely operated vehicle.
11. A user equipment UE (600), comprising: one or more processors (601); as well as one or more memories (602) comprising computer program code (603), The one or more memories (602) and the computer program code (603) are configured to, through the one or more processors (601), cause the UE (600) to at least: receiving edge related information sent by a server, wherein the edge related information indicates an edge application server EAS, and the EAS is serving or is to serve another UE paired with the UE; and A connection is established with the EAS indicated by the edge-related information.
12. The UE according to claim 11, wherein the one or more memories and the computer program code are configured to, through the one or more processors, cause the UE to perform the method according to any one of claims 2 to 10.
13. A computer readable medium carrying a computer program code (603) thereon, which, when executed on a computer, causes the computer to perform any step of the method according to any one of claims 1 to 10.
14. A method (520) performed by a central application server CAS, comprising: receiving (522) edge related information from an edge application server EAS, wherein the edge related information indicates that the EAS is serving or is to serve a user equipment UE; as well as The registration information of the UE is maintained (524) according to the edge related information, wherein the registration information of the UE indicates the service EAS of the UE. The method according to claim 14 , wherein the edge-related information further indicates an edge platform EP associated with the EAS.
16. The method according to claim 14 or 15, wherein maintaining the registration information of the UE according to the edge related information comprises: The registration information of the UE is generated according to the edge related information, wherein the registration information includes a registration identifier of the UE.
17. The method according to claim 16, further comprising: A registration identifier of the UE is sent to the EAS.
18. The method according to any one of claims 14 to 17, further comprising: pairing the UE with another UE; as well as Pairing information is sent to the EAS, wherein the pairing information indicates the UE and the other UE.
19. The method according to any one of claims 14 to 18, further comprising: The edge related information is sent to another UE paired with the UE.
20. The method according to claim 19, further comprising: A request for the edge-related information is received from the other UE, wherein the request indicates the UE.
21. The method according to claim 19 or 20, wherein when the other UE is authorized by the CAS, the edge related information is sent to the other UE.
22. The method according to claim 19, wherein the edge-related information further indicates the UE.
23. The method according to claim 19 or 22, further comprising: A message is received from the other UE, wherein the message indicates that the edge-related information is received by the other UE.
24. The method according to claim 14 or 15, wherein the EAS is a target EAS, the UE is to be handed over from a source EAS to the target EAS, and the received edge-related information includes a registration identifier of the UE.
25. The method according to claim 24, wherein maintaining the registration information of the UE according to edge related information comprises: The registration information of the UE is updated by changing a serving EAS of the UE from the source EAS to the target EAS according to the registration identifier of the UE.
26. The method according to claim 25, further comprising: The EAS is notified of an update of the registration information of the UE.
27. A central application server CAS (600), comprising: one or more processors (601); as well as one or more memories (602) comprising computer program code (603), The one or more memories (602) and the computer program code (603) are configured to, through the one or more processors (601), cause the CAS (600) to at least: receiving edge related information from an edge application server EAS, wherein the edge related information indicates that the EAS is serving or is to serve a user equipment UE; as well as The registration information of the UE is maintained according to the edge related information, wherein the registration information of the UE indicates a service EAS of the UE.
28. The CAS according to claim 27, wherein the one or more memories and the computer program code are configured to, through the one or more processors, cause the CAS to perform the method according to any one of claims 15 to 26.
29. A computer readable medium carrying computer program code (603) thereon, which, when executed on a computer, causes the computer to perform any of the steps of the method according to any one of claims 14 to 26.
30. A method (530) performed by an edge application server EAS, comprising: Sending (532) edge related information to a central application server CAS, wherein the edge related information indicates that the EAS is serving or is to serve a user equipment UE; as well as Information related to registration of the UE is received (534) from the CAS. The method according to claim 30 , wherein the edge-related information further indicates an edge platform EP associated with the EAS.
32. The method of claim 30 or 31, wherein the information related to the registration of the UE comprises a registration identifier of the UE.
33. The method according to any one of claims 30 to 32, further comprising: Pairing information is received from the CAS, wherein the pairing information indicates the UE and another UE paired with the UE.
34. The method according to claim 30 or 31, wherein the EAS is a target EAS, the UE is to be handed over from a source EAS to the target EAS, and the edge-related information sent to the CAS includes a registration identifier of the UE.
35. The method of claim 34, further comprising: An application context of the UE and another UE paired with the UE is received from the source EAS, wherein the application context includes a registration identifier of the UE and / or pairing information indicating the UE and the other UE.
36. The method according to claim 34 or 35, wherein the information related to the registration of the UE indicates that the registration information of the UE at the CAS is updated by changing the serving EAS of the UE to the target EAS.
37. The method according to claim 33 or 35, further comprising: A connection is created with the other UE to support communication between the UE and the other UE.
38. An edge application server EAS (600), comprising: one or more processors (601); as well as one or more memories (602) comprising computer program code (603), The one or more memories (602) and the computer program code (603) are configured to, through the one or more processors (601), cause the EAS (600) to at least: Sending edge related information to a central application server CAS, wherein the edge related information indicates that the EAS is serving or is to serve a user equipment UE; as well as Information related to registration of the UE is received from the CAS.
39. The EAS of claim 38, wherein the one or more memories and the computer program code are configured to, via the one or more processors, cause the EAS to perform the method of any one of claims 31 to 37.
40. A computer readable medium carrying computer program code (603) thereon, which, when executed on a computer, causes the computer to perform any step of the method according to any one of claims 30 to 37.
41. A method (540) performed by an edge application server EAS, comprising: When another UE paired with the user equipment UE switches from the EAS to another EAS, sending (542) edge related information to the UE, wherein the edge related information indicates that the other EAS is serving or is to serve the other UE; as well as The application context of the UE and another UE is transmitted (544) to the another EAS, wherein the application context includes: a registration identifier of the another UE and / or pairing information indicating the UE and another UE.
42. The method of claim 41, wherein the edge-related information further indicates an edge platform EP associated with the other EAS.
43. The method according to claim 41 or 42, wherein a registration identifier of the other UE is provided by a central application server (CAS) when the other UE registers to the CAS.
44. The method according to any one of claims 41 to 43, further comprising: A notification is sent to the UE, wherein the notification indicates a status of an application context relocation (ACR) of the UE and another UE.
45. An edge application server EAS (600), comprising: one or more processors (601); as well as one or more memories (602) comprising computer program code (603), The one or more memories (602) and the computer program code (603) are configured to, via the one or more processors (601), cause the EAS (600) to at least: When another UE paired with the user equipment UE switches from the EAS to another EAS, sending edge related information toward the UE, wherein the edge related information indicates that the other EAS is serving or is to serve the other UE; as well as The application context of the UE and another UE is transmitted to the another EAS, wherein the application context includes: a registration identifier of the other UE, and / or pairing information indicating the UE and the other UE.
46. The EAS of claim 45, wherein the one or more memories and the computer program code are configured to, via the one or more processors, cause the EAS to perform the method of any one of claims 42 to 44.
47. A computer readable medium carrying computer program code (603) thereon, which, when executed on a computer, causes the computer to perform any step of the method according to any one of claims 41 to 44.
