WO2023150605A1

WO2023150605A1 - Service mesh enabled sixth generation (6g) architecture

Info

Publication number: WO2023150605A1
Application number: PCT/US2023/061828
Authority: WO
Inventors: Zongrui DING; Qian Li; Xiaopeng Tong; Alexandre Saso STOJANOVSKI; Thomas Luetzenkirchen; Sudeep Palat; Ching-Yu Liao; Abhijeet Kolekar; Sangeetha L. Bangolae; Youn Hyoung Heo
Original assignee: Intel Corporation
Priority date: 2022-02-02
Filing date: 2023-02-02
Publication date: 2023-08-10

Abstract

Various embodiments herein provide techniques related to implementation of a service infrastructure control function (SICF). In embodiments, the SICF may interact, with an evolved service communication proxy for control plane (eSCP-C) or an evolved service communication proxy for user plane (eSCP-U). In embodiments, the interaction may related to configuration of the eSCP-C and/or the eSCP-U. Other embodiments may be described and/or claimed.

Description

SERVICE MESH ENABLED SIXTH GENERATION (6G) ARCHITECTURE

CROSS REFERENCE TO RELATED APPLICATION

The present application claims priority to U.S. Provisional Patent Application No. 63/305,787, which was filed February 2, 2022.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to sixth generation (6G) wireless networks.

BACKGROUND

Various embodiments generally may relate to the field of wireless communications.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

Figure 1 illustrates an example 6G architecture with a service mesh as a communication infrastructure, in accordance with various embodiments.

Figure 2 illustrates an alternative 6G architecture with a service mesh as a communication infrastructure, in accordance with various embodiments.

Figure 3 illustrates an example service mesh configuration through a service infrastructure control function (SICF), in accordance with various embodiments.

Figure 4 illustrates an example technique related to network function (NF) subscription to a service mesh telemetry, statistics, or traces, in accordance with various embodiments.

Figure 5 illustrates an example technique related to a query to an SICF for service discovery with defined criteria, in accordance with various embodiments.

Figure 6 illustrates an example technique related to an SICF leveraging a network repository function (NRF) as a repository for an evolved service communication proxy’s (eSCP’s) status, in accordance with various embodiments.

Figure 7 illustrates an example technique related to eSCP registration to an SICF, in accordance with various embodiments.

Figure 8 illustrates an example technique related to SICF configuration procedure for an eSCP-control plane (eSCP-C) and eSCP-user plane (eSCP-U), in accordance with various embodiments.

Figure 9 illustrates an example technique related to a distributed procedure for eSCP monitoring, in accordance with various embodiments. Figure 10 depicts an example procedure for practicing the various embodiments discussed herein.

Figure 11 schematically illustrates a wireless network in accordance with various embodiments.

Figure 12 schematically illustrates components of a wireless network in accordance with various embodiments.

Figure 13 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

Figure 14 schematically illustrates an alternative wireless network, in accordance with various embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

As used herein, the term “Service Mesh” may refer to a configurable infrastructure layer for microservices applications to facilitate service to service communications. There may be control plane and data planes for a service mesh. The control plane function may not affect or control the packets/requests in the network, but may provide policy and configuration for all of the running data planes in the mesh. The data plane function(s) may act as proxies that surrogate packets and requests in the system and may be responsible for service discovery, telemetry, routing, load balancing, authentication/authorization, and observability. The protocols among the microservices may be, for example, hypertext transfer protocol (HTTP), remote procedure call (RPC), etc.

In the fifth generation (5G) architecture, service mesh has been considered as a potential infrastructure to connect control plane functions and a Service Communication Proxy (SCP) as defined, for example, in section 6.2.19 of the third generation partnership project (3GPP) technical specification (TS) 23.501. For 5G networks, service mesh may only be used to facilitate the communication among control plane (CP) functions. In sixth generation (6G) networks or other beyond fifth generation (5G) (B5G) networks, the user plane functions may be virtualized as microservices in the network. Additionally, there may also be computing tasks, microservices from applications, etc. These are functions, tasks, or microservices may be virtual function instances which can be highly dynamic. The communication among these instances may be very challenging. For 6G network architecture with further cloudification, the service mesh may provide connectivity among different network functions on control plane as well as service instances on user plane. To efficiently configure and monitor these function or service instances, interfaces and functions are needed to be aware of the cellular network information such as policies and status, and a user equipment’s (UE’s) information.

Embodiments herein may relate to one or more of the following:

• How to provide an interface to the control plane functions in the cellular network to monitor, configure the 3 GPP aware service mesh for CP and user plane (UP)?

• How to manage the service proxies provided by service mesh to monitor the CP/UP functions and service instances?

• How to maintain a repository of the CP/UP functions and service instances to facilitate service discovery?

Specifically, embodiments may relate to a network function service infrastructure control function (SICF) to provide an interface to monitor, configure the eSCP-C and eSCP-U functions, which are the communication proxies provided by service mesh infrastructure for control plane (CP) service mesh and user plane (UP) service mesh respectively. The procedure for the network function (NF) to interact with SICF, the procedures for SICF to interact with eSCPs and for eSCPs to interact with each other may also be present in various embodiments. SICF can also leverage NRF to maintain the repository of eSCPs for registration, monitoring, service discovery, etc.

An example 6G architecture is shown in Figure 1 (Optionl) and Figure 2 (Option2), where the described functions are indicated with alternating dot/dash lines to enable service meshes for control plane and user plane functions, as well as UE connects to the CP via a service based interface (SBI) named Nue (although the name may be different in other embodiments). In this architecture, the 6G network includes a communication plane, computing plane, and data plane functions as defined in [1], The functions may include the Service Infrastructure Control Function (SICF), Evolved Service Communication Proxy for Control plane (eSCP-C), and Evolved Service Communication Proxy for User plane (eSCP-U). There may be various options for the eSCP-U to connect to the SICF. One such option may be to use an SBI called Nescpu (Optionl, as indicated in Figure 1). Another option may be to use a non-SBI, i.e., Nsm4 (Option2, as indicated in Figure 2).

The CP service mesh may interconnect the CP functions where there are multiple eSCP-C instances. The CP functions connect to the corresponding eSCP-C via Nescpc. The UP service mesh interconnects the UP functions where there are multiple eSCP-U instances. The UP functions connect to the corresponding eSCP-U via Nsml or Nsm2. SICF may configure eSCPs via Nescpc or Nescpu (Nsm4). (Note that, in some embodiments, the UP service mesh may be optional for some UE or services. A UE can have the tunnel based user plane per its services). The term eSCP may be used herein to refer to one or both of the eSCP-C and eSCP-U.

The functions described herein may include:

• Service Infrastructure Control Function (SICF) o SICF provides the SBI for other functions to configure the eSCP-Cs or eSCP-Us(which will conduct and enforce the policy according to the configuration) for the following

■ The traffic management rules on routing, access rules, load balancing, etc.

■ Information about service discovery

■ the required statistics/telemetry/tracing policy configuration for monitoring

■ the security policy and configuration o SICF provides a repository of the microservices 3GPP specific services and corresponding endpoints in the cellular infrastructure which may include one or more logic service meshes. SICF also provides the SBI for NF to query about the information in the repository for an NF or service instance with defined criteria

■ NF can subscribe to the status change or information of the NF in CP or microservices in UP, and get notifications about the information. o SICF provides centralized monitoring policy (telemetry for example) for the eSCP-Cs and eSCP-Us. Or SICF facilitate a distributed monitoring between eSCP-Cs and eSCP-Us which will enforce the policy and conduct the monitor

• Evolved Service Communication Proxy for Control plane (eSCP-C) o eSCP-C is the service mesh proxy for control plane functions, which can be configured, queried, and monitored by SICF for CP traffic rules, statistics ■ Support 3 GPP specific rules such as “allowedNetworkSlice”, “allowedUE,” etc.

■ Service Discovery within each eSCP-c cluster

■ L7 Traffic Management (load balance, route to different destination subsets, traffic split among the different subsets of destination services)

■ L7 Security Policies Enforcement

■ L7 Proxy and TLS Termination

■ Telemetry (running metrics)

■ Storage to save polices, thus support client-side discovery methodology.

■ Besides above proxy(sidecar) feature, it should also support ingress/egress functions for inter-connectivity among the different clusters

• Evolved Service Communication Proxy for User plane (eSCP-U) o eSCP-U is the service mesh proxy for user plane functions and other microservices such as application instances, which can be configured, queried, and monitored by SICF for UP traffic rules, statistics o Support 3GPP specific rules such as “allowedNetworSlice,” “allowedUE,” etc. o L3 Network Service Discovery within each eSCP-U cluster o L3 Traffic Management (load balance, routing) o Security based on technology like SPIFFE o Telemetry (running metrics) o Storage to save polices, thus support client-side discovery methodology o Beside above proxy(sidecar) feature, it should also support ingress/egress functions for inter-connectivity among the different clusters

For a service mesh enabled 6G network, respective CP or UP function(s) or microservice(s) may have a corresponding eSCP, which forms the service mesh data plane, intercepts the traffic from these function instances, and monitors the status of these instances. The CP or UP function or microservice instance are generally referred to as a function instance in this disclosure.

From the function and deployment aspect, SICF may play a centralized service mesh controller, handles request from orchestration type NFs like SOCF, and configures eSCP-C and eSCP-U with policy. Example procedures between NF and SICF

Example service mesh configuration through SICF

NF can request related configuration to be applied to eSCP-C or eSCP-U through SICF as shown in the example technique of Figure 3 although it will be understood that other techniques may include or relate to more/fewer/different elements or parameters. The service mesh configuration can be UE related or UE non-related.

1) NF sends a service mesh configuration request to SICF. This request may include configuration indications or information about one or more of the following (although, it will be noted, the below are intended as examples and other embodiments may have more/fewer/different parameters): a. Traffic management rules, e.g., Routing, load-balancing

■ The message may include the identifier of the function(s), UE identifier(s), the traffic filter and the routing rule or loadbalancing rule. For example, the identifier of a function can be used to identify the corresponding eSCP-C or eSCP-U that needs to be configured. The identifier can be in the form of an existing identifier such as GUAMI, DNN, S-NSSAI, URL or an IP address: port number, etc.. The traffic filter can identify the key words in a URL or a special S-NSSAI, or combination of these identifiers. The routing rule and load balancing rule can include how to process the traffic such as the proportion of the traffic to different instances. The routing rule can also include the effective time window for the routing and load balancing rules, which can be based on the state of a UE or PDU session. b. Access policy and rules

■ The message may include whether an identified entity can be allowed to access the service mesh or not. For example, the access policy can include a UE ID which is allowed to access the service mesh based on UE’s RRC states or CN states.

■ And the access policy also can specify the access permission from specific network slice (S-NSSAI), specific consumer services. ■ Overall, the access policy should contain 3 GPP specific information as below example for SMF NF :

c. Security

■ The message may include the identifiers and related security credentials such as private and public keys. For example, the identifiers can be used to identify a UE, a group of UE, or a network slice, etc. The security credentials can be used to configure the eSCP-C and eSCP-U for authentication and encryption, etc.

2) SICF sends a service mesh configuration response to the NF, which may include the results of the request such as success or failure. If the configuration is not successful, a cause may be included.

Example NF subscription to SICF for service mesh related information

SICF can maintain the repository of the eSCPs, and further the CP, UP functions or in- network micro-services that may be behind a Comp SF. NF can subscribe to SICF about this information such as telemetry, traffic statistics and traces and get notified about a status change or information, as shown in the example technique of Figure 4. The technique of Figure 4 may include one or more of the following, although it will be noted that the technique may be different in different embodiments and include additional or alternative elements.

1) NF sends a request for subscription to telemetry, statistics or traces to SICF. The message may include the identifiers and requested telemetry, statistics and tracing requirements. For example, the identifiers can be used to identify the related eSCP-C and eSCP-U, which can collect the data based on the rules for telemetry or data collection for statistics and tracing.

2) SICF sends a response for subscription to telemetry, statistics or traces to the requesting NF. This message includes the subscription results to indicate whether it is successful or failed. If failed, a reason may be included. 3) When the subscription criteria are met, SICF sends a notification to the NF about the subscribed information or status change.

4) NF sends an acknowledgement about the receipt of the notification.

Example NF query SICF for service discovery

SICF as the infrastructure control function can assist the service discovery when eSCP- C/eSCP-U can not find suitable instances according to the criteria from NFs based the preconfigured policies. Then NFs can send service discovery request to SICF to find the appropriate instances according to the request criteria.

SICF may maintain a repository about the NFs in the CP service mesh and the microservices in the UP service mesh. When a function instance is brought up, an associated eSCP shall be configured with the SICF identifier managing the service mesh that the function instance belongs to. Service discovery is defined as finding the specific identifier(AKA endpoint) for a function instance, e.g., the IP address: port number, Thus consumer NF instance can talk with producer NF instance.

The difference between SICF repository and NRF is that SICF may not only maintain the information about the 6G functions, i.e., CP and UP functions, but also the information about the microservices in the cellular network service mesh. NF or eSCP-C/eSCP-U can query SICF for service discovery with certain criteria as shown in Figure 5. Specifically, the information described below and the elements depicted in Figure 5 will be understood to be examples of one embodiment, and other embodiments may include more/fewer/different elements or parameters.

1) NF or eSCP-C/eSCP-U can send a service discovery request with criteria to SICF to discovery other NF or microservices. This request can come from NF or eSCP-C or eSCP-U via Nsicf. The criteria may include the following: a. Location b. Application, DNN, S-NSSAI, etc. c. Performance such as response time, capacity, capabilities

2) SICF responds with the information related to the function or service instances that meet the criteria. The response may include the identifiers of the function or service instances, how to access the service such as IP address: port number, etc.

Example SICF management procedure for eSCPs

Example SICF leveraging NRF to find appropriate eSCP-C or eSCP-U SICF can leverage NRF to maintain a repository of the eSCPs. The SICF can retrieve a list of eSCPs based on the criteria provided to NRF as shown in the example technique of Figure 6. It will be understood that, in other embodiments, the technique may have more/fewer/different elements or parameters than are depicted in Figure 6.

1) eSCPs send registration request to NRF with information such as the serving microservices, NF information, location, IP addresses, port numbers, access rules, etc. For example, CU-service can be described as:

Specs-Services:

ServiceName: URI CU Services

Loaction: TAC1

ServiceList { Neu Al RR Service, Neu Session}

NetworkSlice: NSSAI A

Specs- Traffic-Policy: loadBalancer:

3GPP: PF(proportional to fairness)

Specs-Access-Rules

IsLimitedUEAccess {UE SUP I? HTTP token? }

IsLimitedNetworkSliceAccess {ComputeSlice-Vendor A }

IsLimitedProducerServiceA ccess {

SOCF [Neu Al RRM Service ], AMF [Neu Session ]

2) NRF sends registration response to eSCPs to confirm the registration.

3) SICF sends a request with the criteria of the eSCPs to NRF to retrieve a list of the eSCPs.

4) NRF sends a response with the matched eSCP instances information to SICF, including access rules, IP addresses, port numbers, location, status, etc.

SICF maintaining the status information about eSCPs

In this case, the SICF maintains the registry of the eSCP related information without using a NRF as shown in the example technique of Figure 7, although it will be understood that other techniques may include or relate to more/fewer/different elements or parameters.

1) eSCP sends registration request to SICF similar to Step 1) in 5.1.4. eSCP can also send status update such as whether a NF or microservice instance is running, stopped or in error. 2) Upon receive the registration request or status update request, SICF shall update the NF or microservice information in its repository and sends the response message to confirm the receipt of the request.

SICF configuration procedure for eSCP-C and eSCP-U

SICF may configure the eSCPs following the procedure shown in the example technique of Figure 8, although it will be understood that other techniques may include or relate to more/fewer/different elements or parameters.

1) SICF sends an eSCP configuration request to the eSCP-C/eSCP-U. This request can be used to configure the following: a. Access rules b. Traffic management: routing c. Security credential distribution: distribute keys, telemetry

2) eSCP sends an eSCP configuration response to confirm that the configuration is applied. If the configuration is failed, the message shall include a reason for the failure. eSCP monitoring procedures

SICF can subscribe to eSCP information similar to the procedure in 5.1.2. When the subscription notification conditions are met, the eSCP-C and eSCP-U can send notifications to the SICF. This monitoring procedure is centralized and maintained by SICF. eSCP can subscribe to the other eSCP information and status in a distributed way as shown in the example technique of Figure 9, although it will be understood that other techniques may include or relate to more/fewer/different elements or parameters.

1) eSCP sends a request to subscribe to the information or status of another eSCP. This information can include: a. the subscriber’s identity, security credential, UE related information b. the status of the function instance: running, stopped or in error c. the performance, e.g., response time, packet loss of the function instance d. the service details about the function instance such as publisher, version e. the computing resource occupied by the function instance such as the number of GPUs and accelerators

2) eSCP can optionally send a request to SICF to get authorized about the subscription 3) SICF sends a response to the eSCP who sends the request to confirm or reject the subscription request

4) eSCP sends a response to indicate whether the subscription request is successful and the cause of a failure.

SYSTEMS AND IMPLEMENTATIONS

Figures 11-14 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 11 illustrates a network 1100 in accordance with various embodiments. The network 1100 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3 GPP systems, or the like.

The network 1100 may include a UE 1102, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1104 via an over-the-air connection. The UE 1102 may be communicatively coupled with the RAN 1104 by a Uu interface. The UE 1102 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

In some embodiments, the network 1100 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 1102 may additionally communicate with an AP 1106 via an over-the-air connection. The AP 1106 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 1104. The connection between the UE 1102 and the AP 1106 may be consistent with any IEEE 802.11 protocol, wherein the AP 1106 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 1102, RAN 1104, and AP 1106 may utilize cellular- WLAN aggregation (for example, LWA/LWIP). Cellular- WLAN aggregation may involve the UE 1102 being configured by the RAN 1104 to utilize both cellular radio resources and WLAN resources. The RAN 1104 may include one or more access nodes, for example, AN 1108. AN 1108 may terminate air-interface protocols for the UE 1102 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 1108 may enable data/voice connectivity between CN 1120 and the UE 1102. In some embodiments, the AN 1108 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 1108 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 1108 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In embodiments in which the RAN 1104 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 1104 is an LTE RAN) or an Xn interface (if the RAN 1104 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs of the RAN 1104 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 1102 with an air interface for network access. The UE 1102 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 1104. For example, the UE 1102 and RAN 1104 may use carrier aggregation to allow the UE 1102 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 1104 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 1102 or AN 1108 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 1104 may be an LTE RAN 1110 with eNBs, for example, eNB 1112. The LTE RAN 1110 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSLRS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 1104 may be an NG-RAN 1114 with gNBs, for example, gNB 1116, or ng-eNBs, for example, ng-eNB 1118. The gNB 1116 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 1116 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 1118 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 1116 and the ng-eNB 1118 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 1114 and a UPF 1148 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN1114 and an AMF 1144 (e.g., N2 interface).

The NG-RAN 1114 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSLRS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G-NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH. In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 1102 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 1102, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 1102 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 1102 and in some cases at the gNB 1116. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 1104 is communicatively coupled to CN 1120 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 1102). The components of the CN 1120 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 1120 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 1120 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1120 may be referred to as a network sub-slice.

In some embodiments, the CN 1120 may be an LTE CN 1122, which may also be referred to as an EPC. The LTE CN 1122 may include MME 1124, SGW 1126, SGSN 1128, HSS 1130, PGW 1132, and PCRF 1134 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 1122 may be briefly introduced as follows.

The MME 1124 may implement mobility management functions to track a current location of the UE 1102 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 1126 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 1122. The SGW 1126 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 1128 may track a location of the UE 1102 and perform security functions and access control. In addition, the SGSN 1128 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 1124; MME selection for handovers; etc. The S3 reference point between the MME 1124 and the SGSN 1128 may enable user and bearer information exchange for inter-3 GPP access network mobility in idle/active states. The HSS 1130 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 1130 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 1130 and the MME 1124 may enable transfer of subscription and authentication data for authenticating/authorizing user access to the LTE CN 1120.

The PGW 1132 may terminate an SGi interface toward a data network (DN) 1136 that may include an application/content server 1138. The PGW 1132 may route data packets between the LTE CN 1122 and the data network 1136. The PGW 1132 may be coupled with the SGW 1126 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 1132 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 1132 and the data network 11 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 1132 may be coupled with a PCRF 1134 via a Gx reference point.

The PCRF 1134 is the policy and charging control element of the LTE CN 1122. The PCRF 1134 may be communicatively coupled to the app/content server 1138 to determine appropriate QoS and charging parameters for service flows. The PCRF 1132 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 1120 may be a 5GC 1140. The 5GC 1140 may include an AUSF 1142, AMF 1144, SMF 1146, UPF 1148, NSSF 1150, NEF 1152, NRF 1154, PCF 1156, UDM 1158, and AF 1160 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 1140 may be briefly introduced as follows.

The AUSF 1142 may store data for authentication of UE 1102 and handle authentication- related functionality. The AUSF 1142 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 1140 over reference points as shown, the AUSF 1142 may exhibit an Nausf service-based interface.

The AMF 1144 may allow other functions of the 5GC 1140 to communicate with the UE 1102 and the RAN 1104 and to subscribe to notifications about mobility events with respect to the UE 1102. The AMF 1144 may be responsible for registration management (for example, for registering UE 1102), connection management, reachability management, mobility management, lawful interception of AMF -related events, and access authentication and authorization. The AMF 1144 may provide transport for SM messages between the UE 1102 and the SMF 1146, and act as a transparent proxy for routing SM messages. AMF 1144 may also provide transport for SMS messages between UE 1102 and an SMSF. AMF 1144 may interact with the AUSF 1142 and the UE 1102 to perform various security anchor and context management functions. Furthermore, AMF 1144 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 1104 and the AMF 1144; and the AMF 1144 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 1144 may also support NAS signaling with the UE 1102 over an N3 IWF interface.

The SMF 1146 may be responsible for SM (for example, session establishment, tunnel management between UPF 1148 and AN 1108); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 1148 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 1144 over N2 to AN 1108; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 1102 and the data network 1136.

The UPF 1148 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 1136, and a branching point to support multi-homed PDU session. The UPF 1148 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF- to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1148 may include an uplink classifier to support routing traffic flows to a data network.

The NSSF 1150 may select a set of network slice instances serving the UE 1102. The NSSF 1150 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 1150 may also determine the AMF set to be used to serve the UE 1102, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 1154. The selection of a set of network slice instances for the UE 1102 may be triggered by the AMF 1144 with which the UE 1102 is registered by interacting with the NSSF 1150, which may lead to a change of AMF. The NSSF 1150 may interact with the AMF 1144 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 1150 may exhibit an Nnssf service-based interface.

The NEF 1152 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 1160), edge computing or fog computing systems, etc. In such embodiments, the NEF 1152 may authenticate, authorize, or throttle the AFs. NEF 1152 may also translate information exchanged with the AF 1160 and information exchanged with internal network functions. For example, the NEF 1152 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 1152 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 1152 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1152 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 1152 may exhibit an Nnef servicebased interface.

The NRF 1154 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 1154 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 1154 may exhibit the Nnrf service-based interface.

The PCF 1156 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 1156 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 1158. In addition to communicating with functions over reference points as shown, the PCF 1156 exhibit an Npcf service-based interface.

The UDM 1158 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 1102. For example, subscription data may be communicated via an N8 reference point between the UDM 1158 and the AMF 1144. The UDM 1158 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 1158 and the PCF 1156, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1102) for the NEF 1152. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 1158, PCF 1156, and NEF 1152 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM- FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 1158 may exhibit the Nudm service-based interface.

The AF 1160 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 1140 may enable edge computing by selecting operator/3^rd party services to be geographically close to a point that the UE 1102 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 1140 may select a UPF 1148 close to the UE 1102 and execute traffic steering from the UPF 1148 to data network 1136 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1160. In this way, the AF 1160 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 1160 is considered to be a trusted entity, the network operator may permit AF 1160 to interact directly with relevant NFs. Additionally, the AF 1160 may exhibit an Naf service-based interface.

The data network 1136 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 1138.

Figure 12 schematically illustrates a wireless network 1200 in accordance with various embodiments. The wireless network 1200 may include a UE 1202 in wireless communication with an AN 1204. The UE 1202 and AN 1204 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.

The UE 1202 may be communicatively coupled with the AN 1204 via connection 1206. The connection 1206 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 1202 may include a host platform 1208 coupled with a modem platform 1210. The host platform 1208 may include application processing circuitry 1212, which may be coupled with protocol processing circuitry 1214 of the modem platform 1210. The application processing circuitry 1212 may run various applications for the UE 1202 that source/sink application data. The application processing circuitry 1212 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 1214 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 1206. The layer operations implemented by the protocol processing circuitry 1214 may include, for example, MAC, RLC, PDCP, RRC and NAS operations. The modem platform 1210 may further include digital baseband circuitry 1216 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 1214 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 1210 may further include transmit circuitry 1218, receive circuitry 1220, RF circuitry 1222, and RF front end (RFFE) 1224, which may include or connect to one or more antenna panels 1226. Briefly, the transmit circuitry 1218 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 1220 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 1222 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 1224 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 1218, receive circuitry 1220, RF circuitry 1222, RFFE 1224, and antenna panels 1226 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 1214 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 1226, RFFE 1224, RF circuitry 1222, receive circuitry 1220, digital baseband circuitry 1216, and protocol processing circuitry 1214. In some embodiments, the antenna panels 1226 may receive a transmission from the AN 1204 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 1226.

A UE transmission may be established by and via the protocol processing circuitry 1214, digital baseband circuitry 1216, transmit circuitry 1218, RF circuitry 1222, RFFE 1224, and antenna panels 1226. In some embodiments, the transmit components of the UE 1204 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 1226.

Similar to the UE 1202, the AN 1204 may include a host platform 1228 coupled with a modem platform 1230. The host platform 1228 may include application processing circuitry 1232 coupled with protocol processing circuitry 1234 of the modem platform 1230. The modem platform may further include digital baseband circuitry 1236, transmit circuitry 1238, receive circuitry 1240, RF circuitry 1242, RFFE circuitry 1244, and antenna panels 1246. The components of the AN 1204 may be similar to and substantially interchangeable with like- named components of the UE 1202. In addition to performing data transmission/reception as described above, the components of the AN 1208 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Figure 13 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 13 shows a diagrammatic representation of hardware resources 1300 including one or more processors (or processor cores) 1310, one or more memory/storage devices 1320, and one or more communication resources 1330, each of which may be communicatively coupled via a bus 1340 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 1302 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1300.

The processors 1310 may include, for example, a processor 1312 and a processor 1314. The processors 1310 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory/storage devices 1320 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1320 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc. The communication resources 1330 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 1304 or one or more databases 1306 or other network elements via a network 1308. For example, the communication resources 1330 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 1350 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1310 to perform any one or more of the methodologies discussed herein. The instructions 1350 may reside, completely or partially, within at least one of the processors 1310 (e.g., within the processor’s cache memory), the memory/storage devices 1320, or any suitable combination thereof. Furthermore, any portion of the instructions 1350 may be transferred to the hardware resources 1300 from any combination of the peripheral devices 1304 or the databases 1306. Accordingly, the memory of processors 1310, the memory/storage devices 1320, the peripheral devices 1304, and the databases 1306 are examples of computer-readable and machine-readable media.

Figure 14 illustrates a network 1400 in accordance with various embodiments. In some embodiments, the network 1400 may be similar to, or be considered an alternative embodiment to, the networks depicted in one or both of Figures 1 and 2. The network 1400 may include elements similar to those described or discussed above with respect to one or both of Figures 1 and 2. To the extent that the descriptions herein may include additional or alternative descriptions of various elements than are described elsewhere herein, such descriptions may be considered to be alternative embodiments.

The network 1400 may operate in a matter consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, the network 1400 may operate concurrently with network 1100. For example, in some embodiments, the network 1400 may share one or more frequency or bandwidth resources with network 1100. As one specific example, a UE (e.g., UE 1402) may be configured to operate in both network 1400 and network 1100. Such configuration may be based on a UE including circuitry configured for communication with frequency and bandwidth resources of both networks 1100 and 1400. In general, several elements of network 1400 may share one or more characteristics with elements of network 1100. For the sake of brevity and clarity, such elements may not be repeated in the description of network 1400.

The network 1400 may include a UE 1402, which may include any mobile or non-mobile computing device designed to communicate with a RAN 1408 via an over-the-air connection. The UE 1402 may be similar to, for example, UE 1102. The UE 1402 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in- vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

Although not specifically shown in Figure 14, in some embodiments the network 1400 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc. Similarly, although not specifically shown in Figure 14, the UE 1402 may be communicatively coupled with an AP such as AP 1106 as described with respect to Figure 11. Additionally, although not specifically shown in Figure 14, in some embodiments the RAN 1408 may include one or more ANss such as AN 1108 as described with respect to Figure 11. The RAN 1408 and/or the AN of the RAN 1408 may be referred to as a base station (BS), a RAN node, or using some other term or name.

The UE 1402 and the RAN 1408 may be configured to communicate via an air interface that may be referred to as a sixth generation (6G) air interface. The 6G air interface may include one or more features such as communication in a terahertz (THz) or sub-THz bandwidth, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that allows for wireless communication as well as radar-based sensing via various types of multiplexing. As used herein, THz or sub-THz bandwidths may refer to communication in the 80 GHz and above frequency ranges. Such frequency ranges may additionally or alternatively be referred to as “millimeter wave” or “mmWave” frequency ranges.

The RAN 1408 may allow for communication between the UE 1402 and a 6G core network (CN) 1410. Specifically, the RAN 1408 may facilitate the transmission and reception of data between the UE 1402 and the 6G CN 1410. The 6G CN 1410 may include various functions such as NSSF 1150, NEF 1152, NRF 1154, PCF 1156, UDM 1158, AF 1160, SMF 1146, and AUSF 1142. The 6G CN 1410 may additional include UPF 1148 and DN 1136 as shown in Figure 14.

Additionally, the RAN 1408 may include various additional functions that are in addition to, or alternative to, functions of a legacy cellular network such as a 4G or 5G network. Two such functions may include a Compute Control Function (Comp CF) 1424 and a Compute Service Function (Comp SF) 1436. The Comp CF 1424 and the Comp SF 1436 may be parts or functions of the Computing Service Plane. Comp CF 1424 may be a control plane function that provides functionalities such as management of the Comp SF 1436, computing task context generation and management (e.g., create, read, modify, delete), interaction with the underlaying computing infrastructure for computing resource management, etc.. Comp SF 1436 may be a user plane function that serves as the gateway to interface computing service users (such as UE 1402) and computing nodes behind a Comp SF instance. Some functionalities of the Comp SF 1436 may include: parse computing service data received from users to compute tasks executable by computing nodes; hold service mesh ingress gateway or service API gateway; service and charging policies enforcement; performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 1436 instance may serve as the user plane gateway for a cluster of computing nodes. A Comp CF 1424 instance may control one or more Comp SF 1436 instances.

Two other such functions may include a Communication Control Function (Comm CF) 1428 and a Communication Service Function (Comm SF) 1438, which may be parts of the Communication Service Plane. The Comm CF 1428 may be the control plane function for managing the Comm SF 1438, communication sessions creation/configuration/releasing, and managing communication session context. The Comm SF 1438 may be a user plane function for data transport. Comm CF 1428 and Comm SF 1438 may be considered as upgrades of SMF 1146 and UPF 1148, which were described with respect to a 5G system in Figure 11. The upgrades provided by the Comm CF 1428 and the Comm SF 1438 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, SMF 1146 and UPF 1148 may still be used. Two other such functions may include a Data Control Function (Data CF) 1422 and Data Service Function (Data SF) 1432 may be parts of the Data Service Plane. Data CF 1422 may be a control plane function and provides functionalities such as Data SF 1432 management, Data service creation/configuration/releasing, Data service context management, etc. Data SF 1432 may be a user plane function and serve as the gateway between data service users (such as UE 1402 and the various functions of the 6G CN 1410) and data service endpoints behind the gateway. Specific functionalities may include include: parse data service user data and forward to corresponding data service endpoints, generate charging data, report data service status.

Another such function may be the Service Orchestration and Chaining Function (SOCF) 1420, which may discover, orchestrate and chain up communi cation/computing/data services provided by functions in the network. Upon receiving service requests from users, SOCF 1420 may interact with one or more of Comp CF 1424, Comm CF 1428, and Data CF 1422 to identify Comp SF 1436, Comm SF 1438, and Data SF 1432 instances, configure service resources, and generate the service chain, which could contain multiple Comp SF 1436, Comm SF 1438, and Data SF 1432 instances and their associated computing endpoints. Workload processing and data movement may then be conducted within the generated service chain. The SOCF 1420 may also responsible for maintaining, updating, and releasing a created service chain. Another such function may be the service registration function (SRF) 1414, which may act as a registry for system services provided in the user plane such as services provided by service endpoints behind Comp SF 1436 and Data SF 1432 gateways and services provided by the UE 1402. The SRF 1414 may be considered a counterpart of NRF 1154, which may act as the registry for network functions.

Other such functions may include an evolved service communication proxy (eSCP) and service infrastructure control function (SICF) 1426, which may provide service communication infrastructure for control plane services and user plane services. The eSCP may be related to the service communication proxy (SCP) of 5G with user plane service communication proxy capabilities being added. The eSCP is therefore expressed in two parts: eCSP-C 1412 and eSCP- U 1434, for control plane service communication proxy and user plane service communication proxy, respectively. The SICF 1426 may control and configure eCSP instances in terms of service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

Another such function is the AMF 1444. The AMF 1444 may be similar to 1144, but with additional functionality. Specifically, the AMF 1444 may include potential functional repartition, such as move the message forwarding functionality from the AMF 1444 to the RAN 1408.

Another such function is the service orchestration exposure function (SOEF) 1418. The SOEF may be configured to expose service orchestration and chaining services to external users such as applications.

The UE 1402 may include an additional function that is referred to as a computing client service function (comp CSF) 1404. The comp CSF 1404 may have both the control plane functionalities and user plane functionalities, and may interact with corresponding network side functions such as SOCF 1420, Comp CF 1424, Comp SF 1436, Data CF 1422, and/or Data SF 1432 for service discovery, request/response, compute task workload exchange, etc. The Comp CSF 1404 may also work with network side functions to decide on whether a computing task should be run on the UE 1402, the RAN 1408, and/or an element of the 6G CN 1410.

The UE 1402 and/or the Comp CSF 1404 may include a service mesh proxy 1406. The service mesh proxy 1406 may act as a proxy for service-to-service communication in the user plane. Capabilities of the service mesh proxy 1406 may include one or more of addressing, security, load balancing, etc.

EXAMPLE PROCEDURES

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 11-13, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 10, and may be implemented by an apparatus of a core network (CN) of a third generation partnership project (3 GPP) cellular network such as a sixth generation (6G) network. The process may include, at 1001, implementing a SICF. The process may further include, at 1002, interacting, via the SICF, with one or both of an eSCP-C and an eSCP-U. In some embodiments, the interaction may relate to configuration of one or both of the eSCP-C and the eSCP-U by a CN function of the cellular network.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

EXAMPLES

Example 1 may include a control plane function SICF o SICF provides the SBI for other functions to configure the eSCP-Cs or eSCP-Us for the following

■ The traffic rules on routing, access rules, load balancing, etc.

■ Information about service discovery

■ Information about the required statistics for monitoring

■ Information about security o SICF provides a repository of the microservices in the cellular infrastructure which may include one or more logic service meshes. SICF also provides the SBI for NF to query about the information in the repository for an NF or service instance with defined criteria

■ NF can subscribe to the status change or information of the NF in CP or microservices in UP, and get notifications about the information. o SICF provides centralized monitoring for the eSCP-Cs and eSCP-Us. Or SICF facilitate a distributed monitoring between eSCP-Cs and eSCP-Us.

Example 2 may include Evolved Service Communication Proxy for Control plane (eSCP-C) o eSCP-C is the service mesh proxy for control plane functions, which can be configured, queried, and monitored by SICF for CP traffic rules, statistics

Example 3 may include Evolved Service Communication Proxy for User plane (eSCP-U) o eSCP-U is the service mesh proxy for user plane functions and other microservices such as application instances, which can be configured, queried, and monitored by SICF for UP traffic rules, statistics

Example 4 may include UE connects to the cellular network via SBI named Nue Example 5 may include Procedure between NF and SICF in 5.1.1 o NF can send a configuration request to SICF which include the identifiers to identify the eSCPs such as DNN, S-NSSAI, function name, UE identifier, or URL, IP address: port number.

■ The request can also include the rules such as access rule, load balancing, security credential, etc. o NF can send a subscription request to the information of the eSCPs, further the function instances that eSCP associated with, and then get notified for any status change and information update. o NF can query SICF for the status of the eSCPs and discovery the eSCPs with certain criteria

Example 6 may include SICF management procedure for eSCPs in 5.1.2 o SICF can leverage NRF to maintain the repository of the eSCPs o SICF can maintain the repository of the eSCPs by registration procedure between eSCP and SICF

Example 7 may include SICF configuration procedure for eSCP-C and eSCP-U in 5.1.3 o SICF can sends request to eSCPs to configure the access rules, load balancing, and security credentials, etc.

Example 8 may include eSCP monitoring procedures in 5.1.4 o A centralized method: SICF can send request to eSCP to monitor traffic with certain criteria and get the statistics and traces collected at the eSCP. o A distributed method: eSCP can subscribe to and query the information of another eSCP with optional authorization from SICF.

Example 9 includes an apparatus for use in a core network (CN) of a third generation partnership project (3 GPP) cellular network, wherein the apparatus comprises: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors are to cause the apparatus to implement a service infrastructure control function (SICF) that is to interact with one or both of an evolved service communication proxy for control plane (eSCP-C) and an evolved service communication proxy for user plane (eSCP-U).

Example 10 includes the apparatus of example 9, and/or some other example herein, wherein the cellular network is a sixth generation (6G) cellular network.

Example 11 includes the apparatus of any of examples 9-10, and/or some other example herein, wherein the SICF is to provide a service-based interface (SB I) to one or more other CN functions related to configuration of the eSCP-C and/or the eSCP-U.

Example 12 includes the apparatus of example 11, and/or some other example herein, wherein configuration of the eSCP-C and/or the eSCP-U relates to traffic rules, service discovery, monitoring, and/or security.

Example 13 includes the apparatus of any of examples 9-12, and/or some other example herein, wherein the SICF is to provide a repository of microservices in the cellular infrastructure.

Example 14 includes the apparatus of any of examples 9-13, and/or some other example herein, wherein the SICF is to provide a service-based interface (SB I) related to a network function (NF) of the CN.

Example 15 includes the apparatus of any of examples 9-14, and/or some other example herein, wherein the SICF is to facilitate monitoring of one or both of the eSCP-C and the eSCP- U.

Example 16 includes the apparatus of any of examples 9-15, and/or some other example herein, wherein the eSCP-C is a service mesh proxy for control plane functions.

Example 17 includes the apparatus of any of examples 9-16, and/or some other example herein, wherein the eSCP-U is a service mesh proxy for user plane functions.

Example 18 includes an apparatus to implement one or more of the eSCP-C and eSCP-U as described in any of examples 1-17 or 19-38 herein.

Example 19 includes a method to be performed by an apparatus for use in a core network (CN) of a third generation partnership project (3 GPP) cellular network, wherein the method comprises: implementing a service infrastructure control function (SICF); and interacting, via the SICF, with an evolved service communication proxy for control plane (eSCP-C) or an evolved service communication proxy for user plane (eSCP-U).

Example 20 includes the method of example 19, and/or some other example herein, wherein the cellular network is a sixth generation (6G) cellular network.

Example 21 includes the method of any of examples 19-20, and/or some other example herein, wherein the instructions to interact with the eSCP-C or the eSCP-U via the SICF include instructions to provide, via the SICF, a service-based interface (SBI) to a core network (CN) function related to configuration of the eSCP-C or the eSCP-U by the CN function.

Example 22 includes the method of example 21, and/or some other example herein, wherein configuration of the eSCP-C or the eSCP-U relates to configuration, by the CN function, of traffic rules, service discovery, statics, or security of the eSCP-U or the eSCP-C.

Example 23 includes the method of example 21, and/or some other example herein, wherein the instructions are further to provide the SBI to the CN function based on a configuration request received from the CN function.

Example 24 includes the method of example 21, and/or some other example herein, wherein the configuration request includes an indication of an identifier of the eSCP-C or the eSCP-U, and wherein the identifier is a data network name (DNN), a single network slice selection assistance information (S-NSSAI), a function name, or a user equipment (UE) identifier.

Example 25 includes the method of any of examples 19-24, and/or some other example herein, wherein the eSCP-C is a service mesh proxy for control plane functions.

Example 26 includes the method of any of examples 19-25, and/or some other example herein, wherein the eSCP-U is a service mesh proxy for user plane functions.

Example 27 includes one or more non-transitory computer readable media (NTCRM) comprising instructions that, upon execution of the instructions, are to cause an electronic device to: implement a service infrastructure control function (SICF); identify a configuration request received from a core network (CN) function of a cellular network, wherein the configuration request relates to an evolved service communication proxy for control plane (eSCP-C) or an evolved service communication proxy for user plane (eSCP-U); and provide an interface for the CN function to configure the eSCP-C or the eSCP-U.

Example 28 includes the one or more NTCRM of example 27, and/or some other example herein, wherein the cellular network is a sixth generation (6G) cellular network.

Example 29 includes the one or more NTCRM of any of examples 27-28, and/or some other example herein, wherein the interface is a service-based interface (SBI).

Example 30 includes the one or more NTCRM of example 29, and/or some other example herein, wherein the SBI is a Nescpu interface.

Example 31 includes the one or more NTCRM of any of examples 27-30, and/or some other example herein, wherein configuration of the eSCP-C or the eSCP-U relates to configuration, by the CN function, of traffic rules, service discovery, statics, or security of the eSCP-U or the eSCP-C. Example 32 includes the one or more NTCRM of any of examples 27-31, and/or some other example herein, wherein the configuration request includes an indication of an identifier of the eSCP-C or the eSCP-U, and wherein the identifier is a data network name (DNN), a single network slice selection assistance information (S-NSSAI), a function name, or a user equipment (UE) identifier.

Example 33 includes the one or more NTCRM of any of examples 27-32, and/or some other example herein, wherein the eSCP-C is a service mesh proxy for control plane functions.

Example 34 includes the one or more NTCRM of any of examples 27-33, and/or some other example herein, wherein the eSCP-U is a service mesh proxy for user plane functions.

Example 35 includes an apparatus to implement a service infrastructure control function (SICF), wherein the apparatus comprises: one or more processors; and one or more non- transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors, are to cause the SICF to: identify a configuration request received from a core network (CN) function of a cellular network, wherein the configuration request relates to an evolved service communication proxy for control plane (eSCP-C) or an evolved service communication proxy for user plane (eSCP-U); and provide a Nescpu interface for the CN function to configure the eSCP-C or the eSCP-U.

Example 36 includes the apparatus of example 35, and/or some other example herein, wherein configuration of the eSCP-C or the eSCP-U relates to configuration, by the CN function, of traffic rules, service discovery, statics, or security of the eSCP-U or the eSCP-C.

Example 37 includes the apparatus of any of examples 35-36, and/or some other example herein, wherein the configuration request includes an indication of an identifier of the eSCP-C or the eSCP-U, and wherein the identifier is a data network name (DNN), a single network slice selection assistance information (S-NSSAI), a function name, or a user equipment (UE) identifier.

Example 38 includes the apparatus of any of examples 35-37, and/or some other example herein, wherein the eSCP-C is a service mesh proxy for control plane functions and the eSCP-U is a service mesh proxy for user plane functions.

Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-38, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-38, or any other method or process described herein. Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1-38, or any other method or process described herein.

Example Z04 may include a method, technique, or process as described in or related to any of examples 1-38, or portions or parts thereof.

Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-38, or portions thereof.

Example Z06 may include a signal as described in or related to any of examples 1-38, or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-38, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in or related to any of examples 1-38, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1-38, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-38, or portions thereof.

Example Z11 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1-38, or portions thereof.

Example Z12 may include a signal in a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communication as shown and described herein.

Example Z15 may include a device for providing wireless communication as shown and described herein. Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Abbreviations

Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 vl6.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.

3 GPP Third Generation 35 AP Application BRAS Broadband

Partnership Protocol, Antenna Remote Access Project Port, Access Point 70 Server

4G Fourth API Application BSS Business Generation Programming Interface Support System

5G Fifth Generation 40 APN Access Point BS Base Station

5GC 5G Core Name BSR Buffer Status network ARP Allocation and 75 Report AC Retention Priority BW Bandwidth

Application ARQ Automatic BWP Bandwidth Part Client 45 Repeat Request C-RNTI Cell

ACR Application AS Access Stratum Radio Network Context Relocation ASP 80 Temporary ACK Application Service Identity

Acknowledgeme Provider CA Carrier nt 50 Aggregation, ACID ASN.l Abstract Syntax Certification

Application Notation One 85 Authority Client Identification AUSF Authentication CAPEX CAPital AF Application Server Function Expenditure Function 55 AWGN Additive CBRA Contention

AM Acknowledged White Gaussian Based Random Mode Noise 90 Access

AMBRAggregate BAP Backhaul CC Component Maximum Bit Rate Adaptation Protocol Carrier, Country AMF Access and 60 BCH Broadcast Code, Cryptographic

Mobility Channel Checksum

Management BER Bit Error Ratio 95 CCA Clear Channel Function BFD Beam Assessment

AN Access Network Failure Detection CCE Control Channel

ANR Automatic 65 BLER Block Error Rate Element

Neighbour Relation BPSK Binary Phase CCCH Common AO A Angle of Shift Keying 100 Control Channel

Arrival CE Coverage

Enhancement CDM Content Delivery CoMP Coordinated Resource Network Multi-Point Indicator

CDMA Code- CORESET Control C-RNTI Cell Division Multiple Resource Set RNTI

Access 40 COTS Commercial Off- 75 CS Circuit Switched

CDR Charging Data The-Shelf CSCF call Request CP Control Plane, session control function

CDR Charging Data Cyclic Prefix, CSAR Cloud Service Response Connection Archive

CFRA Contention Free 45 Point 80 CSI Channel-State Random Access CPD Connection Information CG Cell Group Point Descriptor CSI-IM CSI CGF Charging CPE Customer Interference

Gateway Function Premise Measurement CHF Charging 50 Equipment 85 CSI-RS CSI

Function CPICHCommon Pilot Reference Signal

CI Cell Identity Channel CSI-RSRP CSI CID Cell-ID (e g., CQI Channel Quality reference signal positioning method) Indicator received power CIM Common 55 CPU CSI processing 90 CSI-RSRQ CSI Information Model unit, Central reference signal CIR Carrier to Processing Unit received quality Interference Ratio C/R CSI-SINR CSI CK Cipher Key Command/Resp signal-to-noise and CM Connection 60 onse field bit 95 interference ratio Management, CRAN Cloud Radio CSMA Carrier Sense

Conditional Access Network, Multiple Access Mandatory Cloud RAN CSMA/CA CSMA CMAS Commercial CRB Common with collision Mobile Alert Service 65 Resource Block 100 avoidance CMD Command CRC Cyclic CSS Common Search CMS Cloud Redundancy Check Space, Cell- specific Management System CRI Channel -State Search Space CO Conditional Information Resource CTF Charging Optional 70 Indicator, CSI-RS 105 Trigger Function CTS Clear-to-Send DSL Domain Specific 70 ECSP Edge CW Codeword Language. Digital Computing Service CWS Contention Subscriber Line Provider Window Size DSLAM DSL EDN Edge

D2D Device-to- 40 Access Multiplexer Data Network

Device DwPTS 75 EEC Edge

DC Dual Downlink Pilot Enabler Client

Connectivity, Direct Time Slot EECID Edge Current E-LAN Ethernet Enabler Client

DCI Downlink 45 Local Area Network Identification

Control E2E End-to-End 80 EES Edge

Information EAS Edge Enabler Server

DF Deployment Application Server EESID Edge Flavour ECCA extended clear Enabler Server

DL Downlink 50 channel Identification

DMTF Distributed assessment, 85 EHE Edge

Management Task extended CCA Hosting Environment Force ECCE Enhanced EGMF Exposure

DPDK Data Plane Control Channel Governance

Development Kit 55 Element, Management

DM-RS, DMRS Enhanced CCE 90 Function

Demodulation ED Energy EGPRS

Reference Signal Detection Enhanced GPRS DN Data network EDGE Enhanced EIR Equipment DNN Data Network 60 Datarates for GSM Identity Register Name Evolution (GSM 95 eLAA enhanced

DNAI Data Network Evolution) Licensed Assisted Access Identifier EAS Edge Access,

Application Server enhanced LAA

DRB Data Radio 65 EASID Edge EM Element

Bearer Application Server 100 Manager

DRS Discovery Identification eMBB Enhanced

Reference Signal ECS Edge Mobile

DRX Discontinuous Configuration Server Broadband Reception EMS Element E-UTRAN Evolved FDM Frequency

Management System UTRAN Division eNB evolved NodeB, EV2X Enhanced V2X Multiplex E-UTRAN Node B F1AP Fl Application FDM A F requency EN-DC E- 40 Protocol 75 Division Multiple UTRA-NR Dual F 1 -C F 1 C ontrol pl ane Access

Connectivity interface FE Front End EPC Evolved Packet Fl-U Fl User plane FEC Forward Error Core interface Correction

EPDCCH enhanced 45 FACCH Fast 80 FFS For Further

PDCCH, enhanced Associated Control Study

Physical CHannel FFT Fast Fourier

Downlink Control FACCH/F Fast Transformation Cannel Associated Control feL AA further enhanced

EPRE Energy per 50 Channel/Full 85 Licensed Assisted resource element rate Access, further EPS Evolved Packet FACCH/H Fast enhanced LAA System Associated Control FN Frame Number

EREG enhanced REG, Channel/Half FPGA Field- enhanced resource 55 rate 90 Programmable Gate element groups FACH Forward Access Array ETSI European Channel FR Frequency

Tel ecommuni cat FAUSCH Fast Range ions Standards Uplink Signalling FQDN Fully Qualified Institute 60 Channel 95 Domain Name

ETWS Earthquake and FB Functional Block G-RNTI GERAN T sunami W arning FBI Feedback Radio Network System Information Temporary eUICC embedded FCC Federal Identity UICC, embedded 65 Communications 100 GERAN

Universal Commission GSM EDGE

Integrated Circuit FCCH Frequency RAN, GSM EDGE Card Correction CHannel Radio Access

E-UTRA Evolved FDD Frequency Network UTRA 70 Division Duplex GGSN Gateway GPRS 35 GTP GPRS Tunneling 70 HSS Home Support Node Protocol Subscriber Server GLONASS GTP-UGPRS HSUPA High

GLObal'naya Tunnelling Protocol Speed Uplink Packet

NAvigatsionnay for User Plane Access a Sputnikovaya 40 GTS Go To Sleep 75 HTTP Hyper Text Si sterna (Engl.: Signal (related to Transfer Protocol Global Navigation WUS) HTTPS Hyper

Satellite System) GUMMEI Globally Text Transfer Protocol gNB Next Generation Unique MME Identifier Secure (https is NodeB 45 GUTI Globally Unique 80 http/ 1.1 over gNB-CU gNB- Temporary UE SSL, i.e. port 443) centralized unit, Next Identity LBlock

Generation HARQ Hybrid ARQ, Information

NodeB Hybrid Block centralized unit 50 Automatic 85 ICCID Integrated gNB-DU gNB- Repeat Request Circuit Card distributed unit, Next HANDO Handover Identification

Generation HFN HyperFrame IAB Integrated

NodeB Number Access and Backhaul distributed unit 55 HHO Hard Handover 90 ICIC Inter-Cell GNSS Global HLR Home Location Interference Navigation Satellite Register Coordination

System HN Home Network ID Identity,

GPRS General Packet HO Handover identifier Radio Service 60 HPLMN Home 95 IDFT Inverse Discrete

GPSI Generic Public Land Mobile Fourier

Public Subscription Network Transform

Identifier HSDPA High IE Information

GSM Global System Speed Downlink element for Mobile 65 Packet Access 100 IBE In-Band

Communications HSN Hopping Emission , Groupe Special Sequence Number IEEE Institute of Mobile HSPA High Speed Electrical and

Packet Access Electronics 35 loT Internet of 70 code, USIM

Engineers Things Individual key

IEI Information IP Internet Protocol kB Kilobyte (1000

Element Identifier Ipsec IP Security, bytes)

IEIDL Information Internet Protocol kbps kilo-bits per

Element Identifier 40 Security 75 second

Data Length IP-CAN IP- Kc Ciphering key

IETF Internet Connectivity Access Ki Individual

Engineering Task Network subscriber

Force IP-M IP Multicast authentication

IF Infrastructure 45 IPv4 Internet Protocol 80 key

IIOT Industrial Version 4 KPI Key

Internet of Things IPv6 Internet Protocol Performance Indicator

IM Interference Version 6 KQI Key Quality

Measurement, IR Infrared Indicator

Intermodulation, 50 IS In Sync 85 KSI Key Set

IP Multimedia IRP Integration Identifier

IMC IMS Credentials Reference Point ksps kilo-symbols per

IMEI International ISDN Integrated second

Mobile Services Digital KVM Kernel Virtual

Equipment 55 Network 90 Machine

Identity ISIM IM Services LI Layer 1

IMGI International Identity Module (physical layer) mobile group identity ISO International Ll-RSRP Layer 1 IMPI IP Multimedia Organisation for reference signal

Private Identity 60 Standardisation 95 received power

IMPU IP Multimedia ISP Internet Service L2 Layer 2 (data

PUblic identity Provider link layer)

IMS IP Multimedia IWF Interworking- L3 Layer 3

Subsystem Function (network layer)

IMSI International 65 LWLAN 100 LAA Licensed

Mobile Interworking Assisted Access

Subscriber WLAN LAN Local Area

Identity Constraint length Network of the convolutional LADN Local M2M Machine-to- 70 MCG Master Cell

Area Data Network Machine Group

LBT Listen Before MAC Medium Access MCOT Maximum

Talk Control (protocol Channel

LCM LifeCycle 40 layering context) Occupancy Time

Management MAC Message 75 MCS Modulation and

LCR Low Chip Rate authentication code coding scheme

LCS Location (security/ encry pti on MD AF Management

Services context) Data Analytics

LCID Logical 45 MAC-A MAC Function

Channel ID used for 80 MD AS Management

LI Layer Indicator authentication Data Analytics

LLC Logical Link and key Service

Control, Low Layer agreement (TSG MDT Minimization of

Compatibility 50 T WG3 context) Drive Tests

LMF Location MAC-IMAC used for 85 ME Mobile

Management Function data integrity of Equipment

LOS Line of signalling messages MeNB master eNB

Sight (TSG T WG3 context) MER Message Error

LPLMN Local 55 MANO Ratio

PLMN Management and 90 MGL Measurement

LPP LTE Positioning Orchestration Gap Length

Protocol MBMS MGRP Measurement

LSB Least Significant Multimedia Gap Repetition

Bit 60 Broadcast and Multicast Period

LTE Long Term Service 95 MIB Master

Evolution MBSFN Information Block,

LWA LTE-WLAN Multimedia Management aggregation Broadcast multicast Information Base

LWIP LTE/WLAN 65 service Single MIMO Multiple Input

Radio Level Frequency 100 Multiple Output

Integration with Network MLC Mobile Location

IPsec Tunnel MCC Mobile Country Centre

LTE Long Term Code MM Mobility

Evolution Management MME Mobility MSID Mobile Station NE-DC NR-E- Management Entity Identifier UTRA Dual MN Master Node MSIN Mobile Station Connectivity

MNO Mobile Identification NEF Network

Network Operator 40 Number 75 Exposure Function MO Measurement MSISDN Mobile NF Network

Object, Mobile Subscriber ISDN Function

Originated Number NFP Network

MPBCH MTC MT Mobile Forwarding Path

Physical Broadcast 45 Terminated, Mobile 80 NFPD Network

CHannel Termination Forwarding Path

MPDCCH MTC MTC Machine-Type Descriptor Physical Downlink Communications NFV Network

Control CHannel mMTCmassive MTC, Functions

MPDSCH MTC 50 massive Machine- 85 Virtualization Physical Downlink Type Communications NFVI NFV

Shared CHannel MU-MIMO Multi Infrastructure

MPRACH MTC User MIMO NF VO NFV Physical Random MWUS MTC Orchestrator

Access CHannel 55 wake-up signal, MTC 90 NG Next Generation,

MPUSCH MTC wus Next Gen

Physical Uplink Shared NACK Negative NGEN-DC NG-RAN Channel Acknowledgement E-UTRA-NR Dual

MPLS MultiProtocol NAI Network Access Connectivity

Label Switching 60 Identifier 95 NM Network

MS Mobile Station NAS Non-Access Manager MSB Most Significant Stratum, Non- Access NMS Network Bit Stratum layer Management System

MSC Mobile NCT Network N-PoP Network Point Switching Centre 65 Connectivity Topology 100 of Presence MSI Minimum NC-JT NonNMIB, N-MIB

System coherent Joint Narrowband MIB

Information, Transmission NPBCH MCH Scheduling NEC Network Narrowband Information 70 Capability Exposure 105 Physical Broadcast NSA Non- Standalone 70 OSI Other System

CHannel operation mode Information

NPDCCH NSD Network Service OSS Operations

Narrowband Descriptor Support System

Physical 40 NSR Network Service OTA over-the-air

Downlink Record 75 PAPR Peak-to- Average

Control CHannel NSSAINetwork Slice Power Ratio

NPDSCH Selection PAR Peak to Average

Narrowband Assistance Ratio

Physical 45 Information PBCH Physical

Downlink S-NNSAI Single- 80 Broadcast Channel

Shared CHannel NSSAI PC Power Control,

NPRACH NSSF Network Slice Personal

Narrowband Selection Function Computer

Physical Random 50 NW Network PCC Primary Access CHannel NWU S N arrowb and 85 Component Carrier,

NPUSCH wake-up signal, Primary CC

Narrowband N arrowb and WU S P-CSCF Proxy

Physical Uplink NZP Non-Zero Power CSCF Shared CHannel 55 O&M Operation and PCell Primary Cell

NPSS Narrowband Maintenance 90 PCI Physical Cell ID,

Primary ODU2 Optical channel Physical Cell

Synchronization Data Unit - type 2 Identity Signal OFDM Orthogonal PCEF Policy and

NSSS Narrowband 60 Frequency Division Charging

Secondary Multiplexing 95 Enforcement

Synchronization OFDMA Function Signal Orthogonal PCF Policy Control

NR New Radio, Frequency Division Function Neighbour Relation 65 Multiple Access PCRF Policy Control NRF NF Repository OOB Out-of-band 100 and Charging Rules Function OO S Out of Sync Function

NRS Narrowband OPEX OPerating PDCP Packet Data Reference Signal EXpense Convergence Protocol, NS Network Service Packet Data Convergence PNFD Physical 70 PSCCH Physical Protocol layer Network Function Sidelink Control PDCCH Physical Descriptor Channel Downlink Control PNFR Physical PSSCH Physical Channel 40 Network Function Sidelink Shared

PDCP Packet Data Record 75 Channel Convergence Protocol POC PTT over PSCell Primary SCell PDN Packet Data Cellular PSS Primary Network, Public PP, PTP Point-to- Synchronization

Data Network 45 Point Signal

PDSCH Physical PPP Point-to-Point 80 PSTN Public Switched

Downlink Shared Protocol Telephone Network

Channel PRACH Physical PT-RS Phase-tracking

PDU Protocol Data RACH reference signal Unit 50 PRB Physical PTT Push-to-Talk

PEI Permanent resource block 85 PUCCH Physical Equipment PRG Physical Uplink Control

Identifiers resource block Channel

PFD Packet Flow group PUS CH Physical Description 55 ProSe Proximity Uplink Shared

P-GW PDN Gateway Services, 90 Channel PHICH Physical Proximity -Based QAM Quadrature hybrid-ARQ indicator Service Amplitude channel PRS Positioning Modulation

PHY Physical layer 60 Reference Signal QCI QoS class of PLMN Public Land PRR Packet 95 identifier Mobile Network Reception Radio QCL Quasi co¬

PIN Personal PS Packet Services location

Identification Number PSBCH Physical QFI QoS Flow ID,

PM Performance 65 Sidelink Broadcast QoS Flow Identifier Measurement Channel 100 QoS Quality of

PMI Precoding PSDCH Physical Service Matrix Indicator Sidelink Downlink QPSK Quadrature

PNF Physical Channel (Quaternary) Phase Network Function Shift Keying QZSS Quasi -Zenith RL Radio Link 70 RRC Radio Resource

Satellite System RLC Radio Link Control, Radio

RA-RNTI Random Control, Radio Resource Control

Access RNTI Link Control layer

RAB Radio Access 40 layer RRM Radio Resource

Bearer, Random RLC AM RLC 75 Management

Access Burst Acknowledged Mode RS Reference Signal

RACH Random Access RLC UM RLC RSRP Reference Signal

Channel Unacknowledged Mode Received Power

RADIUS Remote 45 RLF Radio Link RSRQ Reference Signal

Authentication Dial In Failure 80 Received Quality

User Service RLM Radio Link RS SI Received Signal

RAN Radio Access Monitoring Strength Indicator

Network RLM-RS RSU Road Side Unit

RAND RANDom 50 Reference Signal RSTD Reference Signal number (used for for RLM 85 Time difference authentication) RM Registration RTP Real Time

RAR Random Access Management Protocol

Response RMC Reference RTS Ready-To-Send

RAT Radio Access 55 Measurement Channel RTT Round Trip

Technology RMSI Remaining MSI, 90 Time

RAU Routing Area Remaining Rx Reception,

Update Minimum Receiving, Receiver

RB Resource block, System S1AP SI Application

Radio Bearer 60 Information Protocol

RBG Resource block RN Relay Node 95 Sl-MME SI for group RNC Radio Network the control plane

REG Resource Controller Sl-U SI for the user

Element Group RNL Radio Network plane

Rel Release 65 Layer S-CSCF serving

REQ REQuest RNTI Radio Network 100 CSCF

RF Radio Frequency Temporary Identifier S-GW Serving Gateway

RI Rank Indicator ROHC RObust Header S-RNTI SRNC

RIV Resource Compression Radio Network indicator value Temporary SCTP Stream Control SgNB Secondary gNB

Identity 35 Transmission 70 SGSN Serving GPRS

S-TMSI SAE Protocol Support Node

Temporary Mobile SDAP Service Data S-GW Serving Gateway

Station Identifier Adaptation Protocol, SI System

SA Standalone Service Data Information operation mode 40 Adaptation 75 SI-RNTI System

SAE System Protocol layer Information RNTI

Architecture SDL Supplementary SIB System

Evolution Downlink Information Block

SAP Service Access SDNF Structured Data SIM Subscriber

Point 45 Storage Network 80 Identity Module

SAPD Service Access Function SIP Session Initiated

Point Descriptor SDP Session Protocol

SAPI Service Access Description Protocol SiP System in

Point Identifier SDSF Structured Data Package

SCC Secondary 50 Storage Function 85 SL Sidelink

Component Carrier, SDT Small Data SLA Service Level

Secondary CC Transmission Agreement

SCell Secondary Cell SDU Service Data SM Session

SCEF Service Unit Management

Capability Exposure 55 SEAF Security Anchor 90 SMF Session

Function Function Management Function

SC-FDMA Single SeNB secondary eNB SMS Short Message

Carrier Frequency SEPP Security Edge Service

Division Protection Proxy SMSF SMS Function

Multiple Access 60 SFI Slot format 95 SMTC SSB-based

SCG Secondary Cell indication Measurement Timing

Group SFTD Space- Configuration

SCM Security Context Frequency Time SN Secondary Node,

Management Diversity, SFN Sequence Number

SCS Subcarrier 65 and frame timing 100 SoC System on Chip

Spacing difference SON Self-Organizing

SFN System Frame Network Number SpCell Special Cell SP-CSI-RNTISemi- Reference Signal TCI Transmission

Persi stent CSI RNTI Received Quality Configuration Indicator

SPS Semi-Persistent SS-SINR TCP Transmission

Scheduling Synchronization Communication

SQN Sequence 40 Signal based Signal to 75 Protocol number Noise and Interference TDD Time Division

SR Scheduling Ratio Duplex

Request SSS Secondary TDM Time Division

SRB Signalling Radio Synchronization Multiplexing

Bearer 45 Signal 80 TDMATime Division

SRS Sounding SSSG Search Space Set Multiple Access

Reference Signal Group TE Terminal

SS Synchronization SSSIF Search Space Set Equipment

Signal Indicator TEID Tunnel End

SSB Synchronization 50 SST Slice/Service 85 Point Identifier

Signal Block Types TFT Traffic Flow

SSID Service Set SU-MIMO Single Template

Identifier User MIMO TMSI Temporary

SS/PBCH Block SUL Supplementary Mobile

SSBRI SS/PBCH Block 55 Uplink 90 Subscriber

Resource Indicator, TA Timing Identity

Synchronization Advance, Tracking TNL Transport

Signal Block Area Network Layer

Resource Indicator TAC Tracking Area TPC Transmit Power

SSC Session and 60 Code 95 Control

Service TAG Timing Advance TPMI Transmitted

Continuity Group Precoding Matrix

SS-RSRP TAI Tracking Indicator

Synchronization Area Identity TR Technical Report

Signal based 65 TAU Tracking Area 100 TRP, TRxP

Reference Signal Update Transmission

Received Power TB Transport Block Reception Point

SS-RSRQ TBS Transport Block TRS Tracking

Synchronization Size Reference Signal Signal based 70 TBD To Be Defined 105 TRx Transceiver TS Technical 35 UML Unified 70 V2V Vehicle-to-

Specifications, Modelling Language Vehicle

Technical UMTS Universal V2X Vehicle-to-

Standard Mobile everything

TTI Transmission Tel ecommuni cat VIM Virtualized

Time Interval 40 ions System 75 Infrastructure Manager

Tx Transmission, UP User Plane VL Virtual Link,

Transmitting, UPF User Plane VLAN Virtual LAN,

Transmitter Function Virtual Local Area

U-RNTI UTRAN URI Uniform Network

Radio Network 45 Resource Identifier 80 VM Virtual Machine

Temporary URL Uniform VNF Virtualized

Identity Resource Locator Network Function

UART Universal URLLC UltraVNFFG VNF

Asynchronous Reliable and Low Forwarding Graph

Receiver and 50 Latency 85 VNFFGD VNF

Transmitter USB Universal Serial Forwarding Graph

UCI Uplink Control Bus Descriptor Information USIM Universal VNFMVNF Manager

UE User Equipment Subscriber Identity VoIP Voice-over-IP,

UDM Unified Data 55 Module 90 Voice-over- Internet

Management USS UE-specific Protocol

UDP User Datagram search space VPLMN Visited Protocol UTRA UMTS Public Land Mobile

UDSF Unstructured Terrestrial Radio Network

Data Storage Network 60 Access 95 VPN Virtual Private Function UTRAN Universal Network

UICC Universal Terrestrial Radio VRB Virtual Resource

Integrated Circuit Access Network Block

Card UwPTS Uplink WiMAX

UL Uplink 65 Pilot Time Slot 100 Worldwide

UM V2I Vehicle-to- Interoperability

Unacknowledge Infrastruction for Microwave d Mode V2P Vehicle-to- Access

Pedestrian WLANWireless Local

Area Network

WMAN Wireless Metropolitan Area Network

WPANWireless Personal Area Network

X2-C X2-Control plane X2-U X2 -User plane XML extensible Markup

Language XRES EXpected user RESponse

XOR exclusive OR ZC Zadoff-Chu ZP Zero Power

Terminology

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computerexecutable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, VO interfaces, peripheral component interfaces, network interface cards, and/or the like. The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/ systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like.

The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “SMTC” refers to an S SB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration .

The term “SSB” refers to an SS/PBCH block. The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC. The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell.

The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC CONNECTED configured with CA/.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Claims

1. An apparatus for use in a core network (CN) of a third generation partnership project (3GPP) cellular network, wherein the apparatus comprises: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors are to cause the apparatus to: implement a service infrastructure control function (SICF); and interact, via the SICF, with an evolved service communication proxy for control plane (eSCP-C) or an evolved service communication proxy for user plane (eSCP-U).

2. The apparatus of claim 1, wherein the cellular network is a beyond 5G (B5G) or sixth generation (6G) cellular network.

3. The apparatus of claim 1, wherein the instructions to interact with the eSCP-C or the eSCP-U via the SICF include instructions to provide, via the SICF, a service-based interface (SB I) to a core network (CN) function related to configure the eSCP-C or the eSCP-U by the CN function.

4. The apparatus of claim 3, wherein configuration of the eSCP-C or the eSCP-U relates to configuration, by the CN function, of traffic rules, access policies and rules, or security of the eSCP-U or the eSCP-C.

5. The apparatus of claim 3, wherein the instructions are further to provide the SBI to the CN function based on a configuration request received from the CN function.

6. The apparatus of claim 3, wherein the configuration request includes an indication of an identifier of the eSCP-C or the eSCP-U, and wherein the identifier is a data network name (DNN), a single network slice selection assistance information (S-NSSAI), a function name, or a user equipment (UE) identifier.

7. The apparatus of any of claims 1-6, wherein the eSCP-C is a service mesh proxy for control plane functions.

8. The apparatus of any of claims 1-6, wherein the eSCP-U is a service mesh proxy for user plane functions.

9. One or more non-transitory computer readable media (NTCRM) comprising instructions that, upon execution of the instructions, are to cause an electronic device to: implement a service infrastructure control function (SICF); identify a configuration request received from a core network (CN) function of a cellular network, wherein the configuration request relates to an evolved service communication proxy for control plane (eSCP-C) or an evolved service communication proxy for user plane (eSCP- U); and provide an interface for the CN function to configure the eSCP-C or the eSCP-U.

10. The one or more NTCRM of claim 9, wherein the cellular network is a sixth generation (6G) cellular network.

11. The one or more NTCRM of claim 9, wherein the interface is a service-based interface (SBI).

12. The one or more NTCRM of claim 11, wherein the SBI is a Nescpu interface.

13. The one or more NTCRM of any of claims 9-12, wherein configuration of the eSCP- C or the eSCP-U relates to configuration, by the CN function, of traffic rules, service discovery, statics, or security of the eSCP-U or the eSCP-C.

14. The one or more NTCRM of any of claims 9-12, wherein the configuration request includes an indication of an identifier of the eSCP-C or the eSCP-U, and wherein the identifier is a data network name (DNN), a single network slice selection assistance information (S-NSSAI), a function name, or a user equipment (UE) identifier.

15. The one or more NTCRM of any of claims 9-12, wherein the eSCP-C is a service mesh proxy for control plane functions.

16. The one or more NTCRM of any of claims 9-12, wherein the eSCP-U is a service mesh proxy for user plane functions.

17. An apparatus to implement a service infrastructure control function (SICF), wherein the apparatus comprises: one or more processors; and one or more non-transitory computer-readable media comprising instructions that, upon execution of the instructions by the one or more processors, are to cause the SICF to: identify a configuration request received from a core network (CN) function of a cellular network, wherein the configuration request relates to an evolved service communication proxy for control plane (eSCP-C) or an evolved service communication proxy for user plane (eSCP-U); and provide a Nescpu interface for the CN function to configure the eSCP-C or the eSCP-U.

18. The apparatus of claim 17, wherein configuration of the eSCP-C or the eSCP-U relates to configuration, by the CN function, of traffic rules, service discovery, statics, or security of the eSCP-U or the eSCP-C.

19. The apparatus of any of claims 17-18, wherein the configuration request includes an indication of an identifier of the eSCP-C or the eSCP-U, and wherein the identifier is a data network name (DNN), a single network slice selection assistance information (S-NSSAI), a function name, or a user equipment (UE) identifier.

20. The apparatus of any of claims 17-18, instructions are further to cause the SICF to facilitate, via the Nescpu interface, service discovery and subscription communication between the CN function and the eSCP-C or the eSCP-U.