Microservice communication and computing offloading via service mesh
Various embodiments herein provide techniques to enable communication between a user equipment (UE) microservice and a microservice of a wireless cellular network via service mesh. A first solution is described, in which the service mesh is in the network, and the network includes a service mesh proxy to communicate with the UE. A second solution is also described, in which the UE is part of the cellular network service mesh and includes a service mesh proxy in the UE. Other embodiments may be described and claimed.
1 . One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by a service mesh proxy, configure the service mesh proxy to:
receive a computing service request from a user equipment (UE), the computing service request including an indication of a service mesh container or information element (IE); and
encode a hypertext transfer protocol (HTTP) computing service request message for transmission to a service orchestration control function (SOCF) based on the computing service request from the UE.
2 . The one or more NTCRM of claim 1 , wherein the HTTP computing service request message includes an indication of: a computing resource requirement, a software version, a data rate, a quality-of-service (QOS) parameter, or a latency.
3 . The one or more NTCRM of claim 1 , wherein the service mesh proxy is implemented by an access and mobility management function (AMF).
4 . The one or more NTCRM of claim 3 , wherein the computing service request from the UE is received via a non-access stratum (NAS) message.
5 . The one or more NTCRM of claim 1 , wherein the service mesh proxy is implemented by centralized unit-control plane (CU-CP).
6 . The one or more NTCRM of claim 1 , wherein the computing service request from the UE is received via a radio resource control (RRC) message.
7 . The one or more NTCRM of claim 1 , wherein the instructions, when executed, are further to configure the service mesh proxy to:
receive, from the SOCF, a first response to the HTTP computing service request message; and
encode, for transmission to the UE, a second response based on the first response.
8 . The one or more NTCRM of claim 7 , wherein the first and second responses include an identifier associated with: a communication service function (Comm SF), a computing service function (Comp SF), or a microservice.
9 . An apparatus to be implemented in a user equipment (UE), the apparatus comprising:
a processor circuitry; and
a service mesh proxy to:
receive, from the processor circuitry, a first request for a computing service;
send, based on the first request, a second request for the computing service to a service orchestration control function (SOCF); and
receive, from the SOCF, a response that includes an identifier associated with the requested computing service.
10 . The apparatus of claim 9 , wherein the second request for the computing service is sent to the SOCF via an evolved service communication proxy (eSCP).
11 . The apparatus of claim 9 , wherein the processor circuitry is further to encode, for transmission to an access and mobility management function (AMF), a registration message, wherein the registration message includes an indication that the UE includes the service mesh proxy.
12 . The apparatus of claim 9 , wherein the service mesh proxy is further to receive, from a service infrastructure control function (SICF), configuration information to configure access and traffic management rules, security-related information, or discoverable services.
13 . The apparatus of claim 12 , wherein the configuration information from the SICF is received via an access and mobility management function (AMF) as a non-access stratum (NAS) message or as part of UE route selection policy information.
14 . The apparatus of claim 9 , wherein the processor circuitry is to run an application, and wherein the service mesh proxy is further to receive, from the application, a service mesh service registration request.
15 . One or more non-transitory computer-readable media (NTCRM) having instructions, stored thereon, that when executed by one or more processors configure a service orchestration control function (SOCF) to:
receive, from a service mesh proxy, a request for a computing service for a user equipment (UE);
determine one or more requirements for the computing service based on the request; and
send a message to a computing control function (Comp CF) via an evolved service communication proxy (eSCP) to indicate the one or more requirements.
16 . The one or more NTCRM of claim 15 , wherein the service mesh proxy is included in an access and mobility management function (AMF).
17 . The one or more NTCRM of claim 15 , wherein the service mesh proxy is included in the UE.
18 . The one or more NTCRM of claim 15 , wherein the request includes an identifier of the computing service, a UE identifier of the UE, and one or more of: a software version, a data rate, a quality of service, or a latency associated with the requested computing service.
19 . The one or more NTCRM of claim 15 , wherein the instructions, when executed, are further to configure the SOCF to send a request to a service infrastructure control function (SICF) via the eSCP to configure a service mesh for the computing service.
20 . The one or more NTCRM of claim 19 , wherein the request to the SICF indicates one or more traffic management rules for a user plane eSCP (eSCP-U).