Method and apparatus for ACR scene selection

Abstract

The embodiment of the invention provides a method and device for ACR scene selection. A method performed by a first network node includes deciding to perform application context relocation (ACR). The method further includes sending the first message to the second network node. The first message includes information for requesting the second network node to select at least one ACR scenario to be used in the next ACR.

Description

Technical Field

[0001] Non-limiting and exemplary embodiments of the present disclosure generally relate to the field of communication technology, and in particular to methods and apparatus for application context relocation (ACR) scene selection. Background Art

[0002] This section introduces various aspects that may help to better understand the present disclosure. Therefore, the statements in this section should be read in this light, and should not be understood as an admission about what is or is not in the prior art.

[0003] Edge computing is a concept that enables services to be hosted close to the service consumers and provides benefits such as efficient service delivery with significantly reduced end-to-end latency and reduced load on the transport network. The benefits of edge computing will enhance the promise of 5G (fifth generation) and expand prospects for several new and enhanced use cases, including virtual and augmented reality, Internet of Things (IoT), Industrial IoT, autonomous driving, real-time multiplayer gaming, etc.

[0004] The 3rd Generation Partnership Project (3GPP) TS23.558 V17.4.0 (the disclosure of which is incorporated herein by reference in its entirety) specifies the application layer architecture, processes, and information flows required to enable edge applications on 3GPP networks. It includes architectural requirements for enabling edge applications, application layer architectures that meet the architectural requirements, and processes for enabling deployment of edge applications.

[0005] Figure 1a A reference point representation of an architecture for edge-enabled applications according to an embodiment of the present disclosure is shown. Figure 1a Same as Figure 6.2-4 of 3GPP TS23.558V17.4.0. The Edge Data Network (EDN) is a local data network. One or more edge application servers and edge enabler servers are included in the EDN. The edge configuration server provides configuration related to the EES, including detailed information of the edge data network hosted (edge ​​enabler server). The UE contains one or more application clients (AC) and edge enabler clients (EEC). One or more edge application servers, edge enabler servers and edge configuration servers can interact with the 3GPP core network.

[0006] Functional entities include:

[0007] Edge Enabler Server (EES): EES provides the support functions required for EAS and EEC, such as EEC registration, EAS discovery, and network APIs for EAS and service continuity support.

[0008] Edge Enabler Client (EEC): The EEC provides support functions required by one or more ACs, such as retrieval and provision of configuration information to enable application data services, and EAS discovery.

[0009] Edge Configuration Server (ECS): ECS provides the support functions required for EEC to connect with EES, such as providing edge configuration information to EEC, and EES discovery.

[0010] Application Client (AC): AC is an application residing in the UE that performs client functions.

[0011] Edge Application Server (EAS): EAS is an application server that resides in the EDN and performs server functions. ACs connect to EAS to utilize the services of applications with the benefits of edge computing.

[0012] NOTE: EDGE reference point explanation can be found in clause 6.5 of 3GPP TS 23.558 V17.4.0.

[0013] 3GPP TR 23.700-98 V1.1.1, the disclosure of which is incorporated herein by reference in its entirety, is a technical report that documents research on an enhanced architecture for enabling edge applications on 3GPP networks.

[0014] Figure 1b A reference point representation of an architecture for edge-enabled applications according to another embodiment of the present disclosure is shown. Figure 1b Same as Figure 6.2.1-1 of 3GPP TR 23.700-98 V1.1.1.

[0015] Compared with the 3GPP TS23.558V17.4.0 edge application (EDGEAPP) architecture for non-roaming scenarios, a new reference point EDGE-10 is defined between ECSs.

[0016] Clause 8.8.2 of 3GPP TS23.558 V17.4.0 describes different ACR scenarios in service continuity. For example, ACR scenarios may include ACR triggered by the user equipment (UE) (e.g., triggered by EEC) and ACR scenarios triggered by the data network (DN) side (i.e., triggered by S-EAS (source EAS) or S-EES (source EES)). Summary of the invention

[0017] This Summary is provided in a simplified form to introduce selected concepts that are further described below in the Detailed Description. 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.

[0018] As described in 3GPP TS 23.558 V17.4.0 clause 8.8.2, AC, EEC, EES, and EAS may support multiple ACR scenarios and may trigger these ACR scenarios simultaneously.

[0019] Supporting and using multiple ACR scenes in the system can facilitate timely ACR detection, but it also introduces complexity in the system to handle, for example, race conditions. It is also desirable to have ACR scene selection to narrow the number of ACR scenes used (e.g., select only one ACR scene) to reduce complexity.

[0020] Key Issue (KI) #19 in 3GPP TR 23.700-98 V1.1.1 also describes an ACR scenario combination with one or more ACR scenarios to be used, as shown below.

[0021] Multiple ACR scenarios are specified in 3GPP TS 23.558 [2] clause 8.8. An application can utilize one or more ACR scenarios. The edge enabler layer should enable applications to utilize different combinations of ACR scenarios (e.g., only one ACR scenario is allowed or several ACR scenarios are allowed).

[0022] Open issues:

[0023] - Whether and how can EEL (Edge Enabler Layer) support determining the ACR scenario for an AC?

[0024] Solution #19 of 3GPP TR 23.700-98 V1.1.1 mentions that the EES makes the selection of the ACR scenario. Solution #35 of 3GPP TR 23.700-98 V1.1.1 mentions that the EEC makes the selection of the ACR scenario. They are suitable for the initial EAS discovery triggered by the EEC and the T-EAS discovery triggered by the EEC during the ACR.

[0025] No solution is provided for DN-side triggered T-EAS discovery during ACR, where the S-EAS and S-EES communicate with each other to determine the T-EAS.

[0026] To overcome or mitigate at least one of the above-referenced problems or other problems, an improved solution for ACR scene selection may be desired.

[0027] In an embodiment, during T-EAS (target EAS) discovery, the T-EAS service continuity support capabilities (e.g., supported ACR scenarios) are considered together with the service continuity support capabilities of AC, EEC, and EES. Then, the ACR scenario selection can be further decided between S-EAS and S-EES, and the final result needs to be notified to EEC and T-EAS.

[0028] In a first aspect of the present disclosure, a method performed by a first network node is provided. The method may include deciding to perform application context relocation (ACR). The method may also include sending a first message to a second network node. The first message may include information for requesting the second network node to select at least one ACR scene to be used in a next ACR.

[0029] In an embodiment, at least one ACR scenario to be used in the next ACR may be supported by an application client (AC), an edge enabler client (EEC), a target edge application server (EAS), and a target edge enabler server (EES).

[0030] In an embodiment, the first network node may comprise a source EES and the second network node may comprise a target EES.

[0031] In an embodiment, the method may further include sending a fourth message to the EEC. The fourth message may include information about at least one ACR scenario to be used in the next ACR.

[0032] In an embodiment, the fourth message may be a target information notification message.

[0033] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0034] In a second aspect of the present disclosure, a method performed by a second network node is provided. The method may include receiving a first message from a first network node. The first message may include information for requesting the second network node to select at least one ACR scene to be used in a next ACR. The method may also include selecting at least one ACR scene to be used in the next ACR.

[0035] In an embodiment, at least one ACR scenario to be used in the next ACR may be supported by the AC, the EEC, the target EAS, and the target EES.

[0036] In an embodiment, the first network node may comprise a source EES and the second network node may comprise a target EES.

[0037] In an embodiment, the method may further include sending a sixth message to the EEC. The sixth message may include information about at least one ACR scene to be used in the next ACR. The method may further include sending a ninth message to the target EAS. The ninth message may include information about at least one ACR scene to be used in the next ACR.

[0038] In an embodiment, the sixth message may be a target information notification message.

[0039] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0040] In an embodiment, when the first network node includes a source EES and the second network node includes a target EES, the method may further include sending a message including information about at least one ACR scenario to be used in a next ACR to the first network node.

[0041] In a third aspect of the present disclosure, a method performed by a target EAS is provided. The method may include receiving an eighth message from the target EES. The eighth message may include information about at least one ACR scene to be used in a next ACR.

[0042] In an embodiment, the method may further include storing information about at least one ACR scenario to be used in the next ACR.

[0043] In an embodiment, at least one ACR scenario to be used in the next ACR may be supported by the AC, the EEC, the target EAS, and the target EES.

[0044] In an embodiment, the method may further include sending an ACR scene selection subscription request to the target EES. The method may further include receiving an ACR scene selection subscription response from the target EES.

[0045] In an embodiment, the eighth message may be an ACR selection notification message.

[0046] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0047] In a fourth aspect of the present disclosure, a method performed by an EEC is provided. The method may include receiving a message including information about at least one ACR scene to be used in a next ACR from an EES in an ACR scene. The method also includes storing information about at least one ACR scene to be used in a next ACR.

[0048] In an embodiment, the method may further include sending a message including information about at least one ACR scenario to be used in a next ACR to the AC.

[0049] In an embodiment, at least one ACR scenario to be used in the next ACR may be supported by the AC, the EEC, the target EAS, and the target EES.

[0050] In an embodiment, the message may be a target information notification message.

[0051] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0052] In a fifth aspect of the present disclosure, a first network node is provided. The first network node may include a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The first network node is operable to decide to perform application context relocation (ACR). The first network node is further operable to send a first message to a second network node. The first message may include information for requesting the second network node to select at least one ACR scene to be used in the next ACR.

[0053] In a sixth aspect of the present disclosure, a second network node is provided. The second network node includes a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The second network node is operable to receive a first message from the first network node. The first message may include information for requesting the second network node to select at least one ACR scene to be used in the next ACR. The second network node is further operable to select at least one ACR scene to be used in the next ACR.

[0054] In a seventh aspect of the present disclosure, a target EAS is provided. The target EAS includes a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The target EAS is operable to receive an eighth message from the target EES. The eighth message may include information about at least one ACR scene to be used in the next ACR.

[0055] In an eighth aspect of the present disclosure, an EEC is provided. The EEC includes a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The EEC is operable to receive a message including information about at least one ACR scene to be used in the next ACR from an EES in an ACR scene. The EEC is further operable to store information about at least one ACR scene to be used in the next ACR.

[0056] In another aspect of the present disclosure, a first network node is provided. The first network node may include a decision module configured to decide to perform application context relocation (ACR). The first network node may also include a first sending module configured to send a first message to a second network node. The first message may include information for requesting the second network node to select at least one ACR scene to be used in the next ACR.

[0057] In an embodiment, the first network node may further include a second sending module configured to send a fourth message to the EEC. The fourth message may include information about at least one ACR scenario to be used in the next ACR.

[0058] In another aspect of the present disclosure, a second network node is provided. The second network node may include a receiving module configured to receive a first message from the first network node. The first message may include information for requesting the second network node to select at least one ACR scene to be used in the next ACR. The second network node may also include a selection module configured to select at least one ACR scene to be used in the next ACR.

[0059] In an embodiment, the second network node may further include a first sending module configured to send a sixth message to the EEC. The sixth message may include information about at least one ACR scenario to be used in a next ACR.

[0060] In an embodiment, the second network node may further include a second sending module configured to send a ninth message to the target EAS. The ninth message may include information about at least one ACR scenario to be used in the next ACR.

[0061] In an embodiment, when the first network node may include a source EES and the second network node may include a target EES, the second network node may further include a third sending module configured to send a message including information about at least one ACR scenario to be used in the next ACR to the first network node.

[0062] In another aspect of the present disclosure, a target EAS is provided. The target EAS may include a first receiving module configured to receive an eighth message from the target EES. The eighth message may include information about at least one ACR scene to be used in a next ACR.

[0063] In an embodiment, the target EAS may further include a storage module configured to store information about at least one ACR scenario to be used in the next ACR.

[0064] In an embodiment, the target EAS may further include a sending module configured to send an ACR scene selection subscription request to the target EES.

[0065] In an embodiment, the target EAS may further include a second receiving module configured to receive an ACR scenario selection subscription response from the target EES.

[0066] In another aspect of the present disclosure, an EEC is provided. The EEC may include a receiving module configured to receive a message from an EES in an ACR scene. The message may include information about at least one ACR scene to be used in the next ACR. The EEC may also include a storage module configured to store information about at least one ACR scene to be used in the next ACR.

[0067] In an embodiment, the EEC may further include a transmitting module configured to transmit a message including information about at least one ACR scenario to be used in a next ACR to the AC.

[0068] In another aspect of the present disclosure, a computer program product is provided, comprising instructions, which, when executed by at least one processor, cause the at least one processor to perform a method according to any one of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0069] In another aspect of the present disclosure, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed by at least one processor, the instructions cause the at least one processor to perform a method according to any one of the first aspect, the second aspect, the third aspect or the fourth aspect.

[0070] In another aspect of the present disclosure, a communication system including a host computer is provided. The host computer includes a processing circuit configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes a network node (e.g., the first network node or the second network node described above) and / or a terminal device (e.g., the EEC described above).

[0071] In an embodiment of the present disclosure, the system further includes a terminal device. The terminal device is configured to communicate with the network node.

[0072] In an embodiment of the present disclosure, a processing circuit of a host computer is configured to execute a host application to provide user data; and a terminal device includes a processing circuit configured to execute a client application associated with the host application.

[0073] In another aspect of the present disclosure, a communication system is provided, which includes a host computer and a network node. The host computer includes a communication interface, which is configured to receive user data originating from a transmission from a terminal device. The transmission is from the terminal device to the network node. The terminal device is the above-mentioned EEC.

[0074] In an embodiment of the present disclosure, the processing circuit of the host computer is configured to execute a host application. The terminal device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0075] In another aspect of the present disclosure, a method implemented in a communication system is provided, the communication system may include a host computer, a network node and a terminal device. The method may include providing user data at the host computer. Optionally, the method may include initiating a transmission carrying user data to the terminal device at the host computer via a cellular network including the network node.

[0076] In another aspect of the present disclosure, a communication system including a host computer is provided. The host computer may include processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network may include a network node having a radio interface and processing circuitry.

[0077] In another aspect of the present disclosure, a method implemented in a communication system is provided, which may include a host computer, a network node, and a terminal device. The method may include providing user data at the host computer. Alternatively, the method may include initiating a transmission carrying user data to the terminal device via a cellular network including the network node at the host computer. The terminal device may perform any steps of the method according to the fifth and sixth aspects of the present disclosure.

[0078] In another aspect of the present disclosure, a communication system including a host computer is provided. The host computer may include a processing circuit configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The terminal device may include a radio interface and a processing circuit. The processing circuit of the terminal device may be configured to perform any steps of the method according to the fifth and sixth aspects of the present disclosure.

[0079] In another aspect of the present disclosure, a method implemented in a communication system is provided, the communication system may include a host computer, a network node and a terminal device. The method may include, at the host computer, receiving user data sent from the terminal device to the network node, the terminal device may perform any steps of the method according to the fifth aspect and the sixth aspect of the present disclosure.

[0080] In another aspect of the present disclosure, a communication system including a host computer is provided. The host computer may include a communication interface configured to receive user data originating from a transmission from a terminal device to a network node. The terminal device may include a radio interface and a processing circuit. The processing circuit of the terminal device may be configured to perform any steps of the method according to the fifth and sixth aspects of the present disclosure.

[0081] In another aspect of the present disclosure, a method implemented in a communication system is provided, which may include a host computer, a network node, and a terminal device. The method may include, at the host computer, receiving from the network node user data originating from a transmission that the network node has received from the terminal device.

[0082] In another aspect of the present disclosure, a communication system is provided, which may include a host computer. The host computer may include a communication interface configured to receive user data originating from a transmission from a terminal device to a network node. The network node may include a radio interface and a processing circuit.

[0083] The embodiments herein may provide many advantages, and the following is a non-exhaustive list of examples of advantages. In some embodiments herein, it may address KI#19 of 3GPP TR 23.700-98V1.1.1 in the ACR scenario determined by S-EAS, which allows S-EAS to determine one or more ACR scenarios or request S-EES to determine one or more ACR scenarios to be used. In some embodiments herein, it may address KI#19 of 3GPP TR 23.700-98V1.1.1 in the ACR scenario executed by S-EES, which allows S-EES to determine one or more ACR scenarios to be used. In some embodiments herein, the proposed solution provides an active way to reduce the system complexity for subsequent ACRs during ACRs triggered on the data network side. In some embodiments herein, during EAS discovery, the ideal situation would be that AC, EEC, EES, and EAS support and only support exactly the same ACR scenarios. But in reality, it may be that a suitable T-EAS (meeting the KPI (key performance indicator) requirements of AC) supports more ACR scenarios than S-EAS and S-EES or AC and EEC. The ACR scenario selection solution determined by S-EES is then used to make an ACR scenario selection for the appropriate T-EAS and notify the corresponding entity of the selection. The embodiments herein are not limited to the above features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] The above and other aspects, features and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description with reference to the accompanying drawings, by way of example, in which like reference numerals or letters are used to refer to similar or equivalent elements. The accompanying drawings are shown to facilitate a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein:

[0085] Figure 1a A reference point representation of an architecture for edge-enabled applications according to an embodiment of the present disclosure is shown;

[0086] Figure 1b shows a reference point representation of an architecture for edge-enabled applications according to another embodiment of the present disclosure;

[0087] Figure 2a Schematically illustrates a high-level architecture in a fifth generation network according to an embodiment of the present disclosure;

[0088] Figure 2b The system architecture in a 4G network according to an embodiment of the present disclosure is schematically shown;

[0089] Figure 3a A flowchart of a method according to an embodiment of the present disclosure is shown;

[0090] Figure 3b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0091] Figure 3c A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0092] Figure 3d A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0093] Figure 3e A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0094] Figure 3f A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0095] Figure 3g A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0096] Figure 4a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0097] Figure 4b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0098] Figure 4c A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0099] Figure 4d A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0100] Figure 5a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0101] Figure 5b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0102] Figure 5c A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0103] Figure 6a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0104] Figure 6b A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0105] Figure 6cA flowchart showing a method according to another embodiment of the present disclosure is shown;

[0106] Figure 7a A flowchart showing a method according to another embodiment of the present disclosure is shown;

[0107] Figure 7b A flowchart of ACR scene selection determined by S-EAS according to an embodiment of the present disclosure is shown;

[0108] Figure 7c A flowchart of ACR scene selection for S-EAS request according to an embodiment of the present disclosure is shown;

[0109] Figure 7d A flowchart of ACR scene selection determined by S-EES according to an embodiment of the present disclosure is shown;

[0110] Figure 8a is a block diagram illustrating an apparatus suitable for practicing some embodiments of the present disclosure;

[0111] Figure 8b is a block diagram illustrating a first network node according to an embodiment of the present disclosure;

[0112] Figure 8c is a block diagram illustrating a second network node according to an embodiment of the present disclosure;

[0113] Figure 8d is a block diagram illustrating a target EES according to another embodiment of the present disclosure;

[0114] Figure 8e is a block diagram illustrating a target EAS according to another embodiment of the present disclosure;

[0115] Figure 8f is a block diagram illustrating an EEC according to another embodiment of the present disclosure;

[0116] Figure 8g is a block diagram showing an AC according to another embodiment of the present disclosure;

[0117] Fig. 9 is a schematic diagram illustrating a wireless network according to some embodiments;

[0118] Fig.10 is a schematic diagram illustrating a user equipment according to some embodiments;

[0119] Fig.11 is a schematic diagram illustrating a virtualized environment according to some embodiments;

[0120] Fig.12 is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments;

[0121] Fig.13 is a schematic diagram illustrating a host computer communicating with a user device via a base station over a partially wireless connection according to some embodiments;

[0122] Fig.14 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0123] Fig.15 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments;

[0124] Fig.16 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments; and

[0125] Fig.17 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments. DETAILED DESCRIPTION

[0126] Embodiments of the present disclosure are described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed only for the purpose of enabling those skilled in the art to better understand and thus realize the present disclosure, rather than suggesting any limitation on the scope of the present disclosure. References to features, advantages or similar language throughout the specification do not mean that all features and advantages that can be implemented with the present disclosure should be in or in any single embodiment of the present disclosure. On the contrary, the language referring to features and advantages should be understood to mean that specific features, advantages or characteristics described in conjunction with the embodiments are included in at least one embodiment of the present disclosure. In addition, in one or more embodiments, the features, advantages and characteristics described in the present disclosure may be combined in any suitable manner. Those skilled in the relevant art will recognize that the present disclosure may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in certain embodiments, and the additional features and advantages may not exist in all embodiments of the present disclosure.

[0127] As used herein, the term "network" refers to a network that complies with any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), and other wireless networks. A CDMA network can implement radio technologies such as Universal Terrestrial Radio Access (UTRA). UTRA includes other variants of WCDMA and CDMA. A TDMA network can implement radio technologies such as Global System for Mobile Communications (GSM). An OFDMA network can implement radio technologies such as Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, Ad-hoc networks, wireless sensor networks, etc. In the following description, the terms "network" and "system" may be used interchangeably. In addition, communication between two devices in a network may be performed according to any suitable communication protocol, including but not limited to communication protocols defined by standard organizations such as 3GPP. For example, the communication protocol may include first generation (1G), 2G, 3G, 4G, 4.5G, 5G communication protocols and / or any other protocol currently known or developed in the future.

[0128] The term "network node" or "network node" refers to any suitable network function (NF) that can be implemented in a (physical or virtual) network element of a communication network. For example, a network function can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on an appropriate platform (e.g., on a cloud infrastructure). For example, a 5G system (5GS) may include multiple NFs, such as an access and mobility function (AMF), a session management function (SMF), an authentication service function (AUSF), a unified data management (UDM), a policy control function (PCF), an application function (AF), a network open function (NEF), a user plane function (UPF) and a network repository function (NRF), a radio access network (RAN), a service communication agent (SCP), a network data analysis function (NWDAF), a network slice selection function (NSSF), a network slice specific authentication and authorization function (NSSAAF), etc. For example, a 4G system (e.g., LTE) may include a mobility management entity (MME), a home subscriber server (HSS), a PCRF (Policy and Charging Rules Function), a packet data network gateway (PGW), a PGW control plane (PGW-C), a serving gateway (SGW), a SGW control plane (SGW-C), an E-UTRAN Node B (eNB), etc. In other embodiments, the network functions may include different types of NFs, e.g., depending on the specific network.

[0129] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. By way of example and not limitation, a terminal device refers to a mobile terminal, a user equipment (UE) or other suitable device. A UE may be, for example, a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). A terminal device may include, but is not limited to, a portable computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable device, a personal digital assistant (PDA), a portable computer, a desktop computer, a wearable terminal device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless customer premises equipment (CPE), etc. In the following description, the terms "terminal device", "terminal", "user equipment" and "UE" may be used interchangeably. As an example, a terminal device may represent a UE configured to communicate in accordance with one or more communication standards (e.g., 3GPP's LTE standard or NR standard) issued by 3GPP (3rd Generation Partnership Project). As used herein, a "user equipment" or "UE" may not necessarily have a "user" in terms of a human user who owns and / or operates the associated device. In some embodiments, a terminal device may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a communication network, a terminal device may be designed to send information to the network according to a predetermined schedule. Alternatively, a UE may represent a device that is intended to be sold to a human user or operated by a human user but may not initially be associated with a specific human user.

[0130] As another example, in an Internet of Things (IoT) scenario, a terminal device may represent a machine or other device that performs monitoring and / or measurement, and sends the results of such monitoring and / or measurement to another terminal device and / or network device. In this case, the terminal device may be a machine-to-machine (M2M) device, which may be referred to as a machine type communication (MTC) device in the 3GPP context. As a specific example, the terminal device may be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., electricity meters), industrial machinery, or household or personal appliances, such as refrigerators, televisions, personal wearable devices (e.g., watches), etc. In other scenarios, a terminal device may represent a vehicle or other device that is capable of monitoring and / or reporting its operating status or other functions related to its operation.

[0131] References in the specification to "one embodiment," "an embodiment," "an exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not necessarily every embodiment includes the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is claimed that it is within the knowledge of those skilled in the art to affect that feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0132] It should be understood that although the terms "first" and "second" etc. 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 element. For example, without departing from the scope of the exemplary embodiments, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more associated listed terms.

[0133] As used herein, the phrase "at least one of A and B" or "at least one of A or B" should be understood to mean "only A, only B, or both A and B". The phrase "A and / or B" should be understood to mean "only A, only B, or both A and B".

[0134] The terms used herein are for the purpose of describing specific embodiments only and are not intended to limit the example embodiments. Unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" as used herein are also intended to include the plural forms. It will be further understood that when used herein, the terms "include", "comprise", "have", "have", "contain" and / or "cover" specify the presence of the 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.

[0135] Note that these terms used in this article are only used to facilitate description and to distinguish between nodes, devices or networks, etc. As technology develops, other terms with similar / same meanings may also be used.

[0136] In the following description and claims, unless defined otherwise, 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 disclosure belongs.

[0137] Although the subject matter described herein can be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are directed to systems that conform to Figure 2a , Figure 2bFor simplicity, the communication system of the exemplary system architecture shown is described. Figure 2a , Figure 2b The system architecture of only depicts some exemplary elements. In practice, the communication system may further include any additional elements suitable for supporting communication between terminal devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). The communication system may provide communication and various types of services to one or more terminal devices to facilitate the terminal devices to access and / or use services provided by or via the communication system.

[0138] Figure 2a The high-level architecture in the fifth generation network according to an embodiment of the present disclosure is schematically shown. For example, the fifth generation network may be 5GS. Figure 2a The architecture is the same as Figure 4.2.3-2 described in 3GPP TS 23.501 V17.2.0, the disclosure of which is incorporated herein by reference in its entirety. Figure 2a The system architecture may include some exemplary elements, such as AUSF, AMF, DN (data network), NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP (service communication agent), NSSAAF (network slice specific authentication and authorization function), NSACF (network slice admission control function), etc.

[0139] According to an exemplary embodiment, Figure 2a As shown in , the UE can establish a signaling connection with the AMF through reference point N1. The signaling connection enables NAS (non-access stratum) signaling exchange between the UE and the core network, including a signaling connection between the UE and the (R)AN and an N2 connection between the (R)AN and the AMF for the UE. The (R)AN can communicate with the UPF through reference point N3. The UE establishes a protocol data unit (PDU) session to the DN (data network, such as an operator network or the Internet) through the UPF through reference point N6.

[0140] like Figure 2a As further shown in FIG. 1 , the exemplary system architecture also includes some reference points, such as N1, N2, N3, N4, N6, N9 and N15, which can support the interaction between NF services in NF. For example, these reference points can be implemented through corresponding NF service-based interfaces and by specifying some NF service consumers and providers and their interactions in order to perform specific system processes. The PCF provides the AM-related policies for the registered UE to the AMF via the N15 interface. The AMF can obtain the AM policy during the AM policy association establishment / modification process.

[0141] Figure 2a The various NFs shown in the figure may be responsible for functions such as session management, mobility management, authentication, security, etc. AUSF, AMF, DN, NEF, NRF, NSSF, PCF, SMF, UDM, UPF, AF, UE, (R)AN, SCP, NSACF may include, for example, the functions defined in clause 6.2 of 3GPP TS23.501 V17.2.0.

[0142] Figure 2b The system architecture in a 4G network according to an embodiment of the present disclosure is schematically shown, which is the same as FIG. 4.2-1a of 3GPP TS23.682 V17.2.0, the disclosure of which is incorporated herein by reference in its entirety. Figure 2b The system architecture may include some exemplary elements, such as service capability server (SCS), application server (AS), SCEF (service capability exposure function), HSS, UE, RAN (radio access network), SGSN (serving GPRS (general packet radio service) support node), MME, MSC (mobile switching center), S-GW (serving gateway), GGSN / P-GW (gateway GPRS support node / PDN (packet data network) gateway), MTC-IWF (machine type communication-interworking function), CDF / CGF (charging data function / charging gateway function), MTC-AAA (machine type communication-authentication, authorization and charging), SMS-SC / GMSC / IWMSC (short message service-service center / gateway MSC / interworking MSC), IP-SM-GW (Internet Protocol Short Message Gateway). Figure 2b The network elements and interfaces shown in may be the same as the corresponding network elements and interfaces described in 3GPP TS 23.682 V17.2.0.

[0143] The system architecture shows an architecture in which a UE for MTC is connected to a 3GPP network (UTRAN (Universal Terrestrial Radio Access Network), E-UTRAN (Evolved UTRAN), GERAN (GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network), etc.) via a Um / Uu / LTE-Uu interface. The system architecture also shows the opening of 3GPP network service capabilities to SCS and AS.

[0144] like Figure 2b As further shown in , the exemplary system architecture also includes various reference points.

[0145] Tsms: A reference point used by entities outside the 3GPP network to communicate with UEs for MTC via SMS (Short Message Service).

[0146] Tsp: Reference point used by the SCS to communicate with the MTC-IWF related control plane signaling.

[0147] T4: Reference point used between MTC-IWF and SMS-SC in HPLMN.

[0148] T6a: Reference point used between SCEF and serving MME.

[0149] T6b: Reference point used between SCEF and serving SGSN.

[0150] T8: Reference point used between SCEF and SCS / AS.

[0151] S6m: Reference point used by the MTC-IWF to query the HSS / HLR (Home Location Register).

[0152] S6n: Reference point used by MTC-AAA to query HSS / HLR.

[0153] S6t: Reference point used between SCEF and HSS.

[0154] SGs: Reference point used between MSC and MME.

[0155] Gi / SGi: Reference point used between GGSN / P-GW and application server and between GGSN / P-GW and SCS.

[0156] Rf / Ga: Reference point used between MTC-IWF and CDF / CGF.

[0157] Gd: Reference point used between SMS-SC / GMSC / IWMSC and SGSN.

[0158] SGd: Reference point used between SMS-SC / GMSC / IWMSC and MME.

[0159] E: Reference point used between SMS-SC / GMSC / IWMSC and MSC.

[0160] Figure 3a A flowchart of a method according to an embodiment of the present disclosure is shown, and the method can be performed by a device implemented in a first network node, or a device implemented at a first network node, or a device implemented as a first network node, or a device communicatively coupled to a first network node. Therefore, the device can provide components or modules for implementing various parts of the method 300, and components or modules for implementing other processes in combination with other components.

[0161] At block 302, a first network node may decide to perform application context relocation (ACR). For example, ACR may be used for AC.

[0162] The first network node may be any suitable network node in the ACR scenario. For example, the first network node may be an S-EES (source EES) or an S-EAS (source EAS).

[0163] In an embodiment, the first network node may be an S-EES. For example, as described in clause 8.8.2.5 of 3GPP TS 23.558 V17.4.0, in the ACR performed by the S-EES, the S-EES may decide to perform the ACR.

[0164] In an embodiment, the first network node may be an S-EAS. For example, as described in clause 8.8.2.4 of 3GPP TS 23.558 V17.4.0, in an S-EAS-decided ACR scenario, the S-EAS may decide to perform ACR.

[0165] At block 304, the first network node may send a first message to the second network node. The first message may include information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.

[0166] In an embodiment, the first network node may select at least one ACR scenario to be used in the next ACR.

[0167] The first message may be any suitable message, such as an existing message or a new message. For example, the first message may be any suitable existing message in a corresponding ACR scenario as described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.

[0168] In an embodiment, the first message is a Selected Target EAS Declaration message as described in 3GPP TS 23.558 V17.4.0.

[0169] The second network node may be any suitable network node in the ACR scenario. For example, the second network node may be an S-EES (source EES) or a T-EES (target EES).

[0170] For example, when the first network node is an S-EES or an S-EAS, the first network node may select at least one ACR scenario to be used in the next ACR.

[0171] For example, when the first network node is an S-EAS, the first network node may send a first message to a second network node (eg, an S-EES).

[0172] For example, when the first network node is an S-EES, the first network node may send a first message to a second network node (eg, a T-EES).

[0173] In an embodiment, at least one ACR scenario to be used in a next ACR is supported by an application client (AC), an edge enabler client (EEC), a target edge application server (EAS), and a target edge enabler server (EES).

[0174] The first network node may obtain or know the ACR scenarios supported in the service continuity support capabilities in AC, EEC, T-EES (target EES), and T-EAS (target EAS). For example, S-EES may include AC service continuity support capabilities (as part of the AC profile) and EEC service continuity support capabilities in a T-EAS discovery request sent to one or more T-EES. The one or more T-EASs discovered are the result of filtering that takes into account the ACR scenarios commonly supported in the service continuity support capabilities in AC, EEC, T-EES, and T-EAS. The first network node (e.g., S-EAS or S-EES) may select one or more ACR scenarios based on the ACR scenarios supported by the selected T-EAS.

[0175] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery (e.g., as described in clause 8.8.2.2 of 3GPP TS23.558V17.4.0), ACR performed by the EEC via the source EES (e.g., as described in clause 8.8.2.3 of 3GPP TS23.558V17.4.0), ACR determined by the source EAS (e.g., as described in clause 8.8.2.4 of 3GPP TS23.558V17.4.0), ACR performed by the source EES (e.g., as described in clause 8.8.2.5 of 3GPPTS23.558V17.4.0), or ACR performed by the EEC via the target EES (e.g., as described in clause 8.8.2.6 of 3GPPTS23.558V17.4.0).

[0176] It is worth noting that when the next ACR is determined by the first network node, the first network node may also perform the proposed method according to various embodiments.

[0177] In an embodiment, when the first network node is S-EES and the second network node is T-EES, after T-EES selects at least one ACR scene to be used in the next ACR, T-EES may send a message to EEC and T-EAS. The message may include information about at least one ACR scene to be used in the next ACR.

[0178] Figure 3b A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a first network node, or a device implemented at a first network node, or a device implemented as a first network node, or a device communicatively coupled to a first network node. Therefore, the device can provide components or modules for implementing various parts of the method 310, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0179] In this embodiment, the first network node may include an origin edge application server (EAS), and the first network node may select at least one ACR scenario to be used in a next ACR.

[0180] At block 312, the first network node may send a first EAS discovery request to a source edge enabler server (EES).

[0181] The EAS discovery request may be the same as the EAS discovery request as described in 3GPP TS 23.558 V17.4.0.

[0182] At block 314, the first network node may receive a first EAS discovery response from the source EES. The first EAS discovery response may include information about at least one candidate target EAS. The at least one candidate target EAS is a result of filtering that considers at least one commonly supported ACR scenario in the service continuity support capability among the AC, EEC, target EAS, and target EES.

[0183] For example, using the improved T-EAS discovery process, the S-EES does not need to include its own service continuity support capabilities and the S-EAS service continuity support capabilities. Instead, the S-EES includes the AC service continuity support capabilities (as part of the AC profile) and the EEC service continuity support capabilities in the T-EAS discovery request sent to one or more T-EES. The one or more T-EASs discovered are the result of filtering that takes into account the ACR scenarios that are commonly supported in the service continuity support capabilities among AC, EEC, T-EES, and T-EAS.

[0184] At block 316, the first network node may select a target EAS from the at least one candidate target EAS. The first network node may select a target EAS from the at least one candidate target EAS in a variety of ways, as the present disclosure is not limited in this regard.

[0185] Figure 3c A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a first network node, or a device implemented at a first network node, or a device implemented as a first network node, or a device communicatively coupled to a first network node. Therefore, the device can provide components or modules for implementing various parts of method 320, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0186] In this embodiment, the first network node may include an origin edge application server (EAS), and the first network node may select at least one ACR scenario to be used in a next ACR.

[0187] At block 322, the first network node may send a second message to the second network node. The second message may include information about at least one ACR scenario to be used in a next ACR.

[0188] The second message may be any suitable message, such as an existing message or a new message. For example, the second message may be any suitable existing message in the corresponding ACR scenario as described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.

[0189] In an embodiment, the second message is a Selected Target EAS Declaration message as described in 3GPP TS 23.558 V17.4.0.

[0190] Figure 3d A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a first network node, or a device implemented at a first network node, or a device implemented as a first network node, or a device communicatively coupled to a first network node. Therefore, the device can provide components or modules for implementing various parts of the method 330, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0191] In this embodiment, the first network node may include an originating edge application server (EAS), and the first network node may send the first message to the second network node.

[0192] At block 332, the first network node may send a second EAS discovery request to the source EES.

[0193] The second EAS discovery request may be the same as the EAS discovery request as described in 3GPP TS 23.558 V17.4.0.

[0194] At block 334, the first network node may receive a second EAS discovery response from the source EES. The second EAS discovery response may include information about at least one candidate target EAS. The at least one candidate target EAS is a result of filtering that considers at least one commonly supported ACR scenario in the service continuity support capability among the AC, EEC, target EAS, and target EES.

[0195] For example, using the improved T-EAS discovery process, the S-EES does not need to include its own service continuity support capabilities and the S-EAS service continuity support capabilities. Instead, the S-EES includes the AC service continuity support capabilities (as part of the AC profile) and the EEC service continuity support capabilities in the T-EAS discovery request sent to one or more T-EES. The one or more T-EASs discovered are the result of filtering that takes into account the ACR scenarios that are commonly supported in the service continuity support capabilities among AC, EEC, T-EES, and T-EAS.

[0196] At block 336, the first network node may select a target EAS from at least one candidate target EAS.

[0197] Figure 3e A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a first network node, or a device implemented at a first network node, or a device implemented as a first network node, or a device communicatively coupled to a first network node. Therefore, the device can provide components or modules for implementing various parts of method 340, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0198] In this embodiment, the first network node may include a source EES. The source EES may select at least one ACR scenario to be used in the next ACR and / or may send a first message to a second network node such as a T-EES.

[0199] At block 342, the first network node may send a third EAS discovery request to the target EES. The third EAS discovery request may include AC service continuity support capabilities and EEC service continuity support capabilities.

[0200] At block 344, the first network node may receive a third EAS discovery response from the target EES. The third EAS discovery response may include information about at least one candidate target EAS. The at least one candidate target EAS is a result of filtering that considers at least one commonly supported ACR scenario in the service continuity support capability among the AC, EEC, target EAS, and target EES.

[0201] For example, using the improved T-EAS discovery process, the S-EES does not need to include its own service continuity support capabilities and the S-EAS service continuity support capabilities. Instead, the S-EES includes the AC service continuity support capabilities (as part of the AC profile) and the EEC service continuity support capabilities in the T-EAS discovery request sent to one or more T-EES. The one or more T-EASs discovered are the result of filtering that takes into account the ACR scenarios that are commonly supported in the service continuity support capabilities among AC, EEC, T-EES, and T-EAS.

[0202] At block 346, the first network node may select a target EAS from at least one candidate target EAS.

[0203] The first network node may select the target EAS from the at least one candidate target EAS in various ways, and the present disclosure is not limited in this regard.

[0204] Figure 3f A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a first network node, or a device implemented at a first network node, or a device implemented as a first network node, or a device communicatively coupled to a first network node. Therefore, the device can provide components or modules for implementing various parts of the method 350, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0205] At block 352, the first network node may send a third message to the target EES. The third message may include information about at least one ACR scenario to be used in the next ACR.

[0206] For example, when the first network node (eg, S-EES) may select at least one ACR scenario to be used in the next ACR, it may send a third message to the target EES.

[0207] The third message may be any suitable message, such as an existing message or a new message. For example, the third message may be any suitable existing message in the corresponding ACR scenario described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.

[0208] In an embodiment, the third message is a selected target EAS announcement message.

[0209] At block 354, the first network node may send a fourth message to the EEC. The fourth message may include information about at least one ACR scenario to be used in the next ACR.

[0210] For example, when the first network node (eg, S-EES) may select at least one ACR scenario to be used in the next ACR, it may send a third message to the EEC.

[0211] The fourth message may be any suitable message, such as an existing message or a new message. For example, the fourth message may be any suitable existing message in the corresponding ACR scenario described in Section 8.8.2 of 3GPP TS23.558 V17.4.0.

[0212] In an embodiment, the fourth message is a target information notification message as described in clause 8.8.2 of 3GPP TS 23.558 V17.4.0.

[0213] Figure 3g A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a first network node, or a device implemented at a first network node, or a device implemented as a first network node, or a device communicatively coupled to a first network node. Therefore, the device can provide components or modules for implementing various parts of method 360, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0214] In this embodiment, the second network node may include a target EES, and the source EES may send the first message to the target EES. The target EES may select at least one ACR scenario to be used in the next AC.

[0215] At block 362 , the first network node may receive a message including information about at least one ACR scenario to be used in a next ACR from a target EES.

[0216] For example, the message may be a selected target EAS assertion response.

[0217] Then, the first network node may send a fourth message to the EEC. The fourth message may include information about at least one ACR scenario to be used in the next ACR.

[0218] Figure 4a A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a second network node, or a device implemented at a second network node, or a device implemented as a second network node, or a device communicatively coupled to a second network node. Therefore, the device can provide components or modules for implementing various parts of method 400, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0219] At block 402, the second network node may receive a first message from the first network node. The first message may include information for requesting the second network node to select at least one ACR scenario to be used in a next ACR.

[0220] In an embodiment, the second network node may be a S-EES and the first network node may be a S-EAS.

[0221] In an embodiment, the second network node may be a T-EES and the first network node may be a S-EES.

[0222] In an embodiment, the first message is a selected target EAS announcement message.

[0223] In an embodiment, the first network node may include a source edge application server (EAS), and the second network node may include a source EES.

[0224] At block 404 , the second network node may select at least one ACR scenario to be used in a next ACR.

[0225] In an embodiment, at least one ACR scenario to be used in a next ACR is supported by an application client (AC), an edge enabler client (EEC), a target edge application server (EAS), and a target edge enabler server (EES).

[0226] The second network node may obtain or know the ACR scenarios supported in the service continuity support capabilities in AC, EEC, T-EES (target EES), and T-EAS (target EAS). For example, S-EES may include AC service continuity support capabilities (as part of the AC profile) and EEC service continuity support capabilities in a T-EAS discovery request sent to one or more T-EES. The one or more T-EASs discovered are the result of filtering that takes into account the ACR scenarios commonly supported in the service continuity support capabilities in AC, EEC, T-EES, and T-EAS. The second network node (e.g., S-EES or T-EES) may select one or more ACR scenarios based on the ACR scenarios supported by the selected T-EAS.

[0227] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0228] Figure 4b A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a second network node, or a device implemented at a second network node, or a device implemented as a second network node, or a device communicatively coupled to a second network node. Therefore, the device can provide components or modules for implementing various parts of method 410, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0229] At block 412, the second network node may receive a second EAS discovery request from the first network node.

[0230] At block 414, the second network node may send a fourth EAS discovery request to the target EES. The fourth EAS discovery request may include AC service continuity support capabilities and EEC service continuity support capabilities.

[0231] At block 416, the second network node receives a fourth EAS discovery response from the target EES. The fourth EAS discovery response may include information about at least one candidate target EAS. The at least one candidate target EAS is a result of filtering that considers at least one commonly supported ACR scenario in the service continuity support capability among the AC, EEC, target EAS, and target EES.

[0232] At block 418, the second network node may send a second EAS discovery response to the first network node. The second EAS discovery response may include information about at least one candidate target EAS.

[0233] In an embodiment, blocks 412, 414, 416, and 418 may be performed when the first network node is an S-EAS and the second network node is an S-EES.

[0234] In an embodiment, when the first network node is an S-EES and the second network node is a T-EES, blocks 414 and 416 are omitted. In this case, the second EAS discovery request may include AC service continuity support capabilities and EEC service continuity support capabilities.

[0235] Figure 4c A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a second network node, or a device implemented at a second network node, or a device implemented as a second network node, or a device communicatively coupled to a second network node. Therefore, the device can provide components or modules for implementing various parts of method 420, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0236] At block 422, the second network node may send a fifth message to the target EES. The fifth message may include information about at least one ACR scenario to be used in the next ACR.

[0237] For example, when the first network node is S-EAS and the second network node is S-EES, the second network node may send a fifth message to the target EES. When the first network node is S-EES and the second network node is T-EES, block 422 may be omitted and T-EES may store information about at least one ACR scenario to be used in the next ACR.

[0238] At block 424, the second network node may send a sixth message to the EEC. The sixth message may include information about at least one ACR scenario to be used in the next ACR. In an embodiment, the EEC may notify the AC of at least one ACR scenario to be used in the next ACR.

[0239] For example, when the first network node is S-EAS and the second network node is S-EES, the second network node may send a sixth message to the EEC. When the first network node is S-EES and the second network node is T-EES, the second network node may send a sixth message to the EEC and store information about at least one ACR scenario to be used in the next ACR. For example, for T-EES to directly notify the EEC without the EEC subscribing to T-EES, if a control plane-based notification to the UE (e.g., short message service or non-IP data transmission) is used, this is a possible method.

[0240] In an embodiment, the fifth message is a selected target EAS declaration message, and the sixth message is a target information notification message.

[0241] At block 426, the second network node may send a ninth message to the target EAS. The ninth message may include information about at least one ACR scenario to be used in the next ACR.

[0242] For example, when the first network node is an S-EES and the second network node is a T-EES, the second network node may send a ninth message to the EAS.

[0243] Figure 4d A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a second network node, or a device implemented at a second network node, or a device implemented as a second network node, or a device communicatively coupled to a second network node. Therefore, the device can provide components or modules for implementing various parts of method 430, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0244] In this embodiment, the first network node may include a source EES. The second network node may include a target EES. The target EES may select at least one ACR scenario to be used in the next AC.

[0245] At block 432, the second network node may send a message including information about at least one ACR scenario to be used in the next ACR to the first network node.

[0246] For example, the message may be a selected target EAS assertion response.

[0247] Then, the first network node may send a fourth message to the EEC. The fourth message may include information about at least one ACR scene to be used in the next ACR. The second network node sends a ninth message to the target EAS. The ninth message may include information about at least one ACR scene to be used in the next ACR.

[0248] Figure 5a A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a target EES, or a device implemented at a target EES, or a device implemented as a target EES, or a device communicatively coupled to a target EES. Therefore, the device can provide components or modules for implementing various parts of method 500, as well as components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0249] At block 502, the target EES may receive a seventh message from the source EES. The seventh message may include information about at least one ACR scene to be used in a next ACR.

[0250] At block 504, the target EES may store information about at least one ACR scene to be used in the next ACR. In the next ACR, the target EES may act as the source EES and know which ACR scene to use. Therefore, the proposed method provides a proactive way to reduce system complexity for subsequent ACRs during an ACR triggered on the data network side.

[0251] At block 506, the target EES may send an eighth message to the target EAS. The eighth message may include information about at least one ACR scenario to be used in the next ACR.

[0252] In the next ACR, the target EAS can act as the source EAS and know which ACR scenario will be used. Therefore, the proposed method provides a proactive way to reduce the system complexity for subsequent ACRs during an ACR triggered on the data network side.

[0253] In an embodiment, at least one ACR scenario to be used in the next ACR is supported by the AC, the EEC, the target EAS, and the target EES.

[0254] In an embodiment, the seventh message is a selected target EAS declaration message, and the eighth message is an ACR selection notification message.

[0255] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0256] Figure 5b A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a target EES, or a device implemented at a target EES, or a device implemented as a target EES, or a device communicatively coupled to a target EES. Therefore, the device can provide components or modules for implementing various parts of method 510, as well as components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0257] At block 512, the target EES may receive an EAS discovery request from the source EES. The EAS discovery request may include AC service continuity support capabilities and EEC service continuity support capabilities.

[0258] At block 514, the target EES may discover at least one candidate target EAS. The at least one candidate target EAS is a result of filtering that considers at least one commonly supported ACR scenario in service continuity support capabilities among the AC, the EEC, the target EAS, and the target EES.

[0259] At block 516, the target EES may send an EAS discovery response to the source EES. The EAS discovery response may include information about at least one candidate target EAS.

[0260] Figure 5c A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a target EES, or a device implemented at a target EES, or a device implemented as a target EES, or a device communicatively coupled to a target EES. Therefore, the device can provide components or modules for implementing various parts of method 520, as well as components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0261] Step 522 : The target EES receives an ACR scene selection subscription request from the target EAS.

[0262] Step 524: The target EES sends an ACR scenario selection subscription response to the target EAS.

[0263] In an embodiment, the target EES may send an eighth message to the target EAS in response to receiving the ACR scene selection subscription request from the target EAS.

[0264] Figure 6a A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a target EAS, or a device implemented at a target EAS, or a device implemented as a target EAS, or a device communicatively coupled to a target EAS. Therefore, the device can provide components or modules for implementing various parts of method 600, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0265] At block 602, the target EAS may receive an eighth message from the target EES. The eighth message may include information about at least one ACR scenario to be used in a next ACR.

[0266] At block 604, optionally, the target EAS may store information about at least one ACR scenario to be used in the next ACR. In the next ACR, the target EAS may act as the source EAS and know which ACR scenario to use. Therefore, the proposed method provides a proactive way to reduce the system complexity for subsequent ACRs during triggering of ACRs on the data network side.

[0267] In an embodiment, at least one ACR scenario to be used in the next ACR is supported by the AC, the EEC, the target EAS, and the target EES.

[0268] In an embodiment, the eighth message is an ACR selection notification message.

[0269] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0270] Figure 6b A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in a target EAS, or a device implemented at a target EAS, or a device implemented as a target EAS, or a device communicatively coupled to a target EAS. Therefore, the device can provide components or modules for implementing various parts of method 610, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0271] At block 612, the target EAS may send an ACR scene selection subscription request to the target EES.

[0272] At block 614, the target EAS may receive an ACR scene selection subscription response from the target EES.

[0273] In an embodiment, the target EAS may receive an eighth message from the target EES in response to sending the ACR scene selection subscription request to the target EES.

[0274] Figure 6c A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in an EEC, or a device implemented at an EEC, or a device implemented as an EEC, or a device communicatively coupled to an EEC. Therefore, the device can provide components or modules for implementing various parts of method 620, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0275] At block 622, the EEC may receive a message from the EES in an ACR scenario. The message may include information about at least one ACR scenario to be used in the next ACR.

[0276] In an embodiment, the decision to perform ACR in an ACR scenario may be made by a source EES or a source EAS. The EES may be a source EES or a target EES.

[0277] At block 624, the EEC may store information about at least one ACR scenario to be used in the next ACR. In the next ACR, the EEC knows which ACR scenario will be used. Therefore, the proposed method provides a proactive way to reduce system complexity for subsequent ACRs during triggering of ACRs on the data network side.

[0278] At block 626 , the EEC may optionally send a message to the AC including information about at least one ACR scenario to be used in the next ACR.

[0279] In an embodiment, the EEC may inform the AC of at least one ACR scenario to be used in the next ACR.

[0280] In an embodiment, at least one ACR scenario to be used in the next ACR is supported by the AC, the EEC, the target EAS, and the target EES.

[0281] In an embodiment, the message is a target information notification message.

[0282] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0283] Figure 7a A flow chart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in an AC, or a device implemented at an AC, or a device implemented as an AC, or a device communicatively coupled to an AC. Therefore, the device can provide components or modules for implementing various parts of method 700, and components or modules for implementing other processes in combination with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0284] At block 702, the AC may receive a message from the EEC in an ACR scenario. The message may include information about at least one ACR scenario to be used in the next ACR.

[0285] At block 704, the AC may store information about at least one ACR scenario to be used in the next ACR. The decision to execute the ACR in the ACR scenario is made by the source EES or the source EAS. In the next ACR, the AC knows which ACR scenario will be used. Therefore, the proposed method provides a proactive way to reduce the system complexity for subsequent ACRs during an ACR triggered on the data network side.

[0286] In an embodiment, at least one ACR scenario to be used in the next ACR is supported by the AC, the EEC, the target EAS, and the target EES.

[0287] In an embodiment, at least one ACR scenario may include at least one of: ACR initiated by the EEC using conventional EAS discovery, ACR performed by the EEC via a source EES, ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via a target EES.

[0288] When ACR occurs for the S-EAS initiated case as described in 3GPP TS 23.558 V17.4.0 clause 8.8.2.4, the S-EAS discovers one or more candidate T-EASs via the S-EES and may select a T-EAS. In addition, after T-EAS selection, the S-EAS may:

[0289] - self-select one or more ACR scenarios to be used; or

[0290] - Requests the S-EES to select one or more ACR scenes to be used.

[0291] After receiving a request from S-EAS to select one or more ACR scenes to be used, EES may select one or more ACR scenes to be used or request T-EES to select one or more ACR scenes to be used. T-EES may then send information about one or more ACR scenes to be used to S-EES. T-EAS and EEC may then be notified of the information about one or more ACR scenes to be used.

[0292] When ACR occurs for the case of S-EES execution as described in 3GPP TS23.558V17.4.0 Clause 8.8.2.5, S-EES finds one or more candidate T-EAS and selects T-EAS. In addition, S-EES further selects one or more ACR scenes to be used or requires T-EES to select one or more ACR scenes to be used. T-EES can then send information about one or more ACR scenes to be used to S-EES. Then, information about one or more ACR scenes to be used is notified to T-EAS and EEC.

[0293] Note: The selected one or more ACR scenarios may be the same as or a subset of the ACR scenarios commonly supported by AC, EEC, EES, and EAS.

[0294] Figure 7b A flowchart of ACR scene selection determined by S-EAS according to an embodiment of the present disclosure is shown.

[0295] exist Figure 7b Compared with the scenario description in 3GPP TS23.558V17.4.0 clause 8.8.2.4, the differences are:

[0296] - Using the improved T-EAS discovery process in step 3, the S-EES does not need to include its own service continuity support capabilities and the S-EAS service continuity support capabilities. Instead, the S-EES includes the AC service continuity support capabilities (as part of the AC profile) and the EEC service continuity support capabilities in the T-EAS discovery request sent to one or more T-EES. The one or more T-EASs discovered are the result of filtering that takes into account the ACR scenarios that are commonly supported in the service continuity support capabilities among AC, EEC, T-EES, and T-EAS.

[0297] Note 1: In 3GPP TS23.558V17.4.0 clause 8.8.2.4, during step 3 T-EAS discovery process, the discovered T-EAS provided by S-EES to S-EAS is the result of filtering, which takes into account the ACR scenarios commonly supported in the service continuity support capabilities of AC, EEC, S-EES, T-EES, S-EAS and T-EAS as described in 3GPPTS23.558V17.4.0 clause 8.8.3.2, and the selected T-EAS and T-EES cannot support more ACR scenarios than S-EAS and S-EES.

[0298] - The S-EAS additionally selects one or more ACR scenes based on the ACR scenes supported by the selected T-EAS before sending the selected T-EAS Declaration Request to the S-EES in step 4. The S-EAS then includes the selected ACR scene list in the selected T-EAS Declaration Request to the S-EES.

[0299] - Added new steps 4b and 4c. The S-EES declares the selected T-EAS and the selected ACR scene list to the T-EES. The T-EES stores the selected ACR scene to be used and notifies the selected T-EAS of the selected ACR scene list. The T-EAS then stores the selected ACR scene to be used and confirms the ACR selection notification, and the T-EES in turn responds to the S-EES to the selected T-EAS declaration.

[0300] NOTE 2: If the EES is unchanged (ie, S-EES is the same as T-EES), step 4b is not performed, and step 4c is performed between S-EES and T-EAS.

[0301] Note 3: T-EAS should subscribe to ACR selection notification in advance.

[0302] - In step 6, the S-EES additionally includes a list of selected ACR scenarios in the target information notification sent to the EEC. The EEC stores the selected ACR scenarios to be used.

[0303] Figure 7b The other steps may be the same as the corresponding steps described in 3GPP TS23.558V17.4.0 clause 8.8.2.4, and their description is omitted here for brevity.

[0304] Figure 7c A flowchart of ACR scene selection for S-EAS request according to an embodiment of the present disclosure is shown.

[0305] exist Figure 7cCompared with the scenario description in 3GPP TS23.558V17.4.0 clause 8.8.2.4, the differences are:

[0306] - Using the improved T-EAS discovery process in step 3, the S-EES does not need to include its own service continuity support capabilities and the S-EAS service continuity support capabilities. Instead, the S-EES includes the AC service continuity support capabilities (as part of the AC profile) and the EEC service continuity support capabilities in the T-EAS discovery request sent to one or more T-EES. The one or more T-EASs discovered are the result of filtering that takes into account the ACR scenarios that are commonly supported in the service continuity support capabilities among AC, EEC, T-EES, and T-EAS.

[0307] Note 1: In clause 8.8.2.4 of 3GPP TS23.558V17.4.0, during step 3 of the T-EAS discovery process, the discovered T-EAS provided by the S-EES to the S-EAS is the result of filtering that takes into account the ACR scenarios commonly supported in the service continuity support capabilities of AC, EEC, S-EES, T-EES, S-EAS and T-EAS as described in clause 8.8.3.2 of 3GPP TS23.558V17.4.0, and the selected T-EAS and T-EES cannot support more ACR scenarios than S-EAS and S-EES.

[0308] -For the selected T-EAS declaration request sent by S-EAS to S-EES in step 4, S-EAS further requests S-EES to select one or more ACR scenarios. S-EES then selects one or more ACR scenarios from the ACR scenarios supported in the service continuity support capabilities for the selected T-EAS based on the selected T-EAS information received in the selected T-EAS declaration request. Alternatively, S-EES may also request T-EES to select the ACR scenario to be used, in which case T-EES selects the ACR scenario based on the selected T-EAS information received in the selected T-EAS declaration request and responds to S-EES with the selected ACR scenario list. The selected ACR scenario list is then notified to T-EAS and EEC.

[0309] - Add new steps 4b and 4c. The S-EES declares the selected T-EAS and the selected ACR scene list to the T-EES. The T-EES stores the selected ACR scene to be used and notifies the selected T-EAS of the selected ACR scene list. The T-EAS then stores the selected ACR scene to be used and confirms the ACR selection notification, and the T-EES in turn responds to the S-EES to the selected T-EAS declaration.

[0310] NOTE 2: If the EES is unchanged (i.e., S-EES is the same as T-EES), step 4b is not performed and step 4c is performed between S-EES and T-EAS.

[0311] Note 3: T-EAS should subscribe to ACR selection notification in advance.

[0312] - In step 6, the S-EES additionally includes a list of selected ACR scenarios in the target information notification sent to the EEC. The EEC stores the selected ACR scenarios to be used.

[0313] Figure 7c The other steps may be the same as the corresponding steps described in 3GPP TS23.558V17.4.0 clause 8.8.2.4, and their description is omitted here for brevity.

[0314] Figure 7d A flowchart of S-EES deciding ACR scene selection according to an embodiment of the present disclosure is shown.

[0315] exist Figure 7d Compared with the scenario description in 3GPP TS23.558V17.4.0 clause 8.8.2.5, the differences are:

[0316] - Using the improved T-EAS discovery process in step 5, the S-EES does not need to include its own service continuity support capabilities and the S-EAS service continuity support capabilities. Instead, the S-EES includes the AC service continuity support capabilities (as part of the AC profile) and the EEC service continuity support capabilities in the T-EAS discovery request sent to one or more T-EES. In addition to the commonly supported ACR scenarios, the discovered EAS can also support more ACR scenarios than AC and EEC.

[0317] Note 1: In 3GPP TS 23.558 V17.4.0 clause 8.8.2.5, during step 5 of the T-EAS discovery process, the discovered T-EAS provided by the T-EES to the S-EAS is the result of filtering that takes into account the ACR scenarios commonly supported in the service continuity support capabilities in AC, EEC, S-EES, T-EES and T-EAS as described in 3GPP TS 23.558 V17.4.0 clause 8.8.3.2, and the selected T-EAS and T-EES cannot support more ACR scenarios than S-EAS and S-EES, or AC and EEC.

[0318] -After determining T-EAS in step 5, S-EES additionally considers the ACR scenarios commonly supported in AC, EEC, T-EES and T-EAS to select one or more ACR scenarios. S-EES knows the service continuity support capabilities in AC and EEC during the initial EAS discovery, so it can select T-EAS that supports more ACR scenarios than AC and EEC, but the selected one or more ACR scenarios need to be supported by AC and EEC (and also supported by T-EES and T-EAS).

[0319] -Add new steps 5b and 5c. S-EES declares the selected T-EAS and the selected ACR scene list to T-EES. T-EES stores the selected ACR scene to be used and notifies the selected T-EAS of the selected ACR scene list. T-EAS then stores the selected ACR scene to be used and confirms the ACR selection notification, and T-EES in turn responds to the S-EES for the selected T-EAS declaration. Alternatively, S-EES may also request T-EES to select the ACR scene to be used, in which case T-EES selects the ACR scene based on the selected T-EAS information received in the selected T-EAS declaration request, and responds to S-EES with the selected ACR scene list. The selected ACR scene list is then notified to T-EAS and EEC.

[0320] NOTE 2: If the EES is unchanged (ie, S-EES is the same as T-EES), step 5b is not performed, and step 5c is performed between S-EES and T-EAS.

[0321] Note 3: T-EAS should subscribe to ACR selection notification in advance.

[0322] - In step 7, the S-EES additionally includes a selected ACR scene list in the target information notification sent to the EEC. The EEC stores the selected ACR scenes to be used.

[0323] Figure 7d The remaining steps may be the same as the corresponding steps described in 3GPP TS 23.558 V17.4.0 clause 8.8.2.5, and their description is omitted here for brevity.

[0324] In an embodiment, the following content may be added to 3GPP TR 23.700-98 V1.1.1. 7.X.2.4 Information table impact Table 7.X.2.4-1 describes the information elements used for ACR information notification from EES to EEC. Table 7.X.2.4-1: ACR information notification Table 7.X.2.4-2 describes the information elements for a Selected Target EAS Declaration Request sent from an S-EAS to an S-EES or from an S-EES to a T-EES. Table 7.X.2.4-2: Selected Target EAS Declaration Request Table 7.X.2.4-3 describes the information elements for the Selected Target EAS Declaration Response sent from the T-EES to the S-EES. Table 7.X.2.4-3: Selected Target EAS Assertion Response Table 7.X.2.3-4 describes the information elements used for ACR management event notification (including ACR selection notification information) from S-EES / T-EES to T-EAS. Table 7.X.2.4-4: ACR management event notification

[0325] The embodiments herein may provide many advantages, and the following is a non-exhaustive list of examples of advantages. In some embodiments herein, it may address KI#19 of 3GPP TR 23.700-98V1.1.1 in the ACR scenario determined by S-EAS, which allows S-EAS to determine one or more ACR scenarios or request S-EES to determine one or more ACR scenarios to be used. In some embodiments herein, it may address KI#19 of 3GPP TR 23.700-98V1.1.1 in the ACR scenario executed by S-EES, which allows S-EES to determine one or more ACR scenarios to be used. In some embodiments herein, the proposed solution provides an active way to reduce the system complexity for subsequent ACRs during ACRs triggered on the data network side. In some embodiments herein, during EAS discovery, the ideal situation would be that AC, EEC, EES, and EAS support and only support exactly the same ACR scenarios. But in reality, it may be that a suitable T-EAS (meeting the KPI (key performance indicator) requirements of AC) supports more ACR scenarios than S-EAS and S-EES or AC and EEC. The ACR scenario selection solution determined by S-EES is then used to make an ACR scenario selection for the appropriate T-EAS and notify the corresponding entity of the selection. The embodiments herein are not limited to the above features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description.

[0326] Figure 8a 800 is a block diagram showing an apparatus suitable for practicing some embodiments of the present disclosure. For example, any of the above-mentioned first network node, second network node, target EES, target EAS, AC or EEC can be implemented as apparatus 800 or implemented by apparatus 800.

[0327] The device 800 includes at least one processor 821, such as a digital processor (DP), and at least one memory (MEM) 822 coupled to the processor 821. The device 800 may further include a transmitter TX and a receiver RX 823 coupled to the processor 821. The MEM 822 stores a program (PROG) 824. The PROG 824 may include instructions that, when executed on the associated processor 821, enable the device 800 to operate according to embodiments of the present disclosure. The combination of at least one processor 821 and at least one MEM 822 may form a processing device 825 suitable for implementing various embodiments of the present disclosure.

[0328] Various embodiments of the present disclosure may be implemented by a computer program that may be executed by one or more of the processor 821 , software, firmware, hardware, or a combination thereof.

[0329] The MEM 822 may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples.

[0330] Processor 821 may be of any type suitable to the local technical environment, and may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples.

[0331] In an embodiment where the apparatus is implemented as or at a first network node, the memory 822 stores instructions executable by the processor 821, whereby the first network node operates according to any method related to a first network node as described above.

[0332] In an embodiment where the apparatus is implemented as or at a second network node, the memory 822 stores instructions executable by the processor 821, whereby the second network node operates according to any method related to a second network node as described above.

[0333] In embodiments where the apparatus is implemented as or at a target EES, the memory 822 stores instructions executable by the processor 821 whereby the target EES operates according to any of the methods described above in relation to the target EES.

[0334] In embodiments where the apparatus is implemented as or at a target EAS, the memory 822 stores instructions executable by the processor 821 whereby the target EAS operates according to any of the methods described above in relation to the target EAS.

[0335] In embodiments where the apparatus is implemented as or at an EEC, the memory 822 stores instructions executable by the processor 821 whereby the EEC operates according to any of the methods described above in relation to the EEC.

[0336] In embodiments where the apparatus is implemented as or at an AC, the memory 822 stores instructions executable by the processor 821 whereby the AC operates according to any of the methods described above in relation to the AC.

[0337] Figure 8b840 is a block diagram illustrating a first network node according to an embodiment of the present disclosure. As shown in the figure, the first network node 840 may include a decision module 841, which is configured to decide to perform application context relocation (ACR). The first network node 840 may also include a first sending module 842, which is configured to send a first message to the second network node. The first message may include information for requesting the second network node to select at least one ACR scene to be used in the next ACR.

[0338] In an embodiment, the first network node 840 may further include a second sending module 843 configured to send a fourth message to the EEC. The fourth message may include information about at least one ACR scenario to be used in the next ACR.

[0339] Figure 8c 860 is a block diagram illustrating a second network node 860 according to an embodiment of the present disclosure. As shown in the figure, the second network node 860 may include a receiving module 861, which is configured to receive a first message from the first network node. The first message may include information for requesting the second network node to select at least one ACR scene to be used in the next ACR. The second network node 860 may also include a selection module 862, which is configured to select at least one ACR scene to be used in the next ACR.

[0340] In an embodiment, the second network node 860 may further include a first sending module 863 configured to send a sixth message to the EEC. The sixth message may include information about at least one ACR scenario to be used in the next ACR.

[0341] In an embodiment, the second network node 860 may further include a second sending module 864 configured to send a ninth message to the target EAS. The ninth message may include information about at least one ACR scenario to be used in the next ACR.

[0342] In an embodiment, when the first network node may include a source EES and the second network node may include a target EES, the second network node 860 may further include a third sending module 865 configured to send a message including information about at least one ACR scenario to be used in the next ACR to the first network node.

[0343] Figure 8d870 is a block diagram showing a target EES according to another embodiment of the present disclosure. As shown in the figure, the target EES 870 may include a first receiving module 871, which is configured to receive a seventh message from the source EES. The seventh message may include information about at least one ACR scene to be used in the next ACR. The target EES 870 may also include a storage module 872, which is configured to store information about at least one ACR scene to be used in the next ACR. The target EES 870 may also include a first sending module 873, which is configured to send an eighth message to the target EAS. The eighth message may include information about at least one ACR scene to be used in the next ACR.

[0344] In an embodiment, the target EES 870 may further include a second receiving module 874 configured to receive an EAS discovery request from the source EES. The EAS discovery request may include AC service continuity support capabilities and EEC service continuity support capabilities.

[0345] In an embodiment, the target EES 870 may further include a discovery module 875 configured to discover at least one candidate target EAS. The at least one candidate target EAS is a result of filtering that considers at least one ACR scenario commonly supported in service continuity support capabilities among AC, EEC, target EAS, and target EES.

[0346] In an embodiment, the target EES 870 may further include a second sending module 876 configured to send an EAS discovery response to the source EES. The EAS discovery response may include information about at least one candidate target EAS.

[0347] In an embodiment, the target EES 870 may further include a third receiving module 877 configured to receive an ACR scene selection subscription request from the target EAS.

[0348] In an embodiment, the target EES 870 may further include a third sending module 878 configured to send an ACR scenario selection subscription response to the target EAS.

[0349] Figure 8e 8 is a block diagram showing a target EAS according to another embodiment of the present disclosure. As shown in the figure, the target EAS 880 may include a first receiving module 881, which is configured to receive an eighth message from the target EES. The eighth message may include information about at least one ACR scene to be used in the next ACR.

[0350] In an embodiment, the target EAS 880 may further include a storage module 882 configured to store information about at least one ACR scenario to be used in the next ACR.

[0351] In an embodiment, the target EAS 880 may further include a sending module 883 configured to send an ACR scene selection subscription request to the target EES.

[0352] In an embodiment, the target EAS 880 may further include a second receiving module 884 configured to receive an ACR scene selection subscription response from the target EES.

[0353] Figure 8f 890 is a block diagram showing an EEC according to another embodiment of the present disclosure. As shown in the figure, the EEC 890 may include a receiving module 891, which is configured to receive a message from the EES in an ACR scene. The message may include information about at least one ACR scene to be used in the next ACR. The EEC 890 may also include a storage module 892, which is configured to store information about at least one ACR scene to be used in the next ACR.

[0354] In an embodiment, the EEC 890 may further include a transmitting module 893 configured to transmit a message including information about at least one ACR scenario to be used in a next ACR to the AC.

[0355] Figure 8g 895 is a block diagram showing an AC according to another embodiment of the present disclosure. As shown in the figure, AC 895 may include a receiving module 896, which is configured to receive a message from EEC in an ACR scene. The message may include information about at least one ACR scene to be used in the next ACR. AC 895 may also include a storage module 897, which is configured to store information about at least one ACR scene to be used in the next ACR. The decision to perform ACR in the ACR scene is made by the source EES or the source EAS.

[0356] By using functional units, EES, EEC, AC or EAS does not need fixed processors or memories, and any computing resources and storage resources can be deployed from EES, EEC, AC or EAS in the communication system. The introduction of virtualization technology and network computing technology can improve the efficiency of network resource utilization and network flexibility.

[0357] According to one aspect of the present disclosure, a computer program product is provided, which is tangibly stored on a computer-readable storage medium and includes instructions. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform any of the above methods.

[0358] According to one aspect of the present disclosure, a computer-readable storage medium is provided, which stores instructions. When the instructions are executed on at least one processor, the instructions cause the at least one processor to perform any of the above methods.

[0359] In addition, an exemplary overall communication system including a terminal device and a network node will be introduced below.

[0360] Embodiments of the present disclosure provide a communication system including a host computer, the host computer including: a processing circuit configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes a network node (such as a base station, EES, EAS, etc.) and / or a terminal device, such as the above-mentioned AC or EEC.

[0361] In an embodiment of the present disclosure, the system further includes a terminal device. The terminal device is configured to communicate with the base station.

[0362] In an embodiment of the present disclosure, a processing circuit of a host computer is configured to execute a host application to provide user data; and a terminal device includes a processing circuit configured to execute a client application associated with the host application.

[0363] The embodiment of the present disclosure also provides a communication system including a host computer and a base station, wherein the host computer includes: a communication interface configured to receive user data originating from a transmission from a terminal device. The transmission is from the terminal device to the base station.

[0364] In an embodiment of the present disclosure, the processing circuit of the host computer is configured to execute a host application. The terminal device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0365] Fig. 9 is a schematic diagram illustrating a wireless network according to some embodiments.

[0366] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to wireless networks, such as Fig. 9 For simplicity, Fig. 9The wireless network of FIG. 1 depicts only the network 1006, the network nodes 1060 (corresponding to the network side nodes) and 1060b, and the WDs (corresponding to the terminal devices) 1010, 1010b, and 1010c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline phone, a service provider, or any other network node or terminal device). In the components shown, the network node 1060 and the wireless device (WD) 1010 are depicted with additional details. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless device to access services provided by the wireless network and / or use services provided by or via the wireless network.

[0367] A wireless network may include and / or interface with any type of communication, telecommunication, data, cellular and / or radio network or other similar type of system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, particular embodiments of a wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards such as IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0368] The network 1006 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communications between devices.

[0369] The network node 1060 and WD 1010 include various components described in more detail below. These components work together to provide network node and / or wireless device functions, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and signals via wired or wireless connections.

[0370] As used herein, a network node refers to a device that is capable of, configured, arranged and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to a wireless device and / or perform other functions (e.g., management) in a wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, node Bs, evolved node Bs (eNBs), and NR node Bs (gNBs)). Base stations can be classified based on the amount of coverage they provide (or, in other words, their transmit power levels), and then may also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node that controls a relay. A network node may further include one or more components (or all components) of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. Components of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet another example of a network node includes a multi-standard radio (MSR) device (e.g., an MSRBS), a network controller (e.g., a radio network controller (RNC) or a base station controller (BSC)), a base transceiver station (BTS), a transmission point, a transmission node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node as described in more detail below. However, more generally, a network node may represent any suitable device (or group of devices) that is capable of, configured, arranged, and / or operable to enable and / or provide a wireless device with access to a wireless network or to provide certain services to a wireless device that has accessed a wireless network.

[0371] exist Fig. 9 In the embodiment, the network node 1060 includes a processing circuit 1070, a device readable medium 1080, an interface 1090, an auxiliary device 1084, a power supply 1086, a power supply circuit 1087, and an antenna 1062. Fig. 9The network node 1060 shown in the example wireless network of can represent a device including the combination of hardware components shown, but other embodiments can include network nodes with different combinations of components. It should be understood that the network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. In addition, although the components of the network node 1060 are depicted as a single box located within a larger box or a single box nested within multiple boxes, in reality, the network node can include multiple different physical components that constitute a single illustrated component (for example, the device readable medium 1080 can include multiple separate hard drives and multiple RAM modules).

[0372] Similarly, the network node 1060 may be composed of multiple physically separated components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own corresponding components. In certain scenarios where the network node 1060 includes multiple individual components (e.g., BTS and BSC components), one or more individual components may be shared between several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may be considered a single individual network node in some cases. In some embodiments, the network node 1060 may be configured to support multiple radio access technologies (RATs). In such an embodiment, some components (e.g., separate device-readable media 1080 for different RATs) may be repeated, and some components may be reused (e.g., the same antenna 1062 may be shared by the RATs). The network node 1060 may further include multiple sets of various illustrated components for different wireless technologies integrated into the network node 1060, such as GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chips or chipsets and other components within network node 1060 .

[0373] The processing circuit 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) as described herein as provided by the network node. Such operations performed by the processing circuit 1070 may include processing information obtained by the processing circuit 1070 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information and making a determination as a result of the processing.

[0374] The processing circuit 1070 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic, which can operate alone or in conjunction with other network node 1060 components (e.g., device readable medium 1080) to provide network node 1060 functions. For example, the processing circuit 1070 can execute instructions stored in the device readable medium 1080 or a memory within the processing circuit 1070. Such functions may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuit 1070 may include a system on a chip (SOC).

[0375] In some embodiments, processing circuit 1070 may include one or more of the following: radio frequency (RF) transceiver circuit 1072 and baseband processing circuit 1074. In some embodiments, radio frequency (RF) transceiver circuit 1072 and baseband processing circuit 1074 may be on separate chips (or chipsets), boards, or units (e.g., a radio unit and a digital unit). In alternative embodiments, part or all of RF transceiver circuit 1072 and baseband processing circuit 1074 may be on the same chip or chipset, board, or unit.

[0376] In certain embodiments, some or all of the functions described herein as provided by a network node, base station, eNB, or other such network node may be performed by processing circuit 1070 executing instructions stored on device-readable medium 1080 or memory within processing circuit 1070. In alternative embodiments, some or all of the functions may be provided by processing circuit 1070, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable medium. In any of these embodiments, processing circuit 1070 may be configured to perform the described functions, whether or not executing instructions stored on a device-readable storage medium. The benefits provided by such functions are not limited to processing circuit 1070 or to other components of network node 1060, but are generally enjoyed by network node 1060 as a whole and / or by end users and wireless networks.

[0377] Device readable medium 1080 may include any form of volatile or non-volatile computer readable memory, including but not limited to persistent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer executable storage device that stores information, data and / or instructions that can be used by processing circuit 1070. Device readable medium 1080 may store any suitable instructions, data or information that can be executed by processing circuit 1070 and used by network node 1060, including computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.), and / or other instructions. Device readable medium 1080 may be used to store any calculations made by processing circuit 1070 and / or any data received through interface 1090. In some embodiments, processing circuit 1070 and device readable medium 1080 may be considered integrated.

[0378] Interface 1090 is used for wired or wireless communication of signaling and / or data between network node 1060, network 1006 and / or WD 1010. As shown, interface 1090 includes one or more ports / one or more terminals 1094, which are used, for example, to send data to network 1006 and receive data from network 1006 via a wired connection. Interface 1090 further includes a radio front-end circuit 1092, which can be coupled to antenna 1062, or in some embodiments is part of antenna 1062. Radio front-end circuit 1092 includes filter 1098 and amplifier 1096. Radio front-end circuit 1092 can be connected to antenna 1062 and processing circuit 1070. The radio front-end circuit can be configured to adjust the signal transmitted between antenna 1062 and processing circuit 1070. Radio front-end circuit 1092 can receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front end circuit 1092 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 1098 and / or amplifiers 1096. The radio signal may then be transmitted through the antenna 1062. Similarly, when receiving data, the antenna 1062 may collect the radio signal, which may then be converted into digital data by the radio front end circuit 1092. The digital data may be passed to the processing circuit 1070. In other embodiments, the interface may include different components and / or different combinations of components.

[0379] In some alternative embodiments, the network node 1060 may not include a separate radio front end circuit 1092, and instead, the processing circuit 1070 may include the radio front end circuit and may be connected to the antenna 1062 without the separate radio front end circuit 1092. Similarly, in some embodiments, all or some of the RF transceiver circuit 1072 may be considered part of the interface 1090. In still other embodiments, the interface 1090 may include one or more ports or terminals 1094, the radio front end circuit 1092, and the RF transceiver circuit 1072 as part of a radio unit (not shown), and the interface 1090 may communicate with the baseband processing circuit 1074, which is part of the digital unit (not shown).

[0380] Antenna 1062 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 1062 may be coupled to radio front-end circuit 1090 and may be any type of antenna capable of wirelessly sending and receiving data and / or signals. In some embodiments, antenna 1062 may include one or more omnidirectional, sector or flat panel antennas operable to transmit / receive radio signals between, for example, 2 GHz and 66 GHz. Omnidirectional antennas may be used to send / receive radio signals in any direction, sector antennas may be used to send / receive radio signals to / from devices in a specific area, and flat panel antennas may be line of sight antennas used to send / receive radio signals in a relatively straight line. In some cases, using more than one antenna may be referred to as MIMO. In some embodiments, antenna 1062 may be separated from network node 1060 and may be connected to network node 1060 via an interface or port.

[0381] Antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any receiving operation and / or certain obtaining operation described herein as being performed by a network node. Any information, data and / or signal can be received from a wireless device, another network node and / or any other network device. Similarly, antenna 1062, interface 1090 and / or processing circuit 1070 can be configured to perform any sending operation described herein as being performed by a network node. Any information, data and / or signal can be sent to a wireless device, another network node and / or any other network device.

[0382] The power circuit 1087 may include or be coupled to a power management circuit and is configured to provide power to the components of the network node 1060 for performing the functions described herein. The power circuit 1087 may receive power from the power supply 1086. The power supply 1086 and / or the power circuit 1087 may be configured to provide power to the various components of the network node 1060 in a form suitable for the various components (e.g., at the voltage and current level required by each respective component). The power supply 1086 may be included in the power circuit 1087 and / or the network node 1060 or outside the power circuit 1087 and / or the network node 1060. For example, the network node 1060 may be connected to an external power source (e.g., a power outlet) via an input circuit or interface (e.g., a cable), whereby the external power source supplies power to the power circuit 1087. As another example, the power supply 1086 may include a power source in the form of a battery or a battery pack, which is connected to the power circuit 108 or integrated in the power circuit 1087. If the external power source fails, the battery can provide backup power. Other types of power sources, such as photovoltaic devices, may also be used.

[0383] Alternative embodiments of network node 1060 may include, in addition to Fig. 9 , which may be responsible for providing certain aspects of the network node functionality, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 1060 may include a user interface device to allow information to be input to the network node 1060 and to allow information to be output from the network node 1060. This may allow a user to perform diagnostic, maintenance, repair, and other management functions for the network node 1060.

[0384] As used herein, a wireless device (WD) refers to a device that can, is configured, is arranged and / or is operable to wirelessly communicate with a network node and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with a user equipment (UE) in this article. Wireless communication may involve the use of electromagnetic waves, radio waves, infrared waves and / or other types of signals suitable for transmitting information through the air to send and / or receive wireless signals. In some embodiments, a WD may be configured to send and / or receive information without direct human interaction. For example, when triggered by an internal or external event, or in response to a request from a network, a WD may be designed to send information to a network according to a predetermined schedule. Examples of WD include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, laptop embedded devices (LEEs), laptop computer installation devices (LMEs), smart devices, wireless client devices (CPEs), vehicle-mounted wireless terminal devices, etc. For example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), WD can support device-to-device (D2D) communication, and in this case, WD can be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, WD can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another WD and / or network node. In this case, WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, WD can be a UE that implements the 3GPP narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, such as metering devices of power meters, industrial machinery, or household or personal appliances (such as refrigerators, televisions, etc.), personal wearable devices (such as watches, fitness trackers, etc.). In other scenarios, WD can represent a vehicle or other device that can monitor and / or report its operating status or other functions associated with its operation. As mentioned above, WD can represent the end point of wireless connection, in which case, the device can be referred to as a wireless terminal. In addition, as mentioned above, WD can be mobile, in which case, it can also be referred to as a mobile device or a mobile terminal.

[0385] As shown, wireless device 1010 includes antenna 1011, interface 1014, processing circuit 1020, device readable medium 1030, user interface device 1032, auxiliary device 1034, power supply 1036 and power supply circuit 1037. WD 1010 may include multiple sets of one or more of the components shown for different wireless technologies supported by WD 1010 (e.g., such as GSM, WCDMA, LTE, NR, WiFi, WiMAX or Bluetooth wireless technologies, to name a few). These wireless technologies may be integrated into the same or different chips or chipsets as other components within WD 1010.

[0386] Antenna 1011 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and connected to interface 1014. In some alternative embodiments, antenna 1011 may be separated from WD 1010 and may be connected to WD 1010 via an interface or port. Antenna 1011, interface 1014 and / or processing circuit 1020 may be configured to perform any receiving or transmitting operation described herein as being performed by a WD. Any information, data and / or signal may be received from a network node and / or another WD. In some embodiments, radio front end circuitry and / or antenna 1011 may be considered as an interface.

[0387] As shown, the interface 1014 includes a radio front-end circuit 1012 and an antenna 1011. The radio front-end circuit 1012 includes one or more filters 1018 and an amplifier 1016. The radio front-end circuit 1014 is connected to the antenna 1011 and the processing circuit 1020, and is configured to condition the signals communicated between the antenna 1011 and the processing circuit 1020. The radio front-end circuit 1012 may be coupled to the antenna 1011 or may be part of the antenna 1011. In some embodiments, the WD 1010 may not include a separate radio front-end circuit 1012; instead, the processing circuit 1020 may include a radio front-end circuit and may be connected to the antenna 1011. Similarly, in some embodiments, some or all of the RF transceiver circuit 1022 may be considered part of the interface 1014. The radio front-end circuit 1012 may receive digital data, which will be sent to other network nodes or WDs via a wireless connection. The radio front-end circuit 1012 may convert the digital data into a radio signal with appropriate channel and bandwidth parameters using a combination of filters 1018 and / or amplifiers 1016. The radio signal may then be transmitted via antenna 1011. Similarly, when receiving data, antenna 1011 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1012. The digital data may be passed to processing circuit 1020. In other embodiments, the interface may include different components and / or different combinations of components.

[0388] The processing circuit 1020 may include a combination of one or more of the following: a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic, which can operate to provide WD 1010 functions alone or in conjunction with other WD 1010 components (e.g., device readable medium 1030). Such functions may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 1020 may execute instructions stored in the device readable medium 1030 or a memory within the processing circuit 1020 to provide the functions disclosed herein.

[0389] As shown, the processing circuit 1020 includes one or more of the following: RF transceiver circuit 1022, baseband processing circuit 1024, and application processing circuit 1026. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 1020 of WD 1010 may include a SOC. In some embodiments, the RF transceiver circuit 1022, the baseband processing circuit 1024, and the application processing circuit 1026 may be on a separate chip or chipset. In an alternative embodiment, part or all of the baseband processing circuit 1024 and the application processing circuit 1026 may be combined in one chip or chipset, and the RF transceiver circuit 1022 may be on a separate chip or chipset. In another alternative embodiment, part or all of the RF transceiver circuit 1022 and the baseband processing circuit 1024 may be on the same chip or chipset, and the application processing circuit 1026 may be on a separate chip or chipset. In yet another alternative embodiment, part or all of RF transceiver circuit 1022, baseband processing circuit 1024, and application processing circuit 1026 may be combined in the same chip or chipset. In some embodiments, RF transceiver circuit 1022 may be part of interface 1014. RF transceiver circuit 1022 may condition RF signals for processing circuit 1020.

[0390] In some embodiments, some or all of the functions described herein as being performed by the WD may be provided by the processing circuit 1020 executing instructions stored on the device-readable medium 1030, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by the processing circuit 1020, for example, in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, the processing circuit 1020 may be configured to perform the described functions, regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 1020 or to other components of the WD 1010, but are generally enjoyed by the WD 1010 as a whole and / or by end users and wireless networks.

[0391] Processing circuit 1020 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by WD. Such operations as performed by processing circuit 1020 may include processing information obtained by processing circuit 1020 by, for example, converting the obtained information into other information, comparing the obtained information or the converted information with information stored by WD 1010, and / or performing one or more operations based on the obtained information or the converted information and making a determination as a result of the processing.

[0392] Device-readable medium 1030 is operable to store computer programs, software, applications (including one or more of logic, rules, code, tables, etc.), and / or other instructions that can be executed by processing circuit 1020. Device-readable medium 1030 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disk (CD) or digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by processing circuit 1020. In some embodiments, processing circuit 1020 and device-readable medium 1030 may be considered integrated.

[0393] The user interface device 1032 may provide a component that allows a human user to interact with the WD 1010. This interaction may be in multiple forms, such as visual, auditory, tactile, etc. The user interface device 1032 may operate to generate output to the user and allow the user to provide input to the WD 1010. The type of interaction may vary depending on the type of user interface device 1032 installed in the WD 1010. For example, if the WD 1010 is a smart phone, the interaction may be through a touch screen; if the WD 1010 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alarm (e.g., if smoke is detected). The user interface device 1032 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device 1032 is configured to allow information to be input into the WD 1010, and is connected to the processing circuit 1020 to allow the processing circuit 1020 to process the input information. The user interface device 1032 may include, for example, a microphone, a proximity sensor or other sensor, a key / button, a touch display, one or more cameras, a USB port, or other input circuits. The user interface device 1032 is also configured to allow information to be output from the WD 1010, and to allow the processing circuit 1020 to output information from the WD 1010. The user interface device 1032 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuits. Using one or more input and output interfaces, devices, and circuits of the user interface device 1032, the WD 1010 can communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.

[0394] Auxiliary device 1034 is operable to provide more specific functions that may not normally be performed by a WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communications such as wired communications, etc. The inclusion and types of components of auxiliary device 1034 may vary depending on the embodiment and / or scenario.

[0395] In some embodiments, the power source 1036 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. The WD 1010 may further include a power circuit 1037 for delivering power from the power source 1036 to various components of the WD 1010 that require power from the power source 1036 to perform any function described or indicated herein. In some embodiments, the power circuit 1037 may include a power management circuit. The power circuit 1037 may additionally or alternatively be operable to receive power from an external power source; in this case, the WD 1010 may be connected to an external power source (e.g., a power outlet) via an input circuit or an interface such as a power cable. In some embodiments, the power circuit 1037 may also be operable to deliver power from an external power source to the power source 1036. This may be used, for example, to charge the power source 1036. The power circuit 1037 may perform any formatting, conversion, or other modifications to the power from the power source 1036 to make the power suitable for the various components of the WD 1010 being powered.

[0396] Fig.10 is a schematic diagram illustrating a user equipment according to some embodiments.

[0397] Fig.10 One embodiment of a UE in accordance with various aspects described herein is shown. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated equipment. Rather, a UE may represent a device that is intended to be sold to or operated by a human user but may not be, or may not initially be, associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended to be sold to or operated by an end user but may be associated with or operated for the benefit of a user (e.g., a smart meter). UE 1100 may be any UE identified by the Third Generation Partnership Project (3GPP), including a NB-IoT UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Fig.10 As shown, UE 1100 is an example of a WD that is configured to communicate in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE and / or 5G standards. As previously mentioned, the terms WD and UE can be used interchangeably. Therefore, although Fig.10 It is UE, but the components discussed here are also applicable to WD, and vice versa.

[0398] exist Fig.10 In the embodiment, UE 1100 includes a processing circuit 1101, which is operably coupled to an input / output interface 1105, a radio frequency (RF) interface 1109, a network connection interface 1111, a memory 1115 (including a random access memory (RAM) 1117, a read-only memory (ROM) 1119, and a storage medium 1121, etc.), a communication subsystem 1131, a power supply 1113 and / or any other components, or any combination thereof. The storage medium 1121 includes an operating system 1123, an application 1125, and data 1127. In other embodiments, the storage medium 1121 may store other similar types of information. Some UEs may utilize Fig.10 All components shown in the UE or only a subset of the components. The level of integration between components may vary from one UE to another. In addition, some UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0399] exist Fig.10 In the embodiment of the present invention, the processing circuit 1101 can be configured to process computer instructions and data. The processing circuit 1101 can be configured to implement any sequential state machine that is operable to execute machine instructions stored as a machine-readable computer program in a memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and appropriate firmware; one or more stored programs, general-purpose processors, such as microprocessors or digital signal processors (DSPs), and appropriate software; or any combination of the above. For example, the processing circuit 1101 may include two central processing units (CPUs). The data may be information in a form suitable for use by a computer.

[0400] In the depicted embodiment, the input / output interface 1105 may be configured to provide a communication interface to an input device, an output device, or an input and output device. The UE 1100 may be configured to use an output device through the input / output interface 1105. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to the UE 1100 and provide output from the UE 1100. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 1100 may be configured to use an input device through the input / output interface 1105 to allow a user to capture information into the UE 1100. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. For example, the sensor can be an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0401] exist Fig.10 In the embodiment of the present invention, the RF interface 1109 can be configured to provide a communication interface to RF components such as transmitters, receivers and antennas. The network connection interface 1111 can be configured to provide a communication interface to the network 1143a. The network 1143a can include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1143a can include a Wi-Fi network. The network connection interface 1111 can be configured to include a receiver and a transmitter interface, which is used to communicate with one or more other devices through a communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). The network connection interface 1111 can implement receiver and transmitter functions suitable for communication network links (e.g., optical, electrical, etc.). The transmitter and receiver functions can share circuit components, software or firmware, or can alternatively be implemented separately.

[0402] RAM 1117 may be configured to interface with processing circuit 1101 via bus 1102 to provide storage or caching of data or computer instructions during execution of software programs such as operating systems, applications, and device drivers. ROM 1119 may be configured to provide computer instructions or data to processing circuit 1101. For example, ROM 1119 may be configured to store unchanging low-level system code or data for basic system functions, such as basic input and output (I / O), booting, or receipt of keystrokes from a keyboard, which are stored in non-volatile memory. Storage media 1121 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable tape, or flash drive. In one example, the storage medium 1121 may be configured to include an operating system 1123, an application 1125 (e.g., a web browser application, a widget or gadget engine, or another application), and a data file 1127. The storage medium 1121 may store any operating system or combination of operating systems from a variety of operating systems for use by the UE 1100.

[0403] The storage medium 1121 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, a flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD) optical drive, an internal hard drive, a Blu-ray optical drive, a holographic digital data storage (HDDS) optical drive, an external mini dual in-line memory module (DIMM), a synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, a smart card memory (e.g., a user identity module or a removable user identity (SIM / RUIM) module), other memory, or any combination thereof. The storage medium 1121 may allow the UE 1100 to access computer executable instructions, applications, etc. stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture (e.g., an article of manufacture utilizing a communication system) may be tangibly embodied in the storage medium 1121, which may include a device-readable medium.

[0404] exist Fig.10In the embodiment of the present invention, the processing circuit 1101 can be configured to communicate with the network 1143b using the communication subsystem 1131. The network 1143a and the network 1143b can be the same network or multiple networks or different networks or multiple networks. The communication subsystem 1131 can be configured to include one or more transceivers for communicating with the network 1143b. For example, the communication subsystem 1131 can be configured to include one or more transceivers for communicating with the network 1143b. For example, the communication subsystem 1131 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device capable of wireless communication according to one or more communication protocols (e.g., IEEE802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.), such as another WD, UE or base station of a radio access network (RAN). Each transceiver can include a transmitter 1133 and / or a receiver 1135 to respectively implement a transmitter or receiver function (e.g., frequency allocation, etc.) suitable for a RAN link. In addition, the transmitter 1133 and the receiver 1135 of each transceiver can share circuit components, software or firmware, or can alternatively be implemented separately.

[0405] In the illustrated embodiment, the communication functions of the communication subsystem 1131 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a global positioning system (GPS) to determine the location, another similar communication function, or any combination thereof. For example, the communication subsystem 1131 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1143b may include a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1143b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1113 may be configured to provide alternating current (AC) power or direct current (DC) power to the components of the UE 1100.

[0406] The features, benefits and / or functions described herein may be implemented in one of the components of UE 1100 or divided across multiple components of UE 1100. In addition, the features, benefits and / or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, the communication subsystem 1131 may be configured to include any component described herein. In addition, the processing circuit 1101 may be configured to communicate with any such component via a bus 1102. In another example, any such component may be represented by a program instruction stored in a memory, and when the program instruction is executed by the processing circuit 1101, the program instruction performs the corresponding function described herein. In another example, the function of any such component may be divided between the processing circuit 1101 and the communication subsystem 1131. In another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0407] Fig.11 is a schematic diagram illustrating a virtualized environment according to some embodiments.

[0408] Fig.11 1 is a schematic block diagram illustrating a virtualized environment 1200 in which functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or a component thereof, and relates to an implementation in which at least a portion of a function is implemented as one or more virtual components (e.g., by one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0409] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1200 hosted by one or more hardware nodes 1230. Furthermore, in embodiments where the virtual nodes are not radio access nodes or do not require radio connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0410] Functionality may be implemented by one or more applications 1220 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) that are operable to implement some features, functions, and / or benefits of some embodiments disclosed herein. Applications 1220 run in a virtualized environment 1200 that provides hardware 1230 including processing circuitry 1260 and memory 1290-1. Memory 1290-1 stores instructions 1295 that may be executed by processing circuitry 1260, whereby applications 1220 are operable to provide one or more features, benefits, and / or functionality disclosed herein.

[0411] The virtualized environment 1200 includes general or special purpose network hardware devices 1230, which include a set of one or more processors or processing circuits 1260, which may be commercial off-the-shelf (COTS) processors, special purpose application-specific integrated circuits (ASICs), or any other type of processing circuit, including digital or analog hardware components or special purpose processors. Each hardware device may include a memory 1290-1, which may be a non-persistent memory for temporarily storing instructions 1295 or software executed by the processing circuit 1260. Each hardware device may include one or more network interface controllers (NICs) 1270, also known as network interface cards, which include a physical network interface 1280. Each hardware device may further include a non-transitory, persistent, machine-readable storage medium 1290-2 in which software 1295 and / or instructions that may be executed by the processing circuit 1260 have been stored. The software 1295 may include any type of software, including software for instantiating one or more virtualization layers 1250 (also known as hypervisors), software for executing virtual machines 1240, and software that enables them to perform functions, features and / or benefits associated with some of the embodiments described herein.

[0412] The virtual machine 1240 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 1250 or hypervisor. Different embodiments of instances of the virtual device 1220 may be implemented on one or more virtual machines 1240 and may be implemented in different ways.

[0413] During operation, processing circuitry 1260 executes software 1295 to instantiate a hypervisor or virtualization layer 1250, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 1250 may present a virtual operating platform that appears to virtual machines 1240 as networked hardware.

[0414] like Fig.11As shown in , hardware 1230 can be a standalone network node with common or specific components. Hardware 1230 can include antenna 12225 and some functions can be implemented through virtualization. Alternatively, hardware 1230 can be part of a larger hardware cluster (e.g., in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed by management and orchestration (MANO) 12100, which, among other things, oversees the lifecycle management of application 1220.

[0415] Virtualization of hardware is referred to in some contexts as network function virtualization (NFV). NFV can be used to consolidate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premises devices.

[0416] In the context of NFV, a virtual machine 1240 can be a software implementation of a physical machine that runs a program as if the program were running on a physical, non-virtualized machine. Each virtual machine 1240, and that portion of the hardware 1230 on which the virtual machine executes, whether hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines 1240, forms a separate virtual network element (VNE).

[0417] Still in the context of NFV, a virtual network function (VNF) is responsible for handling a specific network function running in one or more virtual machines 1240 on the hardware networking infrastructure 1230 and corresponds to Fig.11 Application 1220.

[0418] In some embodiments, one or more radio units 12200 (each radio unit includes one or more transmitters 12220 and one or more receivers 12210) can be coupled to one or more antennas 12225. The radio unit 12200 can communicate directly with the hardware node 1230 through one or more appropriate network interfaces, and can be used in conjunction with virtual components to provide a virtual node with radio capabilities, such as a radio access node or base station.

[0419] In some embodiments, some signaling may be implemented using a control system 12230 , which may alternatively be used for communications between the hardware node 1230 and the radio unit 12200 .

[0420] Fig.12 is a schematic diagram illustrating a telecommunications network connected to a host computer via an intermediary network according to some embodiments.

[0421] Reference Fig.12According to an embodiment, the communication system includes a telecommunication network 1310, such as a 3GPP type cellular network, which includes an access network 1311, such as a radio access network, and a core network 1314. The access network 1311 includes a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each of which defines a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c may be connected to the core network 1314 via a wired or wireless connection 1315. A UE 1391 located in the coverage area 1313c is configured to be wirelessly connected to or paged by the corresponding base station 1312c. A relay UE 1392 located in the coverage area 1313a may be wirelessly connected to the corresponding base station 1312a. Although multiple UEs 1391, 1392 are shown in this example, the disclosed embodiments are equally applicable to situations where only a UE is in the coverage area or a only UE is connected to a corresponding base station 1312a, 1312b, 1312c.

[0422] The telecommunications network 1310 itself is connected to a host computer 1330, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server farm. The host computer 1330 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. Connections 1321 and 1322 between the telecommunications network 1310 and the host computer 1330 may extend directly from the core network 1314 to the host computer 1330, or may extend to the host computer 1330 through an optional intermediate network 1320. The intermediate network 1320 may be one of the following, or a combination of more than one of the following: a public network, a private network, or a hosted network; the intermediate network 1320, if any, may be a backbone network or the Internet; in particular, the intermediate network 1320 may include two or more sub-networks (not shown).

[0423] Fig.12The communication system as a whole enables connectivity between the connected UEs 1391, 1392 and the host computer 1330. The connectivity may be described as an over-the-top (OTT) connection 1350. The host computer 1330 and the connected UEs 1391, 1392 are configured to transmit data and / or signaling via the OTT connection 1350 using the access network 1311, the core network 1314, any intermediate networks 1320, and possible further infrastructure (not shown) as intermediaries. The OTT connection 1350 may be transparent in the sense that the participating communication devices through which the OTT connection 1350 passes are unaware of the routing of uplink and downlink communications. For example, the base stations 1312a, 1312b, 1312c may not or need to be informed of the past routing of incoming downlink communications having data originating from the host computer 1330 to be forwarded (e.g., handed over) to the connected UE 1391. Similarly, base stations 1312a , 1312b , 1312c need not be aware of the future routing of outgoing uplink communications originating from UE 1391 to host computer 1330 .

[0424] Fig.13 is a schematic diagram illustrating a host computer communicating with a user device over a partially wireless connection via a base station according to some embodiments.

[0425] According to the embodiment, reference will now be made to Fig.13 Describe the example implementations of the UE, base station, and host computer discussed in the previous paragraphs. In the communication system 1400, the host computer 1410 includes: hardware 1415, which includes a communication interface 1416, which is configured to establish and maintain a wired or wireless connection with the interface of different communication devices of the communication system 1400. The host computer 1410 further includes a processing circuit 1418, which may have storage and / or processing capabilities. In particular, the processing circuit 1418 may include: one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 1410 further includes software 1411, which is stored in the host computer 1410 or can be accessed by the host computer 1410 and can be executed by the processing circuit 1418. Software 1411 includes a host application 1412. The host application 1412 may operate to provide services to a remote user, such as a UE 1430 connected via an OTT connection 1450 terminated at the UE 1430 and the host computer 1410. In providing services to the remote user, the host application 1412 may provide user data sent using the OTT connection 1450.

[0426] The communication system 1400 further includes a base station 1420, which is provided in the telecommunication system and includes hardware 1425 that enables it to communicate with the host computer 1410 and the UE 1430. The hardware 1425 may include a communication interface 1426 for establishing and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 1400, and for communicating with devices located in the coverage area ( Fig.13 1420) establishes and maintains at least a radio interface 1427 of a wireless connection 1470. The communication interface 1426 may be configured to facilitate a connection 1460 to the host computer 1410. The connection 1460 may be direct, or it may be through a core network ( Fig.13 1420) and / or through one or more intermediate networks external to the telecommunications system. In the illustrated embodiment, the hardware 1425 of the base station 1420 further includes processing circuitry 1428, which may include: one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) adapted to execute instructions. The base station 1420 also has software 1421 stored internally or accessible via an external connection.

[0427] The communication system 1400 further includes the UE 1430 already mentioned. Its hardware 1435 may include a radio interface 1437, which is configured to establish and maintain a wireless connection 1470 with a base station serving the coverage area where the UE 1430 is currently located. The hardware 1435 of the UE 1430 further includes a processing circuit 1438, which may include: one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The UE 1430 further includes software 1431, which is stored in the UE 1430 or can be accessed by the UE 1430 and can be executed by the processing circuit 1438. The software 1431 includes a client application 1432. The client application 1432 can operate to provide services to human or non-human users via the UE 1430 with the support of the host computer 1410. In the host computer 1410, the executing host application 1412 can communicate with the executing client application 1432 by terminating the OTT connection 1450 at the UE 1430 and the host computer 1410. In providing services to users, the client application 1432 can receive request data from the host application 1412 and provide user data in response to the request data. The OTT connection 1450 can send both the request data and the user data. The client application 1432 can interact with the user to generate the user data it provides.

[0428] Notice, Fig.13The host computer 1410, base station 1420 and UE 1430 shown in FIG. Fig.12 The host computer 1330, one of the base stations 1312a, 1312b, 1312c and one of the UEs 1391, 1392 are similar or identical to each other. That is, the internal workings of these entities can be as follows Fig.13 As shown, and independently, the surrounding network topology can be Fig.12 The surrounding network topology.

[0429] exist Fig.13 14, an OTT connection 1450 has been abstractly drawn to illustrate communications between a host computer 1410 and a UE 1430 through a base station 1420, without explicit reference to any intermediate devices and the precise routing of messages via those devices. The network infrastructure can determine the routing, which can be configured to be hidden from the UE 1430 or from the service provider operating the host computer 1410, or from both. When the OTT connection 1450 is active, the network infrastructure can also make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0430] The wireless connection 1470 between the UE 1430 and the base station 1420 is in accordance with the teachings of the embodiments described throughout the present disclosure. One or more of the various embodiments use the OTT connection 1450 to improve the performance of the OTT service provided to the UE 1430, wherein the wireless connection 1470 forms the last segment. More precisely, in some embodiments herein, it can address KI#19 of 3GPP TR 23.700-98V1.1.1 in the ACR scenario determined by S-EAS, which allows S-EAS to determine one or more ACR scenarios or request S-EES to determine one or more ACR scenarios to be used. In some embodiments herein, it can address KI#19 of 3GPP TR 23.700-98V1.1.1 in the ACR scenario executed by S-EES, which allows S-EES to determine one or more ACR scenarios to be used. In some embodiments herein, the proposed solution provides a proactive way to reduce the system complexity for subsequent ACRs during ACRs triggered on the data network side. In some embodiments of this document, during EAS discovery, the ideal situation would be that AC, EEC, EES, and EAS support and only support exactly the same ACR scenarios. But in reality, it may be that a suitable T-EAS (satisfying the KPI (key performance indicator) requirements of AC) supports more ACR scenarios than S-EAS and S-EES or AC and EEC. Then, the ACR scenario selection solution determined by S-EES is used to make an ACR scenario selection for the appropriate T-EAS and notify the corresponding entity of the selection.

[0431] The measurement process may be provided for the purpose of monitoring data rates, delays, and other factors that are improved by one or more embodiments. There may also be optional network functions for reconfiguring the OTT connection 1450 between the host computer 1410 and the UE 1430 in response to changes in the measurement results. The measurement process and / or network functions for reconfiguring the OTT connection 1450 may be implemented in the software 1411 and hardware 1415 of the host computer 1410 or in the software 1431 and hardware 1435 of the UE 1430 or in both. In an embodiment, a sensor (not shown) may be deployed in or associated with a communication device through which the OTT connection 1450 passes; the sensor may participate in the measurement process by providing the values ​​of the monitoring quantities exemplified above or providing the values ​​of other physical quantities, and the software 1411, 1431 may calculate or estimate the monitoring quantities from the values ​​of other physical quantities. The reconfiguration of the OTT connection 1450 may include message formats, retransmission settings, preferred routes, etc.; the reconfiguration does not necessarily affect the base station 1420, and the base station 1420 may be unaware or imperceptible. Such processes and functions are known and practiced in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates host computer 1410 measurements of throughput, propagation time, latency, etc. The measurements may be implemented in software 1411 and 1431 that uses OTT connection 1450 to transmit messages (particularly null messages or "dummy" messages) while software 1411 and 1431 monitors propagation time, errors, etc.

[0432] Fig.14 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0433] Fig.14 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.12 and Fig.13 For the sake of brevity of this disclosure, this section will only include references Fig.14 . In step 1510, the host computer provides user data. In sub-step 1511 of step 1510 (which may be optional), the host computer provides the user data by executing a host application. In step 1520, the host computer initiates a transmission to the UE carrying the user data. In step 1530 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station sends the user data carried in the transmission initiated by the host computer to the UE. In step 1540 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0434] Fig.15 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0435] Fig.15 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.12 and Fig.13 For the sake of brevity of this disclosure, only references Fig.15 . In step 1610 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 1620, the host computer initiates a transmission to the UE carrying the user data. According to the teachings of the embodiments described throughout the present disclosure, the transmission may be passed via a base station. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

[0436] Fig.16 is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0437] Fig.16 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.12 and Fig.13 For the sake of brevity of this disclosure, this section will only include references Fig.16 . In step 1710 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1720, the UE provides user data. In sub-step 1721 of step 1720 (which may be optional), the UE provides user data by executing a client application. In sub-step 1711 of step 1710 (which may be optional), the UE executes a client application, which provides user data in response to the received input data provided by the host computer. In providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner of providing user data, the UE initiates the transmission of user data to the host computer in sub-step 1730 (which may be optional). In step 1740 of the method, according to the teachings of the embodiments described throughout the present disclosure, the host computer receives user data transmitted from the UE.

[0438] Fig.17is a schematic diagram illustrating a method implemented in a communication system including a host computer, a base station and a user equipment according to some embodiments.

[0439] Fig.17 is a flow chart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station and a UE, which can be reference Fig.12 and 13 For the sake of brevity of this disclosure, this section will only include references Fig.17 In step 1810 (which may be optional), in accordance with the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In step 1820 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1830 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0440] In addition, the present disclosure may also provide a carrier containing the above-mentioned computer program, wherein the carrier is one of an electronic signal, an optical signal, a radio signal or a computer-readable storage medium. The computer-readable storage medium may be, for example, an optical disc or an electronic storage device, such as a RAM (random access memory), a ROM (read-only memory), a flash memory, a magnetic tape, a CD-ROM, a DVD, a Blu-ray disc, etc.

[0441] The techniques described herein can be implemented in various ways so that the device that implements one or more functions of the corresponding device described in the embodiments includes not only prior art components, but also components for implementing one or more functions of the corresponding device described using the embodiments, and it can include separate components for each separate function, or can be configured as components that perform two or more functions. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For firmware or software, the implementation can be accomplished by modules (e.g., processes, functions, etc.) that perform the functions described herein.

[0442] Exemplary embodiments of the present invention have been described above with reference to block diagrams and flow charts of methods and apparatus. It will be understood that each block of the block diagrams and flow charts and combinations of blocks in the block diagrams and flow charts, respectively, can be implemented by various components including computer program instructions. These computer program instructions can be loaded onto a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, whereby the instructions executed on the computer or other programmable data processing device create components for implementing the functions specified in the flow chart block or blocks.

[0443] In addition, although the operations are depicted in a particular order, this should not be understood as requiring that the operations be performed in the particular order shown or in sequence, or that all illustrated operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although the above discussion contains several specific implementation details, these should not be interpreted as limitations on the scope of the subject matter described herein, but should be interpreted as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0444] Although this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of any implementation or the scope that may be claimed, but should be interpreted as descriptions of features that may be specific to a particular embodiment of a particular implementation. Certain features described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented separately in multiple embodiments or in any suitable sub-combination. In addition, although the above-mentioned features may be described as working in certain combinations and even initially claimed to be so protected, one or more features from the claimed combination may be deleted from the combination in some cases, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.

[0445] It is obvious to those skilled in the art that, with the advancement of technology, the inventive concept can be implemented in various ways. The above embodiments are given for the purpose of describing rather than limiting the present disclosure, and it should be understood that, as those skilled in the art will readily appreciate, modifications and variations can be made without departing from the spirit and scope of the present disclosure. Such modifications and variations are considered to be within the scope of the present disclosure and the appended claims. The scope of protection of the present disclosure is defined by the appended claims.

Claims

1. A method (300) performed by a first network node, comprising: Decide (302) to perform application context relocation ACR; as well as sending (304) a first message to a second network node, The first message includes information for requesting the second network node to select at least one ACR scenario to be used in the next ACR.

2. The method according to claim 1, wherein: The at least one ACR scenario to be used in the next ACR is supported by an application client AC, an edge enabler client EEC, a target edge application server EAS, and a target edge enabler server EES.

3. The method according to claim 1 or 2, wherein: The first network node comprises a source EES, and the second network node comprises a target EES.

4. The method according to any one of claims 1 to 3, further comprising: A fourth message is sent (354) to the EEC, wherein the fourth message includes the information about the at least one ACR scene to be used in the next ACR.

5. The method according to claim 4, wherein: The fourth message is a target information notification message.

6. The method according to any one of claims 1 to 5, wherein: The at least one ACR scenario includes at least one of the following: ACR initiated by EEC using regular EAS discovery, ACR performed by EEC via source EES, The ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via the target EES.

7. A method (400) performed by a second network node, comprising: receiving (402) a first message from a first network node, wherein the first message includes information for requesting the second network node to select at least one ACR scenario to be used in a next ACR; and The at least one ACR scene to be used in the next ACR is selected (404).

8. The method according to claim 7, wherein: The at least one ACR scenario to be used in the next ACR is supported by the AC, the EEC, the target EAS, and the target EES.

9. The method according to claim 7 or 8, wherein: The first network node comprises a source EES, and the second network node comprises a target EES.

10. The method according to any one of claims 7 to 9, further comprising: sending (424) a sixth message to the EEC, wherein the sixth message includes the information about the at least one ACR scene to be used in the next ACR; and / or A ninth message is sent (426) to the target EAS, wherein the ninth message includes the information about the at least one ACR scene to be used in the next ACR.

11. The method according to claim 10, wherein: The sixth message is a target information notification message.

12. The method according to any one of claims 7 to 11, wherein: The at least one ACR scenario includes at least one of the following: ACR initiated by EEC using regular EAS discovery, ACR performed by EEC via source EES, The ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via the target EES.

13. The method according to any one of claims 7 to 12, wherein: When the first network node comprises a source EES and the second network node comprises a target EES, the method further comprises: A message including information about the at least one ACR scenario to be used in the next ACR is sent (432) to the first network node.

14. A method (600) performed by a target EAS, comprising: An eighth message is received (602) from a target EES, wherein the eighth message includes information about at least one ACR scene to be used in a next ACR.

15. The method according to claim 14, further comprising: The information about the at least one ACR scene to be used in the next ACR is stored (604).

16. The method according to claim 14 or 15, wherein: The at least one ACR scenario to be used in the next ACR is supported by the AC, the EEC, the target EAS, and the target EES.

17. The method according to any one of claims 14 to 16, further comprising: Sending (612) an ACR scene selection subscription request to the target EES; as well as An ACR scene selection subscription response is received (614) from the target EES.

18. The method according to any one of claims 14 to 17, wherein: The eighth message is an ACR selection notification message.

19. The method according to any one of claims 14 to 18, wherein: The at least one ACR scenario includes at least one of the following: ACR initiated by EEC using regular EAS discovery, ACR performed by EEC via source EES, The ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via the target EES.

20. A method (620) performed by an EEC, comprising: In the ACR scenario, receiving (622) a message from the EES including information about at least one ACR scenario to be used in a next ACR; as well as The information about the at least one ACR scene to be used in the next ACR is stored (624).

21. The method according to claim 20, wherein: The at least one ACR scenario to be used in the next ACR is supported by the AC, the EEC, the target EAS, and the target EES.

22. The method according to claim 20 or 21, wherein: The message is a target information notification message.

23. The method according to any one of claims 20 to 22, wherein: The at least one ACR scenario includes at least one of the following: ACR initiated by EEC using regular EAS discovery, ACR performed by EEC via source EES, The ACR determined by the source EAS, ACR performed by the source EES, or ACR performed by the EEC via the target EES.

24. The method according to any one of claims 20 to 23, further comprising: A message including the information about the at least one ACR scenario to be used in the next ACR is sent (626) to the AC.

25. A first network node (800), comprising: Processor(821); as well as a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the first network node (800) is operable to: Decide to perform application context relocation ACR; as well as sending a first message to a second network node, The first message includes information for requesting the second network node to select at least one ACR scenario to be used in the next ACR.

26. The first network node according to claim 25, wherein: The first network node is further operable to perform the method of any one of claims 2 to 6.

27. A second network node (800), comprising: Processor(821); as well as a memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the second network node (800) is operable to: receiving a first message from a first network node, wherein the first message includes information for requesting the second network node to select at least one ACR scenario to be used in a next ACR; as well as The at least one ACR scene to be used in the next ACR is selected.

28. The second network node according to claim 27, wherein: The second network node is further operable to perform the method of any one of claims 8 to 13.

29. A target EAS (800), comprising: Processor(821); as well as A memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the target EAS (800) is operable to: An eighth message is received from the target EES, wherein the eighth message includes information about at least one ACR scene to be used in a next ACR.

30. The targeted EAS of claim 29, wherein: The target EAS is further operable to perform the method of any one of claims 15 to 19.

31. An EEC (800), comprising: Processor(821); as well as A memory (822) coupled to the processor (821), the memory (822) storing instructions executable by the processor (821), whereby the EEC (800) is operable to: In the ACR scenario, receiving a message including information about at least one ACR scenario to be used in a next ACR from the EES; as well as The information about the at least one ACR scene to be used in the next ACR is stored.

32. The EEC of claim 31, wherein: The EEC is further operable to perform the method of any one of claims 21 to 24.

33. A computer-readable storage medium storing instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 24.

34. A computer program product comprising instructions which, when executed by at least one processor, cause the at least one processor to perform the method according to any one of claims 1 to 24.

Images