Patent Application
20240236621
This disclosure is generally directed to Multicast/Broadcast Service (MBS) configuration dissemination for improving network efficiency.
There has always been a demand for Multicast Broadcast Services (MBS) in wireless communication networks. In particular, mission critical communication services may be implemented by using MBS. Increasing network resources utilization efficiency while still being able to meet the uplink data latency requirement are desirable for supporting more users in a cell.
This disclosure relates to methods, systems, and devices for MBS configuration dissemination as well as MBS status report and feedback between base stations and terminal devices.
In some implementations, a method for receiving multicast broadcast service (MBS) by a user equipment (UE) in a wireless network is disclosed. The method may include receiving a first message comprising a first MBS configuration associated with the MBS from a first network element of the wireless network; and receiving an MBS configuration update notification from the first network element.
In some other implementations, a method for sending transmission mode switch request or MBS reception report to a first network element in a wireless network by a user equipment (UE) receiving MBS in the wireless network is disclosed. The method may include receiving a first MBS configuration associated with the MBS from a first network element of the wireless network; and in response to a predefined event occurring, sending an RRC resume message to the first network element.
In some other implementations, a method transmitting MBS by a first network element in a wireless network is disclosed. The method may include sending a first message comprising a first MBS configuration associated with the MBS to a User Equipment (UE) of the wireless network; and sending an MBS configuration update notification to the UE.
A network element and/or UE is further disclosed. The network element and/or UE includes a processor and a memory, wherein the processor is configured to read computer code from the memory to implement the method above. A computer-readable medium is further disclosed. The computer-readable medium includes instructions or a computer program which, when executed by a wireless terminal, cause the wireless terminal to carry out the method above.
The above embodiments and other aspects and alternatives of their implementations are described in greater detail in the drawings, the descriptions, and the claims below.
The following description and drawing set forth certain illustrative implementations of the disclosure in detail, which are indicative of several example manners in which the various principles of the disclosure may be carried out. The illustrated examples, however, are not exhaustive of the many possible embodiments of the disclosure. Other objects, advantages and novel features of the disclosure will be set forth in the following detailed description when considered in conjunction with the drawings.
Multicast Broadcast Services (MBS) has been provided in wireless systems to some extent. One of such examples includes mission critical communication service such as Mission Critical Push to Talk (MCPTT) over MBS. For an MCPTT service, once the uplink unicast radio bearer (typically Guaranteed Bit Rate (GBR)) is established for a group call, it stays allocated to the UE for the entire duration of the group call, whether the user ever talks or not. However, the traffic model for group call shows that the radio bearer may be actually used relatively rarely, namely only when the user has the floor. In particular, in the case of mission critical broadcast group, only one talker such as a chief officer can have the floor. As such, a lot of uplink resource may be wasted. On the other hand, there may be a large number of users joining an MCPTT session, and the number may exceed the limit a cell may be able to support. When this happens, a user may be denied of service because there is not enough uplink radio resource or access resource.
The various implementations below describes a mechanism for supporting MBS sessions for a UE in various Radio Resource Control (RRC) states: RRC connected (RRC_CONNECTED), RRC inactive (RRC_INACTIVE), and RRC idle (RRC_IDLE) state. The UE may receive MBS data even it is in RRC_INACTIVE or RRC_IDLE state. Under this mechanism, dedicated radio resources is assigned to a UE on demand. That is, the dedicated radio resources is only assigned to a UE when the UE needs to have the floor, or the UE needs to have the dedicated radio resources for some other purposes such as updating some parameters with the base station.
During an MBS session, the MBS configuration may be updated, and the update may be triggered by the base station or the UE. In this disclosure, various mechanisms are described to enable the UE to receive the updated MBS configuration, for UE in different the RRC states. For example, for a UE receiving MBS data in RRC_INACTIVE state, the UE may keep monitoring a MBS configuration update notification. Once the UE receives the notification, the UE may acquire the updated MBS configuration from a broadcast channel without RRC state transition, or the UE may transition to RRC_CONNECTED state first, then receive the updated MBS configuration.
From the perspective of radio access network (RAN), two delivery modes or methods are available for the transmission of MBS packet flows over radio:
In this disclosure, Point-to-Point (PTP) delivery mode/method may be described as PTP, and Point-to-Multipoint (PTM) delivery mode/method may be described as PTM.
The gNB 124 may further include a central unit (CU) 126 and at least one distributed unit (DU) 128. The CU and the DU may be co-located in a same location, or they may be split in different locations. The CU 126 and the DU 128 may be connected via an F1 interface. Alternatively, for an eNB which is capable of connecting to the 5G network, it may also be similarly divided into a CU and at least one DU, referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and the ng-eNB-DU may be connected via a W1 interface.
The wireless communication network 100 may also include at least one User Equipment (UE) 130. The UE 130 may be implemented as mobile or fixed communication devices which are capable of accessing the wireless communication network 100. The UE 130 may include but is not limited to mobile phones, laptop computers, tablets, personal digital assistants, wearable devices, IoT/NB-IoT devices, MTC/eMTC devices, distributed remote sensor devices, roadside assistant equipment, and desktop computers. The UE 130 may communicate with the base station through Over the Air (OTA) radio communication interface and resources. As shown in
The wireless communication network 100 may be implemented as, for example, a 2G, 3G, 4G/LTE, or 5G cellular communication network. Correspondingly, the base stations 122 and 124 may be implemented as a 2G base station, a 3G NodeB, an LTE eNB, or a 5G NR gNB (even though, the base station 122 is labeled as an eNB and the base station 124 is labeled as gNB for illustration purposes).
While the description below focuses on cellular wireless communication systems as shown in
Step 1. UE receives the first configuration from the network. The first configuration may include the initial MBS configuration for the UE. The MBS configuration enables the UE to receive the MBS data in RRC_CONNECTED, RRC_IDLE, or RRC_INACTIVE state. Optionally the MBS configuration may include the configuration on how UE monitors and receives the MBS configuration update. The first MBS configuration may be included in an RRC Release signaling.
Step 2. UE receives the MBS data from the network.
Step 3. UE is triggered by a predefined event. There may be multiple predefined triggering events. The predefined triggering event may be a notification from the network (e.g., base station). For example, the event may be that the UE receives an MBS configuration update notification indicating there is an updated MBS configuration for the UE to receive. The event may further include other types of events. For example, the event may be that the UE receives an MBS configuration update notification indicating that the MBS is about to be stopped or suspended, UE might release or suspend the existing MBS configuration and stop monitoring the transmission of the MBS data. For example, the event may be that the UE detects its MBS reception quality falls below a predefined threshold.
Step 4. UE network interaction. After the detection of a triggering event, UE may be triggered to perform further UE and network (e.g., base station) interaction based on the triggering event. For example, UE may be triggered to receive the updated MBS configuration from the broadcast control channel (or may be referred to as broadcast signaling); or UE may request its RRC state transition to RRC_CONNECTED state to receive the updated MBS configuration in dedicated signaling; or UE may be triggered to report MBS related information such as MBS reception report to the network, so the network may make corresponding MBS configuration update on the MBS session.
For a UE participating an MBS, a first MBS configuration may be provided to the UE by the base station. The MBS configuration may be updated from time to time, for example, due to a change of network resource availability. The UE needs to update to the latest MBS configuration whenever an update happens in order to receive uninterrupted service. The UE may participate in multiple MBSs. In this case, the UE may have an MBS configuration corresponding to each of the MBSs.
The MBS configuration (the first MBS configuration, or the updated MBS configuration) includes following parameters:
The time domain information in this disclosure comprises the radio frame information and/or sub-frame information, which may further include the period and offset information of the radio frame and the sub-frame, respectively, or a combination of them.
The frequency domain information in this disclosure comprised the bandwidth part (BWP), and/or the frequency range information.
A packet loss rate in this disclosure may be defined as: in a time window T, the ratio between the number of lost packets and the total number of received packets. One packet corresponds to one PDCP Service Data Unit (SDU) or PDCP Protocol Data Unit (PDU). The total number of received PDCP packets may be defined as: during the time window T, the difference between the highest received PDCP packet Serial Number (SN) and the lowest received PDCP packet SN. The number of lost PDCP packets may be defined as: during the time window T, the number of PDCP packet that are lost between the highest PDCP packet SN and the lowest PDCP packet SN. The time window T may be a pre-configured time duration. A packet may belong to one specific radio bearer; a subset of the radio bearers of one specific MBS session; all the radio bearers of one specific MBS session; or all the radio bearers of all the MBS session that the UE is associated with. Therefore, the packet loss rate may be defined with different granularities, such as per radio bearer, per MBS, or per UE. In some embodiments, based on the granularity, the packet loss rate may be associated with an identifier (ID) of a radio bearer and/or an MB S identifier (ID). The ratio may be further quantified into an integer (e.g., by multiplying with a predefined number and taking a floor or ceiling operation).
The error rate may be a Block Error Rate (BLER). The BLER may be computed over a measurement period, as the ratio between the number of received transport blocks resulting in Cyclic Redundancy Check (CRC) errors and the total number of received transport blocks of a specific MBS or MBS session. In some embodiments, the calculation may be performed for all the related Hybrid Automatic Repeat Request (HARQ) processes that are associated with the MBS service. The measurement period may be a configured time duration. The error rate may be a rate that is computed based on the number of errors of downlink initial transport blocks over the total number of downlink initial transport blocks. The error rate may have a granularity associated with a Modulation and Coding Scheme (MCS). For example, the error rate only takes into account of the transport blocks that use the same MCS. For another example, the error rate may have a granularity of the MBS to account for all MCSs associated with the MBS. The error rate may be further quantified into an integer (e.g., by multiplying with a predefined number and taking a floor or ceiling operation).
The MBS configuration may be updated due to various reasons and there are multiple types of MBS configuration update, which are listed below:
In some scenarios, the term of suspend is used interchangeably with deactivate. In some scenarios, the term of resume is used interchangeably with activate.
Event Triggered from UE
In some scenarios, the predefined event may be triggered by the UE based on the first MBS configuration. For example, when the UE detects its MBS reception quality is below a predefined threshold, the predefined threshold may be carried in the MBS configuration.
Step 1: Whenever there is an MBS configuration update, the UE first needs to get notified that there is an update. Based on the type of the MBS configuration update, the UE performs the corresponding action:
Step 2: This step in optional and involves UE and network interaction. For certain kind of MBS configuration update, for example, in the case the MBS configuration is about to be modified, the UE needs to receive the updated MBS configuration. There are two options for the UE to receive the updated MBS configuration:
In this disclosure, various methods for the UE to receive the notification on the MBS configuration update are described. Various methods for the UE to further receive the updated MBS configuration are also described.
Various methods for the UE to receive the MBS configuration update notification are described in detail below.
In some implementations, the notification is sent in a broadcast channel. The notification may apply to a single MBS service or an MBS service group including multiple MBSs. The UE that are associated or interested in a certain MBS may monitor the broadcast channel for the notification based on notification configuration, the notification configuration includes at least one of: time domain information such as a notification cycle, radio frame information, sub-frame information, or on duration timer for the MBS configuration update notification. The base station may send the MBS configuration update notification in a notification cycle whenever there is an MBS configuration update. The notification cycle may be defined by radio frame. For example, the notification cycle may contain 64, 128, or 256 radio frames. Within each notification cycle, there may be a radio frame carrying the MBS configuration update notification. The notification configuration also includes information for this radio frame. For example, the radio frame may be defined by an offset from the start of each notification cycle. Optionally, the MBS configuration update notification may be defined as MBS specific, and different notification scheduling information may apply to different MBSs. For a UE that is associated with more than one MBS, the UE monitors the MBS configuration update notification for each MBS. In some implementations, transmissions of the MBS configuration update notification may be associated with a predefined Radio Network Temporary Identifier (RNTI). The RNTI may be a cell level identifier. In this case, the MBS configuration update notification applies to all the MBSs transmitted by the cell. The RNTI may also be associated with an MBS group. In this case, the MBS configuration update notification applies to all the MBSs in the MBS group. The RNTI may also be associated with a single MBS, for example, the RNTI may be a group-RNTI (G-RNTI). Furthermore, the RNTI may be associated with a DCI, and the DCI is associated with a data payload. The data payload may include one of an MBS identity such as G-RNTI; an MBS index; an MBS ID (e.g., TMGI) or any other kind of identifier that uniquely identifies the MBS service.
In some implementations, MBS configuration update notification may be carried in system information block (SIB), or a multicast control channel or paging message.
In another example, the notification mechanism relies on the notification transmission along with the transmission of the MBS data. There are also a few optional choices:
2.1. Layer 1 notification: For UE that are interested or associated with one specific MBS, UE receives the MBS data by monitoring the transmission of DCI identified by per MBS RNTI, e.g., G-RNTI (group RNTI). The MBS configuration update may be indicated on DCI, e.g., by using 1 bit indicating that the MBS configuration is about to be updated. There are optionally other information (e.g., additional bits) in the DCI to indicate that the MBS configuration update, for example, the MBS is about to be updated, to start, suspend, stop, or mode switching command for the corresponding MBS, as described earlier.
2.2. Medium Access Control layer Control Element (MAC CE): The MBS configuration update may be indicated in one specific MAC CE with a specific logical channel ID, which indicates that the MBS configuration is about to be updated. There are optionally other information within the same or separate MAC CE to indicate that MBS configuration update, for example, the MBS is about to be updated, to start, suspend, stop, or mode switching command for the corresponding MBS, as described earlier in this disclosure, the information in the MAC CE can be directly identified by the predefined LCID in the sub-header of the MAC CE, or optionally in the bit stream in the MAC CE.
2.3. Separate logical channel: The MBS configuration may be transmitted in one separated logical channel, and transmitted to the UE in the same method as the MBS data. The MBS configuration might be multiplexed with the MBS data, or transmitted separately. After the UE receives the MBS configuration, UE applies the configuration and receives the MBS data based on the updated MBS configuration. In this option, the MBS configuration update notification include the updated MBS configuration, so the UE gets notified about the update and receives the updated MBS configuration in one step.
Dedicated RRC signaling: The network may send the MBS configuration update notification using Dedicated RRC signaling.
After the UE receives the MBS configuration update notification, and the notification indicates there is updated MBS configuration for the UE to receive, the UE will be triggered to receive the updated MBS configuration.
In one implementation, UE is released to RRC_INACTIVE state and continues to receive the MBS service data. When the MBS configuration is about to be updated, and the UE receives the MBS configuration update notification (through a mechanism described above), UE performs the random access procedure to transit to RRC_CONNECTED state to receive the updated MBS configuration. Optionally, cause value which identify the type of MBS notification may be indicated in the RRC resume signaling.
In another implementation, after UE receives the MBS configuration update notification (e.g., for a PTM configuration update), UE checks the broadcast control channel based on broadcast control channel configuration information (e.g., time and frequency domain information) to receive the updated MBS configuration. The broadcast control channel configuration information is also referred to as a reception configuration. Optionally, if the MBS is about to be stopped or suspended, UE sends a confirmation to the network without further checking the broadcast control channel—since there is no need to do so in case of MBS session is stopped or suspended. The UE stops receiving the MBS until further notifications is received notifying the MBS service start or resume. Optionally, the UE may send a confirmation message to the base station to confirm the receipt of the MBS configuration update notification.
The reception configuration may be delivered to UE beforehand and may include:
In another implementation, after UE receives the notification of the PTM configuration update, UE checks the broadcast control channel based on the reception configuration (time and frequency domain information) to receive the updated MBS configuration as in step 4 in the general procedure. In some implementations, if the MBS is about to be stopped or suspended, UE sends the confirmation about the notification without checking the broadcast control channel (since there is no need to do so, as UE stops receiving the MBS until notifications on the service start or resume is received later).
In another example, after UE successfully receives the updated MBS configuration on the broadcast control channel, UE sends feedback to the network, to confirm the MBS configuration update. The confirmation may be sent using 3 kinds of signaling messages:
After the UE has been notified about the MBS configuration update, UE takes action based on the type of the MBS configuration.
For MBS service start, UE might establish the bearer and start monitoring the MBS transmission in MAC/PHY layer based on the updated configuration.
For MBS service stop, UE releases the resources associated with the MBS, including the bearer configuration and stop monitoring the transmission in MAC/PHY layer.
For MBS service suspend, UE suspend the allocated resources associated with the MBS, including the bearer configuration, and stop monitoring the transmission in MAC/PHY layer.
For MBS service resume, UE resume the MBS configuration associated with the MBS, including resume the bearer configuration, and resume the monitoring of the transmission in MAC/PHY layer.
In this embodiment, UE is released to RRC_INACTIVE state and UE continues to receive the MBS service data. When the MBS configuration is about to be updated, UE needs to be notified by the network about such update to continue the reception of the MBS data with updated MBS configuration. The UE may use the notification mechanism 1, notification mechanism 2.1, 2.2, and 2.3, to receive the MBS configuration update notification.
After the UE received the MBS configuration update notification that the MBS configuration is about to be updated, UE will then performs the random access procedure to transition to RRC_CONNECTED state to receive the updated MBS configuration, in which UE may use the RRC Resume cause value to inform the network about the reasons why the UE initiating the RRC state transitioning.
In this embodiment, the UE is in RRC_CONNECTED state and the MBS configuration or part of the MBS configuration is transmitted in the broadcast control channel. The network may utilize a dedicated signaling as described in notification mechanism 3 to notify the UE about the MBS configuration update. Alternatively, the network may also use notification mechanism 2.1 and 2.2 to serve the same purpose. The updated MBS configuration may include: PTM configuration update, MBS service is about to start, stop, suspend or resume.
The reception configuration, including scheduling information on time domain and frequency domain, may be delivered to the UE beforehand and may include:
The UE then receives the updated MBS configuration based on the reception configuration.
Referring to
After UE1 successfully receives the updated MBS configuration, UE1 sends a feedback to the network to indicate or confirm that the new MBS configuration has been received, or the new MBS configuration has been deployed.
In this embodiment, the UE may be in RRC_IDLE or RRC_INACTIVE state but was previously in RRC_CONNECTED state. The UE may be configured with the broadcast control channel scheduling information, also referred to as a reception configuration. And the UE may be configured with the notification configuration. Referring to
The reception configuration may include:
The reception configuration may have different level of granularity and it may be per MBS group, per MBS, or per UE. For example, the modification period may be per MBS, which means each MBS is associated with its own specific modification period. Or the modification period may be per MBS group, which means all the MBSs in the MBS group are associated with the same modification period. For another example, if the reception configuration is per UE, then the UE receives the updated MBS configuration based on the same reception configuration for all the MBSs that the UE participates.
The UE receives updated MBS configuration in a cyclic repetition period. In particular, the UE may locate the specific sub-frame carrying the updated MBS configuration based on the sub-frame information as configured in the reception configuration. Similar to the notification cycle described earlier, the modification cycle may also be define by radio frames. If the UE is associated with more than one MBS service, UE receives updated MBS configuration for each of the MBS according to the reception configuration.
The repetition period is a time period within the modification period, within which the same updated MBS configuration may be re-transmitted according to the re-transmission number. For example, if the re-transmission number is 5, then the same updated MBS configuration may be re-transmitted for 5 times based on the repetition period, to obtain a more reliable data transmission. As such, the UE may receive updated MBS configuration from the broadcast channel multiple times in case previous reception fails. In some implementations, the re-transmission number and the repetition period may or may not be the same for each MBS.
Layer 1 notification ID in the notification configuration is a physical layer Radio Network Temporary Identifier (RNTI), which is used by the UE to monitor the notification of MBS update. The layer 1 notification ID may be per MBS, which means for each MBS, such ID is different. In this case, the UE monitors updated MBS configuration for each MBS independently. The layer 1 notification ID may be per MBS group, which means for each MBS group, such ID is different. The layer 1 notification ID may be per cell, which means for the same cell, such ID is the same or predefined.
Layer 1 ID in the reception configuration is a physical layer Radio Network Temporary Identifier (RNTI), which is used by the UE to monitor the MBS configuration transmission in the broadcast control channel. The layer 1 ID may be per MBS, which means for each MBS, such ID is different. In this case, the UE monitors updated MBS configuration for each MBS independently. The layer 1 ID may be per MBS group, which means for each MBS group, such ID is different. The layer 1 ID may be per cell, which means for the same cell, such ID is the same or predefined.
Refer to
For example, for UE2, D-RRC2 includes following information:
For UE3, D-RRC3 includes following information:
M2 and M3 are different. UE2 and UE3 monitor the MBS configuration update notification based on their corresponding notification configuration. For MBS2, it has higher requirement on the control plane latency compared with MBS3, therefore the modification period for MBS2 on UE2 is shorter than the modification period for MBS3 on UE3. As shown in
UE2 and UE3 receive updated MBS configuration based on their corresponding reception configuration. Furthermore, if the updated MBS configuration in the broadcast control channel is transmitted with repetition, after UE2 and UE3 receive the MBS configuration update notification, UE 2 and UE3 may keep receiving the updated MBS configuration based on the repetition period and re-transmission number, and based on the sub-frame information.
In some implementations, the Layer 1 ID, RNTI, and the Layer 1 notification ID may be the same or different in the dedicated signaling sent to UE2 and UE3. For example, if one specific UE is interested in both MBS2 and MBS3, and the RNTIs associated with MBS2 and MBS3 are different, then the UE needs to monitor both notification and receive updated MBS configuration from the broadcast control channels independently based on the notification and reception configuration, as the notification and reception configuration may have different scheduling information for MBS2 and MBS3.
In some implementations, the notification cycle in the notification configuration may or may not be the same as the modification cycle in the reception configuration.
The MBS configuration includes the bearer configuration associated with the MBS service. UE establishes the radio bearers according to the received MBS configuration. The MBS configuration may further include the resource allocation information of the MBS service.
In one example, as shown in
For certain part of the MBS configuration that is common to all the UEs receiving the MBS data, it may be carried in the dedicated signaling or Broadcast control channel; for certain part of the MBS configuration that is specific to a certain UE, the MBS configuration may be sent through dedicated signaling message to the UE. For example, if the radio bearer ID space is per MBS, it is common to all UE who are interested in the MBS. If the radio bearer ID space if per UE, it is specific to one UE and may be sent to UE in a dedicated signaling.
The MBS configuration or part of the MBS configuration may be sent to the UE in an RRC Release signaling message (e.g., in
The MBS configuration may include:
The RBID may be per UE or per MBS.
If the RBID is per UE, it means that the radio bearer associated with the MBS can be identified within the scope of one specific UE. The configuration of RBID may be delivered to UE in dedicated RRC signaling.
If the RBID is per MBS, it means the radio bearer associated with the MBS may be identified within the scope of one specific MBS. The configuration of RBID can be delivered to UE through dedicated signaling or broadcast control channel. In the dedicated signaling, the radio bearer may be identified by the RBID and is in the scope of one specific MBS.
For radio bearers associated with the MBS, there may be two different logical channels or RLC entities serving the same radio bearer. In an MBS session, UE receives the MBS data from either the point to multi-point (PTM) type RLC entity (or the first RLC entity/logical channel) or the point to point (PTP) type RLC entity (second RLC entity or logical channel), based on the configuration from network. The two different logical channels or RLC entities may be associated with the same RBID if both RLC entities are configured to the same UE.
If the UE receives MBS in PTM transmission mode (or PTM mode), the LCID of the PTM type RLC entity or logical channel may be per UE per cell group, or per MBS.
If the LCID is per UE per cell group, it means the logical channel is identified within the scope of one specific UE and its associated cell group. The configuration of LCID may be delivered to the UE in dedicated RRC signaling. In the configuration, there are two LCIDs (LCID1 and LCID2) associated with the PTM type RLC entity or logical channel. Whenever UE receives MAC PDU in which there are MAC Service Data Unit (SDU) identified by LCID1, the MAC SDU is submitted to the RLC entity or logical entity identified by LCID2 in the receiving UE. That is, the mapping from LCID to LCID2 instructs the UE how to deliver the MAC SDU to the corresponding RLC entity.
For example, as shown in
If the LCID is per MBS, it means the logical channel is identified by the UE within the scope of one specific MBS, or the logical channel needs to be identified in a specific name space associated with the MBS. For example, a same LCID8 may be used for both MBS1 and MBS2, and it may be read as MBS1 plus LCID8, or MBS2 plus LCID2 for the UE to identify the logical channels if UE is interested in both MBS1 and MBS2. The configuration of LCID may be delivered to UE in dedicated RRC signaling or in the broadcast channel. There is one LCID associated with the PTM type RLC entity or logical channel for one specific MBS. Whenever UE receives MAC PDU in the MBS data transmission identified by a group or MBS specific G-RNTI, based on the association of the G-RNTI and MBS service, the MAC SDU is submitted to the specific RLC entity or logical channel associated with the MBS based on the LCID in the MAC PDU sub-header.
The LCID of the PTP type (or the second) RLC entity or logical channel may be per UE per cell group, or per MBS.
If the LCID is per UE per cell group, it means the logical channel is identified within the scope of one specific UE and its associated cell group. The configuration of LCID may be delivered to the UE in dedicated RRC signaling.
If the LCID is per MBS, it means the logical channel is identified within the scope of one specific MBS. The configuration of LCID may be delivered to the UE in dedicated RRC signaling or broadcast control channel. For PTP transmission identified by UE specific physical layer ID, e.g., C-RNTI (cell RNTI), the related MAC SDU shall be submitted to the logical channel or RLC entity identified by the per MBS LCID. Therefore, the MBS information may be included in the DCI identified by C-RNTI of the UE, or in the sub-header of the MAC subPDU associated with the corresponding MBS and the logical channel. The MBS information includes MBS identity that may be used by the UE to identify the MBS service, e.g., MBS index configured to the UE, or MBS session ID, or TMGI.
For example, referring to
In some implementations, UE is configured with the PTM configuration for an MBS before the UE is released to RRC_INACTIVE state. The UE receives the MBS data based on the received PTM configuration. UE is further configured with the events definition as defined earlier in the MBS configuration in which thresholds or timer might be defined. When the predefined thresholds is reached or the enabled timer expires periodically, UE triggers the RRC resume procedure.
For example, UE is configured with the condition when to initiate the RRC resume to transition to RRC_CONNECTED state. A parameter of threshold value may be configured on the UE as defined in the first or updated MBS configuration. The parameter may reflect the MBS reception quality. When the reception quality is below the configured threshold, UE initiates the RRC state transition procedure, to resume to RRC_CONNECTED state to request the MBS mode switching from PTM to PTP. The mode switching request may be carried in the uplink information in different options:
For another example, UE is configured with the reception status report of one MBS or a list of MBSs UE is associated with. The UE is configured with the report period or report timer, and in each report period or the enabled timer periodically expires, UE reports the reception status in RRC Resume request message. UE initiates the RRC state transition procedure periodically based on the configured report period. The reception status report may be carried in the uplink information in different options:
As a response, the network may release the UE after the reception status report is received successfully or resume the RRC connection for other reasons.
Optionally, the network may be able to disable or enable the report during an MBS session.
The description and accompanying drawings above provide specific example embodiments and implementations. The described subject matter may, however, be embodied in a variety of different forms and, therefore, covered or claimed subject matter is intended to be construed as not being limited to any example embodiments set forth herein. A reasonably broad scope for claimed or covered subject matter is intended. Among other things, for example, subject matter may be embodied as methods, devices, components, systems, or non-transitory computer-readable media for storing computer codes. Accordingly, embodiments may, for example, take the form of hardware, software, firmware, storage media or any combination thereof. For example, the method embodiments described above may be implemented by components, devices, or systems including memory and processors by executing computer codes stored in the memory.
Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment/implementation” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment/implementation” as used herein does not necessarily refer to a different embodiment. It is intended, for example, that claimed subject matter includes combinations of example embodiments in whole or in part.
In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and”, “or”, or “and/or,” as used herein may include a variety of meanings that may depend at least in part on the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a,” “an,” or “the,” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.
Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present solution should be or are included in any single implementation thereof. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of the features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.
Furthermore, the described features, advantages and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. One of ordinary skill in the relevant art will recognize, in light of the description herein, that the present solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.
| Number | Date | Country | |
|---|---|---|---|
| 20240137732 A1 | Apr 2024 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2020/122776 | Oct 2022 | WO |
| Child | 18305071 | US |
