Provide and open a user equipment (UE) communication mode associated with an application to request traffic of the application to be analyzed in a core network (CN)

Abstract

An embodiment includes a method for exchanging UE communication mode information with a core network CN in an application function AF. The method includes: providing communication information related to one or more user equipment UEs to a network exposure function NEF in the CN, the communication information including an identifier of an application associated with the AF and an indication of one or more first parameters describing a first UE communication mode associated with the application. The method further includes sending a subscription request to the NEF, where the subscription request includes an identifier of the application. Further still, the method includes receiving a report from the NEF, the report indicating an analysis of the traffic of the application based at least on the one or more first parameters.

Description

Technical Field

[0001] This application generally relates to the field of communication networks, and more particularly to techniques for network discovery and exposure of the communication pattern of a user equipment (e.g., in a communication network) to a content provider (e.g., outside the network). Background Art

[0002] In general, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or implied from the context in which it is used. All references to an / a / the element, apparatus, component, part, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, part, step, etc., unless otherwise explicitly stated. The steps of any method and / or process disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step, and / or it is implied that a step must follow or precede another step. In any appropriate case, any feature of any embodiment disclosed herein can be applied to any other embodiment. Similarly, any advantage of any embodiment can be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0003] Long Term Evolution (LTE) is an umbrella term for the so-called fourth generation (4G) radio access technology developed within the Third Generation Partnership Project (3GPP) and initially standardized in Releases 8 and 9, which is also known as Evolved UTRAN (E-UTRAN). LTE targets various licensed frequency bands and is accompanied by improvements to the non-radio aspects, commonly referred to as the System Architecture Evolution (SAE), which includes the Evolved Packet Core (EPC) network. LTE continues to evolve through subsequent releases. One of the features of Release 11 is the enhanced physical downlink control channel (ePDCCH), which aims to increase capacity and improve the spatial reuse of control channel resources, improve inter-cell interference coordination (ICIC), and support antenna beamforming and / or transmit diversity for the control channel.

[0004] Figure 1An overall exemplary architecture of a network including LTE and SAE is shown. The E-UTRAN 100 includes one or more evolved Node Bs (eNBs) (such as eNBs 105, 110, and 115) and one or more user equipments (UEs) (such as UE 120). As used in the 3GPP standards, "user equipment" or "UE" means any wireless communication device (e.g., a smart phone or a computing device) capable of communicating with network devices compliant with 3GPP standards, including the E-UTRAN as well as the UTRAN and / or GERAN, since the third-generation ("3G") and second-generation ("2G") 3GPP radio access networks are well known.

[0005] As specified by 3GPP, the E-UTRAN 100 is responsible for all radio-related functions in the network, including radio bearer control, radio access control, radio mobility control, scheduling, and dynamic allocation of resources to the UE in the uplink and downlink, as well as the security of communication with the UE. These functions reside in the eNBs (such as eNBs 105, 110, and 115). The eNBs in the E-UTRAN communicate with each other via the X1 interface, as Figure 1 shown. The eNBs are also responsible for the E-UTRAN interface to the EPC 130, specifically to the Figure 1 S1 interfaces to the mobility management entity (MME) and serving gateway (SGW), collectively referred to as MME / S-GW 134 and 138 in

[0006] general. The MME / S-GW generally handles both the overall control of the UE and the data flow between the UE and the rest of the EPC. More specifically, the MME processes the signaling (e.g., control plane) protocols between the UE and the EPC, which are referred to as non-access stratum (NAS) protocols. The S-GW handles all Internet protocol (IP) data packets (e.g., data or user plane) between the UE and the EPC and acts as a local mobility anchor for data bearers when the UE moves between eNBs such as eNBs 105, 110, and 115.

[0007] In some embodiments, the HSS 131 may be connected to a user data repository (UDR) via the Ud interface - in Figure 1Marked in the figure as EPC-UDR 135 - for communication. The EPC-UDR 135 can store user credentials after they have been encrypted by the AuC algorithm. These algorithms are not standardized (i.e., vendor-specific), such that the encrypted credentials stored in the EPC-UDR 135 are not accessible to any other vendor except the vendor of the HSS 131.

[0008] In 3GPP, the research project on the new radio interface for the fifth-generation (5G) cellular (e.g., wireless) network has been completed, and 3GPP is now standardizing this new radio interface, commonly abbreviated as NR (New Radio). Figure 2 An advanced view of the 5G network architecture consisting of the next-generation RAN (NG-RAN) 299 and the 5G core (5GC) 298 is shown. The NG-RAN 299 may include a set of gNodeBs (gNBs) connected to the 5GC via one or more NG interfaces, such as gNB 200 and 250 connected via interfaces 202 and 252, respectively. Additionally, the gNBs may be interconnected via one or more Xn interfaces, such as the Xn interface 240 between gNB 200 and 250. Regarding the NR interface to the UE, each of the gNBs may support frequency-division duplex (FDD), time-division duplex (TDD), or a combination thereof.

[0009] The NG-RAN 299 is layered into a radio network layer (RNL) and a transport network layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes and the interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the relevant TNL protocol and functionality are specified. The TNL provides services for user plane transport and signaling transport. In some exemplary configurations, each gNB is connected to all 5GC nodes within the "AMF area" defined in 3GPP TS 23.501. If security protection of the CP and UP data on the TNL of the NG-RAN interface is supported, then NDS / IP (3GPP TS 33.401) will be applied.

[0010] Figure 2The NG RAN logical nodes shown (and described in 3GPP TS 38.401 and 3GPP TR 38.801) include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB 200 includes gNB-CU 210 as well as gNB-DU 220 and 230. The CU (e.g., gNB-CU 210) is a logical node that hosts higher layer protocols and performs various gNB functions such as controlling the operation of the DUs. Each DU is a logical node that hosts lower layer protocols and, depending on the functional division, may include various subsets of gNB functions. Thus, each of the CU and DU may include various circuits required to perform their respective functions, the circuits including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry. Additionally, the terms "central unit" and "centralized unit" may be used interchangeably herein, as may the terms "distributed unit" and "decentralized unit".

[0011] The gNB-CU is connected to the gNB-DUs via corresponding F1 logical interfaces, such as Figure 3 the interfaces 222 and 232 shown. The gNB-CU and the connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. In other words, the F1 interface is not visible outside of the gNB-CU.

[0012] Figure 3 Shows a high-level view of an exemplary 5G network architecture including a Next Generation Radio Access Network (NG-RAN) 399 and a 5G Core (5GC) 398. As shown in the figure, the NG-RAN 399 may include gNBs 310 (e.g., 310a, b) and ng-eNBs 320 (e.g., 320a, b) interconnected with each other via corresponding Xn interfaces. The gNBs and ng-eNBs are also connected to the 5GC 398 via the NG interface, more specifically, to the AMF (Access and Mobility Management Function) 330 (e.g., AMF 330a, b) via the corresponding NG-C interface and to the UPF (User Plane Function) 340 (e.g., UPF 340a, b) via the corresponding NG-U interface. Additionally, the AMF340a, b may communicate with one or more Policy Control Functions (PCF, e.g., PCF 350a, b) and Network Exposure Functions (NEF, e.g., NEF 360a, b). The AMF, UPF, PCF, and NEF will be further described below.

[0013] Each of the gNBs 310 may support an NR radio interface, including Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), or a combination thereof. In contrast, each of the ng-eNBs 320 supports an LTE radio interface, but differs from a conventional LTE eNB such asFigure 1 Unlike the LTE eNB shown in

[0014] Deployments based on different 3GPP architecture options (e.g., EPC-based or 5GC-based) and UEs with different capabilities (e.g., EPC NAS and 5GC NAS) can coexist simultaneously within a network (e.g., a PLMN). It is generally assumed that a UE that can support 5GC NAS procedures can also support EPC NAS procedures (e.g., as defined in 3GPP TS24.301) to operate in a legacy network such as during roaming. Therefore, the UE will use EPC NAS or 5GC NAS procedures depending on the core network (CN) serving it.

[0015] Another change in the 5G network (e.g., in the 5GC) is that traditional peer-to-peer interfaces and protocols (e.g., those found in the LTE / EPC network) are modified by the so-called service-based architecture (SBA), in which network functions (NFs) provide one or more services to one or more service consumers. For example, this can be done through Hypertext Transfer Protocol / Representational State Transfer (HTTP / REST) application programming interfaces (APIs). Generally speaking, various services are self-contained functional entities that can be changed and modified in an isolated manner without affecting other services.

[0016] In addition, a service consists of various "service operations", which are more refined divisions of the overall service functionality. To access a service, both the service name and the target service operation must be indicated. The interaction between a service consumer and a producer can be of the "request / response" or "subscription / notification" type. In 5G SBA, the Network Repository Function (NRF) allows each network function to discover the services provided by other network functions, and the Data Storage Function (DSF) allows each network function to store its context.

[0017] As discussed above, a service can be deployed as part of a network function (NF) in 5G SBA. Further adopting this SBA model that adheres to principles such as modularity, reusability, and self-containment of NFs enables deployments to leverage the latest virtualization and software technologies. Figure 4 An exemplary non-roaming 5G reference architecture is shown, with service-based interfaces and various 3GPP-defined NFs within the control plane (CP). These include the following NFs, with additional details provided for those most relevant to the present disclosure:

[0018] · Access and Mobility Management Function (AMF) with the Namf interface;

[0019] · Session Management Function (SMF) with Nsmf interface - interacts with the decoupled user (or data) plane, creates, updates, and removes Protocol Data Unit (PDU) sessions, and manages session context together with the User Plane Function (UPF), e.g., for event reporting;

[0020] · User Plane Function (UPF) with Nupf interface - supports the handling of user plane traffic based on rules received from the SMF, including packet inspection and different enforcement actions (e.g., event detection and reporting);

[0021] · Policy Control Function (PCF) with Npcf interface - supports a unified policy framework to manage network behavior, e.g., by providing PCC rules to the SMF;

[0022] · Network Exposure Function (NEF) with Nnef interface - acts as the entry point to the operator network by securely exposing network capabilities and events provided by 3GPP NFs to the AF and providing a channel for the AF to securely provide information to the 3GPP network;

[0023] · Network Repository Function (NRF) with Nnrf interface;

[0024] · Network Slice Selection Function (NSSF) with Nnssf interface;

[0025] · Authentication Server Function (AUSF) with Nausf interface;

[0026] · Application Function (AF) with Naf interface - interacts with the 3GPP CN to provide information to the network operator and subscribe to certain events occurring in the operator network;

[0027] · Network Data Analytics Function (NWDAF) (not shown); and

[0028] · Unified Data Management (UDM) with Nudm interface.

[0029] The UDM is similar to the HSS in the LTE / EPC network discussed above. The UDM supports the generation of 3GPP AKA authentication credentials, user identity handling, access authorization based on subscription data, and other subscriber-related functions. To provide this functionality, the UDM uses subscription data (including authentication data) stored in the 5GC Unified Data Repository (UDR). In addition to the UDM, the UDR also supports the PCF to store and retrieve policy data, and the NEF to store and retrieve application data.

[0030] 3GPP Rel-15 also specifies a Network Data Analytics Function (NWDAF), which includes a service (referred to as "Nnwdaf") that facilitates basic policy and network slice control based on analytics information, where the analytics information may include statistical information and / or prediction information of past events. 3GPP Rel-16 enhances the Rel-15 analytics architecture and services based on the new 3GPP TS23.288 (v16.0.0). Different NWDAF instances may exist in the 5GC, with each analytics category having possible specializations. The capabilities of a specific NWDAF instance are described in the NWDAF profile stored in the NRF. In addition, various other NFs provide specific services that support the NWDAF.

[0031] However, there are various problems and / or deficiencies associated with these existing solutions. For example, the current techniques for providing UE communication patterns in a 5G network or other networks do not provide sufficient information for the AF to determine how a UE will actually connect and / or behave in a 5G network. Generally speaking, from the perspective of the AF, it would be desirable to extend the reporting capabilities of the core network regarding UE traffic. Summary of the Invention

[0032] Accordingly, exemplary embodiments of the present disclosure are directed to solving these and other difficulties in exchanging UE communication pattern information between the core network and an Application Function (AF) associated with an application, for example.

[0033] According to various exemplary embodiments of the present disclosure, the exemplary embodiments of the present disclosure include methods and / or processes for exchanging UE communication pattern information with a Core Network (CN). These exemplary methods and / or processes may be performed by an Application Function (AF, e.g., an application server) associated with an application inside or outside the CN.

[0034] These exemplary methods and / or processes may include providing the CN with communication information related to one or more User Equipments (UEs). The communication information may include an identifier of an application associated with the AF, and a plurality of first parameters that describe an expected UE communication pattern associated with the application. The plurality of first parameters may be arranged in one or more sets associated with respective connection phases.

[0035] In some embodiments, each set of first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting. In some embodiments, each set of first parameters may include one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval, packet round-trip delay, and connection source. In some embodiments, at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value. In some embodiments, the communication information may include identifiers of multiple first parameters.

[0036] These exemplary methods and / or processes may further include sending a subscription request to the CN for one or more second parameters that describe the actual UE communication patterns associated with the application and one or more UEs. The subscription request may include an identifier of the application. In some embodiments, the subscription request may further include identifiers of one or more second parameters. In some embodiments, one or more of the second parameters are included in one or more of the first parameters, while in other embodiments, one or more of the second parameters include at least one parameter not included in one or more of the first parameters.

[0037] These exemplary methods and / or processes may further include receiving, from the CN, a report that includes one or more second parameters. In some embodiments, the report includes second parameters associated with a specific connection phase that is also associated with a specific set of first parameters.

[0038] Other exemplary embodiments of the present disclosure include methods and / or processes for exchanging UE communication pattern information with an application function (AF). These exemplary methods and / or processes may be performed by a network exposure function (NEF) in the CN (e.g., 5GC).

[0039] These exemplary methods and / or processes may include receiving, from the AF, communication information related to one or more user equipment (UEs). The communication information may include an identifier of the application associated with the AF, and multiple first parameters that describe the expected UE communication patterns associated with the application. The multiple first parameters may be arranged in one or more sets associated with corresponding connection phases.

[0040] In some embodiments, each set of first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting. In some embodiments, each set of first parameters may include one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval, packet round-trip delay, and connection source. In some embodiments, at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value. In some embodiments, the communication information may include identifiers of multiple first parameters.

[0041] In some embodiments, these exemplary methods and / or processes may further include sending a discovery request to a network repository function (NRF) to identify a network data analytics function (NWDAF) that supports a first parameter. In some embodiments, these exemplary methods and / or processes may further include receiving, from the NRF, an indication that a first NWDAF supports the first parameter, and sending a message including an identifier of the application and an identifier of the first parameter to the first NWDAF.

[0042] These exemplary methods and / or processes may further include receiving a subscription request from an AF for one or more second parameters that describe an actual UE communication pattern associated with the application and one or more UEs. The subscription request may include an identifier of the application, e.g., as previously received. In some embodiments, the subscription request may further include an identifier of one or more second parameters. In some embodiments, one or more second parameters are included in one or more first parameters, while in other embodiments, one or more second parameters include at least one parameter not included in one or more first parameters.

[0043] In some embodiments, these exemplary methods and / or processes may further include: determining whether the first NWDAF supports the second parameter; and based on determining that the first NWDAF supports the second parameter, sending a second subscription request to the first NWDAF. The second subscription request may include an identifier of the application and an identifier of the second parameter. In such embodiments, these exemplary methods and / or processes may further include receiving a report including one or more second parameters from the NWDAF.

[0044] These exemplary methods and / or processes may further include sending a report including one or more second parameters to the AF.

[0045] Other exemplary embodiments of the present disclosure include methods and / or processes for exchanging UE communication pattern information with an application function (AF). These exemplary methods and / or processes may be performed by a network data analytics function (NWDAF) in a CN (e.g., 5GC).

[0046] In some embodiments, these exemplary methods and / or processes may include sending a registration request to a network repository function (NRF) in the CN. The registration request may include an identifier of the NWDAF; identifiers of one or more services associated with UE communication information supported by the NWDAF; and identifiers of one or more parameters associated with UE communication that may be generated by the NWDAF.

[0047] In some embodiments, these exemplary methods and / or processes may further include receiving a message from a Network Exposure Function (NEF), the message including an identifier of an application associated with an Application Function (AF) and a plurality of first parameters describing an expected UE communication pattern associated with the application and one or more UEs. The plurality of first parameters may be arranged in one or more sets associated with respective connection phases.

[0048] In some embodiments, each set of first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting. In some embodiments, each set of first parameters may include one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source. In some embodiments, at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value. In some embodiments, the message may include identifiers of the plurality of first parameters.

[0049] These exemplary methods and / or processes may further include receiving a subscription request associated with the AF from the NEF. The subscription request may include an identifier of an application associated with the AF and an identifier of one or more second parameters describing an actual UE communication pattern associated with the application and one or more UEs.

[0050] These exemplary methods and / or processes may further include sending a request for one or more traffic metrics associated with the second parameters to a User Plane Function (UPF). The request may include an identifier of the application. In some embodiments, these exemplary methods and / or processes may further include determining one or more traffic metrics to request from the UPF based on the first parameters and the second parameters.

[0051] These exemplary methods and / or processes may further include receiving one or more traffic metrics from the UPF; determining one or more second parameters based on the traffic metrics; sending a report including the one or more second parameters to the NEF.

[0052] Other exemplary embodiments include a core network (e.g., nodes and / or functions) and an Application Function (AF) configured to perform operations corresponding to any of the exemplary methods and / or processes described herein. Other exemplary embodiments include a non-transitory computer-readable medium storing computer-executable instructions that, when executed by a processing circuit associated with such a core network node / function or AF, configure the same core network node / function or AF to perform operations corresponding to any of the exemplary methods and / or processes described herein.

[0053] In view of the accompanying drawings described briefly below, these and other objects, features, and advantages of the exemplary embodiments of the present disclosure will become apparent when reading the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 is a high-level block diagram of an exemplary architecture of an evolved UTRAN (E-UTRAN) and an evolved packet core (EPC) network evolved from Long-Term Evolution (LTE) standardized by 3GPP.

[0055] Figures 2 - 3 Shows two different high-level views of the 5G network architecture.

[0056] Figure 4 Shows an exemplary non-roaming 5G reference architecture with service-based interfaces and various network functions (NFs) in the core network as further described in 3GPP TS23.501 (v16.1.0).

[0057] Figures 5A - 5B Is a table showing two exemplary data structures that can be used to provide expected and actual UE communication mode information.

[0058] Figure 5C Shows exemplary methods and / or processes performed by an application function (AF), a network exposure function (NEF), and a network data analytics function (NWDAF) according to various exemplary embodiments of the present disclosure.

[0059] Figure 6 Shows a flow and / or sequence diagram illustrating an exemplary network data analytics function (NWDAF) registration with a network repository function (NRF) in a 5G core network (5GC) according to various exemplary embodiments of the present disclosure.

[0060] Figures 7-9 show flow and / or sequence diagrams illustrating three variants of an exemplary process for exchanging UE communication mode information between various network functions (NFs) and an application function (AF) in a 5GC according to various exemplary embodiments of the present disclosure.

[0061] Figure 10 Shows exemplary methods and / or processes performed by an application function (AF) according to various exemplary embodiments of the present disclosure.

[0062] Figure 11 Shows exemplary methods and / or processes performed by a network exposure function (NEF) according to various exemplary embodiments of the present disclosure.

[0063] Figure 12 Shows exemplary methods and / or processes performed by a network data analytics function (NWDAF) according to various exemplary embodiments of the present disclosure.

[0064] Figure 13 Illustrative embodiments of a wireless network in accordance with various illustrative embodiments of the present disclosure are shown.

[0065] Figure 14 Illustrative embodiments of a UE in accordance with various illustrative embodiments of the present disclosure are shown.

[0066] Figure 15 is a block diagram showing an illustrative virtualization environment that can be used to implement the various embodiments described herein.

[0067] Figures 16 - 17 is a block diagram of various illustrative communication systems and / or networks in accordance with various illustrative embodiments of the present disclosure.

[0068] Figures 18 - 21 is a flowchart of an illustrative method and / or process for transmitting and / or receiving user data in accordance with various illustrative embodiments of the present disclosure. Detailed Description

[0069] Some embodiments of what is contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Further, throughout the following description, the following terms are used:

[0070] · Radio node: As used herein, a "radio node" may be a "radio access node" or a "wireless device".

[0071] · Radio access node: As used herein, a "radio access node" (or "radio network node") may be any node in a radio access network (RAN) of a cellular communication network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, base stations in a 3GPP fifth generation (5G) new radio (NR) network (e.g., an NR base station (gNB) or an enhanced or evolved node B (eNB) in a 3GPP LTE network), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, home eNBs, or the like), and relay nodes.

[0072] · Core network node: As used herein, a "core network node" is any type of node in a core network. Some examples of core network nodes include, for example, a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), or the like.

[0073] · Wireless device: As used herein, a "wireless device" (or simply "WD") is any type of device that has access to a cellular communication network (i.e., is served by a cellular communication network) by wirelessly communicating with a network node and / or other wireless devices. Unless otherwise indicated, the term "wireless device" is used interchangeably herein with "user equipment" (or simply "UE"). Some examples of wireless devices include, but are not limited to, UEs and machine type communication (MTC) devices in a 3GPP network. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information through the air.

[0074] · Network node: As used herein, a "network node" is any node that is part of the core network or radio access network of a cellular communication network. Functionally, a network node is a device that is capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in the cellular communication network to enable and / or provide wireless access to the wireless device and / or to perform other functions (e.g., management) in the cellular communication network.

[0075] Note that the description given herein focuses on 3GPP cellular communication systems and thus generally uses 3GPP terms or terms similar to 3GPP terms. However, the concepts disclosed herein are not limited to 3GPP systems. Additionally, although the term "cell" is used herein, it should be understood that (especially for 5G NR) beams may be used instead of cells, and thus the concepts described herein apply equally to both cells and beams.

[0076] In this disclosure, the term "service" is generally used to refer to a collection of data associated with one or more applications that is to be delivered via a network with certain specific delivery requirements that need to be met for the applications to succeed. In this disclosure, the term "component" is generally used to refer to any component required to deliver a service. Examples of components are the RAN (e.g., E-UTRAN, NG-RAN, or parts thereof such as eNB, gNB, base station (BS), etc.), the CN (e.g., EPC, 5GC, or parts thereof, including all types of links between RAN and CN entities), and cloud infrastructure with associated resources (such as computing, storage). Generally, each component may have a "manager", a term that is typically used to refer to an entity that can collect historical information about resource utilization and provide information about the current and predicted future availability of resources associated with the component (e.g., RAN manager).

[0077] As briefly mentioned above, there are various problems and / or deficiencies associated with the amount and / or type of UE information open to the AF. For example, current techniques for providing UE communication modes in 5G networks do not provide the AF with enough information to determine how the UE will actually connect and / or behave in the 5G network.

[0078] More specifically, 3GPP TS29.122 (v16.3.0), 29.522 (v16.1.0), and 23.501 (v16.1.0) define the Nnef_ParameterProvision service that allows a content provider (e.g., the AF) to provide expected UE behavior and service-specific parameters (such as the UE's communication mode). For example, this can be done using the data type CpParameterSet defined in Figure 5A . However, this information lacks various important details about the UE communication mode to be provided, such as the expected traffic volume generated by the application associated with the AF. Therefore, for example, the 3GPP network cannot determine how the UE will actually connect and / or behave in the 3GPP network for that application.

[0079] Similarly, these specifications also define the Nnef_AnalyticsExposure service that includes an AF subscription to the UE communication mode. For example, the NWDAF can obtain (e.g., current or actual) UE communication modes and provide such information to the AF in the ueCommInfo information element (IE) of the data type AnalyEventNotif, as shown in Figure 5B . However, the content of ueCommInfo is currently undefined, so it is not exactly clear what information will be provided. Therefore, even if the subscription receives such information, the AF cannot determine how the UE actually behaves in the network.

[0080] Exemplary embodiments of the present disclosure seek to address these and other problems, challenges, and / or disputes by providing additional information in various network services to facilitate network and AF awareness of UE communication modes.

[0081] According to one aspect, a method for exchanging UE communication mode information between an Application Function (AF) and a Core Network (CN) is proposed. The method includes providing communication information related to one or more User Equipments (UEs) to a Network Exposure Function (NEF) in the CN, the communication information including an identifier of an application associated with the AF and an indication of one or more first parameters that describe a first UE communication mode associated with the application. The method further includes sending a subscription request to the NEF, where the subscription request includes the identifier of the application. Additionally, the method includes receiving a report from the NEF, the report indicating an analysis of the traffic of the application based at least on the one or more first parameters.

[0082] One or more first parameters describing a first UE communication mode may define a traffic model of the traffic of an application to be analyzed in the CN. The first UE communication mode may thus indicate the traffic model (e.g., the expected or predictable communication mode).

[0083] A subscription request may be sent for one or more second parameters, which describe a second UE communication mode associated with the application and optionally with one or more UEs. The second UE communication mode may be the actual or current communication mode actually detected in the application traffic. The second UE communication mode may be a sub-mode of the first UE communication mode (e.g., because one or more second parameters further define the first UE communication mode, which in turn is defined by one or more first parameters).

[0084] One or more second parameters may define information about the traffic of the application to be reported in the subscription.

[0085] One or more first parameters and one or more second parameters may jointly define the traffic to be reported in the subscription.

[0086] Communication information may trigger the NEF (e.g., upon receiving it) to perform a Network Data Analytics Function (NWDAF) discovery process based on one or more first parameters. The subscription request may trigger the NEF to forward one or more second parameters to the NWDAF determined by the NWDAF discovery process.

[0087] One or more first parameters may be arranged in one or more sets associated with respective connection phases. Each set of first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting. In some scenarios, for a particular set of first parameters, the communication information also includes information about the associated connection phase.

[0088] At least one of the one or more first parameters may include one or more of the following: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source. At least one of the one or more first parameters may include one or more of or be specified by one or more of the following: maximum value, minimum value, and average value. At least one of the one or more first parameters may be specified in the communication information by a parameter type and an associated parameter value (i.e., a type-value pair). One or more first parameters describing the first UE communication mode may define the traffic characteristics of the traffic to be analyzed in the CN.

[0089] One or more second parameters may define service characteristics of a service to be analyzed in the CN. The one or more second parameters may be included in the one or more first parameters. Thus, the one or more second parameters may form a subset, in particular a proper subset, of the one or more first parameters. The one or more second parameters may include at least one parameter not included in the one or more first parameters.

[0090] The communication information provided to the NEF may include identifiers of the one or more first parameters. The subscription request may include identifiers of the one or more second parameters.

[0091] The report may include one or more second parameters associated with a specific connection phase, which is also associated with a specific set of first parameters. The report may include a numerical value indicating the percentage of services associated with (e.g., satisfying the constraints defined by) the one or more second parameters.

[0092] There is also provided a method for exchanging UE communication pattern information with an application function AF, performed by a network exposure function NEF in a core network CN according to a second aspect. The method includes receiving, from the AF, communication information related to one or more user equipments (UEs), the communication information including an identifier of an application associated with the AF and an indication of one or more first parameters describing a first UE communication pattern associated with the application. The method also includes receiving, from the AF, a subscription request, where the subscription request includes an identifier of the application. Further, the method includes sending a report to the AF, the report indicating an analysis of the service of the application based at least on the one or more first parameters.

[0093] The reception of the communication information may trigger the NEF to perform a network data analytics function NWDAF discovery process based on the one or more first parameters. The subscription request received for the one or more second parameters may describe a second UE communication pattern associated with the application and the one or more UEs. Optionally, the reception of the subscription request may trigger the NEF to forward the one or more second parameters to the NWDAF determined by the NWDAF discovery process.

[0094] The one or more first parameters may be arranged in one or more sets associated with respective connection phases. Each set of first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting.

[0095] At least one of the one or more first parameters may include one or more of the following: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source. At least one of the one or more first parameters may include one or more of or be specified by one or more of the following: maximum value, minimum value, and average value.

[0096] One or more second parameters may be included in one or more first parameters. One or more second parameters may include at least one parameter not included in one or more first parameters.

[0097] The communication information received from the AF may include identifiers of one or more first parameters. The subscription request may include identifiers of one or more second parameters.

[0098] The method of the second aspect may further include sending a discovery request to a Network Repository Function (NRF) to identify a Network Data Analytics Function (NWDAF) that supports one or more first parameters, receiving an indication from the NRF that a first NWDAF supports one or more first parameters, and sending a message including an identifier of the application and identifiers of one or more first parameters to the first NWDAF. The method may also include: determining whether the first NWDAF supports one or more second parameters; and based on determining that the first NWDAF supports one or more second parameters, sending a second subscription request to the first NWDAF, the second subscription request including an identifier of the application and identifiers of one or more second parameters. The method may further include receiving a report in response to the second subscription request from the first NWDAF. The method may also include: based on determining that the first NWDAF does not support one or more second parameters, sending a second discovery request to the NRF to identify an NWDAF that supports one or more second parameters; and receiving an indication from the NRF that a second NWDAF supports one or more second parameters, wherein the second subscription request is sent to the second NWDAF instead of the first NWDAF, and the report is received from the second NWDAF instead of the first NWDAF.

[0099] The report may include or relate to one or more second parameters associated with a specific connection phase that is also associated with a specific set of one or more first parameters.

[0100] A third aspect relates to a method for exchanging user equipment (UE) communication mode information with an Application Function (AF) performed by a Network Data Analytics Function (NWDAF) in a Core Network (CN). The method includes receiving a message from a Network Exposure Function (NEF) in the CN, the message including an identifier of an application associated with the AF and an indication of one or more first parameters that describe a first UE communication mode associated with the application and with one or more UEs. The method also includes: receiving a subscription request associated with the AF from the NEF, the subscription request including an identifier of the application associated with the AF; and sending a request for one or more traffic metrics to a User Plane Function (UPF), wherein the request includes an identifier of the application. The method also includes receiving one or more traffic metrics from the UPF, analyzing the traffic metrics based at least on one or more first parameters, and sending a report indicating the analysis to the NEF.

[0101] The method of the third aspect further includes receiving, from the NEF and in a subscription request associated with the AF, an identifier of one or more second parameters that describe a second UE communication mode associated with an application and one or more UEs, and sending a request for one or more traffic metrics associated with the one or more second parameters to the UPF.

[0102] One or more first parameters may be arranged in one or more sets associated with respective connection phases. Each set of the one or more first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting. The one or more first parameters include one or more of the following: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, connection source. The one or more first parameters may include or specify one or more of the following: maximum value, minimum value, and average value.

[0103] One or more second parameters may be included in the one or more first parameters.

[0104] One or more second parameters include at least one parameter that is not included in the one or more first parameters. The method may further include: before receiving a message from the NEF, sending a registration request to a network repository function NRF, where the registration request includes an identifier of the NWDAF, identifiers of one or more services associated with UE communication information supported by the NWDAF, and identifiers of one or more parameters associated with UE communication that can be generated by the NWDAF.

[0105] In all method aspects disclosed herein, the first UE communication mode may be one of an expected and predictable UE communication mode associated with an application. Alternatively or additionally, the second UE communication mode may be one of an actual and current UE communication mode associated with an application.

[0106] An application function AF is also provided, which is configured to exchange UE communication mode information with a core network CN. The AF includes interface circuitry configured to communicate with a network exposure function NEF in the CN, and processing circuitry operably coupled to the interface circuitry. Thus, the processing circuitry and the interface circuitry are configured to perform operations corresponding to any of the method aspects in the method aspects related to the AF.

[0107] An AF is further provided, which is configured to exchange UE communication mode information with a core network CN. The AF is arranged to perform operations corresponding to any of the method aspects in the method aspects related to the AF.

[0108] There is also provided a non - transitory computer - readable medium storing computer - executable instructions which, when executed by a processing circuit associated with an AF, configure the AF to perform operations corresponding to any of the method aspects related to the AF.

[0109] There is also provided a computer program product comprising computer - executable instructions which, when executed by a processing circuit associated with an AF, configure the AF to perform operations corresponding to any of the method aspects related to the AF.

[0110] There is also provided a core network CN configured to exchange UE communication mode information with an application function AF. The CN includes one or more network nodes, and the network nodes are configured to provide at least one of a network exposure function NEF and a network data analytics function NWDAF operable to communicate with the AF. One or more of the network nodes include a processing circuit configured to perform operations corresponding to any of the methods in the second and / or third aspects.

[0111] One or more CN nodes may also be configured to provide at least one of a network repository function NRF and a user plane function UPF.

[0112] There is also provided a core network CN configured to exchange UE communication mode information with an application function AF, and the CN is arranged to perform operations corresponding to any of the methods in the second and / or third aspects.

[0113] There is also provided a non - transitory computer - readable medium storing computer - executable instructions which, when executed by a processing circuit associated with a CN, configure the CN to perform operations corresponding to any of the methods in the second and / or third aspects.

[0114] Furthermore, there is provided a computer program product which includes computer - executable instructions which, when executed by a processing circuit associated with a core network CN, configure the CN to perform operations corresponding to any of the methods in the second and / or third aspects.

[0115] Hereinafter, reference will be made to Figure 5C and the application function (AF) 660, network exposure function (NEF) 650, and network data and analytics function (NWDAF) 630 shown therein to describe the flowchart 300 of the method embodiments of the present disclosure. The NWDAF 630 and NEF 650 may be components of the CN. The AF 660 may be operated by a service provider and may be configured to communicate with one or more of the CN components (e.g., via a network such as the Internet). The AF 660 may be configured as an application server hosting one or more applications or otherwise associated with one or more applications.

[0116] The method includes step 302 of the AF 660 providing communication information related to one or more user equipments UE to the NEF 650, the communication information including an identifier of an application associated with the AF and an indication of one or more first parameters describing a first UE communication mode associated with the application (e.g., an expected or expectable service model). The indication may include one or more of the first parameters themselves (e.g., as type - value information) and / or their identifiers.

[0117] The method further includes step 304 of the NEF 650 receiving communication information related to one or more user equipments (UE) from the AF 660. In this way, the NEF 650 receives communication information including an identifier of an application associated with the AF 600, and an indication of one or more first parameters describing a first UE communication mode associated with the application.

[0118] The NEF 650 forwards at least some of the information received from the AF 660 in step 304 directly or via a proxy to the NWDAF 630. Thus, the method further includes step 306 of the NWDAF 630 receiving a message from the NEF 650, the message including an identifier of an application associated with the AF 660 and an indication of one or more first parameters describing a first UE communication mode associated with the application and associated with one or more UEs.

[0119] The method further includes step 310 of the AF 660 sending a subscription request to the NEF 650, where the subscription request includes an identifier of an application. The method further includes step 312 of the NEF 650 receiving the subscription request with the identifier of the application from the AF 660.

[0120] The NEF 650 forwards at least some of the information received from the AF 660 in step 312 directly or via a proxy to the NWDAF 630. The method thus further includes step 314 of the NWDAF 630 receiving a subscription request associated with the AF 660 (i.e., an identifier of an application associated with the AF 660) from the NEF. Then, in step 316, the NWDAF 630 sends a request for one or more traffic metrics to a user plane function UPF (not shown), where the request includes an identifier of an application. Optionally, the request may include one or more additional parameters received by the NWDAF 630 from the NEF 650 with the subscription request. In step 312, the NEF 650 may have received those additional parameters from the AF 660.

[0121] The method further includes step 318 of receiving, from a UPF, one or more traffic metrics. Optionally, the UPF may have generated the traffic metrics, considering additional parameters received from the NWDAF 630 in step 316.

[0122] Further, the method may include step 320 of the NWDAF 630 analyzing the traffic metrics received in step 318 based at least on one or more first parameters, and step 322 of sending a report indicating the analysis to the NEF 650.

[0123] After receiving the report at the NEF 650, the method includes step 324: the NEF 650 sending (e.g., forwarding) a report indicating the analysis of the applied service by the NWDAF 630 based at least on one or more first parameters to the AF 660. Further, the method includes step 326 of the AF 660 receiving, from the NEF 650, a report indicating the analysis of the applied service based at least on one or more first parameters.

[0124] The above (e.g., referring to Figure 5C ) exemplary embodiments and other aspects described below include the Nnef_AnalyticsExposure service extension, which is achieved by defining the ueCommInfo element to include a communication pattern obtained by a network operator based on UE user plane parameters. This information can be obtained from a UPF reporting the detected UE communication pattern (e.g., based on user plane parameters), such as by extending the Packet Forwarding Control Protocol (PCFP) with a Usage Reporting Rule (URR) to include such information, and / or by defining a new Nupf_EventExposure service to report the detected communication pattern. Other embodiments include the Nnef_ParameterProvision service extension by defining new parameters related to the UE communication pattern (such as the expected traffic volume generated by a specific application associated with the AF).

[0125] In other embodiments, the NWDAF may utilize both the UE communication pattern provided by the AF (e.g., with the expected traffic volume) and the detected UE communication pattern reported by the UPF to determine a corresponding model of the UE communication pattern. For example, the determination may be based on machine learning (ML) techniques.

[0126] In various embodiments, when the NWDAF registers with the Network Repository Function (NRF), the NWDAF may indicate which analysis subtype(s) it supports. Figure 6Shows a flow chart and / or sequence diagram illustrating an exemplary registration of an NWDAF with the NRF. These entities are labeled 630 and 640 respectively, but for the sake of brevity, their numerical labels will not be used to refer to them in the following description. In this document, the same reference numerals represent the same or similar components and functions. Additionally, unless specifically noted in the following description, Figure 6 the numerical labels of the operations in

[0127] are only for the sake of clarity in explanation and do not imply a specific order. In other words, unless specifically noted, the operations may be performed in an order different from the numerical labels.

[0128] o The NF to be registered (nfType = NWDAF)

[0129] o The service(s) offered by the NWDAF, such as:

[0130] -(nfService = Nnwdaf_EventsSubscription)

[0131] -(nfService = Nnwdaf_ParameterProvision)

[0132] o The analysis supported by the NWDAF:

[0133] -Event-ID = ueCommInfo

[0134] -ParameterList: All the parameters supported by the NWDAF as defined in more detail below, such as security, connection phase, etc.

[0135] In operation 2, the NRF responds to the NWDAF with an Nnrf_NFManagementResponse message. In operation 3, the NRF creates and stores an NF profile for the NWDAF that includes all the information received in operation 1, specifically the nwdafInfo data structure that includes Analytic-ID and Analytic-Subtype.

[0136] Figure 7 (collectively representing Figure 7A and Figure 7B ) shows a flow chart and / or sequence diagram that shows an exemplary process for exchanging UE communication mode information between the AF and various other NFs of the 5GC. Figure 8 (collectively representing Figure 8A and Figure 8B) shows another example where the AF also subscribes to notifications of parameters it provides (e.g., in an expected UE communication mode). Figure 9 (collectively referred to as Figure 9A and Figure 9B ) shows another example where the AF also subscribes to notifications of parameters it does not provide. As an example, the UE shown in Figures 7 - 9 can be a surveillance camera that detects when there is movement and notifies accordingly.

[0137] In Figures 7 - 9, operations occur between the UE 610, UPF 620, NWDAF 630, NRF 640, NEF 650, and AF 660 (also see Figure 5C ). For example, NWDAF 630 and NRF 640 can be Figure 6 elements with similar numbers shown in

[0138] . However, for simplicity, their numerical labels will not be used to refer to these entities in the following description. Additionally, unless specifically noted in the following description, the numerical markings of the operations in Figure 7 are only for ease of explanation and do not imply a specific order. In other words, unless specifically noted, the operations can be performed in an order different from the numerical labels (one or more). Figure 5A In operation 1, the UE establishes a PDU session with the AF according to various known techniques. In operation 2, the AF triggers an Nnef process to the NEF using the Nnef_ParameterProvision service to provide the UE communication mode including the IE, which includes Figure 5C the CpParameterSet shown in

[0139] · Connection phases [0..N]. An array of communication information parameters, each parameter identifying a phase of the connection between the UE and the network. For example, the UE does not follow the same communication mode as the server when it starts up and when it updates its firmware. It provides the following phases. Parameters shown in Figure 5A can be provided for each connection phase. For example, some exemplary phases include:

[0140] o Booting: When the UE starts to connect

[0141] o Client registration: The UE registers in the AF

[0142] o Device management: For example, the UE downloads firmware from the AF, or the AF configures how the device should connect to it.

[0143] o Information reporting: The UE sends information to the AF.

[0144] · For each connection phase, the following additional information may be included as parameters (e.g., as type-value pairs, as identifiers, and / or others):

[0145] o Security [0..1]: Boolean value

[0146] - Indicates whether the traffic is encrypted or in plain text. Boolean value.

[0147] o Data Payload Bytes [0...1] It contains the following metrics,

[0148] - Expected maximum data bytes per packet

[0149] - Expected minimum data bytes per packet

[0150] - Expected average data bytes per packet

[0151] o Data Payload Packets [0...1]: It contains the following metrics,

[0152] - Expected maximum number of packets

[0153] - Expected minimum number of packets

[0154] - Expected average number of packets

[0155] o Traffic Volume [0...1]: Expected total number of bytes.

[0156] - Expected maximum number of 5-tuples applied

[0157] - Expected minimum number of 5-tuples applied

[0158] - Expected average number of 5-tuples applied

[0159] o Number of Flows [0...1]: It contains the following metrics,

[0160] - Expected maximum number of 5-tuples applied

[0161] - Expected minimum number of 5-tuples applied

[0162] - Expected average number of 5-tuples applied

[0163] o Packet Arrival Interval Time [0...1]:

[0164] - Expected maximum time between packets

[0165] - Expected shortest time between packets

[0166] - Expected average time between packets

[0167] o Round-Trip Delay [0...1]:

[0168] - Expected end-to-end delay of the connection

[0169] - Expected end-to-end delay of the connection

[0170] - Expected end-to-end delay of the connection

[0171] o Connection source [0...1]: Initiator, e.g., first client, first server, or both.

[0172] · Identifier of the application of interest (App-ID)

[0173] · (Optional) Identifier of the UE (UE-ID) or group of IEs.

[0174] As an example, in Figure 8, the AF provides the following information (no other parameters are provided):

[0175] · Connection phase = Information

[0176] · Number of flows: Maximum = 5

[0177] · Connection source = First server

[0178] · Security = No

[0179] · App-ID = Surveillance camera.

[0180] As another example, in Figure 9, the AF provides the following information (no other parameters are provided):

[0181] · Connection phase = Information

[0182] · Number of flows: Maximum = 5

[0183] · Connection source = First server

[0184] · App-ID = Surveillance camera.

[0185] In operation 3, if the NRF supports the provided parameters, the NRF responds with OK, but if it does not support the provided parameters, it responds with an error.

[0186] In operation 4, the NEF triggers the NWDAF discovery process by sending an Nnrf_NFDiscovery request message to the NRF that includes the following information:

[0187] · NF to be discovered (nfType = NWDAF)

[0188] · Service of interest (nfService = Nnwdaf_ParameterProvision)

[0189] · Analyses of interest:

[0190] o Event-ID = ueCommInfo

[0191] o Parameter-list = connection phase, security, data payload bytes, data payload packets, traffic volume, number of flows, packet arrival interval, RTT, connection source.

[0192] As an example, in both Figures 8 - 9, the NEF requests from the NRF an NWDAF that can provide the following parameters:

[0193] · Connection phase

[0194] o Number of flows

[0195] o Connection source

[0196] o Security

[0197] This example is an optimized way of requesting specific parameters. The NEF can request more parameters than those initially provided (e.g., all parameters in the list).

[0198] In operation 5, the NRF answers the NEF with an Nnrf_NFDiscovery response message that includes an NWDAF instance. In operation 6, the NEF sends the information received in operation 2 to the NWDAF (see also step 306 in Figure 5C ). This includes an extension of the API between the NEF and the NWDAF to include the App-ID and all information elements related to the communication parameters (e.g., connection phase, security, data payload bytes, etc.). In operation 7, the NWDAF acknowledges the request.

[0199] In operation 8, the AF uses the Nnef_AnalyticsExposure service to trigger an Nnef procedure to the NEF in order to subscribe to information related to the communication with the UE (see also steps 310 and 312 in Figure 5C ). The NEF acknowledges the request in operation 9.

[0200] In the message sent in operation 8, the AF may include the following information:

[0201] · Identifier of the application of interest (App-ID).

[0202] · Optionally, the identifier of the UE (UE-ID). Note that the subscription may involve a single UE or a group of UEs.

[0203] · Optionally, the AF may subscribe to specific parameters of the communication, which are optionally included in the configuration of operation 2. Alternatively, if no parameters are included, the AF is considered to subscribe to all possible parameters (e.g., exactly or at least the parameters sent in operation 2).

[0204] For example, in Figure 8, the AF subscribes to the number of parameter streams it provided previously, while in Figure 9, the AF subscribes to parameter security it did not provide previously.

[0205] In operation 10, the NEF queries the NWDAF to see if it supports the requested AF subscription and receives an affirmative response in operation 11. Operations 10 - 11 are optional and are only required when the NWDAF previously selected in operations 6 - 7 does not support the desired subscription of the AF (or when the NEF does not know the support of the selected NWDAF). For example, it is not required in Figure 8 because the subscribed parameters are the same as the supplied parameters. On the other hand, operations 10 - 11 may be required in Figure 9.

[0206] In operation 12, the NEF sends the subscription request of the AF (e.g., in operation 8) to the NWDAF (also see step 314 in Figure 5C ). This includes the App-ID parameter, which is an extension of the API between the NEF and the NWDAF. In operation 13, the NWDAF acknowledges the message from the NEF. In operation 14, upon receiving the request, the NWDAF uses the event open API to notify the UPF that it should provide traffic metrics and / or information for the UE (or a group of UEs) associated with this request (also see step 316 in Figure 5C ). As discussed above, this can be identified by the optional UE-ID included in the subscription request.

[0207] In addition, at the same time or approximately at the same time as sending the message in operation 14, the NWDAF may trigger its analysis and / or data collection logic based on the optional parameters in the subscription request. For example, the NWDAF may trigger data collection from the UPF by sending a Nupf_EventExposureSubscribe (HTTP POST) message, which includes:

[0208] · Events of interest (e.g., event = traffic metrics). Based on this event, the UPF will report all parameters. Optionally, in some scenarios, the NWDAF may only indicate to the UPF the specific parameters that need to be reported. For example, in Figure 8, it may indicate the number of flows, security, and connection source.

[0209] · Application of interest (App-ID).

[0210] · Optionally, the identifier of the UE (UE-ID) or a group of UEs.

[0211] As another example, this can be done by extending the existing PDCP URR procedure.

[0212] In operation 15, the UPF acknowledges the message in operation 14 with OK. In operation 16, the UPF starts collecting data and / or determining metrics from the user traffic associated with the subscription request. In operation 17, the UPF provides the requested traffic metrics to the NWDAF (see also Figure 5C step 318 in

[0213] The NWDAF analyzes the traffic metrics provided by the UPF and compares them with the attributes of the model provided in operation 4 (see also Figure 5C step 320 in Figure 5C ). In operation 18, the NWDAF provides UE communication information to the NEF according to the subscription of the AF (see also Figure 5C step 322 in

[0214] ). For example, if the AF subscribes to specific parameters of UE communication, the NWDAF sends the corresponding information related to these parameters. On the other hand, if the AF has subscribed to UE communication information without specifying any parameters, the NWDAF may include all relevant parameters. In operation 19, the NEF acknowledges the message received in operation 18. In operation 20, the NEF forwards the information received from the NWDAF to the subscribing AF, and in operation 21, the AF acknowledges the message received in operation 20 (see also Figure 5C steps 324 and 326 in

[0214] As an example, in Figure 8, the AF has subscribed to the number of flows parameter. Therefore, the NWDAF analyzes the traffic against the following characteristics:

[0215] · Connection phase = Information

[0216] · Maximum number of flows = 5

[0217] · Connection source = First server

[0218] · Security = NO

[0219] Since the AF has subscribed to the number of flows parameter, the NWDAF will send the following information in operation 18:

[0220] · Number of flows: Maximum = 4, Minimum = 0, Average = 2.

[0221] · Percentage = 100%

[0222] In this case, the percentage means that 100% of the traffic analyzed by the UPF matches the characteristics.

[0223] As another example, in FIG. 9, the AF has subscribed to security parameters. Therefore, the NWDAF analyzes the service against the following characteristics:

[0224] · Connection phase = Information

[0225] · Maximum number of flows = 5

[0226] · Connection source = First server

[0227] Since the AF has subscribed to security parameters, the NWDAF will send the following information in operation 18:

[0228] · Security = Yes.

[0229] · Percentage = 80%

[0230] In this case, the percentage means that 80% of the services analyzed by the UPF match the characteristics.

[0231] The above embodiments are further illustrated by Figures 10 - 12 the exemplary methods and / or processes shown in, as described below. For example, the features of the various embodiments discussed above are included in Figures 10 - 12 the various operations of the exemplary methods and / or processes shown in. Those embodiments can be combined with Figure 5C the embodiments of.

[0232] More specifically, Figure 10 shows an exemplary method and / or process for exchanging UE communication mode information with a core network (CN) according to various exemplary embodiments of the present disclosure. Figure 10 The exemplary methods and / or processes shown in can be performed by an application function (AF, e.g., an application server) associated with an application inside or outside the CN. Although the exemplary methods and / or processes are illustrated in Figure 10 by specific boxes in a specific order, the operations corresponding to the boxes can be performed in an order different from the shown order and can be combined and / or divided into boxes and / or operations having different functionality from the shown functionality. In addition, Figure 10 the exemplary methods and / or processes shown in can be complementary to other exemplary methods and / or processes disclosed herein (e.g., Figure 6 -9, 11-12), such that they can be used in cooperation to provide benefits, advantages, and / or solutions to the problems described herein. Optional boxes and / or operations are indicated by dashed lines.

[0233] An exemplary method and / or process may include an operation at block 1010, where an AF may provide communication information related to one or more user equipments (UEs) to a CN. The communication information may include an identifier of an application associated with the AF, and a plurality of first parameters describing an expected UE communication pattern associated with the application. The plurality of first parameters may be arranged in one or more sets associated with respective connection phases. For example, this operation may correspond to operation 4 shown in FIGS. 7-9.

[0234] In some embodiments, each set of first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting. In some embodiments, each set of first parameters may include one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source. In some embodiments, at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value.

[0235] An exemplary method and / or process may include an operation at block 1020, where an AF may send a subscription request to a CN for one or more second parameters describing an actual UE communication pattern associated with an application and one or more UEs. The subscription request may include, for example, the identifier of the application also provided at block 1010. In some embodiments, the subscription request may also include an identifier of one or more second parameters. In some embodiments, one or more second parameters are included in one or more first parameters (e.g., as shown in FIG. 8), while in other embodiments, one or more second parameters include at least one parameter not included in one or more first parameters (e.g., as shown in FIG. 9).

[0236] An exemplary method and / or process may further include an operation at block 1030, where an AF may receive a report from the CN that includes one or more second parameters. In some embodiments, the report includes second parameters associated with a specific connection phase that is also associated with a specific set of first parameters. For example, the report may include second parameters associated with an "information" connection phase, as shown in FIGS. 8-9.

[0237] In addition, Figure 11 Another exemplary method and / or process for exchanging UE communication pattern information with an application function (AF) in accordance with various exemplary embodiments of the present disclosure is shown. Figure 11 The exemplary method and / or process shown may be performed by a network exposure function (NEF) in a 5GC, as described herein. Although the exemplary method and / or process is in Figure 11is illustrated by specific boxes in a specific order, but the operations corresponding to the boxes may be performed in an order different from the order shown, and may be combined and / or divided into boxes and / or operations having functionality different from the functionality shown. Additionally, Figure 11 the exemplary methods and / or processes shown herein may be complementary to other exemplary methods and / or processes disclosed herein (e.g., Figures 6 - 10 , 12), such that they can be used in concert to provide benefits, advantages, and / or solutions to the problems described herein. Optional boxes and / or operations are indicated by dashed lines.

[0238] The exemplary method and / or process may include an operation of box 1110, where the NEF may receive communication information related to one or more user equipments (UEs) from the AF. The communication information may include an identifier of an application associated with the AF, and a plurality of first parameters describing an expected UE communication pattern associated with the application. The plurality of first parameters may be arranged in one or more sets associated with respective connection phases. For example, this operation may correspond to operation 4 shown in FIGS. 7-9.

[0239] In some embodiments, each set of first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting. In some embodiments, each set of first parameters may include one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source. In some embodiments, at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value.

[0240] In some embodiments, the exemplary method and / or process may further include operations of boxes 1115-1125. In box 1115, the NEF may send a discovery request to the Network Repository Function (NRF) to identify a Network Data Analytics Function (NWDAF) that supports the first parameters. In box 1120, the NEF may receive an indication from the NRF that a first NWDAF supports the first parameters. In box 1125, the NEF may send a message to the first NWDAF, the message including: an identifier of the application and an identifier of the first parameters.

[0241] The exemplary method and / or process may also include the operation of block 1130, where the NEF may receive a subscription request from the AF for one or more second parameters that describe the actual UE communication patterns associated with the application and one or more UEs. The subscription request may include an identifier of the application, which is also received, for example, in block 1110. In some embodiments, the subscription request may also include an identifier of one or more second parameters. In some embodiments, one or more second parameters are included in one or more first parameters (e.g., as shown in FIG. 8), while in other embodiments, one or more second parameters include at least one parameter not included in one or more first parameters (e.g., as shown in FIG. 9).

[0242] In some embodiments, the exemplary method and / or process may also include some or all of the operations of blocks 1135 - 1155. In block 1135, the NEF may determine whether a first NWDAF supports the second parameter. In block 1140, based on determining that the first NWDAF supports the second parameter, the NEF may send a second subscription request to the first NWDAF. The second subscription request may include an identifier of the application and an identifier of the second parameter.

[0243] On the other hand, in block 1145, based on determining (e.g., in block 1135) that the first NWDAF does not support the second parameter, the NEF may send a second discovery request to the NRF to identify a NWDAF that supports the second parameter. In block 1150, the NEF may receive an indication from the NRF that a second NWDAF supports the second parameter. In this case, the NEF may send the second subscription request (e.g., in block 1140) to the second NWDAF instead of the first NWDAF. In block 1155, the NEF may receive a report that includes one or more second parameters. The report may be received from the first NWDAF or the second NWDAF (i.e., the NWDAF to which the second subscription request is sent), which in turn depends on the determination result in block 1135.

[0244] The exemplary method and / or process may also include the operation of block 1160, where the NEF may send a report that includes one or more second parameters to the AF. In some embodiments, the report includes second parameters associated with a specific connection phase, and the specific connection phase is also associated with a specific set of first parameters. For example, the report may include second parameters associated with the "information" connection phase, as shown in FIGS. 8 - 9.

[0245] In addition, Figure 12 Another exemplary method and / or process for exchanging UE communication pattern information with an Application Function (AF) according to various exemplary embodiments of the present disclosure is shown. Figure 12The exemplary methods and / or processes shown may be performed by a Network Data Analytics Function (NWDAF) in a 5GC, such as described herein. Although the exemplary methods and / or processes are illustrated by specific boxes in a Figure 12 specific order, the operations corresponding to the boxes may be performed in an order different from the order shown and may be combined and / or divided into boxes and / or operations having different functionality than the functionality shown. Additionally, Figure 12 the exemplary methods and / or processes shown may be complementary to other exemplary methods and / or processes disclosed herein (e.g., Figures 6 - 11 ), such that they can be used in concert to provide benefits, advantages, and / or solutions to the problems described herein. Optional boxes and / or operations are indicated by dashed lines.

[0246] In some embodiments, the exemplary methods and / or processes may include the operation of box 1210, where the NWDAF may send a registration request to a Network Repository Function (NRF) in the CN. The registration request may include an identifier of the NWDAF; identifiers of one or more services associated with UE communication information supported by the NWDAF; and identifiers of one or more parameters associated with UE communication that may be generated by the NWDAF. For example, the registration request sent in box 1210 may correspond to Figure 6 operation 1 in

[0247] In some embodiments, the exemplary methods and / or processes may further include the operation of box 1220, where the NWDAF may receive a message from a Network Exposure Function (NEF) that includes an identifier of an application associated with an Application Function (AF), and a plurality of first parameters that describe an expected UE communication pattern associated with the application and with one or more UEs. The plurality of first parameters may be arranged in one or more sets associated with respective connection phases. For example, this operation may correspond to operation 6 shown in FIGS. 7-9.

[0248] In some embodiments, each set of first parameters may be associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting. In some embodiments, each set of first parameters may include one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source. In some embodiments, at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value.

[0249] The exemplary method and / or process may further include operations of block 1230, where the NWDAF may receive a subscription request associated with the AF from the NEF. The subscription request may include an identifier of an application associated with the AF, and an identifier of one or more second parameters describing an actual UE communication pattern associated with the application and with one or more UEs. For example, these operations may correspond to operation 12 in FIGS. 7-9.

[0250] In some embodiments, one or more second parameters are included in one or more first parameters (e.g., as shown in FIG. 8), while in other embodiments, one or more second parameters include at least one parameter not included in one or more first parameters (e.g., as shown in FIG. 9).

[0251] The exemplary method and / or process may further include operations of block 1250, where the NWDAF may send a request for one or more traffic metrics associated with the second parameters to a user plane function (UPF). The request may include an identifier of the application. For example, these operations may correspond to operation 14 shown in FIGS. 7-9. In some embodiments, the exemplary method and / or process may further include operations of block 1240, where the NWDAF may determine one or more traffic metrics to request from the UPF based on the first parameters (e.g., received in block 1220) and the second parameters (e.g., received in block 1230).

[0252] The exemplary method and / or process may further include operations of block 1260, where the NWDAF may receive one or more traffic metrics from the UPF. The exemplary method and / or process may further include operations of block 1270 and block 1280, where in block 1270 the NWDAF may determine one or more second parameters based on the traffic metrics, and in block 1280 the NWDAF may send a report including the one or more second parameters to the NEF. For example, these operations may correspond to operations 16-18 shown in FIGS. 7-9.

[0253] Although the subject matter described herein may be implemented using any suitable components in any appropriate type of system, the embodiments disclosed herein are described with respect to a wireless network (such as Figure 11 the example wireless network shown). For simplicity, Figure 13The wireless network only depicts network 1306, network nodes 1360 and 1360b, and WDs 1310, 1310b, and 1310c. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Among the components shown, network node 1360 and wireless device (WD) 1310 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0254] The wireless network may include any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system and / or interface therewith. In some embodiments, the wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, a particular embodiment of the wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards such as the IEEE 802.11 standards; and / or any other suitable wireless communication standards such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0255] Network 1306 may include one or more backhaul networks, core networks, IP networks, Public Switched Telephone Network (PSTN), packet data networks, optical networks, Wide Area Networks (WAN), Local Area Networks (LAN), Wireless Local Area Networks (WLAN), wired networks, wireless networks, Metropolitan Area Networks, and other networks capable of enabling communication between devices.

[0256] Network node 1360 and WD 1310 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing a wireless connection in the wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in transmitting data and / or signals either via a wired connection or via a wireless connection.

[0257] Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node B, evolved Node B (eNB), and NR Node B (gNB)). Base stations can be classified based on the amount of coverage they provide (or, in other words, their transmission power levels), and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls a relay. A network node can also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna into a radio device with an integrated antenna. The parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS).

[0258] Further examples of network nodes include multi-standard radio (MSR) devices (such as MSR BSs), network controllers (such as radio network controllers (RNCs) or base station controllers (BSCs)), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node as described in more detail below.

[0259] In Figure 13 , the network node 1360 includes a processing circuit 1370, a device-readable medium 1380, an interface 1390, an auxiliary device 1384, a power supply 1386, a power circuit 1387, and an antenna 1362. Although the network node 1360 shown in the example wireless network of Figure 13 can represent a device including the combination of the shown hardware components, other embodiments may include network nodes with different combinations of components. It is to be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods and / or processes disclosed herein. Further, although the components of the network node 1360 are depicted as a single box located within a larger box or nested within multiple boxes, in reality, a network node can include multiple different physical components that make up a single shown component (e.g., the device-readable medium 1380 can include multiple individual hard disk drives as well as multiple RAM modules).

[0260] Similarly, network node 1360 can be composed of multiple physically separated components (e.g., NodeB components and RNC components or BTS components and BSC components, etc.), and these components can each have their own corresponding components. In some scenarios where network node 1360 includes multiple individual components (e.g., BTS and BSC components), one or more of the individual components can be shared among several network nodes. For example, a single RNC can control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair can be considered as a single individual network node in some instances. In some embodiments, network node 1360 can be configured to support multiple radio access technologies (RATs). In such embodiments, some components can be repeated (e.g., individual device-readable media 1380 for different RATs), and some components can be reused (e.g., the RATs can share the same antenna 1362). Network node 1360 can also include multiple sets of various shown components for different wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) to be integrated into network node 1360. These wireless technologies can be integrated into the same or different chips or chip sets and other components within network node 1360.

[0261] Processing circuitry 1370 can be configured to perform any determination, calculation, or similar operation described herein as being provided by the network node (e.g., certain obtaining operations). These operations performed by processing circuitry 1370 can include processing information obtained by processing circuitry 1370, which is, for example, carried out by: converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the network node, and / or performing one or more operations based on the obtained information or the converted information, and making a determination as a result of the processing.

[0262] Processing circuitry 1370 can include one or more combinations of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic that is operable to provide the functionality of network node 1360 alone or in combination with other network node 1360 components (such as device-readable medium 1380). For example, processing circuitry 1370 is capable of executing instructions stored in device-readable medium 1380 or in a memory within processing circuitry 1370. Such functionality can include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 1370 can include a system on a chip (SOC).

[0263] In some embodiments, the processing circuitry 1370 may include one or more of a radio frequency (RF) transceiver circuitry 1372 and a baseband processing circuitry 1374. In some embodiments, the radio frequency (RF) transceiver circuitry 1372 and the baseband processing circuitry 1374 may be on separate chips (or chip sets), boards, or units (such as a radio unit and a digital unit). In alternative embodiments, some or all of the RF transceiver circuitry 1372 and the baseband processing circuitry 1374 may be on the same chip or chip set, board, or unit.

[0264] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 1370 executing instructions stored on a memory or a device-readable medium 1380 within the processing circuitry 1370. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 1370 (such as, in a hardwired manner) without executing instructions stored on a separate or discrete device-readable medium. In any of those embodiments, whether or not instructions are executed on a device-readable storage medium, the processing circuitry 1370 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry 1370 alone or to other components of the network node 1360, but are enjoyed by the network node 1360 as a whole, and / or generally by the end user and the wireless network.

[0265] The device-readable medium 1380 may include any form of volatile or non-volatile computer-readable memory, including but not limited to a permanent storage device, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (such as a hard disk), removable storage media (such as a flash drive, compact disc (CD), or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device storing information, data, and / or instructions that can be used by the processing circuitry 1370. The device-readable medium 1380 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions that can be executed by the processing circuitry 1370 and utilized by the network node 1360. The device-readable medium 1380 may be used to store any calculations performed by the processing circuitry 1370 and / or any data received via the interface 1390. In some embodiments, the processing circuitry 1370 and the device-readable medium 1380 may be considered integrated.

[0266] Interface 1390 is used for wired or wireless communication of signaling and / or data between network node 1360, network 1306, and / or WD 1310. As shown, interface 1390 includes one or more ports / terminals 1394 to send data to and receive data from network 1306, for example, via a wired connection. Interface 1390 also includes radio front-end circuitry 1392, which may be coupled to antenna 1362 or, in some embodiments, is part of antenna 1362. Radio front-end circuitry 1392 includes filter 1398 and amplifier 1396. Radio front-end circuitry 1392 may be connected to antenna 1362 and processing circuitry 1370. The radio front-end circuitry may be configured to condition the signals transmitted between antenna 1362 and processing circuitry 1370. Radio front-end circuitry 1392 may receive digital data to be transmitted out to other network nodes or WDs via a wireless connection. Radio front-end circuitry 1392 may use a combination of filter 1398 and / or amplifier 1396 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. The radio signal may then be transmitted via antenna 1362. Similarly, when data is received, antenna 1362 may collect the radio signals, which are then converted into digital data by radio front-end circuitry 1392. The digital data may be passed to processing circuitry 1370. In other embodiments, the interface may include different components and / or different combinations of components.

[0267] In certain alternative embodiments, network node 1360 may not include a separate radio front-end circuitry 1392. Instead, processing circuitry 1370 may include radio front-end circuitry and may be connected to antenna 1362 without a separate radio front-end circuitry 1392. Similarly, in some embodiments, all or some of RF transceiver circuitry 1372 may be considered part of interface 1390. In still other embodiments, interface 1390 may include one or more ports or terminals 1394, radio front-end circuitry 1392, and RF transceiver circuitry 1372 as part of a radio unit (not shown), and interface 1390 may communicate with baseband processing circuitry 1374, which is part of a digital unit (not shown).

[0268] Antenna 1362 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 1362 may be coupled to radio front-end circuitry 1390 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 1362 may include one or more omnidirectional, sector, or panel antennas operable to transmit / receive radio signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas may be used to transmit / receive radio signals in any direction, sector antennas may be used to transmit / receive radio signals from devices within a particular area, and panel antennas may be line-of-sight antennas for transmitting / receiving radio signals in a relatively straight line. In some instances, using more than one antenna may be referred to as MIMO. In certain embodiments, antenna 1362 may be separate from network node 1360 and may be connectable to network node 1360 via an interface or port.

[0269] Antenna 1362, interface 1390, and / or processing circuitry 1370 may be configured to perform any of the receiving operations and / or certain obtaining operations described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network equipment. Similarly, antenna 1362, interface 1390, and / or processing circuitry 1370 may be configured to perform any of the transmitting operations described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0270] Power circuitry 1387 may include or be coupled to power management circuitry and may be configured to supply power for performing the functionality described herein to the components of network node 1360. Power circuitry 1387 may receive power from power source 1386. Power source 1386 and / or power circuitry 1387 may be configured to supply power to the respective components of network node 1360 in a form suitable for the respective components (e.g., at the voltage and current levels required for each respective component). Power source 1386 may be included within power circuitry 1387 and / or network node 1360 or external to power circuitry 1387 and / or network node 1360. For example, network node 1360 may be connectable via an input circuit or interface (such as a cable) to an external power source (such as an electrical outlet) that supplies power to power circuitry 1387. As another example, power source 1386 may include a power source in the form of a battery or battery pack that is connected to or integrated within power circuitry 1387. The battery may provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0271] Alternative embodiments of network node 1360 may include in addition to Figure 13Additional components beyond those shown in [description], which may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 1360 may include a user interface device to allow and / or facilitate the input of information into network node 1360 and to allow and / or facilitate the output of information from network node 1360. This may allow and / or facilitate a user to perform diagnostic, maintenance, repair, and other administrative functions on network node 1360.

[0272] In some embodiments, a wireless device (WD, such as WD 1310) may be configured to transmit and / or receive information without direct human interaction. For example, the WD may be designed to transmit information to the network at a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of WDs include, but are not limited to, smart phones, mobile phones, cellular phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premise equipment (CPE), machine type communication (MTC) devices, Internet of Things (IoT) devices, in-vehicle wireless terminal devices, and the like.

[0273] For example, by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X), the WD can support device-to-device (D2D) communication, and in this case the WD can be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, the WD can represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another WD and / or network node. In this case, the WD can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, the WD can be a UE that implements the 3GPP NarrowBand Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or household or personal appliances (e.g., refrigerators, TVs, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the WD can represent a vehicle or other device capable of monitoring and / or reporting its operating state or other functions associated with its operation. The WD as described above can represent an endpoint of a wireless connection, and in this case, the device can be referred to as a wireless terminal. Additionally, the WD as described above can be mobile, and in this case, it can also be referred to as a mobile device or mobile terminal.

[0274] As shown in the figure, the wireless device 1310 includes an antenna 1311, an interface 1314, a processing circuit 1320, a device-readable medium 1330, a user interface device 1332, an auxiliary device 1334, a power supply 1336, and a power circuit 1337. The WD 1310 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by the WD 1310, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few. These wireless technologies can be integrated into the same or different chips or chip sets as other components within the WD 1310.

[0275] The antenna 1311 can include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to the interface 1314. In certain alternative embodiments, the antenna 1311 can be separate from the WD 1310 and can be connected to the WD 1310 through an interface or port. The antenna 1311, the interface 1314, and / or the processing circuit 1320 can be configured to perform any of the receiving or transmitting operations described herein as being performed by the WD. Any information, data, and / or signals can be received from a network node and / or another WD. In some embodiments, the radio front-end circuit and / or the antenna 1311 can be considered an interface.

[0276] As shown in the figure, interface 1314 includes radio front-end circuit 1312 and antenna 1311. The radio front-end circuit 1312 includes one or more filters 1318 and amplifiers 1316. The radio front-end circuit 1314 is connected to antenna 1311 and processing circuit 1320, and can be configured to condition signals transmitted between antenna 1311 and processing circuit 1320. The radio front-end circuit 1312 can be coupled to antenna 1311 or be part of antenna 1311. In some embodiments, WD 1310 may not include a separate radio front-end circuit 1312; instead, the processing circuit 1320 may include a radio front-end circuit and can be connected to antenna 1311. Similarly, in some embodiments, some or all of the RF transceiver circuit 1322 can be considered part of interface 1314. The radio front-end circuit 1312 can receive digital data to be transmitted via a wireless connection to other network nodes or WDs. The radio front-end circuit 1312 can use a combination of filters 1318 and / or amplifiers 1316 to convert the digital data into a radio signal with appropriate channel and bandwidth parameters. Then, the radio signal can be transmitted via antenna 1311. Similarly, when data is received, antenna 1311 can collect radio signals, which are then converted into digital data by the radio front-end circuit 1312. The digital data can be passed to the processing circuit 1320. In other embodiments, the interface may include different components and / or different combinations of components.

[0277] The processing circuit 1320 can include one or more combinations of a microprocessor, a controller, a microcontroller, a central processing unit, a digital signal processor, an application specific integrated circuit, a field programmable gate array, or any other suitable computing device, resource, or a combination of hardware, software, and / or encoded logic operable to provide WD 1310 functionality alone or in combination with other WD 1310 components (such as device-readable medium 1330). Such functionality can include providing any of the various wireless features or benefits discussed herein. For example, the processing circuit 1320 can execute instructions stored in the device-readable medium 1330 or in a memory within the processing circuit 1320 to provide the functionality disclosed herein.

[0278] As shown in the figure, the processing circuit 1320 includes one or more of an RF transceiver circuit 1322, a baseband processing circuit 1324, and an application processing circuit 1326. In other embodiments, the processing circuit may include different components and / or different combinations of components. In certain embodiments, the processing circuit 1320 of the WD 1310 may include a SOC. In some embodiments, the RF transceiver circuit 1322, the baseband processing circuit 1324, and the application processing circuit 1326 may be on separate chips or chip sets. In an alternative embodiment, some or all of the baseband processing circuit 1324 and the application processing circuit 1326 may be combined into one chip or chip set, and the RF transceiver circuit 1322 may be on a separate chip or chip set. In yet some alternative embodiments, some or all of the RF transceiver circuit 1322 and the baseband processing circuit 1324 may be on the same chip or chip set, and the application processing circuit 1326 may be on a separate chip or chip set. In yet some alternative embodiments, some or all of the RF transceiver circuit 1322, the baseband processing circuit 1324, and the application processing circuit 1326 may be combined in the same chip or chip set. In some embodiments, the RF transceiver circuit 1322 may be part of the interface 1314. The RF transceiver circuit 1322 may condition RF signals for the processing circuit 1320.

[0279] In certain embodiments, some or all of the functionality described herein as being performed by the WD may be provided by the processing circuit 1320 executing instructions stored on a device-readable medium 1330. In certain embodiments, the device-readable medium 1330 may be a computer-readable storage medium. In an alternative embodiment, some or all of the functionality may be provided by the processing circuit 1320 (such as, in a hardwired manner) without executing instructions stored on a separate or discrete device-readable storage medium. In any of those particular embodiments, the processing circuit 1320 can be configured to perform the described functionality whether or not instructions stored on the device-readable storage medium are executed. The benefits provided by such functionality are not limited to the processing circuit 1320 alone or to other components of the WD 1310, but are enjoyed by the WD 1310 as a whole and / or generally by the end user and the wireless network.

[0280] The processing circuit 1320 may be configured to perform any determination, calculation, or similar operation described herein as being performed by the WD (e.g., certain obtaining operations). These operations as performed by the processing circuit 1320 may include processing information obtained by the processing circuit 1320, which may be done, for example, by converting the obtained information into other information, comparing the obtained information or the converted information with information stored in the WD 1310, and / or performing one or more operations based on the obtained information or the converted information and making a determination as a result of such processing.

[0281] The apparatus-readable medium 1330 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc., and / or other instructions executable by the processing circuitry 1320. The apparatus-readable medium 1330 may include a computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), a mass storage medium (e.g., a hard disk), a removable storage medium (e.g., a compact disk (CD) or a digital video disk (DVD)), and / or any other volatile or non-volatile, non-transitory apparatus-readable and / or computer-executable memory device storing information, data, and / or instructions usable by the processing circuitry 1320. In some embodiments, the processing circuitry 1320 and the apparatus-readable medium 1330 may be regarded as integrated.

[0282] The user interface device 1332 may include components that permit and / or facilitate interaction of a human user with the WD 1310. Such interaction may take many forms, such as visual, auditory, tactile, etc. The user interface device 1332 may be operable to generate output to the user and permit and / or facilitate the user to provide input to the WD 1310. The type of interaction may vary depending on the type of the user interface device 1332 installed in the WD 1310. For example, if the WD 1310 is a smart phone, the interaction may be via a touch screen; if the WD 1310 is a smart meter, the interaction may be through a screen providing usage (e.g., gallons used) or a speaker providing an auditory alert (e.g., if smoke is detected). The user interface device 1332 may include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. The user interface device 1332 is configured to permit and / or facilitate input of information into the WD 1310 and is connected to the processing circuitry 1320 to permit and / or facilitate the processing circuitry 1320 to process the input information. The user interface device 1332 may include, for example, a microphone, a proximity sensor or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device 1332 is also configured to permit and / or facilitate output of information from the WD 1310 and permit and / or facilitate the processing circuitry 1320 to output information from the WD 1310. The user interface device 1332 may include, for example, a speaker, a display, a vibration circuit, a USB port, a headphone jack, or other output circuitry. Using one or more of the input and output interfaces, devices, and circuitry of the user interface device 1332, the WD 1310 may communicate with an end user and / or a wireless network and permit and / or facilitate them to benefit from the functionality described herein.

[0283] The auxiliary device 1334 is operable to provide more specific functionality that may not typically be performed by the WD. This can include dedicated sensors for making measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device 1334 can vary according to the embodiment and / or scenario.

[0284] In some embodiments, the power source 1336 can take the form of a battery or battery pack. Other types of power sources can also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power cell. The WD 1310 can further include a power circuit 1337 for delivering power from the power source 1336 to the various parts of the WD 1310 that require power from the power source 1336 to perform any of the functionality described or indicated herein. In certain embodiments, the power circuit 1337 can include a power management circuit. The power circuit 1337 can additionally or alternatively be operable to receive power from an external power source; in such a case, the WD 1310 can be connected to an external power source (such as an electrical outlet) via an input circuit or interface (such as a power cable). In certain embodiments, the power circuit 1337 can also be operable to deliver power from an external power source to the power source 1336. For example, this can be used for charging the power source 1336. The power circuit 1337 can perform any conversion or other modification on the power from the power source 1336 to make it suitable for supply to the corresponding components of the WD 1310.

[0285] Figure 14 An embodiment of a UE in accordance with various aspects described herein is illustrated. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE can represent a device intended to be sold to or operated by a human user, but the device may not be or may not initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended to be sold to or operated by an end user but that can be associated with or operate for the benefit of a user (e.g., a smart meter). The UE 1400 can be any UE identified by the Third Generation Partnership Project (3GPP), including an NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As Figure 14 illustrated, the UE 1400 is an example of a WD configured to communicate according to one or more communication standards published by the Third Generation Partnership Project (3GPP), such as the GSM, UMTS, LTE, and / or 5G standards of 3GPP. As previously mentioned, the terms WD and UE may be used interchangeably. Thus, although Figure 14 it is a UE, the components discussed herein are equally applicable to the WD, and vice versa.

[0286] In Figure 14 , the UE 1400 includes processing circuitry 1401 that is operatively coupled to an input / output interface 1405, a radio frequency (RF) interface 1409, a network connection interface 1411, a memory 1415 including a random access memory (RAM) 1417, a read only memory (ROM) 1419, and a storage medium 1421 or the like, a communication subsystem 1431, a power supply 1433, and / or any other components or any combination thereof. The storage medium 1421 includes an operating system 1423, application programs 1425, and data 1427. In other embodiments, the storage medium 1421 may include other similar types of information. Some UEs may utilize all of the components shown in Figure 14 , or only a subset of the components. The level of integration between components may vary from one UE to another. Additionally, some UEs may include multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0287] In Figure 14 , the processing circuitry 1401 may be configured to process computer instructions and data. The processing circuitry 1401 may be configured to implement any sequential state machine operable to execute machine instructions stored in the memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic along with appropriate firmware; one or more stored programs, a general-purpose processor, such as a microprocessor or a digital signal processor (DSP), along with appropriate software; or any combination of the above. For example, the processing circuitry 1401 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0288] In the depicted embodiment, the input / output interface 1405 may be configured to provide a communication interface to an input device, an output device, or both an input and output device. The UE 1400 may be configured to use the output device via the input / output interface 1405. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide both input to and output from the UE 1400. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, a transmitter, a smart card, another output device, or any combination thereof. The UE 1400 may be configured to use the input device via the input / output interface 1405 to allow and / or facilitate a user to capture information into the UE 1400. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. For example, the sensor may be an accelerometer, a gyroscope, an inclinometer, a force sensor, a magnetometer, a light sensor, a proximity sensor, another similar sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0289] In Figure 14 , the RF interface 1409 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface 1411 may be configured to provide a communication interface to the network 1443a. The network 1443a may encompass a wired and / or wireless network such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1443a may include a Wi-Fi network. The network connection interface 1411 may be configured to include a receiver and a transmitter interface for communicating with one or more other devices over a communication network according to one or more communication protocols such as Ethernet, TCP / IP, SONET, ATM, or the like. The network connection interface 1411 may implement receiver and transmitter functionality suitable for a communication network link (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0290] The RAM 1417 can be configured to be interfaced with the processing circuitry 1401 via the bus 1402 to provide storage or caching of data or computer instructions during the execution of software programs such as an operating system, application programs, and device drivers. The ROM 1419 can be configured to provide computer instructions or data to the processing circuitry 1401. For example, the ROM 1419 can be configured to store invariant low-level system code or data of basic system functions stored in non-volatile memory, basic system functions such as basic input and output (I / O), startup, or receiving keystrokes from a keyboard. The storage medium 1421 can be configured to include a memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge tape, or flash drive. In one example, the storage medium 1421 can be configured to include an operating system 1423, application programs 1425 (such as a web browser application, widget or gadget engine, or another application), and data files 1427. The storage medium 1421 can store any one of a variety of operating systems or combinations of operating systems for use by the UE 1400.

[0291] The storage medium 1421 can be configured to include multiple physical drive units such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-definition digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-ray disc drive, holographic digital data storage (HDDS) optical disc drive, external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (such as a subscriber identity module or removable user identity (SIM / RUIM) module), other memories, or any combination thereof. The storage medium 1421 can allow and / or facilitate the UE 1400 to access computer-executable instructions, application programs, or the like stored on a temporary or non-temporary storage medium to offload data or upload data. An article of manufacture such as a communication system can be tangibly embodied in the storage medium 1421, and the storage medium 1421 can include a device-readable medium.

[0292] In Figure 14In [the figure], the processing circuit 1401 may be configured to communicate with the network 1443b using the communication subsystem 1431. The network 1443a and the network 1443b may be the same one or more networks or different one or more networks. The communication subsystem 1431 may be configured to include one or more transceivers for communicating with the network 1443b. For example, the communication subsystem 1431 may be configured to include one or more transceivers for communicating with one or more remote transceivers of another device capable of wireless communication (such as another WD, UE, or a base station of a radio access network (RAN)) according to one or more communication protocols (such as IEEE 802.12, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like). Each transceiver may include a transmitter 1433 and / or a receiver 1435 to respectively implement transmitter or receiver functionality suitable for the RAN link (such as frequency allocation and the like). Additionally, the transmitter 1433 and the receiver 1435 of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0293] In the illustrated embodiment, the communication functions of the communication subsystem 1431 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using the Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. For example, the communication subsystem 1431 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 1443b may cover wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 1443b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 1413 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 1400.

[0294] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 1400 or divided across multiple components of UE 1400. Additionally, the features, benefits, and / or functions described herein may be implemented using any combination of hardware, software, or firmware. In one example, communication subsystem 1431 may be configured to include any of the components described herein. Additionally, processing circuitry 1401 may be configured to communicate with any of such components via bus 1402. In another example, any of such components may be represented by program instructions stored in memory that, when executed by processing circuitry 1401, perform the corresponding functions described herein. In another example, the functionality of any of such components may be divided between processing circuitry 1401 and communication subsystem 1431. In another example, the non-computationally intensive functions of any of such components may be implemented using software or firmware, and the computationally intensive functions may be implemented using hardware.

[0295] Figure 15 is a schematic block diagram illustrating virtualization environment 1500, where the functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of a device or devices, which may include a virtualized hardware platform, storage, and networking resources. As used herein, virtualization may be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or a device (e.g., a UE, a wireless device, or any other type of communication device) or its components, and involves the implementation in which at least a portion of the functionality (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks) is implemented as one or more virtual components.

[0296] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 1500 hosted by one or more of hardware nodes 1530. Additionally, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be fully virtualized.

[0297] These functions can be implemented by one or more applications 1520 (alternatively they may be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits in the embodiments disclosed herein. The applications 1520 run in a virtualized environment 1500 that provides hardware 1530 including processing circuitry 1560 and memory 1590. The memory 1590 contains instructions 1595 executable by the processing circuitry 1560, whereby the applications 1520 are operable to provide one or more of the features, benefits, and / or functions disclosed herein.

[0298] The virtualized environment 1500 includes general-purpose or specialized network hardware devices 1530 that include a collection of one or more processors or processing circuitry 1560, which can be a commercial off-the-shelf (COTS) processor, a specialized application-specific integrated circuit (ASIC), or any other type of processing circuitry, including digital or analog hardware components or specialized processors. Each hardware device may include a memory 1590-1, which can be a non-permanent memory for temporarily storing software or instructions 1595 executed by the processing circuitry 1560. Each hardware device may include one or more network interface controllers (NICs) 1570 (also referred to as network interface cards), which include a physical network interface 1580. Each hardware device may also include a non-transitory permanent machine-readable storage medium 1590-2 in which instructions and / or software 1595 executable by the processing circuitry 1560 are stored. The software 1595 can include any type of software, including software for instantiating one or more virtualization layers 1550 (also referred to as hypervisors), software for executing virtual machines 1540, and software that allows it to perform the functions, features, and / or benefits described in connection with some of the embodiments herein.

[0299] The virtual machines 1540 include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by corresponding virtualization layers 1550 or hypervisors. Different embodiments of instances of the virtual appliances 1520 can be implemented on one or more of the virtual machines 1540, and this implementation can be done in different ways.

[0300] During operation, the processing circuitry 1560 executes the software 1595 to instantiate the hypervisor or virtualization layer 1550, which is sometimes referred to as a virtual machine monitor (VMM). The virtualization layer 1550 can present a virtual operating platform to the virtual machines 1540 that appears like networking hardware.

[0301] As Figure 15As shown, the hardware 1530 can be an independent network node with general or specific components. The hardware 1530 may include an antenna 15225, and some functions can be implemented via virtualization. Alternatively, the hardware 1530 can be part of a larger hardware cluster (such as in a data center or customer premise equipment (CPE)), where many hardware nodes work together and are managed via management and orchestration (MANO) 15100, and the management and orchestration (MANO) 15100 also supervises the lifecycle management of the application 1520.

[0302] Hardware virtualization is referred to as network function virtualization (NFV) in some contexts. NFV can be used to integrate many network device types onto industry-standard high-volume server hardware, physical switches, and physical storage devices, which can be located in data centers and customer premise equipment.

[0303] In the context of NFV, a virtual machine 1540 can be a software implementation of a physical machine that runs programs as if they were executed on a physical, non-virtualized machine. Each of the virtual machines 1540 and that part of the hardware 1530 that executes the virtual machine, if it is hardware dedicated to the virtual machine and / or hardware shared by the virtual machine with other virtual machines in the virtual machines 1540, forms a separate virtual network element (VNE).

[0304] Still in the context of NFV, a virtual network function (VNF) is responsible for handling specific network functions running in one or more virtual machines 1540 over the hardware networking infrastructure 1530, and corresponds to Figure 15 the application 1520 in

[0305] In some embodiments, one or more radio units 15200 each including one or more transmitters 15220 and one or more receivers 15210 can be coupled to one or more antennas 15225. The radio units 15200 can communicate directly with the hardware node 1530 via one or more appropriate network interfaces, and can be used in combination with virtual components to provide radio capabilities to virtual nodes, such as radio access nodes or base stations.

[0306] In some embodiments, some signaling can be performed by a control system 15230, which can alternatively be used for communication between the hardware node 1530 and the radio units 15200.

[0307] Referring to Figure 16, according to an embodiment, a communication system includes a telecommunications network 1610, such as a 3GPP-type cellular network, which includes an access network 1611 (such as a radio access network) and a core network 1614. The access network 1611 includes a plurality of base stations 1612a, 1612b, 1612c, such as NB, eNB, gNB or other types of wireless access points, and each base station defines a corresponding coverage area 1613a, 1613b, 1613c. Each base station 1612a, 1612b, 1612c can be connected to the core network 1614 through a wired or wireless connection 1615. A first UE 1691 located in the coverage area 1613c can be configured to be wirelessly connected to the corresponding base station 1612c or paged by the corresponding base station 1612c. A second UE 1692 in the coverage area 1613a can be wirelessly connected to the corresponding base station 1612a. Although a plurality of UEs 1691, 1692 are shown in this example, the disclosed embodiments are equally applicable to the case where there is a single UE in the coverage area or a single UE is connecting to the corresponding base station 1612.

[0308] The telecommunications network 1610 itself is connected to a host computer 1630, which can be embodied in a stand-alone server, cloud-implemented server, hardware and / or software of a distributed server, or as processing resources in a server farm. The host computer 1630 can be under the ownership or control of a service provider, or can be operated by or on behalf of a service provider. The connections 1621 and 1622 between the telecommunications network 1610 and the host computer 1630 can extend directly from the core network 1614 to the host computer 1630, or can be via an optional intermediate network 1620. The intermediate network 1620 can be one or more combinations of a public, private or hosted network; the intermediate network 1620 (if any) can be a backbone network or the Internet; in particular, the intermediate network 1620 can include two or more subnets (not shown).

[0309] Figure 16The communication system as a whole is capable of enabling connectivity between the connected UEs 1691, 1692 and the host computer 1630. This connectivity can be described as an over-the-top (OTT) connection 1650. The host computer 1630 and the connected UEs 1691, 1692 are configured to use the access network 1611, the core network 1614, any intermediate network 1620, and possibly additional infrastructure (not shown) as intermediaries to transfer data and / or signaling via the OTT connection 1650. The OTT connection 1650 can be transparent in the sense that the participating communication devices through which the OTT connection 1650 passes are not aware of the routing of the uplink and downlink communications. For example, it may not be necessary or required to inform the base station 1612 of the past routing of incoming downlink communications having data originating from the host computer 1630 to be forwarded (e.g., handed over) to the connected UE 1691. Similarly, the base station 1612 does not need to know the future routing of outgoing uplink communications originating from the UE 1691 towards the host computer 1630.

[0310] According to an embodiment, an example implementation of the UE, base station, and host computer discussed in the previous paragraphs will now be described with reference to Figure 17 In a communication system 1700, the host computer 1710 includes hardware 1715, and the hardware 1715 includes a communication interface 1716 configured to establish and maintain a wired or wireless connection to an interface of different communication devices of the communication system 1700. The host computer 1710 further includes a processing circuit 1718, which may have storage and / or processing capabilities. In particular, the processing circuit 1718 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or a combination of these (not shown) suitable for executing instructions. The host computer 1710 further includes software 1711, which is stored in or accessible by the host computer 1710 and executable by the processing circuit 1718. The software 1711 includes a host application 1712. The host application 1712 may be operable to provide services to remote users, such as a UE 1730 connected via an OTT connection 1750 terminating at the UE 1730 and the host computer 1710. When providing services to remote users, the host application 1712 may provide user data transmitted using the OTT connection 1750.

[0311] The communication system 1700 may also include a base station 1720, which provides in a telecommunication system and includes hardware 1725 enabling it to communicate with the host computer 1710 and the UE 1730. The hardware 1725 may include a communication interface 1726 for establishing and maintaining a wired or wireless connection for interfaces with different communication devices of the communication system 1700, and a radio interface 1727 for at least establishing and maintaining a wireless connection 1770 with the UE 1730 located in a coverage area ( Figure 17 not shown) served by the base station 1720. The communication interface 1726 may be configured to facilitate the connection 1760 to the host computer 1710. The connection 1760 may be direct, or it may be through the core network of the telecommunication system ( Figure 17 not shown) and / or through one or more intermediate networks external to the telecommunication system. In the illustrated embodiment, the hardware 1725 of the base station 1720 may also include a processing circuit 1728, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations of these (not shown) suitable for executing instructions. The base station 1720 may also include software 1721 stored internally or accessible via an external connection.

[0312] The communication system 1700 may also include a UE 1730, which includes a radio interface 1737 configured to establish and maintain a wireless connection 1770 with a base station serving the coverage area where the UE 1730 is currently located. The hardware 1735 of the UE 1730 may also include a processing circuit 1738, which may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations of these (not shown) suitable for executing instructions. The UE 1730 also includes software 1731, which is stored in or accessible by the UE 1730 and executable by the processing circuit 1738. The software 1731 includes a client application 1732. The client application 1732 may be operable to provide a service to a human or non - human user via the UE 1730 with the support of the host computer 1710. In the host computer 1710, the executing host application 1712 may communicate with the executing client application 1732 via an OTT connection 1750 terminating at the UE 1730 and the host computer 1710. When providing a service to the user, the client application 1732 may receive request data from the host application 1712 and provide user data in response to the requested data. The OTT connection 1750 may transfer both the request data and the user data. The client application 1732 may interact with the user to generate the user data it provides.

[0313] Note that Figure 17The host computer 1710, base station 1720, and UE 1730 shown in Figure 16 may be similar to or equivalent to one of the host computer 1230, base stations 1612a, 1612b, 1612c, and one of the UEs 1691, 1692 of Figure 17 . In other words, the internal workings of these entities may be as shown in Figure 16 , and independently, the surrounding network topology may be the network topology of

[0314] In Figure 17 , the OTT connection 1750 has been abstractly drawn to illustrate the communication between the host computer 1710 and the UE 1730 via the base station 1720, without explicitly referring to any intermediate devices and the exact routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide the routing from the UE 1730 or the service provider operating the host computer 1710 or both. When the OTT connection 1750 is active, the network infrastructure may further make decisions by which it dynamically changes the routing (e.g., based on network reconfiguration or load balancing considerations).

[0315] The wireless connection 1770 between the UE 1730 and the base station 1720 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT services provided to the UE 1730 using the OTT connection 1750, where the wireless connection 1770 forms the final segment. More precisely, the exemplary embodiments disclosed herein may improve the flexibility of network monitoring of the end-to-end quality of service (QoS) of data flows associated with data sessions between a user equipment (UE) and another entity (such as an OTT data application or service external to the 5G network), including their corresponding radio bearers. These and other advantages can facilitate the more timely design, implementation, and deployment of 5G / NR solutions. In addition, such embodiments may facilitate the flexible and timely control of data session QoS, which can lead to improvements in capacity, throughput, latency, etc. envisioned by 5G / NR and are important for the growth of OTT services.

[0316] For purposes of monitoring data rate, latency, and other aspects of network operation improved by one or more embodiments, a measurement process may be provided. There may also be optional network functionality for reconfiguring the OTT connection 1750 between the host computer 1710 and the UE 1730 in response to changes in measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 1750 may be implemented by the software 1711 and hardware 1715 of the host computer 1710, or by the software 1731 and hardware 1735 of the UE 1730, or by both. In an embodiment, sensors (not shown) may be deployed in or associated with the communication device through which the OTT connection 1750 passes; the sensors may participate in the measurement process by providing values of the monitored quantities illustrated above or by providing values of other physical quantities from which the software 1711, 1731 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 1750 may include message format, retransmission settings, preferred routing, etc.; the reconfiguration need not affect the base station 1720, and it may be unknown or imperceptible to the base station 1720. Such processes and functionality may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling to facilitate measurement by the host computer 1710 of throughput, propagation time, latency, and the like. The measurement may be achieved by the software 1711 and 1731 using the OTT connection 1750 to cause messages (especially empty or 'virtual' messages) to be transmitted while it monitors propagation time, errors, etc.

[0317] Figure 18 is a flowchart showing an exemplary method and / or process implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which in some exemplary embodiments may be those described with reference to other figures herein. To simplify the present disclosure, only references to Figure 18 will be included in this section. In step 1810, the host computer provides user data. In sub-step 1811 of step 1810 (which may be optional), the host computer provides user data by executing a host application. In step 1820, the host computer initiates a transmission carrying the user data to the UE. In step 1830 (which may be optional), according to the teachings of the embodiments described throughout the present disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 1840 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0318] Figure 19is a flowchart illustrating an exemplary method and / or process implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to other figures herein. To simplify the present disclosure, only references to Figure 19 will be included in this section. In 1910 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1920, the host computer initiates a transmission carrying the user data to the UE. According to the teachings of the embodiments described throughout the present disclosure, the transmission can be relayed via the base station. In step 1930 (which may be optional), the UE receives the user data carried in the transmission.

[0319] Figure 20 is a flowchart illustrating an exemplary method and / or process implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to other figures herein. To simplify the present disclosure, only references to Figure 20 will be included in this section. In step 2010 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2020, the UE provides user data. In sub-step 2021 of step 2020 (which may be optional), the UE provides user data by executing a client application. In sub-step 2011 of step 2010 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the particular manner in which the user data is provided, in sub-step 2030 (which may be optional), the UE initiates a transmission of the user data to the host computer. In step 2040 of the method, according to the teachings of the embodiments described throughout the present disclosure, the host computer receives the user data transmitted from the UE.

[0320] Figure 21 is a flowchart illustrating an exemplary method and / or process implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those described with reference to other figures herein. To simplify the present disclosure, only references to Figure 21 will be included in this section. In step 2110 (which may be optional), according to the teachings of the embodiments described throughout the present disclosure, the base station receives user data from the UE. In step 2120 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 2130 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0321] The foregoing merely illustrates the principles of the present disclosure. In light of the teachings herein, various modifications and variations to the described embodiments will be apparent to those skilled in the art. Accordingly, it will be recognized that those skilled in the art will be able to design many systems, arrangements, and processes that, although not explicitly shown or described herein, embody the principles of the present disclosure and are thus within the spirit and scope of the present disclosure. As will be understood by those of ordinary skill in the art, the various exemplary embodiments may be used together with one another and may be interchanged with one another.

[0322] As used herein, the term unit may have its conventional meaning in the fields of electronics, electrical devices, and / or electronic devices and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs, or instructions for performing corresponding tasks, processes, calculations, outputs, and / or display functions, etc., such as those described herein.

[0323] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via processing circuitry that may include one or more microprocessors or microcontrollers and other digital hardware that may include a digital signal processor (DSP), application-specific digital logic, and the like. The processing circuitry may be configured to execute program code stored in a memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in the memory includes program instructions for performing one or more telecommunication and / or data communication protocols and instructions for performing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the corresponding functional units to perform the corresponding functions according to one or more embodiments of the present disclosure.

[0324] As described herein, a device and / or equipment may be represented by a semiconductor chip, a chipset, or a (hardware) module including such a chip or chipset; however, this excludes the possibility that the functionality of the device or equipment is not implemented by hardware but is implemented as a software module, such as a computer program or a computer program product, which includes an executable software code portion for execution or running on a processor. In addition, the functionality of the device or equipment may be implemented by any combination of hardware and software. The device or equipment may also be regarded as an assembly of multiple devices and / or equipment, whether they cooperate with each other functionally or are independent of each other. In addition, the device and equipment may be implemented in a distributed manner throughout the system as long as the functionality of the device or equipment is retained. Such and similar principles are considered to be known to those skilled in the art.

[0325] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It will be further understood that terms used herein should be interpreted as having a meaning consistent with their meaning in the relevant art and the context of this specification, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0326] In addition, certain terms used in this disclosure, including the specification, the drawings, and their exemplary embodiments, may be used synonymously in certain instances, including but not limited to, for example, data and information. It should be understood that although these words and / or other words that may be synonymous with each other may be used synonymously herein, there may be instances where such words are not intended to be used synonymously. Additionally, to the extent that prior art knowledge has not been expressly incorporated herein by reference above, it is hereby incorporated by reference in its entirety. All publications cited are incorporated by reference in their entirety herein.

[0327] Exemplary embodiments of the technologies and devices described herein include, but are not limited to, the following enumerated examples:

[0328] 1. A method for exchanging UE communication mode information with a core network CN (298, 398) in an application function AF (660, 1520), the method comprising:

[0329] Providing (1010) communication information related to one or more user equipments (UEs) to a network exposure function NEF (360, 650, 1520) in the CN, the communication information including:

[0330] An identifier of an application associated with the AF, and

[0331] Describe a plurality of first parameters that characterize the expected UE communication patterns associated with the application, where the plurality of first parameters are arranged in one or more sets associated with respective connection phases;

[0332] Send (1020) a subscription request to the NEF for one or more second parameters that characterize the actual UE communication patterns associated with the application and the one or more UEs, where the subscription request includes the identifier of the application; and

[0333] Receive (1030) a report from the NEF, the report including the one or more second parameters.

[0334] 2. The method of embodiment 1, wherein each set of first parameters is associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting.

[0335] 3. The method of any of embodiments 1 - 2, wherein each set of first parameters includes one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source.

[0336] 4. The method of embodiment 3, wherein at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value.

[0337] 5. The method of any of embodiments 1 - 4, wherein the one or more second parameters are included in the one or more first parameters.

[0338] 6. The method of any of embodiments 1 - 4, wherein the one or more second parameters include at least one parameter not included in the one or more first parameters.

[0339] 7. The method of any of embodiments 1 - 6, wherein the communication information provided to the NEF further includes identifiers of the plurality of first parameters.

[0340] 8. The method of any of embodiments 1 - 7, wherein the subscription request further includes identifiers of the one or more second parameters.

[0341] 9. The method of any of embodiments 1 - 8, wherein the report includes second parameters associated with a specific connection phase, and the specific connection phase is also associated with a specific set of the first parameters.

[0342] 10. A method for exchanging UE communication mode information with an Application Function (AF) (660, 1520) performed by a Network Exposure Function (NEF) (360, 650, 1520) in a Core Network (CN) (298, 398), the method comprising:

[0343] Receiving (1110) from the AF communication information related to one or more User Equipments (UEs), the communication information including:

[0344] An identifier of an application associated with the AF, and

[0345] A plurality of first parameters describing an expected UE communication mode associated with the application, wherein the plurality of first parameters are arranged in one or more sets associated with respective connection phases;

[0346] Receiving (1130) from the AF a subscription request for one or more second parameters describing an actual UE communication mode associated with the application and the one or more UEs, wherein the subscription request includes the identifier of the application; and sending (1160) to the AF a report including the one or more second parameters.

[0347] 11. The method of embodiment 10, wherein each set of first parameters is associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting.

[0348] 12. The method of any of embodiments 10 - 11, wherein each set of first parameters includes one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source.

[0349] 13. The method of embodiment 12, wherein at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value.

[0350] 14. The method of any of embodiments 10 - 13, wherein the one or more second parameters are included in the one or more first parameters.

[0351] 15. The method of any of embodiments 10 - 13, wherein the one or more second parameters include at least one parameter not included in the one or more first parameters.

[0352] 16. The method of any of embodiments 10 - 15, wherein the communication information received from the AF further includes an identifier of the plurality of first parameters.

[0353] 17. The method of any of embodiments 10 - 16, wherein the subscription request further includes an identifier of the one or more second parameters.

[0354] 18. The method of any of embodiments 10 - 17, further comprising:

[0355] Sending (1115) a discovery request to a network repository function NRF (640, 1520) to identify a network data analytics function NWDAF (630, 1520) that supports the first parameter; and

[0356] Receiving (1120) an indication from the NRF that a first NWDAF supports the first parameter;

[0357] Sending (1125) a message to the first NWDAF, the message including:

[0358] The identifier of the application, and

[0359] The identifier of the first parameter.

[0360] 19. The method of embodiment 18, further comprising:

[0361] Determining (1135) whether the first NWDAF supports the second parameter;

[0362] Based on determining that the first NWDAF supports the second parameter, sending (1140) a second subscription request to the first NWDAF, the second subscription request including:

[0363] The identifier of the application, and

[0364] The identifier of the second parameter; and

[0365] Receiving (1155) the report including the one or more second parameters from the first NWDAF.

[0366] 20. The method of any of embodiments 18 - 19, further comprising:

[0367] Based on determining that the first NWDAF does not support the second parameter, sending (1145) a second discovery request to the NRF to identify a NWDAF that supports the second parameter; and

[0368] Receiving (1150) an indication from the NRF that a second NWDAF supports the second parameter,

[0369] wherein the second subscription request is sent to the second NWDAF instead of the first NWDAF, and the report is received from the second NWDAF instead of the first NWDAF.

[0370] The method of any one of embodiments 10 - 20, wherein the report includes a second parameter associated with a specific connection phase, and the specific connection phase is also associated with a specific set of the first parameters.

[0371] 22. A method for exchanging user equipment UE communication mode information with an application function AF (660, 1520) performed by a network data analytics function NWDAF (630, 1520) in a core network CN (298, 398), the method comprising:

[0372] Receiving (1230) from a network exposure function NEF (360, 650, 1520) in the CN a subscription request associated with the AF, the subscription request including:

[0373] An identifier of an application associated with the AF, and

[0374] An identifier of one or more second parameters describing an actual UE communication mode associated with the application and with the one or more UEs; and

[0375] Sending (1250) to a user plane function UPF (340, 620, 1520) a request for one or more traffic metrics associated with the second parameter, wherein the request includes the identifier of the application;

[0376] Receiving (1260) the one or more traffic metrics from the UPF;

[0377] Determining (1270) the one or more second parameters based on the traffic metrics; and

[0378] Sending (1280) to the NEF a report including the one or more second parameters.

[0379] 23. The method of embodiment 22, further comprising:

[0380] Receiving (1220) from the NEF a message, the message including:

[0381] An identifier of an application associated with an application function AF, and

[0382] A plurality of first parameters that describe an expected UE communication mode associated with the application and with one or more UEs, wherein the plurality of first parameters are arranged in one or more sets associated with respective connection phases; and

[0383] Determining (1240) the one or more traffic metrics to request from the UPF based on the first parameters and the second parameters.

[0384] 24. The method of embodiment 23, wherein each set of the first parameters is associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting.

[0385] 25. The method of any of embodiments 23 - 24, wherein each set of the first parameters includes one or more of the following first parameters: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round - trip delay, and connection source.

[0386] 26. The method of embodiment 25, wherein at least one of the first parameters includes one or more of the following: maximum value, minimum value, and average value.

[0387] 27. The method of any of embodiments 23 - 26, wherein the one or more second parameters are included in the one or more first parameters.

[0388] 28. The method of any of embodiments 23 - 26, wherein the one or more second parameters include at least one parameter not included in the one or more first parameters.

[0389] 29. The method of any of embodiments 23 - 28, further comprising: before receiving (1220) the message from the NEF, sending (1210) a registration request to a network repository function NRF (640, 1520), wherein the registration request includes:

[0390] The identifier of the NWDAF;

[0391] The identifier of one or more services associated with UE communication information supported by the NWDAF; and

[0392] The identifier of one or more parameters that can be generated by the NWDAF associated with UE communication.

[0393] 30. An application function AF (660, 1520) configured to exchange UE communication mode information with a core network CN (298, 398), the AF comprising:

[0394] Interface circuitry (1570) configured to communicate with a network exposure function NEF (360, 650, 1520) in the CN; and

[0395] Processing circuitry (1560) operably coupled to the interface circuitry, whereby the processing circuitry and the interface circuitry are configured to perform operations corresponding to any of the methods of embodiments 1 - 9.

[0396] 31. An application function AF (660, 1520) is configured to exchange UE communication mode information with a core network CN (298, 398), and the AF is arranged to perform operations corresponding to any of the methods in Embodiments 1-9.

[0397] 32. A non-transitory computer-readable medium (1590) storing computer-executable instructions (1595), which, when executed by a processing circuit (1560) associated with an application function AF (660, 1520), configure the AF to perform operations corresponding to any of the methods in Embodiments 1-9.

[0398] 33. A computer program product comprising computer-executable instructions (1595), which, when executed by a processing circuit (1560) associated with an application function AF (660, 1520), configure the AF to perform operations corresponding to any of the methods in Embodiments 1-9.

[0399] 34. A core network CN (298, 398) is configured to exchange UE communication mode information with an application function AF (660, 1520), and the CN includes:

[0400] One or more network nodes (1360, 1530) configured to provide:

[0401] A network exposure function NEF (360, 650, 1520) operable to communicate with the AF, and

[0402] A network data analytics function NWDAF (630, 1520);

[0403] Wherein, the one or more network nodes include a processing circuit (1370, 1560) configured to perform operations corresponding to any of the methods in Embodiments 10-29.

[0404] 35. The CN of Embodiment 34, wherein the one or more nodes (1360, 1530) are further configured to provide: a network repository function NRF (640, 1520); and

[0405] A user plane function UPF (340, 620, 1520).

[0406] 36. A core network CN (298, 398) is configured to exchange UE communication mode information with an application function AF (660, 1520), and the CN is arranged to perform operations corresponding to any of the methods in Embodiments 10-29.

[0407] 37. A non-transitory computer-readable medium (1380, 1590) storing computer-executable instructions (1595) that, when executed by processing circuitry (1370, 1560) associated with a core network CN (298, 398), configure the CN to perform operations corresponding to any of the methods of the methods of Embodiments 10-29.

[0408] 38. A computer program product comprising computer-executable instructions (1595) that, when executed by processing circuitry (1370, 1560) associated with a core network CN (298, 398), configure the CN to perform operations corresponding to any of the methods of the methods of Embodiments 10-29.

Claims

1. A method for exchanging UE communication mode information with a core network CN (298, 398) in an application function AF (660, 1520), the method comprising: Providing (302, 1010) communication information related to one or more user equipments UE to a network exposure function NEF (360, 650, 1520) in the CN, the communication information including: An identifier of an application associated with the AF, and An indication of one or more first parameters describing a first UE communication mode associated with the application; wherein the one or more first parameters are arranged in one or more sets associated with respective connection phases; Sending (310, 1020) a subscription request to the NEF, wherein the subscription request includes the identifier of the application; and Receiving (326, 1030) a report from the NEF, the report indicating an analysis of the traffic of the application based at least on the one or more first parameters.

2. The method according to claim 1, wherein, The one or more first parameters describing the first UE communication mode define a traffic model of the application to be analyzed in the CN.

3. The method according to claim 1, wherein Sending the subscription request for one or more second parameters describing a second UE communication mode associated with the application and the one or more UEs.

4. The method according to claim 3, wherein, The one or more second parameters define information about the traffic of the application to be reported in the subscription.

5. The method according to claim 4, wherein, The one or more first parameters and the one or more second parameters together define the traffic to be reported in the subscription.

6. The method according to claim 3, wherein, The communication information triggers the NEF to perform a network data analytics function NWDAF discovery process based on the one or more first parameters.

7. The method according to claim 6, wherein, The subscription request triggers the NEF to forward the one or more second parameters to an NWDAF determined by the NWDAF discovery process.

8. The method according to claim 1, wherein, Each set of first parameters is associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting.

9. The method according to claim 8, wherein, For a selected set of first parameters, the communication information further includes information about the associated connection phase.

10. The method according to claim 1, wherein, At least one of the one or more first parameters includes one or more of the following: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source.

11. The method according to claim 1, wherein, At least one of the one or more first parameters includes one or more of the following or is specified by one or more of the following: maximum value, minimum value, and average value.

12. The method according to claim 1, wherein At least one of the one or more first parameters is specified in the communication information by a parameter type and an associated parameter value.

13. The method according to claim 1, wherein The one or more first parameters describing the first UE communication mode define the traffic characteristics of the traffic to be analyzed in the CN.

14. The method according to claim 3, wherein, The one or more second parameters define the traffic characteristics of the traffic to be analyzed in the CN.

15. The method according to claim 3, wherein, The one or more second parameters are included in the one or more first parameters.

16. The method according to claim 3, wherein The one or more second parameters include at least one parameter not included in the one or more first parameters.

17. The method according to any one of claims 1-16, wherein, The communication information provided to the NEF includes identifiers of the one or more first parameters.

18. The method according to claim 3, wherein The subscription request includes identifiers of the one or more second parameters.

19. The method according to claim 8, wherein, The report includes one or more second parameters associated with a selected connection phase, and the selected connection phase is also associated with a selected set of the first parameters.

20. The method according to claim 3, wherein, The report includes a numerical value indicating the percentage of traffic associated with the one or more second parameters.

21. A method for exchanging UE communication mode information with an application function AF (660, 1520) performed by a network exposure function NEF (360, 650, 1520) in a core network CN (298, 398), the method comprising: Receiving (304, 1110) from the AF communication information related to one or more user equipments (UEs), the communication information including: An identifier of an application associated with the AF, and An indication of one or more first parameters describing a first UE communication mode associated with the application; wherein the one or more first parameters are arranged in one or more sets associated with respective connection phases; Receiving (312, 1130) from the AF a subscription request, wherein the subscription request includes the identifier of the application; and Sending (324, 1160) to the AF a report indicating an analysis of the traffic of the application based at least on the one or more first parameters.

22. The method according to claim 21, wherein, The receipt of the communication information triggers the NEF to perform a network data analytics function NWDAF discovery process based on the one or more first parameters.

23. The method according to claim 22, wherein, Receiving the subscription request for one or more second parameters describing a second UE communication mode associated with the application and the one or more UEs.

24. The method according to claim 23, wherein, The receipt of the subscription request triggers the NEF to forward the one or more second parameters to the NWDAF determined by the NWDAF discovery process.

25. The method according to claim 21, wherein, Each set of first parameters is associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting.

26. The method according to claim 21, wherein, At least one of the one or more first parameters includes one or more of the following: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source.

27. The method according to claim 21, wherein At least one of the one or more first parameters includes one or more of or is specified by one or more of the following: maximum value, minimum value, and average value.

28. The method according to claim 23, wherein, The one or more second parameters are included in the one or more first parameters.

29. The method according to claim 23, wherein The one or more second parameters include at least one parameter not included in the one or more first parameters.

30. The method according to claim 21, wherein, The communication information received from the AF includes identifiers of the one or more first parameters.

31. The method according to claim 23, wherein The subscription request includes identifiers of the one or more second parameters.

32. The method according to claim 23, further comprising: Send (1115) a discovery request to a network repository function NRF (640, 1520) to identify a network data analytics function NWDAF (630, 1520) that supports the one or more first parameters; And Receive (1120) an indication from the NRF that a first NWDAF supports the one or more first parameters; And Send (1125) a message to the first NWDAF, the message including: The identifier of the application, and The identifier of the one or more first parameters.

33. The method according to claim 32, further comprising: Determine (1135) whether the first NWDAF supports the one or more second parameters; Based on determining that the first NWDAF supports the one or more second parameters, send (1140) a second subscription request to the first NWDAF, the second subscription request including: The identifier of the application, and The identifier of the one or more second parameters; And Receive (1155) a report in response to the second subscription request from the first NWDAF.

34. The method according to claim 33, further comprising: Based on determining that the first NWDAF does not support the one or more second parameters, send (1145) a second discovery request to the NRF to identify a NWDAF that supports the one or more second parameters; And Receive (1150) an indication from the NRF that a second NWDAF supports the one or more second parameters, Wherein, the second subscription request is sent to the second NWDAF instead of the first NWDAF, and the report is received from the second NWDAF instead of the first NWDAF.

35. The method according to claim 25, wherein The report includes or relates to one or more second parameters associated with a selected connection phase, and the selected connection phase is also associated with a selected set of the one or more first parameters.

36. A method for exchanging user equipment UE communication mode information with an application function AF (660, 1520) performed by a network data analysis function NWDAF (630, 1520) in a core network CN (298, 398), the method comprising: Receive (306, 1230) a message from a network exposure function NEF (360, 650, 1520) in the CN, the message including: The identifier of an application associated with an application function AF, and An indication of one or more first parameters that describe a first UE communication mode associated with the application and with one or more UEs; wherein, the one or more first parameters are arranged in one or more sets associated with respective connection phases; Receive (314, 1230) a subscription request associated with the AF from the NEF, the subscription request including: The identifier of the application associated with the AF; Send (316, 1250) a request for one or more traffic metrics to a user plane function UPF (340, 620, 1520), wherein the request includes the identifier of the application; Receive (318, 1260) the one or more traffic metrics from the UPF; Analyze the traffic metrics at least based on the one or more first parameters; and Send (320, 1280) a report indicating the analysis to the NEF.

37. The method according to claim 36, further comprising: receiving (1230) from the NEF and in the subscription request associated with the AF an identifier that describes one or more second parameters of a second UE communication mode associated with the application and with one or more UEs; and sending (1250) a request for one or more traffic metrics associated with the one or more second parameters to the UPF (340, 620, 1520).

38. The method according to claim 36, wherein each set of one or more first parameters is associated with one of the following connection phases: bootstrapping, registration, device management, and information reporting.

39. The method according to claim 36, wherein, The one or more first parameters include one or more of the following: security, data packet size, number of data packets, traffic volume, number of flows, packet arrival interval time, packet round-trip delay, and connection source.

40. The method according to claim 36, wherein, The one or more first parameters include or specify one or more of the following: maximum value, minimum value, and average value.

41. The method according to claim 37, wherein, The one or more second parameters are included in the one or more first parameters.

42. The method according to claim 37, wherein The one or more second parameters include at least one parameter not included in the one or more first parameters.

43. The method according to claim 36, further comprising: Before receiving (1220) the message from the NEF, sending (1210) a registration request to a network repository function NRF (640, 1520), wherein the registration request includes: the identifier of the NWDAF; identifiers of one or more services associated with UE communication information supported by the NWDAF; and identifiers of one or more parameters that can be generated by the NWDAF associated with UE communication.

44. The method according to claim 37, wherein, The first UE communication mode is one of the expected and predictable UE communication modes associated with the application and / or wherein the second UE communication mode is one of the actual and current UE communication modes associated with the application.

45. An application function AF (660, 1520), configured to exchange UE communication mode information with a core network CN (298, 398), the AF comprising: an interface circuit (1570), the interface circuit (1570) being configured to communicate with a network exposure function NEF (360, 650, 1520) in the CN; and a processing circuit (1560), the processing circuit (1560) being operably coupled to the interface circuit, whereby the processing circuit and the interface circuit are configured to perform operations corresponding to any one of the methods described in claims 1-20.

46. An application function AF (660, 1520), configured to exchange UE communication mode information with a core network CN (298, 398), the AF being arranged to perform operations corresponding to any one of the methods described in claims 1-20.

47. A non - transitory computer - readable medium (1590) storing computer - executable instructions (1595), which, when executed by a processing circuit (1560) associated with an application function AF (660, 1520), configure the AF to perform operations corresponding to any one of the methods recited in claims 1 - 20.

48. A computer program product comprising computer - executable instructions (1595), which, when executed by a processing circuit (1560) associated with an application function AF (660, 1520), configure the AF to perform operations corresponding to any one of the methods recited in claims 1 - 20.

49. A core network CN (298, 398) configured to exchange UE communication mode information with an application function AF (660, 1520), the CN comprising: One or more network nodes (1360, 1530) configured to provide at least one of the following: A network exposure function NEF (360, 650, 1520) operable to communicate with the AF, and A network data analytics function NWDAF (630, 1520); Wherein the one or more network nodes include a processing circuit (1370, 1560) configured to perform operations corresponding to any one of the methods recited in claims 21 - 44.

50. The core network CN according to claim 49, wherein, The one or more nodes (1360, 1530) are further configured to provide at least one of the following: A network repository function NRF (640, 1520); and A user plane function UPF (340, 620, 1520).

51. A core network CN (298, 398) configured to exchange UE communication mode information with an application function AF (660, 1520), the CN being arranged to perform operations corresponding to any one of the methods recited in claims 21 - 44.

52. A non - transitory computer - readable medium (1380, 1590) storing computer - executable instructions (1595), which, when executed by a processing circuit (1370, 1560) associated with a core network CN (298, 398), configure the CN to perform operations corresponding to any one of the methods recited in claims 21 - 44.

53. A computer program product comprising computer - executable instructions (1595), which, when executed by a processing circuit (1370, 1560) associated with a core network CN (298, 398), configure the CN to perform operations corresponding to any one of the methods recited in claims 21 - 44.

Images