User equipment mobility for multicast and broadcast services
By using HO and CHO mechanisms in mobile radio telecommunications systems, the UE enters an idle/inactive state to receive multicast and broadcast services in the target cell, solving the problems of resource waste and delay in the prior art and improving link stability and energy efficiency.
Patent Information
- Application Number
- CN202380032630.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-04
- Filing Date
- 2023-03-06
- Publication Date
- 2024-11-15
AI Technical Summary
The existing multicast and broadcast service (MBS) frameworks have resource waste, delay and energy consumption problems in mobile radio telecommunications systems, especially when the UE switches from the source cell to the target cell, additional signaling and RRC state transitions are required. Causes link failure and handover failure.
By using the HO request and CHO mechanism in the RRC_CONNECTED state, the UE can enter an idle/inactive state in the target cell, use DM-2 mode to receive multicast and broadcast service sessions, reduce signaling overhead and optimize the switching process.
It realizes efficient reception of multicast and broadcast services in the target cell, reduces signaling overhead and delay, improves link stability and energy efficiency, and reduces the risk of mobile-triggered radio link failure and handover failure.
Smart Images

Figure CN118975395A_ABST
Abstract
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 327,208, filed on April 4, 2022. The entire contents of that prior-filed application are incorporated herein by reference. Technical Field
[0002] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) New Radio (NR) access technology, or above 5G, or other communication systems. For example, certain example embodiments may relate to apparatus, systems and / or methods for user equipment (UE) mobility for multicast and broadcast services (MBS). Background Art
[0003] Examples of mobile or wireless telecommunication systems may include Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), Advanced LTE (LTE-A), MulteFire, LTE-A Pro and / or fifth generation (5G) wireless access technology or new radio (NR) access technology. The fifth generation (5G) wireless system refers to the next generation (NG) radio system and network architecture. 5G network technology is mainly based on new radio (NR) technology, but 5G (or NG) networks can also be built on E-UTRAN radio. It is estimated that NR will provide bit rates of about 10-20Gbit / s or higher, and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low latency communications (URLLC) and massive machine type communications (mMTC). NR is expected to provide extreme broadband and ultra-robust, low latency connectivity and large-scale networking to support the Internet of Things (IoT). Summary of the invention
[0004] Some example embodiments may be directed to a method. The method may include receiving a multicast and broadcast service session via point-to-point transmission or point-to-multipoint transmission with an established radio resource control connection with a source network element. The method may also include receiving a radio resource control message indicating information of a target network element. The method may also include releasing the radio resource control connection and entering a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the method may include selecting a target cell based on information received in the radio resource control message. Further, the method may include performing radio communication with the target cell. In addition, the method may include receiving the multicast and broadcast service session in the target cell in an inactive state or an idle state.
[0005] Other example embodiments may relate to an apparatus. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may also be configured, together with the at least one processor, to cause the apparatus to at least: receive a multicast and broadcast service session via point-to-point transmission or point-to-multipoint transmission in the case of an established radio resource control connection with a source network element. The apparatus may also be caused to receive a radio resource control message indicating target network element information. The apparatus may also be caused to release the radio resource control connection and enter a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the apparatus may also be caused to select a target cell based on information received in the radio resource control message. In addition, the apparatus may also be caused to perform radio communication with the target cell. In addition, the apparatus may also be caused to receive a multicast and broadcast service session in the target cell in an inactive state or an idle state.
[0006] Other example embodiments may relate to an apparatus. The apparatus may include a component for receiving a multicast and broadcast service session via point-to-point transmission or point-to-multipoint transmission in the case of an established radio resource control connection with a source network element. The apparatus may also include a component for receiving a radio resource control message indicating information of a target network element. The apparatus may also include a component for releasing the radio resource control connection and entering a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the apparatus may include a component for selecting a target cell based on information received in the radio resource control message. Further, the apparatus may include a component for performing radio communication with the target cell. In addition, the apparatus may include a component for receiving a multicast and broadcast service session in the target cell in an inactive state or an idle state.
[0007] According to other example embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may include receiving a multicast and broadcast service session via a point-to-point transmission or a point-to-multipoint transmission with an established radio resource control connection with a source network element. The method may also include receiving a radio resource control message indicating target network element information. The method may also include releasing the radio resource control connection and entering a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the method may include selecting a target cell based on information received in the radio resource control message. Further, the method may include performing radio communications with the target cell. In addition, the method may include receiving the multicast and broadcast service session in an inactive state or an idle state in the target cell.
[0008] Other example embodiments may relate to a computer program product for performing a method. The method may include receiving a multicast and broadcast service session via a point-to-point transmission or a point-to-multipoint transmission with an established radio resource control connection with a source network element. The method may also include receiving a radio resource control message indicating information of a target network element. The method may also include releasing the radio resource control connection and entering a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the method may include selecting a target cell based on information received in the radio resource control message. Further, the method may include performing radio communication with the target cell. In addition, the method may include receiving the multicast and broadcast service session in an inactive state or an idle state in the target cell.
[0009] Other example embodiments may relate to an apparatus that may include a circuit configured to receive a multicast and broadcast service session via point-to-point transmission or point-to-multipoint transmission with an established radio resource control connection with a source network element. The apparatus may also include a circuit configured to receive a radio resource control message indicating information of a target network element. The apparatus may also include a circuit configured to release the radio resource control connection and enter a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the apparatus may include a circuit configured to select a target cell based on information received in the radio resource control message. Further, the apparatus may include a circuit configured to perform radio communication with the target cell. In addition, the apparatus may include a circuit configured to receive a multicast and broadcast service session in the target cell in an inactive state or an idle state.
[0010] Certain example embodiments may be directed to a method. The method may include transmitting a handover request message to a target network element. The method may also include receiving a handover request response message including network communication information. The method may also include transmitting a radio resource control message indicating target network element information to a user equipment.
[0011] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured, with the at least one processor, to cause the apparatus to at least: transmit a handover request message to a target network element. The apparatus may also be caused to receive a handover request response message including network communication information. The apparatus may also be caused to transmit a radio resource control message indicating target network element information to a user equipment.
[0012] Other example embodiments may be directed to an apparatus. The apparatus may include means for transmitting a handover request message to a target network element. The apparatus may also include means for receiving a handover request response message including network communication information. The apparatus may also include means for transmitting a radio resource control message indicating target network element information to a user equipment.
[0013] According to other example embodiments, a non-transitory computer readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may include transmitting a handover request message to a target network element. The method may also include receiving a handover request response message including network communication information. The method may also include transmitting a radio resource control message indicating target network element information to a user equipment.
[0014] Other example embodiments may be directed to a computer program product for performing a method. The method may include transmitting a handover request message to a target network element. The method may also include receiving a handover request response message including network communication information. The method may also include transmitting a radio resource control message indicating target network element information to a user equipment.
[0015] Other example embodiments may be directed to an apparatus that may include circuitry configured to transmit a handover request message to a target network element. The apparatus may also include circuitry configured to receive a handover request response message including network communication information. The apparatus may also include circuitry configured to transmit a radio resource control message indicating target network element information to a user equipment.
[0016] Certain example embodiments may be directed to a method. The method may include receiving a handover request message from a source network element. The method may also include, in response to the handover request message, transmitting a handover request response message including network communication information to the source network element. The method may also include transmitting, using point-to-multipoint transmission, multicast and broadcast service session information to a user equipment in a radio resource control idle state or inactive state.
[0017] Other example embodiments may be directed to an apparatus. The apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code may be configured to, together with the at least one processor, cause the apparatus to at least: receive a handover request message from a source network element. The apparatus may also be caused to transmit a handover request response message including network communication information to the source network element in response to the handover request message. The apparatus may also be caused to transmit multicast and broadcast service session information to a user equipment in a radio resource control idle state or an inactive state using point-to-multipoint transmission.
[0018] Other example embodiments may be directed to an apparatus. The apparatus may include a component for receiving a handover request message from a source network element. The apparatus may also include a component for transmitting a handover request response message including network communication information to the source network element in response to the handover request message. The apparatus may also include a component for transmitting multicast and broadcast service session information to a user equipment in a radio resource control idle state or an inactive state using point-to-multipoint transmission.
[0019] According to other example embodiments, a non-transitory computer readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may include receiving a handover request message from a source network element. The method may also include transmitting a handover request response message including network communication information to the source network element in response to the handover request message. The method may also include transmitting multicast and broadcast service session information to a user equipment in a radio resource control idle state or an inactive state using point-to-multipoint transmission.
[0020] Other example embodiments may be directed to a computer program product for performing a method. The method may include receiving a handover request message from a source network element. The method may also include, in response to the handover request message, transmitting a handover request response message including network communication information to the source network element. The method may also include transmitting, using point-to-multipoint transmission, multicast and broadcast service session information to a user equipment in a radio resource control idle state or inactive state.
[0021] Other example embodiments may be directed to an apparatus that may include circuitry configured to receive a handover request message from a source network element. The apparatus may also include circuitry configured to transmit, in response to the handover request message, a handover request response message including network communication information to the source network element. The apparatus may also include circuitry configured to transmit, using point-to-multipoint transmission, multicast and broadcast service session information to a user equipment in a radio resource control idle state or inactive state. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] For a proper understanding of the example embodiments, reference should be made to the accompanying drawings, in which:
[0023] Figure 1 An exemplary architecture of protocol layers for Delivery Mode 1 (DM-1) is shown.
[0024] Figure 2 An exemplary architecture of the protocol layers for Delivery Mode 2 (DM-2) is shown.
[0025] Figure 3 An exemplary signal flow for a conditional switch (CHO) is shown.
[0026] Figure 4An exemplary signal diagram of an exemplary problem scenario is shown.
[0027] Figure 5 An example signal diagram with baseline switching (HO) is shown in accordance with certain example embodiments.
[0028] Figure 6 An example signal diagram with conditional switching (CHO) is shown in accordance with certain example embodiments.
[0029] Figure 7 Another example signal diagram with a baseline HO is shown in accordance with certain example embodiments.
[0030] Figure 8 Another example signal diagram with CHO is shown, in accordance with certain example embodiments.
[0031] Fig. 9 An example signal diagram based on configuration update between gNBs without HO is shown in accordance with certain example embodiments.
[0032] Fig.10 An exemplary flow chart of a method according to certain example embodiments is shown.
[0033] Fig.11 An example flow chart illustrating another method according to certain example embodiments.
[0034] Fig.12 An exemplary flow chart illustrating a further method according to certain example embodiments is shown.
[0035] Fig.13 A set of apparatuses according to certain example embodiments is shown. DETAILED DESCRIPTION
[0036] It will be readily appreciated that the components of certain example embodiments as generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. The following is a detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for user equipment (UE) mobility for multicast and broadcast systems.
[0037] The features, structures, or characteristics of the example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the use of the phrases "certain embodiments," "example embodiments," "some embodiments," or other similar language throughout this specification refers to the fact that a particular feature, structure, or characteristic described in conjunction with an embodiment may be included in at least one embodiment. Therefore, the phrases "certain embodiments," "example embodiments," "in some embodiments," "in other embodiments," or other similar language appearing throughout this specification do not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. In addition, the terms "cell," "node," "gNB," or other similar language may be used interchangeably throughout this specification. In addition, the term "gNB" may be an example of a "node."
[0038] The 3rd Generation Partnership Project (3GPP) supports multicast and broadcast services (MBS). According to 3GPP, point-to-multipoint (PTM) transmission can effectively supply MBS to multiple users by using the same radio framework as unicast transmission. UEs in the RRC CONNECTED state can receive delivery mode 1 (i.e., multicast), and UEs in all RRC_states can receive delivery mode 2 (i.e., broadcast). Delivery mode 1 (DM-1) can provide transport blocks (TBs) to UEs in a PTM or point-to-point (PTP) manner. In some examples, hybrid automatic repeat request (HARQ) feedback can be used for link adaptation in DM-1, while delivery mode 2 (DM-2) can provide transport blocks (TBs) in a PTM manner without HARQ feedback.
[0039] Figure 1 shows an exemplary architecture of the protocol layers for DM-1, and Figure 2 An exemplary architecture of the protocol layers for DM-2 is shown. In some cases, the terms "multicast" and "broadcast" may have different meanings from the core network and radio access network (RAN) perspectives. In certain example embodiments, the term "broadcast" may relate to transmissions performed in DM-2, while "multicast" may relate to transmissions performed in DM-1 (i.e., from the RAN perspective). On the other hand, from the core network perspective, multicast may be a service for which the UE sends a join request, while broadcast may be a service for which the UE does not send any join request. Certain example embodiments described herein may utilize multicast from the core network perspective.
[0040] According to 3GPP, conditional handover (CHO) may be introduced to minimize radio link failure (RLF) and handover failure (HOF) caused by timing issues and mobility-triggered cell changes. Figure 3An exemplary signal diagram of CHO is shown. At 300, the UE may send a measurement report to the source node. At 305, the source node may make a CHO decision based on the measurement report. At 310 and 315, the source node may send a CHO request to the target node and other potential target nodes, respectively. At 320 and 325, the target node and other potential target nodes may perform an admission control process in response to the request. At 330 and 335, the target node and other potential target nodes may send a CHO request confirmation message to the source node. In response, at 340, the source node may send a radio resource control reconfiguration to the UE. At 345, the UE may evaluate the CHO condition. At 350, user data may be exchanged between the UE and the source node. Further, at 355, the UE may determine that the target node satisfies the CHO condition and stops Tx / Rx to / from the source node.
[0041] Furthermore, if Figure 3 As shown, at 360, the UE may send a physical random access channel (PRACH) preamble to the target node. At 365, the target node may send a random access channel (RACH) response to the UE. After receiving the RACH response, at 370, the UE may send an RRC reconfiguration complete (RRC ReconfigurationComplete) message to the target node. At 375, the target node may send a handover (HO) success message to the source node, indicating that the handover from the source node to the target node is successful. At 380, the source node may stop Tx / Rx to / from the UE and start forwarding data to the target node. At 385, the source node may send an SN Status Transfer (SN Status Transfer) message to the target node, and at 390, start forwarding data to the target node. At 395, the source node may cancel the CHO at other potential target nodes. At 397, a path switching process may be performed between the source node and the target node (i.e., the node receiving the RRC reconfiguration complete message), a session management function (SMF), a serving gateway (S-GW) / user plane function (UPF), and a mobility management entity (MME) / access management function (AMF). Figure 3 For each protocol data unit (PDU) session, the AMF may transparently transmit a path switch request transmission information element (IE) to the SMF associated with the relevant PDU session.
[0042] Existing MBS frameworks may encounter certain challenges, including, for example, wasting resources (i.e., signaling overhead) because some additional dedicated signaling may be required between the target cell and the UE for handover and RRC state transition. In addition, unnecessary delays and energy consumption may also be introduced. Such challenges may arise when a UE receives a multicast session in the RRC_CONNECTED state that can be served using PTP or PTM (DM-1) in the source cell. Here, it can be assumed that such a UE is handed over to the target cell using a handover (HO) procedure. If the target cell decides to use DM-2 to provide multicast session services for UEs in the RRC_IDLE / INACTIVE state (i.e., in the case where there is an ongoing DM-2 for the multicast session in the target), the target cell may send another RRC message (e.g., RRC release message) to the UE after the HO is completed to change its state from RRC_CONNECTED to RRC_IDLE / RRC_INACTIVE, and the UE initially starts in the RRC_CONNECTED state.
[0043] Figure 4 An exemplary signal diagram of an exemplary problem scenario is shown. At 400, the UE may be in an RRC connection with a source cell. At 405, the UE may receive an MBS session using PTP. At 410, the UE may send L3 measurements on the target cell to the source gNB. In response, at 415, the source gNB may send a HO request to the target gNB, and at 420, the target gNB may send a HO request acknowledgment (ACK) to the source gNB. At 425, the source gNB may send a HO command to the UE, and at 430, the UE may execute the HO command. Once the HO command is executed, at 435, the UE may connect to the target cell. At 440, the target gNB may decide to provide MBS services to the UE via broadcast. At 445, the target gNB may send an RRC release message to the UE, after which the UE releases the RRC connection with the target cell. At 450, the UE may be in idle mode, and at 455, the UE may select a target cell. While in the idle or inactive state, at 460, the UE may receive MBS services from the target cell.
[0044] As discussed herein, certain example embodiments may provide solutions for addressing the problems and challenges in the existing MBS framework as described above. For example, when both the target gNB and the source gNB support 3GPP Rel-18, when sending a (C-)HO request to the target gNB, the source gNB may instruct the UE to receive MBS session services using an MBS radio bearer (MRB) in the RRC_CONNECTED state. The MRB may be configured with only a PTP branch, only a PTM branch, or both a PTP and a PTM branch. In its response, the target gNB may indicate that for this session, it will use DM-2 in the idle / inactive state.
[0045] According to certain example embodiments, in a baseline HO scenario, the target gNB may send the above information (i.e., an indication of the source gNB that the UE is receiving MBS sessions using MRBs in the RRC_CONNECTED state) with a HO Request Preparation Failure message. In response, the source gNB may release the UE's RRC connection and may indicate a target frequency and / or target cell ID (and more information provided by the target in the HO Request Preparation Failure message for receiving DM-2 transmissions for the MBS session). Thus, the HO Request Preparation Failure message may indicate one or more candidate target cell IDs, and more information provided by each cell or set of cells (i.e., MBS configuration for DM-2), and upon receiving the RRC Release message, the UE may receive the MBS session in the RRC Idle / Inactive state. In other example embodiments, when the HO is CHO, the target gNB may reply with a HO Request Acknowledgement (ACK) message and include in the RRC Reconfiguration message a command to enter the Idle / Inactive state after the condition is performed. In some other embodiments, the target gNB may reply with a HO Request Acknowledgement (ACK) message and include in the RRC Release message a command to enter the Idle / Inactive state after the condition is performed. In addition, the HO Request Confirm message may include information for receiving the broadcast service.
[0046] In certain example embodiments, when the source gNB supports 3GPP Rel-17 and the target gNB supports 3GPP Rel-18, the mechanism may be transparent to the source gNB. As such, the source gNB may not indicate to the target gNB in the HO Request message that the UE is at the source gNB in RRC_CONNECTED state, e.g., using DM-1 for an MBS session. Instead, the target gNB may infer from the provided MBS information that the UE is at the source gNB using DM-1 for an MBS session. In other example embodiments, the target gNB may reply with a HO Request ACK message that may include an RRC Reconfiguration message that includes a command to enter the IDLE / INACTIVE state (after performing the conditions in the CHO scenario). In other example embodiments, the target gNB may reply with a HO Request ACK message that may include an RRC Release message that includes a command to enter the IDLE / INACTIVE state (after performing the conditions in the CHO scenario). The HO Request ACK message may also include additional information to receive the MBS session.
[0047] According to certain example embodiments, in CHO, when both the target and source gNB support 3GPP Rel-18, and in baseline HO, when the source gNB supports 3GPP Rel-17 and the target gNB supports 3GPP Rel-18, a core network change may be required when the UE is to be directed to the RRC Idle state. Specifically, at the end of the HO process, the target gNB may not have the UE context, the signaling connection to the AMF, and the N3 transport. Therefore, the target gNB may behave as if it has accepted the HO and may send an indication of HO to Idle to the AMF in a PATH SWITCH REQUEST message. In this example embodiment, when the indication of HO to Idle is received, the AMF knows that there is no signaling connection and no new N3 tunnel is to be established. In addition, the AMF may transmit a PATH SWITCH REQUEST message or a portion thereof including information indicating the HO to Idle to the SMF. The SMF may be prompted to release the N3 tunnel used with the source gNB.
[0048] According to other example embodiments, in CHO, when both the target and source gNBs support 3GPP Rel-18, and when the gNB supports 3GPP Rel-17 and the target gNB supports 3GPP Rel-18, the target gNB may not know whether the UE has performed CHO configuration. As a result, the target gNB cannot know when to send a UE context release message to the source gNB. Therefore, the RRC reconfiguration sent by the target gNB and forwarded to the UE via the source gNB may include dedicated resources (e.g., dedicated RACH preamble). As a result, after the UE starts receiving broadcast services from the target cell in an idle / inactive state, the UE can utilize the dedicated resources. Upon receiving this transmission, the target gNB may transmit a UE context release message to the source gNB. This may be in a HO success message.
[0049] In certain example embodiments, alternatives to the above solutions may be provided. For example, in contrast to the above solutions, certain example embodiments may focus on solutions that do not involve a HO request to the target gNB. Instead, the gNB may exchange information about its serving cells with neighboring gNBs that provide MBS sessions. Based on the information received from the neighboring gNBs, if the source gNB decides to handover the UE to one of the neighboring gNBs that provided this information, the source gNB may not perform the HO, but instead release the UE to an idle / inactive state and provide the necessary configuration to receive the MBS session in one or more cells of the target gNB.
[0050] Figure 5 An example signal diagram with a baseline HO is shown in accordance with certain example embodiments. At 500, the UE may be in an RRC connection with a source cell. At 505, the UE may receive an MBS session using DM-1 over PTP and / or PTM (i.e., an MBS radio bearer (MRB) with only a PTP branch, only a PTM branch, or both a PTP and a PTM branch). At 510, the UE may obtain an L3 measurement of the target cell and send it to the source gNB, indicating that the quality of the target cell (e.g., reference signal received power or reference signal received quality) is better than the quality of the serving cell. At 515, the source gNB may send a handover request message to the target gNB. In accordance with certain example embodiments, the handover request message may indicate via a flag that the UE is receiving an MBS session using DM-1. At 520, in response to the handover request message, the target gNB may reply to the source gNB with a handover request preparation failure message. According to certain example embodiments, the handover request preparation failure message may indicate in at least one of the Xn Application Protocol (XnAP) cause values or the new XnAP information element that the MBS session in the target cell is served using DM-2 and / or an MBS configuration for DM-2 at the target cell (e.g., an MBS PTM traffic channel (MTCH) configuration).
[0051] At 525, the source gNB may send an RRC release message with redirection information including the target frequency and / or target cell ID, and the MBS configuration at the target cell. Upon receipt of the message, the RRC release message may release or suspend the RRC connection. At 530, the UE may release its RRC connection and enter an idle / inactive state. The UE may also select a target cell based on the redirection information in the RRC release message received from the source gNB. At 535, the UE may receive an MBS session via broadcast in the target cell using the MBS information received in the RRC release message. For example, in certain example embodiments, the UE may receive an MBS session from the target cell using DM-2 in an idle state.
[0052] Figure 6 An example signal diagram with CHO is shown in accordance with certain example embodiments. At 600, the UE may be in an RRC connection with a source cell. At 605, the UE may receive an MBS session over PTP and / or PTM (i.e., MRB) utilizing DM-1. At 610, the UE may obtain an L3 measurement of the target cell and send it to the source gNB, indicating that the quality of the target cell (e.g., reference signal received power or reference signal received quality) is better than the quality of the serving cell. At 615, the source gNB may send a CHO request message to the target gNB. In accordance with certain example embodiments, the CHO request message may indicate via a flag or an XnAP information element that the UE is receiving an MBS session utilizing DM-1. At 620, the target gNB may reply with a HO request ACK message. In accordance with certain example embodiments, the HO request ACK message may include an idle / inactive command for the UE to enter an idle / inactive state after conditional execution and an MBS configuration (e.g., MTCH configuration) at the target cell. The HO Request ACK message may also include additional resources, such as a RACH preamble or a RACH opportunity, dedicated for the UE to signal to the target gNB that the UE has applied the CHO configuration.
[0053] At 625, the source gNB may send an RRC reconfiguration message with redirection information including the target frequency and / or target cell ID, and the MBS configuration and dedicated RACH preamble at the target cell. At 630, the UE may evaluate the CHO condition. At 635, when the CHO condition is met, the UE may apply the configuration. After the condition is met, the UE may enter an idle state and apply the redirection information to select a target cell. At 640, the UE may apply the MBS information received in the RRC reconfiguration message to receive the MBS session via broadcast in the target cell. For example, in certain example embodiments, the UE may receive the MBS session from the target cell using DM-2 in idle mode. At 645, the UE may perform radio transmissions on dedicated resources (e.g., RACH preamble). Thereafter, at 650, the gNB may send a path switch request to the AMF. According to certain example embodiments, the path switch request may include information indicating the HO to an idle / inactive state. In this way, there is no need to establish a signaling connection and a new tunnel. In addition, the AMF may transmit a Path Switch Request message or a portion thereof including information indicating HO to IDLE to the SMF. The SMF may be caused to release the tunnel (N3 tunnel) used with the source gNB. According to some example embodiments, operations 640 and 645 may be performed in reverse order. At 660, the target gNB may send a UE Context Release, which may be an XnAP HO Success message, to the source gNB.
[0054] Figure 7Another example signal diagram with baseline HO is shown in accordance with certain example embodiments. At 700, the UE may be in an RRC connection with a source cell. At 705, the UE may receive an MBS session using DM-1 over PTP and / or PTM (i.e., MRB). At 710, the UE may obtain an L3 measurement of the target cell and send it to the source gNB, indicating that the quality of the target cell (e.g., reference signal received power or reference signal received quality) is better than the quality of the serving cell. Further, at 715, the source gNB may send a HO request message to the target gNB. At 720, the target gNB may reply with a HO request ACK message. In accordance with certain example embodiments, the HO request ACK message may include an RRC reconfiguration including a command to put the UE into an idle / inactive state, a configuration required to select a target cell, and a configuration to receive an MBS session in the target cell using DM-2. At 725, the source gNB may forward the RRC reconfiguration to the UE. In accordance with certain example embodiments, the RRC reconfiguration may include an idle / inactive command and an MBS configuration received from the target gNB. At 730, the UE may release its RRC connection and enter an idle / inactive state. The UE may also select a target cell based on information in the RRC reconfiguration message received from the source gNB.
[0055] At 735, the target gNB may send a path switch request message to the AMF. According to certain example embodiments, the path switch request message may include information indicating the HO to idle state. Therefore, no signaling connection needs to be established and no new tunnel needs to be established. In addition, the AMF may transmit the path switch request message or a portion thereof including the information indicating the HO to idle to the SMF. The SMF may be prompted to release the N3 tunnel used with the source gNB. At 740, the target gNB may send a UE context release to the source gNB, notifying the source gNB that the HO was successful. At 745, the UE may select a target cell based on the information received in the RRC reconfiguration message. According to certain example embodiments, the UE may receive an MBS session via broadcast in the target cell using the MBS information received in the RRC reconfiguration message. For example, in certain example embodiments, the UE may receive an MBS from the target cell using DM-2 in idle mode.
[0056] Figure 8Another example signal diagram with CHO is shown in accordance with certain example embodiments. At 800, the UE may be in an RRC connection with a source cell. At 805, the UE may receive an MBS session over PTP and / or PTM (i.e., MRB) utilizing DM-1. At 810, the UE may send an L3 measurement of the target cell to the source gNB indicating that the quality (e.g., reference signal received power or reference signal received quality) of the target cell is better than the quality of the serving cell. At 815, the source gNB may send a CHO request message to the target gNB. At 820, the target gNB may reply with a HO request ACK message. In accordance with certain example embodiments, the HO request ACK message may include: an idle / inactive command for the UE to enter an idle / inactive state after conditional execution and an MBS configuration (e.g., MTCH configuration) at the target cell. The HO request ACK message may also include additional resources, such as including a RACH preamble or a RACH opportunity, dedicated for the UE to signal the target gNB that the UE has applied the CHO configuration.
[0057] At 825, the source gNB may send an RRC reconfiguration message with redirection information including one or more of: a target cell ID and / or a target frequency, and an MBS configuration and a dedicated RACH preamble at the target cell. In certain example embodiments, when there is more than one target cell ID, the MBS configuration and RACH preamble may be provided for each cell or set of cells. At 830, the UE may evaluate a CHO condition. At 835, when the CHO condition is met, the UE may apply the configuration. After the condition is met, the UE may enter an idle state and apply the redirection information to select a target cell. At 840, the UE may use the MBS information received in the RRC reconfiguration message to receive an MBS session via a broadcast in the target cell. For example, in certain example embodiments, the UE may receive an MBS session from the target cell using DM-2 in an idle state. At 845, the UE may perform a radio transmission on a dedicated resource (e.g., a RACH preamble). At 850, the gNB may send a path switch request to the AMF. According to certain example embodiments, the path switch request may include information indicating the HO to idle / inactive state. In this way, there is no need to establish a signaling connection and a new tunnel. In addition, the AMF may transmit a path switch request message or a portion thereof including the information indicating the HO to idle to the SMF. The SMF may be caused to release the N3 tunnel used with the source gNB. According to some example embodiments, operations 840 and 845 may be performed in reverse order. At 855, the target gNB may send a UE context release to the source gNB, which may be an XnAP HO success message.
[0058] Fig. 9An example signal diagram based on a configuration update between gNBs without HO is shown according to certain example embodiments. According to other example embodiments, the solution may not involve a HO request to the target gNB. For example, it may not be necessary to request a HO for each UE that moves to a cell that provides an MBS session to a UE in an idle / inactive state. Instead, the gNBs may exchange information about their serving cells in advance. In certain example embodiments, the information may include information for each cell and may include at least an identification of the MBS session (MBS session ID) and whether the session is being served to a UE in an idle / inactive state. In other example embodiments, the gNBs may exchange configuration information (e.g., MTCH configuration) required to receive a multicast session in an idle / inactive state.
[0059] At 900, the source gNB and the target gNB may exchange information. In some example embodiments, the information exchange between the source and target gNBs may be performed using XnAP Setup / Response, XnAP NG-RAN Node Configuration Update / Update ACK, etc. In some example embodiments, the information may be related to the serving cell, including each serving cell / beam and each MBS session. For example, the information may include a session identifier (e.g., MBS session ID), information about whether the MBS session is delivered to a UE in an idle / inactive state, and / or an RRC configuration for a UE in an idle / inactive state in the cell.
[0060] At 905, the UE may be in an RRC connection with a source cell. At 910, the UE may connect to the network and join a multicast MBS session. For example, the source gNB may configure the UE to receive the multicast MBS session using PTP / PTM (DM-1) in the RRC_CONNECTED state. At 915, the UE may send an L3 measurement of the target cell to the source gNB indicating that the quality (e.g., reference signal received power or reference signal received quality) of the target cell is better than the quality of the serving cell. At 920, based on information previously received from the target gNB, the source gNB may decide to perform mobility to the target gNB using an RRC connection release, which releases the UE to an idle / inactive state.
[0061] At 925, the source gNB may send an RRC release message to the UE indicating one or more target cells that the UE should attempt to reselect. If the source gNB receives an MBS configuration for the cell for the UE in an idle / inactive state from the target gNB, this information may be provided to the UE. In doing so, the time that the UE is able to receive a multicast MBS session in the target cell may be minimized because the UE may not be required to acquire a system information block (e.g., SIBx) and / or a multicast control channel (MCCH) in the target cell prior to receiving the corresponding MTCH. At 925, the UE may release the RRC connection, and at 930, the UE may perform cell reselection towards the target cell indicated in operation 925. At 935, the UE may receive a multicast MBS session (MBS service) from the target cell in an idle / inactive state.
[0062] Fig.10 An exemplary flow chart of a method according to certain exemplary embodiments is shown. In an exemplary embodiment, Fig.10 The method may be performed by a network entity or a group of multiple network elements in a 3GPP system (such as LTE or 5G-NR). For example, in an example embodiment, Fig.10 The method can be similar to Fig.13 The UE or device of one of the apparatuses 10 or 20 shown in FIG. 1 is executed.
[0063] According to certain example embodiments, Fig.10 The method may include, at 1000, receiving a multicast and broadcast service session via point-to-point transmission or point-to-multipoint transmission with an established radio resource control connection with a source network element. The method may also include, at 1005, receiving a radio resource control message indicating information of a target network element. The method may also include, at 1010, releasing the radio resource control connection and entering a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the method may include, at 1015, selecting a target cell based on information received in the radio resource control message. Further, the method may include, at 1020, performing radio communication with the target cell. In addition, the method may include, at 1025, receiving an MBS session in a radio resource control idle state or an inactive state.
[0064] According to certain example embodiments, the radio resource control message may be a radio resource control reconfiguration message or a radio resource control release message. According to further example embodiments, the target network element information may include one or more of: a target cell frequency, a target cell identifier, and a multicast and broadcast service session configuration at the target cell. According to some example embodiments, the target network element information may include an idle state command at the target cell, and a multicast and broadcast service session configuration. According to further example embodiments, the target network element information may also include a dedicated random access channel resource.
[0065] In certain example embodiments, the method may further include receiving a point-to-multipoint transmission of a multicast and broadcast service session in a target cell using a multicast and broadcast service session configuration in an idle state or an inactive state. In some example embodiments, the radio communication is performed on dedicated resources. In other example embodiments, the dedicated resource may be a radio access channel preamble.
[0066] Fig.11 An example of a flow chart of another method according to certain example embodiments is shown. In an example embodiment, Fig.11 The method may be performed by a network entity or a group of multiple network elements in a 3GPP system (such as LTE or 5G-NR). For example, in an example embodiment, Fig.11 The method can be similar to Fig.13 The network or gNB of one of the devices 10 or 20 shown in FIG. 1 is executed.
[0067] According to certain example embodiments, Fig.11 The method may include: at 1100, transmitting a handover request message to a target network element. The method may also include: at 1105, receiving a handover request response message including network communication information. The method may also include: at 1110, transmitting a radio resource control message indicating target network element information to a user equipment.
[0068] According to some example embodiments, the handover request message includes a flag indicating that the user equipment is receiving a point-to-point and / or point-to-multipoint transmission of a multicast and broadcast service session in a radio resource control connected state. According to some example embodiments, the handover request response may be a handover request preparation failure message. According to other example embodiments, the network communication information includes at least one of the following: an indication that the multicast and broadcast service session in the target cell is used to serve a user equipment in an idle or inactive delivery state using point-to-multipoint transmission, and a multicast and broadcast service session configuration. In other example embodiments, the radio resource control message may be a radio resource control release message. In some example embodiments, the handover request response may be a handover request confirmation message. In some example embodiments, the handover request confirmation message may include at least one of the following: a command to cause the user equipment to enter a radio resource control idle state or an inactive state, a multicast and broadcast service session configuration, and a dedicated random access channel resource. In further example embodiments, the radio resource control message may be a radio resource control reconfiguration message or a radio resource control release message. In other example embodiments, the handover request response may be an Xn application protocol handover request confirmation message. In a further example embodiment, the network communication information may include a command for the user equipment to enter a radio resource control idle state or an inactive state, and a multicast and broadcast service session configuration at a target cell.
[0069] According to certain example embodiments, the target network element information may include a target cell frequency, a target cell identifier, and a multicast and broadcast service session configuration at the target cell. According to other example embodiments, the target network element information may include a dedicated random access channel resource. In some example embodiments, the target network element information may include one or more of: a command to enter a radio resource control idle state or an inactive state, a multicast and broadcast service session configuration at the target cell, and a dedicated random access channel resource. In further example embodiments, the method may further include receiving a context release message from the target network element or receiving a HO success message from the target network element.
[0070] Fig.12 An example of a flow chart of another method according to certain example embodiments is shown. In an example embodiment, Fig.12 The method may be performed by a network entity or a group of multiple network elements in a 3GPP system such as LTE or 5G-NR. For example, in an example embodiment, Fig.12 The method can be similar to Fig.13 The network or gNB of one of the devices 10 or 20 shown is executed.
[0071] According to certain example embodiments, Fig.12The method may include: receiving a handover request message from a source network element at 1200. The method may also include: transmitting a handover request response message including network communication information to the source network element in response to the handover request message at 1205. The method may also include: transmitting multicast and broadcast service session information to a user equipment in a radio resource control idle state or inactive state using point-to-multipoint transmission at 1210.
[0072] According to certain example embodiments, the method may further include sending a path switch request to a network element, the path switch request including information indicating that the user equipment is switched to an idle state. According to other example embodiments, the method may further include transmitting a context release message to a source network element. According to other example embodiments, the method may further include transmitting a handover success message to the source network element. According to other example embodiments, the method may further include receiving a transmission from the user equipment on a dedicated random access channel resource.
[0073] In some example embodiments, the handover request message includes a flag indicating that the user equipment is receiving a point-to-point and / or point-to-multipoint transmission of a multicast and broadcast service session in a radio resource control connected state. In some example embodiments, the handover request response may be a handover request preparation failure message. In other example embodiments, the network communication information may include at least one of the following: an indication that the multicast and broadcast service session in the target cell target is used to serve the user equipment in the radio resource control idle state or inactive state using point-to-multipoint transmission, and a multicast and broadcast service session configuration. In a further example embodiment, the handover request response may be a handover request confirmation message. In other example embodiments, the handover request confirmation message may include at least one of the following: a command to put the user equipment into the radio resource control idle state or inactive state, a multicast and broadcast service session configuration, and a dedicated random access channel resource. According to some example embodiments, the handover request response may be a handover request preparation failure message. According to other example embodiments, the network communication information may include a command to put the user equipment into the radio resource control idle state or inactive state, and a multicast and broadcast service configuration.
[0074] Fig.13 A set of apparatuses 10 and 20 according to certain example embodiments are shown. In certain example embodiments, the apparatus 10 may be a node or element in a communication network or associated with such a network, such as a UE, a mobile equipment (ME), a mobile station, a mobile device, a stationary device, an IoT device, or other device. It should be noted that a person of ordinary skill in the art will understand that the apparatus 10 may include a device that is not in Fig.13 Components or features shown in .
[0075] In some example embodiments, the apparatus 10 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some example embodiments, the apparatus 10 may be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that one of ordinary skill in the art will appreciate that the apparatus 10 may include components not described in the specification. Fig.13 Components or features shown in .
[0076] like Fig.13 As shown in the example of , the device 10 may include or be coupled to a processor 12 for processing information and executing instructions or operations. The processor 12 may be any type of general or special purpose processor. In fact, as examples, the processor 12 may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although in Fig.13 A single processor 12 is shown in FIG. 1 , but multiple processors may be used according to other example embodiments. For example, it should be understood that in some example embodiments, the apparatus 10 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 12 may represent a multiprocessor). According to some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
[0077] Processor 12 may perform functions associated with the operation of device 10, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of device 10, including Figure 1-10 The process shown in .
[0078] The device 10 may also include or be coupled to a memory 14 (internal or external), which may be coupled to the processor 12 for storing information and instructions that may be executed by the processor 12. The memory 14 may be one or more memories and any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 may be composed of any combination of random access memory (RAM), read-only memory (ROM), static storage such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transitory machine or computer readable medium. The instructions stored in the memory 14 may include program instructions or computer program code that, when executed by the processor 12, enables the device 10 to perform tasks as described herein.
[0079] In certain example embodiments, the device 10 may also include or be coupled to a (internal or external) drive or port configured to accept and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store programs for execution by the processor 12 and / or the device 10 to perform Figure 1-10 A computer program or software comprising any method shown.
[0080] In some example embodiments, the apparatus 10 may also include or be coupled to one or more antennas 15 for receiving downlink signals and for transmitting from the apparatus 10 via an uplink. The apparatus 10 may also include a transceiver 18 configured to send and receive information. The transceiver 18 may also include a radio interface (e.g., a modem) coupled to the antenna 15. The radio interface may correspond to a plurality of radio access technologies, including one or more of the following: GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc., to process symbols carried by the downlink or uplink, such as OFDMA symbols.
[0081] For example, the transceiver 18 may be configured to modulate information onto a carrier waveform for transmission by the antenna 15, and to demodulate information received via the antenna 15 for further processing by other elements of the device 10. In other example embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some example embodiments, the device 10 may include input and / or output devices (I / O devices). In certain example embodiments, the device 10 may also include a user interface, such as a graphical user interface or a touch screen.
[0082] In certain example embodiments, the memory 14 stores software modules that provide functionality when executed by the processor 12. The modules may include, for example, an operating system that provides operating system functionality for the device 10. The memory may also store one or more functional modules such as applications or programs to provide additional functionality for the device 10. The components of the device 10 may be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, the device 10 may optionally be configured to communicate with the device 20 via a wireless or wired communication link 70 according to any radio access technology (e.g., NR).
[0083] According to certain example embodiments, the processor 12 and the memory 14 may be included in or may form part of a processing circuit or a control circuit. In addition, in some example embodiments, the transceiver 18 may be included in or may form part of a transceiver circuit.
[0084] For example, in certain example embodiments, the device 10 may be controlled by the memory 14 and the processor 12 to receive a multicast and broadcast service session via a point-to-point transmission or a point-to-multipoint transmission with an established radio resource control connection with a source network element. The device 10 may also be controlled by the memory 14 and the processor 12 to receive a radio resource control message indicating information of a target network element. The device 10 may also be controlled by the memory 14 and the processor 12 to release the radio resource control connection and enter a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the device 10 may be controlled by the memory 14 and the processor 12 to select a target cell according to information received in the radio resource control message. Further, the device 10 may be controlled by the memory 14 and the processor 12 to perform radio communication with the target network element via the target cell. In addition, the device 10 may be controlled by the memory 14 and the processor 12 to receive a multicast and broadcast service session in the target cell in an inactive state or an idle state.
[0085] like Fig.13As shown in the example of , the apparatus 20 may be a network, a core network element, or an element in or associated with a communication network, such as a gNB. It should be noted that a person of ordinary skill in the art will understand that the apparatus 20 may include an element not in Fig.13 Components or features shown.
[0086] like Fig.13 As shown in the example of , the device 20 may include a processor 22 for processing information and executing instructions or operations. The processor 22 may be any type of general or special purpose processor. For example, as an example, the processor 22 may include one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although in Fig.13 A single processor 22 is shown in FIG. 1 , but multiple processors may be utilized according to other example embodiments. For example, it should be understood that in some example embodiments, the apparatus 20 may include two or more processors that may form a multiprocessor system that may support multiprocessing (e.g., in which case the processor 22 may represent a multiprocessor). In some example embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).
[0087] According to certain example embodiments, processor 22 may perform functions associated with the operation of apparatus 20, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of apparatus 20, including Figure 1-9 , 11 and 12.
[0088] The device 20 may also include or be coupled to a memory 24 (internal or external), which may be coupled to the processor 22 for storing information and instructions that may be executed by the processor 22. The memory 24 may be one or more memories and any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 24 may include any combination of random access memory (RAM), read-only memory (ROM), static storage such as a magnetic disk or optical disk, a hard disk drive (HDD), or any other type of non-transient machine or computer readable medium. The instructions stored in the memory 24 may include program instructions or computer program code that, when executed by the processor 22, enables the device 20 to perform tasks as described herein.
[0089] In certain example embodiments, the apparatus 20 may also include or be coupled to a (internal or external) drive or port configured to receive and read an external computer-readable storage medium, such as an optical disk, a USB drive, a flash drive, or any other storage medium. For example, the external computer-readable storage medium may store programs for execution by the processor 22 and / or the apparatus 20 to perform Figures 1 to 9 , Fig.11 and Fig.12 A computer program or software for the method shown in .
[0090] In certain example embodiments, the apparatus 20 may also include or be coupled to one or more antennas 25 for transmitting signals and / or data to and receiving signals and / or data from the apparatus 20. The apparatus 20 may also include or be coupled to a transceiver 28 configured to transmit and receive information. The transceiver 28 may include, for example, a plurality of radio interfaces that may be coupled to the antennas 25. The radio interfaces may correspond to a variety of radio access technologies, including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, Radio Frequency Identifier (RFID), Ultra-Wideband (UWB), MulteFire, etc. The radio interfaces may include components such as filters, converters (e.g., digital-to-analog converters, etc.), mappers, Fast Fourier Transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and for receiving symbols (e.g., via an uplink).
[0091] As such, the transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by the antenna 25, and to demodulate information received via the antenna 25 for further processing by other elements of the apparatus 20. In other example embodiments, the transceiver 18 may be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some example embodiments, the apparatus 20 may include input and / or output devices (I / O devices).
[0092] In certain example embodiments, memory 24 may store software modules that provide functionality when executed by processor 22. The modules may include, for example, an operating system that provides operating system functionality for device 20. The memory may also store one or more functional modules, such as applications or programs, to provide additional functionality for device 20. The components of device 20 may be implemented in hardware, or as any suitable combination of hardware and software.
[0093] According to some example embodiments, the processor 22 and the memory 24 may be included in or may form part of a processing circuit or a control circuit. In addition, in some example embodiments, the transceiver 28 may be included in or may form part of a transceiver circuit.
[0094] As used herein, the term "circuit" may refer to a hardware circuit implementation only (e.g., analog and / or digital circuits), a combination of hardware circuits and software, a combination of analog and / or digital hardware circuits and software / firmware, any portion of hardware processor(s) and software (including digital signal processors) that work together to enable a device (e.g., devices 10 and 20) to perform various functions, and / or hardware circuit(s) and / or processor(s), or portions thereof, that operate using software but may not be present when not required for operation. As a further example, as used herein, the term "circuit" may also cover an implementation of a hardware circuit or processor (or multiple processors) only or a portion of a hardware circuit or processor and its accompanying software and / or firmware. The term circuit may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.
[0095] For example, in certain example embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to transmit a handover request message to a target network element. Apparatus 20 may also be controlled by memory 24 and processor 22 to receive a handover request response message including network communication information. Apparatus 20 may be further controlled by memory 24 and processor 22 to transmit a radio resource control message indicating target network element information to a user equipment.
[0096] In other example embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to receive a handover request message from a source network element. The apparatus 20 may also be controlled by the memory 24 and the processor 22 to transmit a handover request response message including network communication information to the source network element in response to the handover request message. The apparatus 20 may be further controlled by the memory 24 and the processor 22 to transmit multicast and broadcast service session information to a user equipment in a radio resource control idle state or an inactive state using point-to-multipoint transmission.
[0097] In some example embodiments, an apparatus (e.g., apparatus 10 and / or apparatus 20) may include means for performing a method, process, or any variant discussed herein. Examples of an apparatus may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program codes for causing operations to be performed.
[0098] Certain example embodiments may relate to an apparatus comprising means for performing any of the methods described herein, including, for example, means for receiving a multicast and broadcast service session via point-to-point transmission or point-to-multipoint transmission with an established radio resource control connection with a source network element. The apparatus may also include means for receiving a radio resource control message indicating information of a target network element. The apparatus may also include means for releasing the radio resource control connection and entering a radio resource control idle state or an inactive state in response to the radio resource control message. In addition, the apparatus may include means for selecting a target cell based on information received in the radio resource control message. Further, the apparatus may include means for performing radio communications with a target cell. In addition, the apparatus may include means for receiving a multicast and broadcast service session in a target cell in an inactive state or an idle state.
[0099] Certain example embodiments may also be directed to an apparatus. The apparatus includes a component for transmitting a handover request message to a target network element. The apparatus may also include a component for receiving a handover request response message including network communication information. The apparatus may also include a component for transmitting a radio resource control message indicating target network element information to a user equipment.
[0100] Other example embodiments may be directed to an apparatus. The apparatus may include a component for receiving a handover request message from a source network element. The apparatus may also include a component for transmitting a handover request response message including network communication information to the source network element in response to the handover request message. The apparatus may also include a component for transmitting multicast and broadcast service session information to a user equipment in a radio resource control idle state or an inactive state using point-to-multipoint transmission.
[0101] Certain example embodiments described herein provide several technical improvements, enhancements and / or advantages.For example, in some example embodiments, a UE may move directly to an idle / inactive state without using any dedicated resources in a target cell, thereby reducing control signaling overhead.
[0102] The computer program product may include one or more computer executable components that are configured to perform some example embodiments when the program is run. The one or more computer executable components may be at least one software code or part thereof. Modifications and configurations required to implement the functionality of some example embodiments may be performed as routines that may be implemented as added or updated software routines. The software program may be downloaded to a device.
[0103] For example, the software or computer program code or part thereof may be in source code form, object code form or some intermediate form, and it may be stored in some carrier, distribution medium or computer readable medium, which may be any entity or device capable of carrying the program. For example, these carriers may include recording media, computer memory, read-only memory, optoelectronic and / or electrical carrier signals, telecommunication signals, and software distribution packages. Depending on the processing power required, the computer program may be executed in a single electronic digital computer or it may be distributed among multiple computers. The computer readable medium or computer readable storage medium may be a non-transitory medium.
[0104] In other example embodiments, the function may be performed by hardware or circuitry included in a device (e.g., device 10 or device 20), such as by using an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the function may be implemented as a signal, a non-tangible device that may be carried by an electromagnetic signal downloaded from the Internet or other network.
[0105] According to certain example embodiments, an apparatus (such as a node, a device or a corresponding component) may be configured as a circuit, a computer or a microprocessor (such as a single-chip computer element) or a chipset, which includes at least a memory for providing storage capacity for arithmetic operations and an operation processor for performing arithmetic operations.
[0106] Those skilled in the art will readily appreciate that the invention as discussed above may be implemented with procedures in a different order and / or with hardware elements in configurations different from those disclosed. Therefore, although the present disclosure has been described based on these example embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be apparent while remaining within the spirit and scope of the example embodiments. Although the above embodiments relate to 5G NR and LTE technologies, the above embodiments may also be applied to any other current or future 3GPP technologies, such as Advanced LTE and / or fourth generation (4G) technologies. Some vocabulary: 3GPP Third Generation Partnership Project 5G 5th Generation 5GCN 5G Core Network 5GS 5G System BS Base Station CHO Condition Switch DL Downlink DM-1 Delivery Mode 1DM-2 Delivery Mode 2eNB Enhanced Node B E-UTRAN Evolved UTRAN gNB 5G or next generation base station HO Switchover LTE Long Term Evolution NR New Radio PTM Point to Multipoint PTP Point-to-Point RLF Radio Link Failure RS Reference Symbol UE User Equipment UL Uplink
Claims
1. A method comprising: receiving a multicast and broadcast service session via point-to-point transmission or point-to-multipoint transmission with an established radio resource control connection with a source network element; receiving a radio resource control message indicating target network element information; In response to the radio resource control message, releasing the radio resource control connection and entering a radio resource control idle state or an inactive state; selecting a target cell based on information received in the radio resource control message; performing radio communication with the target cell; as well as The multicast and broadcast service session is received in the target cell in an inactive state or an idle state. 2 . The method according to claim 1 , wherein the radio resource control message is a radio resource control reconfiguration message or a radio resource control release message.
3. The method according to claim 1, wherein the target network element information comprises one or more of the following: Target cell frequency, the target cell identifier, and A multicast and broadcast service session configuration at the target cell. 4 . The method of claim 1 , wherein the target network element information comprises an idle state command at the target cell, and a multicast and broadcast service session configuration.
5. The method according to any one of claims 1 to 3, wherein the target network element information further includes a dedicated random access channel resource.
6. The method according to any one of claims 1 to 5, further comprising: The point-to-multipoint transmission of the multicast and broadcast service session in the target cell is received using the multicast and broadcast service session configuration in an idle state or an inactive state.
7. The method according to any one of claims 1 to 6, wherein the radio communication is performed on dedicated resources. The method of claim 7 , wherein the dedicated resource is a radio access channel preamble.
9. A method comprising: transmitting a handover request message to a target network element; receiving a handover request response message including network communication information; as well as A radio resource control message indicating target network element information is transmitted to the user equipment.
10. The method according to claim 9, wherein the handover request message comprises a flag indicating that the user equipment is receiving point-to-point and / or point-to-multipoint transmission of the multicast and broadcast service session in a radio resource control connected state.
11. The method according to claim 9, wherein the handover request response is a handover request preparation failure message, and wherein the network communication information includes at least one of the following: an indication that the multicast and broadcast service session in the target cell uses point-to-multipoint transmission to serve user equipment in an idle or inactive delivery state, and a multicast and broadcast service session configuration; and The radio resource control message is a radio resource control release message.
12. The method according to claim 9, wherein the handover request response is a handover request confirmation message, and The handover request confirmation message includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources, and The radio resource control message is a radio resource control reconfiguration message or a radio resource control release message.
13. The method according to claim 9, The handover request response is an Xn application protocol handover request confirmation message, and The network communication information includes: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, and Multicast and broadcast service session configuration.
14. The method according to any one of claims 9 to 13, wherein the target network element information comprises: Target cell frequency, the target cell identifier, and A multicast and broadcast service session configuration at the target cell.
15. The method according to any one of claims 9 to 13, wherein the target network element information comprises a dedicated random access channel resource.
16. The method according to any one of claims 9 to 13, wherein the target network element information comprises one or more of the following: A command to enter the radio resource control idle state or inactive state, a multicast and broadcast service session configuration at the target cell, and Dedicated random access channel resources.
17. The method according to any one of claims 9 to 16, further comprising: A context release message is received from the target network element.
18. A method comprising: receiving a handover request message from a source network element; In response to the handover request message, transmitting a handover request response message including network communication information to the source network element; as well as Multicast and broadcast service session information is transmitted to user equipment in a radio resource control idle or inactive state using point-to-multipoint transmission.
19. The method according to claim 18, further comprising: A path switch request is sent to a network element, the path switch request including information instructing the user equipment to switch to an idle state.
20. The method according to claim 18 or 19, further comprising: A transmission is received from the user equipment on a dedicated random access channel resource.
21. The method according to any one of claims 18 to 20, wherein the handover request message comprises a flag indicating that the user equipment is receiving point-to-point and / or point-to-multipoint transmission of a multicast and broadcast service session in a radio resource control connected state.
22. The method according to claim 18, wherein the handover request response is a handover request preparation failure message, and The network communication information includes at least one of the following: an indication that the multicast and broadcast service session in the target cell uses point-to-multipoint transmission to serve user equipment in a radio resource control idle state or an inactive state, and a multicast and broadcast service session configuration.
23. The method according to claim 18, wherein the handover request response is a handover request confirmation message, and The handover request confirmation message includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources.
24. The method according to claim 18, wherein the handover request response is a handover request preparation failure message, and The network communication information includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources.
25. An apparatus comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving a multicast and broadcast service session via point-to-point transmission or point-to-multipoint transmission with an established radio resource control connection with a source network element; receiving a radio resource control message indicating target network element information; In response to the radio resource control message, releasing the radio resource control connection and entering a radio resource control idle state or an inactive state; selecting a target cell based on information received in the radio resource control message; performing radio communication with the target cell; as well as The multicast and broadcast service session is received in the target cell in an inactive state or an idle state.
26. The apparatus of claim 25, wherein the radio resource control message is a radio resource control reconfiguration message or a radio resource control release message.
27. The apparatus of claim 25, wherein the target network element information comprises one or more of the following: Target cell frequency, the target cell identifier, and A multicast and broadcast service session configuration at the target cell.
28. The apparatus of claim 25, wherein the target network element information comprises an idle state command at the target cell, and a multicast and broadcast service session configuration.
29. The apparatus according to any one of claims 25 to 27, wherein the target network element information further comprises a dedicated random access channel resource.
30. The apparatus of any one of claims 25 to 29, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus to at least: The point-to-multipoint transmission of the multicast and broadcast service session in the target cell is received using the multicast and broadcast service session configuration in an idle state or an inactive state.
31. The apparatus of any one of claims 25 to 30, wherein the radio communication is performed on dedicated resources.
32. The apparatus of claim 31, wherein the dedicated resource is a radio access channel preamble.
33. An apparatus comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, with the at least one process, cause the apparatus to at least: transmitting a handover request message to a target network element; receiving a handover request response message including network communication information; as well as A radio resource control message indicating target network element information is transmitted to the user equipment.
34. The apparatus according to claim 33, wherein the handover request message comprises a flag indicating that the user equipment is receiving point-to-point and / or point-to-multipoint transmission of a multicast and broadcast service session in a radio resource control connected state.
35. The device according to claim 33, wherein the handover request response is a handover request preparation failure message, and wherein the network communication information includes at least one of the following: an indication that the multicast and broadcast service session in the target cell uses point-to-multipoint transmission to serve user equipment in an idle or inactive delivery state, and a multicast and broadcast service session configuration; and The radio resource control message is a radio resource control release message.
36. The device according to claim 33, wherein the handover request response is a handover request confirmation message, and The handover request confirmation message includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources, and The radio resource control message is a radio resource control reconfiguration message or a radio resource control release message.
37. The device according to claim 33, The handover request response is an Xn application protocol handover request confirmation message, and The network communication information includes: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, and Multicast and broadcast service session configuration.
38. The apparatus according to any one of claims 33 to 37, wherein the target network element information comprises: Target cell frequency, the target cell identifier, and A multicast and broadcast service session configuration at the target cell.
39. The apparatus according to any one of claims 33 to 37, wherein the target network element information comprises a dedicated random access channel resource.
40. The apparatus according to any one of claims 33 to 37, wherein the target network element information comprises one or more of the following: A command to enter the radio resource control idle state or inactive state, a multicast and broadcast service session configuration at the target cell, and Dedicated random access channel resources.
41. The apparatus of any one of claims 33 to 40, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus to at least: A context release message is received from the target network element.
42. An apparatus comprising: at least one processor; as well as at least one memory including computer program code, The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving a handover request message from a source network element; In response to the handover request message, transmitting a handover request response message including network communication information to the source network element; as well as Multicast and broadcast service session information is transmitted to user equipment in a radio resource control idle or inactive state using point-to-multipoint transmission.
43. The apparatus of claim 42, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus to at least: A path switch request is sent to a network element, the path switch request including information instructing the user equipment to switch to an idle state.
44. The apparatus of claim 42 or 43, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus to at least: A transmission is received from the user equipment on a dedicated random access channel resource.
45. An apparatus according to any one of claims 42 to 44, wherein the handover request message comprises a flag indicating that the user equipment is receiving point-to-point and / or point-to-multipoint transmission of a multicast and broadcast service session in a radio resource control connected state.
46. The device according to claim 42, wherein the handover request response is a handover request preparation failure message, and The network communication information includes at least one of the following: an indication that the multicast and broadcast service session in the target cell uses point-to-multipoint transmission to serve user equipment in a radio resource control idle state or an inactive state, and a multicast and broadcast service session configuration.
47. The device according to claim 42, wherein the handover request response is a handover request confirmation message, and The handover request confirmation message includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources.
48. The device according to claim 42, wherein the handover request response is a handover request preparation failure message, and The network communication information includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources.
49. An apparatus comprising: means for receiving a multicast and broadcast services session via point-to-point transmission or point-to-multipoint transmission with an established radio resource control connection with a source network element; means for receiving a radio resource control message indicating target network element information; means for releasing the radio resource control connection and entering a radio resource control idle state or an inactive state in response to the radio resource control message; means for selecting a target cell based on information received in the radio resource control message; means for performing radio communication with said target cell; as well as Means for receiving the multicast and broadcast service session in the target cell in an inactive state or an idle state.
50. The apparatus of claim 49, wherein the radio resource control message is a radio resource control reconfiguration message or a radio resource control release message.
51. The device according to claim 49, The target network element information includes one or more of the following: Target cell frequency, the target cell identifier, and A multicast and broadcast service session configuration at the target cell.
52. The apparatus of claim 49, wherein the target network element information comprises an idle state command at the target cell, and a multicast and broadcast service session configuration.
53. The apparatus of any one of claims 49 to 51, wherein the target network element information further comprises a dedicated random access channel resource.
54. The apparatus according to any one of claims 49 to 53, further comprising: Means for receiving a point-to-multipoint transmission of a multicast and broadcast service session in the target cell using the multicast and broadcast service session configuration in an idle state or an inactive state.
55. An apparatus according to any one of claims 49 to 54, wherein the radio communication is performed on dedicated resources.
56. The apparatus of claim 55, wherein the dedicated resource is a radio access channel preamble.
57. An apparatus comprising: means for transmitting a handover request message to a target network element; means for receiving a handover request response message including network communication information; as well as Means for transmitting a radio resource control message indicating target network element information to a user equipment.
58. The apparatus of claim 57, wherein the handover request message comprises a flag indicating that the user equipment is receiving point-to-point and / or point-to-multipoint transmission of a multicast and broadcast service session in a radio resource control connected state.
59. The device according to claim 57, wherein the handover request response is a handover request preparation failure message, and wherein the network communication information includes at least one of the following: an indication that the multicast and broadcast service session in the target cell uses point-to-multipoint transmission to serve user equipment in an idle or inactive delivery state, and a multicast and broadcast service session configuration; and The radio resource control message is a radio resource control release message.
60. The device according to claim 57, wherein the handover request response is a handover request confirmation message, and The handover request confirmation message includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources, and The radio resource control message is a radio resource control reconfiguration message or a radio resource control release message.
61. The device according to claim 57, The handover request response is an Xn application protocol handover request confirmation message, and The network communication information includes: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, and Multicast and broadcast service session configuration.
62. The apparatus according to any one of claims 57 to 61, wherein the target network element information comprises: Target cell frequency, the target cell identifier, and A multicast and broadcast service session configuration at the target cell.
63. An apparatus according to any one of claims 57 to 61, wherein the target network element information comprises a dedicated random access channel resource.
64. The device according to any one of claims 57 to 61, The target network element information includes one or more of the following: A command to enter the radio resource control idle state or inactive state, a multicast and broadcast service session configuration at the target cell, and Dedicated random access channel resources.
65. The apparatus of any one of claims 57 to 64, further comprising: Means for receiving a context release message from the target network element.
66. An apparatus comprising: means for receiving a handover request message from a source network element; means for transmitting, in response to the handover request message, a handover request response message including network communication information to the source network element; as well as Means for transmitting multicast and broadcast service session information to user equipment in a radio resource control idle state or inactive state using point-to-multipoint transmission.
67. The apparatus of claim 66, further comprising: Means for sending a path switch request to a network element, the path switch request including information instructing the user equipment to switch to an idle state.
68. The apparatus of claim 66 or 67, further comprising: Means for receiving a transmission from the user equipment on a dedicated random access channel resource.
69. An apparatus according to any one of claims 66 to 68, wherein the switching request message includes a flag indicating that the user equipment is receiving point-to-point and / or point-to-multipoint transmission of a multicast and broadcast service session in a radio resource control connected state.
70. The device according to claim 66, wherein the handover request response is a handover request preparation failure message, and The network communication information includes at least one of the following: an indication that the multicast and broadcast service session in the target cell uses point-to-multipoint transmission to serve user equipment in a radio resource control idle state or an inactive state, and a multicast and broadcast service session configuration.
71. The device according to claim 66, wherein the handover request response is a handover request confirmation message, and The handover request confirmation message includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources.
72. The device according to claim 66, wherein the handover request response is a handover request preparation failure message, and The network communication information includes at least one of the following: A command to cause the user equipment to enter a radio resource control idle state or an inactive state, Multicast and broadcast service session configuration, and Dedicated random access channel resources.
73. A non-transitory computer readable medium comprising program instructions stored thereon, the program instructions being used to execute the method according to any one of claims 1 to 24.
74. An apparatus comprising circuitry configured to cause the apparatus to perform a process according to any one of claims 1 to 24.
