Multicast and broadband service communication with mobile terminal small data transmission

Abstract

The present invention relates to Multicast and Broadband Service Communication with Mobile Terminal Small Data Transmission. The method comprises: receiving configuration information of a plurality of multicast MBS sessions and configuration information of a plurality of broadcast MBS sessions; receiving a paging transmission comprising at least one paging record, the paging record comprising an MT-SDT indicator and a paging group list comprising a plurality of MBS session identifiers; initiating a RRC connection resume procedure based on the at least one paging record, the resume cause being set to indicate MT-SDT in case that the conditions for receiving data in RRC_INACTIVE state are determined to be fulfilled and all MBS sessions indicated by the MBS session identifiers comprised in the paging group list are configured to receive data in RRC_INACTIVE state; and the resume cause being set to indicate MT-Access in case that the conditions for receiving data in RRC_INACTIVE state are determined to be not fulfilled or not all MBS sessions indicated by the MBS session identifiers comprised in the paging group list are configured to receive data in RRC_INACTIVE state.

Description

Technical Field

[0001] This application generally relates to small data transmissions of wireless devices. Background Technology

[0002] As wireless devices send and receive larger volumes of data, improving the efficiency of data communication becomes increasingly important. In many cases, it may be desirable to transmit information in the RRC_INACTIVE state. However, performing such communication for multicast and broadcast services (MBS) requires specific configuration and operation. Summary of the Invention

[0003] Various aspects of the invention are set forth in the claims.

[0004] One or more embodiments may provide an apparatus, a computer-readable medium, a non-transitory computer-readable medium, a computer program product, and / or a method for a user equipment (UE) to perform, comprising: receiving configuration information for multiple multicast multicast and broadcast service (MBS) sessions configured to receive data in an RRC_INACTIVE state, and configuration information for multiple broadcast MBS sessions not configured to receive data in an RRC_INACTIVE state; receiving a paging transmission when the UE is in an RRC_INACTIVE state, the paging transmission including at least one paging record, the paging record including: a UE identity matching a Radio Network Temporary Identifier (RNTI) of the UE, a Mobile Terminal Small Data Transfer (MT-SDT) indicator, and a paging group list including multiple MBS session identifiers; determining whether conditions for receiving data in an RRC_INACTIVE state are met; and determining the M included in the paging group list. Whether all MBS sessions indicated by the BS session identifier are configured to receive data in the RRC_INACTIVE state; initiating an RRC connection recovery procedure based on at least one paging record, wherein the recovery reason is set to indicate MT-SDT in the following cases: the conditions for receiving data in the RRC_INACTIVE state are determined to be met, and all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state; and initiating an RRC connection recovery procedure based on at least one paging record, wherein the recovery reason is set to indicate mobile terminal access (MT-Access) in the following cases: the conditions for receiving data in the RRC_INACTIVE state are determined to be unmet, or not all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state.

[0005] An apparatus includes at least one processor and at least one memory, the memory including machine-readable instructions that, when executed, cause the apparatus to: receive configuration information for multiple multicast and broadcast service (MBS) sessions configured to receive data in an RRC_INACTIVE state, and configuration information for multiple broadcast MBS sessions not configured to receive data in an RRC_INACTIVE state; when a UE is in an RRC_INACTIVE state, receive a paging transmission, the paging transmission including at least one paging record, the paging record including: a UE identity matching the UE's RNTI, a Mobile Terminal Small Data Transfer (MT-SDT) indicator, and a paging group list including multiple MBS session identifiers; determine whether conditions for receiving data in an RRC_INACTIVE state are met; and determine the MBS session identifiers indicated in the paging group list. Whether an MBS session is configured to receive data in the RRC_INACTIVE state; initiating an RRC connection recovery procedure based on at least one paging record, wherein the recovery reason is set to indicate MT-SDT in the following cases: the conditions for receiving data in the RRC_INACTIVE state are determined to be met, and all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state; initiating an RRC connection recovery procedure based on at least one paging record, wherein the recovery reason is set to indicate mobile terminal access (MT-Access) in the following cases: the conditions for receiving data in the RRC_INACTIVE state are determined to be unmet, or not all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state.

[0006] In at least one exemplary embodiment, each multicast MBS session and each broadcast MBS session are identified by an MBS session identifier, and determining whether all MBS sessions indicated by the MBS session identifiers included in the paging group list are configured to receive data in the RRC_INACTIVE state includes: determining whether each MBS session identifier included in the paging group list identifies a multicast MBS session configured to receive data in the RRC_INACTIVE state.

[0007] In at least one example embodiment, the MBS session identifier is a Temporary Mobile Group Identity (TMGI).

[0008] In at least one example embodiment, the paging transmission is a paging message received from a base station.

[0009] In at least one example embodiment, the base station is a gNodeB (gNB).

[0010] In at least one example embodiment, the paging transmission is a message transmission sidelink message received from another UE.

[0011] In at least one example embodiment, the other UE is a Layer 2 (L2) UE-to-Network (U2N) relay UE.

[0012] In at least one example embodiment, the RNTI of the UE is a fully inactive-RNTI (I-RNTI).

[0013] In at least one example embodiment, determining whether the conditions for receiving data in the RRC_INACTIVE state are met includes: the Media Access Control (MAC) entity determining whether the conditions for initiating a Small Data Transfer (SDT) procedure are met.

[0014] In at least one example embodiment, determining whether the conditions for initiating an SDT procedure are met includes determining whether the RSRP of the downlink path loss reference is higher than the configured RSRP threshold for SDT.

[0015] In at least one example embodiment, determining that the conditions for initiating the SDT procedure are met includes: determining that the RSRP of the downlink path loss reference is higher than the configured RSRP threshold for SDT.

[0016] In at least one example embodiment, determining that the conditions for initiating the SDT procedure are not met includes: determining that the RSRP of the downlink path loss reference is not higher than the configured RSRP threshold of the SDT.

[0017] In at least one example embodiment, configuration information for multiple multicast MBS sessions is received in an MBS multicast configuration message, and configuration information for multiple broadcast MBS sessions is received in an MBS broadcast configuration message.

[0018] In at least one example embodiment, the MBS multicast configuration message and the MBS broadcast configuration message are different from each other.

[0019] In at least one example embodiment, the MBS multicast configuration message includes information that cannot be included in the MBS broadcast configuration message.

[0020] In at least one example embodiment, a subset of parameters included in the MBS multicast configuration message exists in the MBS broadcast configuration message.

[0021] In at least one example embodiment, the configuration information for multiple multicast MBS sessions includes a list of MBS session information for multicast, and the configuration information for multiple broadcast MBS sessions is a list of MBS session information for broadcast.

[0022] In at least one example embodiment, the MBS multicast configuration message includes a list of MBS session information for multicasting, and the MBS broadcast configuration message includes a list of MBS session information for broadcasting.

[0023] In at least one example embodiment, the list of MBS session information used for broadcasting is the MBS-SessionInfoList information element.

[0024] In at least one example embodiment, configuration information for multiple multicast MBS sessions and configuration information for multiple broadcast MBS sessions are received in a public MBS configuration message.

[0025] In at least one example embodiment, the configuration information for multiple multicast MBS sessions includes a list of MBS session information for multicast, and the configuration information for multiple broadcast MBS sessions is a list of MBS session information for broadcast.

[0026] In at least one example embodiment, the list of MBS session information used for broadcasting is the MBS-SessionInfoList information element.

[0027] In at least one example embodiment, configuration information for multiple multicast MBS sessions and configuration information for multiple broadcast MBS sessions are included in a public MBS session information list.

[0028] In at least one example embodiment, the configuration information of multiple multicast MBS sessions includes multiple public MBS session information elements included in the public MBS session information list, and the multiple broadcast MBS sessions are different multiple public MBS session information elements included in the public MBS session information list.

[0029] In at least one example embodiment, multiple broadcast MBS sessions are multiple public MBS session information elements included in the public MBS session information list, which are different from the public MBS session information elements of multicast MBS sessions.

[0030] In at least one example embodiment, the public MBS session information list is the MBS-SessionInfoList information element.

[0031] In at least one example embodiment, the public MBS session information element is the MBS-SessionInfo information element.

[0032] In at least one example embodiment, the configuration information for multiple multicast MBS sessions corresponds to a public MBS session information record, which includes optional parameters specific to multicast MBS. In at least one example embodiment, the configuration information for multiple broadcast MBS sessions corresponds to a public MBS session information record that does not include optional parameters specific to multicast MBS. Attached Figure Description

[0033] To gain a more complete understanding of the embodiments of the present invention, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein:

[0034] Figure 1 This is a block diagram of an apparatus according to at least one example embodiment.

[0035] Figure 2 This is a block diagram of a wireless communication system according to at least one example embodiment.

[0036] Figure 3 This is a diagram of a protocol stack 300 according to at least one example embodiment.

[0037] Figure 4 This is an interaction diagram illustrating activities associated with Mobile Terminal Small Data Transmission (MT-SDT) according to at least one example embodiment, and

[0038] Figure 5 It is a flowchart illustrating the activities associated with initiating communication, based on at least one example embodiment. Detailed Implementation

[0039] By referring to the attached figures Figures 1 to 5 To understand the embodiments of the present invention and its potential advantages.

[0040] Some embodiments will be described more fully below with reference to the accompanying drawings, which illustrate some, but not all, embodiments. Various embodiments of the invention may be implemented in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided to enable this disclosure to meet applicable legal requirements. The same reference numerals throughout refer to the same elements. As used herein, the terms “data,” “content,” “information,” and similar terms are used interchangeably to refer to data that can be transmitted, received, and / or stored according to embodiments of the invention. Therefore, the use of any such terms should not be considered as limiting the spirit and scope of the embodiments of the invention.

[0041] Furthermore, as used herein, the term "circuit" means (a) a hardware circuit implementation only (e.g., an implementation in analog and / or digital circuitry); (b) a combination of a circuit and one or more computer program products, including software and / or firmware instructions stored on one or more computer-readable storage media, which work together to enable a device to perform one or more functions described herein; and (c) a circuit, such as, for example, one or more microprocessors or a portion thereof, which requires software or firmware to operate, even if the software or firmware is not physically present. This definition of "circuit" applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuit" also includes an implementation comprising one or more processors and / or portions thereof, along with accompanying software and / or firmware. As another example, the term "circuit" as used herein also includes, for example, baseband integrated circuits or application processor integrated circuits for mobile phones, or similar integrated circuits in servers, cellular network devices, other network devices, and / or other computing devices.

[0042] As defined herein, a “non-transitory computer-readable medium” referring to a physical medium (e.g., a volatile or non-volatile storage device) can be distinguished from a “transitory computer-readable medium” referring to an electromagnetic signal.

[0043] Figure 1 This is a block diagram illustrating an apparatus (e.g., electronic device 100) according to at least one example embodiment. However, it should be understood that the electronic device shown and described below is merely an illustration of electronic devices from which embodiments of the invention may benefit, and therefore should not be construed as limiting the scope of the invention. While electronic device 100 is shown and will be described below for illustrative purposes, other types of electronic devices can readily employ embodiments of the invention. Electronic device 100 may be a network node (e.g., user equipment (UE) or base station), or may be a personal digital assistant (PDA), pager, mobile computer, desktop computer, television, gaming device, laptop computer, tablet computer, media player, camera, video recorder, mobile phone, global positioning system (GPS) device, automobile, kiosk, electronic table, and / or any other type of electronic system. Furthermore, the apparatus of at least one example embodiment need not be the entire electronic device, but may be a component or group of components of the electronic device in other example embodiments. For example, the apparatus may be an integrated circuit, a set of integrated circuits, etc.

[0044] Furthermore, the device can readily employ embodiments of the invention, regardless of its intended purpose of providing mobility. In this regard, although embodiments of the invention can be described in conjunction with mobile applications, it should be understood that embodiments of the invention can be utilized in conjunction with a variety of other applications both within and outside the mobile communications industry. For example, the device can be at least part of a non-portable device, such as a large-screen television, electronic table, information kiosk, automobile, etc.

[0045] In at least one example embodiment, electronic device 100 includes a processor 110 and a memory 140. The processor 110 can be any type of processor, controller, embedded controller, processor core, etc. In at least one example embodiment, the processor 110 utilizes computer program code to cause the device to perform one or more actions. The memory 140 may include volatile memory (e.g., volatile random access memory (RAM) including a buffer for temporary data storage) and / or other memory (e.g., non-volatile memory, which may be embedded and / or removable). Non-volatile memory may include EEPROM, flash memory, etc. The memory 140 may store any one of multiple pieces of information and data. Electronic device 100 can use this information and data to implement one or more functions of electronic device 100, such as the functions described herein. In at least one example embodiment, the memory 140 includes computer program code such that the memory and the computer program code are configured to work with the processor to cause the device to perform one or more actions described herein.

[0046] Electronic device 100 may also include transceiver 120. In at least one example embodiment, transceiver 120 is coupled to one or more antennas 130. In at least one example embodiment, processor 110 provides signals to and / or receives signals from transceiver 120. Signals may include signaling information according to a communication interface standard, user voice, received data, user-generated data, etc. Transceiver 120 may operate using one or more air interface standards, communication protocols, modulation types, and access types. For example, the electronic transceiver 120 can be based on second-generation (2G) wireless communication protocols IS-136 (Time Division Multiple Access (TDMA)), Global System for Mobile Communications (GSM) and IS-95 (Code Division Multiple Access (CDMA)), third-generation (3G) wireless communication protocols (such as Universal Mobile Telecommunications System (UMTS), CDMA2000, Wideband CDMA (WCDMA) and Time Division Synchronous CDMA (TD-SCDMA)), and / or fourth-generation (4G) wireless communication protocols (such as LTE), fifth-generation (5G) protocols (such as New Radio (NR)), wireless networking protocols (such as 802.11, short-range radio protocols, such as Bluetooth), etc.

[0047] Processor 110 may include components such as circuitry for implementing audio, video, communication, navigation, logic functions, and other functions required for implementing embodiments of the invention, including one or more functions as described herein. For example, processor 110 may include components such as digital signal processor devices, microprocessor devices, various analog-to-digital converters, digital-to-analog converters, processing circuitry, and other support circuitry for performing various functions, including one or more functions as described herein. The device may perform control and signal processing functions of electronic device 100 among these devices, depending on their respective capabilities. Therefore, processor 110 may include the ability to encode and interleave messages and data prior to modulation and transmission. Processor 110 may additionally include an internal voice encoder and may include an internal data modem. Furthermore, processor 110 may include the ability to operate one or more software programs, which may be stored in memory, and in particular, enable processor 110 to implement at least a portion of an embodiment, including one or more functions as described herein. For example, processor 110 may operate a connectivity program, such as a conventional internet browser. The connection program allows electronic device 100 to send and receive Internet content, such as location-based content and / or other web page content, according to protocols such as Transmission Control Protocol (TCP), Internet Protocol (IP), User Datagram Protocol (UDP), Internet Message Access Protocol (IMAP), Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), etc.

[0048] Electronic device 100 may include a user interface for providing output and / or receiving input. Electronic device 100 may include output devices, such as audio output devices like ringers, headphones, and speakers; haptic output devices like vibration transducers; electronically deformable surfaces; electronically deformable structures; and visual output devices like displays and / or lights. Electronic device may include input devices, such as light sensors, proximity sensors, microphones, touch sensors, force sensors, buttons, keypads, motion sensors, magnetic field sensors, cameras, etc. In at least one example embodiment, the device receives an input indication. The device may receive the indication from sensors, drivers, separate devices, etc. The information indicating the input may include information that conveys the indication of input, the aspect of the indication of input, information indicating the occurrence of the input, etc.

[0049] Figure 2An example of a wireless communication system 200 according to at least one example embodiment is shown. The wireless communication system 200 includes one or more base stations 202, a core network 203, and one or more user equipments (UEs), such as UE 201 and / or UE 204. In some examples, the wireless communication system 200 may be a Long Term Evolution (LTE), LTE-Advanced (LTE-A) network, a New Radio (NR) network, etc. In some cases, the wireless communication system 200 may support enhanced broadband communication, ultra-reliable (i.e., mission-critical) communication, low-latency communication, and communication with low-cost and low-complexity devices. To improve the reliability of some communications (e.g., Ultra-Reliable Low-Latency Communication (URLLC) packets), the wireless communication system 200 may be configured to generate and transmit duplicate packets. In such a duplication system, the transmitting device (e.g., base station 202, UE 201, or UE 204) may duplicate packets. The original packets and duplicate packets may be transmitted to the receiving device (e.g., base station 202, UE 201, or UE 204). Transmitting multiple packets containing the same information can increase the likelihood that the receiving device receives information included in multiple packets.

[0050] One or more base stations 202 can wirelessly communicate with one or more UEs (e.g., UE 201 or UE 204) via one or more base station antennas. Each base station 202 can provide communication coverage for its respective geographic coverage area. The communication link in the wireless communication system 200 can include uplink transmission from the UE to the base station 202, or downlink transmission from the base station 202 to the UE. Depending on various technologies, control information and data can be multiplexed on the uplink channel or the downlink channel. For example, time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM technologies can be used to multiplex control information and data on the downlink channel. In some examples, control information transmitted during the transmission time interval (TTI) of the downlink channel can be distributed in a cascaded manner between different control areas (e.g., between a common control area and one or more UE-specific control areas).

[0051] Multiple UEs can be distributed across 200 locations in a wireless communication system, and each UE can be fixed or mobile. A UE can also be referred to as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. A UE can also be a cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, tablet computer, laptop computer, cordless phone, personal electronic device, handheld device, personal computer, wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, machine-type communication (MTC) device, appliance, automobile, etc.

[0052] In some cases, a UE may also be able to communicate directly with other UEs using sidelink communication (e.g., using peer-to-peer (P2P) or device-to-device (D2D) protocols). For example, Figure 2 An example of this communication between UE 201 and UE 204 is provided. One or more of a group of UEs utilizing sidelink communication may be within the cell's coverage area. Other UEs in the group may be outside the cell's coverage area, or in other cases, unable to receive transmissions from base station 202. In some cases, the group of UEs communicating via sidelink communication may utilize a one-to-many (1:M) system, where each UE transmits to every other UE in the group. In some cases, base station 202 assists in scheduling resources for sidelink communication. In other cases, sidelink communication is performed independently of base station 202.

[0053] In some cases, UE 204 can operate as a relay UE for UE 201. For example, instead of communicating directly with base station 202, UE 204 can be configured to operate as a relay, allowing UE 201 to communicate with base station 202 directly through UE 204. For example, UE 204 can operate as a Layer 2 (L2) UE-to-Network (U2N) relay.

[0054] Some UEs (such as MTC or IoT devices) can be low-cost or low-complexity devices that provide automated communication between machines, i.e., machine-to-machine (M2M) communication. M2M or MTC can refer to data communication technologies that allow devices to communicate with each other or with a base station without human intervention. For example, M2M or MTC can refer to communication from devices that integrate sensors or instruments to measure or capture information and relay that information to a central server or application, which can then utilize that information or present it to people interacting with the program or application. Some UEs can be designed to collect information or automate machine behavior. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0055] In some cases, MTC devices can operate at reduced peak rates using half-duplex (one-way) communication. MTC devices can also be configured to enter a power-saving "deep sleep" mode when not engaged in active communication. In some cases, MTC or IoT devices can be designed to support mission-critical functions, and the wireless communication system can be configured to provide ultra-reliable communication for these functions.

[0056] Base station 202 can communicate with core network 203 and one or more other base stations. For example, the base station can interface with core network 203 via a backhaul link (e.g., S1, etc.). Base stations can communicate with each other directly or indirectly (e.g., via core network 203) via other backhaul links (e.g., X2, etc.). The base station can perform radio configuration and scheduling for communicating with the UE, or it can operate under the control of a base station controller (not shown). In some examples, base station 202 can be a macro cell, small cell, hotspot, etc. The base station can also be referred to as an evolved NodeB (NB), such as eNB, gNB, etc.

[0057] Base station 202 can connect to core network 203 via the S1 interface. The core network can be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME can be a control node handling signaling between UE 201 and the EPC. All user Internet Protocol (IP) packets can be transmitted through the S-GW, which itself can connect to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW can connect to network operator IP services. Operator IP services may include the Internet, intranets, IP Multimedia Subsystem (IMS), and packet-switched (PS) streaming services.

[0058] Core network 203 provides user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. At least some network devices (e.g., base station 202) may include sub-components, such as access network entities, which may be examples of access node controllers (ANCs). Each access network entity can communicate with multiple UEs through multiple other access network transport entities, each of which may be an example of a smart radio headend or a transmit / receive point (TRP). In some configurations, the various functions of each access network entity or base station may be distributed across various network devices (e.g., radio headends and access network controllers) or consolidated into a single network device (e.g., base station 202).

[0059] Wireless communication system 200 can operate in the ultra-high frequency (UHF) frequency region using a frequency band from 700 MHz to 2600 MHz (2.6 GHz), but some networks (e.g., wireless local area networks (WLANs)) can use frequencies up to 4 GHz. This region can also be called the decimeter band because the wavelength ranges from approximately 1 decimeter to 1 meter. UHF waves may primarily propagate through the line of sight and may be blocked by buildings and environmental features. However, the waves can penetrate walls sufficiently to provide service to UEs located indoors. Compared to transmissions using smaller frequencies (and longer waves) in the high frequency (HF) or very high frequency (VHF) portions of the spectrum, UHF wave transmission is characterized by smaller antennas and shorter ranges (e.g., less than 100 km). In some cases, wireless communication system 200 can also utilize the extremely high frequency (EHF) portion of the spectrum (e.g., from 30 GHz to 300 GHz). This region can also be called the millimeter band because the wavelength ranges from approximately 1 millimeter to 1 centimeter. Therefore, EHF antennas may be smaller and more closely spaced than UHF antennas. In some cases, this can facilitate the use of antenna arrays within the UE 201 (e.g., for directional beamforming). However, EHF transmissions may suffer from greater atmospheric attenuation and shorter range compared to UHF transmissions.

[0060] Therefore, the wireless communication system 200 can support millimeter-wave (mmW) communication between user equipment and base station. Devices operating in the mmW or EHF band can have multiple antennas to allow beamforming. That is, base station 202 can use multiple antennas or antenna arrays for beamforming operations to enable directional communication with UE 201. Beamforming (also known as spatial filtering or directional transmission) is a signal processing technique that can be used at a transmitter (e.g., a base station) to shape and / or guide the entire antenna beam in the direction of a target receiver (e.g., a UE). This can be achieved by combining elements in an antenna array such that signals transmitted at a specific angle undergo constructive interference, while other signals undergo destructive interference.

[0061] Multiple-input multiple-output (MIMO) wireless systems use transmission schemes between transmitters (e.g., base stations) and receivers (e.g., UEs), where both transmitters and receivers are equipped with multiple antennas. Some portions of the wireless communication system 200 may utilize beamforming. For example, base station 202 may have an antenna array with multiple rows and columns of antenna ports, which the base station can use for beamforming in communication with UE 201. Signals can be transmitted multiple times in different directions (e.g., each transmission can be beamformed differently). The mmW receiver (e.g., UE) can attempt multiple beams (e.g., antenna subarrays) while receiving a synchronization signal.

[0062] In some cases, the antennas of base station 202 or UE 201 may be located within one or more antenna arrays, which may support beamforming or MIMO operation. One or more base station antennas or antenna arrays may be juxtaposed at an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with base station 202 may be located in different geographical locations. Base station 202 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with UE 201.

[0063] In some cases, the wireless communication system 200 may be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer may be IP-based. In some cases, the RLC layer may perform packet fragmentation and reassembly for communication over logical channels. The Media Access Control (MAC) layer may perform priority processing and multiplexing logical channels into transport channels. The MAC layer may also provide retransmissions at the MAC layer using Hybrid Automatic Repeat Request (HARQ) to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide the establishment, configuration, and maintenance of RRC connections between the UE 201 and network equipment or core network 203 supporting user plane data radio bearers. At the physical (PHY) layer, transport channels may be mapped to physical channels.

[0064] In LTE or NR, time intervals can be expressed as multiples of a basic time unit (which can be a sampling period of Ts = 1 / 30,720,000 seconds). Time resources can be organized according to radio frames of length 10 ms (Tf = 307,200 Ts), identified by System Frame Numbers (SFNs) ranging from 0 to 1023. Each frame can include 10 subframes of 1 ms each, numbered from 0 to 9. Subframes can be further divided into two 0.5 ms slots, each containing six or seven modulation symbol periods (depending on the length of the cyclic prefix pre-added to each symbol). Excluding the cyclic prefix, each symbol comprises 2048 sampling periods. In some cases, a subframe can be the smallest scheduling unit, also known as a Time Interval (TTI). In other cases, the TTI can be shorter than a subframe or can be dynamically selected (e.g., in short TTI bursts or in selected component carriers using short TTIs).

[0065] A resource element can consist of one symbol period and one subcarrier (e.g., a 15 kHz frequency range). A resource block can include 12 consecutive subcarriers in the frequency domain, and for each normal cyclic prefix in an Orthogonal Frequency Division Multiplexing (OFDM) symbol, it can include 7 consecutive OFDM symbols (one time slot) in the time domain, or 84 resource elements. The number of bits carried by each resource element can depend on the modulation scheme (the configuration of symbols that can be selected during each symbol period). Therefore, the more resource blocks the UE receives and the higher the modulation scheme, the higher the data rate may be.

[0066] The wireless communication system 200 can support operation on multiple cells or carriers, a feature that may be referred to as carrier aggregation (CA) or multi-carrier operation. A carrier may also be referred to as a component carrier (CC), layer, channel, etc. The terms “carrier,” “component carrier,” “cell,” and “channel” are used interchangeably herein. The UE 201 can be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0067] In some cases, wireless system 200 may utilize both licensed and unlicensed radio spectrum bands. For example, wireless system 200 may employ LTE Licensed Assisted Access (LTE-LAA) or LTE Unlicensed (LTE U) radio access technology or NR technology in unlicensed bands such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in unlicensed radio spectrum bands, wireless devices such as base station 202 and UE 201 may employ a Listen-Before-Speak (LBT) procedure to ensure that the channel is idle before transmitting data. In some cases, operation in unlicensed bands may be based on CA configuration and CC configuration for operation in licensed bands. Operation in unlicensed spectrum may include downlink transmission, uplink transmission, or both. Duplexing in unlicensed spectrum may be based on FDD, TDD, or a combination of both.

[0068] Figure 3 This is a diagram of a protocol stack 300 according to at least one example embodiment. Figure 3 The example provided is merely an example and does not necessarily limit the scope of the claims.

[0069] In at least one example embodiment, the physical (PHY) layer 304 provides information transmission services to higher layers using a physical channel. The PHY layer 304 can be connected to the higher-level Media Access Control (MAC) layer 303 via a transport channel. Data can be transmitted between the MAC layer 303 and the PHY layer 304 via the transport channel. Data can be transmitted between the physical layers on the transmitting and receiving sides via the physical channel. The physical channel uses time and frequency as radio resources. In some cases, the physical channel is modulated using an orthogonal frequency division multiple access (OFDMA) scheme in the downlink and a single-carrier frequency division multiple access (SC-FDMA) scheme in the uplink.

[0070] In at least one example embodiment, MAC layer 303 provides services to the higher-level Radio Link Control (RLC) layer 302 via a logical channel. The second-layer RLC layer 302 supports reliable data transmission. The functionality of RLC layer 302 can be implemented by function blocks of MAC layer 303. Packet Data Convergence Protocol (PDCP) layer 301 performs header compression to reduce unnecessary control information for efficient transmission of Internet Protocol (IP) packets, such as IP version 4 (IPv4) or IP version 6 (IPv6) packets, over radio interfaces with relatively limited bandwidth.

[0071] In at least one exemplary embodiment, the PDCP layer 301 is implemented by PDCP entities that perform various actions of the PDCP layer. In this way, the operating network node includes one or more PDCP entities for performing PDCP layer activities. In operation, the PDCP entities receive data transmitted from higher layers in PDCP Service Data Units (SDUs). The PDCP entities perform various operations on the PDCP SDUs received from higher layers for transmission, such as header compression, uplink data compression, integrity protection, encryption, etc. The PDCP entities perform these operations on the received PDCP SDUs to generate PDCP Packet Data Units (PDUs), which are then transmitted by means of the PDCP entities sending the PDCP SDUs to lower layers for transmission.

[0072] In at least one exemplary embodiment, the RLC layer 302 is implemented by RLC entities that perform various actions of the RLC layer. In this way, the operating network node includes one or more RLC entities for performing RLC layer activities. In operation, the RLC entity receives data transmitted from higher layers in RLC SDUs. The RLC entity performs various operations on the RLC SDUs received from higher layers for transmission, such as header compression, uplink data compression, integrity protection, encryption, etc. The RLC entity performs these operations on the received RLC SDUs to generate RLC PDUs, which are then transmitted by sending the RLC SDUs to lower layers for transmission.

[0073] In at least one example embodiment, MAC layer 303 is implemented by MAC entities that perform various actions of the MAC layer. In this way, the operating network node includes one or more MAC entities for performing MAC layer activities. In operation, the MAC entity receives data transmitted from higher layers in MAC SDUs. The MAC entity performs various operations on the MAC SDUs received from higher layers for transmission, such as header compression, uplink data compression, integrity protection, encryption, etc. The MAC entity performs these operations on the received MAC SDUs to generate MAC PDUs, which are then transmitted by sending the MAC SDUs to lower layers for transmission.

[0074] Figure 4 This is an interaction diagram illustrating activities (400) associated with Mobile Terminal Small Data Transmission (MT-SDT) according to at least one example embodiment. In at least one example embodiment, there is a set of operations corresponding to... Figure 4 At least some of the activities. For example, there may be activities related to... Figure 4 A set of operations associated with the activities of one or more devices. Devices (e.g., Figure 1Electronic device 100 or a part thereof, Figure 2 The device 201 or a part thereof, Figure 2 The device 202 or a part thereof, or Figure 2 The apparatus 204 or a portion thereof may utilize this set of operations. The apparatus may include components for performing these operations, such as including… Figure 1 The processor 110. In an example embodiment, the device (e.g., Figure 1 Electronic device 100) by causing memory (e.g. Figure 1 The memory 140 includes computer code for transformation, which is configured to interact with a processor (e.g., Figure 1 The processor 110 works together to enable the device to perform Figure 4 A set of operations.

[0075] With the development of wireless communication, facilitating point-to-multipoint communication has become increasingly important. In at least one example embodiment, the UE implements multicast and broadcast services (MBS) to provide point-to-multipoint communication with the radio access network (RAN). In some cases, it may be desirable to provide different types of MBS services. For example, in some cases, it may be desirable for the RAN to support scenarios where the RAN receives packets to be sent to multiple UEs and performs point-to-point transmissions to each individual UE to send the packets. In this way, the UE receives packets via point-to-point communication. In at least one example embodiment, this type of communication is referred to as broadcast MBS. In this way, broadcast MBS is characterized by each UE receiving a different copy of the packets via separate point-to-point communication from the RAN.

[0076] In other cases, the RAN may need to support scenarios where it receives packets to be sent to multiple UEs and performs point-to-multipoint transmissions to each individual UE to send the packets. In this way, the UEs receive packets via point-to-multipoint communication. In at least one example embodiment, this type of communication is referred to as multicast MBS. In this manner, multicast MBS is characterized by each UE receiving the same packets via point-to-multipoint communication from the RAN.

[0077] In operation, the UE performs operations for configuring the reception of MBS information and for receiving MBS information. For example, in at least one example embodiment, the UE receives configuration information for one or more MBS sessions. This configuration information includes parameters required for the UE to receive MBS information and effectively communicate with the RAN regarding the MBS information. For example, the UE can be configured to receive MBS information about one or more MBS sessions. In at least one example embodiment, an MBS session refers to a communication flow carrying MBS information, such that the UE and RAN can transmit control information about the communication flow by identifying the applicable communication flow. In this way, the UE and RAN can use an MBS session identifier to specify a particular MBS session. In at least one example embodiment, the UE is configured with an MBS session identifier. The MBS session identifier can then be used in communication between the UE and the RAN to identify a particular MBS session.

[0078] Once the UE has been configured to receive MBS information for an MBS session, the operation of receiving the MBS information for the MBS session is performed. In at least one example embodiment, the UE receives a paging transmission indicating an MBS session identifier, and then performs an operation to receive the MBS information for the MBS session indicated in the paging transmission. For example, the paging transmission may include a paging record indicating an MBS session identifier. In some cases, the UE may receive the paging transmission while the UE is not in the RRC_CONNECTED state. For example, the UE may be in the RRC_INACTIVE state. In at least one example embodiment, the UE initiates an RRC connection recovery procedure based on a paging transmission (or a paging record included in a paging transmission) to receive the MBS information for the MBS session indicated by the MBS session identifier. In this way, the RRC connection recovery procedure transitions the UE to a state where it can receive MBS information. In this way, the UE may initiate the RRC connection recovery procedure based on at least one paging record, as the paging record triggered the initiation.

[0079] Because point-to-point communication is involved, the UE may need to transition from the RRC_INACTIVE state to the RRC_CONNECTED state to receive broadcast MBS information. However, at least because point-to-multipoint communication involving multicast MBS does not necessarily require the UE to be in the RRC_CONNECTED state, it may be desirable for the UE to receive MBS information while in the RRC_INACTIVE state. In at least one example embodiment, the UE utilizes a Small Data Transmission (SDT) procedure, which allows data and / or signaling to be transmitted while the UE remains in the RRC_INACTIVE state. Since the UE's reception of MBS information is initiated by a paging transmission, in this case, the SDT procedure is initiated by the RAN, not by the UE. In at least one example embodiment, the RAN-initiated SDT is referred to as Mobile Terminal SDT (MT-SDT).

[0080] In at least one example embodiment, the UE initiates MT-SDT by initiating an RRC connection recovery procedure that specifies MT-SDT. By initiating an RRC connection recovery procedure that specifies MT-SDT, the UE enables the RAN to perform the operations necessary to transmit MBS information to the UE using the SDT, which allows the UE to receive data in the RRC_INACTIVE state. In at least one example embodiment, the UE specifies MT-SDT by setting the recovery reason of the RRC connection recovery procedure to indicate MT-SDT. In at least one example embodiment, the UE initiates MT-SDT by sending an RRC connection recovery request to the RAN that includes an RRC connection recovery request identifying the recovery reason of MT-SDT.

[0081] In at least one example embodiment, the paging transmission indicates whether the UE should consider initiating an RRC connection restoration procedure with a specified MT-SDT. For example, the RAN may want the UE to receive information using an SDT if conditions are favorable. In at least one example embodiment, the paging transmission includes an MT-SDT indicator. In at least one example embodiment, the presence of the MT-SDT indicator in the paging transmission indicates an instruction from the RAN to the UE for initiating an RRC connection restoration procedure with a specified MT-SDT. In this way, the UE can initiate an RRC connection restoration procedure based on the paging record, because determining whether an MT-SDT is specified in the RRC connection restoration procedure is partly based on whether the paging transmission specifies an MT-SDT.

[0082] As mentioned earlier, there may be situations where the UE determines it is receiving MBS information in the RRC_CONNECTED state. In this case, the UE initiates an RRC connection recovery procedure, where the recovery reason indicates communication in the RRC_CONNECTED state. In at least one example embodiment, the UE utilizes the recovery reason of Mobile Terminal Access (MT-Access) to initiate the RRC connection recovery procedure in order to initiate communication in the RRC_CONNECTED state.

[0083] Due to the differences between the operation of broadcast MBS and multicast MBS, as well as the differences in the capabilities available to multicast MBS and broadcast MBS, the configurations of broadcast MBS sessions and multicast MBS sessions are different.

[0084] In at least one example embodiment, the UE receives configuration information for an MBS session. In at least one example embodiment, the UE receives an MBS configuration message that includes configuration information for the MBS session. The configuration information includes parameters governing how the UE and RAN perform communication for the MBS session. In at least one example embodiment, the configuration information for a multicast MBS session includes parameters for configuring the multicast MBS session to receive data in the RRC_INACTIVE state. In at least one example embodiment, the configuration information for a broadcast MBS session includes parameters for configuring the broadcast MBS session to receive data in the RRC_CONNECTED state. In this way, the configuration information for the broadcast MBS session is not configured to receive data in the RRC_INACTIVE state.

[0085] In at least one example embodiment, both the configuration information for multicast MBS sessions and the configuration information for broadcast MBS information include an MBS session identifier. The MBS session identifier can be used to identify an MBS session in various situations. For example, it can be used in paging transmissions to identify the MBS session from which the UE is receiving data. In at least one example embodiment, the MBS session identifier is a Temporary Mobile Group Identity (TMGI).

[0086] Since broadcast MBS was deployed prior to the initial specification of multicast MBS, backward compatibility may be required for multicast MBS configuration specifications and further configuration specifications for broadcast MBS sessions.

[0087] As mentioned earlier, the configuration information for a multicast MBS session is necessarily different from that for a broadcast MBS session. In at least one example embodiment, the broadcast MBS session is configured based on received broadcast MBS session information records. In at least one example embodiment, the multicast MBS session is configured based on received multicast MBS session information records. In at least one example embodiment, the record is an information element.

[0088] In at least one example embodiment, the broadcast MBS session information record includes parameters for specifying communication of the associated broadcast MBS session. In at least one example embodiment, the broadcast MBS session information record is an MBS-SessionInfo information element. The broadcast MBS session information record may include the following:

[0089] • MBS session identifier, such as the TMGI used to identify an MBS session,

[0090] • Radio Network Temporary Identifier (RNTI), which identifies the RNTI used to scramble communications in an MBS session.

[0091] • Broadcast-Specific Multicast Resource Bearer (MRB) configuration information for MBS session communication.

[0092] • Multicast Service Channel (MTCH) configuration information used for MBS session communication, and

[0093] • Physical downlink shared channel (PDSCH) configuration information used for MBS session communication.

[0094] In at least one example embodiment, the UE receives configuration information for multiple broadcast MBS sessions. In at least one example embodiment, the configuration information for the multiple broadcast MBS sessions is a list of broadcast MBS session information. In at least one example embodiment, the list of broadcast MBS session information includes a list of broadcast MBS session information records. In at least one example embodiment, the list of broadcast MBS session information is an MBS-SessionInfoList information element.

[0095] In at least one example embodiment, the multicast MBS session information record includes parameters for specifying communication of an associated multicast MBS session. The multicast MBS session information record may include the following:

[0096] • MBS session identifier, such as the TMGI used to identify an MBS session,

[0097] • RNTI, which identifies the RNTI used to scramble MBS session communications.

[0098] • Multicast-specific MRB configuration information used for MBS session communication

[0099] • MTCH configuration information used for MBS session communication

[0100] • PDSCH configuration information used for MBS session communication

[0101] • A threshold indicator used to receive data in the RRC_INACTIVE state.

[0102] • A PDCP synchronization indicator used to receive data in the RRC_INACTIVE state, and

[0103] • Instructions for stopping monitoring, such as an indicator that instructs the UE to stop monitoring the RNTI of the MBS session.

[0104] In at least one example embodiment, the UE receives configuration information for multiple multicast MBS sessions. In at least one example embodiment, the configuration information for the multiple multicast MBS sessions is a list of MBS session information for multicast. In at least one example embodiment, the list of MBS session information for multicast includes a list of multicast MBS session information records.

[0105] As can be seen from the above discussion, multicast MBS session information records and broadcast MBS session information records are different from each other. For example, multicast MBS session information records include information that cannot be included in broadcast MBS session information records, such as multicast-specific MRB configuration information, threshold indicators, PDCP synchronization indicators, and indicators for stopping monitoring. Furthermore, a subset of parameters included in multicast MBS session information records exist in broadcast MBS session information records, such as MBS session identifiers, RNTI, MTCH configuration information, and PDSCH configuration information.

[0106] In at least one example embodiment, the UE receives an MBS configuration message that includes configuration information for MBS sessions. In at least one example embodiment, there is an MBS multicast configuration message for configuring multicast MBS and an MBS broadcast configuration message for configuring broadcast MBS. In at least one example embodiment, configuration information for multiple multicast MBS sessions is received in the MBS multicast configuration message, and configuration information for multiple broadcast MBS sessions is received in the MBS broadcast configuration message. In this way, the MBS multicast configuration message and the MBS broadcast configuration message are different from each other. Therefore, in at least one example embodiment, the MBS multicast configuration message includes information that cannot be included in the MBS broadcast configuration message. Similarly, in at least one example embodiment, a subset of parameters included in the MBS multicast configuration message exists in the MBS broadcast configuration message.

[0107] While there may be benefits associated with providing backward compatibility by having different configuration information structures between broadcast MBS and multicast MBS, it may be desirable to provide a simpler communication structure by offering a common structure for configuring broadcast MBS and multicast MBS.

[0108] In some cases, it may be necessary to provide a public MBS configuration message. In at least one example embodiment, the public MBS configuration message includes a list of MBS session information for multicast and a list of MBS session information for broadcast. However, in some cases, it may be desirable to provide a public MBS session information list, which may include both multicast MBS session information records and broadcast MBS session information records. In at least one example embodiment, the public MBS configuration message includes a public MBS session information list, wherein each element in the public MBS session information list is either a multicast MBS session information record or a broadcast MBS session information record.

[0109] In some cases, it may be necessary to provide public MBS session information records. As mentioned earlier, the configuration information for multicast MBS sessions will necessarily differ from that for broadcast MBS sessions. In at least one example embodiment, broadcast MBS sessions and multicast MBS sessions are each configured based on received public MBS session information records. In at least one example embodiment, the record is an information element.

[0110] In at least one example embodiment, the public MBS session information record includes parameters for specifying communication of an associated broadcast MBS session or multicast MBS session. In at least one example embodiment, the public MBS session information record is an MBS-SessionInfo information element. In at least one example embodiment, the public MBS information element is specified by mandatory parameters and optional parameters, wherein the mandatory parameters are parameters common to both the multicast MBS session configuration and the broadcast MBS session configuration, while the optional parameters are parameters specific to only one of the broadcast MBS session configuration or the multicast MBS session configuration. Note that the terms "optional" and "mandatory" are used only to characterize the nature of the parameters with respect to the common configuration structure and do not involve any determination of whether the relevant feature is mandatory or optional as a claim element. In this way, the use of the terms optional and mandatory does not limit the claims in any way unless these terms are expressly included in the claims. The public MBS session information record may include the following:

[0111] • Mandatory - MBS Session Identifier, such as the TMGI used to identify an MBS session; • Mandatory - RNTI, which identifies the RNTI used to scramble communication in the MBS session; • Mandatory - MRB Configuration Information, which is one of the following:

[0112] • Broadcast-specific MRB configuration information used for MBS session communication, or

[0113] • Multicast-specific MRB configuration information used for MBS session communication

[0114] • Configuration information for the multicast service channel (MTCH) of forced-MBS session communication, and • Configuration information for the PDSCH of forced-MBS session communication.

[0115] • Optional - Threshold indicator for receiving data in RRC_INACTIVE state, • Optional - PDCP synchronization indicator for receiving data in RRC_INACTIVE state, and • Optional - Indication for stopping monitoring, such as an indicator instructing the UE to stop monitoring the RNTI of this MBS session.

[0116] In at least one example embodiment, the UE receives configuration information for multiple MBS sessions, which can be multiple multicast MBS sessions and multiple broadcast MBS sessions. In at least one example embodiment, the configuration information for the multiple MBS sessions is a public MBS session information list. In at least one example embodiment, the public MBS session information list includes a list of public MBS session information records. In at least one example embodiment, the MBS session information list used for broadcasting is an MBS-SessionInfoList information element.

[0117] In at least one example embodiment, the configuration information for multiple multicast MBS sessions corresponds to a public MBS session information record that includes optional parameters specific to multicast MBS. In at least one example embodiment, the configuration information for multiple broadcast MBS sessions corresponds to a public MBS session information record that does not include optional parameters specific to multicast MBS.

[0118] At interaction 410, UE 401 receives configuration information for multiple multicast MBS sessions and multiple broadcast MBS sessions from radio access network (RAN) 408. In at least one example embodiment, the UE is in the RRC_CONNECTED state when receiving the configuration information.

[0119] At interaction 411, UE 401 receives an RRC release message from RAN 408. In at least one example embodiment, when the RRC release message is received, the UE is in the RRC_CONNECTED state and transitions to RRC_INACTIVE in response to receiving the RRC release message.

[0120] At interaction 412, UE 401 receives a paging transmission from RAN 408. In at least one example embodiment, the paging transmission includes at least one paging record. In at least one example embodiment, the UE is in RRC_INACTIVE when the paging transmission is received. In at least one example embodiment, the paging record indicates the specific UE used to receive the paging record. In at least one example embodiment, the UE has an assigned RNTI, and the paging record includes a UE identity that matches the UE's RNTI. For example, the UE's RNTI could be a full I-RNTI. In at least one example embodiment, the paging record includes an MT-SDT indicator.

[0121] In at least one example embodiment, the paging record includes a paging group list indicating one or more MBS sessions to which the UE will receive MBS information. In at least one example embodiment, the paging group list is a list of MBS session identifiers. In at least one example embodiment, the paging group list includes one or more MBS session identifiers that identify one or more MBS sessions that the UE has been configured with.

[0122] In at least one example embodiment, paging transmission is initiated from a base station (e.g., Figure 2 The paging message is received from base station 202. In at least one example embodiment, the paging transmission is from another UE (e.g., base station 202). Figure 2 The UE 204 receives a message that transmits a sidelink message. In such an example, the other UE could be a Layer 2 (L2) UE to a U2N (U2N) relay UE.

[0123] At interaction 413, UE 401 initiates an RRC connection restoration procedure, with the restoration reason set to indicate MT-SDT, and sends an RRC restoration request, with the restoration reason indicating MT-SDT. It should be noted that, although... Figure 4 The example shows the UE sending an RRC recovery request indicating MR-SDT, but in some cases, the UE may want to send an RRC recovery request indicating MT-Access instead of MT-SDT.

[0124] At interaction group 420, UE 401 and RAN 408 perform SDT communication. In at least one example embodiment, SDT communication involves the device receiving MBS information in the RRC_INACTIVE state.

[0125] In some cases, it may be necessary to ensure that one or more conditions are met before the UE initiates an RRC connection restoration procedure specifying MT-SDT. For example, in some cases, it may be desirable to initiate an RRC connection restoration procedure specifying MT-Access even if the UE receives a paging transmission that includes an MT-SDT indicator.

[0126] In some cases, it may be necessary to ensure that the conditions for receiving data in the RRC_INACTIVE state are met before initiating an RRC connection recovery procedure for a specified MT-SDT. In at least one example embodiment, the UE determines whether the conditions for receiving data in the RRC_INACTIVE state are met. In at least one example embodiment, the UE initiates an RRC connection recovery procedure for a specified MT-SDT if it has determined that the conditions for receiving data in the RRC_INACTIVE state are met, and initiates an RRC connection recovery procedure for a specified MT-Access if it has determined that the conditions for receiving data in the RRC_INACTIVE state are not met. In at least one example embodiment, the MAC entity determines whether the conditions for receiving data in the RRC_INACTIVE state are met.

[0127] In at least one example embodiment, determining whether the conditions for receiving data in the RRC_INACTIVE state are met includes the MAC entity determining whether the conditions for initiating the SDT procedure are met. For example, it may be desirable to ensure that the downlink path loss reference has a sufficiently high measurement reference signal received power (RSRP) for the SDT to be reliably effective. In this case, it may be necessary to configure an RSRP threshold for the SDT.

[0128] For example, it may be necessary to avoid initiating an SDT procedure when the measured RSRP of the downlink path loss reference is less than or equal to the configured RSRP threshold of the SDT. Furthermore, it may be desirable to initiate an SDT procedure when the measured RSRP of the downlink path loss reference is higher than the configured RSRP threshold of the SDT. In at least one example embodiment, the UE determines whether the measured RSRP of the downlink path loss reference is higher than the configured RSRP threshold of the SDT. In at least one example embodiment, the UE initiates an RRC connection recovery procedure for a specified MT-SDT when it has determined that the measured RSRP of the downlink path loss reference is higher than the configured RSRP threshold of the SDT, and the UE initiates an RRC connection recovery procedure for a specified MT-Access when it has determined that the measured RSRP of the downlink path loss reference is not higher than the configured RSRP threshold of the SDT.

[0129] In some cases, the paging group list included in the paging transmission can indicate MBS sessions that are not configured to receive data in the RRC_INACTIVE state. For example, a paging group can indicate a broadcast MBS session. In this case, the UE may necessarily need to receive MBS information for a broadcast MBS session in the RRC_CONNECTED state. Therefore, it may be desirable for the UE to initiate an RRC connection restoration procedure specifying MT-Access when it has been determined that the paging group list included in the paging transmission indicates an MBS session that is not configured to receive data in the RRC_INACTIVE state. Similarly, it may be desirable for the UE to initiate an RRC connection restoration procedure specifying MT-SDT when it has been determined that all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state (e.g., when all MBS sessions indicated by the MBS session identifier included in the paging group list are multicast MBS sessions).

[0130] In at least one exemplary embodiment, the UE determines whether all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state. In at least one example embodiment, if the UE has determined that all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state, it initiates an RRC connection recovery procedure specifying MT-SDT; and if the UE has determined that not all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state, it initiates an RRC connection recovery procedure specifying MT-Access.

[0131] Figure 5 This is a flowchart illustrating activities associated with initiating communication, based on at least one example embodiment. In at least one example embodiment, there is a set of operations corresponding to... Figure 5 Activities. For example Figure 1 The electronic device 100 or a portion thereof can utilize this set of operations. The device may include components for performing these operations, such as including… Figure 1 The processor 110. In one example embodiment, the device (e.g., Figure 1 Electronic device 100) by causing memory (e.g. Figure 1 The memory 140 includes computer code for transformation, which is configured to interact with a processor (e.g., Figure 1 The processor 110 works together to enable the device to perform Figure 5 A set of operations.

[0132] In box 501, the device receives configuration information for multiple multicast MBS sessions and configuration information for multiple broadcast MBS sessions.

[0133] In block 502, when the UE is in the RRC_INACTIVE state, the device receives a paging transmission including at least one paging record.

[0134] In block 503, the device determines whether the conditions for receiving data in the RRC_INACTIVE state are met.

[0135] In block 504, the device determines whether all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state.

[0136] In block 505, if it is determined that the conditions for receiving data in the RRC_INACTIVE state are met and all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state, the process proceeds to block 506. If the device has determined that the conditions for receiving data in the RRC_INACTIVE state are not met, or that not all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state, the process proceeds to block 507.

[0137] In box 506, the device initiates an RRC connection restoration procedure, wherein the restoration reason is set to indicate MT-SDT. In this manner, the UE initiates the RRC connection restoration procedure based on at least one paging record, wherein the restoration reason is set to indicate MT-SDT if the conditions for receiving data in the RRC_INACTIVE state are determined to be met and all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state.

[0138] In box 507, the device initiates an RRC connection restoration procedure, wherein the restoration reason is set to indicate MT-Access. In this manner, the UE initiates the RRC connection restoration procedure based on at least one paging record, wherein the restoration reason is set to indicate MT-Access if the conditions for receiving data in the RRC_INACTIVE state are determined to be unmet or if not all MBS sessions indicated by the MBS session identifier included in the paging group list are configured to receive data in the RRC_INACTIVE state.

[0139] Embodiments of the present invention may be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and / or hardware may reside on a device, a separate device, or multiple separate devices. If desired, portions of the software, application logic, and / or hardware may reside on a device, portions of the software, application logic, and / or hardware may reside on a separate device, and portions of the software, application logic, and / or hardware may reside on multiple separate devices. In exemplary embodiments, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media.

[0140] If necessary, the different functions described herein may be executed in different orders and / or simultaneously with each other. For example, Figure 5 Box 503 can be found Figure 5 The function will execute after a 504 error. Furthermore, one or more of the above functions can be optional or combined, if needed. For example, Figure 5 Boxes 503 and 504 can be optional and / or related to... Figure 5 The 505 frame combination.

[0141] While various aspects of the invention are set forth in the independent claims, other aspects of the invention include other combinations of the features of the described embodiments and / or dependent claims with the features of the independent claims, and not only the combinations expressly set forth in the claims.

[0142] This document also notes that although exemplary embodiments of the invention have been described above, these descriptions should not be considered limiting. Rather, various changes and modifications may be made without departing from the scope of the invention as defined by the appended claims.

Claims

1. A method performed by a user equipment (UE), comprising: receiving configuration information for a plurality of multicast and broadcast services (MBS) sessions configured to receive data in an RRC_INACTIVE state, and configuration information for a plurality of broadcast MBS sessions; receiving, while the UE is in the RRC_INACTIVE state, a paging transmission comprising at least one paging record and a paging group list comprising a plurality of MBS session identifiers, the paging record comprising: a UE identity matching a radio network temporary identifier (RNTI) of the UE, and a mobile terminated small data transmission (MT-SDT) indicator; determining whether a condition for receiving data in the RRC_INACTIVE state is satisfied; determining whether all MBS sessions indicated by the MBS session identifiers included in the paging group list are configured to receive data in the RRC_INACTIVE state; initiating a RRC connection resume procedure based on the at least one paging record, wherein the resume cause is set to indicate MT-SDT in case of: the condition for receiving data in the RRC_INACTIVE state is determined to be satisfied, and all MBS sessions indicated by the MBS session identifiers included in the paging group list are configured to receive data in the RRC_INACTIVE state; and initiating a RRC connection resume procedure based on the at least one paging record, wherein the resume cause is set to indicate mobile terminated access (MT-Access) in case of: the condition for receiving data in the RRC_INACTIVE state is determined to be not satisfied, or not all MBS sessions indicated by the MBS session identifiers included in the paging group list are configured to receive data in the RRC_INACTIVE state. 2.The method of claim 1, wherein: the MBS session identifiers are temporary mobile group identities (TMGIs), each multicast MBS session and each broadcast MBS session is identified by a TMGI, and determining whether all MBS sessions indicated by the MBS session identifiers included in the paging group list are configured to receive data in the RRC_INACTIVE state comprises determining whether each TMGI included in the paging group list identifies a MBS session configured to receive data in the RRC_INACTIVE state.

3. The method of claim 1, wherein, determining whether the condition for receiving data in the RRC_INACTIVE state is satisfied comprises determining, by a medium access control (MAC) entity, whether a reference signal received power (RSRP) of a downlink pathloss reference is higher than a configured RSRP threshold for small data transmission (SDT). 4.The method of claim 1, wherein: the configuration information for the plurality of multicast MBS sessions is received in an MBS multicast configuration message, the configuration information for the plurality of broadcast MBS sessions is received in an MBS broadcast configuration message, and the MBS multicast configuration message and the MBS broadcast configuration message are different from each other. 5.The method of claim 4, wherein: the MBS multicast configuration message includes information that cannot be included in the MBS broadcast configuration message, and a subset of parameters included in the MBS multicast configuration message is present in the MBS broadcast configuration message. 6.The method of claim 1, wherein: the configuration information for the plurality of multicast MBS sessions and the configuration information for the plurality of broadcast MBS sessions are received in a common MBS configuration message, the configuration information for the plurality of multicast MBS sessions includes a list of MBS session information for multicast, and the configuration information for the plurality of broadcast MBS sessions is a list of MBS session information for broadcast. 7.The method of claim 6, wherein: the configuration information for the plurality of multicast MBS sessions and the configuration information for the plurality of broadcast MBS sessions are included in a common list of MBS session information, the configuration information for the plurality of multicast MBS sessions includes a plurality of common MBS session information elements included in the common list of MBS session information, and the plurality of broadcast MBS sessions are a plurality of common MBS session information elements included in the common list of MBS session information that are different from the common MBS session information elements of the multicast MBS sessions. 8.A user equipment (UE), comprising: at least one processor; at least one memory including computer program code, the memory and the computer program code configured to, working with the processor, cause the UE to perform at least the following: receive configuration information for a plurality of multicast multicast and broadcast service (MBS) sessions configured to receive data in an RRC_INACTIVE state, and configuration information for a plurality of broadcast MBS sessions; when the UE is in the RRC_INACTIVE state, receive a paging transmission including at least one paging record and a paging group list including a plurality of MBS session identifiers, the paging record including: a UE identity matching a radio network temporary identifier (RNTI) of the UE, and a mobile terminated small data transmission (MT-SDT) indicator; determine whether a condition for receiving data in the RRC_INACTIVE state is satisfied; determine whether all MBS sessions indicated by the MBS session identifiers included in the paging group list are configured to receive data in the RRC_INACTIVE state; initiate a RRC connection resume procedure based on the at least one paging record, wherein the resume cause is set to indicate MT-SDT in case that: the condition for receiving data in the RRC_INACTIVE state is determined to be satisfied, and all MBS sessions indicated by the MBS session identifiers included in the paging group list are configured to receive data in the RRC_INACTIVE state; and initiate a RRC connection resume procedure based on the at least one paging record, wherein the resume cause is set to indicate mobile terminated access (MT-Access) in case that: the condition for receiving data in the RRC_INACTIVE state is determined to be not satisfied, or the MBS session identifiers included in the paging group list do not indicate any MBS session configured to receive data in the RRC_INACTIVE state. Not all MBS sessions indicated by the MBS session identifiers included in the list of paging groups are configured to receive data in the RRC_INACTIVE state.

9. The UE of claim 8, wherein: The MBS session identifiers are temporary mobile group identities (TMGIs), Each multicast MBS session and each broadcast MBS session is identified by a TMGI, and determining whether all MBS sessions indicated by the MBS session identifiers included in the list of paging groups are configured to receive data in the RRC_INACTIVE state comprises determining whether each TMGI included in the list of paging groups identifies a MBS session configured to receive data in the RRC_INACTIVE state.

10. The UE of claim 8, wherein, Determining whether the condition for receiving data in the RRC_INACTIVE state is satisfied comprises determining, by a medium access control (MAC) entity, whether a reference signal received power (RSRP) of a downlink pathloss reference is higher than a configured RSRP threshold for small data transmission (SDT).

11. The UE of claim 8, wherein: The configuration information for the plurality of multicast MBS sessions is received in an MBS multicast configuration message, The configuration information for the plurality of broadcast MBS sessions is received in an MBS broadcast configuration message, and the MBS multicast configuration message and the MBS broadcast configuration message are different from each other.

12. The UE of claim 11, wherein: The MBS multicast configuration message includes information that cannot be included in the MBS broadcast configuration message, and a subset of parameters included in the MBS multicast configuration message is present in the MBS broadcast configuration message.

13. The UE of claim 8, wherein: The configuration information for the plurality of multicast MBS sessions and the configuration information for the plurality of broadcast MBS sessions are received in a common MBS configuration message, The configuration information for the plurality of multicast MBS sessions comprises a list of MBS session information for multicast, and the configuration information for the plurality of broadcast MBS sessions is a list of MBS session information for broadcast.

14. The UE of claim 13, wherein: The configuration information for the plurality of multicast MBS sessions and the configuration information for the plurality of broadcast MBS sessions are included in a common list of MBS session information, The configuration information for the plurality of multicast MBS sessions comprises a plurality of common MBS session information elements included in the common list of MBS session information, and The plurality of broadcast MBS sessions are a plurality of common MBS session information elements included in the common list of MBS session information that are different from the common MBS session information elements for multicast MBS sessions.

15. At least one non-transitory computer-readable medium encoded with instructions that, when executed by a processor in a user equipment (UE), perform the following operations: receiving configuration information for a plurality of multicast multicast and broadcast service (MBS) sessions configured to receive data in an RRC_INACTIVE state, and configuration information for a plurality of broadcast MBS sessions; receiving a paging transmission while the UE is in an RRC_INACTIVE state, the paging transmission comprising at least one paging record and a paging group list comprising a plurality of MBS session identifiers, the paging record comprising: a UE identity matching a radio network temporary identifier (RNTI) of the UE, and a mobile terminal small data transmission (MT-SDT) indicator; determining whether a condition for receiving data in the RRC_INACTIVE state is satisfied; determining whether all MBS sessions indicated by the MBS session identifiers comprised in the paging group list are configured to receive data in the RRC_INACTIVE state; initiating an RRC connection resume procedure based on the at least one paging record, wherein the resume cause is set to indicate MT-SDT in case of: the condition for receiving data in the RRC_INACTIVE state being determined to be satisfied, and all MBS sessions indicated by the MBS session identifiers comprised in the paging group list being configured to receive data in the RRC_INACTIVE state; and initiating an RRC connection resume procedure based on the at least one paging record, wherein the resume cause is set to indicate mobile terminal access (MT-Access) in case of: the condition for receiving data in the RRC_INACTIVE state being determined to be not satisfied, or not all MBS sessions indicated by the MBS session identifiers comprised in the paging group list being configured to receive data in the RRC_INACTIVE state.

16. The medium of claim 15, wherein: the MBS session identifiers are temporary mobile group identities (TMGIs), each multicast MBS session and each broadcast MBS session is identified by a TMGI, and determining whether all MBS sessions indicated by the MBS session identifiers comprised in the paging group list are configured to receive data in the RRC_INACTIVE state comprises determining whether each TMGI comprised in the paging group list identifies an MBS session configured to receive data in the RRC_INACTIVE state.

17. The medium of claim 15, wherein, determining whether the condition for receiving data in the RRC_INACTIVE state is satisfied comprises determining, by a medium access control (MAC) entity, whether a reference signal received power (RSRP) of a downlink pathloss reference is above a configured RSRP threshold for small data transmission (SDT).

18. The medium of claim 15, wherein: configuration information for a plurality of multicast MBS sessions is received in an MBS multicast configuration message, configuration information for a plurality of broadcast MBS sessions is received in an MBS broadcast configuration message, and the MBS multicast configuration message and the MBS broadcast configuration message are different from each other.

19. The medium of claim 18, wherein: the MBS multicast configuration message comprises information that cannot be comprised in the MBS broadcast configuration message, and a subset of parameters comprised in the MBS multicast configuration message is present in the MBS broadcast configuration message.

20. The medium of claim 15, wherein: receiving configuration information for a plurality of multicast MBS sessions and configuration information for a plurality of broadcast MBS sessions in a common MBS configuration message, the configuration information for the plurality of multicast MBS sessions includes a list of MBS session information for multicast, and the configuration information for the plurality of broadcast MBS sessions is a list of MBS session information for broadcast.

Images