Resource efficient delivery of multicast and broadcast services

Abstract

Methods and systems are disclosed for techniques for enabling a wireless device to receive a multicast service in a radio resource control inactive (RRCINCTIVE state. In one embodiment, a method of wireless communication comprises receiving, by a first network node from a second network node, session management signaling comprising an alternative quality of service profile, and transmitting, by the first network node, multicast session data to a wireless device based on the alternative quality of service profile during a radio resource control inactive period.

Description

Technical Field

[0001] This patent document is generally directed to wireless communications. Background Art

[0002] Mobile communication technology is driving the world towards an increasingly connected and networked society. The rapid growth of mobile communications and technological advances have led to greater demand for capacity and connectivity. Other aspects such as energy consumption, equipment cost, spectrum efficiency and latency are also important to meet the needs of various communication scenarios. Various technologies are currently being discussed, including new methods to provide higher quality of service, longer battery life and improved performance. Summary of the invention

[0003] Among other things, the patent document describes techniques for enabling a wireless device to receive multicast services in a radio resource control inactive (RRC_INCTIVE) state.

[0004] In one aspect, a method of data communication is disclosed. The method includes receiving, by a first network node, session management signaling including an alternative quality of service profile from a second network node, and transmitting, by the first network node, multicast session data based on the alternative quality of service profile to a wireless device during a radio resource control inactive period.

[0005] In another aspect, a method of data communication is disclosed. The method includes receiving, by a wireless device, a configuration associated with a multicast session from a network node, wherein the configuration assists the wireless device in receiving or continuing to receive the multicast session in a specific cell, and receiving, by the wireless device, multicast session data after transitioning to a radio resource control inactive state.

[0006] In another aspect, a method of data communication is disclosed. The method includes obtaining, by a wireless device, assistance information provided from an application layer or a service layer to an access layer, and receiving, by the wireless device, a point-to-multipoint configuration associated with a multicast and broadcast service.

[0007] In another aspect, a method of data communication is disclosed. The method includes receiving, by a wireless device, a network configuration to report a receive-only mode (ROM) service configuration, and transmitting, by the wireless device to a network node, a ROM report associated with a ROM service that the wireless device is receiving or is about to receive based on the network configuration.

[0008] In another aspect, a method of data communication is disclosed. The method includes transmitting, by a wireless device, to a network node, a first receive-only mode (ROM) report associated with a ROM service that the wireless device is receiving or is about to receive to report a ROM service configuration, receiving, by the wireless device, from the network node, an inquiry regarding a second ROM report of the network node, and transmitting, by the wireless device, the second ROM report of the network node to the network node.

[0009] In another aspect, a method of data communication is disclosed. The method includes transmitting, by a wireless device, to a network node, a first receive-only mode (ROM) report associated with a ROM service being received or to be received by the wireless device to report a ROM service configuration, receiving, by the wireless device, an indication for the wireless device to transmit an updated ROM report to the network node, and, if update reporting of the ROM report is enabled by the network and if the ROM service configuration has been updated, transmitting, by the wireless device, the updated report to the network node.

[0010] In another example aspect, a wireless communication apparatus is disclosed, comprising a processor configured to implement the above method.

[0011] In another example aspect, a computer storage medium having stored thereon codes for implementing the above method is disclosed.

[0012] This document describes these and other aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 An example of a wireless communication system based on some example embodiments of the disclosed technology is shown.

[0014] Figure 2 is a block diagram representation of a portion of an apparatus based on some embodiments of the disclosed technology.

[0015] Figure 3 An example is shown in which a UE released to the RRC Inactive state continues to receive multicast communications on the SCell.

[0016] Figure 4 Examples of processes for wireless communications based on some example embodiments of the disclosed technology are shown.

[0017] Figure 5 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0018] Figure 6 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0019] Fig. 7A The reporting procedure for partial or full receive-only mode (ROM) reporting is shown. Figure 7B The reporting procedure of ROM report based on network query is shown. Figure 7C The update procedure of the ROM report is shown.

[0020] Figure 8 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0021] Fig. 9 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0022] Fig.10 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown. DETAILED DESCRIPTION

[0023] The section headings used in this document are only for ease of understanding and do not limit the scope of the embodiments to the sections in which they are described. In addition, although the embodiments are described with reference to 5G examples, the disclosed technology can be applied to wireless systems using protocols other than 5G or 3GPP protocols.

[0024] Figure 1 An example of a wireless communication system (e.g., Long Term Evolution (LTE), 5G, or NR cellular network) including a BS 120 and one or more user equipment (UE) 111, 112, and 113 is shown. In some embodiments, uplink transmissions (131, 132, 133) may include uplink control information (UCI), higher layer signaling (e.g., UE assistance information or UE capabilities), or uplink information. In some embodiments, downlink transmissions (141, 142, 143) may include DCI or higher layer signaling or downlink information. The UE may be, for example, a smartphone, a tablet, a mobile computer, a machine-to-machine (M2M) device, a terminal, a mobile device, an Internet of Things (IoT) device, etc.

[0025] Figure 2It is a block diagram representation of a portion of an apparatus based on some embodiments of the disclosed technology. An apparatus 205 such as a network device or a base station or a wireless device (or UE) may include a processor electronic device 210 such as a microprocessor, which implements one or more technologies proposed in this document. The apparatus 205 may include a transceiver electronic device 215 to send and / or receive wireless signals through one or more communication interfaces (such as an antenna 220). The apparatus 205 may include other communication interfaces for transmitting and receiving data. The apparatus 205 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, the processor electronic device 210 may include at least a portion of the transceiver electronic device 215. In some embodiments, the apparatus 205 is used to implement at least some of the disclosed technologies, modules, or functions.

[0026] With the introduction of New Radio (NR) Multicast and Broadcast Service (MBS) in 5G System (5GS), 5GS will gain a reliable alternative to achieve efficient data delivery by leveraging the broadcast nature of wireless communications.

[0027] The disclosed techniques may be implemented in some embodiments to provide scalability of MBS: by enabling the UE to receive multicast services in a radio resource control inactive (RRC_INACTIVE) state, including network behavior when making such a decision and information required by the 5GC, and in the case of multicast reception on an SCell instead of a PCell, where a mechanism is defined for service continuity during RRC state transitions; by enabling the UE to receive broadcast services from a public land mobile network (PLMN) that is different from the PLMN that provides the UE's unicast connectivity; and by providing MBS in the case of network sharing, the network is able to support such network sharing with minimal Uu interface overhead.

[0028] For multicast services defined by 3GPP, both UEs in the RRC_CONNECTED state and UEs in the RRC_INACTIVE state will be supported for different services with different requirements, for example, the network can provide some advanced functions to provide higher reliability for UEs in the RRC_CONNECTED state. For multicast services like mission-critical push-to-talk (MCPTT) with a large number of receiving UEs in one cell, or when there is a requirement for energy saving on the UE, multicast reception can be performed on UEs in the RRC_INACTIVE state to release network resources or reduce power consumption of keeping the UE in the RRC_CONNECTED state.

[0029] It is beneficial to enable UE to receive multicast services in the Radio Resource Control Inactive (RRC_INACTIVE) state. For mission-critical communication services via multicast defined in cellular networks, there are the following requirements:

[0030] The main driver for this key issue is to enable services for a large number of UEs in a cell.

[0031] In general, a UE may be denied entry to a cell based on several constraints, including the maximum number of connected UEs and the amount of traffic in the cell. Based on the public safety group call model, the amount of traffic in the cell may be relatively low compared to other types of traffic, since the public safety UEs participating in the group call can use (share) only one bearer (multicast) for the downlink, and it typically has only one UE transmitting at a time.

[0032] These issues include how to identify the traffic model of a group call from the perspective of how the resources required and consumed at different points in time during the group call affect the preemption and admission of bearers and UEs.

[0033] Since there is a clear possibility that the number of UEs may exceed the limit that can be served in a cell, potential procedures for UEs to receive and participate in service in these situations are studied.

[0034] Since some number of UEs may end up with no or limited service because they are too many within a cell, methods of providing information to various related subsystems are studied to indicate which UEs are selected for service exclusion / degradation and restoration.

[0035] Currently, once an uplink unicast (side) radio bearer (usually a guaranteed bit rate (GBR)) is established for a group call, it is allocated to the UE for the duration of the group call, regardless of whether the user is speaking or not. However, the traffic model for group calls dictates that the radio bearer may actually be used relatively infrequently, i.e. only when a user has the floor. In the case of a mission-critical broadcast group, no user may speak except the one speaker.

[0036] The proposed solution is that the UE only has an uplink GBR bearer when it holds the floor. This assumes that the radio bearer (or a large portion of the bandwidth associated with it) can be allocated and released quickly so that when the user activates the PTT key, the key performance indicators (KPIs) associated with this type of group call can still be met.

[0037] According to current standards, the time for radio bearer setup in LTE (unicast, GBR) is 115ms, including the estimated (10ms radio link delay, 5ms network interface delay and 5ms processing delay). It should be noted that the UE is already in connected mode rather than idle mode, saving transition time, and part of the radio bearer setup can be run while processing the floor control request, with the end result that according to current standards, it should be possible to allocate radio bearers (or extend the uplink bandwidth of radio bearers) on demand and meet KPI 1 requirements.

[0038] Standardization group experts are working to define signaling mechanisms to enable fast and temporary changes in bandwidth associated with uplink bearers, typically triggered by floor control signaling. Uplink floor control (typically small (S)RTCP packets) messages can be sent via a reduced bandwidth uplink bearer or via a separate (typically non-GBR) radio bearer.

[0039] A Mission Critical Application Server (MCAS) may wish to remedy or mitigate the reported situation. For example, MCAS may influence some UEs in a cell reported as having high congestion to switch to receiving data in idle mode to avoid the chance of UEs being preempted.

[0040] UEs receiving data in idle mode will have potentially degraded service when it comes to transmission, as the time they take to gain access to the uplink radio bearer will be longer than would be the case for UEs in a "normal" mode of operation.

[0041] Depending on how they are configured, UEs may attempt to quickly access a cell when instructed by the user, when a mobility event occurs, or when they need to update certain parameters.

[0042] The above scenarios require the following design considerations for multicast services in the radio access network (RAN): (1) the maximum number of UEs in a cell is limited, so not all UEs are in the RRC_CONNECTED state; (2) in rare cases, a UE may need to apply floor control to perform uplink transmission. However, it is expected that the latency with which the UE can perform uplink transmission is low.

[0043] Therefore, it is expected that the UE can perform multicast reception in the radio resource control inactive (RRC_INACTIVE) state while resuming the RRC connection so that the uplink can be performed with lower latency. The radio resource control inactive (RRC_INACTIVE) state is introduced in 5GNR so that the UE context in the access layer is maintained in the radio access network (RAN), and this mechanism enables the UE to remain in a lower power mode with less network resource consumption and resume the RRC connection with lower latency and less signaling overhead.

[0044] One solution for the above-mentioned multicast reception mission-critical push-to-talk (MCPTT) scenario is to enable the UE to receive multicast services in the radio resource control inactive (RRC_INACTIVE) state: when network resources are scarce, the UE can be released to the radio resource control inactive (RRC_INACTIVE) state; for UEs with uplink requirements, for example, UEs intending to take over floor control and send voice or video, the UE can be sent back to the radio resource control connected (RRC_CONNECTED) state with low latency.

[0045] To maximize the scalability of MBS service delivery in the RAN, other measures need to be supported: MBS services delivered by one public land mobile network (PLMN) can be received by UEs connected to another PLMN; MBS services can be delivered in a network sharing scenario and the overhead of duplicate resource consumption needs to be avoided.

[0046] In some embodiments of the disclosed technology, the word "MBS" may be used to identify a service that may be an MBS multicast service or an MBS broadcast service. In some examples, the terms "MBS multicast service" or "multicast service", and "MBS broadcast service" or "broadcast service" may be used explicitly.

[0047] For broadcast communication services, the same service and the same specific content data are provided to all UEs in a geographic area at the same time (e.g., all UEs in the broadcast service area are authorized to receive data). Broadcast communication services are delivered to UEs using broadcast sessions. UEs can receive broadcast communication services in RRC_IDLE, RRC_INACTIVE, and RRC_CONNECTED states.

[0048] For multicast communication services, the same service and the same specific content data are provided to a dedicated set of UEs at the same time (e.g., not all UEs in the multicast service area are authorized to receive data). Multicast communication services are delivered to UEs using multicast sessions. UEs can receive multicast communication services in RRC_CONNECTED state or RRC_INACTIVE state through mechanisms such as PTP and / or PTM delivery. HARQ feedback / retransmission can be applied to point-to-point (PTP) and point-to-multipoint (PTM) transmissions.

[0049] In some embodiments of the disclosed technology, the PTM configuration may indicate a point-to-multicast configuration based on which UE receives the MBS data.

[0050] In some embodiments of the disclosed technology, it is assumed that not all multicast services can or need to be scheduled to a UE in RRC_INACTIVE state. The RAN node decides to schedule multicast services for UEs in RRC_CONNECTED and / or RRC_INACTIVE based on information received from the 5GC (e.g., quality of service (QoS) information) and the availability of radio resource information.

[0051] For MBS services delivered to UEs in RRC_INACITVE state, QoS may be impaired. Providing or continuing to provide services with impaired QoS may be the best solution compared to not being able to provide the service at all. Therefore, in the case where the gNB needs to schedule the service with an alternative QoS, the 5GC may provide an alternative QoS for a specific QoS flow of the MBS session, which may be an impaired QoS.

[0052] In some embodiments of the disclosed technology, a prioritized list of one or more alternative QoS profiles for a multicast session may be provided to the NG-RAN.

[0053] In one example, the network is allowed to schedule a multicast session for transmission to a UE in RRC_INACTIVE if only one or more alternative QoS profiles for such multicast session are received from the 5GC. That is, multicast services can only be delivered to UEs in RRC_CONNECTED if no other QoS is received from the 5GC.

[0054] In another example, if an alternative QoS profile is received from the 5GC, the network uses the first alternative QoS profile in the list to schedule the multicast session for transmission to the UE in RRC_INACTIVE so that the network can have a value that matches the alternative QoS profile.

[0055] In another example, if a multicast session with an alternative QoS profile is configured to be scheduled for a UE in RRC_INACTIVE, the gNB triggers a notification to the 5GC about the scheduling decision of the alternative QoS profile that the RAN can satisfy.

[0056] In another example, if a multicast session is configured to be scheduled for a UE returning to RRC_CONNECTED, the gNB triggers a notification to the 5GC about the scheduling decision to allow the UE to receive the multicast session with a normal QoS profile in RRC_CONNECTED.

[0057] In some embodiments of the disclosed technology, an alternative QoS profile is provided in a protocol data unit (PDU) session context, and the PDU session is associated with a multicast session.

[0058] Sample Set 1

[0059] Various implementations of the features of the disclosed technology can be implemented based on the examples listed below.

[0060] Example 1. To enable a radio access network (RAN) node to deliver a multicast session to a UE in RRC_INACTIVE, the RAN node receives an alternative QoS profile in session management signaling, and the RAN node transmits the multicast session data for the UE in RRC_INACTIVE based on the alternative QoS profile.

[0061] Example 2. A method according to Example 1, wherein the RAN node is allowed to schedule a multicast session for transmission to a UE in RRC_INACTIVE if an alternative QoS profile for only one multicast session is received from a 5G core network (5GC).

[0062] Example 3. A method according to Example 1, wherein, if an alternative QoS profile is received from the 5GC, the network uses the first alternative QoS profile in the list that the network is able to meet with a value matching the alternative QoS profile to schedule a multicast session for transmission to the UE in RRC_INACTIVE.

[0063] Example 4. A method according to Example 3, wherein the session management signaling also includes a notification control enable indication, and if an alternative QoS profile is to be used to schedule multicast services for UEs in RRC_INACTIVE, the gNB triggers a notification of the scheduling decision to the 5GC with reference to the alternative QoS profile that the RAN can satisfy.

[0064] Example 5. A method according to Example 4, wherein the session management signaling further includes a notification control enable indication, and if a multicast service is to be scheduled for the UE that is transitioned back to RRC_CONNECTED, the gNB triggers a notification of the scheduling decision to the 5GC to allow the UE to receive the multicast session using a normal QoS profile in RRC_CONNECTED.

[0065] Example 6. The method of Example 1, 4, or 5, wherein the session management signaling is PDU session management signaling of a PDU session of one UE associated with the multicast session.

[0066] Example 7. The method of Example 1, 4, or 5, wherein the session management signaling is multicast session management signaling for each multicast session.

[0067] In some embodiments of the disclosed technology, the UE continues to receive multicast transmissions on the SCell.

[0068] A multicast session may be configured on the SCell of one UE. If the UE is to be released to the RRC_INACTIVE state, the UE will stop receiving data even though the configuration may not be released on the UE side. As a result, multicast reception will be interrupted, for example, if the PTM configuration for multicast is delivered via dedicated signaling, or if the multicast service is not provided in the cell where the UE resides.

[0069] The disclosed techniques may be implemented in some embodiments to provide an enhanced mechanism for allowing a UE to receive or continue to receive multicast data on a configured SCell with minimal delay or interruption when the UE is in RRC_CONNECTED.

[0070] A UE can receive multicast data based on two different delivery methods, namely, through dedicated signaling or through broadcast signaling.

[0071] If the UE wants to receive multicast data based on the configuration in the dedicated signaling, the UE obtains the PTM configuration of the multicast session in the SCell through dedicated RRC signaling.

[0072] If the UE wants to receive multicast data based on the configuration in the broadcast signaling, the UE obtains the PTM configuration of the multicast session in the SCell based on the information system information block 20 (SIB20) of the SCell and the multicast and broadcast service control channel (MCCH), and SIB20 and / or MCCH can be received by the UE in the broadcast signaling after residing in the SCell, or SIB20 and / or MCCH are delivered to the UE through dedicated signaling before the UE is released to RRC_INACTIVE.

[0073] This solution is presented in the following example, with different assumptions on how the UE receives the PTM configuration.

[0074] Figure 3 An example is shown in which a UE released to the RRC Inactive state continues to receive multicast communications on the SCell.

[0075] In one example, a UE is configured with carrier aggregation (e.g., PCell and SCell) and a multicast service can be provided on the SCell. Therefore, if the UE is to be released from RRC_CONNECTED to RRC_INACTIVE, all data reception activities on the SCell will stop. There are several options that can be considered to reduce potential service disruption. Assume that a multicast session is a service to be scheduled to a UE in RRC_INACTIVE.

[0076] In one example, the UE is indicated by the network on which cell to camp on preferentially. In this case, the SCell is indicated to the UE after release, and the UE camps on the SCell in the RRC_INACTIVE state to receive or continue to receive the multicast service.

[0077] In one example, the network can prioritize cells providing multicast data by indicating an offset that is temporarily applied to the indicated cells, and thus, during the cell selection phase, the UE can select a cell with multicast with a higher probability. For example, in the current cell selection criteria framework, the cell selection criteria S is met when:

[0078] Srxlev>0 and Squal>0

[0079] in:

[0080] Srxlev=Q rxlevmeas –(Q rxlevmin +Q rxlevminoffset )–P compensation -Qoffset temp

[0081] Squal=Q qualmeas –(Q qualmin +Q qualminoffset )-Qoffset temp

[0082] in:

[0083]

[0084]

[0085]

[0086] Therefore, configure Qoffset for the UE temp and the indicated cell (eg SCell) to help the UE select a serving cell to continue multicast data reception.

[0087] In another example, based on the associated cell that scheduled the multicast before the UE was released, and the multicast service to be scheduled to the UE in RRC_INACTIVE, the UE considers the associated cell to be prioritized and resides on the associated cell. For example, the UE can receive multicast data based on dedicated signaling, which carries a cell group configuration including multicast scheduling information. The cell group configuration is associated with a cell. If the UE is to receive multicast data based on broadcast signaling (e.g., MCCH), the cell that schedules MCCH is the associated cell.

[0088] In the above example, the UE remains synchronized with the SCell and the multicast configuration associated with the SCell to continue multicast data reception.

[0089] Sample Set 2

[0090] Various implementations of the features of the disclosed technology can be implemented based on the examples listed below.

[0091] Example 1. To enable multicast session delivery to a UE in RRC_INACTIVE with less interruption, the UE receives a configuration associated with the multicast session from the network, and the UE receives or continues to receive multicast session data after being released into the RRC_INACTIVE state.

[0092] Example 2. A method according to Example 1, wherein the configuration associated with the multicast session includes cell information, and the UE considers the cell with the highest priority during cell selection, resides on the indicated cell, and receives or continues to receive multicast session data after releasing to the RRC_INACTIVE state.

[0093] Example 3. A method according to Example 1, wherein the configuration associated with the multicast session includes cell information and an offset value of the indicated cell, and the UE selects a suitable cell based on the offset value.

[0094] Example 4. A method according to Example 1, wherein the configuration associated with the multicast session from the network is scheduling information for the multicast session, which includes cell information on which the multicast is being scheduled, and the UE considers the cell with the highest priority during cell selection, resides on the indicated cell, and receives or continues to receive multicast session data after being released to the RRC_INACTIVE state.

[0095] Example 5. The method of Example 1, wherein the UE remains synchronized with the SCell and the multicast configuration associated with the SCell to continue multicast data reception.

[0096] The disclosed techniques may be implemented in some embodiments to perform MBS reception in the context of network sharing.

[0097] In the case of network sharing, multiple multi-operator core networks (MOCNs) from different PLMNs can be connected to the same RAN node, e.g., a gNB. To avoid allocating duplicate resources to the same MBS service, the RAN recognizes that even MBS sessions with different session IDs (e.g., TMGI or IP multicast address) are actually the same MBS service in the application layer. In addition, the RAN avoids duplicating resources for the same identified MBS service. In some embodiments, for the same MBS broadcast session, there is a common set of PTM configurations in the MCCH and a common point-to-multipoint traffic channel (MTCH) resource is allocated.

[0098] In some embodiments of the disclosed technology, the UE may be configured with multiple TMGIs associated with the same broadcast service, and thus the UE can be associated with the TMGI list. If the UE can provide such a TMGI list from the service layer to the access layer, the UE can use one of the TMGIs in the TMGI list to receive the broadcast service on the Uu interface.

[0099] In one example, the UE provides a list of TMGIs from the service layer to the access layer. By looking at the service list in the MCCH, the UE is able to match the TMGI list with the TMGI list in the MCCH. If any TMGI provided in the service layer (e.g., user service description) matches the TMGI provided in the MCCH, the UE receives the broadcast data based on the PTM configuration identified by the identified TMGI. The TMGI information from the service layer may also include PLMN information, and thus the UE is able to accurately match the TMGI information, which also includes the PLMN information in the MCCH.

[0100] Depending on whether it is explicit PLMN information or PLMN index in TMGI IE, the UE can recover the complete TMGI including the complete PLMN and service ID. Such TMGI can uniquely identify the MBS between PLMNs.

[0101] Sample Set 3

[0102] Various implementations of the features of the disclosed technology can be implemented based on the examples listed below.

[0103] Example 1. In order to avoid allocation of duplicate radio resources for the same MBS service in case of network sharing, assistance information is provided from an upper layer to the access layer, and the UE receives the PTM configuration of the MBS service based on such information.

[0104] Example 2. The method of Example 1, wherein the auxiliary information is a list of TMGIs, wherein the TMGIs are associated with the same MBS service.

[0105] Example 3. The method of Example 2, wherein the auxiliary information including the TMGI list is included in a user service description provided in a service layer.

[0106] Example 4. A method according to Example 2, wherein the UE compares the TMGI list with the TMGI list in the MCCH, because any identified TMGI included in the MCCH is also included in the TMGI list from the upper layer, and the UE receives MBS data based on the PTM configuration identified by the identified TMGI in the MCCH.

[0107] Figure 4 Examples of processes for wireless communications based on some example embodiments of the disclosed technology are shown.

[0108] In some embodiments, process 400 for wireless communication may include: at 410, receiving, by a first network node, session management signaling including an alternative quality of service profile from a second network node, and at 420, transmitting, by the first network node, multicast session data to a wireless device based on the alternative quality of service profile during a radio resource control inactive period.

[0109] Figure 5 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0110] In some embodiments, process 500 for wireless communication may include: at 510, receiving, by the wireless device, a configuration associated with a multicast session from a network node, wherein a primary cell and a secondary cell are assigned to the wireless device, and at 520, receiving, by the wireless device, multicast session data after transitioning to a radio resource control inactive state.

[0111] Figure 6 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0112] In some embodiments, process 600 for wireless communication may include, at 610, obtaining, by a wireless device, assistance information provided from an application layer or a service layer to an access layer, and, at 620, receiving, by the wireless device, a point-to-multipoint configuration associated with a multicast and broadcast service.

[0113] Fig. 7A The reporting procedure for partial or full receive-only mode (ROM) reporting is shown. Figure 7B The reporting procedure of ROM report based on network query is shown. Figure 7C The update procedure of the ROM report is shown.

[0114] Sample Set 4

[0115] The Rel-17 NR MBS broadcast solution allows UEs to receive broadcast services in a downlink-only manner, for example, to perform broadcast reception without prior access to the network. Such multicast and broadcast service (MBS) broadcast services may be referred to as receive-only mode (ROM) services. However, in a typical use case for broadcasting, a UE may need to receive broadcast services and unicast services from one or more networks of the same or another operator at the same time, and some UEs may share hardware resources between broadcast and unicast. Therefore, for such UEs, unicast connectivity may be affected by broadcast reception. An example solution is to enable the UE to report a ROM service configuration that indicates the occupancy of UE capabilities caused by such a service to assist the network in making better scheduling decisions, such as better handover decisions, or making scheduling decisions to receive ROM services and unicast services simultaneously in the same cell or in different cells.

[0116] However, one thing that should not be overlooked in NR ROM support is the overhead caused by UE MII reporting to ROM services. Even if a network control mechanism is introduced to turn this feature on or off, there may still be overhead, including:

[0117] (1) Larger configuration set for NR ROM. For NR broadcast, optimization can minimize the MCCH size, for example, using some indexes to cover common configurations between different MBS services, such as DRX-ConfigPTM-Index-r17 and PDSCH-ConfigIndex-r17 in Rel-17. However, for UE reporting from another PLMN to the network, this optimization may not work, and such reporting still has a larger configuration set.

[0118] (2) In some cases, there may be many UEs consuming the same ROM service and may initiate the same larger report at the same time. Such scenarios should not be ignored because broadcast reception is designed to support a large number of UEs.

[0119] (3) Such reporting may not be needed in the beginning. There is also the same PLMN case where the UE's PCell may already know the configuration for the same operator. Therefore, if they are from the same operator, reporting one TMGI and cell information is enough, and everything else would be a waste of radio resources. The rest can be based on the network implementation with minimal overhead.

[0120] In some embodiments of the disclosed technology, information reported by the UE to the network may allow the network to be aware of ROM service configurations that may occupy a portion of the UE's capabilities.

[0121] (1) ROM report. This report includes all the configurations that need to be reported to the network to allow the network to understand the scheduling decisions for broadcast services and, therefore, to make better scheduling decisions for unicast. For example, enabling the UE to receive unicast and broadcast services simultaneously within the UE's capabilities, including handing over the UE to a cell or carrier frequency that allows the UE to do so. To avoid overhead, the ROM report may include two parts, as described below. It may also include information on the frequencies on which ROM services are scheduled as a priority. The UE may infer such information from the User Service Description (USD) and from the system information broadcast by the cell in which the ROM service is provided. This inference follows the existing mechanism: the USD provides a mapping between service IDs (e.g., TMGI) and service area IDs, while the system information provided by the access layer provides a mapping between service area IDs and carrier frequencies. Therefore, the UE is able to know the mapping of services and carrier frequencies and may therefore prioritize these frequencies during cell reselection.

[0122] (2) The first part of the ROM report. To avoid the overhead of such reporting (as mentioned in the previous section), the UE may only need to report a minimum set of ROM reports to the network. It may include a service ID (e.g., TMGI of a broadcast service) and carrier information (carrier information may include frequency or cell information) to uniquely identify possible broadcast configurations.

[0123] (3) The second part of the ROM report. This part of the ROM report includes scheduling information indicating the UE capabilities occupied by the ROM service. Based on such information, the network is able to schedule unicasts allowed by the UE capabilities to the UE. It may include the configuration of the ROM services that the UE is interested in receiving or is about to receive. The configuration may include numbers such as subcarrier spacing, service bandwidth, MBS radio bearers (MRBs) and their configuration (including header compression of MRBs). Such information indicates the UE capabilities occupied by the ROM service.

[0124] (4) Update ROM report. Since the broadcast configuration determined by another network entity can update the configuration, the gNB that establishes the UE RRC connection also needs to be aware of this configuration modification. Therefore, the UE may need to indicate the update of the ROM report to the network.

[0125] The disclosed techniques may be implemented in some embodiments to reduce what the UE needs to report, for example, to allow the UE to report a minimum set of content, because the network may already know the relevant configuration through OAM, reports from other UEs, or network interfaces (to be determined by RAN3). For example, the UE may need to send the first part of the ROM report in the first report, and send the entire ROM report or the second part of the ROM report in the second report.

[0126] The disclosed technology can be implemented in some embodiments to explicitly instruct the UE to report part or all of the configuration (e.g., broadcast signaling), or to trigger an inquiry to the UE at a later stage. For configuration updates, the network also indicates to the UE whether such an update needs to be made to multiple UEs to initiate such a configuration update. Various implementations of the features of the disclosed technology can be implemented based on the examples listed below.

[0127] Example 1. The network indicates a partial or full ROM report.

[0128] In one embodiment, the network instructs the UE to report part or all of the ROM report, and thus the UE does not always or by default report the full ROM report.

[0129] In one example, the network may broadcast such an indication in broadcast signaling, and the indication includes whether the ROM service that the UE is interested in receiving or is about to receive requires partial or full configuration. After receiving such an indication, if only a part of the ROM set is required, the UE reports the first part of the ROM to the network, and if the ROM service requires a complete configuration, the UE reports a full ROM report, which includes the configuration of the first part of the ROM and the configuration of the second part of the ROM.

[0130] Example 2. The UE reports the first part, and reports the second part only when asked by the network.

[0131] In some embodiments, the network query is related to a full ROM report based on the first part of the ROM report from the UE. After receiving the first ROM report from the UE, if the network needs more information than this, the network can trigger the UE to send such information by sending a query to the UE. The UE follows the network query to trigger a second ROM report. In one example, the following operations can be performed:

[0132] (1) For a UE that is interested in receiving or is about to receive ROM service, if the network allows and the triggering conditions are met, the UE reports the first part of the ROM report.

[0133] (2) The UE receives a query from the network to report the second ROM report.

[0134] (3) The UE reports the second ROM report to the network.

[0135] Example 3. ROM reported update.

[0136] In the case where the ROM service configuration is updated, a ROM report is provided to the network. However, not all ROM report updates are required, as the network can actively obtain such updates from some UEs, for example, only selected UEs are required to perform ROM reporting. In one example, the following operations may be performed:

[0137] (1) For a UE that is interested in receiving or is about to receive ROM service, if the network allows and the triggering conditions are met, the UE reports the first part of the ROM report.

[0138] (2) The UE receives an indication as to whether the UE needs to send an updated ROM report to the network.

[0139] (3) If the UE needs to send an updated ROM report to the network, the UE reports the updated ROM report to the network; if the UE does not need to send an updated ROM report to the network, the UE does not report the updated ROM report to the network even when the ROM report has been updated as indicated by the cell scheduling the ROM service.

[0140] Figure 8 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0141] In some embodiments, process 800 for wireless communication may include: receiving, by a wireless device, a network configuration to report a receive-only mode (ROM) service configuration at 810, and transmitting, by the wireless device, to a network node, a ROM report associated with a ROM service being received or to be received by the wireless device based on the network configuration at 820.

[0142] Fig. 9 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0143] In some embodiments, process 900 for wireless communication may include: at 910, the wireless device transmits to a network node a first receive-only mode (ROM) report associated with a ROM service being received or to be received by the wireless device to report a ROM service configuration, at 920, the wireless device receives from the network node an inquiry regarding a second ROM report of the network node, and at 930, the wireless device transmits to the network node the second ROM report of the network node.

[0144] Fig.10 Another example of a process for wireless communication based on some example embodiments of the disclosed technology is shown.

[0145] In some embodiments, process 1000 for wireless communication may include: at 1010, the wireless device transmits a first receive-only mode (ROM) report associated with a ROM service being received or to be received by the wireless device to a network node to report a ROM service configuration, at 1020, the wireless device receives a query about a second ROM report of the network node from the network node, and at 1030, the wireless device transmits the second ROM report of the network node to the network node.

[0146] It should be understood that this document discloses techniques that can be embodied in various embodiments to determine downlink control information in a wireless network. The disclosed and other embodiments, modules and functional operations described in this document can be implemented in digital electronic circuits, or in computer software, firmware or hardware, including the structures disclosed in this document and their structural equivalents, or in a combination of one or more thereof. The disclosed embodiments and other embodiments can be implemented in one or more computer program products, that is, a module of one or more computer program instructions encoded on a computer-readable medium for execution or control of its operation by a data processing device. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that affects a machine-readable propagation signal, or one or more combinations thereof. The term "data processing device" includes all devices, equipment and machines for processing data, including, for example, a programmable processor, a computer or multiple processors or multiple computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, for example, code constituting processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more thereof. A propagated signal is an artificially generated signal, eg, a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

[0147] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions). A computer program may be deployed to execute on one computer or on multiple computers located at one site or distributed across multiple sites and interconnected by a communications network.

[0148] The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and the apparatus can also be implemented with, special purpose logic circuitry, for example, an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).

[0149] Processors suitable for executing computer programs include, by way of example, general and special purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include, or be operatively coupled to receive data from or transfer data to one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM optical disks. The processor and memory may be supplemented by or incorporated into dedicated logic circuits.

[0150] Some embodiments may preferably implement one or more of the following solutions listed in clause format. The following clauses are supported and further described in the above embodiments and this document. As used in the following clauses and claims, a wireless device may be a user equipment, a mobile station, or any other wireless terminal including a fixed node such as a base station. The network device includes a base station including a next generation Node B (gNB), an enhanced Node B (eNB), or any other device that performs as a base station.

[0151] Clause 1. A wireless communication method, the method comprising: receiving, by a first network node, session management signaling from a second network node, the session management signaling comprising an alternative quality of service profile; and transmitting, by the first network node, multicast session data to a wireless device based on the alternative quality of service profile during a radio resource control inactive period.

[0152] Clause 2. The method of clause 1, wherein, upon receiving an alternate quality of service profile for a multicast session, the transmission of the multicast session data comprises scheduling the one multicast session for the wireless device during a radio resource control inactive period.

[0153] Clause 3. A method according to clause 1, wherein the transmission of multicast session data comprises: receiving a priority list of alternative quality of service profiles, the list comprising a plurality of alternative quality of service profiles and priorities of the quality of service profiles; and scheduling a multicast session for a wireless device during a radio resource control inactive period based on a first alternative quality of service profile that can be implemented by a first network node in the list.

[0154] Clause 4. A method according to clause 3, wherein the session management signaling also includes a notification control enable indication, wherein, in the presence of a multicast service to be scheduled for the wireless device during the radio resource control inactive period, the first network node triggers a notification of the scheduling determination to the second network node based on an alternative service quality profile that the first network node is able to meet.

[0155] Clause 5. A method according to clause 3, wherein the session management signaling further comprises a notification control enable indication, wherein, after the radio resource control inactive period transitions back to the radio resource control active period, in the event that there is a multicast service to be scheduled for the wireless device, the first network node triggers a notification of a scheduling determination to the second network node to allow the wireless device to receive the multicast session data during the radio resource control active period.

[0156] Clause 6. The method of clause 1, 4, or 5, wherein the session management signaling is protocol data unit (PDU) session management signaling for a PDU session of a wireless device associated with the multicast session.

[0157] Clause 7. A method as described in clauses 1, 4 or 5, wherein the session management signaling is multicast session management signaling for each multicast session.

[0158] Clause 8. A wireless communication method, the method comprising: receiving, by a wireless device, a configuration associated with a multicast session from a network node, wherein the configuration assists the wireless device in receiving or continuing to receive the multicast session in a particular cell; and receiving, by the wireless device, multicast session data after transitioning to a radio resource control inactive state.

[0159] Clause 9. A method according to Clause 8, wherein the configuration associated with the multicast session includes cell information, wherein the method further comprises: selecting, by the wireless device, a cell with the highest priority based on the cell information; and receiving, by the wireless device, multicast session data by resident on the cell indicated by the cell information after transitioning to a radio resource control inactive state.

[0160] Clause 10. The method of clause 8, wherein the configuration associated with the multicast session includes cell information and an offset value for the cell indicated by the cell information, wherein the method further comprises selecting, by the wireless device, the cell based on the offset value.

[0161] Clause 11. A method according to Clause 8, wherein the configuration associated with the multicast session includes scheduling information for the multicast session, the scheduling information including cell information about cells scheduled for the multicast session, wherein the method further comprises: selecting, by the wireless device, a cell with the highest priority based on the cell information; and receiving, by the wireless device, multicast session data by resident on the cell indicated by the cell information after transitioning to a radio resource control inactive state.

[0162] Clause 12. The method of clause 8, wherein receiving the multicast session data after transitioning to the radio resource control inactive state comprises maintaining, by the wireless device, synchronization with a supplementary cell and a multicast configuration associated with the supplementary cell.

[0163] Clause 13. A wireless communication method, the method comprising: obtaining, by a wireless device, assistance information provided from an application layer or a service layer to an access layer; and receiving, by the wireless device, a point-to-multipoint configuration associated with a multicast and broadcast service.

[0164] Clause 14. A method according to clause 13, wherein the auxiliary information includes a list of temporary mobile group identities (TMGIs), the list including TMGIs associated with multicast and broadcast services, and each TMGI is individually configured by a different public land mobile network (PLMN).

[0165] Clause 15. The method of clause 14, wherein the TMGI list is included in a user service description provided in a service layer.

[0166] Clause 16. The method according to clause 14 further includes: comparing, by the wireless device, the TMGI list with the TMGI list in the multicast and broadcast service control channel (MCCH); and receiving, by the wireless device, multicast and broadcast service data based on the point-to-multipoint configuration identified by the TMGI identified in the MCCH, when the TMGI identified in the MCCH is also included in the TMGI list from the application layer or the service layer.

[0167] Clause 17. A wireless communication method, the method comprising: receiving, by a wireless device, a network configuration to report a receive-only mode (ROM) service configuration; and transmitting, by the wireless device to a network node, a ROM report associated with a ROM service that the wireless device is receiving or is about to receive based on the network configuration.

[0168] Clause 18. A method according to clause 17, wherein the network configuration includes an indication for the wireless device to transmit a portion or the entire ROM report, wherein if the indication is associated with a first portion of the ROM report or if the wireless device is allowed to indicate the first portion of the ROM report to the network node, the wireless device transmits the first portion of the ROM report, or if the indication is associated with the entire ROM report or requires the wireless device to indicate the entire ROM report to the network node, the wireless device transmits the entire ROM report.

[0169] Clause 19. The method of clause 18, wherein the first portion of the ROM report includes a minimum set of ROM reports that uniquely identifies the ROM service to the network node to identify the associated scheduling configuration.

[0170] Clause 20. The method of clause 19, wherein the first portion of the ROM report includes a service identification (ID) of the ROM service and cell information associated with a cell in which the ROM service is scheduled.

[0171] Clause 21. A method according to clause 18, wherein the full ROM report includes: a minimum set of ROM reports for a network node to uniquely identify a ROM service; and scheduling information indicating UE capabilities occupied by the ROM service.

[0172] Clause 22. A method according to clause 21, wherein the scheduling information includes at least one of: a number of ROM service configurations including subcarrier spacing; a service bandwidth; or a configuration of a multicast and broadcast service radio bearer (MRB) and the MRB including header compression of the MRB.

[0173] Clause 23. The method of clause 21, wherein the scheduling information includes frequency priority information including a list of frequencies at which the ROM service is scheduled.

[0174] Clause 24. A wireless communication method, the method comprising: transmitting, by a wireless device, to a network node a first receive-only mode (ROM) report associated with a ROM service that the wireless device is currently receiving or is about to receive to report a ROM service configuration; receiving, by the wireless device, from the network node an inquiry regarding a second ROM report of the network node; and transmitting, by the wireless device, to the network node the second ROM report of the network node.

[0175] Clause 25. The method of clause 24, wherein the first ROM report comprises a minimum ROM report set for the network node to uniquely identify the ROM service to identify the associated scheduling configuration.

[0176] Clause 26. A method according to clause 25, wherein the first ROM report includes a service identification (ID) of the ROM service, the service identification (ID) including a temporary mobile group identification of the ROM service, and cell information associated with a cell on which the ROM service is scheduled.

[0177] Clause 27. The method of clause 24, wherein the second ROM report includes scheduling information indicating UE capabilities occupied by the ROM service.

[0178] Clause 28. A method according to clause 27, wherein the second ROM report includes at least one of: a number of ROM service configurations including subcarrier spacing; service bandwidth; or a configuration of a multicast and broadcast service radio bearer (MRB) and the MRB including header compression of the MRB.

[0179] Clause 29. The method of clause 27, wherein the scheduling information includes frequency priority information including a list of frequencies on which the ROM service is scheduled.

[0180] Clause 30. A wireless communication method, the method comprising: transmitting, by a wireless device, to a network node a first receive-only mode (ROM) report associated with a ROM service being received or to be received by the wireless device to report a ROM service configuration; receiving, by the wireless device, an indication for the wireless device to transmit an updated ROM report to the network node; and transmitting, by the wireless device, the updated report to the network node if update reporting of the ROM report is enabled by the network and if the ROM service configuration has been updated.

[0181] Clause 31. The method of clause 30, wherein the first ROM report comprises a minimum ROM report set for the network node to uniquely identify the ROM service to identify the associated scheduling configuration.

[0182] Clause 32. A method as described in clause 30, wherein the first ROM report and the updated ROM report include a minimum set of ROM reports for the network node to uniquely identify the ROM service, and scheduling information indicating UE capabilities occupied by the ROM service.

[0183] Clause 33. An apparatus for wireless communications, the apparatus comprising a processor configured to perform the method of any of clauses 1 to 32.

[0184] Clause 34. A non-transitory computer-readable medium having stored thereon code which, when executed by a processor, causes the processor to perform the method of any one of clauses 1 to 32.

[0185] Some embodiments described herein are described in the general context of methods or processes, which can be implemented in one embodiment by a computer program product, which is embodied in a computer-readable medium, including computer-executable instructions, such as program code, executed by a computer in a network environment. Computer-readable media may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), compact disk (CD), digital versatile disk (DVD), etc. Therefore, computer-readable media may include non-transient storage media. In general, program modules may include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. Computer or processor executable instructions, related data structures, and program modules represent examples of program codes for executing the steps of the methods disclosed herein. A specific sequence of such executable instructions or related data structures represents an example of corresponding behavior for implementing the functions described in these steps or processes.

[0186] In some disclosed embodiments, a device or module that can be implemented using hardware circuits, software, or a combination thereof. For example, a hardware circuit implementation may include discrete analog and / or digital components, such as being integrated as a part of a printed circuit board. Alternatively or additionally, the disclosed components or modules can be implemented as application specific integrated circuits (ASICs) and / or field programmable gate arrays (FPGAs) devices. Some embodiments additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor whose architecture is optimized for the operational requirements of digital signal processing related to the functions disclosed in the present application. Similarly, various components or subcomponents within each module may be implemented in software, hardware, or firmware. The connection between the modules and / or components within the modules may be provided using any of the connection methods and media known in the art, including but not limited to the communication performed by the Internet, wired, or wireless networks using appropriate protocols.

[0187] Although this document contains many details, these details should not be interpreted as limitations on the scope of the claimed invention or the content that can be claimed, but should be interpreted as descriptions of specific features of specific embodiments. Certain features described herein in the context of separate embodiments can also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment can also be implemented individually or in any suitable sub-combination in multiple embodiments. In addition, although the above-mentioned features can be described as working in a specific combination, and even initially required to be so, one or more features from the required combination can be cut out from the required combination in some embodiments, and the required combination can be for a sub-combination or a variant of a sub-combination. Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be understood as requiring the operations to be performed in the specific order or sequential order shown, or requiring the operations of all the diagrams to be performed to achieve the desired results.

[0188] Only some implementations and examples are described herein, and other implementations, improvements and variations can be made based on what is described and illustrated in this disclosure.

Claims

1. A wireless communication method, the method comprising: receiving, by the first network node from the second network node, session management signaling including a replacement quality of service profile; as well as During a radio resource control inactive period, multicast session data is transmitted by the first network node to a wireless device based on the alternative quality of service profile.

2. The method according to claim 1, wherein: Upon receiving an alternate quality of service profile for a multicast session, the transmission of the multicast session data includes scheduling the one multicast session for the wireless device during a radio resource control inactivity period.

3. The method according to claim 1, wherein: The transmission of the multicast session data includes: receiving an alternative quality of service profile priority list, the list comprising a plurality of alternative quality of service profiles and priorities of the quality of service profiles; and A multicast session is scheduled for the wireless device during a radio resource control inactive period based on a first alternative quality of service profile that is achievable by a first network node in the list.

4. The method according to claim 3, wherein: The session management signaling also includes a notification control enabled indication, wherein, in the event that there is a multicast service to be scheduled for the wireless device during a radio resource control inactive period, the first network node triggers a notification of a scheduling determination to the second network node based on an alternative quality of service profile that the first network node can meet.

5. The method according to claim 3, wherein: The session management signaling also includes a notification control enable indication, wherein, in the event that there is a multicast service to be scheduled for the wireless device after the radio resource control inactive period transitions back to the radio resource control active period, the first network node triggers a notification of a scheduling determination to the second network node to allow the wireless device to receive the multicast session data during the radio resource control activity.

6. The method according to claim 1, 4 or 5, wherein: The session management signaling is protocol data unit (PDU) session management signaling for a PDU session of the wireless device associated with a multicast session.

7. The method according to claim 1, 4 or 5, wherein: The session management signaling is multicast session management signaling for each multicast session.

8. A wireless communication method, the method comprising: receiving, by a wireless device from a network node, a configuration associated with a multicast session, wherein the configuration assists the wireless device in receiving or continuing to receive the multicast session in a particular cell; as well as After transitioning to the radio resource control inactive state, multicast session data is received by the wireless device.

9. The method according to claim 8, wherein: The configuration associated with the multicast session includes cell information, wherein the method further comprises: selecting, by the wireless device, a cell having a highest priority based on the cell information; and After transitioning to the radio resource control inactive state, the multicast session data is received by the wireless device by camping on the cell indicated by the cell information.

10. The method according to claim 8, wherein: The configuration associated with the multicast session includes cell information and an offset value of a cell indicated by the cell information, wherein the method further includes selecting, by the wireless device, a cell based on the offset value.

11. The method according to claim 8, wherein: The configuration associated with the multicast session includes scheduling information for the multicast session, the scheduling information including cell information about cells scheduled for the multicast session, wherein the method further comprises: selecting, by the wireless device, a cell having a highest priority based on the cell information; and After transitioning to the radio resource control inactive state, the multicast session data is received by the wireless device by camping on the cell indicated by the cell information.

12. The method according to claim 8, wherein: Receiving the multicast session data after transitioning to the radio resource control inactive state includes maintaining, by the wireless device, synchronization with a supplementary cell and a multicast configuration associated with the supplementary cell.

13. A wireless communication method, the method comprising: Acquiring, by the wireless device, auxiliary information provided to the access layer from the application layer or the service layer; as well as A point-to-multipoint configuration associated with a multicast and broadcast service is received by the wireless device.

14. The method according to claim 13, wherein: The auxiliary information includes a temporary mobile group identity (TMGI) list, the list includes TMGIs associated with the multicast and broadcast services, and each TMGI is individually configured by a different public land mobile network (PLMN).

15. The method according to claim 14, wherein: The TMGI list is included in the user service description provided in the service layer.

16. The method according to claim 14, further comprising: comparing, by the wireless device, the TMGI list with a TMGI list in a multicast and broadcast service control channel (MCCH); as well as In case the identified TMGI in the MCCH is also included in the TMGI list from the application layer or the service layer, multicast and broadcast service data is received by the wireless device based on the point-to-multipoint configuration identified by the identified TMGI in the MCCH.

17. A wireless communication method, the method comprising: receiving, by the wireless device, a network configuration to report a receive-only mode (ROM) service configuration; as well as Based on the network configuration, a ROM report associated with a ROM service being received or to be received by the wireless device is transmitted to a network node by the wireless device.

18. The method according to claim 17, wherein: The network configuration includes an indication for the wireless device to transmit a portion or the entire ROM report, wherein the wireless device transmits the first portion of the ROM report if the indication is associated with a first portion of the ROM report or if the wireless device is allowed to indicate the first portion of the ROM report to the network node, or the wireless device transmits the entire ROM report if the indication is associated with the entire ROM report or requires the wireless device to indicate the entire ROM report to the network node.

19. The method according to claim 18, wherein: The first portion of the ROM report includes a minimum ROM report set for the network node to uniquely identify the ROM service to identify an associated scheduling configuration.

20. The method according to claim 19, wherein: The first part of the ROM report includes a service identification (ID) of the ROM service and cell information associated with the cell on which the ROM service is scheduled.

21. The method according to claim 18, wherein: The complete ROM report includes: a minimum ROM report set for the network node to uniquely identify the ROM service; and scheduling information indicating UE capabilities occupied by the ROM service.

22. The method according to claim 21, wherein: The scheduling information includes at least one of: a number of ROM service configuration including subcarrier spacing; a service bandwidth; or a multicast and broadcast service radio bearer (MRB) and configuration of the MRB including header compression of the MRB.

23. The method according to claim 21, wherein: The scheduling information includes frequency priority information including a list of frequencies on which the ROM service is scheduled.

24. A wireless communication method, the method comprising: transmitting, by a wireless device to a network node, a first receive-only mode (ROM) report associated with a ROM service being received or to be received by the wireless device to report a ROM service configuration; receiving, by the wireless device, from the network node an inquiry regarding a second ROM report of the network node; as well as A second ROM report of the network node is transmitted by the wireless device to the network node.

25. The method according to claim 24, wherein: The first ROM report includes a minimum ROM report set for the network node to uniquely identify the ROM service to identify an associated scheduling configuration.

26. The method according to claim 25, wherein: The first ROM report includes a service identification (ID) of the ROM service, the service identification (ID) including a temporary mobile group identification of the ROM service, and cell information associated with a cell on which the ROM service is scheduled.

27. The method according to claim 24, wherein: The second ROM report includes scheduling information indicating UE capabilities occupied by the ROM service.

28. The method according to claim 27, wherein: The second ROM report includes at least one of: a number of ROM service configuration including subcarrier spacing; a service bandwidth; or a multicast and broadcast service radio bearer (MRB) and configuration of the MRB including header compression of the MRB.

29. The method according to claim 27, wherein: The scheduling information includes frequency priority information including a list of frequencies on which the ROM service is scheduled.

30. A wireless communication method, the method comprising: transmitting, by a wireless device to a network node, a first receive-only mode (ROM) report associated with a ROM service being received or to be received by the wireless device to report a ROM service configuration; receiving, by the wireless device, an indication for the wireless device to transmit an updated ROM report to the network node; as well as In case update reporting of the ROM report is enabled by the network, and if the ROM service configuration has been updated, an updated report is transmitted by the wireless device to the network node.

31. The method according to claim 30, wherein: The first ROM report includes a minimum ROM report set for the network node to uniquely identify the ROM service to identify an associated scheduling configuration.

32. The method of claim 30, wherein: The first ROM report and the updated ROM report include a minimum ROM report set for the network node to uniquely identify the ROM service, and scheduling information indicating UE capabilities occupied by the ROM service.

33. An apparatus for wireless communication, the apparatus comprising a processor configured to perform the method of any one of claims 1 to 32.

34. A non-transitory computer readable medium having stored thereon code which, when executed by a processor, causes the processor to implement the method of any one of claims 1 to 32.

Images