Methods, apparatuses, and computer program products for wireless communication

Abstract

A method of wireless communication is disclosed. The method includes receiving, by a wireless communication device, a message from a wireless communication node, where the message includes an indication indicating continuity of a multicast radio bearer (MRB) packet data convergence protocol (PDCP) entity associated with a multicast session to which the wireless communication device is joined.

Description

Technical Field

[0001] This document generally deals with wireless communication, and in particular with 5G or 6G communication. Background Technology

[0002] New Radio (NR) Multicast and Broadcast Service (MBS) enables the simultaneous and efficient delivery of data to multiple users, enhancing the ability to stream content and provide real-time updates. With its ability to reach a broad audience, NR MBS promises to transform how people consume media, receive emergency alerts, and access information, ensuring a seamless and dynamic broadcast experience for users worldwide. However, service continuity for MBS remains a topic of discussion. Summary of the Invention

[0003] This document relates to methods, systems, and computer program products for wireless communication.

[0004] One aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: receiving a message from a wireless communication node by a wireless communication device, wherein the message includes an indication for indicating continuity of a Multicast Radio Bearers (MRBs) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session joined by the wireless communication device.

[0005] Various embodiments may preferably implement the following features: Preferably, in response to an indication that indicates the continuity of PDCP entities, the PDCP variables corresponding to the PDCP entities are not initialized.

[0006] Preferably, the message enables at least one of the following: releasing the RadioLink Control (RLC) entity associated with the PDCP entity, or establishing the RLC entity based on a Point to Multi-Point (PTM) configuration.

[0007] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: a wireless communication device receiving a point-to-multipoint (PTM) configuration from a wireless communication node, wherein, based on at least one of an MRB configuration or a lower-level configuration of the PTM configuration, the message indicates to the wireless communication device a continuation of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session to which the wireless communication device has joined.

[0008] Various embodiments may preferably implement the following features: Preferably, in response to an indication that PDCP entities are continuous, the PDCP variables corresponding to the PDCP entities are not initialized.

[0009] Preferably, the PTM configuration message is received by the wireless communication device in an RRRCRelease message or a Multicast Broadcast Service called MBS Control Channel (MCCH) message.

[0010] Preferably, in response to a PTM configuration that does not include an MRB configuration and a PTM configuration that includes a lower-level configuration, the message indicates that PDCP entities are continuous.

[0011] Preferably, in response to the PTM configuration including the MRB configuration, the PDCP entity is initialized based on the MRB configuration.

[0012] Preferably, the message enables at least one of the following: releasing the Radio Link Control (RLC) entity associated with the PDCP entity, or establishing an RLC entity based on the PTM configuration.

[0013] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: receiving a point-to-multipoint (PTM) configuration from a wireless communication node by a wireless communication device, wherein an MRB configuration based on the received PTM configuration is compared with a previously received MRB configuration, the message allowing the wireless communication device to determine the continuity of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session joined by the wireless communication device.

[0014] Various embodiments may preferably implement the following features: Preferably, the message includes an RRRCRelease message or an MBS control channel (MCCH) message.

[0015] Preferably, the previously received MRB configuration is included in an RRCReconfiguration message, an RRCRelease message, or an MCCH message.

[0016] Preferably, in response to the continuity of PDCP entities, the PDCP variables corresponding to the PDCP entities are not initialized.

[0017] Preferably, when the MRB configuration of the received PTM configuration is different from the previously received MRB configuration, the wireless communication device applies the MRB configuration of the received PTM configuration to initialize the PDCP entity.

[0018] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: in response to instructing a PDCP entity to be continuous to an inactive wireless communication device, transmitting an RLC Service Data Unit (SDU) from the RLC entity to the PDCP entity based on an existing association between the wireless link control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

[0019] Various embodiments may preferably implement the following features: Preferably, the wireless communication method according to any one of claims 23 to 36 indicates to the wireless communication device that the PDCP entity is continuous.

[0020] Preferably, the existing association configuration between the RLC entity and the PDCP entity is in the RRCReconfiguration message.

[0021] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: receiving, by a first unit, an indication from a second unit for enabling inactive reception in multicast reception, wherein the first unit is indicated that multicast transmission is stopped or multicast transmission is in progress.

[0022] Various embodiments may preferably implement the following features: Preferably, the first unit receives a point-to-multipoint (PTM) configuration request to be transmitted to the wireless communication device from the second unit.

[0023] Preferably, in response to the PTM configuration request from the second unit, the first unit transmits the PTM configuration to the second unit.

[0024] Preferably, the first unit transmits an indication to the second unit that it does not support the PTM configuration distribution function.

[0025] Preferably, in response to a PTM configuration update, the first unit transmits the PTM configuration to the second unit.

[0026] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: transmitting a message from a wireless communication node to a wireless communication device, wherein the message includes an indication for indicating continuity of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session joined by the wireless communication device.

[0027] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: a wireless communication node transmitting a point-to-multipoint (PTM) configuration in a message to a wireless communication device, wherein, based on at least one of an MRB configuration or a lower-level configuration of the PTM configuration, the message indicates to the wireless communication device a continuation of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session to which the wireless communication device has joined.

[0028] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: a wireless communication node transmitting a point-to-multipoint (PTM) configuration in a message to a wireless communication device, wherein an MRB configuration based on the received PTM configuration is compared with a previously received MRB configuration, the message allowing the wireless communication device to determine the continuity of Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entities associated with a multicast session to which the wireless communication device has joined.

[0029] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: in response to instructing a PDCP entity to be continuous to a wireless communication device in an inactive state, the PDCP entity receiving an RLC Service Data Unit (SDU) from the RLC entity based on an existing association between the wireless link control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

[0030] Another aspect of this disclosure relates to a wireless communication method. In an embodiment, the wireless communication method includes: a second unit transmitting an indication to a first unit for enabling inactive reception in multicast reception, wherein the second unit indicates to the first unit that multicast transmission is stopped or multicast transmission is in progress.

[0031] Another aspect of this disclosure relates to a wireless communication device. In an embodiment, the wireless communication device includes a communication unit and a processor. The processor is configured to receive a message from a wireless communication node, wherein the message includes an indication for indicating continuity of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session joined by the wireless communication device.

[0032] Another aspect of this disclosure relates to a wireless communication device. In an embodiment, the wireless communication device includes a communication unit and a processor. The processor is configured to receive a point-to-multipoint (PTM) configuration from a wireless communication node, wherein the message indicates to the wireless communication device, based on at least one of an MRB configuration or a lower-level configuration of the PTM configuration, that a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity continuation associated with a multicast session to which the wireless communication device has joined.

[0033] Another aspect of this disclosure relates to a wireless communication device. In an embodiment, the wireless communication device includes a communication unit and a processor. The processor is configured to receive a point-to-multipoint (PTM) configuration from a wireless communication node, wherein an MRB configuration based on the received PTM configuration is compared with a previously received MRB configuration, the message allowing the wireless communication device to determine the continuity of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session to which the wireless communication device has joined.

[0034] Another aspect of this disclosure relates to a wireless communication device. In an embodiment, the wireless communication device includes a communication unit and a processor. The processor is configured to: in response to an instruction to a PDCP entity to continue in an inactive state of the wireless communication device, transmit RLC Service Data Units (SDUs) from the RLC entity to the PDCP entity based on an existing association between the wireless link control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

[0035] Another aspect of this disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to receive from a second unit an indication for enabling inactive reception in multicast reception, wherein a first unit is indicated that multicast transmission is stopped or multicast transmission is in progress.

[0036] Another aspect of this disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to transmit a message to a wireless communication device, wherein the message includes an indication for continuity of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session joined by the wireless communication device.

[0037] Another aspect of this disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to transmit a point-to-multipoint (PTM) configuration in a message to a wireless communication device, wherein, based on at least one of an MRB configuration or a lower-level configuration of the PTM configuration, the message indicates to the wireless communication device that a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity is continuous with respect to a multicast session to which the wireless communication device has joined.

[0038] Another aspect of this disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to transmit a point-to-multipoint (PTM) configuration in a message to a wireless communication device, wherein an MRB configuration based on a received PTM configuration is compared with a previously received MRB configuration, the message allowing the wireless communication device to determine the continuity of Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entities associated with a multicast session to which the wireless communication device has joined.

[0039] Another aspect of this disclosure relates to a wireless communication device. In an embodiment, the wireless communication device includes a communication unit and a processor. The processor is configured to: in response to indicating to the inactive wireless communication device that a PDCP entity is continuous, receive RLC Service Data Units (SDUs) from the RLC entity by the PDCP entity based on an existing association between the wireless link control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

[0040] Another aspect of this disclosure relates to a wireless communication node. In an embodiment, the wireless communication node includes a communication unit and a processor. The processor is configured to transmit an indication to a first unit for enabling inactive reception in multicast reception, wherein a second unit indicates to the first unit that multicast transmission is stopped or multicast transmission is in progress.

[0041] This disclosure relates to a computer program product comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to implement any of the preceding methods of wireless communication.

[0042] The exemplary embodiments disclosed herein are intended to provide features that will become apparent from the following description taken in conjunction with the accompanying drawings. Exemplary systems, methods, apparatus, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of illustration rather than limitation, and it will be apparent to those skilled in the art upon reading this disclosure that various modifications can be made to the disclosed embodiments that still fall within the scope of this disclosure.

[0043] Therefore, this disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order and / or hierarchy of steps in the methods disclosed herein are merely exemplary methods. The specific order or hierarchy of steps in the disclosed methods or processes may be rearranged based on design preferences while remaining within the scope of this disclosure. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this disclosure is not limited to the specific order or hierarchy presented.

[0044] The above and other aspects and their embodiments are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0045] Figure 1 A schematic diagram illustrating the mapping relationship between PDCP (Packet Data Convergence Protocol) entities and RLC (Radio Link Control) entities according to embodiments of the present disclosure is shown.

[0046] Figure 2 An example of a schematic diagram of a wireless communication device according to an embodiment of the present disclosure is shown.

[0047] Figure 3 An example of a schematic diagram of a wireless communication device according to an embodiment of the present disclosure is shown.

[0048] Figures 4 to 13 A flowchart illustrating a wireless communication method according to some embodiments of the present disclosure is shown. Detailed Implementation

[0049] 5G has introduced support for NR (New Radio) MBS (Multicast and Broadcast Services). MBS services target one or more UEs (User Equipment) within a cell and are applied to serve multiple UEs via PTM (Point-to-Multipoint) transmission, achieving high resource efficiency. During this phase, UEs can only receive MBS multicast services in the RRC_CONNECTED (Radio Resource Control Connected) state, for example, based on the configuration in the RRCReconfiguration message.

[0050] It is expected that the UE can start or continue MBS reception in the RRC_INACTIVE state to achieve optimal scalability.

[0051] To achieve better service continuity for the UE, the "PDCP (Packet Data Convergence Protocol) entity of the MRB (Multicast Radio Bearer)" or "multiple MRBs" can be kept continuous under various circumstances. For example, when the UE is released from the RRC_CONNECTED state to the RRC_INACTIVE state (e.g., when the UE transitions from the RRC_CONNECTED state to the RRC_INACTIVE state), the UE can receive the updated PTM configuration in the RRCRelease message; or when the PTM configuration is updated, the UE receives the updated PTM configuration in the multicast MCCH (MBS control channel); or when the UE returns to the RRC_CONNECTED state, it receives the new PTM configuration from dedicated signaling. The above situations can be referred to as "PDCP entity continuity of the MRB," which in this application means that PDCP variables are not initialized. In this application, the terms "PDCP continuity" or "MRB continuity" are interchangeable.

[0052] Some embodiments of this disclosure provide methods for notifying a UE of “PDCP entity continuity of MRB” in the above-described scenario, and methods for the UE to make PDCP entity continuity (i.e., specific UE behavior).

[0053] In some embodiments, from the base station's perspective, the gNB (gNodeB) can provide the UE with the PTM configuration of the MBS received in the RRC_INACTIVE state in the following two scenarios: multicast data transmission continues / is in progress, and multicast data transmission stops / is not in progress. In a separate deployment architecture of the Radio Access Network (RAN) consisting of gNB-Central Unit (gNB-CU) and gNB-Distributed Unit (gNB-DU), an F1 Application Protocol (F1AP) solution is also required to coordinate between gNB-CU and gNB-DU, thereby providing the UE that will be released to the RRC_INACTIVE state (e.g., the UE enters the RRC_INACTIVE state) with the PTM configuration that will be used in the RRCRelease message.

[0054] For a UE that has joined a multicast session, the network (e.g., gNB) can enable multicast reception in the RRC_INACTIVE state. For a UE that will be released to the RRC_INACTIVE state, the UE can receive the PTM configuration for MBS in the RRCRelease message in either of the following scenarios: In the first scenario, the multicast session is still in progress (e.g., the multicast session is active), and the UE may have already received the PTM configuration in the RRCReconfiguration message in the RRC_CONNECTED state. After the UE is released to the RRC_INACTIVE state, the UE can receive and apply the PTM configuration in the RRCRelease message until the PTM configuration is updated in the MCCH message.

[0055] In the second scenario, when the multicast session is not in progress (e.g., the multicast session is deactivated), a PTM configuration is sent to the UE to initiate MBS multicast reception in the RRC_INACTIVE state via a specific group paging indicated by the network for the corresponding MBS service.

[0056] Based on the above scenario, we can conclude that the UE can obtain the PTM configuration through the following messages: - The UE can obtain the PTM configuration from the network in the RRCReconfiguration message; - The UE can obtain another PTM configuration from the network in the RRRCRelease message; - The UE can obtain another PTM configuration from the network in the multicast MCCH broadcast in the cell; - A UE can obtain another PTM configuration (an update of the previous PTM configuration) from the network in a multicast MCCH broadcast within a cell. This cell can be the current cell or another cell after cell reselection; and - The UE can return to the RRC_CONNECTED state and obtain the updated PTM configuration from the network in the RRCReconfiguration message.

[0057] During the transition between different scenarios, different solutions can be used to send PTM configurations to the UE to ensure the continuity of the "PDCP entity of MRB" or "MRB". For example, when the UE is released from the RRC_CONNECTED state to the RRC_INACTIVE state, it receives a potentially updated PTM configuration in the RRCReconfiguration message. If the PTM configuration is updated, the UE can obtain the updated PTM configuration in the MCCH. And if the UE returns to the RRC_CONNECTED state, it can receive the updated PTM configuration from dedicated signaling (which may be the RRCReconfiguration message).

[0058] In this application, the PTM configuration may include the following information: - MRB configuration or higher / upper layer configuration, which further includes PDCP configuration and / or RadioLink Control (RLC) configuration. - Lower-layer configuration, which further includes MAC (Media Access Control) and physical layer configurations, such as DRX (Discontinuous Receive) configuration and PDCCH (Physical Downlink Control Channel) / PDSCH (Physical Data Sharing Channel) configuration, and - Additional information to guide the UE in MBS multicast reception.

[0059] Some aspects of this disclosure are provided below, but this disclosure is not limited thereto. Furthermore, unless otherwise expressly stated, the different aspects described below may be combined.

[0060] Aspect 1 - PDCP Continuity #Explicit Instructions Some embodiments of this application provide a wireless communication method for indicating the continuity of PDCP entities in the RRC_INACTIVE state. Specifically, the method includes: The wireless communication device receives a Radio Resource Control Release (RRCRelease) message. The RRCRelease message includes an indication that it is associated with a multicast session that the wireless communication device has joined, and notifies the wireless communication device that the multicast session is continuous.

[0061] In some embodiments, the UE joins a multicast session, where the network enables the UE to multicast receive in the RRC_INACTIVE state. If the UE is subsequently released into the RRC_INACTIVE state, it can receive the PTM configuration for MBS multicast in an RRCLease message. If the PTM configuration is included in the RRCLease message, an explicit indication or an indication associated with the MBS multicast session notifies the UE that the multicast session is continuous.

[0062] In some embodiments of this application, multicast session continuity may include PDCP entity continuity of MRB in multicast.

[0063] Based on this explicit indication / instruction, during the RRC Release phase, the UE continues MBS multicast reception, ensuring that the PDCP entity of the MRB in the corresponding MBS session is continuous from the RRC_CONNECTED state to the RRC_INACTIVE state. In some embodiments, the expression "PDCP entity continuity" means that the PDCP variable is not initialized.

[0064] In some embodiments of this application, the RRCrease message may additionally include RLC configuration to release and create RLC entities associated with these PDCP entities accordingly.

[0065] #Implicit indication of MRB-based configuration availability Another wireless communication method is disclosed that implicitly indicates multicast session continuity. Specifically, the method includes: The wireless communication device receives the Point-to-Multipoint (PTM) configuration message. The PTM configuration message notifies the wireless communication device of multicast session initialization or multicast session continuation. The multicast session is a session that the wireless communication device has joined. The PTM configuration includes MRB configuration or lower-level configuration.

[0066] In some embodiments of this application, the initialization / continuation of a multicast session includes the initialization / continuation of a PDCP entity or the initialization / continuation of an MRB.

[0067] Depending on whether the PTM configuration message includes MRB configuration, the UE can be instructed whether the PDCP entity is continuous or discontinuous. If the PTM configuration includes MRB configuration, the UE can apply the MRB configuration, meaning the PDCP entity can be initialized based on the MRB configuration in the PTM configuration. Conversely, if the PTM configuration message does not include MRB configuration but includes lower-level configuration, the UE can be instructed to maintain continuity of the PDCP entity from the RRC_CONNECTED state to the RRC_INACTIVE state. In this case, the PDCP variables are not initialized (because the MRB configuration does not exist).

[0068] In some embodiments of this application, the UE can receive PTM configuration messages via RRCLease messages or multicast MCCH messages. In the latter case, the UE is already in the RRC_INACTIVE state and continuously monitors the multicast MCCH to obtain any potentially updated PTM configurations within it. After receiving the PTM configuration from the RRCLease message or multicast MCCH message, the availability of the MRB configuration in the PTM configuration message can indicate to the UE that the PDCP entity remains continuous. If the MRB configuration exists in the RRCLease message or multicast MCCH message, the UE can apply that MRB configuration to initialize the PDCP entity. Conversely, if the PTM configuration message does not include the MRB configuration but includes lower-layer configurations, it indicates to the UE that the PDCP entity remains continuous from the RRC_CONNECTED state to the RRC_INACTIVE state. In this case, the PDCP variables are not initialized (because the MRB configuration is not present).

[0069] In some embodiments, implicit indications can also be determined by checking whether the PDCP configuration is available or whether it is included in the MRB configuration. If the PDCP configuration is included in the MRB configuration, the UE can apply the updated PDCP configuration, meaning that PDCP entities can be initialized based on this configuration. If the PTM configuration does not include the MRB configuration but includes a lower-layer configuration, the UE is notified of PDCP continuity, meaning that the MRB PDCP entities for the corresponding MBS session can remain continuous from the RRC_CONNECTED state to the RRC_INACTIVE state. In this case, PDCP variables are not initialized.

[0070] In some embodiments, the MRB configuration may additionally include an RLC configuration, based on which an RLC entity associated with a PDCP entity can be released and / or created.

[0071] #UE checks if MRB configuration is the same Another wireless communication method is disclosed, which indicates multicast session continuity in an alternative manner. Specifically, the method includes: The PTM configuration message is received by the wireless communication device, and The wireless communication device compares the MRB configuration included in the received PTM configuration with the previously received MRB configuration. When the MRB configuration in the received PTM configuration is the same as the previously received MRB configuration, it is determined that the multicast session joined by the wireless communication device is continuous.

[0072] In some embodiments, the UE receives the PTM configuration message from the RRRCRelease message.

[0073] Specifically, in some embodiments, the UE can check whether the MRB configuration included in the RRCReconfiguration message is the same as another MRB configuration received in the RRCReconfiguration message. In particular, as described above, the UE can receive the RRCReconfiguration message in the RRC_CONNECTED state. If the PDCP configurations in the two MRB configurations received in the RRCReconfiguration and RRCReconfiguration messages are different, the UE can apply the MRB configuration in the RRCReconfiguration message, meaning that the PDCP entity can be initialized based on the updated configuration in the RRCReconfiguration message. Conversely, if the PDCP configurations in the two MRB configurations are the same, the UE is indicated to have PDCP continuity, meaning that the PDCP entity of the corresponding MBS session's MRB can remain continuous from the RRC_CONNECTED state to the RRC_INACTIVE state. In this case, since the PDCP configurations are the same, the PDCP variables are not initialized.

[0074] In some embodiments, the UE may have already started multicast reception in the RRC_INACTIVE state based on the PTM configuration in the RRCReconfiguration, RRCLease, or MCCH messages. During this process, the MCCH and UE can be notified whenever any PTM configuration is updated. The UE can check whether the MRB configuration in the MCCH is the same as the MRB configuration previously received via the RRCReconfiguration, RRCLease, or MCCH messages. When the MRB configurations in these messages differ, the UE can apply the updated MRB configuration included in the MCCH, meaning that the PDCP entity can be initialized based on the updated MRB configuration. Conversely, when the MRB configurations in these messages are the same, PDCP continuity is indicated to the UE, meaning that the PDCP entity for the corresponding MBS session's MRB can continue. PDCP variables are not initialized.

[0075] In some embodiments, the UE may have already started multicast reception in the RRC_INACTIVE state based on the PTM configuration in the RRCReconfiguration message. Once the UE is released to the RRC_INACTIVE state, even if the MRB is not suspended (i.e., the PDCP entities of the MRB for a session are continuous), the MRB ID is retained as part of the UE context and can be used by the network in subsequent configurations, such as MRB ID changes or MRB releases based on the MRB ID in the RRCReconfiguration message before the UE is released.

[0076] In some embodiments, the UE can be notified in an RRRCRelease message that cells in the RAN notification area (RNA) are synchronized. This means that the PDCP of the session's MRB is continuous with mobility between cells in the RNA. When the UE moves from one cell to another within the RNA area, the UE may receive a PTM configuration with different lower-layer configurations, and the network ensures that the MRB configuration or PDCP configuration is the same and has the same order. For example, in cells belonging to the RNA area, the MRB list includes a list of MRBs with indices 1 to 3, each MRB having an MRB configuration (which further includes the corresponding PDCP configuration). For each cell, the PDCP configuration provided in each cell is the same and has the same order in the MRB list.

[0077] #UE User Plane Behavior A wireless communication method is disclosed to enable a UE to correctly transmit data in the uplink. The wireless communication method includes: A wireless communication device at the RRC_INACTIVE layer transmits Media Access Control Packet Data Units (MAC SDUs) to an RLC entity and a PDCP entity, wherein the wireless communication device is instructed to be continuous with the PDCP entity, and the transmission is based on the original association between the RLC entity and the PDCP entity.

[0078] In some embodiments, the indication of PDCP entity continuity for the UE can be implemented or processed based on any of the methods described above.

[0079] Specifically, once the UE begins receiving MBS in the RRC_INACTIVE state, one issue is how the UE associates the MAC SDUs (Serving Data Units) received in the MAC layer with the correct logical channel (identified by the logical channel ID or LCID) and how it associates them with the correct PDCP entity (identified by the MRB ID (Multicast Radio Bearer ID)). However, the MRB configured for the UE's RRC_INACTIVE state does not have an MRB ID. It can be assumed that the UE receives multicast sessions based on the relationship MRB ID = y, LCID = x, where (MRB ID = y, LCID = x) is configured by the network in the RRCReconfiguration message (see...). Figure 1This message can be received in the RRC_CONNECTED state. Whenever the UE receives a MAC SDU at the MAC layer (where the MAC subheader includes LCID = x), it passes the MAC SDU to the associated RLC entity based on the LCID in the MAC subheader, and then passes it to the PDCP entity identified by the corresponding MRB ID = y based on the established relationship described above. If it is necessary to maintain PDCP entity continuity based on the configuration in the RRCRelease message or MCCH message when the UE enters the RRC_INACTIVE state, the UE can pass the RLC SDU to the associated PDCP entity based on the original relationship or association between the RLC entity and the PDCP entity (rather than the association based on LCID and MRB ID).

[0080] In some embodiments of this application, the original relationship or association between the RLC entity and the PDCP entity can be configured in the RRCReconfiguration message, which can be received by the UE in the RRC_ACTIVE state.

[0081] Aspect 2 - F1AP supports PTM configuration allocation Another wireless communication method is disclosed to establish F1AP (F1 Application Protocol) support, which provides signaling services between gNB-CU and gNB-DU for the PTM configuration described in this application.

[0082] The wireless communication method includes: The first wireless communication node receives instructions from the wireless communication device, which are associated with the activation of a multicast session in the RRC_INACTIVE state. The first wireless communication node is informed of the status of the multicast transmission of the wireless communication device.

[0083] In some embodiments, the status of multicast transmission includes a multicast transmission in progress state or a multicast transmission not in progress state. For example, the gNB-CU can indicate to the gNB-DU whether the UE's multicast transmission is in progress or not.

[0084] Specifically, in the case of a separate network architecture, gNodeB is divided into gNB-CU (central unit) and gNB-DU (distributed unit). Once the network or gNB-CU decides to enable UE multicast reception in RRC_INACTIVE state, coordination between gNB-CU and gNB-DU is required so that gNB-DU can provide the lower layer of PTM configuration.

[0085] Specifically, when a multicast session is conducted in the RRC_INACTIVE state, the network can provide the UE with the PTM configuration for the corresponding multicast session in the RRCLease message. For example, the gNB-CU can indicate to the gNB-DU that such configuration (PTM configuration) is required. Based on this instruction, the gNB-DU can decide to respond with the requested PTM configuration.

[0086] Even when no multicast session is in the RRC_INACTIVE state, including situations where the multicast session is deactivated or there is temporarily no data, the network can still configure PTM configuration for the UE in the RRC_INACTIVE message. Using this pre-configured PTM configuration, the UE can begin MBS multicast reception in the RRC_INACTIVE state based on the specific group paging indicated by the network for the corresponding MBS service, until the UE receives any PTM configuration via other channels (e.g., MCCH). Such configuration in the RRC_INACTIVE message can be referred to as a pre-configuration, which establishes an inactive multicast session and is used by the UE in the RRC_INACTIVE state.

[0087] In some embodiments, the gNB-CU indicates to the gNB-DU that a multicast session is not in progress. Based on this information, the gNB-DU can stop the corresponding MBS transmission and indicate the cessation of the MBS transmission in the MCCH broadcast on the UE interface.

[0088] In some embodiments, the gNB-CU also indicates to the gNB-DU that PTM configuration is required for unused MBS sessions. Based on this instruction, the gNB-DU may decide to respond with the requested PTM configuration, or the gNB-DU may decide that the requested PTM configuration is unavailable or that the pre-configuration feature is not supported. Alternatively, the gNB-DU may be triggered to proactively provide pre-configuration to the gNB-CU upon request.

[0089] Figure 2This is a schematic diagram relating to a wireless communication device 30 according to embodiments of the present disclosure. The wireless communication device 30 may be a tag, mobile phone, laptop computer, tablet computer, e-book, or portable computer system, and is not limited thereto. The wireless communication device 30 can be used to implement the UE described in this disclosure. The wireless communication device 30 may include a processor 300 such as a microprocessor or application-specific integrated circuit (ASIC), a storage unit 310, and a communication unit 320. The storage unit 310 may be any data storage device storing program code 312, which is accessed and executed by the processor 300. Embodiments of the stored code 312 include, but are not limited to, a Subscriber Identity Module (SIM), Read-Only Memory (ROM), Flash memory, Random Access Memory (RAM), hard disk, and optical data storage devices. The communication unit 320 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) based on the processing results of the processor 300. In embodiments, the communication unit 320 transmits and receives signals via at least one antenna 322 or through wiring.

[0090] In this embodiment, storage unit 310 and program code 312 may be omitted, and processor 300 may include storage unit with stored program code.

[0091] The processor 300 may, for example, implement any of the steps in the exemplary embodiment on the wireless communication device 30 by executing program code 312.

[0092] The communication unit 320 may be a transceiver. The communication unit 320 may alternatively or additionally combine a transmitting unit and a receiving unit, which are configured to transmit signals to and receive signals from the wireless communication node, respectively.

[0093] In some embodiments, the wireless communication device 30 can be used to perform the operations of the UE described in this disclosure. In some embodiments, the processor 300 and the communication unit 320 cooperate to perform the operations described in this disclosure. For example, the processor 300 performs operations and transmits or receives signals, messages and / or information through the communication unit 320.

[0094] Figure 3This diagram relates to a wireless communication node 40 according to an embodiment of the present disclosure. The wireless communication node 40 may be a satellite, base station (BS), gNB, network entity, Domain Name System (DNS) server, Mobility Management Entity (MME), Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), Radio Access Network (RAN), Next Generation RAN (NG-RAN), data network, core network, a communication node in the core network, or Radio Network Controller (RNC), and is not limited thereto. Furthermore, the wireless communication node 40 may include (perform) at least one network function, such as Access and Mobility Management Function (AMF), Session Management Function (SMF), User Location Function (UPF), Policy Control Function (PCF), Application Function (AF), etc. The wireless communication node 40 may be used to implement the gNB, network, node in the network, gNB-CU, or gNB-DU described in this disclosure. The wireless communication node 40 may include a processor 400 such as a microprocessor or ASIC, a storage unit 410, and a communication unit 420. The storage unit 410 may be any data storage device storing program code 412, which is accessed and executed by the processor 400. Examples of storage unit 412 include, but are not limited to, SIM, ROM, flash memory, RAM, hard disk, and optical data storage devices. Communication unit 420 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) based on the processing results of processor 400. In embodiments, communication unit 420 transmits and receives signals via at least one antenna 422 or through wiring.

[0095] In this embodiment, the storage unit 410 and the program code 412 may be omitted. The processor 400 may include a storage unit containing the stored program code.

[0096] The processor 400 may, for example, implement any of the steps described in the exemplary embodiment on the wireless communication node 40 by executing program code 412.

[0097] The communication unit 420 may be a transceiver. The communication unit 420 may alternatively or additionally combine the transmitting unit and the receiving unit, which are configured to transmit signals, messages or information to the wireless communication node and receive signals, messages or information from the wireless communication node, respectively.

[0098] In some embodiments, the wireless communication node 40 can be used to perform the operations of the gNB, network, gNB-CU, or gNB-DU described in this disclosure. In some embodiments, the processor 400 and the communication unit 420 cooperate to perform the operations described in this disclosure. For example, the processor 400 performs operations and transmits or receives signals through the communication unit 420.

[0099] According to embodiments of this disclosure, a wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication device (e.g., a UE). In one embodiment, the wireless communication device can be implemented using the wireless communication device 30 described in this disclosure, but is not limited thereto.

[0100] refer to Figure 4 In an embodiment, the wireless communication method includes: receiving a message (e.g., an RRRCRelease message) from a wireless communication node by a wireless communication device, wherein the message includes an indication for indicating the continuity of Packet Data Convergence Protocol (PDCP) entities of a multicast radio bearer (MRB) associated with a multicast session joined by the wireless communication device.

[0101] For details, please refer to the paragraphs above, which will not be repeated here.

[0102] According to embodiments of this disclosure, a wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication device (e.g., a UE). In one embodiment, the wireless communication device can be implemented using the wireless communication device 30 described in this disclosure, but is not limited thereto.

[0103] refer to Figure 5 In an embodiment, the wireless communication method includes: a wireless communication device receiving a point-to-multipoint (PTM) configuration from a wireless communication node, wherein the message indicates to the wireless communication device, based on at least one of an MRB configuration or a lower-level configuration of the PTM configuration, that a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session to which the wireless communication device has joined is continuous.

[0104] For details, please refer to the paragraphs above, which will not be repeated here.

[0105] According to embodiments of this disclosure, a wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication device (e.g., a UE). In one embodiment, the wireless communication device can be implemented using the wireless communication device 30 described in this disclosure, but is not limited thereto.

[0106] refer to Figure 6 In one embodiment, the wireless communication method includes: receiving a point-to-multipoint (PTM) configuration from a wireless communication node by a wireless communication device, wherein, based on a comparison between the MRB configuration included in the received PTM configuration and a previously received MRB configuration, the message allows the wireless communication device to determine the continuity of Packet Data Convergence Protocol (PDCP) entities of the multicast radio bearer (MRB) associated with the multicast session to which the wireless communication device has joined.

[0107] For details, please refer to the paragraphs above, which will not be repeated here.

[0108] According to embodiments of this disclosure, a wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication device (e.g., a UE). In one embodiment, the wireless communication device can be implemented using the wireless communication device 30 described in this disclosure, but is not limited thereto.

[0109] refer to Figure 7 In an embodiment, the wireless communication method includes: in response to instructing a PDCP entity to be continuous to a wireless communication device in an inactive state (e.g., RRC_INACTIVE state), the RLC entity transmits an RLC Service Data Unit (SDU) to the PDCP entity based on an existing association between the wireless link control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

[0110] For details, please refer to the paragraphs above, which will not be repeated here.

[0111] According to embodiments of this disclosure, another wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication node (e.g., a gNB-DU). In one embodiment, the wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0112] refer to Figure 8 In an embodiment, the wireless communication method includes: receiving, by a first unit, an indication from a second unit for enabling inactive reception (e.g., RRC_INACTIVE reception) in multicast reception, wherein the first unit is indicated whether multicast transmission is stopped or in progress.

[0113] For details, please refer to the paragraphs above, which will not be repeated here.

[0114] According to embodiments of this disclosure, another wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication node (e.g., a gNB). In one embodiment, the wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0115] refer to Figure 9 In one embodiment, the wireless communication method includes: transmitting a message (e.g., an RRRCRelease message) from a wireless communication node to a wireless communication device, wherein the message includes an indication for indicating continuity of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session joined by the wireless communication device.

[0116] For details, please refer to the paragraphs above, which will not be repeated here.

[0117] According to embodiments of this disclosure, another wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication node (e.g., a gNB). In one embodiment, the wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0118] refer to Figure 10 In an embodiment, the wireless communication method includes: a wireless communication node transmitting a point-to-multipoint (PTM) configuration in a message to a wireless communication device, wherein, based on at least one of an MRB configuration or a lower-level configuration of the PTM configuration, the message indicates to the wireless communication device that a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity is continuous with respect to a multicast session to which the wireless communication device has joined.

[0119] For details, please refer to the paragraphs above, which will not be repeated here.

[0120] According to embodiments of this disclosure, another wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication node (e.g., a gNB). In one embodiment, the wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0121] refer to Figure 11 In one embodiment, the wireless communication method includes: a wireless communication node transmitting a point-to-multipoint (PTM) configuration in a message to a wireless communication device, wherein, based on a comparison between the MRB configuration included in the received PTM configuration and a previously received MRB configuration, the message allows the wireless communication device to determine the continuity of Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entities associated with the multicast session to which the wireless communication device has joined.

[0122] For details, please refer to the paragraphs above, which will not be repeated here.

[0123] According to embodiments of this disclosure, a wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication device (e.g., a UE). In one embodiment, the wireless communication device can be implemented using the wireless communication device 30 described in this disclosure, but is not limited thereto.

[0124] refer to Figure 12In an embodiment, the wireless communication method includes: in response to instructing a PDCP entity to be continuous to a wireless communication device in an inactive state (e.g., RRC_INACTIVE state), the PDCP entity receives an RLC Service Data Unit (SDU) from the RLC entity based on an existing association between the wireless link control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

[0125] For details, please refer to the paragraphs above, which will not be repeated here.

[0126] According to embodiments of this disclosure, another wireless communication method is also provided. In embodiments, this wireless communication method can be performed using a wireless communication node (e.g., a gNB-CU). In one embodiment, the wireless communication node can be implemented using the wireless communication node 40 described in this disclosure, but is not limited thereto.

[0127] refer to Figure 13 In one embodiment, the wireless communication method includes: a second unit transmitting an indication to a first unit for enabling inactive reception (e.g., RRC_INACTIVE reception) in multicast reception, wherein the second unit indicates to the first unit whether multicast transmission is stopped or in progress.

[0128] For details, please refer to the paragraphs above, which will not be repeated here.

[0129] In some embodiments, the wireless communication device used in this disclosure may instruct the aforementioned UE.

[0130] In some embodiments, the wireless communication node used in this disclosure may refer to the aforementioned gNB.

[0131] In some embodiments, the first unit used in this disclosure may refer to the gNB-DU described above.

[0132] In some embodiments, the second unit used in this disclosure may refer to the aforementioned gNB-CU.

[0133] In some embodiments, the term "PDCP entity continuity" as used in this disclosure can indicate the situation where the aforementioned PDCP entities remain continuous.

[0134] While various embodiments of this disclosure have been described above, it should be understood that they are presented by way of example only and not by way of limitation. Similarly, various diagrams may depict exemplary architectures or configurations provided to enable those skilled in the art to understand the exemplary features and functionality of this disclosure. However, those skilled in the art will understand that this disclosure is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, those skilled in the art will understand that one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the exemplary embodiments described above.

[0135] It should be understood that in this disclosure, the term "and / or" or the symbol " / " can include any and all combinations of one or more of the associated listed items. For example, A and / or B and / or C includes any and all combinations of one or more of A, B, and C, including A, B, C, A and B, A and C, B and C, and combinations of A, B, and C. Similarly, A / B / C includes any and all combinations of one or more of A, B, and C, including A, B, C, A and B, A and C, B and C, and combinations of A, B, and C.

[0136] It should also be understood that any reference to elements using designations such as "first," "second," etc., herein does not generally limit the number or order of these elements. Rather, these designations are used herein as a convenient means of distinguishing between two or more elements or multiple instances of a single element. Therefore, references to first and second elements do not imply that only two elements can be used, nor do they imply that the first element must somehow precede the second element.

[0137] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0138] Those skilled in the art will further understand that any of the various illustrative logic blocks, units, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code incorporating instructions (which may be referred to herein as "software" or "software unit" for convenience), or any combination of these technologies.

[0139] To clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, units, circuits, and steps have been described above, generally according to function. Whether this function is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art can implement the described functions in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure. According to various embodiments, processors, devices, components, circuits, structures, machines, units, etc., can be configured to perform one or more functions described herein. As used herein with respect to a specified operation or function, the terms "configured to" or "configured for" mean a processor, device, component, circuit, structure, machine, unit, etc., physically constructed, programmed, and / or arranged to perform a specified operation or function.

[0140] Furthermore, those skilled in the art will understand that the various exemplary logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by integrated circuits (ICs), including general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. Logic blocks, cells, and circuits may further include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein may be implemented as software stored on a computer-readable medium.

[0141] Computer-readable media include computer storage media and communication media, with communication media including any medium that enables the transfer of computer programs or code from one place to another. Storage media can be any available medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.

[0142] In this document, the term "unit" as used herein refers to software, firmware, hardware, and any combination of such elements for performing the relevant functions described herein. Furthermore, for the purposes of discussion, various units are described as discrete units; however, it will be apparent to those skilled in the art that two or more modules can be combined to form a single unit performing the relevant functions according to embodiments of this disclosure.

[0143] Additionally, in embodiments of this disclosure, memory or other storage devices and communication components may be employed. It should be understood that, for clarity, embodiments of this disclosure have been described above with reference to different functional units and processors. However, it will be apparent that any suitable functional distribution among different functional units, processing logic elements, or domains may be used without departing from this disclosure. For example, functions illustrated as being performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to suitable means for providing the described functions and do not indicate a strict logical or physical structure or organization.

[0144] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of the claims. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be endowed with the broadest scope consistent with the novel features and principles disclosed herein as set forth in the following claims.

Claims

1. A wireless communication method, comprising: A message is received from a wireless communication node by a wireless communication device, wherein the message includes an indication for indicating continuity of a Multicast Radio Bearer (MRB) Packet Data Convergence Protocol (PDCP) entity associated with a multicast session joined by the wireless communication device.

2. The wireless communication method as described in claim 1, wherein, In response to the instruction indicating the continuity of PDCP entities, the PDCP variables corresponding to the PDCP entities are not initialized.

3. The wireless communication method as described in claim 1 or 2, wherein, The message enables at least one of the following: releasing the Radio Link Control (RLC) entity associated with the PDCP entity, or establishing an RLC entity based on a Point-to-Multipoint (PTM) configuration.

4. A wireless communication method, comprising: A point-to-multipoint (PTM) configuration is received from a wireless communication node by a wireless communication device, wherein, based on at least one of the MRB configuration of the PTM configuration or the lower-level configuration of the PTM configuration, the message indicates to the wireless communication device that the multicast radio bearer MRB packet data aggregation protocol (PDCP) entity is continuous with respect to the multicast session to which the wireless communication device has joined.

5. The wireless communication method as described in claim 4, wherein, In response to an indication that PDCP entities are continuous, the PDCP variables corresponding to the PDCP entities are not initialized.

6. The wireless communication method as described in claim 4 or 5, wherein, The PTM configuration message is received by the wireless communication device in either the RRRCRelease message or the Multicast Broadcast Service Control Channel (MCCH) message.

7. The wireless communication method according to any one of claims 4 to 6, wherein, In response to the PTM configuration not including an MRB configuration and the PTM configuration including a low-level configuration, the message indicates that the PDCP entity is continuous.

8. The wireless communication method according to any one of claims 4 to 7, wherein, In response to the PTM configuration including the MRB configuration, the PDCP entity is initialized based on the MRB configuration.

9. The wireless communication method according to any one of claims 4 to 8, wherein, The message enables at least one of the following: releasing the Radio Link Control (RLC) entity associated with the PDCP entity, or establishing an RLC entity based on the PTM configuration.

10. A wireless communication method, comprising: A wireless communication device receives a message from a wireless communication node containing a point-to-multipoint (PTM) configuration, wherein the MRB configuration based on the received PTM configuration is compared with a previously received MRB configuration. The message allows the wireless communication device to determine the continuity of the multicast radio bearer MRB packet data aggregation protocol (PDCP) entities associated with the multicast session to which the wireless communication device has joined.

11. The wireless communication method as described in claim 10, wherein, The message includes the RRRCRelease message or the Multicast Broadcast Service Control Channel (MCCH) message.

12. The wireless communication method as described in claim 10 or 11, wherein, The previously received MRB configuration is included in the RRCReconfiguration message, RRCRelease message, or MCCH message.

13. The wireless communication method according to any one of claims 10 to 12, wherein, In response to the continuity of the PDCP entity, the PDCP variables corresponding to the PDCP entity are not initialized.

14. The wireless communication method according to any one of claims 10 to 13, wherein, If the MRB configuration of the received PTM configuration is different from the previously received MRB configuration, the wireless communication device applies the MRB configuration of the received PTM configuration to initialize the PDCP entity.

15. A wireless communication method, comprising: In response to instructing the PDCP entity to remain continuous to the inactive wireless communication device, the RLC entity transmits the RLC Service Data Unit (SDU) to the PDCP entity based on the existing association between the wireless link control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

16. The wireless communication method as described in claim 15, wherein, The wireless communication method according to any one of claims 1 to 14 indicates to the wireless communication device that the PDCP entity is continuous.

17. The wireless communication method as described in claim 15 or 16, wherein, The existing association configuration between the RLC entity and the PDCP entity is in the RRCReconfiguration message.

18. A wireless communication method, comprising: The first unit receives an indication from the second unit to enable inactive reception in multicast reception, wherein the first unit is indicated that multicast transmission is stopped or multicast transmission is in progress.

19. The wireless communication method as described in claim 18, wherein, The first unit receives a point-to-multipoint (PTM) configuration request to be transmitted to the wireless communication device from the second unit.

20. The wireless communication method as described in claim 18 or 19, wherein, In response to the PTM configuration request from the second unit, the first unit transmits the PTM configuration to the second unit.

21. The wireless communication method according to any one of claims 18 to 20, wherein, The first unit transmits an indication to the second unit that it does not support the PTM configuration distribution function.

22. The wireless communication method according to any one of claims 18 to 21, wherein, In response to a PTM configuration update, the first unit transmits the PTM configuration to the second unit.

23. A wireless communication method, comprising: A message is transmitted from a wireless communication node to a wireless communication device, wherein the message includes an indication that the multicast radio bearer MRB packet data aggregation protocol PDCP entity associated with the multicast session joined by the wireless communication device is continuous.

24. The wireless communication method as described in claim 23, wherein, In response to the instruction indicating the continuity of PDCP entities, the PDCP variables corresponding to the PDCP entities are not initialized.

25. The wireless communication method as described in claim 23 or 24, wherein, The message enables at least one of the following: releasing the Radio Link Control (RLC) entity associated with the PDCP entity, or establishing an RLC entity based on a Point-to-Multipoint (PTM) configuration.

26. A wireless communication method, comprising: A point-to-multipoint (PTM) configuration is transmitted from a wireless communication node to a wireless communication device in a message, wherein, based on at least one of the MRB configuration of the PTM configuration or the lower-level configuration of the PTM configuration, the message indicates to the wireless communication device that the multicast radio bearer MRB packet data aggregation protocol (PDCP) entity is continuous with the multicast session to which the wireless communication device has joined.

27. The wireless communication method as described in claim 26, wherein, In response to an indication that PDCP entities are continuous, the PDCP variables corresponding to the PDCP entities are not initialized.

28. The wireless communication method as described in claim 26 or 27, wherein, The PTM configuration message is received by the wireless communication device in either the RRRCRelease message or the Multicast Broadcast Service Control Channel (MCCH) message.

29. The wireless communication method according to any one of claims 26 to 28, wherein, In response to the PTM configuration not including an MRB configuration and the PTM configuration including a low-level configuration, the message indicates that the PDCP entity is continuous.

30. The wireless communication method according to any one of claims 26 to 29, wherein, In response to the PTM configuration including the MRB configuration, the PDCP entity is initialized based on the MRB configuration.

31. The wireless communication method according to any one of claims 26 to 30, wherein, The message enables at least one of the following: releasing the Radio Link Control (RLC) entity associated with the PDCP entity, or establishing an RLC entity based on the PTM configuration.

32. A wireless communication method, comprising: The wireless communication node transmits a point-to-multipoint (PTM) configuration message to the wireless communication device, wherein the MRB configuration based on the received PTM configuration is compared with the previously received MRB configuration. The message allows the wireless communication device to determine the continuity of the multicast radio bearer MRB packet data aggregation protocol (PDCP) entities associated with the multicast session to which the wireless communication device has joined.

33. The wireless communication method as described in claim 32, wherein, The message includes the RRRCRelease message or the Multicast Broadcast Service Control Channel (MCCH) message.

34. The wireless communication method as described in claim 32 or 33, wherein, The previously received MRB configuration is included in the RRCReconfiguration message, RRCRelease message, or MCCH message.

35. The wireless communication method according to any one of claims 32 to 34, wherein, In response to the continuity of the PDCP entity, the PDCP variables corresponding to the PDCP entity are not initialized.

36. The wireless communication method according to any one of claims 32 to 35, wherein, If the MRB configuration of the received PTM configuration is different from the previously received MRB configuration, the wireless communication device applies the MRB configuration in the received PTM configuration to initialize the PDCP entity.

37. A wireless communication method, comprising: In response to instructing the PDCP entity to remain continuous to the inactive wireless communication device, the PDCP entity receives RLC Service Data Unit (SDU) from the RLC entity based on the existing association between the wireless link control (RLC) entity and the PDCP entity of the wireless communication device.

38. The wireless communication method as described in claim 37, wherein, The wireless communication method according to any one of claims 23 to 36 indicates to the wireless communication device that the PDCP entity is continuous.

39. The wireless communication method as described in claim 37 or 38, wherein, The existing association configuration between the RLC entity and the PDCP entity is in the RRCReconfiguration message.

40. A wireless communication method, comprising: The second unit transmits an indication to the first unit for enabling inactive reception in multicast reception, wherein the second unit indicates to the first unit that multicast transmission is stopped or multicast transmission is in progress.

41. The wireless communication method as described in claim 40, wherein, The first unit receives a point-to-multipoint (PTM) configuration request to be transmitted to the wireless communication device from the second unit.

42. The wireless communication method as described in claim 40 or 41, wherein, In response to the PTM configuration request from the second unit, the first unit transmits the PTM configuration to the second unit.

43. The wireless communication method according to any one of claims 40 to 42, wherein, The first unit transmits an indication to the second unit that it does not support the PTM configuration distribution function.

44. The wireless communication method according to any one of claims 40 to 43, wherein in response to a PTM configuration update, the first unit transmits the PTM configuration to the second unit.

45. A wireless communication device, comprising: Communication unit; and The processor is configured to receive a message from a wireless communication node, wherein the message includes an indication for indicating continuity of a multicast radio bearer (MRB) packet data aggregation protocol (PDCP) entity associated with a multicast session joined by the wireless communication device.

46. ​​The wireless communication device as claimed in claim 45, wherein, The processor is also configured to perform the wireless communication method as described in claim 2 or 3.

47. A wireless communication device, comprising: Communication unit; and The processor is configured to receive a point-to-multipoint (PTM) configuration from a wireless communication node, wherein, based on at least one of an MRB configuration or a lower-level configuration of the PTM configuration, the message indicates to the wireless communication device a continuation of a multicast radio bearer MRB packet data convergence protocol (PDCP) entity associated with a multicast session to which the wireless communication device has joined.

48. The wireless communication device of claim 47, wherein, The processor is also configured to perform the wireless communication method as described in any one of claims 5 to 9.

49. A wireless communication device, comprising: Communication unit; and The processor is configured to receive a point-to-multipoint (PTM) configuration from a wireless communication node, wherein the MRB configuration based on the received PTM configuration is compared with a previously received MRB configuration, and the message allows the wireless communication device to determine the continuity of the multicast radio bearer MRB packet data convergence protocol (PDCP) entities associated with the multicast session to which the wireless communication device has joined.

50. The wireless communication device as claimed in claim 49, wherein, The processor is also configured to perform the wireless communication method as described in any one of claims 11 to 14.

51. A wireless communication device, comprising: Communication unit; and The processor is configured to: in response to instructing the PDCP entity to continue in an inactive wireless communication device, transmit RLC Service Data Unit (SDU) from the RLC entity to the PDCP entity based on the existing association between the Radio Link Control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

52. The wireless communication device as claimed in claim 51, wherein, The processor is also configured to perform the wireless communication method as described in claim 16 or 17.

53. A wireless communication node, comprising: Communication unit; and The processor is configured to receive from the second unit an indication for enabling inactive reception in multicast reception, wherein the first unit is indicated that multicast transmission is stopped or multicast transmission is in progress.

54. The wireless communication node according to claim 53, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 19 to 22.

55. A wireless communication node, comprising: Communication unit; and A processor is configured to transmit a message to a wireless communication device, wherein the message includes an indication for indicating a continuity of a multicast radio bearer (MRB) packet data convergence protocol (PDCP) entity associated with a multicast session to which the wireless communication device has joined.

56. The wireless communication node as claimed in claim 55, wherein, The processor is also configured to perform the wireless communication method as described in claim 24 or 25.

57. A wireless communication node, comprising: Communication unit; and The processor is configured to: transmit a point-to-multipoint (PTM) configuration in a message to a wireless communication device, wherein, based on at least one of an MRB configuration or a lower-level configuration of the PTM configuration, the message indicates to the wireless communication device that a multicast radio bearer MRB packet data convergence protocol (PDCP) entity is continuous with respect to a multicast session to which the wireless communication device has joined.

58. The wireless communication node according to claim 57, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 27 to 31.

59. A wireless communication node, comprising: Communication unit; and The processor is configured to transmit a point-to-multipoint (PTM) configuration in a message to the wireless communication device, wherein the MRB configuration based on the received PTM configuration is compared with a previously received MRB configuration, and the message allows the wireless communication device to determine the continuity of the multicast radio bearer MRB packet data convergence protocol (PDCP) entities associated with the multicast session to which the wireless communication device has joined.

60. The wireless communication node according to claim 59, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 33 to 36.

61. A wireless communication device, comprising: Communication unit; and The processor is configured to: in response to instructing the PDCP entity to continue in an inactive wireless communication device, receive RLC Service Data Unit (SDU) from the RLC entity by the PDCP entity based on the existing association between the Radio Link Control (RLC) entity of the wireless communication device and the PDCP entity of the wireless communication device.

62. The wireless communication device as claimed in claim 61, wherein, The processor is also configured to perform the wireless communication method as described in claim 38 or 39.

63. A wireless communication node, comprising: Communication unit; and The processor is configured to transmit an indication to a first unit for enabling inactive reception in multicast reception, wherein the second unit indicates to the first unit that multicast transmission is stopped or multicast transmission is in progress.

64. The wireless communication node according to claim 63, wherein, The processor is also configured to perform the wireless communication method according to any one of claims 41 to 44.

65. A computer program product comprising computer-readable program medium code stored thereon, which, when executed by a processor, causes the processor to perform the method as described in any one of claims 1 to 44.

Images