WO2024060035A1 - Procédé, dispositif et support de stockage informatique de communication - Google Patents

Procédé, dispositif et support de stockage informatique de communication Download PDF

Info

Publication number
WO2024060035A1
WO2024060035A1 PCT/CN2022/120014 CN2022120014W WO2024060035A1 WO 2024060035 A1 WO2024060035 A1 WO 2024060035A1 CN 2022120014 W CN2022120014 W CN 2022120014W WO 2024060035 A1 WO2024060035 A1 WO 2024060035A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
multicast session
message
multicast
terminal device
Prior art date
Application number
PCT/CN2022/120014
Other languages
English (en)
Inventor
Gang Wang
Original Assignee
Nec Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nec Corporation filed Critical Nec Corporation
Priority to PCT/CN2022/120014 priority Critical patent/WO2024060035A1/fr
Publication of WO2024060035A1 publication Critical patent/WO2024060035A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media of communication for multicast and broadcast service (MBS) .
  • MBS multicast and broadcast service
  • the third generation partnership project (3GPP) has developed new radio (NR) broadcast and multicast in Release 17.
  • NR new radio
  • Release 17 multicast is only specified for a connected state, which may not fully fulfil requirements of some services (e.g., mission critical services) especially for cells with a large number of UEs.
  • some services e.g., mission critical services
  • to always keep UEs in a connected state is not power efficient. It is therefore important to support multicast for UEs in an inactive state.
  • solutions of managing multicast reception in an inactive state are still incomplete and need to be further developed.
  • embodiments of the present disclosure provide methods, devices and computer storage media of communication for multicast reception in an inactive state.
  • a method of communication comprises: receiving, at a terminal device in an inactive state and from a network device, a paging message comprising a paging cause for a multicast session, the paging cause indicating a start, stop or modification of the multicast session; and performing an operation for the multicast session based on the paging cause.
  • a method of communication comprises: transmitting, at a terminal device in an inactive state and to a network device, a first message for requesting a configuration for multicast reception in the inactive state; and receiving, from the network device, a radio resource control release message comprising the configuration.
  • a method of communication comprises: transmitting, at a network device and to a terminal device in an inactive state, a paging message comprising a paging cause for a multicast session, the paging cause indicating a start, stop or modification of the multicast session.
  • a method of communication comprises: receiving, at a network device and from a terminal device in an inactive state, a first message for requesting a configuration for multicast reception in the inactive state; and transmitting, to the terminal device, a radio resource control release message comprising the configuration.
  • a device of communication comprising a processor configured to cause the device to perform the method according to any of the first to fourth aspects of the present disclosure.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to any of the first to fourth aspects of the present disclosure.
  • FIG. 1 illustrates an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 2A illustrates a schematic diagram of a unicast scenario in which some embodiments of the present disclosure can be implemented
  • FIG. 2B illustrates a schematic diagram of a multicast scenario in which some embodiments of the present disclosure can be implemented
  • FIG. 3 illustrates a schematic diagram illustrating a process of communication for multicast reception in an inactive state according to embodiments of the present disclosure
  • FIG. 4 illustrates a schematic diagram illustrating another process of communication for a multicast reception in an inactive state according to embodiments of the present disclosure
  • FIG. 5 illustrates an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates another example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • FIG. 7 illustrates an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure
  • FIG. 8 illustrates another example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • FIG. 9 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV)
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporated one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node such as a fe
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial intelligence
  • Machine learning capability it generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz to 7125 MHz) , FR2 (24.25GHz to 71GHz) , frequency band larger than 100GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • test equipment e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • MMS may be interchangeably used with “multicast” , “multicast service” , “multicast transmission” or “multicast data” .
  • multicast reception may be interchangeably used with “MBS reception” .
  • a connected state may be interchangeably used with “a RRC_CONNECTED state”
  • an idle state may be interchangeably used with “a RRC_IDLE state”
  • an inactive state may be interchangeably used with “a RRC_INACTIVE state” .
  • a conventional MBS paging mechanism is merely used for notifying RRC_INACTIVE UE or RRC_IDLE UE of re-connecting with a network for multicast reception.
  • Only a temporary mobile group identifier (TMGI) indication is comprised in a paging message.
  • TMGI temporary mobile group identifier
  • it is to support multicast reception in an inactive state.
  • some UEs may be receiving multicast in a connected state, and enter an inactive state to continue the multicast reception.
  • some UEs may have joined a multicast session and stay in an inactive state, but the multicast session is not started yet. In these scenarios, only a TMGI indication in a paging message is not sufficient.
  • a network device transmits, to a terminal device in an inactive state, a paging message comprising a paging cause for a multicast session.
  • the paging cause indicates a start, stop or modification of the multicast session.
  • the terminal device performs an operation for the multicast session based on the paging cause. In this way, more information may be provided for a UE in an inactive state to differentiate paging information for a multicast session state.
  • a terminal device in an inactive state transmits, to a network device, a message (for convenience, also referred to as a first message herein) for requesting a configuration for multicast reception in the inactive state.
  • the network device transmits, to the terminal device, a radio resource control release message comprising the configuration.
  • a UE may stay in an inactive state to adjust its configuration for multicast reception in the inactive state.
  • FIG. 1 illustrates a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure can be implemented.
  • the communication network 100 may include a terminal device 110 and a network device 120.
  • the network device 120 may provide a serving cell (also referred to as a cell herein) 121 to serve one or more terminal devices.
  • the terminal device 110 is shown as being located in the cell 121 and served by the network device 120.
  • the communication network 100 may include any suitable number of network devices and/or terminal devices and/cells adapted for implementing implementations of the present disclosure.
  • the terminal device 110 may communicate with the network devices 120 and 130 via a channel such as a wireless communication channel.
  • the communications in the communication network 100 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • FIG. 2A illustrates a schematic diagram of a unicast scenario 200A in which some embodiments of the present disclosure can be implemented.
  • a base station 210 may transmit downlink control information (DCI) on a physical downlink control channel (PDCCH) 201 with a cell-radio network temporary identifier (C-RNTI) for UE1.
  • DCI downlink control information
  • PDCH physical downlink control channel
  • C-RNTI cell-radio network temporary identifier
  • UE1 may be scheduled to receive data (for example, video stream) on a physical downlink shared channel (PDSCH) 202 in unicast.
  • PDSCH physical downlink shared channel
  • the base station 210 may transmit DCI on a PDCCH 203 with a C-RNTI for UE2 to schedule UE2 to receive the data on a PDSCH 204 in unicast.
  • the base station 210 may transmit DCI on a PDCCH 205 with a C-RNTI for UE3 to schedule UE3 to receive the data on a PDSCH 206 in unicast.
  • FIG. 2B illustrates a schematic diagram of a multicast scenario 200B in which some embodiments of the present disclosure can be implemented.
  • the base station 210 may transmit DCI on a PDCCH 207 with a group-radio network temporary identifier (G-RNTI) for a set of UEs 220.
  • G-RNTI group-radio network temporary identifier
  • the set of UEs 220 may be scheduled to receive the data on a PDSCH 208 in multicast, i.e., to receive the data simultaneously.
  • a multicast communication service is delivered to the UEs using a multicast session.
  • a UE can receive a multicast communication service in a connected state with mechanisms such as point-to-point (PTP) and/or PTM delivery.
  • PTP point-to-point
  • the terminal device 110 may receive data of MBS multicast session only in a connected state. If the terminal device 110 which joined a multicast session is in a connected state and when the multicast session starts, the network device 120 may transmit a radio resource control (RRC) reconfiguration message with relevant MBS configuration (also referred to as a multicast configuration) for the multicast session to the terminal device 110. In this case, there is no need for separate session activation notification for the terminal device 110.
  • RRC radio resource control
  • the network device 120 may cause the terminal device 110 to enter an inactive state.
  • the network device 120 may use a group notification mechanism (i.e., multicast paging) to notify the terminal device 110 in an inactive state.
  • a conventional MBS paging mechanism is merely used for notifying RRC_INACTIVE UE or RRC_IDLE UE of re-connecting with a network for multicast reception. Only one TMGI indication is comprised in a paging message. However, there may be three types of notifications for multicast in an inactive state, e.g., how to notify UE that a multicast session is stopped, modified and started. Thus, only one TMGI indication in a paging message is not sufficient for supporting multicast reception in an inactive state.
  • embodiments of the present disclosure provide solutions for multicast reception in an inactive state so as to overcome the above and other potential issues. The detailed description will be made with reference to FIGs. 3 and 4 below.
  • FIG. 3 illustrates a schematic diagram illustrating a process 300 of communication for multicast reception in an inactive state according to embodiments of the present disclosure.
  • the process 300 will be described with reference to FIG. 1.
  • the process 300 may involve the terminal device 110 and the network device 120 as illustrated in FIG. 1. It is to be understood that the steps and the order of the steps in FIG. 3 are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added. It is assumed that the terminal device 110 is in an inactive state.
  • the network device 120 may transmit 310, to the terminal device 110, downlink control information (DCI) scheduling reception of a paging message.
  • DCI downlink control information
  • the DCI may comprise an indication indicating that only multicast information is present in the paging message.
  • the DCI may comprise a short message indicator as shown in Table 1.
  • pagingGroupList i.e., MBS related paging
  • the terminal device 110 may skip 320 the paging message. For example, an example procedure may be described as below.
  • the UE monitors paging PDCCH occasions, if the UE has not joined or interested in any MBS session when in RRC_INACTIVE, it is not required to schedule paging message in PDSCH when the short message indicator in paging DCI indicating 00.
  • the network device 120 may transmit 330, to the terminal device 110, a paging message comprising a paging cause for a multicast session.
  • the paging cause may indicate a start of the multicast session.
  • the paging cause may indicate a start of the multicast session in an inactive state.
  • the paging cause may indicate a start of the multicast session in a connected state.
  • the paging cause may indicate a stop of the multicast session.
  • the paging cause may indicate a modification of the multicast session.
  • a paging message may be configured as below.
  • a paging cause (pagingCause-MBS) is introduced for a paging group list (PagingGroupList-V1800) .
  • the pagingCause-MBS indicates a state of a MBS session (e.g., TMGI) for a corresponding pagingGroup entry.
  • the network device 120 may page two entries for MBS session by using PagingGroupList: TMGI1/TMGI2. These entries correspond to pagingGroupList-V1800 entry 1 (start) and entry 2 (modification) . It means that MBS session 1 will be started soon and a configuration for MBS session 2 will be modified.
  • the terminal device 110 may perform 340 an operation for the multicast session based on the paging cause.
  • the terminal device 110 may apply the configuration for reception of the multicast session in the inactive state. If the configuration is unavailable for the terminal device, the terminal device 110 may initiate a random access (RA) procedure for acquisition of the configuration.
  • RA random access
  • the terminal device 110 may initiate a RA procedure for acquisition of a configuration for multicast reception in the connected state, and receive the multicast session in the connected state based on the configuration.
  • the terminal device 110 may stop monitoring the multicast session, and store a configuration for the multicast session in the inactive state.
  • the terminal device 110 may initiate a RA procedure for modification of a configuration for multicast reception in the inactive state.
  • the UE Upon receiving the Paging message by the UE, the UE shall:
  • the UE Upon receiving the Paging message by the UE, the UE shall:
  • each TMGI indication may be mapped to one of three types of notification, to let a UE in an inactive state know the current MBS session state.
  • a network may want to modify a configuration for multicast reception.
  • a UE supports multicast reception in an inactive state, but a configuration for multicast reception in the inactive state is unavailable to the UE, e.g., a multicast session may be not started yet. In this case, it is unclear whether to directly start a multicast session without entering a connected state.
  • embodiments of the present disclosure provide a solution of multicast reception in an inactive state to solve the above and other potential issues.
  • the solution will be detailed in connection with FIG. 4.
  • FIG. 4 illustrates a schematic diagram illustrating another process 400 of communication for multicast reception in an inactive state according to embodiments of the present disclosure.
  • the process 400 will be described with reference to FIG. 1.
  • the process 400 may involve the terminal device 110 and the network device 120 as illustrated in FIG. 1. It is to be understood that the steps and the order of the steps in FIG. 4 are merely for illustration, and not for limitation. For example, the order of the steps may be changed. Some of the steps may be omitted or any other suitable additional steps may be added. It is assumed that the terminal device 110 is in an inactive state.
  • the terminal device 110 may transmit 410, to the network device 120, a message (for convenience, also referred to as a first message herein) for requesting a configuration for multicast reception in an inactive state.
  • a message for convenience, also referred to as a first message herein
  • the first message may be an uplink common control channel (UL-CCCH) message.
  • the first message may comprise an identity of the terminal device 110.
  • the first message may comprise at least one of an inactive-radio network temporary identifier (I-RNTI) , a fifth-generation system temporary mobile subscriber identity (5G-S-TMSI) or a cell-radio network temporary identifier (C-RNTI) of the terminal device 110.
  • I-RNTI inactive-radio network temporary identifier
  • 5G-S-TMSI fifth-generation system temporary mobile subscriber identity
  • C-RNTI cell-radio network temporary identifier
  • the first message may comprise an indication indicating modification of the configuration. In some embodiments, the first message may comprise an indication indicating acquisition of the configuration. For example, the first message may comprise an indication indicating acquisition of the configuration in a connected state. In another example, the first message may comprise an indication indicating acquisition of the configuration in an inactive state.
  • a new UL-CCCH or UL-CCCH1 message type (denoted as rrcMBSRequest herein) may be introduced as below.
  • RRCMBSRequest (i.e., the first message) is used for requesting a MBS related configuration.
  • the terminal device 110 may transmit the UL-CCCH1 message for MBS configuration acquisition or update. It is to be understood that this is merely an example, and the UL-CCCH1 message may be transmitted in any other suitable scenarios.
  • the RRCMBSRequest message may be configured as below.
  • the RRCMBSRequest message may comprise UE-Identity.
  • the UE-Identity may be at least one of I-RNTI, 5G-S-TMSI or C-RNTI.
  • the RRCMBSRequest message may also comprise two information elements (IEs) : mbsConfigurationAcquistition; mbsConfigurationUpdate.
  • IEs information elements
  • mbsConfigurationAcquistition used for MBS configuration acquisition.
  • the terminal device 110 receives paging message indicating session start, the terminal device 110 transmits RRCMBSRequest message with the IE mbsConfigurationAcquisition set to true.
  • mbsConfigurationUpdate used for MBS configuration update.
  • the terminal device 110 receives paging message indicating session modification, the terminal device 110 transmits RRCMBSRequest message with the IE mbsConfigurationUpdate set to true.
  • a RRCMBSRequest message may be configured as below.
  • the RRCMBSRequest message may comprise UE-Identity.
  • the UE-Identity may be at least one of I-RNTI, 5G-S-TMSI or C-RNTI.
  • the RRCMBSRequest message may also comprise three IEs: mbsConfigurationAcquistition-CONNECTED; mbsConfigurationAcquistition-INACTIVE; mbsConfigurationUpdate.
  • mbsConfigurationAcquistition-CONNECTED used for MBS configuration acquisition in a connected state.
  • mbsConfigurationAcquistition-INACTIVE used for MBS configuration acquisition in an inactive state.
  • the terminal device 110 When the terminal device 110 receives paging message indicating session start, the terminal device 110 sends RRCMBSRequest message with the IE mbsConfigurationAcquisition-CONNECTED or mbsConfigurationAcquistition-INACTIVE set to true. In this case, the terminal device 110 may provide a preference on MBS reception in a connected state or an inactive state to the network device 120.
  • mbsConfigurationUpdate used for MBS configuration update.
  • the terminal device 110 receives paging message indicating session modification, the terminal device 110 transmits RRCMBSRequest message with the IE mbsConfigurationUpdate set to true.
  • the first message may adopt any suitable forms.
  • a new UL-CCCH message may be introduced for random access to request MBS configuration without entering a connected state. Accordingly, UE in an inactive state is not required to fallback to a connected state to receive a new MBS configuration. Thus, power saving and latency reduction may be efficiently achieved.
  • the first message may be a RRC resume request message comprising a resume cause
  • the resume cause may indicate information of the configuration.
  • the information of the configuration may comprise modification of the configuration.
  • the information of the configuration may comprise acquisition of the configuration.
  • the information of the configuration may comprise acquisition of the configuration in a connected state.
  • the information of the configuration may comprise acquisition of the configuration in an inactive state.
  • a RRC resume request message may be configured as below.
  • mbs-Acquisition used for MBS config acquisition, when UE receives network indication (e.g. paging message) that indicating the MBS session will be started, UE sends RRCResumeRequest with resumeCause set to this value.
  • network indication e.g. paging message
  • mbs-Update used for MBS config update, when UE receives network indication (e.g. paging message) that indicating the MBS configuration will be modified, UE sends RRCResumeRequest with resumeCause set to this value.
  • network indication e.g. paging message
  • mbs-Acquisition it may be divided into two types:
  • mbs-Acquisition-CONNECTED UE prefers to receive the MBS session in RRC_CONNCTED when the session starts;
  • mbs-Acquisition-INACTIVE UE prefers to receive the MBS session in RRC_INACTIVE when the session starts.
  • a new resume cause may be introduced into a RRC resume request message to request MBS configuration without entering a connected state. Accordingly, UE in an inactive state can indicate, to a network, that a resume reason is just for MBS configuration reception, probably no need to fallback to a connected state. Thus, power saving and latency reduction may also be efficiently achieved.
  • the network device 120 may transmit 420, to the terminal device 110, a RRC release message comprising the configuration.
  • the network device 120 may send RRCRelease message to the terminal device 110 as a response.
  • RRCRelease message includes newly (updated) MBS related configuration.
  • the network device 120 may, based on implementation, send RRCRelease message to provide MBS related configuration for MBS reception during an inactive state, or, send RRCResume message to let the terminal device 110 fallback to a connected state to receive the MBS related configuration.
  • a new UL-CCCH message e.g., a RRCMBSRequest message
  • an example procedure may be described as below.
  • Step 1 UE selects the contention-based preamble to perform the Random Access Preamble transmission procedure.
  • Step 2 UE receives a downlink assignment (i.e. Msg2 -RAR MAC PDU) on the PDCCH for the RA-RNTI.
  • a downlink assignment i.e. Msg2 -RAR MAC PDU
  • Step 3 UE process Time Advance Command, Power Ramping, UL Grant, TC-RNTI.
  • UE After performing the above procedure, UE sends Msg3 by containing UL-CCCH (1) SDU with RRCMBSRequest message.
  • the MAC entity shall:
  • Step 1 UE selects the contention-based preamble to perform the Random Access Preamble transmission procedure.
  • Step 2 UE receives a downlink assignment (Msg2/RAR MAC PDU) on the PDCCH for the RA-RNTI.
  • Msg2/RAR MAC PDU downlink assignment
  • Step 3 UE process Time Advance Command, Power Ramping, UL Grant, TC-RNTI.
  • UE After performing the above procedure, UE sends Msg3 by containing UL-CCCH (1) SDU with RRCResumeRequest message.
  • the MAC entity shall:
  • the terminal device 110 may apply 430 the configuration to receive a multicast session in the inactive state. In some alternative embodiments, the terminal device 110 may enter 440 a connected state to receive the multicast session based on the configuration.
  • a new UL-CCCH message e.g., a RRCMBSRequest message
  • an example procedure may be described as below.
  • a UE in an inactive state may receive a configuration for multicast reception without entering a connected state.
  • power saving and latency reduction may be achieved.
  • process 300 and the process 400 may be performed separately or in any suitable combination.
  • embodiments of the present disclosure provide methods of communication implemented at a terminal device. These methods will be described below with reference to FIGs. 5 to 8.
  • FIG. 5 illustrates an example method 500 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 500 may be performed at the terminal device 110 as shown in FIG. 1.
  • the method 500 will be described with reference to FIG. 1. It is to be understood that the method 500 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • a terminal device in an inactive state receives, from a network device (e.g., the network device 120) , a paging message comprising a paging cause for a multicast session, the paging cause indicating a start, stop or modification of the multicast session.
  • a network device e.g., the network device 120
  • the terminal device 110 performs an operation for the multicast session based on the paging cause.
  • the terminal device 110 may apply the configuration for reception of the multicast session in the inactive state. If the configuration is unavailable for the terminal device, the terminal device 110 may initiate a random access procedure for acquisition of the configuration.
  • the terminal device 110 may initiate a random access procedure for acquisition of a configuration for multicast reception in the connected state, and receive the multicast session in the connected state based on the configuration.
  • the terminal device 110 may stop monitoring the multicast session, and store a configuration for the multicast session in the inactive state.
  • the terminal device 110 may initiate a random access procedure for modification of a configuration for multicast reception in the inactive state.
  • the terminal device 110 may receive, from the network device 120, downlink control information scheduling reception of the paging message, the downlink control information comprising an indication indicating that only multicast information is present in the downlink control information. If the terminal device 110 has not joined a multicast session in the inactive state, the terminal device 110 may skip the paging message.
  • more information may be comprised in a paging message and multicast reception in an inactive state may be well supported.
  • FIG. 6 illustrates another example method 600 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 600 may be performed at the terminal device 110 as shown in FIG. 1.
  • the method 600 will be described with reference to FIG. 1. It is to be understood that the method 600 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • a terminal device in an inactive state (e.g., the terminal device 110) transmits, to a network device (e.g., the network device 120) , a first message for requesting a configuration for multicast reception in the inactive state.
  • a network device e.g., the network device 120
  • the first message may be an uplink common control channel message and may comprise an identity of the terminal device.
  • the first message may further comprise at least one of the following: an indication indicating acquisition of the configuration; an indication indicating modification of the configuration; an indication indicating acquisition of the configuration in a connected state; or an indication indicating acquisition of the configuration in the inactive state.
  • the first message may be a radio resource control resume request message comprising a resume cause, the resume cause indicating information of the configuration.
  • the information of the configuration may comprise at least one of the following: acquisition of the configuration; modification of the configuration; acquisition of the configuration in a connected state; or acquisition of the configuration in the inactive state.
  • the terminal device 110 receives, from the network device 130, a radio resource control release message comprising the configuration.
  • the terminal device 110 may apply the configuration to receive a multicast session in the inactive state. In some embodiments, the terminal device 110 may enter a connected state to receive the multicast session based on the configuration.
  • a UE in an inactive state may receive a configuration for multicast reception without entering a connected state.
  • power saving and latency reduction may be achieved.
  • FIG. 7 illustrates an example method 700 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 700 may be performed at the network device 120 as shown in FIG. 1.
  • the method 700 will be described with reference to FIG. 1. It is to be understood that the method 700 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • a network device transmits, to a terminal device in an inactive state (e.g., the terminal device 110) , a paging message comprising a paging cause for a multicast session, the paging cause indicating a start, stop or modification of the multicast session.
  • the start of the multicast session may comprise the start of the multicast session in the inactive state or the start of the multicast session in a connected state.
  • the network device 120 may further transmit, to the terminal device 110, downlink control information scheduling reception of the paging message, the downlink control information comprising an indication indicating that only multicast information is present in the downlink control information.
  • more information may be comprised in a paging message and multicast reception in an inactive state may be well supported.
  • FIG. 8 illustrates another example method 800 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 800 may be performed at the network device 120 as shown in FIG. 1.
  • the method 800 will be described with reference to FIG. 1. It is to be understood that the method 800 may include additional blocks not shown and/or may omit some blocks as shown, and the scope of the present disclosure is not limited in this regard.
  • a network device receives, from a terminal device in an inactive state (e.g., the terminal device 110) , a first message for requesting a configuration for multicast reception in the inactive state.
  • the first message may be an uplink common control channel message and may comprise an identity of the terminal device.
  • the first message may further comprise at least one of the following: an indication indicating acquisition of the configuration; an indication indicating modification of the configuration; an indication indicating acquisition of the configuration in a connected state; or an indication indicating acquisition of the configuration in the inactive state.
  • the first message may be a radio resource control resume request message comprising a resume cause, the resume cause indicating information of the configuration.
  • the information of the configuration may comprise at least one of the following: acquisition of the configuration; modification of the configuration; acquisition of the configuration in a connected state; or acquisition of the configuration in the inactive state.
  • the network device 130 transmits, to the terminal device 110, a radio resource control release message comprising the configuration.
  • the network device 120 may indicate the terminal device 110 to apply the configuration to receive a multicast session in the inactive state. In some embodiments, the network device 120 may indicate the terminal device 110 to enter a connected state to receive the multicast session based on the configuration.
  • a UE in an inactive state may receive a configuration for multicast reception without entering a connected state.
  • power saving and latency reduction may be achieved.
  • FIG. 9 is a simplified block diagram of a device 900 that is suitable for implementing embodiments of the present disclosure.
  • the device 900 can be considered as a further example implementation of the terminal device 110 or the network device 120 as shown in FIG. 1. Accordingly, the device 900 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
  • the device 900 includes a processor 910, a memory 920 coupled to the processor 910, a suitable transmitter (TX) and receiver (RX) 940 coupled to the processor 910, and a communication interface coupled to the TX/RX 940.
  • the memory 910 stores at least a part of a program 930.
  • the TX/RX 940 is for bidirectional communications.
  • the TX/RX 940 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 930 is assumed to include program instructions that, when executed by the associated processor 910, enable the device 900 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 1 to 8.
  • the embodiments herein may be implemented by computer software executable by the processor 910 of the device 900, or by hardware, or by a combination of software and hardware.
  • the processor 910 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 910 and memory 920 may form processing means 950 adapted to implement various embodiments of the present disclosure.
  • the memory 920 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 920 is shown in the device 900, there may be several physically distinct memory modules in the device 900.
  • the processor 910 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 900 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a terminal device comprises a circuitry configured to: receive, in an inactive state and from a network device, a paging message comprising a paging cause for a multicast session, the paging cause indicating a start, stop or modification of the multicast session; and perform an operation for the multicast session based on the paging cause.
  • a terminal device comprises a circuitry configured to: transmit, in an inactive state and to a network device, a first message for requesting a configuration for multicast reception in the inactive state; and receive, from the network device, a radio resource control release message comprising the configuration.
  • a network device comprises a circuitry configured to: transmit, to a terminal device in an inactive state, a paging message comprising a paging cause for a multicast session, the paging cause indicating a start, stop or modification of the multicast session.
  • a network device comprises a circuitry configured to: receive, from a terminal device in an inactive state, a first message for requesting a configuration for multicast reception in the inactive state; and transmit, to the terminal device, a radio resource control release message comprising the configuration.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • embodiments of the present disclosure may provide the following solutions.
  • a method of communication comprises: receiving, at a terminal device in an inactive state and from a network device, a paging message comprising a paging cause for a multicast session, the paging cause indicating a start, stop or modification of the multicast session; and performing an operation for the multicast session based on the paging cause.
  • the paging cause indicates the start of the multicast session or the start of the multicast session in the inactive state.
  • performing the operation for the multicast session comprises: in accordance with a determination that a configuration for multicast reception in the inactive state is available for the terminal device, applying the configuration for reception of the multicast session in the inactive state; or in accordance with a determination that the configuration is unavailable for the terminal device, initiating a random access procedure for acquisition of the configuration.
  • the paging cause indicates the start of the multicast session in a connected state.
  • performing the operation for the multicast session comprises: initiating a random access procedure for acquisition of a configuration for multicast reception in the connected state; and receiving the multicast session in the connected state based on the configuration.
  • the paging cause indicates the stop of the multicast session.
  • performing the operation for the multicast session comprises: in accordance with a determination that the terminal device is receiving the multicast session, stopping monitoring the multicast session; and storing a configuration for the multicast session in the inactive state.
  • the paging cause indicates the modification of the multicast session.
  • performing the operation for the multicast session comprises: initiating a random access procedure for modification of a configuration for multicast reception in the inactive state.
  • the method above further comprises: receiving, from the network device, downlink control information scheduling reception of the paging message, the downlink control information comprising an indication indicating that only multicast information is present in the downlink control information; and in accordance with a determination that the terminal device has not joined a multicast session in the inactive state, skipping the paging message.
  • a method of communication comprises: transmitting, at a terminal device in an inactive state and to a network device, a first message for requesting a configuration for multicast reception in the inactive state; and receiving, from the network device, a radio resource control release message comprising the configuration.
  • the first message is an uplink common control channel message and comprises an identity of the terminal device.
  • the first message further comprises at least one of the following: an indication indicating acquisition of the configuration; an indication indicating modification of the configuration; an indication indicating acquisition of the configuration in a connected state; or an indication indicating acquisition of the configuration in the inactive state.
  • the first message is a radio resource control resume request message comprising a resume cause, the resume cause indicating information of the configuration.
  • the information of the configuration comprises at least one of the following: acquisition of the configuration; modification of the configuration; acquisition of the configuration in a connected state; or acquisition of the configuration in the inactive state.
  • the method above further comprises: applying the configuration to receive a multicast session in the inactive state; or entering a connected state to receive the multicast session based on the configuration.
  • a method of communication comprises: transmitting, at a network device and to a terminal device in an inactive state, a paging message comprising a paging cause for a multicast session, the paging cause indicating a start, stop or modification of the multicast session.
  • the method above further comprises: transmitting, to the terminal device, downlink control information scheduling reception of the paging message, the downlink control information comprising an indication indicating that only multicast information is present in the downlink control information.
  • the start of the multicast session comprises the start of the multicast session in the inactive state or the start of the multicast session in a connected state.
  • a method of communication comprises: receiving, at a network device and from a terminal device in an inactive state, a first message for requesting a configuration for multicast reception in the inactive state; and transmitting, to the terminal device, a radio resource control release message comprising the configuration.
  • the first message is an uplink common control channel message and comprises an identity of the terminal device.
  • the first message further comprises at least one of the following: an indication indicating acquisition of the configuration; an indication indicating modification of the configuration; an indication indicating acquisition of the configuration in a connected state; or an indication indicating acquisition of the configuration in the inactive state.
  • the first message is a radio resource control resume request message comprising a resume cause, the resume cause indicating information of the configuration.
  • the information of the configuration comprises at least one of the following: acquisition of the configuration; modification of the configuration; acquisition of the configuration in a connected state; or acquisition of the configuration in the inactive state.
  • transmitting the radio resource control release message comprises: indicating the terminal device to apply the configuration to receive a multicast session in the inactive state; or indicating the terminal device to enter a connected state to receive the multicast session based on the configuration.
  • a device of communication comprises: a processor configured to cause the device to perform the method according to any of the above methods.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGs. 1 to 8.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés, des dispositifs et des supports lisibles par ordinateur de communication. Dans le procédé, un dispositif terminal dans un état inactif reçoit, en provenance d'un dispositif de réseau, un message de radiomessagerie comprenant une cause de radiomessagerie pour une session de multidiffusion, et effectue une opération pour la session de multidiffusion sur la base de la cause de radiomessagerie. La cause de radiomessagerie indique un début, un arrêt ou une modification de la session de multidiffusion. De cette manière, davantage d'informations peuvent être fournies pour un UE dans un état inactif pour différencier des informations de radiomessagerie pour un état de session de multidiffusion.
PCT/CN2022/120014 2022-09-20 2022-09-20 Procédé, dispositif et support de stockage informatique de communication WO2024060035A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/120014 WO2024060035A1 (fr) 2022-09-20 2022-09-20 Procédé, dispositif et support de stockage informatique de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/120014 WO2024060035A1 (fr) 2022-09-20 2022-09-20 Procédé, dispositif et support de stockage informatique de communication

Publications (1)

Publication Number Publication Date
WO2024060035A1 true WO2024060035A1 (fr) 2024-03-28

Family

ID=90453750

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/120014 WO2024060035A1 (fr) 2022-09-20 2022-09-20 Procédé, dispositif et support de stockage informatique de communication

Country Status (1)

Country Link
WO (1) WO2024060035A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039503A (zh) * 2006-03-18 2007-09-19 华为技术有限公司 实现多媒体广播/组播业务中寻呼的方法
CN101094510A (zh) * 2006-08-04 2007-12-26 中兴通讯股份有限公司 向移动通信系统分发寻呼请求的设备及方法
CN114071376A (zh) * 2020-08-03 2022-02-18 华为技术有限公司 一种通信方法、装置以及系统
WO2022086736A1 (fr) * 2020-10-21 2022-04-28 Qualcomm Incorporated Alerte de service de multidiffusion/diffusion

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101039503A (zh) * 2006-03-18 2007-09-19 华为技术有限公司 实现多媒体广播/组播业务中寻呼的方法
CN101094510A (zh) * 2006-08-04 2007-12-26 中兴通讯股份有限公司 向移动通信系统分发寻呼请求的设备及方法
CN114071376A (zh) * 2020-08-03 2022-02-18 华为技术有限公司 一种通信方法、装置以及系统
WO2022086736A1 (fr) * 2020-10-21 2022-04-28 Qualcomm Incorporated Alerte de service de multidiffusion/diffusion

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Discussion on SA2 LS and Multicast Session Activation", 3GPP TSG-RAN WG2 MEETING #113BIS-E, R2-2102838, 2 April 2021 (2021-04-02), XP052174413 *

Similar Documents

Publication Publication Date Title
WO2024060035A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023141830A1 (fr) Procédé, dispositif et support de stockage destinés à la communication
WO2023141837A1 (fr) Procédé, dispositif et support de stockage destinés à des communications
US20240015616A1 (en) Method, device and computer storage medium of communication
WO2023245437A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024124383A1 (fr) Dispositif et procédé de communication
WO2021128162A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024087170A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024016169A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023201694A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
WO2024152200A1 (fr) Dispositifs et procédés de communication
WO2024159533A1 (fr) Dispositif et procédé de communication
WO2024119378A1 (fr) Procédé, dispositif et support de stockage informatique pour la communication
WO2024148575A1 (fr) Dispositif et procédé de communication
WO2024187475A1 (fr) Dispositifs et procédés de communication
WO2024138395A1 (fr) Dispositif et procédé de communication
WO2023201496A1 (fr) Procédés, dispositifs et support lisible par ordinateur destinés à la communication
WO2024168700A1 (fr) Dispositifs et procédés de communication
WO2024164114A1 (fr) Procédés, dispositifs et support de communication
WO2024103377A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
WO2023108502A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024168570A1 (fr) Dispositifs et procédés de communication
WO2024065433A1 (fr) Procédé, dispositif et support de communication
WO2024130677A1 (fr) Dispositif et procédé de communication
WO2023168603A1 (fr) Procédé, dispositif et support de stockage informatique de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22959047

Country of ref document: EP

Kind code of ref document: A1