WO2023069199A1 - Communication basée sur un plan de commande de clés de service de service de diffusion/multidiffusion multimédia - Google Patents

Communication basée sur un plan de commande de clés de service de service de diffusion/multidiffusion multimédia Download PDF

Info

Publication number
WO2023069199A1
WO2023069199A1 PCT/US2022/042227 US2022042227W WO2023069199A1 WO 2023069199 A1 WO2023069199 A1 WO 2023069199A1 US 2022042227 W US2022042227 W US 2022042227W WO 2023069199 A1 WO2023069199 A1 WO 2023069199A1
Authority
WO
WIPO (PCT)
Prior art keywords
msk
mbms
cellular network
network entity
transmit
Prior art date
Application number
PCT/US2022/042227
Other languages
English (en)
Inventor
Soo Bum Lee
Adrian Edward Escott
Anand Palanigounder
Hongil Kim
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/653,022 external-priority patent/US11785427B2/en
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to CN202280069467.4A priority Critical patent/CN118140503A/zh
Priority to KR1020247009936A priority patent/KR20240087744A/ko
Publication of WO2023069199A1 publication Critical patent/WO2023069199A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/043—Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
    • H04W12/0431—Key distribution or pre-distribution; Key agreement
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events

Definitions

  • aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for control plane-based communication of multimedia broadcast/multicast service service keys.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasts.
  • Typical wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, or the like).
  • 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 enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).
  • UMTS Universal Mobile Telecommunications System
  • 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 communications and uplink communications.
  • Downlink (or “DL”) refers to a communication link from the base station to the UE
  • uplink (or “UL”) refers to a communication link from the UE to the base station.
  • NR New Radio
  • 5G is a set of enhancements to the LTE mobile standard promulgated by the 3GPP.
  • NR is designed to better support mobile broadband internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using orthogonal frequency division multiplexing (OFDM) with a cyclic prefix (CP) (CP-OFDM) on the downlink, using 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, as well as supporting beamforming, multiple -input multiple -output (MIMO) antenna technology, and carrier aggregation.
  • OFDM orthogonal frequency division multiplexing
  • SC-FDM single-carrier frequency division multiplexing
  • DFT-s-OFDM discrete Fourier transform spread OFDM
  • MIMO multiple -input multiple -output
  • Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE).
  • the method may include registering to a cellular network associated with a multicast/broadcast service.
  • the method may include transmitting, to the cellular network, a request to join the multimedia broadcast/multicast service (MBMS).
  • the method may include receiving, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MBMS service key (MSK) and MSK identifier pair.
  • MSK MBMS service key
  • the method may include receiving, from a UE and via a cellular network, a request to join the MBMS.
  • the method may include transmitting 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.
  • 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 to a cellular network associated with a multicast/broadcast service.
  • the one or more processors may be configured to transmit, to the cellular network, a request to join the MBMS.
  • the one or more processors may be configured to receive, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MSK and MSK identifier pair.
  • 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, from a UE and via a cellular network, a request to join the MBMS.
  • the one or more processors may be configured to transmit a 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.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores 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 to 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, to the cellular network, a request to join the MBMS.
  • the set of instructions when executed by one or more processors of the UE, may cause the UE to receive, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MSK and MSK identifier pair.
  • Some aspects described herein relate to a non-transitory computer-readable medium that stores 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 and via a cellular network, a request to join the MBMS.
  • the set of instructions when executed by one or more processors of the network entity, may cause the network entity to transmit a 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.
  • the apparatus may include means for registering to a cellular network associated with a multicast/broadcast service.
  • the apparatus may include means for transmitting, to the cellular network, a request to join the MBMS.
  • the apparatus may include means for receiving, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MSK and MSK identifier pair.
  • the apparatus may include means for receiving, from a UE and via a cellular network, a request to join the MBMS.
  • the apparatus may include means for transmitting a 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.
  • aspects generally include a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, wireless communication device, and/or processing system as substantially described herein with reference to and as illustrated by the drawings and specification.
  • the foregoing has outlined rather broadly the features and technical advantages of examples according to the disclosure in order that the detailed description that follows may be better understood. Additional features and advantages will be described hereinafter. The conception and specific 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 constructions do not depart from the scope of the appended claims.
  • aspects are described in the present disclosure by illustration to some examples, those skilled in the art will understand that such aspects may be implemented in many different arrangements and scenarios.
  • Techniques described herein may be implemented using different platform types, devices, systems, shapes, sizes, and/or packaging arrangements.
  • some aspects may be implemented via integrated chip embodiments or other non-modulecomponent based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, and/or artificial intelligence 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 described aspects and features may include additional components and features for implementation and practice of claimed and described aspects.
  • transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders, and/or summers).
  • RF radio frequency
  • aspects described herein may be practiced in a wide variety of devices, components, systems, distributed arrangements, and/or end-user devices of varying size, shape, and constitution.
  • FIG. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.
  • FIG. 2 is a diagram illustrating an example of a base station in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.
  • UE user equipment
  • FIG. 3 is a diagram illustrating an example of delivery of a multimedia broadcast/multicast service (MBMS) service key (MSK), in accordance with the present disclosure.
  • MBMS multimedia broadcast/multicast service
  • MSK service key
  • Fig. 4 is a diagram illustrating an example associated with network architectures, in accordance with the present disclosure.
  • FIGs. 5 and 6 are diagrams illustrating examples associated with control plane-based communication of MSKs, in accordance with the present disclosure.
  • Figs. 7 and 8 are diagrams illustrating example processes associated with control plane-based communication of MSKs, in accordance with the present disclosure.
  • FIG. 9 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.
  • Fig. 10 is a diagram of example components of a device, in accordance with the present disclosure.
  • aspects may be described herein using terminology commonly associated with a 5G or New Radio (NR) radio access technology (RAT), aspects of the present disclosure can be applied to other RATs, such as a 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).
  • NR New Radio
  • Fig. 1 is a diagram illustrating an example of a wireless network 100, in accordance with the present disclosure.
  • the wireless network 100 may be or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g., Long Term Evolution (LTE)) network, among other examples.
  • 5G e.g., NR
  • 4G e.g., Long Term Evolution (LTE) network
  • the wireless network 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110b, a BS 110c, and a BS 1 lOd), a user equipment (UE) 120 or multiple UEs 120 (shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e), and/or other network entities.
  • a base station 110 is an entity that communicates with UEs 120.
  • a base station 110 may include, for example, an NR base station, an LTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G), an access point, and/or a transmission reception point (TRP).
  • Each base station 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of a base station 110 and/or a base station subsystem serving this coverage area, depending on the context in which the term is used.
  • 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., several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs 120 having association with the femto cell (e.g., UEs 120 in a closed subscriber group (CSG)).
  • CSG closed subscriber group
  • 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.
  • the BS 110a may be a macro base station for a macro cell 102a
  • the BS 110b may be a pico base station for a pico cell 102b
  • the 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.
  • a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a base station 110 that is mobile (e.g., a mobile base station).
  • the base stations 110 may be interconnected to one another 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 a direct physical connection or a virtual network, using any suitable transport network.
  • the wireless network 100 may include one or more relay stations.
  • a relay station is an entity that can receive a transmission of data from an upstream station (e.g., a base station 110 or a UE 120) and send a transmission of the data to a downstream station (e.g., a UE 120 or a base station 110).
  • a relay station may be a UE 120 that can relay transmissions for other UEs 120.
  • the BS 1 lOd e.g., a relay base station
  • the BS 110a e.g., a macro base station
  • the UE 120d in order to facilitate communication between the BS 110a and the UE 120d.
  • a base station 110 that relays communications may be referred to as a relay station, a relay base station, a relay, or the like.
  • the wireless network 100 may be a heterogeneous network that includes base stations 110 of different types, such as macro base stations, pico base stations, femto base stations, relay base stations, or the like. These different types of base stations 110 may have different transmit power levels, different coverage areas, and/or different impacts on interference in the wireless network 100. For example, macro base stations may have a high transmit power level (e.g., 5 to 40 watts) whereas pico base stations, femto base stations, and relay base stations may have lower transmit power levels (e.g., 0. 1 to 2 watts).
  • a network controller 130 may couple to or communicate with a set of base stations 110 and may provide coordination and control for these base stations 110.
  • the network controller 130 may communicate with the base stations 110 via a backhaul communication link.
  • the base stations 110 may communicate with one another directly or indirectly via a wireless or wireline backhaul communication link.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE 120 may be stationary or mobile.
  • a UE 120 may include, for example, an access terminal, a terminal, a mobile station, and/or a subscriber unit.
  • a UE 120 may be a cellular phone (e.g., a smart phone), 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, smart clothing, smart glasses, a smart wristband, 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 vehicular component or sensor,
  • Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs.
  • An MTC UE and/or an eMTC UE 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 Intemet-of-Things (loT) devices, and/or may be implemented as NB-IoT (narrowband loT) devices.
  • Some UEs 120 may be considered a Customer Premises Equipment.
  • a UE 120 may be included inside a housing that houses components of the UE 120, such as processor components and/or memory components.
  • the processor components and the memory components may be coupled together.
  • the processor components e.g., one or more processors
  • the memory components e.g., a memory
  • the processor components and the memory components may be operatively coupled, communicatively coupled, electronically coupled, and/or electrically coupled.
  • 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.
  • a RAT may be referred to as a radio technology, an air interface, or the like.
  • a frequency may be referred to as a carrier, a frequency channel, or the like.
  • Each frequency may support a single RAT in a given geographic area in order to avoid interference between wireless networks of different RATs.
  • NR or 5G RAT networks may be deployed.
  • two or more UEs 120 may communicate directly using one or more sidelink channels (e.g., without using a base station 110 as an intermediary to communicate with one another).
  • the UEs 120 may communicate using peer-to-peer (P2P) communications, device-to-device (D2D) communications, a vehicle-to-everything (V2X) protocol (e.g., which may include a vehicle-to- vehicle (V2V) protocol, a vehicle-to-infrastructure (V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or a mesh network.
  • V2X vehicle-to-everything
  • a UE 120 may perform scheduling operations, resource selection operations, and/or other operations described elsewhere herein as being performed by the base station 110.
  • Devices of the wireless network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, channels, or the like.
  • devices of the wireless network 100 may communicate using one or more operating bands.
  • 5G NR two initial operating bands have been identified as frequency range designations FR1 (410 MHz - 7.125 GHz) and FR2 (24.25 GHz - 52.6 GHz).
  • FR1 frequency range designations FR1 (410 MHz - 7.125 GHz)
  • FR2 24.25 GHz - 52.6 GHz.
  • FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in various documents and articles.
  • FR2 which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
  • EHF extremely high frequency
  • ITU International Telecommunications Union
  • FR3 7.125 GHz - 24.25 GHz
  • Frequency bands falling within FR3 may inherit FR1 characteristics and/or FR2 characteristics, and thus may effectively extend features of FR1 and/or FR2 into mid-band frequencies.
  • higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz.
  • three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz).
  • Each of these higher frequency bands falls within the EHF band.
  • sub-6 GHz may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies.
  • millimeter wave may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band.
  • frequencies included in these operating bands may be modified, and techniques described herein are applicable to those modified frequency ranges.
  • the UE 120 may include a communication manager 140.
  • the communication manager 140 may register to a cellular network associated with a multimedia broadcast/multicast service (MBMS) transmit, to the cellular network, a request to join the MBMS; and receive, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MSK and MSK identifier pair.
  • the response may indicate one or more MSK and MSK identifier pairs. Different MSK and MSK identifier pairs may have different validity times.
  • the communication manager 140 may perform one or more other operations described herein.
  • the base station 110 may include a communication manager 150.
  • the communication manager 150 may receive, from a UE, a request to join the MBMS; forward the request to join the MBMS service to a network entity; receive a MSK from the network entity; and transmit an 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 communication manager 150 may perform one or more other operations described herein.
  • the term “base station” (e.g., the base station 110), cellular network device, “network node,” or “network entity” may refer to an aggregated base station, a disaggregated base station (e.g., described in connection with Fig. 9), an integrated access and backhaul (IAB) node, a relay node, and/or one or more components thereof.
  • a disaggregated base station e.g., described in connection with Fig. 9
  • IAB integrated access and backhaul
  • base station 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.
  • the term “base station,” “network node,” or “network entity” may refer to one device configured to perform one or more functions, such as those described herein in connection with the base station 110.
  • the term “base station,” “network node,” or “network entity” may refer to a plurality of devices configured to perform the one or more functions.
  • each of a number of different devices may be configured to perform at least a portion of a function, or to duplicate performance of at least a portion of the function, and the term “base station,” “network node,” or “network entity” may refer to any one or more of those different devices.
  • 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.
  • two or more base station functions may be instantiated on a single device.
  • the term “base station,” “network node,” or “network entity” may refer to one of the base station functions and not another. In this way, a single device may include more than one base station.
  • Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.
  • Fig. 2 is a diagram illustrating an example 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 (T> 1).
  • the UE 120 may be equipped with a set of antennas 252a through 252r, such as R antennas (R > 1).
  • a transmit processor 220 may receive data, from a data source 212, intended for the UE 120 (or a set of UEs 120).
  • 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 that UE 120.
  • MCSs modulation and coding schemes
  • CQIs channel quality indicators
  • the base station 110 may process (e.g., encode and modulate) the data for the UE 120 based at least in part on the MCS(s) selected for the UE 120 and may provide data symbols for 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 upper layer signaling) and provide overhead symbols and control symbols.
  • the transmit processor 220 may generate reference symbols for reference signals (e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)) and synchronization signals (e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)).
  • reference signals e.g., a cell-specific reference signal (CRS) or a demodulation reference signal (DMRS)
  • synchronization signals e.g., a primary synchronization signal (PSS) or a secondary synchronization signal (SSS)
  • a transmit (TX) multiple -input multiple -output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (e.g., T output symbol streams) to a corresponding set of modems 232 (e.g., T modems), shown as modems 232a through 232t.
  • each output symbol stream may be provided to a modulator component (shown as MOD) of a modem 232.
  • Each modem 232 may use a respective modulator component to process a respective output symbol stream (e.g., for OFDM) to obtain an output sample stream.
  • Each modem 232 may further use a respective modulator component to process (e.g., convert to analog, amplify, fdter, and/or upconvert) the output sample stream to obtain a downlink signal.
  • the modems 232a through 232t may transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas), shown as antennas 234a through 234t.
  • a set of antennas 252 may receive the 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), shown as modems 254a through 254r.
  • R received signals e.g., R received signals
  • each received signal may be provided to a demodulator component (shown as DEMOD) of a modem 254.
  • DEMOD demodulator component
  • Each modem 254 may use a respective demodulator component to condition (e.g., filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples.
  • Each modem 254 may use a demodulator component to further process the input samples (e.g., for OFDM) to obtain received symbols.
  • a MIMO detector 256 may obtain received symbols from the modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols.
  • a receive processor 258 may process (e.g., demodulate and decode) the detected symbols, may provide decoded data for the UE 120 to a data sink 260, and may provide decoded control information and system information to a controller/processor 280.
  • controller/processor may refer to one or more controllers, one or more processors, or a combination thereof.
  • a 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.
  • RSRP reference signal received power
  • RSSI received signal strength indicator
  • RSSRQ reference signal received quality
  • CQI CQI parameter
  • 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 station 110 via the communication unit 294.
  • One or more antennas may include, or may be included 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, an antenna group, a set of antenna elements, and/or an antenna array may include one or more antenna elements (within 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 transmission and/or reception components, such as one or more components of Fig. 2.
  • a transmit processor 264 may receive and process data from a data source 262 and control information (e.g., for reports that include 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 a TX MIMO processor 266 if applicable, further processed by the modems 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to the base station 110.
  • the modem 254 of the UE 120 may include a modulator and a demodulator.
  • 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., the controller/processor 280) and the memory 282 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 5-10).
  • the uplink signals from UE 120 and/or other UEs may be received by the antennas 234, processed by the modem 232 (e.g., a demodulator component, shown as DEMOD, of the modem 232), 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 provide the decoded control information to the 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.
  • the modem 232 of the base station 110 may include a modulator and a demodulator.
  • the base station 110 includes a transceiver.
  • the transceiver may include any combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 220, and/or the TX MIMO processor 230.
  • the transceiver may be used by a processor (e.g., the controller/processor 240) and the memory 242 to perform aspects of any of the methods described herein (e.g., with reference to Figs. 5-10).
  • 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 one or more techniques associated with control plane-based communication of MSKs, as described in more detail elsewhere herein.
  • 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 operations 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.
  • the memory 242 and/or the memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and/or program code) for wireless communication.
  • the one or more instructions when executed (e.g., directly, or after compiling, converting, and/or interpreting) by one or more processors of the base station 110 and/or the UE 120, 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.
  • executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.
  • the UE includes means for registering to a cellular network associated with an MBMS means for transmitting, to the cellular network, a request to join the MBMS; and/or means for receiving, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MSK and MSK identifier pair.
  • the means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.
  • the network entity includes means for receiving, from a UE and via a cellular network, a request to join the MBMS; and/or means for transmitting a 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.
  • the means for the network entity to perform operations described herein may include, for example, one or more of components shown in Fig. 10, such as processor 1020 memory 1030, input component 1040, output component 1050, and/or communication component, among other examples.
  • Fig. 2 While blocks in Fig. 2 are illustrated as distinct components, the functions 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, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.
  • Fig. 2 is provided as an example. Other examples may differ from what is described with regard to Fig. 2.
  • Fig. 3 gives an example 300 of the network elements involved in MBMS from a security perspective.
  • the UE may include an MBMS key generation and validation function/storage (MGV-S/F) 305 configured to manage security keys for MBMS communications.
  • MMV-S/F MBMS key generation and validation function/storage
  • the Bootstrapping Server Function (BSF) 310 is a part of generic bootstrapping architecture (GBA).
  • GBA generic bootstrapping architecture
  • the UE 120 and the BM-SC 315 use the GBA to establish shared keys that are used to protect point-to-point communication between the UE 120 and the BM-SC 315.
  • One or more 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.
  • the BM-SC 315 is a source for MBMS data. Additionally, or alternatively, the BM- SC 315 may be responsible for scheduling data and receiving data from third parties (e.g., the content provider 345) for transmission.
  • the BM-SC 315 is responsible for establishing shared secrets with the UE 120 using the GBA, authenticating the UE 120 with a hypertext transfer protocol (HTTP) digest authentication mechanism, registering and de -registering UEs 120 for MBMS user services, generating and distributing keys necessary for MBMS security to the UEs 120 with multimedia internet keying (MIKEY) protocol and for applying appropriate protection to data that is transmitted as part of an MBMS user service.
  • the BM-SC 315 also provides MBMS bearer authorization for UEs 120 attempting to establish an MBMS bearer.
  • the BM-SC 315 also verifies whether a UE 120 is authorized to register and receive keys for the MBMS user service. For MBMS multicast mode, this authorization may be performed with use of a membership function 320 or associated with the BM-SC 315. For an MBMS broadcast mode, this authorization may be performed without use of the membership function 320 based at least in part on the membership function 320 only being defined in context of MBMS multicast mode.
  • the UE 120 may be responsible for establishing shared secrets with the BM-SC 315 using the GBA, registering to and de-registering from MBMS user services, requesting and receiving keys for the MBMS user service from the BM-SC 315 and also using those keys to decrypt MBMS data that is received.
  • the BM-SC 315 may include sub-functions related to MBMS security.
  • 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 key distribution function 335.
  • the key request function 330 is responsible for retrieving GBA keys from the BSF, deriving an MBMS user key and/or MBMS request key from GBA keys, performing MBMS user service registration, deregistration and MSK request procedures and related user authentication using MBMS request key (MRK), providing MBMS user key (MUK) to a key distribution function 335, and/or performing an authorization check.
  • MRK MBMS request key
  • MUK MBMS user key
  • the key request function 330 may implement the following functions and procedures: bootstrapping initiation, bootstrapping re-negotiation, HTTP digest authentication, MRK derivation, MBMS user service registration procedure, MBMS user service deregistration procedure, and/or a MSK request procedure, among other examples.
  • the key distribution function 335 is responsible for retrieving MUK from the key request function 330 and/or a registration function, generating and distributing MSKs and MBMS traffic keys (MTKs to the UE, and/or providing MTK to Session and Transmission function 340, among other examples).
  • the key distribution function 335 implements the following security procedures: MSK delivery procedure, MTK delivery procedure, and/or BM- SC solicited pull procedure, among other examples.
  • the session and transmission function 340 is responsible for session and transmission functions. As part of these session and transmission functions, the session and transmission function 340 performs protection of data with MTK (encryption and/or integrity protection). The session and transmission function 340 implements the following security procedures: protection of streaming data and/or protection of download data.
  • MTK encryption and/or integrity protection
  • the membership function 320 is used to verify if a user is authorized to register, receive keys, or to establish an MBMS bearer for MBMS multicast mode.
  • the Membership function may be defined only for MBMS multicast mode.
  • Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.
  • FIG. 4 is a diagram illustrating an example 400 associated with network architectures, in accordance with the present disclosure.
  • the network architecture includes multiple functions and/or entities.
  • One or more functions and/or entities described in connection with Fig. 4 and otherwise herein 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.
  • a policy control function performs functions to support Multicast and Broadcast Services (MBS)if dynamic Policy and Control Charging (PCC)for MBS is needed.
  • the PCF may support QoS handling for an MBS Session, provide policy information regarding the MBS session to multicast/broadcast Session Management Function (MB-SMF) for authorizing the related QoS profile, interact with User Data Repository (UDR) for QoS information retrieval, and/or receive MBS information from Application Function (AF), Network Exposure Function (NEF) or Multicast/B roadcast Service Function (MBSF), based at least in part on, for example, different configuration options.
  • An MB-SMF also performs the functions to support MBS.
  • the MB- SMF may support MBS session management (including QoS control), configure Multicast/Broadcast user plane function (MB-UPF) for multicast and broadcast flows transport based on the policy rules for multicast and broadcast services from PCF or local policy, allocate and de-allocate temporary mobile group identities (TMGIs), among other examples.
  • MBS session management including QoS control
  • MB-UPF Multicast/Broadcast user plane function
  • TMGIs temporary mobile group identities
  • the MB-SMF may, for broadcast sessions, interact with a RAN (via Access and Mobility Management Function (AMF)) to control data transport using a 5GC shared MBS traffic delivery method. Additionally, or alternatively, the MB-SMF may, for multicast sessions, interact with a Session Management Function (SMF) to modify a Protocol Data Unit (PDU) Session associated with an MBS session, interact with a RAN (via AMF and SMF) to establish data transmission resources between MB-UPF and RAN nodes for a 5GC Shared MBS traffic delivery method, and/or control multicast data transport using a 5GC Individual MBS traffic delivery method, among other examples.
  • SMF Session Management Function
  • PDU Protocol Data Unit
  • An SMF may also perform functions to support MBS. For example, the SMF may discover MB-SMF for a multicast session, authorize multicast session join operation if needed, interact with MB-SMF to obtain and manage multicast session context, and/or interact with 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.
  • the MB-UPF may also perform functions to support MBS.
  • the MB- UPF may, multicast and broadcast sessions, perform packet filtering of incoming downlink packets for multicast and broadcast flows, enforce QoS (MFBR) and counting/reporting based on existing means, interact with MB-SMF for receiving multicast and broadcast data, deliver multicast and broadcast data to RAN nodes for 5GC Shared MBS traffic delivery method, among other examples.
  • MFBR QoS
  • the MB-UPF may deliver multicast data to user plane function (UPF) for 5GC Individual MBS traffic delivery method.
  • UPF user plane function
  • the UPF may also perform functions to support MBS.
  • the UPF may interact with SMF for receiving multicast data from MB-UPF for 5GC Individual MBS traffic delivery method, deliver multicast data to UEs via a PDU session for a 5GC individual MBS traffic delivery method.
  • the UPF and MB-UPF may be co-located or deployed separately.
  • the AMF may also perform functions to support MBS.
  • the AMF may signal with an NG-RAN and an MB-SMF for MBS session management, select NG-RANs for notification of multicast session activation toward UEs in a CM-IDLE state, select NG-RANs for broadcast traffic distribution, and/or the AMF may be aware of NG-RAN 5G MBS capability.
  • the NG-RAN may also perform functions to support MBS.
  • the NG- RAN may manage MBS QoS flows via N2, deliver MBS data packets from 5GC shared for multiple UEs over radio using point-to-multipoint (PTM) or point-to-point (PTP), configure UE for MBS QoS flow reception at access stratum (AS) layer, control switching between PTM and PTP delivery per UE, support multicast sessions continuity during Xn Handover and N2 Handover, and/or support notification of multicast session activation over radio toward UEs in CM-IDLE state and CM-CONNECTED with a radio resource control (RRC) Inactive state, among other examples.
  • PTM point-to-multipoint
  • PTP point-to-point
  • AS access stratum
  • RRC radio resource control
  • 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, handle incoming MBS QoS flows, support, signaling for joining and leaving multicast MBS session, provide MBS resource management support at AS layer, and/or receive notification in CM-IDLE state and CM-CONNECTED with RRC Inactive state for multicast data transmission, among other examples.
  • the AF may also perform functions to support MBS.
  • the AF may requesting multicast or broadcast service from the 5GC by providing service information including QoS requirement to 5GC, instruct MBS session operation towards 5GC if needed, and/or interact with NEF for MBS related service exposure, among other examples.
  • the NEF may also perform functions to support MBS.
  • the NEF may provide an interface to AFs for MBS procedures including service provisioning, MBS session and QoS management, interact with AF and NFs in 5GC, (e.g., MB-SMF for MBS session operations), determine transport parameters, and/or select MB-SMF to serve an MBS Session.
  • the MBSF may also perform functions to support MBS.
  • the MBSF may provide service level functionality to support MBS and interworking with LTE MBMS, interact with AF and MB-SMF for MBS session operations, determine transport parameters, determine session transport, select MB-SMF to serve an MBS session, control Multicast/Broadcast Service Transport Function (MBSTF) if the MBSTF is used, and/or determine sender internet protocol (IP) multicast address for the MBS session if IP multicast address is sourced by MBSTF, among other examples.
  • MBSTF Multicast/Broadcast Service Transport Function
  • IP internet protocol
  • MBSF functionality related to service and MBS data handling is to be determined with SA WG4.
  • the MBSTF may also perform functions to support MBS.
  • the MBSTF may provide a media anchor for MBS data traffic if needed, source IP multicast if needed, provide generic packet transport functionalities available to any IP multicast enabled 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.
  • MBSTF functionality related to MBS data handling e.g. encoding
  • SA WG4 the SA WG4.
  • the UDM may also perform functions to support MBS.
  • the UDM may support management of subscription for authorization for multicast MBS sessions.
  • the UDR may also perform functions to support MBS.
  • the UDR may support management of UE authorization information for multicast MBS session and/or support management of policy information for multicast or broadcast MBS session, among other examples.
  • the NRF may also perform functions to support MBS.
  • the NRF may support new NF types MB-SMF and MBSF and corresponding NF profdes, support (e.g., for multicast and/or broadcast MBS sessions) MB-SMF discovery based on parameters such as DNN, S-NSSAI and MB service area, at MBS Session creation, and/or support (e.g., for multicast MBS sessions) MB-SMF discovery based on MBS Session identifier (ID) by SMF serving the multicast Session at UE join, among other examples.
  • ID MBS Session identifier
  • An NF profile in the NRF may include, for MB-SMF, MBS Session ID(s), Area Session ID(s) and corresponding MBS service area(s) if available.
  • a 5G system architecture for MBS reuses existing reference points of Nl, N2, N4, N10, N11, N30 and N33 with enhancement to support MBS.
  • Fig. 4 is provided as an example. Other examples may differ from what is described with regard to Fig. 4.
  • a UE attempting to receive an MBMS may receive one or more keys from a MB-SC using a broadcast or multicast communication on a user plane. For example, the UE may receive an MSK via a PTP communication and then receive an MTK via a PTM communication. The UE may decrypt the MSK using a MUK and then may decrypt the MTK using the MSK. Although the use of these keys provides security and reduces unauthorized access to MBMS data, a UE attempting to establish the MBMS may observe latency based at least in part on timing of reception of the MTK and the MSK and may consume computing resources used for decryption and/or generation of the different keys.
  • an MBSF may derive and/or generate an MSK and distribute the MSK to the UE using a control plane-based communication.
  • the MBSF may transmit the MSK to the UE via one or more cellular network devices and may transmit the MSK to one or more network entities, such as a BM-SC or MBSTF (e.g., which may co-exist with the BM-SC and/or may have a subset of BM-SC functionalities).
  • the UE may receive the MSK with reduced latency and/or the MSK may not be encrypted with an MUK or other key based at least in part on reliance on security already established on the control plane. In this way, the UE may improve latency and/or reduce consumption of computing resources to establish a secure connection for receiving the MBMS.
  • an MBSTF includes a key distribution function and session and transmission function of the BM-SC.
  • the MSK generation at the MB-SC may be replaced with a key supplied by the MBSF. Additionally, or alternatively, a procedure for the BM-SC to generate and provide the MSK may not be required.
  • the UE receives the MSK during an MBS session join procedure using, for example, a non-access stratum (NAS) message.
  • NAS non-access stratum
  • MTK delivery and MBS traffic processing may be provided via the MB-SC as described in connection with Fig. 3.
  • the MTK may be transmitted to the UE along with MSK via the control plane. This may enable the UE to process MBS traffic immediately upon joining the MBMS rather than waiting to receive the MTK which is sent in a PTM (or multicast/broadcast) message and protected using the MSK.
  • the MTK when a new MTK is generated by MBSTF, the MTK is provided to the MBSF. Additionally, or alternatively, the MBSF may generate the MTK and supply the MTK to the MBSTF. In some aspects, MTK generation may be periodic or triggered (requested) by the MBSTF. In some aspects, an MTK change may be indicated to the UE via 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 UEs that have joined the MBS session along with the indication.
  • a NAS procedure e.g., a new key request or an existing PDU session modification procedure
  • Fig. 5 is a diagram illustrating an example 500 associated with control plane-based communication of MSKs, in accordance with the present disclosure.
  • a UE e.g., UE 120
  • may communication with one or more cellular network devices e.g., base station 110, an AMF, an SMF, an MB-SMF, among other examples
  • 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 operations shown in Fig. 5.
  • the UE may register to a cellular network provided by the one or more cellular network devices.
  • the cellular network is associated with an MBMS.
  • the UE may transmit a request to join an MBMS after registering to the cellular network.
  • the UE may transmit the request to join the MBMS via a control plane signaling message (e.g., a control plane communication).
  • the UE control plane signaling message may include an uplink NAS message.
  • 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 the one or more network entities.
  • the one or more network entities may receive, and the one or more cellular network devices may transmit, the request to join the MBMS initiated by the UE.
  • the one or more network entities may generate an MSK and/or an MTK.
  • a MBSF generates the MSK and/or the MTK.
  • the MBSF may generate both of the MSK and the MTK, or the MBSF may generate the MSK and may receive the MTK from an additional network entity (e.g., a MB-SC and/or MBSTF).
  • an additional network entity e.g., a MB-SC and/or MBSTF.
  • the one or more entities may generate the MSK based at least in part on a change of multicast/broadcast membership, a periodicity for updating the MSK, and/or detection of a security event (e.g., a determination that the MSK is compromised) associated with the MSK, among other examples.
  • a security event e.g., a determination that the MSK is compromised
  • 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, the MSK identifier (ID), the MTK, and/or an MTK identifier.
  • the MSK and the MSK identifier may form an MSK-MSK identifier pair.
  • the MSK may be associated with a unique MSK identifier that is provided with the MSK.
  • the first network entity may transmit an indication of multiple MSKs (e.g., simultaneously and/or in a same message).
  • a first MSK may be valid for a first time period and a second MSK may be valid for a second time period.
  • a first MSK may be used to encrypt a second MSK and/or a third MSK, among other examples.
  • a first MSK may be valid for a first service and a second MSK may be valid for a second service.
  • 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.
  • MTK identifier may match the MSK identifier of the MSK or may otherwise indicated compatibility of the MTK with the MSK.
  • the MBSF may generate the MSK and provide the MSK to an BM- SC, an MBSTF, and/or a key distribution entity, among other examples.
  • the MBSF may also generate the MTK and provide the MTK to the MBSTF.
  • the MBSTF may generate the MTK based at least in part on the MSK and may provide the MTK to the MBSF.
  • the one or more network entities may transmit the indication of the MSK, the MSK identifier, the MTK, and/or the MTK identifier to the one or more cellular network devices.
  • the one or more network entities may transmit an indication of multiple MSKs (e.g., simultaneously and/or in a same message).
  • a first MSK may be valid for a first time period and a second MSK may be valid for a second time period.
  • a first MSK may be used to encrypt a second MSK and/or a third MSK, among other examples.
  • a first MSK may be valid for a first service and a second MSK may be valid for a second service.
  • the UE may receive, and the one or more cellular network devices may transmit, the indication of the MSK, the MSK identifier, the MTK, and/or the MTK identifier.
  • the UE may receive the indication of the MSK, the MSK identifier, the MTK, and/or the MTK identifier via a response from the cellular network that is based at least in part on the UE being registered to the cellular network.
  • the one or more cellular network devices may rely on security of the control plane to provide the indication of the MSK, the MSK identifier, the MTK, and/or the MTK identifier.
  • the UE may receive, and the one or more cellular network devices may transmit, the indication of the MSK and/or MSK identifier in a separate transmission from the indication of the MTK and/or the MTK identifier.
  • the UE may receive a first MTK with the MSK and may receive (e.g., via the control plan or the user plane) a second MTK after receiving the MSK.
  • the MTK may be encrypted using the MSK.
  • the UE may receive the MSK via the control plane (e.g., a control plane signaling message) of the cellular network based at least in part on transmission from a network entity (e.g., an MBSF) to one or more of the cellular network devices.
  • the control plane signaling message includes a downlink NAS message.
  • 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.
  • the UE may receive the MSK from the MBSF via the control plane of the cellular network based at least in part on, for example, receiving the MSK via the multicast/broadcast session management function, the session management function, and/or the access and mobility management function.
  • the response may include an indication of a validity of the MSK, an MTK associated with the MSK, an MTK identifier associated with the MTK, and/or an indication of a validity of the MTK.
  • the response may indicate that the MSK is used to protect (e.g., encrypt) multiple MTKs, where multiple MTKs are used at different time intervals.
  • the MSK may be indicated as valid for a day and MTKs may be indicated or configured to be valid for an hour.
  • the MSK is used to protect MTK1 which is broadcast over a user plane.
  • the MSK is used to protect MTK2 and at a third time, the MSK is used to protect MTK3.
  • the UE may also receive a current (e.g., currently valid) MTK along with the MSK. For example, if the UE joins the MBMS service between t2 and t3, the UE may receive the MSK and MTK2 over the control -plane.
  • the UE may receive the MSK via the control plane and may receive the MTK via a PTP communication from the one or more network entities.
  • the US may receive an indication of multiple MSKs (e.g., simultaneously and/or in a same message).
  • a first MSK may be valid for a first time period and a second MSK may be valid for a second time period.
  • a first MSK may be used to encrypt a second MSK and/or a third MSK, among other examples.
  • a first MSK may be valid for a first service and a second MSK may be valid for a second service.
  • the UE may receive (e.g., in a same message) an indication of how to use the multiple MSKs (e.g., as described herein).
  • the UE may decrypt the MTK using the MSK.
  • 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.
  • the MTK may be encrypted using the MSK based at least in part the MTK being transmitted to the UE via the user plane.
  • the UE may receive, and the one or more network entities may transmit, MBMS data via one or more PTM communications.
  • the UE may decrypt the MBMS data based at least in part on the MTK.
  • the first network entity of the one or more network entities may transmit, and the second network entity of the one or more network entities may receive, an indication of an update to the MSK, the MSK identifier, the MTK, and/or the MSK identifier.
  • the first network entity e.g., the MBSF
  • the second network entity may generate an updated MTK and provide the updated MTK to the second network entity (the MBSTF or BM-SC) and to the UE (to the UE using the control plane).
  • the first network entity may receive an updated MTK generated by the second network entity (the MBSTF or BM-SC) and transmit the updated MTK to the UE (to the UE using the control plane).
  • the first network entity may use the updated MTK and/or an associated MTK identifier to confirm validity of an active MSK.
  • the first network entity may transmit the MTK based at least in part on receiving, from the second network entity, a request for the MTK, or a periodicity for updating the MTK.
  • the UE may transmit, and the one or more cellular network devices may receive, a request for an updated MTK.
  • the UE may transmit the request for the updated MTK based at least in part on receiving an indication that the MTK is updated (e.g., in an updated MTK message).
  • the UE may transmit the request via the control plane.
  • the UE may receive a response from the one or more network entities (e.g., the MBSF) via the one or more cellular network devices.
  • the UE response may indicate the updated MTK based at least in part on, for example, the UE failing to receive the updated MTK via a PTP or PTM communication from the one or more network entities (e.g., the MBSTF or BM-SC).
  • the one or more network entities e.g., the MBSTF or BM-SC.
  • the one or more network entities may transmit, and the UE may receive, an indication of an updated MTK and/or MTK identifier.
  • the UE may receive the updated MTK message via a PTM communication.
  • a first network entity may transmit the updated MTK based at least in part on receiving an indication, from a second network entity, to update the MTK.
  • the one or more network entities may transmit an updated MSK to the UE.
  • 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.
  • the UE may receive the MSK with reduced latency and/or the MSK may not be encrypted with an MUK or other key based at least in part on reliance on security already established on the control plane. In this way, the UE may improve latency and/or reduce consumption of computing resources to establish a secure connection for receiving the MBMS.
  • Fig. 5 is provided as an example. Other examples may differ from what is described with regard to Fig. 5.
  • Fig. 6 is a diagram illustrating an example 600 associated with control plane-based communication of MSKs, in accordance with the present disclosure.
  • a UE 120 may communication with one or more cellular network devices 610 (e.g., base station 110, an AMF, an SMF, an MB-SMF, among other examples), a network entity 615 (e.g., an MBSF) and an additional network entity 620 (e.g., an MBSTF and/or a BM-SC).
  • 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 operations shown in Fig. 6.
  • the UE may receive an MSK and/or an MTK from the network entity 615 via the one or more cellular network devices 610.
  • the MBSF may transmit the MSK through the one or more cellular network devices 610 to the UE and may transmit the MSK to the additional network entity 620, the key management function 625, and/or the key distribution function 630.
  • the UE may manage and/or validate keys, such as the MSK and/or MTK, using an MBMS key generation and validation function/storage (MGV-S/F) 605.
  • MMV-S/F MBMS key generation and validation function/storage
  • 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 (e.g., with an MTK identifier for validation of the MSK) to the UE via the user plane and/or may provide the MTK (e.g., with an MSK identifier for validation of the MSK) to the network entity 615 to confirm validity of the MSK.
  • the network entity 615 may transmit the MSK to the additional network entity 620 and/or may update the MSK.
  • the network entity 615 may generate the MTK and may provide the MTK to the additional network entity 620, the key management function 625, and/or the key distribution function 630 to be used for encoding data associated with the network entity 615.
  • the network entity 615 may also provide the MTK to the UE via the one or more cellular network devices 610.
  • the MBSF may transmit a first MTK (e.g., a current MTK when the UE 120 joins the MBMS) via the control plane and the BM-SC 620 may transmit a second MTK via the user plane (e.g., using a PTM communication).
  • a first MTK e.g., a current MTK when the UE 120 joins the MBMS
  • the BM-SC 620 may transmit a second MTK via the user plane (e.g., using a PTM communication).
  • the additional network entity 620 may use the MTK, at the Session and Transmission function 635, to encrypt data received from a content provider 640.
  • the additional network entity 620 may transmit traffic as encrypted data to the UE 120 for decryption using the MTK at the UE 120.
  • Fig. 6 is provided as an example. Other examples may differ from what is described with regard to Fig. 6.
  • Fig. 7 is a diagram illustrating an example process 700 performed, for example, by a UE, in accordance with the present disclosure.
  • Example process 700 is an example where the UE (e.g., UE 120) performs operations associated with control plane-based communication of MSKs.
  • process 700 may include registering to a cellular network associated with an MBMS transmitting, to the cellular network, a request to join the MBMS (block 710).
  • the UE e.g., using communication manager 140 and/or communication manager 908, depicted in Fig. 9 may register to a cellular network associated with an MBMS transmitting, to the cellular network, a request to join the MBMS, as described above.
  • process 700 may include transmitting, to the cellular network, a request to join the MBMS (block 720).
  • the UE e.g., using communication manager 140 and/or transmission component 904, depicted in Fig. 9 may transmit, to the cellular network, a request to join the MBMS, as described above.
  • process 700 may include receiving, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MSK and MSK identifier pair (block 720).
  • the UE e.g., using communication manager 140 and/or reception component 902, depicted in Fig. 9 may receive, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MSK and MSK identifier pair, as described above.
  • Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • the response comprises one or more of an indication of a validity of the MSK, an MTK associated with the MSK, an MTK identifier associated with the MTK, or an indication of a validity of the MTK.
  • receiving the MTK message comprises one or more of receiving the MTK message via the control plane of the cellular network, or receiving the MTK message via a point-to-multipoint communication.
  • process 700 includes receiving, after receiving the MTK message via the control plane of the cellular network, an updated MTK message via the point-to-multipoint communication.
  • the MTK is encrypted based at least in part on the MSK.
  • process 700 includes decrypting the MTK based at least in part on the MSK.
  • process 700 includes receiving MBMS data via a point-to-multipoint communication and decrypting the MBMS data based at least in part on the MTK. [0141] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process 700 includes receiving, via a point-to-multipoint communication, an indication of an update to the MTK.
  • process 700 includes transmitting, to the cellular network, a request for an updated MTK based at least in part on receiving the indication of the update to the MTK and receiving the updated MTK via the control plane of the cellular network.
  • receiving the response comprises 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.
  • transmitting the request to join the MBMS comprises transmitting the request to join the MBMS via a control plane signaling message.
  • control plane signaling message comprises an uplink NAS message.
  • receiving the response comprises receiving the response via a control plane signaling message.
  • control plane signaling message comprises a downlink NAS message.
  • process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.
  • FIG. 8 is a diagram illustrating an example process 800 performed, for example, by a network entity, in accordance with the present disclosure.
  • Example process 800 is an example where the network entity (e.g., device 1000) performs operations associated with control planebased communication of MSKs.
  • process 800 may include receiving, from a UE and via a cellular network, a request to j oin the MBMS (block 810).
  • the network entity e.g., using communication component 1060, depicted in Fig. 10) may receive, from a UE and via a cellular network, a request to join the MBMS, as described above.
  • process 800 may include transmitting a 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 (block 820).
  • the network entity e.g., using communication component 1060
  • Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below and/or in connection with one or more other processes described elsewhere herein.
  • process 800 includes generating the MSK before transmitting the MSK.
  • generating the MSK before transmitting the MSK comprises generating the MSK based at least in part on one or more of a change of multicast/broadcast membership, a periodicity for updating the MSK, detecting a security event associated with the MSK.
  • the network entity comprises a MBSF.
  • process 800 includes receiving, from an additional network entity, an MTK that is associated with the MSK.
  • process 800 includes transmitting an MTK to an additional network entity.
  • transmitting the MTK to the additional network entity comprises transmitting the MTK to the additional network entity based at least in part on one or more of receiving, from the additional network entity, a request for the MTK, or a periodicity for updating the MTK.
  • process 800 includes generating the MTK before transmitting the MTK.
  • the additional network entity comprises one or more of a BM-SC, an MBSTF or a key distribution entity.
  • process 800 includes transmitting, to the UE, an MTK message via the control plane of the cellular network.
  • the MTK is encrypted based at least in part on the MSK.
  • process 800 includes receiving, from an additional network entity, an updated MTK, transmitting, to the UE, the updated MTK via the control plane of the cellular network, or a combination thereof.
  • process 800 includes transmitting, to an additional network entity, the updated MTK.
  • process 800 includes transmitting, to the UE, the updated MTK via the control plane of the cellular network.
  • transmitting the updated MTK via the control plane of the cellular network comprises transmitting the updated MTK based at least in part on reception of a request from the UE, or transmitting the updated MTK to the UE based at least in part on the UE joining the MBMS.
  • process 800 includes receiving, from an additional network entity, an indication to update the MSK, and transmitting, to the additional network entity, an updated MSK.
  • process 800 includes transmitting, to the UE, the updated MSK.
  • transmitting the MSK to the UE via the control plane of the cellular network comprises 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.
  • process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 8. Additionally, or alternatively, two or more of the blocks of process 800 may be performed in parallel.
  • Fig. 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.
  • the apparatus 900 includes a reception component 902 and a transmission component 904, which may be in communication with one another (for example, via one or more buses and/or one or more other components).
  • the apparatus 900 may communicate with another apparatus 906 (such as a UE, a base station, or another wireless communication device) using the reception component 902 and the transmission component 904.
  • the apparatus 900 may include a communication manager 908 (e.g., the communication manager 140).
  • the apparatus 900 may be configured to perform one or more operations described herein in connection with Figs. 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 Fig. 7.
  • the apparatus 900 and/or one or more components shown in Fig. 9 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 9 may be implemented within one or more components described in connection with Fig. 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 a processor to perform the functions or operations of the component.
  • the reception component 902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 906.
  • the reception component 902 may provide received communications to one or more other components of the apparatus 900.
  • the reception component 902 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 900.
  • the reception 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 the UE described in connection with Fig. 2.
  • the transmission component 904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 906.
  • one or more other components of the apparatus 900 may generate communications and may provide the generated communications to the transmission component 904 for transmission to the apparatus 906.
  • the transmission component 904 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 906.
  • the transmission 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 the UE described in connection with Fig. 2. In some aspects, the transmission component 904 may be co-located with the reception component 902 in a transceiver.
  • the communication manager 908 may register to a cellular network associated with an MBMS.
  • the transmission component 904 may transmit, to the cellular network, a request to join the MBMS.
  • the reception component 902 may receive, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MBMS service key (MSK) and MSK identifier pair.
  • MSK MBMS service key
  • the reception component 902 may receive, after receiving the response via the control plane of the cellular network, an updated response via the point-to-multipoint communication.
  • the communication manager 908 and/or the reception component 902 may decrypt the MBMS traffic key based at least in part on the MSK.
  • the reception component 902 may receive MBMS data via a point-to-multipoint communication.
  • the communication manager 908 and/or the reception component 902 may decrypt the MBMS data based at least in part on the MBMS traffic key.
  • the reception component 902 may receive, via a point-to-multipoint communication, an indication of an update to the MBMS traffic key.
  • the transmission component 904 may transmit, to the cellular network, a request for an updated MBMS traffic key based at least in part on receiving the indication of the update to the MBMS traffic key.
  • the reception component 902 may receive the updated MBMS traffic key via the control plane of the cellular network.
  • Fig. 9 The number and arrangement of components shown in Fig. 9 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 9. Furthermore, two or more components shown in Fig. 9 may be implemented within a single component, or a single component shown in Fig. 9 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 9 may perform one or more functions described as being performed by another set of components shown in Fig. 9.
  • Fig. 10 is a diagram of example components of a device 1000, which may correspond to the network entity 615 (e.g., the MBSF), one or more of the one or more cellular network devices 610, the BM-SC 620, the key management function 625, and/or the key distribution function 630.
  • the network entity 615 e.g., the MBSF
  • the network entity 615 e.g., the MBSF
  • the key management function 625, and/or the key distribution function 630 include one or more devices 1000 and/or one or more components of device 1000.
  • 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.
  • Bus 1010 includes one or more components that enable wired and/or wireless communication among the components of device 1000. Bus 1010 may couple together two or more components of Fig. 10, such as via operative coupling, communicative coupling, electronic coupling, and/or electric coupling.
  • 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.
  • Processor 1020 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 1020 includes one or more processors capable of being programmed to perform one or more operations or processes described elsewhere herein.
  • Memory 1030 includes volatile and/or nonvolatile memory.
  • memory 1030 may include random access memory (RAM), read only memory (ROM), a hard disk drive, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory).
  • RAM random access memory
  • ROM read only memory
  • Hard disk drive and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory).
  • Memory 1030 may include internal memory (e.g., RAM, ROM, or a hard disk drive) and/or removable memory (e.g., removable via a universal serial bus connection).
  • Memory 1030 may be a non-transitory computer-readable medium.
  • Memory 1030 stores information, instructions, and/or software (e.g., one or more software applications) related to the operation of device 1000.
  • memory 1030 includes one or more memories that are coupled to one or more processors (e.g., processor 1020), such as via bus 1010.
  • Input component 1040 enables device 1000 to receive input, such as user input and/or sensed input.
  • input component 1040 may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and/or an actuator.
  • Output component 1050 enables device 1000 to provide output, such as via a display, a speaker, and/or a light-emitting diode.
  • Communication component 1060 enables device 1000 to communicate with other devices via a wired connection and/or a wireless connection.
  • communication component 1060 may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.
  • Device 1000 may perform one or more operations or processes described herein.
  • a non-transitory computer-readable medium e.g., memory 1030
  • Processor 1020 may execute the set of instructions to perform one or more operations or processes described herein.
  • 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.
  • hardwired circuitry is used instead of or in combination with the instructions to perform one or more operations or processes described herein.
  • processor 1020 may be configured to perform one or more operations or processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software. [0189] The number and arrangement of components shown in Fig. 10 are provided as an example. Device 1000 may include additional components, fewer components, different components, or differently arranged components than those shown in Fig. 10. Additionally, or alternatively, a set of components (e.g., one or more components) of device 1000 may perform one or more functions described as being performed by another set of components of device 1000.
  • Aspect 1 A method of wireless communication performed by a user equipment (UE), comprising: registering to a cellular network associated with a multimedia broadcast/multicast service (MBMS); transmitting, to the cellular network, a request to join the MBMS; and receiving, from the cellular network and based at least in part on being registered with the cellular network, a response that indicates an MBMS service key (MSK) and MSK identifier pair.
  • MBMS multimedia broadcast/multicast service
  • MSK MBMS service key
  • Aspect 2 The method of Aspect 1, wherein the response comprises one or more of: an indication of a validity of the MSK, an MBMS traffic key (MTK) associated with the MSK, an MTK identifier associated with the MTK, or an indication of a validity of the MBMS traffic key.
  • MTK MBMS traffic key
  • MTK MTK identifier
  • Aspect 3 The method of Aspect 2, wherein receiving the response comprises one or more of: receiving the response via the control plane of the cellular network, or receiving the response via a point-to-multipoint communication.
  • Aspect 4 The method of Aspect 3, further comprising: receiving, after receiving the response via the control plane of the cellular network, an updated response via the point-to- multipoint communication.
  • Aspect 5 The method of Aspect 2, wherein the MBMS traffic key is encrypted based at least in part on the MSK.
  • Aspect 6 The method of any of Aspects 2-5, further comprising: decrypting the MBMS traffic key based at least in part on the MSK.
  • Aspect 7 The method of any of Aspects 2-6, further comprising: receiving MBMS data via a point-to-multipoint communication; and decrypting the MBMS data based at least in part on the MBMS traffic key.
  • Aspect 8 The method of any of Aspects 2-7, further comprising: receiving, via a point-to-multipoint communication, an indication of an update to the MBMS traffic key.
  • Aspect 9 The method of Aspect 8, further comprising: transmitting, to the cellular network, a request for an updated MBMS traffic key based at least in part on receiving the indication of the update to the MBMS traffic key; and receiving the updated MBMS traffic key via the control plane of the cellular network.
  • Aspect 10 The method of any of Aspects 1-9, wherein receiving the MSK from the MBSF via the control plane of the cellular network comprises receiving the response comprises 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.
  • Aspect 11 The method of any of Aspects 1-10, wherein transmitting the request to join the MBMS comprises: transmitting the request to join the MBMS via a control plane signaling message.
  • Aspect 12 The method of Aspect 11, wherein the control plane signaling message comprises an uplink non-access stratum (NAS) message.
  • NAS uplink non-access stratum
  • Aspect 13 The method of any of Aspects 1-12, wherein receiving the response comprises: receiving the response via a control plane signaling message.
  • Aspect 14 The method of Aspect 13, wherein the control plane signaling message comprises a downlink non-access stratum (NAS) message.
  • NAS downlink non-access stratum
  • a method of wireless communication performed by a network entity comprising: receiving, from a user equipment (UE) and via a cellular network, a request to join the MBMS; and transmitting a multimedia broadcast/multicast service (MBMS) service key (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.
  • MBMS multimedia broadcast/multicast service
  • Aspect 16 The method of Aspect 15, further comprising: generating the MSK before transmitting the MSK.
  • Aspect 17 The method of Aspect 16, wherein generating the MSK before transmitting the MSK comprises generating the MSK based at least in part on one or more of: a change of multicast/broadcast membership, a periodicity for updating the MSK, detecting a security event associated with the MSK.
  • Aspect 18 The method of any of Aspects 15-17, wherein the network entity comprises a multicast/broadcast service function (MBSF).
  • MBSF multicast/broadcast service function
  • Aspect 19 The method of any of Aspects 15-18, further comprising: receiving, from an additional network entity, an MBMS traffic key that is associated with the MSK.
  • Aspect 20 The method of any of Aspects 15-18, further comprising: transmitting an MBMS traffic key to an additional network entity.
  • Aspect 21 The method of Aspect 20, wherein transmitting the MBMS traffic key to the additional network entity comprises: transmitting the MBMS traffic key to the additional network entity based at least in part on one or more of: receiving, from the additional network entity, a request for the MBMS traffic key, or a periodicity for updating the MBMS traffic key.
  • Aspect 22 The method of Aspect 20, further comprising: generating the MBMS traffic key before transmitting the MBMS traffic key.
  • Aspect 23 The method of Aspect 20, wherein the additional network entity comprises one or more of: a broadcast/multicast service center (BM-SC), a MBSTF or a key distribution entity.
  • BM-SC broadcast/multicast service center
  • MBSTF MBSTF
  • key distribution entity a broadcast/multicast service center
  • Aspect 24 The method of Aspect 15, further comprising: transmitting, to the UE, an response via the control plane of the cellular network.
  • Aspect 25 The method of Aspect 24, wherein the MBMS traffic key is encrypted based at least in part on the MSK.
  • Aspect 26 The method of any of Aspects 24-25, further comprising: receiving, from an additional network entity, an updated MBMS traffic key; and transmitting, to the UE, the updated MBMS traffic key via the control plane of the cellular network.
  • Aspect 27 The method of Aspect 26, further comprising: transmitting, to an additional network entity, the updated MBMS traffic key.
  • Aspect 28 The method of Aspect 26, further comprising: transmitting, to the UE, the updated MBMS traffic key via the control plane of the cellular network.
  • Aspect 29 The method of Aspect 28, wherein transmitting the updated MBMS traffic key via the control plane of the cellular network comprises: transmitting the updated MBMS traffic key based at least in part on reception of a request from the UE, or transmitting the updated MBMS traffic key to the UE based at least in part on the UE joining the MBMS.
  • Aspect 30 The method of any of Aspects 15-29, further comprising: receiving, from an additional network entity, an indication to update the MSK; and transmitting, to the additional network entity, an updated MSK.
  • Aspect 31 The method of Aspect 30, further comprising: transmitting, to the UE, the updated MSK.
  • Aspect 32 The method of any of Aspects 15-30, wherein transmitting the MSK to the UE via the control plane of the cellular network comprises 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.
  • Aspect 33 An apparatus for wireless communication at a device, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method of one or more of Aspects 1-32.
  • 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 perform the method of one or more of Aspects 1-32.
  • Aspect 35 An apparatus for wireless communication, comprising at least one means for performing the method of one or more of Aspects 1-32.
  • Aspect 36 A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method of one or more of Aspects 1-32.
  • Aspect 37 A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-32.
  • the term “component” is intended to be broadly construed as hardware and/or a combination of hardware and software.
  • “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and/or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • a “processor” is implemented in hardware and/or a combination of hardware and software. It will be apparent that systems and/or methods described herein may be implemented in different forms of hardware and/or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and/or methods is not limiting of the aspects. Thus, the operation and behavior of the systems and/or methods are described herein without reference to specific software code, since those skilled in the art will understand that software and hardware can be designed to implement the systems and/or methods based, at least in part, on the description herein.
  • satisfying a threshold may, depending on the context, 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, or the like.
  • a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (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 ordering of a, b, and c).
  • the terms “has,” “have,” “having,” or the like are intended to be open-ended terms that do not limit an element that they modify (e.g., an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or,” unless explicitly stated otherwise (e.g., if used in combination with “either” or “only one of’).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation portent d'une manière générale sur la communication sans fil. Selon certains aspects, un équipement utilisateur (UE) peut s'enregistrer auprès d'un réseau cellulaire associé à un service multimédia de diffusion/multidiffusion (MBMS). L'UE peut transmettre, au réseau cellulaire, une demande pour rejoindre le MBMS. L'UE peut recevoir, en provenance du réseau cellulaire et sur la base, au moins en partie, de son enregistrement auprès du réseau cellulaire, une réponse qui indique une paire clé de service MBMS (MSK) et identifiant de MSK. La divulgation concerne en outre de nombreux autres aspects.
PCT/US2022/042227 2021-10-20 2022-08-31 Communication basée sur un plan de commande de clés de service de service de diffusion/multidiffusion multimédia WO2023069199A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202280069467.4A CN118140503A (zh) 2021-10-20 2022-08-31 多媒体广播/多播服务服务密钥的基于控制平面的通信
KR1020247009936A KR20240087744A (ko) 2021-10-20 2022-08-31 멀티미디어 브로드캐스트/멀티캐스트 서비스 서비스 키들의 제어 평면 기반 통신

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202163262781P 2021-10-20 2021-10-20
US63/262,781 2021-10-20
US17/653,022 2022-03-01
US17/653,022 US11785427B2 (en) 2021-10-20 2022-03-01 Control plane-based communication of multimedia broadcast/multicast service service keys

Publications (1)

Publication Number Publication Date
WO2023069199A1 true WO2023069199A1 (fr) 2023-04-27

Family

ID=83598570

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/042227 WO2023069199A1 (fr) 2021-10-20 2022-08-31 Communication basée sur un plan de commande de clés de service de service de diffusion/multidiffusion multimédia

Country Status (1)

Country Link
WO (1) WO2023069199A1 (fr)

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; 3G Security; Security of Multimedia Broadcast/Multicast Service (MBMS) (Release 16)", vol. SA WG3, no. V16.0.0, 10 July 2020 (2020-07-10), pages 1 - 75, XP051924921, Retrieved from the Internet <URL:ftp://ftp.3gpp.org/Specs/archive/33_series/33.246/33246-g00.zip 33246-g00.doc> [retrieved on 20200710] *
PHILIPS INTERNATIONAL B V: "Update in Solution#9", vol. SA WG3, no. e-meeting; 20210927 - 20210930, 20 September 2021 (2021-09-20), XP052062995, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG3_Security/TSGS3_104-e_ad_hoc/Docs/S3-213542.zip S3-213542 - Update in Solution #9.doc> [retrieved on 20210920] *
PHILIPS INTERNATIONAL B V: "Update Solution 11 for reduced key update overhead", vol. SA WG3, no. e-meeting; 20210816 - 20210827, 9 August 2021 (2021-08-09), XP052063416, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG3_Security/TSGS3_104e/Docs/S3-212765.zip S3-212765 - MBS - Update solution 11.doc> [retrieved on 20210809] *
ZTE: "Update the solution #12", vol. SA WG3, no. e-meeting; 20210816 - 20210827, 9 August 2021 (2021-08-09), XP052063212, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_sa/WG3_Security/TSGS3_104e/Docs/S3-212555.zip S3-212555 Update the solution #12.doc> [retrieved on 20210809] *

Similar Documents

Publication Publication Date Title
WO2021041062A1 (fr) Sécurité de diffusion/multidiffusion 5g
US11671824B2 (en) 5G broadcast/multicast security key refresh
US11785427B2 (en) Control plane-based communication of multimedia broadcast/multicast service service keys
CN115004741B (zh) 用于网络切片选择的基于证书的应用描述符
US20230050764A1 (en) Hybrid 5g media streaming
US20220360966A1 (en) Secure link establishment
WO2022232740A1 (fr) Association de dispositifs avec des points d&#39;accès à l&#39;aide de justificatifs d&#39;identité
US20230292226A1 (en) Method and Apparatus for Media Application Function Exposure Functionality
WO2023069199A1 (fr) Communication basée sur un plan de commande de clés de service de service de diffusion/multidiffusion multimédia
US20230052505A1 (en) Multicast-broadcast user service architecture
US20220353683A1 (en) Associating devices with access points using credentials
US20230319551A1 (en) Security protection of user equipment (ue)-to-ue relay discovery
US11985498B2 (en) Secure sidelink communications
US20240155338A1 (en) Key hierarchies in trusted networks with 5g networks
EP4385172A1 (fr) Architecture de service d&#39;utilisateur de multidiffusion-diffusion
US20240073777A1 (en) Mobile station relaying verification
US20230247445A1 (en) Multiple path support for layer 3 user equipment to network relay
WO2024026664A1 (fr) Réassociation entre une station et un point d&#39;accès
WO2021138880A1 (fr) Communication de diffusion/multidiffusion en mode mixte
WO2022236326A1 (fr) Établissement de liaison sécurisée
EP4385195A1 (fr) Diffusion en continu multimédia 5g hybride
WO2023196100A1 (fr) Protection de sécurité d&#39;une découverte de relais ue-ue d&#39;équipement utilisateur
CN117795907A (zh) 多播-广播用户服务架构
TW202126012A (zh) 用於解調參考訊號通訊的擴展解調參考訊號加擾識別符

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22786158

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2401001747

Country of ref document: TH

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112024006903

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2022786158

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022786158

Country of ref document: EP

Effective date: 20240521