CN118104392A

CN118104392A - Downlink multicast service transmission

Info

Publication number: CN118104392A
Application number: CN202280068771.7A
Authority: CN
Inventors: H·T·贝利恩; P·戈丁; M·A·纳萨尔
Original assignee: Nokia Technologies Oy
Current assignee: Nokia Technologies Oy
Priority date: 2021-08-12
Filing date: 2022-08-10
Publication date: 2024-05-28
Also published as: WO2023017082A1; EP4135473A1

Abstract

There is provided an apparatus comprising: means for receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively; means for waking up at one or more wake-up times; and means for starting to receive multicast data at one or more wakeup times, and/or means for receiving a paging request for multicast data at one or more wakeup times.

Description

Downlink multicast service transmission

Technical Field

The present disclosure relates to downlink transmission of multicast service data and discontinuous reception of multicast service data.

Background

The network may provide the same service and selected content data to a plurality of user equipments UE simultaneously. In a broadcast service, the same service and selected content data are provided to all UEs within a geographic coverage area that are authorized to receive the service and content. In a multicast service, the same service and selected content data are provided to a dedicated set of UEs.

Disclosure of Invention

According to some aspects, efficient utilization of power save modes in enabling reception of downlink multicast broadcast service, MBS, data is provided. In at least some embodiments, the MBS data and/or MBS session content is multicast data. In at least some embodiments, the MBS session is a multicast service session.

According to a first aspect, there is provided an apparatus configured (e.g. by comprising respective components, processor-memory configuration, circuitry, etc.) to perform at least: receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively; wake up at one or more wake up times; and beginning to receive multicast data and/or receiving a paging request for the multicast data at one or more wake-up times.

According to a second aspect, there is provided an apparatus comprising application functionality, the apparatus being configured (e.g. by comprising respective components, processor-memory configuration, circuitry, etc.) to perform at least: configuring a multicast service session, the session configuration including a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively; transmitting the session configuration to a network entity and/or transmitting the session configuration as a service announcement of the multicast service session to a user equipment; and transmitting data of the multicast service session at the wake-up time.

According to a third aspect, there is provided an apparatus comprising multicast broadcast session management functionality, the apparatus being configured (e.g. by comprising respective components, processor-memory configuration, circuitry, etc.) to perform at least: receiving a session configuration of the multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively; storing a multicast service session configuration including a multicast service session identifier and one or more wake-up times; and activating one or more multicast service sessions configured to transmit downlink data based on the multicast service session identifier and the one or more wake-up times.

According to a fourth aspect, there is provided an apparatus comprising session management functionality, the apparatus being configured (e.g. by comprising respective components, processor-memory configuration, circuitry, etc.) to perform at least: retrieving multicast service session configuration information for one or more multicast service sessions upon receiving a join request from a user device; receiving a multicast service session identifier as part of a multicast service session configuration, and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively; and transmitting the multicast service session identifier and the one or more wake-up times to the user equipment as a reply to the join request.

According to a fifth aspect, there is provided an apparatus comprising access and mobility functions, the apparatus being configured (e.g. by comprising respective components, processor-memory arrangements, circuitry, etc.) to perform at least: receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively; and in response to receiving a request to page one or more user devices of the multicast service session, paging the one or more user devices during one or more wake-up periods, regardless of a current power saving mode of the one or more user devices.

According to a sixth aspect, there is provided a method comprising receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively; wake up at one or more wake up times; and beginning to receive multicast data and/or receiving a paging request for the multicast data at one or more wake-up times.

According to a seventh aspect, there is provided a method comprising configuring a multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively; transmitting a session configuration to the network entity and/or transmitting a session configuration of a service announcement as a multicast service session to the user equipment; and transmitting data of the multicast service session at the wake-up time.

According to an eighth aspect, there is provided a method comprising receiving a session configuration of a multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively; storing a multicast service session configuration, the multicast service session configuration including a multicast service session identifier and one or more wake-up times; and activating one or more multicast service sessions configured to transmit downlink data based on the multicast service session identifier and the one or more wake-up times.

According to a ninth aspect, there is provided a method comprising retrieving multicast service session configuration information for one or more multicast service sessions upon receipt of a join request from a user equipment, receiving a multicast service session identifier and one or more wake-up times as part of the multicast service session configuration, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively, and transmitting the multicast service session identifier and the one or more wake-up times to the user equipment as a reply to the join request.

According to a tenth aspect, there is provided a method comprising receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively; and paging the one or more user devices during the one or more awake periods in response to receiving the request for paging the one or more user devices of the multicast service session, regardless of a current power saving mode of the one or more user devices.

According to a further aspect, there is provided a computer program configured to cause an apparatus to perform any of the methods of the sixth, seventh, eighth, ninth or tenth aspects.

According to a further aspect, there is provided a non-transitory computer readable medium comprising program instructions which, when executed by at least one processor, cause an apparatus to perform at least any of the methods of the sixth, seventh, eighth, ninth or tenth aspects.

Drawings

FIG. 1 illustrates an example system in accordance with at least some embodiments.

Fig. 2A illustrates signal transmission in accordance with at least some embodiments.

Fig. 2B illustrates signal transmission in accordance with at least some embodiments.

FIG. 3 illustrates an example apparatus capable of supporting at least some embodiments.

Fig. 4A illustrates a flow chart of a method in accordance with at least some embodiments.

Fig. 4B illustrates a flow chart of a method in accordance with at least some embodiments.

Fig. 4C illustrates a flow chart of a method in accordance with at least some embodiments.

Fig. 4D illustrates a flow chart of a method in accordance with at least some embodiments.

Fig. 4E illustrates a flow chart of a method in accordance with at least some embodiments.

Detailed Description

Discontinuous reception, DRX, for downlink, DL, multicast service transmissions is provided. For example, a downlink multicast service may be used for discontinuous software updates. To be able to save power, the UE utilizes DRX to be in sleep mode during inactivity and only wakes up at a specific time. To enable DL multicast data transfer, the receiving UE should be in active mode or awake. To avoid the UE continuously monitoring for possible multicast data transmissions, the UE is configured to wake up at the indicated wake-up time and to start receiving multicast data. The wake-up time may be provided to the UE by the 3GPP fifth generation core 5GC or by the application function AF. The 5GC may be configured to provide a wake-up time to the UE in response to a session join request sent by the UE. The AF may be configured to provide a predefined wake-up time to the UE in a service announcement of an MBS session. In addition, when configuring the MBS session, the AF provides the multicast broadcast session management function MB SMF with information on the wake-up time. The MB SMF is configured to activate MBS sessions based on the wake-up time. Hereinafter, a multicast service session for DL transmission is mentioned.

FIG. 1 illustrates an example system in accordance with at least some embodiments. The system comprises a user equipment UE 110 and a communication network 120.UE 110 may be capable of receiving data from communication network 120 or via communication network 120 via a point-to-multipoint PTM and point-to-point PTP connection.

The communication network 120 may be a public land mobile network PLMN or a non-public network NPN, e.g. as defined in the 3GPP standardization specification TS 23.501. The NPN may be a stand alone NPN (SNPN) or a public network integrated NPN (PNI-NPN). The communication network 120 may be a non-3 GPP network such as a cable network, an IEEE 802.11 wireless network protocol based network, wi-Fi, or a wireless local area network WLAN. The communication network 120 or wireless access may be based on advanced long term evolution LTE ADVANCED (LTE-a) or new radio NR (also referred to as fifth generation 5G), although the present embodiment is not limited to such an architecture. The present embodiment can also be applied to other types of communication networks having appropriate components by appropriately adjusting parameters and procedures. Some examples of other options for a suitable system and radio access network RAN are: universal Mobile Telecommunications System (UMTS) radio access network (UTRAN or E-UTRAN), long term evolution (LTE, same as E-UTRA), worldwide Interoperability for Microwave Access (WiMAX), bluetoothPersonal Communication Service (PCS),/>Wideband Code Division Multiple Access (WCDMA), systems using Ultra Wideband (UWB) technology, sensor networks, mobile ad hoc networks (MANET), and internet protocol multimedia subsystem (IMS), or any combination thereof.

Non-3 GPP access (e.g., WLAN access) can be arranged via a non-3 GPP interworking function N3 IWF. The N3IWF is configured to provide an access point for the 5G core network outside the 5G radio access network RAN. The N3IWF is configured to route messages outside the 5G RAN of the non-3 GPP network through an internet protocol, IP, secure tunnel. The AMF of the 5G core network is configured to implement non-access stratum NAS security, such as ciphering and integrity protection algorithms.

In fig. 1, user equipment UE 110 comprises a mobile device including a wireless mobile communication device with or without a subscriber identity module SIM. The user identifier may comprise a subscriber identity module SIM, a universal subscriber identity module USIM or any corresponding user identifier, e.g. an executable or programmable identifier. The user identifier implements a user identity, e.g. for authentication between the UE and the network. User equipment may include, but is not limited to: smart phones, cellular phones, notebook computers, tablet computers, machine-to-machine nodes, M2M nodes, machine type communication nodes, MTC nodes, large-scale machine type communication nodes, mMTC nodes, internet of things (IoT nodes), automotive telemetry units, or any terminal or entity capable of wireless communication or access to a wireless network. The UE may be a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a gaming machine, a notebook, and a multimedia device. The UE may be a device with the capability to operate in an internet of things (IoT) network, which is a scenario in which objects are provided with the capability to communicate data over the network without requiring person-to-person or person-to-computer interaction.

The 5G can use multiple input-multiple output (MIMO) technology at the UE and network side (many more base stations or nodes than LTE (so-called small cell concept), including macro sites operating in cooperation with small base stations), and employ various radio technologies according to service requirements, use cases, and/or available spectrum. 5G mobile communications support a wide range of use cases and related applications including video streaming, augmented reality, different modes of data sharing, and various forms of machine-type applications, (e.g., (large-scale) machine-type communications (mMTC), including vehicle security, different sensors, and real-time control). It is expected that 5G has multiple radio interfaces, i.e., below 7GHz, centimeter waves, and millimeter waves, and may also be integrated with existing legacy wireless access technologies (e.g., LTE). The frequency range below 7GHz may be referred to as FR1, and the frequency range above 24GHz (or more precisely 24-52.6 GHz) may be referred to as FR2, respectively. At least in early stages, integration with LTE can be implemented as a system, where macro coverage is provided over LTE, and 5G radio interface access comes from small cells aggregated over LTE. In other words, 5G is designed to support both inter-RAT operability (e.g., LTE-5G) and inter-RI operability (inter-radio interface operability, e.g., below 7GHz-cmWave, below 7 GHz-cmWave-mmWave). One of the concepts that is considered to be used in 5G networks is network slicing, where multiple independent and dedicated virtual sub-networks (network instances) can be created within the same infrastructure to run services with different demands on latency, reliability, throughput and mobility.

The 5G may also utilize satellite communications to enhance or supplement coverage for 5G services, such as by providing backhaul. Possible use cases are to provide service continuity for machine-to-machine (M2M) or internet of things (IoT) devices or passengers on board vehicles, or to ensure service availability for critical communications as well as future rail/maritime/aviation communications. Satellite communications may utilize geostationary orbit (GEO) satellite systems, but may also utilize Low Earth Orbit (LEO) satellite systems, particularly large satellite constellations (systems in which hundreds of (nano) satellites are deployed). Each satellite in the constellation may cover several satellite-enabled network entities, thereby forming an above-ground cell. An on-ground cell may be created by an on-ground relay node or a gNB located on the ground or in a satellite.

In fig. 1, a communication network 120 is equipped with one or more network functions NF 122. A network function may refer to an operating and/or physical entity. The network function may be a specific network node or network element, or may be a specific function or set of functions performed by one or more entities, e.g. virtualized network elements VNFs. One physical node may be configured to perform multiple NFs. Examples of such network functions include resource control or management functions, session management or control functions, interworking, data management or storage functions, authentication functions, or a combination of two or more of these functions.

In the case of the third generation partnership project (3 GPP), fifth generation (5G), system Services Based Architecture (SBA), core network, NF may include at least some of the following: the access and mobility management function AMF, session management function SMF, network slice selection function NSSF, network opening function NEF, network repository function NRF, unified data management UDM, unified data repository UDR, authentication server function AUSF, policy control function PCF and application function AF. The NEF is configured to provide access to open network services and functions. The UDM is configured to manage network user data in a single centralized element. The UDM is configured to host data management related functions, such as an authentication credential repository and processing function ARPF, configured to select an authentication method based on a user identity and a configuration policy. UDR facilitates sharing and providing user-related data throughout services of 3GPP systems.

The communication network 120 may further include a secure edge protection proxy SEPP configured to operate as a secure edge node or gateway. For example, NFs may communicate with each other using a representational state transfer REST application programming interface. These may be referred to as RESTful APIs. Further examples of NFs include NFs associated with gaming, streaming media, or industrial process control. The system may also include nodes in a 3G or 4G node system, such as a home subscriber server HSS, and appropriate interworking functions that perform protocol conversions between, for example, diameter and JSON-based RESTful APIs. Although primarily described herein using the terminology of 5G systems, the principles described herein are also applicable to other communication networks, such as 4G networks and non-3 GPP networks.

Although the example of fig. 1 has one communication network 120, there may be two or more networks. In the case of a multi-network, in fig. 1, SEPP is a network node located at the operator network boundary that may be configured to receive messages (e.g., hypertext transfer protocol HTTP requests or HTTP responses from NF), protect the sending application, and forward such reformatted messages to the recipient SEPP via an intermediate node chain (e.g., IP eXchanges IPX). The receiver SEPP receives the message sent by the sender SEPP and forwards the message to NF within its operator network, e.g. AUSF.

The physical link from a user equipment to a network node is called the uplink UL or reverse link, and the physical link from a network node to a user equipment is called the downlink DL or forward link. The network node or its functionality may be implemented using any entity suitable for such use, such as a node, host, server or access point. A communication system typically comprises more than one network node, in which case the network nodes may also be configured to communicate with each other over wired or wireless links designed for that purpose. These links may be used for signal transmission purposes. A network node is a computing device configured for controlling radio resources of a communication system to which it is coupled. A network node may also be referred to as a Base Station (BS), an access point, or any other type of interface device, including a relay station capable of operating in a wireless environment. The network node comprises or is coupled to a transceiver. From the transceiver of the network node, a connection is provided to the antenna unit for establishing a bi-directional radio link with the user equipment. The antenna unit may comprise a plurality of antennas or antenna elements. The network node is further connected to a core network CN or a next generation core network NGC. Depending on the system, the corresponding device on the CN side may be a serving gateway S-GW that routes and forwards user data packets, a packet data network gateway P-GW or a mobility management entity MME for providing a connection of the user equipment UE with an external packet data network, etc.

The multicast broadcast service MBS refers to a point-to-multipoint service configured to simultaneously provide the same service and specific content to a plurality of UEs. MBS includes multimedia broadcast multicast service MBMS, which refers to a point-to-multipoint interface specification for existing and upcoming 3GPP cellular networks, which is specified to provide transport of broadcast and multicast services within both cells as well as core networks. When the transmission is delivered over an LTE network, the specification refers to evolved multimedia broadcast multicast service eMBMS or LTE broadcast. The 5G CN is configured to receive a single copy of the MBS data packet and to transmit the single copy of the MBS data packet to the respective UE in PTP via the UE-specific PDU session. In PTP, each UE is associated with an MBS session via a PDU session. In the case of PTM, the 5G CN is configured to receive a single copy of the MBS data packet and to transmit the single copy of the MBS data packet to the RAN node.

In broadcast, the distributed service announcement includes information about the service, service parameters for activating the service, one or more wake-up times, and optionally other parameters. At distributed wake-up time or times, a session is established enabling DL to broadcast between the 5GC and NG RAN. The data is then broadcast over the air interface. After the data has been broadcast and/or after the broadcast session period expires, session and 5GC resources are released.

In multicasting, the distributed service announcement includes information about the service, service parameters for activating the service, one or more wake-up times, and optionally other parameters. The UE joins the session by indicating to the 5GC that the UE wants to receive multicast data. Sessions are identified by multicast session IDs distributed in service announcements. A UE session join request to join a session may trigger a session establishment in which transmission resources are established for transporting DL multicast data between the 5GC and NG RAN. After the session has been established, the multicast data is sent to the UE and other UEs that have been authorized to receive the multicast content. After the data has been sent and/or after the multicast session period expires, the UE sends a session leave message and exits the multicast session. After multicast data does not need to be transmitted, resources in 5GC and multicast session are released. Multicast MBS sessions require that 5GS authorize UEs based on authorization information (e.g., preconfigured or provided by AF). For example, UE authorization for a particular multicast MBS session may be performed via a service announcement.

To schedule an MBS session, the UE is configured to perform reception of MBS data. MBS data may be transmitted to the UE via the established point-to-multipoint PTM or point-to-point PTP connection. The UE is configured to perform signaling for joining and leaving MBS sessions.

The RAN is configured to control the switching of each UE between PTM and PTP transmissions. The RAN is configured to support MBS sessions during handover. The NG RAN is configured to transmit data packets over the air from 5G shared to multiple UEs using PTM and/or PTP, and to control switching of each UE between PTM/PTP transmissions. The NG RAN is configured to support MBS session continuity through a driven handover and to support notification of MBS session activation over the radio interface.

The AMF is configured to select an MBS-capable SMF. The SMF is configured to discover multicast broadcast SMF (MB SMF) of MBS sessions and to authorize MBS session join operations, if applicable. The SMF is configured to interact with the MB SMF to obtain MSB data for separate transfer and to manage MSB session content. The SMF is configured to interact with the RAN for shared data transmission resource establishment.

The MB SMF is configured to handle MBs session management, including quality of service QoS control. The MB SMF is configured to control MBs streaming from the multicast broadcast user plane function MB UPF to the RAN. The user plane function UPF is configured to support features and capabilities that facilitate user plane operations such as packet routing and forwarding, interconnection with data networks, policy enforcement, and data buffering. The MB SMF is configured to schedule MB UPF for multicast broadcast MB streaming based on local policies or policy rules from a policy control function PCF that provides policy rules for control plane functions. The MB SMF is configured to interact with the SMF to modify protocol data unit PDU sessions associated with the MBS. The MB SMF is configured to interact with the RAN via the AMF and the SMF to establish data transmission resources between the MB UPF and the RAN node for the 5GC shared MBs service delivery method. The MB SMF is configured to control data transmission using a 5GC separate MBs service transfer method.

The AF is configured to provide MBS service information or a request for MBS service from 5GC by providing service information, which may include QoS requirements for 5 GC. The AF is configured to negotiate with the NEF for MBS-related service disclosure. The AF is configured to assign temporary mobile group identities TGMI, and to initiate MBS sessions and MBS transmissions. For shared MBS delivery, the AF is configured to schedule the resources of MBS sessions established in the MB UPF and NG RAN. The AF is configured to signal both the NG RAN and MB SMF for MBS session management. The AF is configured to select NG RAN for notification and broadcast of MBS session activation. The AF is configured to signal the NG RAN for NG RAN MBS capabilities and to interact with the NEF for MBS related service openness. AF gets 5GC authorization to transfer MBS data to and/or interact with 5 GC. For signal exchange with the 5GC, the NEF/MB SF is configured to perform authorization for external AF to determine whether interaction with the 5GC is allowed.

The NEF is configured to provide interfaces of MBS procedures (including service provisioning, MBS session, and QoS management) to the AF. The NEF is configured to interact with AF and MB SMF for MBS session operations, determining transmission parameters, and session transmissions. The NEF is configured to select a serving MB SMF for the MBS session.

The MB STF is configured to handle packet transport functions such as framing, multiple streams, packet forward error correction FEC, and encoding for any IP multicast enabled application. The MB STF is configured to process MBs transmissions of an input file as an object or object stream.

The UDM is configured to support subscription management for authorization and MBS sessions. The subscriber profile in the UDM includes subscription information to provide subscriptions for MBS services in the UDM. Subscriptions to MBS may include a particular multicast service that allows joining any multicast service or that allows joining an indication. MBS subscription data is provided to the SMF through the UDM during PDU session establishment, e.g. as defined in TS23.502, using Numd _sdm service for the subscription data type "UE context in SMF data". As described in TS23.502, SMF selection subscription data is provided to the AMF by the UDM. The UDR supports UE authorization information for managing MBS sessions. The UE authorization of the multicast service may define whether the UE is authorized to fully receive any MBS multicast session data or whether and how the UE is authorized to receive a particular multicast service. If the UE is not authorized to receive MBS session data, the network will not send data to the UE even if the MBS session is open to any UE.

The MBS session identifier ID is used to identify MBS sessions in the entire 5G system on interfaces towards AF, between AF and UE and towards UE. The MBS session ID may include a source specific IP multicast address for the MBS multicast session or a temporary mobile group identification TGMI for identifying the multicast or broadcast session. The TMGI is a radio resource configured to identify MBS bearer services. This can be used instead of using an IP multicast address and an access point name. The TMGI is allocated by the multicast broadcast service center MB SC, and the TMGI of a specific MBs is provided to the UE during the MBs activation procedure. The UE may obtain at least one MBS session ID via the MBS service announcement. For MBS multicast sessions, the source specific IP multicast address may be assigned by the 5GC or by an external network. The source specific IP multicast address is used to identify the MBS multicast session, and it includes two IP addresses: one IP unicast address used AS a source address in an IP packet for identifying the source of a multicast service such AS AF/AS, and the other IP multicast address used AS a destination address in an associated IP packet for identifying the multicast service associated with the source.

Fig. 2A illustrates signal transmission according to some embodiments. Arranged left to right on the longitudinal axis: UE, RAN, AMF, SMF, MB SMF, and AF. Time advances from top to bottom.

The MBS session is configured. The AF may provide MBS service information or a request for MBS service from the 5 GC. For MBS-related service disclosures, the AF may negotiate with the NEF. The AF may assign a temporary mobile group identity TGMI. The AF may schedule resources for MBs sessions established in the MB UPF and NG RANs for shared MBs transmissions. The AF may signal both the NG RAN and MB SMF for MBS session management. The AF may select the NG RAN to inform MBS session activation and broadcasting. The AF may signal the NG RAN for NG RAN MBS capabilities and interact with the NEF for MBS-related service disclosure. The NEF may provide interfaces for MBS procedures to the AF, including service provisioning, MBS session, and QoS management. The NEF may interact with the AF and MB SMF for MBs session operations, determining transmission parameters and session transmissions. The NEF may choose to serve MB SMF for MBS session.

In stage 202, the af provides a configuration request to the MB SMF. The configuration request includes an MBS session identifier, an MBS session ID, and one or more wake-up times. The request may be sent via NEF or MB SF. The wake-up time is configured to correspond to the MBS session time. For example, the one or more wake-up times may include a fixed time per day or hour or minute, a first wake-up time, and a repeating cycle or list of wake-up times. The one or more wakeup times may include one or more start times of an MBS session, one or more start times and end times of an MBS session, one or more start times and time periods of an MBS session.

In stage 203, MB SMF stores MBS session configuration and wake-up time. The MB SMF stores the wake-up time in response to receiving a configuration request including the wake-up time.

In stage 204, mb SMF sends a configuration reply to AF. After the wake-up time and MBS session configuration are stored, the MB SMF is configured to send a reply to the AF sending the configuration request.

In stage 205, the AF sends service announcements for MBS sessions. The AF is configured to send a service announcement to the UE. The service announcement distributes information about the service and parameters about the activation of the service. The service announcement is prolonged with the wake-up time. The service announcement of the MBS session includes the MBS session ID and the wake-up time. At this stage, the UE is informed of wake-up times, which correspond to upcoming MBS session times.

In stage 206, the ue wakes up at a wake-up time indicated in the service announcement. The UE is configured to wake up at the indicated wake-up time and to start receiving MBS data and/or to listen for pages related to MBS sessions. Alternatively or additionally, the UE may be configured to: when it wakes up at the indicated wake-up time, a session join for the MBS session is sent. Via session joining, the UE indicates to the 5GC that the UE wishes to receive MBS data identified by a particular MBS session ID. Session joining from the UE may trigger transmission resource establishment of DL MBS data between the 5GC and NG-RAN. The UE may participate in multiple MBS sessions or be authorized to receive multiple MBS session transmissions. In this case, the UE wakes up at the indicated wake-up time of the plurality of MBS sessions to receive DL transmissions of each MBS session. In addition, the UE may employ other power saving modes, DRX or eDRX, and monitor for pages at indicated intervals.

In stage 207, the mb SMF activates the MBS session at the indicated wake-up time. The MG SMF may be configured to activate and deactivate multicast or broadcast sessions according to the MB SID and according to the indicated wake-up time.

In stage 208, the mb SMF sends a paging message to the SMF. At stage 209, the smf sends a paging message to the AMF. At stage 210, the amf sends a paging message to the RAN. In stage 211, the ran sends a paging message to the UE. A paging message or an activation message is sent to the UE in order to inform the UE of the activation of the MBS session. The UE may listen for unicast paging occasions after one or more wake-up times.

In stage 212, the AF starts sending MBS session content at wake-up time. MBS session content is transmitted to the UE via the DL link. The MBS data is transmitted to the UE. After the MBS data has been transmitted, the UE may leave the MBS session one by one. This may be indicated to 5G by sending a session leave message. After the MBS session ends and MBS data is transmitted, the MBS session is released. The resources established for the MBS session in 5G are released.

Fig. 2B illustrates signal transmission in accordance with at least some embodiments. Arranged left to right on the longitudinal axis: UE, RAN, AMF, SMF, MB SMF, and AF. Time advances from top to bottom.

The MBS session is configured. The AF may provide MBS service information or a request for MBS service from the 5 GC. The AF may negotiate with the NEF for MBS-related service disclosure. The AF may assign a temporary mobile group identity TGMI. The AF may schedule resources for MBs sessions established in the MB UPF and NG RANs for shared MBs transmissions. The AF may signal both the NG RAN and MB SMF for MBS session management. The AF may select NG RAN for informing MBS session activation and broadcasting. The AF may signal the NG RAN for NG RAN MBS capabilities and interact with the NEF for MBS-related service disclosure. The NEF may provide interfaces for MBS procedures to the AF, including service provisioning, MBS session, and QoS management. The NEF may interact with the AF and MB SMF for MBs session operations, determining transmission parameters and session transmissions. The NEF may select a serving MB SMF for the MBS session.

In stage 220, the af provides a configuration request to the MB SMF. The configuration request includes an MBS session identifier, an MBS session ID, and one or more wake-up times. The request may be sent via NEF or MB SF. The wake-up time is configured to correspond to a scheduling time of the MBS session. For example, the one or more wake-up times may include a fixed time per day or hour or minute, a first wake-up time, and a repeating cycle or list of wake-up times. The one or more wakeup times may include one or more start times of an MBS session, one or more start and end times of an MBS session, one or more start times of an MBS session, and a time period.

In stage 221, the mb SMF sends a configuration reply to the AF. The MB SMF is configured to send a reply to the AF that sent the configuration request.

In stage 222, the MB SMF stores MBS session configuration and wake-up time. In response to receiving a configuration request including a wake-up time, the MB SMF stores the wake-up time. The wake-up time may be stored together with the MBS session information, e.g. in UDM/UDR or MB SMF.

In stage 223, the AF sends a service announcement including MBS session ID. The service announcement provides information about the MBS service and parameters for activating the MBS service. After the service announcement, an MBS session is established to enable DL MBS data to be transferred between the 5GC and the NG-RAN. Session establishment may be triggered by a request from the AF.

The UE joins the MBS session. The UE may indicate that it wishes to utilize the sleep period. The indication is optional.

In stage 224, the ue sends a PDU session modification message to the SMF. The PDU session modification message includes a request to join the MBS. The message may include an indication that the UE wishes to use the sleep period.

In stage 225, the SMF sends a request to the MB SMF for information about the MBS session. The SMF is configured to send a request to the MB SMF in response to receiving the PDU session modification message from the UE.

In stage 226, the mb SMF sends an information response to the SMF. The response is sent in response to receiving a request from the SMF for information about the MBS session. The response includes one or more wake-up times in addition to other parameters such as QoS parameters and 5QI (5G QoS identifier). At this stage, the wake-up time is sent from MB SMF to SMF. The SMF configured to process the joining MBS receives information on a wake-up time, which may be UDM/UDR or MB SMF, from a database storing information on MBS sessions.

In stage 227, in response to receiving the information response from the MB SMF, the SMF sends a PDU session modification response to the UE. The PDU session modification response includes a join acknowledgement with a wakeup time. At this stage, in response to sending the PDU session modification message to join the MBS at stage 224, the UE receives a wake-up time corresponding to the time of the upcoming MBS session.

At stage 228, the ue wakes up at the wake-up time indicated in the service announcement. The UE is configured to wake up at the indicated wake-up time and to start receiving MBS data and/or to listen for pages related to MBS sessions. Alternatively or additionally, the UE may be configured to: when it wakes up at the indicated wake-up time and leaves the PSM mode, a join request for the MBS session is sent. The UE may participate in multiple MBS sessions or be authorized to receive multiple MBS session transmissions. In this case, the UE wakes up at the indicated wake-up time of the plurality of MBS sessions in order to receive DL transmission of each MBS session. Further, the UE may use DRX or eDRX and monitor for pages at indicated intervals.

In stage 229, the mb SMF activates the MBS session at the indicated wake-up time. The MG SMF may be configured to activate and deactivate multicast or broadcast sessions according to the MBS ID and according to the indicated wake-up time.

In stage 230, the mb SMF sends a paging message to the SMF. At stage 231, the smf sends a paging message to the AMF. At stage 232, the amf sends a paging message to the RAN. In stage 233, the ran sends a paging message to the UE. A paging or activation message is sent to the UE to inform and announce the activation of the MBS session to the UE. The UE may listen for unicast paging occasions after one or more wake-up times.

In stage 234, the AF starts sending MBS session content at wake-up time. MBS session content is transmitted to the UE via the DL link. After DL MBS data has been transmitted or after MBS session expiration, MBS session is released. The UE may leave the session by sending a leave session message. The resources of 5GC for MBS session are released.

In case the UE wakes up at the indicated wake-up time, as in the previous embodiments and shown in fig. 2a and 2b, but the UE does not receive data via the MBS session, the UE may enter an idle mode or PSM mode. Alternatively, the UE may send a request to leave the MBS session upon entering PSM mode.

In previous solutions, a UE receiving data via unicast may be in a power save mode PSM, where the UE sleeps indefinitely after a certain timer expires. The timer is negotiated with the network via NAS signaling. Time starts when the UE enters idle mode. Once there is UL data to send, the UE exits the PSM, but upon entering the PSM, the UE cannot receive DL data or monitor for paging. In the DRX case, DRX parameters are negotiated with the network via NAS signaling. DRX is used at a lower level to define on-time to monitor the paging control channel PCCH for activity in preparation for paging reception. In DRX mode, the UE may sleep during inactive off times. DRX may be in the millisecond range. Under extended DRX (eDRX), an extended idle mode DRX cycle length is negotiated with the network via NAS signaling. The cycle length of eDRX may be a hierarchy from seconds to hours or days. In eDRX mode, the UE may achieve paging in a particular paging hyper-frame PH, which corresponds to a particular set of H-SFN values. The PH calculation formula is a function of the extended idle mode DRX cycle and the UE specific identifier as described in TS 36.304. In addition to the previous PSM, DRX or eDRX, there is an enabled power saving mode, which is interrupted at the indicated predefined wake-up time. The UE receives the multicast service session at the indicated predefined wake-up time. The multicast service session is timed according to the indicated wake-up time. Additionally or alternatively, the provided wake-up time may be used with prior art solutions (such as PSM, DRX, and/or eDRX). For example, when there is multicast data to send, this causes IoT devices with fixed wake-up times to wake up at the same time. This causes all IoT devices to wake up at the same time to receive multicast DL data. In this way, the inactive or dormant periods of the IoT device may be optimized such that power savings are achieved.

The MBS may be provided in one or more MBS service areas. The MBS service area may be identified by a cell list or a tracking area list. Only UEs within the MBS service area may receive the content data, while UEs outside the MBS service area are not allowed to receive the location specific content. For multicast, UEs outside the MBS service are not allowed to join the MBS service. The network should not transmit location specific content to any UE that moves out of the MBS service region. The UE may obtain service area information for the local multicast service via MBS service announcement or via NAS signaling, wherein the accepted or rejected replies include a cell list or tracking area list during UE session join message transmission. The location-related MBS includes a local MBS in a plurality of MBS zones. Each MBS service zone in the location-related MBS uses the same MBS session ID and a different zone session ID. The zone session ID may be allocated by the MB SMF and used in combination with the MBs session ID. The UE may not know the zone session ID but only the MBS session ID. The location dependent MBS enables different content data to be distributed to different MBS zones.

FIG. 3 illustrates an example apparatus capable of supporting at least some embodiments. Shown is an apparatus 300, which may comprise, for example, an NF, DCS node or entity or UE. The processor 310 is included in the device 300, for example, the processor 310 may include a single-core processor including one processing core or a multi-core processor including more than one processing core. Processor 310 may generally include a control device. Processor 310 may include more than one processor. The processor 310 may be a control device. The processing cores may include, for example, cortex-A8 processing cores manufactured by ARM holders or Zen processing cores designed by Advanced Micro Devices Corporation. For example, the processor 310 may include at least one AMD THREADRIPPER and/or Intel kernel processors. The processor 310 may include at least one application specific integrated circuit ASIC. The processor 310 may include at least one field programmable gate array FPGA. Processor 310 may be a component in device 300 for performing method steps, such as processing, obtaining, determining, running, receiving, and responding, for example. Processor 310 may be configured, at least in part, by computer instructions, to perform actions.

The processor may comprise or consist of circuitry or multiple circuitry configured to perform the various stages of the methods according to embodiments described herein. As used in this disclosure, the term "circuitry" may refer to one or more or all of the following: (a) Hardware-only circuit implementations, e.g., implementations in analog and/or digital circuitry only, and (b) combinations of hardware circuitry and software, e.g., as applicable: (i) A combination of analog and/or digital hardware circuitry and software/firmware, and (ii) a hardware processor (including a digital signal processor) with software, any portion of software and memory that work together to cause a device (e.g., a server) to perform various functions, and (c) a hardware circuit and/or processor, such as a microprocessor or a portion of a microprocessor, that requires software (e.g., firmware) to operate, but where software is not required to operate, the software may not be present.

This definition of circuit applies to all uses of this term in this application, including in any claims. As a further example, as used in the present application, the term circuit also encompasses: only a hardware circuit or processor (or processors) or a portion of a hardware circuit or processor (or their accompanying software and/or firmware implementations. For example, and if applicable to particular claim elements, the term circuitry also encompasses: the baseband integrated circuit or processor integrated circuit of the mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

The device 300 may include a memory 320. Memory 320 may include random access memory and/or persistent memory. Memory 320 may include at least one RAM chip. For example, memory 320 may include solid state, magnetic, optical, and/or holographic memory. Memory 320 may at least partially access processor 310. Memory 320 may be at least partially included in processor 310. Memory 320 may be a means for storing information. Memory 320 may include computer instructions that processor 310 is configured to execute. When computer instructions configured to cause processor 310 to perform a particular action are stored in memory 320 and device 300 as a whole is configured to run under direction of processor 310 using computer instructions from memory 320, processor 310 and/or at least one processing core thereof may be considered to be configured to perform the particular action. Memory 320 may be at least partially included in processor 310. Memory 320 may be at least partially external to device 300, but may be accessed by device 300.

The device 300 may include a transmitter 330. The device 300 may include a receiver 340. The transmitter 330 and the receiver 340 may be configured to transmit and receive information, respectively, according to at least one cellular or non-cellular standard. Transmitter 330 may include more than one transmitter. Receiver 340 may comprise more than one receiver.

The device 300 may include a user interface UI 360.UI 360 may include at least one of the following: a display, a keyboard, a touch screen, a vibrator (configured to signal to a user by vibrating the device 300), a speaker, and a microphone. The user is able to operate the device 300 via the UI 360, for example to configure user data management parameters.

The device 300 may include or be configured to accept a user identity module 370. The subscriber identity module 370 may comprise, for example, a subscriber identity module SIM card that may be installed in the device 300. User identity module 370 may include information identifying a subscription of a user of device 300. User identity module 370 may include encrypted information that may be used to verify the identity of a user of device 300 and/or facilitate encryption of communication information and billing of communications effected by the user of device 300 via device 300. The UE comprises a user identity module 370 configured to include the disclosed real user identifier.

Processor 310 may be equipped with a transmitter configured to output information from processor 310 to other devices included in device 300 via wires internal to device 300. Such a transmitter may include a serial bus transmitter configured to output information to memory 320 for storage therein, for example, via at least one wire. Instead of a serial bus, the transmitter may comprise a parallel bus transmitter. Likewise, the processor 310 may include a receiver configured to receive information in the processor 310 from other devices included in the device 300 via wires internal to the device 300. Such a receiver may comprise a serial bus receiver, for example, configured to receive information from receiver 340 via at least one wire for processing in processor 310. Instead of a serial bus, the receiver may comprise a parallel bus receiver. The device 300 may comprise further devices not shown in fig. 3.

Processor 310, memory 320, transmitter 330, receiver 340, UI 360, and/or user identity module 370 may be interconnected by wires internal to device 300 in a number of different ways. For example, each of the devices described above may be separately connected to a main bus internal to device 300 to allow the devices to exchange information. However, as will be appreciated by those skilled in the art, this is merely one example, and various ways of interconnecting at least two of the above-described devices may be selected according to embodiments without departing from the scope of the invention.

Fig. 4A is a flow chart of a method 400 in accordance with at least some embodiments. The stages of the illustrated method may be performed in an apparatus such as a UE or IoT device, for example, where the UE may include means for performing the method or in a control device configured to control its functions when installed therein.

Stage 410 includes receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively. Stage 420 includes waking up at one or more wake-up times. The UE may be ready to receive data for one or more multicast services and/or to listen for paging requests for multicast services. Stage 425 includes beginning to receive multicast data and/or receiving a paging request for multicast data at one or more wakeup times.

The method 400 of fig. 4A may further include receiving a service announcement for a multicast service including one or more wake-up times. The method may further include sending a join multicast service request and receiving a join multicast service reply including one or more wake times. The method may further include receiving the join reply as a Downlink (DL), non-access stratum (NAS) message. The one or more wake-up times include at least one of: a fixed repetition time; a first time and repetition frequency; a fixed time of day. The method may include receiving a plurality of wakeup times corresponding to a plurality of multicast service session times, and means for waking up and starting to receive multicast data at the wakeup time of each multicast service session. Receiving a paging request for multicast data at one or more wake-up times may include listening for unicast paging occasions after the one or more wake-up times.

Fig. 4B is a flow chart of a method 401 in accordance with at least some embodiments. The stages of the illustrated method may be performed in an apparatus such as an NF (e.g. AF), which may include components for performing the method, or in a control device configured to control its functions when installed therein. Stage 430 includes configuring a multicast service session, the session configuration including a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively. Stage 440 includes sending a session configuration to a network entity and/or the session configuration for sending a service announcement to a user equipment as the multicast service session. Stage 445 includes transmitting data for the multicast service session at the wake time.

The method 401 may further include sending a service announcement for the multicast service session including the multicast service session identifier and one or more wake times.

Fig. 4C is a flow chart of a method 402 in accordance with at least some embodiments. The stages of the illustrated method may be performed in an apparatus such as an NF (e.g., MB SMF), which may include components for performing the method, or in a control device configured to control its functions when installed therein. Stage 450 includes receiving a session configuration for a multicast service session, the session configuration including a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, such as timed, allocated or scheduled. Stage 460 includes storing a multicast service session configuration that includes a multicast service session identifier and one or more wake-up times. Multicast service session configuration may be stored to MB SMF or UDM/UDR. Stage 465 includes activating one or more multicast service sessions configured to transmit downlink data based on the multicast service session identifier and one or more wake-up times. The method 402 may further include providing a wake time in response to the information request for the multicast service session. The method 402 may further include transmitting the multicast service session configuration including the multicast service session identifier and the one or more wakeup times to other session management functions when querying the multicast service configuration information.

Fig. 4D is a flow chart of a method 403 in accordance with at least some embodiments. The stages of the illustrated method may be performed in an apparatus such as NF (e.g., SMF), where the SMF may include means for performing the method or in a control device configured to control its functions when installed therein. Stage 470 includes retrieving MBS session configuration information for one or more multicast service sessions upon receiving a join request from a user equipment. Stage 475 includes receiving a multicast service session identifier and one or more wake-up times as part of a multicast service session configuration, where the one or more wake-up times correspond to the one or more multicast service session times, respectively. Stage 480 includes transmitting, to the user device, a multicast service session identifier and one or more wake-up times in reply to the join request.

Fig. 4E is a flow chart of a method 404 in accordance with at least some embodiments. The stages of the illustrated method may be performed in an apparatus such as an NF (e.g., AMF), which may include components for performing the method, or in a control device configured to control its functions when installed therein. Stage 485 includes receiving one or more wake-up times, where the one or more wake-up times correspond to one or more multicast service session times, respectively. The multicast service session time refers to a scheduled time of the multicast service session. Stage 490 includes: in response to receiving a request to page one or more user devices of a multicast service session, the one or more user devices are paged during one or more wake-up periods regardless of a current power saving mode of the one or more user devices. The method 404 may further include rejecting the request to page the user device outside of the awake period if the user device is in a power save mode.

According to the previously introduced utilization of the wake-up time, the UE may enter PSM when there is no DL multicast data until the next wake-up time. This enables improved power saving, wherein the access stratum is deactivated in the PSM. In the previous PSM arrangement, the UE cannot receive the page because the lower layer or RRC of the UE becomes deactivated in the PSM and the UE wakes up only when it is about to transmit UL data. Further, when receiving the DL data notification message, the network or AMF will send a DL data notification rejection message to the SMF, because the AMF knows that the UE is dormant and cannot receive pages.

The embodiments described herein utilize PSM. However, unlike the previous solutions, the UE is configured to wake up not only when there is UL data to be transmitted, but also when the MBS preconfigured wake-up time indicates an activation time in order to listen to any incoming MBS content or data. On the network side, when the AMF receives a request to page the UE for an MBS session at any one of the wakeup times or wakeup periods, the AMF does not reject the request to return to the SMF, but will proceed and page the UE. Thus, the AMF knows the wake-up time of the multicast service session. For example, the AMF may obtain wake-up time information during the join reply.

The aforementioned wake-up refers to an interruption of the power saving mode or activation of a device or function. The aforementioned wake-up time or period may be referred to as an indicated, shared, configured or preconfigured wake-up time. The wake-up time indicates a wake-up time of one or more UEs, and the same time refers to a timed multicast service session. The wake-up time corresponds to an allocated or scheduled multicast service session time. The wake-up time may indicate a time period corresponding to a multicast service session time period. The wake-up time is configured according to a subsequent or upcoming multicast service session. For example, the one or more wake-up times may include: a fixed time per day or hour or minute, a first wake-up time and repetition period, or a list of wake-up times. The one or more wake-up times may include: one or more start times of the multicast service session, one or more start and end times of the multicast service session, one or more start times of the multicast service session, and a time period.

It is to be understood that the disclosed embodiments of the invention are not limited to the specific structures, process steps, or materials disclosed herein, but are extended to equivalents thereof as recognized by those of ordinary skill in the relevant arts. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting.

Reference throughout this specification to one embodiment or embodiment means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of the phrases "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Where a term such as "for example," "about" or "substantially" is used to refer to a numerical value, the exact numerical value is also disclosed.

For convenience, a plurality of items, structural elements, compositional elements, and/or materials may be presented herein in a common list. These lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. Furthermore, various embodiments and examples of the invention are mentioned herein, along with alternatives to the various components thereof. It should be understood that these embodiments, examples, and alternatives are not to be construed as actual equivalents of each other, but rather as independent autonomous representations of the invention.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the previous descriptions, numerous specific details are provided, such as lengths, widths, shapes, etc., to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.

While the foregoing illustrates the principles of the invention in one or more specific applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and implementation details can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the invention. Accordingly, it is not intended to limit the invention except as indicated by the claims set forth below.

The verbs "comprise" and "comprise" as used in this document are open-ended limits and neither exclude nor require the presence of unrecited features. The features recited in the dependent claims may be freely combined with each other unless explicitly stated otherwise. Furthermore, it should be understood that the use of "a" or "an" throughout this document (i.e., the singular forms) do not exclude the plural forms.

At least some embodiments of the invention find industrial application in the implementation of power saving modes.

Claims

1. An apparatus, comprising:

Means for receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively;

means for waking up at the one or more wake-up times; and

Means for receiving multicast data beginning at the one or more wakeup times, and/or means for receiving a paging request for multicast data at the one or more wakeup times.

2. The apparatus of claim 1, comprising: means for receiving a service announcement for a multicast service including the one or more wake-up times.

3. The apparatus of claim 1, comprising: means for sending a session join request for a multicast service session, and means for receiving a session join reply for the multicast service session, the session join reply including the one or more wake times.

4. The apparatus of any of claims 1 to 3, wherein the one or more wake-up times comprise at least one of: a fixed repetition time; a first time and repetition frequency; a fixed time of day; one or more start times; one or more start and end times; and one or more start times and time periods.

5. The apparatus according to any one of claims 1 to 4, wherein the apparatus comprises: means for receiving a plurality of wake-up times corresponding to a plurality of multicast service session times, and means for waking up at the wake-up time for each of the multicast service sessions and beginning to receive multicast data.

6. The apparatus of any of claims 1-5, wherein the means for receiving a paging request for multicast data at the one or more wake-up times comprises: means for listening for unicast paging occasions after the one or more wake-up times.

7. An apparatus comprising an application function, comprising:

Means for configuring a multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively;

Means for sending the session configuration to a network entity, and/or means for sending the session configuration to a user equipment as a service announcement for the multicast service session; and

And means for transmitting data of the multicast service session at the wake time.

8. An apparatus comprising multicast broadcast session management functionality, comprising:

Means for receiving a session configuration of a multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively;

means for storing the multicast service session configuration, the multicast service session configuration comprising the multicast service session identifier and the one or more wake-up times; and

Means for activating the one or more multicast service sessions configured to transmit downlink data based on the multicast service session identifier and the one or more wake-up times.

9. The apparatus of claim 8, comprising: means for transmitting the multicast service session configuration including the multicast service session identifier and the one or more wakeup times to other session management functions upon querying multicast service configuration information.

10. An apparatus comprising session management functions, comprising:

Means for retrieving multicast service session configuration information for one or more multicast service sessions upon receiving a join request from a user device;

Means for receiving a multicast service session identifier as part of the multicast service session configuration, and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively; and

Means for transmitting the multicast service session identifier and the one or more wake-up times to the user equipment as a reply to the join request.

11. An apparatus comprising access and mobility functions, comprising:

Means for receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively; and

Means for paging one or more user devices of a paging multicast service session in response to receiving a request for the one or more user devices, regardless of a current power saving mode of the one or more user devices during the one or more wake-up periods.

12. The apparatus of any one of claims 1 to 11, wherein the one or more wake-up times comprise: a fixed time per day or hour or minute, a first wake-up time and repetition period, or a list of wake-up times.

13. An apparatus, comprising:

At least one processor; and

At least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to perform:

receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively;

waking up at the one or more wake-up times; and

And starting to receive the multicast data at the one or more wake-up times, and/or receiving a paging request for the multicast data.

14. The apparatus of claim 13, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform:

A service announcement of a multicast service including the one or more wake-up times is received.

15. The apparatus of claim 13, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform:

Transmitting a session join request for a multicast service session, and receiving a session join reply for the multicast service session, the session join reply including the one or more wake-up times.

16. The apparatus of any of claims 13 to 15, wherein the one or more wake-up times comprise at least one of: a fixed repetition time; a first time and repetition frequency; a fixed time of day; one or more start times; one or more start and end times; and one or more start times and time periods.

17. The apparatus according to any of claims 13 to 16, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least perform:

A plurality of wake-up times corresponding to a plurality of multicast service session times are received, and wake-up at the wake-up time for each of the multicast service sessions and begin receiving multicast data.

18. The apparatus according to any of claims 13 to 17, wherein the instructions, when executed by the at least one processor, cause the apparatus to at least perform:

listening for unicast paging occasions after the one or more wake-up times.

19. An apparatus comprising an application function, comprising:

At least one processor; and

Configuring a multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively;

Transmitting the session configuration to a network entity and/or transmitting the session configuration as a service announcement of the multicast service session to a user equipment; and

And sending the data of the multicast service session at the wake-up time.

20. An apparatus comprising multicast broadcast session management functionality, comprising:

At least one processor; and

receiving a session configuration of a multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively;

Storing the multicast service session configuration, the multicast service session configuration including the multicast service session identifier and the one or more wake-up times; and

Based on the multicast service session identifier and the one or more wake-up times, the one or more multicast service sessions configured to transmit downlink data are activated.

21. The apparatus of claim 20, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to perform:

Upon querying multicast service configuration information, transmitting the multicast service session configuration including the multicast service session identifier and the one or more wakeup times to other session management functions.

22. An apparatus comprising session management functions, comprising:

At least one processor; and

retrieving multicast service session configuration information for one or more multicast service sessions upon receiving a join request from a user device;

Receiving a multicast service session identifier as part of the multicast service session configuration, and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively; and

Transmitting the multicast service session identifier and the one or more wake-up times to the user equipment as a reply to the join request.

23. An apparatus comprising access and mobility functions, comprising:

At least one processor; and

Receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively; and

In response to receiving a request to page one or more user devices of a multicast service session, the one or more user devices are paged during the one or more wake-up periods regardless of a current power saving mode of the one or more user devices.

24. The apparatus of any of claims 13 to 23, wherein the one or more wake-up times comprise: a fixed time per day or hour or minute, a first wake-up time and repetition period, or a list of wake-up times.

25. An apparatus, comprising:

circuitry configured to: receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively;

Circuitry configured to: waking up at the one or more wake-up times; and

Circuitry configured to: starting to receive multicast data at the one or more wake-up times, and/or circuitry configured to: a paging request for multicast data is received at the one or more wake-up times.

26. An apparatus comprising an application function, comprising:

Circuitry configured to: configuring a multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively;

circuitry configured to: transmitting the session configuration to a network entity and/or the session configuration for transmitting a service announcement as the multicast service session to a user equipment; and

Circuitry configured to: and sending the data of the multicast service session at the wake-up time.

27. An apparatus comprising multicast broadcast session management functionality, comprising:

Circuitry configured to: receiving a session configuration of a multicast service session, the session configuration comprising a multicast service session identifier and one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively;

Circuitry configured to: storing the multicast service session configuration, the multicast service session configuration including the multicast service session identifier and the one or more wake-up times; and

Circuitry configured to: based on the multicast service session identifier and the one or more wake-up times, the one or more multicast service sessions configured to transmit downlink data are activated.

28. An apparatus comprising session management functions, comprising:

Circuitry configured to: retrieving multicast service session configuration information for one or more multicast service sessions upon receiving a join request from a user device;

Circuitry configured to: receiving a multicast service session identifier as part of the multicast service session configuration, and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively; and

Circuitry configured to: transmitting the multicast service session identifier and the one or more wake-up times to the user equipment as a reply to the join request.

29. An apparatus comprising access and mobility functions, comprising:

Circuitry configured to: receiving one or more wake-up times, wherein the one or more wake-up times correspond to one or more multicast service session times, respectively; and

Circuitry configured to: in response to receiving a request to page one or more user devices of a multicast service session, the one or more user devices are paged during the one or more wake-up periods regardless of a current power saving mode of the one or more user devices.

30. A method, comprising:

waking up at the one or more wake-up times; and

And starting to receive the multicast data and/or receiving the paging request for the multicast data at the one or more wake-up times.

31. A method, comprising:

And sending the data of the multicast service session at the wake-up time.

32. A method, comprising:

33. A method, comprising:

34. A method, comprising:

35. A non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform:

waking up at the one or more wake-up times; and

36. A non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform:

Transmitting the session configuration to a network entity and/or the session configuration for transmitting a service announcement as the multicast service session to a user equipment; and

And sending the data of the multicast service session at the wake-up time.

37. A non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform:

38. A non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform:

Receiving a multicast service session identifier as part of the multicast service session configuration, and one or more wake-up times, wherein the one or more wake-up times correspond to the one or more multicast service session times, respectively, and

39. A non-transitory computer-readable medium comprising instructions that, when executed by an apparatus, cause the apparatus to perform: