US20230262531A1 - Apparatus and method of wireless communication for mbs - Google Patents

Apparatus and method of wireless communication for mbs Download PDF

Info

Publication number
US20230262531A1
US20230262531A1 US18/303,559 US202318303559A US2023262531A1 US 20230262531 A1 US20230262531 A1 US 20230262531A1 US 202318303559 A US202318303559 A US 202318303559A US 2023262531 A1 US2023262531 A1 US 2023262531A1
Authority
US
United States
Prior art keywords
5mbs
5mbsn
base station
content
information
Prior art date
Legal status (The legal status 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 status listed.)
Pending
Application number
US18/303,559
Other languages
English (en)
Inventor
Chiu-Wen CHEN
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Purplevine Innovation Co Ltd
Original Assignee
Purplevine Innovation Co Ltd
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 Purplevine Innovation Co Ltd filed Critical Purplevine Innovation Co Ltd
Priority to US18/303,559 priority Critical patent/US20230262531A1/en
Assigned to PURPLEVINE INNOVATION COMPANY LIMITED reassignment PURPLEVINE INNOVATION COMPANY LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHEN, CHIU-WEN
Publication of US20230262531A1 publication Critical patent/US20230262531A1/en
Pending legal-status Critical Current

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/26—Reselection being triggered by specific parameters by agreed or negotiated communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to the field of communication systems, and more particularly, to an apparatus and a method of wireless communication for multicast and broadcast service (MBS), which can provide a good communication performance and/or high reliability.
  • MMS multicast and broadcast service
  • the architecture of 5G NR multicast and broadcast service is expected to be similar to SC-PTM defined in LTE. Further, multicast-broadcast single-frequency network (MBSFN) described in LTE is not expected to be supported in 5MBS.
  • MMSFN multicast-broadcast single-frequency network
  • NR supports the reception of 5MBS transmission by mobile UEs in idle/inactive/connected states. It means that when the 5MBS transmission is delivered in a small area (e.g., single cell), handovers and tracking area updates may frequently occur between small areas because of small coverage area of SC-PTM. Service interruption of 5MBS is happened during performing UE handover and tracking area update. This results in a serious 5MBS data loss and un-reliable 5MBS transmission.
  • An object of the present disclosure is to propose an apparatus and a method of wireless communication for multicast and broadcast service (MBS) of the same, which can solve issues in the prior art, provide a lower power consumption for 5MBS reception, provide a better resource efficiency for 5MBS networks, provide a higher reliability of 5MBS transmission, reduce a data loss during handover, provide a service continuity due to mobility, and/or provide a good communication performance.
  • MBS multicast and broadcast service
  • a method of wireless communication for multicast and broadcast service (MBS) by a user equipment (UE) comprises being configured, from at least one of a first base station, a second base station, or a third base station, with a shared-5G multicast and broadcast service network (S-5MBSN) information in a S-5MBSN before a cell reselection and receiving, from the at least one of the first base station, the second base station, or the third base station, an MBS data in the S-5MBSN during a UE mobility, wherein the S-5MBSN is shared by an inter-cell, an inter node, and/or multiple public land mobile networks (PLMNs), the S-5MBSN provides a same 5MBS session/content, and the same 5MBS session/content is scheduled by the inter-cell, the inter node, and/or the multiple PLMNs independently.
  • S-5MBSN shared-5G multicast and broadcast service network
  • a method of wireless communication for multicast and broadcast service (MBS) by a base station comprises configuring, to one or more user equipments (UEs), a shared-5G multicast and broadcast service network (S-5MBSN) information in a S-5MBSN before a cell reselection and transmitting, to the one or more UEs, an MBS data in the S-5MBSN during a UE mobility, wherein the S-5MBSN is shared by an inter-cell, an inter node, and/or multiple public land mobile networks (PLMNs), the S-5MBSN provides a same 5MBS session/content, and the same 5MBS session/content is scheduled by the inter-cell, the inter node, and/or the multiple PLMNs independently.
  • UEs user equipments
  • S-5MBSN shared-5G multicast and broadcast service network
  • PLMNs public land mobile networks
  • a UE comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver.
  • the processor is configured, from at least one of a first base station, a second base station, or a third base station, with a shared-5G multicast and broadcast service network (S-5MBSN) information in a S-5MBSN before a cell reselection
  • the transceiver is configured to receive, from the at least one of the first base station, the second base station, or the third base station, an MBS data in the S-5MBSN during a UE mobility, wherein the S-5MBSN is shared by an inter-cell, an inter node, and/or multiple public land mobile networks (PLMNs), the S-5MBSN provides a same 5MBS session/content, and the same 5MBS session/content is scheduled by the inter-cell, the inter node, and/or the multiple PLMNs independently.
  • PLMNs public land mobile networks
  • a base station comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver.
  • the processor is configured to configure, to one or more user equipments (UEs), a shared-5G multicast and broadcast service network (S-5MBSN) information in a S-5MBSN before a cell reselection, and the transceiver is configured to transmit, to the one or more UEs, an MBS data in the S-5MBSN during a UE mobility, wherein the S-5MBSN is shared by an inter-cell, an inter node, and/or multiple public land mobile networks (PLMNs), the S-5MBSN provides a same 5MBS session/content, and the same 5MBS session/content is scheduled by the inter-cell, the inter node, and/or the multiple PLMNs independently.
  • PLMNs public land mobile networks
  • a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method.
  • a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method.
  • a computer readable storage medium in which a computer program is stored, causes a computer to execute the above method.
  • a computer program product includes a computer program, and the computer program causes a computer to execute the above method.
  • a computer program causes a computer to execute the above method.
  • FIG. 1 A is a schematic diagram illustrating a communication controlling system according to an embodiment of the present disclosure.
  • FIG. 1 B is a block diagram illustrating a communication controlling system according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic diagram illustrating a user plane radio protocol architecture within a gNB and a UE for 5G multicast and broadcast service (5MBS) according to an embodiment of the present disclosure.
  • FIG. 3 is a schematic diagram illustrating that in a radio access network (RAN) functional split, a gNB further comprises a centralized unit (CU) and a plurality of distributed unit (DUs) according to an embodiment of the present disclosure.
  • RAN radio access network
  • CU centralized unit
  • DUs distributed unit
  • FIG. 4 is a schematic diagram illustrating a shared-5MBS network (S-5MBSN) configuration procedure according to an embodiment of the present disclosure.
  • FIG. 5 A is a schematic diagram illustrating an architecture of 5 MB S service continuity according to an embodiment of the present disclosure.
  • FIG. 5 B is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 6 is a flowchart illustrating a method of wireless communication for multicast and broadcast service (MBS) performed by a UE according to an embodiment of the present disclosure.
  • MMS multicast and broadcast service
  • FIG. 7 is a flowchart illustrating a method of wireless communication for multicast and broadcast service (MBS) performed by a first base station according to an embodiment of the present disclosure.
  • MMS multicast and broadcast service
  • FIG. 8 is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic diagram illustrating an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • FIG. 16 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.
  • FIG. 1 A and FIG. 1 B illustrate that, in some embodiments, a communication controlling system 1 according to an embodiment of the present disclosure is provided.
  • the communication controlling system 1 comprises a user equipment 10 and a base station 20 .
  • the user equipment 10 and the base station 20 may communicate with each other either wirelessly or in a wired way.
  • the base station 20 and a next generation core network 30 may also communicate with each other either wirelessly or in a wired way.
  • the next generation core network 30 is a backend serving network system and may comprise an access and mobility management function (AMF), a user plane function (UPF), and a session management function (SMF).
  • AMF access and mobility management function
  • UPF user plane function
  • SMF session management function
  • the user equipment 10 may be a non-public network (NPN) capable apparatus or a non-NPN capable apparatus, but the present disclosure is not limited to this.
  • the user equipment 10 comprises a processor 11 , a memory 12 , and a transceiver 13 .
  • the processor 11 is coupled to the memory 12 and the transceiver 13 .
  • the transceiver 13 of the user equipment 10 is configured to transmit a signal to the base station 20 so that the user equipment 10 communicates with the base station 20 each other.
  • the base station 20 may include a processor 21 , a memory 22 , and a transceiver 23 .
  • the processor 21 is coupled to the memory 22 and the transceiver 23 .
  • the processor 11 or 21 may be configured to implement proposed functions, procedures and/or methods described in this description.
  • Layers of radio interface protocol may be implemented in the processor 11 or 21 .
  • the memory 12 or 22 is operatively coupled with the processor 11 or 21 and stores a variety of information to operate the processor 11 or 21 .
  • the transceiver 13 or 23 is operatively coupled with the processor 11 or 21 , and the transceiver 13 or 23 transmits and/or receives a radio signal.
  • the processor 11 or 21 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device.
  • the memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and/or other storage device.
  • the transceiver 13 or 23 may include baseband circuitry to process radio frequency signals.
  • modules e.g., procedures, functions, and so on
  • the modules can be stored in the memory 12 or 22 and executed by the processor 11 or 21 .
  • the memory 12 or 22 can be implemented within the processor 11 or 21 or external to the processor 11 or 21 in which case those can be communicatively coupled to the processor 11 or 21 via various means as is known in the art.
  • 5G multicast and broadcast service 5G multicast and broadcast service
  • 5GCN 5G core network
  • RAN radio access network
  • some UE-assisted information can be taken into account.
  • FIG. 2 illustrates a user plane radio protocol architecture within a gNB and a UE for 5G multicast and broadcast service (5MBS) according to an embodiment of the present disclosure.
  • the user plane radio protocol architecture within the gNB and the UE for 5MBS includes a service data adaptation protocol (SDAP), a packet data convergence protocol (PDCP), a radio link control (RLC), and a medium access control (MAC).
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • RLC radio link control
  • MAC medium access control
  • a gNB further comprises a centralized unit (CU) and a plurality of distributed unit (DUs) as shown in FIG. 3 .
  • the protocol stack of the CU comprises an RRC layer, a SDAP layer, and a PDCP layer, while the protocol stack of DU comprises an RLC layer, a MAC layer, and a PHY layer.
  • the F1 interface between the CU and the DU is established between the PDCP layer of the protocol stack and the RLC layer of the protocol stack.
  • the gNB providing 5MBS towards the UEs, can decide to transmit 5MBS flows via multicast radio bearer (e.g., MRB) and/or unicast data radio bearer (e.g., specific DRB) based on 5MBS QoS (e.g., reliability) requirement.
  • MRB multicast radio bearer
  • unicast data radio bearer e.g., specific DRB
  • 5MBS QoS e.g., reliability
  • the 5MBS using point-to-multipoint (PTM) transmissions is delivered by MRB for a given UE(s) as well as the PDCCH-scheduled PTM PDSCH data is scrambled by a specific Group-RNTI (G-RNTI).
  • G-RNTI Group-RNTI
  • the 5MBS using point-to-point (PTP) transmissions is delivered by the specific DRB with the scrambled C-RNTI for a given UE(s) as well as the PDCCH-scheduled PTP PDSCH data is scrambled by a specific Cell-RNTI (C-RNTI).
  • PTP point-to-point
  • 5MBS with carrier aggregation (CA) duplication and dual connectivity (DC) duplication can be used to improve reliability of multicast/broadcast data transmission and achieve service continuity during bearer switching and mobility.
  • CA carrier aggregation
  • DC dual connectivity
  • PDCP duplication with more than one active RLC entity for 5MBS the reliability requirements in MAC/PHY layer can be relaxed and low data loss can be expected during handover (for connected UEs), even tracking area updates (for idle/inactive UEs). It would be beneficial to (but are not limited to) mission critical, public safety, V2X applications, software update via RAN, and some other group communications in IoT applications.
  • a shared-5MBS network is a network shared by inter-cell/inter-node/multiple PLMNs that provides the same multicast or broadcast session/content.
  • the shared 5MBS packet is scheduled by the gNBs independently based on the different 5MBS data arrive time from 5G core network(s) (5GCN).
  • 5GCN 5G core network(s)
  • All 5MBS traffic mapped to PDSCH can be dynamically scheduled with unicast traffic.
  • the S-5MBSN can be a public network, an integrated private network, or a standalone private network. At least the 5MBS bearer context in the S-5MBSN is shared.
  • the 5MBS bearer context includes all information describing the particular 5BMS bearer information and is stored in each gNB involved in the same S-5MBSN.
  • FIG. 4 shows an example of S-5MBSN configuration procedure. After 5MBS session is activated, the following S-5MBSN configuration information (but not limited to) is exchanged between inter-cell/inter-node/multiple PLMNs when the S-5MBSN configuration procedure is performed.
  • the following S-5MBSN configuration information may include S-5MBSN identifier (e.g., the identifier associated with service area ID (SAT)), 5MBS identifier (e.g., MBS Session ID, TMGI, etc.), G-RNTI, bearer type (e.g., PTM bearer (MRB) or PTP bearer (specific DRB) for 5MBS), transmission frequency and period, start sequence number, end sequence number, 5MBS service continuity bit, UE context information, UE capability (e.g., UE supported/interested frequency), Group UE identifier, UE's mobility restriction for 5G private network, CAG ID for 5G private network, and/or some UE-specific information (e.g., DRX configuration) which can be exchanged if necessary.
  • S-5MBSN identifier e.g., the identifier associated with service area ID (SAT)
  • 5MBS identifier e.g., MBS Session ID, TMGI, etc.
  • the exchanged S-5MBSN configuration procedure (it may include request and response messages) between inter-cell/inter-node/multiple PLMNs can be performed in any time during the activation of 5MBS session when necessary. Furthermore, some of the S-5MBSN configuration information can be forwarded to UE(s) via broadcast or unicast with at least one RRC signaling (e.g., SIB, paging, RRCReconfiguration, etc.). In some cases, the associated S-5MBSN configuration information can be transmitted in multiple system information blocks (e.g., SIBs).
  • RRC signaling e.g., SIB, paging, RRCReconfiguration, etc.
  • the associated S-5MBSN configuration information can be transmitted in multiple system information blocks (e.g., SIBs).
  • associated S-5MBSN information e.g., S-5MBSN identifier, 5MBS identifier, associated transmission frequency, etc.
  • some other associated S-5MBSN information DRX configuration, 5MBS service continuity bit, etc.
  • those nodes e.g., serving gNB/target gNB/MN/SN
  • those nodes who provide the 5MBS transmission may broadcast the associated S-5MBSN configuration information/change notification in system information (e.g., gNB1 transmits SIB2, or new SIB as shown in FIG. 4 , but not limit to), 5G multicast control channel (5MCCH), and/or paging.
  • system information e.g., gNB1 transmits SIB2, or new SIB as shown in FIG. 4 , but not limit to
  • 5MCCH 5G multicast control channel
  • S-5MBSN identifier/5MBS identifier there is an association between S-5MBSN identifier/5MBS identifier and transmission frequency/period/resource.
  • the S-5MBSN identifier is mapped to an associated/pre-configured transmission frequency.
  • the mapping between S-5MBSN identifier and the associated/pre-configured transmission frequency is provided in the broadcast signaling (e.g., SIB).
  • SIB broadcast signaling
  • only S-5MBSN identifier/5MBS identifier is broadcasted in the broadcast signaling to imply the pre-configured transmission frequency/period/resource.
  • the serving gNB may transmit the associated S-5MBSN configuration information in on-demand system information response (e.g., new SIB), RRC message (e.g., RRCReconfiguration, paging).
  • on-demand system information response e.g., new SIB
  • RRC message e.g., RRCReconfiguration, paging.
  • the on-demand system information (SI) request is a specific preamble required by a UE who is interested to receive the associated 5MBS as shown in FIG. 4 .
  • the on-demand system information response e.g., SIB as shown in FIG. 4
  • the transmitted RRC message (e.g., RRCReconfiguration as shown in FIG.
  • the UE is allowed to prioritize the interested 5MBS frequency upon the reception of SIB carrying the MCCH configuration from the reselected cell. If the reselected cell does not provide MCCH configuration, the UE may apply the stored valid MCCH configuration of the serving cell or may request the on-demand SIB for 5MBS.
  • FIG. 4 illustrates that, in some embodiments, the RRCReconfigurationComplete carrying the associated S-5MBSN configuration complete is transmitted when RRCReconfiguration is used.
  • the S-5MBSN configuration complete is transmitted between S-5MBSN and 5GCN(s) when the S-5MBSN configuration information forwards to UE(s).
  • the UE can be an idle/inactive/connected state UE
  • a gNB1 can be a serving gNB
  • MN master node
  • a gNB2 can be a target gNB or a secondary node (SN).
  • the S-5MBSN configuration procedure is used before/when performing 5MBS handover, 5MBS tracking area update, 5MBS DC, and/or 5MBS DC bearer switching with service continuity.
  • Some 5MBS service continuity (SC) mechanisms are defined in some embodiments of this disclosure. It includes the transmission of 5MBS service continuity indication/bit/request/response/timer.
  • a 5MBS service continuity (SC) indication is used to indicate the interested/duplicate 5MBS transmission of the target gNB or the SN without packet loss. It can be also used as an assistance information for gNB to activate the 5MBS transmission during cell reselection. In some cases, it can be used for PDCP duplication activation when the SN leg is deactivated.
  • the indication is transmitted from the idle/inactive/connected UE to the serving/target gNB or the MN/SN.
  • the 5MBS SC indication may be one bit for SC reception.
  • the 5MBS SC indication may include some information (e.g., the interested 5MBS frequency, the priority of reception frequency, the received end of 5MBS sequence number, the preferred bearer type, the preferred target gNB, etc.) to indicate the gNB(s) for 5MBS service continuity.
  • the NR counting message or 5MBS InterestIndication is used to notify the gNB to count the number of UEs that are interested in the reception of the 5MBS content(s).
  • the UE in the idle/inactive/connected state can transmit the NR counting message or 5MBS InterestIndication via CCCH/MCCH.
  • the gNB may restart a 5MBS SC timer for sustaining 5MBS content transmission.
  • a 5MBS service continuity (SC) request is used to require the corresponding information for the continuing/duplicate 5MBS transmission.
  • the request is transmitted from the serving gNB/MN to the target gNB/SN.
  • the request is transmitted from the target gNB/SN to the serving gNB/MN for requiring the associated 5MBS configuration information.
  • the transmitted request information may include some of the proposed S-5MBSN configuration information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI, bearer type, transmission frequency and period, start/end sequence number, 5MBS service continuity bit, UE context information, UE supported/interested frequency, group UE identifier, UE's mobility restriction, DRX configuration, etc.) when the S-5MBSN configuration procedure is not performed.
  • the transmitted information may include the 5MBS service continuity bit and the end sequence number to activate the continuing/duplicate 5MBS transmission when the S-5MBSN configuration procedure is performed.
  • the request is from the serving gNB/target gNB/MN/SN to the target gNB/serving gNB/SN/MN respectively.
  • the 5MBS service continuity (SC) response is used to reply the corresponding information for the continuing/duplicate 5MBS transmission.
  • the response is transmitted from the target gNB/SN to the serving gNB/MN.
  • the response is transmitted from the serving gNB/MN to the target gNB/SN for replying the associated 5MBS configuration information.
  • the transmitted response information may include some of the proposed S-5MBSN configuration information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI, bearer type, transmission frequency and period, start/end sequence number, 5MBS service continuity bit, UE context information, UE supported/interested frequency, group UE identifier, UE's mobility restriction, DRX configuration, etc.) and/or some other reject/modify information (e.g., suggested bearer type from request) when the S-5MBSN configuration procedure is not performed.
  • the transmitted information may include the confirmation of 5MBS service continuity bit and/or some other reject information when the S-5MBSN configuration procedure is performed.
  • the response is from the target gNB/serving gNB/SN/MN to the serving gNB/target gNB/MN/SN respectively.
  • a 5MBS service continuity (SC) bit is one bit carrying in the inter-node message (e.g., 5MBS SC request, 5MBS SC response, HandoverCommand, HandoverPreparationInformation, CG-Config, CG-ConfigInfo, UERadioPagingInformation, UERadioAccessCapabilityInformation, exchanged S-5MBSN configuration message, etc.). It is used to inform/activate the continuing/duplicate 5MBS transmission.
  • 5MBS SC request e.g., 5MBS SC request, 5MBS SC response, HandoverCommand, HandoverPreparationInformation, CG-Config, CG-ConfigInfo, UERadioPagingInformation, UERadioAccessCapabilityInformation, exchanged S-5MBSN configuration message, etc.
  • a 5MBS service continuity (SC) timer is a timer for gNB(s).
  • the target gNB/candidate gNBs/SN may start the 5MBS SC timer after the reception of a 5MBS SC request from the source gNB/serving gNB/MN and stop the transmission of 5MBS content when the timer is expired.
  • the target gNB/candidate gNBs/SN should stop the transmission of 5MBS content after the timer is expired.
  • the gNB may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • FIG. 5 A and FIG. 5 B illustrate an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • the scenario would be gNBs in the same S-5MBSN using the same 5MBS session for 5MBS handover/tracking area update/dual connectivity/inter-cell bearer switching.
  • the inter-cell bearer switching means 5MBS transmission between PTM and PTP with service continuity (i.e., bearer switching within more than one cell/node) for a given UE(s).
  • FIG. 5 A it is applicable to use cases of UE(s) handover and UE(s) tracking area update.
  • a gNB1 can be a source gNB/serving gNB, and a gNB2 can be a target gNB/candidate gNB.
  • 5MBS handover/tracking area update may performer by a group of UE(s) via PTP or PTM radio bearer.
  • PTP or PTM radio bearer In FIG. 5 B , it is applicable to use cases of inter-cell bearer switching/(de)activation within dual connectivity.
  • the gNB1 and the gNB2 can be MN and SN respectively. Based on the above S-5MBSN configuration and service continuity notification, reliability and service continuity can be supported for 5MBS transmission.
  • a shared-5MBS network (S-5MBSN) is proposed in some embodiments of this disclosure.
  • S-5MBSN configuration procedure is initiated before/when performing 5MBS handover, 5MBS tracking area update, 5MBS DC, and/or 5MBS bearer switching.
  • SC service continuity
  • 5MBS with CA duplication and DC duplication can be used to improve reliability of 5MBS data transmission and achieve service continuity during bearer switching and mobility.
  • the main advantages of the disclosed exemplary methods include lower power consumption for 5MBS reception, better resource efficiency for 5MBS networks, a higher reliability of 5MBS transmission, reliability requirements in MAC/PHY layer which can be relaxed in PDCP duplication, lower data loss which can be expected during handover (for connected UEs), even tracking area update (for idle/inactive UEs), and/or service continuity due to mobility.
  • the processor 11 is configured from at least one of a first base station, a second base station, or a third base station, with a shared-5G multicast and broadcast service network (S-5MBSN) information in a S-5MBSN before a cell reselection
  • the transceiver 13 is configured to receive, from the at least one of the first base station, the second base station, or the third base station, an MBS data in the S-5MBSN during a UE mobility, wherein the S-5MBSN is shared by an inter-cell, an inter node, and/or multiple public land mobile networks (PLMNs), the S-5MBSN provides a same 5MBS session/content, and the same 5MBS session/content is scheduled by the inter-cell, the inter node, and/or the multiple PLMNs independently (i.e., no synchronization).
  • PLMNs public land mobile networks
  • the processor 21 is configured to configure, to one or more user equipments (UEs) 10 , a shared-5G multicast and broadcast service network (S-5MBSN) information in a S-5MBSN before a cell reselection, and the transceiver 23 is configured to transmit, to the one or more UEs 10 , an MBS data in the S-5MBSN during a UE mobility, wherein the S-5MBSN is shared by an inter-cell, an inter node, and/or multiple public land mobile networks (PLMNs), the S-5MBSN provides a same 5MBS session/content, and the same 5MBS session/content is scheduled by the inter-cell, the inter node, and/or the multiple PLMNs independently (i.e., no synchronization).
  • UEs user equipments
  • S-5MBSN shared-5G multicast and broadcast service network
  • FIG. 6 illustrates a method 200 of wireless communication for multicast and broadcast service (MBS) performed by a UE according to an embodiment of the present disclosure.
  • the method 200 includes: a block 202 , being configured, from at least one of a first base station, a second base station, or a third base station, with a shared-5G multicast and broadcast service network (S-5MBSN) information in a S-5MBSN before a cell reselection, and a block 204 , receiving, from the at least one of the first base station, the second base station, or the third base station, an MBS data in the S-5MBSN during a UE mobility, wherein the S-5MBSN is shared by an inter-cell, an inter node, and/or multiple public land mobile networks (PLMNs), the S-5MBSN provides a same 5MBS session/content, and the same 5MBS session/content is scheduled by the inter-cell, the inter node, and/or the multiple PLMNs independently (i.e., no
  • FIG. 7 illustrates a method 300 of wireless communication for multicast and broadcast service (MBS) performed by a first base station according to an embodiment of the present disclosure.
  • the method 300 includes: a block 302 , configuring, to one or more user equipments (UEs), a shared-5G multicast and broadcast service network (S-5MBSN) information in a S-5MBSN before a cell reselection, and a block 304 , transmitting, to the one or more UEs, an MBS data in the S-5MBSN during a UE mobility, wherein the S-5MBSN is shared by an inter-cell, an inter node, and/or multiple public land mobile networks (PLMNs), the S-5MBSN provides a same 5MBS session/content, and the same 5MBS session/content is scheduled by the inter-cell, the inter node, and/or the multiple PLMNs independently (i.e., no synchronization).
  • UEs user equipments
  • S-5MBSN shared-5G multicast and broadcast service network
  • FIG. 8 illustrates an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • a UE is an RRC_Connected UE
  • a gNB1 is a source gNB
  • a gNB2 is a target gNB for 5MBS SC UE handover.
  • a UE-initiated or gNB1-initiated S-5MBSN configuration procedure is performed.
  • a S-5MBSN configuration information is exchanged between the gNB1 and the gNB2, and then an S-5MBSN is setup.
  • the configuration threshold may be pre-configured or configured in initial radio access phase, and it is associated with 5MBS QoS requirement and/or channel quality.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, UE's mobility restriction, CAG ID, etc. If the gNB2 accepts to join the S-5MBSN, it would start to buffer the 5MBS content for achieving 5MBS QoS (e.g., reliability) requirement and service continuity.
  • 5MBS QoS e.g., reliability
  • the gNB1 transmits the 5MBS SC request with SC bit and the end of transmitted 5MBS sequence number to the gNB2.
  • FIG. 8 illustrates that, in some embodiments, the gNB2 may buffer at least the end of 5MBS sequence number of 5MBS content and start to broadcast the 5MBS content for the UE.
  • the gNB2 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired.
  • the gNB2 should stop the transmission of 5MBS content after the timer is expired. Then the gNB2 responds the 5MBS SC response with the related accepted 5MBS SC handover information (e.g., target transmitted frequency and period).
  • the gNB1 transmits the 5MBS SC handover (HO) command (e.g., with the target transmitted frequency and period) for SC configuration.
  • the 5MBS SC HO command may transmit by RRCReconfiguration to inform the UE for performing 5MBS SC UE handover.
  • the UE may transmit the 5MBS SC HO complete (e.g., RRCReconfigurationComplete) with SC indication/the end of received 5MBS sequence number to the gNB1/gNB2 ( FIG. 8 only shows the message is sent to gNB2).
  • the UE detects the boundary of source or target gNB by some of S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC HO complete for service continuity. Then the UE path switching is performed by S-5MBSN and 5MBS system.
  • the 5MBS content is transmitted continuously during the 5MBS SC UE handover.
  • the 5MBS SC HO complete (e.g., RRCReconfigurationComplete) with SC indication/the end of received 5MBS sequence number is transmitted to the gNB1.
  • the UE path switching is performed by S-5MBSN and 5MBS system.
  • the UE detects the boundary of target gNB based on some of received S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, or the other UL feedback) to the gNB2 for 5MBS SC HO.
  • S-5MBSN information e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI
  • the 5MBS content is transmitted continuously during the 5MBS SC HO.
  • the gNB2 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • the gNB1 and gNB2 may unicast or broadcast the 5MBS content for the UE.
  • the transmitted 5MBS SC HO command and 5MBS SC HO complete is unicast signaling.
  • FIG. 9 illustrates an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • the UE is an RRC_Connected UE
  • the gNB1 is a source gNB
  • the gNB2 is a target gNB for 5MBS SC UE handover.
  • the UE-initiated or gNB1-initiated S-5MBSN configuration procedure as above is performed.
  • the S-5MBSN configuration information is exchanged between the gNB1 and the gNB2 after UE measurement report, and then the S-5MBSN is setup.
  • the configuration threshold may be pre-configured or configured in initial radio access phase, and it is associated with 5MBS QoS requirement and/or channel quality.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, UE's mobility restriction, CAG ID, etc.
  • the gNB2 accepts to join the S-5MBSN, it would start to buffer the 5MBS content for achieving 5MBS QoS (e.g., reliability) requirement and service continuity.
  • the 5MBS SC UE handover condition is met (e.g., UE detects the boundary of gNB1/gNB2/S-5MBSN), the UE transmits the 5MBS SC indication to the gNB1 for initiating 5MBS SC UE handover.
  • the gNB1 transmits the 5MBS SC request with SC bit and the end of transmitted 5MBS sequence number to the gNB2.
  • the gNB2 may buffer at least the end of 5MBS sequence number of 5MBS content and start to broadcast the 5MBS content for the UE.
  • the gNB2 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired.
  • the gNB2 should stop the transmission of 5MBS content after the timer is expired. Then the gNB2 responds the 5MBS SC response with the related accepted 5MBS SC handover information (e.g., target transmitted frequency and period).
  • the gNB1 transmits the 5MBS SC HO command (e.g., with the target transmitted frequency and period) for SC configuration.
  • the 5MBS SC HO command may transmit by RRCReconfiguration to inform the UE for performing 5MBS SC UE handover.
  • the UE may transmit the 5MBS SC HO complete (e.g., RRCReconfigurationComplete) with SC indication/the end of received 5MBS sequence number to the gNB1/gNB2 ( FIG. 9 only shows the message is sent to gNB2).
  • the UE detects the boundary of source or target gNB by some of S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC HO complete for service continuity. Then the UE path switching is performed by S-5MBSN and 5MBS system.
  • the 5MBS content is transmitted continuously during the 5MBS SC UE handover.
  • the 5MBS SC HO complete (e.g., RRCReconfigurationComplete) with SC indication/the end of received 5MBS sequence number is transmitted to the gNB1.
  • the UE path switching is performed by S-5MBSN and 5MBS system.
  • the UE detects the boundary of target gNB based on some of received S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, or the other UL feedback) to the gNB2 for 5MBS SC HO.
  • S-5MBSN information e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI
  • the 5MBS content is transmitted continuously during the 5MBS SC HO.
  • the gNB2 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • the gNB1 and gNB2 may unicast or broadcast the 5MBS content for the UE.
  • the transmitted 5MBS SC indication and 5MBS SC HO complete is unicast to the gNBs separately.
  • the 5MBS HO command is unicast signaled to the UE.
  • FIG. 10 illustrates an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • UEs i.e., at least one UE
  • a gNB1 is a source gNB
  • a gNB2 is a target gNB for 5MBS SC group handover.
  • a group of UEs requiring the same 5MBS content may be pre-configured with a group UE identifier.
  • the UE-initiated or gNB1-initiated S-5MBSN configuration procedure as above is performed.
  • the S-5MBSN configuration information is exchanged between the gNB1 and the gNB2, and then the S-5MBSN is setup.
  • the configuration threshold may be pre-configured or configured in initial radio access phase, and it is associated with 5MBS QoS requirement and/or channel quality.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, group UE identifier, UE's mobility restriction, etc. If the gNB2 accepts to join the S-5MBSN, it would start to buffer the 5MBS content for achieving 5MBS QoS (e.g., reliability) requirement and service continuity.
  • 5MBS QoS e.g., reliability
  • the gNB1 When the 5MBS UEs handover condition is met (e.g., some UEs close to the cell boundary of gNB1/S-5MBSN), the gNB1 transmits the 5MBS SC request with SC bit and the transmitted started sequence number to the gNB2. Furthermore, if this embodiment is applicable to 5G private networks, setting S-5MBSN and the 5MBS SC group handover condition should take the group of UEs' mobility restriction into account.
  • the gNB2 may buffer at least the start of started sequence number of 5MBS content and start to broadcast the 5MBS content for the group of UEs.
  • the gNB2 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired.
  • the gNB2 should stop the transmission of 5MBS content after the timer expired. Then the gNB2 responds the 5MBS SC response with the related accepted 5MBS SC handover information (e.g., target transmitted frequency and period).
  • the gNB1 transmits the 5MBS SC handover (HO) command (e.g., with the target transmitted frequency and period) for SC configuration.
  • the 5MBS SC HO command may transmit by the broadcasted system information to inform the group of UEs for performing 5MBS SC group handover.
  • the UE(s) may transmit the 5MBS SC HO complete (e.g., NR Counting message(s), 5MBS InterestIndication) with SC indication/the end of received 5MBS sequence number to the gNB1/gNB2 ( FIG. 10 only shows the message is sent to gNB2).
  • the UE detects the boundary of source or target gNB by some of S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC HO complete for service continuity. Then the group UEs' path switching is performed by S-5MBSN and 5MBS system.
  • the 5MBS content is transmitted continuously during the 5MBS SC group handover.
  • the 5MBS SC HO complete (e.g., NR Counting for target gNB) with SC indication/the end of received 5MBS sequence number is transmitted to the gNB1.
  • the gNB1 may transmit the 5MBS SC request with SC bit and the transmitted ended sequence number to the gNB2 during UE path switching.
  • the gNB2 may buffer at least the ended sequence number of 5MBS content and start to broadcast the 5MBS content for the group of UEs.
  • the gNB2 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired.
  • the gNB2 should stop the transmission of 5MBS content after the timer is expired.
  • S-5MBSN information e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI
  • the UE can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, or the other UL feedback) to the gNB2 for 5MBS SC HO.
  • the 5MBS content is transmitted continuously during the 5MBS SC HO.
  • the gNB2 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • the gNB1 and gNB2 may unicast or broadcast the 5MBS content for the UEs depending on the number of interests UEs.
  • the transmitted 5MBS SC HO command is broadcasted to the UEs.
  • the 5MBS SC HO complete is unicast signaling.
  • FIG. 11 illustrates an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • the UEs i.e., at least one UE
  • the UEs are a group of RRC_Connected UEs
  • a gNB1 is a source gNB
  • a gNB2 is a target gNB for 5MBS SC group handover.
  • the same 5MBS content required by a group of UEs may be pre-configured with a group UE identifier.
  • the UE-initiated or gNB1-initiated S-5MBSN configuration procedure as above is performed.
  • the S-5MBSN configuration information is exchanged between the gNB1 and the gNB2, and then the S-5MBSN is setup.
  • the configuration threshold may be pre-configured or configured in initial radio access phase, and it is associated with 5MBS QoS requirement and/or channel quality.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, group UE identifier, UE's mobility restriction, etc. If the gNB2 accepts to join the S-5MBSN, it would start to buffer the 5MBS content for achieving 5MBS QoS (e.g., reliability) requirement and service continuity.
  • 5MBS QoS e.g., reliability
  • the UE When the 5MBS SC group handover condition is met (e.g., at least one UE detects the boundary of gNB1/gNB2/S-5MBSN), the UE transmits the 5MBS SC indication (e.g., On-demand system information (SI) request) to the gNB1 for initiating 5MBS SC group handover. Furthermore, if this embodiment is applicable to 5G private networks, setting S-5MBSN and the 5MBS SC group handover condition should take the UEs' mobility restriction into account.
  • the gNB1 transmits the 5MBS SC request with SC bit and the transmitted started sequence number to the gNB2.
  • the gNB2 may buffer at least the start of started sequence number of 5MBS content and start to broadcast the 5MBS content for the group of UEs.
  • the gNB2 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired. It means that if all of the group UEs do not enter in the coverage of gNB2 and/or there is no other UE(s) interests the 5MBS content in gNB2, the gNB2 should stop the transmission of 5MBS content after the timer is expired. Then the gNB2 responds the 5MBS SC response with the related accepted 5MBS SC handover information (e.g., target transmitted frequency and period). The gNB1 transmits the 5MBS SC handover (HO) command (e.g., with the target transmitted frequency and period) for SC configuration.
  • HO 5MBS SC handover
  • the 5MBS SC HO command may transmit by the unicast or broadcasted system information to inform the group of UEs for performing 5MBS SC group handover.
  • the UE(s) may transmit the 5MBS SC HO complete (e.g., NR Counting message(s), 5MBS InterestIndication) with SC indication/the end of received 5MBS sequence number to the gNB1/gNB2 ( FIG. 11 only shows the message is sent to gNB2).
  • the UE When the UE detects the boundary of source or target gNB by some of S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC HO complete for service continuity. Then the group UEs' path switching is performed by S-5MBSN and 5MBS system. The 5MBS content is transmitted continuously during the 5MBS SC group handover. In some cases, the 5MBS SC HO complete (e.g., NR Counting for target gNB) with SC indication/the end of received 5MBS sequence number is transmitted to the gNB1. Then the group UEs' path switching is performed by S-5MBSN and 5MBS system.
  • S-5MBSN information e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI
  • the gNB1 may transmit the 5MBS SC request with SC bit and the transmitted ended sequence number to the gNB2 during UE path switching.
  • the gNB2 may buffer at least the ended sequence number of 5MBS content and start to broadcast the 5MBS content for the group of UEs.
  • the gNB2 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired. It means that if all of the group UEs do not enter in the coverage of gNB2 and/or there is no other UE(s) interests the 5MBS content in gNB2, the gNB2 should stop the transmission of 5MBS content after the timer is expired.
  • the UE When the UE detects the boundary of target gNB based on some of received S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, or the other UL feedback) to the gNB2 for 5MBS SC HO.
  • the 5MBS content is transmitted continuously during the 5MBS SC HO.
  • the gNB2 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • the gNB1 and gNB2 may unicast or broadcast the 5MBS content for the UEs depending on the number of interests UEs.
  • the transmitted 5MBS SC indication e.g., on-demand SI request
  • 5MBS SC HO complete e.g., NR counting message, 5MBS InterestIndication, etc.
  • the 5MBS HO command is broadcasted or unicast signaled to the UE(s) depending on the number of interests UEs.
  • FIG. 12 illustrates an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • the UE is an RRC_Inactive/RRC_Idle UE
  • the gNB1 is a source gNB
  • the gNB2 is a target gNB for 5MBS SC tracking area update (TAU).
  • TAU 5MBS SC tracking area update
  • the UE Upon the reception of RRCResume/RRCRelease from the gNB1, the UE enters in RRC_Inactive/RRC_Idle after performing the above S-5MBSN configuration procedure.
  • the S-5MBSN configuration information is exchanged between the gNB1 and the gNB2, and then the S-5MBSN is setup.
  • the configuration threshold may be pre-configured or configured in initial radio access phase, and it is associated with 5MBS QoS requirement and/or channel quality.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source/candidate transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, UE's mobility restriction, CAG ID, etc. If the gNB2 accepts to join the S-5MBSN, it would start to buffer the 5MBS content for achieving 5MBS QoS (e.g., reliability) requirement and service continuity. The 5MBS content is continued provide to the UE in RRC_Inactive/RRC_Idle for saving power of UE and network resource.
  • 5MBS QoS e.g., reliability
  • the UE When the 5MBS SC UE TAU condition is met (e.g., UE detects the boundary of gNB1/gNB2/S-5MBSN), the UE transmits the 5MBS SC indication/received end of 5MBS sequence number (e.g., in ProximityIndication) to the gNB1 for 5MBS SC TAU. Furthermore, if this embodiment is applicable to 5G private networks, setting S-5MBSN and the 5MBS SC TAU condition should take the UE's mobility restriction into account.
  • the gNB1 transmits the 5MBS SC request with SC bit and the end of transmitted 5MBS sequence number to the gNB2.
  • the gNB2 may buffer at least the end of 5MBS sequence number of 5MBS content and start to broadcast the 5MBS content for the UE.
  • the gNB2 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired. It means that if the UE does not enter in the coverage of gNB2 and/or there is no other UE(s) interests the 5MBS content in gNB2, the gNB2 should stop the transmission of 5MBS content after the timer is expired. Then the UE path switching is performed by S-5MBSN and 5MBS system.
  • the UE When the UE detects the boundary of target gNB based on some of received S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, on-demand SI request, or the other UL feedback) to the gNB2 for 5MBS SC TAU.
  • the 5MBS content is transmitted continuously during the 5MBS SC TAU.
  • the gNB2 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • the gNB1 and gNB2 may unicast or broadcast the 5MBS content for the UE.
  • the transmitted 5MBS SC indication is unicast to the gNBs separately.
  • the UE(s) i.e., at least one UE
  • G-TAU 5MBS SC group TAU
  • the same 5MBS content required by a group of UEs may be pre-configured with a group UE identifier before/when entering RRC_Inactive/RRC_Idle.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source/candidate transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, group UE identifier, UEs' mobility restriction, etc.
  • the 5MBS SC G-TAU condition e.g., at least one UE detects it is leaving or entering the boundary of gNB1/gNB2/S-5MBSN
  • the UE(s) transmits the 5MBS SC indication/received end of 5MBS sequence number (e.g., in ProximityIndication) to the gNB1 for 5MBS SC G-TAU.
  • the gNB1 transmits the 5MBS SC request with SC bit and the transmitted started sequence number to the gNB2.
  • the gNB2 may buffer at least the start of started sequence number of 5MBS content and start to broadcast the 5MBS content for the group of UEs.
  • the gNB2 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired.
  • the gNB2 should stop the transmission of 5MBS content after the timer is expired.
  • the UE(s) can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, on-demand SI request, or the other UL feedback) to the gNB2 for 5MBS SC G-TAU.
  • the 5MBS content is transmitted continuously during the 5MBS SC G-TAU.
  • the gNB2 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • FIG. 13 illustrates an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • the UE is an RRC_Connected UE
  • the gNB1 is a master node (MN)
  • the gNB2/gNB3 is a secondary node (SN) for 5MBS SC dual connectivity (DC) with SN change.
  • the UE-initiated or gNB-initiated S-5MBSN configuration procedure is performed.
  • the configuration threshold may be pre-configured or configured in initial radio access phase, and it is associated with 5MBS QoS requirement and/or channel quality. If the UE supports DC capability, the SN addition procedure is also performed and the above S-5MBSN configuration procedure is integrated with the DC procedure.
  • the S-5MBSN configuration information is exchanged between the gNB1 and the gNB2, and then the S-5MBSN is setup.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, UE's mobility restriction, CAG ID, bearer type, etc.
  • the gNB2 If PDCP duplication is activated and the gNB2 accepts to join the S-5MBSN, it activates the SN leg and starts to duplicate the 5MBS content transmission for achieving 5MBS QoS (e.g., reliability) requirement.
  • the S-5MBSN/SN modification condition e.g., upon the reception of SN measurement report and the UE moves to the cell boundary/the boundary of S-5MBSN, e.g., gNB1/gNB2, FIG. 13 only shows the UE moves to the coverage boundary of gNB2, but not limit to)
  • the gNB2 transmits the 5MBS SC request with end of SN transmitted sequence number/bearer type (e.g., PTM bearer or PTP bearer) to the gNB1.
  • end of SN transmitted sequence number/bearer type e.g., PTM bearer or PTP bearer
  • the gNB1 decides to change the SN to gNB3 for the UE. Furthermore, if this embodiment is applicable to 5G private networks, setting S-5MBSN and the SN modification condition should take the UE's mobility restriction into account.
  • the gNB1 transmits the 5MBS SC request with SC bit/bearer type/end of SN received sequence number to the gNB3.
  • the gNB3 may buffer at least the end of SN 5MBS sequence number of 5MBS content and start to broadcast the 5MBS content for the UE.
  • the gNB3 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired.
  • the gNB3 should stop the transmission of 5MBS content after the timer is expired. Then the gNB3 responds the 5MBS SC response with the related accepted 5MBS SC DC modification information (e.g., new SN transmitted frequency and period).
  • the gNB1 transmits the 5MBS SC response to the gNB2 for SN change.
  • the UE path switching is performed by S-5MBSN and 5MBS system.
  • the 5MBS content is transmitted continuously during the 5MBS SC SN change.
  • the gNB1 transmits the 5MBS SC SN change command (e.g., with new SN transmitted frequency and period) for SC configuration.
  • the 5MBS SC SN change command may transmit by RRCReconfiguration to inform the UE for performing 5MBS SC SN change.
  • the UE may transmit the 5MBS SC SN change complete (e.g., RRCReconfigurationComplete) with SC indication/the end of received SN 5MBS sequence number to the gNB1/gNB3 ( FIG. 13 only shows the message is sent to gNB3).
  • the UE When the UE detects it is entering the boundary of gNB3 with some of S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC SN change complete for service continuity.
  • the 5MBS content is transmitted continuously during the 5MBS SC SN change.
  • PTM bearer and PTP bearer may be transmitted simultaneously in MN/SN depends on QoS requirement, DL loading, number of interests UE, etc.
  • the 5MBS content may be transmitted by PTM bearer of MN and PTP bearer of SN (some other cases may PTM with PTM, PTP with PTM, PTP with PTP).
  • the transmitted bearer type can be exchanged between MN and SN for high reliability consideration.
  • the 5MBS SC SN change complete e.g., RRCReconfigurationComplete
  • SC indication/the end of received 5MBS sequence number is transmitted to the gNB1 for service continuity.
  • the UE When the UE detects the boundary of gNB3 based on some of received S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, or the other UL feedback) to the gNB3 for 5MBS SC SN change.
  • the 5MBS content is transmitted continuously during the 5MBS SC SN change.
  • the gNB3 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • the dual connectivity i.e., MN and SN
  • multiple connectivity i.e., MCG and SCG
  • the UE is configured a S-5MBSN for 5MBS reception with MCG and/or SCG.
  • the path switch for the UE is established.
  • the source gNB1 may stop 5MBS content transmission upon receiving UE context release from the target gNB2.
  • the gNB1, gNB2, and gNB3 may unicast or broadcast the 5MBS content for the UE.
  • the transmitted 5MBS SC SN change command and 5MBS SC SN change complete is unicast signaling.
  • FIG. 14 illustrates an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • the UE is an RRC_Connected UE
  • the gNB1 is a master node (MN)
  • the gNB2/gNB3 is a secondary node (SN) for 5MBS SC dual connectivity (DC) with SN change.
  • the UE-initiated or gNB-initiated S-5MBSN configuration procedure is performed.
  • the configuration threshold may be pre-configured or configured in initial radio access phase, and it is associated with 5MBS QoS requirement and/or channel quality. If the UE supports DC capability, the SN addition procedure is also performed and the above S-5MBSN configuration procedure is integrated with the DC procedure.
  • the S-5MBSN configuration information is exchanged between the gNB1 and the gNB2, and then the S-5MBSN is setup.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, UE's mobility restriction, CAG ID, bearer type, etc.
  • the gNB2 If PDCP duplication is activated and the gNB2 accepts to join the S-5MBSN, it activates the SN leg and starts to duplicate the 5MBS content transmission for achieving 5MBS QoS (e.g., reliability) requirement.
  • the S-5MBSN/SN modification condition e.g., the UE detects the cell boundary/the boundary of S-5MBSN, e.g., gNB1/gNB2, FIG. 14 only shows the UE moves to the coverage boundary of gNB2, but not limit to
  • the UE transmits the 5MBS SC indication (e.g., On-demand system information (SI) request) to the gNB1 for initiating 5MBS SC SN change.
  • SI On-demand system information
  • the gNB1 transmits the 5MBS SC SN change request for SN change to the gNB2.
  • the gNB2 responds the 5MBS SC SN change response with the end of SN transmitted sequence number upon the reception of 5MBS SC SN change request.
  • the gNB1 decides to change the SN to gNB3 for the UE.
  • setting S-5MBSN and the SN modification condition should take the UE's mobility restriction into account.
  • the gNB1 transmits the 5MBS SC request with SC bit/bearer type/end of SN transmitted sequence number to the gNB3.
  • the gNB3 may buffer at least the end of SN 5MBS sequence number of 5MBS content and start to broadcast the 5MBS content for the UE.
  • the gNB3 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer is expired. It means that if the UE does not enter in the coverage of gNB3 and/or there is no other UE(s) interests the 5MBS content in gNB3, the gNB3 should stop the transmission of 5MBS content after the timer is expired. Then the gNB3 responds the 5MBS SC response with the related accepted 5MBS SC DC modification information (e.g., new SN transmitted frequency and period).
  • the related accepted 5MBS SC DC modification information e.g., new SN transmitted frequency and period.
  • the UE path switching is performed by S-5MBSN and 5MBS system.
  • the 5MBS content is transmitted continuously during the 5MBS SC SN change.
  • the gNB1 transmits the 5MBS SC SN change command (e.g., with new SN transmitted frequency and period) for SC configuration.
  • the 5MBS SC SN change command may transmit by system information to inform the UE for performing S-5MBSN update/5MBS SC SN change.
  • the UE may transmit the 5MBS SC SN change complete (e.g., in NR counting, 5MBS InterestIndication, or the other UL feedback) with SC indication/the end of received SN 5MBS sequence number to the gNB1/gNB3 ( FIG. 14 only shows the message is sent to gNB3).
  • the UE When the UE detects the boundary of gNB3 with some of S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC SN change complete for service continuity.
  • the 5MBS content is transmitted continuously during the 5MBS SC SN change.
  • PTM bearer and PTP bearer may be transmitted simultaneously in MN/SN depends on QoS requirement, DL loading, number of interests UE, etc.
  • the 5MBS content may be transmitted by PTM bearer of MN and PTP bearer of SN (some other cases may PTM with PTM, PTP with PTM, PTP with PTP).
  • the transmitted bearer type can be exchanged between MN and SN for high reliability consideration.
  • the 5MBS SC SN change complete e.g., in NR counting for new SN, 5MBS InterestIndication, or the other UL feedback
  • SC indication/the end of received 5MBS sequence number is transmitted to the gNB1 for service continuity.
  • the UE When the UE detects the boundary of gNB3 based on some of received S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, or the other UL feedback) to the gNB3 for 5MBS SC SN change.
  • the 5MBS content is transmitted continuously during the 5MBS SC SN change.
  • the gNB3 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • the dual connectivity i.e., MN and SN
  • multiple connectivity i.e., MCG and SCG
  • the UE is configured a S-5MBSN for 5MBS reception with MCG and/or SCG.
  • the path switch for the UE is established.
  • the source gNB1 may stop 5MBS content transmission upon receiving UE context release from the target gNB2.
  • the gNB1, gNB2, and gNB3 may unicast or broadcast the 5MBS content for the UE.
  • the transmitted 5MBS SC SN change command and 5MBS SC SN change complete is unicast signaling.
  • FIG. 15 illustrates an architecture of 5MBS service continuity according to an embodiment of the present disclosure.
  • the UE is an RRC_Connected UE
  • the gNB1 is a master node (MN)
  • the gNB2/gNB3 is a secondary node (SN) for 5MBS SC dual connectivity (DC) with SN change and bearer switching.
  • the UE initially connects to the gNB1 acting as the MN and reports to the MN periodically/triggered by event.
  • the UE-initiated or gNB-initiated S-5MBSN configuration procedure as above is performed.
  • the configuration threshold may be pre-configured or configured in initial radio access phase, and it is associated with 5MBS QoS requirement and/or channel quality. If the UE supports DC capability, the SN addition procedure is also performed and the above S-5MBSN configuration procedure is integrated with the DC procedure.
  • the S-5MBSN configuration information is exchanged between the gNB1 and the gNB2, and then the S-5MBSN is setup.
  • the exchanged S-5MBSN configuration information may include (but not limit to) S-5MBSN identifier, 5MBS identifier, G-RNTI, source transmitted frequency and period, started 5MBS sequence number, UE context information, UE supported/interested frequency, UE's mobility restriction, CAG ID, bearer type, etc. If PDCP duplication is deactivated and the gNB2 accepts to join the S-5MBSN, it may deactivate the SN leg based on the threshold of leg activation for saving network resource.
  • the 5MBS content is only transmitted by gNB1 although DC for the UE is established.
  • the gNB2 transmits the 5MBS SC SN change request with end of SN transmitted sequence number/bearer type (e.g., PTM bearer or PTP bearer) to the gNB1. Based on the setting S-5MBSN and the SN modification condition, the gNB1 decides to change the SN to gNB3 for the UE.
  • the 5MBS SC SN change request with end of SN transmitted sequence number/bearer type (e.g., PTM bearer or PTP bearer) to the gNB1.
  • the gNB1 decides to change the SN to gNB3 for the UE.
  • the gNB1 transmits the 5MBS SC request with SC bit/bearer type/end of SN received sequence number to the gNB3.
  • the gNB3 may buffer the end of old SN transmitted 5MBS sequence number for 5MBS content for the UE.
  • the gNB3 responds the 5MBS SC response with the related accepted 5MBS SC DC modification information (e.g., new SN transmitted frequency and period).
  • the UE path switching is performed by S-5MBSN and 5MBS system.
  • the 5MBS content is transmitted continuously during the 5MBS SC SN change.
  • the gNB1 transmits the 5MBS SC SN change command (e.g., new SN transmitted frequency and period) for SC configuration.
  • the 5MBS SC SN change command may transmit by RRCReconfiguration to inform the UE for performing 5MBS SC SN change.
  • the UE may transmit the 5MBS SC SN change complete (e.g., RRCReconfigurationComplete) with SC indication/the end of received SN 5MBS sequence number to the gNB1/gNB3 ( FIG. 15 only shows the message is sent to gNB3).
  • the gNB3 may buffer at least the end of received SN 5MBS sequence number of 5MBS content.
  • the gNB1 When the gNB1 decides to deactivate the MN leg, it transmits the 5MBS SC request with SC bit/bearer type/end of MN transmitted sequence number to the gNB3.
  • the gNB3 may transmit the 5MBS content when SN leg is activated.
  • the gNB3 may start a 5MBS SC timer after the reception of 5MBS SC request from gNB1 and stop the transmission of 5MBS content when the timer expiry. It means that if the UE does not enter in the coverage of gNB3 and/or there is no other UE(s) interests the 5MBS content in gNB3, the gNB3 should stop the transmission of 5MBS content after the timer is expired.
  • the gNB1 also transmits the 5MBS SC leg modification command (e.g., MN leg deactivation and 5MBS bearer switching) for SC configuration.
  • the 5MBS SC leg modification command may transmit by RRCReconfiguration to inform the UE for performing 5MBS SC leg modification.
  • the UE detects the gNB3 with some of S-5MBSN information (e.g., S-5MBSN identifier, 5MBS identifier, G-RNTI) belonging to the stored S-5MBSN, the UE can transmit the 5MBS SC leg modification complete (e.g., in RRCReconfigurationComplete) for service continuity.
  • the 5MBS content is transmitted continuously during the 5MBS SC leg modification.
  • PTM bearer or PTP bearer is transmitted in MN/SN depends on QoS requirement, DL loading, number of interests UE, etc.
  • the 5MBS content may be transmitted by PTP bearer of MN or PTM bearer of SN.
  • the transmitted bearer type can be exchanged between MN and SN for high reliability consideration.
  • the UE when the 5MBS SC leg modification command is transmitted by System information to inform the UE for performing 5MBS SC leg modification, the UE can transmit the 5MBS SC indication/received end of 5MBS sequence number (e.g., in NR counting, 5MBS InterestIndication, or the other UL feedback) to the gNB3 for 5MBS SC leg modification.
  • the 5MBS content is transmitted continuously during the 5MBS SC leg modification.
  • the gNB3 may stop/restart the 5MBS SC timer for sustaining 5MBS content transmission.
  • the dual connectivity i.e., MN and SN
  • multiple connectivity i.e., MCG and SCG
  • the UE is configured a S-5MBSN for 5MBS reception with MCG and/or SCG.
  • the path switch for the UE is established.
  • the source gNB1 may stop 5MBS content transmission upon receiving UE context release from the target gNB2.
  • the gNB1, gNB2, and gNB3 may unicast or broadcast the 5MBS content for the UE.
  • the transmitted 5MBS SC SN change command, 5MBS SC leg modification command, 5MBS SC SN change complete, 5MBS SC leg modification complete is unicast signaling.
  • the gNB1, the gNB2, and the gNB3 may adopt the RAN functional split.
  • the related gNB-CU/gNB-DU UE F1AP identifier and parameters in the 5MBS transmission may be used.
  • the same 5MBS frequency can be adopted between the inter-cell within the same gNB-DU/gNB-CU for 5MBS transmission.
  • a procedure related to the 5MBS HO/5MBS TAU/5MBS DC transmission/5MBS bearer switching in DC scenario is performed as the aforesaid embodiments, wherein the RRC message proposed in the above embodiments is encapsulated in the F1AP message(s) (e.g., UE Context Modification, DL/UL RRC Message Transfer, etc.) and will not be described again.
  • the RRC message proposed in the above embodiments is encapsulated in the F1AP message(s) (e.g., UE Context Modification, DL/UL RRC Message Transfer, etc.) and will not be described again.
  • Some embodiments of the present disclosure are a combination of “techniques/processes” that can be adopted in 3GPP specification to create an end product. Some embodiments of the present disclosure could be adopted in the 5G NR licensed and non-licensed or shared spectrum communications. Some embodiments of the present disclosure propose technical mechanisms.
  • FIG. 16 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software.
  • FIG. 16 illustrates the system 700 including a radio frequency (RF) circuitry 710 , a baseband circuitry 720 , an application circuitry 730 , a memory/storage 740 , a display 750 , a camera 760 , a sensor 770 , and an input/output (I/O) interface 780 , coupled with each other at least as illustrated.
  • the application circuitry 730 may include a circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors.
  • the processors may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system.
  • the baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processors may include a baseband processor.
  • the baseband circuitry may handle various radio control functions that enables communication with one or more radio networks via the RF circuitry.
  • the radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc.
  • the baseband circuitry may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuit
  • the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency.
  • baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
  • the RF circuitry 710 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency.
  • RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.
  • the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and/or the application circuitry.
  • “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality.
  • ASIC Application Specific Integrated Circuit
  • the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules.
  • some or all of the constituent components of the baseband circuitry, the application circuitry, and/or the memory/storage may be implemented together on a system on a chip (SOC).
  • SOC system on a chip
  • the memory/storage 740 may be used to load and store data and/or instructions, for example, for system.
  • the memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)), and/or non-volatile memory, such as flash memory.
  • DRAM dynamic random access memory
  • flash memory non-volatile memory
  • the I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system.
  • User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc.
  • Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.
  • the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system.
  • the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit.
  • the positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.
  • GPS global positioning system
  • the display 750 may include a display, such as a liquid crystal display and a touch screen display.
  • the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, an AR/VR glasses, etc.
  • system may have more or less components, and/or different architectures.
  • methods described herein may be implemented as a computer program.
  • the computer program may be stored on a storage medium, such as a non-transitory storage medium.
  • the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways.
  • the above-mentioned embodiments are exemplary only.
  • the division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped.
  • the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms.
  • the units as separating components for explanation are or are not physically separated.
  • the units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.
  • the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer.
  • the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product.
  • one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product.
  • the software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure.
  • the storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other kinds of media capable of storing program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
US18/303,559 2020-10-20 2023-04-19 Apparatus and method of wireless communication for mbs Pending US20230262531A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/303,559 US20230262531A1 (en) 2020-10-20 2023-04-19 Apparatus and method of wireless communication for mbs

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US202063093842P 2020-10-20 2020-10-20
PCT/CN2021/124909 WO2022083618A1 (en) 2020-10-20 2021-10-20 Apparatus and method of wireless communication for mbs
US18/303,559 US20230262531A1 (en) 2020-10-20 2023-04-19 Apparatus and method of wireless communication for mbs

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/124909 Continuation WO2022083618A1 (en) 2020-10-20 2021-10-20 Apparatus and method of wireless communication for mbs

Publications (1)

Publication Number Publication Date
US20230262531A1 true US20230262531A1 (en) 2023-08-17

Family

ID=81291565

Family Applications (2)

Application Number Title Priority Date Filing Date
US18/303,559 Pending US20230262531A1 (en) 2020-10-20 2023-04-19 Apparatus and method of wireless communication for mbs
US18/303,597 Pending US20230262532A1 (en) 2020-10-20 2023-04-20 Apparatus and method of wireless communication for mbs

Family Applications After (1)

Application Number Title Priority Date Filing Date
US18/303,597 Pending US20230262532A1 (en) 2020-10-20 2023-04-20 Apparatus and method of wireless communication for mbs

Country Status (4)

Country Link
US (2) US20230262531A1 (zh)
CN (2) CN116746168A (zh)
TW (2) TW202224454A (zh)
WO (2) WO2022083647A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2622352A (en) * 2022-05-23 2024-03-20 Nec Corp Communication System
WO2023236194A1 (en) * 2022-06-10 2023-12-14 Apple Inc. Multicast and broadcast services in radio access network sharing deployments

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101674186B (zh) * 2008-09-12 2012-02-08 中兴通讯股份有限公司 多播业务与单播业务的复用方法及装置
KR20120123914A (ko) * 2011-05-02 2012-11-12 주식회사 팬택 Ｍｂｍｓ 서비스의 연속성을 위한 제어정보의 전송장치 및 방법
EP3473027B1 (en) * 2016-06-15 2021-09-22 Apple Inc. Services provisioning for internet-of-things devices in cellular networks

Also Published As

Publication number Publication date
WO2022083647A1 (en) 2022-04-28
US20230262532A1 (en) 2023-08-17
TW202224454A (zh) 2022-06-16
CN116746168A (zh) 2023-09-12
TW202224455A (zh) 2022-06-16
CN116711371A (zh) 2023-09-05
WO2022083618A1 (en) 2022-04-28

Similar Documents

Publication Publication Date Title
WO2018050121A1 (zh) 一种车联网业务处理方法、装置及车联网系统
US20230262531A1 (en) Apparatus and method of wireless communication for mbs
US20150341494A1 (en) Method, system, base station and cluster EPC for establishing group call context
WO2021056596A1 (zh) 一种寻呼方法及装置
CN108029051B (zh) 通过支持公共安全服务的终端重选空闲模式小区的方法和装置
EP3713153B1 (en) Method and apparatus for group communication in wireless communication system
CN112866982B (zh) 一种寻呼方法及装置
CN113661722B (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2022027537A1 (en) Apparatus and method for multicast/broadcast service
US20230015209A1 (en) Apparatus and method of wireless communication
WO2022012526A1 (zh) 处理方法、发送方法及相关设备
CN116391408A (zh) 动态切换多播和广播服务（mbs）数据包传送模式的方法和装置
CN114342421A (zh) 一种业务数据传输方法及装置、终端设备
WO2024066901A1 (zh) 一种通信的方法和装置
WO2023202386A1 (zh) 一种通信方法及装置
US20240163865A1 (en) User equipment, base station, and wireless communication method
US20230269758A1 (en) Managing multicast and broadcast services
WO2024066858A1 (zh) 一种通信的方法和装置
WO2023201694A1 (en) Method, device and computer storage medium of communication
US20240080645A1 (en) Communication control method
WO2024017374A1 (en) Cell reselection method for mbs service continuity, method for providing mbs service continuity, and related devices
WO2022194113A1 (zh) 一种被用于无线通信的方法和设备
US20230189299A1 (en) Communication control method
US20240008128A1 (en) Systems and method for configuring user equipments for multicast reception in a wireless communication system
CN117835163A (zh) 一种通信的方法和装置

Legal Events

Date Code Title Description
AS Assignment

Owner name: PURPLEVINE INNOVATION COMPANY LIMITED, CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CHEN, CHIU-WEN;REEL/FRAME:063383/0726

Effective date: 20230418

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION