WO2024096502A1 - Procédé et dispositif de prise en charge d'une transmission de service de multidiffusion - Google Patents

Procédé et dispositif de prise en charge d'une transmission de service de multidiffusion Download PDF

Info

Publication number
WO2024096502A1
WO2024096502A1 PCT/KR2023/017066 KR2023017066W WO2024096502A1 WO 2024096502 A1 WO2024096502 A1 WO 2024096502A1 KR 2023017066 W KR2023017066 W KR 2023017066W WO 2024096502 A1 WO2024096502 A1 WO 2024096502A1
Authority
WO
WIPO (PCT)
Prior art keywords
mbs
message
base station
multicast
information
Prior art date
Application number
PCT/KR2023/017066
Other languages
English (en)
Inventor
Hong Wang
Lixiang Xu
Weiwei Wang
Original Assignee
Samsung Electronics 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 Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2024096502A1 publication Critical patent/WO2024096502A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • 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
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • 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
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components

Definitions

  • the application relates to wireless communication technology, and specifically, to a method and device for an improved multicast service transmission.
  • 5G mobile communication technologies define broad frequency bands such that high transmission rates and new services are possible, and can be implemented not only in “Sub 6GHz” bands such as 3.5GHz, but also in “Above 6GHz” bands referred to as mmWave including 28GHz and 39GHz.
  • 6G mobile communication technologies referred to as Beyond 5G systems
  • terahertz bands for example, 95GHz to 3THz bands
  • IIoT Industrial Internet of Things
  • IAB Integrated Access and Backhaul
  • DAPS Dual Active Protocol Stack
  • 5G baseline architecture for example, service based architecture or service based interface
  • NFV Network Functions Virtualization
  • SDN Software-Defined Networking
  • MEC Mobile Edge Computing
  • multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), array antennas and large-scale antennas, metamaterial-based lenses and antennas for improving coverage of terahertz band signals, high-dimensional space multiplexing technology using OAM (Orbital Angular Momentum), and RIS (Reconfigurable Intelligent Surface), but also full-duplex technology for increasing frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technology for implementing system optimization by utilizing satellites and AI (Artificial Intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at levels of complexity exceeding the limit of UE operation capability by utilizing ultra-high-performance communication and computing resources.
  • FD-MIMO Full Dimensional MIMO
  • OAM Organic Angular Momentum
  • RIS Reconfigurable Intelligent Surface
  • the 5G or pre-5G communication system is also called “beyond 4G network” or "post LTE system”
  • Wireless communication is one of the most successful innovations in modern history. Recently, a number of subscribers of wireless communication services has exceeded 5 billion, and it continues growing rapidly. With the increasing popularity of smart phones and other mobile data devices (such as tablet computers, notebook computers, netbooks, e-book readers and machine-type devices) in consumers and enterprises, a demand for wireless data services is growing rapidly. In order to meet rapid growth of mobile data services and support new applications and deployments, it is very important to improve efficiency and coverage of wireless interfaces.
  • MBS Multicast and Broadcast Service
  • MBS Multicast and Broadcast Service
  • an aspect of the present invention provides a method and apparatus for supporting a multicast service transmission.
  • a method performed by a second node in a wireless communication system including: receiving, from a first node, a first message carrying related information of a UE in an RRC inactive state; and processing based on the first message.
  • the related information of the UE in the RRC inactive state includes one of: an identifier of the UE; a number of UEs; indication information that there is the UE in the RRC inactive state; a session identifier of an MBS that the UE joins; state information of the MBS; configuration information of an MBS radio bearer (MRB); an area range; indication information of whether to support the UE in the RRC inactive state to receive an MBS service; indication information that MBS context information and/or configuration information continues to be maintained.
  • MBS radio bearer MBS radio bearer
  • the area range is a RAN paging range or a predetermined list of cells.
  • the second node belongs to a same area range as the first node.
  • the indication information that there is the UE in the RRC inactive state indicates that there is the UE in the RRC inactive state in a range of the first node or in an area range to which the first node belongs.
  • the first message is a UE-specific message.
  • the first message is one of:
  • the processing includes at least one of: maintaining, by the second node, UE context information; maintaining, by the second node, MBS context information; continuing, by the second node, a multicast data transmission; not releasing, by the second node, a signaling resource and/or a user plane resource of a multicast service; not initiating a multicast context release request message or not distributing a release command message to the first node by the second node.
  • a number of the UE in the RRC inactive state is at least 1.
  • the UE in the RRC inactive state is at the first node or an area range to which the first node belongs.
  • the processing further includes at least one of: transmitting, to a core network, a request to establish a user plane; transmitting, to a third node, a third message carrying the related information of the UE in the RRC inactive state; transmitting, to the first node, a second message carrying the related information of the UE in the RRC inactive state.
  • the third message includes the related information of the UE in the RRC inactive state of the second node and/or related information of the UE in the RRC inactive state of other received nodes.
  • a number of the other received nodes is at least 1.
  • the second node receives, from the third node, a response message carrying the related information of the UE in the RRC inactive state of the third node.
  • MRB configuration information carried in the response message is the same as that carried in the third message.
  • the second node is a base station, a distributed unit (DU) or a central unit (CU), and the first node is a base station or a central unit (CU).
  • DU distributed unit
  • CU central unit
  • a method performed by a second node in a wireless communication system including: receiving, from a first node, a first message carrying indication information of whether the first node can enable a UE in an RRC inactive state to receive an MBS service; transmitting a second message to the first node.
  • the second message carries indicating whether the second node supports the UE in the RRC inactive state to receive the MBS service.
  • a node device in a wireless communication network including: a transceiver; and a processor coupled with the transceiver and configured to perform the methods as described according to the embodiments.
  • the present invention provides a method and device for a multicast service transmission.
  • the method and device for the enhanced broadcast and multicast service transmission can enable the UE to receive multicast data in the RRC inactive state, ensure the continuous reception of data, and achieve the purpose of saving power for the UE.
  • Fig. 1 is a system architecture diagram of system architecture evolution (SAE);
  • Fig. 2 is a schematic diagram of an initial overall architecture of 5G
  • Fig. 3 is an example of a first embodiment in which a multicast service transmission is supported according to an embodiment of the present invention
  • Fig. 4 is an example of a second embodiment in which a multicast service transmission is supported according to an embodiment of the present invention
  • Fig. 5 is an example of a third embodiment in which a multicast service transmission is supported according to an embodiment of the present invention
  • Fig. 6 is an example of a fourth embodiment in which a multicast service transmission is supported according to an embodiment of the present invention.
  • Fig. 7 is an example of a fifth embodiment in which a multicast service transmission is supported according to an embodiment of the present invention.
  • Fig. 8 is an example of a sixth embodiment in which a multicast service transmission is supported according to an embodiment of the present invention.
  • Fig. 9 is an example of a seventh embodiment in which a multicast service transmission is supported according to an embodiment of the present invention.
  • Fig. 10 is a block diagram of a network node device according to an embodiment of the present invention.
  • Fig. 11 is a structure of a user equipment (UE) to which embodiments of the disclosure can be applied.
  • Fig. 12 is a structure of a base station in a wireless communication system to which embodiments of the disclosure can be applied.
  • Couple and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with one another.
  • transmit and “communicate,” as well as derivatives thereof, encompass both direct and indirect communication.
  • the term “or” is inclusive, meaning and/or.
  • controller means any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and/or firmware. The functionality associated with any particular controller can be centralized or distributed, whether locally or remotely.
  • phrases "at least one of,” when used with a list of items, means that different combinations of one or more of the listed items can be used, and only one item in the list can be needed.
  • “at least one of: A, B, and C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.
  • “at least one of: A, B, or C” includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A, B and C.
  • various functions described below can be implemented or supported by one or more computer programs, each of which is formed from computer-readable program code and embodied in a computer-readable medium.
  • application and “program” refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer-readable program code.
  • computer-readable program code includes any type of computer code, including source code, object code, and executable code.
  • computer-readable medium includes any type of medium capable of being accessed by a computer, such as Read-Only Memory (ROM), Random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • CD Compact Disc
  • DVD Digital Video Disc
  • a "non-transitory” computer-readable medium excludes wired, wireless, optical, or other communication links that transport transitory electrical or other signals.
  • a non-transitory computer-readable medium includes media where data can be permanently stored and media where data can be stored and later overwritten, such as a rewritable optical disc or an erasable memory device.
  • any reference to “an example” or “example”, “an implementation” or “implementation”, “an embodiment” or “embodiment” means that particular elements, features, structures or characteristics described in connection with the embodiment is included in at least one embodiment.
  • the phrases “in one embodiment” or “in one example” appearing in different places in the specification do not necessarily refer to the same embodiment.
  • a portion of something means “at least some of” the thing, and as such may mean less than all of, or all of, the thing.
  • a portion of a thing includes the entire thing as a special case, i.e., the entire thing is an example of a portion of the thing.
  • the technical schemes of the embodiments of the present application can be applied to various communication systems, and for example, the communication systems may include global systems for mobile communications (GSM), code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) systems, general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) systems or new radio (NR) systems, etc.
  • GSM global systems for mobile communications
  • CDMA code division multiple access
  • WCDMA wideband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • TDD LTE time division duplex
  • UMTS universal mobile telecommunications system
  • WiMAX worldwide interoperability for microwave access
  • 5G 5th generation
  • NR new radio
  • the term “include” or “may include” refers to the existence of a corresponding disclosed function, operation or component which can be used in various embodiments of the present disclosure and does not limit one or more additional functions, operations, or components.
  • the terms such as “include” and/or “have” may be construed to denote a certain characteristic, number, step, operation, constituent element, component or a combination thereof, but may not be construed to exclude the existence of or a possibility of addition of one or more other characteristics, numbers, steps, operations, constituent elements, components or combinations thereof.
  • a or B may include A, may include B, or may include both A and B.
  • a method performed by a second node in a wireless communication system including: receiving, from a first node, a first message carrying related information of a UE in an RRC inactive state; and processing based on the first message.
  • the related information of the UE in the RRC inactive state includes one of: an identifier of the UE; a number of UEs; indication information that there is the UE in the RRC inactive state; a session identifier of an MBS that the UE joins; state information of the MBS; configuration information of an MBS radio bearer (MRB); an area range; indication information of whether to support the UE in the RRC inactive state to receive an MBS service; indication information that MBS context information and/or configuration information continues to be maintained.
  • MBS radio bearer MBS radio bearer
  • the area range is a RAN paging range or a predetermined list of cells.
  • the second node belongs to a same area range as the first node.
  • the indication information that there is the UE in the RRC inactive state indicates that there is the UE in the RRC inactive state in a range of the first node or in an area range to which the first node belongs.
  • the first message is a UE-specific message.
  • the first message is one of:
  • the processing includes at least one of: maintaining, by the second node, UE context information; maintaining, by the second node, MBS context information; continuing, by the second node, a multicast data transmission; not releasing, by the second node, a signaling resource and/or a user plane resource of a multicast service; not initiating a multicast context release request message or not distributing a release command message to the first node by the second node.
  • a number of the UE in the RRC inactive state is at least 1.
  • the UE in the RRC inactive state is at the first node or an area range to which the first node belongs.
  • the processing further includes at least one of: transmitting, to a core network, a request to establish a user plane; transmitting, to a third node, a third message carrying the related information of the UE in the RRC inactive state; transmitting, to the first node, a second message carrying the related information of the UE in the RRC inactive state.
  • the third message includes the related information of the UE in the RRC inactive state of the second node and/or related information of the UE in the RRC inactive state of other received nodes.
  • a number of the other received nodes is at least 1.
  • the second node receives, from the third node, a response message carrying the related information of the UE in the RRC inactive state of the third node.
  • MRB configuration information carried in the response message is the same as that carried in the third message.
  • the second node is a base station, a distributed unit (DU) or a central unit (CU), and the first node is a base station or a central unit (CU).
  • DU distributed unit
  • CU central unit
  • a method performed by a second node in a wireless communication system including: receiving, from a first node, a first message carrying indication information of whether the first node can enable a UE in an RRC inactive state to receive an MBS service; transmitting a second message to the first node.
  • the second message carries indicating whether the second node supports the UE in the RRC inactive state to receive the MBS service.
  • a node device in a wireless communication network including: a transceiver; and a processor coupled with the transceiver and configured to perform the methods as described according to the embodiments.
  • Fig. 1 is an exemplary system architecture 100 of system architecture evolution (SAE).
  • UE User equipment
  • E-UTRAN evolved universal terrestrial radio access network
  • E-UTRAN is a radio access network, which includes a macro base station (eNodeB/NodeB) that provides UE with interfaces to access the radio network.
  • a mobility management entity (MME) 103 is responsible for managing mobility context, session context and security information of the UE.
  • MME mobility management entity
  • SGW serving gateway
  • a packet data network gateway (PGW) 105 is responsible for functions of charging, lawful interception, etc., and may be in the same physical entity as the SGW 104.
  • a policy and charging rules function entity (PCRF) 106 provides quality of service (QoS) policies and charging criteria.
  • a general packet radio service support node (SGSN) 108 is a network node device that provides routing for data transmission in a universal mobile telecommunications system (UMTS).
  • UMTS universal mobile telecommunications system
  • a home subscriber server (HSS)109 is a home subsystem of the UE, and is responsible for protecting user information including a current location of the user equipment, an address of a serving node, user security information, and packet data context of the user equipment, etc.
  • Fig. 2 is an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of the present disclosure.
  • User equipment (UE) 201 is a terminal device for receiving data.
  • a next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (a gNB or an eNB connected to 5G core network 5GC, and the eNB connected to the 5GC is also called ng-gNB) that provides UE with interfaces to access the radio network.
  • An access control and mobility management function entity (AMF) 203 is responsible for managing mobility context and security information of the UE.
  • a user plane function entity (UPF) 204 mainly provides functions of user plane.
  • a session management function entity SMF 205 is responsible for session management.
  • a data network (DN) 206 includes, for example, services of operators, access of Internet and service of third parties.
  • An interface between the AMF and the NG-RAN is called an NG-C interface, or an NG interface or an N2 interface.
  • An interface between the UPF and the NG-RAN is called an NG-U interface, or an N3 interface, and signaling between the UE and the AMF is called Non-Access Stratum (NAS) signaling, also called an N1 interface.
  • NAS Non-Access Stratum
  • An interface between base stations is called an Xn interface.
  • MBS Multicast and Broadcast Service
  • MBS services There are two kinds of MBS services, one is a multicast service, in which a UE needs to join the multicast service first, and then when the multicast service starts, if the UE is in a PMM idle mode, a network transmits a paging message to let the UE enter a PMM connected mode to receive the service.
  • a broadcast service in which the UE does not need to join a certain group, and start information and configuration information of the service will be transmitted to the UE by broadcast, and data can be received in all PMM connected modes and PMM idle modes.
  • the base station When the MBS is a broadcast service, the base station transmits the data to the UE by broadcast, and the UE in RRC idle and connected modes can receive the data of the MBS service.
  • information related to MBS is provided by a CU-CP to a Distributed Unit (DU), which generates MBS control messages, and MBS broadcast configuration messages, which are transmitted to the UE through common channels, for example, through MCCH.
  • DU Distributed Unit
  • the CU-CP transmits the related configuration information of the MBS to the UE through an RRC message, and only the UE in the RRC connected mode can receive the data of the MBS service.
  • the power of the UE is limited. In order to save power for the UE, if the UE has no other services, it is not necessary to let the UE be in the radio resource control (RRC) connected mode to receive data, and the UE can enter the RRC inactive state to receive the data of multicast services through discontinuous reception (DRX).
  • RRC radio resource control
  • Nodes involved in the invention are:
  • a first node, a second node and a third node including, but not limited to, at least one of: a source base station, a destination base station, a core network node, a base station Central Unit (CU) (gNB Central Unit, referred to as CU), a base station distributed unit (DU) (gNB distributed Unit, referred to as DU) or a base station central unit user plane (gNB CU-UP, referred to as CU-UP).
  • CU base station Central Unit
  • DU base station distributed unit
  • gNB CU-UP base station central unit user plane
  • Fig. 3 describes a first embodiment in which a multicast service transmission is supported.
  • a first node such as a first base station, saves a context of a UE, which is aimed at one UE.
  • the context of the UE includes an identifier of the UE, capability information of the UE, information of a radio bearer of the UE, and also includes information of a multicast service that the UE joins, such as a multicast session identifier (TMGI) that the UE joins.
  • TMGI multicast session identifier
  • the first base station After the first base station knows the multicast service that the UE joins, if the UE is the first UE to join this service, the first base station initiates a process of establishing a user plane with a core network, that is, transmits a distribution establishment request message to the core network, and the core network transmits a distribution establishment response message to the first base station.
  • the first base station further obtains more information of the multicast service from the core network, such as a serving range of the multicast service, an identification of a QoS flow and quality requirement (QoS) parameters included in the multicast service, and multicast service state information.
  • the multicast service state information indicates whether a service indicated by the TMGI is active or inactive.
  • the first base station saves the information of the multicast service, that is, the context information of the MBS, which is aimed at one MBS service.
  • the first base station transmits a first message to a second node, such as a second base station.
  • the first base station decides that the UE enters an RRC inactive state.
  • the first base station can decide that some UEs enter the RRC inactive state to receive the MBS service according to the UE's capability, whether the UE has other unicast services to receive, a cell load, and a service state of the MBS and so on.
  • the first base station decides an area range, which is a predetermined area configured by an Operation Administration and Maintenance, or a specific area decided by the first base station.
  • the area range is a radio access network (RAN) paging range of the UE, which may include a list of identifiers of a group of cells, or a group of RAN area identifiers.
  • RAN radio access network
  • the base station Even if there are no users in an RRC connected mode and UEs in the RRC inactive state on a certain base station, the base station continues to save the context of the MBS, and continues the transmission of MBS data without releasing the resources of the MBS because other base stations in this area range have UEs in the RRC inactive state. To this end, the first base station transmits a message to the second base station in the area range.
  • the message may be a UE-specific message, such as an inactive UE context establishment request, an inactive UE context modification request, or other names.
  • the message includes an identifier of XnAP allocated by the first base station for the UE, and the message may also include indication information that the UE enters the RRC inactive state.
  • a session identifier of the MBS that the UE joins, state information of the MBS, and configuration information of an MBS radio bearer (MRB) may also be included.
  • the configuration information of the MBS radio bearer includes at least an MRB identifier, and may also include information of a QoS flow, QoS information, a PDCP sequence number (SN) length and so on.
  • the second node belongs to the same area range as the first node.
  • the message transmitted by the first base station to the second base station may also be a message dedicated to MBS multicast, such as a multicast activation request message, a multicast context establishment request message, a multicast context modification request message, a multicast bearer establishment request message, or other names.
  • the message includes the identifier of XnAP allocated by the first base station for the MBS.
  • the message transmitted by the first base station to the second base station may also be a common message, in which case the first message also includes a node identifier of the first base station.
  • the message transmitted by the first base station is used to inform the second base station that there are UEs in the RRC inactive state to receive MBS services in an area range.
  • the first base station may also transmit the message to the second base stations in the area range when the MBS is in an active state.
  • the first base station may know that the MBS is in the active state from the service state of the MBS received by the core network, or when the first base station receives an MBS activation request message transmitted by the core network.
  • the message transmitted by the first base station to the second base station carries related information of the UE in the RRC inactive state, specifically, the message includes one or more of:
  • the identifier of the UE receiving MBS data in the RRC inactive state such as C-RNTI, or RAN UE paging identifier I-RNTI, or an identifier allocated by a first base station for the UE.
  • the identifier of the UE may also be a list of UE identifiers, indicating identifiers of multiple UEs receiving MBS data in the RRC inactive state.
  • the number of UEs receiving MBS data in the RRC inactive state for example, the number of UEs in the RRC inactive state is at least 1.
  • TMGI indicates a multicast session identifier received by the UE in the inactive state.
  • the service state indicates whether the multicast service is in an active state or inactive state.
  • MBS radio bearer an identifier of the MBS radio bearer (MRB), an identifier used to identify a radio bearer that transmits MBS data over the air interface. This is an identifier of a radio bearer allocated by the first base station to transmit the MBS service.
  • the configuration information of the MBS radio bearer includes at least an MRB identifier, and may also include information of a QoS flow, QoS information, RLC information, a PDCP SN length on the MRB and so on.
  • the area range may be a RAN paging range, or a list of identifiers of a group of cells, or an identification of a predetermined range.
  • the area range indicates that there is a UE in the RRC inactive state receiving MBS services in this area.
  • the second base station receives the message and saves the information in the context of the UE or the context of the MBS.
  • the UE served by the second base station has no UE to receive the multicast service, but since there are UEs to receive the multicast service in the area range, if the second base station has not established a user plane for transmitting the MBS service with the core network, the second base station transmits a distribution establishment request message to the core network to establish the user plane of the MBS service between the base station and the core network.
  • the second base station saves the related information of the UE in the RRC inactive state, such as the identifier of the UE or the number of the UEs in the RRC inactive state.
  • the second base station knows that there is a UE in the RRC inactive state to receive the MBS service in the area range, and the second base station does not delete the user plane for receiving the MBS service between the base station and the core network, and continues to transmit the data of the MBS service on the radio bearer of the MBS.
  • the UE in the RRC inactive state may move to the second base station without notifying the second base station, and the second base station saves the received context of the UE in the inactive state, maintain the MBS context information, and continue the multicast data transmission, and cannot release the signaling connection of the MBS and the resources of the user plane.
  • the second base station may refer to the configuration information of the MRB transmitted by the first base station, and the second base station may configure the same MRB to transmit the data of the multicast service.
  • the second base station also broadcasts the configuration information of the MRB for receiving the MBS which is configured for the UE in the inactive RRC state over the air interface.
  • the second base station transmits a second message to the first base station.
  • the second base station transmits the second message to the first base station, which may be a response message of the first message.
  • the message may include the information of the UE in the RRC inactive state saved on the second base station.
  • the second message is also aimed at one UE.
  • the second message includes the identifier of XnAP allocated by the second base station for the UE, and the identifier of XnAP allocated by the first base station for the UE. It also includes the session identifier of the MBS that the UE joins, and the configuration information of the MBS radio bearer (MRB) configured by the second base station for the session.
  • the configuration information is aimed at a certain cell on the second base station, so the second message also includes the identifier of the cell.
  • the configuration information of the MBS radio bearer includes at least the MRB identifier, and may also include the information of the QoS flow, the QoS information, the PDCP sequence number (SN) length and so on.
  • the first base station receives the configuration information of the MBS radio bearer configured by the second base station, and the first base station may include the radio bearer configuration information of the MBS configured by the second base station or a cell on the second base station in broadcast information. That is, the broadcast information of the first base station includes the MBS session identifier, or indication information identifying a certain session, cell identifier of a neighboring cell, and MRB configuration information in the cell.
  • the first base station transmits an RRC reconfiguration request message to the UE, which includes the cell identifier of the neighboring cell and the MRB configuration information for a certain MBS session on the cell.
  • the UE receives the configuration information of the neighboring cell.
  • the UE may continue to receive the MBS data without entering the RRC connected state.
  • the response message includes the identifier of XnAP allocated by the second base station for MBS and the identifier of XnAP allocated by the first base station for MBS. If the message in step 301 is a common message, the second message also includes the node identifier of the second base station. In addition, the second message may include one or more of:
  • the identifier of the UE receiving MBS data in the RRC inactive state such as C-RNTI, or RAN UE paging identifier I-RNTI, or an identifier allocated by a first base station for the UE.
  • the number of UEs receiving MBS data in the RRC inactive state for example, the number of UEs in the RRC inactive state is at least 1.
  • the identifier of the UE may also be a list of UE identifiers, indicating identifiers of multiple UEs receiving MBS data in the RRC inactive state.
  • the identifier of the UE may also be a list of UE identifiers, indicating identifiers of multiple UEs receiving MBS data in the RRC inactive state.
  • TMGI indicates a multicast session identifier received by the UE in the inactive state.
  • the service state indicates whether the multicast service is in an active state or inactive state.
  • MBS radio bearer an identifier of the MBS radio bearer (MRB), an identifier used to identify a radio bearer that transmits MBS data over the air interface.
  • MBS MBS radio bearer
  • the configuration information of the MBS radio bearer includes at least an MRB identifier, and may also include information of a QoS flow, QoS information, RLC information, a PDCP SN length on the MRB and so on.
  • the area range may be a RAN paging range, or a list of identifiers of a group of cells, or an identification of a predetermined range.
  • the area range indicates that there is a UE in the RRC inactive state receiving MBS services in this area.
  • the first base station obtains the information of the UE in the RRC inactive state on the second base station, and saves the information in the context of the MBS.
  • the first base station may refer to the configuration information of the MRB transmitted by the second base station, and the first base station may configure the same MRB to transmit the data of the multicast service.
  • the first base station also broadcasts the configuration information of the MRB for receiving the MBS which is configured for the UE in the inactive RRC state over the air interface.
  • the first base station may delete the user plane with the core network, delete the resources of the MBS radio bearer on the base station, and stop broadcasting the configuration information of the MBS radio bearer over the air interface.
  • the first base station and the second base station prepare MBS resources in advance for the UE in the RRC inactive state to receive multicast data or keep the MBS resources from being deleted, so that the UE normally receives MBS multicast data in the inactive state, and the purpose of saving power for the UE is achieved.
  • Fig. 4 describes a second embodiment in which a multicast service transmission is supported.
  • a first node such as a first base station, saves a context of a UE, and the context of the UE saves information of a multicast service that the UE joins, for example, an identifier TMGI of the multicast service that the UE joins has been saved in the context of the UE.
  • the first base station After the first base station knows the multicast service that the UE joins, if the UE is the first UE to join this service, the first base station initiates a process of establishing a user plane with a core network, that is, transmits a distribution establishment request message to the core network, and the core network transmits a distribution establishment response message to the first base station.
  • the first base station further obtains more information of the multicast service from the core network, such as a serving range of the multicast service, an identification of a QoS flow and quality requirement (QoS) parameters included in the multicast service, and multicast service state information.
  • the multicast service state information indicates whether a service indicated by the TMGI is active or inactive.
  • the first base station saves the information of the multicast service, that is, the context information of the MBS.
  • the first base station transmits a message to a second node, such as a second base station.
  • the first base station decides that the UE enters an RRC inactive state.
  • the first base station can decide that some UEs enter the RRC inactive state to receive the MBS service according to the UE's capability, whether the UE has other unicast services to receive, a cell load, and a service state of the MBS and so on.
  • the first base station is configured with an area range, such as a RAN paging range of a UE, which may include a list of identifiers of a group of cells, or a group of RAN area identifiers, and a central base station is also configured in this area range.
  • the second base station is a central base station. The first base station transmits a message to the second base station.
  • the message may be a UE-specific message, such as an inactive UE context establishment request, an inactive UE context modification request, or other names.
  • the message includes an identifier of F1AP allocated by the first base station for the UE, and the message may also include indication information that the UE enters the RRC inactive state.
  • a session identifier of the MBS that the UE joins, state information of the MBS, and configuration information of an MBS radio bearer (MRB) may also be included.
  • the configuration information of the MBS radio bearer includes at least an MRB identifier, and may also include information of a QoS flow, QoS information, a PDCP sequence number (SN) length and so on.
  • the message transmitted by the first base station to the second base station may also be a message dedicated to the MBS multicast service, such as a multicast context establishment request message or a multicast context modification request message or other names.
  • the message includes an identifier of XnAP allocated by the first base station for MBS.
  • the message transmitted by the first base station to the second base station may also be a common message.
  • the message transmitted by the first base station is used to inform the second base station that there is a UE in the RRC inactive state to receive MBS services in the area range.
  • the first base station may also transmit the message to the second base stations in the area range when the MBS is in an active state.
  • the first base station may know that the MBS is in the active state from the above service state of the MBS, or when the first base station receives an MBS activation request message transmitted by the core network.
  • the message transmitted by the first base station to the second base station carries related information of the UE in the RRC inactive state, specifically, it includes one or more of:
  • the identifier of the UE receiving MBS data in the RRC inactive state such as C-RNTI, or RAN UE paging identifier I-RNTI, or an identifier allocated by a first base station for the UE.
  • the identifier of the UE may also be a list of UE identifiers, indicating identifiers of multiple UEs receiving MBS data in the RRC inactive state.
  • the number of UEs receiving MBS data in the RRC inactive state for example, the number of UEs in the RRC inactive state is at least 1.
  • TMGI indicates a multicast session identifier received by the UE in the inactive state.
  • the service state indicates whether the multicast service is in an active state or inactive state.
  • MBS radio bearer an identifier of the MBS radio bearer (MRB), an identifier used to identify a radio bearer that transmits MBS data over the air interface.
  • MBS MBS radio bearer
  • the configuration information of the MBS radio bearer includes at least an MRB identifier, and may also include information of a QoS flow, QoS information, RLC information, a PDCP SN length on the MRB and so on.
  • the area range may be a RAN paging range, or a list of identifiers of a group of cells, or an identification of a predetermined range.
  • the second base station transmits a message to a third node, such as a third base station.
  • the second base station receives the message and saves the information in the context of the UE or the context of the MBS.
  • the second base station informs other base stations in the area of the information of the UE in the RRC inactive state.
  • the second base station may transmit the message in step 402 to other base stations in a predetermined area.
  • the second base station receives the activation request message transmitted by the core network, and transmits the message in step 402 to other base stations in the predetermined area.
  • the message may include related information of all UEs in the RRC inactive state in a specific area obtained by the second base station. Specifically, the message may include one or more of:
  • the identifier of the UE receiving MBS data in the RRC inactive state such as C-RNTI, or RAN UE paging identifier I-RNTI, or an identifier allocated by a first base station for the UE.
  • the identifier of the UE may also be a list of UE identifiers, indicating identifiers of multiple UEs receiving MBS data in the RRC inactive state.
  • the number of UEs receiving MBS data in the RRC inactive state for example, the number of UEs in the RRC inactive state is at least 1.
  • TMGI indicates a multicast session identifier received by the UE in the inactive state.
  • the service state indicates whether the multicast service is in an active state or inactive state.
  • MBS radio bearer an identifier of the MBS radio bearer (MRB), an identifier used to identify a radio bearer that transmits MBS data over the air interface.
  • MBS MBS radio bearer
  • the configuration information of the MBS radio bearer includes at least an MRB identifier, and may also include information of a QoS flow, QoS information, RLC information, a PDCP SN length on the MRB and so on.
  • the area range may be a RAN paging range, or a list of identifiers of a group of cells, or an identification of a predetermined range.
  • the third base station receives the message and saves the information in the context of the UE or in the context of the MBS. If the third base station has not established the user plane of MBS with the core network, the third base station transmits a distribution establishment request message to the core network to establish the user plane of the MBS service between the base station and the core network.
  • the third base station saves the received information of the inactive UE, such as the identifier of the UE or the number of UEs in the RRC inactive state.
  • the third base station knows that there is a UE in the RRC inactive state to receive the MBS service in the area range, and the third base station does not delete the user plane for receiving the MBS service between the base station and the core network, and continues to transmit the data of the MBS service on the radio bearer of the MBS.
  • the UE in the RRC inactive state may move to the third base station without notifying the third base station, and the third base station cannot release the signaling connection of the MBS and the resources of the user plane.
  • the third base station may refer to the configuration information of the MRB transmitted by the second base station, and the third base station may configure the same MRB to transmit the data of the multicast service.
  • the third base station transmits a response message to the second base station.
  • the third base station may also inform the second base station whether there is an inactive UE receiving the multicast service on the third base station and/or transmitting configuration information of the MRB of the multicast service on the third base station. That is, the information described in the message in step 402 is included.
  • the central base station Through the method of the embodiment, through the central base station, it can be ensured that the base stations in the same area prepare MBS resources in advance for the UE in the RRC inactive state to receive multicast data or keep the MBS resources from being deleted, so that the UE normally receives MBS multicast data in the inactive state, and the purpose of saving power for the UE is achieved.
  • Fig. 5 describes a third embodiment in which a multicast service transmission is supported.
  • a first node such as a central unit CU, saves a context of a UE, and the CU belongs to a part of a separated base station.
  • the base station is divided into the central unit CU and a distributed unit DU, and the CU may be further divided into a control plane (CU-CP) and a user plane (CU-UP).
  • CU-CP control plane
  • CU-UP user plane
  • the following CU may also refer to the CU-CP.
  • the CU saves the context of the UE and the context of the MBS.
  • the context of the UE is aimed at one UE, and the context of the MBS is aimed at one MBS service.
  • the context of the UE includes the identifier of the UE, the capability information of the UE, the information of the radio bearer of the UE, and the information of the multicast service that the UE joins, such as the multicast session identifier TMGI that the UE joins.
  • the multicast service identifier that the UE joins is transmitted to the CU by the core network, for example, the MBS session identifier list is carried by the PDU session resource establishment request message or the PDU session resource modification request message.
  • the CU After knowing the multicast service that the UE joins, if the UE is the first UE to join this service, the CU initiates the process of establishing the user plane between with the core network, that is, the CU transmits a distribution establishment request message to the core network, carries the MBS session identifier and shares the transport layer address information of the NG-U.
  • the core network transmits a distribution establishment response message to the CU, which includes more information of the multicast service, and carries the MBS session identifier, QoS flow identifier and QoS parameters included in the multicast service, and multicast service state information.
  • the multicast service state information indicates whether the service indicated by the TMGI is active or inactive. After obtaining these information, the CU saves the information in the context information of the MBS.
  • the CU transmits a message to a second node, such as a DU.
  • the CU decides that the UE enters an RRC inactive state.
  • the CU can decide that some UEs enter the RRC inactive state to receive the MBS service according to the UE's capability, whether the UE has other unicast services to receive, a cell load, and a service state of the MBS and so on.
  • the CU transmits a message to the DU, which carries the related information of the UE in the RRC inactive state.
  • the message may be a UE-specific message, such as an inactive UE context establishment request, or an inactive UE context modification request, or a UE context modification request message, or other names.
  • the message includes the identifier of F1AP allocated by the CU for the UE, and/or the identifier of F1AP allocated by the DU for the UE, and includes the indication information that UE enters the RRC inactive state. It may also include the session identifier of the MBS that the UE joins, the state information of the MBS, and the configuration information of the MBS radio bearer (MRB).
  • the configuration information of the MBS radio bearer at least includes an MRB identifier.
  • the message transmitted by the CU to the DU may also be a message dedicated to the MBS multicast service, such as a multicast context establishment request message or a multicast context modification request message or other names.
  • the message includes the identifier of F1AP allocated by the CU for MBS and/or the identifier of F1AP allocated by the DU for MBS.
  • the message transmitted by the CU to the DU is used to inform the DU that there is a UE in the RRC inactive state to receive the MBS service in the range of the DU, or in the cell on the DU, or in the MBS multicast service area.
  • the CU may also transmit the message to the DU when the MBS is in the active state.
  • the CU may know that the MBS is in the active state from the service state of the MBS received by the core network, or when the CU receives an MBS activation request message transmitted by the core network.
  • the message transmitted by the CU to the DU carries one or more of:
  • MBS session identifier such as TMGI
  • - area identifier information which may be MBS service area information or identifier information of a cell.
  • RRC inactive users which may be a number of users receiving the MBS service in the RRC inactive state, or a list of identifiers of UEs receiving the MBS service in the RRC inactive state, or indicate that there are RRC inactive users in the range indicated by the area identifier on the DU or the DU.
  • the DU After receiving the information of RRC inactive users, the DU maintains the MBS context information, and does not initiate the multicast context release request message or multicast distribution release request message.
  • the DU Upon receiving the MBS state information, the DU maintains the MBS context information, and does not initiate the multicast context release request message or multicast distribution release request message.
  • the DU maintains the MBS context information, and does not initiate the multicast context release request message or the multicast distribution release request message.
  • the DU Upon receiving the indication information, the DU maintains the MBS context information, and does not initiate the multicast context release request message or the multicast distribution release request message.
  • the configuration information of the MBS radio bearer includes at least an MRB identifier, and may also include information of a QoS flow, QoS information, a PDCP SN length and so on.
  • the DU transmits a response message to the CU.
  • the DU transmits the response message to the CU. If the message in step 501 is a message aimed at the UE, the response message includes the identifier of F1AP allocated by the CU for the UE, and the identifier of F1AP allocated by the DU for the UE.
  • the response message includes the identifier of F1AP allocated by the CU for MBS, and the identifier of F1AP allocated by the DU for MBS.
  • the DU can be allowed to continue to maintain the transmission of MBS data, so that the UE normally receives MBS multicast data in the inactive state, and the purpose of saving power for the UE is achieved.
  • Fig. 6 describes a fourth embodiment in which a multicast service transmission is supported.
  • a first node for example, a central control node CU in an access network, saves a context of a UE and a context of an MBS.
  • the context of the UE is aimed at one UE, and the context of the MBS is aimed at one MBS service.
  • the context of the UE includes the identifier of the UE, the capability information of the UE, the information of the radio bearer of the UE, and the information of the multicast service that the UE joins, such as the multicast session identifier TMGI that the UE joins.
  • the multicast service identifier that the UE joins is transmitted to the CU by the core network, for example, the MBS session identifier list is carried by the PDU session resource establishment request message or the PDU session resource modification request message.
  • the CU After knowing the multicast service that the UE joins, if the UE is the first UE to join this service, the CU initiates the process of establishing the user plane between with the core network, that is, the CU transmits a distribution establishment request message to the core network, carries the MBS session identifier and shares the transport layer address information of the NG-U.
  • the core network transmits a distribution establishment response message to the CU, which includes more information of the multicast service, and carries the MBS session identifier, QoS flow identifier and QoS parameters included in the multicast service, and multicast service state information.
  • the multicast service state information indicates whether the service indicated by the TMGI is active or inactive. After obtaining these information, the CU saves the information in the context information of the MBS.
  • the CU can decide to allow some UEs for MBS to enter the RRC inactive state to receive the data of the MBS service.
  • the CU can decide that some UEs enter the RRC inactive state according to the UE's capability, whether the UE has other unicast services to receive, a cell load, and a service state of the MBS and so on.
  • the UE enters the RRC inactive state, which means that the CU transmits an RRC release request to the UE, and the RRC release request message indicates that the UE will be in the RRC inactive state.
  • the UE can receive the broadcast message and move in the radio access network (RAN) paging range, without notifying the base station.
  • RAN radio access network
  • the UE cannot transmit or receive the data of the unicast service, and the context information of the UE is only saved in the CU.
  • the CU transmits a UE context release request message to the DU to release the UE information on the DU.
  • the CU transmits a message to a second node, such as a DU.
  • the message in step 601 may be the UE context release request, which includes the identifier of F1AP allocated by CU for the UE, the identifier of F1AP allocated by DU for the UE, and the reason for release.
  • the message also includes an MBS session identifier, such as TMGI, and indication information indicating that the MBS session state is the active state on the DU, or indicating that the context information of MBS needs to be maintained, or indicating the DU not to delete the context information of MBS.
  • the context information includes information or resources of the control plane and the user plane.
  • the DU will release the context and resources of the MBS, thus causing the UE in the RRC inactive state to be unable to correctly receive the data of the MBS.
  • the CU judges that, at the time of the last UE context release request or before transmitting the last UE context release request, the CU transmits a message to the DU, informing the DU that the MBS session state on the DU is the active state, or that the context information of the MBS needs to be maintained, or that the DU do not delete the context information of the MBS.
  • the CU may also transmit an MBS related message 600, for example, the name of the message is the multicast modification request message or others, and the message carries one or more of:
  • MBS session identifier such as TMGI
  • - area identifier information which may be MBS service area information or identifier information of a cell.
  • RRC inactive users which may be a number of users receiving the MBS service in the RRC inactive state, or a list of identifiers of UEs receiving the MBS service in the RRC inactive state, or indicate that there are RRC inactive users in the range indicated by the area identifier on the DU or the DU.
  • the DU After receiving the information of RRC inactive users, the DU maintains the MBS context information, and does not initiate the multicast context release request message or multicast distribution release request message.
  • the DU Upon receiving the MBS state information, the DU maintains the MBS context information, and does not initiate the multicast context release request message or multicast distribution release request message.
  • the DU maintains the MBS context information, and does not initiate the multicast context release request message or the multicast distribution release request message.
  • the DU Upon receiving the indication information, the DU maintains the MBS context information, and does not initiate the multicast context release request message or the multicast distribution release request message.
  • DU After receiving the message, DU maintains the multicast context information, and continues the transmission of multicast service data when there is no multicast UE context, and does not initiate the multicast context release request message to the CU or the multicast distribution release request message to the CU.
  • the CU may transmit the message in step 601, UE context release request message, to release the context of the multicast UE saved by the DU. Even if the context of all the UEs to receive the multicast data is released, the DU continues to transmit the multicast service data until the multicast context release request message transmitted by the CU in step 803 is received.
  • the DU transmits a response message to the CU.
  • the DU transmits a response message corresponding to the message in step 601 and confirms that the message in step 601 is received.
  • the CU transmits a multicast context release command message to the DU.
  • the CU can transmit a multicast context release command message to the DU, including the reason for the release.
  • the reason for the release may indicate that no user is to receive the MBS service.
  • no user means that there is neither the UE in the RRC connected mode nor the UE in the RRC inactive mode to receive the MBS service.
  • the DU can delete the context of the MBS, delete the resources of the signaling plane and user plane related to MBS, and stop transmitting control information and user data of the MBS over the air interface.
  • the DU transmits a multicast context release complete message to the CU.
  • the DU Upon receiving the message in step 603, the DU releases all signaling connections and user plane transmission resources related to multicast, and the DU transmits the multicast context release complete message to the CU.
  • the DU can be allowed to continue to maintain the transmission of MBS data, so that the UE normally receives MBS multicast data in the inactive state, and the purpose of saving power for the UE is achieved.
  • Fig. 7 describes a fifth embodiment in which a multicast service transmission is supported.
  • a first node such as a DU
  • a second node such as a CU
  • the DU transmits a message to the CU.
  • Context information of a user to receive an MBS service is saved in the DU, and the identifier of the MBS radio bearer MRB is saved in the context of the UE.
  • a bearer indicated by the MRB identifier is related to an MBS session.
  • the DU Through the multicast context establishment request message transmitted by the CU, the DU knows the relationship between the MBS session and the MRB, and saves this relationship in the context of the MBS.
  • the DU may transmit a message on MBS release in step 701 to the CU, and the message in step 701 may be a multicast context release request message, a distribution release command message, or other message names.
  • the message on MBS release in step 701 that is, the multicast context release request message, or the distribution release command message, or other message names, includes the identifier of F1AP allocated by the CU for MBS, and the identifier of F1AP allocated by the DU for MBS, including the reason for release.
  • the reason for the release may indicate that there is no user to receive the MBS service.
  • the CU can know which MBS service it is, and there is no user on the DU to receive the MBS service.
  • the CU transmits a failure response message to the DU.
  • the CU knows which MBS service it is, and there is no user to receive the MBS service on the DU. For this MBS service, the CU also saves the UE context received by the UE that is to receive the service data and is RRC inactive. Some RRC-inactive UEs need to receive MBS data from the DU, or the CU knows that there are RRC-inactive UEs to receive MBS data in a certain predetermined range, so the CU transmits a failure message as a response message to the message in step 701.
  • the failure response message may carry indication information indicating that there are UEs in the RRC inactive mode, indicating the DU to maintain MBS context information, continue transmission of multicast data, not to release signaling resources and user plane resources of the multicast service, and not to initiate the multicast context release request message or the distribution release command message to the CU.
  • the DU can continue to maintain the transmission of the MBS data, so that the UE normally receive the MBS multicast data in the inactive state, and the purpose of saving power for the UE is achieved.
  • Fig. 8 describes a sixth embodiment in which a multicast service transmission is supported.
  • a CU indicates a DU that the CU supports allowing a UE to enter an RRC inactive state to receive MBS data
  • the DU indicates the CU that the DU supports transmission of multicast data when there is no MBS UE context.
  • a first node such as the DU, transmits an F1 setup request message.
  • the DU starts the setup of the F1 interface by transmitting the F1 SETUP REQUEST message including appropriate data to a second node, such as the CU.
  • the exchanged data are stored in their respective nodes.
  • the F1 interface may run and other F1 messages may be exchanged.
  • the DU should include DU system information and a slice support list in the F1 setup request message, including RAN area codes, and also information of a serving cell.
  • the information of the serving cell includes a physical layer identifier of the cell and a unique identifier of the cell, including all MBS frequency selection area identifiers related to the cell.
  • the F1 setup request message also includes indication information indicating whether the DU has a function of allowing the UE to receive the MBS service in the RRC inactive state.
  • the DU has this function, which can maintain the transmission of multicast data and the multicast context on the DU. Even when the context information of the MBS UE is not saved on the DU, the DU still transmits the multicast data without releasing signaling resources and user plane resources of the multicast service, and the DU does not initiate a multicast context release request message or a distribution release command message to the CU.
  • the indication information may also be included in a DU configuration update request message.
  • the CU transmits an F1 setup response message.
  • the CU responds with the F1 setup response message including appropriate data.
  • the F1 setup response message includes a list of cells to be activated. It also includes indication information indicating whether the CU has the function of allowing the UE to receive the MBS service in the RRC inactive state.
  • the CU has this function, which can decide to allow the UE in the RRC connected mode to enter the RRC inactive state to receive a certain MBS multicast data. In some implementations, the CU has this function, and the CU can decide whether to release resources related to this MBS resource on the CU and DU according to whether there is a UE in the RRC inactive mode receiving MBS in a neighboring cell.
  • the indication information may also be included in the CU configuration update request message.
  • the CU can decide to allow some UEs to enter the RRC inactive state to receive the MBS service, so as to achieve the purpose of saving power for the UE.
  • Fig. 9 describes a seventh embodiment in which a multicast service transmission is supported.
  • a CU indicates a DU that the CU supports allowing a UE to enter an RRC inactive state to receive MBS data, and the DU indicates the CU that the DU supports transmission of multicast data when there is no MBS UE context.
  • the indication information may be aimed at a certain MBS multicast service or all MBS multicast services.
  • a first node such as the CU, transmits a multicast context establishment request message to a second node, such as the DU.
  • the multicast context establishment request message includes the identifier of F1AP allocated by the CU for MBS, including a multicast session identifier, a multicast serving range and configuration information of a multicast radio bearer to be established.
  • the message also includes indication information indicating that the CU supports or enables or configures the UE to enter an inactive state to receive the MBS service.
  • the DU Upon receiving the indication information, the DU maintains the multicast context information, and continues transmission of multicast service data when there is no multicast UE context, and does not initiate a multicast context release request message to the CU or a multicast distribution release request message to the CU.
  • the DU transmits a multicast context establishment response message to the CU.
  • the multicast context establishment response message includes the identifier of F1AP allocated by the DU for MBS, the identifier of F1AP allocated by the CU for MBS, and the identifier of the MBS radio bearer established successfully.
  • the message also includes indication information indicating whether the DU has a function of allowing the UE to receive the MBS service in the RRC inactive state.
  • the DU has this function, which can maintain the transmission of multicast data and the multicast context on the DU. Even when the context information of the MBS UE is not saved on the DU, the DU still transmits the multicast data without releasing signaling resources and user plane resources of the multicast service, and the DU does not initiate a multicast context release request message to the CU.
  • the CU can decide to allow some UEs to enter the RRC inactive mode to receive the MBS multicast service.
  • the CU can decide to allow some UEs to enter the RRC inactive state to receive the MBS service, so as to achieve the purpose of saving power for the UE.
  • Fig. 10 is a block diagram of a node device in a network according to the present invention.
  • the node device in the network may be used to implement the DU, CU-UP, CU-CP, gNB, eNB source base station, destination station, source DU, source CU-UP, source CU-CP, destination DU, destination CU-UP, destination CU-CP, primary base station, secondary base station, OAM, UDM, AMF, SMF or UPF, etc. of the present invention.
  • a network device includes a transceiver 1010, a controller 1020 and a memory 1030.
  • the transceiver 1010, the controller 1020 and the memory 1030 are configured to perform the operations of the methods and/or embodiments of the present invention.
  • transceiver 1010, the controller 1020 and the memory 1030 are shown as separate entities, they may be implemented as a single entity, such as a single chip.
  • the transceiver 1010, the controller 1020 and the memory 1030 may be electrically connected or coupled to each other.
  • the transceiver 1010 may transmit signals to and receive signals from other network devices, such as a UE, a base station or a core network node.
  • the controller 1020 may include one or more processing units and may control the network device to perform the operations and/or functions according to one of the above embodiments.
  • the memory 1030 may store instructions for implementing the operations and/or functions of one of the above embodiments.
  • the method and device for supporting the multicast service transmission have been completed.
  • the UE can receive the MBS data in the RRC inactive state, so as to achieve the effect of saving the energy of the UE.
  • Fig. 11 is a structure of a user equipment (UE) to which embodiments of the disclosure can be applied.
  • UE user equipment
  • Fig. 11 The structure of the UE to which embodiments of the disclosure can be applied is illustrated in Fig. 11.
  • the UE includes a radio frequency (RF) processor 1110, a baseband processor 1120, a storage unit 1130, and a controller 1140.
  • RF radio frequency
  • the RF processor 1110 performs a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of a signal. That is, the RF processor 1110 up-converts a baseband signal provided from the baseband processor 1120 into an RF band signal, transmits the RF band signal through an antenna, and then down-converts the RF band signal received through the antenna into a baseband signal.
  • the RF processor 1110 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), and the like.
  • DAC digital-to-analog converter
  • ADC analog-to-digital converter
  • the RF processor 1110 may include a plurality of RF chains. Moreover, the RF processor 1110 may perform beamforming. For the beamforming, the RF processor 1110 may control a phase and a size of each signal transmitted/received through a plurality of antennas or antenna elements. The RF processor may perform MIMO and receive a plurality of layers when performing the MIMO operation. The RF processor 1110 may appropriately configure a plurality of antennas or antenna elements according to the control of the controller to perform reception beam sweeping or control a direction of a reception beam and a beam width so that the reception beam corresponds to a transmission beam.
  • the baseband processor 1120 performs a function for a conversion between a baseband signal and a bitstream according to a physical layer standard of the system. For example, when data is transmitted, the baseband processor 1120 generates complex symbols by encoding and modulating a transmission bitstream. Further, when data is received, the baseband processor 1120 reconstructs a reception bitstream by demodulating and decoding a baseband signal provided from the RF processor 1110.
  • the baseband processor 1120 when data is transmitted, the baseband processor 1120 generates complex symbols by encoding and modulating a transmission bitstream, mapping the complex symbols to subcarriers, and then configures OFDM symbols through an inverse fast Fourier transform (IFFT) operation and a cyclic prefix (CP) insertion. Further, when data is received, the baseband processor 1120 divides the baseband signal provided from the RF processor 1110 in the unit of OFDM symbols, reconstructs the signals mapped to the subcarriers through a fast Fourier transform (FFT) operation, and then reconstructs a reception bitstream through demodulation and decoding.
  • OFDM orthogonal frequency division multiplexing
  • the baseband processor 1120 and the RF processor 1110 transmit and receive signals as described above. Accordingly, the baseband processor 1120 and the RF processor 1110 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit. Further, at least one of the baseband processor 1120 and the RF processor 1110 may include a plurality of communication modules to support a plurality of different radio access technologies. In addition, at least one of the baseband processor 1120 and the RF processor 1110 may include different communication modules to process signals of different frequency bands. For example, the different radio-access technologies may include an LTE network and an NR network. Further, the different frequency bands may include a super high frequency (SHF) (for example, 2.5 GHz and 5 Ghz) band and a millimeter (mm) wave (for example, 60 GHz) band.
  • SHF super high frequency
  • mm millimeter
  • the storage unit 1130 stores data such as basic program, an application, and setting information for the operation of the UE.
  • the storage unit 1130 provides the stored data according to a request from the controller 1140.
  • the controller 1140 controls the overall operation of the UE. For example, the controller 1140 transmits/receives a signal through the baseband processor 1120 and the RF processor 1110. In addition, the controller 1140 may record data in the storage unit 1130 and read the data. To this end, the controller 1140 may include at least one processor. For example, the controller 1140 may include a communication processor (CP) that performs a control for communication, and an application processor (AP) that controls a higher layer such as an application program.
  • CP communication processor
  • AP application processor
  • Fig. 12 is a structure of a base station in a wireless communication system to which embodiments of the disclosure can be applied.
  • the base station includes an RF processor 1210, a baseband processor 1220, a backhaul communication unit 1230, a storage unit 1240, and a controller 1250.
  • the RF processor 1210 performs a function for transmitting and receiving a signal through a wireless channel, such as band conversion and amplification of a signal. That is, the RF processor 1210 up-converts a baseband signal provided from the baseband processing unit 1220 into an RF band signal and then transmits the converted signal through an antenna, and down-converts an RF band signal received through the antenna into a baseband signal.
  • the RF processor 1210 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, and an ADC.
  • Fig. 12 illustrates only one antenna, the first access node may include a plurality of antennas.
  • the RF processor 1210 may include a plurality of RF chains. Moreover, the RF processor 1210 may perform beamforming. For the beamforming, the RF processor 1210 may control a phase and a size of each of the signals transmitted and received through a plurality of antennas or antenna elements. The RF processor may perform a downlink MIMO operation by transmitting one or more layers.
  • the baseband processor 1220 performs a function of performing conversion between a baseband signal and a bitstream according to a physical layer standard of the first radio access technology. For example, when data is transmitted, the baseband processor 1220 generates complex symbols by encoding and modulating a transmission bitstream. Further, when data is received, the baseband processor 1220 reconstructs a reception bitstream by demodulating and decoding a baseband signal provided from the RF processor 1210. For example, in an OFDM scheme, when data is transmitted, the baseband processor 1220 may generate complex symbols by encoding and modulating the transmission bitstream, map the complex symbols to subcarriers, and then configure OFDM symbols through an IFFT operation and CP insertion.
  • the baseband processor 1220 divides a baseband signal provided from the RF processor 1210 in units of OFDM symbols, recovers signals mapped with sub-carriers through an FFT operation, and then recovers a reception bitstream through demodulation and decoding.
  • the baseband processor 1220 and the RF processor 1210 transmit and receive signals as described above. Accordingly, the baseband processor 1220 and the RF processor 2010 may be referred to as a transmitter, a receiver, a transceiver, or a communication unit.
  • the communication unit 1230 provides an interface for communicating with other nodes within the network.
  • the storage unit 1240 stores data such as a basic program, an application, and setting information for the operation of the MeNB. Particularly, the storage unit 1240 may store information on bearers allocated to the accessed UE and the measurement result reported from the accessed UE. Further, the storage unit 1240 may store information on a reference for determining whether to provide multiple connections to the UE or stop the multiple connections. In addition, the storage unit 1240 provides data stored therein according to a request from the controller 1250.
  • the controller 1250 controls the overall operation of the MeNB. For example, the controller 1250 transmits and receives a signal through the baseband processor 1220 and the RF processor 1210 or through the backhaul communication unit 1230. In addition, the controller 1250 may record data in the storage unit 1240 and read the data. To this end, the controller 1250 may include at least one processor.
  • the various illustrative logic blocks, modules, and circuits described in this application may be implemented or performed by a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logics, discrete hardware components, or any combination thereof designed to perform the functions described herein.
  • the general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • the processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.
  • the steps of the method or algorithm described in this application may be embodied directly in hardware, in a software module executed by a processor, or in a combination thereof.
  • the software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, register, hard disk, removable disk, or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to a processor to enable the processor to read and write information from/to the storage media.
  • the storage medium may be integrated into the processor.
  • the processor and the storage medium may reside in an ASIC.
  • the ASIC may reside in a user terminal.
  • the processor and the storage medium may reside in the user terminal as discrete components.
  • the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function may be stored as one or more pieces of instructions or codes on a computer-readable medium or delivered through it.
  • the computer-readable medium includes both a computer storage medium and a communication medium, the latter including any medium that facilitates the transfer of computer programs from one place to another.
  • the storage medium may be any available medium that can be accessed by a general purpose or special purpose computer.

Landscapes

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

Abstract

La divulgation concerne un système de communication 5G ou 6G permettant de prendre en charge un débit supérieur de transmission de données. La présente divulgation concerne un procédé et un dispositif pour prendre en charge une transmission de service de multidiffusion, un procédé mis en œuvre par un second nœud dans un système de communication sans fil étant divulgué, le procédé consistant à : recevoir, en provenance d'un premier nœud, un premier message transportant des informations associées d'un UE dans un état inactif RRC ; et réaliser un traitement sur la base du premier message.
PCT/KR2023/017066 2022-11-02 2023-10-31 Procédé et dispositif de prise en charge d'une transmission de service de multidiffusion WO2024096502A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211364734.9 2022-11-02
CN202211364734.9A CN118042420A (zh) 2022-11-02 2022-11-02 支持组播业务传输的方法和设备

Publications (1)

Publication Number Publication Date
WO2024096502A1 true WO2024096502A1 (fr) 2024-05-10

Family

ID=90931086

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2023/017066 WO2024096502A1 (fr) 2022-11-02 2023-10-31 Procédé et dispositif de prise en charge d'une transmission de service de multidiffusion

Country Status (2)

Country Link
CN (1) CN118042420A (fr)
WO (1) WO2024096502A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220015063A1 (en) * 2020-07-07 2022-01-13 Lg Electronics Inc. Method and apparatus for paging for multicast and broadcast service in a wireless communication system
CN115278790A (zh) * 2021-04-30 2022-11-01 华为技术有限公司 一种通信方法及通信装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220015063A1 (en) * 2020-07-07 2022-01-13 Lg Electronics Inc. Method and apparatus for paging for multicast and broadcast service in a wireless communication system
CN115278790A (zh) * 2021-04-30 2022-11-01 华为技术有限公司 一种通信方法及通信装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON, AT&T: "Corrections to the example message flow for multicast MBS Context establishment", 3GPP DRAFT; R3-225444, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20221010 - 20221018, 27 September 2022 (2022-09-27), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052265581 *
ERICSSON, AT&T: "Introduction of multicast MBS session status in Multicast Context Management messages", 3GPP DRAFT; R3-225966, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20221010 - 20221018, 18 October 2022 (2022-10-18), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052266104 *

Also Published As

Publication number Publication date
CN118042420A (zh) 2024-05-14

Similar Documents

Publication Publication Date Title
WO2018199611A1 (fr) Procédé et équipement utilisateur permettant de transmettre une demande d'enregistrement à un réseau, et procédé et dispositif de réseau permettant de recevoir une demande d'enregistrement
WO2023146310A1 (fr) Procédé et appareil pour la prise en charge de changement de tranche de réseau dans un système de communication sans fil
WO2022225315A1 (fr) Procédé et dispositif de notification d'état de mbs
WO2022235120A1 (fr) Appareil et procédé de prise en charge de commutation de réseau d'équipement utilisateur dans un système de communication sans fil
WO2023191478A1 (fr) Procédé et dispositif de support de mouvement de véhicule aérien sans pilote
WO2023158234A1 (fr) Procédé et appareil pour le changement conditionnel d'une pscell dans un système de communication mobile de prochaine génération
WO2023121112A1 (fr) Procédé et appareil de prise en charge d'un équipement utilisateur (ue) aérien dans une communication mobile de nouvelle génération
WO2023014161A1 (fr) Procédé et appareil pour fournir des informations de contrôle d'accès dans un système de communication mobile
WO2022240185A1 (fr) Procédé et appareil pour améliorer la qualité d'expérience dans les communications mobiles
WO2022173274A1 (fr) Procédé et appareil pour prendre en charge une tranche de réseau dans un système de communication sans fil
WO2024096502A1 (fr) Procédé et dispositif de prise en charge d'une transmission de service de multidiffusion
WO2024172540A1 (fr) Procédé et dispositif pour prendre en charge une transmission de service de diffusion de groupe
WO2024123066A1 (fr) Procédé et appareil de gestion d'opération dans un réseau non public autonome (snpn)
WO2024167257A1 (fr) Procédé pour effectuer une resélection de cellule d'un répéteur de contrôle de réseau dans un système de communication sans fil
WO2024071703A1 (fr) Procédé et appareil de réalisation de mesures de qoe pour des services de diffusion de mbs dans un système de communication mobile nouvelle génération
WO2023219417A1 (fr) Procédé et appareil de rapport de mesure de qoe dans un système de communication mobile de prochaine génération
WO2023128486A1 (fr) Procédé et appareil pour une capacité d'ue et une signalisation d'assistance pour un service mbs dans un système de communication sans fil
WO2023211089A1 (fr) Procédé et appareil de transfert intercellulaire
WO2023158169A1 (fr) Procédé et appareil de signalisation de capacité d'ue pour un changement conditionnel de pscell dans un système de communication sans fil
WO2024128805A1 (fr) Procédé et appareil de gestion d'informations d'historique de mobilité de cellule pscell dans un système de communication mobile de prochaine génération
WO2024172351A1 (fr) Appareil et procédé d'utilisation de groupe d'accès à une tranche de réseau (nsag) dans un système de communication sans fil
WO2024172426A1 (fr) Procédé et dispositif pour réaliser un transfert dans un système de communication sans fil
WO2024177453A1 (fr) Procédé et appareil de transfert d'un équipement utilisateur à des fins d'économie d'énergie de réseau dans un système de communication mobile de nouvelle génération
WO2023191502A1 (fr) Procédé et dispositif de fourniture d'un trajet d'accès dans un système de communication sans fil
WO2024014898A1 (fr) Procédé et dispositif permettant de mesurer qoe dans un système de communication sans fil

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: 23886198

Country of ref document: EP

Kind code of ref document: A1