Control Plane Based Communication of Service Keys for Multimedia Broadcast / Multicast Services

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may register with a cellular network associated with a multicast / broadcast multimedia service (MBMS). The UE may transmit a request to join the MBMS to the cellular network. The UE may receive a response from the cellular network indicating an MBMS service key (MSK) and MSK identifier pair based at least in part on being registered with the cellular network. Numerous other aspects are described.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS)

[0001] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 262,781, entitled "CONTROL PLANE-BASED COMMUNICATION OF MULTIMEDIA BROADCAST / MULTICAST SERVICE SERVICE KEYS," filed on October 20, 2021, and to U.S. Nonprovisional Patent Application No. 17 / 653,022, entitled "CONTROL PLANE-BASED COMMUNICATION OF MULTIMEDIA BROADCAST / MULTICAST SERVICE SERVICE KEYS," filed on March 1, 2022, which are expressly incorporated by reference into this specification.

[0002] Aspects of the present disclosure generally relate to techniques and apparatus for wireless communications and control plane-based communication of service keys for multimedia broadcast / multicast services. [Background technology]

[0003]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, and broadcast. A typical wireless communication system may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is a set of extensions to the Universal Mobile Telecommunications System (Europe) (UMTS) mobile standard promulgated by the 3rd Generation Partnership Project (3GPP).

[0004]

[0004] A wireless network may include one or more base stations that support communication for a user equipment (UE) or multiple UEs. A UE may communicate with a base station via downlink and uplink communications. "Downlink" (or "DL") refers to the communication link from a base station to a UE, and "uplink" (or "UL") refers to the communication link from a UE to a base station.

[0005]

[0005] The above multiple access techniques have been adopted in various telecommunication standards to provide a common protocol that allows different UEs to communicate on a city, national, regional, and / or global scale. New Radio (NR), sometimes referred to as 5G, is a set of extensions to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, using Orthogonal Frequency Division Multiplexing (OFDM) with Cyclic Prefix (CP) (CP-OFDM) on the downlink and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Spread OFDM (DFT-s-OFDM)) on the uplink, and better integrating with other open standards that support beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation. As the demand for mobile broadband access continues to grow, further improvements in LTE, NR, and other radio access technologies will remain useful. Summary of the Invention

[0006]

[0006] Certain aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include registering with a cellular network associated with a multicast / broadcast service. The method may include transmitting a request to join a Multimedia Broadcast / Multicast Service (MBMS) to the cellular network. The method may include receiving a response from the cellular network indicating a pair of an MBMS service key (MSK) and an MSK identifier based at least in part on the registration with the cellular network.

[0007]

[0007] Certain aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving, from a UE, a request to join an MBMS over a cellular network. The method may include transmitting, to the UE, an MSK over a control plane of the cellular network based at least in part on the UE being registered with the cellular network.

[0008]

[0008] Some aspects described herein relate to a UE for wireless communication. The user equipment may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to register with a cellular network associated with a multicast / broadcast service. The one or more processors may be configured to send a request to join an MBMS to the cellular network. The one or more processors may be configured to receive a response from the cellular network indicating a pair of an MSK and an MSK identifier based at least in part on being registered with the cellular network.

[0009]

[0009] Some aspects described herein relate to a network entity for wireless communication. The network entity may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a request to join an MBMS from a UE via a cellular network. The one or more processors may be configured to transmit an MSK to the UE via a control plane of the cellular network based at least in part on the UE being registered with the cellular network.

[0010]

[0010] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to register with a cellular network associated with a multicast / broadcast service. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit a request to join an MBMS to the cellular network. The set of instructions, when executed by the one or more processors of the UE, may cause the UE to receive a response from the cellular network indicating an MSK and MSK identifier pair based at least in part on being registered with the cellular network.

[0011]

[0011] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive, from a UE, a request to join an MBMS over a cellular network. The set of instructions, when executed by the one or more processors of the network entity, may cause the network entity to transmit, over a control plane of the cellular network, an MSK to the UE based at least in part on the UE being registered with the cellular network.

[0012]

[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for registering with a cellular network associated with a multicast / broadcast service. The apparatus may include means for transmitting a request to join an MBMS to the cellular network. The apparatus may include means for receiving a response from the cellular network indicating the MSK and MSK identifier pair based at least in part on being registered with the cellular network.

[0013]

[0013] Certain aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a UE, a request to join an MBMS via a cellular network. The apparatus may include means for transmitting, based at least in part on the UE being registered with the cellular network, an MSK to the UE via a control plane of the cellular network.

[0014]

[0014] Aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, wireless communication devices, and / or processing systems as substantially fully described in this specification with reference to the drawings and this specification, and as illustrated in the drawings and this specification.

[0015]

[0015] The foregoing has outlined rather broadly the features and technical advantages of the embodiments according to the present disclosure in order that the following "Description of the Preferred Embodiments" may be better understood. Additional features and advantages are described hereinafter. The concepts and examples disclosed may be readily utilized as a basis for modifying or designing other structures for carrying out the same purposes of the present disclosure. Such equivalent structures do not depart from the scope of the appended claims. The nature of the concepts disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in conjunction with the accompanying figures. Each of the figures is provided for illustration and explanation, and not as a definition of the limits of the claims.

[0016]

[0016] Although aspects are described in this disclosure by illustrating some examples, those skilled in the art will understand that such aspects can be implemented in many different configurations and scenarios. The techniques described herein can be implemented using different platform types, devices, systems, shapes, sizes, and / or packaging configurations. For example, some aspects may be implemented via integrated chip embodiments or other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, and / or artificial intelligence-enabled devices). Aspects may be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components, and / or system-level components. Devices incorporating the described aspects and features may include additional components and features for the implementation and practice of the claimed and described aspects. For example, the transmission and reception of wireless signals may include one or more components for analog and digital applications (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and / or summers). It is contemplated that aspects described herein may be practiced in a wide variety of devices, components, systems, distributed configurations, and / or end user devices of various sizes, shapes, and configurations. [Brief description of the drawings]

[0017]

[0017] In order to be able to understand in detail the above-listed features of the present disclosure, a more detailed description of which has been briefly summarized above may be obtained by referring to the embodiments, some of which are shown in the attached drawings. However, it should be noted that the attached drawings show only some typical embodiments of the present disclosure, and therefore should not be considered as limiting its scope, since the present description may admit of other equally effective embodiments. The same reference numbers in different drawings may identify the same or similar elements. [Figure 1]

[0018] FIG. 1 illustrates an example of a wireless network in accordance with the present disclosure. [Diagram 2]

[0019] FIG. 1 illustrates an example of a base station in communication with user equipment (UE) in a wireless network in accordance with the present disclosure. [Diagram 3]

[0020] FIG. 2 illustrates an example of a Multimedia Broadcast / Multicast Service (MBMS) Service Key (MSK) distribution according to the present disclosure. [Figure 4]

[0021] FIG. 1 is a diagram illustrating an embodiment of a network architecture according to the present disclosure. [Diagram 5]

[0022] FIG. 1 illustrates an embodiment relating to MSK control plane based communication in accordance with the present disclosure. [Figure 6] FIG. 1 illustrates an embodiment relating to MSK control plane based communication in accordance with the present disclosure. [Figure 7]

[0023] FIG. 2 illustrates an example process associated with MSK control plane based communication in accordance with the present disclosure. [Figure 8] FIG. 2 illustrates an example process associated with MSK control plane based communication in accordance with the present disclosure. [Figure 9]

[0024] 1 is a diagram of an exemplary apparatus for wireless communication in accordance with the present disclosure. [Figure 10]

[0025] FIG. 2 is a diagram of exemplary components of a device according to the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018]

[0026] Various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure may be embodied in many different forms and should not be construed as limited to any specific structure or function presented throughout the present disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to encompass any aspect of the present disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the present disclosure. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. It should be understood that the scope of the present disclosure is intended to encompass such an apparatus or method that is implemented using other structure, functionality, or structure and functionality in addition to or other than the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0019]

[0027] Several aspects of a telecommunications system are now presented with reference to various devices and techniques, which are described in the detailed description that follows and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the particular application and design constraints imposed on the overall system.

[0020]

[0028] Although aspects may be described herein using terminology commonly associated with 5G or New Radio (NR) radio access technologies (RATs), aspects of the disclosure may apply to other RATs, such as 3G RATs, 4G RATs, and / or post-5G (e.g., 6G) RATs.

[0021]

[0029] 1 is a diagram illustrating an example of a wireless network 100 in accordance with the present disclosure. Wireless network 100 may be or include elements of a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples. Wireless network 100 may include one or more base stations 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other network entities. Base station 110 is an entity that communicates with UE 120. The base stations 110 (which may be referred to as Base Stations (BSs)) may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, and / or transmit / receive points (TRPs). Each base station 110 may provide communication coverage for a particular geographic area. In the 3rd Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​a base station 110 and / or a base station subsystem serving that coverage area, depending on the context in which the term is used.

[0022]

[0030] A base station 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a few kilometers in radius) but may allow unrestricted access by UEs 120 with a service subscription. A pico cell may cover a relatively small geographic area but may allow unrestricted access by UEs 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., the home) but may allow restricted access by UEs 120 that have an association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A base station 110 for a macro cell may be referred to as a macro base station. A base station 110 for a pico cell may be referred to as a pico base station. A base station 110 for a femto cell may be referred to as a femto base station or an in-home base station. 1, BS 110a may be a macro base station for a macro cell 102a, BS 110b may be a pico base station for a pico cell 102b, and BS 110c may be a femto base station for a femto cell 102c. A base station may support one or multiple (e.g., three) cells.

[0023]

[0031] In some embodiments, the cells may not necessarily be stationary and the geographic area of ​​the cells may move according to the location of the base stations 110 that are mobile (e.g., mobile base stations). In some embodiments, the base stations 110 may be interconnected to each other and / or to one or more other base stations 110 or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces, such as direct physical connections or virtual networks, using any suitable transport network.

[0024]

[0032] The wireless network 100 may include one or more relay stations. A relay station is an entity that may receive a data transmission from an upstream station (e.g., a base station 110 or a UE 120) and send the data transmission to a downstream station (e.g., a UE 120 or a base station 110). A relay station may be a UE 120 that may relay a transmission for another UE 120. In the embodiment shown in FIG. 1, a BS 110d (e.g., a relay base station) may communicate with a BS 110a (e.g., a macro base station) and a UE 120d to facilitate communication between the BS 110a and the UE 120d. A base station 110 that relays communication may be referred to as a relay station, a relay base station, a relay, etc.

[0025]

[0033] The wireless network 100 may be a heterogeneous network including different types of base stations 110, such as macro base stations, pico base stations, femto base stations, relay base stations, etc. These different types of base stations 110 may have different transmit power levels, different coverage areas, and / or different susceptibility to interference in the wireless network 100. For example, a macro base station may have a high transmit power level (e.g., 5-40 watts), while the pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0.1-2 watts).

[0026]

[0034] A network controller 130 may couple to or communicate with a set of base stations 110 and provide coordination and control for these base stations 110. The network controller 130 may communicate with the base stations 110 via backhaul communication links. The base stations 110 may communicate with each other directly or indirectly via wireless backhaul communication links or wired backhaul communication links.

[0027]

[0035] The UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be fixed or mobile. The UEs 120 may include, for example, an access terminal, a terminal, a mobile station, and / or a subscriber unit. The UEs 120 may be a cellular telephone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smart watch, a smart clothing, a smart glasses, a smart wristband, a smart jewelry (e.g., a smart ring or a smart bracelet)), an entertainment device (e.g., a music device, a video device, and / or a satellite radio), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing equipment, a global positioning system device, and / or any other suitable device configured to communicate over a wireless medium.

[0028]

[0036] Some UEs 120 may be considered as machine type communication (MTC) UEs or evolved or extended machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, and / or a location tag that may communicate with a base station, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as customer premises equipment. The UE 120 may be included within a housing that houses components of the UE 120, such as a processor component and / or a memory component. In some embodiments, the processor component and the memory component may be coupled to each other. For example, the processor component (e.g., one or more processors) and the memory component (e.g., a memory) may be operatively coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

[0029]

[0037] In general, any number of wireless networks 100 may be deployed in a given geographic area. Each wireless network 100 may support a particular RAT and may operate on one or more frequencies. The RAT may be referred to as a radio technology, an air interface, etc. The frequencies may be referred to as a carrier, a frequency channel, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR networks or 5G RAT networks may be deployed.

[0030]

[0038] In some embodiments, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly (e.g., without using base station 110 as an intermediary to communicate with each other) using one or more sidelink channels. For example, UEs 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (which may include, e.g., vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), and / or mesh networks. In such embodiments, UEs 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0031]

[0039] The devices of the wireless network 100 may communicate using an electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, etc. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified, designated frequency ranges FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). It should be understood that FR1 is often referred to (interchangeably) as a "sub-6 GHz" band in various documents and papers, although a portion of FR1 is higher than 6 GHz. A similar nomenclature issue may arise with respect to FR2, which is often referred to (interchangeably) as a "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as a "millimeter wave" band by the International Telecommunications Union (ITU).

[0032]

[0040] Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified operating bands for these mid-band frequencies as a frequency range designation FR3 (7.125 GHz to 24.25 GHz). Frequency bands that fall within FR3 may inherit FR1 and / or FR2 characteristics, and thus may in effect extend the characteristics of FR1 and / or FR2 to the mid-band frequencies. Additionally, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0033]

[0041] With the above examples in mind, it should be understood that unless otherwise specified, terms such as "sub-6 GHz" as used herein may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. Additionally, unless otherwise specified, it should be understood that terms such as "millimeter wave" as used herein may broadly refer to frequencies that may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, may include mid-band frequencies, or may be within the EHF band. The frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and it is contemplated that the techniques described herein are applicable to those modified frequency ranges.

[0034]

[0042] In some aspects, the UE 120 may include a communications manager 140. As described in more detail elsewhere herein, the communications manager 140 may register with a cellular network associated with a multimedia broadcast / multicast service (MBMS), send a request to the cellular network to join the MBMS, and receive a response from the cellular network indicating an MSK and MSK identifier pair based at least in part on being registered with the cellular network. The response may indicate one or more MSK and MSK identifier pairs. Different MSK and MSK identifier pairs may have different validity times. Additionally or alternatively, the communications manager 140 may perform one or more other operations described herein.

[0035]

[0043] In some aspects, the base station 110 may include a communications manager 150. As described in more detail elsewhere herein, the communications manager 150 may receive a request to join an MBMS from a UE, forward the request to join the MBMS service to a network entity, receive an MSK from the network entity, and transmit the MSK to the UE via a control plane of a cellular network associated with the base station based at least in part on the UE being registered with the cellular network. Additionally or alternatively, the communications manager 150 may perform one or more other operations described herein.

[0036]

[0044] In some aspects, the term "base station" (e.g., base station 110), cellular network device, "network node", or "network entity" may refer to an aggregated base station, a distributed base station (e.g., as described in connection with FIG. 9), an integrated access backhaul (IAB) node, a relay node, and / or one or more components thereof. For example, in some aspects, a "base station", "network node", or "network entity" may refer to a central unit (CU), a distributed unit (DU), a radio unit (RU), a near-real-time (Near-RT) RAN intelligent controller (RIC), or a non-real-time (Non-RT) RIC, or a combination thereof. In some aspects, the term "base station", "network node", or "network entity" may refer to one device configured to perform one or more functions, such as the functions described herein with respect to base station 110. In some aspects, the term "base station", "network node", or "network entity" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of several different devices (which may be located at the same geographic location or different geographic locations) may be configured to perform at least a portion of the functions or to replicate the performance of at least a portion of the functions, and the term "base station," "network node," or "network entity" may refer to any one or more of those different devices. In some aspects, the term "base station," "network node," or "network entity" may refer to one or more virtual base stations and / or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be embodied on a single device. In some aspects, the term "base station," "network node," or "network entity" may refer to one of the base station functions and not another base station function. In this manner, a single device may include two or more base stations.

[0037]

[0045] As noted above, Figure 1 is provided as an example. Other examples may differ from that described with respect to Figure 1.

[0038]

[0046] 2 illustrates an embodiment 200 of a base station 110 in communication with a UE 120 in a wireless network 100 in accordance with the present disclosure. The base station 110 may be equipped with a set of antennas 234a through 234t, such as T antennas, where T≧1. The UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas, where R≧1.

[0039]

[0047] At the base station 110, a transmit processor 220 may receive data destined for a UE 120 (or set of UEs 120) from a data source 212. The transmit processor 220 may select one or more modulation and coding schemes (MCSs) for the UE 120 based at least in part on one or more channel quality indicators (CQIs) received from the UE 120. The base station 110 may process (e.g., code and modulate) data for the UE 120 based at least in part on the MCS(es) selected for the UE 120 and provide data symbols to the UE 120. The transmit processor 220 may process system information (e.g., for semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, and / or higher layer signaling) and provide overhead symbols and control symbols. The transmit processor 220 may generate reference symbols for a reference signal (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and a synchronization signal (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set (e.g., T modems) of modems 232, denoted as modems 232a through 232t. For example, each output symbol stream may be provided to a modulator component (denoted as MOD) of modem 232. Each modem 232 may process a respective output symbol stream using a respective modulator component (e.g., for OFDM) to obtain an output sample stream. Each modem 232 may further process the output sample stream using a respective modulator component (e.g., convert to analog, amplify, filter, and / or upconvert the signal) to obtain a downlink signal.Modems 232a through 232t may transmit a set of downlink signals (eg, T downlink signals) via a corresponding set of antennas 234 (eg, T antennas) that are denoted as antennas 234a through 234t.

[0040]

[0048] At the UE 120, a set of antennas 252 (depicted as antennas 252a through 252r) may receive downlink signals from the base station 110 and / or other base stations 110 and may provide a set of received signals (e.g., R received signals) to a set of modems 254 (e.g., R modems) depicted as modems 254a through 254r. For example, each received signal may be provided to a demodulator component (depicted as DEMOD) of the modems 254. Each modem 254 may condition (e.g., filter, amplify, downconvert, and / or digitize) the received signal using a respective demodulator component to obtain input samples. Each modem 254 may further process the input samples using the demodulator component (e.g., for OFDM) to obtain received symbols. A MIMO detector 256 may obtain received symbols from the modems 254, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. The receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for the UE 120 to a data sink 260, and provide decoded control and system information to the controller / processor 280. The term "controller / processor" may refer to one or more controllers, one or more processors, or a combination thereof. The channel processor may determine a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, and / or a CQI parameter, among other examples. In some embodiments, one or more components of the UE 120 may be included within a housing 284.

[0041]

[0049] The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller 130 may include, for example, one or more devices in a core network. The network controller 130 may communicate with the base stations 110 via the communication unit 294.

[0042]

[0050] One or more antennas (e.g., antennas 234a-t and / or antennas 252a-r) may include or be contained within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, among other examples. An antenna panel, antenna group, set of antenna elements, and / or antenna array may include one or more antenna elements (in a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, and / or one or more antenna elements coupled to one or more transmitting and / or receiving components, such as one or more components of FIG.

[0043]

[0051] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI) from the controller / processor 280. The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110. In some embodiments, the modem 254 of the UE 120 may include a modulator and demodulator. In some embodiments, the UE 120 includes a transceiver. The transceiver may include any combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, and / or the TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figures 5-10).

[0044]

[0052] At the base station 110, uplink signals from the UE 120 and / or other UEs may be received by an antenna 234, processed by a modem 232 (e.g., a demodulator component of the modem 232, denoted as DEMOD), detected by a MIMO detector 236, if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The base station 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink and / or uplink communications. In some embodiments, the modem 232 of the base station 110 may include a modulator and a demodulator. In some embodiments, the base station 110 includes a transceiver. The transceiver may include any combination of antenna(s) 234, modem(s) 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the methods described herein (e.g., with reference to FIGS. 5-10).

[0045]

[0053] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) of FIG. 2 may implement one or more techniques associated with MSK control plane based communication, as described in more detail elsewhere herein. For example, the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or any other component(s) of FIG. 2 may perform or direct the operation of, for example, process 700 of FIG. 7, process 800 of FIG. 8, and / or other processes as described herein. The memory 242 and the memory 282 may store data and program codes for the base station 110 and the UE 120, respectively. In some embodiments, the memory 242 and / or the memory 282 may include a non-transitory computer-readable medium that stores one or more instructions (e.g., code and / or program code) for wireless communication. For example, the one or more instructions, when executed by one or more processors of the base station 110 and / or the UE 120 (e.g., directly or after being compiled, translated, and / or interpreted), may cause the one or more processors, the UE 120, and / or the base station 110 to perform or direct operations of, for example, process 700 of FIG. 7, process 800 of FIG. 8, and / or other processes as described herein. In some embodiments, executing the instructions may include executing the instructions, translating the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0046]

[0054] In some aspects, the UE includes means for registering with a cellular network associated with the MBMS, means for sending a request to join the MBMS to the cellular network, and / or means for receiving a response from the cellular network indicating the MSK and MSK identifier pair based at least in part on being registered with the cellular network. Means for causing the UE to perform operations described herein may include, for example, one or more of the communications manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0047]

[0055] In some aspects, the network entity includes means for receiving a request to join the MBMS from the UE over the cellular network and / or means for transmitting the MSK to the UE over a control plane of the cellular network based at least in part on the UE being registered with the cellular network. In some aspects, the means for the network entity to perform the operations described herein may include one or more of the components shown in FIG. 10, such as, for example, the processor 1020, the memory 1030, the input component 1040, the output component 1050, and / or a communication component, among other examples.

[0048]

[0056] 2 are shown as separate components, the functionality described above with respect to the blocks may be implemented in a single hardware, software, or combination component, or in various combinations of components. For example, functionality described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0049]

[0057] As noted above, Figure 2 is provided as an example. Other examples may differ from that described with respect to Figure 2.

[0050]

[0058] FIG. 3 gives an example 300 of network elements involved in MBMS from a security perspective. Nearly all security functions for MBMS, except for normal network bearer security, reside in either the Broadcast / Multicast Service Center (BM-SC) 315 or the UE 120. The UE may include an MBMS Key Generation and Verification Function / Storage (MGV-S / F) 305, configured to manage security keys for MBMS communications. A Bootstrapping Server Function (BSF) 310 is part of a Generic Bootstrapping Architecture (GBA). The UE 120 and the BM-SC 315 use the GBA to establish a shared key used to secure point-to-point communications between the UE 120 and the BM-SC 315. One or more of the functions described in connection with FIG. 3 include hardware and / or a combination of hardware and software. The hardware may be included in a server, a base station, and / or another network device.

[0051]

[0059] The BM-SC 315 is the source of MBMS data. Additionally or alternatively, the BM-SC 315 may be responsible for scheduling data for transmission and receiving data from third parties (e.g., content provider 345). The BM-SC 315 is responsible for establishing a shared secret with the UE 120 using the GBA, authenticating the UE 120 using the HyperText Transfer Protocol (HTTP) digest authentication mechanism, registering and deregistering the UE 120 for MBMS user services, generating and delivering to the UE 120 the keys required for MBMS security using the Multimedia Internet Keying (MIKEY) protocol, and applying appropriate protection to data transmitted as part of the MBMS user services. The BM-SC 315 also provides MBMS bearer authorization to UEs 120 attempting to establish MBMS bearers.

[0052]

[0060] The BM-SC 315 also verifies whether the UE 120 is authorized to register and receive keys for MBMS user services. In case of MBMS multicast mode, this authorization may be performed using the membership function 320 or may be associated with the BM-SC 315. In case of MBMS broadcast mode, this authorization may be performed without using the membership function 320, based at least in part on the fact that the membership function 320 is defined only in the context of the MBMS multicast mode.

[0053]

[0061] UE 120 may also be responsible for establishing a shared secret with BM-SC 315 using the GBA, registering with and deregistering from MBMS User Services, requesting and receiving keys for MBMS User Services from BM-SC 315, and using those keys to decrypt received MBMS data.

[0054]

[0062] The BM-SC 315 may include sub-functions related to MBMS security. For example, the BM-SC 315 may include a key management function 325. The key management function 325 includes two sub-functions: a key request function 330 and a key distribution function 335. The key request function 330 is responsible for retrieving the GBA key from the BSF, deriving the MBMS user key and / or the MBMS request key from the GBA key, performing the MBMS user service registration, deregistration, and MSK request procedures and associated user authentication using the MBMS request key (MRK), providing the MBMS user key (MUK) to the key distribution function 335, and / or performing authorization checks. The key request function 330 may perform the following functions and procedures: bootstrapping initiation, bootstrapping renegotiation, HTTP digest authentication, MRK derivation, MBMS user service registration procedure, MBMS user service deregistration procedure, and / or MSK request procedure, among other examples.

[0055]

[0063] The key distribution function 335 is responsible for retrieving the MUK from the key request function 330 and / or the registration function, and generating and distributing the MSK and MBMS traffic keys (e.g., distributing the MTK to the UE and / or providing the MTK to the session and transmission function 340, among other examples). The key distribution function 335 performs the following security procedures: the MSK distribution procedure, the MTK distribution procedure, and / or the BM-SC response pull procedure, among other examples.

[0056]

[0064] The Session and Send function 340 is responsible for the session and send functions. As part of these functions, the Session and Send function 340 performs the protection of data by the MTK (encryption and / or integrity protection). The Session and Send function 340 performs the following security procedures: protection of streaming data and / or protection of downloaded data.

[0057]

[0065] The membership function 320 is used to verify whether a user is allowed to register, receive a key, or establish an MBMS bearer for the MBMS multicast mode. The membership function may be defined only for the MBMS multicast mode.

[0058]

[0066] As noted above, Figure 3 is provided as an example. Other examples may differ from that described with respect to Figure 3.

[0059]

[0067] FIG. 4 is a diagram illustrating one embodiment of a network architecture 400 according to the present disclosure.

[0060]

[0068] The network architecture includes multiple functions and / or entities. One or more of the functions and / or entities described in connection with FIG. 4 include hardware and / or a combination of hardware and software. The hardware may be included in a server, a base station, and / or another network device.

[0061]

[0069] The Policy Control Function (PCF) performs functions to support Multicast and Broadcast Services (MBS) when Dynamic Policy and Control Charging (PCC) for MBS is required. For example, the PCF may provide policy information regarding MBS sessions to a Multicast / Broadcast Session Management Function (MB-SMF) to support QoS handling for MBS sessions and authorize associated QoS profiles, interact with a User Data Repository (UDR) for QoS information retrieval, and / or receive MBS information from an Application Function (AF), a Network Publication Function (NEF), or a Multicast / Broadcast Service Function (MBSF), for example, based at least in part on different configuration options.

[0062]

[0070] The MB-SMF also performs functions supporting MBS. For example, the MB-SMF may support MBS session management (including QoS control), configure the Multicast / Broadcast User Plane Function (MB-UPF) for multicast and broadcast flow forwarding based on policy rules for multicast and broadcast services from the PCF or local policy, and allocate and de-allocate Temporary Mobile Group Identities (TMGIs). Additionally or alternatively, the MB-SMF may interact with the RAN (via the Access and Mobility Management Function (AMF)) to control data forwarding using the 5GC shared MBS traffic delivery method for broadcast sessions. Additionally or alternatively, in the case of a multicast session, the MB-SMF may interact with a Session Management Function (SMF) to modify a Protocol Data Unit (PDU) session associated with the MBS session, among other examples, interact with the RAN (via the AMF and SMF) to establish data transmission resources between the MB-UPF node and the RAN node for the 5GC shared MBS traffic delivery method, and / or control multicast data forwarding using the 5GC dedicated MBS traffic delivery method.

[0063]

[0071] The SMF may also perform functions to support MBS. For example, the SMF may discover the MB-SMF for a multicast session, authorize multicast session join operations as necessary, interact with the MB-SMF to obtain and manage multicast session context, and / or interact with the RAN for shared data transmission resource establishment, among other examples. In some networks, the SMF and MB-SMF may be co-located or deployed separately.

[0064]

[0072] The MB-UPF may also perform functions supporting MBS. For example, the MB-UPF may, among other examples, conduct multicast and broadcast sessions, perform packet filtering of incoming downlink packets for multicast and broadcast flows, implement QoS (MFBR) and counting / reporting based on existing means, interact with the MB-SMF to receive multicast and broadcast data, and deliver multicast and broadcast data to RAN nodes for the 5GC shared MBS traffic delivery method. Additionally or alternatively, in case of multicast sessions, the MB-UPF may deliver multicast data to a user plane function (UPF) for the 5GC dedicated MBS traffic delivery method.

[0065]

[0073] The UPF may also perform functions supporting MBS. For example, the UPF may interact with the SMF to receive multicast data from the MB-UPF for the 5GC dedicated MBS traffic distribution method, and may distribute multicast data to the UE via a PDU session for the 5GC dedicated MBS traffic distribution method. The UPF and the MB-UPF may be co-located or deployed separately.

[0066]

[0074] The AMF may also perform functions supporting MBS, for example, the AMF may signal with the NG-RAN and the MB-SMF for MBS session management, may select an NG-RAN for multicast session activation notification to a UE in CM-IDLE state, may select an NG-RAN for broadcast traffic delivery, and / or the AMF may be aware of NG-RAN 5G MBS capabilities.

[0067]

[0075] The NG-RAN may also perform functions supporting MBS, such as managing MBS QoS flows over N2, delivering MBS data packets from 5GC shared for multiple UEs over the air using point-to-multipoint (PTM) or point-to-point (PTP), configuring UEs for MBS QoS flow reception at the access stratum (AS) layer, controlling per-UE switching between PTM and PTP delivery, supporting multicast session continuity during Xn and N2 handovers, and / or supporting over-the-air multicast session activation notification for UEs in CM-IDLE and CM-CONNECTED states in a radio resource control (RRC) inactive state, among other examples.

[0068]

[0076] The UE may also perform functions to support MBS. For example, the UE may receive multicast data using PTM / PTP, receive broadcast data using PTM, process incoming MBS QoS flows, support signaling to join and leave multicast MBS sessions, provide MBS resource management support at the AS layer, and / or receive notifications in CM-CONNECTED with CM-IDLE and RRC inactive states for multicast data transmission, among other examples.

[0069]

[0077] The AF may also perform functions to support MBS, for example, the AF may request multicast or broadcast services from the 5GC by providing service information, including QoS requirements, to the 5GC, command MBS session operations towards the 5GC as needed, and / or interact with the NEF for MBS-related service publication, among other examples.

[0070]

[0078] The NEF may also perform functions supporting MBS. For example, the NEF may provide an interface to the AF for MBS procedures including service provisioning, MBS session, and QoS management, interact with the AF and NFs in 5GC (e.g., MB-SMF for MBS session operation), determine forwarding parameters, and / or select the MB-SMF to serve the MBS session.

[0071]

[0079] The MBSF may also perform functions supporting the MBS. For example, the MBSF may provide service level functions to support the MBS, interwork with the LTE MBMS, interact with the AF and the MB-SMF for MBS session operation, determine forwarding parameters, determine session forwarding, select an MB-SMF to service the MBS session, control a Multicast / Broadcast Service Forwarding Function (MBSTF) if one is used, and / or determine a sender Internet Protocol (IP) multicast address for the MBS session if an IP multicast address is sourced by the MBSTF, among other examples. In some networks, MBSF functions related to services and MBS data processing (e.g., encoding) should be determined using SA WG4.

[0072]

[0080] The MBSTF may also perform functions that support the MBS. For example, the MBSTF may provide a media anchor for MBS data traffic as needed, source IP multicast as needed, provide general packet forwarding functions available to any IP multicast capable application, such as framing, multiple flows, packet FEC (encoding), and / or provide multicast / broadcast delivery of input files as objects or object flows, among other examples. In some networks, MBSTF functions related to MBS data processing (e.g., encoding) are to be determined using SA WG4.

[0073]

[0081] The UDM may also perform functions to support MBS, for example, the UDM may support management of subscriptions for authorization for multicast MBS sessions.

[0074]

[0082] The UDR may also perform functions that support MBS, such as supporting management of UE authorization information for multicast MBS sessions and / or supporting management of policy information for multicast or broadcast MBS sessions, among other examples.

[0075]

[0083] The NRF may also perform functions to support MBS. For example, the NRF may support new NF types MB-SMF and MBSF and corresponding NF profiles, and may support MB-SMF discovery based on parameters such as DNN, S-NSSAI, and MB service area at MBS session creation (e.g., for multicast and / or broadcast MBS sessions), and / or MB-SMF discovery based on MBS session identifier (ID) at UE joining by the SMF serving the multicast session at UE joining (e.g., for multicast MBS sessions), among other examples.

[0076]

[0084] The NF profile in the NRF, in the case of a MB-SMF, may include the MBS Session ID(s), Area Session ID(s), and, if available, the corresponding MBS Service Area(s).

[0077]

[0085] The 5G system architecture for MBS reuses existing reference points N1, N2, N4, N10, N11, N30, and N33, with extensions to support MBS.

[0078]

[0086] As noted above, Figure 4 is provided as an example. Other examples may differ from that described with respect to Figure 4.

[0079]

[0087] In some networks, a UE attempting to receive an MBMS may receive one or more keys from the MB-SC using broadcast or multicast communication on the user plane as described herein. For example, the UE may receive the MSK via PTP communication and then the MTK via PTM communication. The UE may use the MUK to decrypt the MSK and then the MSK to decrypt the MTK. While the use of these keys provides security and reduces unauthorized access to the MBMS data, a UE attempting to establish an MBMS may observe latency and consume computing resources used for decrypting and / or generating different keys based at least in part on the timing of receipt of the MTK and MSK.

[0080]

[0088] In some aspects described herein, the MBSF may derive and / or generate the MSK and deliver the MSK to the UE using control plane based communication. For example, the MBSF may transmit the MSK to the UE via one or more cellular network devices, or may transmit the MSK to one or more network entities, such as a BM-SC or an MBSTF (e.g., which may coexist with the BM-SC and / or have a subset of the BM-SC functionality). In this manner, the UE may receive the MSK with reduced latency and / or the MSK may not be encrypted with a MUK or other key, based at least in part on a reliance on security already established on the control plane. In this manner, the UE may improve latency and / or reduce consumption of computing resources to establish a secure connection for receiving MBMS.

[0081]

[0089] In some aspects, the MBSTF includes a key distribution function and a session and transmission function of the BM-SC. The MSK generation at the MB-SC may be replaced with a key provided by the MBSF. Additionally or alternatively, a procedure for the BM-SC to generate and provide the MSK may not be required. In some aspects, the UE receives the MSK during the MBS Session Join procedure, for example, using a Non-Access Stratum (NAS) message.

[0082]

[0090] In some aspects, MTK distribution and MBS traffic processing may be provided via the MB-SC, as described in connection with Figure 3. Alternatively, the MTK may be transmitted to the UE together with the MSK via the control plane. This may enable the UE to process the MBS traffic as soon as it joins the MBMS, instead of waiting to receive the MTK sent in a PTM (or multicast / broadcast) message and protected using the MSK.

[0083]

[0091] In some aspects, the MTK is provided to the MBSF when a new MTK is generated by the MBSTF. Additionally or alternatively, the MBSF may generate the MTK and provide the MTK to the MBSTF. In some aspects, the MTK generation may be periodic or may be triggered (requested) by the MBSTF. In some aspects, the MTK change may be indicated to the UE via the NAS so that the UE may request an updated MTK. In some aspects, the UE may request the MTK using a NAS procedure (e.g., a new key request or an existing PDU session modification procedure). In some aspects, the MB-SMF may push the MTK to the UEs participating in the MBS session with an indication.

[0084]

[0092] FIG. 5 illustrates an example 500 related to MSK control plane based communication in accordance with the present disclosure. As illustrated in FIG. 5, a UE (e.g., UE 120) may communicate with one or more cellular network devices (e.g., base station 110, AMF, SMF, MB-SMF, among other examples) and / or one or more network entities. In some aspects, the one or more cellular network devices and the UE may be part of a wireless network (e.g., wireless network 100). The UE and the one or more cellular network devices may have established a wireless connection prior to the operations illustrated in FIG. 5.

[0085]

[0093] The UE may register with a cellular network provided by one or more cellular network devices, as indicated by reference numeral 505. In some aspects, the cellular network is associated with MBMS.

[0086]

[0094] As indicated by reference numeral 510, the UE may transmit a request to join the MBMS after registering with the cellular network. In some aspects, the UE may transmit the request to join the MBMS via a control plane signaling message (e.g., control plane communication). In some aspects, the UE control plane signaling message may include an uplink NAS message. In some aspects, the UE may transmit the request to join the MBMS based at least in part on an advertisement received via the cellular network and / or via one or more network entities.

[0087]

[0095] As indicated by reference numeral 515, one or more network entities may receive a request to join the UE initiated MBMS, and one or more cellular network devices may send a request to join the UE initiated MBMS.

[0088]

[0096] One or more network entities may generate the MSK and / or the MTK, as indicated by reference numeral 520. In some aspects, the MBSF generates the MSK and / or the MTK. For example, the MBSF may generate both the MSK and the MTK, or the MBSF may generate the MSK and receive the MTK from an additional network entity (e.g., the MB-SC and / or the MBSTF).

[0089]

[0097] In some aspects, one or more entities (e.g., the MBSF) may generate the MSK based at least in part on multicast / broadcast membership changes, periodicity for updating the MSK, and / or detection of a security event related to the MSK (e.g., a determination that the MSK has been compromised), among other examples.

[0090]

[0098] A first network entity of the one or more network entities may transmit, and a second network entity of the one or more network entities may receive, an indication of the MSK, an MSK identifier (ID), an MTK, and / or an MTK identifier, as indicated by reference numeral 525. The MSK and the MSK identifier may form an MSK-MSK identifier pair. For example, the MSK may be associated with a unique MSK identifier provided with the MSK.

[0091]

[0099] In some aspects, the first network entity may transmit (e.g., simultaneously and / or in the same message) an indication of multiple MSKs. In some aspects, the first MSK may be valid for a first period of time and the second MSK may be valid for a second period of time. In some aspects, the first MSK may be used to encrypt the second MSK and / or the third MSK, among other examples. In some aspects, the first MSK may be valid for a first service and the second MSK may be valid for a second service.

[0092]

[0100] In some aspects, the MTK may be associated with an MTK identifier (e.g., as an MTK-MTK identifier pair) to indicate that the MTK may be used with the MSK. For example, the MTK identifier may match the MSK identifier of the MSK or may otherwise indicate compatibility of the MTK and the MSK.

[0093]

[0101] In some aspects, the MBSF may generate the MSK and provide the MSK to the BM-SC, the MBSTF, and / or the key distribution entity, among other examples. In some aspects, the MBSF may also generate the MTK and provide the MTK to the MBSTF. Alternatively, the MBSTF may generate the MTK based at least in part on the MSK and provide the MTK to the MBSF.

[0094]

[0102] As indicated by reference numeral 530, the one or more network entities may transmit an indication of the MSK, the MSK identifier, the MTK, and / or the MTK identifier to one or more cellular network devices.

[0095]

[0103] In some aspects, one or more network entities may transmit (e.g., simultaneously and / or in the same message) an indication of multiple MSKs. In some aspects, a first MSK may be valid for a first period of time and a second MSK may be valid for a second period of time. In some aspects, the first MSK may be used to encrypt a second MSK and / or a third MSK, among other examples. In some aspects, the first MSK may be valid for a first service and the second MSK may be valid for a second service.

[0096]

[0104] The UE may receive, and the one or more cellular network devices may transmit, an indication of the MSK, MSK identifier, MTK, and / or MTK identifier, as indicated by reference numeral 535. In some aspects, the UE may receive the indication of the MSK, MSK identifier, MTK, and / or MTK identifier via a response from the cellular network based at least in part on the UE being registered with the cellular network. For example, the one or more cellular network devices may rely on control plane security to provide the indication of the MSK, MSK identifier, MTK, and / or MTK identifier.

[0097]

[0105] In some aspects, the UE may receive, or one or more cellular network devices may transmit, an indication of the MSK and / or an MSK identifier in a separate transmission from the indication of the MTK and / or the MTK identifier. In some aspects, the UE may receive a first MTK along with the MSK and may receive a second MTK (e.g., via the control plane or user plane) after receiving the MSK. For an MTK received via the user plane, the MTK may be encrypted using the MSK.

[0098]

[0106] In some aspects, the UE may receive the MSK via a control plane (e.g., a control plane signaling message) of the cellular network based at least in part on a transmission from a network entity (e.g., an MBSF) to one or more of the cellular network devices. In some aspects, the control plane signaling message includes a downlink NAS message.

[0099]

[0107] In some aspects, the one or more network devices may include a multicast / broadcast session management function, a session management function, and / or an access and mobility management function, among other examples. For example, the UE may receive the MSK from the MBSF via a control plane of the cellular network based at least in part on receiving the MSK via the multicast / broadcast session management function, the session management function, and / or the access and mobility management function.

[0100]

[0108] In some aspects, the response may include an indication of the validity of the MSK, an MTK associated with the MSK, an MTK identifier associated with the MTK, and / or an indication of the validity of the MTK. In some aspects, the response may indicate that the MSK is used to protect (e.g., encrypt) multiple MTKs, where the multiple MTKs are used at different time intervals.

[0101]

[0109] In an example application embodiment of an MSK and multiple associated MTKs, the MSK may be indicated as valid for one day, and the MTK may be indicated or configured as valid for one hour. First, the MSK is used to protect MTK1 broadcasted over the user plane. At a second time, the MSK is used to protect MTK2, and at a third time, the MSK is used to protect MTK3. In the described control plane based indication, when the UE receives the MSK from the network, the UE may also receive the current (e.g., currently valid) MTK along with the MSK. For example, when the UE joins an MBMS service between t2 and t3, the UE may receive the MSK and MTK2 over the control plane.

[0102]

[0110] In some aspects, the UE may receive the MSK via the control plane and may receive the MTK via PTP communication from one or more network entities.

[0103]

[0111] In some aspects, the US may receive (e.g., simultaneously and / or in the same message) an indication of multiple MSKs. In some aspects, the first MSK may be valid for a first time period and the second MSK may be valid for a second time period. In some aspects, the first MSK may be used to encrypt the second MSK and / or the third MSK, among other examples. In some aspects, the first MSK may be valid for a first service and the second MSK may be valid for a second service. In some aspects, the UE may receive (e.g., in the same message) an indication of how to use multiple MSKs (e.g., as described herein).

[0104]

[0112] The UE may decrypt the MTK using the MSK, as indicated by reference numeral 540. In some aspects, the UE may decrypt the MTK using the MSK based at least in part on receiving the MSK via the control plane and receiving the MTK via the user plane. In some aspects, the MTK may be encrypted using the MSK based at least in part on the MTK being sent to the UE via the user plane.

[0105]

[0113] As indicated by reference numeral 545, the UE may receive the MBMS data, and one or more network entities may transmit the MBMS data, via one or more PTM communications.

[0106]

[0114] As indicated by reference numeral 550, the UE may decode the MBMS data based at least in part on the MTK.

[0107]

[0115] As indicated by reference numeral 555, a first network entity of the one or more network entities may transmit an indication of an update to the MSK, an MSK identifier, an MTK, and / or an MSK identifier, which may be received by a second network entity of the one or more network entities. In some aspects, the first network entity (e.g., MBSF) may generate an updated MTK and provide the updated MTK to a second network entity (MBSTF or BM-SC) and a UE (UE using a control plane). In some aspects, the first network entity (e.g., MBSF) may receive an updated MTK generated by the second network entity (MBSTF or BM-SC) and transmit the updated MTK to the UE (UE using a control plane). In some aspects, the first network entity may use the updated MTK and / or the associated MTK identifier to verify the validity of the active MSK.

[0108]

[0116] In some aspects, the first network entity may transmit the MTK based at least in part on receiving a request for the MTK, or a periodicity for updating the MTK, from the second network entity.

[0109]

[0117] As indicated by reference numeral 560, the UE may transmit a request for an updated MTK, and one or more cellular network devices may receive the request for the updated MTK. In some aspects, the UE may transmit the request for an updated MTK based at least in part on receiving an indication that the MTK has been updated (e.g., in an updated MTK message). In some aspects, the UE may transmit the request via the control plane. In some aspects, the UE may receive a response from one or more network entities (e.g., MBSF) via one or more cellular network devices. In some aspects, the UE response may indicate the updated MTK, for example, based at least in part on the UE failing to receive an updated MTK via PTP or PTM communication from one or more network entities (e.g., MBSTF or BM-SC).

[0110]

[0118] One or more network entities may transmit, and the UE may receive, an indication of the updated MTK and / or MTK identifier, as indicated by reference numeral 565. In some aspects, the UE may receive the updated MTK message via a PTM communication.

[0111]

[0119] In some aspects, the first network entity may transmit the updated MTK based at least in part on receiving an indication to update the MTK from the second network entity.

[0112]

[0120] Additionally or alternatively, the one or more network entities may transmit an updated MSK to the UE. For example, the one or more network entities may transmit the updated MSK based at least in part on receiving an indication to update the MSK from another of the one or more network entities.

[0113]

[0121] Based at least in part on the UE receiving the MSK and / or MTK via control plane communications, the UE may receive the MSK with reduced latency and / or the MSK may not be encrypted with the MUK or other keys based at least in part on reliance on security already established on the control plane. In this manner, the UE may improve latency and / or reduce consumption of computing resources to establish a secure connection for receiving MBMS.

[0114]

[0122] As noted above, Figure 5 is provided as an example. Other examples may differ from those described with respect to Figure 5.

[0115]

[0123] FIG. 6 is a diagram illustrating an example 600 related to MSK control plane based communication according to the present disclosure. As shown in FIG. 6, the UE 120 may communicate with one or more cellular network devices 610 (e.g., base station 110, AMF, SMF, MB-SMF, among other examples), a network entity 615 (e.g., MBSF), and additional network entities 620 (e.g., MBSTF and / or BM-SC). In some aspects, the one or more cellular network devices 610 and the UE may be part of a wireless network (e.g., wireless network 100). The UE and the one or more cellular network devices may have established a wireless connection prior to the operations illustrated in FIG. 6.

[0116]

[0124] As shown in Figure 6, in contrast to Figure 3, the UE may receive the MSK and / or MTK from a network entity 615 via one or more cellular network devices 610. As shown, the MBSF may transmit the MSK to the UE via one or more cellular network devices 610 and may transmit the MSK to additional network entities 620, a key management function 625, and / or a key distribution function 630. The UE may manage and / or verify keys, such as the MSK and / or MTK, using an MBMS key generation and verification function / storage mechanism (MGV-S / F) 605.

[0117]

[0125] In some aspects, the additional network entity 620, the key management function 625, and / or the key distribution function 630 may use the MSK to generate an MTK. The additional network entity 620, the key management function 625, and / or the key distribution function 630 may transmit the MTK to the UE (e.g., along with an MTK identifier for validation of the MSK) over the user plane and / or provide the MTK to the network entity 615 (e.g., along with an MSK identifier for validation of the MSK) to verify the validity of the MSK. In some aspects, the network entity 615 may transmit the MSK to the additional network entity 620 and / or update the MSK if the MTK verifies the invalidity of the MSK.

[0118]

[0126] In some aspects, the network entity 615 may generate an MTK and may provide the MTK to be used to encode data associated with the network entity 615 to additional network entities 620, a key management function 625, and / or a key distribution function 630. The network entity 615 may also provide the MTK to the UE via one or more cellular network devices 610.

[0119]

[0127] In some aspects, the MBSF may transmit a first MTK (e.g., the current MTK if the UE 120 joins MBMS) via the control plane, and the BM-SC 620 may transmit a second MTK via the user plane (e.g., using PTM communication).

[0120]

[0128] The additional network entity 620 may encrypt data received from the content provider 640 using the MTK in a session and transmission function 635. The additional network entity 620 may transmit the traffic to the UE 120 as encrypted data for decryption at the UE 120 using the MTK.

[0121]

[0129] As noted above, Figure 6 is provided as an example. Other examples may differ from that described with respect to Figure 6.

[0122]

[0130] 7 illustrates an example process 700, implemented, for example, by a UE, in accordance with the present disclosure. The example process 700 is an example implementation in which a UE (e.g., UE 120) performs operations related to MSK control plane based communications.

[0123]

[0131] 7, in some aspects, process 700 may include registering with a cellular network associated with the MBMS and sending a request to join the MBMS to the cellular network (block 710). For example, the UE may register with the cellular network associated with the MBMS (e.g., using the communications manager 140 and / or communications manager 908 shown in FIG. 9) sending a request to the cellular network to join the MBMS, as described above.

[0124]

[0132] 7, in some aspects, the process 700 may include transmitting a request to join the MBMS to the cellular network (block 720). For example, the UE may transmit (e.g., using the communications manager 140 and / or the transmitting component 904 shown in FIG. 9) a request to join the MBMS to the cellular network, as described above.

[0125]

[0133] 7, in some aspects, the process 700 may include receiving a response from the cellular network indicating the pair of MSK and MSK identifier based at least in part on being registered with the cellular network (block 720). For example, the UE (e.g., using the communications manager 140 and / or receiving component 902 shown in FIG. 9) may receive a response from the cellular network indicating the pair of MSK and MSK identifier based at least in part on being registered with the cellular network, as described above.

[0126]

[0134] Process 700 may include additional aspects, such as any single aspect or any combination of aspects, described below and / or with respect to one or more other processes described elsewhere herein.

[0127]

[0135] In a first aspect, the response includes one or more of an indication of validity of the MSK, an MTK associated with the MSK, an MTK identifier associated with the MTK, or an indication of validity of the MTK.

[0128]

[0136] In a second aspect, alone or in combination with the first aspect, receiving the MTK message includes one or more of receiving the MTK message via a control plane of a cellular network or receiving the MTK message via point-to-multipoint communication.

[0129]

[0137] In a third aspect, alone or in combination with one or more of the first and second aspects, the process 700 includes receiving an updated MTK message via point-to-multipoint communication after receiving an MTK message via a control plane of the cellular network.

[0130]

[0138] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the MTK is encrypted at least in part based on the MSK.

[0131]

[0139] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the process 700 includes decrypting the MTK based at least in part on the MSK.

[0132]

[0140] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the process 700 includes receiving MBMS data via point-to-multipoint communication and decoding the MBMS data based at least in part on the MTK.

[0133]

[0141] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the process 700 includes receiving an indication of an update to the MTK via point-to-multipoint communication.

[0134]

[0142] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the process 700 includes receiving an indication of an update to the MTK and sending a request for an updated MTK to the cellular network based at least in part on receiving the updated MTK via a control plane of the cellular network.

[0135]

[0143] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, receiving the response includes receiving the response via a control plane of the cellular network and via one or more of a multicast / broadcast session management function, a session management function, or an access and mobility management function.

[0136]

[0144] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, transmitting a request to join the MBMS comprises transmitting the request to join the MBMS via a control plane signaling message.

[0137]

[0145] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the control plane signaling message comprises an uplink NAS message.

[0138]

[0146] In a twelfth aspect, alone or in combination with one or more of the first aspect to the eleventh aspect, receiving the response includes receiving the response via a control plane signaling message.

[0139]

[0147] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the control plane signaling message comprises a downlink NAS message.

[0140]

[0148] 7 illustrates example blocks of process 700, in some aspects process 700 may include additional blocks, fewer blocks, different blocks, or blocks configured differently than those illustrated in FIG 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0141]

[0149] 8 illustrates an example process 800 implemented, for example, by a network entity, in accordance with the present disclosure. The example process 800 is an example of a network entity (e.g., device 1000) performing operations associated with control plane-based communication of MSK.

[0142]

[0150] 8, in some aspects, process 800 may include receiving a request to join the MBMS over a cellular network from a UE (block 810). For example, a network entity (e.g., using the communications component 1060 shown in FIG. 10) may receive a request to join the MBMS over a cellular network from the UE, as described above.

[0143]

[0151] 8, in some aspects, process 800 may include transmitting the MSK to the UE over a control plane of the cellular network based at least in part on the UE being registered with the cellular network (block 820). For example, the network entity (e.g., using communication component 1060) may transmit the MSK to the UE over a control plane of the cellular network based at least in part on the UE being registered with the cellular network, as described above.

[0144]

[0152] Process 800 may include additional aspects, such as any single aspect or any combination of aspects, described below and / or with respect to one or more other processes described elsewhere herein.

[0145]

[0153] In a first aspect, the process 800 includes generating the MSK prior to transmitting the MSK.

[0146]

[0154] In a second aspect, alone or in combination with the first aspect, generating the MSK prior to transmitting the MSK includes generating the MSK based at least in part on one or more of a multicast / broadcast membership change, a periodicity for updating the MSK, and detecting a security event associated with the MSK.

[0147]

[0155] In a third aspect, alone or in combination with one or more of the first and second aspects, the network entity includes an MBSF.

[0148]

[0156] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the process 800 includes receiving an MTK associated with the MSK from an additional network entity.

[0149]

[0157] In a fifth aspect, either alone or in combination with one or more of the first through fourth aspects, the process 800 includes transmitting the MTK to an additional network entity.

[0150]

[0158] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, transmitting the MTK to the additional network entity includes transmitting the MTK to the additional network entity based at least in part on one or more of a request for the MTK or periodicity receiving for updating the MTK from the additional network entity.

[0151]

[0159] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the process 800 includes generating the MTK prior to transmitting the MTK.

[0152]

[0160] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the additional network entity includes one or more of a BM-SC, an MBSTF, or a key distribution entity.

[0153]

[0161] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the process 800 includes transmitting an MTK message to the UE via a control plane of the cellular network.

[0154]

[0162] In a tenth aspect, either alone or in combination with one or more of the first to ninth aspects, the MTK is encrypted at least in part based on the MSK.

[0155]

[0163] In an eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the process 800 includes receiving an updated MTK from an additional network entity, transmitting the updated MTK to the UE via a control plane of the cellular network, or a combination thereof.

[0156]

[0164] In a twelfth aspect, either alone or in combination with one or more of the first through eleventh aspects, the process 800 includes transmitting the updated MTK to an additional network entity.

[0157]

[0165] In a thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the process 800 includes transmitting the updated MTK to the UE via a control plane of the cellular network.

[0158]

[0166] In a fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, transmitting the updated MTK via a control plane of the cellular network includes transmitting the updated MTK based at least in part on receiving a request from the UE or transmitting the updated MTK to the UE based at least in part on the UE joining the MBMS.

[0159]

[0167] In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the process 800 includes receiving an indication to update the MSK from an additional network entity and transmitting the updated MSK to the additional network entity.

[0160]

[0168] In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the process 800 includes transmitting the updated MSK to the UE.

[0161]

[0169] In a seventeenth aspect, alone or in combination with one or more of the first to sixteenth aspects, transmitting the MSK to the UE via a control plane of the cellular network includes transmitting the MSK via one or more of a multicast / broadcast session management function, a session management function, or an access and mobility management function.

[0162]

[0170] 8 illustrates example blocks of process 800, in some aspects process 800 may include additional, fewer, different, or differently arranged blocks compared to the blocks illustrated in FIG 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0163]

[0171] 9 is a diagram of an example apparatus 900 for wireless communication. The apparatus 900 may be a UE, or a UE may include the apparatus 900. In some aspects, the apparatus 900 includes a receiving component 902 and a transmitting component 904, which may be in communication with one another (e.g., via one or more buses and / or one or more other components). As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using the receiving component 902 and the transmitting component 904. As further shown, the apparatus 900 may include a communications manager 908 (e.g., the communications manager 140).

[0164]

[0172] In some aspects, the apparatus 900 may be configured to perform one or more operations described herein with respect to Figures 5 and 6. Additionally or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as process 700 of Figure 7. In some aspects, the apparatus 900 and / or one or more components shown in Figure 9 may include one or more components of a UE described in connection with Figure 2. Additionally or alternatively, one or more components shown in Figure 9 may be implemented within one or more components described in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by a controller or processor to perform the function or operation of the component.

[0165]

[0173] The receiving component 902 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 906. The receiving component 902 may provide the received communications to one or more other components of the device 900. In some aspects, the receiving component 902 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, among other examples) on the received communications and provide the processed signals to one or more other components of the device 900. In some aspects, the receiving component 902 may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller / processor, a memory, or a combination thereof of a UE as described in connection with FIG. 2.

[0166]

[0174] The transmitting component 904 may transmit a communication, such as a reference signal, control information, a data communication, or a combination thereof, to the device 906. In some aspects, one or more other components of the device 900 may generate a communication and provide the generated communication to the transmitting component 904 for transmission to the device 906. In some aspects, the transmitting component 904 may perform signal processing (such as filtering, amplifying, modulating, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) on the generated communication and may transmit the processed signal to the device 906. In some aspects, the transmitting component 904 may include one or more antennas, a modem, a modulator, a transmit MIMO processor, a transmit processor, a controller / processor, a memory, or a combination thereof, of a UE as described in connection with FIG. 2. In some aspects, the transmitting component 904 may be collocated with the receiving component 902 in a transceiver.

[0167]

[0175] The communications manager 908 may register with a cellular network associated with the MBMS. The transmitting component 904 may transmit a request to join the MBMS to the cellular network. The receiving component 902 may receive a response from the cellular network indicating an MBMS service key (MSK) and MSK identifier pair based at least in part on being registered with the cellular network.

[0168]

[0176] The receiving component 902 may receive an updated response via point-to-multipoint communication after receiving the response via the control plane of the cellular network.

[0169]

[0177] The communications manager 908 and / or the receiving component 902 may decrypt the MBMS traffic keys based at least in part on the MSK.

[0170]

[0178] The receiving component 902 may receive MBMS data via point-to-multipoint communication.

[0171]

[0179] The communications manager 908 and / or the receiving component 902 may decrypt the MBMS data based at least in part on the MBMS traffic key.

[0172]

[0180] The receiving component 902 may receive an indication of an update to an MBMS traffic key via point-to-multipoint communication.

[0173]

[0181] The transmitting component 904 may transmit a request to the cellular network for an updated MBMS traffic key based at least in part on receiving the indication of an update to the MBMS traffic key.

[0174]

[0182] The receiving component 902 may receive the updated MBMS traffic key via the control plane of the cellular network.

[0175]

[0183] The number and arrangement of components shown in Figure 9 is given as one example. In practice, there may be additional, fewer, different, or differently arranged components compared to those shown in Figure 9. Furthermore, two or more of the components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple distributed components. Additionally or alternatively, a set of components (or components) shown in Figure 9 may perform one or more functions that are described as being performed by another set of components shown in Figure 9.

[0176]

[0184] 10 is a diagram of example components of a device 1000 that may correspond to a network entity 615 (e.g., MBSF), one or more of the one or more cellular network devices 610, a BM-SC 620, a key management function 625, and / or a key distribution function 630. In some implementations, the network entity 615 (e.g., MBSF), one or more of the one or more cellular network devices 610, a BM-SC 620, a key management function 625, and / or a key distribution function 630 include one or more of the devices 1000 and / or one or more components of the device 1000. As shown in FIG. 10, the device 1000 may include a bus 1010, a processor 1020, a memory 1030, an input component 1040, an output component 1050, and a communication component 1060.

[0177]

[0185] The bus 1010 includes one or more components that enable wired and / or wireless communication between the components of the device 1000. The bus 1010 may couple two or more components of FIG. 10 together, such as via operational, communication, electronic, and / or electrical couplings. The processor 1020 includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field programmable gate array, an application specific integrated circuit, and / or another type of processing component. The processor 1020 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, the processor 1020 includes one or more processors that can be programmed to perform one or more operations or processes described elsewhere herein.

[0178]

[0186] The memory 1030 includes volatile and / or non-volatile memory. For example, the memory 1030 may include random access memory (RAM), read-only memory (ROM), a hard disk drive, and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). The memory 1030 may include internal memory (e.g., RAM, ROM, or hard disk drive) and / or removable memory (e.g., removable via a universal serial bus connection). The memory 1030 may be a non-transitory computer-readable medium. The memory 1030 stores information, instructions, and / or software (e.g., one or more software applications) related to the operation of the device 1000. In some implementations, the memory 1030 includes one or more memories coupled to one or more processors (e.g., processor 1020), such as via a bus 1010.

[0179]

[0187] The input components 1040 enable the device 1000 to receive inputs, such as user inputs and / or sensed inputs. For example, the input components 1040 may include a touch screen, a keyboard, a keypad, a mouse, buttons, a microphone, switches, sensors, global positioning system sensors, accelerometers, gyroscopes, and / or actuators. The output components 1050 enable the device 1000 to provide output, such as via a display, a speaker, and / or a light emitting diode. The communication components 1060 enable the device 1000 to communicate with other devices via wired and / or wireless connections. For example, the communication components 1060 may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and / or an antenna.

[0180]

[0188] The device 1000 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory 1030) may store a set of instructions (e.g., one or more instructions or code) for execution by the processor 1020. The processor 1020 may execute the set of instructions to perform one or more operations or processes described herein. In some implementations, execution of the set of instructions by one or more processors 1020 causes the one or more processors 1020 and / or the device 1000 to perform one or more operations or processes described herein. In some implementations, hardwired circuitry is used in place of or in combination with instructions to perform one or more operations or processes described herein. Additionally or alternatively, the processor 1020 may be configured to perform one or more operations or processes described herein. Thus, implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0181]

[0189] The number and arrangement of components shown in Figure 10 are provided as one example. Device 1000 may include additional, fewer, different, or differently arranged components than those shown in Figure 10. Additionally or alternatively, a set of components (e.g., one or more components) of device 1000 may perform one or more functions that are described as being performed by another set of components of device 1000.

[0182]

[0190] The following provides a summary of several aspects of the disclosure.

[0183]

[0191] Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: registering with a cellular network associated with a Multimedia Broadcast / Multicast Service (MBMS); sending a request to the cellular network to join the MBMS; and receiving a response from the cellular network indicating a pair of an MBMS service key (MSK) and an MSK identifier based at least in part on being registered with the cellular network.

[0184]

[0192] Aspect 2: The method of aspect 1, wherein the response includes one or more of an indication of validity of the MSK, an MBMS traffic key (MTK) associated with the MSK, an MTK identifier associated with the MTK, or an indication of validity of the MBMS traffic key.

[0185]

[0193] Aspect 3: The method of aspect 2, wherein receiving the response includes one or more of receiving the response via a control plane of a cellular network or receiving the response via point-to-multipoint communication.

[0186]

[0194] Aspect 4: The method of aspect 3, further comprising receiving an updated response via point-to-multipoint communication after receiving the response via a control plane of the cellular network.

[0187]

[0195] Aspect 5: The method of aspect 2, wherein the MBMS traffic key is encrypted at least in part based on the MSK.

[0188]

[0196] Example 6: The method of any one of Examples 2 to 5, further comprising decrypting an MBMS traffic key based at least in part on the MSK.

[0189]

[0197] Aspect 7: The method of any one of Aspects 2 to 6, further including: receiving the MBMS data via point-to-multipoint communication; and decrypting the MBMS data based at least in part on the MBMS traffic key.

[0190]

[0198] Aspect 8: The method of any one of Aspects 2 to 7, further comprising receiving an indication of an update to the MBMS traffic key via point-to-multipoint communication.

[0191]

[0199] Aspect 9: The method of aspect 8, further comprising: sending a request for an updated MBMS traffic key to a cellular network based at least in part on receiving an indication of an update to the MBMS traffic key; and receiving the updated MBMS traffic key via a control plane of the cellular network.

[0192]

[0200] Aspect 10: A method as described in any of aspects 1 to 9, wherein receiving the MSK from the MBSF via a control plane of the cellular network includes receiving a response via the control plane of the cellular network and via one or more of a multicast / broadcast session management function, a session management function, or an access and mobility management function.

[0193]

[0201] Example 11: The method of any one of Examples 1 to 10, wherein sending the request to join the MBMS includes sending the request to join the MBMS via a control plane signaling message.

[0194]

[0202] Aspect 12: The method of aspect 11, wherein the control plane signaling message includes an uplink non-access stratum (NAS) message.

[0195]

[0203] Example 13: The method of any one of Examples 1 to 12, wherein receiving the response includes receiving the response via a control plane signaling message.

[0196]

[0204] Aspect 14: The method of aspect 13, wherein the control plane signaling message includes a downlink Non-Access Stratum (NAS) message.

[0197]

[0205] Aspect 15: A method of wireless communication performed by a network entity, the method including: receiving, via a cellular network, a request from a user equipment (UE) to join an MBMS; and transmitting, via a control plane of the cellular network, a Multimedia Broadcast / Multicast Service (MBMS) service key (MSK) to the UE based at least in part on the UE being registered with the cellular network.

[0198]

[0206]

[0031] Aspect 16: The method of aspect 15, further comprising, prior to transmitting the MSK, generating the MSK.

[0199]

[0207] Aspect 17: The method of aspect 16, wherein generating the MSK prior to transmitting the MSK includes generating the MSK based at least in part on one or more of a change in multicast / broadcast membership, a periodicity for updating the MSK, and detecting a security event associated with the MSK.

[0200]

[0208] Example 18: The method of any one of examples 15 to 17, wherein the network entity includes a multicast / broadcast service function (MBSF).

[0201]

[0209] Example 19: The method of any one of Examples 15 to 18, further comprising receiving an MBMS traffic key associated with the MSK from an additional network entity.

[0202]

[0210] Example 20: The method of any one of Examples 15 to 18, further comprising: transmitting the MBMS traffic key to an additional network entity.

[0203]

[0211] Aspect 21: The method of aspect 20, wherein transmitting the MBMS traffic key to the additional network entity includes receiving a request for the MBMS traffic key from the additional network entity or transmitting the MBMS traffic key to the additional network entity based at least in part on one or more of a periodicity for updating the MBMS traffic key.

[0204]

[0212]

[0041] Aspect 22: The method of aspect 20, further comprising generating an MBMS traffic key before transmitting the MBMS traffic key.

[0205]

[0213] Aspect 23: The method of aspect 20, wherein the additional network entity includes one or more of a broadcast / multicast service center (BM-SC), an MBSTF, or a key distribution entity.

[0206]

[0214] Example 24: The method of example 15, further comprising transmitting a response to the UE via a control plane of the cellular network.

[0207]

[0215] Example 25: The method of example 24, wherein the MBMS traffic key is encrypted at least in part based on the MSK.

[0208]

[0216] Example 26: A method according to any one of Examples 24 to 25, further comprising: receiving an updated MBMS traffic key from an additional network entity; and transmitting the updated MBMS traffic key to the UE via a control plane of the cellular network.

[0209]

[0217]

[0071] Example 27: The method of example 26, further comprising: sending the updated MBMS traffic key to an additional network entity.

[0210]

[0218] Example 28: The method of example 26, further comprising: transmitting the updated MBMS traffic key to the UE via a control plane of the cellular network.

[0211]

[0219] Aspect 29: The method of aspect 28, wherein transmitting the updated MBMS traffic key via a control plane of the cellular network includes transmitting the updated MBMS traffic key to the UE based at least in part on receiving a request from the UE, or transmitting the updated MBMS traffic key to the UE based at least in part on the UE participating in MBMS.

[0212]

[0220] Example 30: The method of any of Examples 15 to 29, further including: receiving an instruction to update the MSK from an additional network entity; and transmitting the updated MSK to the additional network entity.

[0213]

[0221] Example 31: The method of example 30, further comprising transmitting the updated MSK to the UE.

[0214]

[0222] Aspect 32: A method as described in any of aspects 15 to 30, wherein transmitting the MSK to the UE via a control plane of the cellular network includes transmitting the MSK via one or more of a multicast / broadcast session management function, a session management function, or an access and mobility management function.

[0215]

[0223] Aspect 33: An apparatus for wireless communication in a device, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method described in one or more of aspects 1 to 32.

[0216]

[0224] Aspect 34: A device for wireless communication, comprising a memory and one or more processors coupled to the memory, the one or more processors configured to execute the methods described in one or more of aspects 1 to 32.

[0217]

[0225] Aspect 35: An apparatus for wireless communication, comprising at least one means for performing the method described in one or more of aspects 1 to 32.

[0218]

[0226] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by a processor to perform a method described in one or more of aspects 1 to 32.

[0219]

[0227] Aspect 37: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions including one or more instructions that, when executed by one or more processors of a device, cause the device to perform a method described in one or more of aspects 1 to 32.

[0220]

[0228] The above disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments.

[0221]

[0229] As used herein, the term "component" shall be broadly construed as hardware and / or a combination of hardware and software. "Software" shall be broadly construed to mean, among other examples, instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein may be implemented in different forms of hardware and / or a combination of hardware and software. The actual dedicated control hardware code or software code used to implement these systems and / or methods is not a limiting aspect. Accordingly, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, as those skilled in the art will understand that software and hardware may be designed to implement the systems and / or methods based at least in part on the description herein.

[0222]

[0230] As used herein, "meeting a threshold" may refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc., depending on the context.

[0223]

[0231] Although particular combinations of features are recited in a claim and / or disclosed herein, those combinations do not limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims and / or disclosed herein. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set. As used herein, a phrase referring to "at least one of" a listing of items refers to any combination of those items, including single elements. As an example, "at least one of: a, b, or c" is intended to include a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other permutation of a, b, and c).

[0224]

[0232] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Additionally, as used herein, the article "the" is intended to include one or more items referred to in relation to the article "the" and may be used interchangeably with "the one or more." Additionally, as used herein, the terms "set" and "group" are intended to include one or more items and may be used interchangeably with "one or more." When only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, terms such as "has," "have," and "having" are intended to be open-ended terms that do not limit the elements they modify (e.g., an element that "has" A can also have B). Additionally, the phrase "based on" is intended to mean "based, at least in part, on," unless expressly stated otherwise. Also, as used herein, the term "or" is intended to be inclusive when used in a sequence and may be used interchangeably with "and / or," unless expressly stated otherwise (e.g., when used in combination with "either" or "only one of").

Claims

1. User equipment (UE) for wireless communication, Memory and One or more processors connected to the memory, wherein the one or more processors Register with a cellular network associated with Multimedia Broadcast / Multicast Service (MBMS), A request to join the MBMS is sent to the cellular network. The system comprises one or more processors configured to receive a response including a pair of MBMS service keys (MSK) and MSK identifiers, at least partially based on being registered with the cellular network, via the control plane of the cellular network. The MSK included in the response received via the control plane is not encrypted using the MBMS User Key (MUK) or any other key, and relies on security already established on the control plane, for the user equipment (UE).

2. The above response is, Instructions for the effectiveness of the aforementioned MSK, The MBMS traffic key associated with the aforementioned MSK, The MBMS traffic key identifier associated with the MBMS traffic key, or The instruction for validating the MBMS traffic key, and optionally one or more of the above, The aforementioned one or more processors Based at least in part on receiving instructions to update the MBMS traffic key, a request for the updated MBMS traffic key is transmitted to the cellular network. The UE according to claim 1, further configured to receive the updated MBMS traffic key via the control plane of the cellular network.

3. The aforementioned one or more processors After receiving the response via the control plane of the cellular network, the system is further configured to receive an updated response via point-to-multipoint communication, or The one or more processors, via the control plane of the cellular network, multicast / broadcast session management functions, Session management function, or The UE according to claim 1, configured to receive the response via one or more of the access and mobility management functions.

4. The aforementioned one or more processors It is configured to receive the response via a control plane signaling message, and optionally, The UE according to claim 1, wherein the control plane signaling message includes a downlink non-access layer (NAS) message.

5. A network entity for wireless communication, Memory and One or more processors connected to the memory, wherein the one or more processors The system receives a request from a user device (UE) via a cellular network to participate in a multimedia broadcast / multicast service (MBMS). The system comprises one or more processors configured to send a response to the UE via the control plane of the cellular network, at least in part, based on the fact that the UE is registered with the cellular network, A network entity in which the MSK included in the response transmitted via the control plane is not encrypted using an MBMS user key (MUK) or other key, and relies on security already established on the control plane.

6. The aforementioned one or more processors It is further configured to generate the MSK before sending the MSK, and optionally, One or more of the aforementioned processors generate the MSK before transmitting the MSK, Changes to multicast / broadcast membership, Periodicity for updating the aforementioned MSK, The network entity according to claim 5, configured to generate the MSK based at least in part on one or more of the following: detecting a security event associated with the MSK.

7. The aforementioned network entity is equipped with multicast / broadcast service functionality (MBSF), or The aforementioned one or more processors The network entity according to claim 5, further configured to receive MBMS traffic keys associated with the MSK from additional network entities.

8. The aforementioned one or more processors The MBMS traffic key is further configured to send to additional network entities, optionally. The one or more processors transmit the MBMS traffic key to the additional network entity. Receiving a request for the MBMS traffic key from the aforementioned additional network entity, or The system is configured to transmit the MBMS traffic key to the additional network entity based at least partially on one or more of the periodicities for updating the MBMS traffic key, or The aforementioned one or more processors The system is further configured to generate the MBMS traffic key before transmitting the MBMS traffic key, or The aforementioned additional network entity, Broadcast / Multicast Service Center (BM-SC), Multicast / Broadcast Service Forwarding (MBSTF), or The network entity according to claim 5, comprising one or more of the key distribution entities.

9. The aforementioned one or more processors Receive updated MBMS traffic keys from additional network entities. The updated MBMS traffic key is transmitted to the UE via the control plane of the cellular network, or These combinations are further configured to perform, optionally, The aforementioned one or more processors The updated MBMS traffic key is further configured to send to additional network entities, or The one or more processors transmit the updated MBMS traffic key via the control plane of the cellular network. Based at least in part on receiving the request from the UE, the updated MBMS traffic key is transmitted, or The network entity according to claim 5, configured to transmit the updated MBMS traffic key to the UE, at least in part on the UE participating in the MBMS.

10. The aforementioned one or more processors An instruction to update the MSK was received from an additional network entity. The system is further configured to send the updated MSK to the aforementioned additional network entities, optionally The aforementioned one or more processors The network entity according to claim 5, further configured to transmit the updated MSK to the UE.

11. The one or more processors transmit the MSK to the UE via the control plane of the cellular network. multicast / broadcast session management functions, Session management function, or The network entity according to claim 5, configured to transmit the MSK via one or more of the access and mobility management functions.

12. A method of wireless communication performed by user equipment (UE), Registering with a cellular network associated with Multimedia Broadcast / Multicast Services (MBMS), Sending a request to the cellular network to join the MBMS, The process includes receiving a response indicating a pair of MBMS service keys (MSK) and MSK identifiers via the control plane of the cellular network, at least in part, based on being registered with the cellular network. A wireless communication method wherein the MSK included in the response received via the control plane is not encrypted using an MBMS user key (MUK) or other key, and relies on security already established on the control plane.

13. A method of wireless communication performed by a network entity, Receiving requests from user equipment (UE) via a cellular network to participate in multimedia broadcast / multicast services (MBMS), The process includes, at least in part, that the UE is registered with the cellular network, and sending a response to the UE via the control plane of the cellular network, including an MBMS service key (MSK). A wireless communication method wherein the MSK included in the response transmitted via the control plane is not encrypted using an MBMS user key (MUK) or other key, and relies on security already established on the control plane.

14. A non-temporary computer-readable medium for storing a set of instructions for wireless communication by a user device (UE), wherein the set of instructions, when executed by one or more processors of the UE, Registering with a cellular network associated with Multimedia Broadcast / Multicast Services (MBMS), Sending a request to the cellular network to join the MBMS, The control plane of the cellular network receives a response containing a pair of MBMS service keys (MSK) and MSK identifiers, at least in part, based on being registered with the cellular network. The MSK included in the response received via the control plane is not encrypted using an MBMS user key (MUK) or other key, and relies on security already established on the control plane, in a non-temporary computer-readable medium.

15. A non-temporary computer-readable medium for storing a set of instructions for wireless communication by a network entity, wherein the set of instructions, when executed by one or more processors of the network entity, Receiving requests from user equipment (UE) via a cellular network to participate in multimedia broadcast / multicast services (MBMS), Based at least partially on the fact that the UE is registered with the cellular network, the control plane of the cellular network is used to send a response to the UE including an MBMS service key (MSK), The MSK included in the response transmitted via the control plane is not encrypted using an MBMS user key (MUK) or other key, and relies on security already established on the control plane, in a non-temporary, computer-readable medium.

Images