WO2021063215A1 - 一种网络切片的组播方法及装置 - Google Patents

一种网络切片的组播方法及装置 Download PDF

Info

Publication number
WO2021063215A1
WO2021063215A1 PCT/CN2020/116795 CN2020116795W WO2021063215A1 WO 2021063215 A1 WO2021063215 A1 WO 2021063215A1 CN 2020116795 W CN2020116795 W CN 2020116795W WO 2021063215 A1 WO2021063215 A1 WO 2021063215A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
identifier
network slice
message
service channel
Prior art date
Application number
PCT/CN2020/116795
Other languages
English (en)
French (fr)
Inventor
罗海燕
黄曲芳
戴明增
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20872762.8A priority Critical patent/EP4030846A4/en
Publication of WO2021063215A1 publication Critical patent/WO2021063215A1/zh
Priority to US17/705,893 priority patent/US20220217509A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/16—Arrangements for providing special services to substations
    • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
    • H04L12/189—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast in combination with wireless systems
    • 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
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/30—Resource management for broadcast services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • This application relates to the field of wireless communication technologies, and in particular to a multicast method and device for network slicing.
  • multicast technology can effectively solve the problems of single-point transmission and multi-point reception, so as to achieve efficient point-to-multipoint data transmission in the network, so as to save network bandwidth and reduce network load.
  • the multicast method When some devices in the network (that is, the receiver) need information, if the multicast method is adopted, these devices can be added to the same multicast group, and the multicast source (that is, the source) can join the multicast group. The group only needs to send one piece of information, and then the information will be accurately sent to each device in the multicast group.
  • the present application provides a multicast method and device for network slicing, in order to realize multicast at the granularity of network slicing.
  • the present application provides a multicast method for network slicing, which includes an access network device generating a first message; sending a first message to the UE, and the first message includes the identifier of the network slice and the multicast service channel The identifier of the network slice corresponds to the multicast service channel; the UE receives the first message from the access network device, and the UE uses the multicast service channel to receive the group corresponding to the network slice Broadcast data.
  • the access network device sends the identification of the network slice and the configuration information of the multicast service channel to the UE.
  • the identification of the network slice corresponds to the multicast service channel, and the UE can directly obtain the identification of the network slice and the multicast service.
  • Channel configuration information in this way, the UE can obtain multicast data through the multicast service channel corresponding to the identifier of the network slice, thereby realizing multicast at the granularity of network slices, and realizing a multicast mechanism based on network slices.
  • the method further includes: the access network device receives a network slice identifier and indication information from a core network device, where the indication information indicates the multicast data corresponding to the network slice identifier.
  • the access network device receives the network slice identifier and indication information from the core network device.
  • the access network device can determine that it may subsequently receive the multicast data corresponding to the network slice sent by the core network device by receiving the network slice identification and indication information sent by the core network device, so that the access network device can do Good preparations before transmitting the multicast data, such as generating the first message, etc.
  • the first message may also include a temporary mobile group identifier TMGI, and the TMGI corresponds to the identifier of the network slice.
  • TMGI temporary mobile group identifier
  • the access network device can also send the TMGI to the UE.
  • the TMGI corresponds to the identifier of the network slice, and the UE can also directly obtain the TMGI corresponding to the identifier of the network slice.
  • the UE can receive multicast data through the multicast service channel corresponding to the TMGI, and can learn the network slice identifier corresponding to the multicast data, so as to realize the network slice granular multicast and realize the multicast mechanism based on the network slice.
  • the access network device can send the configuration information of the multicast service channel corresponding to the identifier of the network slice and the TMGI corresponding to the identifier of the network slice to the UE through a single message, thereby reducing signaling consumption.
  • the configuration information of the multicast service channel includes at least one of the following information: last subframe configuration, data modulation coding value, scheduling period, logical channel identifier, duration timer, DRX The inactive timer and the start deviation of the scheduling period.
  • the access network device may also use the multicast service channel to send the multicast data corresponding to the network slice.
  • the access network device sends the multicast data corresponding to the network slice through the multicast service channel, so that the UE can receive the multicast data through the multicast service channel corresponding to the identifier of the network slice, thereby realizing multicast at the granularity of the network slice , Achieve a multicast mechanism based on network slicing.
  • the access network device may be an access network distribution unit DU.
  • the present application provides a multicast method for network slicing, which includes an access network centralization unit CU generating a multicast session establishment message, and sending a multicast session establishment message to the access network distribution unit DU, the multicast session
  • the establishment message includes the identifier of the multicast session
  • the DU receives the multicast session establishment message sent by the CU
  • the DU sends a second message to the UE
  • the second message includes the identifier of the multicast session and the configuration information of the multicast service channel
  • the identifier of the multicast session corresponds to the multicast service channel.
  • the DU sends the multicast session establishment message to the CU, and the CU sends the identifier of the multicast session and the configuration information of the multicast service channel to the UE.
  • the identifier of the network slice corresponds to the multicast service channel, and the UE can obtain it directly To the identifier of the network slice and the configuration information of the multicast service channel, the UE can obtain multicast data through the multicast service channel corresponding to the identifier of the network slice, so that under the CU-DU separation architecture, the multicast session can also be realized Transceiving, and when the identifier of the multicast session includes the identifier of the network slice, the multicast of the granularity of the network slice can be realized, and the multicast mechanism based on the network slice can be realized.
  • the identifier of the multicast session includes at least one of the following information: TMGI, session identifier, or network slice identifier.
  • the identifier of the multicast session may include TMGI; or the identifier of the multicast session includes the session identifier; or the identifier of the multicast session includes the identifier of a network slice; or the identifier of the multicast session includes TMGI and session identifier; or the multicast session identifier includes TMGI and network slice identifiers; or the multicast session identifier includes session identifier and network slice identifier; or the multicast session identifier includes TMGI, session Identification and identification of the network slice.
  • the DU may also feed back a downlink user plane tunnel endpoint information to the CU; the CU may receive a downlink user plane tunnel endpoint information from the DU; or the DU may also report The CU feeds back a set of downlink user plane tunnel endpoint information, the set of downlink user plane tunnel endpoint information includes the downlink user plane tunnel endpoint information corresponding to each multicast session; the CU receives a set of downlink user plane tunnel endpoint information from the DU User plane tunnel endpoint information.
  • the DU when the DU establishes a user plane tunnel common to all multicast sessions, it feeds back a downlink user plane tunnel endpoint information to the CU; when the DU establishes a user plane tunnel corresponding to each multicast session, the feedback to the CU includes each A group of downlink user plane tunnel endpoint information corresponding to a multicast session.
  • the DU can realize the transmission of multicast data between the CU and the DU by establishing the user plane tunnel corresponding to the multicast session between the CU, so that the DU can receive the group through the user plane tunnel between the CU and the CU. Broadcast the data, and then send the multicast data to the terminal equipment UE, so as to realize the sending and receiving of the multicast session.
  • the CU may also send a third message to the DU, where the third message is used to instruct the DU to feed back one downlink user plane tunnel endpoint information or a group of downlink user plane tunnel endpoint information;
  • the DU receives the third message from the CU.
  • the CU sends a third message to the DU.
  • the DU determines to establish a user plane tunnel common to all multicast sessions or establish a user plane tunnel corresponding to each multicast session through the third message indicated by the CU, thereby realizing the transmission of multicast data.
  • the CU may also send a fourth message to the DU, where the fourth message is used to instruct to start the multicast session, and the fourth message includes the identifier of the multicast session ;
  • the DU may also receive a fourth message from the CU.
  • the CU instructs the DU to start the multicast session by sending the fourth message including the identifier of the multicast session to the DU, and the DU determines which multicast data corresponding to the identifier of the multicast session is subsequently received from the CU through the F1 interface
  • the purpose of obtaining the multicast session identifier corresponding to the multicast data by the DU is achieved through the control plane, so that the DU can send the multicast data on the multicast service channel corresponding to the multicast session identifier.
  • the method further includes: the CU sends data to the DU through a public user plane tunnel, and the data includes multicast data and an identifier of the multicast session; and the DU through a public user plane tunnel Receive data from the CU.
  • the CU sends data containing the multicast data and the identifier of the multicast session to the DU through the public user plane tunnel on the F1 interface, so as to achieve the purpose of obtaining the multicast session identifier corresponding to the multicast data by the DU through the user plane. , So that the DU can send the multicast data on the multicast service channel corresponding to the identifier of the multicast session.
  • the present application provides a multicast method for network slicing, including a core network device acquiring an identifier of a network slice and a temporary mobility group identifier TMGI, where the identifier of the network slice corresponds to the TMGI; the core network The device sends a non-access stratum NAS message to the user terminal UE.
  • the NAS message includes the identifier of the network slice and the TMGI, and the identifier of the network slice corresponds to the TMGI; the UE receives the NAS message sent from the core network device,
  • the UE uses the multicast service channel corresponding to the TMGI to receive the multicast data corresponding to the network slice.
  • the core network device sends the network slice identifier and TMGI to the UE.
  • the TMGI corresponds to the network slice identifier
  • the UE can also obtain the TMGI corresponding to the network slice identifier.
  • the UE can finally receive the multicast data corresponding to the network slice through the multicast service channel corresponding to the TMGI, so as to realize the multicast with the granularity of the network slice and the multicast mechanism based on the network slice.
  • the core network device may also obtain an identifier of an application program, and the identifier of the application program corresponds to the identifier of the network slice.
  • the core network device obtains the identification of the network slice and the identification of the application, and the identification of the application corresponds to the identification of the network slice, so that the core network device can also send the identification of the application corresponding to the identification of the network slice to UE, UE can receive multicast data on the multicast service channel corresponding to the TMGI of the network slice of the application of interest, thereby realizing network slice granular multicast and realizing the multicast mechanism based on network slice.
  • the NAS message may also include identification information of an application, and the identification of the application corresponds to the identification of the network slice.
  • the core network device can also send the identification information of the application to the UE, and the UE can also obtain the identification of the application corresponding to the identification of the network slice.
  • the UE can correspond to the TMGI in the network slice of the application of interest.
  • the multicast service channel receives multicast data, thereby realizing multicast at the granularity of network slicing, and realizing a multicast mechanism based on network slicing.
  • the UE may also receive a fifth message sent by the base station.
  • the fifth message includes configuration information of TMGI and multicast service channel, and the TMGI corresponds to the multicast service channel. .
  • the base station sends the configuration information including the TMGI and the multicast service channel to the UE.
  • the TMGI corresponds to the multicast service channel, and the UE can find the corresponding TMGI through the network slice of interest.
  • multicast data is received through the multicast service channel corresponding to TMGI, thereby realizing multicast at the granularity of network slicing, and realizing a multicast mechanism based on network slicing.
  • a network slicing multicast device has the functions of the access network equipment, UE, and core network equipment in the foregoing method, and includes means for executing the steps or functions described in the foregoing method.
  • the steps or functions can be realized by software, or by hardware (such as a circuit), or by a combination of hardware and software.
  • the access network equipment includes the access network equipment, and/or CU-DU.
  • the above-mentioned device includes one or more processors and communication units.
  • the one or more processors are configured to support the apparatus to perform corresponding functions of the access network equipment, the UE, and the core network equipment in the foregoing method.
  • the device may further include one or more memories, where the memory is used for coupling with the processor and stores necessary program instructions and/or data for the device.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor. This application is not limited.
  • the above device includes a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver or the input/output circuit to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to run the computer program in the memory so that the device executes the first aspect or any one of the first aspect
  • the method implemented by the access network device and the UE in the possible implementation manners, or the method implemented by the access network device and the UE in any of the second aspect or the second aspect in any one of the possible implementation manners, or the third aspect or the third aspect A method completed by the core network equipment and UE in any of the possible implementation modes.
  • the above-mentioned device includes one or more processors and communication units.
  • the one or more processors are configured to support the apparatus to perform corresponding functions of the access network equipment, the UE, and the core network equipment in the foregoing method.
  • the apparatus may further include one or more memories, where the memories are configured to be coupled with the processor and store program instructions and/or data necessary for the access network equipment, the UE, and the core network equipment.
  • the one or more memories may be integrated with the processor, or may be provided separately from the processor. This application is not limited.
  • the device may be located in an access network device, UE, or core network device, or may be an access network device, UE, or core network device.
  • the above device includes a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver or the input/output circuit to send and receive signals
  • the memory is used to store a computer program
  • the processor is used to run the computer program in the memory, so that the device executes the first aspect or any one of the first aspect.
  • the method implemented by the access network device and the UE in the implementation manner, or the method implemented by the access network device and the UE in the second aspect or any one of the possible implementation manners of the second aspect, or the implementation of the third aspect or the third aspect A method completed by the core network equipment and the UE in any possible implementation manner.
  • a computer-readable storage medium for storing a computer program.
  • the computer program includes methods for executing the first aspect, the second aspect, the third aspect, or the first, second, and third aspect. Any one of the possible implementations of the method in the aspect.
  • a computer program product includes: computer program code, which when the computer program code runs on a computer, causes the computer to execute the first aspect, the second aspect, and the third aspect. , Or a method in any one of the possible implementation manners of the first, second, and third aspects.
  • the present application provides a chip system that includes a transceiver for implementing the functions of the access network device, UE, and core network device in the methods of the foregoing aspects, for example, receiving or sending the foregoing methods
  • the data and/or information involved in is included in.
  • the chip system further includes a memory, and the memory is used to store program instructions and/or data.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the application
  • Figure 2 is a schematic diagram of a network slicing multicast process provided by an embodiment of the application
  • FIG. 3 is a schematic diagram of a multicast flow of network slicing provided by an embodiment of this application.
  • FIG. 4 is a schematic diagram of a network slicing multicast process provided by an embodiment of the application.
  • FIG. 5 is a schematic structural diagram of a network slicing multicast device provided by an embodiment of this application.
  • Fig. 6 is a schematic structural diagram of a network slicing multicast device provided by an embodiment of the application.
  • the fourth generation (4th Generation, 4G) the 4G system includes the long term evolution (LTE) system
  • the fifth generation (5th Generation, 5G) Systems
  • NR new radio access technology
  • 6G systems future communication systems, such as 6G systems.
  • the word "exemplary” is used to mean serving as an example, illustration, or illustration. Any embodiment or design solution described as an "example” in this application should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, the term example is used to present the concept in a concrete way.
  • UE User equipment
  • MS mobile station
  • MT mobile terminal
  • UE User equipment
  • UE can also be referred to as terminal for short.
  • MS mobile station
  • MT mobile terminal
  • UE User equipment
  • UE can also be referred to as terminal for short.
  • it is also called mobile station (MS), mobile terminal (MT), etc., which provide voice to users And/or data connectivity equipment.
  • handheld devices with wireless connectivity vehicle-mounted devices, etc.
  • some examples of terminals are: mobile phones (mobile phones), tablet computers, notebook computers, handheld computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, and augmented reality.
  • augmented reality, AR equipment
  • wireless terminals in industrial control wireless terminals in self-driving, wireless terminals in remote medical surgery, and smart grids
  • a network device is a device in a wireless network.
  • a network device may be a radio access network (RAN) node (or device) that connects a terminal to the wireless network, and may also be called a base station.
  • RAN nodes are: continuously evolving node B (gNB), transmission reception point (TRP), evolved Node B (eNB), radio network controller, RNC), Node B (Node B, NB), base station controller (BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB) , Baseband unit (BBU), or wireless fidelity (wireless fidelity, Wifi) access point (AP), etc.
  • gNB continuously evolving node B
  • TRP transmission reception point
  • eNB evolved Node B
  • RNC radio network controller
  • Node B Node B
  • BSC base station controller
  • BTS base transceiver station
  • home base station for example, home evolved NodeB, or home Node B, H
  • the network device may include a centralized unit (CU) node, or a distributed unit (DU) node, or a RAN device including a CU node and a DU node.
  • the RAN equipment including the CU node and the DU node splits the protocol layer of the eNB in the long term evolution (LTE) system.
  • LTE long term evolution
  • Some of the protocol layer functions are placed under the centralized control of the CU, and some or all of the protocol layer functions are left.
  • Distributed in DU, DU is centrally controlled by CU.
  • the network device may be a core network (CN) device that provides service support for the terminal.
  • CN core network
  • AMF access and mobility management function
  • SMF session management function
  • UPF user plane function
  • the wireless communication system is mainly divided into three data transmission modes: unicast, broadcast and multicast/multicast.
  • a cell also called a cell, is an area covered by a base station or a part of a base station (generally referred to as an area covered by wireless signals), and terminals located in the cell can communicate with the base station through wireless channels.
  • the CU-DU separation architecture is introduced in the 5G NR system.
  • One CU and multiple DUs form a base station.
  • CU is mainly responsible for the radio resource control layer (radio resource control, RRC), service data adaptation protocol (service data adaptation protocol, SDAP) and packet data convergence protocol (packet data convergence protocol, PDCP) protocol layer
  • DU is mainly responsible for the wireless link Layer control protocol (radio link control, RLC), media access control layer (media access control, MAC) and physical layer (physical layer, PHY) protocol layers
  • CU and DU are connected through an F1 interface.
  • a CU-DU separation architecture is also introduced. The difference is that the CU only contains the RRC and PDCP protocol layers. In addition, the CU and DU of LTE are connected through the W1 interface.
  • Network slice also called slice, it refers to different logical networks customized according to different service requirements based on physical or virtual network infrastructure.
  • Network slicing technology allows operators to separate multiple virtual end-to-end networks in a hardware infrastructure.
  • Each network slice is logically isolated from the device to the access network to the transmission network to the core network, adapting to various types Different characteristic requirements of the service.
  • a network slice can be a complete end-to-end network including terminals, access networks, transmission networks, core networks, and application servers, which can provide complete telecommunication services and have certain network capabilities; network slices can also be the above-mentioned terminals and connections. Any combination of network access, transmission network, core network and application server.
  • Network slicing may have one or more of the following characteristics: the access network may or may not be sliced. The access network may be shared by multiple network slices. The characteristics of different network slices and the network functions that compose them may be different.
  • system and “network” in the embodiments of this application can be used interchangeably.
  • Multiple refers to two or more than two, and other quantifiers are similar.
  • And/or describes the association relationship of the associated object, indicating that there can be three types of relationships, for example, A and/or B, which can mean: A alone exists, A and B exist at the same time, and B exists alone.
  • a and/or B which can mean: A alone exists, A and B exist at the same time, and B exists alone.
  • a and/or B which can mean: A alone exists, A and B exist at the same time, and B exists alone.
  • a device means to one or more such devices.
  • At least one (at least one of)" means one or any combination of subsequent associated objects, for example, at least one of a, b, or c, which can mean : A, b, c, ab, ac, bc or abc, where a, b, c can be single or multiple.
  • first and second are used to distinguish multiple objects, and are not used to limit the order, timing, priority, or order of multiple objects. Importance.
  • first data packet and the second data packet are only for distinguishing different data packets, but do not indicate the difference in content, priority, sending order, or importance of the two data packets.
  • the network device sends the configuration information of the multicast service channel corresponding to the identifier of the network slice to the UE, and then uses the multicast service channel corresponding to the network slice to send multicast data, where the network device includes an access network device and/ Or core network equipment, the UE receives the configuration information of the multicast service channel corresponding to the identifier of the network slice.
  • the UE can listen to the multicast data on the multicast service channel corresponding to the network slice of interest. Multicast with network slicing granularity.
  • the access network device sends a first message to the UE.
  • the first message includes the identifier of the network slice and the configuration information of the multicast service channel.
  • the identifier of the network slice corresponds to the multicast service channel
  • the UE receives
  • the first message can listen to the multicast data according to the multicast service channel corresponding to the network slice of interest, thereby achieving network slice granular multicast, or the DU sends a second message to the UE.
  • the second message includes the identifier of the multicast session and The configuration information of the multicast service channel and the identifier of the multicast session correspond to the multicast service channel.
  • the sending and receiving of multicast sessions can also be realized, and the multicast identifier of the session includes network slices. It can also meet the multicast of network slice granularity; or the core network device sends a non-access stratum (NAS) message to the UE.
  • the NAS message includes the network slice identifier and TMGI, and the network slice identifier
  • the UE receives the NAS message and can listen to the multicast data according to the multicast service channel of the TMGI corresponding to the network slice of interest, thereby achieving network slice granular multicast.
  • FIG 1 is a schematic diagram of an application scenario of a patent application.
  • network equipment such as the core network equipment and access network equipment in Figure 1
  • multiple UEs such as UE1, UE2, UE3, UE4, and UE5 in Figure 1.
  • the network device may send the identification information of the multicast service channel corresponding to the identification of the network slice to the UE.
  • the core network device may send the multicast data to the access network device, and the access network device sends the multicast data to the UE through the multicast service channel corresponding to the network slice.
  • the identifier of a network slice includes slice1 and slice2.
  • the core network device can send the multicast data of slice1 and the multicast data of slice2 to the access network device, and the access network device can send the multicast data of slice1 through the multicast service channel corresponding to slice1.
  • the multicast data is sent to UE1, UE2, and UE3, and the multicast data of slice2 is sent to UE4 and UE5 through the multicast service channel corresponding to slice2.
  • UE1, UE2, and UE3 can listen to the multicast data of slice1 on the multicast service channel corresponding to slice1, and UE4 and UE5 can listen to the multicast data of slice2 on the multicast service channel corresponding to slice2. Realize multicast in a network with network slicing.
  • the embodiment of the present application provides a multicast method for network slicing, and the method can be applied to the application scenario shown in FIG. 1.
  • the following describes the specific process of network slicing multicast in detail in the following manner.
  • the process includes:
  • Step 201 The access network device generates a first message, where the first message includes the identifier of the network slice and the configuration information of the multicast service channel, and the identifier of the network slice corresponds to the multicast service channel.
  • the access network device may be a base station, or may be a DU.
  • the first message includes the identifier of the network slice and the configuration information of the multicast service channel, that is, the first message supports the configuration information of the multicast service channel corresponding to the network slice.
  • the first message may be a SlicingMBMSConfiguration (Slicing Multimedia Broadcast Multicast Service Configuration) message sent on the Slicing-MCCH (Slicing Multicast Control Channel), which contains the network slice identifier and the configuration information of the corresponding multicast service channel. .
  • the first message may also include a TMGI, and the TMGI corresponds to the identifier of the network slice.
  • the access network device may include the identifier of the network slice in the message supporting the configuration information of the multicast service channel corresponding to the TMGI, so as to generate the first message.
  • the message supporting the configuration information of the multicast service channel corresponding to TMGI can be the MBSFNAreaConfiguration (multicast broadcast co-frequency network area configuration) message sent on the multicast control channel (multicast control channel, MCCH), or in a single cell group Broadcast the SCPTMConfiguration (single-cell point-to-multipoint configuration) message sent on the control channel (single-cell multicast control channel, SC-MCCH). That is, the message includes the TMGI, the network slice identifier, and the configuration information of the corresponding multicast service channel.
  • MBSFNAreaConfiguration multicast broadcast co-frequency network area configuration
  • SC-MCCH single cell group
  • the message includes the TMGI, the network slice identifier, and the configuration information of the corresponding multicast service channel.
  • the multicast service channel includes a multicast traffic channel (multicast traffic channel, MTCH) and/or a single-cell multicast traffic channel (single-cell multicast traffic channel, SC-MTCH).
  • MTCH multicast traffic channel
  • SC-MTCH single-cell multicast traffic channel
  • the access network device broadcasts a system information block type (SIB) message (such as a SIB13 message or a SIB20 message), and the SIB message includes MCCH/SC-MCCH configuration information.
  • SIB system information block type
  • the access network device sends the TMGI and MTCH/SC-MTCH configuration information on the MCCH/SC-MCCH.
  • the access network equipment sends multicast data on the MTCH/SC-MTCH.
  • MBMS multimedia broadcast multicast service
  • MMSFN multimedia broadcast multicast service
  • the configuration information of TMGI and MTCH is sent on the MTCH, and then the multicast data is sent on the MTCH.
  • SC-PTM single cell-point to multi-point
  • the access network equipment broadcasts the SC-MCCH configuration information through the SIB20 message, and sends the TMGI and SC-MTCH configuration on the MCCH Information, and finally send multicast data on SC-MTCH.
  • the configuration information of the multicast service channel includes at least one of the following information: the last subframe configuration, the value of the data modulation code, the scheduling period, the logical channel identifier, the duration timer, the DRX inactive timer, or the scheduling period Start to deviate.
  • the multicast service channel is MTCH.
  • the configuration information of the multicast service channel includes at least one of the following information: the last subframe configuration (such as the last subframe configuration sf-allocend), the value of data modulation and coding (such as data modulation and coding strategy datamcs), and the scheduling period (such as Multi-channel scheduling period mch-scheduling period), logical channel identification (such as logical channel identity or LCID), in the MBMS mechanism based on SC-PTM, the multicast service channel is SC-MTCH, and the configuration of the multicast service channel
  • the information includes at least one of the following information: duration timer (such as SCPTM duration timer onDurationTimerSCPTM), DRX inactive timer (such as SCPTM discontinuous reception inactive timer drx-InactivityTimerSCPTM), scheduling period start deviation (such as SCPTM scheduling period start offset schedulingPeriodStartOffsetSCPTM).
  • the multicast service channel may be bound to the data radio bearer (DRB), that is, if the base station includes the DRB ID and the group-radio network temporary identifier (group-radio network temporary) in the RRC reconfiguration message
  • DRB data radio bearer
  • group-radio network temporary group-radio network temporary
  • the configuration information of the multicast service channel corresponding to the TMGI means that the TMGI corresponds to the multicast service channel, that is, the multicast service channel is the multicast service channel used by the UE when listening to the multicast data of the TMGI of interest.
  • the TMGI that the UE is interested in may be a TMGI corresponding to an application (application, APP) that the UE is interested in, that is, a TMGI associated with the APP that the UE is interested in.
  • the identifier of the network slice corresponds to the multicast service channel, that is, the multicast service channel is the multicast service channel used by the UE when listening to the multicast data of the network slice of interest.
  • the network slice that the UE is interested in may be a network slice corresponding to the APP that the UE is interested in, that is, a network slice associated with the APP that the UE is interested in.
  • the TMGI corresponds to the identifier of the network slice, that is, the TMGI is the TMGI when the UE listens to the multicast data of the network slice of interest.
  • the access network device may use one of the following implementation manners to generate the first message, and the first message supports the configuration information of the multicast service channel corresponding to the network slice. There is no conflict between the first message and the message supporting the configuration information of the multicast service channel corresponding to the TMGI.
  • the first message includes Slicing-MTCH configuration information.
  • the Slicing-MTCH configuration information is as follows, where Slicing-MTCH-Info (Slice Multicast Control Channel) is Slicing-MTCH configuration information, sliceID is the identifier of the network slice, and g- RNTI (Group Radio Network Temporary Identifier) is related information of G-RNTI, slicing-mtch-schedulingInfo (slicing-mtch-schedulingInfo (slicing multicast control channel scheduling information) is the configuration information of the multicast service channel:
  • the first message includes slicing-PMCH (slicing physical multicast channel) configuration information.
  • the slicing-PMCH configuration information is as follows, where Slicing-PMCH-Info (slicing physical multicast channel information) is slicing-PMCH configuration information, sliceID Is the identification of the network slice, pmch-Config (physical multicast channel configuration) is the configuration information of the multicast service channel:
  • the first message includes each MBMS-SessionInfo (multimedia broadcast multicast service session information) cell in Slicing-MBMS-SessionInfo (slicing multimedia broadcast multicast service session information), and the MBMS-SessionInfo cell is as follows, where MBMS -SessionInfo is the MBMS-SessionInfo information element in Slicing-MBMS-SessionInfo, sliceID is the identifier of the network slice, logicalChannelIdentity (logical channel identifier) is the configuration information of the multicast service channel (specifically, LCID related information):
  • the access network device may use one of the following implementation manners to generate the first message, the first message supporting TMGI, identification information of the network slice, and configuration information of the multicast service channel.
  • the message supporting the configuration information of the multicast service channel corresponding to the TMGI includes the identification information of the network slice.
  • the first message includes the SC-mtch-InfoList (single-cell multicast service channel information list) in the SCPTMConfiguration (single-cell point-to-multipoint configuration) of the SC-MCCH-Message (single-cell multicast control channel) SC-MTCH-Info (single cell multicast service channel information), where SC-MTCH-Info (single cell multicast service channel information) supports the configuration information of the multicast service channel corresponding to TMGI, mbmsSessionInfo
  • Multimedia Broadcast and Multicast Service Session Information is the relevant information of the multicast session
  • sliceID is the identifier of the network slice
  • g-RNTI identifier of the network slice
  • sc-mtch-schedulingInfo single cell multicast service channel scheduling information
  • sc-mtch-neighbourCell The single-cell multicast service channel (adjacent cells) are the configuration information of the multicast service channel.
  • multiple multicast sessions correspond to the same network slice identifier:
  • the first message includes the mbmsSessionInfo in the SC-MTCH-Info in the SC-MTCH-Info in the SC-MTCH-InfoList in the SCPTMConfiguration of the SC-MCCH-Message, where the MBMSSessionInfo supports the configuration information of the multicast service channel corresponding to the TMGI, tmgi (temporary mobile Group ID) and sessionId-r13 (session ID) are the configuration information of the multicast service channel, sliceID is the ID of the network slice:
  • the first message includes PMCH-Info (physical multicast channel information) in PMCH-InfoList (physical multicast channel information list) in MBSFNAreaConfiguration of MCCH-Message, where PMCH-Info supports the multicast service channel corresponding to TMGI
  • PMCH-Info supports the multicast service channel corresponding to TMGI
  • the configuration information of pmch-Config and mbms-SessionInfoList are the configuration information of the multicast service channel, and sliceID is the identifier of the network slice.
  • multiple multicast sessions correspond to the same ID of the network slice:
  • the first message includes mbms-SessionInfo of mbms-SessionInfoList, where MBMS-SessionInfo supports the configuration information of the multicast service channel corresponding to TMGI, and tmgi (TMGI), sessionId (session identifier) and logicalChannelIdentity are the configuration of the multicast service channel Information, sliceID is the identifier of the network slice.
  • a multicast session corresponds to the identifier of a network slice:
  • Step 202 The access network device sends a first message to the UE.
  • the access network device sends the first message on the multicast control channel.
  • the first message contains the network slice identifier and the configuration information of the multicast service channel.
  • the access network device may also send the first message to the UE through an RRC reconfiguration message.
  • the access network device receives a network slice identifier and indication information from a core network device, where the indication information indicates that there is multicast data corresponding to the network slice identifier.
  • the access network device can also send multicast data on the multicast service channel identified by the network slice according to the first message, and the multicast data is from the core network.
  • the multicast data identified by the network slice of the device is from the core network.
  • Step 203 The UE receives the first message sent from the access network device.
  • the UE may also store the identifier of the network slice and the configuration information of the multicast service channel in the first message correspondingly.
  • Step 204 The UE receives the multicast data corresponding to the network slice on the multicast service channel.
  • the UE may listen to the multicast data corresponding to the network slice of interest on the multicast service channel corresponding to the network slice of interest.
  • the multicast service channel is a DRB
  • the UE can listen to the multicast data corresponding to the network slice on the DRB corresponding to the network slice.
  • a mobility management entity sends an MBMS session start (MBMS session start) message to a multi-instance CE (Multi-VPN-Instance CE, MCE).
  • MME mobility management entity
  • MCE Multi-VPN-Instance CE
  • the MBMS session start message is used to indicate to start the multicast session.
  • the MBMS session start message includes MBMS Service Area (MBMS service area/MBMS service range), and may also include MBMS Cell List (MBMS cell list).
  • MBMS cell list MBMS Cell List
  • the MCE sends an MBMS session start message to the base stations within the multicast range, and the MBMS session start message includes the MBMS Service Area.
  • the MBMS session start message also includes SC-PTM information, where the SC-PTM information includes a list of MBMS cells.
  • SC-PTM information includes a list of MBMS cells.
  • the MBMS session start message includes the identifier of the network slice, and the identifier of the network slice is used by the receiver to determine the sending range of the multicast session according to the identifier of the network slice.
  • the access network device determines, according to the network slice identifier in the MBMS session start message sent by the core network device, that the sending range of the multicast session does not exceed the coverage range of the cell corresponding to the network slice identifier. In this way, when the access network device sends the multicast data of the multicast session, the sending range of the multicast data is limited to the cell to which the identifier of the network slice is mapped (such as the identifier of the cell).
  • the access network device determines the sending range of the multicast session. For example, the access network device receives the MBMS session start message for the network slice sent by the core network device.
  • the MBMS session start message for the network slice includes the identification information of the network slice, and the access network device determines that the sending range of the multicast session does not exceed The coverage area of the cell corresponding to the identifier of the network slice. In this way, when the access network device sends the multicast data of the multicast session, the sending range of the multicast data is limited to the cell to which the identifier of the network slice is mapped (such as the identifier of the cell).
  • the MBMS session start message (such as the slicing MBMS session start message) for the network slicing can also be introduced.
  • the sending range of the multicast session is determined by the access network device.
  • the core network device determines that the sending range of the multicast session does not exceed the coverage of the cell corresponding to the identification information of the network slice.
  • the AMF/MME sends an MBMS session start message for network slices to the SMF/MCE, and the MBMS session start message for network slices contains the identifier of the network slice.
  • the SMF/MCE limits the sending range of the multicast session to the coverage of the cell corresponding to the identification information of the network slice; or the core network device determines the identification of the cell corresponding to the identification information of the network slice according to the identification information of the network slice Determine the sending range of the multicast session according to the coverage area corresponding to the cell and the obtained service area (service area).
  • the AMF/MME sends the MBMS session start message for network slices to the SMF/MCE, the MBMS session start message for network slices includes the identifier of the network slice and the identifier of the service area (such as service area ID).
  • the SMF/MCE may take the intersection of the coverage of the cell corresponding to the network slice identifier and the service area, and determine that the cell in the intersection is the sending range of the multicast session.
  • Hop on slice (network slice instant messaging) is also called a network slice instant messaging method.
  • the base station broadcasts the data radio bearer (Data Radio Bearer, DRB) configuration information corresponding to the slice on the air interface.
  • DRB Data Radio Bearer
  • the DRB configuration information corresponding to the slice is included in the system information x.
  • the UE does not need to establish an RRC connection with the base station, and can directly configure the DRB corresponding to the slice, thereby directly sending data to the base station.
  • the base station identifies the corresponding slice through the DRB, and then can send data to the core network through the user plane tunnel corresponding to the slice.
  • the core network device may deliver slice multicast data to the UE.
  • UEs that support the Hop on slice mechanism only monitor system information x, and multicast related information (including configuration information of the multicast control channel) is included in system information y, which is different from system information x.
  • the UE does not monitor the system information y, it cannot obtain the relevant information of the multicast control channel in the system information y, and cannot listen to the configuration information of the multicast service channel, and cannot listen to the corresponding multicast service channel. Multicast data. Therefore, in the first manner of the embodiment of the present application, it may also be considered to instruct the UE to read the system information y in combination with the first manner.
  • the improvement is mainly made for the scenario where the DRB configuration information corresponding to the slice is included in the system information x, and the multicast related information is included in the system information y.
  • SIB13 corresponding to the MBMS mechanism based on MBSFN or the SIB20 corresponding to the SC-PTM mechanism is mainly described as SIB20 in the embodiments of this application, and the process of adopting SIB13 is similar, so it will not be repeated.
  • the multicast related information is placed in the system information x.
  • the configuration information of the multicast control channel, the network slice identifier and the configuration information of the DRB are included in the same message.
  • the access network device may not additionally send the configuration information of the multicast control channel corresponding to the slice, thereby avoiding additional signaling overhead.
  • the system message x is as follows, where Slicelist is a network slice list, slice ID is a network slice identifier, DRB configuration (DRB configuration) is DRB configuration information, and MCCH configuration (multicast control channel configuration) is multicast related information:
  • the MCCH configuration and the network slice identifier correspond one-to-one.
  • the MCCH configuration is shared by all network slice identifiers.
  • the access network device may send first indication information to the UE, where the first indication information is used to indicate that the UE needs to read multicast data.
  • the UE specifically refers to a UE that works through hop on slice, that is, the UE is a UE that only receives multicast data through the network slicing mechanism.
  • the access network device in addition to sending the first indication information to the UE, also sends which system message to read to the UE.
  • the first indication information is used to instruct the UE to read the first message in the first manner, that is, to instruct the UE to read the configuration information of the multicast control channel.
  • the first indication information indicates that the type of the system message read by the UE is SIB20.
  • the UE can obtain the configuration information of the multicast control channel MCCH through the SIB20, and then the UE can obtain the configuration information of the multicast service channel corresponding to the identifier of the network slice by monitoring the MCCH.
  • the access network device puts the configuration information of the multicast control channel, as well as the network slice identifier and the configuration information of the multicast service channel in the same SIB, then the UE only needs to listen to the broadcast message to obtain the network slice Identifies the configuration information of the corresponding multicast service channel.
  • the subsequent methods are also applicable, so I won't repeat them here.
  • the first indication information may be included in the same message as the network slice identifier and DRB configuration information.
  • the configuration information of the multicast control channel related to the network slice is included in the SIB20.
  • the access network device includes in the system information x the configuration information of the DRB corresponding to the identifier of the network slice, and the first indication information used to instruct the UE to read the SIB20.
  • the UE can obtain the configuration information of the multicast control channel by reading the SIB20, and then monitor the multicast control channel to obtain the network slice identification and multicast service channel configuration information, and the network slice identification and group Corresponds to the broadcast service channel.
  • the information element sent by the access network device to the UE is as follows.
  • the information element includes the network slice ID (slice ID), DRB configuration information (DRB configuration), first indication information (broadcast indication broadcast indication), and system message type (MBMS SIB type SIB type for MBMS).
  • the system message type is optional cell.
  • the core network device indicates that the access network device has multicast data corresponding to the network slice identifier, that is, slice-specific (network slice dedicated) multicast data may be sent subsequently.
  • the access network device generates a SIB message (such as SIB20) containing the configuration information of the multicast control channel.
  • a multicast user plane tunnel for network slicing is established between the access network device and the core network device.
  • the user plane tunnel between the access network device and the core network supports unicast data and multicast data as well as multicast data for network slicing.
  • the core network device can also connect to the NG3 interface (that is, between the base station and the UPF). Add a multicast indication to the GTP-U (GPRS Tunneling Protocol-User Plane) package.
  • GTP-U GPRS Tunneling Protocol-User Plane
  • the core network device if the core network device receives the information transmitted by the UE in the Hop on slice mode, the core network device sends the network slice identifier and second indication information to the UE, and the second indication information is used to indicate that there is Multicast data for this network slice. In this way, the UE can determine which network slice has multicast data.
  • the UE listens to the SIB message containing the configuration information of the multicast control channel broadcast by the access network device, and then obtains the configuration information of the multicast service channel corresponding to the network slice by monitoring the multicast control channel. Subsequently, the multicast data can be listened to on the multicast service channel corresponding to the network slice with the multicast data.
  • the UE when it registers for the first time, it may send the indication information transmitted by the UE in the Hop on slice mode to the core network device.
  • the access network device sends the network slice identification and the configuration information of the multicast service channel to the UE.
  • the network slice identification corresponds to the multicast service channel, and the UE The identification of the network slice and the configuration information of the multicast service channel can be directly obtained.
  • the UE can obtain multicast data through the multicast service channel corresponding to the identifier of the network slice, thereby realizing multicast at the granularity of network slices and realizing a multicast mechanism based on network slices.
  • the DU sends a second message to the UE.
  • the second message includes the identifier of the multicast session and the configuration information of the multicast service channel.
  • the identifier corresponds to the multicast service channel, and the process includes:
  • Step 301 The CU generates a multicast session establishment message, and the multicast session establishment message includes the identifier of the multicast session.
  • the multicast session establishment message is used to establish a multicast session.
  • the message name of the multicast session establishment message is not limited.
  • the multicast session establishment message may be MBMS Session setup request (MBMS Session Setup Request). )news.
  • the identifier of the multicast session includes at least one of the following information: TMGI, session identifier, or network slice identifier.
  • the identification information of the multicast session includes TMGI; or the identification information of the multicast session includes the session identifier; or the identifier of the multicast session includes the identifier of a network slice; or the identifier of the multicast session includes TMGI And session identifier; or the multicast session identifier includes TMGI and network slice identifiers; or the multicast session identifier includes session identifier and network slice identifier; or the multicast session identifier includes TMGI and session identifier And the identification of the network slice.
  • the identifier of the multicast session may also be the group radio network temporary identifier G-RNTI.
  • G-RNTI group radio network temporary identifier
  • the access network device will tell the UE the correspondence between the DRB ID and G-RNTI.
  • the access network device includes the DRB ID and G-RNTI in the RRC reconfiguration message.
  • the CU additionally informs the DU which UEs and which DRBs of which G-RNTI is associated with, for example, the CU sends the following list to the DU:
  • the UE ID may be a gNB-CU UE F1AP ID, or a gNB-DU UE F1AP ID, or it may be a cell-radio network temporary identifier (C-RNTI).
  • the DRB ID can be DRB ID, or UP TNL Information (uplink transmission network layer information), such as tunnel endpont identity (TEID).
  • the DU receives multicast data from the CU from the user plane tunnel corresponding to the G-RNTI, the DU will use the list previously sent by the CU (e.g., UE List UE list), the list includes the DRB corresponding to the UE, and the multicast data is sent through the DRB corresponding to the UE in the UE list, so that the CU-DU architecture supports the multicast mechanism.
  • the list previously sent by the CU (e.g., UE List UE list)
  • the list includes the DRB corresponding to the UE
  • the multicast data is sent through the DRB corresponding to the UE in the UE list, so that the CU-DU architecture supports the multicast mechanism.
  • the user plane tunnel corresponding to the G-RNTI is not established between the CU and the DU, the user plane tunnel corresponding to the DRB of the UE is used to transmit the multicast data. Then when the CU sends data through the user plane tunnel corresponding to the DRB of the UE, the CU needs to indicate whether the current data packet of the DU is unicast or multicast, so that the DU can decide whether to use C-RNTI or G-RNTI to scramble the data. code. For example, the CU may add a 1-bit indication to the GTP-U header, and when the value is 0, it means unicast, and the DU decides to use the C-RNTI to scramble the data. When the value is 1, it means multicast, and the DU decides to use G-RNTI to scramble the data.
  • the multicast session establishment message may also include configuration information of the multicast service channel, and/or third indication information.
  • the third indication information is used to indicate whether the base station adopts the MBSFN mechanism or the SC-PTM mechanism for air interface multicast.
  • the multicast service channel includes MTCH or SC-MTCH.
  • Step 302 The CU sends a multicast session establishment message to the DU.
  • CU and DU belong to the same access network device.
  • the CU may also send a third message to the DU, where the third message is used to instruct the DU to feed back one downlink user plane tunnel endpoint information or a group of downlink user plane tunnel endpoint information.
  • the DU may establish a user plane tunnel corresponding to the multicast between the CUs according to the instruction in the third message of the CU.
  • the third message and the multicast session establishment message may be the same message, or the third message and the multicast session establishment message may be different messages.
  • the CU may also send instruction information to the DU, where the instruction information is used to instruct the DU to establish a common user plane tunnel for all multicast sessions, or to suggest a corresponding user plane tunnel for each multicast session.
  • Step 303 The DU receives the multicast session establishment message sent by the CU.
  • the DU may feed back the endpoint information of a downlink user plane tunnel to the CU, that is, the DU establishes a common user plane tunnel for all multicast sessions.
  • the DU feeds back a set of downlink user plane tunnel endpoint information to the CU, the set of downlink user plane tunnel endpoint information includes the downlink user plane tunnel endpoint information corresponding to each multicast session, that is, the DU is for each multicast session.
  • the session establishes a corresponding user plane tunnel.
  • a set of downlink user plane tunnel endpoint information includes the identifier of each multicast session and the corresponding downlink user plane tunnel endpoint information.
  • the CU receives a downlink user plane tunnel endpoint information from the DU.
  • the CU receives a set of downlink user plane tunnel endpoint information from the DU, where the set of downlink user plane tunnel endpoint information includes downlink user plane tunnel endpoint information corresponding to the user plane tunnel of each multicast session.
  • Step 304 The DU sends a second message to the UE.
  • the second message includes the identifier of the multicast session and the configuration information of the multicast service channel, and the identifier of the multicast session corresponds to the multicast service channel.
  • the second message may be generated by the CU and then sent to the DU, or the second message may be generated by the DU.
  • the DU sends the configuration information of the multicast service channel to the CU.
  • the CU generates a corresponding second message according to the configuration information of the multicast service channel and sends it to the DU, and the DU sends the second message to UE.
  • the DU sends the second message on MCCH/SC-MCCH.
  • the CU informs the DU of the multicast data corresponding to the identifier of the subsequent multicast session, the DU generates the second message according to the identifier of the multicast session and the configuration information of the multicast service channel, and the DU broadcasts the second message To the UE.
  • the second message refer to the first message in step 201 in the first manner.
  • the configuration information of the multicast service channel in step 201 which will not be repeated here.
  • the DU If the DU establishes a common user plane tunnel for all multicast sessions. When the multicast data starts to be transmitted, the DU needs to determine which multicast session the received multicast data or the soon-to-be-received multicast data is the multicast data. In this way, the DU can determine which UE or UEs to deliver the multicast data to according to the determined multicast session to which the multicast data belongs.
  • the CU may also send a fourth message to the DU, and the DU receives a fourth message from the CU.
  • the fourth message is used to instruct to start the multicast session, and the fourth message includes the identifier of the multicast session.
  • the message name of the fourth message is not limited.
  • the fourth message is an MBMS session start (MBMS session start) message.
  • the fourth message may also include the identifier of the multicast session, so that the DU can determine that what is subsequently received in the user plane tunnel is the multicast data corresponding to the multicast session identifier.
  • the fourth message may also include a cell list (cell list).
  • the CU determines the cell list according to the identifier of the multicast session and/or the MBMS service area.
  • the DU may also report the mapping relationship between the identifier of the multicast session and the cell identifier.
  • a user plane tunnel carries a multicast session identifier.
  • the CU can also send data to the DU through a public user plane tunnel.
  • the DU receives multicast data from the CU through a public user plane tunnel, and the multicast data includes the multicast data and the identifier of the multicast session.
  • the CU includes the identification information of the multicast session in the GTP-U header of the F1 user plane tunnel, so that the DU knows which multicast session identification information will be used to send the multicast data in the subsequent multicast service channel.
  • Step 305 The UE receives the second message sent by the DU.
  • Step 306 The UE uses the multicast service channel to receive the multicast data corresponding to the network slice.
  • the DU sends the session establishment message to the CU, and the CU sends the identifier of the multicast session and the configuration information of the multicast service channel to the UE.
  • the identifier of the network slice and the multicast service channel are the same.
  • the UE can directly obtain the identifier of the network slice and the configuration information of the multicast service channel, so that the UE can obtain the multicast data through the multicast service channel corresponding to the identifier of the network slice, so that under the CU-DU separation architecture, It can realize the sending and receiving of the multicast session, and when the identifier of the multicast session includes the identifier of the network slice, the network slice granular multicast can be realized, and the multicast mechanism based on the network slice can be realized.
  • the core network device sends a NAS message to the UE.
  • the NAS message includes the identifier of the network slice and TMGI.
  • the identifier of the network slice corresponds to the TMGI.
  • the process includes:
  • Step 401 The core network device obtains the identifier of the network slice and the TMGI, and the identifier of the network slice corresponds to the TMGI.
  • the TMGI corresponds to the identifier of the network slice, that is, the TMGI is the TMGI when the UE listens to the multicast data of the network slice of interest.
  • the core network device may also obtain the identifier of the application program, and the identifier of the application program corresponds to the identifier of the network slice.
  • an application function entity (application function, AF) sends a network slice identifier and TMGI to a policy control function (policy control function, PCF) in the core network device, and the network slice identifier corresponds to the TMGI.
  • policy control function policy control function
  • the PCF sends the corresponding network slice identifier and TMGI to the access and mobility management function entity (access and mobility management function, AMF).
  • the method for the core network device to obtain the mapping relationship between the network slice identifier and TMGI is not limited.
  • the mapping relationship between the network slice identifier and TMGI is included in the user route selection policy (UE route selection policy, URSP) .
  • Step 402 The core network device sends a NAS message to the UE.
  • the NAS message includes the identifier of the network slice and the TMGI, and the identifier of the network slice corresponds to the TMGI.
  • the AMF may also send a NAS message to the UE, and the NAS message includes the URSP.
  • the multicast mechanism on the base station side may remain unchanged.
  • the base station sends a fifth message to the UE.
  • the fifth message includes configuration information of the TMGI and the multicast service channel, and the TMGI corresponds to the multicast service channel.
  • Step 403 The UE receives the NAS message sent from the core network device.
  • the UE may also receive a fifth message sent by the base station, where the fifth message includes configuration information of a TMGI and a multicast service channel, and the TMGI corresponds to the multicast service channel.
  • Step 404 The UE uses the multicast service channel corresponding to the TMGI to receive the multicast data corresponding to the network slice.
  • the UE determines the TMGI corresponding to the network slice of interest, and then uses the multicast service channel corresponding to the TMGI to receive the multicast data corresponding to the network slice.
  • the core network device sends the network slice identifier and TMGI to the UE without changing the air interface.
  • the TMGI corresponds to the network slice identifier, and the UE can also obtain the network slice.
  • the identifier corresponds to the TMGI, so that the UE can finally receive the multicast data corresponding to the network slice through the multicast service channel corresponding to the TMGI, so as to realize the multicast at the granularity of the network slice and the multicast mechanism based on the network slice.
  • the embodiment of the present application also provides a network slicing multicast device As shown in FIG. 5, the network slicing multicast device 500 includes a processing unit 501 and a transceiver unit 502, and the device 500 can be used to implement the method described in the foregoing embodiment of the method applied to core network equipment, UE, or access network equipment Methods.
  • the apparatus 500 is applied to an access network device, where the access network device may be an access network device or a DU in an access network device.
  • the processing unit 501 is configured to generate the first message
  • the transceiving unit 502 is configured to send a first message to the user terminal UE, the first message including the identifier of the network slice and the configuration information of the multicast service channel, and the identifier of the network slice is related to the multicast service channel. correspond.
  • the transceiving unit 502 is further configured to receive a network slice identifier and indication information from a core network device, where the indication information indicates the multicast data corresponding to the network slice identifier.
  • the first message further includes a temporary mobility group identifier TMGI, and the TMGI corresponds to the identifier of the network slice.
  • the configuration information of the multicast service channel includes at least one of the following information: last subframe configuration, data modulation and coding value, scheduling period, duration timer, DRX inactive timer, scheduling Cycle start deviation.
  • the transceiver unit 502 is further configured to use the multicast service channel to send the multicast data corresponding to the network slice.
  • the apparatus 500 is applied to a user terminal UE.
  • the processing unit 501 is configured to receive a first message from an access network device through the transceiver unit 502, where the first message includes the identifier of the network slice and the configuration information of the multicast service channel, and the network slice
  • the identifier corresponds to the multicast service channel; the multicast service channel is used to receive the multicast data corresponding to the network slice.
  • the first message further includes a temporary mobility group identifier TMGI, and the TMGI corresponds to the identifier of the network slice.
  • the configuration information of the multicast service channel includes at least one of the following information: last subframe configuration, data modulation and coding value, scheduling period, duration timer, DRX inactive timer, scheduling Cycle start deviation.
  • the apparatus 500 is applied to the access network distribution unit DU.
  • the processing unit 501 is configured to receive, through the transceiver unit 502, a multicast session establishment message sent by the access network centralization unit CU, where the multicast session establishment message includes the identifier of the multicast session; and sends the message to the user terminal UE.
  • the second message, the second message includes the identifier of the multicast session and the configuration information of the multicast service channel, and the identifier of the multicast session corresponds to the multicast service channel.
  • the identifier of the multicast session includes at least one of the following information: TMGI, session identifier, or network slice identifier.
  • the transceiving unit 502 is further configured to feed back a set of downlink user plane tunnel endpoint information to the CU; or to feed back a set of downlink user plane tunnel endpoint information to the CU, the set of downlink user plane tunnel endpoint information
  • the tunnel endpoint information includes the downlink user plane tunnel endpoint information corresponding to each multicast session.
  • the transceiving unit 502 is further configured to receive a third message from the CU, where the third message is used to instruct the DU to feed back a downlink user plane tunnel endpoint information or a group of downlink users Face tunnel endpoint information.
  • the transceiving unit 502 is further configured to receive a fourth message from the CU, the fourth message is used to instruct to start the multicast session, and the fourth message includes the multicast The ID of the session.
  • the transceiving unit 502 is further configured to receive data from the CU through a public user plane tunnel, and the data includes multicast data and an identifier of the multicast session.
  • the apparatus 500 is applied to the access network central unit CU.
  • the processing unit 501 is configured to generate a multicast session establishment message
  • the transceiver unit 502 is configured to send a multicast session establishment message to the access network distribution unit DU, where the multicast session establishment message includes the identifier of the multicast session.
  • the identifier of the multicast session includes at least one of the following information: TMGI, session identifier, or network slice identifier.
  • the transceiving unit 502 is further configured to receive a set of downlink user plane tunnel endpoint information from the DU; or receive a set of downlink user plane tunnel endpoint information from the DU, and the set of downlink user plane tunnel endpoint information
  • the user plane tunnel endpoint information includes the downlink user plane tunnel endpoint information corresponding to the user plane tunnel of each multicast session.
  • the transceiving unit 502 is further configured to send a third message to the DU, where the third message is used to instruct the DU to feed back a downlink user plane tunnel endpoint information or a group of downlink user planes Tunnel endpoint information.
  • the transceiver unit 502 is further configured to send a fourth message to the DU, where the fourth message is used to instruct to start the multicast session, and the fourth message includes the multicast session Logo.
  • the transceiving unit 502 also sends data to the DU through a public user plane tunnel, and the data includes multicast data and an identifier of the multicast session.
  • the apparatus 500 is applied to a core network device.
  • the processing unit 501 is configured to obtain a network slice identifier and a temporary mobility group identifier TMGI, where the network slice identifier corresponds to the TMGI;
  • the transceiving unit 502 is configured to send a non-access stratum NAS message to the user terminal UE.
  • the NAS message includes a network slice identifier and a TMGI, and the network slice identifier corresponds to the TMGI.
  • the processing unit 501 is further configured to obtain an identifier of an application program, and the identifier of the application program corresponds to the identifier of the network slice.
  • the NAS message further includes identification information of an application, and the identification of the application corresponds to the identification of the network slice.
  • the apparatus 500 is applied to a user terminal UE.
  • the processing unit 501 is configured to receive, through the transceiver unit 502, a NAS message sent from a core network device.
  • the NAS message includes the network slice identifier and the temporary mobile group identifier TMGI, the network slice identifier and all The TMGI corresponds; the multicast service channel corresponding to the TMGI is used to receive the multicast data corresponding to the network slice.
  • the NAS message further includes identification information of an application, and the identification of the application corresponds to the identification of the network slice.
  • the transceiver unit 502 is further configured to receive a fifth message sent by the base station, and the fifth message includes configuration information of the TMGI and the multicast service channel, and the TMGI and the multicast service channel Corresponding.
  • each functional unit in each embodiment of the present application It can be integrated in one processing unit, or it can exist alone physically, or two or more units can be integrated in one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium.
  • the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including a number of instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disks or optical disks and other media that can store program codes. .
  • an embodiment of the present application also provides a schematic structural diagram of a network slicing multicast device 600.
  • the apparatus 600 may be used to implement the method described in the foregoing method embodiment applied to an access network device, a UE, or a core network device, and reference may be made to the description in the foregoing method embodiment.
  • the apparatus 600 may be in an access network device, a UE, or a core network device, or may be an access network device, a UE, or a core network device.
  • the apparatus 600 includes one or more processors 601, and the one or more processors 601 can implement the method for access network equipment, UE, or core network equipment in the above-mentioned embodiment.
  • processor 601 may also implement other functions in addition to implementing the methods in the above-mentioned embodiments.
  • the processor 601 may execute instructions to make the device 600 execute the method described in the foregoing method embodiment.
  • the instructions may be stored in the processor in whole or in part, such as the instruction 603, or in the memory 602 coupled to the processor, in whole or in part, such as the instruction 604, or the instructions 603 and 604 may be used together to make The apparatus 600 executes the method described in the foregoing method embodiment.
  • the communication device 600 may also include a circuit, and the circuit may implement the functions of the access network device, the UE, or the core network device in the foregoing method embodiment.
  • the device 600 may include one or more memories 602, on which instructions 604 are stored, and the instructions may be executed on the processor, so that the device 600 executes the above method.
  • data may also be stored in the memory.
  • the optional processor may also store instructions and/or data.
  • the one or more memories 602 may store the corresponding relationship described in the foregoing embodiment, or related parameters or tables involved in the foregoing embodiment.
  • the processor and the memory can be provided separately or integrated together.
  • the device 600 may further include a transceiver 605 and an antenna 606.
  • the processor 601 may be referred to as a processing unit, which controls a device (terminal or base station).
  • the transceiver 605 may be called a transceiver, a transceiver circuit, or a transceiver unit, etc., and is used to implement the transceiver function of the device through the antenna 606.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application specific integrated circuit (ASIC), a ready-made programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA ready-made programmable gate array
  • Programming logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application can be directly embodied as executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the embodiment of the present application also provides a computer-readable medium on which a computer program is stored.
  • the computer program When the computer program is executed by a computer, the computer program implements the method described in any of the above-mentioned method embodiments applied to an access network device, a UE, or a core network device. Multicast method of network slicing.
  • the embodiments of the present application also provide a computer program product that, when executed by a computer, implements the multicast method for network slicing described in any of the above-mentioned method embodiments applied to access network equipment, UE, or core network equipment .
  • the computer may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk, SSD)) etc.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the network slicing described in any method embodiment applied to an access network device, a UE, or a core network device The multicast method.
  • the foregoing processing device may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, At this time, the processor may be a general-purpose processor, which is realized by reading the software code stored in the memory, and the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a computer.
  • computer readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or can be used to carry or store instructions or data in the form of structure
  • Any connection can suitably become a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable , Fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, wireless and microwave are included in the fixing of the media.
  • Disk and disc include compact discs (CD), laser discs, optical discs, digital versatile discs (DVD), floppy discs and Blu-ray discs. Disks usually copy data magnetically, while discs The laser is used to optically copy the data. The above combination should also be included in the protection scope of the computer-readable medium.
  • the embodiment of the present application also provides a computer-readable medium on which a computer program is stored.
  • the computer program When the computer program is executed by a computer, the computer program implements the method described in any of the above-mentioned method embodiments applied to an access network device, a UE, or a core network device. Multicast method of network slicing.
  • the embodiments of the present application also provide a computer program product that, when executed by a computer, implements the multicast method for network slicing described in any of the above-mentioned method embodiments applied to access network equipment, UE, or core network equipment .
  • the computer may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (for example, a solid state disk, SSD)) etc.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the network slicing described in any method embodiment applied to an access network device, a UE, or a core network device The multicast method.
  • the foregoing processing device may be a chip, and the processor may be implemented by hardware or software.
  • the processor When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc.; when implemented by software, At this time, the processor may be a general-purpose processor, which is realized by reading the software code stored in the memory, and the memory may be integrated in the processor, may be located outside the processor, and exist independently.
  • the disclosed system, device, and method may be implemented in other ways.
  • the device embodiments described above are merely illustrative, for example, the division of units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented.
  • the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments of the present application.
  • the functional units in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.
  • the computer-readable medium includes a computer storage medium and a communication medium, where the communication medium includes any medium that facilitates the transfer of a computer program from one place to another.
  • the storage medium may be any available medium that can be accessed by a computer.
  • computer readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or can be used to carry or store instructions or data in the form of structure
  • Any connection can suitably become a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave
  • coaxial cable , Fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, wireless and microwave are included in the fixing of the media.
  • Disk and disc include compact discs (CD), laser discs, optical discs, digital versatile discs (DVD), floppy discs and Blu-ray discs. Disks usually copy data magnetically, while discs The laser is used to optically copy the data. The above combination should also be included in the protection scope of the computer-readable medium.

Landscapes

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

Abstract

本申请实施例涉及一种网络切片的组播方法及装置，用以实现网络切片粒度的组播，该网络切片的组播方法为：接入网设备生成第一消息；所述接入网设备向用户终端UE发送第一消息，所述第一消息包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应。

Description

一种网络切片的组播方法及装置
相关申请的交叉引用
本申请要求在2019年09月30日提交中国专利局、申请号为201910945418.2、申请名称为“一种网络切片的组播方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种网络切片的组播方法及装置。
背景技术
组播(multicast)技术作为一种通信方式，能够有效地解决单点发送、多点接收的问题，从而实现网络中点到多点的高效数据传输，以节省网络带宽、降低网络负载。当网络中的某些设备(即接收者receiver)需要信息时，若采用组播的方式，可以让这些设备加入同一个组播组(multicast group)，组播源(即source)向该组播组只需发送一份信息，然后该信息会准确地发送给该组播组中的每个设备。
5G网络中引入了网络切片的概念，如何在具有网络切片的网络中实现组播，是值得考虑的问题。
发明内容
本申请提供一种网络切片的组播方法及装置，以期实现网络切片粒度的组播。
第一方面，本申请提供了一种网络切片的组播方法，包括接入网设备生成第一消息；向UE发送第一消息，所述第一消息中包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应；UE接收来自接入网设备的第一消息，所述UE使用所述组播业务信道接收所述网络切片对应的组播数据。
上述方法中，接入网设备将网络切片的标识和组播业务信道的配置信息发送给UE，网络切片的标识和组播业务信道相对应，UE可以直接获取到网络切片的标识和组播业务信道的配置信息，这样，UE可以通过网络切片的标识对应的组播业务信道获取组播数据，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。
在一种可能的设计中，还包括：所述接入网设备接收来自核心网设备的网络切片标识和指示信息，所述指示信息指示有所述网络切片标识对应的组播数据。可选的，可以是在接入网设备生成第一消息之后，所述接入网设备接收来自核心网设备的网络切片标识和指示信息。
通过上述方法，接入网设备通过接收核心网设备发送的网络切片标识和指示信息，可以确定后续可能会接收到核心网设备发送的该网络切片对应的组播数据，以便于接入网设备做好传输组播数据前的准备，如生成第一消息等。
在一种可能的设计中，所述第一消息中还可以包括临时移动组标识TMGI，所述TMGI和所述网络切片的标识相对应。
通过上述方法，接入网设备还可以将TMGI发送给UE，TMGI和网络切片的标识相对应，UE还可以直接获取到网络切片的标识对应的TMGI。这样，UE可以通过TMGI对应的组播业务信道接收组播数据，并可以获知组播数据对应的网络切片标识，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。并且接入网设备通过一条消息就可以将网络切片的标识相对应的组播业务信道的配置信息，以及网络切片的标识相对应的TMGI发送给UE，减少信令消耗。
在一种可能的设计中，所述组播业务信道的配置信息包括以下信息中的至少一种：最后子帧配置，数据调制编码取值、调度周期、逻辑信道标识、持续时间计时器、DRX非激活计时器、调度周期开始偏差。
在一种可能的设计中，所述接入网设备还可以使用所述组播业务信道发送所述网络切片对应的组播数据。
通过上述方法，接入网设备通过组播业务信道发送网络切片对应的组播数据，这样UE可以通过网络切片的标识对应的组播业务信道接收到组播数据，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。
在一种可能的设计中，所述接入网设备可以为接入网分布单元DU。
第二方面，本申请提供了一种网络切片的组播方法，包括接入网集中单元CU生成组播会话建立消息，向接入网分布单元DU发送组播会话建立消息，所述组播会话建立消息中包括组播会话的标识；DU接收CU发送的组播会话建立消息；DU向UE发送第二消息，所述第二消息中包括组播会话的标识和组播业务信道的配置信息，所述组播会话的标识和所述组播业务信道相对应。
上述方法中，DU将组播会话建立消息发送给CU，CU将组播会话的标识和组播业务信道的配置信息发送给UE，网络切片的标识和组播业务信道相对应，UE可以直接获取到网络切片的标识和组播业务信道的配置信息，这样UE可以通过网络切片的标识对应的组播业务信道获取到组播数据，从而在CU-DU分离架构下，也能够实现组播会话的收发，并且在组播会话的标识包括网络切片的标识时，能够实现网络切片粒度的组播，实现基于网络切片的组播机制。
在一种可能的设计中，所述组播会话的标识包括以下信息中的至少一种：TMGI、会话标识、或网络切片的标识。可选的，所述组播会话的标识可以包括TMGI；或者所述组播会话的标识包括会话标识；或者所述组播会话的标识包括网络切片的标识；或者所述组播会话的标识包括TMGI和会话标识；或者所述组播会话的标识包括TMGI和网络切片的标识；或者所述组播会话的标识包括会话标识和网络切片的标识；或者所述组播会话的标识包括TMGI、会话标识和网络切片的标识。
在一种可能的设计中，所述DU还可以向所述CU反馈一个下行用户面隧道端点信息；所述CU接收来自所述DU的一个下行用户面隧道端点信息；或者所述DU还可以向所述CU反馈一组下行用户面隧道端点信息，所述一组下行用户面隧道端点信息包括每个组播会话对应的下行用户面隧道端点信息；所述CU接收来自所述DU的一组下行用户面隧道端点信息。
可选的，DU当建立一个所有组播会话公共的用户面隧道时，向CU反馈一个下行用户面隧道端点信息；DU当建立每个组播会话对应的用户面隧道时，向CU反馈包括每个组播会话对应的下行用户面隧道端点信息的一组下行用户面隧道端点信息。
通过上述方法，DU通过建立与CU之间的组播会话对应的用户面隧道，可以实现组播数据在CU和DU之间的传输，这样，DU可以通过与CU之间的用户面隧道接收组播数据，然后将组播数据发送给终端设备UE，从而实现组播会话的收发。
在一种可能的设计中，CU还可以向所述DU发送第三消息，所述第三消息用于指示所述DU反馈一个下行用户面隧道端点信息还是反馈一组下行用户面隧道端点信息；所述DU接收来自所述CU的第三消息。
具体的，DU在建立与CU之间的用户面隧道之前，即在DU向CU反馈下行用户面隧道端点信息之前，CU向DU发送第三消息。
通过上述方法，DU通过CU指示的第三消息，确定建立所有组播会话公共的用户面隧道，或者建立每个组播会话对应的用户面隧道，从而实现组播数据的传输。
在一种可能的设计中，所述CU还可以向所述DU发送第四消息，所述第四消息用于指示启动所述组播会话，所述第四消息包括所述组播会话的标识；所述DU还可以接收来自所述CU的第四消息。
通过上述方法，CU通过向DU发送包括组播会话的标识的第四消息，向DU指示启动所述组播会话，DU确定后续通过F1接口从CU接收哪个组播会话的标识对应的组播数据，从而通过控制面实现DU获取组播数据对应的组播会话标识的目的，从而使得DU可以在所述组播会话标识对应的组播业务信道上发送所述组播数据。
在一种可能的设计中，还包括：所述CU通过公共的用户面隧道向所述DU发送数据，所述数据包含组播数据以及所述组播会话的标识；DU通过公共的用户面隧道接收来自所述CU的数据。
通过上述方法，CU通过F1接口上公共的用户面隧道向DU发送包含组播数据以及所述组播会话的标识的数据，从而通过用户面实现DU获取组播数据对应的组播会话标识的目的，从而使得DU可以在所述组播会话的标识对应的组播业务信道上发送所述组播数据。
第三方面，本申请提供了一种网络切片的组播方法，包括核心网设备获取网络切片的标识和临时移动组标识TMGI，所述网络切片的标识和所述TMGI相对应；所述核心网设备向用户终端UE发送非接入层NAS消息，所述NAS消息中包括网络切片的标识和TMGI，所述网络切片的标识和所述TMGI相对应；UE接收来自核心网设备发送的NAS消息，所述UE使用所述TMGI对应的组播业务信道接收所述网络切片对应的组播数据。
上述方法中，在不改变空口的情况下，核心网设备将网络切片的标识和TMGI发送给UE，TMGI和网络切片的标识相对应，UE还可以获取到网络切片的标识对应的TMGI，这样，UE最终可以通过TMGI对应的组播业务信道接收网络切片对应的组播数据，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。
在一种可能的设计中，所述核心网设备还可以获取应用程序的标识，所述应用程序的标识和所述网络切片的标识相对应。
通过上述方法，核心网设备获取到网络切片的标识与应用程序的标识，应用程序的标识和网络切片的标识相对应，这样核心网设备还可以将网络切片的标识对应的应用程序的标识发送给UE，UE可以在感兴趣的应用程序的网络切片对应TMGI的组播业务信道上接收组播数据，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。
在一种可能的设计中，所述NAS消息中还可以包括应用程序的标识信息，所述应用程序的标识和所述网络切片的标识相对应。
通过上述方法，核心网设备还可以将应用程序的标识信息发送给UE，UE还可以获取到网络切片的标识对应的应用程序的标识，这样，UE可以在感兴趣的应用程序的网络切片对应TMGI的组播业务信道接收组播数据，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。
在一种可能的设计中，所述UE还可以接收基站发送的第五消息，所述第五消息中包括TMGI和组播业务信道的配置信息，所述TMGI和所述组播业务信道相对应。
通过上述方法，在不改变空口的情况下，基站将包括TMGI和组播业务信道的配置信息发送给UE，TMGI和组播业务信道相对应，UE可以通过感兴趣的网络切片找到对应的TMGI，从而通过TMGI对应的组播业务信道接收组播数据，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。
第四方面，提供了一种网络切片的组播装置。本申请提供的装置具有上述方法方面接入网设备、UE、核心网设备的功能，其包括用于执行上述方法方面所描述的步骤或功能相对应的部件(means)。所述步骤或功能可以通过软件实现，或硬件(如电路)实现，或者通过硬件和软件结合来实现。其中，接入网设备包括接入网设备，和/或CU-DU。
在一种可能的设计中，上述装置包括一个或多个处理器和通信单元。所述一个或多个处理器被配置为支持所述装置执行上述方法中接入网设备、UE、核心网设备相应的功能。
可选的，所述装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，其保存装置必要的程序指令和/或数据。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置。本申请并不限定。
另一个可能的设计中，上述装置，包括收发器、处理器和存储器。该处理器用于控制收发器或输入/输出电路收发信号，该存储器用于存储计算机程序，该处理器用于运行该存储器中的计算机程序，使得该装置执行第一方面或第一方面中任一种可能实现方式中接入网设备、UE完成的方法，或执行第二方面或第二方面中任一种可能实现方式中接入网设备、UE完成的方法，或执行第三方面或第三方面中任一种可能实现方式中核心网设备、UE完成的方法。
在一种可能的设计中，上述装置包括一个或多个处理器和通信单元。所述一个或多个处理器被配置为支持所述装置执行上述方法中接入网设备、UE、核心网设备相应的功能。
可选的，所述装置还可以包括一个或多个存储器，所述存储器用于与处理器耦合，其保存接入网设备、UE、核心网设备必要的程序指令和/或数据。所述一个或多个存储器可以和处理器集成在一起，也可以与处理器分离设置。本申请并不限定。
所述装置可以位于接入网设备、UE、核心网设备中，或为接入网设备、UE、核心网设备。
另一个可能的设计中，上述装置，包括收发器、处理器和存储器。该处理器用于控制收发器或输入/输出电路收发信号，该存储器用于存储计算机程序，该处理器用于运行存储器中的计算机程序，使得该装置执行第一方面或第一方面中任一种可能实现方式中接入网设备、UE完成的方法，或执行第二方面或第二方面中任一种可能实现方式中接入网设备、UE完成的方法，或执行第三方面或第三方面中任一种可能实现方式中核心网设备、UE完成的方法。
第五方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第一方面、第二方面、第三方面，或第一方面、第二方面、第三方面中任一种 可能实现方式中的方法的指令。
第六方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面、第二方面、第三方面，或第一方面、第二方面、第三方面中任一种可能实现方式中的方法。
第七方面，本申请提供了一种芯片***，该芯片***包括收发器，用于实现上述各方面的方法中接入网设备、UE、核心网设备的功能，例如，例如接收或发送上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片***还包括存储器，所述存储器，用于保存程序指令和/或数据。该芯片***，可以由芯片构成，也可以包括芯片和其他分立器件。
附图说明
图1为本申请实施例提供的一种应用场景示意图；
图2为本申请实施例提供的一种网络切片的组播流程示意图；
图3为本申请实施例提供的一种网络切片的组播流程示意图；
图4为本申请实施例提供的一种网络切片的组播流程示意图；
图5为本申请实施例提供的一种网络切片的组播装置的结构示意图；
图6为本申请实施例提供的一种网络切片的组播装置的结构示意图。
具体实施方式
下面将结合附图对本发明作进一步地详细描述。
本申请实施例的技术方案可以应用于各种通信***，例如：***(4th Generation，4G)，4G***包括***长期演进(long term evolution，LTE)***，第五代(5th Generation，5G)***，如新一代无线接入技术(new radio access technology，NR)，及未来的通信***，如6G***等。
本申请将围绕可包括多个设备、组件、模块等的***来呈现各个方面、实施例或特征。应当理解和明白的是，各个***可以包括另外的设备、组件、模块等，并且/或者可以并不包括结合附图讨论的所有设备、组件、模块等。此外，还可以使用这些方案的组合。
另外，在本申请实施例中，“示例的”一词用于表示作例子、例证或说明。本申请中被描述为“示例”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用示例的一词旨在以具体方式呈现概念。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
以下对本申请实施例的部分用语进行解释说明，以便于本领域技术人员理解。
1)用户终端(user equipment，UE)，也可以简称为终端，在通信***中，又称之为移动台(mobile station，MS)、移动终端(mobile terminal，MT)等，是指向用户提供语音和/或数据连通性的设备。例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网 设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
2)网络设备，是无线网络中的设备，例如网络设备可以为将终端接入到无线网络的无线接入网(radio access network，RAN)节点(或设备)，又可以称为基站。目前，一些RAN节点的举例为：继续演进的节点B(gNB)、传输接收点(transmission reception point，TRP)、演进型节点B(evolved Node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、基带单元(base band unit，BBU)，或无线保真(wireless fidelity，Wifi)接入点(access point，AP)等。另外，在一种网络结构中，网络设备可以包括集中单元(centralized unit，CU)节点、或分布单元(distributed unit，DU)节点、或包括CU节点和DU节点的RAN设备。其中包括CU节点和DU节点的RAN设备将长期演进(long term evolution，LTE)***中eNB的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。又例如网络设备可以是为终端提供业务支持的核心网(core network，CN)设备，常见的核心网设备包括接入和移动性管理功能(access and mobility management function，AMF)实体、会话管理功能(session management function，SMF)实体、用户面功能(user plane function，UPF)实体等等，此处不一一列举。其中，所述AMF实体可以负责终端的接入管理和移动性管理；所述SMF实体可以负责会话管理，如用户的会话建立等；所述UPF实体可以是用户面的功能实体，主要负责连接外部网络。
3)数据传输方式，无线通信***主要分为单播(unicast)、广播(broadcast)和多播/组播(multicast)3种数据传输方式。
4)小区，也称蜂窝小区，一个基站或基站的一部分所覆盖的区域(一般指无线信号所覆盖的区域)，位于小区内的终端可以通过无线信道与基站进行通信。
5)CU-DU分离架构，5G NR***中引入了CU-DU分离架构，一个CU和多个DU组成一个基站。CU主要负责无线资源控制层(radio resource control，RRC)，服务数据适配协议(service data adaptation protocol，SDAP)以及分组数据汇聚协议(packet data convergence protocol，PDCP)协议层，DU主要负责无线链路层控制协议(radio link control，RLC)，媒体接入控制层(media access control，MAC)以及物理层(physical layer，PHY)协议层，CU和DU之间通过F1接口连接。对于LTE***，也引入了CU-DU分离架构，所不同的是CU只包含RRC和PDCP协议层。此外，LTE的CU和DU之间通过W1接口连接。
6)网络切片(Network slice)：也称slice，指在物理或者虚拟的网络基础设施之上，根据不同的服务需求定制化的、不同的逻辑网络。网络切片技术可以让运营商在一个硬件基础设施分出多个虚拟的端到端网络，每个网络切片从设备到接入网到传输网再到核心网在逻辑上隔离，适配各种类型服务的不同特征需求。网络切片可以是一个包括了终端、接入网、传输网、核心网和应用服务器的完整的端到端网络，能够提供完整的电信服务，具有一定网络能力；网络切片也可以是上述终端、接入网、传输网、核心网和应用服务器的任 意组合。网络切片可能具有如下一个或多个特性：接入网可能切片，也可能不切片。接入网可能是多个网络切片共用的。不同的网络切片的特性和组成它们的网络功能可能是不一样。
7)本申请实施例中的术语“***”和“网络”可被互换使用。“多个”是指两个或两个以上，其它量词与之类似。“和/或”描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。此外，对于单数形式“a”，“an”和“the”出现的元素(element)，除非上下文另有明确规定，否则其不意味着“一个或仅一个”，而是意味着“一个或多于一个”。例如，“a device”意味着对一个或多个这样的device。再者，至少一个(at least one of).......”意味着后续关联对象中的一个或任意组合，例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c或a-b-c，其中a，b，c可以是单个，也可以是多个。
以及，除非有相反的说明，本申请实施例提及“第一”、“第二”等序数词是用于对多个对象进行区分，不用于限定多个对象的顺序、时序、优先级或者重要程度。例如，第一数据包和第二数据包，只是为了区分不同的数据包，而并不是表示这两个数据包的内容、优先级、发送顺序或者重要程度等的不同。
5G网络中引入了网络切片的概念，但是现有机制中无法支持网络切片粒度的组播，不能满足网络切片粒度的组播。鉴于此，为了满足网络切片粒度的组播，本申请提出了一种网络切片的组播方法。
在该方法中，网络设备将网络切片的标识对应的组播业务信道的配置信息发送给UE，然后采用网络切片对应的组播业务信道发送组播数据，其中网络设备包括接入网设备和/或核心网设备，UE接收网络切片的标识对应的组播业务信道的配置信息，在收听组播数据时，UE可以在感兴趣的网络切片对应的组播业务信道上收听组播数据，从而实现网络切片粒度的组播。
具体的，在该方法中，接入网设备向UE发送第一消息，第一消息包括网络切片的标识和组播业务信道的配置信息，网络切片的标识和组播业务信道相对应，UE接收第一消息，可以根据感兴趣的网络切片对应的组播业务信道收听组播数据，从而实现网络切片粒度的组播，或者DU向UE发送第二消息，第二消息包括组播会话的标识和组播业务信道的配置信息，组播会话的标识和组播业务信道相对应，这样，在CU-DU分离架构下，也可以实现组播会话的收发，并且在会话组播的标识包括网络切片的标识时，也能够满足网络切片粒度的组播；或者核心网设备向UE发送非接入层(non-access stratum，NAS)消息，NAS消息中包括网络切片的标识和TMGI，网络切片的标识和TMGI相对应，UE接收NAS消息，可以根据感兴趣的网络切片对应的TMGI的组播业务信道收听组播数据，从而实现网络切片粒度的组播。
图1为本专利申请的一个应用场景的示意图。该场景中，有网络设备(如图1中的核心网设备和接入网设备)和多个UE(如图1中的UE1、UE2、UE3、UE4和UE5)。网络设备可以将网络切片的标识对应的组播业务信道的标识信息发送给UE。在组播数据传输过程中，核心网设备可以将组播数据发送给接入网设备，由接入网设备通过网络切片对应的组播业务信道，将组播数据发送给UE。
例如网络切片的标识包括slice1和slice2。具体的，在组播数据传输过程中，核心网设 备可以将slice1的组播数据和slice2的组播数据发送给接入网设备，接入网设备可以通过slice1对应的组播业务信道将slice1的组播数据发送给UE1、UE2和UE3，通过slice2对应的组播业务信道将slice2的组播数据发送给UE4和UE5。这样，UE1、UE2和UE3就可以在slice1对应的组播业务信道上收听到slice1的组播数据，UE4和UE5就可以在slice2对应的组播业务信道上收听到slice2的组播数据，从而在具有网络切片的网络中实现组播。
本申请实施例提供了一种网络切片的组播方法，该方法可以应用于如图1所示的应用场景中。下面以下述方式详细说明网络切片的组播的具体过程。
方式一
首先参见图2所示的网络切片的组播过程，该过程包括：
步骤201：接入网设备生成第一消息，所述第一消息包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应。
在本申请实施例中接入网设备可以为基站，或者可以为DU。
其中，第一消息包括网络切片的标识和组播业务信道的配置信息，即第一消息支持网络切片对应的组播业务信道的配置信息。示例性的，第一消息可以是在Slicing-MCCH(切片组播控制信道)上发送的SlicingMBMSConfiguration(切片多媒体广播组播业务配置)消息，里面包含网络切片标识以及对应的组播业务信道的配置信息。
可选的，所述第一消息中还可以包括TMGI，所述TMGI和所述网络切片的标识相对应。例如，接入网设备可以在支持TMGI对应的组播业务信道的配置信息的消息中，包括有网络切片的标识，从而生成第一消息。
其中，支持TMGI对应的组播业务信道的配置信息的消息可以是在组播控制信道(multicast control channel，MCCH)上发送的MBSFNAreaConfiguration(多播广播同频网络区域配置)消息，或者在单小区组播控制信道(single-cell multicast control channel，SC-MCCH)上发送的SCPTMConfiguration(单小区点对多点配置)消息。即在所述消息中包含TMGI，网络切片标识以及对应的组播业务信道的配置信息。
具体的，所述组播业务信道包括组播业务信道(multicast traffic channel，MTCH)和/或单小区组播业务信道(single-cell multicast traffic channel，SC-MTCH)。
示例性的，接入网设备广播***信息块类型(system information block type，SIB)消息(如SIB13消息或SIB20消息)，所述SIB消息中包含MCCH/SC-MCCH的配置信息。之后接入网设备在MCCH/SC-MCCH上发送TMGI和MTCH/SC-MTCH的配置信息。然后接入网设备在MTCH/SC-MTCH上发送组播数据。例如基于多播广播同频网络(multicast broadcast over single frequency network，MBSFN)的多媒体广播组播业务(multimedia broadcast multicast service，MBMS)机制中，接入网设备通过SIB13消息广播MCCH的配置信息，在MCCH上发送TMGI和MTCH的配置信息，然后在MTCH上发送组播数据。基于单小区点对多点(single cell-point to multi-point，SC-PTM)机制中，接入网设备通过SIB20消息广播SC-MCCH的配置信息，在MCCH上发送TMGI和SC-MTCH的配置信息，最后在SC-MTCH上发送组播数据。
所述组播业务信道的配置信息包括以下信息中的至少一种：最后子帧配置，数据调制编码取值、调度周期、逻辑信道标识、持续时间计时器、DRX非激活计时器、或调度周期开始偏差。
例如，在基于MBSFN的MBMS机制中，组播业务信道为MTCH。组播业务信道的 配置信息包括以下信息中的至少一种：最后子帧配置(如最后子帧配置sf-allocend)，数据调制编码取值(如数据调制与编码策略datamcs)、调度周期(如多信道调度周期mch-scheduling period)，逻辑信道标识(如逻辑信道标识logical channel identity或LCID)，在基于SC-PTM的MBMS机制中，组播业务信道为SC-MTCH，组播业务信道的配置信息包括以下信息中的至少一种：持续时间计时器(如SCPTM持续时间计时器onDurationTimerSCPTM)、DRX非激活计时器(如SCPTM非连续接收非激活计时器drx-InactivityTimerSCPTM)、调度周期开始偏差(如SCPTM调度周期开始偏差schedulingPeriodStartOffsetSCPTM)。未来在NR MBMS机制中，组播业务信道可能和数据无线承载(data radio bearer，DRB)绑定，即若基站在RRC重配置消息中包含DRB ID和组无线网络临时标识(group-radio network temporary identifier，G-RNTI)的映射关系，即认为该数据无线承载等价于组播业务信道。
TMGI对应的组播业务信道的配置信息指TMGI与组播业务信道相对应，即所述组播业务信道为UE在收听感兴趣的TMGI的组播数据时采用的组播业务信道。其中UE感兴趣的TMGI可以为UE感兴趣的应用程序(application，APP)对应的TMGI，即与UE感兴趣的APP关联的TMGI。
网络切片的标识和组播业务信道相对应，即所述组播业务信道为UE在收听感兴趣的网络切片的组播数据时所采用的组播业务信道。其中UE感兴趣的网络切片可以为UE感兴趣的APP对应的网络切片，即与UE感兴趣的APP关联的网络切片。
TMGI和网络切片的标识相对应，即所述TMGI为UE在收听感兴趣的网络切片的组播数据时的TMGI。
示例的，接入网设备可以采用以下实现方式中的一种，来生成第一消息，该第一消息支持网络切片对应的组播业务信道的配置信息。其中该第一消息与支持TMGI对应的组播业务信道的配置信息的消息之间不冲突。
1、例如第一消息包括Slicing-MTCH配置信息，该Slicing-MTCH配置信息如下，其中Slicing-MTCH-Info(切片组播控制信道)为Slicing-MTCH配置信息，sliceID为网络切片的标识，g-RNTI(组无线网络临时标识)为G-RNTI的相关信息，slicing-mtch-schedulingInfo(切片组播控制信道调度信息)为组播业务信道的配置信息：
Figure PCTCN2020116795-appb-000001
2、例如第一消息包括slicing-PMCH(切片物理组播信道)配置信息，该slicing-PMCH配置信息如下，其中Slicing-PMCH-Info(切片物理组播信道信息)为slicing-PMCH配置信息，sliceID为网络切片的标识，pmch-Config(物理组播信道配置)为组播业务信道的配置信息：
Figure PCTCN2020116795-appb-000002
Figure PCTCN2020116795-appb-000003
3、例如第一消息包括Slicing-MBMS-SessionInfo(切片多媒体广播组播业务会话信息)中每个MBMS-SessionInfo(多媒体广播组播业务会话信息)信元，该MBMS-SessionInfo信元如下，其中MBMS-SessionInfo为Slicing-MBMS-SessionInfo中的MBMS-SessionInfo信元，sliceID为网络切片的标识，logicalChannelIdentity(逻辑信道标识)为组播业务信道的配置信息(具体为LCID的相关信息)：
Figure PCTCN2020116795-appb-000004
示例的，接入网设备可以采用以下实现方式中的一种，来生成第一消息，该第一消息支持TMGI，网络切片的标识信息和组播业务信道的配置信息。具体为在支持TMGI对应的组播业务信道的配置信息的消息中包括网络切片的标识信息。
1、例如第一消息包括SC-MCCH-Message(单小区组播控制信道)的SCPTMConfiguration(单小区点对多点配置)中的SC-mtch-InfoList(单小区组播业务信道信息列表)中的SC-MTCH-Info(单小区组播业务信道信息)，其中SC-MTCH-Info(单小区组播业务信道信息)支持TMGI对应的组播业务信道的配置信息，mbmsSessionInfo
(多媒体广播组播业务会话信息)为组播会话的相关信息，sliceID为网络切片的标识，g-RNTI、sc-mtch-schedulingInfo(单小区组播业务信道调度信息)以及sc-mtch-neighbourCell(单小区组播业务信道邻小区)都为组播业务信道的配置信息，在该实现方式中多个组播会话对应一个相同的网络切片的标识：
Figure PCTCN2020116795-appb-000005
2、例如第一消息包括SC-MCCH-Message的SCPTMConfiguration中的SC-mtch-InfoList中的SC-MTCH-Info中的mbmsSessionInfo，其中MBMSSessionInfo支持TMGI对应的组播业务信道的配置信息，tmgi(临时移动组标识)和sessionId-r13(会话标识)为组播业务信道的配置信息，sliceID为网络切片的标识：
Figure PCTCN2020116795-appb-000006
Figure PCTCN2020116795-appb-000007
3、例如第一消息包括MCCH-Message的MBSFNAreaConfiguration中的PMCH-InfoList(物理组播信道信息列表)中的PMCH-Info(物理组播信道信息)，其中PMCH-Info支持TMGI对应的组播业务信道的配置信息，pmch-Config和mbms-SessionInfoList(多媒体广播组播业务会话信息)为组播业务信道的配置信息，sliceID为网络切片的标识，在该实现方式中多个组播会话对应一个相同的网络切片的标识：
Figure PCTCN2020116795-appb-000008
4、例如第一消息包括mbms-SessionInfoList的mbms-SessionInfo，其中MBMS-SessionInfo支持TMGI对应的组播业务信道的配置信息，tmgi(TMGI)、sessionId(会话标识)和logicalChannelIdentity为组播业务信道的配置信息，sliceID为网络切片的标识，在该实现方式中一个组播会话对应一个网络切片的标识：
Figure PCTCN2020116795-appb-000009
步骤202：接入网设备向UE发送第一消息。
例如接入网设备在组播控制信道上发送第一消息。第一消息包含网络切片标识和组播业务信道的配置信息。例如接入网设备也可以通过RRC重配置消息给UE发送所述第一消息。
可选的，接入网设备接收来自核心网设备的网络切片标识和指示信息，所述指示信息指示有所述网络切片标识对应的组播数据。这样，接入网设备向UE发送第一消息后，接入网设备还可以根据第一消息，在所述网络切片标识的组播业务信道上发送组播数据，组播数据为来自于核心网设备的所述网络切片标识的组播数据。
步骤203：UE接收来自接入网设备发送的第一消息。
UE接收到第一消息之后，还可以将第一消息中的所述网络切片的标识和所述组播业务信道的配置信息对应的保存。
步骤204：UE在所述组播业务信道上接收所述网络切片对应的组播数据。
UE可以在感兴趣的网络切片对应的组播业务信道上，收听所述网络切片对应的组播数据。当组播业务信道为DRB时，UE可以在网络切片对应的DRB上，收听所述网络切片对应的组播数据。
在LTE MBMS机制的一种场景中，移动性管理实体(Mobility Management Entity，MME)给多实例CE(Multi-VPN-Instance CE，MCE)发送MBMS session start(MBMS 会话启动)消息。该MBMS session start消息用于指示启动组播会话。该MBMS session start消息包含MBMS Service Area(MBMS服务区域/MBMS服务范围)，还可以包含MBMS Cell List(MBMS小区列表)。MCE收到MBMS session start消息后，可以确定组播的范围。然后MCE向组播范围内的基站发送MBMS session start消息，该MBMS session start消息中包含MBMS Service Area。另外对于SC-PTM机制，该MBMS session start消息中还包含SC-PTM information，其中SC-PTM information中包含MBMS小区列表。但是由于目前还未确定5G NR的MBMS机制，因此在本申请实施例的方式一中，还可以考虑该方式一对MBMS session start消息的影响。
因此在一种可能的实现方式中，在LTE MBMS机制下，MBMS session start消息中包括网络切片的标识，该网络切片的标识用于接收方根据该网络切片的标识确定组播会话的发送范围。例如接入网设备根据核心网设备发送的MBMS session start消息中的网络切片的标识，确定组播会话的发送范围不超过该网络切片的标识对应的小区的覆盖范围。这样接入网设备在发送组播会话的组播数据时，在组播数据的发送范围限制在该网络切片的标识映射到的小区(如小区的标识)上。
在另一种可能的实现方式中，如果在步骤201中生成第一消息支持网络切片对应的组播业务信道的配置信息，还可以引入针对网络切片的MBMS session start消息(如slicing MBMS session start消息)，由接入网设备确定组播会话的发送范围。例如接入网设备接收核心网设备发送的针对网络切片的MBMS session start消息，该针对网络切片的MBMS session start消息中包括网络切片的标识信息，接入网设备确定组播会话的发送范围不超过该网络切片的标识对应的小区的覆盖范围。这样接入网设备在发送组播会话的组播数据时，在组播数据的发送范围限制在该网络切片的标识映射到的小区(如小区的标识)上。
在又一种可能的实现方式中，如果步骤201中生成第一支持网络切片对应的组播业务信道的配置信息，还可以引入针对网络切片的MBMS session start消息(如slicing MBMS session start消息)，由接入网设备确定组播会话的发送范围。如核心网设备确定组播会话的发送范围不超过网络切片的标识信息对应的小区的覆盖范围。例如AMF/MME给SMF/MCE发送针对网络切片的MBMS session start消息，该针对网络切片的MBMS session start消息包含网络切片的标识。SMF/MCE将组播会话的发送范围限制到网络切片的标识信息对应的小区的覆盖范围内；或者所述核心网设备根据网络切片的标识信息，确定该网络切片的标识信息对应的小区的标识，根据所述小区对应的覆盖范围和获取到的service area(服务区域)的范围，确定组播会话的发送范围。如AMF/MME给SMF/MCE发送针对网络切片的MBMS session start消息，该针对网络切片的MBMS session start消息包含网络切片的标识和service area的标识(如service area ID)。SMF/MCE可以取网络切片的标识对应的小区的覆盖范围和service area的范围的交集，确定交集内的小区为组播会话的发送范围。
相关专利中提出了一种Hop on slice的概念，Hop on slice(网络切片即时通信)也称为网络切片即时通信方式。在RAN侧，基站在空口广播slice对应数据无线承载(Data Radio Bearer，DRB)配置信息。假设slice对应的DRB配置信息包含在***信息x中。这样，UE不需要和基站建立RRC连接，就可以直接配置slice对应的DRB，从而直接发送数据给基站。如果基站和核心网设备之间事先建立好了slice对应的用户面隧道，基站通过DRB 识别对应的slice，然后可以将数据通过该slice对应的用户面隧道发送给核心网。基于该Hop on slice的基站，核心网设备可能会下发slice的组播数据给UE。但是支持Hop on slice机制的UE只监听***信息x，而组播相关信息(包括组播控制信道的配置信息)包含在***信息y中，***信息y和***信息x不同。因此UE由于不监听***信息y，无法获取到***信息y中的组播控制信道的相关信息，也就无法收听到组播业务信道的配置信息，也就无法在相应的组播业务信道上收听组播数据。因此在本申请实施例的方式一中，还可以考虑结合该方式一指示UE读取***信息y。主要针对slice对应的DRB配置信息包含在***信息x中，而组播相关信息包含在***信息y中的场景所作出的改进。
基于MBSFN的MBMS机制对应的SIB13或者基于SC-PTM机制对应的SIB20，在本申请实施例中主要以SIB20进行了说明，采用SIB13的过程相似，因此不做赘述。
在一种可能的实现中，将组播相关信息放在***信息x中。组播控制信道的配置信息，以及网络切片标识和DRB的配置信息包含在同一消息中。这样接入网设备可以不额外发送slice对应的组播控制信道的配置信息，避免了增加额外的信令开销。
例如，***消息x如下，其中Slice list为网络切片列表，slice ID为网络切片标识，DRB configuration(DRB配置)为DRB的配置信息，MCCH configuration(组播控制信道配置)为组播相关信息：
Slice list
>slice ID
>DRB configuration
>MCCH configuration
或者
Slice list
>slice ID
>DRB configuration
MCCH configuration
其中第一种方法中，MCCH configuration和网络切片标识一一对应。第二种方法中，MCCH configuration为所有网络切片标识共享。
在另一种可能的实现中，接入网设备可以向UE发送第一指示信息，该第一指示信息用于指示UE需要读取组播数据。如该UE具体指通过hop on slice工作的UE，即该UE为仅通过网络切片机制接收组播数据的UE。
可选的，接入网设备除向UE发送第一指示信息外，还向UE发送读取哪个***消息。如该第一指示信息用于指示UE读取该方式一中的第一消息，即指示UE读取组播控制信道的配置信息。例如，如果网络切片相关的组播控制信道的配置信息包含在SIB20中，则该第一指示信息指示UE读取的***消息类型为SIB20。UE通过SIB20可以获取组播控制信道MCCH的配置信息，之后UE监听MCCH就可以获取网络切片的标识对应的组播业务信道的配置信息。
可选地，如果接入网设备将组播控制信道的配置信息，以及网络切片标识和组播业务信道的配置信息都放在相同的SIB中，那么UE只需要收听广播消息即可以获取网络切片标识对应的组播业务信道的配置信息。后续的方法也同样适用，后续不再赘述。
可选的，该第一指示信息，可以与网络切片标识和DRB的配置信息包含在同一消息 中。例如，网络切片相关的组播控制信道的配置信息包含在SIB20中。接入网设备在***信息x中包含网络切片的标识对应的DRB的配置信息，和用于指示UE读取SIB20的第一指示信息。UE基于第一指示信息，读取SIB20可以获取到组播控制信道的配置信息，之后监听组播控制信道即可以获取网络切片的标识和组播业务信道的配置信息，且网络切片的标识和组播业务信道相对应。
例如，接入网设备向UE发送的信元如下所示。其中该信元中包括网络切片标识(slice ID)、DRB的配置信息(DRB configuration)、第一指示信息(广播指示broadcast indication)和***消息类型(MBMS的SIB类型SIB type for MBMS)。其中***消息类型为可选信元。
Slice list
>slice ID
>DRB configuration
>broadcast indication
>SIB type for MBMS(可选)
可选的，可以是协议规定好SIB消息(如SIB20)中需要包含的组播控制信道的配置信息。例如核心网设备指示接入网设备有网络切片标识对应的组播数据，即后续可能会发送slice-specific(网络切片专用)的组播数据。接入网设备生成包含组播控制信道的配置信息的SIB消息(如SIB20)。另外，接入网设备和核心网设备之间建立针对网络切片的组播用户面隧道。或者接入网设备和核心网之间的用户面隧道除支持单播数据和组播数据外，还支持针对网络切片的组播数据，则核心网设备还可以在NG3接口(即基站和UPF之间)的GTP-U(GPRS隧道传输协议-用户面)包中增加多播指示。
在又一种可能的实现中，核心网设备如果接收到UE通过Hop on slice方式传输的信息，核心网设备向UE发送网络切片的标识和第二指示信息，该第二指示信息用于指示有该网络切片的组播数据。这样UE就可以确定哪个网络切片上有组播数据。相应地，UE收听接入网设备广播的包含组播控制信道的配置信息的SIB消息，接着通过监听组播控制信道获取网络切片对应的组播业务信道的配置信息。后续可以在有组播数据的网络切片对应的组播业务信道上收听组播数据。
可选的，UE在首次注册时，可以向核心网设备发送该UE通过Hop on slice方式传输的指示信息。
通过本申请实施例中方式一提供的方案，通过改变空口，接入网设备将网络切片的标识和组播业务信道的配置信息发送给UE，网络切片的标识和组播业务信道相对应，UE可以直接获取到网络切片的标识和组播业务信道的配置信息。这样，UE可以通过网络切片的标识对应的组播业务信道获取组播数据，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。
方式二
首先参见图3所示的网络切片的组播过程，该过程中主要是由DU向UE发送第二消息，第二消息包括组播会话的标识和组播业务信道的配置信息，组播会话的标识和组播业务信道相对应，该过程包括：
步骤301：CU生成组播会话建立消息，所述组播会话建立消息中包括组播会话的标识。
其中组播会话建立消息用于建立组播会话，在本申请实施例中对组播会话建立消息的 消息名称不做限定，例如，组播会话建立消息可以为MBMS Session setup request(MBMS会话建立请求)消息。
所述组播会话的标识包括以下信息中的至少一种：TMGI、会话标识、或网络切片的标识。如，所述组播会话的标识信息包括TMGI；或者所述组播会话的标识信息包括会话标识；或者所述组播会话的标识包括网络切片的标识；或者所述组播会话的标识包括TMGI和会话标识；或者所述组播会话的标识包括TMGI和网络切片的标识；或者所述组播会话的标识包括会话标识和网络切片的标识；或者所述组播会话的标识包括TMGI、会话标识和网络切片的标识。特别地，所述组播会话的标识还可以为组无线网络临时标识G-RNTI。对于用G-RNTI标识组播会话的情况，适用于未来NR MBMS机制，即通过UE的DRB实现MBMS。接入网设备将告诉UE DRB ID和G-RNTI的对应关系，例如接入网设备在RRC重配置消息中包含DRB ID和G-RNTI。此外，假设CU还额外告知DU所述G-RNTI和哪些UE的哪些DRB关联，例如CU给DU发送如下列表：
Figure PCTCN2020116795-appb-000010
其中UE ID可能是gNB-CU UE F1AP ID，或者gNB-DU UE F1AP ID，也可能是小区无线网络临时标识(cell-radio network temporary identifier，C-RNTI)。其中DRB ID可以是DRB ID，也可以是UP TNL Information(上行传输网络层信息)，例如隧道端点地址(tunnel endpont identity，TEID)。
假设CU和DU之间建立G-RNTI对应的用户面隧道，如果DU从所述G-RNTI对应的用户面隧道接收到来自CU的组播数据，则DU根据之前CU之前发送的列表(如UE列表UE list)，列表中包括UE对应的DRB，将所述组播数据通过UE list中的UE对应的DRB发送，从而实现CU-DU架构支持组播机制。
如果CU和DU之间不建立G-RNTI对应的用户面隧道，而是利用UE的DRB对应的用户面隧道传输组播数据。那么CU在通过UE的DRB对应的用户面隧道发送数据时，需CU还可以要指示DU当前数据包为单播还是组播，以便DU决策用C-RNTI还是G-RNTI对所述数据进行扰码。例如CU可以在GTP-U header(头部)中增加1bit指示，当值为0表示为单播，DU决策用C-RNTI对所述数据进行加扰。当值为1表示为组播，DU决策用G-RNTI对所述数据进行加扰。
可选的，所述组播会话建立消息中还可以包括组播业务信道的配置信息，和/或第三指示信息。该第三指示信息用于指示基站采用MBSFN机制还是SC-PTM机制进行空口组播。组播业务信道包括MTCH或SC-MTCH。
步骤302：CU向DU发送组播会话建立消息。其中，CU和DU属于同一接入网设备。
此外，CU还可以向DU发送第三消息，所述第三消息用于指示所述DU反馈一个下行用户面隧道端点信息还是反馈一组下行用户面隧道端点信息。DU可以根据CU第三消息中的指示，建立与CU之间的组播对应的用户面隧道。其中，第三消息可以与组播会话建立消息为同一消息，或者第三消息与组播会话建立消息为不同消息。
CU还可以向DU发送指示信息，所述指示信息用于指示DU建立为所有的组播会话建立一个公共的用户面隧道，或者为每个组播会话建议一个对应的用户面隧道。
步骤303：DU接收CU发送的组播会话建立消息。
具体的，DU可以向所述CU反馈一个下行用户面隧道端点信息，即DU为所有的组播会话建立一个公共的用户面隧道。或者所述DU向所述CU反馈一组下行用户面隧道端点信息，所述一组下行用户面隧道端点信息包括每个组播会话对应的下行用户面隧道端点信息，即DU为每个组播会话建立了对应的用户面隧道。示例的，一组下行用户面隧道端点信息包括每个组播会话的标识和对应的下行用户面隧道端点信息。
对应的，所述CU接收来自所述DU的一个下行用户面隧道端点信息。或者所述CU接收来自所述DU的一组下行用户面隧道端点信息，所述一组下行用户面隧道端点信息包括每个组播会话的用户面隧道对应的下行用户面隧道端点信息。
步骤304：DU向UE发送第二消息，所述第二消息中包括组播会话的标识和组播业务信道的配置信息，所述组播会话的标识和所述组播业务信道相对应。
示例性的，第二消息可以是CU生成然后发送给DU，或者第二消息可以是DU生成的。如果CU生成第二消息发送给DU，DU将组播业务信道的配置信息发送给CU，CU根据组播业务信道的配置信息生成对应的第二消息发送给DU，DU将该第二消息发送给UE。例如DU在MCCH/SC-MCCH上发送所述第二消息。如果DU生成第二消息，CU通知DU后续后组播会话的标识对应的组播数据，DU根据组播会话的标识和组播业务信道的配置信息生成第二消息，DU将该第二消息广播给UE。
第二消息可以参见上述方式一中步骤201中的第一消息，具体可以参见步骤201中的组播业务信道的配置信息，在此不做赘述。
如果DU为所有的组播会话建立一个公共的用户面隧道。在组播数据开始传输时，DU需要确定接收到的组播数据或即将接收到的组播数据为针对哪个组播会话的组播数据。这样，DU可以根据确定的组播数据所属的组播会话，确定将组播数据下发给哪个或哪些UE。
在一种可能的实现中，我们称为控制面指示组播会话标识的方法。CU还可以向DU发送第四消息，DU接收来自CU的第四消息，该第四消息用于指示启动组播会话，该第四消息包括组播会话的标识。在本申请实施例中对第四消息的消息名称不做限定，例如该第四消息为MBMS session start(MBMS会话启动)消息。第四消息还可以包括组播会话的标识，以使DU确定后续在用户面隧道接收的是所述组播会话标识对应的组播数据。
进一步地，第四消息还可以包括小区列表(cell list)。这样，CU根据组播会话的标识和/或MBMS service area确定小区列表。在CU确定小区列表之前，DU还可以上报组播会话的标识和小区标识的映射关系。
在又一种可能的实现中，我们称为用户面隧道携带组播会话标识的方法。CU还可以通过公共的用户面隧道向DU发送数据。DU通过公共的用户面隧道接收来自CU的组播数据，所述组播数据包含组播数据以及所述组播会话的标识。示例的，CU在F1用户面隧道的GTP-U包头中包含组播会话的标识信息，以便于DU获知后续将通过哪个组播会话的标识信息对应的组播业务信道发送所述组播数据。
步骤305：UE接收DU发送的第二消息。
步骤306：UE使用所述组播业务信道接收所述网络切片对应的组播数据。
通过本申请实施例中方式二提供的方案，DU将会话建立消息发送给CU，CU将组播会话的标识和组播业务信道的配置信息发送给UE，网络切片的标识和组播业务信道相对应，UE可以直接获取到网络切片的标识和组播业务信道的配置信息，这样UE可以通过网 络切片的标识对应的组播业务信道获取到组播数据，从而在CU-DU分离架构下，也能够实现组播会话的收发，并且在组播会话的标识包括网络切片的标识时，能够实现网络切片粒度的组播，实现基于网络切片的组播机制。
方式三
首先参见图4所示的网络切片的组播过程，该过程中主要是由核心网设备向UE发送NAS消息，NAS消息中包括网络切片的标识和TMGI，网络切片的标识和TMGI相对应，该过程包括：
步骤401：核心网设备获取网络切片的标识和TMGI，所述网络切片的标识和所述TMGI相对应。
TMGI和网络切片的标识相对应，即所述TMGI为UE在收听感兴趣的网络切片的组播数据时的TMGI。
所述核心网设备还可以获取应用程序的标识，所述应用程序的标识和所述网络切片的标识相对应。
例如，应用功能实体(application function，AF)向所述核心网设备中的策略控制功能实体(policy control function，PCF)发送网络切片的标识和TMGI，网络切片的标识和TMGI相对应。PCF将相对应的网络切片的标识和TMGI发送给接入和移动管理功能实体(access and mobility management function，AMF)。
本申请实施例中对核心网设备获取网络切片的标识和TMGI的映射关系的方式不做限定，例如网络切片的标识和TMGI的映射关系包含在用户路径选择策略(UE route selection policy，URSP)中。
步骤402：核心网设备向UE发送NAS消息，所述NAS消息中包括网络切片的标识和TMGI，所述网络切片的标识和所述TMGI相对应。
例如，AMF还可以将NAS消息发送给UE，所述NAS消息包含所述URSP。
基站侧的组播机制可以保持不变，基站向UE发送第五消息，所述第五消息中包括TMGI和组播业务信道的配置信息，所述TMGI和所述组播业务信道相对应。
步骤403：UE接收来自核心网设备发送的NAS消息。
所述UE还可以接收基站发送的第五消息，所述第五消息中包括TMGI和组播业务信道的配置信息，所述TMGI和所述组播业务信道相对应。
步骤404：所述UE使用所述TMGI对应的组播业务信道接收所述网络切片对应的组播数据。
例如，UE确定感兴趣的网络切片对应的TMGI，然后使用该TMGI对应的组播业务信道接收该网络切片对应的组播数据。
通过本申请实施例中方式三提供的方案，在不改变空口的情况下，核心网设备将网络切片的标识和TMGI发送给UE，TMGI和网络切片的标识相对应，UE还可以获取到网络切片的标识对应的TMGI，这样，UE最终可以通过TMGI对应的组播业务信道接收网络切片对应的组播数据，从而实现网络切片粒度的组播，实现基于网络切片的组播机制。
结合图1至图4详细说明了本申请实施例的网络切片的组播方法，基于与上述网络切 片的组播方法的同一发明构思，本申请实施例还提供了一种网络切片的组播装置，如图5所示，所述网络切片的组播装置500中包含处理单元501和收发单元502，装置500可用于实现上述应用于核心网设备、UE或接入网设备的方法实施例中描述的方法。
在方式一的情况下，在一个实施例中，装置500应用于接入网设备，其中，所述接入网设备可以接入网设备或接入网设备中的DU。
具体的，处理单元501，用于生成第一消息；
所述收发单元502，用于向用户终端UE发送第一消息，所述第一消息包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应。
在一个实现方式中，所述收发单元502，还用于接收来自核心网设备的网络切片标识和指示信息，所述指示信息指示有所述网络切片标识对应的组播数据。
在一个实现方式中，所述第一消息中还包括临时移动组标识TMGI，所述TMGI和所述网络切片的标识相对应。
在一个实现方式中，所述组播业务信道的配置信息包括以下信息中的至少一种：最后子帧配置，数据调制编码取值、调度周期、持续时间计时器、DRX非激活计时器、调度周期开始偏差。
在一个实现方式中，所述收发单元502，还用于使用所述组播业务信道发送所述网络切片对应的组播数据。
在另一个实施例中，装置500应用于用户终端UE。
具体的，所述处理单元501，用于通过收发单元502接收来自接入网设备第一消息，所述第一消息中包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应；使用所述组播业务信道接收所述网络切片对应的组播数据。
在一个实现方式中，所述第一消息中还包括临时移动组标识TMGI，所述TMGI和所述网络切片的标识相对应。
在一个实现方式中，所述组播业务信道的配置信息包括以下信息中的至少一种：最后子帧配置，数据调制编码取值、调度周期、持续时间计时器、DRX非激活计时器、调度周期开始偏差。
在方式二的情况下，在一个实施例中，装置500应用于接入网分布单元DU。
具体的，所述处理单元501，用于通过收发单元502接收接入网集中单元CU发送的组播会话建立消息，所述组播会话建立消息中包括组播会话的标识；向用户终端UE发送第二消息，所述第二消息中包括组播会话的标识和组播业务信道的配置信息，所述组播会话的标识和所述组播业务信道相对应。
在一个实现方式中，所述组播会话的标识包括以下信息中的至少一种：TMGI、会话标识、或网络切片的标识。
在一个实现方式中，所述收发单元502，还用于向所述CU反馈一个下行用户面隧道端点信息；或者向所述CU反馈一组下行用户面隧道端点信息，所述一组下行用户面隧道端点信息包括每个组播会话对应的下行用户面隧道端点信息。
在一个实现方式中，所述收发单元502，还用于接收来自所述CU的第三消息，所述第三消息用于指示所述DU反馈一个下行用户面隧道端点信息还是反馈一组下行用户面隧道端点信息。
在一个实现方式中，所述收发单元502，还用于接收来自所述CU的第四消息，所述 第四消息用于指示启动所述组播会话，所述第四消息包括所述组播会话的标识。
在一个实现方式中，所述收发单元502，还用于通过公共的用户面隧道接收来自所述CU的数据，所述数据包含组播数据以及所述组播会话的标识。
在另一个实施例中，装置500应用于接入网集中单元CU。
具体的，所述处理单元501，用于生成组播会话建立消息；
所述收发单元502，用于向接入网分布单元DU发送组播会话建立消息，所述组播会话建立消息中包括组播会话的标识。
在一个实现方式中，所述组播会话的标识包括以下信息中的至少一种：TMGI、会话标识、或网络切片的标识。
在一个实现方式中，所述收发单元502，还用于接收来自所述DU的一个下行用户面隧道端点信息；或者接收来自所述DU的一组下行用户面隧道端点信息，所述一组下行用户面隧道端点信息包括每个组播会话的用户面隧道对应的下行用户面隧道端点信息。
在一个实现方式中，所述收发单元502，还用于向所述DU发送第三消息，所述第三消息用于指示所述DU反馈一个下行用户面隧道端点信息还是反馈一组下行用户面隧道端点信息。
在一个实现方式中，所述收发单元502，还用于向所述DU发送第四消息，所述第四消息用于指示启动所述组播会话，所述第四消息包括所述组播会话的标识。
在一个实现方式中，所述收发单元502，还通过公共的用户面隧道向所述DU发送数据，所述数据包含组播数据以及所述组播会话的标识。
在方式二的情况下，在一个实施例中，装置500应用于核心网设备。
具体的，所述处理单元501，用于获取网络切片的标识和临时移动组标识TMGI，所述网络切片的标识和所述TMGI相对应；
所述收发单元502，用于向用户终端UE发送非接入层NAS消息，所述NAS消息中包括网络切片的标识和TMGI，所述网络切片的标识和所述TMGI相对应。
在一个实现方式中，所述处理单元501，还用于获取应用程序的标识，所述应用程序的标识和所述网络切片的标识相对应。
在一个实现方式中，所述NAS消息中还包括应用程序的标识信息，所述应用程序的标识和所述网络切片的标识相对应。
在另一个实施例中，装置500应用于用户终端UE。
具体的，所述处理单元501，用于通过收发单元502接收来自核心网设备发送的NAS消息，所述NAS消息中包括网络切片的标识和临时移动组标识TMGI，所述网络切片的标识和所述TMGI相对应；使用所述TMGI对应的组播业务信道接收所述网络切片对应的组播数据。
在一个实现方式中，所述NAS消息中还包括应用程序的标识信息，所述应用程序的标识和所述网络切片的标识相对应。
在一个实现方式中，所述收发单元502，还用于接收基站发送的第五消息，所述第五消息中包括TMGI和组播业务信道的配置信息，所述TMGI和所述组播业务信道相对应。
需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是单独物理存在，也可以两个或两个以上单元集成在一个单元 中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
基于与上述网络切片的组播方法相同的构思，如图6所示，本申请实施例还提供了一种网络切片的组播装置600的结构示意图。装置600可用于实现上述应用于接入网设备、UE或核心网设备的方法实施例中描述的方法，可以参见上述方法实施例中的说明。所述装置600可以处于接入网设备、UE或核心网设备中，或为接入网设备、UE或核心网设备。
所述装置600包括一个或多个所述处理器601，所述一个或多个处理器601可实现上述所示的实施例中接入网设备、UE或核心网设备的方法。
可选的，处理器601除了实现上述所示的实施例的方法，还可以实现其他功能。
可选的，一种设计中，处理器601可以执行指令，使得所述装置600执行上述方法实施例中描述的方法。所述指令可以全部或部分存储在所述处理器内，如指令603，也可以全部或部分存储在与所述处理器耦合的存储器602中，如指令604，也可以通过指令603和604共同使得装置600执行上述方法实施例中描述的方法。
在又一种可能的设计中，通信装置600也可以包括电路，所述电路可以实现前述方法实施例中接入网设备、UE或核心网设备的功能。
在又一种可能的设计中所述装置600中可以包括一个或多个存储器602，其上存有指令604，所述指令可在所述处理器上被运行，使得所述装置600执行上述方法实施例中描述的方法。可选的，所述存储器中还可以存储有数据。可选的处理器中也可以存储指令和/或数据。例如，所述一个或多个存储器602可以存储上述实施例中所描述的对应关系，或者上述实施例中所涉及的相关的参数或表格等。所述处理器和存储器可以单独设置，也可以集成在一起。
在又一种可能的设计中，所述装置600还可以包括收发器605以及天线606。所述处理器601可以称为处理单元，对装置(终端或者基站)进行控制。所述收发器605可以称为收发机、收发电路、或者收发单元等，用于通过天线606实现装置的收发功能。
应注意，本申请实施例中的处理器可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用 译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述应用于接入网设备、UE或核心网设备的任一方法实施例所述的网络切片的组播方法。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品被计算机执行时实现上述应用于接入网设备、UE或核心网设备的任一方法实施例所述的网络切片的组播方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器，用于执行上述应用于接入网设备、UE或核心网设备的任一方法实施例所述的网络切片的组播方法。
应理解，上述处理装置可以是一个芯片，所述处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来 实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，改存储器可以集成在处理器中，可以位于所述处理器之外，独立存在。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本申请所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本申请技术方案的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在 本申请的保护范围之内。
本申请实施例还提供了一种计算机可读介质，其上存储有计算机程序，该计算机程序被计算机执行时实现上述应用于接入网设备、UE或核心网设备的任一方法实施例所述的网络切片的组播方法。
本申请实施例还提供了一种计算机程序产品，该计算机程序产品被计算机执行时实现上述应用于接入网设备、UE或核心网设备的任一方法实施例所述的网络切片的组播方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器，用于执行上述应用于接入网设备、UE或核心网设备的任一方法实施例所述的网络切片的组播方法。
应理解，上述处理装置可以是一个芯片，所述处理器可以通过硬件来实现也可以通过软件来实现，当通过硬件实现时，该处理器可以是逻辑电路、集成电路等；当通过软件来实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现，改存储器可以集成在处理器中，可以位于所述处理器之外，独立存在。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的***、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的***、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个***，或一些特征可以忽略，或不执行。另外，所显示或讨论 的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
通过以上的实施方式的描述，所属领域的技术人员可以清楚地了解到本申请可以用硬件实现，或固件实现，或它们的组合方式来实现。当使用软件实现时，可以将上述功能存储在计算机可读介质中或作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是计算机能够存取的任何可用介质。以此为例但不限于：计算机可读介质可以包括RAM、ROM、EEPROM、CD-ROM或其他光盘存储、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质。此外。任何连接可以适当的成为计算机可读介质。例如，如果软件是使用同轴电缆、光纤光缆、双绞线、数字用户线(DSL)或者诸如红外线、无线电和微波之类的无线技术从网站、服务器或者其他远程源传输的，那么同轴电缆、光纤光缆、双绞线、DSL或者诸如红外线、无线和微波之类的无线技术包括在所属介质的定影中。如本申请所使用的，盘(Disk)和碟(disc)包括压缩光碟(CD)、激光碟、光碟、数字通用光碟(DVD)、软盘和蓝光光碟，其中盘通常磁性的复制数据，而碟则用激光来光学的复制数据。上面的组合也应当包括在计算机可读介质的保护范围之内。
总之，以上所述仅为本申请技术方案的较佳实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (18)

  1. 一种网络切片的组播方法，其特征在于，包括：
    接入网设备生成第一消息；
    所述接入网设备向用户终端UE发送第一消息，所述第一消息包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应。
  2. 如权利要求1所述的方法，其特征在于，还包括：
    所述接入网设备接收来自核心网设备的网络切片标识和指示信息，所述指示信息指示有所述网络切片标识对应的组播数据。
  3. 如权利要求1或2所述的方法，其特征在于，所述第一消息中还包括临时移动组标识TMGI，所述TMGI和所述网络切片的标识相对应。
  4. 如权利要求1-3任一项所述的方法，其特征在于，所述组播业务信道的配置信息包括以下信息中的至少一种：最后子帧配置，数据调制编码取值、调度周期、逻辑信道标识、持续时间计时器、DRX非激活计时器、调度周期开始偏差。
  5. 如权利要求1-4任一项所述的方法，其特征在于，还包括：
    所述接入网设备使用所述组播业务信道发送所述网络切片对应的组播数据。
  6. 一种网络切片的组播方法，其特征在于，包括：
    用户终端UE接收来自接入网设备第一消息，所述第一消息中包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应；
    所述UE使用所述组播业务信道接收所述网络切片对应的组播数据。
  7. 如权利要求6所述的方法，其特征在于，所述第一消息中还包括临时移动组标识TMGI，所述TMGI和所述网络切片的标识相对应。
  8. 如权利要求6或7所述的方法，其特征在于，所述组播业务信道的配置信息包括以下信息中的至少一种：最后子帧配置，数据调制编码取值、调度周期、逻辑信道标识、持续时间计时器、DRX非激活计时器、调度周期开始偏差。
  9. 如权利要求6-8任一项所述的方法，其特征在于，所述接入网设备为接入网分布单元DU。
  10. 一种网络切片的组播装置，其特征在于，所述装置包括：处理器和收发器；
    所述处理器，用于生成第一消息；
    所述收发器，用于向用户终端UE发送第一消息，所述第一消息包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应。
  11. 如权利要求10所述的装置，其特征在于，所述收发器，还用于接收来自核心网设备的网络切片标识和指示信息，所述指示信息指示有所述网络切片标识对应的组播数据。
  12. 如权利要求10或11所述的装置，其特征在于，所述第一消息中还包括临时移动组标识TMGI，所述TMGI和所述网络切片的标识相对应。
  13. 如权利要求10-12任一项所述的方法，其特征在于，所述组播业务信道的配置信息包括以下信息中的至少一种：最后子帧配置，数据调制编码取值、调度周期、逻辑信道标识、持续时间计时器、DRX非激活计时器、调度周期开始偏差。
  14. 如权利要求10-13任一项所述的方法，其特征在于，所述收发器，还用于使用所述组播业务信道发送所述网络切片对应的组播数据。
  15. 一种网络切片的组播装置，其特征在于，所述装置包括：处理器和收发器；
    所述处理器，用于通过所述收发器接收来自接入网设备发送的第一消息，所述第一消息中包括网络切片的标识和组播业务信道的配置信息，所述网络切片的标识和所述组播业务信道相对应；使用所述组播业务信道接收所述网络切片对应的组播数据；
    所述收发器，用于接收来自接入网设备发送的第一消息；使用所述组播业务信道接收所述网络切片对应的组播数据。
  16. 如权利要求15所述的装置，其特征在于，所述第一消息中还包括临时移动组标识TMGI，所述TMGI和所述网络切片的标识相对应。
  17. 如权利要求15或16所述的装置，其特征在于，所述组播业务信道的配置信息包括以下信息中的至少一种：最后子帧配置，数据调制编码取值、调度周期、逻辑信道标识、持续时间计时器、DRX非激活计时器、调度周期开始偏差。
  18. 如权利要求15-17任一项所述的装置，其特征在于，接入网设备为接入网分布单元DU。
PCT/CN2020/116795 2019-09-30 2020-09-22 一种网络切片的组播方法及装置 WO2021063215A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20872762.8A EP4030846A4 (en) 2019-09-30 2020-09-22 METHOD AND DEVICE FOR MULTICASTING NETWORK SLICES
US17/705,893 US20220217509A1 (en) 2019-09-30 2022-03-28 Network slice multicast method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910945418.2 2019-09-30
CN201910945418.2A CN112584511B (zh) 2019-09-30 2019-09-30 一种网络切片的组播方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/705,893 Continuation US20220217509A1 (en) 2019-09-30 2022-03-28 Network slice multicast method and apparatus

Publications (1)

Publication Number Publication Date
WO2021063215A1 true WO2021063215A1 (zh) 2021-04-08

Family

ID=75117022

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/116795 WO2021063215A1 (zh) 2019-09-30 2020-09-22 一种网络切片的组播方法及装置

Country Status (4)

Country Link
US (1) US20220217509A1 (zh)
EP (1) EP4030846A4 (zh)
CN (1) CN112584511B (zh)
WO (1) WO2021063215A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023133242A1 (en) * 2022-01-06 2023-07-13 Google Llc Configuring resources for multicast and/or broadcast services in a distributed base station architecture

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111901764A (zh) * 2020-04-24 2020-11-06 中兴通讯股份有限公司 广播/组播业务的管理方法、装置、电子设备和存储介质
WO2022151265A1 (zh) * 2021-01-14 2022-07-21 华为技术有限公司 一种通信方法、终端设备和网络设备
CN118283827A (zh) * 2022-12-29 2024-07-02 上海数字电视国家工程研究中心有限公司 一种多播业务配置方法及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018126342A1 (zh) * 2017-01-03 2018-07-12 华为技术有限公司 一种通信方法及设备
WO2018175974A1 (en) * 2017-03-24 2018-09-27 Intel Corporation Systems and methods for group based services provisioning
CN109644330A (zh) * 2016-08-22 2019-04-16 三星电子株式会社 用于通过使用切片向终端提供网络服务的方法和装置
WO2019136128A1 (en) * 2018-01-03 2019-07-11 Convida Wireless, Llc Multicast and broadcast services in 5g networks for iot applications

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9473906B2 (en) * 2013-03-22 2016-10-18 Mediatek Inc. Idle mode reception for group communication over LTE eMBMS
CN104469691B (zh) * 2013-09-25 2018-04-17 电信科学技术研究院 一种组通信方法、设备及***
CN106572516B (zh) * 2016-09-28 2021-02-12 华为技术有限公司 一种网络切片选择方法、终端设备及网络设备
US10142963B2 (en) * 2016-12-02 2018-11-27 Ofinno Technologies, Llc MBMS configuration between eNBs for V2X services
CN108174392B (zh) * 2016-12-07 2020-08-14 华为技术有限公司 接入网络切片的方法及装置
CN109561423B (zh) * 2017-01-26 2020-07-14 华为技术有限公司 一种接入目标小区的方法以及装置
WO2018141134A1 (zh) * 2017-04-26 2018-08-09 北京小米移动软件有限公司 关于网络切片的接入方法及装置
US10341872B2 (en) * 2017-09-08 2019-07-02 Verizon Patent And Licensing Inc. Dynamic network slice resolution
CN109769150B (zh) * 2017-11-09 2021-02-23 华为技术有限公司 一种传输组播业务的方法和设备
JP2021072454A (ja) * 2018-02-27 2021-05-06 ソニー株式会社 端末装置、通信制御装置、基地局、ゲートウェイ装置、制御装置、方法及び記録媒体

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109644330A (zh) * 2016-08-22 2019-04-16 三星电子株式会社 用于通过使用切片向终端提供网络服务的方法和装置
WO2018126342A1 (zh) * 2017-01-03 2018-07-12 华为技术有限公司 一种通信方法及设备
WO2018175974A1 (en) * 2017-03-24 2018-09-27 Intel Corporation Systems and methods for group based services provisioning
WO2019136128A1 (en) * 2018-01-03 2019-07-11 Convida Wireless, Llc Multicast and broadcast services in 5g networks for iot applications

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CHINA UNICOM: "China Unicom Views on Rel-17", 3GPP TSG RAN MEETING #84 RP-191328, 6 June 2019 (2019-06-06), XP051739655 *
See also references of EP4030846A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023133242A1 (en) * 2022-01-06 2023-07-13 Google Llc Configuring resources for multicast and/or broadcast services in a distributed base station architecture

Also Published As

Publication number Publication date
US20220217509A1 (en) 2022-07-07
CN112584511B (zh) 2022-09-09
EP4030846A4 (en) 2022-11-02
EP4030846A1 (en) 2022-07-20
CN112584511A (zh) 2021-03-30

Similar Documents

Publication Publication Date Title
WO2021063215A1 (zh) 一种网络切片的组播方法及装置
WO2021077434A1 (zh) 一种通信方法及装置
EP1656811B1 (en) Apparatus and method for sharing radio protocol entities in wireless communication system
US7706318B2 (en) Method and apparatus for transmitting and receiving MBMS packet data and control information
US8170569B2 (en) Method for facilitate efficient multimedia broadcast/multicast service in a telecommunication system
EP3409035B1 (en) Dynamic switching of streaming service between broadcast and unicast delivery
JP4510083B2 (ja) マルチメディアブロードキャスト／マルチキャストサービスシステムにおける選好周波数情報を知らせる方法及び装置
WO2021164564A1 (zh) 传输组播业务的方法和装置
US20150341494A1 (en) Method, system, base station and cluster EPC for establishing group call context
JP5911586B2 (ja) Ｍｃｅがクラスタセッション確立を制御する方法およびシステム
WO2022073246A1 (zh) 一种通信方法及装置
WO2014153705A1 (zh) 新载波类型小区的业务处理方法、装置及通信***
EP4354908A1 (en) Session establishment method and apparatus
WO2015143795A1 (zh) Mbms差错处理方法、通信节点、通信***和存储介质
JP7469564B2 (ja) 通信制御方法、ユーザ装置、プロセッサ、ネットワークノード及び移動通信システム
JP7425259B2 (ja) 通信制御方法及び基地局
WO2023272619A1 (zh) 一种传输方式的确定方法及装置、终端设备、网络设备
WO2023071983A1 (zh) 网元之间协商网络编码的方法和通信装置
KR102689205B1 (ko) 브로드캐스트/멀티캐스트 서비스 관리 방법, 장치, 전자 설비, 저장 매체
WO2021189458A1 (zh) 一种数据转发方法及装置、通信设备
KR20230004776A (ko) 브로드캐스트/멀티캐스트 서비스 관리 방법, 장치, 전자 설비, 저장 매체
CN117560739A (zh) 通信方法、通信装置及通信***
KR20110087057A (ko) 멀티 셀 환경에서 단말의 물리 채널 변경 제어 방법

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020872762

Country of ref document: EP

Effective date: 20220412