Multicast and broadband service communications with mobile terminal small data transmissions

Abstract

The invention relates to multicast and broadband service communications with mobile terminal small data transmissions. The method comprises the following steps: 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 an RRC connection recovery process based on at least one paging record, a recovery cause being set to indicate MT-SDT in a case where a condition for receiving data in an RRCINACTIVE state is determined to be satisfied and all MBS sessions indicated by an MBS session identifier included in the paging group list are configured to receive data in the RRCINACTIVE state; and initiating an RRC connection recovery procedure based on the at least one paging record, a recovery cause being set to indicate MT-Access in a case where a condition for receiving data in the RRCINACTIVE state is determined to be not satisfied or that an MBS session identifier included in the paging group list indicates that not all MBS sessions are configured to receive data in the RRCINACTIVE state.

Description

Technical Field

[0001] This application generally relates to small data transmission of wireless devices. Background Art

[0002] As wireless devices send and receive larger amounts of data, it becomes increasingly important to improve the efficiency of data communication. 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 configurations and operations. Summary of the Invention

[0003] Aspects of example embodiments of the present 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. The method for execution by a User Equipment (UE) includes: receiving configuration information for a plurality of Multicast Multicast and Broadcast Services (MBS) sessions configured to receive data in the RRC_INACTIVE state, and configuration information for a plurality of Broadcast MBS sessions not configured to receive data in the RRC_INACTIVE state; when the UE is in the RRC_INACTIVE state, receiving a paging transmission, the paging transmission including at least one paging record, the paging record including: a UE identity matching the UE's Radio Network Temporary Identifier (RNTI), a Mobile Terminal Small Data Transmission (MT-SDT) indicator, and a paging group list including a plurality of MBS session identifiers; 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 an RRC connection resume procedure based on at least one paging record, wherein the resume cause is set to indicate MT-SDT when: 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 an RRC connection resume procedure based on at least one paging record, wherein the resume cause is set to indicate Mobile Terminal Access (MT-Access) when: the condition for receiving data in the RRC_INACTIVE state is determined not to be 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.

[0005] An apparatus, comprising 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 a plurality of multicast and broadcast services (MBS) sessions configured to receive data in the RRC_INACTIVE state, and configuration information for a plurality of broadcast MBS sessions not configured to receive data in the RRC_INACTIVE state; when the UE is in the 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 transmission (MT-SDT) indicator, and a paging group list including a plurality of MBS session identifiers; determine whether a condition for receiving data in the RRC_INACTIVE state is met; 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 an RRC connection resume procedure based on at least one paging record, wherein the resume reason is set to indicate MT-SDT when: the condition for receiving data in the RRC_INACTIVE state is determined to be met, 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; initiate an RRC connection resume procedure based on at least one paging record, wherein the resume reason is set to indicate mobile terminal access (MT-Access) when: the condition for receiving data in the RRC_INACTIVE state is determined not to be met, 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.

[0006] In at least one exemplary embodiment, each multicast MBS session and each broadcast MBS session is 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 exemplary embodiment, the paging transmission is a message transmission sidelink message received from another UE.

[0011] In at least one exemplary embodiment, the other UE is a layer 2 (L2) UE-to-network (U2N) relay UE.

[0012] In at least one exemplary embodiment, the RNTI of the UE is an all-inactive - RNTI (I-RNTI).

[0013] In at least one exemplary 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 transmission (SDT) procedure are met.

[0014] In at least one exemplary 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 of the SDT.

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

[0016] In at least one exemplary embodiment, determining that the conditions for initiating an 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 exemplary embodiment, the configuration information of multiple multicast MBS sessions is received in an MBS multicast configuration message, and the configuration information of multiple broadcast MBS sessions is received in an MBS broadcast configuration message.

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

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

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

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

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

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

[0024] In at least one exemplary embodiment, the configuration information of multiple multicast MBS sessions and the configuration information of multiple broadcast MBS sessions are received in a common MBS configuration message.

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

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

[0027] In at least one exemplary embodiment, the configuration information of multiple multicast MBS sessions and the configuration information of multiple broadcast MBS sessions are included in a common MBS session information list.

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

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

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

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

[0032] In at least one exemplary embodiment, the configuration information of multiple multicast MBS sessions corresponds to a common MBS session information record, which includes optional parameters specific to multicast MBS. In at least one exemplary embodiment, the configuration information of multiple broadcast MBS sessions corresponds to a common MBS session information record that does not include optional parameters specific to multicast MBS. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] To more fully understand the embodiments of the present invention, reference is now made to the following description taken in conjunction with the accompanying drawings, in which:

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

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

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

[0037] Figure 4 is an interaction diagram illustrating activities associated with mobile terminal small data transfer (MT-SDT) according to at least one example embodiment, and

[0038] Figure 5 is a flowchart illustrating activities associated with initiating a communication according to at least one example embodiment. DETAILED DESCRIPTION

[0039] Embodiments of the present invention and their potential advantages are understood by reference to the Figures 1 to 5 in the accompanying drawings.

[0040] Some embodiments will be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all embodiments are shown. The various embodiments of the present 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 so that this disclosure will satisfy applicable legal requirements. Like reference numerals always refer to like elements. As used herein, the terms "data," "content," "information," and similar terms may be used interchangeably to refer to data that can be sent, received, and / or stored according to embodiments of the present invention. Thus, the use of any such term should not be regarded as limiting the spirit and scope of the embodiments of the present invention.

[0041] In addition, as used herein, the term "circuitry" refers to (a) only hardware circuitry implementations (e.g., implementations in analog and / or digital circuitry); (b) a combination of circuitry and one or more computer program products, including software and / or firmware instructions stored on one or more computer-readable memories, which work together to cause an apparatus to perform one or more functions described herein; and (c) circuitry, such as, for example, one or more microprocessors or a portion of one or more microprocessors, which require software or firmware to operate even if the software or firmware is not physically present. This definition of "circuitry" applies to all uses of the term herein, including in any claim. As another example, as used herein, the term "circuitry" also includes an implementation that includes one or more processors and / or a portion thereof and accompanying software and / or firmware. As another example, the term "circuitry" as used herein also includes, for example, a baseband integrated circuit or an application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, a cellular network device, other network devices, and / or other computing devices.

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

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

[0044] In addition, the apparatus can easily adopt the embodiments of the present invention regardless of its intention to provide mobility. In this regard, although the embodiments of the present invention may be described in connection with mobile applications, it should be understood that the embodiments of the present invention can be utilized in connection with a variety of other applications in and outside the mobile communication industry. For example, the apparatus can be at least a part of a non-portable apparatus such as a large screen television, an electronic table, a kiosk, a vehicle, etc.

[0045] In at least one example embodiment, the 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 can include volatile memory (e.g., volatile random access memory (RAM) including a buffer for temporarily storing data) and / or other memory (e.g., non-volatile memory, which can be embedded and / or removable). The non-volatile memory can include EEPROM, flash memory, etc. The memory 140 can store any of a plurality of pieces of information and data. The electronic device 100 can use this information and data to implement one or more functions of the 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 such that the device performs one or more actions described herein.

[0046] The electronic device 100 may further include a transceiver 120. In at least one example embodiment, the transceiver 120 is coupled to one or more antennas 130. In at least one example embodiment, the processor 110 provides signals to the transceiver 120 and / or receives signals from the transceiver 120. The signals can include signaling information according to a communication interface standard, user voice, received data, user-generated data, etc. The transceiver 120 can operate using one or more air interface standards, communication protocols, modulation types, and access types. By way of example, the electronic transceiver 120 can operate according to the 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)), according to the third generation (3G) wireless communication protocols (e.g., Universal Mobile Telecommunications System (UMTS), CDMA2000, Wideband CDMA (WCDMA), and Time Division Synchronous CDMA (TD-SCDMA)), and / or according to the fourth generation (4G) wireless communication protocols (e.g., LTE), fifth generation (5G) protocols (e.g., New Radio (NR)), wireless networking protocols (e.g., 802.11, short-range wireless protocols such as Bluetooth), etc.

[0047] Processor 110 may include components such as circuitry for implementing audio, video, communication, navigation, logic functions, etc. and for implementing embodiments of the present invention, including for example one or more of the functions 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 for example one or more of the functions described herein. The device may perform the control and signal processing functions of electronic device 100 among these devices according to the respective capabilities of these devices. Thus, processor 110 may include functions for encoding and interleaving messages and data prior to modulation and transmission. Processor 1 may additionally include an internal voice encoder and may include an internal data modem. Further, processor 110 may include functions for operating one or more software programs that may be stored in memory and that may in particular cause processor 110 to implement at least a portion of an embodiment, including for example one or more of the functions described herein. For example, processor 110 may operate a connectivity program such as a conventional Internet browser. The connectivity program may allow electronic device 100 to send and receive Internet content, such as location-based content and / or other web content, according to, for example, 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 an output device, which may include, for example, an audio output device such as a ringer, headphones, a speaker, a haptic output device such as a vibration transducer, an electronically deformable surface, an electronically deformable structure, a visual output device such as a display and / or a light. The electronic device may include an input device such as a light sensor, a proximity sensor, a microphone, a touch sensor, a force sensor, a button, a keypad, a motion sensor, a magnetic field sensor, a camera, etc. In at least one example embodiment, the device receives an indication of an input. The device may receive the indication from sensors, drivers, separate devices, etc. The information indicating the input may include information such as that which conveys the indication of the input, aspects of the indication of the input, information of the occurrence of the indication of the input, etc.

[0049] Figure 2Shows an example of a wireless communication system 200 according to at least one example embodiment. 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 send duplicate packets. In such a duplicate system, a sending device (e.g., base station 202, UE 201, or UE 204) may duplicate a packet. The original packet and the duplicate packet may be sent to a receiving device (e.g., base station 202, UE 201, or UE 204). Sending multiple packets including the same information may increase the likelihood that the receiving device receives the information included in the multiple packets.

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

[0051] Multiple UEs may be dispersed throughout the wireless communication system 200, and each UE may be fixed or mobile. A UE may also be referred to as a mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, cellular phone, user agent, mobile client, client, or some other suitable term. A UE may 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 capable of directly communicating 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 such communication between UE 201 and UE 204 is provided. One or more of a group of UEs utilizing sidelink communication may be within the coverage area of a cell. Other UEs in the group may be outside the coverage area of the cell or, in other cases, unable to receive transmissions from the base station 202. In some cases, a group of UEs communicating via sidelink communication may utilize a one-to-many (1:M) system, where each UE transmits to each other UE in the group. In some cases, the base station 202 assists in scheduling resources for sidelink communication. In other cases, sidelink communication is performed independently of the base station 202.

[0053] In some cases, UE 204 may operate as a relay UE for UE 201. For example, instead of the UE directly communicating with the base station 202, UE 204 may be configured to operate as a relay such that UE 201 communicates with the base station 202 via communication directly through UE 204. For example, UE 204 may operate as a layer 2 (L2) UE-to-network (U2N) relay.

[0054] Some UEs (e.g., MTC or IoT devices) can be low-cost or low-complexity devices and can 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 meters to measure or capture information and relay that information to a central server or application, which can utilize the information or present the information to a person interacting with the program or application. Some UEs can be designed to collect information or implement automated behavior of machines. Examples of applications of MTC devices include smart metering, inventory monitoring, water level monitoring, device monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[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 participating 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 UEs, or 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 be connected to core network 203 via the S1 interface. The core network can be an evolved packet core (EPC), which can 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 that processes signaling between UE 201 and the EPC. All user Internet protocol (IP) packets can be transported through the S-GW, which itself can be connected to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW can be connected to the network operator's IP services. The operator's IP services can include the Internet, intranet, IP multimedia subsystem (IMS), and packet-switched (PS) streaming services.

[0058] The core network 203 can provide user authentication, access authorization, tracking, IP connectivity, and other access, routing, or mobility functions. At least some of the network devices (such as the base station 202) can include subcomponents, such as access network entities, which can be examples of access node controllers (ANCs). Each access network entity can communicate with multiple UEs via a plurality of other access network transport entities, each of which can be an example of an intelligent radio head or a transmit / receive point (TRP). In some configurations, the various functions of each access network entity or base station can be distributed across various network devices (such as radio heads and access network controllers), or combined into a single network device (such as the base station 202).

[0059] The 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 (such as wireless local area networks (WLANs)) can use frequencies up to 4 GHz. This region can also be referred to as the decimeter band because the wavelength ranges from approximately 1 decimeter to 1 meter in length. UHF waves may primarily propagate through 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 transmissions are characterized by smaller antennas and shorter ranges (e.g., less than 100 km). In some cases, the 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 referred to as the millimeter band because the wavelength ranges from approximately 1 millimeter to 1 centimeter in length. Thus, 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, compared to UHF transmissions, EHF transmissions may experience greater atmospheric attenuation and shorter ranges.

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

[0061] Multiple-Input Multiple-Output (MIMO) wireless systems use a transmission scheme between a transmitter (e.g., a base station) and a receiver (e.g., a UE), where both the transmitter and the receiver are equipped with multiple antennas. Some parts of the wireless communication system 200 may use beamforming. For example, the base station 202 may have an antenna array, where the antenna array has antenna ports in multiple rows and columns, and the base station may use it for beamforming in communication with the UE 201. Signals can be sent multiple times in different directions (e.g., each transmission can be beamformed differently). The mmW receiver (e.g., the UE) may attempt multiple beams (e.g., antenna sub-arrays) while receiving the synchronization signal.

[0062] In some cases, the antennas of the base station 202 or the UE 201 may be located within one or more antenna arrays, which may support beamforming or MIMO operations. One or more base station antennas or antenna arrays may be collocated at an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with the base station 202 may be located at different geographical locations. The base station 202 may use multiple antennas or antenna arrays for beamforming operations to perform directional communication with the 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, the communication at the bearer or PDCP layer may be IP-based. In some cases, the RLC layer may perform packet segmentation and reassembly for communication over the logical channels. The Medium Access Control (MAC) layer may perform priority handling and multiplex the logical channels into the transport channels. The MAC layer may also use Hybrid Automatic Repeat Request (HARQ) to provide retransmission at the MAC layer to improve the link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide the establishment, configuration, and maintenance of the RRC connection between the UE 201 and the network device or the core network 203 that supports the radio bearers for user plane data. At the Physical (PHY) layer, the transport channels may be mapped to the physical channels.

[0064] Time intervals in LTE or NR can be expressed as multiples of a basic time unit, which can be a sampling period of Ts = 1 / 30720000 seconds. Time resources can be organized according to radio frames of length 10 ms (Tf = 307200 Ts), which can be identified by a system frame number (SFN) ranging from 0 to 1023. Each frame can include 10 subframes numbered from 0 to 9, each subframe being 1 millisecond long. A subframe can be further divided into two 0.5 ms time slots, each time slot including 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 includes 2048 sampling periods. In some cases, a subframe can be the smallest scheduling unit, also referred to as a TTI. In other cases, the TTI can be shorter than a subframe or can be dynamically selected (e.g., in a short TTI burst or in a selected component carrier using short TTI).

[0065] A resource element can consist of a symbol period and a subcarrier (e.g., a 15 KHz frequency range). A resource block can include 12 consecutive subcarriers in the frequency domain, and for a normal cyclic prefix in each orthogonal frequency division multiplexing (OFDM) symbol, 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). Thus, the more resource blocks the UE receives and the higher the modulation scheme, the higher the data rate is likely to be.

[0066] The wireless communication system 200 can support operation on multiple cells or carriers, a feature that can be referred to as carrier aggregation (CA) or multi-carrier operation. A carrier can also be referred to as a component carrier (CC), layer, channel, etc. The terms “carrier,” “component carrier,” “cell,” and “channel” can be 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 with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers.

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

[0068] Figure 3 is a diagram of a protocol stack 300 according to at least one example embodiment. Figure 3 The example 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 uses physical channels to provide an information transmission service to higher layers. The PHY layer 304 may be connected to the Media Access Control (MAC) layer 303 located at a higher layer through a transport channel. Data may be transmitted between the MAC layer 303 and the PHY layer 304 through the transport channel. Data may be transmitted between the physical layer on the transmitting side and the physical layer on the receiving side via a 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, the MAC layer 303 provides services to the Radio Link Control (RLC) layer 302 at a higher layer through logical channels. The second-layer RLC layer 302 supports reliable data transmission. The functions of the RLC layer 302 may be implemented by the functional blocks of the MAC layer 303. The Packet Data Convergence Protocol (PDCP) layer 301 performs a header compression function to reduce unnecessary control information for efficient transmission of Internet Protocol (IP) packets, such as IP version 4 (IPv4) packets or IP version 6 (IPv6) packets, over a radio interface with a relatively small 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, an operating network node includes one or more PDCP entities for performing PDCP layer activities. In operation, a PDCP entity receives data to be transmitted from a higher layer in a PDCP service data unit (SDU). The PDCP entity performs various operations on the PDCP SDU it receives from the higher layer for transmission, such as header compression, uplink data compression, integrity protection, encryption, etc. The PDCP entity performs these operations on the received PDCP SDU to generate a PDCP packet data unit (PDU), which is sent in a manner that the PDCP entity sends the PDCP SDU to a lower layer 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, an operating network node includes one or more RLC entities for performing RLC layer activities. In operation, an RLC entity receives data to be transmitted from a higher layer in an RLC SDU. The RLC entity performs various operations on the RLC SDU it receives from the higher layer for transmission, such as header compression, uplink data compression, integrity protection, encryption, etc. The RLC entity performs these operations on the received RLC SDU to generate an RLC PDU, which is sent in a manner that the RLC entity sends the RLC SDU to a lower layer for transmission.

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

[0074] Figure 4 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 that correspond to Figure 4 at least some of the activities of. For example, there may be a set of operations associated with the activities of one or more devices of Figure 4 the. Devices (such as Figure 1the electronic 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 device 204 or a part thereof) may utilize this set of operations. The device may include components for performing these operations, such as including Figure 1 the processor 110. In an example embodiment, the device (such as Figure 1 the electronic device 100) is transformed by causing a memory (such as Figure 1 the memory 140) to include computer code that is configured to work with a processor (such as Figure 1 the processor 110) such that the device performs Figure 4 a set of operations.

[0075] With the development of wireless communication, it has become increasingly important to facilitate point-to-multipoint communication. In at least one example embodiment, a UE implements multicast and broadcast services (MBS) to provide point-to-multipoint communication with a 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 a scenario 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 UEs receive the packets in a point-to-point communication manner. In at least one example embodiment, this type of communication is referred to as broadcast MBS. In this way, broadcast MBS is characterized in that each UE receives a different copy of the packet in a separate point-to-point communication manner from the RAN.

[0076] In other cases, it may be necessary for the RAN to support the following scenario: where the RAN 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 the packets in a point-to-multipoint communication manner. In at least one example embodiment, this type of communication is referred to as multicast MBS. In this way, multicast MBS is characterized in that each UE receives the same packet in a single point-to-multipoint communication manner 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. The configuration information includes parameters required for the UE to receive MBS information and to effectively communicate with the RAN regarding the MBS information. For example, the UE may be configured to receive MBS information regarding 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 the RAN can convey control information regarding the communication flow by identifying the applicable communication flow. In this way, the UE and the RAN can use the 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 the 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 MBS information for the MBS session is to be performed. In at least one example embodiment, the UE receives a paging transmission indicating the MBS session identifier of the MBS session and then performs an operation to receive the MBS information of the MBS session indicated in the paging transmission. For example, the paging transmission may include a paging record indicating the MBS session identifier of the MBS session. In some cases, the UE may receive the paging transmission during a period when 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 resume procedure based on the paging transmission (or the paging record included in the paging transmission) to receive the MBS information for the MBS session indicated by the MBS session identifier. In this way, the RRC connection resume procedure transitions the UE to a state capable of receiving MBS information. In this way, the UE can initiate an RRC connection resume procedure based on at least one paging record because the paging record triggers the initiation.

[0079] Due to the involvement of point-to-point communication, it may be necessary for the UE to transition from the RRC_INACTIVE state to the RRC_CONNECTED state to receive broadcast MBS information. However, it may be desirable for the UE to receive MBS information while in the RRC_INACTIVE state, at least because the point-to-multipoint communication involving multicast MBS does not necessarily require the UE to be in the RRC_CONNECTED state. In at least one example embodiment, the UE utilizes the small data transfer (SDT) procedure, which allows data and / or signaling to be transferred while the UE remains in the RRC_INACTIVE state. Due to the fact that the UE's reception of MBS information is initiated by paging transmission, in this case, the SDT procedure is initiated by the RAN rather than by the UE. In at least one example embodiment, the SDT initiated by the RAN 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 resume procedure that specifies MT-SDT. By initiating an RRC connection resume procedure that specifies MT-SDT, the UE enables the RAN to perform the operations necessary to transfer MBS information to the UE using SDT, which allows the UE to receive data while in the RRC_INACTIVE state. In at least one example embodiment, the UE specifies MT-SDT by setting the resume cause of the RRC connection resume procedure to indicate MT-SDT. In at least one example embodiment, the UE initiates MT-SDT by sending an RRC connection resume request to the RAN that includes a resume cause identifying MT-SDT.

[0081] In at least one example embodiment, the paging transmission indicates whether the UE should consider initiating an RRC connection resume procedure that specifies MT-SDT. For example, if the conditions are favorable, the RAN may want the UE to receive information using SDT. 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 indication from the RAN to the UE to initiate an RRC connection resume procedure that specifies MT-SDT. In this way, the UE can initiate the RRC connection resume procedure based on the paging record, since determining whether MT-SDT is specified in the RRC connection resume procedure is partially based on whether the paging transmission specifies MT-SDT.

[0082] As described above, there may be a case where the UE determines to receive MBS information in the RRC_CONNECTED state. In this case, the UE initiates an RRC connection resume procedure, where the resume reason indicates communication in the RRC_CONNECTED state. In at least one example embodiment, the UE uses the resume reason of Mobile Terminal Access (MT-Access) to initiate the RRC connection resume procedure to initiate communication in the RRC_CONNECTED state.

[0083] Due to the differences between the operation of broadcast MBS and the operation of multicast MBS, as well as the differences in the capabilities available for 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 of an MBS session. In at least one example embodiment, the UE receives an MBS configuration message, which includes the configuration information of the MBS session. The configuration information includes parameters for managing the way the UE and the RAN perform communication for the MBS session. In at least one example embodiment, the configuration information of the 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 of the 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 of 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 of the multicast MBS session and the configuration information of the broadcast MBS information include an MBS session identifier. The MBS session identifier can be used to identify the MBS session in various situations. For example, the MBS session identifier can be used in paging transmissions to identify the MBS session for which the UE is to receive 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, it may be necessary to provide backward compatibility for the multicast MBS configuration specification as well as further configuration specifications for broadcast MBS sessions.

[0087] As described above, the configuration information of the multicast MBS session is necessarily different from the configuration information of the broadcast MBS session. In at least one example embodiment, the broadcast MBS session is configured according to the received broadcast MBS session information record. In at least one example embodiment, the multicast MBS session is configured according to the received multicast MBS session information record. In at least one example embodiment, the record is an information element.

[0088] In at least one example embodiment, a broadcast MBS session information record includes parameters for specifying the communication of an 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: · An MBS session identifier, such as a TMGI for identifying the MBS session, · A Radio Network Temporary Identifier (RNTI) that identifies the RNTI used for scrambling the communication of the MBS session, · Broadcast-specific Multicast Resource Bearer (MRB) configuration information for the MBS session communication, · Multicast Traffic Channel (MTCH) configuration information for the MBS session communication, and · Physical Downlink Shared Channel (PDSCH) configuration information for the MBS session communication.

[0089] 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 multiple broadcast MBS sessions is a list of MBS session information for broadcast. In at least one example embodiment, the list of MBS session information for broadcast includes a list of broadcast MBS session information records. In at least one example embodiment, the list of MBS session information for broadcast is an MBS-SessionInfoList information element.

[0090] In at least one example embodiment, a multicast MBS session information record includes parameters for specifying the communication of an associated multicast MBS session. The multicast MBS session information record may include the following: · An MBS session identifier, such as a TMGI for identifying the MBS session, · An RNTI that identifies the RNTI used for scrambling the MBS session communication, · Multicast-specific MRB configuration information for the MBS session communication, · MTCH configuration information for the MBS session communication, · PDSCH configuration information for the MBS session communication, · A threshold indicator for receiving data in the RRC_INACTIVE state, · A PDCP synchronization indicator for receiving data in the RRC_INACTIVE state, and · An indication for stopping monitoring, such as an indicator for instructing the UE to stop monitoring the RNTI of the MBS session.

[0091] In at least one example embodiment, the UE receives configuration information for a plurality of multicast MBS sessions. In at least one example embodiment, the configuration information for the plurality of 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.

[0092] As can be seen from the above discussion, the multicast MBS session information record and the broadcast MBS session information record are different from each other. For example, the multicast MBS session information record includes information that cannot be included in the broadcast MBS session information record, such as multicast-specific MRB configuration information, a threshold indicator, a PDCP synchronization indicator, and an indication for stopping monitoring. In addition, a subset of the parameters included in the multicast MBS session information record is present in the broadcast MBS session information record, such as the MBS session identifier, RNTI, MTCH configuration information, and PDSCH configuration information.

[0093] In at least one example embodiment, the UE receives an MBS configuration message including configuration information for an MBS session. 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, the configuration information for the plurality of multicast MBS sessions is received in the MBS multicast configuration message, and the configuration information for the plurality of 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 the parameters included in the MBS multicast configuration message is present in the MBS broadcast configuration message.

[0094] Although 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 providing a common structure for configuring broadcast MBS and for configuring multicast MBS.

[0095] In some cases, it may be necessary to provide a common MBS configuration message. In at least one example embodiment, the common 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 common list of MBS session information, which may include both multicast MBS session information records and broadcast MBS session information records. In at least one example embodiment, the common MBS configuration message includes a common list of MBS session information, where each element in the common list of MBS session information is a multicast MBS session information record or a broadcast MBS session information record.

[0096] In some cases, it may be necessary to provide a common MBS session information record. As previously mentioned, the configuration information of a multicast MBS session is necessarily different from the configuration information of a broadcast MBS session. In at least one example embodiment, the broadcast MBS session and the multicast MBS session are each configured according to the received common MBS session information record. In at least one example embodiment, the record is an information element.

[0097] In at least one example embodiment, the common MBS session information record includes parameters for specifying the communication of the associated broadcast MBS session or multicast MBS session. In at least one example embodiment, the common MBS session information record is an MBS-SessionInfo information element. In at least one example embodiment, the common MBS information element is specified by mandatory parameters and optional parameters, where the mandatory parameters are parameters common to both the multicast MBS session configuration and the broadcast MBS session configuration, and 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 only used to characterize the nature of the parameters with respect to the common configuration structure, and do not involve any determination of whether the related features are mandatory or optional as claim elements. In this way, the use of the terms optional and mandatory does not limit the claims in any way, unless these terms are explicitly included in the claims. The common MBS session information record may include the following: · Mandatory - MBS session identifier, such as TMGI for identifying the MBS session, · Mandatory - RNTI, which identifies the RNTI used for scrambling the communication of the MBS session, · Mandatory - MRB configuration information, which is one of the following information: · Broadcast - specific MRB configuration information for MBS session communication, or · Multicast - specific MRB configuration information for MBS session communication, · Mandatory - Multicast Traffic Channel (MTCH) configuration information for MBS session communication, and · Mandatory - PDSCH configuration information for MBS session communication. · Optional - Threshold indicator for receiving data in the RRC_INACTIVE state, · Optional - PDCP synchronization indicator for receiving data in the RRC_INACTIVE state, and · Optional - Indicator for stopping monitoring, such as an indicator for instructing the UE to stop monitoring the RNTI of the MBS session.

[0098] In at least one example embodiment, the UE receives configuration information for multiple MBS sessions, and the MBS sessions may 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 list of common MBS session information. In at least one example embodiment, the list of common MBS session information includes a list of common MBS session information records. In at least one example embodiment, the list of MBS session information for broadcasting is the MBS-SessionInfoList information element.

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

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

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

[0102] At interaction 412, the UE 401 receives a paging transmission from the 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 the RRC_INACTIVE state when receiving the paging transmission. In at least one example embodiment, the paging record indicates a specific UE for receiving 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 may be a full I-RNTI. In at least one example embodiment, the paging record includes an MT-SDT indicator.

[0103] In at least one example embodiment, a paging record includes a paging group list that indicates one or more MBS sessions for which the UE is to 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 for which the UE has been configured.

[0104] In at least one example embodiment, the paging transmission is a paging message received from a base station (e.g., Figure 2 base station 202). In at least one example embodiment, the paging transmission is a message transfer side link message received from another UE (e.g., Figure 2 UE 204). In such an example, the other UE may be a layer 2 (L2) UE-to-network (U2N) relay UE.

[0105] At interaction 413, UE 401 initiates an RRC connection restoration procedure in which the restoration cause is set to indicate MT-SDT and sends an RRC restoration request in which the restoration cause indicates MT-SDT. It should be noted that although Figure 4 the example shows the UE sending an RRC restoration request indicating MR-SDT, in some cases, the UE may wish to instead send an RRC restoration request indicating MT-Access rather than MT-SDT.

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

[0107] 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.

[0108] In some cases, it may be necessary to ensure that the conditions for receiving data in the RRC_INACTIVE state are met before initiating the RRC connection resume 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 the RRC connection resume procedure for a specified MT-SDT when it has determined that the conditions for receiving data in the RRC_INACTIVE state are met, and the UE initiates the RRC connection resume procedure for a specified MT-Access when 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.

[0109] 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 measured reference signal received power (RSRP) to make the SDT reliably effective. In such a case, it may be necessary to configure an RSRP threshold for the SDT.

[0110] For example, it may be necessary to avoid initiating the 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. Additionally, it may be desirable to initiate the 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 the RRC connection resume 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 the RRC connection resume 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.

[0111] In some cases, a paging group list included in a paging transmission may indicate an MBS session that is not configured to receive data in the RRC_INACTIVE state. For example, the paging group may indicate a broadcast MBS session. In such a case, the UE may necessarily need to receive MBS information of the broadcast MBS session in the RRC_CONNECTED state. Therefore, it may be desirable for the UE to initiate an RRC connection resume procedure specifying MT-Access when it has 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. Therefore, it may be desirable for the UE to initiate an RRC connection resume procedure specifying MT-SDT when it has determined that 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 (e.g., when all MBS sessions indicated by the MBS session identifiers included in the paging group list are multicast MBS sessions).

[0112] In at least one exemplary embodiment, the UE determines 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. In at least one example embodiment, the UE initiates an RRC connection resume procedure specifying MT-SDT when it has determined that 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 the UE initiates an RRC connection resume procedure specifying MT-Access when it has determined that 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.

[0113] Figure 5 is a flowchart illustrating activities associated with initiating communication according to at least one example embodiment. In at least one example embodiment, there is a set of operations that correspond to Figure 5 the activities. For example Figure 1 a device such as the electronic device 100 or a portion thereof can utilize the 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 (such as Figure 1 the electronic device 100) is transformed by causing a memory (such as Figure 1 the memory 140) to include computer code that is configured to work with a processor (such as Figure 1 the processor 110) such that the device performs Figure 5 the set of operations.

[0114] At block 501, the apparatus receives configuration information for a plurality of multicast MBS sessions and configuration information for a plurality of broadcast MBS sessions.

[0115] At block 502, when the UE is in the RRC_INACTIVE state, the apparatus receives a paging transmission including at least one paging record.

[0116] At block 503, the apparatus determines whether a condition for receiving data in the RRC_INACTIVE state is satisfied.

[0117] At block 504, the apparatus determines 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.

[0118] At block 505, if it is determined that the condition for receiving data in the RRC_INACTIVE state is 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, the process proceeds to block 506. If the apparatus has determined that the condition for receiving data in the RRC_INACTIVE state is 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, the process proceeds to block 507.

[0119] At block 506, the apparatus initiates an RRC connection resume procedure, where the resume cause is set to indicate MT-SDT. In this way, the UE initiates an RRC connection resume procedure based on at least one paging record, where the resume cause is set to indicate MT-SDT when 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.

[0120] At block 507, the apparatus initiates an RRC connection resume procedure, where the resume cause is set to indicate MT-Access. In this way, the UE initiates an RRC connection resume procedure based on at least one paging record, where the resume cause is set to indicate MT-Access when the condition for receiving data in the RRC_INACTIVE state is determined not to be 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.

[0121] 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, on a separate device, or on multiple separate devices. If desired, part of the software, application logic, and / or hardware may reside on a device, part of the software, application logic, and / or hardware may reside on a separate device, and part of the software, application logic, and / or hardware may reside on multiple separate devices. In an example embodiment, the application logic, software, or instruction set is maintained on any of a variety of conventional computer-readable media.

[0122] If desired, the different functions described herein may be performed in a different order and / or concurrently with each other. For example, Figure 5 block 503 of Figure 5 may be performed after Figure 5 block 504 of Figure 5 In addition, if desired, one or more of the above functions may be optional or may be combined. For example,

[0123] Although the various aspects of the present invention are set forth in the independent claims, other aspects of the present invention include other combinations of the features of the described embodiments and / or dependent claims with the features of the independent claims, not just the combinations explicitly set forth in the claims.

[0124] It is also noted herein that although the above describes exemplary embodiments of the present invention, such descriptions should not be considered limiting. Instead, various changes and modifications may be made without departing from the scope of the present 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 the RRC_INACTIVE state, and configuration information for a plurality of broadcast MBS sessions; When the UE is in the RRC_INACTIVE state, receiving a paging transmission, the 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 the 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 met; 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 an RRC connection resume procedure based on at least one paging record, wherein the resume reason is set to indicate MT-SDT in the following cases: The condition for receiving data in the RRC_INACTIVE state is determined to be met, 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 an RRC connection resume procedure based on at least one paging record, wherein the resume reason is set to indicate Mobile Terminal Access (MT-Access) in the following cases: The condition for receiving data in the RRC_INACTIVE state is determined not to be met, 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 according to claim 1, wherein: The MBS session identifier is a Temporary Mobile Group Identity (TMGI), 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 includes: determining whether each TMGI included in the paging group list identifies an MBS session configured to receive data in the RRC_INACTIVE state.

3. The method according to claim 1, wherein Determining whether a condition for receiving data in the RRC_INACTIVE state is met includes: the Media Access Control (MAC) entity determining whether the Reference Signal Received Power (RSRP) of the downlink path loss reference is higher than the configured RSRP threshold for Small Data Transmission (SDT).

4. The method according to claim 1, wherein: Receiving configuration information for a plurality of multicast MBS sessions in an MBS multicast configuration message, Receiving configuration information for a plurality of broadcast MBS sessions 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 according to claim 4, wherein: The MBS multicast configuration message includes information that cannot be included in the MBS broadcast configuration message, and a subset of the parameters included in the MBS multicast configuration message exists in the MBS broadcast configuration message.

6. The method according to claim 1, wherein: Configuration information for a plurality of multicast MBS sessions and configuration information for a 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 according to 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 MBS session information list, The configuration information for the plurality of multicast MBS sessions includes a plurality of common MBS session information elements included in the common MBS session information list, and The plurality of broadcast MBS sessions are a plurality of common MBS session information elements included in the common MBS session information list, which 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 being configured to work with the processor such that the UE at least performs the following operations: Receive configuration information for a plurality of multicast and broadcast services (MBS) sessions configured to receive data in the 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, the 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 that matches the radio network temporary identifier (RNTI) of the UE, and A mobile terminal small data transmission (MT-SDT) indicator; Determine whether the conditions for receiving data in the RRC_INACTIVE state are met; 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 an RRC connection resume procedure based on at least one paging record, wherein when the following conditions are met, the resume reason is set to indicate MT-SDT: The conditions for receiving data in the RRC_INACTIVE state are determined to be met, 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 an RRC connection resume procedure based on at least one paging record, wherein when the following conditions are met, the resume reason is set to indicate mobile terminal access (MT-Access): The conditions for receiving data in the RRC_INACTIVE state are determined not to be met, 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.

9. The UE according to claim 8, wherein: The MBS session identifier is a Temporary Mobile Group Identity (TMGI), 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 includes: determining whether each TMGI included in the paging group list identifies an MBS session configured to receive data in the RRC_INACTIVE state.

10. The UE according to claim 8, wherein, Determining whether the conditions for receiving data in the RRC_INACTIVE state are met includes: the Media Access Control (MAC) entity determining whether the Reference Signal Received Power (RSRP) of the downlink path loss reference is higher than the configured RSRP threshold for Small Data Transmission (SDT).

11. The UE according to claim 8, wherein: Receiving configuration information for a plurality of multicast MBS sessions in an MBS multicast configuration message, Receiving configuration information for a plurality of broadcast MBS sessions 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 according to claim 11, wherein: The MBS multicast configuration message includes information that cannot be included in the MBS broadcast configuration message, and a subset of the parameters included in the MBS multicast configuration message is present in the MBS broadcast configuration message.

13. The UE according to claim 8, 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 a plurality of multicast MBS sessions includes a list of MBS session information for multicast, and the configuration information for a plurality of broadcast MBS sessions is a list of MBS session information for broadcast.

14. The UE according to claim 13, wherein: The configuration information for a plurality of multicast MBS sessions and the configuration information for a plurality of broadcast MBS sessions are included in a common MBS session information list, The configuration information for a plurality of multicast MBS sessions includes a plurality of common MBS session information elements included in the common MBS session information list, and The plurality of broadcast MBS sessions are a plurality of common MBS session information elements included in the common MBS session information list, which are different from the common MBS session information elements of the 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 Services (MBS) sessions configured to receive data in the 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, the 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 the radio network temporary identifier (RNTI) of the UE, and a mobile terminal small data transmission (MT-SDT) indicator; Determine whether conditions for receiving data in the RRC_INACTIVE state are met; 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 an RRC connection resume procedure based on at least one paging record, wherein, in the following cases, the resume cause is set to indicate MT-SDT: The conditions for receiving data in the RRC_INACTIVE state are determined to be met, 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 an RRC connection resume procedure based on at least one paging record, wherein, in the following cases, the resume cause is set to indicate mobile terminal access (MT-Access): The conditions for receiving data in the RRC_INACTIVE state are determined not to be met, 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.

16. The medium according to claim 15, wherein: The MBS session identifier is a temporary mobile group identity (TMGI), 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 includes: determining whether each TMGI included in the paging group list identifies an MBS session configured to receive data in the RRC_INACTIVE state.

17. The medium according to claim 15, wherein Determining whether conditions for receiving data in the RRC_INACTIVE state are met includes: the media access control (MAC) entity determining whether the reference signal received power (RSRP) of the downlink path loss reference is higher than the configured RSRP threshold for small data transmission (SDT).

18. The medium according to claim 15, wherein: Receive configuration information for a plurality of multicast MBS sessions in an MBS multicast configuration message, Receive configuration information for a plurality of broadcast MBS sessions 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 according to claim 18, wherein: The MBS multicast configuration message includes information that cannot be included in the MBS broadcast configuration message, and a subset of the parameters included in the MBS multicast configuration message exists in the MBS broadcast configuration message.

20. The medium according to claim 15, wherein: Receive configuration information for multiple multicast MBS sessions and configuration information for multiple broadcast MBS sessions in a common MBS configuration message. 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.

Images