Multicast broadcast service session status reporting

Abstract

Aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may leave a multicast broadcast service (MBS) session without leaving a packet data unit (PDU) session associated with the MBS session. The UE may send a signaling message after leaving the MBS session. The signaling message may include an information element (IE) that includes an MBS session status indication associated with the MBS session. Numerous other aspects are described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to Greek patent application No. 20220100825, entitled "MULTICAST BROADCASTSERVICES SESSION STATUS REPORTING" filed on October 7, 2022 and assigned to the assignee of this application. The disclosure of the prior application is considered a part of this patent application and is incorporated into this patent application by reference. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communications, and to techniques and apparatus for multicast broadcast service (MBS) session status reporting. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard promulgated by the Third Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communications for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with a network node via downlink communications and uplink communications. A "downlink" (or "DL") refers to a communication link from a network node to a UE, and an "uplink" (or "UL") refers to a communication link from a UE to a network node. Some wireless networks may support device-to-device communications, such as via a local link (e.g., a side link (SL), a wireless local area network (WLAN) link, and / or a wireless personal area network (WPAN) link, etc.).

[0006] The above-mentioned multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different UEs to communicate at a city, country, region and / or global level. New Radio (NR) (which may be referred to as 5G) is a set of enhancements to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by: improving spectrum efficiency; reducing costs; improving services; utilizing new spectrum; and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink, CP-OFDM and / or single carrier frequency division multiplexing (SC-FDM) (also known as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink to better integrate with other open standards; and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation. As the demand for mobile broadband access continues to increase, further improvements in LTE, NR and other radio access technologies remain useful. Summary of the invention

[0007] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a user equipment (UE). The method may include leaving a multicast broadcast service (MBS) session without leaving a packet data unit (PDU) session associated with the MBS session. The method may include sending a signaling message after leaving the MBS session, the signaling message including an information element (IE) including an MBS session state indication associated with the MBS session.

[0008] Some aspects described herein relate to a method of wireless communication performed by an apparatus of a UE. The method may include leaving an MBS session without leaving a PDU session associated with the MBS session. The method may include sending a signaling message for receipt by a radio access network (RAN) node based on leaving the MBS session, the signaling message including an indication that the UE has left the MBS session.

[0009] Some aspects described herein relate to a method performed by an apparatus of a core network node. The method may include receiving a non-access stratum (NAS) message including an MBS session status IE, wherein the MBS session status information IE includes an MBS session identifier corresponding to an MBS session of a UE and an MBS session status indication indicating a status of the MBS session. The method may include identifying a session management function (SMF) node based at least in part on an MBS context associated with the UE and the MBS session identifier. The method may include forwarding the MBS session status indication to the SMF node.

[0010] Some aspects described herein relate to a method performed by an apparatus of a RAN node. The method may include receiving a signaling message including an indication that a UE has left an MBS session. The method may include removing the UE from the MBS session based at least in part on the indication that the UE has left the MBS session.

[0011] Some aspects described herein relate to a method performed by an apparatus of a core network node. The method may include receiving an indication to release an MBS session of a UE, the indication including at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session. The method may include releasing the MBS session based at least in part on the indication to release the MBS session.

[0012] Some aspects described herein relate to a UE for wireless communication. The user equipment may include: a memory and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to leave an MBS session without leaving a PDU session associated with the MBS session. The one or more processors may be configured to send a signaling message after leaving the MBS session, the signaling message including an IE, the IE including an MBS session state indication associated with the MBS session.

[0013] Some aspects described herein relate to a UE for wireless communication. The user equipment may include: a memory and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to leave an MBS session without leaving a PDU session associated with the MBS session. The one or more processors may be configured to send a signaling message for receipt by a RAN node based on leaving the MBS session, the signaling message including an indication that the UE has left the MBS session.

[0014] Some aspects described herein relate to a core network node. The core network node may include a memory and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to receive a NAS message including an MBS session status IE. The one or more processors may be configured to identify an SMF node based at least in part on an MBS context and an MBS session identifier associated with a UE. The one or more processors may be configured to forward an MBS session status indication to the SMF node.

[0015] Some aspects described herein relate to a RAN node. The RAN node may include a memory and one or more processors coupled to the memory. The one or more processors may be configured to receive a signaling message including an indication that a UE has left an MBS session. The one or more processors may be configured to remove the UE from the MBS session based at least in part on the indication that the UE has left the MBS session.

[0016] Some aspects described herein relate to a core network node. The core network node may include a memory and one or more processors, the one or more processors coupled to the memory. The one or more processors may be configured to receive an indication to release an MBS session of a UE, the indication including at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session. The one or more processors may be configured to release the MBS session based at least in part on the indication to release the MBS session.

[0017] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set, when executed by one or more processors of a device, may cause the one or more processors to leave an MBS session without leaving a PDU session associated with the MBS session. The instruction set, when executed by the one or more processors, may cause the device to send a signaling message after leaving the MBS session, the signaling message including an IE, the IE including an MBS session state indication associated with the MBS session.

[0018] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication, which when executed by one or more processors of a device may cause the device to leave an MBS session without leaving a PDU session associated with the MBS session. The set of instructions, when executed by the one or more processors, may cause the device to send a signaling message for receipt by a RAN node based on leaving the MBS session, the signaling message including an indication that a UE has left the MBS session.

[0019] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set via one or more instructions, which when executed by one or more processors of a device may cause the device to receive a NAS message including an MBS session state IE. The instruction set, when executed by the one or more processors, may cause the device to identify an SMF node based at least in part on an MBS context and an MBS session identifier associated with a UE. The instruction set, when executed by the one or more processors, may cause the device to forward an MBS session state indication to the SMF node.

[0020] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions that, when executed by one or more processors of a device, may cause the device to receive a signaling message including an indication that a UE has left an MBS session. The set of instructions, when executed by the one or more processors, may cause the device to remove a UE from the MBS session based at least in part on the indication that the UE has left the MBS session.

[0021] Some aspects described herein relate to a non-transitory computer-readable medium storing an instruction set via one or more instructions, which when executed by one or more processors of a device may cause the device to receive an indication to release an MBS session of a UE, the indication comprising at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session. The instruction set, when executed by the one or more processors, may cause the device to release the MBS session based at least in part on the indication to release the MBS session.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for leaving an MBS session without leaving a PDU session associated with the MBS session. The apparatus may include means for sending a signaling message after leaving the MBS session, the signaling message including an IE including an MBS session state indication associated with the MBS session.

[0023] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for leaving an MBS session without leaving a PDU session associated with the MBS session. The apparatus may include means for sending a signaling message for receipt by a RAN node based on leaving the MBS session, the signaling message including an indication that the UE has left the MBS session.

[0024] Some aspects described herein relate to an apparatus. The apparatus may include means for receiving a NAS message including an MBS session status IE, wherein the MBS session status information IE includes an MBS session identifier corresponding to an MBS session of a UE and an MBS session status indication indicating a status of the MBS session. The apparatus may include means for identifying an SMF node based at least in part on an MBS context associated with the UE and the MBS session identifier. The apparatus may include means for forwarding the MBS session status indication to the SMF node.

[0025] Some aspects described herein relate to an apparatus. The apparatus may include means for receiving a signaling message including an indication that a UE has left an MBS session. The apparatus may include means for removing a UE from the MBS session based at least in part on the indication that the UE has left the MBS session.

[0026] Some aspects described herein relate to an apparatus. The apparatus may include means for receiving an indication to release an MBS session of a UE, the indication including at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session. The apparatus may include means for releasing the MBS session based at least in part on the indication to release the MBS session.

[0027] The various aspects generally include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network entities, network nodes, wireless communication devices and / or processing systems as fully described herein with reference to the drawings, specifications and appendices and as illustrated in the drawings, specifications and appendices.

[0028] The features and technical advantages of examples according to the present disclosure have been outlined quite broadly above so that the following specific embodiments may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as a basis for modifying or designing other structures for achieving the same purpose of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein, both in terms of their organization and method of operation, and the associated advantages will be better understood by considering the following description in conjunction with the accompanying drawings. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description and not as a definition of limitations of the claims.

[0029] Although various aspects are described in the present disclosure by illustrating some examples, it will be understood by those skilled in the art that such aspects can be implemented in many different arrangements and scenarios. The technology described herein can be implemented using different platform types, devices, systems, shapes, sizes and / or packaging arrangements. For example, some aspects can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / shopping equipment, medical equipment and / or artificial intelligence devices). Various aspects can be implemented in chip-level components, modular components, non-modular components, non-chip-level components, device-level components and / or system-level components. The equipment incorporating the various aspects and features described may include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals may include one or more components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders and / or summers). The various aspects described herein are intended to be practiced in various devices, components, systems, distributed arrangements and / or end-user devices of various sizes, shapes and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to be able to understand the above-mentioned features of the present disclosure in detail, a more specific description briefly summarized above may be obtained by reference to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope thereof, as the specification may admit of other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0031] Figure 1 is a diagram illustrating an example of a wireless network according to the present disclosure.

[0032] Figure 2 is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.

[0033] Figure 3 is a diagram illustrating an example decomposed base station architecture according to the present disclosure.

[0034] Figure 4 is a diagram of an example of a core network according to the present disclosure.

[0035] Figure 5 is a diagram of example components of devices associated with a core network according to the present disclosure.

[0036] Fig. 6A and Figure 6B is a diagram illustrating an example associated with an MBS session status report according to the present disclosure.

[0037] Figure 7 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0038] Figure 8 is a diagram illustrating an example process performed, for example, by a UE according to the present disclosure.

[0039] Fig. 9 is a diagram illustrating an example process performed, for example, by a core network node according to the present disclosure.

[0040] Fig.10 is a diagram illustrating an example process performed, for example, by a RAN node according to the present disclosure.

[0041] Fig.11 is a diagram illustrating an example process performed, for example, by a core network node according to the present disclosure.

[0042] Figures 12 to 15 is a diagram of an example apparatus according to the present disclosure. DETAILED DESCRIPTION

[0043] The various aspects of the present disclosure are described more fully below with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms, and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. Instead, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. It should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the disclosure disclosed herein, whether it is independently or in combination with any other aspect of the disclosure. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such a device or method practiced using other structures, functionality, or structure and functionality in addition to or different from the various aspects of the disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the present invention.

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

[0045] Although various aspects may be described herein using terms generally associated with 5G or new radio (NR) radio access technology (RAT), various aspects of the present disclosure may be applicable to other RATs, such as 3G RAT, 4G RAT and / or RATs beyond 5G (e.g., 6G).

[0046] Figure 11 is a diagram illustrating an example of a wireless network 100 according to the present disclosure. The wireless network 100 may be a 5G (e.g., NR) network and / or a 4G (e.g., Long Term Evolution (LTE)) network, or may include elements of a 5G (e.g., NR) network and / or elements of a 4G (e.g., Long Term Evolution (LTE)) network, etc. The wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), and / or other entities. The network node 110 is a network node that communicates with the UE 120. As shown in the figure, the network node 110 may include one or more network nodes. For example, the network node 110 may be a converged network node, which means that the converged network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node (e.g., within a single device or unit). As another example, the network node 110 may be a decomposed network node (sometimes referred to as a decomposed base station), which means that the network node 110 is configured to utilize a protocol stack that is physically or logically distributed between two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0047] In some examples, the network node 110 is a network node that communicates with the UE 120 via a radio access link, such as an RU, or includes a network node that communicates with the UE 120 via a radio access link, such as an RU. In some examples, the network node 110 is a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU, or includes a network node that communicates with other network nodes 110 via a fronthaul link or a midhaul link, such as a DU. In some examples, the network node 110 is a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU, or includes a network node that communicates with other network nodes 110 via a midhaul link or communicates with a core network via a backhaul link, such as a CU. In some examples, the network node 110 (such as an aggregated network node 110 or a decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. The network nodes 110 may include, for example, NR base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, transmit receive points (TRPs), DUs, RUs, CUs, mobility elements of a network, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, the network nodes 110 may be interconnected to each other or to one or more other network nodes 110 in the wireless network 100 via various types of fronthaul interfaces, midhaul interfaces, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks, using any suitable transport network).

[0048] In some examples, the network node 110 may provide communication coverage for a particular geographic area. In the Third Generation Partnership Project (3GPP), the term "cell" may refer to the coverage area of ​​the network node 110 and / or the network node subsystem serving the coverage area, depending on the context in which the term is used. The network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by a UE 120 with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by a UE 120 with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by a UE 120 associated with the femto cell (e.g., a UE 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. The network node 110 for a femto cell may be referred to as a femto network node or a home network node. Figure 1In the example shown in , network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. A network node may support one or more (e.g., three) cells. In some examples, a cell may not necessarily be stationary, and the geographic area of ​​a cell may move depending on the location of a mobile network node 110 (e.g., a mobile network node).

[0049] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, a "base station" or "network node" may refer to a CU, a DU, a RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of a plurality of different devices (which may be located in the same geographic location or in different geographic locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of the function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions may be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one of the base station functions, but not another base station function. In this way, a single device may include more than one base station.

[0050] The wireless network 100 may include one or more relay stations. A relay station is a network node that can receive transmissions of data from an upstream node (e.g., a network node 110 or a UE 120) and transmit transmissions of data to a downstream node (e.g., a UE 120 or a network node 110). A relay station may be a UE 120 that is capable of relaying transmissions for other UEs 120. Figure 1 In the example shown in , a network node 110d (e.g., a relay network node) may communicate with a network node 110a (e.g., a macro network node) and a UE 120d to facilitate communication between the network node 110a and the UE 120d. A network node 110 that relays communications may be referred to as a relay station, a relay base station, a relay network node, a relay node, a relay, etc.

[0051] The wireless network 100 may be a heterogeneous network that includes different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, etc. These different types of network nodes 110 may have different transmit power levels, different coverage areas, and / or different impacts on interference in the wireless network 100. For example, a macro network node may have a high transmit power level (e.g., 5 watts to 40 watts), while a pico network node, a femto network node, and a relay network node may have a lower transmit power level (e.g., 0.1 watt to 2 watts).

[0052] The network controller 130 may be coupled to or in communication with a set of network nodes 110 and may provide coordination and control for the network nodes 110. The network controller 130 may communicate with the network nodes 110 via a backhaul communication link or a midhaul communication link. The network nodes 110 may also communicate directly with each other or indirectly via a wireless or wired backhaul communication link. In some aspects, the network controller 130 may be, or may include, a CU or a core network node.

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

[0054] Some UEs 120 may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC UEs and / or eMTC UEs may include, for example, robots, drones, remote devices, sensors, meters, monitors, and / or location tags that may communicate with a network node, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered as Internet of Things (IoT) devices and / or may be implemented as NB-IoT (narrowband IoT) devices. Some UEs 120 may be considered as user premises equipment. UE 120 may be included inside a housing that houses components of UE 120, such as a processor component and / or a memory component. In some examples, the processor component and the memory component may be coupled together. For example, a processor component (e.g., one or more processors) and a memory component (e.g., a memory) may be operably coupled, communicatively coupled, electronically coupled, and / or electrically coupled.

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

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

[0057] The devices of the wireless network 100 may communicate using an electromagnetic spectrum that may be subdivided into various categories, bands, channels, etc., based on frequency or wavelength. For example, the devices of the wireless network 100 may communicate using one or more operating bands. In 5G NR, two initial operating bands have been identified as frequency ranges designated FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). It should be understood that, although a portion of FR1 is greater than 6 GHz, FR1 is often (interchangeably) referred to as the "below 6 GHz" band in various documents and articles. A similar naming problem sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0058] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz to 24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6GHz to 71GHz), FR4 (52.6GHz to 114.25GHz) and FR5 (114.25GHz to 300GHz). Each of these higher frequency bands falls within the EHF band.

[0059] Considering the above examples, unless otherwise specifically stated, it should be understood that if the term "below 6 GHz" or the like is used herein, the term may broadly refer to frequencies that may be below 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specifically stated, it should be understood that if the term "millimeter wave" or the like is used herein, the term may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR4-a or FR4-1, and / or FR5, or may be within the EHF band. It is contemplated that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0060] In some aspects, UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may leave a multicast broadcast service (MBS) session without leaving a packet data unit (PDU) session associated with the MBS session; and send a signaling message after leaving the MBS session, the signaling message including an information element (IE) including an MBS session state indication associated with the MBS session. Additionally or alternatively, as described in more detail elsewhere herein, the communication manager 140 may leave the MBS session without leaving a PDU session associated with the MBS session; and send a signaling message for receipt by a RAN node (e.g., network node 110) based on leaving the MBS session, the signaling message including an indication that UE 120 has left the MBS session. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0061] In some aspects, a RAN node, such as network node 110, may include a communications manager 150. As described in greater detail elsewhere herein, communications manager 150 may receive a signaling message including an indication that UE 120 has left an MBS session; and remove UE 120 from the MBS session based at least in part on the indication that UE 120 has left the MBS session. Additionally or alternatively, communications manager 150 may perform one or more other operations described herein.

[0062] As indicated above, Figure 1 are provided as examples. Other examples can be found in the Figure 1 The examples described are different.

[0063] Figure 2 2 is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless network 100 according to the present disclosure. The network node 110 may be equipped with a set of antennas 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with a set of antennas 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as an antenna 234 and a modem 254. In some examples, the network node 110 may include an interface, a communication component, or another component that facilitates communication with the UE 120 or another network node. Some network nodes 110 may not include a radio frequency component that facilitates direct communication with the UE 120, such as one or more CUs or one or more DUs.

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

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

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

[0067] One or more antennas (e.g., antennas 234a to 234t and / or antennas 252a to 252r) may include or be included within one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, and / or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, and / or antenna arrays may include one or more antenna elements (in a single housing or multiple housings), sets of coplanar antenna elements, sets of non-coplanar antenna elements, and / or may be coupled to one or more transmit and / or receive components (such as, Figure 2 One or more antenna elements of one or more components in.

[0068] On the uplink, at the UE 120, the transmit processor 264 may receive and process data from the data source 262 and control information from the controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, and / or CQI). The transmit processor 264 may generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be pre-decoded by the TX MIMO processor 266, where applicable, further processed by the modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and sent to the network node 110. In some examples, the modem 254 of the UE 120 may include a modulator and a demodulator. In some examples, the UE 120 includes a transceiver. The transceiver may include any combination of an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, and / or a TX MIMO processor 266. The transceiver may be used by a processor (eg, controller / processor 280) and memory 282 to perform the functions described herein (eg, with reference to FIG. 6A to FIG. 15 )Aspects of any of the methods described herein.

[0069] At the network node 110, uplink signals from the UE 120 and / or other UEs may be received by the antenna 234, processed by the modem 232 (e.g., a demodulator component (shown as DEMOD) of the modem 232), detected by the MIMO detector 236 (where applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 120. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller / processor 240. The network node 110 may include a communication unit 244 and may communicate with the network controller 130 via the communication unit 244. The network node 110 may include a scheduler 246 to schedule one or more UEs 120 for downlink communication and / or uplink communication. In some examples, the modem 232 of the network node 110 may include a modulator and a demodulator. In some examples, the network node 110 includes a transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, and / or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform operations described herein (e.g., with reference to FIG. 6A to FIG. 15 )Aspects of any of the methods described herein.

[0070] The controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component of the UE 120 may perform one or more techniques associated with MBS session status reporting, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component that can execute or guide e.g. Figure 7 The process of 700 Figure 8 The process of 800 Fig.10 1000 and / or operations of other processes as described herein. Memory 242 and memory 282 may store data and program codes for network node 110 and UE 120, respectively. In some examples, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, one or more instructions, when executed (e.g., directly, or after compilation, conversion, and / or interpretation) by one or more processors of network node 110 and / or UE 120, may cause the one or more processors, UE 120, and / or network node 110 to execute or direct, for example Figure 7 The process of 700 Figure 8 The process of 800 Fig.10 The process 1000 and / or operations of other processes as described herein. In some examples, executing instructions may include running instructions, converting instructions, compiling instructions, and / or interpreting instructions, etc.

[0071] In some aspects, the UE 120 includes means for leaving an MBS session without leaving a PDU session associated with the MBS session; and / or means for sending a signaling message after leaving the MBS session, the signaling message including an IE including an MBS session state indication associated with the MBS session. Means for the UE 120 to perform operations described herein may include, for example, one or more of the communications manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0072] In some aspects, the UE 120 includes means for leaving the MBS session without leaving the PDU session associated with the MBS session; and / or means for sending a signaling message based on leaving the MBS session for receipt by a RAN node (e.g., the network node 110), the signaling message including an indication that the UE 120 has left the MBS session. Means for the UE to perform operations described herein may include, for example, one or more of the following: the communication manager 140, the antenna 252, the modem 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, the TX MIMO processor 266, the controller / processor 280, or the memory 282.

[0073] In some aspects, the RAN node (e.g., network node 110) includes means for receiving a signaling message including an indication that UE 120 has left the MBS session; and / or means for removing UE 120 from the MBS session based at least in part on the indication that UE 120 has left the MBS session. Means for the network node 110 to perform operations described herein may include, for example, one or more of the communication manager 150, the transmit processor 220, the TX MIMO processor 230, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, the controller / processor 240, the memory 242, or the scheduler 246.

[0074] Although Figure 2 The blocks in the 2000 and 2010 are illustrated as distinct components, but the functionality described above for these blocks may be implemented in a single hardware, software, or combined component or in various combinations of components. For example, the functionality described for the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0075] As indicated above, Figure 2 are provided as examples. Other examples can be found in the Figure 2 The examples described are different.

[0076] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a RAN node, a core network node, a network element, a base station or network equipment can be implemented in an aggregated or decomposed architecture. For example, a base station (such as a node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a TRP or a cell, etc.) or one or more units (or one or more components) that perform base station functionality can be implemented as an aggregated base station (also referred to as an independent base station or a monolithic base station) or a decomposed base station. "Network entity" or "network node" may refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or a combination thereof).

[0077] An aggregated base station (e.g., an aggregated network node) may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). A decomposed base station (e.g., a decomposed network node) may be configured to utilize a protocol stack that is physically or logically distributed between two or more units (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, a CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may also be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), and the like.

[0078] Base station type operations or network designs may take into account the aggregated nature of base station functionality. For example, a decomposed base station may be utilized in an IAB network, an open radio access network (O-RAN (such as a network configuration initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)) to facilitate the scaling of a communication system by separating base station functionality into one or more units that can be deployed separately. A decomposed base station may include functionality implemented across two or more units at various physical locations, as well as functionality implemented virtually for at least one unit, which may enable flexibility in network design. Individual units of a decomposed base station may be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0079] Figure 33 is a diagram illustrating an example disaggregated base station architecture 300 according to the present disclosure. The disaggregated base station architecture 300 may include a CU 310 that may communicate directly with a core network 320 via a backhaul link, or indirectly with the core network 320 through one or more disaggregated control units, such as a near-RT RIC 325 via an E2 link, or a non-RTRIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via an F1 interface. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective radio frequency (RF) access links. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0080] Each of the units (including CU 310, DU 330, RU 340) and the near-RT RIC 325, non-RT RIC 315, and SMO framework 305 may include or be coupled to one or more interfaces, the one or more interfaces being configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to one or more communication interfaces of the corresponding unit may be configured to communicate with one or more of the other units via a transmission medium. In some examples, each of the units may include a wired interface and a wireless interface, the wired interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, the wireless interface being configured to receive signals or send signals to one or more of the other units via a wired transmission medium, or both.

[0081] In some aspects, the CU 310 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, or service data adaptation protocol (SDAP) functions, etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by the CU 310. The CU 310 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP) functionality), control plane functionality (e.g., central unit-control plane (CU-CP) functionality), or a combination thereof. In some specific implementations, the CU 310 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, the CU 310 may be implemented to communicate with the DU 330 for network control and signaling.

[0082] Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a MAC layer, and one or more high physical (PHY) layers, at least in part, according to a functional partition such as that defined by 3GPP. In some aspects, one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc. In some aspects, the DU 330 may further host one or more low PHY layers, such as one or more modules for fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming or physical random access channel (PRACH) extraction and filtering, etc. Each layer (also referred to as a module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0083] Each RU 340 may implement lower layer functionality. In some deployments, the RU 340 controlled by the DU 330 may correspond to a logical node that hosts RF processing functions or low PHY layer functions based on functional split (e.g., functional split defined by 3GPP) (such as lower layer functional split), such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, etc. In this architecture, each RU 340 may be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, real-time and non-real-time aspects of control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0084] The SMO framework 305 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 305 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 305 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTRIC 325. In some specific implementations, the SMO framework 305 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of the one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 can also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0085] The non-RT RIC 315 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 may be coupled to or communicate with the near-RT RIC 325 (such as via an A1 interface). The near-RT RIC 325 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and O-eNBs with the near-RT RIC 325.

[0086] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 325 and may be received from a non-network data source or from a network function at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 305 (such as via reconfiguration of the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0087] As indicated above, Figure 3 are provided as examples. Other examples can be found in the Figure 3 The examples described are different.

[0088] Figure 4 4 is a diagram of an example 400 of a core network 405 according to the present disclosure. Figure 4 As shown, example 400 may include UE 120, wireless network 100, and core network 405. The devices and / or networks of example 400 may be interconnected via wired connections, wireless connections, or a combination thereof.

[0089] For example, the wireless network 100 may support a cellular radio access technology (RAT). The wireless network 100 may include one or more network nodes, such as a base station (e.g., a base transceiver station, a radio base station, a Node B, an eNodeB (eNB), a gNodeB (gNB), a base station subsystem, a cell site, a cell tower, an access point, a transmit receive point (TRP), a radio access node, a macrocell base station, a microcell base station, a picocell base station, a femtocell base station, or a similar type of device) and other network nodes that may support wireless communications for the UE 120. The wireless network 100 (also referred to as a radio access network (RAN)) may transmit traffic between the UE 120 (e.g., using a cellular RAT), one or more network nodes (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and / or a core network 405. The wireless network 100 may provide one or more cells covering a geographic area.

[0090] In some aspects, the wireless network 100 may perform scheduling and / or resource management for UEs 120 covered by the wireless network 100 (e.g., UEs 120 covered by a cell provided by the wireless network 100). In some aspects, the wireless network 100 may be managed by a network controller (e.g., Figure 1 The network controller 130) controls or coordinates, and the network controller can perform load balancing and / or network level configuration, etc. Figure 1 As described, the network controller may communicate with the wireless network 100 via wireless or wired backhaul. In some aspects, the wireless network 100 may include a network controller, a self-organizing network (SON) module or component, or a similar module or component. Thus, the wireless network 100 may perform network control, scheduling, and / or network management functions (e.g., uplink, downlink, and / or sidelink communications for UEs 120 covered by the wireless network 100).

[0091] Figure 4 The illustrated core network 405 includes an example functional architecture in which the systems and / or methods described herein may be implemented. For example, the core network 405 may include an example architecture of a 5G next generation (NG) core network included in a fifth generation (5G) wireless telecommunications system. Figure 4 The example architecture of the core network 405 shown may be an example of a service-based architecture, but in some aspects the core network 405 may be implemented as a reference point architecture and / or a 4G core network, among others.

[0092] like Figure 4As shown, the core network 405 may include multiple functional elements. The functional elements may include, for example, a network slice selection function (NSSF) 410, a network open function (NEF) 415, an authentication server function (AUSF) 420, a unified data management (UDM) component 425, a policy control function (PCF) 430, an application function (AF) 435, an access and mobility management function (AMF) 440, one or more session management functions (SMF) 445 and / or a user plane function (UPF) 450, etc. These functional elements may be communicatively connected via a message bus 455. Figure 4 Each of the functional elements shown may be implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more of these functional elements may be implemented on a physical device such as an access point, a base station, and / or a gateway, etc. In some implementations, one or more of these functional elements may be implemented on a computing device in a cloud computing environment.

[0093] NSSF 410 may include one or more devices that select a network slice instance for UE 120. Network slicing is a network architecture model in which logically different network slices operate using a common network infrastructure. For example, several network slices may operate as isolated end-to-end networks that are customized to meet different target service standards for different types of applications executed at least in part by UE 120 and / or communications to and from UE 120. Network slices may efficiently provide communications for different types of services with different service standards.

[0094] NSSF 410 may determine a set of network slicing policies to be applied at wireless network 100. For example, NSSF 410 may apply one or more UE routing policy (URSP) rules. In some aspects, NSSF 410 may select a network slice based on a mapping of a data network name (DNN) field included in a routing description (RSD) to a DNN field included in a service descriptor selected by UE 120. By providing network slicing, NSSF 410 allows operators to potentially deploy multiple substantially independent end-to-end networks over the same infrastructure. In some implementations, each slice may be customized for different services.

[0095] NEF 415 may include one or more devices that support the opening of capabilities and / or events in the wireless telecommunication system to help other entities in the wireless telecommunication system discover network services. AUSF 420 may include one or more devices that act as an authentication server and support the process of authenticating UE 120 in the wireless telecommunication system.

[0096] The UDM 425 may include one or more devices that store user data and profiles in a wireless telecommunications system. In some aspects, the UDM 425 may be used for fixed access and / or mobile access in the core network 405, among other things.

[0097] The PCF 430 may include one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and / or mobility management, among other things. In some aspects, the PCF 430 may include one or more URSP rules used by the NSSF 410 to select a network slice instance for the UE 120.

[0098] The AF 435 may include one or more devices that support application impact on traffic routing, access and / or policy control to the NEF 415, etc. The AMF 440 may include one or more devices that act as a termination point for non-access stratum (NAS) signaling and / or mobility management, etc. In some aspects, the AMF 440 may receive (e.g., from the UE 120 via the wireless network 100) a NAS message including a multicast broadcast service (MBS) session state information element (IE), identify the SMF 445 based at least in part on the MBS context and the MBS session identifier associated with the UE 120, and forward the MBS session state indication to the SMF 445, as described herein.

[0099] In some aspects, the AMF 440 may include a communication manager 442. As described in greater detail elsewhere herein, the communication manager 442 may receive a NAS message including an MBS session status IE, wherein the MBS session status information IE includes an MBS session identifier corresponding to an MBS session of the UE 120 and an MBS session status indication indicating a status of the MBS session; identify an SMF 445 (e.g., an SMF node) based at least in part on an MBS context associated with the UE 120 and the MBS session identifier; and forward the MBS session status indication to the SMF 445. Additionally or alternatively, the communication manager 442 may perform one or more other operations described herein.

[0100] In some aspects, the AMF 440 includes means for receiving a NAS message including an MBS session status IE, wherein the MBS session status information IE includes an MBS session identifier corresponding to an MBS session of the UE 120 and an MBS session status indication indicating a status of the MBS session; means for identifying the SMF 445 based at least in part on an MBS context and the MBS session identifier associated with the UE 120; and / or means for forwarding the MBS session status indication to the SMF 445. In some aspects, means for the AMF 440 to perform operations described herein may include, for example, the communication manager 442 and / or as described with respect to Figure 5 One or more of the described components of device 500 (eg, processor 520, memory 530, input component 540, output component 550, and / or communication component 560).

[0101] SMF 445 may include one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, SMF 445 may configure traffic steering policies at UPF 450 and / or enforce UE IP address allocation and policies, etc. In some aspects, SMF 445 may receive an indication to release an MBS session of UE 120, and may release the MBS session based at least in part on the indication, as described herein.

[0102] In some aspects, the SMF 445 may include a communication manager 446. As described in more detail elsewhere herein, the communication manager 446 may receive an indication to release an MBS session of the UE 120, the indication including at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session; and release the MBS session based at least in part on the indication to release the MBS session. Additionally or alternatively, the communication manager 446 may perform one or more other operations described herein.

[0103] In some aspects, the SMF 445 includes means for receiving an indication to release an MBS session of the UE 120, the indication including at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE 120 has been removed from the MBS session; and / or means for releasing the MBS session based at least in part on the indication to release the MBS session. In some aspects, means for the SMF 445 to perform operations described herein may include, for example, the communication manager 446 and / or as for Figure 5 One or more of the described components of device 500 (eg, processor 520, memory 530, input component 540, output component 550, and / or communication component 560).

[0104] UPF 450 may include one or more devices that act as anchor points for intra-RAT and / or inter-RAT mobility. In some aspects, UPF 450 may apply rules to packets, such as rules related to packet routing, service reporting, and / or handling user plane QoS, etc.

[0105] Message bus 455 can be a logical and / or physical communication structure for communicating between functional elements. Therefore, message bus 455 can allow communication between two or more functional elements, whether logically (e.g., using one or more application programming interfaces (APIs), etc.) and / or physically (e.g., using one or more wired connections and / or wireless connections).

[0106] Figure 4 The number and arrangement of devices, components, and networks shown are provided as examples. Figure 4 The devices, elements and / or networks shown may include additional devices, elements and / or networks, fewer devices, elements and / or networks, different devices, elements and / or networks, or devices, elements and / or networks arranged in a different manner than those shown. Figure 4 Two or more of the devices or elements shown may be implemented in a single device or element, or Figure 4 The single device or element shown may be implemented as multiple distributed devices or elements. Additionally or alternatively, a collection of devices or elements (e.g., one or more devices or elements) of the example 400 may perform one or more functions described as being performed by another collection of devices or elements of the example environment 400.

[0107] Figure 5 4 is a diagram of example components of a device 500 associated with a core network 405 according to the present disclosure. The device 500 may correspond to one or more of the NSSF 410, the NEF 415, the AUSF 420, the UDM 425, the PCF 430, the AF 435, the AMF 440, the SMF 445, and / or the UPF 450. In some implementations, the NSSF 410, the NEF 415, the AUSF 420, the UDM 425, the PCF 430, the AF 435, the AMF 440, the SMF 445, and / or the UPF 450 may include one or more of the devices 500 and / or one or more components of the device 500. Figure 5 As shown, device 500 may include a bus 510 , a processor 520 , a memory 530 , an input component 540 , an output component 550 , and / or a communication component 560 .

[0108] The bus 510 may include one or more components that enable wired and / or wireless communication between components of the device 500. The bus 510 may connect the components of the device 500 to the bus 510, such as via an operational coupling, a communicative coupling, an electronic coupling, and / or an electrical coupling. Figure 5Two or more components of a processor 520 are coupled together. For example, bus 510 may include electrical connections (e.g., wires, traces, and / or leads) and / or wireless buses. Processor 520 may include a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field programmable gate array, an application-specific integrated circuit, and / or another type of processing component. Processor 520 may be implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 520 may include one or more processors that can be programmed to perform one or more operations or processes described elsewhere herein.

[0109] The memory 530 may include volatile memory and / or non-volatile memory. For example, the memory 530 may include random access memory (RAM), read-only memory (ROM), a hard disk drive, and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). The memory 530 may include internal memory (e.g., RAM, ROM, or hard disk drive) and / or removable memory (e.g., removable via a universal serial bus connection). The memory 530 may be a non-transitory computer-readable medium. The memory 530 may store information, one or more instructions, and / or software (e.g., one or more software applications) related to the operation of the device 500. In some specific implementations, the memory 530 may include one or more memories such as coupled (e.g., communicatively coupled) to one or more processors (e.g., processor 520) via bus 510. The communicative coupling between the processor 520 and the memory 530 may enable the processor 520 to read and / or process information stored in the memory 530 and / or store information in the memory 530.

[0110] Input component 540 may enable device 500 to receive input, such as user input and / or sensed input. For example, input component 540 may include a touch screen, keyboard, keypad, mouse, button, microphone, switch, sensor, global positioning system sensor, accelerometer, gyroscope and / or actuator. Output component 550 may enable device 500 to provide output such as via a display, speaker and / or light emitting diode. Communication component 560 may enable device 500 to communicate with other devices via wired connection and / or wireless connection. For example, communication component 560 may include a receiver, a transmitter, a transceiver, a modem, a network interface card and / or an antenna.

[0111] The device 500 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory 530) may store an instruction set (e.g., one or more instructions or codes) for execution by the processor 520. The processor 520 may execute the instruction set to perform one or more operations or processes described herein. In some specific implementations, the execution of the instruction set by one or more processors 520 causes one or more processors 520 and / or the device 500 to perform one or more operations or processes described herein. In some specific implementations, hard-wired circuits may be used instead of instructions or in combination with instructions to perform one or more operations or processes described herein. Additionally or alternatively, the processor 520 may be configured to perform one or more operations or processes described herein. Therefore, the specific implementation described herein is not limited to any particular combination of hardware circuits and software.

[0112] Figure 5 The number and arrangement of components shown are provided as examples. Device 500 may include Figure 5 Those components shown may include additional components, fewer components, different components, or components arranged in a different manner. Additionally or alternatively, a set of components (e.g., one or more components) of device 500 may perform one or more functions described as being performed by another set of components of device 500.

[0113] A wireless communication system may support an MBS service that provides multicast services and broadcast services to UEs. A multicast service is provided to a group of UEs. The group of UEs receiving a particular multicast service at least partially shares the network resources required to provide the service. Broadcast services are provided to all UEs. When there are UEs interested in receiving the multicast service, the service may be activated in the network. When there are no longer any UEs receiving the multicast service, the service may be deactivated in the network. Since multicast services consume network resources, network operators are interested in having accurate and timely information about UEs that are actively receiving the service so that the service may be deactivated if there are no UEs receiving the service.

[0114] For multicast services, there are two types of delivery: individual delivery, in which the MBS service flow is delivered to a single UE; and shared delivery, in which the MBS service is delivered to a group of UEs (e.g., in a set of shared resources). For multicast services of either delivery type, a PDU session is established between the UE receiving the multicast service and the core network. The PDU session identifies the physical resources in the network allocated to the data exchanged via the session. For example, the PDU session identifies the rate of data packets exchanged via the PDU session, the quality of service (QoS) parameters of the PDU session (e.g., maximum delay, maximum jitter, etc.), and one or more Internet Protocol (IP) addresses associated with the source and destination of the data packets exchanged via the PDU session. The UE uses the PDU session establishment process to establish a PDU session with the network. According to the PDU session establishment process, the UE sends a PDU session establishment request message. The network can respond with a PDU session establishment accept message to indicate that the PDU session has been established.

[0115] A session during which a UE receives a multicast service (e.g., via a PDU session) is referred to as an MBS session. There may be multiple MBS sessions associated with a PDU session (e.g., multiple MBS sessions of a UE may use the same PDU session of the UE). The UE may establish an MBS session during the PDU session establishment procedure for an associated PDU session by providing an indication of a request to join an MBS session and an identification of the MBS session that the UE wants to join in a PDU session establishment request message.

[0116] A PDU session may be released by the UE or by the network via a PDU session release procedure. If a PDU session is released, all associated MBS sessions are implicitly released. This implicit release of an MBS session may also be referred to as a "local release".

[0117] If the UE performs a local release of an MBS session, the network is not explicitly notified of the local release. In some scenarios, the network may infer that the MBS session has been released by the UE. For example, when a PDU session is released, the network may infer that the UE has released the associated MBS session locally, and the network may also release the MBS session locally. In an example scenario, the UE has an active MBS session associated with a PDU session. When the UE is in RRC connected mode, the UE actively receives MBS services associated with the MBS session. In one example, the UE itself (e.g., rather than the user) may leave the MBS session locally. This may occur, for example, if the UE transmits a PDU session release request message to release a PDU session associated with the MBS session, and the network rejects the request and sends a PDU session release reject message to the UE. For example, a rejection of a PDU session release may occur when a message from the UE is incorrect (e.g., includes an incorrect PDU session identifier). In this example, the UE releases the PDU session and the associated MBS session locally. As another example, the UE itself may locally leave the MBS session during the inter-system change from N1 mode (5G) to S1 mode (LTE) and the associated transmission of the PDU session. Here, since LTE does not support MBS, the UE may locally release the associated MBS session. The inter-system change may not be successful or may be aborted and the UE may stay in N1 mode. The state of the MBS session from the UE's perspective and the state of the MBS session from the network's perspective may be different in this example.

[0118] The local release of the MBS session by the UE and the network creates the possibility of a loss of synchronization between the UE and the network regarding the state of the MBS session. For example, the UE may have performed a local release of the MBS session, but the network did not infer that the local release of the MBS session occurred in the UE. As a result, the network incorrectly believed that the MBS session was active in the UE. Similarly, the UE may incorrectly believe that the MBS session is active in the network after the network has implicitly released the MBS session.

[0119] In some scenarios, the UE may be operating in Radio Resource Control (RRC) inactive mode. RRC inactive mode is a mode at the RRC layer in which the UE is connected to the network in the sense that there is a UE context in the network but there is no active signaling connection between the UE and the network. In order to send or receive traffic to or from the network, a UE in RRC inactive mode will need to resume a signaling connection with the network. Therefore, a UE in RRC inactive mode cannot actively receive MBS traffic associated with an MBS session. Therefore, a UE in RRC inactive may have one or more active MBS sessions associated with one or more PDU sessions, but the UE is not actively receiving MBS traffic associated with the one or more MBS sessions.

[0120] In an example scenario, the UE has an active MBS session associated with a PDU session. When the UE is in RRC connected mode, the UE actively receives MBS services associated with the MBS session. In one example, the MBS session becomes inactive, and thus the radio resources associated with the MBS session are released and the UE is moved (e.g., by the network) to RRC inactive mode. Here, when operating in RRC inactive mode, the UE leaves the MBS session (e.g., based on user input). In this example, the UE leaves the MBS session locally, which means that the network is unaware that the UE has left the MBS session. In addition, there is no need to release the PDU session associated with the MBS session because the PDU session can also be used for other services (e.g., Internet services). In another example, the MBS session becomes inactive, and the UE is moved (e.g., by the network) to RRC idle mode (e.g., if the RRC inactive mode is not supported by the network, if the PDU session is only used for MBS and the UE has no other active PDU sessions, etc.). Here, when operating in RRC idle mode, the UE can leave the MBS session based on user input. In this example, the UE leaves the MBS session locally, which means that the network does not know that the UE has left the MBS session. In addition, there is no need to release the PDU session associated with the MBS session, because the PDU session can also be used for other services.

[0121] Typically, in order to leave an MBS session, the UE moves to RRC connected mode and initiates a PDU session modification procedure for the associated PDU session. Here, the UE includes a leave request in a PDU session modification request message provided to the network. However, since this typical approach requires the UE to move to connected mode, UE resources (e.g., battery power, processing resources, etc.) may be wasted (e.g., when the UE has no other reason to move to RRC connected mode). In addition, the typical approach increases signaling overhead. In this scenario, because the MBS session is inactive, there is no urgency to release the MBS session from the core network's perspective. Therefore, the release of the MBS session can be delayed until the UE needs to resume the signaling connection for another reason (e.g., mobility registration update, service request for other services or applications, etc.).

[0122] Some techniques and apparatus described herein provide MBS session status reporting. In some aspects, a UE (e.g., UE 120) may leave an MBS session without leaving a PDU session associated with the MBS session, and may send a signaling message after leaving the MBS session, wherein the signaling message includes an IE including an MBS session identifier associated with the MBS session and an MBS session status indication associated with the MBS session. In some aspects, a core network node (e.g., AMF 440) may receive a signaling message (e.g., a NAS message) including an MBS session status IE, identify an SMF node (e.g., SMF 445) based at least in part on an MBS context and an MBS session identifier associated with UE 120, and forward the MBS session status indication to the SMF node. In some aspects, the SMF node may receive an MBS session status indication associated with the MBS session and release the MBS session. In some aspects, the UE does not need to send a signaling message until the UE moves to RRC connected mode for another reason. In this way, UE resources may be saved and signaling overhead may be reduced.

[0123] Additionally or alternatively, in some aspects, a UE (e.g., UE 120) may leave an MBS session without leaving a PDU session associated with the MBS session, and may send a signaling message for reception by a RAN node (e.g., network node 110) based on leaving the MBS session, the signaling message including an indication that the UE has left the MBS session. In some aspects, the RAN node may receive a signaling message including an indication that the UE has left the MBS session, and may remove the UE from the MBS session. In addition, in some aspects, the RAN node may send an indication that the UE has been removed from the MBS session to a core network node (e.g., SMF 445). In some aspects, the core network node may receive an indication that the UE has been removed from the MBS session, and may release the MBS session based at least in part on the indication. Additional details are provided below. In some aspects, the UE may send a signaling message to the RAN node before moving to RRC connected mode. In this way, UE resources may be saved and signaling overhead may be reduced. In addition, from the perspective of the RAN, releasing the MBS session in the RAN may improve radio resource management. Additional details are provided below.

[0124] Fig. 6A and Figure 6B are diagrams illustrating examples 600 and 650 , respectively, associated with MBS session status reporting according to the present disclosure.

[0125] like Fig. 6A As shown, example 600 includes communications between UE 120, AMF 440, and SMF 445. In some aspects, UE 120 may be included in a wireless network, such as wireless network 100 (not shown). UE 120 may communicate with AMF 440 via a wireless access link supported by wireless network 100. AMF 440 may communicate with SMF 445 via a message bus 455 of core network 405.

[0126] As shown by reference numeral 602, UE 120 may leave the MBS session without leaving the PDU session associated with the MBS session. For example, UE 120 may leave the MBS session locally (e.g., based on user input, based on a decision of UE 120 itself, etc.). Here, the UE leaves the MBS session locally. However, wireless network 100 (e.g., devices in the RAN) and core network 405 (e.g., devices in the core network) are unaware that UE 120 has left the MBS session.

[0127] As indicated by reference numeral 604, UE 120 may send a signaling message after leaving the MBS session, and AMF 440 may receive the signaling message after leaving the MBS session. In some aspects, the signaling message includes an IE including an MBS session identifier associated with the MBS session and an MBS session state indication associated with the MBS session.

[0128] In some aspects, the UE 120 is operating in RRC inactive mode when leaving the MBS session. In some such aspects, the signaling message is an initial NAS message, and the UE 120 resumes the signaling connection before sending the signaling message. Alternatively, in some aspects, the UE 120 is operating in RRC idle mode when leaving the MBS session. In some such aspects, the signaling message is an initial NAS message, and the UE 120 establishes a signaling connection before sending the signaling message. In some aspects, the initial NAS message is a registration update request message. In some aspects, the initial NAS message is a service request message.

[0129] In some aspects, UE 120 is operating in RRC connected mode when leaving the MBS session. In some such aspects, the signaling message is an uplink NAS message. The uplink NAS message can be, for example, an initial NAS message or an uplink NAS transport message.

[0130] In some aspects, the IE is an MBS Session Status Update IE. The MBS Session Status Update IE is an IE that includes information indicating the status of one or more MBS sessions of the UE 120. The information indicating the status of a given MBS session may include an MBS session identifier associated with the MBS session and an MBS session status indication associated with the MBS session, wherein the MBS session status indication indicates the status of the MBS session (e.g., active, inactive, etc.). In some aspects, the MBS Session Status Update IE includes information indicating the status of multiple MBS sessions. For example, in some aspects, the MBS Session Status Update IE may include information indicating the status of each MBS session of the UE 120. As a specific example, the MBS Session Status Update IE may include a first set of bits indicating an MBS session identifier associated with a first MBS session, a second set of bits indicating the status of the first MBS session (e.g., active), a third set of bits indicating an MBS session identifier associated with a second MBS session, a fourth set of bits indicating the status of the second MBS session (e.g., inactive), and so on. In some aspects, the MBS session identifier associated with the MBS session may include an MBS session identity or a temporary mobile group identifier (TMGI). In some aspects, the MBS session status indication is a one-bit indication (e.g., a value of 0 indicates inactive and a value of 1 indicates active). In some aspects, the MBS session status indication is a two-bit binary value. In some aspects, the MBS session status indication is a three-bit binary value. In some aspects, the MBS session status update IE may include one or more other information items, such as information indicating a length of the MBS session status update IE or information identifying the MBS session status update IE, etc.

[0131] As indicated by reference numeral 606, the AMF 440 may identify the SMF 445 based at least in part on the MBS context and the MBS session identifier associated with the UE 120. For example, the AMF 440 may receive a signaling message (e.g., a NAS message) including an MBS session status IE indicating the status of an MBS session, wherein the MBS session is identified using the MBS session identifier. Next, the AMF 440 may retrieve the MBS context of the UE 120, and may identify the SMF 445 that manages the MBS session based at least in part on the retrieved MBS context and the MBS session identifier. The AMF 440 may perform these operations (e.g., such that the AMF 440 identifies one or more SMFs 445, each associated with the one or more MBS sessions indicated in the MBS session status update IE) for one or more of the MBS sessions indicated in the MBS session status update IE.

[0132] As indicated by reference numeral 608, AMF 440 may forward the MBS session status indication and the MBS session identifier to SMF 445, and SMF 445 may receive the MBS session status indication and the associated MBS session identifier. In example 600, the MBS status indication indicates that the MBS session is inactive (e.g., due to UE 120 leaving the MBS session), and thus the MBS status indication may serve as an indication to release the MBS session.

[0133] Thus, as indicated by reference numeral 610, the SMF 445 may release the MBS session based at least in part on the indication to release the MBS session. In some aspects, associated with releasing the MBS session, the SMF 445 may remove the MBS session from a PDU session context associated with the MBS session and from a UE context associated with the UE 120. The SMF 445 may perform these operations for one or more of the MBS sessions for which the SMF 445 receives the release indication.

[0134] like Figure 6B As shown, example 650 includes communications between UE 120, network node 110, and core network 405. In some aspects, UE 120 and network node 110 may be included in a wireless network, such as wireless network 100 (not shown). UE 120 and network node 110 may communicate via a wireless access link supported by wireless network 100. Network node 110 may communicate with core network 405 (e.g., with one or more devices in core network 405, such as SMF 445) via one or more wireless or wired connections.

[0135] As indicated by reference numeral 652, UE 120 may leave an MBS session without leaving a PDU session associated with the MBS session. For example, UE 120 may leave the MBS session locally (e.g., based on user input). Here, the UE leaves the MBS session locally. However, wireless network 100 (e.g., devices in the RAN) and core network 405 (e.g., devices in the core network) are unaware that UE 120 has left the MBS session.

[0136] As shown by reference numeral 654, based on leaving the MBS session, the UE 120 may send a signaling message including an indication that the UE has left the MBS session, and the network node 110 may receive a signaling message including an indication that the UE has left the MBS session. In some aspects, the UE 120 may send a signaling message for reception by a core network node such as the network node 110. In some such aspects, the UE 120 is operating in an RRC inactive mode when sending the signaling message. Alternatively, in some such aspects, the UE 120 is operating in an RRC idle mode when sending the signaling message. In some aspects, the signaling message is communicated in a message (e.g., Msg3) associated with a random access channel (RACH) procedure. In some aspects, communicating the signaling message in a RACH message provides efficiency in terms of signaling overhead. In some aspects, a conventional small data transmission (SDT) procedure may be used in association with communicating the signaling message.

[0137] In some aspects, the indication that the UE 120 has left the MBS session includes an MBS session identifier associated with the MBS session. The MBS session identifier may include, for example, an MBS session identity or a TMGI.

[0138] As indicated by reference numeral 656, the network node 110 may remove the UE 120 from the MBS session based at least in part on the indication that the UE 120 has left the MBS session and the MBS session identifier. In some aspects, in association with removing the UE 120 from the MBS session, the network node 110 may remove radio resources associated with the UE 120 from the set of radio resources allocated to the MBS session. In some aspects, removing the radio resources associated with the UE 120 improves radio resource management from the perspective of the wireless network 100 (e.g., a RAN including the network node 110).

[0139] As indicated by reference numeral 658, in some aspects, the network node 110 may send an indication that the UE 120 has been removed from the MBS session, and the SMF 445 may receive (e.g., via the core network 405) an indication that the UE has been removed from the MBS session. Here, the indication that the UE 120 has been removed from the MBS session may serve as an indication to release the MBS session. Thus, as indicated by reference numeral 660, the SMF 445 may release the MBS session based at least in part on the indication to release the MBS session. In some aspects, in association with releasing the MBS session, the SMF 445 may remove the MBS session from the PDU session context associated with the MBS session and from the UE context associated with the UE 120.

[0140] It is worth noting that Fig. 6AThe technology associated with example 600 in FIG. 600 may be based on a NAS protocol between UE 120 and core network 405, and Figure 6B The techniques associated with example 650 in the example 600 may be based on signaling between the UE 120 and the wireless network 100 (e.g., RAN). Therefore, while the techniques associated with example 600 and the techniques associated with example 650 may be used as alternatives, these techniques may also be used to complement each other. For example, the UE 120 may use the techniques associated with example 650 to notify the network node 110 (e.g., RAN) about leaving the MBS session (e.g., immediately upon leaving the MBS session), and may use the techniques associated with example 600 to synchronize with the core network 405 about the MBS session at a later time (e.g., after the UE 120 resumes the signaling connection).

[0141] As indicated above, Fig. 6A and Figure 6B are provided as examples. Other examples can be found in Fig. 6A and Figure 6B The examples described are different.

[0142] Figure 7 is a diagram illustrating an example process 700 performed, for example, by a UE in accordance with the present disclosure. Example process 700 is an example in which a UE (eg, UE 120) performs operations associated with MBS session status reporting.

[0143] like Figure 7 As shown, in some aspects, process 700 may include leaving an MBS session without leaving a PDU session associated with the MBS session (block 710). For example, a UE (e.g., using communication manager 140 and / or MBS component 1208, such as Fig.12 ) can leave the MBS session without leaving the PDU session associated with the MBS session, as described above.

[0144] like Figure 7 As further shown, in some aspects, process 700 may include sending a signaling message after leaving the MBS session, the signaling message including an IE including an MBS session state indication associated with the MBS session (block 720). Fig.12 The depicted communication manager 140 and / or transmitting component 1204) may transmit a signaling message after leaving the MBS session, the signaling message including an IE including an MBS session state indication associated with the MBS session, as described above.

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

[0146] In a first aspect, the IE is an MBS Session State Update IE.

[0147] In a second aspect, alone or in combination with the first aspect, the UE is operating in a radio resource control inactive mode when leaving the MBS session, and the signaling message is an initial non-access stratum message, and the process 700 includes resuming the signaling connection before sending the signaling message.

[0148] In a third aspect, alone or in combination with one or more of the first and second aspects, the UE is operating in idle mode when leaving the MBS session and the signaling message is an initial non-access stratum message, and the process 700 includes establishing a signaling connection before sending the signaling message.

[0149] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the signaling message is an initial NAS message, and the initial NAS message is a registration update request message or a service request message.

[0150] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the UE is operating in connected mode and the signaling message is an uplink NAS message.

[0151] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the uplink NAS message is an initial NAS message or an uplink NAS transport message.

[0152] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, the IE includes an MBS session identifier associated with the MBS session of the UE.

[0153] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

[0154] In a ninth aspect, alone or in combination with one or more of the first to eighth aspects, the MBS session status indication is a one-bit indication, a two-bit binary value, or a three-bit binary value.

[0155] In a tenth aspect, alone or in combination with one or more of the first to ninth aspects, the IE includes multiple MBS session identifiers associated with multiple MBS sessions of the UE, and information indicating a state of each of the multiple MBS sessions of the UE.

[0156] although Figure 7 Example blocks of process 700 are shown, but in some aspects, process 700 may include Figure 7The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

[0157] Figure 8 is a diagram illustrating an example process 800 performed, for example, by a UE in accordance with the present disclosure. Example process 800 is an example of operations in which a UE (eg, UE 120) performs operations associated with MBS session status reporting.

[0158] like Figure 8 As shown, in some aspects, process 800 may include leaving an MBS session without leaving a PDU session associated with the MBS session (block 810). For example, a UE (e.g., using communication manager 140 and / or MBS component 1208, such as Fig.12 ) can leave the MBS session without leaving the PDU session associated with the MBS session, as described above.

[0159] like Figure 8 As further shown, in some aspects, process 800 may include sending a signaling message for receipt by a RAN node based on leaving the MBS session, the signaling message including an indication that the UE has left the MBS session (block 820). Fig.12 The depicted communications manager 140 and / or transmitting component 1204) may transmit a signaling message for receipt by a RAN node (eg, network node 110) based on leaving the MBS session, the signaling message including an indication that the UE has left the MBS session, as described above.

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

[0161] In a first aspect, the UE is operating in a radio resource control inactive mode when the signaling message is sent.

[0162] In a second aspect, alone or in combination with the first aspect, when sending the signaling message, the UE is operating in an idle mode.

[0163] In a third aspect, alone or in combination with one or more of the first and second aspects, the indication that the UE has left the MBS session comprises an MBS session identifier associated with the MBS session.

[0164] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

[0165] although Figure 8 An example block diagram of process 800 is shown, but in some aspects, process 800 may include Figure 8 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

[0166] Fig. 9 9 is a diagram illustrating an example process 900 performed, for example, by a core network node in accordance with the present disclosure. The example process 900 is an example in which a core network node (eg, AMF 440) performs operations associated with MBS session status reporting.

[0167] like Fig. 9 As shown, in some aspects, process 900 may include receiving a NAS message including an MBS session status IE, wherein the MBS session status information IE includes an MBS session identifier corresponding to an MBS session of the UE and an MBS session status indication indicating a status of the MBS session (block 910). For example, a core network node (e.g., using Fig.14 The depicted communications manager 442 and / or receiving component 1402) may receive a NAS message including an MBS session status IE, wherein the MBS session status information IE includes an MBS session identifier corresponding to an MBS session of a UE (eg, UE 120) and an MBS session status indication indicating a status of the MBS session, as described above.

[0168] like Fig. 9 As further shown, in some aspects, process 900 may include identifying an SMF node based at least in part on an MBS context and an MBS session identifier associated with the UE (block 920). Fig.14 The depicted communications manager 442 and / or MBS component 1408) may identify an SMF node (e.g., SMF 445) based at least in part on an MBS context and an MBS session identifier associated with the UE, as described above.

[0169] like Fig. 9 As further shown, in some aspects, process 900 may include forwarding the MBS session status indication to the SMF node (block 930). For example, a core network node (e.g., using Fig.14 The depicted communications manager 442 and / or sending component 1404) may forward the MBS session state indication to the SMF node, as described above.

[0170] Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0171] In a first aspect, the NAS message is an initial NAS message, which is a registration update request message or a service request message.

[0172] In a second aspect, alone or in combination with the first aspect, the NAS message is an uplink NAS transport message.

[0173] In a third aspect, alone or in combination with one or more of the first and second aspects, the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

[0174] In a fourth aspect, alone or in combination with one or more of the first to third aspects, the MBS session status update IE includes multiple MBS session identifiers associated with multiple MBS sessions of the UE, and information indicating the status of each of the multiple MBS sessions of the UE.

[0175] although Fig. 9 Example blocks of process 900 are shown, but in some aspects, process 900 may include Fig. 9 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

[0176] Fig.10 is a diagram illustrating an example process 1000 performed, for example, by a RAN node in accordance with the present disclosure. The example process 1000 is an example in which a RAN node (eg, network node 110) performs operations associated with MBS session status reporting.

[0177] like Fig.10 As shown, in some aspects, process 1000 may include receiving a signaling message including an indication that the UE has left an MBS session (block 1010). For example, a RAN node (e.g., using Fig.13 The depicted communications manager 150 and / or receiving component 1302) can receive a signaling message including an indication that a UE (eg, UE 120) has left an MBS session, as described above.

[0178] like Fig.10 As further shown, in some aspects, process 1000 may include removing the UE from the MBS session based at least in part on an indication that the UE has left the MBS session (block 1020). For example, a RAN node (e.g., using Fig.13The depicted communications manager 150 and / or MBS component 1308) may remove the UE from the MBS session based at least in part on an indication that the UE has left the MBS session, as described above.

[0179] Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0180] In a first aspect, removing the UE from the MBS session includes removing radio resources associated with the UE from a set of radio resources allocated to the MBS session.

[0181] In a second aspect, alone or in combination with the first aspect, process 1000 includes sending an indication to a core network node that the UE has been removed from the MBS session.

[0182] In a third aspect, alone or in combination with one or more of the first and second aspects, the indication that the UE has left the MBS session comprises an MBS session identifier associated with the MBS session.

[0183] although Fig.10 Example blocks of process 1000 are shown, but in some aspects, process 1000 may include Fig.10 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

[0184] Fig.11 is a diagram illustrating an example process 1100, performed, for example, by a core network node, in accordance with the present disclosure. The example process 1100 is an example in which a core network node (eg, SMF 445) performs operations associated with MBS session status reporting.

[0185] like Fig.11 As shown, in some aspects, process 1100 may include receiving an indication to release an MBS session of the UE, the indication including at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session (block 1110). For example, a core network node (e.g., using Fig.15 The depicted communications manager 446 and / or receiving component 1502) may receive an indication to release an MBS session of a UE (e.g., UE 120), the indication comprising at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session, as described above.

[0186] like Fig.11 As further shown, in some aspects, process 1100 may include releasing the MBS session based at least in part on the indication to release the MBS session (block 1120). For example, a core network node (e.g., using Fig.15 The depicted communications manager 446 and / or MBS component 1508) may release the MBS session based at least in part on the indication to release the MBS session, as described above.

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

[0188] In a first aspect, releasing the MBS session includes removing the MBS session from a PDU session context associated with the MBS session and a UE context associated with the UE.

[0189] although Fig.11 Example blocks of process 1100 are shown, but in some aspects, process 1100 may include Fig.11 The blocks depicted may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner than those depicted. Additionally or alternatively, two or more of the blocks of process 1100 may be performed in parallel.

[0190] Fig.12 1 is a diagram of an example apparatus 1200 for wireless communication according to the present disclosure. Apparatus 1200 may be a UE, or a UE may include apparatus 1200. In some aspects, apparatus 1200 includes a receiving component 1202 and a transmitting component 1204, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a base station, or another wireless communication device) using receiving component 1202 and transmitting component 1204. As further shown, apparatus 1200 may include a communication manager 140. Communication manager 140 may include an MBS component 1208, among other things.

[0191] In some aspects, the apparatus 1200 may be configured to perform Fig. 6A and Figure 6B Additionally or alternatively, the apparatus 1200 may be configured to perform one or more of the processes described herein, such as Figure 7 The process of 700 Figure 8 In some aspects, Fig.12 The device 1200 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.12 One or more of the components shown may be combined with Figure 2 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0192] The receiving component 1202 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1206. The receiving component 1202 may provide the received communications to one or more other components of the device 1200. In some aspects, the receiving component 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1200. In some aspects, the receiving component 1202 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof of the described UE.

[0193] The transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1206. In some aspects, one or more other components of the device 1200 may generate communications and may provide the generated communications to the transmitting component 1204 for transmission to the device 1206. In some aspects, the transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1206. In some aspects, the transmitting component 1204 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described UE. In some aspects, the transmit component 1204 can be co-located with the receive component 1202 in a transceiver.

[0194] The MBS component 1208 may leave the MBS session without leaving the PDU session associated with the MBS session. In some aspects, the sending component 1204 may send a signaling message after leaving the MBS session, the signaling message including an IE including an MBS session state indication associated with the MBS session. In some aspects, the sending component 1204 may send a signaling message for receipt by the RAN node based on leaving the MBS session, the signaling message including an indication that the UE has left the MBS session.

[0195] Fig.12 The number and arrangement of components shown are provided as examples. Fig.12 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.12 Two or more components shown may be implemented in a single component, or Fig.12 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.12 The illustrated set of component(s) may be described as being executable by Fig.12 Another collection of components shown performs one or more functions.

[0196] Fig.13 1 is a diagram of an example apparatus 1300 according to the present disclosure. Apparatus 1300 may be a network node, or a network node may include apparatus 1300. In some aspects, apparatus 1300 includes a receiving component 1302 and a sending component 1304, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1300 may use receiving component 1302 and sending component 1304 to communicate with another apparatus 1306 (such as a UE, a base station, a core network node, or another device). As further shown, apparatus 1300 may include a communication manager 150. Communication manager 150 may include an MBS component 1308, among other things.

[0197] In some aspects, the apparatus 1300 may be configured to perform Fig. 6A and Figure 6B Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as Fig.10 The process 1000. In some aspects, Fig.13 The device 1300 and / or one or more components shown may include a combination of Figure 2 Additionally or alternatively, Fig.13 One or more of the components shown may be combined with Figure 2Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0198] The receiving component 1302 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1306. The receiving component 1302 may provide the received communications to one or more other components of the device 1300. In some aspects, the receiving component 1302 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1300. In some aspects, the receiving component 1302 may include combining Figure 2 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described network nodes.

[0199] Transmit component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and may provide the generated communications to transmit component 1304 for transmission to device 1306. In some aspects, transmit component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmit component 1304 may include combining Figure 2 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described network nodes. In some aspects, the transmit component 1304 can be co-located with the receive component 1302 in a transceiver.

[0200] Receiving component 1302 can receive a signaling message including an indication that the UE has left the MBS session.MBS component 1308 can remove the UE from the MBS session based at least in part on the indication that the UE has left the MBS session.

[0201] Transmitting component 1304 can transmit an indication to a core network node that the UE has been removed from the MBS session.

[0202] Fig.13 The number and arrangement of components shown are provided as examples. Fig.13 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.13 Two or more components shown may be implemented in a single component, or Fig.13 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.13 The illustrated set of component(s) may be described as being executable by Fig.13 Another collection of components shown performs one or more functions.

[0203] Fig.14 1 is a diagram of an example apparatus 1400 for wireless communication according to the present disclosure. Apparatus 1400 may be a core network node (e.g., an AMF), or a core network node may include apparatus 1400. In some aspects, apparatus 1400 includes a receiving component 1402 and a sending component 1404, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a base station, or another wireless communication device) using receiving component 1402 and sending component 1404. As further shown, apparatus 1400 may include a communication manager 442. Communication manager 442 may include an MBS component 1408, among other things.

[0204] In some aspects, the apparatus 1400 may be configured to perform Fig. 6A and Figure 6B Additionally or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as Fig. 9 The process 900. In some aspects, Fig.14 The device 1400 and / or one or more components shown may include a combination of Figure 5 Additionally or alternatively, Fig.14 One or more of the components shown may be combined with Figure 5 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0205] The receiving component 1402 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1406. The receiving component 1402 may provide the received communications to one or more other components of the device 1400. In some aspects, the receiving component 1402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1400. In some aspects, the receiving component 1402 may include combining Figure 5 One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described core network nodes.

[0206] The transmitting component 1404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to the device 1406. In some aspects, one or more other components of the device 1400 may generate communications and may provide the generated communications to the transmitting component 1404 for transmission to the device 1406. In some aspects, the transmitting component 1404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to the device 1406. In some aspects, the transmitting component 1404 may include combining Figure 5 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described core network nodes. In some aspects, the transmit component 1404 can be co-located with the receive component 1402 in a transceiver.

[0207] The receiving component 1402 may receive a NAS message including an MBS session status IE, wherein the MBS session status information IE includes an MBS session identifier corresponding to an MBS session of the UE and an MBS session status indication indicating a status of the MBS session. The MBS component 1408 may identify an SMF node based at least in part on an MBS context associated with the UE and the MBS session identifier. The sending component 1404 may forward the MBS session status indication to the SMF node.

[0208] Fig.14 The number and arrangement of components shown are provided as examples. Fig.14 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.14 Two or more components shown may be implemented in a single component, or Fig.14 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.14 The illustrated set of component(s) may be described as being executable by Fig.14 Another collection of components shown performs one or more functions.

[0209] Fig.15 1 is a diagram of an example apparatus 1500 according to the present disclosure. Apparatus 1500 may be a core network node (e.g., an SMF), or a core network node may include apparatus 1500. In some aspects, apparatus 1500 includes a receiving component 1502 and a sending component 1504, which may communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, apparatus 1500 may communicate with another apparatus 1506 (such as a UE, a base station, or another wireless communication device) using receiving component 1502 and sending component 1504. As further shown, apparatus 1500 may include a communication manager 446. Communication manager 446 may include an MBS component 1508, among other things.

[0210] In some aspects, the apparatus 1500 may be configured to perform Fig. 6A and Figure 6B Additionally or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as Fig.11 The process 1100. In some aspects, Fig.15 The device 1500 and / or one or more components shown may include a combination of Figure 5 Additionally or alternatively, Fig.15 One or more of the components shown may be combined with Figure 5 Additionally or alternatively, one or more components in the component set may be implemented at least in part as software stored in a memory. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and can be executed by a controller or processor to perform the function or operation of the component.

[0211] The receiving component 1502 may receive communications, such as reference signals, control information, data communications, or combinations thereof, from the device 1506. The receiving component 1502 may provide the received communications to one or more other components of the device 1500. In some aspects, the receiving component 1502 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications and may provide the processed signals to the one or more other components of the device 1500. In some aspects, the receiving component 1502 may include combining Figure 5One or more antennas, modems, demodulators, MIMO detectors, receive processors, controllers / processors, memories, or combinations thereof, of the described core network nodes.

[0212] Transmit component 1504 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1506. In some aspects, one or more other components of device 1500 may generate communications and may provide the generated communications to transmit component 1504 for transmission to device 1506. In some aspects, transmit component 1504 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1506. In some aspects, transmit component 1504 may include combining Figure 5 One or more antennas, modems, modulators, transmit MIMO processors, transmit processors, controllers / processors, memories, or combinations thereof of the described core network nodes. In some aspects, the transmit component 1504 can be co-located with the receive component 1502 in a transceiver.

[0213] The receiving component 1502 may receive an indication to release the MBS session of the UE, the indication comprising at least one of an MBS session state indication associated with the MBS session, an MBS session state indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session. The MBS component 1508 may release the MBS session based at least in part on the indication to release the MBS session.

[0214] Fig.15 The number and arrangement of components shown are provided as examples. Fig.15 Additional components, fewer components, different components, or components arranged in a different manner than those shown. Fig.15 Two or more components shown may be implemented in a single component, or Fig.15 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Fig.15 The illustrated set of component(s) may be described as being executable by Fig.15 Another collection of components shown performs one or more functions.

[0215] The following provides an overview of some aspects of the disclosure:

[0216] Aspect 1: A method of wireless communication performed by an apparatus of a UE, the method comprising: leaving an MBS session without leaving a PDU session associated with the MBS session; and sending a signaling message after leaving the MBS session, the signaling message comprising an IE, the IE comprising an MBS session status indication associated with the MBS session.

[0217] Aspect 2: The method according to aspect 1, wherein the IE is an MBS session status update IE.

[0218] Aspect 3: A method according to any one of aspects 1 to 2, wherein the UE is operating in a radio resource control inactive mode when leaving the MBS session and the signaling message is an initial non-access stratum message, and the method further includes restoring a signaling connection before sending the signaling message.

[0219] Aspect 4: The method according to any one of aspects 1 to 2, wherein the UE is operating in idle mode when leaving the MBS session and the signaling message is an initial non-access stratum message, and the method further includes establishing a signaling connection before sending the signaling message.

[0220] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the signaling message is an initial NAS message, and the initial NAS message is a registration update request message or a service request message.

[0221] Aspect 6: The method according to any one of aspects 1 to 2, wherein the UE is operating in connected mode and the signaling message is an uplink NAS message.

[0222] Aspect 7: The method according to aspect 6, wherein the uplink NAS message is an initial NAS message or an uplink NAS transport message.

[0223] Aspect 8: The method according to any one of aspects 1 to 7, wherein the IE includes an MBS session identifier associated with the MBS session of the UE.

[0224] Aspect 9: The method according to aspect 8, wherein the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

[0225] Aspect 10: The method according to any one of aspects 1 to 9, wherein the MBS session status indication is a one-bit indication, a two-bit binary value, or a three-bit binary value.

[0226] Aspect 11: The method according to any one of aspects 1 to 10, wherein the IE includes multiple MBS session identifiers associated with multiple MBS sessions of the UE, and information indicating the state of each of the multiple MBS sessions of the UE.

[0227] Aspect 12: A method of wireless communication performed by an apparatus of a UE, the method comprising: leaving an MBS session without leaving a PDU session associated with the MBS session; and sending a signaling message for receipt by a RAN node based on leaving the MBS session, the signaling message comprising an indication that the UE has left the MBS session.

[0228] Aspect 13: The method according to aspect 11, wherein when sending the signaling message, the UE is operating in a radio resource control inactive mode.

[0229] Aspect 14: The method according to any one of aspects 11 to 12, wherein when sending the signaling message, the UE is operating in idle mode.

[0230] Aspect 15: The method according to any one of aspects 11 to 13, wherein the indication that the UE has left the MBS session comprises an MBS session identifier associated with the MBS session.

[0231] Aspect 16: The method according to aspect 14, wherein the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

[0232] Aspect 17: A method performed by a device of a core network node, the method comprising: receiving a NAS message including an MBS session status IE, wherein the MBS session status information IE includes an MBS session identifier corresponding to an MBS session of a UE and an MBS session status indication indicating the status of the MBS session; identifying a session management function (SMF) node based at least in part on an MBS context associated with the UE and the MBS session identifier; and forwarding the MBS session status indication to the SMF node.

[0233] Aspect 18: The method according to aspect 16, wherein the NAS message is an initial NAS message, and the initial NAS message is a registration update request message or a service request message.

[0234] Aspect 19: A method according to any one of aspects 16 to 17, wherein the NAS message is an uplink NAS transport message.

[0235] Aspect 20: The method according to any one of aspects 16 to 18, wherein the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

[0236] Aspect 21: The method according to any one of Aspects 17 to 20, wherein the MBS session status update IE includes multiple MBS session identifiers associated with multiple MBS sessions of the UE, and information indicating the status of each of the multiple MBS sessions of the UE.

[0237] Aspect 22: A method performed by an apparatus of a RAN node, the method comprising: receiving a signaling message including an indication that a UE has left an MBS session; and removing the UE from the MBS session based at least in part on the indication that the UE has left the MBS session.

[0238] Aspect 23: The method according to aspect 20, wherein removing the UE from the MBS session comprises removing radio resources associated with the UE from a set of radio resources allocated to the MBS session.

[0239] Aspect 24: The method according to any one of aspects 20 to 21, further comprising: sending an indication to a core network node that the UE has been removed from the MBS session.

[0240] Aspect 25: The method according to any one of aspects 20 to 22, wherein the indication that the UE has left the MBS session comprises an MBS session identifier associated with the MBS session.

[0241] Aspect 26: A method performed by a device of a core network node, the method comprising: receiving an indication to release an MBS session of a UE, the indication comprising at least one of the following items: an MBS session status indication associated with the MBS session, an MBS session status indication indicating that the MBS session is inactive, or an indication that the UE has been removed from the MBS session; and releasing the MBS session based at least in part on the indication to release the MBS session.

[0242] Aspect 27: The method according to aspect 24, wherein releasing the MBS session comprises removing the MBS session from a PDU session context associated with the MBS session and a UE context associated with the UE.

[0243] Aspect 28: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 1 to 11.

[0244] Aspect 29: A device for wireless communication, the device comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to execute the method according to one or more of aspects 1 to 11.

[0245] Aspect 30: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 1 to 11.

[0246] Aspect 31: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 1 to 11.

[0247] Aspect 32: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform one or more of the methods described in aspects 1 to 11.

[0248] Aspect 33: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 12 to 16.

[0249] Aspect 34: A device for wireless communication, the device comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 12 to 16.

[0250] Aspect 35: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 12 to 16.

[0251] Aspect 36: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 12 to 16.

[0252] Aspect 37: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 12 to 16.

[0253] Aspect 38: An apparatus at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 17 to 21.

[0254] Aspect 39: A device comprising: a memory and one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 17 to 21.

[0255] Aspect 40: An apparatus comprising at least one component configured to perform the method according to one or more of aspects 17 to 21.

[0256] Aspect 41: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 17 to 21.

[0257] Aspect 42: A non-transitory computer-readable medium storing an instruction set, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform the method according to one or more of aspects 17 to 21.

[0258] Aspect 43: An apparatus for performing wireless communications at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 22 to 25.

[0259] Aspect 44: A device for wireless communication, the device comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 22 to 25.

[0260] Aspect 45: An apparatus for wireless communication, the apparatus comprising at least one component configured to perform the method according to one or more of aspects 22 to 25.

[0261] Aspect 46: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 22 to 25.

[0262] Aspect 47: A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform one or more of the methods described in aspects 22 to 25.

[0263] Aspect 48: An apparatus at a device, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform one or more of the methods described in Aspects 26 to 27.

[0264] Aspect 49: A device, comprising: a memory and one or more processors, the one or more processors coupled to the memory, the one or more processors configured to perform the method according to one or more of aspects 26 to 27.

[0265] Aspect 50: An apparatus comprising at least one component configured to perform the method according to one or more of aspects 26 to 27.

[0266] Aspect 51: A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to perform the method according to one or more of aspects 26 to 27.

[0267] Aspect 52: A non-transitory computer-readable medium storing an instruction set, the instruction set comprising one or more instructions, which, when executed by one or more processors of a device, causes the device to perform the method according to one or more of aspects 26 to 27.

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

[0269] Further disclosure is included in the appendix. This appendix is ​​provided as an example only and is considered a part of this specification. The definitions, illustrations, or other descriptions in the appendix do not replace or cover similar information included in the specific embodiments or figures. In addition, the definitions, illustrations, or other descriptions in the specific embodiments or figures do not replace or cover similar information included in the appendix. In addition, this appendix is ​​not intended to limit the disclosure of possible aspects.

[0270] As used herein, the term "component" is intended to be broadly interpreted as a combination of hardware and / or hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language or other names, "software" should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures and / or functions, etc. As used herein, a "processor" is implemented in a combination of hardware and / or hardware and software. It will be apparent that the systems and / or methods described herein can be implemented by a combination of hardware and / or hardware and software in different forms. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit various aspects. Therefore, there is no reference to a specific software code herein to describe the operation and behavior of the system and / or method, because those skilled in the art will understand that software and hardware can be designed to implement the system and / or method based at least in part on the description herein.

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

[0272] Although the specific combination of features is set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features can be combined in a manner that is not specifically described in the claims and / or is not disclosed in the specification. The disclosure of various aspects includes each dependent claim combined with each other claim in the claim set. As used herein, the phrase "at least one of" the list of items refers to any combination of these items (it includes a single member). As an example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination with multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).

[0273] Any element, action or instruction used herein should not be interpreted as key or necessary, unless explicitly described as such. In addition, as used herein, the article "one" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more items connected to the article "said", and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more items, and can be used interchangeably with "one or more". If only want to refer to a project, the phrase "only one" or similar terms will be used. In addition, as used herein, the terms "have", "have", "have" etc. are intended to be open terms, which do not limit the elements they modify (for example, "an element with" A can also have B). In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. Furthermore, as used herein, the term "or" when used in a series is intended to be open-ended and used interchangeably with "and / or" unless explicitly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: leaving a multicast broadcast service (MBS) session without leaving a packet data unit (PDU) session associated with the MBS session; and A signaling message is sent after leaving the MBS session, the signaling message comprising an information element (IE) including an MBS session state indication associated with the MBS session. 2 . The UE according to claim 1 , wherein the IE is an MBS session status update IE.

3. The UE of claim 1 , wherein the UE is operating in a radio resource control inactive mode when leaving the MBS session and the signaling message is an initial non-access stratum message, and the one or more processors are further configured to resume a signaling connection before sending the signaling message.

4. The UE of claim 1 , wherein the UE is operating in an idle mode when leaving the MBS session and the signaling message is an initial non-access stratum message, and the one or more processors are further configured to establish a signaling connection before sending the signaling message. 5 . The UE according to claim 1 , wherein the signaling message is an initial non-access stratum (NAS) message, and the initial NAS message is a registration update request message or a service request message.

6. The UE of claim 1, wherein the UE is operating in a connected mode and the signaling message is an uplink non-access stratum (NAS) message. 7 . The UE according to claim 6 , wherein the uplink NAS message is an initial NAS message or an uplink NAS transport message.

8. The UE of claim 1, wherein the IE comprises an MBS session identifier associated with the MBS session of the UE. 9 . The UE according to claim 8 , wherein the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

10. The UE of claim 1, wherein the MBS session status indication is one of a one-bit indication, a two-bit binary value, or a three-bit binary value.

11. The UE of claim 1, wherein the IE comprises a plurality of MBS session identifiers associated with a plurality of MBS sessions of the UE, and information indicating a state of each of the plurality of MBS sessions of the UE.

12. A user equipment (UE) for wireless communication, the user equipment (UE) comprising: Memory; and one or more processors coupled to the memory and configured to: leaving a multicast broadcast service (MBS) session without leaving a packet data unit (PDU) session associated with the MBS session; and A signaling message is sent for receipt by a radio access network (RAN) node based on leaving the MBS session, the signaling message including an indication that the UE has left the MBS session.

13. The UE of claim 12, wherein when sending the signaling message, the UE is operating in a radio resource control inactive mode.

14. The UE of claim 12, wherein the UE is operating in an idle mode when the signaling message is sent.

15. The UE of claim 122, wherein the indication that the UE has left the MBS session comprises an MBS session identifier associated with the MBS session.

16. The UE of claim 155, wherein the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

17. A core network node, the core network node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a non-access stratum (NAS) message including a multicast broadcast service (MBS) session state information element (IE), wherein the MBS session status information IE comprises an MBS session identifier corresponding to an MBS session of a user equipment (UE) and an MBS session status indication indicating a status of the MBS session; identifying a session management function (SMF) node based at least in part on an MBS context associated with the UE and the MBS session identifier; as well as The MBS session status indication is forwarded to the SMF node.

18. The core network node according to claim 177, wherein the NAS message is an initial NAS message, and the initial NAS message is a registration update request message or a service request message.

19. The core network node of claim 177, wherein the NAS message is an uplink NAS transport message.

20. The core network node of claim 17, wherein the MBS session identifier comprises at least one of an MBS session identity or a temporary mobile group identifier.

21. The core network node of claim 17, wherein the MB session status IE comprises a plurality of MBS session identifiers associated with a plurality of MBS sessions of the UE, and information indicating a status of each of the plurality of MBS sessions of the UE.

22. A radio access network (RAN) node for wireless communications, the radio access network (RAN) node comprising: Memory; and one or more processors coupled to the memory and configured to: receiving a signaling message including an indication that the UE has left a multicast broadcast service (MBS) session; as well as The UE is removed from the MBS session based at least in part on the indication that the UE has left the MBS session.

23. The RAN node of claim 22, wherein to remove the UE from the MBS session, the one or more processors are configured to remove radio resources associated with the UE from a set of radio resources allocated to the MBS session.

24. The RAN node of claim 22, wherein the one or more processors are further configured to send an indication to a core network node that the UE has been removed from the MBS session.

25. The RAN node of claim 22, wherein the indication that the UE has left the MBS session comprises an MBS session identifier associated with the MBS session.

26. A method, apparatus, device, computer program product, non-transitory computer-readable medium, user equipment, base station, node, wireless communication device and / or processing system as generally described herein with reference to the accompanying drawings, description and appendix and as illustrated by the accompanying drawings, description and appendix.

Images