Performance measurements relating to application triggering and SMS

NEF and AMF measure application triggering and SMS performance on NAS, which solves the problem that existing systems are difficult to monitor performance, realizes real-time monitoring and indicator provision of application triggering and SMS performance, and improves network stability and User experience.

CN118890650APending Publication Date: 2024-11-01APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411281932.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2019-06-12
Filing Date
2020-06-12
Publication Date
2024-11-01

AI Technical Summary

Technical Problem

Existing wireless communication systems have difficulties in measuring application triggered and non-access layer short message service (SMS) performance, difficulty in effectively monitoring potential problems in networks or network interfaces, and lack real-time performance metrics to provide to end users.

Method used

Measure application-triggered performance through the Network Exposure Function (NEF) and SMS performance on non-access layer (NAS) is measured through the Access and Mobility Management Function (AMF) to generate performance measurements for these network functions, including applications 触发请求、注册请求、消息传输等方面的数据。

Benefits of technology

Real-time monitoring of application triggering and SMS performance on NAS is realized, which can identify potential problems and provide performance indicators, improving network stability and user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118890650A_ABST
    Figure CN118890650A_ABST
Patent Text Reader

Abstract

The invention relates to performance measurements related to application triggering and SMS on NAS. Techniques for performance measurements related to application triggering and short message services (SMS) on a non-access stratum (NAS), the techniques comprising: obtaining original performance measurements from one or more network functions in a wireless communication network, the one or more network functions comprising at least one of a network exposure function (NEF) or an access and mobility management function (AMF); and generating a performance measurement for the one or more network functions based on the original performance measurement.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the Chinese patent application with the application date of June 12, 2020, application number 202080050551.2, and invention name “Performance measurement related to application triggering and SMS on NAS”. Technical Field

[0002] The present disclosure generally relates to performance measurement in wireless communications. Background Art

[0003] Wireless communications have evolved significantly from early voice systems to today's highly complex, integrated communications platforms. The next generation of wireless communications, Fifth Generation New Radio (5G NR), will expand wireless communications to accommodate diverse and sometimes conflicting services and applications. Broadly speaking, 5G NR will evolve based on the 3rd Generation Partnership Project (3GPP) Long Term Evolution Advanced (LTE-Advanced) standard, with the addition of potential new radio access technologies (RATs) to improve wireless connectivity solutions. Summary of the Invention

[0004] In general, in one aspect, a method includes obtaining raw performance measurements from one or more network functions in a wireless communication network, the one or more network functions including at least one of a network exposure function (NEF) or an access and mobility management function (AMF); and generating performance measurements for the one or more network functions based on the raw performance measurements.

[0005] In general, in one aspect, a processor for a telecommunications device includes circuitry for executing one or more instructions that, when executed, cause the processor to perform operations including: obtaining raw performance measurements from one or more network functions in a wireless communication network, the one or more network functions including at least one of an NEF or an AMF; and generating performance measurements for the one or more network functions based on the raw performance measurements.

[0006] Generally, in one aspect, a non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising: obtaining raw performance measurements from one or more network functions in a wireless communication network, the one or more network functions including at least one of an NEF or an AMF; and generating performance measurements for the one or more network functions based on the raw performance measurements.

[0007] Implementations of any of the various aspects may include one or a combination of two or more of the following features.

[0008] In some examples, one or more network functions are NEFs, and the performance measurements relate to application triggers requested by the application functions. The performance measurements may include one or more of the following: the number of application trigger requests, the number of application trigger requests accepted for delivery, the number of application trigger requests rejected for delivery, the number of protocol data unit (PDU) sessions requested for modification, or the number of application trigger delivery reports. The number of application trigger requests may be based on a cumulative counter that is triggered when the NEF receives a delivery request (e.g., Nnef_Trigger_Delivery request) from the application function. The number of application trigger requests accepted for delivery may be based on a cumulative counter that is triggered when the NEF transmits a delivery response (e.g., Nnef_trigger_Delivery response) to the application function, wherein the delivery response includes an indication that the application trigger request has been accepted for delivery to a user equipment (UE). The number of application trigger requests rejected for delivery may be based on a cumulative counter that is triggered when the NEF transmits a delivery response (e.g., Nnef_Trigger_Delivery response) to the application function, wherein the delivery response includes an indication that the application trigger request has been rejected for delivery to the UE. In some examples, the number of application-triggered delivery requests that are rejected for delivery is incremented by an error code (e.g., by a response code, as specified in a 3GPP technical specification). The number of application-triggered delivery reports can be based on a cumulative counter that is triggered when a delivery message (e.g., an Nnef_Trigger_DeliveryNotify message) is transmitted by the NEF to the application function, where the delivery message includes an indication of the application-triggered delivery result. In some examples, the number of application-triggered delivery reports is incremented by a delivery result (e.g., success, failure, or another result specified in a 3GPP technical specification).

[0009] In some examples, the one or more network functions is an AMF, and the performance measurement relates to a short message service (SMS) over a non-access stratum (NAS). The performance measurement includes one or more of the following: a number of registration requests for SMS over the NAS, a number of successful registrations allowed for SMS over the NAS, a number of attempted mobile originated (MO) SMS messages over the NAS, a number of successfully transmitted MO SMS messages over the NAS, a number of attempted mobile terminated (MT) SMS messages over the NAS, or a number of successfully transmitted MT SMS messages over the NAS.

[0010] The number of registration requests for SMS over NAS may be based on a cumulative counter that is triggered when the AMF receives a Registration Request message from the UE, the Registration Request message including an indication that the UE supports SMS delivery over NAS. The number of successful registrations allowed for SMS over NAS may be based on a cumulative counter that is triggered when the AMF transmits a Registration Accept message to the UE, the Registration Accept message including an indication that SMS is allowed.

[0011] The number of attempted MO SMS messages over NAS may be based on a cumulative counter that is triggered when a NAS message is received by the AMF from the UE, the NAS message including an indication of SMS delivery. The number of successfully delivered MO SMS messages over NAS may be based on a cumulative counter that is triggered when a NAS message is transmitted by the AMF to the UE, the NAS message including an indication that the MO SMS message has been successfully delivered.

[0012] The number of attempted MT SMS messages over NAS may be based on a cumulative counter that is triggered when a NAS message is transmitted by the AMF to the UE, the NAS message including an indication of SMS transmission. The number of successfully transmitted MT SMS messages over NAS may be based on a cumulative counter that is triggered when a NAS message is received by the AMF from the UE, the NAS message including an indication that the MT SMS message has been successfully delivered.

[0013] In some examples, performance measurements are separated by access type (e.g., 3GPP access and non-3GPP access). In other examples, performance measurements are performed regardless of access type. A service producer, such as one of one or more NEFs, AMFs, or another management function, may obtain raw performance measurements and may generate performance measurements. The generated performance measurements may be stored, transmitted, displayed, or otherwise provided to an end user (e.g., a service consumer) in any suitable form.

[0014] The details of one or more specific implementations are set forth in the following figures and description. The techniques described herein may be implemented by one or more wireless communication systems, components of wireless communication systems (e.g., user equipment, base stations), or other systems, devices, methods, or non-transitory computer-readable media. Additional features and advantages will be apparent from the detailed description and drawings, as well as from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figures 1 to 3 An exemplary wireless communication system is shown.

[0016] Figure 4 An example of infrastructure equipment is shown.

[0017] Figure 5Examples of platforms or devices are shown.

[0018] Figure 6 Exemplary components of baseband circuitry and radio front-end circuitry are shown.

[0019] Figure 7 Exemplary components of cellular communication circuitry are shown.

[0020] Figure 8 Example protocol functions that may be implemented in a wireless communication system are shown.

[0021] Figure 9 Exemplary components of a core network are shown.

[0022] Figure 10 An exemplary system supporting network function virtualization is shown.

[0023] Figure 11 An exemplary computer system is shown.

[0024] Figure 12 An exemplary device triggering process is shown.

[0025] Figure 13 An exemplary non-roaming architecture is shown.

[0026] Figure 14 An exemplary performance management system is shown.

[0027] Figure 15 An exemplary process for performance measurements related to application triggering and SMS over NAS is shown.

[0028] Like reference symbols in the various drawings indicate like elements. DETAILED DESCRIPTION

[0029] The present disclosure provides techniques for generating performance measurements in wireless communication networks, such as 5G NR networks. Specifically, the techniques described herein provide for measuring the performance of application triggers through the Network Exposure Function (NEF) and the performance of Short Message Service (SMS) over the Non-Access Stratum (NAS) through the Access and Mobility Management Function (AMF). In doing so, the performance of application triggers and SMS over NAS can be monitored to identify potential problems in the network or network interfaces, and performance metrics can be provided to end users.

[0030] Figure 1An exemplary wireless communication system 100 is shown. For convenience and not limitation, the exemplary system 100 is described in the context of LTE and 5G NR communication standards defined by the 3GPP technical specifications. However, the techniques described herein may also be implemented in other communication systems using other communication standards, such as other 3GPP standards or IEEE 802.16 protocols (e.g., WMAN or WiMAX).

[0031] System 100 includes UE 101a and UE 101b (collectively, "UE 101"). In this example, UE 101 is shown as a smartphone (eg, a handheld, touchscreen mobile computing device that can connect to one or more cellular networks). In other examples, any of the plurality of UEs 101 may include other mobile computing devices or non-mobile computing devices, such as consumer electronic devices, cellular phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, on-board mobility equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), connected or “smart” appliances, machine type communication (MTC) devices, machine-to-machine (M2M) devices, Internet of Things (IoT) devices, or combinations thereof, etc.

[0032] In some examples, any of the plurality of UEs 101 may be an IoT UE, which may include a network access layer designed for low-power IoT applications utilizing short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device using, for example, a public land mobile network (PLMN), proximity services (ProSe), device-to-device (D2D) communications, sensor networks, IoT networks, or a combination thereof. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-term connections. The IoT UE may execute background applications (e.g., keep-alive messages or status updates) to facilitate connectivity to the IoT network.

[0033] UE 101 is configured to connect (e.g., be communicatively coupled) to an access network (AN) or radio access network (RAN) 110. In some examples, RAN 110 can be a next-generation RAN (NG RAN), an evolved UMTS terrestrial radio access network (E-UTRAN), or a legacy RAN, such as a UMTS terrestrial radio access network (UTRAN) or a GSM EDGE radio access network (GERAN). As used herein, the term "NG RAN" can refer to the RAN 110 operating in a 5G NR system 100, while the term "E-UTRAN" can refer to the RAN 110 operating in an LTE or 4G system 100.

[0034] To connect to the RAN 110, multiple UEs 101 utilize connections (or channels) 103 and 104, respectively, each of which may include a physical communication interface or layer, as described below. In this example, connections 103 and 104 are shown as air interfaces to achieve communication coupling and can be consistent with cellular communication protocols, such as the Global System for Mobile Communications (GSM) protocol, the Code Division Multiple Access (CDMA) network protocol, the Push-to-Talk (PTT) protocol, the Cellular PTT (POC) protocol, the Universal Mobile Telecommunications System (UMTS) protocol, the 3GPP LTE protocol, the 5G NR protocol, or a combination thereof, as well as other communication protocols. In some examples, multiple UEs 101 can use an interface 105 such as a ProSe interface to directly exchange communication data. The interface 105 may alternatively be referred to as a sidelink interface 105 and may include one or more logical channels, such as a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink downlink channel (PSDCH), or a physical sidelink broadcast channel (PSBCH), or a combination thereof.

[0035] UE 101b is shown configured to access access point (AP) 106 (also referred to as "WLAN node 106," "WLAN 106," "WLAN termination 106," "WT 106," etc.) using connection 107. Connection 107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein AP 106 may include Wireless Fidelity. Router. In this example, AP 106 is shown connected to the Internet without being connected to the core network of the wireless system, as described in further detail below. In various examples, UE 101b, RAN 110, and AP 106 can be configured to use LTE-WLAN aggregation (LWA) operation or LTE / WLAN radio level operation integrated with IPsec tunneling (LWIP). LWA operation may involve RAN nodes 111a, 111b configuring UE 101b in an RRC_CONNECTED state to utilize radio resources of LTE and WLAN. LWIP operation may involve UE 101b using IPsec protocol tunneling to use WLAN radio resources (e.g., connection 107) to authenticate and encrypt packets (e.g., IP packets) sent over connection 107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0036] The RAN 110 includes one or more AN nodes or RAN nodes 111a and 111b (collectively referred to as "RAN nodes 111") that enable connections 103 and 104. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data or voice connections, or both, between a network and one or more users. These access nodes may be referred to as base stations (BSs), gNodeBs, gNBs, eNodeBs, eNBs, NodeBs, RAN nodes, roadside units (RSUs), transmit receive points (TRxPs or TRPs), and the like, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN nodes" and the like may refer to RAN nodes 111 (e.g., gNBs) operating in a 5G NR system 100, while the term "E-UTRAN nodes" and the like may refer to RAN nodes 111 (e.g., eNBs) operating in an LTE or 4G system 100. In some examples, multiple RAN nodes 111 may be implemented as one or more dedicated physical devices such as macrocell base stations or low power (LP) base stations for providing femtocells, picocells, or other similar cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macrocells.

[0037] In some examples, some or all of the multiple RAN nodes 111 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a cloud RAN (CRAN) or a virtual baseband unit pool (vBBUP). The CRAN or vBBUP may implement RAN functional partitioning, such as a packet data convergence protocol (PDCP) partitioning, where the radio resource control (RRC) and PDCP layers are operated by the CRAN / vBBUP, and other layer 2 (e.g., data link layer) protocol entities are operated by individual RAN nodes 111; a medium access control (MAC) / physical layer (PHY) partitioning, where the RRC, PDCP, MAC, and radio link control (RLC) layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 111; or a "lower PHY" partitioning, where the RRC, PDCP, RLC, and MAC layers, as well as the upper portion of the PHY layer, are operated by the CRAN / vBBUP, and the lower portion of the PHY layer is operated by individual RAN nodes 111. This virtualization framework allows idle processor cores of the RAN nodes 111 to execute, for example, other virtualized applications. In some examples, individual RAN nodes 111 may represent nodes using individual F1 interfaces ( Figure 1 In some examples, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Figure 4 ), and the gNB-CU may be operated by a server (not shown) located in RAN 110 or by a server pool in a manner similar to CRAN / vBBUP. Additionally or alternatively, one or more of the RAN nodes 111 may be next-generation eNBs (ng-eNBs), including RAN nodes that provide E-UTRA user plane and control plane protocol terminations to UE 101 and connect to a 5G core network (e.g., core network 120) using a next-generation interface.

[0038] In a vehicle-to-everything (V2X) scenario, one or more of the RAN nodes 111 may be or act as an RSU. The term "roadside unit" or "RSU" refers to any traffic infrastructure entity used for V2X communications. The 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 so on. In some examples, the RSU is a computing device coupled to RF circuitry located on the roadside that provides connectivity support to passing vehicle UEs 101 (vUEs 101). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications or other software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision 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 communication services. Additionally or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) or provide connectivity to one or more cellular networks to provide uplink and downlink communications, or both. Some or all of the computing device and the RSU's RF circuitry may be encapsulated in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network, or both.

[0039] Any one of the RAN nodes 111 may serve as the endpoint for the air interface protocol and may be the first point of contact for the UE 101. In some examples, any one of the multiple RAN nodes 111 may perform various logical functions of the RAN 110, including but not limited to functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0040] In some examples, multiple UEs 101 can be configured to communicate with each other or with any of multiple RAN nodes 111 using orthogonal frequency division multiplexing (OFDM) communication signals over a multi-carrier communication channel in accordance with various communication techniques, such as, but not limited to, OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the techniques described herein is not limited in this respect. The OFDM signal can include multiple orthogonal subcarriers.

[0041] In some examples, a downlink resource grid can be used for downlink transmissions from any of multiple RAN nodes 111 to multiple UEs 101, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink during each time slot. This type of time-frequency plane representation is common for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes multiple resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a collection of resource elements; in the frequency domain, this can represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0042] In some examples, multiple UEs 101 and multiple RAN nodes 111 communicate (e.g., transmit and receive) data over a licensed medium (also referred to as a "licensed spectrum" or "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band.

[0043] To operate in the unlicensed spectrum, the plurality of UEs 101 and the plurality of RAN nodes 111 may operate using license-assisted access (LAA), enhanced LAA (eLAA), or another enhanced LAA (feLAA) mechanism. In these embodiments, the plurality of UEs 101 and the plurality of RAN nodes 111 may perform one or more known medium sensing operations or carrier sensing operations, or both, to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before 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 by which equipment (e.g., the plurality of UEs 101, the plurality of RAN nodes 111) senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operations may include clear channel assessment (CCA), which uses energy detection to determine whether other signals are present on the channel in order to determine whether the channel is occupied or clear. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in the unlicensed spectrum and with other LAA networks. Energy detection may include sensing RF energy in the intended transmission band over a period of time and comparing the sensed RF energy to a predefined or configured threshold.

[0044] The existing system in the 5 GHz band may be a WLAN based on IEEE 802.11 technology. The WLAN adopts a contention-based channel access mechanism (e.g., CSMA with collision avoidance (CSMA / CA). In some examples, when a WLAN node (e.g., a mobile station (MS) such as UE 101, AP 106, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly drawn within the contention window size (CWS), which increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. In some examples, the LBT mechanism designed for LAA is similar to CSMA / CA for WLAN. In some examples, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have an LAA contention window of variable length between X and Y extended CAA (ECCA) time slots, where X and Y are the minimum and maximum values ​​of the CWS for LAA. In one example, the minimum CWS for LAA transmission may be 9 microseconds (μs); however, the size of the CWS and the maximum channel occupancy time (e.g., transmission burst) may be based on government regulatory requirements.

[0045] In some examples, the LAA mechanism is built on the carrier aggregation technology of the LTE-Advanced system. In CA, each aggregated carrier is called a component carrier. In some examples, the component carrier may have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five component carriers may be aggregated to provide a maximum aggregate bandwidth of 100 MHz. In a frequency division duplex (FDD) system, the number of aggregated carriers may be different for DL ​​and UL. For example, the number of UL component carriers may be equal to or less than the number of DL component carriers. In some cases, each component carrier may have a different bandwidth than other component carriers. In a time division duplex (TDD) system, the number of component carriers and the bandwidth of each component carrier are typically the same for DL ​​and UL.

[0046] Carrier aggregation may also include separate serving cells to provide separate component carriers. The coverage of the serving cells may be different, for example, because component carriers on different frequency bands may experience different path losses. The primary serving cell (PCell) may provide the primary component carrier for both UL and DL, and may handle RRC and non-access stratum (NAS) related activities. The other serving cells are referred to as secondary component carriers (SCells), and each SCell may provide a separate secondary component carrier for both UL and DL. Secondary component carriers may be added and removed as needed, while changing the primary component carrier may require the UE 101 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells 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 the same subframe.

[0047] The PDSCH carries user data and higher-layer signaling to multiple UEs 101. The physical downlink control channel (PDCCH) carries information about, among other things, the transport format and resource allocation associated with the PDSCH channel. It can also inform UEs 101 about the transport format, resource allocation, and hybrid automatic repeat request (HARQ) information associated with the uplink shared channel. Downlink scheduling (e.g., allocating control and shared channel resource blocks to UE 101b within a cell) can be performed at any of the RAN nodes 111 based on channel quality information fed back from any of the UEs 101. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 101.

[0048] PDCCH uses control channel elements (CCE) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruples, which can then be arranged using a sub-block interleaver for rate matching. In some examples, one or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to four sets of nine physical resource elements, collectively referred to as resource element groups (REGs). Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the downlink control information (DCI) and the channel conditions, one or more CCEs can be used to transmit the PDCCH. In LTE, there may be four or more different PDCCH formats defined with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0049] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize an enhanced PDCCH (EPDCCH) that uses PDSCH resources for control information transmission. One or more enhanced CCEs (ECCEs) may be used to transmit the EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, collectively referred to as enhanced REGs (EREGs). In some examples, ECCEs may have other numbers of EREGs.

[0050] The RAN nodes 111 are configured to communicate with each other using interfaces 112. In an example, such as if the system 100 is an LTE system (e.g., when the core network 120 is Figure 2In the case of an Evolved Packet Core (EPC) network as shown in FIG, interface 112 may be an X2 interface 112. The X2 interface may be defined between two or more RAN nodes 111 (e.g., two or more eNBs, etc.) connected to the EPC 120, or between two eNBs connected to the EPC 120, or both. In some examples, 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 a flow control mechanism for user packets transmitted over the X2 interface and may be used to convey information regarding the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information regarding user data transmitted from a primary eNB to a secondary eNB; information regarding successful in-sequence delivery of PDCP protocol data units (PDUs) for user data from the secondary eNB to the UE 101; information regarding PDCP PDUs that were not delivered to the UE 101; information regarding the current minimum expected buffer size at the secondary eNB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, or user plane transmission control; load management function; inter-cell interference coordination function; etc.

[0051] In some examples, such as where system 100 is a 5G NR system (e.g., when core network 120 is such as Figure 3), the interface 112 may be an Xn interface 112. The Xn interface may be defined between two or more RAN nodes 111 (e.g., two or more gNBs, etc.) connected to the 5G core network 120, between a RAN node 111 (e.g., a gNB) and an eNB connected to the 5G core network 120, or between two eNBs connected to the 5G core network 120, or a combination thereof. In some examples, 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 functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for the UE 101 in connected mode (e.g., CM-CONNECTED), including functions for managing UE mobility in connected mode between one or more RAN nodes 111; and the like. Mobility support may include context transfer from the old (source) serving RAN node 111 to the new (target) serving RAN node 111, as well as control of the user plane tunnel between the old (source) serving RAN node 111 and the new (target) serving RAN node 111. The Xn-U protocol stack may include a transport network layer built on the Internet Protocol (IP) transport layer, and a GPRS Tunneling Protocol (GTP-U) layer for the user plane, which carries user plane PDUs, built on top of the User Datagram Protocol (UDP) or the IP layer, or both. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of the Stream Control Transmission Protocol (SCTP). SCTP may be built on top of the IP layer and provide guaranteed delivery of application layer messages. Within the transport IP layer, signaling PDUs are delivered using point-to-point transport. In other implementations, the Xn-U protocol stack, the Xn-C protocol stack, or both, may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0052] RAN 110 is shown as being communicatively coupled to a core network 120 (referred to as "CN 120"). CN 120 includes one or more network elements 122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 101) connected to CN 120 using RAN 110. Components of CN 120 may be implemented in one physical node or separate physical nodes and may include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some examples, network function virtualization (NFV) may be used to virtualize some or all of the network node functions described herein using executable instructions stored in one or more computer-readable storage media, as described in further detail below. A logical instance of CN 120 may be referred to as a network slice, and a logical instance of a portion of CN 120 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively, performed by proprietary hardware). In other words, an NFV system may be used to perform virtual or reconfigurable implementations, or both, of one or more network components or functions.

[0053] Generally, the application server 130 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS packet service (PS) domain, LTE PS data service, etc.). The application server 130 may also be configured to utilize the CN 120 to support one or more communication services for the UE 101 (e.g., VoIP sessions, PTT sessions, group communication sessions, social network services, etc.).

[0054] In some examples, CN 120 can be a 5G core network (referred to as "5GC 120"), and RAN 110 can be connected to CN 120 using a next-generation interface 113. In some examples, the next-generation interface 113 can be divided into two parts: a next-generation user plane (NG-U) interface 114, which carries traffic data between multiple RAN nodes 111 and a user plane function (UPF); and an S1 control plane (NG-C) interface 115, which is a signaling interface between the RAN node 111 and the access and mobility management function (AMF). Figure 3 Discussing in more detail, CN 120 is an example of 5GC 120.

[0055] In some examples, CN 120 may be an EPC (referred to as "EPC 120," etc.), and RAN 110 may be connected to CN 120 using an S1 interface 113. In some examples, S1 interface 113 may be divided into two parts: an S1-user plane (S1-U) interface 114, which carries traffic data between RAN node 111 and a serving gateway (S-GW); and an S1-MME interface 115, which is a signaling interface between RAN node 111 and a mobility management entity (MME).

[0056] Figure 2 FIG2 shows an exemplary architecture of a system 200 including a CN 220. In this example, the system 200 may implement the LTE standard such that the CN 220 is a Figure 1 In addition, UE 201 can communicate with EPC 220 of CN 120. Figure 1 The UE 101 is the same as or similar to the UE 101, and the E-UTRAN 210 may be the same as Figure 1 The CN 220 may be a RAN that is the same as or similar to the RAN 110 of the present invention and may include the RAN node 111 discussed previously. The CN 220 may include an MEE 221, an S-GW 222, a PDN Gateway (P-GW) 223, a High Speed ​​Packet Access (HSS) function 224, and a Serving GPRS Support Node (GENEVA) 225.

[0057] The MME 221 may be similar in functionality to the control plane of a traditional SGSN and may implement mobility management (MM) functions to keep track of the current location of the UE 201. The MME 221 may perform various mobility management procedures to manage mobility aspects of access, such as gateway selection and tracking area list management. Mobility management (also referred to as "EPSMM" or "EMM" in the E-UTRAN system) may refer to all applicable procedures, methods, data stores, etc. for maintaining knowledge of the current location of the UE 201, providing user identity confidentiality to users / subscribers, or performing other similar services, or a combination thereof. Each UE 201 and the MME 221 may include an EMM sublayer, and upon successful completion of the attach procedure, a mobility management context may be established in the UE 201 and the MME 221. The mobility management context may be a data structure or database object that stores mobility management-related information for the UE 201. The MME 221 may be coupled to the HSS 224 using an S6a reference point, to the SGSN 225 using an S3 reference point, and to the S-GW 222 using an S11 reference point.

[0058] SGSN 225 may be a node that serves UE 201 by tracking the location of individual UE 201 and performing security functions. Furthermore, SGSN 225 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 221; handling of UE 201 time zone capabilities, as specified by MME 221; and MME selection for handover to E-UTRAN 3GPP access networks, among other functions. The S3 reference point between MME 221 and SGSN 225 may enable user and bearer information exchange for inter-3GPP access network mobility in either an idle state or an active state, or both.

[0059] The HSS 224 may include a database for network users, including subscription-related information used to support network entities handling communication sessions. The EPC 220 may include one or more HSSs 224, depending on the number of mobile users, the capacity of the equipment, the organization of the network, or a combination thereof. For example, the HSS 224 may provide support for routing, roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. The S6a reference point between the HSS 224 and the MEE 221 may enable the transmission of subscription and authentication data between the HSS 224 and the MEE 221 for authenticating or authorizing user access to the EPC 220.

[0060] The S-GW 222 may terminate the S1 interface 113 toward the RAN 210 ( Figure 2 The S-GW 222 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and policy enforcement. The S11 reference point between the S-GW 222 and the MME 221 may provide a control plane between the MME 221 and the S-GW 222. The S-GW 222 may couple to the P-GW 223 using the S5 reference point.

[0061] The P-GW 223 may terminate the SGi interface towards the PDN 230. The P-GW 223 may use the IP interface 125 (see, e.g., Figure 1 ) routes data packets between EPC 220 and external networks, such as a network including application server 130 (sometimes referred to as "AF"). In some examples, P-GW 223 can use IP communication interface 125 (see, e.g., Figure 1 ) is communicatively coupled to an application server (e.g., Figure 1 Application server 130 or Figure 220). The S5 reference point between the P-GW 223 and the S-GW 222 may provide user plane tunneling and tunnel management between the P-GW 223 and the S-GW 222. The S5 reference point may also be used for S-GW 222 relocation due to the mobility of the UE 201 and whether the S-GW 222 needs to connect to a non-collocated P-GW 223 for the required PDN connectivity. The P-GW 223 may also include nodes for policy enforcement and charging data collection, such as a PCEF (not shown). In addition, the SGi reference point between the P-GW 223 and the packet data network (PDN) 230 may be an operator external public, private PDN, or an intra-operator packet data network, for example, for providing IMS services. The P-GW 223 may be coupled to a policy control and charging rules function (PCRF) 226 using the Gx reference point.

[0062] PCRF 226 is the policy and charging control element of EPC 220. In a non-roaming scenario, a single PCRF 226 may exist in the Home Public Land Mobile Network (HPLMN) associated with UE 201's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local traffic breakout, two PCRFs may be associated with UE 201's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Visited PCRF (V-PCRF) in the Visited Public Land Mobile Network (VPLMN). PCRF 226 may be communicatively coupled to application server 230 using P-GW 223. Application server 230 may signal PCRF 226 to indicate a new service flow and select appropriate quality of service (QoS) and charging parameters. PCRF 226 may configure the rules to a PCEF (not shown) with the appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI), which initiates the QoS and charging specified by application server 230. The Gx reference point between PCRF 226 and P-GW 223 may allow for the transfer of QoS policies and charging rules from PCRF 226 to PCEF in P-GW 223. The Rx reference point may reside between PDN 230 (or "AF 230") and PCRF 226.

[0063] Figure 3The architecture of a system 300 including a CN 320 is shown. The system 300 is shown to include a UE 301, which may be the same as or similar to the previously discussed UE 101 and UE 201; a (R)AN 310, which may be the same as or similar to the previously discussed RAN 110 and RAN 210, and which may include the previously discussed RAN node 111; and a data network (DN) 303, which may be, for example, an operator service, internet access, or a third-party service; and a 5GC 320. The 5GC 320 may include an authentication server function (AUSF) 322; an access and mobility management function (AMF) 321; a session management function (SMF) 324; a network exposure function (NEF) 323; a policy control function (PCF) 326; a network repository function (NRF) 325; a unified data management (UDM) function 327; an AF 328; a user plane function (UPF) 302; and a network slice selection function (NSSF) 329.

[0064] The UPF 302 can serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnecting with the DN 303, and a branching point supporting multi-homed PDU sessions. The UPF 302 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, perform lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (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. The UPF 302 may include an uplink classifier to support routing traffic flows to the data network. The DN 303 may represent various network operator services, internet access, or third-party services. The DN 303 may include or be similar to the application server 130 discussed previously. The UPF 302 may interact with the SMF 324 using the N4 reference point between the SMF 324 and the UPF 302.

[0065] In some examples, the UPF 302 supports a performance measurement function (PMF) that can be used by the UE 301 to obtain access performance measurements on the user plane of 3GPP accesses and / or on the user plane of non-3GPP accesses. For example, when the UE 301 requests to establish a multiple access protocol data unit (MA PDU) session and indicates that it can support access traffic steering, handover and splitting (ATSSS), the UE can receive measurement assistance information during the establishment of the MA PDU session. This information helps the UE determine which measurements should be performed on either or both accesses, and whether and when measurement reports should be sent to the network. The measurement assistance information can include, for example, the IP address and UDP port of the PMF in the UPF 302, which the UE 301 can use to send PMF protocol messages. Additional details on access network performance measurements are described in clause 5.32.5 of the 3GPP Technical Specification (TS) 23.501, which is incorporated herein by reference in its entirety.

[0066] In some examples, the following PMF protocol messages may be exchanged between the UE and the PMF: messages for round trip time (RTT) measurements (e.g., when "minimum delay" steering mode is used); and messages for reporting access availability / unavailability by the UE 301 to the UPF 302. In some examples, such as when the UE requests an MA PDU session and indicates that it can only support Multipath TCP (MPTCP) functionality, the network may not send measurement assistance information because the UE can use measurements available at the MPTCP layer.

[0067] The AUSF 322 stores data used for authentication of the UE 301 and handles authentication-related functions. The AUSF 322 can facilitate a common authentication framework for various access types. The AUSF 322 can communicate with the AMF 321 using the N12 reference point between the AMF 321 and the AUSF 322, and can communicate with the UDM 327 using the N13 reference point between the UDM 327 and the AUSF 322. In addition, the AUSF 322 can present an interface based on the NAUSF service.

[0068] AMF 321 is responsible for registration management (e.g., responsible for registering UE 301, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, as well as access authentication and authorization. AMF 321 can be the termination point of the N11 reference point between AMF 321 and SMF 324. AMF 321 can provide transport for SM messages between UE 301 and SMF 324 and act as a transparent proxy for routing SM messages. AMF 321 can also provide communication between UE 301 and SMS Function (SMSF) ( Figure 3301). The AMF 321 may provide transport for Short Message Service (SMS) messages between the (R)AN 310 and the UE 301 (not shown). The AMF 321 may act as a Security Anchor Function (SEAF), which may include interactions with the AUSF 322 and the UE 301 to, for example, receive intermediate keys established as a result of the UE 301 authentication process. In the case of Universal User Identity Module (UMTS) based authentication, the AMF 321 may retrieve security material from the AUSF 322. The AMF 321 may also include a Security Context Management (SCM) function that receives keys from the SEAF to derive access network specific keys. In addition, the AMF 321 may be a termination point for the RAN control plane interface, which may include or be the N2 reference point between the (R)AN 310 and the AMF 321. In some examples, the AMF 321 may be a termination point for NAS (N1) signaling and perform NAS encryption and integrity protection.

[0069] The AMF 321 may also support NAS signaling with the UE 301 over the N3 interworking function (IWF) interface (referred to as "N3IWF"). The N3IWF may be used to provide access to untrusted entities. The N3IWF may be the termination point for the N2 interface between the (R)AN 310 and the AMF 321 for the control plane, and may be the termination point for the N3 reference point between the (R)AN 310 and the UPF 302 for the user plane. Thus, the AMF 321 may process N2 signaling for PDU sessions and QoS from the SMF 324 and the AMF 321, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 301 and the AMF 321 using the N1 reference point between the UE 301 and the AMF 321, and relay uplink and downlink user plane packets between the UE 301 and the UPF 302. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 301. The AMF 321 may present an interface based on Namf services and may be an N14 reference point between two AMFs 321 and an N14 reference point between the AMF 321 and the 5G Equipment Identity Register (EIR) ( Figure 3 The termination point of the N17 reference point between the two reference points (not shown).

[0070] UE 301 can register with AMF 321 to receive network services. Registration Management (RM) is used to register UE 301 with the network (e.g., AMF 321) or deregister UE 301, and establish a UE context in the network (e.g., AMF 321). UE 301 can operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE 301 is not registered with the network, and the UE context in AMF 321 does not hold valid location or routing information of UE 301, so AMF 321 cannot reach UE 301. In the RM-REGISTERED state, UE 301 is registered with the network, and the UE context in AMF 321 can hold valid location or routing information of UE 301, so AMF 321 can reach UE 301. In the RM-REGISTERED state, UE 301 may perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (e.g., to inform the network that UE 301 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0071] The AMF 321 may store one or more RM contexts for the UE 301, where each RM context is associated with a specific access to the network. The RM context may be, for example, a data structure or a database object, etc., which indicates or stores the registration status and periodic update timer for each access type. The AMF 321 may also store a 5GC mobility management (MM) context, which may be the same as or similar to the (E)MM context discussed previously. In some examples, the AMF 321 may store the coverage enhancement mode B restriction parameters of the UE 301 in the associated MM context or RM context. The AMF 321 may also derive values ​​from the UE's usage setting parameters already stored in the UE context (and / or MM / RM context) when needed.

[0072] Connection Management (CM) can be used to establish and release signaling connections between the UE 301 and the AMF 321 over the N1 interface. Signaling connections are used to enable NAS signaling exchanges between the UE 301 and the CN 320, and include signaling connections between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and the UE 301's N2 connection between the AN (e.g., the RAN 310) and the AMF 321. In some examples, the UE 301 can operate in one of two CM modes: CM-IDLE mode or CM-CONNECTED mode. When the UE 301 operates in CM-IDLE mode, the UE 301 may not have a NAS signaling connection established with the AMF 321 over the N1 interface, and there may be a (R)AN 310 signaling connection for the UE 301 (e.g., an N2 or N3 connection, or both). When the UE 301 operates in the CM-CONNECTED mode, the UE 301 may have a NAS signaling connection established with the AMF 321 through the N1 interface, and there may be a (R)AN 310 signaling connection (e.g., N2 and / or N3 connection) for the UE 301. Establishing an N2 connection between the (R)AN 310 and the AMF 321 may cause the UE 301 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 310 and the AMF 321 is released, the UE 301 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0073] The SMF 324 may be responsible for session management (SM), such as session establishment, modification, and release, including tunnel maintenance between the UPF and AN nodes; UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering at the UPF to route traffic to the correct destination; terminating the interface towards the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with the LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to the AN via the AMF over N2; and determining the SSC mode for the session. SM may refer to the management of a PDU session, and a PDU session (or "session") may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 301 and the data network (DN) 303 identified by the data network name (DNN). A PDU session may be established upon request by UE 301, modified upon request by UE 301 and 5GC 320, and released upon request by UE 301 and 5GC 320 using NAS SM signaling exchanged between UE 301 and SMF 324 over the N1 reference point. Upon request from an application server, 5GC 320 may trigger a specific application in UE 301. In response to receiving the trigger message, UE 301 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 301. The identified applications in UE 301 may establish a PDU session to a specific DNN. SMF 324 may check whether the UE 301 request complies with user subscription information associated with UE 301. In this regard, SMF 324 may retrieve and / or request to receive update notifications regarding SMF 324-level subscription data from UDM 327.

[0074] The SMF 324 may include some or all of the following roaming functions: handling local execution to apply QoS service level agreements (SLAs) (e.g., in a VPLMN); charging data collection and charging interfaces (e.g., in a VPLMN); lawful interception (e.g., SM events and interfaces with LI systems in a VPLMN); and supporting interaction with external DNs to transport signaling for PDU session authorization / authentication over external DNs. An N16 reference point between two SMFs 324 may be included in the system 300, which in a roaming scenario may be between another SMF 324 in a visited network and an SMF 324 in a home network. In addition, the SMF 324 may present an interface based on Nsmf services.

[0075] The NEF 323 may provide components for securely exposing services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, application functions (e.g., AF 328), edge computing or fog computing systems, etc. In some examples, the NEF 323 uses a standardized interface (Nudr) of a unified data repository (UDR) to store / retrieve information as structured data, and the NEF 323 may authenticate, authorize, and / or restrict the AF.

[0076] NEF 323 can also convert information exchanged with AF 328 and information exchanged with internal network functions. For example, NEF 323 can convert between AF service identifiers and internal 5GC information. NEF 323 can also receive information from other network functions (NFs) based on the exposed capabilities of other NFs. This information can be stored at NEF 323 as structured data or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by NEF 323 to other NFs and AFs, or used for other purposes such as analysis, or both. In addition, NEF 323 can present an interface based on NNEF services.

[0077] Specifically, in some examples, NEF 323 handles masking of network and user sensitive information from external AFs (e.g., AF 328) based on network policy. NEF 323 may also support a Packet Flow Description (PFD) function that can store and retrieve PFDs from UDRs and provide PFDs to SMF 324 upon request by SMF 324 (sometimes referred to as "pull mode") or upon requesting PFD management from NEF 328 (sometimes referred to as "push mode"), as described in 3GPP TS 23.503, the entire contents of which are incorporated herein by reference.

[0078] In some examples, NEF 323 provides a means for AF 328 to securely provide information (e.g., expected UE behavior, 5G LAN group information, or service-specific information, or a combination thereof, among other information) to the 3GPP network. In this example, NEF can authenticate and authorize AF 328 and help restrict the AF.

[0079] In some examples, NEF 323 may provide one or a combination of two or more of the functions or services summarized below in Table 1 and described in 3GPP TS 23.502, the entire contents of which are incorporated herein by reference.

[0080] Table 1: Example NF services provided by NEF

[0081]

[0082] NRF 325 can support service discovery functionality, receiving NF discovery requests from NF instances and providing information about discovered NF instances to NF instances. NRF 325 also maintains information about available NF instances and the services supported by these instances. As used herein, the term "instantiation" and the like can refer to the creation of an instance, and "instance" can refer to the specific occurrence of an object, which can occur, for example, during the execution of program code. In addition, NRF 325 can present an interface based on Nnrf services.

[0083] Typically, an NF can provide different capabilities and, therefore, different NF services to different consumers. An NF service is a capability that an NF (e.g., an NF service producer) exposes to another authorized NF (e.g., an NF service consumer) via a service-based interface. An NF can expose one or more NF services. Each NF service provided by an NF is self-contained, reusable, and uses a management solution that is independent of other NF services provided by the same NF (e.g., for scaling, repair, etc.). A consumer who has already selected an NF service instance within an NF instance can reselect another service instance of the same NF service within the same NF instance and obtain the same results as using the originally selected NF service instance. If a service consumer is unable to contact the original NF service instance, reselection may be necessary.

[0084] In some examples, each NF service is accessible through an interface. The interface includes one or more operations. NF services can communicate directly between the NF service consumer and the NF service producer, or indirectly via a service communication proxy (SCP). Whether the NF service consumer uses direct communication or indirect communication can be based on the configuration of the NF service consumer. In direct communication, the NF service consumer performs discovery of the target NF service producer through local configuration or via NRF. The NF service consumer then communicates directly with the target NF service producer. In indirect communication, the NF service consumer communicates with the target NF service producer via the SCP. The NF service consumer can be configured to directly perform discovery of the target NF service producer, or to delegate discovery of the target NF service producer to the SCP for indirect communication. In the latter case, the SCP uses parameters provided by the NF service consumer to perform discovery and / or selection of the target NF service producer. The SCP address can be configured in the NF service consumer or locally by the NF service consumer.

[0085] In some examples, if the endpoint address provided by the NF Service Producer points to a specific target NF Producer / NF Service Producer instance within a set, the NF Consumer or SCP can reselect another service instance of the same NF Service within the same NF Service Set within the same NF Instance, or another NF Instance within the same NF Set for subsequent transactions, and achieve the same result as using the originally selected NF Service Instance. For example, reselection can be used if the requester NF is unable to contact the original NF Service Instance. If the endpoint address provided by the NF Service Producer points to an NF Set or NF Service Set, the NF Consumer or SCP is allowed to reselect a different NF Service Instance of the same NF Service within the same Set for the UE and its subsequent transactions. System programs can be constructed by invoking many NF Services (e.g., as specified in 3GPP TS 23.502).

[0086] The PCF 326 can provide control plane functions with the ability to enforce their policy rules and can also support a unified policy framework for managing network behavior. The PCF 326 can also implement a front-end for accessing subscription information related to policy decisions in the Unified Data Repository (UDR) of the UDM 327. The PCF 326 can communicate with the AMF 321 using the N15 reference point between the PCF 326 and the AMF 321, which can include the PCF 326 in the visited network and the AMF 321 in roaming scenarios. The PCF 326 can communicate with the AF 328 using the N5 reference point between the PCF 326 and the AF 328; and with the SMF 324 using the N7 reference point between the PCF 326 and the SMF 324. The system 300 or the CN 320 or both can also include an N24 reference point between the PCF 326 (in the home network) and the PCF 326 in the visited network. Additionally, PCF 326 may present an interface based on Npcf services.

[0087] The UDM 327 may process subscription-related information to support network entities in handling communication sessions and may store subscription data for the UE 301. For example, the subscription data may be transferred between the UDM 327 and the AMF 321 using the N8 reference point between the UDM 327 and the AMF. The UDM 327 may include two parts: the application front end and the UDR ( Figure 3(The front end and UDR are not shown.) The UDR may store subscription data and policy data for the UDM 327 and PCF 326, or structured data for exposure and application data (including PFD for application detection, application request information of multiple UEs 301) of the NEF 323, or both. An interface based on Nudr services may be presented by the UDR 221 to allow the UDM 327, PCF 326, and NEF 323 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of changes to relevant data in the UDR. The UDM may include a UDM front end, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends may serve the same user. The UDM front end accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, registration / mobility management, and subscription management. The UDR may interact with the SMF 324 using the N10 reference point between the UDM 327 and the SMF 324. UDM 327 may also support SMS management, where the SMS front end implements application logic similar to that discussed previously. Additionally, UDM 327 may present an interface based on Nudm services.

[0088] AF 328 can provide application influence on traffic routing, provide access to Network Capability Exposure (NCE), and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC 320 and AF 328 to provide information to each other using NEF 323, which can be used in edge computing implementations. In such implementations, network operators and third-party services can be hosted near the UE 301 access point to achieve efficient service delivery with reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC can select a UPF 302 near the UE 301 and perform traffic steering from the UPF 302 to the DN 303 using the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 328. In this way, AF 328 can influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 328 is considered a trusted entity, the network operator may allow AF 328 to interact directly with relevant NFs. In addition, AF 328 can present an interface based on NAF services.

[0089] The NSSF 329 may select a set of network slice instances to serve the UE 301. If required, the NSSF 329 may also determine the allowed NSSAIs and the mapping to the subscribed single network slice selection assistance information (S-NSSAI). The NSSF 329 may also determine the set of AMFs to serve the UE 301, or a list of candidate AMFs 321, based on appropriate configuration and possibly by querying the NRF 325. The selection of a set of network slice instances for the UE 301 may be triggered by the AMF 321, where the UE 301 registers by interacting with the NSSF 329, which may result in a change in the AMF 321. The NSSF 329 may interact with the AMF 321 using the N22 reference point between the AMF 321 and the NSSF 329; and may interact with the AMF 321 using the N31 reference point ( Figure 3 The NSSF 329 may communicate with another NSSF 329 in the visited network (not shown). In addition, the NSSF 329 may present an interface based on the Nnssf service.

[0090] As previously discussed, CN 320 may include an SMSF that may be responsible for SMS subscription checking and verification, and relaying SM messages to or from UE 301 to or from other entities, such as SMS-GMSC / IWMSC / SMS routers. SMS may also interact with AMF 321 and UDM 327 for notification procedures that UE 301 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 327 when UE 301 is available for SMS).

[0091] CN 120 may also include Figure 3 Other elements not shown include data storage system, 5G-EIR, security edge protection agent (SEPP), etc. The data storage system may include structured data storage function (SDSF), unstructured data storage function (UDSF), or both. Any network function can utilize any NF and UDSF ( Figure 3 The N18 reference point between the UE and UE contexts (not shown) stores or retrieves unstructured data to or from the UDSF (e.g., UE context). Each network function may share a UDSF for storing its respective unstructured data, or each network function may have its own UDSF located at or near each network function. In addition, the UDSF may present an interface based on Nudsf services ( Figure 3 (Not shown). The 5G-EIR may be a network function that checks the status of the Permanent Equipment Identifier (PEI) to determine whether to blacklist a particular equipment or entity from the network.

[0092] The SEPP can be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface. The SEPP protects the connection between service consumers and service producers from a security perspective. For example, the SEPP does not duplicate the service authorization applied by the service producer, as specified in clause 7.1.4 of 3GPP TS 23.501. 3GPP TS 33.501 specifies the detailed functionality of the SEPP, related flows, and the N32 reference point. In some examples, the SEPP applies the aforementioned functionality to every control plane message in inter-PLMN signaling, acting as a service relay between the actual service producer and the actual service consumer. For both service producer and consumer, the result of service relay is equivalent to a direct service interaction. Every control plane message in inter-PLMN signaling between SEPPs can be delivered via the IPX entity. Further details regarding the SEPP and IPX entities are described in 3GPP TS 33.501 and TS 29.500, the entire contents of each of which are incorporated herein by reference.

[0093] In some examples, there may be additional or alternative reference points or service-based interfaces or both between network function services in a network function. However, for clarity, Figure 3 These interfaces and reference points are omitted. In one example, CN 320 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 221) and an AMF 321, to enable intercommunication between CN 320 and CN 220. Other exemplary interfaces or reference points may include an interface based on N5g-EIR services presented by 5G-EIR, an N27 reference point between an NRF in a visited network and an NRF in a home network, or an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0094] Figure 4 An example of infrastructure equipment 400 is shown. Infrastructure equipment 400 (or "system 400") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 111 or AP 106 shown and described previously), an application server 130, or any other component or device described herein. In other examples, system 400 can be implemented in or by a UE.

[0095] System 400 includes application circuitry 405, baseband circuitry 410, one or more radio front-end modules (RFEMs) 415, memory circuitry 420, a power management integrated circuit (PMIC) 425, power tee circuitry 430, network controller circuitry 435, a network interface connector 440, satellite positioning circuitry 445, and user interface circuitry 450. In some examples, system 400 may include additional components such as, for example, memory, storage, a display, a camera, one or more sensors, or input / output (I / O) interfaces, or a combination thereof. In other examples, the components described with reference to system 400 may be included in more than one device. For example, various circuits may be separately included in more than one device for a CRAN, vBBU, or other implementation.

[0096] Application circuitry 405 may include circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a general-purpose programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, general-purpose input / output (I / O or IO), a memory card controller such as a secure digital (SD) multimedia card (MMC) or similar product, a universal serial bus (USB) interface, a mobile industry processor interface (MIPI) interface, and a joint test access group (JTAG) test access port. The processor (or core) of application circuitry 405 may be coupled to or may include a memory or storage element and may be configured to execute instructions stored in the memory or storage element to enable various applications or operating systems to run on system 400. In some examples, the memory or storage element may include on-chip memory circuitry, which may include any suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, or a combination thereof.

[0097] The processor of the application circuit 405 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or a combination thereof. In some examples, the application circuit 405 may include or may be a dedicated processor or controller configured to perform various techniques described herein. As an example, the processor of the application circuit 405 may include one or more Apple A series processors, Intel or Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU), or processors; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some examples, system 400 may not utilize application circuit 405 and instead may include a dedicated processor or controller to process IP data received, for example, from an EPC or 5GC.

[0098] In some examples, the application circuit 405 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) or deep learning (DL) accelerators, or both. In some examples, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs); programmable logic devices (PLDs), such as complex PLDs (CPLDs) or high-capacity PLDs (HCPLDs); ASICs, such as structured ASICs; programmable SoCs (PSoCs), or combinations thereof. In such implementations, the circuitry of the application circuit 405 may include logic blocks or logic fabrics, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, and functions described herein. In some examples, the circuitry of application circuit 405 may 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) or antifuse)) for storing logic blocks, logic structures, data, or other data in a lookup table (LUT), etc.

[0099] The baseband circuit 410 may be implemented, for example, as a solder-in 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. Figure 6 Various hardware electronic components of the baseband circuit 410 are discussed.

[0100] The user interface circuitry 450 may include one or more user interfaces designed to enable a user to interact with the system 400 or a peripheral component interface designed to enable a peripheral component to interact with the system 400. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio emitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, or a combination thereof. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power port, etc.

[0101] The radio front end module (RFEM) 415 may include a millimeter wave (mmWave) RFEM and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some examples, the one or more sub-mmWave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., Figure 6The antenna array 611 is a RFEM that can be connected to multiple antennas. In some examples, both mmWave and sub-millimeter-wave radio functionality can be implemented in the same physical RFEM 415 that combines both mmWave antennas and sub-millimeter-wave antennas.

[0102] The memory circuit 420 may include one or more of the following: volatile memory, such as dynamic random access memory (DRAM) or synchronous dynamic random access memory (SDRAM); and non-volatile memory (NVM), such as high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), or magnetoresistive random access memory (MRAM), or a combination thereof. In some examples, the memory circuit 420 may include a memory device obtained from and For example, the memory circuit 420 may be implemented as one or more of the following: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0103] The PMIC 425 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as batteries or capacitors. The power alarm detection circuit may detect one or more of a brownout (undervoltage) and a surge (overvoltage) condition. The power tee circuit 430 may provide power drawn from the network cable to provide both power and data connectivity for the infrastructure equipment 400 using a single cable.

[0104] The network controller circuitry 435 can provide connectivity to the network using a standard network interface protocol such as Ethernet, Ethernet based on GRE tunnels, Ethernet based on Multi-Protocol Label Switching (MPLS), or some other suitable protocol. Network connectivity can be provided to and from the infrastructure equipment 400 using a physical connection utilizing the network interface connector 440, which can be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuitry 435 may include one or more dedicated processors or FPGAs, or both, for communicating using one or more of the aforementioned protocols. In some examples, the network controller circuitry 435 may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0105] Positioning circuitry 445 includes circuitry for receiving and decoding signals transmitted or broadcast by a global navigation satellite system (GNSS) positioning network. Examples of GNSS include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems, or GNSS augmentation systems (e.g., navigation using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), and France's Doppler Orbit Chart and Satellite Integrated Radiolocation (DORIS)). Positioning circuitry 445 may include various hardware components (e.g., hardware devices to facilitate over-the-air (OTA) communication, such as switches, filters, amplifiers, and antenna elements) to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some examples, positioning circuitry 445 may include a micro-technology (micro-PNT) IC for positioning, navigation, and timing, which uses a master timing clock to perform position tracking and estimation without GNSS assistance. Positioning circuitry 445 may also be part of or interact with baseband circuitry 410 or RFEM 415, or both, to communicate with nodes and components of the positioning network. The positioning circuitry 445 may also provide data (eg, position data, time data) to the application circuitry 405 , which may use the data to synchronize operations with various infrastructure (eg, the RAN node 111 , etc.).

[0106] Figure 4 The components shown can communicate with each other using interface circuitry that can include any number of bus 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 or IX can be a proprietary bus, such as used in SoC-based systems. Other bus or IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, among others.

[0107] Figure 5 An example of a platform 500 (or "device 500") is shown. In some examples, computer platform 500 may be suitable for use as UE 101, 201, 301, application server 130, or any other component or device discussed herein. Platform 500 may include any combination of the components shown in the examples. The components (or portions thereof) of platform 500 may be implemented as integrated circuits (ICs), discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 500, or as components otherwise incorporated within the chassis of a larger system. Figure 5The block diagram is intended to illustrate a high-level view of the components of platform 500. However, in some examples, platform 500 may include fewer, additional, or alternative components, or include Figure 5 Different arrangements of components are shown.

[0108] Application circuit 505 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of: one or more LDOs, an interrupt controller, a serial interface (such as SPI), I2C or a general-purpose programmable serial interface module, an RTC, a timer-counter (including an interval timer and a watchdog timer), general-purpose I / O, a memory card controller (such as an SD MMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of application circuit 505 may be coupled to or include a memory / storage element and may be configured to execute instructions stored in the memory or storage device to enable various applications or operating systems to run on system 500. In some examples, the memory or storage element may be an on-chip memory circuit that may include any suitable volatile or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, or a combination thereof.

[0109] The processor of application circuit 405 may 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 DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multi-threaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some examples, application circuit 405 may include or may be a dedicated processor / controller for executing the techniques described herein.

[0110] As an example, the processor of the application circuit 505 may include an Apple A series processor. The processor of the application circuit 1105 may also be one or more of the following: Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU class processors, or available from Santa Clara, CA company Another such processor is from Intel Corporation, Santa Clara, CA; Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Snapdragon by Technologies, Inc. TM processors, Texas Instruments, Open Multimedia ApplicationsPlatform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some examples, application circuit 505 can be part of a system on a chip (SoC), in which application circuit 505 and other components are formed as a single integrated circuit or a single package.

[0111] Additionally or alternatively, the application circuit 505 may include circuitry such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs); ASICs such as structured ASICs; programmable SoCs (PSoCs), or combinations thereof. In some examples, the application circuit 505 may include logic blocks or logic fabrics, as well as other interconnected resources that can be programmed to perform various functions, such as the processes, methods, and functions described herein. In some examples, the application circuit 505 may 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), or antifuse)) for storing the logic blocks, logic fabrics, data, or other data in a lookup table (LUT).

[0112] The baseband circuit 510 may be implemented, for example, as a solder-in 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. Figure 6 The various hardware electronic components of baseband circuit 510 are discussed.

[0113] The RFEM 515 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some examples, the one or more sub-millimeter wave RFICs may be physically separate from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., Figure 6 The antenna array 611 is a RFEM that can be connected to multiple antennas. In some examples, both mmWave and sub-millimeter-wave radio functionality can be implemented in the same physical RFEM 515 that combines both mmWave antennas and sub-millimeter-wave antennas.

[0114] Memory circuit 520 may include any number and type of memory devices used to provide a fixed amount of system memory. By way of example, memory circuit 520 may include one or more of the following: volatile memory, such as random access memory (RAM), dynamic RAM (DRAM), or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), such as high-speed electrically erasable memory (commonly referred to as flash memory), phase-change random access memory (PRAM), or magnetoresistive random access memory (MRAM), or a combination thereof. Memory circuit 520 may be developed according to Joint Electron Device Engineering Council (JEDEC) low-power double data rate (LPDDR)-based designs, such as LPDDR2, LPDDR3, or LPDDR4. Memory circuit 520 may be implemented as one or more of the following: a solder-in packaged integrated circuit, a single die package (SDP), a dual die package (DDP), or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM), including a micro DIMM or mini DIMM, or soldered to a motherboard using a ball grid array (BGA). In a low-power implementation, the memory circuit 520 may be an on-chip memory or register associated with the application circuit 505. To provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 520 may include one or more mass storage devices, which may include, for example, a solid-state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. In some examples, the computer platform 500 may be combined with a computer obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0115] Removable memory circuitry 523 may include devices, circuitry, housings, casings, ports or receptacles, etc., for coupling portable data storage devices to platform 500. These portable data storage devices may be used for mass storage and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards), as well as USB flash drives, optical disks, or external HDDs, or combinations thereof.

[0116] Platform 500 may also include an interface circuit (not shown) for connecting external devices to platform 500. External devices connected to platform 500 using the interface circuit include sensor circuit 521 and electromechanical components (EMC) 522, and a removable memory device coupled to removable memory circuit 523.

[0117] Sensor circuitry 521 includes devices, modules, or subsystems whose purpose is to detect events or changes in its environment and to send information about the detected events (e.g., sensor data) to one or more other devices, modules, or subsystems. Examples of such sensors include: an inertial measurement unit (IMU), such as an accelerometer, gyroscope, or magnetometer; a microelectromechanical system (MEMS) or nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, or a magnetometer; a liquid level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other audio capture device, or a combination thereof, etc.

[0118] The EMC 522 includes devices, modules, or subsystems designed to enable the platform 500 to change its state, position, or orientation, or to move or control mechanisms, systems, or subsystems. Additionally, the EMC 522 can be configured to generate and send messages or signaling to other components of the platform 500 indicating the current state of the EMC 522. Examples of EMC 522 include, among other electromechanical components, one or more power switches, relays (such as electromechanical relays (EMRs) or solid-state relays (SSRs)), actuators (e.g., valve actuators), audible sound generators, visual warning devices, motors (e.g., DC motors or stepper motors), wheels, thrusters, propellers, claws, clamps, hooks, or combinations thereof. In some examples, the platform 500 is configured to operate one or more EMCs 522 based on one or more capture events, instructions, or control signals received from a service provider, a client, or both.

[0119] In some examples, the interface circuitry may connect the platform 500 to the positioning circuitry 545. The positioning circuitry 545 includes circuitry for receiving and decoding signals transmitted or broadcast by a GNSS positioning network. Examples of GNSS systems may include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., NAVIC), Japan's QZSS, France's DORIS, and others. The positioning circuitry 545 includes various hardware components (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating over-the-air (OTA) communications) to communicate with components of the positioning network, such as navigation satellite constellation nodes. In some examples, the positioning circuitry 545 may include a micro PNT IC that uses a master timing clock to perform position tracking or estimation without GNSS assistance. The positioning circuitry 545 may also be part of or interact with the baseband circuitry 410 or RFEM 515, or both, to communicate with nodes and components of the positioning network. Positioning circuitry 545 may also provide data (eg, position data, time data) to application circuitry 505 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for turn-by-turn navigation applications, and the like.

[0120] In some examples, the interface circuitry can connect the platform 500 to a near-field communication (NFC) circuitry 540. The NFC circuitry 540 is configured to provide contactless, short-range communication based on the radio frequency identification (RFID) standard, where magnetic field induction is used to enable communication between the NFC circuitry 540 and an NFC-enabled device (e.g., an "NFC touchpoint") external to the platform 500. The NFC circuitry 540 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller can be a chip or IC that provides NFC functionality to the NFC circuitry 540 by executing NFC controller firmware and an NFC stack. The NFC stack can be executed by the processor to control the NFC controller, and the NFC controller firmware can be executed by the NFC controller to control the antenna element to transmit short-range RF signals. The RF signals can power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuitry 540, or initiate data transfer between the NFC circuitry 540 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) in close proximity to the platform 500.

[0121] Driver circuitry 546 may include software and hardware components for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to platform 500. Driver circuitry 546 may include various drivers to allow other components of platform 500 to interact with or control various input / output (I / O) devices that may be present within or connected to platform 500. For example, driver circuitry 546 may include a display driver for controlling and enabling access to a display device, a touch screen driver for controlling and enabling access to a touch screen interface of platform 500, a sensor driver for acquiring sensor readings from sensor circuitry 521 and controlling and enabling access to sensor circuitry 521, an EMC driver for acquiring actuator positions of EMC 522 or controlling and enabling access to EMC 522, a camera driver for controlling and enabling access to an embedded image capture device, and an audio driver for controlling and enabling access to one or more audio devices.

[0122] A power management integrated circuit (PMIC) 525 (also referred to as "power management circuit 525") can manage the power provided to various components of the platform 500. Specifically, the PMIC 525 can control power source selection, voltage scaling, battery charging, or DC-DC conversion with respect to the baseband circuit 510. The PMIC 525 can be included when the platform 500 is capable of being powered by a battery 530, for example, when the device is included in a UE 101, 201, or 301.

[0123] In some examples, the PMIC 525 can control or otherwise be part of various power-saving mechanisms of the platform 500. For example, if the platform 500 is in the RRC_Connected state, in which it remains connected to the RAN node because it expects to receive traffic soon, after a period of inactivity, the platform can enter a state known as discontinuous reception mode (DRX). During this state, the platform 500 can be powered down for short intervals, thereby saving power. If there is no data traffic activity for a longer period of time, the platform 500 can transition to the RRC_Idle state, in which it is disconnected from the network and does not perform operations such as channel quality feedback or handovers. This can allow the platform 500 to enter a very low-power state in which it periodically wakes up to listen to the network and then powers down again. In some examples, the platform 500 may not receive data in the RRC_Idle state and must transition back to the RRC_Connected state to receive data. Additional power-saving modes can prevent a device from using the network for periods exceeding the paging interval (ranging from a few seconds to several hours). During this period, the device may be unable to connect to the network and may be completely powered down. Any data sent during this period may be significantly delayed, and it is assumed that the delay is acceptable.

[0124] Battery 530 can power platform 500, but in some examples, platform 500 can be deployed in a fixed location and can have a power source coupled to the power grid. Battery 530 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, or a lithium-air battery. In some examples, such as in V2X applications, battery 530 can be a typical lead-acid automobile battery.

[0125] In some examples, the battery 530 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 500 to track the state of charge (SoCh) of the battery 530. The BMS may be used to monitor other parameters of the battery 530, such as the state of health (SoH) and state of function (SoF) of the battery 530 to provide fault prediction. The BMS may transmit information about the battery 530 to the application circuit 505 or other components of the platform 500. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 505 to directly monitor the voltage of the battery 530 or the current from the battery 530. The battery parameters may be used to determine actions that the platform 500 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0126] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 530. In some examples, the power block 530 can be replaced with a wireless power receiver to wirelessly obtain power, for example, via a loop antenna in the computer platform 500. In these examples, wireless battery charging circuitry can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 530 and, therefore, the required current. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Consortium, or the Rezence charging standard published by the Wireless Power Consortium.

[0127] The user interface circuit 550 includes various input / output (I / O) devices present in or connected to the platform 500, and includes one or more user interfaces designed to implement user interaction with the platform 500 or peripheral component interfaces designed to implement interaction with peripheral components of the platform 500. The user interface circuit 550 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a trackpad, a touch screen, a microphone, a scanner, or a headset, or a combination thereof. The output device circuit includes any physical or virtual means for displaying information or otherwise communicating information (such as sensor readings, actuator positions, or other information). The output device circuitry may include any number or combination of audio or visual displays, including one or more simple visual outputs or indicators (e.g., binary state indicators (e.g., light emitting diodes (LEDs))), multi-character visual outputs, or more complex outputs, such as a display device or touch screen (e.g., a liquid crystal display (LCD), an LED display, a quantum dot display, or a projector), where the output of characters, graphics, or multimedia objects is generated or produced by the operation of platform 500. The output device circuitry may also include a speaker or other audio emitting device, or a printer. In some examples, sensor circuitry 521 may function as an input device circuit (e.g., an image capture device or a motion capture device) and one or more EMCs may function as output device circuitry (e.g., an actuator for providing tactile feedback). In another example, NFC circuitry may be included to read an electronic tag or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, or a power port.

[0128] Although not shown, the components of the platform 500 can communicate with each other using a suitable bus or interconnect (IX) technology, which can include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus or IX can be a proprietary bus or IX, such as used in a SoC-based system. Other bus or IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, among others.

[0129] Figure 6 Exemplary components of a baseband circuit 610 and a radio front end module (RFEM) 615 are shown. The baseband circuit 610 may correspond to Figure 4 The baseband circuit 410 and Figure 5The baseband circuit 510. RFEM 615 may correspond to Figure 4 RFEM415 and Figure 5 RFEM 515. As shown, RFEM 615 may include a radio frequency (RF) circuit 606, a front end module (FEM) circuit 608, and an antenna array 611 coupled together.

[0130] The baseband circuitry 610 includes circuitry or control logic components, or both, configured to execute various radio or network protocols and control functions that enable communication with one or more radio networks using the RF circuitry 606. The radio control functions may include, but are not limited to, signal modulation and demodulation, encoding and decoding, and radio frequency shifting. In some examples, the modulation and demodulation circuitry of the baseband circuitry 610 may include fast Fourier transform (FFT), precoding or constellation mapping and demapping functions. In some examples, the encoding and decoding circuitry of the baseband circuitry 610 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder and decoder functions. The modulation and demodulation and encoder and decoder functions are not limited to these examples and may include other suitable functions in other examples. The baseband circuitry 610 is configured to process baseband signals received from the receive signal path of the RF circuitry 606 and to generate baseband signals for the transmit signal path of the RF circuitry 606. The baseband circuitry 610 is configured to communicate with application circuitry (e.g., Figure 4 and Figure 5 Application circuits 405 and 505 are shown interacting to generate and process baseband signals and control the operation of RF circuitry 606. Baseband circuitry 610 may handle various radio control functions.

[0131] The aforementioned circuits and control logic components of the baseband circuit 610 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 604A, a 4G or LTE baseband processor 604B, a 5G or NR baseband processor 604C, or some other baseband processor 604D for other existing generations, generations under development, or generations to be developed in the future (e.g., the sixth generation (6G)). In some examples, some or all of the functionality of the baseband processors 604A-D may be included in modules stored in the memory 604G and executed using the central processing unit (CPU) 604E. In some examples, some or all of the functionality of the baseband processors 604A-D may be provided as hardware accelerators (e.g., FPGAs or ASICs) loaded with appropriate bitstreams or logic blocks stored in corresponding memory units. In some examples, the memory 604G may store program code of a real-time OS (RTOS), which, when executed by the CPU 604E (or other baseband processor), enables the CPU 604E (or other baseband processor) to manage resources of the baseband circuit 610, schedule tasks, or perform other operations. Examples of RTOS may include Operating System Embedded (OSE) TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-Time Executive (VRTX) provided by Express ThreadX TM ,Depend on FreeRTOS and REX OS provided by OpenKernel (OK) The provided OKL4, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 610 includes one or more audio digital signal processors (DSPs) 604F. The audio DSPs 604F include elements for compression and decompression and echo cancellation, and in some examples may include other suitable processing elements.

[0132] In some examples, each of processors 604A-604E includes a corresponding memory interface to send data to and receive data from memory 604G. Baseband circuit 610 may also include one or more interfaces for communicatively coupling to other circuits or devices, such as an interface for sending data to and receiving data from a memory external to baseband circuit 610; an interface for sending data to and receiving data from a memory external to baseband circuit 610; Figure 4 and Figure 6Application circuit interface for sending data to and receiving data from the application circuit 405, 505; Figure 6 RF circuit 606 to send data and receive data from the RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data and receive data from these wireless hardware elements; and a power management interface for sending power or control signals to the PMIC 525 and receiving power or control signals from the PMIC.

[0133] In some examples (which may be combined with the above examples), the baseband circuit 610 includes one or more digital baseband systems that are coupled to each other and to the CPU subsystem, audio subsystem, and interface subsystem using an interconnect subsystem. The digital baseband subsystem may also be coupled to a digital baseband interface and a mixed-signal baseband subsystem using another interconnect subsystem. Each of the interconnect subsystems may include a bus system, a point-to-point connection, a network-on-chip (NOC) structure, or some other suitable bus or interconnect technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and the like. In some examples, the baseband circuit 610 may include a protocol processing circuit having one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit or the radio frequency circuit (e.g., the radio front-end module 615).

[0134] although Figure 6Not shown, but in some examples, baseband circuitry 610 includes various processing devices (e.g., a "multi-protocol baseband processor" or "protocol processing circuitry") for operating one or more wireless communication protocols and various processing devices for implementing PHY layer functions. In some examples, the PHY layer functions include the aforementioned radio control functions. In some examples, the protocol processing circuitry operates or implements various protocol layers or entities of one or more wireless communication protocols. For example, when baseband circuitry 610 or RF circuitry 606 or both are part of millimeter wave communication circuitry or some other suitable cellular communication circuitry, the protocol processing circuitry may operate LTE protocol entities or 5G NR protocol entities or both. In this example, the protocol processing circuitry may operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In some examples, when baseband circuitry 610 or RF circuitry 606 or both are part of a Wi-Fi communication system, the protocol processing circuitry may operate one or more IEEE-based protocols. In this example, the protocol processing circuitry may operate Wi-Fi MAC and Logical Link Control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 604G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuitry 610 may also support radio communications for more than one wireless protocol.

[0135] The various hardware elements of the baseband circuit 610 discussed herein may be implemented as, for example, a solder-in substrate comprising one or more integrated circuits (ICs), a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module comprising two or more ICs. In some examples, the components of the baseband circuit 610 may be appropriately combined in a single chip or a single chipset, or provided on the same circuit board. In some examples, some or all of the components of the baseband circuit 610 and the RF circuit 606 may be implemented together, such as, for example, a system on a chip (SoC) or a system-in-package (SiP). In some examples, some or all of the components of the baseband circuit 610 may be implemented as a separate SoC communicatively coupled to the RF circuit 606 (or multiple instances of the RF circuit 606). In some examples, some or all of the components of the baseband circuit 610 and the application circuits 405, 505 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").

[0136] In some examples, baseband circuitry 610 can provide communications compatible with one or more radio technologies. For example, baseband circuitry 610 can support communications with E-UTRAN or other WMANs, WLANs, or WPANs. Examples in which baseband circuitry 610 is configured to support radio communications for more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0137] RF circuitry 606 can use modulated electromagnetic radiation to communicate with a wireless network through a non-solid medium. In some examples, RF circuitry 606 can include components such as switches, filters, or amplifiers to facilitate communication with the wireless network. RF circuitry 606 can include a receive signal path that can include circuitry for downconverting RF signals received from FEM circuitry 608 and providing baseband signals to baseband circuitry 610. RF circuitry 606 can also include a transmit signal path that can include circuitry for upconverting baseband signals provided by baseband circuitry 610 and providing an RF output signal to FEM circuitry 608 for transmission.

[0138] The receive signal path of RF circuitry 606 includes mixer circuitry 606a, amplifier circuitry 606b, and filter circuitry 606c. In some examples, the transmit signal path of RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a. RF circuitry 606 also includes synthesizer circuitry 606d for synthesizing frequencies for use by mixer circuitry 606a in the receive and transmit signal paths. In some examples, mixer circuitry 606a in the receive signal path may be configured to downconvert the RF signal received from FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d. Amplifier circuitry 606b may be configured to amplify the downconverted signal, and filter circuitry 606c may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the downconverted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuitry 610 for further processing. In some examples, the output baseband signal can be a zero-frequency baseband signal, although this is not required.In some examples, the mixer circuit 606a of the receive signal path can include a passive mixer.

[0139] In some examples, mixer circuit 606a of the transmit signal path can be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 606d to generate an RF output signal for FEM circuit 608. The baseband signal can be provided by baseband circuit 610 and can be filtered by filter circuit 606c.

[0140] In some examples, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some examples, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some examples, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some examples, the mixer circuit 606a of the receive signal path and the mixer circuit 606a of the transmit signal path may be configured for superheterodyne operation.

[0141] In some examples, the output baseband signal and the input baseband signal can be analog baseband signals. In some examples, the output baseband signal and the input baseband signal can be electronic baseband signals, and the RF circuit 606 can include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and the baseband circuit 610 can include a digital baseband interface to communicate with the RF circuit 606.

[0142] In some dual-mode examples, separate radio IC circuitry may be provided to process signals for each spectrum, but the techniques described herein are not limited in this respect.

[0143] In some examples, synthesizer circuit 606d can be a fractional-N synthesizer or a fractional-N / N+1 synthesizer, although other types of frequency synthesizers can be used. For example, synthesizer circuit 606d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0144] Synthesizer circuit 606d can be configured to synthesize an output frequency based on the frequency input and the divider control input for use by mixer circuit 606a of RF circuit 606. In some examples, synthesizer circuit 606d can be a fractional-N / N+1 synthesizer.

[0145] In some examples, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by baseband circuitry 610 or application circuitry 405 / 505 depending on the desired output frequency. In some examples, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by application circuitry 405, 505.

[0146] The synthesizer circuit 606d of the RF circuit 606 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some examples, the frequency divider may be a dual-modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some examples, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some examples, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. The delay elements may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0147] In some examples, the synthesizer circuit 606 d can be configured to generate a carrier frequency as the output frequency, while in other examples, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some examples, the output frequency can be an LO frequency (fLO). In some examples, the RF circuit 606 can include an IQ or polarity converter.

[0148] FEM circuitry 608 may include a receive signal path that may include circuitry configured to operate on RF signals received from antenna array 611, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 606 for further processing. FEM circuitry 608 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by RF circuitry 606 for transmission by one or more antenna elements in antenna array 611. Amplification by either the transmit signal path or the receive signal path may be performed only in RF circuitry 606, only in FEM circuitry 608, or in both RF circuitry 606 and FEM circuitry 608.

[0149] In some examples, the FEM circuitry 608 may include a TX / RX switch to switch between transmit and receive modes of operation. The FEM circuitry 608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 608 may include an LNA to amplify a received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) for amplifying an input RF signal (e.g., provided by the RF circuitry 606), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 611.

[0150] Antenna array 611 includes one or more antenna elements, each configured to convert electrical signals into radio waves for travel through the air and to convert received radio waves into electrical signals. For example, a digital baseband signal provided by baseband circuitry 610 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted using antenna elements of antenna array 611, which includes one or more antenna elements (not shown). Antenna elements can be omnidirectional, directional, or a combination thereof. Antenna elements can be formed into various arrangements as known and / or discussed herein. Antenna array 611 can include microstrip antennas or printed antennas fabricated on the surface of one or more printed circuit boards. Antenna array 611 can be formed as patches of metal foil of various shapes (e.g., patch antennas) and can be coupled to RF circuitry 606 and / or FEM circuitry 608 using metal transmission lines, etc.

[0151] The processors of the application circuitry 405 / 505 and the processor of the baseband circuitry 610 may be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuitry 610 may be used, alone or in combination, to perform layer 3, layer 2, or layer 1 functions, while the processors of the application circuitry 405, 505 may utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include the RRC layer, which is described in further detail below. As mentioned herein, layer 2 may include the MAC layer, the RLC layer, and the PDCP layer, which are described in further detail below. As mentioned herein, layer 1 may include the PHY layer of the UE / RAN node, which is described in further detail below.

[0152] Figure 7 1 shows exemplary components of the communication circuit 700. In some examples, the communication circuit 700 may be implemented as Figure 4 and Figure 5 The communication circuit 700 is a portion of the system 400 or platform 500 shown. The communication circuit 700 can be communicatively coupled (e.g., directly or indirectly) to one or more antennas, such as antennas 702a-c. In some examples, the communication circuit 700 includes or is communicatively coupled to dedicated receive chains for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR), a processor, or a radio component, or a combination thereof. For example, as Figure 7 As shown, the communication circuit 700 includes a modem 710 and a modem 720, which may correspond to or may be Figure 4 and Figure 5Modem 710 may be configured to communicate in accordance with a first RAT, such as LTE or LTE-A, and modem 720 may be configured to communicate in accordance with a second RAT, such as 5G NR.

[0153] The modem 710 includes one or more processors 712 and a memory 716 in communication with the processor 712. The modem 710 is in communication with a radio frequency (RF) front end 730, which may correspond to or may be Figure 4 and Figure 5 RF front end 730 may include circuitry for transmitting and receiving radio signals. For example, RF front end 730 includes receive circuitry (RX) 732 and transmit circuitry (TX) 734. In some examples, receive circuitry 732 communicates with DL front end 750, which may include circuitry for receiving radio signals from antenna 702a. Switch 770 may selectively couple modem 710 to UL front end 772, which may include circuitry for transmitting radio signals using antenna 702c.

[0154] Similarly, the modem 720 includes one or more processors 722 and a memory 726 in communication with the processor 722. The modem 720 is in communication with an RF front end 740, which may correspond to or may be Figure 4 and Figure 5 RF front end 740 may include circuitry for transmitting and receiving radio signals. For example, RF front end 740 includes receive circuitry 742 and transmit circuitry 744. In some examples, receive circuitry 742 communicates with downlink front end 760, which may include circuitry for receiving radio signals from antenna 702b. Switch 770 may selectively couple modem 720 to uplink front end 772 for transmitting radio signals using antenna 702c.

[0155] The modem 710 may include hardware and software components for time-division multiplexing UL data (e.g., for NSA NR operation) and various other techniques described herein. The processor 712 may include one or more processing elements configured to implement the various features described herein, such as by executing program instructions stored on a memory 716 (e.g., a non-transitory computer-readable memory medium). In some examples, the processor 712 may be configured as a programmable hardware element, such as an FPGA or an ASIC. In some examples, the processor 712 may include one or more ICs configured to perform the functions of the processor 712. For example, each IC may include circuitry configured to perform the functions of the processor 712.

[0156] Modem 720 may include hardware and software components for time division multiplexing UL data (e.g., for NSA NR operation) and various other techniques described herein. Processor 722 may include one or more processing elements configured to implement the various features described herein, such as by executing instructions stored on memory 726 (e.g., a non-transitory computer-readable memory medium). In some examples, processor 722 may be configured as a programmable hardware element, such as an FPGA or ASIC. In some examples, processor 722 may include one or more ICs configured to perform the functions of processor 722. For example, each IC may include circuitry configured to perform the functions of processor 522.

[0157] Figure 8 The various protocol functions that can be implemented in a wireless communication device are shown. Specifically, Figure 8 The present invention includes an arrangement 800 showing the interconnection between various protocol layers / entities. The various protocol layers and entities operating in conjunction with the 5G NR system standard and the LTE system standard are provided. Figure 8 The following description, but Figure 8 Some or all aspects of the present invention may also be applicable to other wireless communication network systems.

[0158] In addition to other higher layer functions not shown, the protocol layers of arrangement 800 may include one or more of PHY 810, MAC 820, RLC 830, PDCP 840, SDAP 847, RRC 855, and NAS layer 857. These protocol layers may include one or more service access points (e.g., Figure 8 Items 859, 856, 850, 849, 845, 835, 825, and 815).

[0159] The PHY 810 can transmit and receive physical layer signals 805, which can be received from or transmitted to one or more other communication devices. The physical layer signals 805 may include one or more physical channels, such as those discussed herein. The PHY 810 may also 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 (e.g., RRC 855). The PHY 810 may further perform error detection on transport channels, forward error correction (FEC) encoding and decoding of transport channels, modulation and demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and MIMO antenna processing. In some examples, an instance of the PHY 810 may use one or more PHY-SAPs 815 to process requests from an instance of the MAC 820 and provide instructions thereto. In some examples, the requests and instructions transmitted using the PHY-SAP 815 may include one or more transport channels.

[0160] Instances of MAC 820 may process requests from instances of RLC 830 and provide indications thereto using one or more MAC-SAPs 825. These requests and indications conveyed using MAC-SAPs 825 may include one or more logical channels. MAC 820 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto transport blocks (TBs) to be delivered to PHY 810 using transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 810 using transport channels onto one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0161] Instances of RLC 830 can utilize one or more Radio Link Control Service Access Points (RLC-SAPs) 835 to process requests from instances of PDCP 840 and provide indications thereto. These requests and indications transmitted using RLC-SAPs 835 can include one or more logical channels. RLC 830 can operate in multiple modes of operation, including Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC 830 can perform transmission of upper layer protocol data units (PDUs), error correction through Automatic Repeat Request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 830 can also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0162] An instance of PDCP 840 may utilize one or more Packet Data Convergence Protocol Service Access Points (PDCP-SAPs) 845 to process requests from an instance of RRC 855 or an instance of SDAP 847, or both, and provide instructions thereto. These requests and instructions conveyed using PDCP-SAPs 845 may include one or more radio bearers. PDCP 840 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-sequence delivery of higher layer PDUs upon reestablishment of lower layers, eliminate duplication of lower layer SDUs upon reestablishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., ciphering, deciphering, integrity protection, or integrity verification).

[0163] An instance of SDAP 847 can utilize one or more SDAP-SAPs 849 to process requests from one or more higher layer protocol entities and provide instructions thereto. These requests and instructions transmitted using SDAP-SAPs 849 may include one or more QoS flows. SDAP 847 can map QoS flows to data radio bearers (DRBs) and vice versa, and can also mark QoS flow identifiers (QFIs) in DL and UL packets. A single SDAP entity 847 can be configured for a separate PDU session. In the UL direction, NG-RAN 110 can control the mapping of QoS flows to DRBs in two different ways: reflective mapping or explicit mapping. For reflective mapping, SDAP 847 of UE 101 can monitor the QFI of DL packets for each DRB and apply the same mapping to packets flowing in the UL direction. For DRBs, SDAP 847 of UE 101 can map UL packets belonging to a QoS flow that corresponds to the QoS flow ID and PDU session observed in the DL packets of that DRB. To implement reflective mapping, the NG-RAN 310 may tag DL packets with a QoS flow ID over the Uu interface. Explicit mapping may involve the RRC 855 configuring the SDAP 847 with explicit mapping rules for QoS flows to DRBs, which may be stored and followed by the SDAP 847. In some examples, the SDAP 847 may be used only in NR implementations and may not be used in LTE implementations.

[0164] The RRC 855 may configure aspects of one or more protocol layers using one or more Management Service Access Points (M-SAPs), which may include one or more instances of PHY 810, MAC 820, RLC 830, PDCP 840, and SDAP 847. In some examples, instances of the RRC 855 may process requests from and provide instructions to one or more NAS entities 857 using one or more RRC-SAPs 856. The primary services and functions of the RRC 855 may include broadcasting of system information (e.g., included in a Master Information Block (MIB) or System Information Block (SIB) related to the NAS), broadcasting of system information related to the Access Stratum (AS), paging, establishment, maintenance, and release of the RRC connection between the UE 101 and the RAN 110 (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 MIB and SIB may include one or more information elements, each of which may include separate data fields or data structures.

[0165] NAS 857 may form the highest layer of the control plane between UE 101 and AMF 321. NAS 857 may support mobility and session management procedures of UE 101 to establish and maintain an IP connection between UE 101 and P-GW in the LTE system.

[0166] In some examples, one or more protocol entities of arrangement 800 may be implemented in UE 101, RAN node 111, AMF 321 in NR implementations or MME 221 in LTE implementations, UPF 302 in NR implementations or S-GW 222 and P-GW 223 in LTE implementations, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In some examples, one or more protocol entities that may be implemented in one or more of UE 101, gNB 111, AMF 321, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using services of corresponding lower layer protocol entities to perform such communication). In some examples, the gNB-CU of gNB 111 may host the gNB's RRC 855, SDAP 847, and PDCP 840 that control operations of one or more gNB-DUs, and the gNB-DUs of gNB 111 may each host the RLC 830, MAC 820, and PHY 810 of gNB 111.

[0167] In some examples, the control plane protocol stack may include, in order from highest layer to lowest layer, NAS 857, RRC 855, PDCP 840, RLC 830, MAC 820, and PHY 810. In this example, upper layers 860 may be built on top of NAS 857, including an IP layer 861, SCTP 862, and an application layer signaling protocol (AP) 863.

[0168] In some examples such as NR implementations, the AP 863 may be an NG application protocol layer (NGAP or NG-AP) 863 for the NG interface 113 defined between the NG-RAN node 111 and the AMF 321, or the AP 863 may be an Xn application protocol layer (XnAP or Xn-AP) 863 for the Xn interface 112 defined between two or more RAN nodes 111.

[0169] The NG-AP 863 may support the functionality of the NG interface 113 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 111 and the AMF 321. NG-AP 863 services may include two groups: UE-associated services (e.g., services related to the UE 101) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 111 and the AMF 321). These services may include functions such as, but not limited to: a paging function for sending a paging request to the NG-RAN node 111 involved in a specific paging area; a UE context management function for allowing the AMF 321 to establish, modify or release the UE context in the AMF 321 and the NG-RAN node 111; a mobility function for the UE 101 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signalling transport function for transporting or rerouting NAS messages between the UE 101 and the AMF 321; a NAS node selection function for determining the association between the AMF 321 and the UE 101; an NG interface management function for setting up the NG interface and monitoring errors over the NG interface; a warning message transport function for providing a means to transport warning messages or cancel an ongoing warning message broadcast using the NG interface; a function for sending a warning message to the NG interface using the CN 120 is a configuration transmission function for requesting and transmitting RAN configuration information (eg, SON information, or performance measurement (PM) data) between two RAN nodes 111; or a combination thereof, etc.

[0170] The XnAP 863 may support the functions of the Xn interface 112 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures for handling UE mobility within the NG RAN 111 (or E-UTRAN 210), such as handover preparation and cancellation procedures, SN status transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or procedures related to dual connectivity. The XnAP global procedures may include procedures not related to a specific UE 101, such as Xn interface setup and reset procedures, NG-RAN update procedures, or cell activation procedures.

[0171] In an LTE implementation, the AP 863 may be an S1 application protocol layer (S1-AP) 863 for the S1 interface 113 defined between the E-UTRAN node 111 and the MME, or the AP 863 may be an X2 application protocol layer (X2AP or X2-AP) 863 for the X2 interface 112 defined between two or more E-UTRAN nodes 111.

[0172] The S1 application protocol layer (S1-AP) 863 may support the functionality of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be the interaction unit between the E-UTRAN node 111 and the MME 221 within the LTE CN 120. S1-AP 863 services may include 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, RAN Information Management (RIM), and configuration transfer.

[0173] The X2AP 863 may support the functions of the X2 interface 112 and may include X2AP basic mobility procedures and X2AP global procedures. The X2AP basic mobility procedures may include procedures for handling UE mobility within the E-UTRAN 120, such as handover preparation and cancellation procedures, SN status transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, or procedures related to dual connectivity. The X2AP global procedures may include procedures not related to a specific UE 101, such as X2 interface setup and reset procedures, load indication procedures, error indication procedures, or cell activation procedures.

[0174] The SCTP layer (alternatively referred to as the SCTP / IP layer) 862 can 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). SCTP 862 can ensure reliable delivery of signaling messages between the RAN node 111 and the AMF 321 / MME 221 based in part on the IP protocol supported by IP 861. The Internet Protocol layer (IP) 861 can be used to perform packet addressing and routing functions. In some implementations, the IP layer 861 can use point-to-point transport to deliver and transmit PDUs. In this regard, the RAN node 111 can include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0175] In some examples, the user plane protocol stack may include, in order from highest layer to lowest layer, SDAP 847, PDCP 840, RLC 830, MAC 820, and PHY 810. The user plane protocol stack may be used for communication between UE 101, RAN node 111, and UPF 302 in an NR implementation, or between S-GW 222 and P-GW 223 in an LTE implementation. In this example, upper layers 851 may be built on top of SDAP 847 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 852, a general packet radio service (GPRS) tunneling protocol layer for the user plane (GTP-U) 853, and a user plane PDU layer (UP PDU) 863.

[0176] The transport network layer 854 (also known as the "transport layer") can be built on top of the IP transport, and GTP-U 853 can be used on top of the UDP / IP layer 852 (including the UDP layer and the IP layer) to carry user plane PDUs (UP-PDUs). The IP layer (also known as the "Internet layer") can be used to perform packet addressing and routing functions. The IP layer can assign IP addresses to user data packets in any of the formats, such as IPv4, IPv6, or PPP.

[0177] GTP-U 853 may be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data may be packets in any of the IPv4, IPv6, or PPP formats. UDP / IP 852 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data flows. The RAN node 111 and the S-GW 222 may utilize the S1-U interface to exchange user plane data using a protocol stack comprising the L1 layer (e.g., PHY 810), the L2 layer (e.g., MAC 820, RLC 830, PDCP 840, and / or SDAP 847), the UDP / IP layer 852, and the GTP-U 853. The S-GW 222 and the P-GW 223 may utilize the S5 / S8a interface to exchange user plane data using a protocol stack comprising the L1 layer, the L2 layer, the UDP / IP layer 852, and the GTP-U 853. As previously discussed, the NAS protocol may support mobility and session management procedures for UE 101 to establish and maintain an IP connection between UE 101 and P-GW 223 .

[0178] In addition, despite Figure 8Not shown, but an application layer may exist above AP 863 and / or transport network layer 854. The application layer may be the layer where a user of UE 101, RAN node 111, or other network element interacts with, for example, software applications executed by application circuitry 405 or application circuitry 505, respectively. The application layer may also provide one or more interfaces for the software applications to interact with the communication system of UE 101 or RAN node 111, such as baseband circuitry 610. In some examples, the IP layer or the application layer, or both, may provide functionality that is the same as or similar to layers 5 through 7 of the Open Systems Interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

[0179] Figure 9 Components of the core network 220 are shown. The components of the CN 220 may be implemented in one physical node or in separate physical nodes and may include components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some examples, the components of the CN 320 can be implemented in the same or similar manner as discussed herein with respect to the components of the CN 220. In some examples, NFV is used to virtualize any or all of the above-described network node functions using executable instructions stored in one or more computer-readable storage media, as will be described in further detail below. A logical instance of the CN 220 may be referred to as a network slice 901, and each logical instance of the CN 220 may provide specific network functions and network features. A logical instance of a portion of the CN 220 may be referred to as a network sub-slice 902 (e.g., the network sub-slice 902 is shown as including a P-GW 223 and a PCRF 226).

[0180] As used herein, the terms "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the concrete occurrence of an object, which may occur, for example, during the execution of program code. A network instance may refer to information identifying a domain, which may be used for traffic detection and routing in different IP domains or in the case of overlapping IP addresses. A network slice instance may refer to a set of network function (NF) instances and the resources required to deploy a network slice (e.g., computing, storage, and network resources).

[0181] Regarding 5G systems (see e.g. Figure 3), a network slice may include a RAN portion and a CN portion. Support for network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. The network can implement different network slices through scheduling or by providing different L1 / L2 configurations, or both. If provided by the NAS, the UE 301 provides assistance information for network slice selection in the appropriate RRC message. Although the network can support a large number of slices, in some examples, the UE does not need to support more than 8 slices simultaneously.

[0182] A network slice may include the CN 320 control plane and user plane NFs, the NG-RAN 310 in the serving PLMN, and the N3IWF functionality in the serving PLMN. Each network slice may have a different S-NSSAI or a different SST, or both. The NSSAI includes one or more S-NSSAIs, and each network slice is uniquely identified by an S-NSSAI. Network slices may differ in terms of supported features and network function optimizations. In some examples, multiple network slice instances may deliver the same services or features, but for different groups of UEs 301 (e.g., enterprise users). For example, each network slice may deliver different committed services or may be dedicated to a specific customer or enterprise, or both. In this example, each network slice may have a different S-NSSAI with the same SST but a different slice differentiator. In addition, a single UE may be served simultaneously by one or more network slice instances using the 5G AN, and the UE may be associated with eight different S-NSSAIs. Furthermore, the AMF 321 instance serving a single UE 301 may belong to each network slice instance serving that UE.

[0183] Network slicing in the NG-RAN 310 involves RAN slice awareness. RAN slice awareness involves differentiated handling of traffic for different pre-configured network slices. Slice awareness in the NG-RAN 310 is introduced at the PDU session level by indicating the S-NSSAI corresponding to the PDU session in all signaling, including PDU session resource information. How the NG-RAN 310 supports slicing in terms of NG-RAN functionality (e.g., a set of network functions per slice) depends on the specific implementation. The NG-RAN 310 selects the RAN portion of the network slice using assistance information provided by the UE 301 or 5GC 320. This assistance information explicitly identifies one or more pre-configured network slices in the PLMN. The NG-RAN 310 also supports resource management and policy enforcement between slices according to SLAs. A single NG-RAN node can support multiple slices, and the NG-RAN 310 can also apply the appropriate RRM policy for the SLA to each supported slice. The NG-RAN 310 also supports QoS differentiation within a slice.

[0184] NG-RAN 310 can also use UE assistance information to select an AMF 321 during the initial attach, if available. NG-RAN 310 uses the assistance information to route the initial NAS to AMF 321. If NG-RAN 310 cannot select an AMF 321 using the assistance information, or if UE 301 does not provide any such information, NG-RAN 310 sends NAS signaling to a default AMF 321, which may be in the AMF 321 pool. For subsequent access, UE 301 provides the temporary ID assigned to UE 301 by 5GC 320 to enable NG-RAN 310 to route NAS messages to the appropriate AMF 321, as long as the temporary ID is valid. NG-RAN 310 is aware of and can reach the AMF 321 associated with the temporary ID. Otherwise, the method used for initial attach applies.

[0185] The NG-RAN 310 supports resource isolation between slices. This isolation is achieved through RRM policies and protection mechanisms that prevent shared resource starvation in situations where one slice disrupts the service-level agreement of another slice. In some examples, NG-RAN 310 resources can be fully dedicated to a slice. How the NG-RAN 310 supports resource isolation is implementation-dependent.

[0186] Some slices may only be partially available in the network. The NG-RAN 310 is aware of the slices supported in its neighboring cells that may be beneficial for inter-frequency mobility in connected mode. Slice availability may not change within the UE's registration area. The NG-RAN 310 and 5GC 320 are responsible for processing service requests for slices that may or may not be available in a given area. Granting or denying access to a slice may depend on factors such as support for the slice, resource availability, and NG-RAN 310 support for the requested service.

[0187] UE 301 can be associated with multiple network slices simultaneously. In the event that UE 301 is associated with multiple slices simultaneously, only one signaling connection is maintained, and for intra-frequency cell reselection, UE 301 attempts to camp on the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency that UE 301 camps on. 5GC 320 will verify that UE 301 has the right to access the network slice. Before receiving the Initial Context Setup Request message, knowing the specific slice that UE 301 is requesting access to allows NG-RAN 310 to apply temporary or local policies. During Initial Context Setup, NG-RAN 310 is informed of the slice whose resources are being requested.

[0188] The NFV architecture and infrastructure can be used to virtualize one or more NFs onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively executed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components and functions.

[0189] Figure 10 An exemplary management system 1000 for a mobile network including virtualized network functions is depicted. The management system 1000 may include a 3GPP management system 1002 and a NFV-MANO framework 1004 (eg, ETSI GS NFV-MAN 001). Figure 10 3GPP management system 1002 is based on a 4G network, but aspects of the management system are applicable to 5G networks or other networks. Architecture 1000 is shown to include a virtualized infrastructure manager (VIM) 1006, a network function virtualization infrastructure (NFVI) 1008, a virtualized network function (VNF) 1010, a VNF manager (VNFM) 1012, an element manager (EM) 1014, a network function virtualization orchestrator (NFVO) 1016, and a network manager (NM) 1018. The mobile network includes both physical and virtualized network elements. 3GPP management system 1002 manages application-specific aspects of both the VNFs and PNFs corresponding to the physical network elements (NEs).

[0190] In system 1000, Itf-N is the interface between NM 1018 and DM / EM 1014, Os-Ma-nfvo is the reference point between the Operation Support System (OSS) / Business Support System (BSS) (e.g., NM 1014) and NFVO 1016, Ve-Vnfm-em is the reference point between EM 1014 and VNFM 1012, and Ve-Vnfm-vnf is the reference point between VNF 1010 and VNFM 1012.

[0191] NFVI 1008 includes hardware and software components that together provide the infrastructure resources where the VNFs are deployed. Infrastructure resources include hardware resources, virtualization layer software, and virtualized resources that the VNFs rely on. The NFVI resources considered are virtualized and non-virtualized resources that support virtualized network functions and partially virtualized network functions. Virtualized resources include those that can be associated with virtualization containers and have been cataloged and provided for consumption through appropriate abstraction services, for example, compute, including machines (e.g., hosts or bare disks) and virtual machines as resources including both CPU and memory; storage, including: storage volumes at the block level or file system level; and networking, including: networks, subnetworks, ports, addresses, links, and forwarding rules for the purpose of ensuring connectivity within and between VNFs.

[0192] EM 1014 tracks performance, faults, and security of functional aspects of VNF 1010. Tracking data from VNFM 1012 and EM 1014 may include, for example, performance management (PM) data used by VIM or NFVI 1008. Both VNFM 1012 and EM 1014 may scale up / down the number of VNFs 1010 of system 1000.

[0193] NM 1018 supports OSS / BSS and is a consumer of the reference point Os-Man-nfvo. NM 1018 provides functions for managing mobile networks, including VNF 1010. NM 1018 can provide an end-user function package responsible for network management, which may include network elements with VNFs, non-virtualized network functions, or both (management of VNFs can occur via EM). NM 1018 can support fault, configuration, charging, performance, and security (FCAPS) management functions for mobile networks (e.g., IMS, EPC, NR, etc.) and 3GPP services (e.g., data services, voice services), and support the management of the mobile network lifecycle. NM 1018 initiates the lifecycle management of NS and VNFs related to the mobile network by interacting with NFV-MANO 1004.

[0194] The EM 1014 and / or DM are responsible for FCAPS management functions for the VNFs 1010 at the application level and the physical NEs at the domain and element levels. This includes: fault management for the VNFs and physical NEs; configuration management for the VNFs and physical NEs; billing management for the VNFs and physical NEs; performance measurement and collection for the VNFs and physical NEs; and security management for the VNFs and physical NEs. The EM / DM participates in the lifecycle management functions of the VNFs, such as by requesting lifecycle management operations for the VNFs from the VNFM and exchanging information about the VNFs and virtualized resources associated with the VNFs. The DM / EM (including EM extension functionality) can manage both PNFs and VNFs.

[0195] NFV-MANO 1004 includes NFVO 1016, VNFM 1012, and VIM 1006. NFVO 1016 and VNFM 1012 share interfaces with NM 1018, DM / EM 1014, and VNF 1010. NFVO 1016 is responsible for orchestrating NFVI resources across multiple VIMs 1006, thereby implementing resource orchestration functionality, and for managing the lifecycle of network services, thereby implementing network service orchestration functionality. NFVO 1016 can coordinate, authorize, release, and join NFVI resources to provide requested services (e.g., to execute network functions, components, or slices).

[0196] The VIM 1006 manages the resources of the NFVI 1008. The NFVI 1008 may include physical or virtual resources and applications (including a hypervisor) for executing the system 1000. The VIM 1006 may utilize the NFVI 1008 to manage the lifecycle of virtual resources (e.g., the creation, maintenance, and teardown of VMs associated with one or more physical resources), track VM instances, track the performance, faults, and security of VM instances and associated physical resources, and expose VM instances and associated physical resources to other management systems.

[0197] The VNFM 1012 manages the VNF 1010. The VNF 1010 may be used to perform network (e.g., EPC, NR, etc.) components / functions. The VNFM 1012 may manage the lifecycle of the VNF 1010 and track the performance, faults, and security of the virtual aspects of the VNF 1010.

[0198] Management and orchestration of virtualized resources includes handling NFVI resources in NFVI Points of Presence (NFVI-PoPs) (e.g., in NFVI nodes). Management of non-virtualized resources is limited to providing PNFs with the connectivity they need when an NS instance includes a PNF that needs to connect to a VNF, or when an NS instance is distributed across multiple NFVI-PoPs or N-PoPs.

[0199] Virtualized resources are used to provide VNFs 1010 with the resources they need. Resource allocation within NFVI 1008 is a potentially complex task, as many requirements and constraints may need to be met simultaneously. Specifically, network allocation requirements add new complexities compared to known resource allocation strategies for computing resources in virtualized environments. For example, some VNFs 1010 may require low-latency or high-bandwidth links to other communication endpoints.

[0200] The allocation and release of resources is a dynamic process that responds to the consumption of those services by other functions. Although VNFs are unaware of the management and orchestration functions of the virtualized infrastructure, resource allocation and release may need to occur throughout the VNF's lifecycle. The advantage of NFV is that as load increases, VNFs can dynamically consume services that allocate additional resources when scaling down is triggered.

[0201] Services that expose virtualized resources include, but are not limited to: discovery of available services; management of virtualized resource availability / allocation / release; and virtualized resource fault / performance management.

[0202] In the case of virtualized resources distributed across multiple NFVI-PoPs, these services can be exposed directly by the management and orchestration functions of each individual NFVI-PoP, or via a higher-level service abstraction that presents the virtualized resources across multiple NFVI-PoPs. Both types of services can be exposed to consuming functions. In the case of the higher-level service abstraction mentioned previously, the management and orchestration of virtualized resources and non-virtualized networking resources across those NFVI-PoPs are the responsibility of the management and orchestration of the virtualized infrastructure, which in turn can use the services directly exposed by the management and orchestration functions of a single NFVI-PoP or across multiple NFVI-PoPs. To provide those services, the management and orchestration of the virtualized infrastructure consumes the services provided by the NFVI.

[0203] The NFV management and orchestration functions that coordinate virtualized resources within a single NFVI-PoP and / or across multiple NFVI-PoPs should ensure the exposure of services that support access to these resources in an open, abstract manner. Other authenticated and appropriately authorized NFV management and orchestration functions (e.g., functions that manage and orchestrate virtualized network functions) may consume these services.

[0204] Network service lifecycle management includes, among other things: bringing a network service online (e.g., registering a network service in a catalog and ensuring that all templates describing the NS are brought online); instantiating a network service (e.g., creating a network service using NS onboarding artifacts); scaling a network service (e.g., increasing or decreasing the capacity of a network service); updating a network service by supporting network service configuration changes of varying complexity (such as changing inter-VNF connectivity or constituent VNF ​​instances); performing create, delete, query, and update procedures for the VNF forwarding graph (VNFFG) associated with the network service; and terminating a network service (e.g., requesting termination of constituent VNF ​​instances, requesting release of NFVI resources associated with the NS, and returning them to the NFVI resource pool where appropriate).

[0205] The deployment and operational behavior requirements for each network service can be captured in a deployment template and stored in the catalog during the network service onboarding process for future selection for instantiation. A deployment template describes the properties and requirements for implementing such a network service. Network service orchestration coordinates the lifecycle of the VNFs that collectively implement the network service. In some examples, this includes managing the associations between different VNFs (and, where appropriate, between VNFs and PNFs), the topology of the network service, and the VNFFGs associated with the network service.

[0206] During the network service lifecycle, if such requirements are captured in the deployment template, the network service orchestration function can monitor the key performance indicators (KPIs) of the network service and can report this information to support explicit requests for such operations by other functions.

[0207] Network service orchestration performs its services by using VNF management functions and by orchestrating the NFV infrastructure that supports the interconnection between VNF functionalities, and its functions are exposed in an open and abstract manner as services for other functions. To fulfill its responsibilities, the network service orchestration function consumes services exposed by other functions (e.g., virtualized infrastructure management functions).

[0208] In some examples, services provided by network services orchestration can be consumed by other functions (e.g., OSS, BSS) that are authenticated and authorized.

[0209] The VNFM 1012 is responsible for the lifecycle management of the VNF instances. It is assumed that each VNF instance has an associated VNF manager. The VNF manager can be assigned the management of a single VNF instance or the management of multiple VNF instances of the same or different types.

[0210] In some examples, it is assumed that the VNFM functionality is a common functionality applicable to multiple VNFs. The NFV-MANO architecture framework can also support the following scenarios: a VNF instance requires specific functionality for its lifecycle management, and such functionality can be specified in the VNF package.

[0211] The VNF 1010 is configured to perform VNF instantiation, including VNF configuration where required by the VNF deployment template (e.g., initial configuration of a VNF with an IP address before completing the VNF instantiation operation); VNF instantiation feasibility check; VNF instance software update / upgrade; VNF instance modification; VNF instance scale-up / down and scale-up / down; collection of NFVI performance measurements and fault / event information related to the VNF instance, and correlation of events / faults related to the VNF instance; VNF instance assisted or automatic healing; VNF instance termination; VNF lifecycle management change notification; integrity management of the VNF instance during its lifecycle; and overall coordination and adaptation of configuration and event reporting between the VIM and the EM. The aforementioned functions may be exposed through interfaces and consumed by other NFV-MANO functional blocks or by authorized external entities.

[0212] The deployment and operational behavior of each VNF 1010 can be captured in a template (e.g., a virtualized network function descriptor (VNFD)) stored in the VNF catalog. NFV-MANO uses the VNFD to create instances of the VNFs it represents and to manage the lifecycle of those instances. A VNFD corresponds one-to-one with a VNF package and describes the properties and requirements for implementing such a VNF. NFVI resources are allocated to the VNF based on the requirements captured in the VNFD (including resource allocation criteria, etc.), but also taking into account specific requirements, constraints, and policies (e.g., operator policies, geographic placement, affinity / anti-affinity rules, local regulations) that may have been pre-provided or accompanied the instantiation request and may override certain requirements in the VNFD.

[0213] The information elements (including VNFD, etc.) to be processed by NFV-MANO 1004 can ensure the flexible deployment and portability of VNF instances across multiple vendors and different NFVI environments (e.g., with different computing resource generations, different virtual network technologies, etc.). To this end, hardware resources are abstracted, and VNF requirements are described according to such abstractions.

[0214] The VNFM 1012 has access to a repository of available VNF packages and their different versions, all represented by their associated VNFDs. Different versions of a VNF package can correspond to different implementations of the same function, different versions running in different execution environments (e.g., on different hypervisors, depending on NFVI resource availability information, etc.), or different releases of the same software. The repository can be maintained by the NFVO or another external entity.

[0215] The VIM 1006 is responsible for controlling and managing NFVI compute, storage, and network resources typically within the operator's infrastructure domain (e.g., all resources within an NFVI-PoP, resources across multiple NFVI-PoPs, or a subset of resources within an NFVI-PoP), as previously described. The VIM 1006 may be specialized for a certain type of NFVI resource (e.g., compute only, storage only, networking only, etc.), or may be able to manage multiple types of NFVI resources (e.g., within NFVI nodes). A specific example of a specialized VIM is a WAN Infrastructure Manager (WIM), which is used to establish connections between PNF endpoints in different NFVI-PoPs.

[0216] In some examples, the VIM 1006 is configured to orchestrate the allocation / promotion / release / reclaim of NFVI resources (which may include optimization of the use of such resources), and manage the association of virtualized resources with physical compute, storage, and networking resources, wherein the VIM maintains an inventory of virtual resources allocated to physical resources (e.g., allocated to server pools, etc.). The VIM also supports the management (creation, query, update, deletion) of VNF forwarding graphs, such as by creating and maintaining virtual links, virtual networks, subnets, and ports, and supports the management of security group policies to ensure network / traffic access control.

[0217] The VIM 1006 also manages inventory-related information of NFVI hardware resources (computing, storage, networking) and software resources (e.g., hypervisors) in a repository, as well as the discovery of capabilities and characteristics of such resources (e.g., related to usage optimization); manages virtualized resource capacity (e.g., the density of virtualized resources to physical resources) and forwards information related to NFVI resource capacity and usage reporting; manages software images (addition, deletion, update, query, replication) based on requests from other NFV-MANO functional blocks (e.g., NFVO). The VIM can maintain a repository of software images to rationalize the allocation of virtualized computing resources, and before storing an image (e.g., VNF package online and update), the VIM needs to perform a verification step on the software image.

[0218] The VIM 1006 may collect (e.g., via notifications) performance and fault information for hardware resources (compute, storage, and networking), software resources (e.g., hypervisors), and virtualized resources (e.g., VMs); and forward performance measurements and fault / event information related to virtualized resources; and

[0219] In some examples, the VIM 1006 manages a catalog of virtualized resources that can be consumed from or by the NFVI 1008. Elements in the catalog can be in the form of virtualized resource configurations (virtual CPU configurations, network connectivity types (e.g., L2, L3), etc.) and / or templates (e.g., a virtual machine with two virtual CPUs and 2GB of virtual memory).

[0220] Figure 11 is a block diagram illustrating components for reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the techniques described herein. Specifically, Figure 11 A schematic diagram of hardware resources 1100 is shown, including one or more processors (or processor cores) 1110, one or more memories or storage devices 1120, and one or more communication resources 1130, each of which may be communicatively coupled using a bus 1140. For implementations in which node virtualization (e.g., NFV) is utilized, a hypervisor 1102 may be executed to provide an execution environment for one or more network slices or sub-slices to utilize the hardware resources 1100.

[0221] Processor 1110 may include processor 1112 and processor 1114. Processor 1110 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0222] The memory / storage device 1120 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1120 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or solid-state storage devices, or a combination thereof.

[0223] The communication resources 1130 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 1104 or one or more databases 1106 using the network 1108. For example, the communication resources 1130 may include wired communication components (e.g., for coupling using USB), cellular communication components, NFC components, (or Low power consumption) components, components and other communication components.

[0224] The instructions 1150 may include software, a program, an application, an applet, an application, or other executable code for causing at least one of the processors 1110 to perform any one or more of the methodologies discussed herein. The instructions 1150 may reside, in whole or in part, within at least one of the processor 1110 (e.g., within a cache memory of the processor), the memory / storage device 1120, or any suitable combination thereof. Furthermore, any portion of the instructions 1150 may be transmitted to the hardware resources 1100 from any combination of the peripheral device 1104 or the database 1106. Thus, the memory of the processor 1110, the memory / storage device 1120, the peripheral device 1104, and the database 1106 are examples of computer-readable and machine-readable media.

[0225] When an AF (e.g., AF 328) needs to trigger a UE (e.g., UE 101, 201, 301) to perform some action, the AF requests the NEF (e.g., NEF 323) to send an application trigger to the UE. To this end, the AF may invoke the Nnef_Trigger service to request the network to send an application trigger to the UE.

[0226] Figure 12 An exemplary device triggering process 1200 according to some embodiments is shown. The device triggering process 1200 may operate as follows:

[0227] 1. The AF determines the need of a triggering device (eg, UE). If the AF does not have contact details for the NEF, it may discover and select NEF services as described in 3GPP TS 23.502.

[0228] 2. The AF communicates with the NEF to invoke the Nnef_Trigger_Delivery service operation to request that an application trigger be sent to the UE and subscribe to notifications about application trigger delivery attempts. Additional details on the Nnef_Trigger_Delivery service operation are described in clause 5.2.6.5.2 of 3GPP TS 23.502.

[0229] 3. The NEF checks that the AF is authorized to send trigger requests and that the AF has not exceeded its trigger submission quota or rate on the Nnef. If this check fails, the NEF sends an Nnef_Trigger_Delivery response to the AF with a reason value indicating the reason for the failure condition, and the process stops at this step. Otherwise, the process continues with step 4 of process 1200.

[0230] 4. When the AF is authorized to trigger the UE, the NEF calls the Nudm_SDM_Get service operation (e.g., with the identifier translation, GPSI, and AF identifier as parameters) to resolve the Universal Public Subscription Identifier (GPSI) to the Subscription Permanent Identifier (SUPI). In some examples, a mapping from GPSI (External Id) to GPSI (Mobile Subscription ISDN Number (MSISDN)) is provided to support infrastructures that do not have MSISDN-less SMS capabilities. Additional details on the Nudm_SDM_Get service operation are described in clause 5.2.3.3.1 of 3GPP TS 23.502.

[0231] 5. The UDM may invoke the Nudr_DM_Query service operation to retrieve a list of AFs permitted to trigger the UE and, based on UDM policy, determine which identifier (e.g., SUPI or MSISDN) should be used to trigger the UE. Additional details regarding the Nudr_DM_Query service operation are described in clause 5.2.12.2.2 of 3GPP TS 23.502. If the AF is authorized to trigger the UE, the UDM provides a Nudm_SDM_Get response with the appropriate identifier (e.g., SUPI or MSISDN, or both). If the AF is not permitted to send trigger information to the UE, or if valid subscription information does not exist for the UE, the NEF sends an Nnef_Trigger_Delivery response with a cause value indicating the cause of the failure condition, and the flow stops at this step. Otherwise, the flow continues with step 6. In some examples, the presence of an MSISDN in the response is interpreted as an indication to the NEF that the MSISDN (rather than the IMSI) is used to identify the UE when sending SMS to the SMS Service Center (SMS-SC) via T4.

[0232] 6. The NEF invokes the Nudm_UECM_Get service operation (eg with SUPI, SMS) to retrieve the UE SMSF identity. Additional details on the Nudm_UECM_Get service operation are described in clause 5.2.3.2.4 of 3GPP TS 23.502.

[0233] 7. The UDM may invoke the Nudr_DM_Query service to retrieve the UE SMSF identity. The UDM provides a Nudm_UECM_Get response with the corresponding UE SMSF identity. The UDM policy (which may depend on the Visited Public Land Mobile Network (VPLMN) ID) may influence which service node identities are returned. In some examples, the NEF may cache the UE's service node information. However, if the cached service node information is out of date, this may increase the probability of a failed trigger delivery attempt.

[0234] 8. The NEF selects an appropriate SMS-SC based on the configured information. In some examples, the NEF acts as a Machine Type Communication Interworking Function (MTC-IWF) and sends a Submit Trigger message (e.g., with GPSI, SUPI, AF identifier, trigger reference number, validity period, priority, SMSF service node ID (if available, obtained from the UDM in step 7), SMS application port ID, trigger payload, and trigger indication) to the SMS-SC. If the NEF indicates that a "Subscriber Absent" message was received from the UDM, the SMS-SC should not submit the message, but instead store it directly and send routing information for the SM to request the UDM to add the SMS-SC address to the message waiting list.

[0235] 9. SMS-SC sends a Submission Trigger Confirmation message to NEF to confirm that the SMS submission has been received.

[0236] SMS-SC accepts.

[0237] 10. The NEF sends an Nnef_Trigger_Delivery response to the AF to indicate whether the device trigger request has been accepted for delivery to the UE.

[0238] 11. SMS-SC performs mobile MT SMS delivery (e.g., as described in 3GPP TS

[0239] 23.502, clause 4.13.3). The SMS-SC may provide the routing information it received in step 6 to the SMS Gateway Mobile Services Switching Centre (GMSC) to avoid UDM interrogation. The SMS-SC generates the necessary call detail record (CDR) information and includes the AF identifier. The trigger indication and the SMS application port ID included in the SM user data header are included in the CDR to enable differentiated billing.

[0240] The SC stores the trigger payload without routing information. If the message delivery fails and delivery is attempted again, a UDM query will be performed. If the message delivery fails and the validity period of the trigger message is not set to zero, the SMS-SC shall send an SM message delivery status report to request the UDM to add the SMS-SC address to the message waiting list. When the message delivery is retried later, a new UDM query will be performed by the SMS-GMSC using the SUPI or MSISDN. The UDM query using SUPI may not be forwarded or relayed to the SMS router or IP-SM-GW. The UDM may

[0241] The GMSC's response includes up to four serving node identities (MSC or MME, SGSN, IP-SM-GW, AMF).

[0242] 12. If the message delivery fails (directly or when the validity period of the triggering message expires) or when the message delivery is successful, the SMS-SC may send a message delivery report (e.g., with reason code, trigger reference number, AF identifier) ​​to the NEF.

[0243] 13. The NEF provides the AF with a Nnef_Trigger_Delivery Notify message, where the delivery report indicates the trigger delivery result (e.g., success, unknown, or failure and the reason for the failure). Additional details on the Nnef_Trigger_Delivery Notify operation are described in clause 5.2.6.5.3 of 3GPP TS 23.502. The NEF generates CDR information including the GPSI and AF identifier.

[0244] 14. In response to the received device trigger, the UE takes a specific action and may take into account the contents of the trigger payload. The action typically involves initiating an immediate or later communication with the AF.

[0245] When a trigger payload is received at the UE, the application in the UE can perform the actions indicated by the trigger payload. For example, the UE can initiate immediate or later communication with the application server based on the information contained in the trigger payload. If the relevant PDU session has not yet been established, this communication may include a PDU session establishment procedure. Therefore, to ensure the normal operation of the application, the network needs to successfully deliver the application trigger to the UE.

[0246] In 5G networks, SMS may be transported over the Non-Access Stratum (NAS). To enable SMS transport over the NAS, the UE includes an "SMS Supported" indication in its Registration Request, which indicates the UE's capabilities for SMS transport over the NAS. In response, the network indicates to the UE in a Registration Accept message whether the network allows SMS message delivery over the NAS. If the network allows SMS over the NAS, the SMS messages may originate from the UE (e.g., for Mobile Originated (MO) messages) or be terminated by the UE (e.g., for Mobile Terminated (MT) messages) via 3GPP or non-3GPP access (see, e.g., clause 4.13.3 of 3GPP TS 23.502). The performance of SMS over the NAS should be monitored as a service provided to end users.

[0247] Figure 13 An exemplary non-roaming architecture 1300 is shown that supports SMS over NAS using a service-based interface within the control plane. In the non-roaming architecture 1300, the SMS function (SMSF) may connect to the SMS-GMSC / IWMSC / SMS router using, for example, one of the standardized interfaces as shown in 3GPP TS 23.203. In some examples, SMSF reallocation when the UE is in the RM REGISTERED state is not supported. Therefore, when reallocating a serving AMF for a given UE, the source AMF includes the SMSF identifier as part of the UE context transfer to the target AMF. The UDM may connect to the SMS-GMSC / IWMSC / SMS router using, for example, one of the standardized interfaces as shown in 3GPP TS 23.203. In some examples, each UE is associated with only one SMSF in a registered PLMN. To support MT SMS domain selection by the IP-SM-GW / SMS router, the IP-SM-GW / SMS router may connect to the SG MSC, MME or SMSF or a combination thereof using one of the standardized interfaces, for example as shown in 3GPP TS 23.203.

[0248] The present disclosure provides techniques for generating performance measurements related to application triggers for the NEF and performance measurements related to SMS over NAS for the AMF. The performance measurements related to application triggers for the NEF provide information for monitoring the performance of the triggers, and the performance measurements related to SMS over NAS for the AMF indicate the performance of providing SMS over NAS to the end user.

[0249] Figure 14An exemplary performance measurement system 1400 is shown. In system 1400, a service producer 1402 (which may include software and / or hardware components) collects raw performance measurements from one or more NFs 1404. A service provider 1402 (or another entity) then uses the raw performance measurements to generate or derive performance data (sometimes referred to herein as "performance metrics") for one or more NFs 1404. This performance data can then be provided to, for example, a service consumer.

[0250] In some examples, one or more NFs in NF 1404 may be part of a NF group or set. Performance measurements of the NF group or set may be aggregated (e.g., according to an aggregation method identified in a performance metric definition) and used to derive a performance metric for the NF group or set.

[0251] Typically, the performance indicator is derived from performance measurements aggregated over one or more NFs, such as, for example, average latency along a network slice instance (NSI). The performance indicator may be derived from performance measurements collected at an NF or at NFs belonging to the group. In some examples, the aggregation method is identified in the performance indicator definition. Performance indicators at the network slice subset instance (NSSI) level may be derived from performance measurements collected at NFs belonging to or constituting the NSSI. The NSSI-level performance indicators may be made available using, for example, corresponding performance management services for the NSSI. In some examples, NSI-level performance indicators may be derived from NSSI-level performance indicators collected at constituting NSSIs and / or NFs. The NSI-level performance indicators may be made available using, for example, corresponding performance management services for the NSI.

[0252] In some examples, performance measurements related to application triggering for the NEF include measurements of application trigger requests. The measurement may provide the number of application trigger requests received by the NEF from the AF. In some examples, the measurement is collected by a cumulative counter (e.g., an integer value) that is updated in response to Nnef_Trigger_Deliver requests received by the NEF from the AF (see, e.g., 3GPP TS 23.502). In some examples, the measurement type of the measurement (e.g., as defined in 3GPP TS 32.404, the entire contents of which are incorporated herein by reference) is AT.AppTriggerReq. In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is NEFFuntion. The measurement may be valid for packet switched traffic and may be a pure 5G system (5GS) measurement (e.g., counting only 5GS events).

[0253] In some examples, performance measurements related to application triggering for the NEF include measurements of application trigger requests accepted for delivery. The measurement may provide the number of application trigger requests accepted for delivery to the UE. In some examples, the measurement is collected by a cumulative counter (e.g., an integer value) that is updated in response to the transmission of an Nnef_Trigger_Delivery response by the NEF to the AF, which indicates that the application trigger request has been accepted for delivery to the UE (see, e.g., 3GPP TS 23.502). In some examples, the measurement type of the measurement (e.g., as defined in 3GPP TS 32.404) is AT.AppTriggerAcc. In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is NEFFuntion. The measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0254] In some examples, a performance measurement related to application triggering for an NEF includes a measurement of application triggering requests rejected for delivery. This measurement may provide a number of application triggering requests rejected for delivery to a UE. In some examples, this measurement is collected by a cumulative counter (e.g., an integer value), which is updated in response to an Nnef_Trigger_Delivery response transmitted by the NEF to the AF, indicating that the application triggering request has been rejected for delivery to the UE (see, e.g., 3GPP TS 23.502). In some examples, this measurement is divided into sub-counters (each of which may be an integer value) according to an error code (e.g., a response code), and each Nnef_Trigger_Delivery response increments the associated sub-counter based on the error code. In some examples, the measurement type (e.g., as defined in 3GPP TS 32.404) of this measurement is AT.AppTriggerRej.ErrorCode. In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is NEFFuntion. This measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0255] In some examples, performance measurements related to application triggering for the NEF include measurements of application trigger delivery reports. This measurement may provide the number of application trigger delivery reports sent by the NEF to the AF, indicating a delivery result (e.g., success or failure). In some examples, this measurement is collected by a cumulative counter (e.g., an integer value), which is updated in response to the NEF transmitting an Nnef_Trigger_DeliveryNotify message to the AF, indicating the delivery result of the application trigger (see, e.g., 3GPP TS 23.502). In some examples, this measurement is divided into sub-counters (each of which may be an integer value) by delivery result, and each Nnef_Trigger_DeliveryNotify message increments the relevant sub-counter based on the delivery result. In some examples, the measurement type (e.g., as defined in 3GPP TS 32.404) of this measurement is AT.AppTriggerRej.DeliveryResult. In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is NEFFuntion. This measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0256] The performance measurements may also include measurements related to SMS over NAS. In some examples, these measurements distinguish between instances of 3GPP access (e.g., access according to 3GPP standards) and non-3GPP access. In other examples, these measurements are made without distinguishing between 3GPP and non-3GPP access.

[0257] In some examples, performance measurements related to SMS over NAS include measurements of registrations of SMS over NAS. The measurement may provide the number of SMS over NAS registration requests received by the AF from the UE. In some examples, the measurement is collected by a cumulative counter (e.g., an integer value) that is updated in response to a registration request message containing an "SMS support" indication received by the AMF from the UE, the registration request message indicating that the UE supports SMS delivery over NAS (see, e.g., 3GPP TS 23.502). In some examples, the measurement is divided into sub-counters (each of which may be an integer value) based on access type (e.g., 3GPP access or non-3GPP access), and each registration request message increments the relevant sub-counter based on the access type. In other examples, no distinction is made between access types (e.g., all registration request messages increment a single counter). In some examples, the measurement type (e.g., as defined in 3GPP TS 32.404) of the measurement is AT.SmsOverNasRegReq (or AT.SmsOverNasReg3GPPReq and AT.SmsOverNasRegNon3GPPReq in the case of access differentiation). In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is AMFFuntion. The measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0258] In some examples, performance measurements related to SMS over NAS include measurements of successful registrations of SMS over NAS. The measurement may provide the number of successful registrations allowed for SMS over NAS sent by the AF to the UE. In some examples, the measurement is collected by a cumulative counter (e.g., an integer value) that is updated in response to a Registration Accept message containing an "SMS allowed" indication transmitted by the AMF to the UE (see, e.g., 3GPP TS 23.502). In some examples, the measurement is divided into sub-counters (each of which may be an integer value) based on access type (e.g., 3GPP access or non-3GPP access), and each Registration Accept message increments the relevant sub-counter based on the access type. In other examples, no distinction is made between access types (e.g., all Registration Accept messages increment a single counter). In some examples, the measurement type (e.g., as defined in 3GPP TS 32.404) of this measurement is AT.SmsOverNasRegSucc (or AT.SmsOverNasReg3GPPSucc and AT.SmsOverNasRegNon3GPPSucc in the case of access differentiation). In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is AMFFuntion. This measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0259] In some examples, performance measurements related to SMS over NAS include measurements of attempted Mobile Originated (MO) SMS messages over NAS. This measurement may provide the number of NAS messages that encapsulate SMS messages received by the AF from the UE. In some examples, the measurement is collected by a cumulative counter (e.g., an integer value) that is updated in response to a NAS message received by the AMF from the UE with an indication of SMS transmission (see, e.g., 3GPP TS 23.502). In some examples, the measurement is divided into sub-counters (each of which may be an integer value) based on the access type used for the message (e.g., 3GPP access or non-3GPP access), and each message increments the relevant sub-counter based on the access type. In other examples, no distinction is made between access types (e.g., all messages increment a single counter). In some examples, the measurement type (e.g., as defined in 3GPP TS 32.404) of the measurement is AT.SmsOverNasMoReq (or AT.SmsOverNasMo3GPPReq and AT.SmsOverNasRegMo3GPPReq in the case of access differentiation). In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is AMFFuntion. The measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0260] In some examples, performance measurements related to SMS over NAS include measurements of successful MO SMS messages over NAS. This measurement may provide the number of MO SMS messages successfully transmitted over NAS. In some examples, this measurement is collected by a cumulative counter (e.g., an integer value) that is updated in response to a NAS message transmitted by the AMF to the UE, the NAS message including a "Submission Report" indicating that the MO SMS message has been successfully delivered (see, e.g., 3GPP TS 23.502). In some examples, this measurement is divided into sub-counters (each of which may be an integer value) based on the access type used to transmit the message (e.g., 3GPP access or non-3GPP access), and each successful message increments the relevant sub-counter based on the access type. In other examples, no distinction is made between access types (e.g., all messages increment a single counter). In some examples, the measurement type (e.g., as defined in 3GPP TS 32.404) of this measurement is AT.SmsOverNasMoSucc (or AT.SmsOverNasMo3GPPSucc and AT.SmsOverNasRegMo3GPPSucc in the case of access differentiation). In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is AMFFuntion. This measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0261] In some examples, performance measurements related to SMS over NAS include measurements of attempted mobile called (MT) SMS messages over NAS. This measurement may provide the number of NAS messages that encapsulate SMS messages sent by the AF to the UE. In some examples, the measurement is collected by a cumulative counter (e.g., an integer value) that is updated in response to the transmission of a NAS message by the AMF to the UE with an indication of SMS transmission (see, for example, 3GPP TS 23.502). In some examples, the measurement is divided into sub-counters (each of which may be an integer value) based on the access type used for the message (e.g., 3GPP access or non-3GPP access), and each message increments the relevant sub-counter based on the access type. In other examples, no distinction is made between access types (e.g., all messages increment a single counter). In some examples, the measurement type (e.g., as defined in 3GPP TS 32.404) of this measurement is AT.SmsOverNasMtReq (or AT.SmsOverNasMt3GPPReq and AT.SmsOverNasRegMt3GPPReq in the case of access differentiation). In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is AMFFuntion. This measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0262] In some examples, performance measurements related to SMS over NAS include measurements of successful MT SMS messages over NAS. This measurement may provide the number of MT SMS messages successfully transmitted over NAS. In some examples, this measurement is collected by a cumulative counter (e.g., an integer value) that is updated in response to a NAS message received by the AMF from the UE, the NAS message including a "delivery report" indicating that the MT SMS message has been successfully delivered (see, e.g., 3GPP TS 23.502). In some examples, this measurement is divided into sub-counters (each of which may be an integer value) based on the access type used to transmit the message (e.g., 3GPP access or non-3GPP access), and each successful message increments the relevant sub-counter based on the access type. In other examples, no distinction is made between access types (e.g., all messages increment a single counter). In some examples, the measurement type (e.g., as defined in 3GPP TS 32.404) of this measurement is AT.SmsOverNasMtSucc (or AT.SmsOverNasMt3GPPSucc and AT.SmsOverNasRegMt3GPPSucc in the case of access differentiation). In some examples, the measurement object class (e.g., as defined in 3GPP TS 32.404) is AMFFuntion. This measurement may be valid for packet switched traffic and may be a pure 5GS measurement.

[0263] Figure 15 A flow chart of an exemplary process 1500 for performance measurements related to application triggering and SMS over NAS is shown. In some examples, Figures 1 to 14 An electronic device, network, system, chip, or component, or a portion or specific implementation thereof, may be configured to perform process 1500.

[0264] The operations of process 1500 include obtaining raw performance measurements from one or more network functions in a wireless communication network (1502). The one or more network functions include at least one of a network exposure function (NEF) or an access and mobility management function (AMF). The raw performance measurements can be obtained, for example, by a core network (e.g., core networks 120, 220, 320, such as a 5G core network) or another component of the wireless communication system 100.

[0265] Performance measurements (or performance indicators) are generated for one or more network functions based on the raw performance measurements (1504). In some examples, the one or more network functions are NEFs (e.g., NEF 323) and the performance measurements are related to application triggers requested by application functions (e.g., AF 328). In some examples, the one or more network functions are AMFs (e.g., AMF 321) and the performance measurements are related to short message services (SMS) over non-access stratum (NAS). In some examples, the performance measurements are specified as part of a communication standard, such as a 3GPP standard (e.g., in 3GPP TS 28.552). In some examples, a service producer, such as one of the one or more NEFs, the AMF, or another management function (e.g., a management function of the core network 120, 220, 320), obtains the raw performance measurements and / or generates the performance measurements. The generated performance measurements can be stored, transmitted, displayed, or otherwise provided to an end user (eg, a service consumer, a UE 101, 201, 301, a user accessing an exposure point of the core network 120, 220, 320, etc.) in any suitable form.

[0266] In some examples, the performance measurement may include one or more of the following: the number of application trigger requests, the number of application trigger requests accepted for delivery, the number of application trigger requests rejected for delivery, the number of protocol data unit (PDU) sessions requested for modification, or the number of application trigger delivery reports. The number of application trigger requests may be based on a cumulative counter that is triggered when a delivery request (e.g., Nnef_Trigger_Delivery request) is received by the NEF from the application function. The number of application trigger requests accepted for delivery may be based on a cumulative counter that is triggered when a delivery response (e.g., Nnef_trigger_Delivery response) is transmitted by the NEF to the application function, wherein the delivery response includes an indication that the application trigger request has been accepted for delivery to the UE. The number of application trigger requests rejected for delivery may be based on a cumulative counter that is triggered when a delivery response (e.g., Nnef_Trigger_Delivery response) is transmitted by the NEF to the application function, wherein the delivery response includes an indication that the application trigger request has been rejected for delivery to the UE. In some examples, the number of application-triggered delivery requests that are rejected for delivery may be incremented by an error code (e.g., by a response code, as specified in a 3GPP technical specification). The number of application-triggered delivery reports may be based on a cumulative counter that is triggered when a delivery message (e.g., an Nnef_Trigger_DeliveryNotify message) is transmitted by the NEF to the application function, where the delivery message includes an indication of the application-triggered delivery result. In some examples, the number of application-triggered delivery reports may be incremented by a delivery result (e.g., success, failure, or another result specified in a 3GPP technical specification).

[0267] In some examples, the performance measurements include one or more of the following: the number of registration requests for SMS over the NAS, the number of successful registrations allowed for SMS over the NAS, the number of attempted mobile originating (MO) SMS messages over the NAS, the number of MO SMS messages successfully transmitted over the NAS, the number of attempted mobile terminated (MT) SMS messages over the NAS, or the number of MT SMS messages successfully transmitted over the NAS.

[0268] The number of registration requests for SMS over NAS may be based on a cumulative counter that is triggered when a Registration Request message is received by the AMF from the UE, the Registration Request message including an indication that the UE supports SMS delivery over NAS (e.g., "SMS Supported" as specified in 3GPP TS 23.502). The number of successful registrations allowed for SMS over NAS may be based on a cumulative counter that is triggered when a Registration Accept message is transmitted by the AMF to the UE, the Registration Accept message including an indication that SMS is allowed (e.g., "SMS Allowed" as specified in 3GPP TS 23.502).

[0269] The number of attempted MO SMS messages over NAS may be based on a cumulative counter that is triggered when a NAS message is received by the AMF from the UE, the NAS message including an indication of SMS delivery. The number of successfully delivered MO SMS messages over NAS may be based on a cumulative counter that is triggered when a NAS message is transmitted by the AMF to the UE, the NAS message including an indication that the MO SMS message has been successfully delivered.

[0270] The number of attempted MT SMS messages over NAS may be based on a cumulative counter that is triggered when a NAS message is transmitted by the AMF to the UE, the NAS message including an indication of SMS transmission. The number of successfully transmitted MT SMS messages over NAS may be based on a cumulative counter that is triggered when a NAS message is received by the AMF from the UE, the NAS message including an indication that the MT SMS message has been successfully delivered.

[0271] In some examples, performance measurements may be separated by access type (e.g., 3GPP access and non-3GPP access). In other examples, performance measurements may be made regardless of access type.

[0272] Below are some non-limiting examples. The following examples relate to additional embodiments, and the details in the examples can be used anywhere in one or more embodiments previously discussed. Any of the following examples can be combined with any other example or any embodiment discussed herein.

[0273] Embodiment 1 may include a service producer supported by one or more processors configured to: obtain raw performance measurements from a NEF; and generate performance measurements for the NEF based on the raw performance measurements.

[0274] Embodiment 2 may include a service producer of embodiment 1 and / or some other embodiments herein, wherein the service producer is located in a NEF or a management function.

[0275] Embodiment 3 may include the service producer of embodiments 1 and 2 and / or some other embodiments herein, wherein the performance measurement is related to an application trigger requested by an AF.

[0276] Embodiment 4 may include a service producer of embodiment 3 and / or some other embodiments herein, wherein the performance measure is the number of application triggered requests, the number of application triggered requests accepted for delivery, the number of application triggered requests rejected for delivery, the number of PDU sessions requested for modification, or the number of application triggered delivery reports.

[0277] Embodiment 5 may include the service producer of embodiment 4 or some other embodiments herein, wherein: the performance measurement of the number of application trigger requests is a cumulative counter (CC) that is triggered when the NEF receives an Nnef_Trigger_Delivery request from the AF; the performance measurement of the number of application trigger requests accepted for delivery is a CC that is triggered when the NEF transmits an Nnef_Trigger_Delivery response to the AF, which indicates that the application trigger request has been accepted for delivery to the UE; the performance measurement of the number of application trigger requests rejected for delivery is a CC that is triggered when the NEF transmits an Nnef_Trigger_Delivery response to the AF, which indicates that the application trigger request has been rejected for delivery to the UE; and the performance measurement of the number of application trigger delivery reports is a CC that is triggered when the NEF transmits an Nnef_Trigger_DeliveryNotify message to the AF, which indicates the application triggered delivery result.

[0278] Embodiment 6 may include the service producer of embodiments 4 and 5 and / or some other embodiments herein, wherein a performance measure of the number of application-triggered requests rejected for delivery is incremented to a relevant sub-counter per error code.

[0279] Embodiment 7 may include the service producer of embodiments 4 and 5 and / or some other embodiments herein, wherein a performance measure of the number of application-triggered delivery reports is incremented to a relevant sub-counter according to the delivery results.

[0280] Embodiment 8 may include a service producer supported by one or more processors configured to: obtain raw performance measurements from an AMF; and generate performance measurements for the AMF based on the raw performance measurements.

[0281] Embodiment 9 may include a service producer of embodiment 8 and / or some other embodiments herein, wherein the service producer is located in the AMF or management function.

[0282] Embodiment 10 may include the service producer of embodiments 8 and 9 and / or some other embodiments herein, wherein the performance measurement relates to SMS over NAS.

[0283] Embodiment 11 may include the service producer of embodiment 10 and / or some other embodiments herein, wherein the performance measurement is the number of registration requests for SMS over NAS, the number of successful registrations allowed for SMS over NAS, the number of attempted MO SMS messages over NAS, the number of MO SMS messages successfully transmitted over NAS, the number of attempted MT SMS messages over NAS, or the number of MT SMS messages successfully transmitted over NAS.

[0284] Embodiment 12 may include the service producer of embodiment 11 and / or some other embodiments herein, wherein: the performance measurement of the number of registration requests for SMS over NAS is a CC triggered when the AMF receives a registration request message containing an "SMS support" indication from the UE, the registration request message indicating that the UE supports SMS delivery over NAS; the performance measurement of the number of successful registrations allowed for SMS over NAS is a CC triggered when the AMF transmits a registration accept message containing an "SMS allowed" indication to the UE; the performance measurement of the number of attempted MO SMS messages over NAS is a CC triggered when the AMF receives a NAS message from the UE, the NAS message having an indication for SMS delivery; the performance measurement of the number of successfully transmitted MO SMS messages over NAS is a CC triggered when the AMF transmits a NAS message to the UE, the NAS message containing a "submission report" indicating that the MO SMS message has been successfully delivered; the performance measurement of the number of attempted MT SMS messages over NAS is a CC triggered when the AMF transmits a NAS message to the UE, the NAS message having an indication for SMS delivery; the performance measurement of the number of successfully transmitted MT SMS messages over NAS is a CC triggered when the AMF transmits a NAS message to the UE, the NAS message having an indication for SMS delivery; The performance measurement of the number of SMS messages is CC triggered when a NAS message is received by the AMF from the UE, which contains a “Delivery Report” indicating that the MT SMS message has been successfully delivered.

[0285] Embodiment 13 may include the service producer of embodiments 10 and 11 and / or some other embodiments herein, wherein the performance measurement is for the case of SMS over NAS accessed via 3GPP.

[0286] Embodiment 14 may include the service producer of embodiments 10 and 11 and / or some other embodiments herein, wherein the performance measurement is for the case of SMS over NAS via non-3GPP access.

[0287] Embodiment 15 may include the service producer of embodiment 13 and / or some other embodiments herein, wherein the message triggering the counter of embodiment 12 is received or sent via 3GPP access.

[0288] Embodiment 16 may include the service producer of embodiment 14 and / or some other embodiments herein, wherein the message that triggers the counter of embodiment 12 is received or sent via a non-3GPP access.

[0289] Embodiment 17 may include a method to be performed by a service producer, the method comprising: obtaining or causing to be obtained raw performance measurements from one or more NFs; and generating or causing to be generated performance measurements (or performance indicators) for one or more NFs based on the raw performance measurements.

[0290] Example 18 may include the method of Example 17 and / or some other examples herein, wherein one or more NFs are NEFs.

[0291] Embodiment 19 may include the method of embodiment 18 and / or some other embodiments herein, wherein the service producer is located in one of the one or more NEFs or management functions.

[0292] Embodiment 20 may include the method of embodiments 18 and 19 and / or some other embodiments herein, wherein the generated performance measurements are related to application triggers requested by the AF.

[0293] Embodiment 21 may include the method of embodiment 20 and / or some other embodiments herein, wherein the performance measurement includes one or more of the following: the number of application triggered requests, the number of application triggered requests accepted for delivery, the number of application triggered requests rejected for delivery, the number of PDU sessions requested for modification, and / or the number of application triggered delivery reports.

[0294] Embodiment 22 may include the method of embodiment 21 and / or some other embodiments herein, wherein the number of application trigger requests is based on the CCs that are triggered when the Nnef_Trigger_Delivery request is received by the NEF from the AF.

[0295] Embodiment 23 may include the methods of embodiments 21 to 22 and / or some other embodiments herein, wherein the number of application trigger requests accepted for delivery is based on the CCs triggered when an Nnef_Trigger_Delivery response is transmitted by the NEF to the AF, indicating that the application trigger request has been accepted for delivery to the UE.

[0296] Embodiment 24 may include the methods of embodiments 21 to 23 and / or some other embodiments herein, wherein the number of application trigger requests rejected for delivery is based on the CCs triggered when an Nnef_Trigger_Delivery response is transmitted by the NEF to the AF, indicating that the application trigger request has been rejected for delivery to the UE.

[0297] Embodiment 25 may include the method of embodiment 24 and / or some other embodiments herein, wherein a number of application-triggered requests rejected for delivery is incremented to a relevant sub-counter according to an error code.

[0298] Embodiment 26 may include the methods of embodiments 21 to 25 and / or some other embodiments herein, wherein the number of application-triggered delivery reports is based on CCs triggered when an Nnef_Trigger_DeliveryNotify message is transmitted from the NEF to the AF, the message indicating the application-triggered delivery result.

[0299] Embodiment 27 may include the method of embodiment 26 and / or some other embodiments herein, wherein the number of application-triggered delivery reports is incremented to a related sub-counter according to the delivery result.

[0300] Example 28 may include the method of Example 17 and / or some other examples herein, wherein one or more NFs are AMFs.

[0301] Embodiment 29 may include the method of embodiment 28 and / or some other embodiments herein, wherein the service producer is located in one of the one or more AMFs or management functions.

[0302] Embodiment 30 may include the method of embodiment 28 or 29 and / or some other embodiments herein, wherein the generated performance measurements relate to SMS over NAS.

[0303] Embodiment 31 may include the method of embodiment 30 and / or some other embodiments herein, wherein the performance measurement comprises one or more of the following: the number of registration requests for SMS over NAS, the number of successful registrations allowed for SMS over NAS, the number of attempted MO SMS messages over NAS, the number of MO SMS messages successfully transmitted over NAS, the number of attempted MT SMS messages over NAS, or the number of MT SMS messages successfully transmitted over NAS.

[0304] Embodiment 32 may include the method of embodiment 31 and / or some other embodiments herein, wherein the number of registration requests for SMS over NAS is a CC triggered when the AMF receives a registration request message containing an "SMS support" indication from the UE, the registration request message indicating that the UE supports SMS delivery over NAS.

[0305] Embodiment 33 may include the method of embodiment 31 or 32 and / or some other embodiments herein, wherein the number of successful registrations allowed for SMS over NAS is a CC triggered when a registration accept message including an "SMS allowed" indication is transmitted by the AMF to the UE.

[0306] Embodiment 34 may include the methods of embodiments 31 to 33 and / or some other embodiments herein, wherein the number of attempted MO SMS messages on NAS is a CC triggered when a NAS message is received by the AMF from the UE, the NAS message having an indication for SMS transmission.

[0307] Embodiment 35 may include the methods of embodiments 31 to 34 and / or some other embodiments herein, wherein the number of MO SMS messages successfully transmitted on the NAS is a CC triggered when the AMF transmits a NAS message to the UE, the NAS message containing a "Submission Report" indicating that the MO SMS message has been successfully delivered.

[0308] Embodiment 36 may include the methods of embodiments 31 to 35 and / or some other embodiments herein, wherein the number of attempted MT SMS messages on NAS is a CC triggered when a NAS message is transmitted by the AMF to the UE, the NAS message having an indication for SMS transmission.

[0309] Embodiment 37 may include the methods of embodiments 31 to 36 and / or some other embodiments herein, wherein the number of MT SMS messages successfully transmitted on the NAS is a CC triggered when the AMF receives a NAS message from the UE, the NAS message containing a "delivery report" indicating that the MT SMS message has been successfully delivered.

[0310] Embodiment 38 may include the methods of embodiments 31 and 37 and / or some other embodiments herein, wherein the performance measurement is for the case of SMS over NAS accessed via 3GPP.

[0311] Embodiment 39 may include the method of embodiment 38 and / or some other embodiments herein, wherein the message triggering the CC is received or sent via 3GPP access.

[0312] Embodiment 40 may include the methods of embodiments 31 and 39 and / or some other embodiments herein, wherein the performance measurement is for the case of SMS over NAS via non-3GPP access.

[0313] Embodiment 41 may include the method of embodiment 40 and / or some other embodiments herein, wherein the message triggering the CC is received or sent via a non-3GPP access.

[0314] Example 42 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Examples 1-41, or any other method or process described herein.

[0315] Embodiment 43 may include one or more non-transitory computer-readable media comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 41 or any other method or process described herein.

[0316] Embodiment 44 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of Embodiments 1-41, or any other method or process described herein.

[0317] Example 45 may include a method, technique, or process as described or related to any one of Examples 1 to 41, or a portion or component thereof.

[0318] Example 46 may include a device comprising: one or more processors and one or more computer-readable media, the 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 methods, techniques, or processes described in or related to any one of Examples 1 to 41, or portions thereof.

[0319] Embodiment 47 may include a signal as described or associated with any one of Embodiments 1 to 41, or a portion or component thereof.

[0320] Embodiment 48 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message as described in or related to any of Embodiments 1 to 41, or a portion or component thereof, or otherwise described in this disclosure.

[0321] Embodiment 49 may include a signal encoded with data as described in or related to any one of Embodiments 1 to 41, or a portion or component thereof, or as otherwise described in this disclosure.

[0322] Embodiment 50 may include a signal encoding a datagram, packet, frame, segment, protocol data unit (PDU) or message as described in or associated with any of Embodiments 1 to 41, or a portion or component thereof, or otherwise described in this disclosure.

[0323] Embodiment 51 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform the method, technique, or process described in or related to any one of Embodiments 1 to 41, or a portion thereof.

[0324] Embodiment 52 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process described in or related to any one of Embodiments 1 to 41, or a portion thereof.

[0325] Embodiment 53 may include signals in a wireless network as shown and described herein.

[0326] Embodiment 54 may include a method of communicating in a wireless network as shown and described herein.

[0327] Embodiment 55 may include a system for providing wireless communications as shown and described herein.

[0328] Embodiment 56 may include an apparatus for providing wireless communications as shown and described herein.

[0329] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

[0330] In different specific implementations, the methods described herein can be implemented in software, hardware, or a combination thereof. In addition, the order of the method blocks can be changed, and various elements can be added, reordered, combined, omitted, modified, etc. Various modifications and changes can be made, which will be apparent to those skilled in the art who benefit from this disclosure. The various specific implementations described herein are intended to be illustrative and not restrictive. Many variations, modifications, additions, and improvements are possible. Therefore, multiple examples can be provided for the components described herein as a single example. The boundaries between various components, operations, and data repositories are arbitrary to a certain extent, and specific operations are shown in the context of specific exemplary configurations. Other allocations of functions are contemplated and may fall within the scope of the appended claims. Finally, the structures and functions presented as discrete components in the exemplary configurations may be implemented as combined structures or components.

[0331] The following terms and definitions may apply to the examples described herein.

[0332] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or memory (shared, dedicated, or group) configured to provide the described functionality, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some embodiments, the circuit can execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" can also refer to a combination of one or more hardware elements and program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code can be referred to as a specific type of circuit.

[0333] As used herein, the term "processor circuitry" means, is part of, or includes circuitry that is capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting 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 with "processor circuitry" and may be referred to as "processor circuitry."

[0334] As used herein, the term "interface circuitry" refers to circuitry that enables, is part of, or includes information exchange between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, and the like.

[0335] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can represent a remote user of network resources in a communication network. Furthermore, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0336] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as networked computers, networking hardware, network equipment, network nodes, routers, switches, hubs, bridges, radio network controllers, RAN equipment, RAN nodes, gateways, servers, virtualized VNFs, NFVIs, etc.

[0337] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[0338] As used herein, the terms "appliance," "computer appliance," and the like refer to a computer device or computer system having program code (e.g., software or firmware) specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[0339] The term "element" refers to an indivisible unit with well-defined boundaries at a given level of abstraction, where an element may be any type of entity including, for example, one or more devices, systems, controllers, network elements, modules, etc., or a combination thereof.

[0340] The term "device" refers to a physical entity that is embedded within or attached to another physical entity in its vicinity that has the capability to transfer digital information to or from the physical entity.

[0341] The term "entity" refers to the different components of an architecture or device, or the information passed as a payload.

[0342] The term "controller" refers to an element or entity that has the ability to affect a physical entity, such as by changing its state or causing the physical entity to move.

[0343] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time and / or processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, ports or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database, and application, workload units, etc. "Hardware resources" may refer to the computing, storage, and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to the computing, storage, and / or network resources provided by a virtualization infrastructure to applications, devices, systems, etc. The terms "network resources" or "communication resources" may refer to resources accessible to a computer device / system via a communication network. The term "system resources" may refer to any type of shared entity that provides a service and may include computing resources and / or network resources. System resources may be considered a set of coherent functions, network data objects, or services accessible through a server, where such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0344] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," and / or any other similar terms indicating a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices over a RAT for transmitting and receiving information.

[0345] The term "communication protocol" (wired or wireless) refers to a set of standardized rules or instructions implemented by communication devices and / or systems to communicate with other devices and / or systems, including instructions for packetizing / unpacking data, modulating / demodulating signals, implementing protocol stacks, etc.

[0346] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0347] As used herein, the terms "coupled," "communicably coupled," and their derivatives are used. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements are in indirect contact with one another but still cooperate or interact with one another, and / or may mean that one or more other elements are coupled or connected between the elements said to be coupled to one another. The term "directly coupled" may mean that two or more elements are in direct contact with one another. The term "communicably coupled" may mean that two or more elements may be in contact with one another by means of communication, including through wires or other interconnections, through wireless communication channels or links, and the like.

[0348] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents.

[0349] The term "admission control" refers to a verification process in a communication system where a check is performed before a connection is established to see if the current resources are sufficient for the proposed connection.

[0350] The term "IP latency" is the time it takes to transmit the first / initial packet in a burst of data from one point to another.

[0351] The term "mapped 5QI" refers to the 5G QoS Identifier (5QI) used for a Data Radio Bearer (DRB) within a gNB when a single 5QI is assigned to the DRB, and / or the 5QI used to separate certain measurements by QoS class. Separate QoS flows into a common 5QI are specified in 3GPP TS 38.473.

[0352] The term "packet delay" refers to the time it takes to transmit any packet from one point to another.

[0353] The term "packet loss rate" refers to the share of packets that are not sent to the destination due to high traffic load or high management, and should be considered as part of the packet loss rate.

[0354] The term "packet loss rate" refers to the fraction of packets that a destination cannot receive, including dropped packets, packets lost in transmission, and packets received with format errors.

[0355] The term "performance metric" refers to performance data aggregated across one or more NFs according to the aggregation method identified in the performance metric definition, which performance data is derived from performance measurements collected at the NFs.

[0356] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0357] The term "SSB" refers to SS / PBCH block.

[0358] The term "primary cell" refers to an MCG cell operating on a primary frequency, where the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0359] The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when reconfiguration is performed using a synchronization procedure for DC operation.

[0360] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured with CA.

[0361] The term "secondary cell group" refers to a subset of serving cells including a PSCell for a UE configured with DC and zero or more secondary cells.

[0362] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED without CA / DC configured, where there is only one serving cell including the primary cell.

[0363] The term "serving cell" refers to a cell group including a special cell for a UE configured with CA / DC and in RRC_CONNECTED and all secondary cells.

[0364] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.

Claims

1. A method of communication, include: obtaining data indicative of a response to a trigger request in a wireless communication network; as well as At least one measurement is performed based at least in part on the data, the at least one measurement being associated with a number of triggered requests that were denied delivery and incrementing a sub-counter per error code.

2. The method of claim 1, wherein the trigger request comprises an application trigger request received by a network exposure function NEF from an application function AF.

3. The method of claim 2, wherein the response comprises a delivery response from the NEF to the AF, the delivery response indicating whether the application trigger request has been successfully delivered.

4. The method of claim 3, wherein the at least one measurement is updated in response to transmission by the NEF to the AF of the delivery response indicating that the application trigger request was not successfully delivered.

5. The method of claim 1, wherein the number of triggered requests rejected for delivery is divided into sub-counters according to error codes.

6. The method of claim 5, wherein the number of triggered requests rejected for delivery increments an associated one of the sub-counters according to an error code.

7. The method of claim 5, wherein the data indicative of the response to the trigger request comprises an error code resulting in a denial of delivery of the trigger request, and wherein performing the at least one measurement comprises incrementing a sub-counter based on the error code.

8. A method of communication, include: obtaining data indicative of a response to a trigger request in a wireless communication network; as well as Measurements are performed based on the data, wherein at least one of the measurements comprises a number of triggered requests accepted for delivery.

9. The method of claim 8, wherein the trigger request comprises an application trigger request received by a network exposure function NEF from an application function AF.

10. The method of claim 9, wherein the response comprises a delivery response by the NEF to the AF, the delivery response indicating that the application trigger request has been accepted for delivery to a user equipment (UE) or rejected for delivery to the UE.

11. The method of claim 10, wherein at least one of the measurements is updated in response to transmission by the NEF to the AF of the delivery response indicating that the application trigger request has been accepted for delivery to the UE.

12. The method of claim 10, wherein the delivery response comprises a Nnef_Trigger_Delivery response from the NEF to the AF.

13. The method of claim 8, wherein the at least one of the measurements comprises a cumulative counter that is incremented based on the number of triggered requests accepted for delivery.

14. A method of communication, include: receiving data indicating a report of a result of a delivery of a trigger in a wireless communication network; as well as A sub-counter is incremented based at least in part on the reporting of the delivery result, the sub-counter indicating a number of triggered delivery reports associated with a first triggered delivery result.

15. The method of claim 14, wherein the report comprises an application triggered delivery report sent by a network exposure function (NEF) to an application function (AF).

16. The method of claim 15, wherein the application triggered delivery report indicates a delivery result of an application trigger received by the NEF from the AF.

17. The method of claim 15, wherein the sub-counter is incremented in response to transmission of the application triggered delivery report by the NEF to the AF.

18. The method of claim 15, wherein the application trigger delivery report comprises an Nnef_Trigger_DeliveryNotify message sent by the NEF to the AF.

19. The method of claim 14, wherein the number of triggered delivery reports is divided into sub-counters according to delivery results, and wherein the number of triggered delivery reports increments a related one of the sub-counters according to the delivery results.

20. The method of claim 14, wherein the data of the report indicative of the delivery result comprises an indication of the delivery result for the trigger, and wherein incrementing the sub-counter is based on the delivery result.

21. An electronic device, include: at least one processor; as well as At least one computer-readable storage device storing instructions executable by the at least one processor to cause the at least one processor to perform the operations of the method according to any one of claims 1 to 20.

22. A non-transitory computer-readable medium storing instructions executable by at least one processor to cause the at least one processor to perform the operations in the method of any one of claims 1 to 20.

23. A computer program product, comprising a plurality of programs which, when executed by an electronic processor, cause the electronic processor to perform the operations of the method according to any one of claims 1 to 20.