Enabling UAS service for identification and operation in 3GPP system

Some embodiments of this disclosure include systems, apparatuses, methods, and computer-readable media for use in a wireless network for facilitating Unmanned Aerial System (UAS) services over evolved packet systems. Some embodiments are directed to a method, the method including receiving a registration request from each of an unmanned aerial vehicle (UAV) and a UAV controller to establish an Unmanned Aerial System (UAS). Additionally, the method includes initiating a UAS Operation Service Request Procedure via a network exposure function (NEF) and associating the UAV and the UAV controller to operate as the UAS in response to obtaining the results of the UAS operation service authorization from each of the UAV and the UAV controller. Moreover, the method also includes transmitting a UAS operation status update procedure to the UAV and the UAV controller, the update procedure including UAS association information, a UAS policy update, and initiation of a UAS operation.

FIELD

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

SUMMARY

Some embodiments of this disclosure include systems, apparatuses, methods, and computer-readable media for use in a wireless network for configuring the operation of a use equipment (UE).

Some embodiments are directed to a method, the method including receiving a registration request from each of an unmanned aerial vehicle (UAV) and a UAV controller to establish an Unmanned Aerial System (UAS), each registration request including an application layer registration through an Unmanned Aircraft Traffic Management (UM) application function (AF), in which an IP address of the server is provided. Additionally, the method includes initiating a UAS Operation Service Request Procedure via a network exposure function (NEF) to obtain results of a UAS operation service authorization from each of the UAV and the UAV controller. Furthermore, the method also includes associating the UAV and the UAV controller to operate as the UAS in response to obtaining the results of the UAS operation service authorization from each of the UAV and the UAV controller. Moreover, the method also includes transmitting a UAS operation status update procedure to the UAV and the UAV controller, the update procedure including UAS association information, a UAS policy update, and initiation of a UAS operation.

Some embodiments are directed to an unmanned aircraft traffic management server facilitating Unmanned Aerial System (UAS) services over evolved packet systems. In some aspects, the server may include network circuitry and processor circuitry coupled to the network circuitry and configured to receive a registration request from each of an unmanned aerial vehicle (UAV) and a UAV controller to establish an Unmanned Aerial System (UAS), each registration request including an application layer registration through an Unmanned Aircraft Traffic Management (UM) application function (AF), in which an IP address of the server is provided. Additionally, the processor circuitry may further be configured to initiate a UAS Operation Service Request Procedure via a network exposure function (NEF) to obtain results of a UAS operation service authorization from each of the UAV and the UAV controller. Furthermore, the processor circuitry may further be configured to associate the UAV and the UAV controller to operate as the UAS in response to obtaining the results of the UAS operation service authorization from each of the UAV and the UAV controller. Moreover, the processor circuitry may further be configured to transmit a UAS operation status update procedure to the UAV and the UAV controller, the update procedure including UAS association information, a UAS policy update, and initiation of a UAS operation.

DETAILED DESCRIPTION

Based on SA1 service requirements in TS 22.125, 3GPP has started the architecture study on 5GS enhanced support of UAS (Unmanned Aerial System) as indicated in SA2 SID: SP-181114.

According to UAS Traffic Management Concept of Operations by NASA (National Aeronautics and Space Administration) and FAA (Federal Aviation Administration), the Unmanned Aircraft Traffic Management (UTM) architecture can refer to UTM concept of operation available from NASA.

Embodiments disclosed herein may be directed to providing UAS service over the 3GPP Evolved Packet System to address the following issues:

Issue 1: Architectural Aspects: A role of 3GPP system to support UAS operation with National Aeronautics and Space Administration—Federal Aviation Administration (NASA-FAA) defined UTM concept of to enable UTM to associate the UAV and UAV controller, and to identify the combination as a UAS.

Issue 2: How the 3GPP system may support UAS association and identification.

Issue 3: How the 3GPP system may provide UAV and UAV controller the 3GPP connectivity for communication between them and with an Unmanned Aerial System Traffic Management (UTM), including communication requirements for UAS cover both the Command and Control (C2) between UAV and UAV controller, but also uplink and downlink data to/from the UAS components towards both the serving 3GPP network and network servers.

Issue 4: When the application function (AF) session is with multiple traffic types, it requires a mechanism to provide differentiated QoS for different traffics in C2 communication.

Issue 5: According to TS22.125, in decentralized traffic management, the local broadcasting mechanism is used for collision avoidance. However, the legacy message may not be sufficient to identify the nearby UAV and keep distance from collision.

In embodiments described herein, the 3GPP system may enable a UAV to broadcast the following identity data in a short-range area for collision avoidance: UAV type, current location and time, route data, operating status.

Furthermore, embodiments may enhance 5GS/Evolved Packet System (EPS) system architecture in support of UAS operation, and to enable UAS operation service by proposed new procedures and the enhancement to the existing procedures.

The legacy functionalities in 5GS/EPS may not sufficiently support a UAS operation.

Accordingly, embodiments disclosed herein may be directed to at least the following implementations for provision UAS services in 5GS/EPSImplementation 0: High level Procedure for UAS Association, Identification, and OperationImplementation 1: UAS subscriptionsImplementation 2, 3: New UAS association and identification procedureImplementation 4: C2 communication Set up for an AS session with required QoSImplementation 5: Flight Plan based UAS operationImplementation 6: UAS association and identification procedure using EPC-Level ProSe Discovery

As a result of one or more of the embodiments disclosed herein, the UAS services may be authorized and identified by the 3GPP system. Further, the UAS operation may be provisioned with required QoS and would result in increased safety for UAS operation.

Embodiments described within this disclosure may include the following:

The UAV and UAV controller are both with 3GPP UE capabilities including required capabilities for UAS operation.

The UAS operation with both UAV and UAV controller is based onFIG.1, in which the UAV and UAV controller communicate to each other via respective unicast connection to 3GPP network via same or different RAN node in the same or different PLMNs. The UAV controller and UAV establish respective unicast C2 (control and command) communication links to the 3GPP network and communicate with each other via 3GPP network.

The UAS operation without UAV controller bases on network navigated C2 communication and flight plan is as shown inFIG.2. The corresponding implementation is in implementation 5.

Embodiments described herein may include the following:

A new network function, Cellular based UAS traffic management (C-UTM), in the control plane is introduced

According to some embodiments, C-UTM function may be supported in EPC architecture (TS 23.401) and 5GS architecture (TS23.501).

According to some embodiments, the C-UTM function may store the authorization information for the UAV and UAV controller for the UAS operation.

According to some embodiments, for EPS, C-UTM function may interface with SCEF (new interface), and SCEF can expose network capabilities requested by SCS/AS with UTM-Application server (TS23.682) over T8.

For 5GS, the UTM-AF interfaces with C-UTM over N33.

The UTM-Application server via SCS/AS or AF can request services from 3GPP network via PCRF (over Rx interface) or PCF or via SCEF in EPS or NEF in 5GS (TS23.203, TS23.682, TS23.501, TS23.502).

According to some embodiments,FIG.3shows service based system architecture in 5GS based on TS 23.501, as an example, in which C-UTM may be a new network function. Alternatively, the C-UTM functionalities can be supported in PCF using existing interfaces to communicate other Network functions, e.g. SMF, NEF, and AF. Embodiments disclosed herein may be directed to enhanced 5GS architecture and procedure 5GS (TS 23.501, 23.502, 23.503). All embodiments are applicable to 3GPP system in EPS (TS 23.401, 23.402, 23.303), with the corresponding additions to the network entities/functions, e.g. HSS is corresponding to UDM, PCRF is corresponding to PCF, SCEF is corresponding to NEF, etc.

FIG.4shows the High-Level Procedure for UAS Association, Identification and Operation, whereby the actions indicate the corresponding implementations. For simplicity, the Figure shows only one 3GPP network. Embodiments described herein may be applicable to the case that the UAV and UAV controller (UAV-C) register to 3GPP network via same or different RAN/CN node in the same or different PLMNs according to the following actions:

Action 0: the UE in the UAV and UAV controller is pre-configured with the UAS operation authorization parameters.

Action 1: the UE in UAV/UAV controller both register to the 5GC with indications to enable UAS operation service if the UE has corresponding UAS subscriptions.

Action 2: the UE in UAV/UAV controller requests to establish PDU session for a specific UAS-DNN. The SMF can initiate secondary authentication procedure with UAS-DN-AAA if the UE sends the request with NAI (network access identifier).

Action 3A: the UE in UAV performs application layer registration to the UTM-Application server associated to UTM-AF, in which IP address of the UTM-Application server is pre-configured in the UE or provided in a PDU session accept message.

Action 3B: the AF initiates UAS Operation Service Request Procedure towards C-UTM/PCF function via NEF to obtain the results of the UAS Operation Service Authorization per Application identified by Application Identifier.

Action 4A, 4B: same as Action 3A, 3B for the UAV controller.

Action 5: when the UTM-AF obtains results of UAS operation service authorization per application from both UAV and UAV controller, it determines if the UAV and UAV controller can be associated to operate as a UAS.

Action 6: If the UAS association is done successfully, the UTM-AF sends UAS

Operation Status Update procedure to notify the UAS operation status including UAS association information, UAS policies updates, and initiation of the UAS operation. When the AF receives response message to the status update, the UAS operation can be started.

Action 7: The UTM-AF initiates AF Session Setup Procedure with required QoS to steer the IP flows for the UTM session between the UAV and the UTM-AF and C2 (command and control) session between UAV and the UAV controller.

It should be appreciated that the actions described above may be performed in any order, or that one of the more actions may be omitted.

Implementation 1: UAS Subscription

A user's profile in the HSS in EPS or UDM in 5GS may contain the subscription information to give the user permission to use UAS service. At any time, the operator can remove the UAS UE subscription rights from user's profile in the HSS/UDM, and revoke the user's permission to use UAS service. The following subscription information may be defined for UAS:Subscription for UE operating UAV in a UAS.Subscription for UE operating UAV Controller in a UAS.Subscription for UAS Operation using Indirect C2 Communication (as shown inFIG.1).Subscription for UAS Operation using network navigated C2 with flight plan (as shown inFIG.2)Subscription for UAS Operation using Direct C2 Communication (i.e. UAS direct communication between UEs).Subscription for EPC-Level UAS Discovery and Association.

Additional parameters related to the ProSe Direct service may be stored in the user's profile, such as:the list of the PLMNs where the UE is authorised for UAS Operation using Indirect C2 Communication:the list of the PLMNs where the UE is authorised for UAS Operation using Direct C2 Communication.the list of the PLMNs whether the UE is authorized for UAS Operation using network navigated C2 with flight plan.the list of the PLMNs where the UE is authorised for UAS Operation using EPC-Level UAS Association Discovery.

According to some embodiments, for each subscription, the UE can be pre-configured or provisioned by the PCF function with the following service authorization parameters:

Authorization for UAS Operation using Indirect C2 Communication:the list of the PLMNs where the UE is authorizedthe list of the allowed Application Identifiers per PLMNthe list of the allowed traffic types per Application IdentifierUAS-DNN

Authorization for UAS Operation using Direct C2 Communication:the list of the PLMNs where the UE is authorizedthe list of the allowed Application Identifiers per PLMN

Authorization for UAS Operation using network navigated C2 with flight planthe list of the PLMNs where the UE is authorizedthe list of the allowed Application Identifiers per PLMNthe list of the UTM Application Servers per Application Identifierthe list of the allowed traffic types per Application IdentifierUAS-DNN

The list of the allowed traffic types can be associated to different port numbers.

This is used to resolve issue 4 in implementation 4.2.

Authorization for UAS Operation using EPC-Level UAS Association Discoverythe list of the PLMNs where the UE is authorizedthe list of the allowed Application Identifiers per PLMN

The provisioning of the UAS operation authorization parameters can use UE configuration update procedure as clause 4.2.4 in TS23.502, and as illustrated inFIG.5(associated with FIG. 4.2.4.3-1 of TS23.502).

Implementation 2: UAS Association and Identification Procedure

For supporting the UAS association between the UAV and UAV controller, the UTM-Application server initiates C-UTM service request procedure for UAV and UAV controller respectively as follows, as shown inFIG.6:

According to some embodiments, the association procedure may follow the following steps:

1. The AF requests for UAS operation service authorization by sending a Nnef_UAS_Operation_Service Request (AF Identifier, Generic Public Subscription Identifier (GPSI)/External Group Identifier of the UAV/UAV controller, external Application Identifiers, UAS operation authorization for each Application Identifier) message to the NEF. In come embodiments, UAS operation authorization indicates that the UAS operation policy is to be created in the operator's network if successfully authorized, e.g. UAS operation mode, including via Network based C2 (as shown inFIG.1) or via Network navigated C2 (as shown inFIG.2), operation location, requested operation start time, flight duration, flight routes, etc., for the UAV/UAV controller.

2. The NEF authorizes the AF to request UAS operation service authorization together with the AF Identifier.If the authorisation is not granted, Action 2 is skipped and the NEF replies to the AF with a Result value indicating that the authorisation failed.If the authorization is granted, the NEF allocates a Transaction Reference ID to identify the follow up messages regarding to the request.Based on operator configuration, the NEF may skip this action. In this case the authorization is performed by the C-UTM/PCF in action 3.

3. The NEF sends a Ncutm_UAS Operation_Authorization Request message (Application Identifier(s), one or more sets of UAS operation information for each Application Identifier, SUPI) to the C-UTMF/PCF.The NEF may query for the translation of GPSI/External Group Identifier of the UAV/UAV controller to Subscription Permanent Identifier (SUPI) of the UE.

4. The C-UTM/PCF function determines whether the request is allowed.If UAS operation authorization is done successfully, it continues to create the list of UAS operation policies into the C-UTM function based on the operator's configured policies for each requested UAS operation per application ID and respond to NEF.

5. the C-UTM function sends Ncutm_UAS Operation_Authorization Request message (Application Identifier(s), Results) message to the NEF and indicates the Results. If any of the services authorization fails, a cause is provided per Application ID, e.g. service suspend, service expiration, service unavailable, etc.

6. The NEF sends a Unef_UAS Operation_Service Response (Transaction Reference ID, Results) message to the UTM-AF to provide the feedback of the result for Unef_UAS Operation_Service Request.The Transaction Reference ID generated in Action is used by the AF to provide the follow up information regarding to the request for the UAS operation of the UAV/UAV controller.

As another example for EPS, the similar procedure can be applied in the following procedure, as illustrated inFIG.7(Procedure for UAS Operation_Service request by the UTM-SCS/AS via SCEF):

1. The 3rd party SCS/AS sends a C-UTM Service Request (SCS/AS Identifier, TTRI, External Identifiers/External Group Identifier of the UAV/UAV controller, external Application Identifiers, UAS operation authorization for each Application Identifier) message to the SCEF.The external Application Identifier(s) may be provided by an 3rd party SCS/AS that is known at the SCEF, so that the 3rd party SCS/AS and the MNO has an SLA in place.The definition of the external identifier or external group identifier of the UAV/UAV controller can be referred to TS23.682 clause 4.6.2.UAS operation authorization indicates that the UAS operation policy is to be created in the operator's network if successfully authorized, e.g. UAS operation mode, including via Network based C2 (as shown inFIG.1) or via Network navigated C2 (as shown inFIG.2), operation location, requested operation start time, flight duration, flight routes, etc., for the UAV/UAV controller.T8 Transaction Reference ID (TTRI) is a parameter which refers to transactions between the SCEF and the SCS/AS when using T8 interface. The transactions consist of one request message followed by one or more response messages. It is created by the originator of the transaction, and is unique through the duration of the transaction. It is stored on both the SCEF and the SCS/AS for the duration of the transaction, in TS23.303 clause 4.9.2.

2. Based on operator policies, if the 3rd party SCS/AS is not authorized to perform this request (e.g. if the SLA does not allow it, e.g. due to the system load situation), the SCEF performs action 6 and provides a Cause value appropriately indicating the error. Otherwise, the SCEF translates each external Application Identifier to the corresponding Application Identifier known at the C-UTM function. Also, the SCEF may interact with HSS to request for the translations of External identifiers/External Group identifiers.

3. The SCEF sends a UAS Operation Service Authorization Request message (Application Identifier(s), one or more sets of UAS operation information for each Application Identifier, External identifiers/External Group identifiers or IMSI) to the C-UTMF.

4. The C-UTM function checks the UAS authorization for the UAV/UAV controller based on External identifiers/External Group identifiers or IMSI.

5. If UAS operation authorization is done successfully, it continues to create the list of UAS operation policies for each Application Identifier into the C-UTM function as requested by the respective UAS operation. If any of the authorization fails, the C-UTM function sends UAS Operation Service Authorization Response (Application Identifier(s), Cause) message to provide the feedback of the handling result for the C-UTM Service Request, whereby the cause can indicates the failure reasons for the authorization per Application ID, e.g. service suspend, service expiration, service unavailable, etc.

6. The SCEF sends a UAS Operation Service Response (TTRI, Result) message to the 3rd party SCS/AS to provide the feedback of the handling result for UAS Operation Service Request.

Implementation 3: UAS Operation Status Update Notification

According to some embodiments, following implementation 2, based on the received C-UTM Service Response from the NEF for both of the UAV and the UAV controller, the AF determines if the UAS authorization can be accepted.If the association is done successfully to find the match, the AF sends a notification to C-UTM function via NEF to notify the UAS operation status including UAS association information, UAS policies updates, and initiation of the UAS operation. When the AF receives response message to the status update, the UAS operation can be started.The AF may reply application layer confirmation message to the UAV and the UAV controller for the start of the UAS operation.

The procedure for notifying UAS operation status in 5GS is illustrated inFIG.8. According to some embodiments, the UAS operation services requested may rely on the following process:

1. The UTM-AF notifies the successful association of a UAS by sending a Nnef_UAS_Operation_Status_Update Request (AF Identifier, Transaction Reference ID, External identifiers/External Group identifiers of the UAV/UAV controller, UAS operation Status for each Application Identifier, UAS_ID) message to the NEF.the UAS operation status can indicate the enabled UAS operation parameters per Application identifier and indicates the corresponding UAS_ID.the UAS_ID is allocated by the UTM-AF to identify the association between a UAV and a UAV controller. The related UAS operation for the UAS is associated to the same UAS-ID.The UAS operation parameters may include: the allowed application IDs for the UAS operation, UAS operation mode (e.g. indirect C2, direct C2, network navigated C2), IP addresses of available UTM application servers, allowed geographical areas, allowed operation time, allowed operation duration, etc.

2. NEF checks the AF authorization of the request for UAS operation status update if the Transaction Reference ID is expired.

3. NEF sends the Ncutm_UAS Status Update request (SUPI, UAS operation Status for each Application Identifier, UAS_ID) message to the C-UTM/PCF.

4. C-UTM/PCF function updates the UAS operation status including the policies per application identifier and the associated UAS_ID.

5. C-UTM/PCF function returns the confirmation of the status update to the NEF by sending Ncutm_UAS Operation Update response (UAS_ID, SUPI) message.

6. The NEF returns the Nnef_UAS_Operation_Status_Update response (Transaction Reference ID) message to the AF.

Alternatively, the UAS_ID can be allocated by the C-UTM/PCF in action 4 to identify the associated UAS operation policies when received the status update indicating the successful association for the UAV/UAV controller. The C-UTM/PCF function starts to use the UAS-ID to identify the UAS and activate UAS operation policy for any indicated UAS services events associated to the UAV and the UAV controller. In this case, the following modification may be implemented:Action 1: replace UAS_ID with External identifiers/External Group identifiers of the UAV/UAV controllerAction 3: UAS_ID is not includedAction 5: UAS_ID is provided along with the SUPI to indicate that the SUPI is with active UAS operation policies associated to the UAS_ID.Action 6: UAS_ID is provided in the Nnef_UAS_Operation_Status_Update response message.

The similar procedure can be supported in EPS as further illustrated inFIG.9(Procedure for Notifying UAS Operating Status in EPS).

The similar message flows can be exchanged between the SCS/AS with UTM-Application Server and the C-UTM function for the UAS operation Stop/Suspend/Resume procedure as shown inFIG.7with proper messages or indication in the messages to indicate the action requested, e.g. start, stop, suspend, resume, for the indicated service identified by the application ID.

Implementation 4: C2 Communication Set Up for an AS Session with Required QoS

According to some embodiments, in the AF session setup with required QoS procedure, the AF includes description of the application flows to indicate the following two sessions:The UTM session between AF and the UAV: this connection is to track real-time UAV trajectories, in flight meters information, etc. In the network navigated C2 (as shown inFIG.2), this session can be used to transport commands to control/operate the UAV remotely and directly.The C2 session between UEs in UAV and the UAV controller: this connection is to transport the control and commands received from the UAV controller, operated by a pilot, and forwarded to UAV, and vice versa. In response, the UAV can also use this C2 session to respond some real-time UAV trajectories, in flight meters information, and even a real-time video. There are two options to anchor the C2 session between the UAV and the UAV controllerOption 1—The AF is the anchor point: the UAV and the UAV controller sends commands and response message to the AF and the AF forwards the message, e.g. from the UAV controller to the UAV.Option 2—The AF session is identified by the policies associated with DNAI (DN access identifier over N6) for the UAV or UAV controller.

According to some aspects, if the PCF support C-UTM functionalities, the procedure of setting up an AS session with required QoS in clause 4.15.6.6 at TS23.502 can be reused with the abovementioned description of the application flows for UTM session and C2 session.

According to some aspects, if the C-UTM function is a standalone network function, the additional message exchange is required to interact with PCF directly (with new interface between PCF and the C-UTM) or via NEF (with request to NEF for triggering message as action 3 and 4 via NEF inFIG.10(Setting up an AS session with required QoS in 5GS).

In EPS, similar message flows can be exchanged between the SCS/AS with UTM-Application Server as shown inFIG.11(Setting up an AS session with required QoS in EPS), in which the C-UTM function can be PCRF or interact with policy control rules function (PCRF) for dynamic Policy and Charging Control (PCC) and inferencing traffics in PDN connections via PCEF (PGW) and BBERF (SGW), TS23.203. The procedure of setting up an AS session with required QoS in clause 5.11 at TS23.682 can be reused with the abovementioned description of the application flows for UTM session and C2 session.

According to some embodiments, following implementation 3, if the UTM-AF detecting the violation of the agreed flight policy, e.g. approaching/entering a forbidden zone, the UTM-AF may enforce the following actions to take over the control of the UAV:

Option 1: (C2 session is anchored at the AF)the UTM application server replaces the commands sent by the UAV controller with its new command to take over the UAV controller using the C2 session.In this option, the UAV is not aware that UTM-AF is involving the C2 communication to fly the UAV.

Option 2: (C2 session is associated with DNAI)The UTM-AF may send warning message to notify the UAV controller for UAS operation via UTM session with UAV controller.The UTM-AF may send notification message to notify the UAV for UAS operation via UTM session with the UAV.the UTM-AF sends a request message to C-UTM/PCF for suspending the UAS operation via C2 session or update the UAS operation mode to network navigated C2 mode (as shown inFIG.2).Further, the UTM-AF uses the UTM session to signal the commands for navigating the UAV directly.The UAV receives the notification indication and then ignores any information sent by the UAV controller and only follows the instructions from the UTM.
Implementation 4.2: For the AF Session with Multiple Traffic Types.

According to some embodiments, following implementation 4, for the C2 session with the traffic types as indicated in Table 1, this implementation provide mechanism for the AF to request differentiated QoS for each IP flows with different traffic types.

Referring toFIG.10, the AF sends Nnef AFsessionWithQoS Create request message and include traffic type information per Description of the application flows, i.e. per application and IP flows.

Option 1: The traffic type definition can be pre-configured in NEF/PCF based on the agreements between the MNO and third party AF. By this way, the NEF and PCF can differentiate the traffic flows based on the traffic type definition and provision with corresponding QoS, whereby the traffic types includes commands, video streaming, real-time traffic (voice), telemetry, etc.

Option 2: the UTM provisions parameters to NEF/PCF for defining traffic types of C2 communication including commands, video streaming, real-time traffic (voice), telemetry, etc. The procedure illustrated inFIG.12(associated with FIG. 4.15.6.2-1 Nnef_ParameterProvision_update request/response operations in TS23.502) can be used to provision parameters of traffic types with associated application identifier to the UDM/UDR via NEF.

Option 3: The UTM allocates different port numbers for an IP flow which is corresponding to different traffic types. The AS session setting up with required QoS procedure as indicated inFIGS.10and11can be used to differentiate IP flows with port number corresponding to different traffic types. Different traffic types can thus be provisioned with required QoS.

According to some aspects, by this way, the NEF and PCF can differentiate the traffic flows with corresponding QoS, in which the following service requirements can be fulfilled.The 5G system shall support a mechanism to interact with UTM for obtaining required UAS service information with traffic types, traffic flows, and requested QoS for handling C2 communication with differentiated QoS and traffic policies.The 5G system shall allow UTM to provision parameters for traffic types of C2 communication including commands, video streaming, telemetry, etc.The 5G system shall be able to identify the traffic of a UAS for command and control (C2) communication and other traffic associated to the same or different applications.The 5G system shall provide a mechanism to provision required QoS to the traffic for C2 communication and other traffic associated to the same or different applications.
Implementation 5: Flight Plan Based UAS Operation

For the flight plan based operation as shown inFIG.2, the UTM-AF acts as a role of UAV controller. Therefore, UAS association procedure is not needed.For the network navigated C2 with flight plan for UAS operation, the previous implementation 2 and 3 are needed only for UAV.For solution3, only UTM session is required.Further, for the subscription, the UAV needs to have subscription for UAS Operation using network navigated C2. In this case, the UAV is remotely controlled by the UTM application server.
Implementation 6: EPS Enhancement for UAS Association and Identification Procedure

This solution provides the following method for the UAS association and UAS identification between the UAV and UAV controller.

In this solution, assuming that the UE in the UAS is registered to EPC, the UAS association between the UAV and UAV controller may reuse the method in TS23.303 clause 5.5 of EPC-level ProSe Discovery procedure, with the following modification as EPC-level UAS Identification and Association procedure for UAS service.The related identifiers can be referred to clause 4.6.1. The corresponding sets of identifiers are designed for UAS users.The C-UTM function acts as a ProSe Function, and the UTM-AF is as Application Server.The C-UTM function stores the UAS service authorization information.After the UAV and the UAV controller get confirmation for the successful association from the C-UTM function, they don't need to perform ProSe direct discovery procedure.

According to some aspects, a Proximity Request procedure comparable to clause 5.5.5 in TS23.303 (illustrated inFIG.13), may be used to identify the UAV and the UAV controller to be associated and can be operated as a UAS:The App Server stores the association information of the UAV and the UAV controller.If UAV and the UAV controller have been registered to the Application server.In action 3, the MAP Response message contains an indication for the confirmation of the association.In action 4, the Proximity Request message indicates to the ProSe Function B for the confirmation of the association.In action 8b, Proximity Request Ack message indicates to the UE-A for the confirmation of the association.The indication in the above message can be an UAS-ID allocated by the App Server/C-UTM Function A.In Action 5, the new criterion to reject the request is added such that the C-UTM Function B may determine that the network cannot provide reliable and low latency C2 communication connection between the UAV and the UAV controller via network. The C-UTM Function B can reject the proximity request with an appropriate cause value.If the indication is an UAS ID, in the Proximity Alert procedure in clause 5.5.7 of TS23.303 (illustrated inFIG.14), in Action 4b and 5a Proximity Alert message may then contain the UAS ID to UE A and UE B, respectively.

Alternatively, since two UEs do not have to be in proximity to be associated (discovered). Therefore, the following optimization can be done:for the proximity Request procedure in clause 5.5.5e, location related procedure may be skipped in action 5a, 7a, 8a, e.g. by setting Range class as a value that can be ignored, e.g. * means any ranges, or making Range IE as optional (not included in the action 1).After receiving Proximity request in action 4, if the UE B has not been authorized by the C-UTM Function B, the C-UTM Function B sets a validity timer for the UE B based on the value of window. If the UE B reaches to C-UTM function B for UAS authorization using Proximity Request to the C-UTM function B, and the C-UTM Function B authorizes the UE B before the validity timer is expired, the C-UTM function B sends Proximity Alert message to UE A via C-UTM Function A, as shown in action 4b in clause 5.5.7, Proximity Alert procedure.

According to some embodiments, for 5GS, the procedure can use the similar message flows with the following additions:Requires new messages to exchange information for interface between the C-UTM/PCF function A and C UTM/PCF function B.Requires new message to exchange information for communication between the UAV/UAV-C and the C-UTM/PCF function. If PCF is with C-UTM functionalities, the UE initiated UE Configuration Update procedure can be applied.LCS related message flows can be replaced by the eLCS procedures in 5GS.
Implementation 7:

This implementation addresses issue 5.

According to some embodiments, the 3GPP system shall enable a UAV to broadcast the following information in broadcasting message in a short-range area for collision avoidance: UAV identities, UAV type, current location and time, locations at point of interest at next 6-10 seconds, current speed, detected information from nearby UAVs, operating status.

The local broadcasting mechanism can refer to TS23.303 clause 5.4.1-5.4.3: Procedures for ProSe Direct one-to-many Communication without related group configuration. Illustrated inFIG.15is a one-to-many ProSe Direct Communication transmission (associated with FIG. 5.4.2-1 of TS23.303).

Systems and Implementations

FIG.16illustrates an example architecture of a system1600of a network, in accordance with various embodiments. The following description is provided for an example system1600that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications. 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 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.

As shown byFIG.16, the system1600includes UE1601aand UE1601b(collectively referred to as “UEs1601” or “UE1601”). In this example, UEs1601are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, MTC devices, M2M, IoT devices, and/or the like.

The UEs1601may be configured to connect, for example, communicatively couple, with an or RAN1610. In embodiments, the RAN1610may be an NG RAN or a 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term “NG RAN” or the like may refer to a RAN1610that operates in an NR or 5G system1600, and the term “E-UTRAN” or the like may refer to a RAN1610that operates in an LTE or 4G system1600. The UEs1601utilize connections (or channels)1603and1604, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below).

In this example, the connections1603and1604are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and/or any of the other communications protocols discussed herein. In embodiments, the UEs1601may directly exchange communication data via a ProSe interface1605. The ProSe interface1605may alternatively be referred to as a SL interface1605and may comprise one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE1601bis shown to be configured to access an AP1606(also referred to as “WLAN node1606,” “WLAN 1606,” “WLAN Termination1606,” “WT1606” or the like) via connection1607. The connection1607can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP1606would comprise a wireless fidelity (Wi-Fi®) router. In this example, the AP1606is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE1601b, RAN1610, and AP1606may be configured to utilize LWA operation and/or LWIP operation. The LWA operation may involve the UE1601bin RRC_CONNECTED being configured by a RAN node1611a-bto utilize radio resources of LTE and WLAN. LWIP operation may involve the UE1601busing WLAN radio resources (e.g., connection1607) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection1607. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

The RAN1610can include one or more AN nodes or RAN nodes1611aand1611b(collectively referred to as “RAN nodes1611” or “RAN node1611”) that enable the connections1603and1604. As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs or TRPs, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to a RAN node1611that operates in an NR or 5G system1600(for example, a gNB), and the term “E-UTRAN node” or the like may refer to a RAN node1611that operates in an LTE or 4G system1600(e.g., an eNB). According to various embodiments, the RAN nodes1611may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In some embodiments, all or parts of the RAN nodes1611may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes1611; a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes1611; or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAN/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes1611. This virtualized framework allows the freed-up processor cores of the RAN nodes1611to perform other virtualized applications. In some implementations, an individual RAN node1611may represent individual gNB-DUs that are connected to a gNB-CU via individual F1 interfaces (not shown byFIG.16). In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs (see, e.g.,FIG.19), and the gNB-CU may be operated by a server that is located in the RAN1610(not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally or alternatively, one or more of the RAN nodes1611may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UEs1601, and are connected to a 5GC (e.g., CN1820ofFIG.18) via an NG interface (discussed infra).

In V2X scenarios one or more of the RAN nodes1611may be or act as RSUs. The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by 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 UEs1601(vUEs1601). 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 operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to 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 operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communications. The computing device(s) and some or all of the radiofrequency circuitry 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 and/or a backhaul network.

Any of the RAN nodes1611can terminate the air interface protocol and can be the first point of contact for the UEs1601. In some embodiments, any of the RAN nodes1611can fulfill various logical functions for the RAN1610including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

According to various embodiments, the UEs1601,1602and the RAN nodes1611,1612communicate data (for example, transmit and receive) data over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”) and an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”). The licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UEs1601,1602and the RAN nodes1611,1612may operate using LAA, eLAA, and/or feLAA mechanisms. In these implementations, the UEs1601,1602and the RAN nodes1611,1612may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UEs1601,1602, RAN nodes1611,1612, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies. WLAN employs a contention-based channel access mechanism, called CSMA/CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE1601or1602, AP1606, or the like) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time. The backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds. The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulatory requirements.

The LAA mechanisms are built upon CA technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a CC. A CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can be different for DL and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.

CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities. The other serving cells are referred to as SCells, and each SCell may provide an individual SCC for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require the UE1601,1602to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.

The PDSCH carries user data and higher-layer signaling to the UEs1601. The PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs1601about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE1601bwithin a cell) may be performed at any of the RAN nodes1611based on channel quality information fed back from any of the UEs1601. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs1601.

The RAN nodes1611may be configured to communicate with one another via interface1612. In embodiments where the system1600is an LTE system (e.g., when CN1620is an EPC1720as inFIG.17), the interface1612may be an X2 interface1612. The X2 interface may be defined between two or more RAN nodes1611(e.g., two or more eNBs and the like) that connect to EPC1620, and/or between two eNBs connecting to EPC1620. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE1601from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE1601; information about a current minimum desired buffer size at the SeNB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.

In embodiments where the system1600is a 5G or NR system (e.g., when CN1620is an 5GC1820as inFIG.18), the interface1612may be an Xn interface1612. The Xn interface is defined between two or more RAN nodes1611(e.g., two or more gNBs and the like) that connect to 5GC1620, between a RAN node1611(e.g., a gNB) connecting to 5GC1620and an eNB, and/or between two eNBs connecting to 5GC1620. In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE1601in a connected mode (e.g., CM-CONNECTED) including functionality to manage the UE mobility for connected mode between one or more RAN nodes1611. The mobility support may include context transfer from an old (source) serving RAN node1611to new (target) serving RAN node1611; and control of user plane tunnels between old (source) serving RAN node1611to new (target) serving RAN node1611. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP. The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

The RAN1610is shown to be communicatively coupled to a core network—in this embodiment, core network (CN)1620. The CN1620may comprise a plurality of network elements1622, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UEs1601) who are connected to the CN1620via the RAN1610. The components of the CN1620may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN1620may be referred to as a network slice, and a logical instantiation of a portion of the CN1620may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

Generally, the application server1630may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server1630can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs1601via the EPC1620.

In embodiments, the CN1620may be a 5GC (referred to as “5GC1620” or the like), and the RAN1610may be connected with the CN1620via an NG interface1613. In embodiments, the NG interface1613may be split into two parts, an NG user plane (NG-U) interface1614, which carries traffic data between the RAN nodes1611and a UPF, and the S1 control plane (NG-C) interface1615, which is a signaling interface between the RAN nodes1611and AMFs. Embodiments where the CN1620is a 5GC1620are discussed in more detail with regard toFIG.18.

In embodiments, the CN1620may be a 5G CN (referred to as “5GC1620” or the like), while in other embodiments, the CN1620may be an EPC). Where CN1620is an EPC (referred to as “EPC1620” or the like), the RAN1610may be connected with the CN1620via an S1 interface1613. In embodiments, the S1 interface1613may be split into two parts, an S1 user plane (S1-U) interface1614, which carries traffic data between the RAN nodes1611and the S-GW, and the S1-MME interface1615, which is a signaling interface between the RAN nodes1611and MMEs. An example architecture wherein the CN1620is an EPC1620is shown byFIG.17.

FIG.17illustrates an example architecture of a system1700including a first CN1720, in accordance with various embodiments. In this example, system1700may implement the LTE standard wherein the CN1720is an EPC1720that corresponds with CN1620ofFIG.16. Additionally, the UE1701may be the same or similar as the UEs1601ofFIG.16, and the E-UTRAN1710may be a RAN that is the same or similar to the RAN1610ofFIG.16, and which may include RAN nodes1611discussed previously. The CN1720may comprise MMEs1721, an S-GW1722, a P-GW1723, a HSS1724, and a SGSN1725.

The MMEs1721may be similar in function to the control plane of legacy SGSN, and may implement MM functions to keep track of the current location of a UE1701. The MMEs1721may perform various MM procedures to manage mobility aspects in access such as gateway selection and tracking area list management. MM (also referred to as “EPS MM” or “EMM” in E-UTRAN systems) may refer to all applicable procedures, methods, data storage, etc. that are used to maintain knowledge about a present location of the UE1701, provide user identity confidentiality, and/or perform other like services to users/subscribers. Each UE1701and the MME1721may include an MM or EMM sublayer, and an MM context may be established in the UE1701and the MME1721when an attach procedure is successfully completed. The MM context may be a data structure or database object that stores MM-related information of the UE1701. The MMEs1721may be coupled with the HSS1724via an S6a reference point, coupled with the SGSN1725via an S3 reference point, and coupled with the S-GW1722via an S11 reference point.

The SGSN1725may be a node that serves the UE1701by tracking the location of an individual UE1701and performing security functions. In addition, the SGSN1725may perform Inter-EPC node signaling for mobility between 2G/3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by the MMEs1721; handling of UE1701time zone functions as specified by the MMEs1721; and MME selection for handovers to E-UTRAN 3GPP access network. The S3 reference point between the MMEs1721and the SGSN1725may enable user and bearer information exchange for inter-3GPP access network mobility in idle and/or active states.

The HSS1724may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The EPC1720may comprise one or several HSSs1724, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS1724can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS1724and the MMEs1721may enable transfer of subscription and authentication data for authenticating/authorizing user access to the EPC1720between HSS1724and the MMEs1721.

The S-GW1722may terminate the S1 interface1613(“S1-U” inFIG.17) toward the RAN1710, and routes data packets between the RAN1710and the EPC1720. In addition, the S-GW1722may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement. The S11 reference point between the S-GW1722and the MMEs1721may provide a control plane between the MMEs1721and the S-GW1722. The S-GW1722may be coupled with the P-GW1723via an S5 reference point.

The P-GW1723may terminate an SGi interface toward a PDN1730. The P-GW1723may route data packets between the EPC1720and external networks such as a network including the application server1630(alternatively referred to as an “AF”) via an IP interface1625(see e.g.,FIG.16). In embodiments, the P-GW1723may be communicatively coupled to an application server (application server1630ofFIG.16or PDN1730inFIG.17) via an IP communications interface1625(see, e.g.,FIG.16). The S5 reference point between the P-GW1723and the S-GW1722may provide user plane tunneling and tunnel management between the P-GW1723and the S-GW1722. The S5 reference point may also be used for S-GW1722relocation due to UE1701mobility and if the S-GW1722needs to connect to a non-collocated P-GW1723for the required PDN connectivity. The P-GW1723may further include a node for policy enforcement and charging data collection (e.g., PCEF (not shown)). Additionally, the SGi reference point between the P-GW1723and the packet data network (PDN)1730may be an operator external public, a private PDN, or an intra operator packet data network, for example, for provision of IMS services. The P-GW1723may be coupled with a PCRF1726via a Gx reference point.

PCRF1726is the policy and charging control element of the EPC1720. In a non-roaming scenario, there may be a single PCRF1726in the Home Public Land Mobile Network (HPLMN) associated with a UE1701's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE1701's IP-CAN session, a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF1726may be communicatively coupled to the application server1730via the P-GW1723. The application server1730may signal the PCRF1726to indicate a new service flow and select the appropriate QoS and charging parameters. The PCRF1726may provision this rule into a PCEF (not shown) with the appropriate TFT and QCI, which commences the QoS and charging as specified by the application server1730. The Gx reference point between the PCRF1726and the P-GW1723may allow for the transfer of QoS policy and charging rules from the PCRF1726to PCEF in the P-GW1723. An Rx reference point may reside between the PDN1730(or “AF1730”) and the PCRF1726.

FIG.18illustrates an architecture of a system1800including a second CN1820in accordance with various embodiments. The system1800is shown to include a UE1801, which may be the same or similar to the UEs1601and UE1701discussed previously; a (R)AN1810, which may be the same or similar to the RAN1610and RAN1710discussed previously, and which may include RAN nodes1611discussed previously; and a DN1803, which may be, for example, operator services, Internet access or 3rd party services; and a 5GC1820. The 5GC1820may include an AUSF1822; an AMF1821; a SMF1824; a NEF1823; a PCF1826; a NRF1825; a UDM1827; an AF1828; a UPF1802; and a NSSF1829.

The UPF1802may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to DN1803, and a branching point to support multi-homed PDU session. The UPF1802may 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. UPF1802may include an uplink classifier to support routing traffic flows to a data network. The DN1803may represent various network operator services, Internet access, or third party services. DN1803may include, or be similar to, application server1630discussed previously. The UPF1802may interact with the SMF1824via an N4 reference point between the SMF1824and the UPF1802.

The AUSF1822may store data for authentication of UE1801and handle authentication-related functionality. The AUSF1822may facilitate a common authentication framework for various access types. The AUSF1822may communicate with the AMF1821via an N12 reference point between the AMF1821and the AUSF1822; and may communicate with the UDM1827via an N13 reference point between the UDM1827and the AUSF1822. Additionally, the AUSF1822may exhibit an Nausf service-based interface.

The AMF1821may be responsible for registration management (e.g., for registering UE1801, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF1821may be a termination point for the an N11 reference point between the AMF1821and the SMF1824. The AMF1821may provide transport for SM messages between the UE1801and the SMF1824, and act as a transparent proxy for routing SM messages. AMF1821may also provide transport for SMS messages between UE1801and an SMSF (not shown byFIG.18). AMF1821may act as SEAF, which may include interaction with the AUSF1822and the UE1801, receipt of an intermediate key that was established as a result of the UE1801authentication process. Where USIM based authentication is used, the AMF1821may retrieve the security material from the AUSF1822. AMF1821may also include a SCM function, which receives a key from the SEA that it uses to derive access-network specific keys. Furthermore, AMF1821may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the (R)AN1810and the AMF1821; and the AMF1821may be a termination point of NAS (N1) signalling, and perform NAS ciphering and integrity protection.

AMF1821may also support NAS signalling with a UE1801over an N3 IWF interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN1810and the AMF1821for the control plane, and may be a termination point for the N3 reference point between the (R)AN1810and the UPF1802for the user plane. As such, the AMF1821may handle N2 signalling from the SMF1824and the AMF1821for PDU sessions and QoS, encapsulate/de-encapsulate packets for IPSec and N3 tunnelling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking taking into account QoS requirements associated with such marking received over N2. N3IWF may also relay uplink and downlink control-plane NAS signalling between the UE1801and AMF1821via an N1 reference point between the UE1801and the AMF1821, and relay uplink and downlink user-plane packets between the UE1801and UPF1802. The N3IWF also provides mechanisms for IPsec tunnel establishment with the UE1801. The AMF1821may exhibit an Namf service-based interface, and may be a termination point for an N14 reference point between two AMFs1821and an N17 reference point between the AMF1821and a 5G-EIR (not shown byFIG.18).

The UE1801may need to register with the AMF1821in order to receive network services. RM is used to register or deregister the UE1801with the network (e.g., AMF1821), and establish a UE context in the network (e.g., AMF1821). The UE1801may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE1801is not registered with the network, and the UE context in AMF1821holds no valid location or routing information for the UE1801so the UE1801is not reachable by the AMF1821. In the RM-REGISTERED state, the UE1801is registered with the network, and the UE context in AMF1821may hold a valid location or routing information for the UE1801so the UE1801is reachable by the AMF1821. In the RM-REGISTERED state, the UE1801may perform mobility Registration Update procedures, perform periodic Registration Update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE1801is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

The AMF1821may store one or more RM contexts for the UE1801, where each RM context is associated with a specific access to the network. The RM context may be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer. The AMF1821may also store a 5GC MM context that may be the same or similar to the (E)MM context discussed previously. In various embodiments, the AMF1821may store a CE mode B Restriction parameter of the UE1801in an associated MM context or RM context. The AMF1821may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and/or MM/RM context).

CM may be used to establish and release a signaling connection between the UE1801and the AMF1821over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE1801and the CN1820, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE1801between the AN (e.g., RAN1810) and the AMF1821. The UE1801may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE1801is operating in the CM-IDLE state/mode, the UE1801may have no NAS signaling connection established with the AMF1821over the N1 interface, and there may be (R)AN1810signaling connection (e.g., N2 and/or N3 connections) for the UE1801. When the UE1801is operating in the CM-CONNECTED state/mode, the UE1801may have an established NAS signaling connection with the AMF1821over the N1 interface, and there may be a (R)AN1810signaling connection (e.g., N2 and/or N3 connections) for the UE1801. Establishment of an N2 connection between the (R)AN1810and the AMF1821may cause the UE1801to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE1801may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN1810and the AMF1821is released.

The SMF1824may be responsible for SM (e.g., session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement 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 over N2 to AN; 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 a UE1801and a data network (DN)1803identified by a Data Network Name (DNN). PDU sessions may be established upon UE1801request, modified upon UE1801and 5GC1820request, and released upon UE1801and 5GC1820request using NAS SM signaling exchanged over the N1 reference point between the UE1801and the SMF1824. Upon request from an application server, the 5GC1820may trigger a specific application in the UE1801. In response to receipt of the trigger message, the UE1801may pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE1801. The identified application(s) in the UE1801may establish a PDU session to a specific DNN. The SMF1824may check whether the UE1801requests are compliant with user subscription information associated with the UE1801. In this regard, the SMF1824may retrieve and/or request to receive update notifications on SMF1824level subscription data from the UDM1827.

The SMF1824may include the following roaming functionality: handling local enforcement to apply QoS SLAB (VPLMN); charging data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signalling for PDU session authorization/authentication by external DN. An N16 reference point between two SMFs1824may be included in the system1800, which may be between another SMF1824in a visited network and the SMF1824in the home network in roaming scenarios. Additionally, the SMF1824may exhibit the Nsmf service-based interface.

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

The NRF1825may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF1825also 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 NRF1825may exhibit the Nnrf service-based interface.

The PCF1826may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behaviour. The PCF1826may also implement an FE to access subscription information relevant for policy decisions in a UDR of the UDM1827. The PCF1826may communicate with the AMF1821via an N15 reference point between the PCF1826and the AMF1821, which may include a PCF1826in a visited network and the AMF1821in case of roaming scenarios. The PCF1826may communicate with the AF1828via an N5 reference point between the PCF1826and the AF1828; and with the SMF1824via an N7 reference point between the PCF1826and the SMF1824. The system1800and/or CN1820may also include an N24 reference point between the PCF1826(in the home network) and a PCF1826in a visited network. Additionally, the PCF1826may exhibit an Npcf service-based interface.

The UDM1827may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE1801. For example, subscription data may be communicated between the UDM1827and the AMF1821via an N8 reference point between the UDM1827and the AMF. The UDM1827may include two parts, an application FE and a UDR (the FE and UDR are not shown byFIG.18). The UDR may store subscription data and policy data for the UDM1827and the PCF1826, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs1801) for the NEF1823. The Nudr service-based interface may be exhibited by the UDR221to allow the UDM1827, PCF1826, and NEF1823to 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. The UDR may interact with the SMF1824via an N10 reference point between the UDM1827and the SMF1824. UDM1827may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM1827may exhibit the Nudm service-based interface.

The AF1828may provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control. The NCE may be a mechanism that allows the 5GC1820and AF1828to provide information to each other via NEF1823, which may be used for edge computing implementations. In such implementations, the network operator and third party services may be hosted close to the UE1801access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF1802close to the UE1801and execute traffic steering from the UPF1802to DN1803via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF1828. In this way, the AF1828may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF1828is considered to be a trusted entity, the network operator may permit AF1828to interact directly with relevant NFs. Additionally, the AF1828may exhibit an Naf service-based interface.

The NSSF1829may select a set of network slice instances serving the UE1801. The NSSF1829may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF1829may also determine the AMF set to be used to serve the UE1801, or a list of candidate AMF(s)1821based on a suitable configuration and possibly by querying the NRF1825. The selection of a set of network slice instances for the UE1801may be triggered by the AMF1821with which the UE1801is registered by interacting with the NSSF1829, which may lead to a change of AMF1821. The NSSF1829may interact with the AMF1821via an N22 reference point between AMF1821and NSSF1829; and may communicate with another NSSF1829in a visited network via an N31 reference point (not shown byFIG.18). Additionally, the NSSF1829may exhibit an Nnssf service-based interface.

As discussed previously, the CN1820may include an SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE1801to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF1821and UDM1827for a notification procedure that the UE1801is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM1827when UE1801is available for SMS).

The CN1820may also include other elements that are not shown byFIG.18, such as a Data Storage system/architecture, a 5G-EIR, a SEPP, and the like. The Data Storage system may include a SDSF, an UDSF, and/or the like. Any NF may store and retrieve unstructured data into/from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown byFIG.18). Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs. Additionally, the UDSF may exhibit an Nudsf service-based interface (not shown byFIG.18). The 5G-EIR may be an NF that checks the status of PEI for determining whether particular equipment/entities are blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

Additionally, there may be many more reference points and/or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted fromFIG.18for clarity. In one example, the CN1820may include an Nx interface, which is an inter-CN interface between the MME (e.g., MME1721) and the AMF1821in order to enable interworking between CN1820and CN1720. Other example interfaces/reference points may include an N5g-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.

FIG.19illustrates an example of infrastructure equipment1900in accordance with various embodiments. The infrastructure equipment1900(or “system1900”) may be implemented as a base station, radio head, RAN node such as the RAN nodes1611and/or AP1606shown and described previously, application server(s)1630, and/or any other element/device discussed herein. In other examples, the system1900could be implemented in or by a UE.

The system1900includes application circuitry1905, baseband circuitry1910, one or more radio front end modules (RFEMs)1915, memory circuitry1920, power management integrated circuitry (PMIC)1925, power tee circuitry1930, network controller circuitry1935, network interface connector1940, satellite positioning circuitry1945, and user interface1950. In some embodiments, the device1900may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (110) interface. In other embodiments, the components described below may be included in more than one device. For example, said circuitries may be separately included in more than one device for CRAN, vBBU, or other like implementations.

In some implementations, the application circuitry1905may include one or 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. As examples, the programmable processing devices may be one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of application circuitry1905may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry1905may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up-tables (LUTs) and the like.

The baseband circuitry1910may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry1910are discussed infra with regard toFIG.21.

The PMIC1925may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions. The power tee circuitry1930may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment1900using a single cable.

The network controller circuitry1935may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to/from the infrastructure equipment1900via network interface connector1940using a physical connection, which may be electrical (commonly referred to as a “copper interconnect”), optical, or wireless. The network controller circuitry1935may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the network controller circuitry1935may include multiple controllers to provide connectivity to other networks using the same or different protocols.

The positioning circuitry1945includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) include United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), etc.), or the like. The positioning circuitry1945comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry1945may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry1945may also be part of, or interact with, the baseband circuitry1910and/or RFEMs1915to communicate with the nodes and components of the positioning network. The positioning circuitry1945may also provide position data and/or time data to the application circuitry1905, which may use the data to synchronize operations with various infrastructure (e.g., RAN nodes1611, etc.), or the like.

The components shown byFIG.19may communicate with one another using interface circuitry, which may include any number of bus and/or interconnect (IX) technologies such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus/IX may be a proprietary bus, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I2C interface, an SPI interface, point to point interfaces, and a power bus, among others.

FIG.20illustrates an example of a platform2000(or “device2000”) in accordance with various embodiments. In embodiments, the computer platform2000may be suitable for use as UEs1601,1602,1701, application servers1630, and/or any other element/device discussed herein. The platform2000may include any combinations of the components shown in the example. The components of platform2000may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform2000, or as components otherwise incorporated within a chassis of a larger system. The block diagram ofFIG.20is intended to show a high level view of components of the computer platform2000. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

The processor(s) of application circuitry1905may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuitry1905may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.

As examples, the processor(s) of application circuitry2005may include an Intel® Architecture Core™ based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation, Santa Clara, CA The processors of the application circuitry2005may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); A5-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; an ARM-based design licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M family of processors; or the like. In some implementations, the application circuitry2005may be a part of a system on a chip (SoC) in which the application circuitry2005and other components are formed into a single integrated circuit, or a single package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.

The baseband circuitry2010may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits. The various hardware electronic elements of baseband circuitry2010are discussed infra with regard toFIG.21.

The memory circuitry2020may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry2020may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry2020may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry2020may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuitry2020may be on-die memory or registers associated with the application circuitry2005. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry2020may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a micro HDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others. For example, the computer platform2000may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.

Removable memory circuitry2023may include devices, circuitry, enclosures/housings, ports or receptacles, etc. used to couple portable data storage devices with the platform2000. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.

The platform2000may also include interface circuitry (not shown) that is used to connect external devices with the platform2000. The external devices connected to the platform2000via the interface circuitry include sensor circuitry2021and electro-mechanical components (EMCs)2022, as well as removable memory devices coupled to removable memory circuitry2023.

The sensor circuitry2021include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units (IMUS) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio capture devices; etc.

EMCs2022include devices, modules, or subsystems whose purpose is to enable platform2000to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally, EMCs2022may be configured to generate and send messages/signalling to other components of the platform2000to indicate a current state of the EMCs2022. Examples of the EMCs2022include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components. In embodiments, platform2000is configured to operate one or more EMCs2022based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients.

In some implementations, the interface circuitry may connect the platform2000with positioning circuitry2045. The positioning circuitry2045includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) include United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.), or the like. The positioning circuitry2045comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry2045may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry2045may also be part of, or interact with, the baseband circuitry1910and/or RFEMs2015to communicate with the nodes and components of the positioning network. The positioning circuitry2045may also provide position data and/or time data to the application circuitry2005, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like

In some implementations, the interface circuitry may connect the platform2000with Near-Field Communication (NFC) circuitry2040. NFC circuitry2040is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry2040and NFC-enabled devices external to the platform2000(e.g., an “NFC touchpoint”). NFC circuitry2040comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry2040by executing NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RF signals. The RF signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry2040, or initiate data transfer between the NFC circuitry2040and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform2000.

The driver circuitry2046may include software and hardware elements that operate to control particular devices that are embedded in the platform2000, attached to the platform2000, or otherwise communicatively coupled with the platform2000. The driver circuitry2046may include individual drivers allowing other components of the platform2000to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform2000. For example, driver circuitry2046may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform2000, sensor drivers to obtain sensor readings of sensor circuitry2021and control and allow access to sensor circuitry2021, EMC drivers to obtain actuator positions of the EMCs2022and/or control and allow access to the EMCs2022, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (PMIC)2025(also referred to as “power management circuitry2025”) may manage power provided to various components of the platform2000. In particular, with respect to the baseband circuitry2010, the PMIC2025may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC2025may often be included when the platform2000is capable of being powered by a battery2030, for example, when the device is included in a UE1601,1602,1701.

A battery2030may power the platform2000, although in some examples the platform2000may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery2030may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery2030may be a typical lead-acid automotive battery.

In some implementations, the battery2030may be a “smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform2000to track the state of charge (SoCh) of the battery2030. The BMS may be used to monitor other parameters of the battery2030to provide failure predictions, such as the state of health (SoH) and the state of function (SoF) of the battery2030. The BMS may communicate the information of the battery2030to the application circuitry2005or other components of the platform2000. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry2005to directly monitor the voltage of the battery2030or the current flow from the battery2030. The battery parameters may be used to determine actions that the platform2000may perform, such as transmission frequency, network operation, sensing frequency, and the like.

A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery2030. In some examples, the power block XS30may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform2000. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery2030, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry2050includes various input/output (I/O) devices present within, or connected to, the platform2000, and includes one or more user interfaces designed to enable user interaction with the platform2000and/or peripheral component interfaces designed to enable peripheral component interaction with the platform2000. The user interface circuitry2050includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform2000. The output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like. In some embodiments, the sensor circuitry2021may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like). In another example, NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.

Although not shown, the components of platform2000may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a Time-Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus/IX may be a proprietary bus/IX, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I2C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.

FIG.21illustrates example components of baseband circuitry2110and radio front end modules (RFEM)2115in accordance with various embodiments. The baseband circuitry2110corresponds to the baseband circuitry1910and2010ofFIGS.19and20, respectively. The RFEM2115corresponds to the RFEM1915and2015ofFIGS.19and20, respectively. As shown, the RFEMs2115may include Radio Frequency (RF) circuitry2106, front-end module (FEM) circuitry2108, antenna array2111coupled together at least as shown.

The baseband circuitry2110includes circuitry and/or control logic configured to carry out various radio/network protocol and radio control functions that enable communication with one or more radio networks via the RF circuitry2106. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry2110may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry2110may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments. The baseband circuitry2110is configured to process baseband signals received from a receive signal path of the RF circuitry2106and to generate baseband signals for a transmit signal path of the RF circuitry2106. The baseband circuitry2110is configured to interface with application circuitry1905/2005(seeFIGS.19and20) for generation and processing of the baseband signals and for controlling operations of the RF circuitry2106. The baseband circuitry2110may handle various radio control functions.

The aforementioned circuitry and/or control logic of the baseband circuitry2110may include one or more single or multi-core processors. For example, the one or more processors may include a 3G baseband processor2104A, a 4G/LTE baseband processor2104B, a 5G/NR baseband processor2104C, or some other baseband processor(s)2104D for other existing generations, generations in development or to be developed in the future (e.g., sixth generation (6G), etc.). In other embodiments, some or all of the functionality of baseband processors2104A-D may be included in modules stored in the memory2104G and executed via a Central Processing Unit (CPU)2104E. In other embodiments, some or all of the functionality of baseband processors2104A-D may be provided as hardware accelerators (e.g., FPGAs, ASICs, etc.) loaded with the appropriate bit streams or logic blocks stored in respective memory cells. In various embodiments, the memory2104G may store program code of a real-time OS (RTOS), which when executed by the CPU2104E (or other baseband processor), is to cause the CPU2104E (or other baseband processor) to manage resources of the baseband circuitry2110, schedule tasks, etc. Examples of the RTOS may include Operating System Embedded (OSE)™ provided by Enea®, Nucleus RTOS™ provided by Mentor Graphics®, Versatile Real-Time Executive (VRTX) provided by Mentor Graphics®, ThreadX™ provided by Express Logic®, FreeRTOS, REX OS provided by Qualcomm®, OKL4 provided by Open Kernel (OK) Labs®, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuitry2110includes one or more audio digital signal processor(s) (DSP)2104F. The audio DSP(s)2104F include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.

In some embodiments, each of the processors2104A-2104E include respective memory interfaces to send/receive data to/from the memory2104G. The baseband circuitry2110may further include one or more interfaces to communicatively couple to other circuitries/devices, such as an interface to send/receive data to/from memory external to the baseband circuitry2110; an application circuitry interface to send/receive data to/from the application circuitry1905/2005ofFIGS.19-21); an RF circuitry interface to send/receive data to/from RF circuitry2106ofFIG.21; a wireless hardware connectivity interface to send/receive data to/from one or more wireless hardware elements (e.g., Near Field Communication (NFC) components, Bluetooth®/Bluetooth® Low Energy components, Wi-Fi® components, and/or the like); and a power management interface to send/receive power or control signals to/from the PMIC2025.

In alternate embodiments (which may be combined with the above described embodiments), baseband circuitry2110comprises one or more digital baseband systems, which are coupled with one another via an interconnect subsystem and to a CPU subsystem, an audio subsystem, and an interface subsystem. The digital baseband subsystems may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem via another interconnect subsystem. Each of the interconnect subsystems may include a bus system, point-to-point connections, network-on-chip (NOC) structures, and/or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include DSP circuitry, buffer memory, program memory, speech processing accelerator circuitry, data converter circuitry such as analog-to-digital and digital-to-analog converter circuitry, analog circuitry including one or more of amplifiers and filters, and/or other like components. In an aspect of the present disclosure, baseband circuitry2110may include protocol processing circuitry with one or more instances of control circuitry (not shown) to provide control functions for the digital baseband circuitry and/or radio frequency circuitry (e.g., the radio front end modules2115).

Although not shown byFIG.21, in some embodiments, the baseband circuitry2110includes individual processing device(s) to operate one or more wireless communication protocols (e.g., a “multi-protocol baseband processor” or “protocol processing circuitry”) and individual processing device(s) to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuitry operates or implements various protocol layers/entities of one or more wireless communication protocols. In a first example, the protocol processing circuitry may operate LTE protocol entities and/or 5G/NR protocol entities when the baseband circuitry2110and/or RF circuitry2106are part of mmWave communication circuitry or some other suitable cellular communication circuitry. In the first example, the protocol processing circuitry would operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, the protocol processing circuitry may operate one or more IEEE-based protocols when the baseband circuitry2110and/or RF circuitry2106are part of a Wi-Fi communication system. In the second example, the protocol processing circuitry would operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g.,2104G) to store program code and data for operating the protocol functions, as well as one or more processing cores to execute the program code and perform various operations using the data. The baseband circuitry2110may also support radio communications for more than one wireless protocol.

The various hardware elements of the baseband circuitry2110discussed herein may be implemented, for example, as a solder-down substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuitry2110may be suitably combined in a single chip or chipset, or disposed on a same circuit board. In another example, some or all of the constituent components of the baseband circuitry2110and RF circuitry2106may be implemented together such as, for example, a system on a chip (SoC) or System-in-Package (SiP). In another example, some or all of the constituent components of the baseband circuitry2110may be implemented as a separate SoC that is communicatively coupled with and RF circuitry2106(or multiple instances of RF circuitry2106). In yet another example, some or all of the constituent components of the baseband circuitry2110and the application circuitry1905/2005may be implemented together as individual SoCs mounted to a same circuit board (e.g., a “multi-chip package”).

In some embodiments, the baseband circuitry2110may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry2110may support communication with an E-UTRAN or other WMAN, a WLAN, a WPAN. Embodiments in which the baseband circuitry2110is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry2106may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry2106may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry2106may include a receive signal path, which may include circuitry to down-convert RF signals received from the FEM circuitry2108and provide baseband signals to the baseband circuitry2110. RF circuitry2106may also include a transmit signal path, which may include circuitry to up-convert baseband signals provided by the baseband circuitry2110and provide RF output signals to the FEM circuitry2108for transmission.

In some embodiments, the receive signal path of the RF circuitry2106may include mixer circuitry2106a, amplifier circuitry2106band filter circuitry2106c. In some embodiments, the transmit signal path of the RF circuitry2106may include filter circuitry2106cand mixer circuitry2106a. RF circuitry2106may also include synthesizer circuitry2106dfor synthesizing a frequency for use by the mixer circuitry2106aof the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry2106aof the receive signal path may be configured to down-convert RF signals received from the FEM circuitry2108based on the synthesized frequency provided by synthesizer circuitry2106d. The amplifier circuitry2106bmay be configured to amplify the down-converted signals and the filter circuitry2106cmay be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry2110for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry2106aof the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry2106aof the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry2106dto generate RF output signals for the FEM circuitry2108. The baseband signals may be provided by the baseband circuitry2110and may be filtered by filter circuitry2106c.

The synthesizer circuitry2106dmay be configured to synthesize an output frequency for use by the mixer circuitry2106aof the RF circuitry2106based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry2106dmay be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry2110or the application circuitry1905/2005depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry1905/2005.

FEM circuitry2108may include a receive signal path, which may include circuitry configured to operate on RF signals received from antenna array2111, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry2106for further processing. FEM circuitry2108may also include a transmit signal path, which may include circuitry configured to amplify signals for transmission provided by the RF circuitry2106for transmission by one or more of antenna elements of antenna array2111. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry2106, solely in the FEM circuitry2108, or in both the RF circuitry2106and the FEM circuitry2108.

In some embodiments, the FEM circuitry2108may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry2108may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry2108may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry2106). The transmit signal path of the FEM circuitry2108may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry2106), and one or more filters to generate RF signals for subsequent transmission by one or more antenna elements of the antenna array2111.

The antenna array2111comprises one or more antenna elements, each of which is configured convert electrical signals into radio waves to travel through the air and to convert received radio waves into electrical signals. For example, digital baseband signals provided by the baseband circuitry2110is converted into analog RF signals (e.g., modulated waveform) that will be amplified and transmitted via the antenna elements of the antenna array2111including one or more antenna elements (not shown). The antenna elements may be omnidirectional, direction, or a combination thereof. The antenna elements may be formed in a multitude of arranges as are known and/or discussed herein. The antenna array2111may comprise microstrip antennas or printed antennas that are fabricated on the surface of one or more printed circuit boards. The antenna array2111may be formed in as a patch of metal foil (e.g., a patch antenna) in a variety of shapes, and may be coupled with the RF circuitry2106and/or FEM circuitry2108using metal transmission lines or the like.

Processors of the application circuitry1905/2005and processors of the baseband circuitry2110may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry2110, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry1905/2005may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., TCP and UDP layers). As referred to herein, Layer 3 may comprise a RRC layer, described in further detail below. As referred to herein, Layer 2 may comprise a MAC layer, an RLC layer, and a PDCP layer, described in further detail below. As referred to herein, Layer 1 may comprise a PHY layer of a UE/RAN node, described in further detail below.

FIG.22illustrates various protocol functions that may be implemented in a wireless communication device according to various embodiments. In particular,FIG.22includes an arrangement2200showing interconnections between various protocol layers/entities. The following description ofFIG.22is provided for various protocol layers/entities that operate in conjunction with the 5G/NR system standards and LTE system standards, but some or all of the aspects ofFIG.22may be applicable to other wireless communication network systems as well.

The protocol layers of arrangement2200may include one or more of PHY2210, MAC2220, RLC2230, PDCP2240, SDAP2247, RRC2255, and NAS layer2257, in addition to other higher layer functions not illustrated. The protocol layers may include one or more service access points (e.g., items2259,2256,2250,2249,2245,2235,2225, and2215inFIG.22) that may provide communication between two or more protocol layers.

The PHY2210may transmit and receive physical layer signals2205that may be received from or transmitted to one or more other communication devices. The physical layer signals2205may comprise one or more physical channels, such as those discussed herein. The PHY2210may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC2255. The PHY2210may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and MIMO antenna processing. In embodiments, an instance of PHY2210may process requests from and provide indications to an instance of MAC2220via one or more PHY-SAP2215. According to some embodiments, requests and indications communicated via PHY-SAP2215may comprise one or more transport channels.

Instance(s) of MAC2220may process requests from, and provide indications to, an instance of RLC2230via one or more MAC-SAPs2225. These requests and indications communicated via the MAC-SAP2225may comprise one or more logical channels. The MAC2220may perform mapping between the logical channels and transport channels, multiplexing of MAC SDUs from one or more logical channels onto TBs to be delivered to PHY2210via the transport channels, de-multiplexing MAC SDUs to one or more logical channels from TBs delivered from the PHY2210via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through HARQ, and logical channel prioritization.

Instance(s) of RLC2230may process requests from and provide indications to an instance of PDCP2240via one or more radio link control service access points (RLC-SAP)2235. These requests and indications communicated via RLC-SAP2235may comprise one or more RLC channels. The RLC2230may operate in a plurality of modes of operation, including: Transparent Mode™, Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC2230may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC2230may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

Instance(s) of PDCP2240may process requests from and provide indications to instance(s) of RRC2255and/or instance(s) of SDAP2247via one or more packet data convergence protocol service access points (PDCP-SAP)2245. These requests and indications communicated via PDCP-SAP2245may comprise one or more radio bearers. The PDCP2240may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

Instance(s) of SDAP2247may process requests from and provide indications to one or more higher layer protocol entities via one or more SDAP-SAP2249. These requests and indications communicated via SDAP-SAP2249may comprise one or more QoS flows. The SDAP2247may map QoS flows to DRBs, and vice versa, and may also mark QFIs in DL and UL packets. A single SDAP entity2247may be configured for an individual PDU session. In the UL direction, the NG-RAN1610may control the mapping of QoS Flows to DRB(s) in two different ways, reflective mapping or explicit mapping. For reflective mapping, the SDAP2247of a UE1601may monitor the QFIs of the DL packets for each DRB, and may apply the same mapping for packets flowing in the UL direction. For a DRB, the SDAP2247of the UE1601may map the UL packets belonging to the QoS flows(s) corresponding to the QoS flow ID(s) and PDU session observed in the DL packets for that DRB. To enable reflective mapping, the NG-RAN1810may mark DL packets over the Uu interface with a QoS flow ID. The explicit mapping may involve the RRC2255configuring the SDAP2247with an explicit QoS flow to DRB mapping rule, which may be stored and followed by the SDAP2247. In embodiments, the SDAP2247may only be used in NR implementations and may not be used in LTE implementations.

The RRC2255may configure, via one or more management service access points (M-SAP), aspects of one or more protocol layers, which may include one or more instances of PHY2210, MAC2220, RLC2230, PDCP2240and SDAP2247. In embodiments, an instance of RRC2255may process requests from and provide indications to one or more NAS entities2257via one or more RRC-SAPs2256. The main services and functions of the RRC2255may include broadcast of system information (e.g., included in MIBs or SIBs related to the NAS), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE1601and RAN1610(e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. The MIBs and SIBs may comprise one or more IEs, which may each comprise individual data fields or data structures.

The NAS2257may form the highest stratum of the control plane between the UE1601and the AMF1821. The NAS2257may support the mobility of the UEs1601and the session management procedures to establish and maintain IP connectivity between the UE1601and a P-GW in LTE systems.

According to various embodiments, one or more protocol entities of arrangement2200may be implemented in UEs1601, RAN nodes1611, AMF1821in NR implementations or MME1721in LTE implementations, UPF1802in NR implementations or S-GW1722and P-GW1723in LTE implementations, or the like to be used for control plane or user plane communications protocol stack between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of UE1601, gNB1611, AMF1821, etc. may communicate with a respective peer protocol entity that may be implemented in or on another device using the services of respective lower layer protocol entities to perform such communication. In some embodiments, a gNB-CU of the gNB1611may host the RRC2255, SDAP2247, and PDCP2240of the gNB that controls the operation of one or more gNB-DUs, and the gNB-DUs of the gNB1611may each host the RLC2230, MAC2220, and PHY2210of the gNB1611.

In a first example, a control plane protocol stack may comprise, in order from highest layer to lowest layer, NAS2257, RRC2255, PDCP2240, RLC2230, MAC2220, and PHY2210. In this example, upper layers2260may be built on top of the NAS2257, which includes an IP layer2261, an SCTP2262, and an application layer signaling protocol (AP)2263.

In NR implementations, the AP2263may be an NG application protocol layer (NGAP or NG-AP)2263for the NG interface1613defined between the NG-RAN node1611and the AMF1821, or the AP2263may be an Xn application protocol layer (XnAP or Xn-AP)2263for the Xn interface1612that is defined between two or more RAN nodes1611.

The NG-AP2263may support the functions of the NG interface1613and may comprise Elementary Procedures (EPs). An NG-AP EP may be a unit of interaction between the NG-RAN node1611and the AMF1821. The NG-AP2263services may comprise two groups: UE-associated services (e.g., services related to a UE1601,1602) and non-UE-associated services (e.g., services related to the whole NG interface instance between the NG-RAN node1611and AMF1821). These services may include functions including, but not limited to: a paging function for the sending of paging requests to NG-RAN nodes1611involved in a particular paging area; a UE context management function for allowing the AMF1821to establish, modify, and/or release a UE context in the AMF1821and the NG-RAN node1611; a mobility function for UEs1601in ECM-CONNECTED mode for intra-system HOs to support mobility within NG-RAN and inter-system HOs to support mobility from/to EPS systems; a NAS Signaling Transport function for transporting or rerouting NAS messages between UE1601and AMF1821; a NAS node selection function for determining an association between the AMF1821and the UE1601; NG interface management function(s) for setting up the NG interface and monitoring for errors over the NG interface; a warning message transmission function for providing means to transfer warning messages via NG interface or cancel ongoing broadcast of warning messages; a Configuration Transfer function for requesting and transferring of RAN configuration information (e.g., SON information, performance measurement (PM) data, etc.) between two RAN nodes1611via CN1620; and/or other like functions.

The XnAP2263may support the functions of the Xn interface1612and may comprise XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may comprise procedures used to handle UE mobility within the NG RAN1611(or E-UTRAN1710), such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, dual connectivity related procedures, and the like. The XnAP global procedures may comprise procedures that are not related to a specific UE1601, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, and the like.

In LTE implementations, the AP2263may be an S1 Application Protocol layer (S1-AP)2263for the S1 interface1613defined between an E-UTRAN node1611and an MME, or the AP2263may be an X2 application protocol layer (X2AP or X2-AP)2263for the X2 interface1612that is defined between two or more E-UTRAN nodes1611.

The S1 Application Protocol layer (S1-AP)2263may support the functions of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may comprise S1-AP EPs. An S1-AP EP may be a unit of interaction between the E-UTRAN node1611and an MME1721within an LTE CN1620. The S1-AP2263services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

The X2AP2263may support the functions of the X2 interface1612and may comprise X2AP basic mobility procedures and X2AP global procedures. The X2AP basic mobility procedures may comprise procedures used to handle UE mobility within the E-UTRAN1620, such as handover preparation and cancellation procedures, SN Status Transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, dual connectivity related procedures, and the like. The X2AP global procedures may comprise procedures that are not related to a specific UE1601, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, cell activation procedures, and the like.

The SCTP layer (alternatively referred to as the SCTP/IP layer)2262may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). The SCTP2262may ensure reliable delivery of signaling messages between the RAN node1611and the AMF1821/MME1721based, in part, on the IP protocol, supported by the IP2261. The Internet Protocol layer (IP)2261may be used to perform packet addressing and routing functionality. In some implementations the IP layer2261may use point-to-point transmission to deliver and convey PDUs. In this regard, the RAN node1611may comprise L2 and L1 layer communication links (e.g., wired or wireless) with the MME/AMF to exchange information.

In a second example, a user plane protocol stack may comprise, in order from highest layer to lowest layer, SDAP2247, PDCP2240, RLC2230, MAC2220, and PHY2210. The user plane protocol stack may be used for communication between the UE1601, the RAN node1611, and UPF1802in NR implementations or an S-GW1722and P-GW1723in LTE implementations. In this example, upper layers2251may be built on top of the SDAP2247, and may include a user datagram protocol (UDP) and IP security layer (UDP/IP)2252, a General Packet Radio Service (GPRS) Tunneling Protocol for the user plane layer (GTP-U)2253, and a User Plane PDU layer (UP PDU)2263.

The transport network layer2254(also referred to as a “transport layer”) may be built on IP transport, and the GTP-U2253may be used on top of the UDP/IP layer2252(comprising a UDP layer and IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also referred to as the “Internet layer”) may be used to perform packet addressing and routing functionality. The IP layer may assign IP addresses to user data packets in any of IPv4, IPv6, or PPP formats, for example.

The GTP-U2253may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP/IP2252may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node1611and the S-GW1722may utilize an S1-U interface to exchange user plane data via a protocol stack comprising an L1 layer (e.g., PHY2210), an L2 layer (e.g., MAC2220, RLC2230, PDCP2240, and/or SDAP2247), the UDP/IP layer2252, and the GTP-U2253. The S-GW1722and the P-GW1723may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising an L1 layer, an L2 layer, the UDP/IP layer2252, and the GTP-U2253. As discussed previously, NAS protocols may support the mobility of the UE1601and the session management procedures to establish and maintain IP connectivity between the UE1601and the P-GW1723.

Moreover, although not shown byFIG.22, an application layer may be present above the AP2263and/or the transport network layer2254. The application layer may be a layer in which a user of the UE1601, RAN node1611, or other network element interacts with software applications being executed, for example, by application circuitry1905or application circuitry2005, respectively. The application layer may also provide one or more interfaces for software applications to interact with communications systems of the UE1601or RAN node1611, such as the baseband circuitry2110. In some implementations the IP layer and/or the application layer may provide the same or similar functionality as layers 5-7, or portions thereof, of the Open Systems Interconnection (OSI) model (e.g., OSI Layer 7—the application layer, OSI Layer 6—the presentation layer, and OSI Layer 5—the session layer).

FIG.23illustrates components of a core network in accordance with various embodiments. The components of the CN1720may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In embodiments, the components of CN1820may be implemented in a same or similar manner as discussed herein with regard to the components of CN1720. In some embodiments, NFV is utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN1720may be referred to as a network slice2301, and individual logical instantiations of the CN1720may provide specific network capabilities and network characteristics. A logical instantiation of a portion of the CN1720may be referred to as a network sub-slice2302(e.g., the network sub-slice2302is shown to include the P-GW1723and the PCRF1726).

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. A network instance may refer to information identifying a domain, which may be used for traffic detection and routing in case of different IP domains or overlapping IP addresses. A network slice instance may refer to a set of network functions (NFs) instances and the resources (e.g., compute, storage, and networking resources) required to deploy the network slice.

With respect to 5G systems (see, e.g.,FIG.18), a network slice always comprises a RAN part and a CN part. The support of network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. The network can realize the different network slices by scheduling and also by providing different L1/L2 configurations. The UE1801provides assistance information for network slice selection in an appropriate RRC message, if it has been provided by NAS. While the network can support large number of slices, the UE need not support more than 8 slices simultaneously.

A network slice may include the CN1820control plane and user plane NFs, NG-RANs1810in a serving PLMN, and a N3IWF functions in the serving PLMN. Individual network slices may have different S-NSSAI and/or may have different SSTs. NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by an S-NSSAI. Network slices may differ for supported features and network functions optimizations, and/or multiple network slice instances may deliver the same service/features but for different groups of UEs1801(e.g., enterprise users). For example, individual network slices may deliver different committed service(s) and/or may be dedicated to a particular customer or enterprise. In this example, each network slice may have different S-NSSAIs with the same SST but with different slice differentiators. Additionally, a single UE may be served with one or more network slice instances simultaneously via a 5G AN and associated with eight different S-NSSAIs. Moreover, an AMF1821instance serving an individual UE1801may belong to each of the network slice instances serving that UE.

Network Slicing in the NG-RAN1810involves RAN slice awareness. RAN slice awareness includes differentiated handling of traffic for different network slices, which have been pre-configured. Slice awareness in the NG-RAN1810is introduced at the PDU session level by indicating the S-NSSAI corresponding to a PDU session in all signaling that includes PDU session resource information. How the NG-RAN1810supports the slice enabling in terms of NG-RAN functions (e.g., the set of network functions that comprise each slice) is implementation dependent. The NG-RAN1810selects the RAN part of the network slice using assistance information provided by the UE1801or the 5GC1820, which unambiguously identifies one or more of the pre-configured network slices in the PLMN. The NG-RAN1810also supports resource management and policy enforcement between slices as per SLAs. A single NG-RAN node may support multiple slices, and the NG-RAN1810may also apply an appropriate RRM policy for the SLA in place to each supported slice. The NG-RAN1810may also support QoS differentiation within a slice.

The NG-RAN1810may also use the UE assistance information for the selection of an AMF1821during an initial attach, if available. The NG-RAN1810uses the assistance information for routing the initial NAS to an AMF1821. If the NG-RAN1810is unable to select an AMF1821using the assistance information, or the UE1801does not provide any such information, the NG-RAN1810sends the NAS signaling to a default AMF1821, which may be among a pool of AMFs1821. For subsequent accesses, the UE1801provides a temp ID, which is assigned to the UE1801by the 5GC1820, to enable the NG-RAN1810to route the NAS message to the appropriate AMF1821as long as the temp ID is valid. The NG-RAN1810is aware of, and can reach, the AMF1821that is associated with the temp ID. Otherwise, the method for initial attach applies.

The NG-RAN1810supports resource isolation between slices. NG-RAN1810resource isolation may be achieved by means of RRM policies and protection mechanisms that should avoid that shortage of shared resources if one slice breaks the service level agreement for another slice. In some implementations, it is possible to fully dedicate NG-RAN1810resources to a certain slice. How NG-RAN1810supports resource isolation is implementation dependent.

Some slices may be available only in part of the network. Awareness in the NG-RAN1810of the slices supported in the cells of its neighbors may be beneficial for inter-frequency mobility in connected mode. The slice availability may not change within the UE's registration area. The NG-RAN1810and the 5GC1820are responsible to handle a service request for a slice that may or may not be available in a given area. Admission or rejection of access to a slice may depend on factors such as support for the slice, availability of resources, support of the requested service by NG-RAN1810.

The UE1801may be associated with multiple network slices simultaneously. In case the UE1801is associated with multiple slices simultaneously, only one signaling connection is maintained, and for intra-frequency cell reselection, the UE1801tries to camp on the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency on which the UE1801camps. The 5GC1820is to validate that the UE1801has the rights to access a network slice. Prior to receiving an Initial Context Setup Request message, the NG-RAN1810may be allowed to apply some provisional/local policies, based on awareness of a particular slice that the UE1801is requesting to access. During the initial context setup, the NG-RAN1810is informed of the slice for which resources are being requested.

NFV architectures and infrastructures may be used to virtualize one or more NFs, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

FIG.24is a block diagram illustrating components, according to some example embodiments, of a system2400to support NFV. The system2400is illustrated as including a VIM2402, an NFVI2404, an VNFM2406, VNFs2408, an EM2410, an NFVO2412, and a NM2414.

The VIM2402manages the resources of the NFVI2404. The NFVI2404can include physical or virtual resources and applications (including hypervisors) used to execute the system2400. The VIM2402may manage the life cycle of virtual resources with the NFVI2404(e.g., creation, maintenance, and tear down of VMs associated with one or more physical resources), track VM instances, track performance, fault and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

The VNFM2406may manage the VNFs2408. The VNFs2408may be used to execute EPC components/functions. The VNFM2406may manage the life cycle of the VNFs2408and track performance, fault and security of the virtual aspects of VNFs2408. The EM2410may track the performance, fault and security of the functional aspects of VNFs2408. The tracking data from the VNFM2406and the EM2410may comprise, for example, PM data used by the VIM2402or the NFVI2404. Both the VNFM2406and the EM2410can scale up/down the quantity of VNFs of the system2400.

The NFVO2412may coordinate, authorize, release and engage resources of the NFVI2404in order to provide the requested service (e.g., to execute an EPC function, component, or slice). The NM2414may provide a package of end-user functions with the responsibility for the management of a network, which may include network elements with VNFs, non-virtualized network functions, or both (management of the VNFs may occur via the EM2410).

FIG.25is 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,FIG.25shows a diagrammatic representation of hardware resources2500including one or more processors (or processor cores)2510, one or more memory/storage devices2520, and one or more communication resources2530, each of which may be communicatively coupled via a bus2540. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor2502may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources2500.

The processors2510may include, for example, a processor2512and a processor2514. The processor(s)2510may 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 radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The communication resources2530may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices2504or one or more databases2506via a network2508. For example, the communication resources2530may include wired communication components (e.g., for coupling via USB), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions2550may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors2510to perform any one or more of the methodologies discussed herein. The instructions2550may reside, completely or partially, within at least one of the processors2510(e.g., within the processor's cache memory), the memory/storage devices2520, or any suitable combination thereof. Furthermore, any portion of the instructions2550may be transferred to the hardware resources2500from any combination of the peripheral devices2504or the databases2506. Accordingly, the memory of processors2510, the memory/storage devices2520, the peripheral devices2504, and the databases2506are examples of computer-readable and machine-readable media.

FIG.26illustrates a flow diagram of a UAS service, according to some embodiments. For example,FIG.26includes a UAS services method2600including identifying or causing to identify a received signal from another UE, according to step2602. Method2600also includes processing or causing to process the signal, according to step2604. Moreover, method2600also includes determining or causing to determine another signal, according to step2606. Additionally, method2600may further include transmitting or causing to transmit the determined other signal to the other UE, wherein the received signal and transmitted signal uses a 3GPP network and wherein the UE and the other UE are part of the UAS system, according to step2608.

FIG.27illustrates an unmanned aircraft traffic management method2700for facilitating Unmanned Aerial System (UAS) services over evolved packet systems. According to some embodiments, method2700may include receiving a registration request from each of an unmanned aerial vehicle (UAV) and a UAV controller to establish an Unmanned Aerial System (UAS), each registration request including an application layer registration through a Unmanned Aircraft Traffic Management (UTM) application function (AF), in which an IP address of the server is provided, as illustrated in step2702. Method2700may further include initiating a UAS Operation Service Request Procedure via a network exposure function (NEF) to obtain results of a UAS operation service authorization from each of the UAV and the UAV controller, as illustrated in step2704. According to some embodiments, method2700may further include associating the UAV and the UAV controller to operate as the UAS in response to obtaining the results of the UAS operation service authorization from each of the UAV and the UAV controller, as illustrated in step2706. Additionally, method2700may further include transmitting a UAS operation status update procedure to the UAV and the UAV controller, the update procedure including UAS association information, a UAS policy update, and initiation of a UAS operation, as illustrated in step2708.

According to other embodiments not illustrated inFIG.27, method2700may further include initiating an AF session setup procedure including a required quality of service (QoS) to manage IP data flows for a UTM session between the UAV and the server, and command and control (C2) session between the UAV and the UAV controller. Additionally, method2700may also include assigning subscription rights to user equipments (UEs) associated with each of the UAV and the UAV controller. According to some aspects, the subscription rights may include a subscription for a UE operating the UAV in the UAS, a subscription of a UE operating the UAV controller in the UAS, a subscription for UAS operation using indirect communication, or a subscription for UAS operation using network navigated C2.

According to some embodiments, method2700may further include providing, to the UE associated with the UAV controller, authorization for the UAS operation enabling controller C2 communication, including a list of public land mobile networks (PLMNs) for which the UAV is authorized, a list of application identifiers per PLMN, a list of allowed traffic types per application identifier, and a UAS-data network name (DNN).

According to some embodiments, method2700may further include providing, to the UE associated with the UAV, authorization for the UAS operation enabling network C2 communication with flight plan, including a list of PLMNs for which the UAV is authorized, a list of application identifiers per PLMN, a list of allowed traffic types per application identifier, and the UAS-DNN.

According to some embodiments, method2700may further include transmitting, to the NEF, a UAS operation service request message including a server identifier, generic public subscription identifier, an external group identifier of the UAV and UAV controller, external application identifiers, and a UAS operation authorization for each application identifier. According to some aspects, the UAS operation authorization may indicate that the UAS operation policy is to be created in a network of an operator when successfully authorized. According to some other aspects, the NEF may request the UAS operation authorization from a policy control function (PCF).

According to some embodiments, method2700may further include receiving, from the NEF, the UAS operation authorization status for each application identifier, and a cause for authorization or denial of authorization for each application identifier.

Example Procedures

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, ofFIGS.16-25, or some other Fig. herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted inFIG.26as described herein. For example, the process may include identifying or causing to identify a received signal from another UE. The process may further include processing or causing to process the signal. The process may further include determining or causing to determine another signal. The process may further include transmitting or causing to transmit the determined other signal to the other UE, wherein the received signal and transmitted signal uses a 3GPP network and wherein the UE and the other UE are part of a UAS system.

EXAMPLES

Example 1 may include a UE apparatus comprising: means for identifying or causing to identify a received signal from another UE; means for processing or causing to process the signal; means for determining or causing to determine another signal; means for transmitting or causing to transmit the determined other signal to the other UE; wherein the received signal and transmitted signal uses a 3GPP network; and wherein the UE and the other UE are part of a UAS system.

Example 2 may include the subject matter of example 1, or of any other example herein, wherein the UE and the other UE communicate via respective unicast connections to the 3GPP network via same or different RAN node in the same or different PLMN.

Example 3 may include the subject matter of example 2, or of any other example herein, wherein the UE and the other UE establish respective unicast C2 communication links to the 3GPP network and communicate via the 3GPP network.

Example 4 may include the subject matter of example 1, or of any other example herein, wherein the transmission or reception is facilitated by a cellular based UAS traffic management (C-UTM) function.

Example 5 may include the subject matter of example 4, or of any other example herein, wherein the C-UTM function exists in the control plane.

Example 6 may include the subject matter of example 4, or of any other example herein, wherein the C-UTM function is supported in EPC architecture or the 5GS architecture.

Example 7 may include the subject matter of example 6, or of any other example herein, wherein the C-UTM function interfaces with SCEF.

Example 8 may include the subject matter of example 7, or of any other example herein, wherein the SCEF exposes network capabilities requested by SCS/AS with UTM-Application server over T8.

Example 9 may include the subject matter of example 6, or of any other example herein, wherein a UTM-AF interfaces with C-UTM over N33.

Example 10 may include the subject matter of example 4, or of any other example herein, wherein the C-UTM function includes authorization information for the UE and for the other UE for UAS operation.

Example 11 may include the subject matter of example 1, or of any other example herein, wherein the UE is pre-configured with UAS operation authorization parameters.

Example 12 may include the subject matter of example 1, or of any other example herein, further including means for registering or causing to register the UE to the 5GC with indications to enable UAS operation service if the UE has corresponding UAS subscriptions.

Example 13 may include the subject matter of example 1, or of any other example herein, further comprising means for establishing or causing to establish a PDU session for a specific UAS-DNN.

Example 14 may include the subject matter of example 1, or of any other example herein, wherein all or part of the UE is a UAV and all or part of the other UE is a UAV controller.

Example 15 include the subject matter of example 1, or of any other example herein, wherein all or part of the other UE is a UAV and all or part of the UE is a UAV controller.

Example 16 may be a method of UAS operation service authorization for a UE of the UAV or UAV controller in 5GS.

Example 17 may include the method of example 16, or of any other example herein, whereby the UAS operation service authorization is initiated by the AF by sending a Nnef_UAS_Operation_Service Request (AF Identifier, Generic Public Subscription Identifier (GPSI)/External Group Identifier of the UAV/UAV controller, external Application Identifiers, UAS operation authorization for each Application Identifier) message to the NEF.

Example 18 may include the method of example 17, or of any other example herein, whereby the UAS operation authorization indicates that the UAS operation policy is to be created in the operator's network if successfully authorized, e.g. UAS operation mode, including via Network based C2 (as shown inFIG.1) or via Network navigated C2 (as shown inFIG.2), operation location, requested operation start time, flight duration, flight routes, etc., for the UAV/UAV controller.

Example 19 may include the method of example 18, or of any other example herein, whereby the AF is authorized by the NEF to request UAS operation service authorization.

Example 20 may include the method of example 19, or of, any other example herein, whereby if the authorization is not granted, the NEF replies to the AF with a Result value indicating that the authorization failed.

Example 21 include the method of example 19, or of any other example herein, whereby if the authorization is granted, the NEF allocates a Transaction Reference ID to identify the follow up messages regarding to the request.

Example 22 may include the method of examples 20 or 21, or of any other example herein, whereby the NEF sends a Ncutm_UAS Operation_Authorization Request message (Application Identifier(s), one or more sets of UAS operation information for each Application Identifier, SUPI) to the C-UTMF/PCF.

Example 23 may include the method of example 22, or of any other example herein, whereby the NEF may query for the translation of GPSI/External Group Identifier of the UAV/UAV controller to Subscription Permanent Identifier (SUPI) of the UE.

Example 24 may include the method of example 23, or of any other example herein, whereby the C-UTM/PCF function determines whether the request is allowed.

Example 25 may include the method of example 24, or of any other example herein, whereby if UAS operation authorization is done successfully, the C-UTM/PCF continues to create the list of UAS operation policies into the C-UTM function based on the operator's configured policies for each requested UAS operation per application ID and respond to NEF.

Example 26 may include the method of example 25, or of any other example herein, whereby the C-UTM function sends Ncutm_UAS Operation_Authorization Request message (Application Identifier(s), Results) message to the NEF and indicates the Results.

Example 27 may include the method of example 26, or of any other example herein, whereby if any of the services authorization fails, cause is provided per Application ID, e.g. service suspend, service expiration, service unavailable.

Example 28 may include the method of example 27, or of any other example herein, whereby the NEF sends a Unef_UAS Operation_Service Response (Transaction Reference ID, Results) message to the UTM-AF to provide the feedback of the result for Unef_UAS Operation_Service Request.

Example 29 may include the method of example 28, or of any other example herein, whereby the Transaction Reference ID is used by the AF to provide the follow up information regarding to the request for the UAS operation of the UAV/UAV controller. Example 30 may be a method of UAS operation status update for a UE of the UAV or UAV controller in 5GS.

Example 31 include the method of example 30, or of any other example herein, whereby the UAS operation status update request is sent by UTM-AF to notify the successful association of a UAS by sending a Nnef_UAS_Operation_Status_Update Request (AF Identifier, Transaction Reference ID, External identifiers/External Group identifiers of the UAV/UAV controller, UAS operation Status for each Application Identifier, UAS_ID) message to the NEF.

Example 32 may include the method of example 31, or of any other example herein, whereby the UAS operation status can indicate the enabled UAS operation parameters per Application identifier and indicates the corresponding UAS_ID.

Example 33 may include the method of example 32, or of any other example herein, whereby the UAS_ID is allocated by the UTM-AF to identify the association between a UAV and a UAV controller in which the related UAS operation for the UAS is associated to the same UAS-ID.

Example 34 may include the method of example 33, or of any other example herein, whereby the UAS operation parameters may include: the allowed application IDs for the UAS operation, UAS operation mode (e.g. indirect C2, direct C2, network navigated C2), IP addresses of available UTM application servers, allowed geographical areas, allowed operation time, allowed operation duration, etc.

Example 35 may include the method of example 34, or of any other example herein, whereby NEF checks the AF authorization of the request for UAS operation status update if the Transaction Reference ID is expired.

Example 36 may include the method of example 35, or of any other example herein, whereby NEF sends the Ncutm_UAS Status Update request (SUPI, UAS operation Status for each Application Identifier, UAS_ID) message to the C-UTM/PCF.

Example 37 may include the method of example 36, or of any other example herein, whereby C-UTM/PCF function updates the UAS operation status including the policies per application identifier and the associated UAS_ID.

Example 38 may include the method of example 37, or of any other example herein, whereby the C-UTM/PCF function returns the confirmation of the status update to the NEF by sending Ncutm_UAS Operation Update response (UAS_ID, SUPI) message.

Example 39 may include the method of example 38, or of any other example herein, whereby the NEF returns the Nnef_UAS_Operation_Status_Update response (Transaction Reference ID) message to the AF.

Example 40 may include a UE apparatus to: identify or cause to identify a received signal from another UE; process or cause to process the signal; determine or cause to determine another signal; transmit or cause to transmit the determined other signal to the other UE; wherein the received signal and transmitted signal uses a 3GPP network; and wherein the UE and the other UE are part of a UAS system.

Example 41 may include the subject matter of example 40, or of any other example herein, wherein the UE and the other UE communicate via respective unicast connections to the 3GPP network via same or different RAN node in the same or different PLMN.

Example 42 may include the subject matter of example 41, or of any other example herein, wherein the UE and the other UE establish respective unicast C2 communication links to the 3GPP network and communicate via the 3GPP network.

Example 43 may include the subject matter of example 40, or of any other example herein, wherein the transmission or reception is facilitated by a cellular based UAS traffic management (C-UTM) function.

Example 44 may include the subject matter of example 43, or of any other example herein, wherein the C-UTM function exists in the control plane.

Example 45 may include the subject matter of example 43, or of any other example herein, wherein the C-UTM function is supported in EPC architecture or the 5GS architecture.

Example 46 may include the subject matter of example 45, or of any other example herein, wherein the C-UTM function interfaces with SCEF.

Example 47 may include the subject matter of example 46, or of any other example herein, wherein the SCEF exposes network capabilities requested by SC S/AS with UTM-Application server over T8.

Example 48 may include the subject matter of example 45, or of any other example herein, wherein a UTM-AF interfaces with C-UTM over N33.

Example 49 may include the subject matter of example 43, or of any other example herein, wherein the C-UTM function includes authorization information for the UE and for the other UE for UAS operation.

Example 50 may include the subject matter of example 40, or of any other example herein, wherein the UE is pre-configured with UAS operation authorization parameters.

Example 51 may include the subject matter of example 40, or of any other example herein, further including register or cause to register the UE to the 5GC with indications to enable UAS operation service if the UE has corresponding UAS subscriptions.

Example 52 may include the subject matter of example 40, or of any other example herein, further comprising establish or cause to establish a PDU session for a specific UAS-DNN.

Example 53 may include the subject matter of example 40, or of any other example herein, wherein all or part of the UE is a UAV and all or part of the other UE is a UAV controller.

Example 54 include the subject matter of example 40, or of any other example herein, wherein all or part of the other UE is a UAV and all or part of the UE is a UAV controller.

Example 55 may include a method for implementing a UE comprising: identifying or causing to identify a received signal from another UE; processing or causing to process the signal; determining or causing to determine another signal; transmitting or causing to transmit the determined other signal to the other UE; wherein the received signal and transmitted signal uses a 3GPP network; and wherein the UE and the other UE are part of a UAS system.

Example 56 may include the subject matter of example 55, or of any other example herein, wherein the UE and the other UE communicate via respective unicast connections to the 3GPP network via same or different RAN node in the same or different PLMN.

Example 57 may include the subject matter of example 56, or of any other example herein, wherein the UE and the other UE establish respective unicast C2 communication links to the 3GPP network and communicate via the 3GPP network.

Example 58 may include the subject matter of example 55, or of any other example herein, wherein the transmission or reception is facilitated by a cellular based UAS traffic management (C-UTM) function.

Example 59 may include the subject matter of example 58, or of any other example herein, wherein the C-UTM function exists in the control plane.

Example 60 may include the subject matter of example 58, or of any other example herein, wherein the C-UTM function is supported in EPC architecture or the 5GS architecture.

Example 61 may include the subject matter of example 60, or of any other example herein, wherein the C-UTM function interfaces with SCEF.

Example 62 may include the subject matter of example 61, or of any other example herein, wherein the SCEF exposes network capabilities requested by SC S/AS with UTM-Application server over T8.

Example 63 may include the subject matter of example 60, or of any other example herein, wherein a UTM-AF interfaces with C-UTM over N33.

Example 64 may include the subject matter of example 58, or of any other example herein, wherein the C-UTM function includes authorization information for the UE and for the other UE for UAS operation.

Example 65 may include the subject matter of example 55, or of any other example herein, wherein the UE is pre-configured with UAS operation authorization parameters.

Example 66 may include the subject matter of example 55, or of any other example herein, further including registering or causing to register the UE to the 5GC with indications to enable UAS operation service if the UE has corresponding UAS subscriptions.

Example 67 may include the subject matter of example 55, or of any other example herein, further comprising establishing or causing to establish a PDU session for a specific UAS-DNN.

Example 68 may include the subject matter of example 55, or of any other example herein, wherein all or part of the UE is a UAV and all or part of the other UE is a UAV controller.

Example 69 include the subject matter of example 55, or of any other example herein, wherein all or part of the other UE is a UAV and all or part of the UE is a UAV controller.

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

Example 72 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-69, or any other method or process described herein.

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

Example 74 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-69, or portions thereof.

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

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

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

Example 79 may include a device for providing wireless communication as shown and described herein.

Abbreviations

For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.3GPP Third Generation Partnership Project4G Fourth Generation5G Fifth Generation5GC 5G Core networkACK AcknowledgementAF Application FunctionAM Acknowledged ModeAMBR Aggregate Maximum Bit RateAMF Access and Mobility Management FunctionAN Access NetworkANR Automatic Neighbour RelationAP Application Protocol, Antenna Port, Access PointAPI Application Programming InterfaceAPN Access Point NameARP Allocation and Retention PriorityARQ Automatic Repeat RequestAS Access StratumASN.1 Abstract Syntax Notation OneAUSF Authentication Server FunctionAWGN Additive White Gaussian NoiseBCH Broadcast ChannelBER Bit Error RatioBFD Beam Failure DetectionBLER Block Error RateBPSK Binary Phase Shift KeyingBRAS Broadband Remote Access ServerBSS Business Support SystemBS Base StationBSR Buffer Status ReportBW BandwidthBWP Bandwidth PartC-RNTI Cell Radio Network Temporary IdentityCA Carrier Aggregation, Certification AuthorityCAPEX CAPital EXpenditureCBRA Contention Based Random AccessCC Component Carrier, Country Code, Cryptographic ChecksumCCA Clear Channel AssessmentCCE Control Channel ElementCCCH Common Control ChannelCE Coverage EnhancementCDM Content Delivery NetworkCDMA Code-Division Multiple AccessCFRA Contention Free Random AccessCG Cell GroupCI Cell IdentityCID Cell-ID (e.g., positioning method)CIM Common Information ModelCIR Carrier to Interference RatioCK Cipher KeyCM Connection Management, Conditional MandatoryCMAS Commercial Mobile Alert ServiceCMD CommandCMS Cloud Management SystemCO Conditional OptionalCoMP Coordinated Multi-PointCORESET Control Resource SetCOTS Commercial Off-The-ShelfCP Control Plane, Cyclic Prefix, Connection PointCPD Connection Point DescriptorCPE Customer Premise EquipmentCPICH Common Pilot ChannelCQI Channel Quality IndicatorCPU CSI processing unit, Central Processing UnitC/R Command/Response field bitCRAN Cloud Radio Access Network, Cloud RANCRB Common Resource BlockCRC Cyclic Redundancy CheckCRI Channel-State Information Resource Indicator, CSI-RS Resource IndicatorC-RNTI Cell RNTICS Circuit SwitchedCSAR Cloud Service ArchiveCSI Channel-State InformationCSI-IM CSI Interference MeasurementCSI-RS CSI Reference SignalCSI-RSRP CSI reference signal received powerCSI-RSRQ CSI reference signal received qualityCSI-SINR CSI signal-to-noise and interference ratioCSMA Carrier Sense Multiple AccessCSMA/CA CSMA with collision avoidanceCSS Common Search Space, Cell-specific Search SpaceCTS Clear-to-SendCW CodewordCWS Contention Window SizeD2D Device-to-DeviceDC Dual Connectivity, Direct CurrentDCI Downlink Control InformationDF Deployment FlavourDL DownlinkDMTF Distributed Management Task ForceDPDK Data Plane Development KitDM-RS, DMRS Demodulation Reference SignalDN Data networkDRB Data Radio BearerDRS Discovery Reference SignalDRX Discontinuous ReceptionDSL Domain Specific Language. Digital Subscriber LineDSLAM DSL Access MultiplexerDwPTS Downlink Pilot Time SlotE-LAN Ethernet Local Area NetworkE2E End-to-EndECCA extended clear channel assessment, extended CCAECCE Enhanced Control Channel Element, Enhanced CCEED Energy DetectionEDGE Enhanced Datarates for GSM Evolution (GSM Evolution)EGMF Exposure Governance Management FunctionEGPRS Enhanced GPRSEIR Equipment Identity RegistereLAA enhanced Licensed Assisted Access, enhanced LAAEM Element ManagereMBB Enhanced Mobile BroadbandEMS Element Management SystemeNB evolved NodeB, E-UTRAN Node BEN-DC E-UTRA-NR Dual ConnectivityEPC Evolved Packet CoreEPDCCH enhanced PDCCH, enhanced Physical Downlink Control CannelEPRE Energy per resource elementEPS Evolved Packet SystemEREG enhanced REG, enhanced resource element groupsETSI European Telecommunications Standards InstituteETWS Earthquake and Tsunami Warning SystemeUICC embedded UICC, embedded Universal Integrated Circuit CardE-UTRA Evolved UTRAE-UTRAN Evolved UTRANEV2X Enhanced V2XFlAP F1 Application ProtocolF1-C F1 Control plane interfaceF1-U F1 User plane interfaceFACCH Fast Associated Control CHannelFACCH/F Fast Associated Control Channel/Full rateFACCH/H Fast Associated Control Channel/Half rateFACH Forward Access ChannelFAUSCH Fast Uplink Signalling ChannelFB Functional BlockFBI Feedback InformationFCC Federal Communications CommissionFCCH Frequency Correction CHannelFDD Frequency Division DuplexFDM Frequency Division MultiplexFDMA Frequency Division Multiple AccessFE Front EndFEC Forward Error CorrectionFFS For Further StudyFFT Fast Fourier TransformationfeLAA further enhanced Licensed Assisted Access, further enhanced LAAFN Frame NumberFPGA Field-Programmable Gate ArrayFR Frequency RangeG-RNTI GERAN Radio Network Temporary IdentityGERAN GSM EDGE RAN, GSM EDGE Radio Access NetworkGGSN Gateway GPRS Support NodeGLONASS GLObal′naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System)gNB Next Generation NodeBgNB-CU gNB-centralized unit, Next Generation NodeB centralized unitgNB-DU gNB-distributed unit, Next Generation NodeB distributed unitGNSS Global Navigation Satellite SystemGPRS General Packet Radio ServiceGSM Global System for Mobile Communications, Groupe SpecialMobileGTP GPRS Tunneling ProtocolGTP-U GPRS Tunnelling Protocol for User PlaneGTS Go To Sleep Signal (related to WUS)GUMMEI Globally Unique MME IdentifierGUTI Globally Unique Temporary UE IdentityHARQ Hybrid ARQ, Hybrid Automatic Repeat RequestHANDO, HO HandoverHFN HyperFrame NumberHHO Hard HandoverHLR Home Location RegisterHN Home NetworkHO HandoverHPLMN Home Public Land Mobile NetworkHSDPA High Speed Downlink Packet AccessHSN Hopping Sequence NumberHSPA High Speed Packet AccessHSS Home Subscriber ServerHSUPA High Speed Uplink Packet AccessHTTP Hyper Text Transfer ProtocolHTTPS Hyper Text Transfer Protocol Secure (https is http/1.1 over SSL, i.e. port 443)I-Block Information BlockICCID Integrated Circuit Card IdentificationICIC Inter-Cell Interference CoordinationID Identity, identifierIDFT Inverse Discrete Fourier TransformIE Information elementIBE In-Band EmissionIEEE Institute of Electrical and Electronics EngineersIEI Information Element IdentifierIEIDL Information Element Identifier Data LengthIETF Internet Engineering Task ForceIF InfrastructureIM Interference Measurement, Intermodulation, IP MultimediaIMC IMS CredentialsIMEI International Mobile Equipment IdentityIMGI International mobile group identityIMPI IP Multimedia Private IdentityIMPU IP Multimedia PUblic identityIMS IP Multimedia SubsystemIMSI International Mobile Subscriber IdentityIoT Internet of ThingsIP Internet ProtocolIpsec IP Security, Internet Protocol SecurityIP-CAN IP-Connectivity Access NetworkIP-M IP MulticastIPv4 Internet Protocol Version 4IPv6 Internet Protocol Version 6IR InfraredIS In SyncIRP Integration Reference PointISDN Integrated Services Digital NetworkISIM IM Services Identity ModuleISO International Organisation for StandardisationISP Internet Service ProviderIWF Interworking-FunctionI-WLAN Interworking WLANK Constraint length of the convolutional code, USIM Individual keykB Kilobyte (1000 bytes)kbps kilo-bits per secondKc Ciphering keyKi Individual subscriber authentication keyKPI Key Performance IndicatorKQI Key Quality IndicatorKSI Key Set Identifierksps kilo-symbols per secondKVM Kernel Virtual MachineL1 Layer 1 (physical layer)L1-RSRP Layer 1 reference signal received powerL2 Layer 2 (data link layer)L3 Layer 3 (network layer)LAA Licensed Assisted AccessLAN Local Area NetworkLBT Listen Before TalkLCM LifeCycle ManagementLCR Low Chip RateLCS Location ServicesLCID Logical Channel IDLI Layer IndicatorLLC Logical Link Control, Low Layer CompatibilityLPLMN Local PLMNLPP LTE Positioning ProtocolLSB Least Significant BitLTE Long Term EvolutionLWA LTE-WLAN aggregationLWIP LTE/WLAN Radio Level Integration with IPsec TunnelLTE Long Term EvolutionM2M Machine-to-MachineMAC Medium Access Control (protocol layering context)MAC Message authentication code (security/encryption context)MAC-A MAC used for authentication and key agreement (TSG T WG3 context)MAC-I MAC used for data integrity of signalling messages (TSG T WG3 context)MANO Management and OrchestrationMBMS Multimedia Broadcast and Multicast ServiceMB SFN Multimedia Broadcast multicast service Single Frequency NetworkMCC Mobile Country CodeMCG Master Cell GroupMCOT Maximum Channel Occupancy TimeMCS Modulation and coding schemeMDAF Management Data Analytics FunctionMDAS Management Data Analytics ServiceMDT Minimization of Drive TestsME Mobile EquipmentMeNB master eNBMER Message Error RatioMGL Measurement Gap LengthMGRP Measurement Gap Repetition PeriodMIB Master Information Block, Management Information BaseMIMO Multiple Input Multiple OutputMLC Mobile Location CentreMM Mobility ManagementMME Mobility Management EntityMN Master NodeMO Measurement Object, Mobile OriginatedMPBCH MTC Physical Broadcast CHannelMPDCCH MTC Physical Downlink Control CHannelMPDSCH MTC Physical Downlink Shared CHannelMPRACH MTC Physical Random Access CHannelMPUSCH MTC Physical Uplink Shared ChannelMPLS MultiProtocol Label SwitchingMS Mobile StationMSB Most Significant BitMSC Mobile Switching CentreMSI Minimum System Information, MCH Scheduling InformationMSID Mobile Station IdentifierMSIN Mobile Station Identification NumberMSISDN Mobile Subscriber ISDN NumberMT Mobile Terminated, Mobile TerminationMTC Machine-Type CommunicationsmMTC massive MTC, massive Machine-Type CommunicationsMU-MIMO Multi User MIMOMWUS MTC wake-up signal, MTC WUSNACK Negative AcknowledgementNAI Network Access IdentifierNAS Non-Access Stratum, Non-Access Stratum layerNCT Network Connectivity TopologyNEC Network Capability ExposureNE-DC NR-E-UTRA Dual ConnectivityNEF Network Exposure FunctionNF Network FunctionNFP Network Forwarding PathNFPD Network Forwarding Path DescriptorNFV Network Functions VirtualizationNFVI NFV InfrastructureNFVO NFV OrchestratorNG Next Generation, Next GenNGEN-DC NG-RAN E-UTRA-NR Dual ConnectivityNM Network ManagerNMS Network Management SystemN-PoP Network Point of PresenceNMIB, N-MIB Narrowband MIBNPBCH Narrowband Physical Broadcast CHannelNPDCCH Narrowband Physical Downlink Control CHannelNPDSCH Narrowband Physical Downlink Shared CHannelNPRACH Narrowband Physical Random Access CHannelNPUSCH Narrowband Physical Uplink Shared CHannelNPSS Narrowband Primary Synchronization SignalNSSS Narrowband Secondary Synchronization SignalNR New Radio, Neighbour RelationNRF NF Repository FunctionNRS Narrowband Reference SignalNS Network ServiceNSA Non-Standalone operation modeNSD Network Service DescriptorNSR Network Service RecordNSSAI ‘Network Slice Selection Assistance InformationS-NNSAI Single-NSSAINSSF Network Slice Selection FunctionNW NetworkNWUS Narrowband wake-up signal, Narrowband WUSNZP Non-Zero PowerO&M Operation and MaintenanceODU2 Optical channel Data Unit—type 2OFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOOB Out-of-bandOOS Out of SyncOPEX OPerating EXpenseOSI Other System InformationOSS Operations Support SystemOTA over-the-airPAPR Peak-to-Average Power RatioPAR Peak to Average RatioPBCH Physical Broadcast ChannelPC Power Control, Personal ComputerPCC Primary Component Carrier, Primary CCPCell Primary CellPCI Physical Cell ID, Physical Cell IdentityPCEF Policy and Charging Enforcement FunctionPCF Policy Control FunctionPCRF Policy Control and Charging Rules FunctionPDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol layerPDCCH Physical Downlink Control ChannelPDCP Packet Data Convergence ProtocolPDN Packet Data Network, Public Data NetworkPDSCH Physical Downlink Shared ChannelPDU Protocol Data UnitPEI Permanent Equipment IdentifiersPFD Packet Flow DescriptionP-GW PDN GatewayPHICH Physical hybrid-ARQ indicator channelPHY Physical layerPLMN Public Land Mobile NetworkPIN Personal Identification NumberPM Performance MeasurementPMI Precoding Matrix IndicatorPNF Physical Network FunctionPNFD Physical Network Function DescriptorPNFR Physical Network Function RecordPOC PTT over CellularPP, PTP Point-to-PointPPP Point-to-Point ProtocolPRACH Physical RACHPRB Physical resource blockPRG Physical resource block groupProSe Proximity Services, Proximity-Based ServicePRS Positioning Reference SignalPRR Packet Reception RadioPS Packet ServicesPSBCH Physical Sidelink Broadcast ChannelPSDCH Physical Sidelink Downlink ChannelPSCCH Physical Sidelink Control ChannelPSSCH Physical Sidelink Shared ChannelPSCell Primary SCellPSS Primary Synchronization SignalPSTN Public Switched Telephone NetworkPT-RS Phase-tracking reference signalPTT Push-to-TalkPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelQAM Quadrature Amplitude ModulationQCI QoS class of identifierQCL Quasi co-locationQFI QoS Flow ID, QoS Flow IdentifierQoS Quality of ServiceQPSK Quadrature (Quaternary) Phase Shift KeyingQZSS Quasi-Zenith Satellite SystemRA-RNTI Random Access RNTIRAB Radio Access Bearer, Random Access BurstRACH Random Access ChannelRADIUS Remote Authentication Dial In User ServiceRAN Radio Access NetworkRAND RANDom number (used for authentication)RAR Random Access ResponseRAT Radio Access TechnologyRAU Routing Area UpdateRB Resource block, Radio BearerRBG Resource block groupREG Resource Element GroupRel ReleaseREQ REQuestRF Radio FrequencyRI Rank IndicatorRIV Resource indicator valueRL Radio LinkRLC Radio Link Control, Radio Link Control layerRLC AM RLC Acknowledged ModeRLC UM RLC Unacknowledged ModeRLF Radio Link FailureRLM Radio Link MonitoringRLM-RS Reference Signal for RLMRM Registration ManagementRMC Reference Measurement ChannelRMSI Remaining MSI, Remaining Minimum System InformationRN Relay NodeRNC Radio Network ControllerRNL Radio Network LayerRNTI Radio Network Temporary IdentifierROHC RObust Header CompressionRRC Radio Resource Control, Radio Resource Control layerRRM Radio Resource ManagementRS Reference SignalRSRP Reference Signal Received PowerRSRQ Reference Signal Received QualityRSSI Received Signal Strength IndicatorRSU Road Side UnitRSTD Reference Signal Time differenceRTP Real Time ProtocolRTS Ready-To-SendRTT Round Trip TimeRx Reception, Receiving, ReceiverS1AP S1 Application ProtocolS1-MME S1 for the control planeS1-U S1 for the user planeS-GW Serving GatewayS-RNTI SRNC Radio Network Temporary IdentityS-TMSI SAE Temporary Mobile Station IdentifierSA Standalone operation modeSAE System Architecture EvolutionSAP Service Access PointSAPD Service Access Point DescriptorSAPI Service Access Point IdentifierSCC Secondary Component Carrier, Secondary CCSCell Secondary CellSC-FDMA Single Carrier Frequency Division Multiple AccessSCG Secondary Cell GroupSCM Security Context ManagementSCS Subcarrier SpacingSCTP Stream Control Transmission ProtocolSDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol layerSDL Supplementary DownlinkSDNF Structured Data Storage Network FunctionSDP Service Discovery Protocol (Bluetooth related)SDSF Structured Data Storage FunctionSDU Service Data UnitSEAF Security Anchor FunctionSeNB secondary eNBSEPP Security Edge Protection ProxySFI Slot format indicationSFTD Space-Frequency Time Diversity, SFN and frame timing differenceSFN System Frame NumberSgNB Secondary gNBSGSN Serving GPRS Support NodeS-GW Serving GatewaySI System InformationSI-RNTI System Information RNTISIB System Information BlockSIM Subscriber Identity ModuleSIP Session Initiated ProtocolSiP System in PackageSL SidelinkSLA Service Level AgreementSM Session ManagementSMF Session Management FunctionSMS Short Message ServiceSMSF SMS FunctionSMTC SSB-based Measurement Timing ConfigurationSN Secondary Node, Sequence NumberSoC System on ChipSON Self-Organizing NetworkSpCell Special CellSP-CSI-RNTI Semi-Persistent CSI RNTISPS Semi-Persistent SchedulingSQN Sequence numberSR Scheduling RequestSRB Signalling Radio BearerSRS Sounding Reference SignalSS Synchronization SignalSSB Synchronization Signal Block, SS/PBCH BlockSSBRI SS/PBCH Block Resource Indicator, Synchronization Signal Block Resource IndicatorSSC Session and Service ContinuitySS-RSRP Synchronization Signal based Reference Signal Received PowerSS-RSRQ Synchronization Signal based Reference Signal Received QualitySS-SINR Synchronization Signal based Signal to Noise and Interference RatioSSS Secondary Synchronization SignalSSSG Search Space Set GroupSSSIF Search Space Set IndicatorSST Slice/Service TypesSU-MIMO Single User MIMOSUL Supplementary UplinkTA Timing Advance, Tracking AreaTAC Tracking Area CodeTAG Timing Advance GroupTAU Tracking Area UpdateTB Transport BlockTBS Transport Block SizeTBD To Be DefinedTCI Transmission Configuration IndicatorTCP Transmission Communication ProtocolTDD Time Division DuplexTDM Time Division MultiplexingTDMA Time Division Multiple AccessTE Terminal EquipmentTEID Tunnel End Point IdentifierTFT Traffic Flow TemplateTMSI Temporary Mobile Subscriber IdentityTNL Transport Network LayerTPC Transmit Power ControlTPMI Transmitted Precoding Matrix IndicatorTR Technical ReportTRP, TRxP Transmission Reception PointTRS Tracking Reference SignalTRx TransceiverTS Technical Specifications, Technical StandardTTI Transmission Time IntervalTx Transmission, Transmitting, TransmitterU-RNTI UTRAN Radio Network Temporary IdentityUART Universal Asynchronous Receiver and TransmitterUCI Uplink Control InformationUE User EquipmentUDM Unified Data ManagementUDP User Datagram ProtocolUDSF Unstructured Data Storage Network FunctionUICC Universal Integrated Circuit CardUL UplinkUM Unacknowledged ModeUML Unified Modelling LanguageUMTS Universal Mobile Telecommunications SystemUP User PlaneUPF User Plane FunctionURI Uniform Resource IdentifierURL Uniform Resource LocatorURLLC Ultra-Reliable and Low LatencyUSB Universal Serial BusUSIM Universal Subscriber Identity ModuleUSS UE-specific search spaceUTRA UMTS Terrestrial Radio AccessUTRAN Universal Terrestrial Radio Access NetworkUwPTS Uplink Pilot Time SlotV2I Vehicle-to-InfrastructionV2P Vehicle-to-PedestrianV2V Vehicle-to-VehicleV2X Vehicle-to-everythingVIM Virtualized Infrastructure ManagerVL Virtual Link,VLAN Virtual LAN, Virtual Local Area NetworkVM Virtual MachineVNF Virtualized Network FunctionVNFFG VNF Forwarding GraphVNFFGD VNF Forwarding Graph DescriptorVNFM VNF ManagerVoIP Voice-over-IP, Voice-over-Internet ProtocolVPLMN Visited Public Land Mobile NetworkVPN Virtual Private NetworkVRB Virtual Resource BlockWiMAX Worldwide Interoperability for Microwave AccessWLAN Wireless Local Area NetworkWMAN Wireless Metropolitan Area NetworkWPAN Wireless Personal Area NetworkX2-C X2-Control planeX2-U X2-User planeXML eXtensible Markup LanguageXRES EXpected user RESponseXOR eXclusive ORZC Zadoff-ChuZP 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 “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. 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 computer-executable instructions, such as program code, software modules, and/or functional processes. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “SMTC” refers to an SSB-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.