WO2023272665A1 - Procédé, dispositif et support lisible par ordinateur pour la communication - Google Patents

Procédé, dispositif et support lisible par ordinateur pour la communication Download PDF

Info

Publication number
WO2023272665A1
WO2023272665A1 PCT/CN2021/103883 CN2021103883W WO2023272665A1 WO 2023272665 A1 WO2023272665 A1 WO 2023272665A1 CN 2021103883 W CN2021103883 W CN 2021103883W WO 2023272665 A1 WO2023272665 A1 WO 2023272665A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbms
mcch
mbs
configuration
terminal device
Prior art date
Application number
PCT/CN2021/103883
Other languages
English (en)
Inventor
Zhe Chen
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/CN2021/103883 priority Critical patent/WO2023272665A1/fr
Publication of WO2023272665A1 publication Critical patent/WO2023272665A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media for communication.
  • Multicast and Broadcast Service has been proposed to make it possible for efficient use of radio and network resources while transmitting audio and video content to a large group of end users.
  • MBS Multicast and Broadcast Service
  • the term “MBS” used herein refers to a point-to-multipoint communication scheme where data packets are transmitted simultaneously from a single source to multiple destinations.
  • MBS is a point-to-multipoint communication scheme where data packets are transmitted simultaneously from a single source to multiple destinations.
  • Broadcast refers to the ability to deliver content to all users.
  • Multicast on the other hand, refers to distribution of content among a specific group of users that are subscribed to those services.
  • embodiments of the present disclosure provide methods, devices and computer storage media for communications.
  • a method of communication comprises: receiving, at a terminal device and from a first network device, information associated with a multimedia broadcast multicast service (MBMS) control channel (MCCH) ; and receiving, from a second network device, a multicast traffic channel (MTCH) based on the information associated with the MCCH.
  • MBMS multimedia broadcast multicast service
  • MCCH multimedia broadcast multicast service control channel
  • MTCH multicast traffic channel
  • a method of communication comprises: transmitting, at a terminal device and to a first network device, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in; and receiving, from the first network device, a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS which is provided by a second network device.
  • MBMS multimedia broadcast multicast service
  • a method of communication comprises: transmitting, at a terminal device and to a first network device, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in; and receiving, from the first network device, information associated with a multimedia broadcast service (MBS) which is provided by a second network device.
  • MBMS multimedia broadcast multicast service
  • a method of communication comprises transmitting, at a first network device and to a terminal device, information associated with a multimedia broadcast multicast service (MBMS) control channel (MCCH) , and wherein the MCCH is associated with a multicast traffic channel (MTCH) which is transmitted by a second network device.
  • MBMS multimedia broadcast multicast service
  • MCCH multimedia broadcast multicast service control channel
  • MTCH multicast traffic channel
  • a method of communication comprises receiving, at a first network device and from a terminal device, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in; and transmitting, to a terminal device, a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS.
  • MBMS multimedia broadcast multicast service
  • a method of communication comprises receiving, at a first network device and from a terminal device, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in; and transmitting, to the terminal device, information associated with a multimedia broadcast service (MBS) which is provided by a second network device.
  • MBMS multimedia broadcast multicast service
  • a method of communication comprises transmitting, at a second network device and to a terminal device, a multicast traffic channel (MTCH) based on the information associated with the MCCH; and transmitting, to the terminal device, the MCCH comprising a configuration of the MTCH.
  • MTCH multicast traffic channel
  • a method of communication comprises receiving, at a second network device and from a first network device, a request indicating a multimedia broadcast multicast service (MBMS) or a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS.
  • MBMS multimedia broadcast multicast service
  • MMS multimedia broadcast service radio bearer
  • a method of communication comprises receiving, at a second network device and from a core network device, a multimedia broadcast service (MBS) session start message comprising one of: quality of service of the MBS or a delivery mode of the MBS; and transmitting, to a first network device, a modification required message.
  • MBS multimedia broadcast service
  • a terminal device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the terminal device to perform the method according to any one of the first, second or third aspect.
  • a network device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the network to perform the method according to any one of the fourth, fifth or sixth aspect.
  • a network device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the network device to perform the method according to any one of the seventh, eighth or ninth aspect.
  • 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 the first, second, third, fourth, fifth, sixth, seventh, eighth, or ninth aspect of the present disclosure.
  • Fig. 1 is a schematic diagram of a communication environment in which embodiments of the present disclosure can be implemented
  • Fig. 2 illustrates a signaling flow of a MBMS according to some embodiments of the present disclosure
  • Fig. 3 illustrates a signaling flow of a MBMS according to some embodiments of the present disclosure
  • Fig. 4 illustrates a signaling flow of a MBMS according to some embodiments of the present disclosure
  • Fig. 5 illustrates a signaling flow of a MBMS according to some embodiments of the present disclosure
  • Fig. 6 illustrates a flow chart of an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • Fig. 7 illustrates a flow chart of an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • Fig. 8 illustrates a flow chart of an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • Fig. 9 illustrates a flow chart of an example method of communication implemented at a first network device in accordance with some embodiments of the present disclosure
  • Fig. 10 illustrates a flow chart of an example method of communication implemented at a first network device in accordance with some embodiments of the present disclosure
  • Fig. 11 illustrates a flow chart of an example method of communication implemented at a first network device in accordance with some embodiments of the present disclosure
  • Fig. 12 illustrates a flow chart of an example method of communication implemented at a second network device in accordance with some embodiments of the present disclosure
  • Fig. 13 illustrates a flow chart of an example method of communication implemented at a second network device in accordance with some embodiments of the present disclosure
  • Fig. 14 illustrates a flow chart of an example method of communication implemented at a second network device in accordance with some embodiments of the present disclosure.
  • Fig. 15 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, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, or image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • UE user equipment
  • PDAs personal digital assistants
  • IoT internet of things
  • IoE Internet of Everything
  • MTC machine type communication
  • X means pedestrian, vehicle, or infrastructure/network
  • image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • 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.
  • Examples of 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) , a low power node such as a femto node, a pico node, 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
  • a low power node such as a femto node, a pico node, and the like.
  • 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 and 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.
  • 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.
  • MBS radio bearer MRB
  • MRB multicast service
  • PTP point to point
  • PTM point to multipoint
  • MBMS multimedia broadcast multicast service
  • MCCH Multiple multimedia broadcast multicast service
  • RRC radio resource control
  • MBS is only supported in master node (MN) . Further, when a new MBS session is started, a large number of UEs need to indicate random access upon the reception of group notification regarding the new MBS session. In that situation, the physical random access channel (PRACH) capacity is not sufficient.
  • PRACH physical random access channel
  • a terminal device receives, from a first network device, information associated with MCCH.
  • the terminal device receives, from a second network device, MTCH based on the information associated with the MCCH.
  • the secondary node can support MBS.
  • Fig. 1 illustrates a schematic diagram of a communication system in which embodiments of the present disclosure can be implemented.
  • the communication system 100 which is a part of a communication network, comprises a terminal device 110-1, a terminal device 110-2, ..., a terminal device 110-N, which can be collectively referred to as “terminal device (s) 110. ”
  • the number N can be any suitable integer number.
  • the communication system 100 further comprises a network device 120-1, a network device 120-2, ..., a network device 120-M, which can be collectively referred to as “network device (s) 120. ”
  • the number M can be any suitable integer number.
  • the network devices 120 and the terminal devices 110 can communicate data and control information to each other.
  • the numbers of devices shown in Fig. 1 are given for the purpose of illustration without suggesting any limitations.
  • the communication system 100 can comprise other communication devices, for example, the device 130.
  • Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • IEEE Institute for Electrical and Electronics Engineers
  • the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Divided Multiple Address (CDMA) , Frequency Divided Multiple Address (FDMA) , Time Divided Multiple Address (TDMA) , Frequency Divided Duplexer (FDD) , Time Divided Duplexer (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Divided Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Divided Multiple Address
  • FDMA Frequency Divided Multiple Address
  • TDMA Time Divided Multiple Address
  • FDD Frequency Divided Duplexer
  • TDD Time Divided Duplexer
  • MIMO Multiple-Input Multiple-Output
  • OFDMA Orthogonal Frequency Divided Multiple Access
  • Embodiments of the present disclosure can be applied to any suitable scenarios.
  • embodiments of the present disclosure can be implemented at reduced capability NR devices.
  • embodiments of the present disclosure can be implemented in one of the followings: NR multiple-input and multiple-output (MIMO) , NR sidelink enhancements, NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz, narrow band-Internet of Thing (NB-IOT) /enhanced Machine Type Communication (eMTC) over non-terrestrial networks (NTN) , NTN, UE power saving enhancements, NR coverage enhancement, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB) , NR Multicast and Broadcast Services, or enhancements on Multi-Radio Dual-Connectivity.
  • MIMO multiple-input and multiple-output
  • NR sidelink enhancements NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz
  • NB-IOT narrow band-Internet of
  • Fig. 2 shows a signaling chart illustrating process 200 among devices according to some example embodiments of the present disclosure. Only for the purpose of discussion, the process 200 will be described with reference to Fig. 1.
  • the process 200 may involve the terminal device 110-1, the network device 120-1 and the network device 120-2 in Fig. 1. It should be noted that the process 200 is only an example not limitation. Only for the purpose of illustrations, the network device 120-1 can refer to a master node (MN) and the network device 120-2 can refer to a secondary node (SN) .
  • MN master node
  • SN secondary node
  • the network device 120-1 (i.e., the first network device) transmits information associated with a multimedia broadcast multi service (MBMS) control channel (MCCH) to the terminal device 110-1.
  • MBMS multimedia broadcast multi service
  • the network device 120-1 may transmit 2005 the MCCH to the terminal device 110-1.
  • the MCCH can comprise a configuration of the MTCH.
  • the MCCH may also comprise a cell identity associated with the network device 120-2 (i.e., the second network device) .
  • the MCCH may comprise a cell group identity associated with the network device 120-2.
  • the network device 120-2 transmits 2020 the MTCH to the terminal device 110-1.
  • the terminal device 110-1 can receive the MTCH based on the configuration of the MTCH received (2005) from the network device 120-1. In this way, it achieves cross node MCCH/MTCH scheduling. Table 1 below shows an example of the MCCH.
  • the network device 120-1 may transmit 2010 a system information block (SIB) to the terminal device 110-1.
  • SIB may comprise a configuration of the MCCH.
  • the configuration of the MCCH may comprise an index of the MCCH.
  • the configuration of the MCCH may comprise a cell identity of the network device 120-2.
  • the configuration of the MCCH may comprise a cell group identity associated with the network device 120-2.
  • the network device 120-2 may transmit 2015 the MCCH to the terminal device 110-1.
  • the terminal device 110-1 can receive the MCCH from the network device 120-2 based on the configuration of the MCCH received (2010) from the network device 120-1.
  • the MCCH may comprise a configuration of the MTCH.
  • the network device 120-2 transmits 2020 the MTCH to the terminal device 110-1.
  • the terminal device 110-1 can receive the MTCH based on the configuration of the MTCH received (2015) from the network device 120-2. In this way, it achieves cross node MCCH/MTCH scheduling.
  • Table 2 below shows an example of the SIB.
  • Fig. 3 shows a signaling chart illustrating process 300 among devices according to some example embodiments of the present disclosure. Only for the purpose of discussion, the process 300 will be described with reference to Fig. 1. The process 300 may involve the terminal device 110-1, the network device 120-1 and the network device 120-2 in Fig. 1. It should be noted that the process 300 is only an example not limitation.
  • the terminal device 110-1 transmits 3005 information indicating a MBMS which the terminal device 110-1 is interested in.
  • the terminal device 110-1 may transmit a MBMS interest indication.
  • the information can comprise a temporary mobile group identity (TMGI) .
  • TMGI temporary mobile group identity
  • the information may also comprise a frequency associated with the MBMS.
  • the information may comprise a MBMS session identity.
  • the network device 120-1 may transmit 3010 a measurement configuration based on the information to the terminal device 110-1.
  • the measurement configuration can comprise one or more of: a reference signal type, a measurement periodicity, a measurement RS transmission period.
  • the measurement configuration can also indicate where to measure the set of reference signals in time domain.
  • the measurement configuration can also indicate where to measure the second set of reference signals in frequency domain.
  • the terminal device 110-1 may perform the measurement based on the measurement configuration.
  • the terminal device 110-1 can measure reference signal received power (RSRP) on the set of reference signals.
  • the terminal device 110-1 can measure reference signal received quality (RSRQ) on the set of reference signals.
  • the terminal device 110-1 can obtain received signal strength indicator (RSSI) of the set of reference signals.
  • the terminal device 110-1 may transmit 3015 a measurement report to the network device 120-1.
  • the measurement report may comprise results of the measurement performed based on the measurement configuration.
  • the network device 120-1 may transmit 3020 a request indicating the MBMS to the network device 120-2.
  • the MBMS can be provided by the network device 120-2.
  • the network device 120-2 may transmit 3025 an acknowledgement to the network device 120-1.
  • the transmitted (3020) request may comprise the MBS service list for the terminal device 110-1.
  • the request may comprise a TMGI list.
  • the request may comprise MBS session ID list.
  • the acknowledgement may comprise the configuration of MRB established for the terminal device 110-1.
  • the acknowledgement can comprise the MRB configuration list.
  • the network device 120-1 can configure a PTM leg in the network device 120-2 and a PTP leg in the network device 120-1.
  • the transmitted (3020) request may comprise the MRB configuration (or the MRB configuration list) .
  • the network device 120-1 may transmit the MRB configuration in a protocol data unit (PDU) session resource setup information to the network device 120-2 for the terminal device 110-1.
  • PDU protocol data unit
  • the network device 120-1 may transmit 3030 a MRB configuration to the terminal device 110-1.
  • the MRB configuration can be transmitted in a RRC reconfiguration message.
  • the MRB configuration can comprise a MRB identity (ID) .
  • the MRB configuration may comprise a radio logic channel (RLC) mode.
  • the MRB configuration may also comprise master node (MN) uplink (UL) protocol data convergence protocol (PDCP) user plane (UP) transport network layer (TNL) information.
  • MRB configuration may also comprise quality of service (QoS) mapped to the MRB. In this way, the secondary node MBS radio bearer can be configured to the terminal device.
  • MN master node
  • UL uplink
  • PDCP protocol data convergence protocol
  • UP transport network layer
  • QoS quality of service
  • the terminal device 110-1 may transmit 3035 a RRC reconfiguration complete message to the network device 120-1.
  • the network device 120-1 may transmit 3040 a SN reconfiguration complete message to the network device 120-2.
  • the terminal device 110-1 may perform 3045 a random access procedure to the network device 120-2.
  • the network device 120-1 may transmit SN status transfer to the network device 120-2.
  • the network device 120-1 may forward data to the network device 120-2 which is from the device 130.
  • the network device 120-1 may perform the path update procedure with the device 130.
  • Fig. 4 shows a signaling chart illustrating process 400 among devices according to some example embodiments of the present disclosure. Only for the purpose of discussion, the process 400 will be described with reference to Fig. 1.
  • the process 400 may involve the terminal device 110-1, the network device 120-1 and the network device 120-2 in Fig. 1. It should be noted that the process 400 is only an example not limitation.
  • the device 130 may transmit 4005 a MBS session start message to the network device 120-2.
  • the MBS session start message can indicate QoS of the MBS service.
  • the MBS session start message can indicate a delivery mode of the MBS.
  • the QoS/delivery mode parameter in SN session start message may indicate that the MBS service is a higher requirement QoS (delivery mode 1) or low requirement (delivery mode 2) .
  • the network device 120-2 may determine 4010 whether to use delivery mode 1 or mode 2 for the MBS service based on the QoS/delivery mode.
  • the network device 120-2 may transmit 4015 a SN modification request to the network device 120-1.
  • the SN modification request may comprise a MRB configuration.
  • the SN modification request can comprise TMGI.
  • the SN modification request can comprise MBS session ID.
  • the SN modification request may also comprise the delivery mode and/or QoS.
  • the SN modification request may comprise any one or combinations of the above parameters.
  • the network device 120-1 may transmit 4025 a paging message to the terminal device 110-1.
  • the network device 120-1 may page all UE to RRC_CONNECTED mode.
  • the paging message may comprise a mapping between one or more cells of the network device 120-2 and a traffic of the MBS.
  • the mapping can comprise a first mapping table between a cell identity associated with the network device 120-2 and a temporary mobile group identity.
  • the mapping can comprise a second mapping table between the cell identity and a MBS session identity.
  • the mapping can comprise a third mapping table between a cell group identity associated with the network device 120-2 and the temporary mobile group identity.
  • the mapping can comprise a fourth mapping table between the cell group identity and the MBS session identity.
  • the terminal device 110-1 may initiate 4030 the random access to the network device 120-1 upon the reception of the cell identity/cell group identity in the paging message. In this way, it achieves a quicker random access.
  • the network device 120-1 may transmit 4035 a RRC setup message to the terminal device 110-1.
  • the RRC setup message may comprise the MCCH configuration.
  • the RRC setup message may also comprise a cell identity.
  • the RRC setup message can comprise frequency of the MBS.
  • the network device 120-1 may transmit MCCH configuration of each MN by associating the MCCH to cell id/cell group id/frequency to the terminal device 110-1 in RRC setup message.
  • the terminal device 110-1 may transmit 4040 a RRC Setup Complete message to the network device 120-1.
  • the network device 120-1 may transmit 4045 a RRC Reconfiguration message with the configuration of MRB in the network device 120-2 to the terminal device 110-1.
  • the network device 120-1 may transmit 4050 a MCCH change notification message to the terminal device 110-1.
  • both RRC_INACTIVE/RRC_CONENCTED mode UE is able to receive the MBS data.
  • the updated MCCH information may comprise a mapping between one or more cells of the network device 120-2 and a traffic of the MBS.
  • the one or more cells of the network device 120-2 can be represented by a cell identity or a cell group identity.
  • the traffic of the MBS may be represented by the MBS session. Alternatively, the traffic of the MBS can be represented by TMGI and/or frequency of the MBS.
  • the mapping can comprise a mapping table between a cell identity associated with the network device 120-2 and a temporary mobile group identity.
  • the mapping can comprise a mapping table between the cell identity and a MBS session identity.
  • the mapping can comprise a mapping table between a cell group identity associated with the network device 120-2 and the temporary mobile group identity.
  • the mapping can comprise a mapping table between the cell group identity and the MBS session identity. In this way, when a MBS session is activated in the secondary node, the master node is capable to configure the MBS service in the secondary node to UE.
  • Fig. 5 shows a signaling chart illustrating process 500 among devices according to some example embodiments of the present disclosure. Only for the purpose of discussion, the process 500 will be described with reference to Fig. 1.
  • the process 500 may involve the terminal device 110-1, the network device 120-1 and the network device 120-2 in Fig. 1. It should be noted that the process 500 is only an example not limitation.
  • the network device 120-1 may transmit 5005 a counting request to the terminal device 110-1.
  • the terminal device 110-1 may transmit 5010 a counting response to the network device 120-1. Therefore, the network device 120-1 may count the number of UE who are interests in the MBS service by counting procedure.
  • the network device 120-1 may transmit determine 5015 whether to configured an extended physical random access channel (PRACH) parameters based on the number of UEs who are interested in the MBS service.
  • the network device 120-1 may transmit 5020 a RRC Reconfiguration which comprises the extended PRACH for the UEs who are interested in the MBS service.
  • the parameters can indicate a total number of random access preambles. Alternatively or in addition, the parameter may indicate synchronization signal and physical broadcast channel block (SSB) per random access channel occasion.
  • Table 3 shows an example of the parameters in the RRC Reconfiguration.
  • the parameter may indicate a random access contention resolution timer.
  • Table 4 shows an example of the parameters in the RRC Reconfiguration.
  • the parameter may indicate a random access response window.
  • Table 5 shows an example of the parameters in the RRC Reconfiguration.
  • the parameter may indicate a back off parameter value. It should be noted that the parameters can indicate any one or combinations of the above parameters. Table 6 shows an example of the parameters in the RRC Reconfiguration.
  • Fig. 6 shows a flowchart of an example method 600 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 600 can be implemented at a terminal device 110-1 as shown in Fig. 1.
  • the terminal device 110-1 receives, from the network device 120-1, information associated with a multimedia broadcast multicast service (MBMS) control channel (MCCH) .
  • MBMS multimedia broadcast multicast service
  • MCCH multimedia broadcast multicast service control channel
  • the terminal device 110-1 may receive, from the network device 120-1, the MCCH comprising at least one of: a configuration of the MTCH, a cell identity associated with the second network device, or a cell group identity associated with the second network device.
  • the terminal device 110-1 may receive, from the network device 120-1, a system information block comprising a configuration of the MCCH.
  • the configuration of the MCCH may comprise at least one of: an index of the MCCH, a cell identity associated with the second network device, or a cell group identity associated with the second network device.
  • the terminal device 110-1 receives, from the network device 120-2, a multicast traffic channel (MTCH) based on the information associated with the MCCH.
  • MTCH multicast traffic channel
  • the terminal device 110-1 may receive, from the network device 120-2, the MCCH based on the configuration of the MCCH.
  • the MCCH can comprise a configuration of the MTCH.
  • the terminal device 110-1 may receive the MTCH based on the configuration of the MTCH.
  • Fig. 7 shows a flowchart of an example method 700 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 700 can be implemented at a terminal device 110-1 as shown in Fig. 1.
  • the terminal device 110-1 transmits, to the network device 120-1, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device 110-1 is interested in.
  • the information associated with the MBMS comprises at least one of: a temporary mobile group identity, a frequency associated with the MBMS, or a MBMS session identity.
  • the terminal device 110-1 receives, from the network device 120-1, a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS which is provided by a second network device.
  • MBS multimedia broadcast service
  • MRB multimedia broadcast service radio bearer
  • the configuration the MRB comprises at least one of: a MRB identity, a radio logic channel mode, master node (MN) uplink (UL) protocol data convergence protocol (PDCP) user plane (UP) transport network layer (TNL) information, quality of service mapped to the MRB.
  • MN master node
  • UL uplink
  • PDCP protocol data convergence protocol
  • UP transport network layer
  • Fig. 8 shows a flowchart of an example method 800 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 800 can be implemented at a terminal device 110-1 as shown in Fig. 1.
  • the terminal device 110-1 transmits, to the network device 120-1, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in.
  • MBMS multimedia broadcast multicast service
  • the terminal device 110-1 receives, from the network device 120-1, information associated with a multimedia broadcast service (MBS) which is provided by a second network device.
  • MBS multimedia broadcast service
  • the terminal device 110-1 may receive a paging message comprising a mapping between one or more cells of the second network device and a traffic of the MBS.
  • the terminal device 110-1 may initiate a random access to the network device 120-1.
  • the terminal device 110-1 can receive, from the network device 120-1, a radio resource control (RRC) setup message.
  • the RRC setup message can comprise a configuration of a MBMS control channel (MCCH) , and the cell identity or the cell group identity.
  • MCCH MBMS control channel
  • the terminal device 110-1 may receive a MBMS control channel (MCCH) change notification.
  • the MCCH change notification can comprise a mapping between one or more cells of the second network device and a traffic of the MBS.
  • the terminal device 110-1 may receive, from the network device 120-1, a radio resource control (RRC) configuration indicating parameters of a physical random access channel.
  • the parameters can indicate at least one of: a total number of random access preambles, synchronization signal and physical broadcast channel block (SSB) per random access channel occasion, a random access contention resolution timer, a random access response window, or a back off parameter value.
  • RRC radio resource control
  • Fig. 9 shows a flowchart of an example method 900 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 900 can be implemented at a network device 120-1 as shown in Fig. 1.
  • the network device 120-1 transmits, to the terminal device 110-1, information associated with a multimedia broadcast multicast service (MBMS) control channel (MCCH) .
  • MBMS multimedia broadcast multicast service
  • MCCH multimedia broadcast multicast service control channel
  • the MCCH is associated with a multicast traffic channel (MTCH) which is transmitted by a second network device.
  • MTCH multicast traffic channel
  • the network device 120-1 may transmit the MCCH.
  • the MCCH may comprise at least one of: a configuration of the MTCH, a cell identity associated with the second network device, or a cell group identity associated with the second network device.
  • the network device 120-1 may transmit a system information block comprising a configuration of the MCCH.
  • the configuration of the MCCH can comprise at least one of: an index of the MCCH, a cell identity associated with the second network device, or a cell group identity associated with the second network device.
  • Fig. 10 shows a flowchart of an example method 1000 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 1000 can be implemented at a network device 120-1 as shown in Fig. 1.
  • the network device 120-1 receives from the terminal device 110-1, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device 110-1 is interested in.
  • the information associated with the MBMS may comprise at least one of: a temporary mobile group identity, a frequency associated with the MBMS, or a MBMS session identity.
  • the network device 120-1 may transmit, to the network device 120-2, a request indicating the MBMS.
  • the network device 120-1 may receive, from the network device 120-2, the configuration of the MRB of the MBMS.
  • the request may comprise at least one of: a temporary mobile group identity, or a MBMS session identity.
  • the network device 120-1 may transmit, to the network device 120-2, a request indicating the configuration of the MRB of the MBMS.
  • the network device 120-1 transmits, to the terminal device 110-1, a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS.
  • the configuration the MRB can comprise at least one of: a MRB identity, a radio logic channel mode, master node (MN) uplink (UL) protocol data convergence protocol (PDCP) user plane (UP) transport network layer (TNL) information, or quality of service mapped to the MRB.
  • MN master node
  • UL uplink
  • PDCP protocol data convergence protocol
  • UP transport network layer
  • Fig. 11 shows a flowchart of an example method 1100 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 1100 can be implemented at a network device 120-1 as shown in Fig. 1.
  • the network device 120-1 receives, from the terminal device 110-1, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in.
  • MBMS multimedia broadcast multicast service
  • the network device 120-1 transmits, to the terminal device 110-1, information associated with a multimedia broadcast service (MBS) which is provided by a network device 120-2.
  • MBS multimedia broadcast service
  • the network device 120-1 may transmit a paging message comprising a mapping between one or more cells of the second network device and a traffic of the MB S.
  • the network device 120-1 may transmit, to the terminal device 110-1, a radio resource control (RRC) setup message.
  • the RRC setup message may comprise a configuration of a MBMS control channel (MCCH) , and the cell identity or the cell group identity.
  • MCCH MBMS control channel
  • the network device 120-1 may transmit MBMS control channel (MCCH) change notification.
  • MCCH MBMS control channel
  • the MCCH change notification can comprise a mapping between one or more cells of the second network device and a traffic of the MBS.
  • the network device 120-1 may receive, from the network device 120-2, a modification required message.
  • the modification required message can indicate at least one of: a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS, a temporary mobile group identity, a MBMS session identity, a delivery mode of the MBS, or quality of service of the MBS.
  • MBS multimedia broadcast service
  • MMBMS multimedia broadcast service
  • MMBMS session identity temporary mobile group identity
  • delivery mode of the MBS or quality of service of the MBS.
  • the network device 120-1 may transmit, to the terminal device 110-1, a radio resource control (RRC) configuration indicating parameters of a physical random access channel.
  • the parameters may indicate at least one of: a total number of random access preambles, synchronization signal and physical broadcast channel block (SSB) per random access channel occasion, a random access contention resolution timer, a random access response window, or a back off parameter value.
  • RRC radio resource control
  • Fig. 12 shows a flowchart of an example method 1200 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 1200 can be implemented at a network device 120-2 as shown in Fig. 1.
  • the network device 120-2 transmits, to the terminal device 110-1, a multicast traffic channel (MTCH) based on the information associated with the MCCH.
  • MTCH multicast traffic channel
  • the network device 120-2 transmits, to the terminal device 110-1, the MCCH comprising a configuration of the MTCH.
  • Fig. 13 shows a flowchart of an example method 1300 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 1300 can be implemented at a network device 120-2 as shown in Fig. 1.
  • the network device 120-2 receives, from the network device 120-1, a request indicating a multimedia broadcast multicast service (MBMS) or a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS.
  • the request may comprise at least one of: a temporary mobile group identity, or a MBMS session identity.
  • the network device 120-2 may transmit, to the network device 120-1, the configuration of the MRB of the MBMS.
  • the configuration the MRB can comprise at least one of: a MRB identity, a radio logic channel mode, master node (MN) uplink (UL) protocol data convergence protocol (PDCP) user plane (UP) transport network layer (TNL) information, or quality of service mapped to the MRB.
  • MN master node
  • UL uplink
  • PDCP protocol data convergence protocol
  • UP transport network layer
  • Fig. 14 shows a flowchart of an example method 1400 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 1400 can be implemented at a network device 120-2 as shown in Fig. 1.
  • the network device 120-2 receives, from a core network device (for example, the device 130) , a multimedia broadcast service (MBS) session start message comprising one of: quality of service of the MBS or a delivery mode of the MBS.
  • a multimedia broadcast service (MBS) session start message comprising one of: quality of service of the MBS or a delivery mode of the MBS.
  • the network device 120-2 transmits, to the network device 120-1, a modification required message.
  • the modification required message may comprise at least one of: a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS, a temporary mobile group identity, a MBMS session identity, a delivery mode of the MBS, or quality of service of the MBS.
  • MBS multimedia broadcast service
  • MMBMS session identity a temporary mobile group identity
  • a MBMS session identity a delivery mode of the MBS
  • quality of service of the MBS quality of service of the MBS.
  • a terminal device comprises circuitry configured to receive, from a first network device, information associated with a multimedia broadcast multicast service (MBMS) control channel (MCCH) ; and receive, from a second network device, a multicast traffic channel (MTCH) based on the information associated with the MCCH.
  • MBMS multimedia broadcast multicast service
  • MCCH multimedia broadcast multicast service control channel
  • MTCH multicast traffic channel
  • the terminal device comprises circuitry configured to receive the information associated with the MCCH by: receiving, from the first network device, the MCCH comprising at least one of: a configuration of the MTCH, a cell identity associated with the second network device, or a cell group identity associated with the second network device.
  • the terminal device comprises circuitry configured to receive the information associated with the MCCH by: receiving, from the first network device, a system information block comprising a configuration of the MCCH, the configuration of the MCCH comprising at least one of: an index of the MCCH, a cell identity associated with the second network device, or a cell group identity associated with the second network device.
  • the terminal device comprises circuitry configured to receive, from the second network device, the MCCH based on the configuration of the MCCH, the MCCH comprising a configuration of the MTCH; and where receiving the MTCH comprises: receiving the MTCH based on the configuration of the MTCH.
  • a terminal device comprises circuitry configured to transmit, to a first network device, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in; and receive, from the first network device, a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS which is provided by a second network device.
  • MBMS multimedia broadcast multicast service
  • the information associated with the MBMS comprises at least one of: a temporary mobile group identity, a frequency associated with the MBMS, or a MBMS session identity.
  • the configuration the MRB comprises at least one of: a MRB identity, a radio logic channel mode, master node (MN) uplink (UL) protocol data convergence protocol (PDCP) user plane (UP) transport network layer (TNL) information, or quality of service mapped to the MRB.
  • MN master node
  • UL uplink
  • PDCP protocol data convergence protocol
  • UP transport network layer
  • TNL transport network layer
  • a terminal device comprises circuitry configured to transmit, to a first network device, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in; and receive, from the first network device, information associated with a multimedia broadcast service (MBS) which is provided by a second network device.
  • MBMS multimedia broadcast multicast service
  • the terminal device comprises circuitry configured to receive the information by: in accordance with a determination that the MBS is a delivery mode 1 service, receiving a paging message comprising a mapping between one or more cells of the second network device and a traffic of the MBS.
  • the terminal device comprises circuitry configured to initiate a random access to the first network device; and receive, from the first network device, a radio resource control (RRC) setup message comprising a configuration of a MBMS control channel (MCCH) , and the cell identity or the cell group identity.
  • RRC radio resource control
  • the terminal device comprises circuitry configured to receive the information by: in accordance with a determination that the MBS is a delivery mode 2 service, receiving a MBMS control channel (MCCH) change notification comprising a mapping between one or more cells of the second network device and a traffic of the MBS.
  • MCCH MBMS control channel
  • the terminal device comprises circuitry configured to receive, from the first network device, a radio resource control (RRC) configuration indicating parameters of a physical random access channel, the parameters indicating at least one of: a total number of random access preambles, synchronization signal and physical broadcast channel block (SSB) per random access channel occasion, a random access contention resolution timer, a random access response window, or a back off parameter value.
  • RRC radio resource control
  • a network device comprises circuitry configured to transmit, to a terminal device, information associated with a multimedia broadcast multicast service (MBMS) control channel (MCCH) , and wherein the MCCH is associated with a multicast traffic channel (MTCH) which is transmitted by a second network device.
  • MBMS multimedia broadcast multicast service
  • MCCH multimedia broadcast multicast service control channel
  • MTCH multicast traffic channel
  • the network device comprises circuitry configured to transmit the information associated with the MCCH by: transmitting the MCCH comprising at least one of: a configuration of the MTCH, a cell identity associated with the second network device, or a cell group identity associated with the second network device.
  • the network device comprises circuitry configured to transmit the information associated with the MCCH by: transmitting a system information block comprising a configuration of the MCCH, the configuration of the MCCH comprising at least one of: an index of the MCCH, a cell identity associated with the second network device, or a cell group identity associated with the second network device.
  • a network device comprises circuitry configured to receive, from a terminal device, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in; and transmit, to a terminal device, a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS.
  • MBMS multimedia broadcast multicast service
  • the information associated with the MBMS comprises at least one of: a temporary mobile group identity, a frequency associated with the MBMS, or a MBMS session identity.
  • the network device comprises circuitry configured to transmit, to a second network device, a request indicating the MBMS; and receive, from the second network device, the configuration of the MRB of the MBMS.
  • the request comprises at least one of: a temporary mobile group identity, or a MBMS session identity.
  • the network device comprises circuitry configured to transmit, to a second network device, a request indicating the configuration of the MRB of the MBMS.
  • the configuration the MRB comprises at least one of: a MRB identity, a radio logic channel mode, master node (MN) uplink (UL) protocol data convergence protocol (PDCP) user plane (UP) transport network layer (TNL) information, or quality of service mapped to the MRB.
  • MN master node
  • UL uplink
  • PDCP protocol data convergence protocol
  • UP transport network layer
  • TNL transport network layer
  • a network device comprises circuitry configured to receive, from a terminal device, information indicating a multimedia broadcast multicast service (MBMS) which the terminal device is interested in; and transmit, to the terminal device, information associated with a multimedia broadcast service (MBS) which is provided by a second network device.
  • MBMS multimedia broadcast multicast service
  • the network device comprises circuitry configured to transmit the information by: in accordance with a determination that the MBS is a delivery mode 1 service, transmitting a paging message comprising a mapping between one or more cells of the second network device and a traffic of the MBS.
  • the network device comprises circuitry configured to transmit, to the terminal device, a radio resource control (RRC) setup message comprising a configuration of a MBMS control channel (MCCH) , and the cell identity or the cell group identity.
  • RRC radio resource control
  • the network device comprises circuitry configured to transmit the information by: in accordance with a determination that the MBS is a delivery mode 2 service, transmitting MBMS control channel (MCCH) change notification comprising a mapping between one or more cells of the second network device and a traffic of the MBS.
  • MCCH MBMS control channel
  • the network device comprises circuitry configured to receive, from the second network device, a modification required message indicating at least one of: a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS, a temporary mobile group identity, a MBMS session identity, a delivery mode of the MBS, or quality of service of the MBS.
  • MBS multimedia broadcast service
  • MMBMS multimedia broadcast service
  • MMBMS session identity temporary mobile group identity
  • delivery mode of the MBS a delivery mode of the MBS
  • quality of service of the MBS quality of service of the MBS.
  • the network device comprises circuitry configured to transmit, to the terminal device, a radio resource control (RRC) configuration indicating parameters of a physical random access channel, the parameters indicating at least one of: a total number of random access preambles, synchronization signal and physical broadcast channel block (SSB) per random access channel occasion, a random access contention resolution timer, a random access response window, or a back off parameter value.
  • RRC radio resource control
  • a network device comprises circuitry configured to transmit, to a terminal device, a multicast traffic channel (MTCH) based on the information associated with the MCCH; and transmit, to the terminal device, the MCCH comprising a configuration of the MTCH.
  • MTCH multicast traffic channel
  • a network device comprises circuitry configured to receive, at a second network device and from a first network device, a request indicating a multimedia broadcast multicast service (MBMS) or a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS.
  • MBMS multimedia broadcast multicast service
  • MMS multimedia broadcast service radio bearer
  • a network device comprises circuitry configured to in accordance with a determination that the request indicates the MBMS, transmit, to the first network device, the configuration of the MRB of the MBMS.
  • the request comprises at least one of: a temporary mobile group identity, or a MBMS session identity.
  • the configuration the MRB comprises at least one of: a MRB identity, a radio logic channel mode, master node (MN) uplink (UL) protocol data convergence protocol (PDCP) user plane (UP) transport network layer (TNL) information, or quality of service mapped to the MRB.
  • MN master node
  • UL uplink
  • PDCP protocol data convergence protocol
  • UP transport network layer
  • TNL transport network layer
  • a network device comprises circuitry configured to receive, from a core network device, a multimedia broadcast service (MBS) session start message comprising one of: quality of service of the MBS or a delivery mode of the MBS; and transmit, to a first network device, a modification required message.
  • MBS multimedia broadcast service
  • the modification required message comprises at least one of: a configuration of a multimedia broadcast service (MBS) radio bearer (MRB) of the MBMS, a temporary mobile group identity, a MBMS session identity, a delivery mode of the MBS, or quality of service of the MBS.
  • MBS multimedia broadcast service
  • MMBMS multimedia broadcast service
  • Fig. 15 is a simplified block diagram of a device 1500 that is suitable for implementing embodiments of the present disclosure.
  • the device 1500 can be considered as a further example implementation of the network device 120, or the terminal device 110 as shown in Fig. 1. Accordingly, the device 1500 can be implemented at or as at least a part of the terminal device 110, or the network device 120.
  • the device 1500 includes a processor 1510, a memory 1520 coupled to the processor 1510, a suitable transmitter (TX) and receiver (RX) 1540 coupled to the processor 1510, and a communication interface coupled to the TX/RX 1540.
  • the memory 1510 stores at least a part of a program 1530.
  • the TX/RX 1540 is for bidirectional communications.
  • the TX/RX 1540 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 interface for bidirectional communications between eNBs, S1 interface for communication between a Mobility Management Entity (MME) /Serving Gateway (S-GW) and the eNB, Un interface for communication between the eNB and a relay node (RN) , or Uu interface for communication between the eNB and a terminal device.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Un interface for communication between the eNB and a relay node (RN)
  • Uu interface for communication between the eNB and a terminal device.
  • the program 1530 is assumed to include program instructions that, when executed by the associated processor 1510, enable the device 1500 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Figs. 2 to 6.
  • the embodiments herein may be implemented by computer software executable by the processor 1510 of the device 1500, or by hardware, or by a combination of software and hardware.
  • the processor 1510 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 1510 and memory 1520 may form processing means adapted to implement various embodiments of the present disclosure.
  • the memory 1520 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 1520 is shown in the device 1500, there may be several physically distinct memory modules in the device 1500.
  • the processor 1510 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 1500 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.
  • 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. 2 to 10.
  • 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)
  • 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 pour la communication. Selon des modes de réalisation de la présente divulgation, un dispositif terminal reçoit, d'un nœud maître, des informations associées au MCCH. Le dispositif terminal reçoit, d'un second dispositif réseau, un MTCH d'après les informations associées au MCCH. De cette manière, le nœud secondaire peut prendre en charge le MBS.
PCT/CN2021/103883 2021-06-30 2021-06-30 Procédé, dispositif et support lisible par ordinateur pour la communication WO2023272665A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/103883 WO2023272665A1 (fr) 2021-06-30 2021-06-30 Procédé, dispositif et support lisible par ordinateur pour la communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/103883 WO2023272665A1 (fr) 2021-06-30 2021-06-30 Procédé, dispositif et support lisible par ordinateur pour la communication

Publications (1)

Publication Number Publication Date
WO2023272665A1 true WO2023272665A1 (fr) 2023-01-05

Family

ID=84689896

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/103883 WO2023272665A1 (fr) 2021-06-30 2021-06-30 Procédé, dispositif et support lisible par ordinateur pour la communication

Country Status (1)

Country Link
WO (1) WO2023272665A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170223662A1 (en) * 2014-08-04 2017-08-03 Nokia Solutions And Networks Oy Method and apparatus for enhancing broadcast service
US20180160342A1 (en) * 2016-12-02 2018-06-07 Ofinno Technologies, Llc Handover Procedure for a UE with V2X Services
US20180160398A1 (en) * 2016-12-02 2018-06-07 Ofinno Technologies, Llc MBMS Configuration between eNBs for V2X Services
US20190075614A1 (en) * 2016-05-06 2019-03-07 Huawei Technologies Co., Ltd. Multicast service receiving method, multicast service sending method, apparatus, and system
CN110460589A (zh) * 2014-01-31 2019-11-15 日本电气株式会社 主基站装置、次级基站装置和用户装置及所进行的方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110460589A (zh) * 2014-01-31 2019-11-15 日本电气株式会社 主基站装置、次级基站装置和用户装置及所进行的方法
US20170223662A1 (en) * 2014-08-04 2017-08-03 Nokia Solutions And Networks Oy Method and apparatus for enhancing broadcast service
US20190075614A1 (en) * 2016-05-06 2019-03-07 Huawei Technologies Co., Ltd. Multicast service receiving method, multicast service sending method, apparatus, and system
US20180160342A1 (en) * 2016-12-02 2018-06-07 Ofinno Technologies, Llc Handover Procedure for a UE with V2X Services
US20180160398A1 (en) * 2016-12-02 2018-06-07 Ofinno Technologies, Llc MBMS Configuration between eNBs for V2X Services

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "Considerations on parallel Configuration between MeNB and SeNB", 3GPP DRAFT; R2-144358 CONSIDERATIONS ON PARALLEL SCG CONFIGURATION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Shanghai, China; 20141006 - 20141010, 5 October 2014 (2014-10-05), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050876569 *
ZTE: "Discussion on the NG-RAN architecture enhancement for MBS", 3GPP DRAFT; R3-204648, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20200817 - 20200828, 6 August 2020 (2020-08-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911221 *

Similar Documents

Publication Publication Date Title
US10849104B2 (en) Methods and devices for broadcasting system information on demand
US20200077287A1 (en) Apparatus, method and computer program
US10979945B2 (en) Device to reduce consumption of radio resources of a macrocell
EP3451737A1 (fr) Procédé et dispositif de communication
US8873452B2 (en) Multimedia multicast/broadcast service providing apparatus and multimedia multicast/broadcast service providing method using the same
CN113840241A (zh) 一种通信方法及通信装置
CN110999437B (zh) 用于无线网络的特定于网络切片的寻呼
KR102246506B1 (ko) FeMTC 및 eNB-IoT에 대한 SC-MCCH 세그먼트 스케줄링
EP3210417B1 (fr) Procédé et appareil d'acquisition d'informations système
EP3533274A1 (fr) Entité de système de télécommunications mobiles pour la transmission d'informations système dans un réseau 5g
WO2019068224A1 (fr) Procédé de communication, appareil et programme informatique
US20210051569A1 (en) System information delivery enhancements
US20200236652A1 (en) Method for Performing Mobile Communications, Mobile Terminal Device, and Mobile Baseband Processing Circuit
US11026126B2 (en) Method and apparatus for facilitating MBMS reception
WO2023272665A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
US20220201662A1 (en) Specifying content of quality report in msg3
WO2022236592A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
EP4024952A1 (fr) Procédé et appareil de communication
WO2022082520A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
CN115399014A (zh) 设备、方法和计算机程序
US20240015618A1 (en) Methods, devices and computer readable media for communications
WO2022140938A1 (fr) Procédés, dispositifs et support lisible par ordinateur de communication
WO2022011515A1 (fr) Procédé et dispositif de communication, et support de stockage d'ordinateur
WO2023044920A1 (fr) Procédé, dispositif et support lisible par ordinateur pour des communications
WO2023000177A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la 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: 21947618

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21947618

Country of ref document: EP

Kind code of ref document: A1