Sample alignment for cross-domain vertical federated learning (VFL) operations

Abstract

Methods of which may be used for cross-domain vertical federated learning artificial intelligence(AI) / machine learning(ML) operations are disclosed. A method comprises sending a sample alignment request including a session identifier and receiving a sample alignment response including the session identifier. The sample alignment request and sample alignment response may be user to perform sample alignment for vertical federated learning.

Description

Docket No. P69542WO1SAMPLE ALIGNMENT FOR CROSS-DOMAIN VERTICAL FEDERATED LEARNING (VFL) OPERATIONSFIELD

[0001] Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods which may be used for cross-domain vertical federated learning operations.DESCRIPTION OF THE RELATED ART

[0002] Wireless communication systems are rapidly growing in usage. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS) and are capable of operating sophisticated applications that utilize these functionalities.

[0003] Long Term Evolution (LTE) has been the technology of choice for the majority of wireless network operators worldwide, providing mobile broadband data and high-speed Internet access to their subscriber base. LTE was first proposed in 2004 and was first standardized in 2008. Since then, as usage of wireless communication systems has expanded exponentially, demand has risen for wireless network operators to support a higher capacity for a higher density of mobile broadband users. In 2015, a study of a new radio access technology began and, in 2017, a first release of Fifth Generation New Radio (5G NR) was standardized.

[0004] 5G-NR, also simply referred to as NR, provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to- device, ultra-reliable, and massive machine type communications with lower latency and / or lower battery consumption. Further, NR may allow for more flexible scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of NR to take advantage of higher throughputs possible at higher frequencies.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] A better understanding of the present subject matter can be obtained when the following detailed description of various embodiments is considered in conjunction with the following drawings, in which:

[0006] FIG. 1 A illustrates an example wireless communication system according to someDocket No. P69542WO1 embodiments.

[0007] FIG. 1 B illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.

[0008] FIG. 2 illustrates an example block diagram of a base station, according to some embodiments.

[0009] FIG. 3 illustrates an example block diagram of a server according to some embodiments.

[0010] FIG. 4 illustrates an example block diagram of a UE according to some embodiments.

[0011] FIG. 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.

[0012] FIG. 6 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.

[0013] FIG. 7 illustrates an example block diagram of an interface of baseband circuitry according to some embodiments.

[0014] FIG. 8 illustrates an example of a control plane protocol stack in accordance with some embodiments.

[0015] FIG. 9 illustrates an example of a user plane protocol stack in accordance with some embodiments.

[0016] FIG. 10 illustrates example components of a core network in accordance with some embodiments.

[0017] FIGS. 1 1A-1 1 B illustrate examples of sample alignment for application function (AF) initiated vertical federated learning (VFL) according to some embodiments.

[0018] FIG. 12 illustrates an example of sample alignment for network data analytics function initiated (NWDAF) vertical federated learning (VFL) according to some embodiments.

[0019] FIGS. 13A-13B illustrate examples of sample updating during and after a vertical federated learning (VFL) training procedure according to some embodiments.

[0020] FIGS. 14A-14B illustrate examples of vertical federated learning (VFL) model management according to some embodiments.

[0021] FIGS. 15A-15B illustrate flow charts of an example method of sample alignment for a vertical federated learning (VFL) training procedure, according to some embodiments.

[0022] FIGS. 16A-16B illustrate flow charts of an example method of sample updating for a vertical federated learning (VFL) training procedure, according to some embodiments.Docket No. P69542WO1

[0023] FIGS. 17A-17B illustrate flow charts of an example method of model management for vertical federated learning (VFL), according to some embodiments.

[0024] While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. It should be understood, however, that the drawings and detailed description thereto are not intended to be limiting to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the subject matter as defined by the appended claims.DETAILED DESCRIPTIONTerms

[0025] The following is a glossary of terms used in this disclosure:

[0026] Memory Medium or Memory - Any of various types of non-transitory memory devices or storage devices. The term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc. The memory medium may include other types of non-transitory memory as well or combinations thereof. In addition, the memory medium may be located in a first computer system in which the programs are executed, or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution. The term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network. The memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.

[0027] Carrier Medium - a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and / or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.

[0028] Programmable Hardware Element includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays), PLDs (Programmable LogicDocket No. P69542WO1Devices), FPOAs (Field Programmable Object Arrays), and CPLDs (Complex PLDs). The programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores). A programmable hardware element may also be referred to as "reconfigurable logic”.

[0029] Computer System (or Computer) - any of various types of computing or processing systems, including a personal computer system (PC), mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA), television system, grid computing system, or other device or combinations of devices. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0030] User Equipment (UE) (or “UE Device") - any of various types of computer systems devices which are mobile or portable and which performs wireless communications. Examples of UE devices include mobile telephones or smart phones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smart watch, smart glasses), PDAs, portable Internet devices, Internet of Things, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), and so forth. In general, the term “UE” or “UE device” can be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) which is easily transported by a user and capable of wireless communication.

[0031] Base Station - The term “Base Station” has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate with UEs as part of a wireless telephone system or radio system, including but not limited Next Generation Node-Bs (gNB or gNodeB) in NR and NG- RAN nodes.

[0032] Processing Element (or Processor) - refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device. Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit), programmable hardware elements such as a field programmable gate array (FPGA), as well any of various combinations of the above.Docket No. P69542WO1

[0033] Channel - a medium used to convey information from a sender (transmitter) to a receiver. It should be noted that since characteristics of the term “channel” may differ according to different wireless protocols, the term “channel” as used herein may be considered as being used in a manner that is consistent with the standard of the type of device with reference to which the term is used. In some standards, channel widths may be variable (e.g., depending on device capability, band conditions, etc.). For example, LTE may support scalable channel bandwidths from 1 .4 MHz to 20MHz. 5G NR can support scalable channel bandwidths from 5 MHz to 100 MHz in Frequency Range 1 (FR1 ) and up to 400 MHz in FR2. In other radio access technologies, WLAN channels may be 22 MHz wide while Bluetooth channels may be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and / or different channels for different uses such as data, control information, etc.

[0034] Band - The term "band" has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.

[0035] Automatically - refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc.), without user input directly specifying or performing the action or operation. Thus, the term "automatically" is in contrast to an operation being manually performed or specified by the user, where the user provides input to directly perform the operation. An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually”, where the user specifies each action to perform. For example, a user filling out an electronic form by selecting each field and providing input specifying information (e.g., by typing information, selecting check boxes, radio selections, etc.) is filling out the form manually, even though the computer system will update the form in response to the user actions. The form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields. As indicated above, the user may invoke the automatic filling of the form, but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed). The present specification provides various examples of operations being automatically performed inDocket No. P69542WO1 response to actions the user has taken.

[0036] Approximately - refers to a value that is almost correct or exact. For example, approximately may refer to a value that is within 1 to 10 percent of the exact (or desired) value. It should be noted, however, that the actual threshold value (or tolerance) may be application dependent. For example, in some embodiments, “approximately” may mean within 0.1 % of some specified or desired value, while in various other embodiments, the threshold may be, for example, 2%, 3%, 5%, and so forth, as desired or as set by the particular application.

[0037] Concurrent - refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner. For example, concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism”, where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.

[0038] Various components may be described as “configured to” perform a task or tasks. In such contexts, “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected). In some contexts, “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on. In general, the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.

[0039] Various components may be described as performing a task or tasks, for convenience in the description. Such descriptions should be interpreted as including the phrase “configured to.” Reciting a component that is configured to perform one or more tasks is expressly intended not to invoke 35 U.S.C. § 112(f) interpretation for that component.

[0040] The example embodiments may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The example embodiments relate to apparatuses, systems and method for reducing energy usage by network components, e.g., base stations in wireless communication systems.

[0041] The example embodiments are described with regard to communication betweenDocket No. P69542WO1 a Next Generation Node B (gNB) and a user equipment (UE). However, reference to a gNB or a UE is merely provided for illustrative purposes. The example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and / or firmware to support for reducing energy usage by network components in wireless communication systems. Therefore, the gNB or UE as described herein is used to represent any appropriate type of electronic component.

[0042] The example embodiments are also described with regard to a fifth generation (5G) New Radio (NR). However, reference to a 5G NR network is merely provided for illustrative purposes. The example embodiments may be utilized with any appropriate type of network.

[0043] Throughout this description various information elements (lEs) are referred to by specific names. It should be understood that these names are only examples and the lEs carrying the information referred to throughout this description may be referred to by other names by various entities.Figures 1 A and 1 B: Communication Systems

[0044] FIG. 1 illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of FIG. 1 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

[0045] As shown, the example wireless communication system includes a base station 102A which communicates over a transmission medium with one or more user devices 106A, 106B, etc., through 106N. Each of the user devices may be referred to herein as a “user equipment” (UE). Thus, the user devices 106 are referred to as UEs or UE devices.

[0046] The base station (BS) 102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs 106A through 106N.

[0047] The communication area (or coverage area) of the base station may be referred to as a “cell.” The base station 102A and the UEs 106 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs), also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1 xEV-DO, HRPD, eHRPD), etc. Note that if the base station 102ADocket No. P69542WO1 is implemented in the context of LTE, also referred to as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN, it may alternately be referred to as an 'eNodeB' or ‘eNB’. Note that if the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’.

[0048] As shown, the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and / or the Internet, among various possibilities). Thus, the base station 102A may facilitate communication between the user devices and / or between the user devices and the network 100. In particular, the cellular base station 102A may provide UEs 106 with various telecommunication capabilities, such as voice, SMS and / or data services.

[0049] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0050] Thus, while base station 102A may act as a “serving cell” for UEs 106A-N as illustrated in FIG. 1 A, each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and / or any other base stations), which may be referred to as “neighboring cells”. Such cells may also be capable of facilitating communication between user devices and / or between user devices and the network 100. Such cells may include “macro” cells, “micro” cells, “pico” cells, and / or cells which provide any of various other granularities of service area size. For example, base stations 102A-B illustrated in FIG. 1A might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.

[0051] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to an evolved packet core (EPC) network and / or to a NR core (NRG) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0052] Note that a UE 106 may be capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicateDocket No. P69542WO1 using a wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD- SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1 xRTT, 1xEV- DO, HRPD, eHRPD), etc.). The UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol, if desired. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0053] In some embodiments, the base station 102A may select a paging configuration and a PEI configuration for UEs 106. The base station 102A may encode and transmit the paging configuration and the PEI configuration to UEs 106 as part of a registration process. Using the paging configuration, UEs 106 can determine which PO and PF to monitor in a paging cycle. Using the PEI configuration, UEs 106 can determine the radio frame that carries relevant PEI.

[0054] FIG. 1 B illustrates user equipment 106 (e.g., one of the devices, such as UEs, 106A through 106N) in communication with a base station 102 and an access point 112, according to some embodiments. The UE 106 may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.

[0055] The UE 106 may include a processor that is configured to execute program instructions stored in memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 may include a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.

[0056] The UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT 1 1xEV-DO I HRPD I eHRPD), LTE / LTE-Advanced, or 5G NR using a single shared radio and / or GSM, LTE, LTE-Advanced, or 5G NR using the single shared radio. The shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) forDocket No. P69542WO1 performing wireless communications. In general, a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, the radio may implement one or more receive and transmit chains using the aforementioned hardware. For example, the UE 106 may share one or more parts of a receive and / or transmit chain between multiple wireless communication technologies, such as those discussed above.

[0057] In some embodiments, the UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate. As a further possibility, the UE 106 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol. For example, the UE 106 might include a shared radio for communicating using either of LTE or 5G NR (or LTE or I xRTTor LTE or GSM), and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.FIG. 2: Block Diagram of a Base Station (gNB)

[0058] FIG. 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of FIG. 2 is merely one example of a possible base station. As shown, the base station 102 may include processor(s) 204 which may execute program instructions for the base station 102. The processor(s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor(s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.

[0059] The base station 102 may include at least one network port 270. The network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in Figures 1 and 2.

[0060] The network port 270 (or an additional network port) may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider. The core network may provide mobility related services and / or other services to a plurality of devices, such as UE devices 106. In some cases, the network port 270 may couple to a telephone network via the core network, and / or the core network may provide a telephoneDocket No. P69542WO1 network (e.g., among other UE devices serviced by the cellular service provider).

[0061] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In such embodiments, base station 102 may be connected to an evolved packet core (EPC) network and / or to a NR core (NRC) network. In addition, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0062] The base station 102 may include at least one antenna 234, and possibly multiple antennas. The at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via radio 230. The antenna 234 communicates with the radio 230 via communication chain 232. Communication chain 232 may be a receive chain, a transmit chain or both. The radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0063] The base station 102 may be configured to communicate wirelessly using multiple wireless communication standards. In some instances, the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR. In such a case, the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0064] As described further subsequently herein, the base station 102 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 204 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 204 of the base station 102, in conjunction withDocket No. P69542WO1 one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.

[0065] In addition, as described herein, processor(s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 204. Thus, processor(s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 204.

[0066] Further, as described herein, radio 230 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 230. Thus, radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio 230.FIG. 3: Block Diagram of a Server

[0067] FIG. 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of FIG. 3 is merely one example of a possible server. As shown, the server 104 may include processor(s) 344 which may execute program instructions for the server 104. The processor(s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor(s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.

[0068] The server 104 may be configured to provide a plurality of devices, such as base station 102, and UE devices 106 access to network functions, e.g., as further described herein.

[0069] In some embodiments, the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network. In some embodiments, the server 104 may be connected to an evolved packet core (EPC) network and / or to a NR core (NRC) network.

[0070] As described herein, the server 104 may include hardware and software components for implementing or supporting implementation of features described herein. The processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing programDocket No. P69542WO1 instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition) the processor 344 of the server 104, in conjunction with one or more of the other components 354, 364, and / or 374 may be configured to implement or support implementation of part or all of the features described herein.

[0071] In addition, as described herein, processor(s) 344 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s) 344. Thus, processor(s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s) 344. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 344.FIG. 4: Block Diagram of a User Equipment (UE)

[0072] FIG. 4 illustrates an example simplified block diagram of a communication device, such as, a UE 106, according to some embodiments. It is noted that the block diagram of the communication device of FIG. 4 is only one example of a possible communication device. According to embodiments, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet, an unmanned aerial vehicle (UAV), a UAV controller (UAC) and / or a combination of devices, among other devices. As shown, the communication device 106 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components 400 may be implemented as separate components or groups of components for the various purposes. The set of components 400 may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 106.

[0073] For example, the communication device 106 may include various types of memory (e.g., including NAND flash 410), an input / output interface such as connector l / F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), theDocket No. P69542WO1 display 460, which may be integrated with or external to the communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry 429 (e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device 106 may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

[0074] The cellular communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown. The short to medium range wireless communication circuitry 429 may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown. Alternatively, the short to medium range wireless communication circuitry 429 may couple (e.g., communicatively; directly or indirectly) to the antennas 435 and 436 in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas 437 and 438. The short to medium range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

[0075] In some embodiments, as further described below, cellular communication circuitry 430 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). In addition, in some embodiments, cellular communication circuitry 430 may include a single transmit chain that may be switched between radios dedicated to specific RATs. For example, a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.

[0076] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include any of various elements, such as display 460 (which may be a touchscreen display), a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of various other elements capable of providing information to a user and / or receiving or interpreting user input.

[0077] The communication device 106 may further include one or more smart cards 445Docket No. P69542WO1 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards 445. Note that the term “SIM” or “SIM entity” is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC(s) cards 445, one or more eUlCCs, one or more eSIMs, either removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that may be embedded, e.g., may be soldered onto a circuit board in the UE 106, or each SIM may be implemented as a removable smart card. Thus, the SIM(s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards”), and / or the SIMs may be one or more embedded cards (such as embedded UICCs (eUlCCs), which are sometimes referred to as “eSIMs” or “eSIM cards”). In some embodiments (such as when the SIM(s) include an eUlCC), one or more of the SIM(s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM(s) may execute multiple SIM applications. Each of the SIMs may include components such as a processor and / or a memory; instructions for performing SIM / eSIM functionality may be stored in the memory and executed by the processor. In some embodiments, the UE 106 may include a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUlCC cards that implement eSIM functionality), as desired. For example, the UE 106 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs. Various other SIM configurations are also contemplated.

[0078] As noted above, in some embodiments, the UE 106 may include two or more SIMs. The inclusion of two or more SIMs in the UE 106 may allow the UE 106 to support two different telephone numbers and may allow the UE 106 to communicate on corresponding two or more respective networks. For example, a first SIM may support a first RAT such as LTE, and a second SIM may support a second RAT such as 5G NR. Other implementations and RATs are of course possible. In some embodiments, when the UE 106 comprises two SIMs, the UE 106 may support Dual SIM Dual Active (DSDA) functionality. The DSDA functionality may allow the UE 106 to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks. The DSDA functionality may also allow the UE 106 to simultaneously receive voice calls or data traffic on either phone number. In certain embodiments the voice call may be a packet switched communication. In other words, the voice call may beDocket No. P69542WO1 received using voice over LTE (VoLTE) technology and / or voice over NR (VoNR) technology. In some embodiments, the UE 106 may support Dual SIM Dual Standby (DSDS) functionality. The DSDS functionality may allow either of the two SIMs in the UE 106 to be on standby waiting for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active. In some embodiments, DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUlCC) that executes multiple SIM applications for different carriers and / or RATs.

[0079] As shown, the SOC 400 may include processor(s) 402, which may execute program instructions for the communication device 106 and display circuitry 404, which may perform graphics processing and provide display signals to the display 460. The processor(s) 402 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor(s) 402 and translate those addresses to locations in memory (e.g., memory 406, read only memory (ROM) 450, NAND flash memory 410) and / or to other circuits or devices, such as the display circuitry 404, short to medium range wireless communication circuitry 429, cellular communication circuitry 430, connector l / F 420, and / or display 460. The MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor(s) 402.

[0080] As described herein, the communication device 106 may include hardware and software components for implementing the above features for a communication device 106 to communicate a scheduling profile for power savings to a network. The processor 402 of the communication device 106 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 402 of the communication device 106, in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460 may be configured to implement part or all of the features described herein.

[0081] In addition, as described herein, processor 402 may include one or more processing elements. Thus, processor 402 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 402. In addition, each integratedDocket No. P69542WO1 circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s) 402.

[0082] Further, as described herein, cellular communication circuitry 430 and short to medium range wireless communication circuitry 429 may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry 430 and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry 429. Thus, cellular communication circuitry 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry 430. Similarly, the short to medium range wireless communication circuitry 429 may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry 429. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short to medium range wireless communication circuitry 429.FIG. 5: Block Diaaram of Cellular Communication Circuitry

[0083] FIG. 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of FIG. 5 is only one example of a possible cellular communication circuit. According to embodiments, cellular communication circuitry 530, which may be cellular communication circuitry 430, may be included in a communication device, such as communication device 106 described above. As noted above, communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and / or a combination of devices, among other devices.

[0084] The cellular communication circuitry 530 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a-b and 436 as shown (in FIG. 4). In some embodiments, cellular communication circuitry 530 may include dedicated receive chains (including and / or coupled to, e.g., communicatively; directly or indirectly, dedicated processors and / or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown in FIG. 5, cellularDocket No. P69542WO1 communication circuitry 530 may include a modem 510 and a modem 520. Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.

[0085] As shown, modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 535. RF front end 535 may include circuitry for transmitting and receiving radio signals. For example, RF front end 535 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534. In some embodiments, receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.

[0086] Similarly, modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receive circuitry 542 and transmit circuitry 544. In some embodiments, receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.

[0087] In some embodiments, a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572. In addition, switch 570 may couple transmit circuitry 544 to UL front end 572. UL front end 572 may include circuitry for transmitting radio signals via antenna 336. Thus, when cellular communication circuitry 530 receives instructions to transmit according to the first RAT (e.g., as supported via modem 510), switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572). Similarly, when cellular communication circuitry 530 receives instructions to transmit according to the second RAT (e.g., as supported via modem 520), switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572).

[0088] As described herein, the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein. The processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 512 may beDocket No. P69542WO1 configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 512, in conjunction with one or more of the other components 530, 532, 534, 535, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0089] In addition, as described herein, processors 512 may include one or more processing elements. Thus, processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 512.

[0090] The processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor 522, in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.

[0091] In addition, as described herein, processors 522 may include one or more processing elements. Thus, processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors 522.FIG. 6: Block Diagram of a Baseband Processor Architecture for a UE

[0092] FIG. 6 illustrates example components of a device 600 in accordance with some embodiments. It is noted that the device of FIG. 6 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various UEs, as desired.

[0093] In some embodiments, the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown. The components of the illustrated device 600 may be included in a UE 106 or a RAN node, e.g., as part of a BS 102A. In some embodiments,Docket No. P69542WO1 the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor / controller to process IP data received from an EPC). In some embodiments, the device 600 may include additional elements such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud- RAN (C-RAN) implementations).

[0094] The application circuitry 602 may include one or more application processors. For example, the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory / storage and may be configured to execute instructions stored in the memory / storage to enable various applications or operating systems to run on the device 600. In some embodiments, processors of application circuitry 602 may process IP data packets received from an EPC.

[0095] The baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606. Baseband processing circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606. For example, in some embodiments, the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 604 (e.g., one or more of baseband processors 604A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 606. In other embodiments, some or all of the functionality of baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments,Docket No. P69542WO1 modulation / demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping / demapping functionality. In some embodiments, encoding / decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder / decoder functionality. Embodiments of modulation / demodulation and encoder / decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0096] In some embodiments, the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F. The audio DSP(s) 604F may be include elements for compression / decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC).

[0097] In some embodiments, the baseband circuitry 604 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0098] RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604. RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.

[0099] In some embodiments, the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c. In some embodiments,Docket No. P69542WO1 the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a. RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d. The amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 604 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a necessity. In some embodiments, mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0100] In some embodiments, the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608. The baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.

[0101] In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.

[0102] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 606 may include analog-to-digital converter (ADC) andDocket No. P69542WO1 digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.

[0103] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0104] In some embodiments, the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0105] The synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N / N+1 synthesizer.

[0106] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a necessity. Divider control input may be provided by either the baseband circuitry 604 or the applications circuitry 602 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications circuitry 602.

[0107] Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0108] In some embodiments, synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and dividerDocket No. P69542WO1 circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 606 may include an IQ / polar converter.

[0109] FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing. FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.

[0110] In some embodiments, the FEM circuitry 608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606). The transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).

[0111] In some embodiments, the PMC 612 may manage power provided to the baseband circuitry 604. In particular, the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[0112] While FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604, in other embodiments the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.

[0113] In some embodiments, the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in a radio resource control_Connected (RRC_Connected) state, where it is still connected to the RANDocket No. P69542WO1 node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.

[0114] If there is no data traffic activity for an extended period of time, then the device 600 may transition off to an RRCJdle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 600 goes into a very low power state and it performs paging where, again, it periodically wakes up to listen to the network and then powers down at least portions of the device again. The device 600 may not receive data in this state. In order to receive data, it will transition back to an RRC_Connected state.

[0115] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.FIG. 7: Block Diagram of an Interface of Baseband Circuitry

[0116] FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments. It is noted that the baseband circuitry of FIG. 7 is merely one example of a possible circuitry, and that features of this disclosure may be implemented in any of various systems, as desired.

[0117] As discussed above, the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors. Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send / receive data to / from the memory 604G.

[0118] The baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries / devices, such as a memory interface 712 (e.g., an interface to send / receive data to / from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send / receive data to / from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send / receive data to / from RF circuitry 606 of FIG. 6), a wireless hardware connectivity interface 718 (e.g., an interface to send / receive data to / from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interfaceDocket No. P69542WO1720 (e.g., an interface to send / receive power or control signals to / from the PMC 612.FIG. 8: Control Plane Protocol Stack

[0119] FIG. 8 is an illustration of a control plane protocol stack in accordance with some embodiments. In this embodiment, a control plane 800 is shown as a communications protocol stack between the UE 106A (or alternatively, the UE 106B), the RAN node 102A (or alternatively, the RAN node 102B), and the mobility management entity (MME) 621 .

[0120] The PHY layer 801 may transmit or receive information used by the MAC layer 802 over one or more air interfaces. The PHY layer 801 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 805. The PHY layer 801 may still further perform error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.

[0121] The MAC layer 802 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0122] The RLC layer 803 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 803 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC layer 803 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

[0123] The PDCP layer 804 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upperDocket No. P69542WO1 layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

[0124] The main services and functions of the RRC layer 805 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting. Said MIBs and SIBs may comprise one or more information elements (lEs), which may each comprise individual data fields or data structures.

[0125] The UE 601 and the RAN node 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 801 , the MAC layer 802, the RLC layer 803, the PDCP layer 804, and the RRC layer 805.

[0126] The non-access stratum (NAS) protocols 806 form the highest stratum of the control plane between the UE 601 and the MME 621. The NAS protocols 806 support the mobility of the UE 601 and the session management procedures to establish and maintain IP connectivity between the UE 601 and the P-GW 623.

[0127] The S1 Application Protocol (S1 -AP) layer 815 may support the functions of the S1 interface and comprise Elementary Procedures (EPs). An EP is a unit of interaction between the RAN node 102A and the network 100. The S1 -AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and configuration transfer.

[0128] The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP / IP layer) 814 may ensure reliable delivery of signaling messages between the RAN node 102A and the MME 621 based, in part, on the IP protocol, supported by the IP layer 813. The L2 layer 812 and the L1 layer 81 1 may refer to communication links (e.g.,Docket No. P69542WO1 wired or wireless) used by the RAN node and the MME to exchange information.

[0129] The RAN node 102A and the MME 621 may utilize an S1 -MME interface to exchange control plane data via a protocol stack comprising the L1 layer 81 1 , the L2 layer 812, the IP layer 813, the SCTP layer 814, and the S1-AP layer 815.FIG. 9: User Plane Protocol Stack

[0130] FIG. 9 is an illustration of an example of a user plane protocol stack in accordance with some embodiments. In this embodiment, a user plane 900 is shown as a communications protocol stack between the UE 106A (or alternatively, the UE 106B or 106N), the RAN node 102A (or alternatively, the RAN node 102B), the S-GW 622, and the P-GW 623. The user plane 900 may utilize at least some of the same protocol layers as the control plane 800. For example, the UE 601 and the RAN node 102A may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 801 , the MAC layer 802, the RLC layer 803, the PDCP layer 804.

[0131] The General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 904 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example. The UDP and IP security (UDP / IP) layer 903 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 102A and the S-GW 622 may utilize an S1 -U interface to exchange user plane data via a protocol stack comprising the L1 layer 81 1 , the L2 layer 812, the UDP / IP layer 903, and the GTP-U layer 904. The S-GW 622 and the P-GW 623 may utilize an S5 / S8a interface to exchange user plane data via a protocol stack comprising the L1 layer 811 , the L2 layer 812, the UDP / IP layer 903, and the GTP-U layer 904. As discussed above with respect to FIG. 8, NAS protocols support the mobility of the UE 106 and the session management procedures to establish and maintain IP layer 813 connectivity between the UE 106 and the P-GW 623.

[0132] For the remainder of this disclosure, references to base station (gNB) and user equipment (UE) are assumed to refer to base station (gNB) 102 and user equipment (UE) 106, even though specific reference numerals may be omitted.FIG. 10: Core Network

[0133] FIG. 10 illustrates an example architecture of a system 1000 including a coreDocket No. P69542WO1 network (CN) 1020 in accordance with various embodiments. The CN 1020 may be a core network for a 5G System (which may be referred to as a 5GC). The system 1000 is shown to include a UE 1001 , which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously; a (R)AN 1010, which may be the same or similar to the BSs 102A or 102N discussed previously; and a data network (DN) 1003, which may be, for example, operator services, Internet access, or 3rd party services; and a CN 1020. The CN 1020 may include a number of network functions (NFs) including an Authentication Server Function (AUSF) 1022; an Access and Mobility Management Function (AMF) 1021 ; a Session Management Function (SMF) 1024; a Network Exposure Function (NEF) 1023; a Policy Control Function (PCF) 1026; a Network Repository Function (NRF) 1025; a Unified Data Management (UDM) 1027; an Application Function (AF) 1028; a User Plane Function (UPF) 1002; a Network Slice Selection Function (NSSF) 1029; and Network Data Analytics Function (NWDAF) 1030. These network functions may be implemented, in some cases, as virtualized software based functions / services. It should be noted that NFs may include additional functions not explicitly illustrated in FIG. 10.

[0134] The UPF 1002 may act as an anchor point for intra-RAT and inter-RAT mobility, an external packet data unit (PDU) session point of interconnect to DN 1003, and a branching point to support mufti-homed PDU session. A PDU session is a logical connection between the UE and the DN. The UPF 1002 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (user plane (UP) collection), perform traffic usage reporting, perform quality of service (QoS) handling for a user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform Uplink Traffic verification (e.g., Service Data Flows (SDF) to QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 1002 may include an uplink classifier to support routing traffic flows to a data network, The DN 1003 may represent various network operator services, Internet access, or third party services. DN 1003 may include, or be similar to, application server 104 discussed previously. The UPF 1002 may interact with the SMF 1024 via an N4 reference point between the SMF 1024 and the UPF 1002.

[0135] The AUSF 1022 may store data for authentication of UE 1001 and handle authentication-related functionality, The AUSF 1022 may facilitate a common authentication frame work for various access types. The AUSF 1022 may communicate with the AMF 1021 via an N12 reference point between the AMF 1021 and the AUSF 1022; and mayDocket No. P69542WO1 communicate with the UDM 1027 via an N13 reference point between the UDM 1027 and the ALISF 1022. Additionally, the AUSF 1022 may exhibit an Nausf service-based interface.

[0136] The AMF 1021 may be responsible for registration management (e.g., for registering UE 1001 , etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. The AMF 1021 may be a termination point for the an N11 reference point between the AMF 1021 and the SMF 1024. The AMF 1021 may provide transport for SM messages between the UE 1001 and the SMF 1024, and act as a transparent proxy for routing SM messages. AMF 1021 may also provide transport for Short Message Service (SMS) messages between UE 1001 and an SMSF (not shown by FIG. 10). AMF 1021 may act as a security anchor function (SEAF), which may include interaction with the AUSF 1022 and the UE 1001 , receipt of an intermediate key that was established as a result of the UE 1001 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 1021 may retrieve the security material from the AUSF 1022. AMF 1021 may also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys. Furthermore, AMF 1021 may be a termination point of a RAN control plane (CP) interface, which may include or be an N2 reference point between the (R)AN 1010 and the AMF 1021 ; and the AMF 1021 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.

[0137] AMF 1021 may also support NAS signaling with a UE 1001 over a non-3GPP Inter-Working Function (N3IWF) interface. The N3IWF may be used to provide access to untrusted entities. N3IWF may be a termination point for the N2 interface between the (R)AN 1010 and the AMF 1021 for the control plane, and may be a termination point for the N3 reference point between the (R)AN 1010 and the UPF 1002 for the user plane. As such, the AMF 1021 may handle N2 signaling from the SMF 1024 and the AMF 1021 for PDU sessions and encapsulate / de- encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking while considering QoS requirements associated with such marking received over N2. N3IWF may also relay uplink and downlink control plane non-access stratum (NAS) signaling between the UE 1001 and AMF 1021 via an N1 reference point between the UE 1001 and the AMF 1021 , and relay uplink and downlink user-plane packets between the UE 1001 and UPF 1002. The N3IWF also provides mechanisms for internet protocol security (IPsec) tunnel establishment with the UE 1001 . The AMF 1021 may exhibit an Namf serviceDocket No. P69542WO1 based interface, and may be a termination point for an N14 reference point between two AMFs 1021 and an N17 reference point between the AMF 1021 and a 5G Equipment Identity Register (5G-EIR) (not shown by FIG. 10).

[0138] The UE 1001 may need to register with the AMF 1021 in order to receive network services. Registration Management (RM) is used to register or deregister the UE 1001 with the network (e.g., AMF 1021 ), and establish a UE context in the network (e.g., AMF 1021 ). The UE 1001 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 1001 is not registered with the network, and the UE context in AMF 1021 holds no valid location or routing information for the UE 1001 so the UE 1001 is not reachable by the AMF 1021. In the RM REGISTERED state, the UE 1001 is registered with the network, and the UE context in AMF 1021 may hold a valid location or routing information for the UE 1001 so the UE 1001 is reachable by the AMF 1021 . In the RM-REGISTERED state, the UE 1001 may perform mobility registration update procedures, perform periodic registration update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 1001 is still active), and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.

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

[0140] Connection Management (CM) may be used to establish and release a signaling connection between the UE 1001 and the AMF 1021 over the N1 interface. The signaling connection is used to enable NAS signaling exchange between the UE 1001 and the CN 1020, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 1001 between the AN (e.g., AN 1010) and the AMF 1021 . The UE 1001 may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode. When the UE 1001 isDocket No. P69542WO1 operating in the CM-IDLE state / mode, the UE 1001 may have no NAS signaling connection established with the AMF 1021 over the N1 interface, and there may be (R)AN 1010 signaling connection (e.g., N2 and / or N3 connections) for the UE 1001 . When the UE 1001 is operating in the CM-CONNECTED state / mode, the UE 1001 may have an established NAS signaling connection with the AMF 1021 over the Nl interface, and there may be a (R)AN 1010 signaling connection (e.g., N2 and / or N3 connections) for the UE 1001. Establishment of an N2 connection between the (R)AN 1010 and the AMF 1021 may cause the UE 1001 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 1001 may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R)AN 1010 and the AMF 1021 is released.

[0141] The SMF 1024 may be responsible for session management (SM) session establishment, modify and release, including tunnel maintain between UPF and AN node); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 1001 and a data network (DN) 1003 identified by a Data Network Name (DNN). PDU sessions may be established upon UE 1001 request, modified upon UE 1001 and CN 1020 request, and released upon UE 1001 and CN 1020 request using NAS SM signaling exchanged over the N1 reference point between the UE 1001 and the SMF 1024. Upon request from an application server, the CN 1020 may trigger a specific application in the UE 1001. In response to receipt of the trigger message, the UE 1001 may pass the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in the UE 1001. The identified application(s) in the UE 1001 may establish a PDU session to a specific data network name (DNN). The SMF 1024 may check whether the UE 1001 requests are compliant with user subscription information associated with the UE 1001. In this regard, the SMF 1024 may retrieve and / or request to receive update notifications on SMF 1024 level subscription data from the UDM 1027.

[0142] The SMF 1024 may include the following roaming functionality: handling local enforcement to apply QoS SLAB virtual Public Land Mobile Network (VPLMN); chargingDocket No. P69542WO1 data collection and charging interface (VPLMN); lawful intercept (in VPLMN for SM events and interface to LI system); and support for interaction with external DN for transport of signaling for PDU session authorization / authentication by external DN. An N16 reference point between two SMFs 1024 may be included in the system 1000, which may be between another SMF 1024 in a visited network and the SMF 1024 in the home network in roaming scenarios. Additionally, the SMF 1024 may exhibit the Nsmf service-based interface.

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

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

[0145] The PCF 1026 may provide policy rules to control plane function(s) to enforce them, and may also support unified policy framework to govern network behavior, The PCF 1026 may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of the UDM 1027. The PCF 1026 may communicate with the AMF 1021 via an N15 reference point between the PCF 1026 and the AMF 1021 , which may include a PCF 1026 in a visited network and the AMF 1021 in case of roaming scenarios. The PCF 1026 may communicate with the AF 1028 via an NS reference point between the PCF 1026 and the AF 1028; and with the SMF 1024 via an N7 reference point between the PCF 1026 and the SMF 1024, The system 1000 and / or CN 1020 may also include an N24Docket No. P69542WO1 reference point between the PCF 1026 (in the home network) and a PCF 1026 in a visited network, Additionally, the PCF 1026 may exhibit an Npcf service-based interface.

[0146] The UDM 1027 may handle subscription-related information to support the network entities' handling of communication sessions, and may store subscription data of UE 1001. For example, subscription data may be communicated between the UDM 1027 and the AMF 1021 via an NS reference point between the UDM 1027 and the AMF. The UDM 1027 may include two parts, an application FE and a UDR (the FE and UDR are not shown by FIG. 10). The UDR may store subscription data and policy data for the UDM 1027 and the PCF 1026, and / or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1001 ) for the NEF 1023. The Nadr service-based interface may be exhibited by the UDR to allow the UDM 1027, PCF 1026, and NEF 1023 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management. The UDR may interact with the SMF 1024 via an NI0 reference point between the UDM 1027 and the SMF 1024. UDM 1027 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 1027 may exhibit the Nudm service based interface.

[0147] The AF 1028 may provide application influence on traffic routing, provide access to the NOE, and interact with the policy framework for policy control. The NCE may be a mechanism that allows the CN 1020 and AF 1028 to provide information to each other via NEF 1023, which may be used for edge computing implementations. In such implementations, the network operator and third party services may be hosted close to the UE 1001 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. For edge computing implementations, the 5GC may select a UPF 1002 close to the UE 1001 and execute traffic steering from the UPF 502 to DN 1003 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1028. In this way, the AF 1028 may influence UPF (re)selection and traffic routing. Based on operator deployment,Docket No. P69542WO1 when AF 1028 is considered to be a trusted entity, the network operator may permit AF 1028 to interact directly with relevant NFs. Additionally, the AF 1028 may exhibit an Nat service-based interface.

[0148] The NSSF 1029 may select a set of network slice instances serving the UE 501 . The NSSF 1029 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI) is, if needed. The NSSF 1029 may also determine the AMF set to be used to serve the UE 1001 , or a list of candidate AMF(s) 1021 based on a suitable configuration and possibly by querying the NRF 1025. The selection of a set of network slice instances for the UE 1001 may be triggered by the AMF 1021 with which the UE 1001 is registered by interacting with the NSSF 1029, which may lead to a change of AMF 1021. The NSSF 1029 may interact with the AMF 1021 via an N22 reference point between AMF 1021 and NSSF 1029; and may communicate with another NSSF 1029 in a visited network via an N31 reference point (not shown by FIG. 10). Additionally, the NSSF 1029 may exhibit an Nnssf service-based interface.

[0149] The NWDAF 1030 may support the following functionality: Data collection based on subscription to events provided by AMF 1021 , SMF 1024, UPF 1002, PCF 1026, UDM 1027, NSACF (Network Slice Admission Control Function) (not shown in FIG. 10), AF 1028 (directly or via NEF 1023) and operation and management (GAM); Analytics and Data collection using the DCCF (Data Collection Coordination Function) (not shown in FIG. 10); Retrieval of information from data repositories; Data collection of location information using Location Service (LCS); Storage and retrieval of information from ADRF (Analytics Data Repository Function) (not shown in FIG. 10); Analytics and Data collection from MFAF (Messaging Framework Adaptor Function) (not shown in FIG. 10); Retrieval of information about NFs; On demand provision of analytics to consumers; Provision of bulked data related to Analytics ID(s); Provision of Accuracy information about Analytics ID(s); Provision or retrieval of ML Model Accuracy Information or ML Model accuracy degradation about a ML Model; and Vertical Federated Learning (VFL).

[0150] That is, the NWDAF 1030 provides the following services: Events Subscription Service, Analytics Information Service, Data Management Service, ML Model Provision Service, ML Model Training Service, ML Model Monitoring Service, Roaming Data Service, and Roaming Analytics Service. Events Subscription Service enable NFs to subscribe to different analytics information from the NWDAF 1030. Analytics Information Service enables NFs to request and get specific analytics or context information related to analyticsDocket No. P69542WO1 subscriptions from the from NWDAF 1030. Data Management Service enables the NFs to subscribe to notifications when subscribed event(s) are detected or retrieve the subscribed data from the NWDAF 1030. ML Model Provision Service enables NFs to subscribe to notifications when a ML model matching the subscription parameters becomes available. ML Model Training Service enables NFs to subscribe to from notifications for a ML model training. ML Model Monitoring Service enables NFs to subscribe for ML model accuracy, provide analytics feedback information for the analytics generated by the NWDAF 1030 and enable the NWDAF 1030 containing Analytics logical function (AnLF) registers the use and monitoring capability for a ML model into the model provider NWDAF. Roaming Data Service enables NFs to subscribe for input data related to roaming UE(s) for NWDAF analytics. Roaming Analytics Service enables NFs to subscribed to notifications for network data analytics related to roaming UE(s). The Nnf interface is defined for the NWDAF 1030

[0151] The NWDAF 1030 may include the following logical functions: Analytics logical function (AnLF), which is a logical function, which performs inference, derives analytics information and exposes analytics service, and Model Training logical function (MTLF), which is a logical function, which trains Machine Learning (ML) models and exposes new training services (e.g. provides trained ML Model).

[0152] As discussed previously, the CN 1020 may include a short message service function (SMSF), which may be responsible for SMS subscription checking and verification, and relaying SM messages to / from the UE 1001 to / from other entities, such as an SMS- GMSC / IWMSC / SMS-router. The SMS may also interact with AMF 1021 and UDM 1027 for a notification procedure that the UE 1001 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 1027 when UE 1001 is available for SMS).

[0153] The CN 1020 may also include other elements that are not shown by FIG. 10, such as a Data Storage system / architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP), and the like. The Data Storage system may include a Structured Data Storage Network Function (SDSF), air Unstructured Data Storage Function (UDSF), and / or the like. Any network function (NF) may store and retrieve unstructured data into / from the UDSF (e.g., UE contexts), via N18 reference point between any NF and the UDSF (not shown by FIG. 10), Individual NFs may share a UDSF for storing their respective unstructured data or individual NFs may each have their own UDSF located at or near the individual NFs. Addition- ally, the UDSF may exhibit an Nudsf service-based interface (not shown by FIG. 10). The 5G-EIR may be an NF that checks the status of permanent equipment identifier (PEI) for determining whether particular equipment / entities areDocket No. P69542WO1 blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.

[0154] Additionally, there may be many more reference points and / or service-based interfaces between the NF services in the NFs; however, these interfaces and reference points have been omitted from FIG. 10 for clarity. In one example, the CN 1020 may include an Nx interface, which is an inter-CN interface between a mobility management entity (MME) and the AMF 1021 in order to enable interworking between CN 1020 and a CN in a 4G system. Other example interfaces / reference points may include an N5G-EIR servicebased interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.AI / ML Model Development

[0155] As described above, the NWDAF 1030 may include the Model Training logical function (MTLF), which is a logical function, which trains Machine Learning (ML) models and exposes new training services (e.g. provides trained ML Model). ML models may also be referred to as Artificial Intelligence (AI)ZMachie Learning (ML) models.

[0156] The development of the AI / ML models can comprise four main phases: a training, emulation (validation), deployment, and inference phase. The main task involved in each phase are briefly described in the proceeding paragraphs.

[0157] Training Phase: In this phase, the Al model is trained on a dataset. This involves feeding the model with input data and corresponding correct output labels, allowing the model to learn patterns and relationships within the data. Training typically involves optimization algorithms to adjust the model's parameters to minimize errors.

[0158] Emulation Phase: In the emulation phase, the trained model is tested extensively to ensure it performs well on data it has not seen before. This phase involves evaluating the model's performance metrics such as accuracy, precision, recall, etc., using validation datasets. Emulation helps identify any issues with the model's generalization and performance before deployment.

[0159] Deployment Phase: Once the model has been trained and successfully emulated, it's ready for deployment. Deployment involves integrating the model into a production environment where it can make predictions or classifications on new, unseen data. This may involve creating application programming interfaces (APIs) or integrating the model into applications or systems where it will be used.Docket No. P69542WO1

[0160] Inference Phase: In this phase, the deployed model is used to make predictions or classifications on real-world data referred to herein as a “scenario.” A scenario typically refers to a specific situation or problem domain in which an AI / ML model is applied or evaluated. Scenarios help frame the context in which AI / ML model is are deployed. The AI / ML model takes input data, processes it, and produces an output referred to as an inference, e.g., a predicted RSRP for a beam (assisted), or a predicted beam ID.AI / ML Model Monitoring

[0161] The life cycle management (LCM) of the AI / ML models may comprise various aspects of AI / ML model development described above and AI / ML model monitoring described below.

[0162] Monitoring and Evaluation: A monitoring entity, such as a UE 106, base station 102, or application function 1028, can continuously monitor various factors such as data characteristics, system performance metrics, or environmental conditions.

[0163] Decision Making: Based on the monitored factors, the monitoring entity can decide whether to switch to a different machine learning model that is better suited for the current conditions or task, finetune the current model using transfer learning to better match the environmental conditions or indicate the need to fall back to non-AI based positioning.

[0164] Al model switching refers to the process of dynamically selecting or switching between different machine learning models or algorithms based on certain conditions or criteria. This approach is often used in adaptive systems where the optimal model for a particular task may change over time or in different contexts. Al model switching may include the following.

[0165] Model Selection: The monitoring entity selects the most appropriate model from a set of pre-defined models or algorithms. This selection can be based on factors such as accuracy, efficiency, or robustness.

[0166] Model finetuning: Once a model is selected, the model can be further trained on a dataset that is specific to a task. This is known as finetuning. Finetuning a pre-trained model can reduce the amount of initial training for the model, while ensuring the model is trained for the specific task for which it will be used. This enables models to be trained more generally for multiple specific tasks. Finetuning a pre-trained model may be optional, depending on how different the initial training is from the end use of the model.

[0167] Adaptation: Once a new model is selected and optionally finetuned, the monitoring entity adapts its operation to use the newly chosen model for making predictionsDocket No. P69542WO1 or decisions.Vertical Federated Learninq

[0168] As described above, NWDAF 1030 may support Vertical Federated Learning (VFL). VFL is a ML technique where local data sets are not exchanged / shared, while maintaining coordination amongst VFL participants, when training and inference are performed on local ML models. The local data set for local model training in different VFL Participants have different feature spaces for the same samples (e.g., UE IDs). For Vertical Federated Learning, there may be one NWDAF or one AF acting as a VFL server and one or multiple NWDAF(s) and / or one or multiple AF(s) acting as VFL Client(s).

[0169] The main functionalities of a VFL server include: An NWDAF acting as VFL server Discovers and Selects VFL client(s) to participate in a VFL procedure; Requests VFL clients to do local ML model training for an Analytic ID; Aggregates intermediate results from VFL client(s) and Computes intermediate training results for updating its own local ML Model and the ML Models of VFL clients during the VFL training process and sends the intermediate training results towards VFL clients involved in the joint VFL training process; Initiates the VFL inference process using VFL model correlation ID; Aggregates local inference results from VFL clients and generates the final VFL inference result; Send, when appropriate, the final VFL inference result to the consumer.

[0170] The main functionalities of a VFL client include: locally Trains ML Model with the available local data set, which includes the data that may not be allowed to be shared with other VFL clients; Computes the intermediate results for their local ML Models involved in the VFL training and provide reports with the intermediate results to the AF or NWDAF acting as VFL server; and Performs inference based on the local model and local data and provides inference results to VFL server.

[0171] VFL enables cross-domain AI / ML operations across the 5G system and the AF to collaboratively predict different operational quantities, thereby enhancing network operations. Some example use cases include the AF 1028 and the NWDAF 1030 collectively predicting the Quality of Experience (QoE) experienced by a user based on information individually accessed by the NWDAF 1030 and the AF 1028 and the NWDAF 1030 and the AF 1028 collectively predicting the required network configuration to support the desired QoE for one or more users of an application.

[0172] It may be necessary to align the data samples across the different domains (e.g., AF and the 5GS / NWDAF) to perform the VFL operations, especially if each participant doesDocket No. P69542WO1 not have visibility into the other participant’s domain / data. Further, there may be a need to dynamically adapt the sample space for VFL training after the process is initiated due to, for example, user characteristics changing (e.g., due to mobility), or in order to comply with requirements (e.g., “Right to Forget” requirements).

[0173] When the AF 1028 is the VFL Server or Active Participant, VFL training may be performed for one or more UEs 106 or an Area of Interest (Aol), e.g., service area. In this case, the NWDAF 1030 needs to identify the users that can be included in the training based on the AF’s requirements, based on similar spatial, temporal or traffic characteristics. When the NWDAF 1030 initiates VFL to determine network requirements to support a particular QoE with multiple AFs, then the AFs should identify and report associated users with similar QoEs.

[0174] According to the techniques herein, mechanisms are provided for aligning VFL training samples across different domains according to location, identity or other characteristics. The techniques described herein, may allow user samples to be deleted from an ongoing training session due to withdrawal of user consent or change in user characteristics.FIGS. 1 1 A-1 1 B: Sample Aliqnment for AF initiated VFL Trainina

[0175] FIG. 1 1 A illustrates an example of sample alignment for application function (AF) initiated vertical federated learning (VFL) according to some embodiments. In the example illustrated in FIG. 11 A, in a case where, the AF 1028 is to perform VFL for a single UE or a group of UEs. AF 1028 sends to the NWDAF 1030 the list of UEs for performing VFL. NWDAF 1030 sends a revised UE list to the AF 1028 to perform the training. This includes additional UEs that share the same spatial, temporal and traffic characteristics of the UEs identified by the AF 1028 for training.

[0176] FIG. 1 1 A illustrates an example illustration of timing diagram signaling 1 100a between an AF 1028, NEF 1023, NFR 1025, UDM 1027, NWDAF 1030, and other NFs, e.g., AMF 1021 , SMF 1024, NSSF 1029, and PCF 1026, according to some embodiments. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired.

[0177] The signaling 1100a may include the AF 1028 as a VFL Active Participant / VFL Server sending a VFL participant discovery request 1 102a to NEF 1023 by indicating optionally a unique Session ID, Application ID, Analytics ID and the UE IDs for which theDocket No. P69542WO1 training is requested. A Session ID uniquely identifies the set of parameters, users and model configuration across training and inference phases. A Session ID may be included if one has been previously allocated for the same task by the NWDAF 1030 during an earlier sample alignment procedure. For the first attempt, the field may be skipped or use a Temp Session ID. A Session may be unique per PLMN (i.e., have the format mcc.mnc.xyz so that an AF can easily work with NWDAFs 1030 across multiple PLMNs).

[0178] The signaling 1100a may include the NEF 1023 mapping external UE IDs to internal UE IDs and requesting the identity of the appropriate VFL Passive Participant / VFL Client (NWDAF 1030) from the NRF 1025 and the UDM 1027 in a VFL Client discovery request 1 104a. The NRF 1025 returns available NWDAF(s) 1030 to the NEF 1023 which support the requested VFL Passive Participant / VFL Client capability and the requested Analytics ID in a VFL Client discovery response 1 106. The NEF 1023 sends the selected NWDAF list to the requesting AF 1028 in a VF participant discovery request 1 108. The NEF 1023 may assign external IDs for the NWDAFs 1030 that are unique per Session ID.

[0179] The AF 1028 sends the VFL sample and feature alignment request 1 110a to the NEF 1023 including the samples (i.e., external UE IDs) the AF 1028 wants to use for the VFL training, the Session ID or a Session ID request, the analytics ID, optionally the application ID, the feature profile and the training configuration (e.g., prediction accuracy, etc.). The NEF 1023 maps the external UE IDs and AF IDs to the internal UE IDs and AF IDs 1112a based on the information exchanged with the UDM 1027. Alternately, the NEF 1023 may identify a particular NWDAF 1030 as the Primary VFL Client, which then coordinates with other identified NWDAFs 1030 on the NEF’s 1023 behalf. The NEF 1023 sends the VFL sample alignment request 1 1 14 to the VFL Client (NWDAF(s) 1030), including the internal UE IDs, Session ID / Session ID request, Application ID, Analytics ID, feature profile and the training configuration. Alternately, the NEF 1023 may use the Member UE Selection Assistance service to identify suitable UEs.

[0180] Based on the feature profile, requested analytics ID, the training configuration and the internal UE IDs, the NWDAF 1030 identifies the required NFs and additional UEs required for the training procedure 1 1 16, e.g., to meet the prediction accuracy requirement. The NWDAF 1030 determines the availability of data related to the internal UE IDs from other NFs and determines the intersection set of samples across all the identified NFs that will satisfy the training requirements and collects input data 1 1 18a. The NWDAF 1030 sends the VFL sample alignment response 1 120 to the NEF 1023 including the session ID, status (e.g., enough samples found, reject due insufficient samples, etc.), additional internalDocket No. P69542WO1UE IDs identified for the training process, optionally the application ID and the analytics ID.

[0181] If multiple NWDAFs 1030 are involved, the NEF 1023 collects the sample alignment responses from the NWDAFs 1030. The NEF 1023 maps the internal UE IDs to the external UE IDs 1 122. Optionally, the NEF may identify a particular NWDAF 1030 as the Primary VFL Client, which then coordinates with other identified NWDAFs 1030 on the NEF’s behalf. The NEF 1023 sends the VFL sample and feature alignment response 1 124 to the AF 1028 including the session ID, status, additional external UE IDs, and optionally application ID and analytics ID.

[0182] the AF 1028 verifies 1126 if the additional external UE IDs identified by the NWDAF 1030 can be supported by the AF 1028. The AF 1028 also verifies whether the selected samples meet the requirements. If the AF 1028 determines that the required analytics quality cannot be achieved with the identified samples, then the AF 1028 can either not go ahead with the training process, if the training process has not yet started or terminate the VFL training process if the training process is already in progress. The AF 1028 can thereafter initiate a new sample alignment process. The AF 1028 can restart the sample alignment process 1 128 with the VFL Client (NWDAF 1030) with different parameters, if the previous attempt is unsuccessful.

[0183] FIG. 1 1 B illustrates an example of sample alignment for application function (AF) initiated vertical federated learning (VFL) according to some embodiments. In the example illustrated in FIG. 11 B, in a case where, the AF 1028 performs VFL for a particular area of interest (AOI). AF 1028 sends to the NWDAF 1030 the AOI for performing VFL. NWDAF 1030 sends a list of UEs to the AF 1028 that belong to the AOI that may be used for training. In some examples, AF 1028 may add a requested time frame along with the training request.

[0184] FIG. 1 1 B illustrates an example illustration of timing diagram signaling 1 100a between an AF 1028, NEF 1023, NFR 1025, UDM 1027, NWDAF 1030, and other NFs, e.g., AMF 1021 , SMF 1024, NSSF 1029, and PCF 1026, according to some embodiments. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired.

[0185] The signaling 1100b may include the AF 1028 as a VFL Active Participant / VFL Server sending a VFL participant discovery request 1 102b to NEF 1023 by indicating optionally a unique Session ID, Application ID, Analytics ID and the Area of Interest (AOI) for which the training is requested. In other examples, additional / alternative filter parameter to AOI may be used. The signaling 1100b may include the NEF 1023 identifying the internalDocket No. P69542WO1UE IDs associated with requested parameters and requests the identity of the appropriate VFL Passive Participant / VFL Client (NWDAF) from the NRF 1025 and the UDM 1027. That is, the NEF 1023 may map the AOI filter condition to internal UE IDs. The NRF 1025 returns available NWDAF(s) to the NEF 1023 which support the requested VFL Passive Participant / VFL Client capability and the requested Analytics ID in a VFL Client discovery response 1 106. The NEF 1023 sends the selected NWDAF list to the requesting AF 1028 in a VF participant discovery request 1108. The NEF 1023 may assign external IDs for the NWDAFs that are unique per Session ID.

[0186] The AF 1028 send the VFL sample and feature alignment request 11 10b to the NEF 1023 including the requested parameters or filters (e.g., Aol) that the AF 1028 to use for the VFL training, the analytics ID, the application ID, the feature profile and the training configuration (e.g., prediction accuracy, etc.). The NEF 1023 identifies the internal UE IDs for the requested parameters or filters 11 12b based on the information exchanged with the UDM 1027. Alternately, the NEF 1023 may use the Member UE Selection Assistance service to identify suitable UEs. The NEF 1023 sends the VFL sample alignment request 11 14 to the VFL Client (NWDAF(s) 1030), including the internal UE IDs, Session ID / Session ID request, Application ID, Analytics ID, feature profile and the training configuration. Alternately, the NEF 1023 may use the Member UE Selection Assistance service to identify suitable UEs.

[0187] Based on the feature profile, requested analytics ID, the training configuration and the internal UE IDs, the NWDAF 1030 identifies the required NFs and additional UEs required for the training procedure 11 16. The NWDAF 1030 determines the availability of data related to the internal UE IDs from other NFs and determines the intersection set of samples across all the identified NFs that will satisfy the training requirements and collects input data 11 18b. The identified UEs may be a sub-set of the internal UE IDs previously identified by the NEF 1023 based on the requested parameters or filters from the AF. The NWDAF 1030 sends the VFL sample alignment response 1 120 to the NEF 1023 including the session ID, status additional internal UE IDs identified for the training process, optionally the application ID and the analytics ID.

[0188] If multiple NWDAFs 1030 are involved, the NEF 1023 collects the sample alignment responses from the NWDAFs 1030. The NEF 1023 maps the internal UE IDs to the external UE IDs 1122. The NEF 1023 sends the VFL sample and feature alignment response 1 124 to the AF 1028 including the session ID, status, additional external UE IDs, and optionally application ID and analytics ID.Docket No. P69542WO1

[0189] The AF 1028 verifies 1126 if the additional external UE IDs identified by the NWDAF 1030 can be supported by the AF 1028. The AF 1028 also verifies whether the selected samples meet the requirements. If the AF 1028 determines that the required analytics quality cannot be achieved with the identified samples, then the AF 1028 can either not go ahead with the training process, if the training process has not yet started or terminate the VFL training process if the training process is already in progress. The AF 1028 can thereafter initiate a new sample alignment process. The AF 1028 can restart the sample alignment process 1 128 with the VFL Client (NWDAF 1030) with different parameters, if the previous attempt is unsuccessful.FIG. 12: Sample Alignment for NWDAF initiated VFL Training

[0190] FIG. 12 illustrates an example of an example of sample alignment for network data analytics function initiated (NWDAF) vertical federated learning (VFL) according to some embodiments. In the example illustrated in FIG. 12, in a case where, the NWDAF 1030 is to perform VFL for a particular feature profile with multiple AFs 1028. NWDAF 1030 sends to the AFs 1028 the feature profile that NWDAF 1030 is to perform VFL for, optionally with additional filter information (e.g., AOI, etc.). The AFs 1028 respond with relevant Application ID(s) and UE ID list corresponding to the requested profile.

[0191] FIG. 12 illustrates an example illustration of timing diagram signaling 1100a between an AF 1028, NEF 1023, NFR 1025, UDM 1027, NWDAF 1030, and other NFs, e.g., AMF 1021 , SMF 1024, NSSF 1029, and PCF 1026, according to some embodiments. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired.

[0192] The signaling 1200 may include NWDAF 1030 as the VFL Active Participant / VFL Server sending VFL participant discovery request 1202 to the NRF 1025 indicating a unique Session ID, Analytics ID (e.g., an Application QoE (e.g., video frame rate)), and optionally, additional parameters or filters (e.g., Aol). The Application QoE may be associated with a tolerance value. The NRF 1025 identifies 1204 the AFs 1028 that support the requested Application QoE within the tolerance limits, and optionally internal UE IDs associated with the requested Application QoE. The NRF 1025 sends a VFL participant discovery response 1206 to the requesting NWDAF 1030, including the Session ID, identified AFs that support the requested Application QoE, and optionally internal UE IDs that are associated with the requested Application QoE at the identified AFs.Docket No. P69542WO1

[0193] Based on the requested analytics ID, Application ID and the internal UE IDs, the NWDAF 1030 identifies 1208 the required NFs. The NWDAF 1030 short-lists a minimum set of samples by identifying 1210 a sub-set of internal UE IDs to perform VFL training with, based on one or more of the following factors: the required prediction accuracy; the similarity in Application QoE requested by the NWDAF 1030 and the supported Application QoEs by the various AF; factors to attain diversity of samples in terms of location, mobility, user types, AF subscription, etc. The NWDAF 1030 sends the VFL sample alignment request 1212 to the NEF 1023 including the Session ID and the list of UEs short-listed by the NWDAF 1030 to perform VFL training with.

[0194] The NEF 1023 maps 1214 the internal UE IDs provided by the NWDAF 1030 to external UE IDs. The NEF 1023 sends the VFL sample alignment request 1216 to the VFL Client (AF(s) 1028) identified by the NWDAF 1030, including the Session ID, optionally the Analytics ID (e.g., Application QoE), and optionally, the list of external UE IDs. The NEF may need to repeat this step with multiple AFs 1023 with their respective UE ID lists. The AF 1028 responds with the VFL sample alignment response 1218 including the Session ID and the status of the sample alignment request (e.g., accept, reject due to user is no longer available, reject due to too many users, etc.), and optionally a list of external UE IDs that support the Analytics ID (Application QoE). The NEF 1023 maps 1220 the external UE IDs provided by the AF 1023 to internal UE IDs. The NEF 1023 sends the VFL sample alignment response 1222 to the requesting NWDAF 1030. 1208 to 1222 may be repeated 1224 if the status in the received VFL sample alignment response 1222 is rejected or if the AF 1028 provides UE ID(s) associated with the requested Application QoE.FIGS. 13A-13B: Sample Alignment for NWDAF initiated VFL T raininq

[0195] FIG. 13A illustrates an example of a sample updating during and after a vertical federated learning (VFL) training procedure, according to some embodiments. In the example illustrated in FIG. 13B, in a case where, UDM 1027 informs NWDAF 1030 about a UE withdrawing consent to share its data for training and NWDAF 1030 initiates a sample update procedure with AF 1028 via NEF 1023 (e.g., for untrusted NEF).

[0196] FIG. 13A illustrates an example illustration of timing diagram signaling 1300a between an AF 1028, NEF 1023, NFR 1025, UDM 1027, NWDAF 1030, and other NFs, e.g., AMF 1021 , SMF 1024, NSSF 1029, and PCF 1026, according to some embodiments. In various embodiments, some of the signaling shown may be performed concurrently, in aDocket No. P69542WO1 different order than shown, or may be omitted. Additional signaling may also be performed as desired.

[0197] The signaling 1300a may include NWDAF 1030 (as VFL Server or Client) and the AF (as VFL Client or Server) previously performing sample alignment, for example, as described above, and having initiated VFL training 1302. In one example, the UDM 1027 notifies the NWDAF 1030 through a Service Specific Authorization Data Notification 1303 about authorization revoke or update of subscription data associated to the UE. The NWDAF 1030 may have subscribed previously during Service Specific Authorization Data Retrieval to receive such notification. The NWDAF 1030 responds with an acknowledgement (ACK) 1304. In one example, another NF sends a remove data request 1305 to the NWDAF 1030 including the affected internal UE ID(s), for example, due to nonavailability of data associated with the UE ID(s). The NWDAF 1030 responds with an ACK 1306.

[0198] The NWDAF 1030 sends a VFL sample update request 1308a to the NEF 1023 including the Session ID, the internal UE ID(s) to be removed from training, optionally internal UE ID(s) to be added to the training process, and optionally re-training parameters (e.g., re-start training, re-train from specified checkpoint, etc.). In some examples, the VFL Server may specify training checkpoints during the training procedure. In one example, when the sample space is updated during training (e.g., UE(s) dropping out of the training process), the VFL Server and Client(s) retrain from the latest training checkpoint with the new sample space, after deleting the identified samples and features.

[0199] The NEF 1023 maps internal UE ID(s) to external UE ID(s) 1310. The NEF 1023 sends VFL sample update request 1312a to the AF 1028 including the Session ID, the external UE ID(s) to be removed from training, optionally internal UE ID(s) to be added to the training process, and optionally re-training parameters (e.g., re-start training, re-train from specified checkpoint, etc.). The AF 1028 responds with VFL sample update response 1314 to the NEF 1023, including Session ID, status (sample deletion successful, unsuccessful, etc.), optionally external UE ID(s) to be added to the training process (If AF is the VFL Server / Active Participant), and optionally re-training parameters.

[0200] The NEF 1023 maps 1316 the external UE ID(s) to internal UE ID(s). The NEF 1023 sends the VFL sample update response 1318 to the requesting NWDAF 1030 including the Session ID, Status, optionally internal UE ID(s) to be added to training process and optionally re-training parameters. It should be noted that in some examples, after model training is completed, if inference is needed for a sample that did not participate in training,Docket No. P69542WO1 then the VFL Server may first determine the prediction quality with the already trained models at the Server and the VFL Clients. If the performance is less than a threshold, the VFL Server may either initiate a new training process or re-train the existing models from the latest checkpoint.

[0201] FIG. 13B illustrates an example of a sample updating during and after a vertical federated learning (VFL) training procedure, according to some embodiments. In the example illustrated in FIG. 13B, AF 1028 initiates a sample update procedure. For example, AF 1028 may initiate a sample update procedure based on NWDAF 1030 determining that a UE should (or is required to) be removed from a training set, for example, due to UE mobility, stopping use of an application, etc.

[0202] FIG. 13B illustrates an example illustration of timing diagram signaling 1300a between an AF 1028, NEF 1023, NFR 1025, UDM 1027, NWDAF 1030, and other NFs, e.g., AMF 1021 , SMF 1024, NSSF 1029, and PCF 1026, according to some embodiments. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired.

[0203] The signaling 1300b may include the NWDAF 1030 (as an Active or Passive participant) and the AF 1028 (as a Passive or Active participant) previously performing sample alignment, for example, as described above, and having initiated VFL training 1302. The AF 1028 sends a VFL sample update request 1308b to the NEF 1023 including the Session ID, the external UE ID(s) to be removed from training, optionally external UE ID(s) to be added to the training process (If AF is the VFL Server / Active Participant), and optionally re-training parameters (e.g., re-start training, re-train from specified checkpoint, etc.). The NEF 1023 maps 1316 external UE IDs to internal UE IDs and determines appropriate NWDAF from the Session ID. The NEF 1023 sends VFL A sample update request 1312b to the NWDAF 1030 including the Session ID, the external UE ID(s) to be removed from training, optionally external UE ID(s) to be added to the training process, and optionally re-training parameters.

[0204] The NWDAF 1030 responds with A VFL sample update response 1314b to the NEF 1023, including Session ID, status (sample deletion successful, unsuccessful, etc.), optionally external UE ID(s) to be added to the training process (If NWDAF 1030 is the VFL Server / Active Participant), and optionally re-training parameters. The NEF 1023 maps 1310 the internal UE ID(s) to external UE ID(s). The NEF 1023 sends the VFL sample update response 1318b to the AF 1028 including the Session ID, Status, optionally external UEDocket No. P69542WO1ID(s) to be added to training process and optionally re-training parameters.FIGS. 14A-14B: VFL Model Management

[0205] FIG. 14A illustrates an example of vertical federated learning (VFL) model management according to some embodiments. In the example illustrated in FIG. 14A, in a case where the NWDAF 1030A acts as the VFL Server, the NWDAF 1030A provides initial local models to the VFL clients. Local VFL models may be assigned unique identifiers, allowing reuse of trained models for multiple sessions.

[0206] FIG. 14A illustrates an example illustration of timing diagram signaling 1400 between an AF 1028, NEF 1023, and NWDAFs 1030A-1030B, according to some embodiments. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired.

[0207] In the example illustrated in FIG. 14A, NWDAF 1030A is the VFL Server. NWDAF 1030A supplies either the local VFL models or model identifiers to the VFL Clients. The VFL Clients may include other NWDAFs 1030B and AF(s) 1028 identified as VFL Clients during a participant discovery procedure. The NWDAF 1030A (VFL Server) assigns an identifier to the supplied local model (e.g., Model ID, VFL Model Correlation ID, etc.). The NWDAF 1030A may assign a PLMN-wide unique identity to the model, for example, by including a portion of the NWDAF’s 1030A own identifier (e.g., {[NWDAF identifier], [Model ID]}). The model identifier may be retained by all participants (VFL Server and Client(s)) for the remainder of the Training phase and also the following Inference phase. For a subsequent VFL session, covering either training / re-training or inference, between the same set of VFL Server and VFL Client(s), the VFL Server may request the VFL Server(s) to use the previously trained local VFL models by including the previously assigned model identifier in the configuration request.

[0208] The signaling 1400, may have a VFL participant discovery procedure, for example, a VFL participant discovery procedure as described above, being previously completed 1402. The NWDAF 1030A (VFL Server) sends the VFL model management request 1404 to the NEF 1023 (for untrusted AF 1028) and other NWDAF(s) 1030B acting as VFL Client(s). The VFL model management request includes the Session ID, VFL local model parameters (if this is the first session w9ith the VFL Client for the same Application ID and Analytics ID) OR VFL model identifier, (i.e., Model ID, VFL model correlation ID, etc.,) if the VFL Server had established a previous session with the same VFL Client(s) forDocket No. P69542WO1 the same Analytics ID and Application ID. The NEF 1023 forwards the VFL model management request 1406 to the AF 1028 (VFL Client). The AF 1028 (VFL Client) responds with the VFL model management response 1408 including the same Session ID and the Status of the request. For example, the status of the request may use SUCCESS when VFL model parameters were successfully configured or when the supplied model identifier matches that of a stored local model at the VFL Client, and use FAIL when either the model parameters were not successfully configured or the supplied model identifier does not match any stored local model. The NEF 1023 forwards the VFL model management response 1410 to the NWDAF 1030A (VFL Server). Other NWDAF(s) 1030B acting as VFL Client(s) may also respond with the VFL model management response(s).

[0209] FIG. 14B illustrates an example of vertical federated learning (VFL) model management according to some embodiments. In the example illustrated in FIG. 14B, in a case where, in a case where the AF 1028 acts as the VFL Server, the NWDAF 1030A provides initial local models to the VFL clients. Local VFL models may be assigned unique identifiers, allowing reuse of trained models for multiple sessions.

[0210] FIG. 14B illustrates an example illustration of timing diagram signaling 1300a between an AF 1028, NEF 1023, and NWDAFs 1030A-1030B, according to some embodiments. In various embodiments, some of the signaling shown may be performed concurrently, in a different order than shown, or may be omitted. Additional signaling may also be performed as desired.

[0211] In the example illustrated in FIG. 14B, AF 1028 act as the VFL Server and the initial local VFL models are supplied by the NWDAF 1030A (VFL Client). If multiple NWDAFs 1030A-1030B have been identified as VFL Clients, then the AF 1028 selects one NWDAF to supply the initial local VFL model. The chosen NWDAF provides the local model or model identifier to other NWDAFs acting as VFL Clients as identified by the AF 1028. The chosen NWDAF assigns an identifier to the supplied local model (e.g., Model ID, VFL Model Correlation ID, etc.). The NWDAF may assign a PLMN-wide unique identity to the model, for example, by including a portion of the NWDAF’s own identifier (e.g., {[NWDAF identifier], [Model ID]}). The model identifier may be retained by all the participants (VFL Server, Client(s)) for the remainder of the Training phase and also the following Inference phase. For a subsequent VFL session between the same set of VFL Server and VFL Client(s), the VFL Server may request the VFL Server(s) to use the previously trained local VFL models by including the previously assigned model identifier in the configuration request.Docket No. P69542WO1

[0212] The signaling 1450 may have a VFL participant discovery procedure, for example, a VFL participant discovery procedure as described above, being previously completed 1402. The AF 1028 (VFL Server) sends the VFL model management request 1454 to the NEF 1023 (for untrusted AF). The model management request 1454 includes the Session ID, VFL model identifier, i.e., Model ID, VFL model correlation ID, etc. (if the VFL Server had established a previous session with the same VFL Client(s) for the same Analytics ID and Application ID), and the external NWDAF ID for the NWDAF chosen as model repository. The NEF 1023 forwards the VFL model management request 1456 to the VFL Client (NWDAF 1030B). The VFL Client (NWDAF 1030B) responds to the NEF 1023 and any other VFL Clients (NWDAFs) previously identified in the participation discovery with the VFL model management response 1458. The VFL model management response 1458 includes the same Session ID and the VFL local model parameters (if this is the first session with the VFL Client for the same Application ID and Analytics ID) OR VFL identifier, i.e., Model ID, VFL model correlation ID, etc. (if the VFL Server had established a previous session with the same VFL Client(s) for the same Analytics ID and Application ID). The NEF 1023 forwards the VFL model management response 1460 to the AF 1028 (VFL Server).FIGS. 15A-15B: Flow Charts of sample alignment for Vertical Federated Learning (VFL) at a Network (NW)

[0213] FIGS. 15A-15B illustrates a flow charts of example methods of sample alignment for a vertical federated learning (VFL) training procedure at a network (NW), according to some embodiments, according to some embodiments. The methods shown in FIGS. 15A- 15B may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0214] Referring to FIG. 15A, the method 1500 comprises sending a sample alignment request, as shown at block 1510 and receiving a sample alignment response, as shown at block 1520.

[0215] Referring to FIG. 15B, the method 1550 comprises receiving a sample alignment request, as shown at block 1560 and sending a sample alignment response, as shown at block 1570.

[0216] The sample alignment request and the sample alignment response may be sentDocket No. P69542WO1 and / or received by various network functions, for example, as described above. Further, the sample alignment request and the sample alignment response may be sent and / or received by a VFL server or VFL client, as described above.

[0217] In some examples, a sample alignment request includes a session identifier, external User Equipment identifiers (UE IDs) identifying UEs for training, and a machine learning (ML) model training configuration.

[0218] In some examples, a sample alignment request includes a session identifier, external, an area of interest filter, and a machine learning (ML) model training configuration.

[0219] In some examples, a sample alignment request includes a list of a sub-set of internal UE IDs.

[0220] In some examples, a sample alignment response includes session identifier, status information, and external User Equipment identifiers (UE IDs) of additional UEs identified for training based on the session identifier and the ML model training configuration.

[0221] In some examples, includes the session identifier, status information, and external User Equipment identifiers (UE IDs) of UEs identified for training based on the session identifier, the area of interest filter, and the ML model training configuration

[0222] In some examples, the session identifier uniquely identifies a set of parameters, user and model configuration across a training phase.

[0223] In some examples, status information indicates whether a sufficient number of samples available for training, wherein samples corresponding to external User Equipment identifiers (UE IDs).FIGS. 16A-16B: Flow Charts of updating sample for Vertical Federated Learning (VFL) at a Network (NW)

[0224] FIGS. 16A-16B illustrates a flow charts of example methods of updating samples for a vertical federated learning (VFL) training procedure at a network (NW), according to some embodiments, according to some embodiments. The methods shown in FIGS. 16A- 16B may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0225] Referring to FIG. 16A, the method 1600 comprises sending a sample update request, as shown at block 1610 and receiving a sample update response, as shown at block 1620.Docket No. P69542WO1

[0226] In some examples, method 1600 further comprises receiving a data update identifying an internal User Equipment identifier (UE ID) of an affected UE.

[0227] In some examples, the data update includes a service specific authorization data notification.

[0228] In some examples, the data update includes a remove data request.

[0229] In some examples, wherein a remove data request includes a revoke user consent.

[0230] In some examples, a remove data request includes a remove data request due to revoking of user consent to participate in a training process.

[0231] Referring to FIG. 16B, the method 1650 comprises receiving a sample update request, as shown at block 1660 and sending a sample update response, as shown at block 1670.

[0232] The sample update request and the sample update response may be sent and / or received by various network functions, for example, as described above. Further, the sample update request and the sample update response may be sent and / or received by a VFL server or VFL client, as described above.

[0233] In some examples, a sample update request includes a session identifier, the internal UE IDs indicating the affected UE is to be removed from training.

[0234] In some examples, a sample update request includes internal UE IDs of UEs to be added to training.

[0235] In some examples, a sample update request includes re-training parameters.

[0236] In some examples, a sample update response includes the session identifier and indication if the update request was successful.

[0237] In some examples, a sample update response includes re-training parameters.

[0238] In some examples, re-training parameters indicate re-training from a starting point or re-training from a check-point.

[0239] In some examples, the sample update response further includes external UE IDs of UEs to be added to training.FIGS. 17A-17B: Flow Charts of model management for Vertical Federated Learning (VFL) at a Network (NW)

[0240] FIGS. 17A-17B illustrates a flow charts of example methods of model management for a vertical federated learning (VFL) at a network (NW), according to some embodiments, according to some embodiments. The methods shown in FIGS. 17A-17BDocket No. P69542WO1 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices. In various embodiments, some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.

[0241] Referring to FIG. 17A, the method 1700 comprises sending a model management request, as shown at block 1710 and receiving a sample model management, as shown at block 1720.

[0242] Referring to FIG. 17B, the method 1750 comprises receiving a model management request, as shown at block 1760 and sending a model management response, as shown at block 1770.

[0243] The model management request and the model management response may be sent and / or received by various network functions, for example, as described above. Further, the model management request and the model management response may be sent and / or received by a VFL server or VFL client, as described above.

[0244] In some examples, a model management request includes a session identifier uniquely identifying a set of parameters, user and model configuration across a training phase.

[0245] In some examples, a model management request includes VFL local model parameters.

[0246] In some examples, a model management request includes a VFL identifier.

[0247] In some examples, a model management request includes an identifier for a network data analytics function (NWDAF) chosen as a model repository.

[0248] In some examples, a model management response includes the session identifier.

[0249] In some examples, a model management response includes a status indicator indicating if VFL model parameters were successful configured.

[0250] In some examples, a model management response includes VFL local model parameters.

[0251] In some examples, a model management response includes a VFL identifier.

[0252] The present disclosure contemplates that, in some embodiments, data used by vertical federated learning (VFL) processes includes publicly available data. To protect user privacy, data may be anonymized, aggregated, and / or otherwise processed to remove or to the degree possible limit any individual identification. As discussed herein, entities that collect, share, and / or otherwise utilize such data should obtain user consent prior to and / orDocket No. P69542WO1 provide transparency when collecting such data. Furthermore, the present disclosure contemplates that the entities responsible for the use of data, including, but not limited to data used in association with vertical federated learning (VFL) processes, should attempt to comply with well-established privacy policies and / or privacy practices.

[0253] For example, such entities may implement and consistently follow policies and practices recognized as meeting or exceeding industry standards and regulatory requirements for developing and / or training vertical federated learning (VFL) processes. In doing so, attempts should be made to ensure all intellectual property rights and privacy considerations are maintained. Training should include practices safeguarding training data, such as personal information, through sufficient protections against misuse or exploitation. Such policies and practices should cover all stages of the vertical federated learning (VFL) processes development, training, and use, including data collection, data preparation, model training, model evaluation, model deployment, and ongoing monitoring and maintenance. Transparency and accountability should be maintained throughout. Such policies should be easily accessible by users and should be updated as the collection and / or use of data changes. User data should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection and sharing should occur through transparency with users and / or after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such data and ensuring that others with access to the data adhere to their privacy policies and procedures. Further, such entities should subject themselves to evaluation by third parties to certify, as appropriate for transparency purposes, their adherence to widely accepted privacy policies and practices. In addition, policies and / or practices should be adapted to the particular type of data being collected and / or accessed and tailored to a specific use case and applicable laws and standards, including jurisdiction-specific considerations.

[0254] In some embodiments, vertical federated learning (VFL) processes may utilize models that may be trained (e.g., supervised learning or unsupervised learning) using various training data, including data collected using a user device. Such use of user- collected data may be limited to operations on the user device. For example, the training of the model can be done locally on the user device so no part of the data is sent to another device. In other implementations, the training of the model can be performed using one or more other devices (e.g., server(s)) in addition to the user device but done in a privacy preserving manner, e.g., via multi-party computation as may be done cryptographically byDocket No. P69542WO1 secret sharing data or other means so that the user data is not leaked to the other devices.

[0255] In some embodiments, the trained model can be centrally stored on the user device or stored on multiple devices, e.g., as in federated learning. Such decentralized storage can similarly be done in a privacy preserving manner, e.g., via cryptographic operations where each piece of data is broken into shards such that no device alone (i.e., only collectively with another device(s)) or only the user device can reassemble or use the data. In this manner, a pattern of behavior of the user or the device may not be leaked, while taking advantage of increased computational resources of the other devices to train and execute the ML model. Accordingly, user-collected data can be protected. In some implementations, data from multiple devices can be combined in a privacy-preserving manner to train an ML model.

[0256] In some embodiments, the present disclosure contemplates that data used for vertical federated learning (VFL) processes may be kept strictly separated from platforms where the vertical federated learning (VFL) processes are deployed and / or used to interact with users and / or process data. In such embodiments, data used for offline training of the vertical federated learning (VFL) processes may be maintained in secured datastores with restricted access and / or not be retained beyond the duration necessary for training purposes. In some embodiments, the vertical federated learning (VFL) processes may utilize a local memory cache to store data temporarily during a user session. The local memory cache may be used to improve performance of the vertical federated learning (VFL) processes. However, to protect user privacy, data stored in the local memory cache may be erased after the user session is completed. Any temporary caches of data used for online learning or inference may be promptly erased after processing. All data collection, transfer, and / or storage should use industry-standard encryption and / or secure communication.

[0257] In some embodiments, as noted above, techniques such as federated learning, differential privacy, secure hardware components, homomorphic encryption, and / or multiparty computation among other techniques may be utilized to further protect personal information data during training and / or use of the vertical federated learning (VFL) processes. The vertical federated learning (VFL) processes should be monitored for changes in underlying data distribution such as concept drift or data skew that can degrade performance of the vertical federated learning (VFL) processes over time.

[0258] In some embodiments, the vertical federated learning (VFL) processes are trained using a combination of offline and online training. Offline training can use curated datasets to establish baseline model performance, while online training can allow theDocket No. P69542WO1 vertical federated learning (VFL) processes to continually adapt and / or improve. The present disclosure recognizes the importance of maintaining strict data governance practices throughout this process to ensure user privacy is protected.

[0259] In some embodiments, the vertical federated learning (VFL) processes may be designed with safeguards to maintain adherence to originally intended purposes, even as the vertical federated learning (VFL) processes adapt based on new data. Any significant changes in data collection and / or applications of vertical federated learning (VFL) process use may (and in some cases should) be transparently communicated to affected stakeholders and / or include obtaining user consent with respect to changes in how user data is collected and / or utilized.

[0260] Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively restrict and / or block the use of and / or access to data. That is, the present disclosure contemplates that hardware and / or software elements can be provided to prevent or block access to data. For example, in the case of some services, the present technology should be configured to allow users to select to “opt in” or “opt out” of participation in the collection of data during registration for services or anytime thereafter. In another example, the present technology should be configured to allow users to select not to provide certain data for training the vertical federated learning (VFL) processes and / or for use as input during the inference stage of such systems. In yet another example, the present technology should be configured to allow users to be able to select to limit the length of time data is maintained or entirely prohibit the use of their data for use by the vertical federated learning (VFL) processes. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user can be notified when their data is being input into the vertical federated learning (VFL) processes for training or inference purposes, and / or reminded when the vertical federated learning (VFL) processes generate outputs or make decisions based on their data.

[0261] The present disclosure recognizes vertical federated learning (VFL) processes should incorporate explicit restrictions and / or oversight to mitigate against risks that may be present even when such systems having been designed, developed, and / or operated according to industry best practices and standards. For example, outputs may be produced that could be considered erroneous, harmful, offensive, and / or biased; such outputs may not necessarily reflect the opinions or positions of the entities developing or deploying these systems. Furthermore, in some cases, references to or failures to cite third-party productsDocket No. P69542WO1 and / or services in the outputs should not be construed as endorsements or affiliations by the entities providing the vertical federated learning (VFL) processes. Generated content can be filtered for potentially inappropriate or dangerous material prior to being presented to users, while human oversight and / or ability to override or correct erroneous or undesirable outputs can be maintained as a failsafe.

[0262] The present disclosure further contemplates that users of the vertical federated learning (VFL) processes should refrain from using the services in any manner that infringes upon, misappropriates, or violates the rights of any party. Furthermore, the vertical federated learning (VFL) processes should not be used for any unlawful or illegal activity, nor to develop any application or use case that would commit or facilitate the commission of a crime, or other tortious, unlawful, or illegal act including misinformation, disinformation, misrepresentations (e.g., deepfakes), deception, impersonation, and propaganda. The vertical federated learning (VFL) processes should not violate, misappropriate, or infringe any copyrights, trademarks, rights of privacy and publicity, trade secrets, patents, or other proprietary or legal rights of any party, and appropriately attribute content as required. Further, the vertical federated learning (VFL) processes should not interfere with any security, digital signing, digital rights management, content protection, verification, or authentication mechanisms. The vertical federated learning (VFL) processes should not misrepresent machine-generated outputs as being human-generated.

[0263] Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.

[0264] In some embodiments, a non-transitory computer-readable memory medium may be configured so that it stores program instructions and / or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.

[0265] In some embodiments, a device (e.g., a UE 106) may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute theDocket No. P69542WO1 program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets). The device may be realized in any of various forms.

[0266] Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station, by interpreting each message / signal X received by the UE in the downlink as message / signal X transmitted by the base station, and each message / signal Y transmitted in the uplink by the UE as a message / signal Y received by the base station.

[0267] Although the embodiments above have been described in considerable detail, numerous variations and modifications will become apparent to those skilled in the art once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications.

Claims

Docket No. P69542WO1CLAIMSWhat is claimed is:1 . A method of initiating vertical federated learning (VFL) by a VFL server, the method comprising: sending a sample alignment request including a session identifier, external User Equipment identifiers (UE IDs) identifying UEs for training, and a machine learning (ML) model training configuration; and receiving a sample alignment response including the session identifier, status information, and external User Equipment identifiers (UE IDs) of additional UEs identified for training based on the session identifier and the ML model training configuration.

2. A method of aligning samples in vertical federated learning (VFL) by a VFL client, the method comprising: receiving a sample alignment request including a session identifier, external User Equipment identifiers (UE IDs) of UEs identified for training, and a machine learning (ML) model training configuration; identifying additional UEs for training; and sending a sample alignment response including the session identifier, status information, and external User Equipment identifiers (UE IDs) of the additional UEs identified for training based on the session identifier and the ML model training configuration.

3. A method of initiating vertical federated learning (VFL) by a VFL server, the method comprising: sending a sample alignment request including a session identifier, external, an area of interest filter, and a machine learning (ML) model training configuration; and receiving a sample alignment response including the session identifier, status information, and external User Equipment identifiers (UE IDs) of UEs identified for training based on the session identifier, the area of interest filter, and the ML model training configuration.

4. The method of claim any of claims 1 -3, wherein the session identifier uniquely identifies a set of parameters, user and model configuration across a training phase.Docket No. P69542WO15. The method of any of claims 1-4, wherein status information indicates whether a sufficient number of samples available for training, wherein samples corresponding to external User Equipment identifiers (UE IDs).

6. A method of sample alignment for vertical federated learning (VFL) initiated by a VFL server, the method comprising: identifying a sub-set of internal User Equipment identifiers (UE IDs) to perform VFL training with, based on one or more of the following factors: required prediction accuracy and similarity between a requested application Quality of Experience (QoE) and a supported application QoE; sending a sample alignment request including a session identifier, and a list of the sub-set of internal UE IDs; and receiving a sample alignment response including the session identifier, status information, and external UE IDs.

7. The method of claim 6, wherein the session identifier uniquely identifies a set of parameters, user and model configuration across a training phase.

8. The method of any of claims 6-7, wherein an application QoE is associated with a tolerance value.

9. The method of any of claims 6-8, wherein factors further include factors to attain diversity of samples in terms of location mobility, user types and subscriptions.

10. The method of any of claims 6-9, wherein status information indicates whether a sufficient number of samples available for training, wherein samples correspond UEs.

11. A method of updating samples in Vertical Federated Learning, the method comprising: receiving a data update identifying an internal User Equipment identifier (UE ID) of an affected UE; sending a sample update request including a session identifier, the internal UE IDs indicating the affected UE is to be removed from training; andDocket No. P69542WO1 receiving a sample update response including the session identifier and indication if the update request was successful.

12. The method of claim 11 , wherein the data update includes a service specific authorization data notification.

13. The method of claim 11 , wherein the data update includes a remove data request.

14. The method of claim 13, wherein a remove data request includes a revoke user consent.

15. The method of claim 13, wherein a remove data request includes a remove data request due to revoking of user consent to participate in a training process.

16. The method of any of claims 11 -15, wherein the sample update request further includes internal UE IDs of UEs to be added to training.

17. The method of any of claims 11 -16 wherein the sample update request further includes re-training parameters.

18. The method claim 17, wherein re-training parameters indicate re-training from a starting point or re-training from a check-point.

19. The method of any of claims 11 -13, wherein the sample update response further includes external UE IDs of UEs to be added to training.

20. The method of any of claims 11 -18, wherein the sample update response further includes re-training parameters.21 . The method claim 21 , wherein re-training parameters indicate re-training from a starting point or re-training from a check-point.

22. A method of updating samples in Vertical Federated Learning, the method comprising:Docket No. P69542WO1 receiving a sample update request including a session identifier, the external UE IDs indicating UEs is to be removed from training; and sending a sample update response including the session identifier and indication if the update request was successful.

23. The method of any of claims 22, wherein the sample update request further includes external UE IDs of UEs to be added to training.

24. The method of any of claims 22-23 wherein the sample update request further includes re-training parameters.

25. The method of any of claims 22-24, wherein the sample update response further includes external UE IDs of UEs to be added to training.

26. The method of any of claims 22-25 wherein the sample update response further includes re-training parameters.

27. A method of model management in Vertical Federated Learning (VFL), the method comprising: sending a model management request including a session identifier uniquely identifying a set of parameters, user and model configuration across a training phase; and receiving a model management response including the session identifier.

28. The method of claim 27, wherein the model management request further includes VFL local model parameters.

29. The method of claim 27, wherein the model management request further includes a VFL identifier.

30. The method of claim 29, wherein the model management request further includes an identifier for a network data analytics function (NWDAF) chosen as a model repository.31 . The method of any of claims 27-30, wherein the model management response further includes a status indicator indicating if VFL model parameters were successfulDocket No. P69542WO1 configured.

32. The method of any of claims 27-30, wherein the model management response further includes VFL local model parameters.

33. The method of any of claims 27-30, wherein the model management response further includes a VFL identifier.

34. A method of model management in Vertical Federated Learning (VFL), the method comprising: receiving a model management request including a session identifier uniquely identifying a set of parameters, user and model configuration across a training phase; and sending a model management response including the session identifier.

35. The method of claim 34, wherein the model management request further includes VFL local model parameters.

36. The method of claim 34, wherein the model management request further includes a VFL identifier.

37. The method of any of claims 34-36, wherein the model management request further includes an identifier for a network data analytics function (NWDAF) chosen as a model repository.

38. The method of any of claims 34-37, wherein the model management response further includes a status indicator indicating if VFL model parameters were successful configured.

39. The method of claims 34-37, wherein the model management response further includes VFL local model parameters.

40. The method of any of claims 34-37, wherein the model management response further includes a VFL identifier.Docket No. P69542WO141 . A device configured for communicating in a wireless communication network, comprising: one or more processors, coupled to a memory, configured to perform any of the methods of claims 1 -40.

42. The device of claim 41 , wherein the device includes a network entity.

43. The device of claim 41 , wherein device includes a device providing an application function.

44. The device of claim 41 , wherein device includes a device providing an network data analytics function (NWDAF).

45. A non-transitory computer program product, comprising computer instructions which, when executed by one or more processors, perform any of the methods of claims 1 -40.

Images