Method and apparatus for application session information management in edge computing

Abstract

The embodiment of the invention provides a method and device for application session information management in edge computing. A method performed by an edge enabler server (EES) includes receiving a first request from an edge enabler client (EEC). The first request includes a service session context and first information indicating that an edge application server (EAS) is in use. The method further includes storing a service session context based on the first information.

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 devices for application session information management in edge computing. 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 fifth generation (5G) and expand the promise for a variety of new and enhanced use cases, including virtual and augmented reality, Internet of Things (IoT), Industrial Internet of Things, autonomous driving, real-time multiplayer gaming, etc.

[0004] In the 3rd Generation Partnership Project (3GPP) Release 17, 3GPP aims to provide native support for edge computing in 3GPP networks. These efforts include initiatives across multiple working groups in 3GPP, including SA6, SA2, SA3, SA4, and SA5, which cover application layer architecture, core network enhancements, security, media processing, and management, respectively.

[0005] SA6 initiated specification work on the normalization of an architecture for enabling edge applications (EDGEAPP). The goal of this work is to define an enabling layer to facilitate communication between an application client (AC) running on a user equipment (UE) and an edge application server (EAS) deployed on an edge data network. This includes aspects of service provisioning and EAS discovery. In addition, the work aims to provide support services such as application context transfer between EAS for service continuity, service enablement, and open APIs towards the capabilities of EAS.

[0006] 3GPP Technical Specification (TS) 23.558 V17.3.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.

[0007] Figure 1a A reference point representation of an architecture for edge-enabled applications is shown. Figure 1aSame as Figure 6.2-4 of 3GPPTS23.558V17.3.0. The edge data network (EDN) is a local data network. The edge application server and edge enabler server 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 an application client (AC) and an edge enabler client (EEC). The edge application server, edge enabler server and edge configuration server can interact with the 3GPP core network.

[0008] Functional entities include:

[0009] 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.

[0010] Edge Enabler Client (EEC): The EEC provides support functions required by the AC, such as retrieving and providing configuration information to enable application data services and EAS discovery.

[0011] 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.

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

[0013] 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 edge computing advantages.

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

[0015] In 3GPP Technical Report (TR) 23.700-98 V1.0.0, the disclosure of which is incorporated herein by reference in its entirety, there is KI #8 which mentions that "the EES procedure for determining EAS selection for a service session is not specified."

[0016] Additionally, Solution 15 of 3GPP TR 23.700-98 V1.0.0 includes an editorial note related to Service Session Context (SSC):

[0017] Editor's Note: Whether the EES can perform more operations (such as storing the SSC) and the timing for the AC to connect to the selected EAS are for future study (FFS).

[0018] Editor's Note: If the EEC is not registered with the EES prior to EAS discovery, whether and how the management of the SSC required by this solution can be provided is for future study.

[0019] Currently, solution 15 of 3GPP TR 23.700-98 V1.0.0 provides a method for EES to affect services for applications (ie, AC-EAS services) after determining EAS (due to EEC sending the selected EAS notification), but it does not solve the SSC problem.

[0020] Figure 1b A flow chart of an initial EAS selection statement (Solution 15) is shown. Figure 1b Compared with 3GPP TR 23.700-98V1.0.0 Figure 7 .15.2-1Same.

[0021] In this solution, the EES may be aware of the selected EAS, and the EES is enabled to trigger the EAS service impact after determining the initial EAS.

[0022] In steps 1 and 2, the EEC performs a startup process for initial service provisioning and EAS discovery. The EEC can send EAS discovery to multiple EESs. If the EES requires registration, the EEC will register with the EES before EAS discovery.

[0023] In step 3, the EEC (or AC and EEC) selects an initial EAS from the discovered EAS candidates.

[0024] In step 4, the EEC sends a selected EAS assertion request with the AC ID, EAS ID, EAS endpoint, and UE ID to the selected EES (which is determined according to the selected EAS).

[0025] In step 5, EES:

[0026] - If EAS service impact has not been performed before, EAS service impact can be applied based on the application KPI using the N6 routing information of EAS in the 3GPP core network.

[0027] Note 1: EES can also affect EAS services in advance.

[0028] The selected EES then responds to the EEC in step 6 with the request success / failure.

[0029] Editor's Note: Whether the EES can perform more operations (such as storing the SSC) and the timing for the AC to connect to the selected EAS are for future study.

[0030] NOTE 2: For simplicity, the AC is not shown in the above figure, and the solution for resolving the interaction between the AC and the EEC is related to steps 1 to 3 of KI#4 of 3GPP TR 23.700-98 V1.0.0.

[0031] Table 7.15.2-1 describes the information elements used for the selected EAS Notification Request sent from the EEC to the Serving EES.

[0032] Table 7.15.2-1: Selected EAS notification requests Information Elements state describe UE ID M UE identifier AC ID O Application Client ID Security credentials M Security credentials Selected EAS ID M The selected EAS identifier The selected EAS endpoint M The selected EAS endpoint Summary of the invention

[0033] 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.

[0034] Since there are outstanding issues related to SSC in solution 15 of 3GPP TR 23.700-98 V1.0.0, it is unclear how to handle SSC and the timing for the AC to connect to the selected EAS.

[0035] To overcome or mitigate at least one of the above-referenced issues or other issues, improved solutions for application session information management in edge computing may be desired.

[0036] In a first aspect of the present disclosure, a method performed by an edge enabler server (EES) is provided. The method may include receiving a first request from an edge enabler client (EEC). The first request may include a service session context and first information indicating that an edge application server (EAS) is in use. The method may further include storing the service session context based on the first information.

[0037] In an embodiment, the service session context may include at least one of an identifier of the EAS, endpoint information of the EAS, or an identifier of an application client (AC).

[0038] In an embodiment, the method may further include sending the first response to the EEC.

[0039] In an embodiment, the first request may allow the EES to know the application session information so that the EES can create a service session context for the initial application service.

[0040] In an embodiment, the service session context may be used for edge-specific operations or processing.

[0041] In an embodiment, the method may further include receiving a second request from the EEC. The second request may include second information indicating that the EAS is no longer in use. The method may further include removing the service session context based on the second information.

[0042] In a second aspect of the present disclosure, a method performed by an edge enabler client (EEC) is provided. The method may include determining an edge application server (EAS) for an application client (AC). The method may further include sending a first request to an edge enabler server (EES). The first request may include a service session context and first information indicating that the EAS is in use.

[0043] In an embodiment, determining that the EAS is used for the AC may include receiving a third request from the AC, and determining that the EAS is used for the AC based on the third request. The third request may include the service session context and the first information.

[0044] In an embodiment, the service session context may include at least one of an identifier of the EAS, endpoint information of the EAS, or an identifier of the AC.

[0045] In an embodiment, the method may further include receiving a first response from the EES.

[0046] In an embodiment, the first request may allow the EES to know the application session information so that the EES can create a service session context for the initial application service.

[0047] In an embodiment, the service session context may be used for edge-specific operations or processing.

[0048] In an embodiment, the method may further include determining that the EAS is no longer used for the AC. The method may further include sending a second request to the EES. The second request may include second information indicating that the EAS is no longer used for the AC.

[0049] In an embodiment, determining that the EAS is no longer used for the AC may include receiving a fourth request from the AC, and determining that the EAS is no longer used for the AC based on the fourth request. The fourth request may include the second information.

[0050] In a third aspect of the present disclosure, a method performed by an application client (AC) is provided. The method may include determining an edge application server (EAS) for the AC. The method may further include sending a third request to an edge enabler client (EEC). The third request may include a service session context and first information indicating that the EAS is in use.

[0051] In an embodiment, the service session context may include at least one of an identifier of the EAS, endpoint information of the EAS, or an identifier of the AC.

[0052] In an embodiment, the method may further include receiving a third response from the EEC.

[0053] In an embodiment, the third request allows the EES to know the application session information so that the EES can create a service session context for the initial application transaction.

[0054] In an embodiment, the service session context may be used for edge-specific operations or processing.

[0055] In an embodiment, the method may further include determining that the EAS is no longer used for the AC. The method may further include sending a fourth request to the EEC. The fourth request may include second information indicating that the EAS is no longer used for the AC.

[0056] In a fourth aspect of the present disclosure, an edge enabler server (EES) is provided. The EES may include a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The EES is operable to receive a first request from an edge enabler client (EEC). The first request may include a service session context and first information indicating that an edge application server (EAS) is in use. The EES is further operable to store a service session context based on the first information.

[0057] In a fifth aspect of the present disclosure, an edge enabler client (EEC) is provided. The EEC may include a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The EEC is operable to determine an edge application server (EAS) for an application client (AC). The EEC is further operable to send a first request to an edge enabler server (EES). The first request may include a service session context and first information indicating that the EAS is in use.

[0058] In a sixth aspect of the present disclosure, an application client (AC) is provided. The AC may include a processor and a memory coupled to the processor. The memory stores instructions executable by the processor. The AC is operable to determine an edge application server (EAS) for the AC. The AC is further operable to send a third request to an edge enabler client (EEC). The third request may include a service session context and first information indicating that the EAS is in use.

[0059] In another aspect of the present disclosure, an EES is provided. The EES may include a first receiving module configured to receive a first request from an edge enabler client (EEC). The first request may include a service session context and first information indicating that an edge application server (EAS) is in use. The EES may further include a storage module configured to store the service session context based on the first information.

[0060] In an embodiment, the EES may further include a sending module configured to send a first response to the EAS or the EEC.

[0061] In an embodiment, the EES may further include a second receiving module configured to receive a second request from the EEC. The second request may include second information indicating that the EAS is no longer in use.

[0062] In an embodiment, the EES may further include a removal module configured to remove the service session context based on the second information.

[0063] In another aspect of the present disclosure, an EEC is provided. The EEC may include a first determination module configured to determine an edge application server (EAS) for an application client (AC). The EEC may further include a first sending module configured to send a first request to an edge enabler server (EES). The first request may include a service session context and first information indicating that the EAS is in use.

[0064] In an embodiment, the EEC may further include a first receiving module configured to receive a first response from the EES.

[0065] In an embodiment, the EEC may further include a second determination module configured to determine that the EAS is no longer used for the AC.

[0066] In an embodiment, the EEC may further include a third sending module configured to send a second request to the EES. The second request may include second information indicating that the EAS is no longer used for the AC.

[0067] In another aspect of the present disclosure, an AC is provided. The AC may include a first determination module configured to determine that an edge application server (EAS) is used for the AC. The AC may further include a first sending module configured to send a third request to an edge enabler client (EEC). The third request may include a service session context and first information indicating that the EAS is in use.

[0068] In an embodiment, the AC may further include a receiving module configured to receive a third response from the EEC.

[0069] In an embodiment, the AC may further include a second determination module configured to determine that the EAS is no longer used for the AC.

[0070] In an embodiment, the AC may further include a second sending module configured to send a fourth request to the EEC. The fourth request may include second information indicating that the EAS is no longer used for the AC.

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

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

[0073] 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 and / or a terminal device (e.g., the AC and / or EEC described above).

[0074] 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.

[0075] 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 the terminal device includes a processing circuit configured to execute a client application associated with the host application.

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

[0077] 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.

[0078] 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, at the host computer, a transmission to the terminal device carrying the user data via a cellular network including the network node.

[0079] 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.

[0080] In another aspect of the present disclosure, a method implemented in a communication system is provided, and 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, at the host computer, a transmission to the terminal device carrying the user data via a cellular network including the network node. The terminal device may perform any steps of the method according to the second aspect and the third aspect of the present disclosure.

[0081] 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 second aspect and the third aspect of the present disclosure.

[0082] 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 receiving user data sent from the terminal device to the network node at the host computer, and the terminal device may perform any steps of the method according to the second aspect and the third aspect of the present disclosure.

[0083] 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 second aspect and the third aspect of the present disclosure.

[0084] 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.

[0085] 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.

[0086] The embodiments of this article may provide many advantages, and the following is a non-exhaustive list of examples of advantages. In some embodiments of this article, it solves the problem of SSC management. In some embodiments of this article, the EEC performs registration with the EES to provide information that the EES can use in edge computing services. In some embodiments of this article, the proposed solution enables initialization, updating, and deletion of EEC context information at the EES. The context can be further used for edge-specific operations or processing, such as analysis. In some embodiments of this article, the proposed solution solves KI#14 of 3GPP TR23.700-98V1.0.0. In some embodiments of this article, the EES is allowed to know the EAS selected in the initial service startup so that the EES can control the application business impact for the initial application business. In some embodiments of this article, the solution also solves KI#8 of 3GPP TR 23.700-98V1.0.0 to allow the EES to know the application session information so that the EES can create an SSC for the initial application business. It is a feasible solution. The embodiments herein are not limited to the above-mentioned 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

[0087] 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:

[0088] Figure 1a A reference point representation of an architecture for edge-enabled applications is shown;

[0089] Figure 1b A flow chart showing an initial EAS selection statement;

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0104] Figure 6c A flowchart showing how the EES according to an embodiment of the present disclosure knows the application session and creates a service session context;

[0105] Figure 6d A flowchart showing how the EES knows the application session and creates a service session context according to another embodiment of the present disclosure;

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

[0107] Figure 8a is a block diagram illustrating an EES according to an embodiment of the present disclosure;

[0108] Figure 8b is a block diagram illustrating an EEC according to an embodiment of the present disclosure;

[0109] Figure 8c is a block diagram illustrating an EAS according to another embodiment of the present disclosure;

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

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

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

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

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

[0115] 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;

[0116] 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;

[0117] 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;

[0118] 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

[0119] 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

[0120] 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 an 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.

[0121] 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 WCDMA and other variants of 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.

[0122] 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 AMF (Access and Mobility Management Function), SMF (Session Management Function), AUSF (Authentication Service Function), UDM (Unified Data Management), PCF (Policy Control Function), AF (Application Function), NEF (Network Exposure Function), UPF (User Plane Function) and NRF (Network Repository Function), RAN (Radio Access Network), SCP (Service Communication Agent), NWDAF (Network Data Analysis Function), NSSF (Network Slice Selection Function), NSSAAF (Network Slice Specific Authentication and Authorization Function), etc. For example, a 4G system (e.g., LTE) may include an MME (Mobility Management Entity), an HSS (Home Subscriber Server), a Policy and Charging Rules Function (PCRF), a Packet Data Network Gateway (PGW), a PGW Control Plane (PGW-C), a Serving Gateway (SGW), an SGW Control Plane, 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.

[0123] The term "terminal device" refers to any terminal device that can access a communication network and receive services therefrom. As an 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). Terminal devices may include, but are not limited to, portable computers, image capture terminal devices such as digital cameras, game terminal devices, music storage and playback devices, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablet computers, wearable devices, personal digital assistants (PDAs), portable computers, desktop computers, wearable terminal devices, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), 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.

[0124] 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 (e.g., 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.

[0125] References in the specification to "embodiment", "embodiment", "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. In addition, these phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, whether or not explicitly described, it is considered to be within the knowledge of those skilled in the art to affect such features, structures, or characteristics in relation to other embodiments.

[0126] 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, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0127] 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".

[0128] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that when used herein, the terms "including," "comprising," "having," “Having”, “containing” and / or “comprising” specifies the existence of stated features, elements and / or components etc., but does not preclude the existence or addition of one or more other features, elements, components and / or combinations thereof.

[0129] 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.

[0130] 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.

[0131] 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-2b For simplicity, the communication system of the exemplary system architecture shown is described. Figure 2a-2bThe 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.

[0132] 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), NSAAF (network slice specific authentication and authorization function), NSACF (network slice admission control function), etc.

[0133] According to an exemplary embodiment, Figure 2a As shown, the UE can establish a signaling connection with the AMF through reference point N1. The signaling connection can realize the NAS (non-access layer) signaling exchange between the UE and the core network, including the signaling connection between the UE and the (R)AN and the 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.

[0134] 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 the 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 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.

[0135] Figure 2aThe 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 TS 23.501 V17.2.0.

[0136] 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, and 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 accounting), SMS-SC / GMSC / IWMSC (short message service center / gateway MSC / interworking MSC), and 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.

[0137] The system architecture shows the architecture for UE for MTC, which is connected to the 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 the Um / Uu / LTE Uu interface. The system architecture also shows the opening of 3GPP network service capabilities for SCS and AS.

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

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

[0140] Tsp: A reference point used by the SCS for control plane signaling communications related to the MTC-IWF.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0154] Figure 3a A flow chart of a method according to an embodiment of the present disclosure is shown, which can be performed by a device implemented in an edge enabler server (EES), by a device implemented at an EES or by a device implemented as an EES, or by a device communicatively coupled to an EES. Therefore, the device can provide components or modules for implementing various parts of method 300, as well as components or modules for implementing other processes together with other components.

[0155] At block 302, the EES may receive a first request from an edge application server (EAS) or an edge enabler client (EEC). The first request includes a service session context and first information indicating that the EAS is in use.

[0156] In an embodiment, the EES may be the same as or similar to the EES described in 3GPP TS 23.558 V17.3.0.

[0157] In an embodiment, the EAS may be the same as or similar to the EAS described in 3GPP TS 23.558 V17.3.0.

[0158] In an embodiment, the EEC may be the same as or similar to the EEC described in 3GPP TS 23.558 V17.3.0.

[0159] The first request may be any suitable request, such as an existing request or a new request.

[0160] In an embodiment, the first request may include at least one of an application session declaration request or a selected EAS declaration request. For example, the selected EAS declaration request may be similar to the selected EAS declaration request described in 3GPP TR 23.700-98 V1.0.0, except that it also includes a service session context and first information indicating that EAS is in use.

[0161] The service session context may include any appropriate information related to the service session context. In an embodiment, the service session context may include information maintained by the EES for services (involving UE-related resources) received from an EAS registered with the EES.

[0162] In an embodiment, the service session context includes at least one of an identifier of the EAS, endpoint information of the EAS, or an identifier of an application client (AC).

[0163] For example, the endpoint information of the EAS may include, for example, a uniform resource identifier (URI), a fully qualified domain name (FQDN), an Internet Protocol (IP) address, etc. of the EAS.

[0164] For example, the first information may be represented by a bit, a flag, an indication, a bitmap, etc.

[0165] In an embodiment, the first request is received after the application client (AC) communicates with the EAS for the first time. When the EEC or EAS determines that the AC is communicating with the EAS for the first time, it can send the first request to the EES. For example, when the AC communicates with the EAS for the first time, it can inform the EEC of this information, and then the EEC can send the first request to the EES. When the AC communicates with the EAS for the first time, the EAS can detect this information and then send the first request to the EES.

[0166] In an embodiment, the first request allows the EES to know the application session information so that the EES can create a service session context for the initial application service.

[0167] In an embodiment, the service session context is used for edge-specific operations or processing, such as analytics.

[0168] In an embodiment, the first request may include at least one service session context and at least one corresponding first information indicating at least one corresponding EAS in use.

[0169] At block 304, the EES may store the service session context based on the first information.

[0170] At block 306, the EES may optionally send a first response to the EAS or EEC.

[0171] In an embodiment, the first response includes at least one of an application session assertion response or a selected EAS assertion response.

[0172] Figure 3b 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 edge enabler server (EES), by a device implemented at an EES, or by a device implemented as an EES, or by a device communicatively coupled to an EES. Therefore, the device can provide components or modules for implementing various parts of method 310, as well as components or modules for implementing other processes with other components.

[0173] At block 312, the EES may receive a second request from the EAS or the EEC. The second request includes second information indicating that the EAS is no longer in use.

[0174] In an embodiment, the second request may further include information indicating the service session context, such as a service session context identifier (ID) or AC ID.

[0175] In an embodiment, the second information may indicate that the EAS is no longer used for the AC or service session context.

[0176] The second request may be any suitable request, such as an existing request or a new request.

[0177] In an embodiment, the second request may be an application session declaration request.

[0178] For example, the second information may be represented by bits, flags, indicators, bitmaps, and the like.

[0179] When the EEC or EAS determines that the EAS is no longer in use, it can send a second request to the EES. For example, when the AC no longer uses the services of the EAS, it can inform the EEC of this information, and then the EEC can send a second request to the EES. When the AC no longer uses the services of the EAS, the EAS can detect this information and then send a second request to the EES.

[0180] In an embodiment, the second request may include at least one information indicating at least one service session context and at least one corresponding second information indicating that at least one corresponding EAS is no longer used.

[0181] At block 314 , the EES may remove the service session context based on the second information.

[0182] At block 316, the EES may optionally send a second response to the EAS or EEC.

[0183] Figure 3c 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 edge enabler server (EES), by a device implemented at an EES, or by a device implemented as an EES, or by a device communicatively coupled to an EES. Therefore, the device can provide components or modules for implementing various parts of method 320, as well as components or modules for implementing other processes with other components.

[0184] At block 322, the EES may receive a first request from an edge enabler client (EEC). The first request may include a service session context and first information indicating that an edge application server (EAS) is in use.

[0185] At block 324 , the EES may store the service session context based on the first information.

[0186] At block 326, the EES may optionally send a first response to the EEC.

[0187] Figure 3dA 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 edge enabler server (EES), by a device implemented at an EES, or by a device implemented as an EES, or by a device communicatively coupled to an EES. Therefore, the device can provide components or modules for implementing various parts of method 330, as well as components or modules for implementing other processes with other components.

[0188] At block 332, the EES may receive a second request from the EEC. The second request may include second information indicating that the EAS is no longer in use.

[0189] At block 334 , the EES may remove the service session context based on the second information.

[0190] At block 336, the EES may optionally send a second response to the EEC.

[0191] Figure 4a A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in an edge enabler client (EEC), by a device implemented at an EEC, or by a device implemented as an EEC, or by a device communicatively coupled to an EEC. Therefore, the device can provide components or modules for implementing various parts of method 400, as well as components or modules for implementing other processes together with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0192] At block 402, the EEC may determine that an edge application server (EAS) is used for an application client (AC). The EEC may determine that the EAS is used for the AC in various ways. For example, the EEC may detect packets between the AC and the EAS. When it has detected packets between the AC and the EAS, it may determine that the EAS is used for the AC. Alternatively, the AC may notify the EEC of this information, and the EEC may then determine that the EAS is used for the AC.

[0193] At block 404, the EEC may send a first request to an edge enabler server (EES). The first request includes a service session context and first information indicating that the EAS is in use.

[0194] At block 406, the EEC may optionally receive a first response from the EES.

[0195] In an embodiment, the service session context includes at least one of an identifier of the EAS, endpoint information of the EAS, or an identifier of the AC.

[0196] In an embodiment, the first request includes at least one of an application session assertion request or a selected EAS assertion request.

[0197] In an embodiment, the first request is sent after the application client (AC) communicates with the EAS for the first time.

[0198] In an embodiment, the first request allows the EES to know the application session information so that the EES can create a service session context for the initial application service.

[0199] In an embodiment, the service session context is used for edge-specific operations or processing.

[0200] Figure 4b A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in an edge enabler client (EEC), by a device implemented at an EEC, or by a device implemented as an EEC, or by a device communicatively coupled to an EEC. Therefore, the device can provide components or modules for implementing various parts of method 410, as well as components or modules for implementing other processes together with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0201] At block 412, the EEC may receive a third request from the AC. The third request may include the service session context and the first information.

[0202] At block 414, the EEC may determine that the EAS is for the AC based on the third request.

[0203] At block 416, the EEC may optionally send a third response to the AC.

[0204] Figure 4c A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in an edge enabler client (EEC), by a device implemented at an EEC, or by a device implemented as an EEC, or by a device communicatively coupled to an EEC. Therefore, the device can provide components or modules for implementing various parts of method 420, as well as components or modules for implementing other processes together 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 422, the EEC may determine that the EAS is no longer in use with the AC.

[0206] At block 424, the EEC may send a second request to the EES. The second request includes second information indicating that the EAS is no longer used for the AC.

[0207] At block 426, the EEC may optionally receive a second response from the EES.

[0208] In an embodiment, the second request may further include information indicating the service session context, such as a service session context identifier (ID) or AC ID.

[0209] Figure 4d A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in an edge enabler client (EEC), by a device implemented at an EEC, or by a device implemented as an EEC, or by a device communicatively coupled to an EEC. Therefore, the device can provide components or modules for implementing various parts of method 430, as well as components or modules for implementing other processes together with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0210] At block 432, the EEC may receive a fourth request from the AC. The fourth request includes the second information.

[0211] In an embodiment, the fourth request may further include information indicating the service session context, such as a service session context identifier (ID) or an AC ID.

[0212] At block 434, the EEC may determine that the EAS is no longer used for the AC based on the fourth request.

[0213] At block 436 , the EEC may optionally send a fourth response to the AC.

[0214] 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 an edge application server (EAS), by a device implemented at an EAS, or by a device implemented as an EAS, or by a device communicatively coupled to an EAS. 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 together with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0215] At block 502, EAS may determine that EAS is for an application client (AC). For example, EAS may detect packets between AC and EAS. When it detects packets between AC and EAS, it may determine that EAS is for AC.

[0216] At block 504, the EAS may send a first request to an edge enabler server (EES). The first request includes a service session context and first information indicating that the EAS is in use.

[0217] In an embodiment, the service session context includes at least one of an identifier of the EAS, endpoint information of the EAS, or an identifier of the AC.

[0218] In an embodiment, the first request is an application session declaration request.

[0219] In an embodiment, the first request is sent after the AC first communicates with the EAS.

[0220] In an embodiment, the first request allows the EES to know the application session information so that the EES can create a service session context for the initial application service.

[0221] In an embodiment, the service session context is used for edge-specific operations or processing.

[0222] At block 506, the EAS may optionally receive a first response from the EES.

[0223] 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 an edge application server (EAS), by a device implemented at an EAS or by a device implemented as an EAS, or by a device communicatively coupled to an EAS. 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 together with other components. For some parts that have been described in the above embodiments, their description is omitted here for the sake of brevity.

[0224] At block 512, the EAS may determine that the EAS is no longer used for the AC.

[0225] At block 514, the EAS may send a second request to the EES. The second request includes second information indicating that the EAS is no longer for the AC.

[0226] At block 516, the EAS may optionally receive a second response from the EES.

[0227] In an embodiment, a method for an EES to manage an SSC is provided.

[0228] In an embodiment, the AC indicates its EAS usage information to the EEC.

[0229] In an embodiment, the EEC indicates the EAS usage information of the AC to the EES.

[0230] In an embodiment, the proposed solution may address SSC EN in solution #15 of 3GPP TR 23.700-98 V1.0.0 (Editor's note).

[0231] After EAS discovery, the timing of connecting to the selected EAS is determined by AC. After EAS connection, AC can notify EEC that "EAS is in use" so that the following EN (Editor's Note) can be resolved.

[0232] Editor's Note: Whether the EES can perform more operations (such as storing SSC) and the timing for AC connection to the selected EAS is FFS.

[0233] In an embodiment, the EAS selection statement / notification with the selected EAS is used to affect the service before the initial AC-EAS service starts. The actual time when the AC starts to communicate with the EAS is determined by the AC and is after the EEC notifies the EES of the EAS selection. This is also reflected in the solution #33 of 3GPP TR 23.700-98 V1.0.0, where the EAS use phase is after the EAS selection phase. Therefore, for SSC processing, it should be part of the EAS use phase.

[0234] In an embodiment, the SSC is a list of application session information and may be decoupled from the EEC context (ie, if no EEC context is created, the SSC is created solely by the EES).

[0235] Figure 6a A flowchart of a method according to another embodiment of the present disclosure is shown, which can be performed by a device implemented in an AC, performed by a device implemented at an AC, or performed by a device implemented as an AC, or performed by a device communicatively coupled to an AC. Therefore, the device can provide components or modules for implementing various parts of method 600, as well as components or modules for implementing other processes together 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 602, the AC may determine that an EAS is for the AC.

[0237] At block 604, the AC may send a third request to an edge enabler client (EEC). The third request includes the service session context and the first information indicating that the EAS is in use.

[0238] At block 606, the AC may optionally receive a third response from the EEC.

[0239] In an embodiment, the service session context includes at least one of an identifier of the EAS, endpoint information of the EAS, or an identifier of the AC.

[0240] In an embodiment, the third request is an application session declaration request.

[0241] In an embodiment, the third request is sent after the AC first communicates with the EAS.

[0242] In an embodiment, the third request allows the EES to know the application session information so that the EES can create a service session context for the initial application transaction.

[0243] In an embodiment, the service session context is used for edge-specific operations or processing.

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

[0245] At block 612, the AC may determine that the EAS is no longer used for the AC.

[0246] At block 614, the AC may send a fourth request to the EEC. The fourth request includes second information indicating that the EAS is no longer used for the AC.

[0247] At block 616, the AC may optionally receive a fourth response from the EEC.

[0248] Figure 6c A flowchart showing how the EES learns about the application session and creates a service session context according to an embodiment of the present disclosure.

[0249] In step 1, the EAS discovery and selection process occurs between the AC, EEC, and EES. After determining the EAS, the AC communicates with the selected EAS. For example, the EAS discovery and selection process may be the same as those described in 3GPP TS23.558 V17.3.0.

[0250] In step 2, the AC sends an application session declaration request to the EEC, which includes the AC ID, EAS ID, EAS endpoint, and EAS in use information. The AC may include a list of application session information in the request.

[0251] In step 3. EEC sends an application session declaration request to EES, including the information received from AC.

[0252] In step 4. after receiving the application session declaration request, EES stores the service session context.

[0253] In step 5-6. EES responds to EEC with an Application Session Assertion Response, and EEC further responds to AC.

[0254] Table 7.15.2-2 describes the information elements used for the service session context, which is managed by the EES if the EEC is not registered with the EES.

[0255] Table 7.15.2-2: Service Session Context Table 7.15.2-2: Service Session Context

[0256] Figure 6d A flowchart showing how the EES learns about the application session and creates a service session context according to another embodiment of the present disclosure.

[0257] After contacting the AC, the EAS may also use the application session announcement to inform the EES that "EAS is in use".

[0258] In step 1, the EAS discovery and selection process occurs between the AC, EEC, and EES. After determining the EAS, the AC communicates with the selected EAS. For example, the EAS discovery and selection process may be the same as those described in 3GPP TS23.558 V17.3.0.

[0259] In step 2, EAS sends an application session declaration request to EES, which includes AC ID, EAS ID, EAS endpoint, and information about EAS in use. EAS can include a list of application session information in the request.

[0260] In step 3. EES stores the service session context after receiving the application session declaration request.

[0261] In step 4. EES responds to EAS with an Application Session Assertion Response.

[0262] In an embodiment, the proposed solution addresses KI#14 of 3GPP TR 23.700-98 V1.0.0. It allows EES to know the selected EAS in the initial service startup so that EES can control the application service impact for the initial application service. The solution also addresses KI#8 of 3GPP TR 23.700-98 V1.0.0 to allow EES to know the application session information so that EES can create an SSC for the initial application service. This is a feasible solution.

[0263] Whether a new selected EAS declaration notification API is needed or an existing API (eg, EEC registration) can be reused is for future study.

[0264] The embodiments of this article may provide many advantages, and the following is a non-exhaustive list of examples of advantages. In some embodiments of this article, it solves the problem of SSC management. In some embodiments of this article, the EEC performs registration with the EES to provide information that the EES can use in edge computing services. In some embodiments of this article, the proposed solution enables initialization, updating, and deletion of EEC context information at the EES. The context can be further used for edge-specific operations or processing, such as analysis. In some embodiments of this article, the proposed solution solves KI#14 of 3GPP TR23.700-98V1.0.0. In some embodiments of this article, the EES is allowed to know the EAS selected in the initial service startup so that the EES can control the application business impact for the initial application business. In some embodiments of this article, the solution also solves KI#8 of 3GPP TR 23.700-98V1.0.0 to allow the EES to know the application session information so that the EES can create an SSC for the initial application business. It is a feasible solution. The embodiments herein are not limited to the above-mentioned features and advantages. Those skilled in the art will recognize additional features and advantages after reading the following detailed description.

[0265] Figure 7 700 is a block diagram showing an apparatus suitable for practicing some embodiments of the present disclosure. For example, any of the above-mentioned EES, EEC, AC or EAS can be implemented as or by the apparatus 700.

[0266] The device 700 includes at least one processor 721, such as a digital processor (DP), and at least one memory (MEM) 722 coupled to the processor 721. The device 700 may further include a transmitter TX and a receiver RX 723 coupled to the processor 721. The MEM 722 stores a program (PROG) 724. The PROG 724 may include instructions that, when executed on the associated processor 721, enable the device 700 to operate according to embodiments of the present disclosure. The combination of the at least one processor 721 and the at least one MEM 722 may form a processing device 725 suitable for implementing various embodiments of the present disclosure.

[0267] Various embodiments of the present disclosure may be implemented by a computer program executable by one or more of the processor 721 , software, firmware, hardware, or a combination thereof.

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

[0269] Processor 721 may be of any type suitable to the local technical environment, and may include one or more of the following: as non-limiting examples, 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.

[0270] In embodiments where the apparatus is implemented as or at an EES, the memory 722 stores instructions executable by the processor 721 such that the EES operates according to any of the methods described above in relation to the EES.

[0271] In embodiments where the apparatus is implemented as or at an EEC, the memory 722 stores instructions executable by the processor 721 such that the EEC operates according to any of the methods described above in relation to the EEC.

[0272] In embodiments where the apparatus is implemented as or at an EAS, the memory 722 stores instructions executable by the processor 721 such that the EAS operates according to any of the methods described above in relation to the EAS.

[0273] In embodiments where the apparatus is implemented as or at an AC, the memory 722 stores instructions executable by the processor 721 such that the AC operates according to any of the methods described above in relation to the AC.

[0274] Figure 8a 800 is a block diagram illustrating an EES according to an embodiment of the present disclosure. As shown in the figure, the EES 800 includes a first receiving module 801, which is configured to receive a first request from an edge enabler client (EEC). The first request may include a service session context and first information indicating that an edge application server (EAS) is in use. The EES 800 also includes a storage module 802, which is configured to store a service session context based on the first information.

[0275] In an embodiment, the EES 800 may further include a sending module 803 configured to send a first response to the EAS or the EEC.

[0276] In an embodiment, the EES 800 may further include a second receiving module 804 configured to receive a second request from the EAS or the EEC. The second request includes second information indicating that the EAS is no longer in use.

[0277] In an embodiment, the EES 800 may further include a removal module 805 configured to remove the service session context based on the second information.

[0278] Figure 8b 820 according to an embodiment of the present disclosure. As shown in the figure, the EEC 820 includes a first determination module 821, which is configured to determine an edge application server (EAS) for an application client (AC). The EEC 820 also includes a first sending module 822, which is configured to send a first request to an edge enabler server (EES). The first request includes a service session context and first information indicating that the EAS is in use.

[0279] In an embodiment, the EEC 820 may further include a first receiving module 823 configured to receive a first response from the EES.

[0280] In an embodiment, the EEC 820 may further include a second sending module 824 configured to send a third response to the AC.

[0281] In an embodiment, the EEC 820 may further include a second determination module 825 configured to determine that the EAS is no longer used for the AC.

[0282] In an embodiment, the EEC 820 may further include a third sending module 826 configured to send a second request to the EES. The second request includes second information indicating that the EAS is no longer used for the AC.

[0283] Figure 8c 840 includes a first determining module 841 configured to determine an EAS for an application client (AC). The EAS 840 also includes a first sending module 842 configured to send a first request to an edge enabler server (EES). The first request includes a service session context and first information indicating that the EAS is in use.

[0284] In an embodiment, the EAS 840 may further include a receiving module 843 configured to receive a first response from the EES.

[0285] In an embodiment, the EAS 840 may further include a second determination module 844 configured to determine that the EAS is no longer used for the AC.

[0286] In an embodiment, the EAS 840 may further include a second sending module 845 configured to send a second request to the EES. The second request includes second information indicating that the EAS is no longer used for the AC.

[0287] Figure 8d 850 includes a first determining module 851 configured to determine an EAS for the AC. The AC 850 also includes a first sending module 852 configured to send a third request to an edge enabler client (EEC). The third request includes a service session context and first information indicating that the EAS is in use.

[0288] In an embodiment, the AC 850 may further include a receiving module 853 configured to receive a third response from the EEC.

[0289] In an embodiment, the AC 850 may further include a second determination module 854 configured to determine that the EAS is no longer used for the AC.

[0290] In an embodiment, the AC 850 may further include a second sending module 855 configured to send a fourth request to the EEC. The fourth request includes second information indicating that the EAS is no longer used for the AC.

[0291] The term unit or module may have a conventional meaning in the field of electronic devices, electrical equipment and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logical solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, output and / or display functions, etc., such as those described herein.

[0292] By using functional units, EES, EEC, AC or EAS does not need fixed processors or memory, and any computing resources and storage resources can be arranged 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.

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

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

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

[0296] 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; a communication interface configured to forward the user data to a cellular network for transmission to a terminal device. The cellular network includes a base station and / or a terminal device such as the AC or EEC described above.

[0297] 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.

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

[0299] 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 transmitted from a terminal device. The transmission is from the terminal device to the base station.

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

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

[0302] Although the subject matter described herein can 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. 9 The 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 can provide communication and other types of services to one or more wireless devices to facilitate wireless devices to access and / or use services provided by or via the wireless network.

[0303] A wireless network may include an interface 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.

[0304] 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 communication between devices.

[0305] The network node 1060 and the 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 over a wired or wireless connection.

[0306] 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 the wireless device and / or perform other functions (e.g., management) in the 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 may then 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 MSR BS), 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 a wireless device to access a wireless network and / or provide access to a wireless network to a wireless device or provide certain services to a wireless device that has accessed a wireless network.

[0307] 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).

[0308] 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 a variety of illustrated components for various 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 .

[0309] The processing circuit 1070 is configured to perform any determination, calculation, or similar operation (e.g., certain obtaining operations) described herein as being 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.

[0310] The processing circuit 1070 may include a combination of one or more of 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 that can operate alone or in conjunction with other network node 1060 components (e.g., device readable medium 1080) to provide network node 1060 functionality. For example, the processing circuit 1070 may execute instructions stored in the device readable medium 1080 or a memory within the processing circuit 1070. Such functionality 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).

[0311] 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.

[0312] In certain embodiments, some or all of the functionality described herein as being 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 functionality 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 functionality, whether or not executing instructions stored on a device-readable storage medium. The benefits provided by such functionality are not limited to processing circuit 1070 or 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.

[0313] The device-readable medium 1080 may include any form of volatile or non-volatile computer-readable memory, including but not limited to a permanent storage device that stores information, data, and / or instructions that can be used by the processing circuit 1070, 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. The device-readable medium 1080 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions that can be executed by the processing circuit 1070 and used by the network node 1060. The device-readable medium 1080 may be used to store any calculations made by the processing circuit 1070 and / or any data received through the interface 1090. In some embodiments, processing circuit 1070 and device readable medium 1080 may be considered integrated.

[0314] 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 port / terminal 1094 which is used to send and receive data to network 1006 via wired connection. Interface 1090 further includes 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. 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 WD via wireless connection. Radio front-end circuit 1092 can use the combination of filter 1098 and / or amplifier 1096 to convert digital data into radio signals with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1062. Similarly, when receiving data, antenna 1062 may collect the radio signal, which may then be converted into digital data by radio front end circuit 1092. The digital data may be passed to processing circuit 1070. In other embodiments, the interface may include different components and / or different combinations of components.

[0315] 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).

[0316] 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 from devices within a specific area to / from devices within 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, the use of 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.

[0317] 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.

[0318] 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 to perform 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 corresponding 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) through 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.

[0319] 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.

[0320] 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 sending 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-computer 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 transmit 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-car equipment (LMEs), smart devices, wireless client equipment (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, in which case it 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 transmits the results of such monitoring and / or measurement to another WD and / or a 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.

[0321] 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., 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 in WD 1010.

[0322] 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 WD. Any information, data and / or signal may be received from a network node and / or another WD. In some embodiments, radio front end circuit and / or antenna 1011 may be considered as an interface.

[0323] 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 regulate 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 the 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.

[0324] 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 encoded logic, which can operate to provide WD 1010 functionality alone or in conjunction with other WD 1010 components (e.g., device readable medium 1030). Such functionality 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 functionality disclosed herein.

[0325] 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 into one chip or a set of chips, and the RF transceiver circuit 1022 may be on a separate chip or a set of chips. 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.

[0326] 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 particular 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 separate processing circuits 1020 or other components of the WD 1010, but are generally enjoyed by the WD 1010 and / or by end users and wireless networks.

[0327] 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 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.

[0328] The device-readable medium 1030 is operable to store a computer program, software, application including one or more of logic, rules, code, tables, etc., and / or other instructions executable by the processing circuit 1020. The readable medium 1030 may include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disk (CD) or a 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 may be used by the processing circuit 1020. In some embodiments, the processing circuit 1020 and the device-readable medium 1030 may be considered integrated.

[0329] 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 a variety of 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.

[0330] Auxiliary device 1034 is operable to provide more specific functions that are not normally 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.

[0331] 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 accessories 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) through an interface such as an input circuit or a power cord. In some embodiments, the power circuit 1037 may be further used 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 modification to the power from the power source 1036 to make the power suitable for the various components of the WD 1010 being powered.

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

[0333] Fig.10 An embodiment of a UE according to various aspects described herein is illustrated. 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 specific 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). UE1100 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 configured to communicate according to 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.

[0334] exist Fig.10In the embodiment, UE 1100 includes a processing circuit 1101 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 1133, 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 include 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.

[0335] 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.

[0336] 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 key, 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.

[0337] 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 be implemented separately.

[0338] 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, application programs, 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), startup or receiving 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 of a variety of different operating systems for use 1100 by the UE.

[0339] 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 disc 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.

[0340] exist Fig.10In the embodiment, 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 according to one or more communication protocols (e.g., IEEE802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.) and one or more remote transceivers of another device capable of wireless communication, such as another WD, UE or a 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 suitable for a RAN link (e.g., frequency allocation, etc.). In addition, the transmitter 1133 and the receiver 1135 of each transceiver can share circuit components, software or firmware, or can be implemented separately.

[0341] 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 AC power (AC) or direct current (DC) power to the components of the UE 1100.

[0342] The features, benefits and / or functions described herein may be implemented in one of the components of UE1100 or divided across multiple components of UE1100. 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.

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

[0344] Fig.11 is a schematic block diagram illustrating a virtualization 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 network 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).

[0345] 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.

[0346] 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.), which 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 executable by processing circuitry 1260, whereby applications 1220 are operable to provide one or more features, benefits, and / or functionality disclosed herein.

[0347] The virtualized environment 1200 includes a general or special purpose network hardware device 1230, which includes a set of one or more processors or processing circuits 1260, which may be commercial off-the-shelf (COTS) processors, dedicated 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 executable by the processing circuit 1260 are 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 allows them to perform functions, features, and / or benefits associated with some embodiments described herein.

[0348] The virtual machine 1240 includes virtual processing, virtual memory, virtual network or interface, 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 at one or more virtual machines 1240 and may be implemented in different ways.

[0349] 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 to virtual machines 1240 a virtual operating platform that appears to be network hardware.

[0350] like Fig.11As shown, hardware 1230 can be an independent 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 life cycle management of application 1220.

[0351] 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.

[0352] 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).

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

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

[0355] 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 .

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

[0357] 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 the corresponding base station 1312a, 1312b, 1312c.

[0358] 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. The 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).

[0359] Fig.12The communication system as a whole enables connectivity between connected UEs 1391, 1392 and a 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, the base stations 1312a , 1312b , 1312c need not be aware of the future routing of outgoing uplink communications from the UE 1391 to the host computer 1330 .

[0360] 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.

[0361] 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 computer application 1412. The host computer application 1412 may be used 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 computer application 1412 may provide user data sent using the OTT connection 1450.

[0362] 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 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 (eg, a wireless network) of the telecommunications system. 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.

[0363] The communication system 1400 further includes the UE 1430 already mentioned. Its hardware 1435 may include a wireless 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 be used 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 computer 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 a service to a user, the client application 1432 may receive request data from the host computer application 1412 and provide user data in response to the request data. The OTT connection 1450 may send both the request data and the user data. The client application 1432 may interact with the user to generate the user data it provides.

[0364] Notice, Fig.13The host computer 1410, base station 1420 and UE 1430 shown can be connected with 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 may be similar to Fig.13 As shown, and independently, the surrounding network topology can be Fig.12 The surrounding network topology.

[0365] exist Fig.13 , an OTT connection 1450 has been abstractly drawn to illustrate communications between a host computer 1410 and a UE 1430 via a base station 1420, without explicit reference to any intermediate devices and the precise routing of messages via those devices. The network infrastructure may determine the routing, which may 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 may further make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or reconfiguration of the network).

[0366] The wireless connection 1470 between UE1430 and base station 1420 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments use OTT connection 1450 to improve the performance of OTT services provided to UE1430, wherein wireless connection 1470 forms the last segment. More specifically, in some embodiments herein, it solves the problem with SSC management. In some embodiments herein, EEC performs registration with EES to provide information that EES can use in edge computing services. In some embodiments herein, the proposed solution enables initialization, updating, and deletion of EEC context information at EES. The context can be further used for edge-specific operations or processing, such as analysis. In some embodiments herein, the proposed solution solves KI#14 of 3GPP TR 23.700-98V1.0.0. In some embodiments herein, EES is allowed to know the EAS selected in the initial service startup so that EES can control the application service impact on the initial application service. In some embodiments herein, the solution also addresses KI#8 of 3GPP TR23.700-98 V1.0.0 to allow EES to know application session information so that EES can create SSC for initial application service. It is a feasible solution.

[0367] The measurement process may be provided for the purpose of monitoring the data rate, latency and other factors improved by one or more embodiments. There may also be an optional network function 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 function 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 value of the monitoring quantity exemplified above or providing the value of other physical quantities, and the software 1411, 1431 may calculate or estimate the monitoring quantity from the value 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.

[0368] 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.

[0369] 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 only includes 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 computer 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 computer application executed by the host computer.

[0370] 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.

[0371] 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 to 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 computer 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 can be passed through a base station. In step 1630 (which may be optional), the UE receives the user data carried in the transmission.

[0372] 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.

[0373] 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 only includes 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 (which may be optional) of step 1720, the UE provides user data by executing a client application. In sub-step 1711 (which may be optional) of step 1710, the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further 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, in accordance with the teachings of the embodiments described throughout the present disclosure, the host computer receives user data sent from the UE.

[0374] 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.

[0375] 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 only includes references Fig.17 In step 1810 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout the present disclosure. 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.

[0376] In addition, the present disclosure may further 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.

[0377] 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 with the embodiments includes not only prior art components, but also components for implementing one or more functions of the corresponding device described with the embodiments, and it can include separate components for each separate function or components that can be configured to 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.

[0378] Exemplary embodiments of the present invention have been described above with reference to the block diagrams and flowchart illustrations of the methods and apparatus. It will be understood that each block of the block diagrams and flowchart illustrations and combinations of blocks in the block diagrams and flowchart illustrations, 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 flowchart block or blocks.

[0379] 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 results. 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.

[0380] Although this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of any implementation or the scope of what may be claimed, but rather 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 in multiple embodiments individually or in any suitable sub-combination. In addition, although the above-mentioned features may be described as working in certain combinations, or even initially claimed to be so protected, in some cases one or more features from the claimed combination may be deleted from the combination, and the claimed combination may be directed to a sub-combination or a variation of the sub-combination.

[0381] It is obvious to those skilled in the art that, as technology advances, 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 (320) performed by an edge enabler server EES, comprising: receiving (322) a first request from an edge enabler client EEC, wherein the first request includes a service session context and first information indicating that an edge application server EAS is in use; and Based on the first information, the service session context is stored (324).

2. The method according to claim 1, wherein: The service session context includes at least one of the following: the EAS identifier, The EAS endpoint information, or The identifier of the application client.

3. The method according to any one of claims 1 to 2, further comprising: A first response is sent (326) to the EEC.

4. The method according to any one of claims 1 to 3, wherein: The first request allows the EES to know application session information so that the EES can create the service session context for the initial application service.

5. The method according to any one of claims 1 to 4, wherein: The service session context is used for edge-specific operations or processing.

6. The method according to any one of claims 1 to 5, further comprising: receiving (332) a second request from the EEC, wherein the second request includes second information indicating that the EAS is no longer in use; and Based on the second information, the service session context is removed (334).

7. A method (400) performed by an edge enabler client EEC, comprising: Determine (402) an edge application server EAS for the application client AC; as well as A first request is sent (404) to an edge enabler server EES, wherein the first request includes a service session context and first information indicating that the EAS is in use.

8. The method according to claim 7, wherein: Determining that the EAS is used for the AC includes: receiving (412) a third request from the AC, wherein the third request includes the service session context and the first information; and The EAS is determined (414) to be used for the AC based on the third request.

9. The method according to any one of claims 7 or 8, wherein: The service session context includes at least one of the following: the EAS identifier, The EAS endpoint information, or The identifier of the AC.

10. The method according to any one of claims 7 to 9, further comprising: A first response is received (406) from the EES.

11. The method according to any one of claims 7 to 10, wherein: The first request allows the EES to know application session information so that the EES can create the service session context for the initial application service.

12. The method according to any one of claims 7 to 11, wherein: The service session context is used for edge-specific operations or processing.

13. The method according to any one of claims 7 to 12, further comprising: determining (422) that the EAS is no longer used for the AC; as well as A second request is sent (424) to the EES, wherein the second request includes second information indicating that the EAS is no longer used for the AC.

14. The method according to claim 13, wherein: Determining that the EAS is no longer used for the AC includes: receiving (432) a fourth request from the AC, wherein the fourth request includes the second information; and Based on the fourth request, it is determined (434) that the EAS is no longer used for the AC.

15. A method (600) performed by an application client AC, comprising: Determine (602) an edge application server EAS for the AC; as well as A third request is sent (604) to the edge enabler client EEC, wherein the third request includes a service session context and first information indicating that the EAS is in use.

16. The method according to claim 15, wherein: The service session context includes at least one of the following: the EAS identifier, The EAS endpoint information, or The identifier of the AC.

17. The method according to any one of claims 15-16, further comprising: A third response is received (606) from the EEC.

18. The method according to any one of claims 15 to 17, wherein: The third request allows the EES to know the application session information so that the EES can create the service session context for the initial application service.

19. The method according to any one of claims 15 to 18, wherein: The service session context is used for edge-specific operations or processing.

20. The method according to any one of claims 15 to 19, further comprising: Determining (612) that the EAS is no longer used for the AC; as well as A fourth request is sent (614) to the EEC, wherein the fourth request includes second information indicating that the EAS is no longer used for the AC.

21. An edge enabler server EES (700), comprising: Processor (721); and A memory (722) coupled to the processor (721), the memory (722) storing instructions executable by the processor (721), whereby the EES (700) is operable to: receiving a first request from an edge enabler client EEC, wherein the first request includes a service session context and first information indicating that an edge application server EAS is in use; as well as The service session context is stored based on the first information.

22. The EES of claim 21, wherein The EES is further operable to perform the method of any one of claims 2 to 6.

23. An edge enabler client EEC (700), comprising: Processor (721); and A memory (722) coupled to the processor (721), the memory (722) storing instructions executable by the processor (721), whereby the EEC (700) is operable to: Determine an edge application server EAS for the application client AC; and A first request is sent to an edge enabler server EES, wherein the first request includes a service session context and first information indicating that the EAS is in use.

24. The EEC of claim 23, wherein: The EEC is further operable to perform the method of any one of claims 8 to 14.

25. An application client AC (700), comprising: Processor (721); and A memory (722) coupled to the processor (721), the memory (722) storing instructions executable by the processor (721), whereby the AC (700) is executable to: Determine an edge application server EAS for the AC; and A third request is sent to the edge enabler client EEC, wherein the third request includes a service session context and first information indicating that the EAS is in use.

26. The AC according to claim 25, wherein The AC is further operable to perform the method of any one of claims 16 to 20.

27. 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 20.

28. 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 20.

Images