WO2023011137A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2023011137A1
WO2023011137A1 PCT/CN2022/105769 CN2022105769W WO2023011137A1 WO 2023011137 A1 WO2023011137 A1 WO 2023011137A1 CN 2022105769 W CN2022105769 W CN 2022105769W WO 2023011137 A1 WO2023011137 A1 WO 2023011137A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
network device
service
information
core network
Prior art date
Application number
PCT/CN2022/105769
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 EP22851851.0A priority Critical patent/EP4369745A1/en
Publication of WO2023011137A1 publication Critical patent/WO2023011137A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5069—Address allocation for group communication, multicast communication or broadcast communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • 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
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • 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
    • H04W76/00—Connection management
    • H04W76/30—Connection release

Definitions

  • the present application relates to the technical field of communication, and in particular to a communication method and device.
  • network co-construction and sharing technology can be used to enable multiple operators to share network infrastructure.
  • the main application of network co-construction and sharing technology includes radio access network (radio access network, RAN) ) sharing.
  • RAN sharing means that one RAN can be connected to multiple operators' core network nodes, and multiple operators can cooperate to build RAN, or one operator can build RAN alone, while other operators lease the operator's RAN network .
  • the present application provides a communication method and device to save resources and improve transmission efficiency.
  • the present application provides a communication method, which is applicable to a scenario where a session is established between an access network device and a terminal device.
  • the execution subject of the method is the access network device or a chip or a module in the access network device, and the description here takes the access network device as the execution subject as an example.
  • the method includes: the access network device acquires first information from the first core network device, and the first information is used to request the first terminal device to join the multicast service session corresponding to the first multicast service; when the first condition is met, Adding the first terminal device to a multicast service session corresponding to the second multicast service, wherein the first condition includes that the first multicast service and the second multicast service are the same multicast service, and the second multicast service is the second multicast service.
  • the access network device acquires first information from the first core network device, and the first information is used to request the first terminal device to join the multicast service session corresponding to the first multicast service; when the first condition is met, Adding the first terminal device to a multicast service session corresponding to the second multicast service, wherein the first condition includes that the first multicast service and the second multicast service are the same multicast service, and the second multicast service is the second multicast service.
  • the access network device acquires first information from the first core network device, and the first information is used to request the first terminal
  • the first terminal device is added to the multicast service session corresponding to the second multicast service, so that the established first multicast service can be used.
  • the relevant resources of the second multicast service provide the service data of the second multicast service to the terminal devices in the two networks at the same time, so as to share the same NG resources and air interface resources for the same multicast service from the two core networks, saving energy resources and improve data transmission efficiency.
  • it also includes: sending second information to the first core network device; wherein, the second information is used to indicate that the first data transmission channel is not established with the first core network device, and the first data transmission The channel is used to transmit service data of the first multicast service.
  • it also includes: sending third information to the first core network device, the third information is used to indicate that the first data transmission channel established with the first core network device is in an inactive state, and the first The data transmission channel is used to transmit service data of the first multicast service.
  • service data can not be obtained through the first core network, and the access network equipment only receives data from the second core network, which saves NG interface resources and improves data transmission efficiency.
  • the method further includes: sending a first user identifier to the first terminal device, where the first user identifier is used to scramble the first scheduling information, and the first scheduling information is used to schedule the service data of the second multicast service ;
  • the first user identifier is the same as the second user identifier
  • the second user identifier is a user identifier sent to the second terminal device
  • the second terminal device belongs to the second core network device.
  • the method further includes: sending first configuration information to the first terminal device, where the first configuration information includes configuration information of a second multicast radio bearer, and the second multicast radio bearer is used to communicate with the second terminal device
  • the second multicast radio bearer is also used to transmit the service data of the second multicast service with the first terminal device.
  • the first terminal device and the second terminal device can use the same multicast radio bearer to receive data, which saves air interface resources and improves data transmission efficiency.
  • the first information includes a first identifier corresponding to the first multicast service; the first condition includes that the first multicast service and the second multicast service are the same multicast service, including: the first identifier If it matches the second identifier corresponding to the second multicast service, the first multicast service and the second multicast service are the same multicast service.
  • the first identifier is the service identifier of the first multicast service corresponding to the first multicast service in the first core network device; or, the first identifier is the service identifier of the first multicast service in the first core network
  • the corresponding first multicast service session identifier in the device; or, the first identifier is the first Internet Protocol IP multicast group address or temporary mobile group identifier corresponding to the first multicast service in the first core network device; or
  • the first identifier is an identifier corresponding to the first multicast service in the service server or another identifier allocated by the service server for the first multicast service.
  • the access network device can identify the first multicast service and the second multicast service as the same multicast service, so that the same multicast service from the two core networks can be further realized to share the same NG resource and /or air interface resources.
  • the method further includes: receiving first release information from the second core network device, where the first release information is used to indicate the release of the second data transmission channel, where the second data transmission channel is used to transmit the second Service data of the multicast service; sending fifth information or sixth information to the first core network device; the fifth information is used to trigger establishment of the first data transmission channel, and the sixth information is used to activate the first data transmission channel.
  • the first release information includes a release reason; before sending the fifth or sixth information to the first core network device, the method further includes: determining that the release reason is any of the following: requesting that the second group The broadcast service is converted from multicast transmission to unicast transmission; the second multicast service is requested to be converted to unicast service; there is no terminal device receiving the service data of the second multicast service in the network corresponding to the second core network device; In the network corresponding to the second core network device, the number of terminal devices receiving service data of the second multicast service is less than or equal to the threshold.
  • the first core network device can obtain the reason why the access network device releases the second multicast service, so as to determine the way to provide the service for the first terminal device.
  • the method further includes: establishing a first multicast radio bearer corresponding to the first multicast service according to the first quality of service flow information; or updating the second multicast radio bearer according to the first quality of service flow information;
  • the first multicast radio bearer is used to transmit the service data of the first multicast service with the first terminal device, and the first quality of service flow information comes from the first core network device;
  • the second multicast radio bearer is used to communicate with the second terminal device
  • the service data of the second multicast service is transmitted between the devices, and the updated second multicast radio bearer is used to transmit the service data of the first multicast service with the first terminal device.
  • the method further includes: sending third configuration information to the first terminal device, where the third configuration information includes a third user ID, and the third user ID is used to scramble the second scheduling information, and the second scheduling information uses Service data for scheduling the first multicast service.
  • the third configuration information further includes configuration information of the first multicast radio bearer.
  • the first terminal device rebuilds or updates the second multicast radio bearer to the first multicast radio bearer.
  • it also includes: sending a first packet number to the first core network device, where the first packet number is the packet number of the last data packet belonging to the first multicast service sent to the first terminal device, Alternatively, the first packet number is the largest packet number among at least one packet number corresponding to at least one buffered data packet, and the at least one data packet is a data packet to be sent to the first terminal device and belongs to the first multicast service.
  • the data packet number when the data packet number reaches a maximum value, such as 4095 (corresponding to the number length of 10 bits), the subsequent packets will start from 0 again, so the above-mentioned maximum packet number essentially means the most Late numbered pack.
  • a maximum value such as 4095 (corresponding to the number length of 10 bits)
  • the subsequent packets will start from 0 again, so the above-mentioned maximum packet number essentially means the most Late numbered pack.
  • the first data packet is numbered 4094
  • the second data packet is numbered 4095
  • the third data packet is numbered 0 ((4095+1) Mod 4096, Mod stands for modulo)
  • Mod stands for modulo
  • it also includes: receiving a data packet belonging to the first multicast service from the first core network device; wherein, the initial data packet in the received data packet is the second data packet, and the second There are N data packets between the data packet and the third data packet, and the third data packet is a data packet obtained from the service server when the first core network device receives the fifth information or the sixth information; N is greater than 0 Integer; or, the preset duration of the corresponding time interval between the second data packet and the third data packet.
  • the preset duration is configured by the access network device, or the preset duration is determined by the first core network device, or the preset duration is determined according to the first delay and the second delay, and the first The delay is the transmission delay between the access network device and the first core network device, and the second delay is the transmission delay between the access network device and the second core network device.
  • the present application further provides a communication device, where the communication device implements any method provided in the first aspect above.
  • the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a processor, where the processor is configured to support the communication device to perform corresponding functions in the methods shown above.
  • the communication device may also include a memory, which may be coupled to the processor, which holds program instructions and data necessary for the communication device.
  • the communication device further includes an interface circuit, which is used to support communication between the communication device and other devices.
  • the communications apparatus may be an access network device, or a chip or a module in the access network device.
  • the communication device includes corresponding functional modules, respectively configured to implement the steps in the above method.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • Hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the above method examples.
  • these units can perform corresponding functions in the above method examples.
  • the present application provides a communication method, which is applicable to a scenario where a session is established between an access network device and a terminal device.
  • the execution subject of the method is the first core network device or a chip or a module in the first core network device, and the first core network device is used as the execution subject as an example for description here.
  • the method includes: the first core network device sends first information to the access network device, the first information is used to request the first terminal device to join the multicast service session corresponding to the first multicast service; the first terminal device joins the second multicast service session; In the case of a multicast service session corresponding to the multicast service, the second information or the third information from the access network device is received; wherein, the first multicast service and the second multicast service are the same multicast service, and the second The multicast service is provided by the second core network device; the second information is used to indicate that the first data transmission channel is not established with the first core network device, and the first data transmission channel is used to transmit the service data of the first multicast service ; The third information is used to indicate that the first data transmission channel established with the first core network device is in an inactive state, and the first data transmission channel is used to transmit service data of the first multicast service.
  • it also includes: receiving fifth information or sixth information from the access network device; the fifth information is used to trigger the establishment of the first data transmission channel, and the sixth information is used to activate the first data transmission channel .
  • it also includes: receiving a first packet number from the access network device, where the first packet number is the last data packet belonging to the first multicast service sent by the access network device to the first terminal device or, the first packet number is the largest packet number among at least one packet number corresponding to at least one data packet cached by the access network device, and at least one data packet is to be sent to the first terminal device and belongs to the first A data packet of the multicast service: using the data packet corresponding to the first packet number as the initial data packet sent to the first terminal device.
  • it also includes: sending a data packet belonging to the first multicast service to the access network device; wherein, the initial data packet in the data packet is the second data packet, and the second data packet and the third There are N data packets between the data packets, and the third data packet is the data packet obtained from the service server when the first core network device receives the fifth information or the sixth information; N is an integer greater than 0; or, the first The corresponding time interval between the second data packet and the third data packet is preset.
  • the preset duration is configured by the access network device, or the preset duration is determined by the first core network device, or the preset duration is determined according to the first delay and the second delay, and the first The delay is the transmission delay between the access network device and the first core network device, and the second delay is the transmission delay between the access network device and the second core network device.
  • the present application further provides a communication device, and the communication device implements any method provided in the second aspect above.
  • the communication device may be realized by hardware, or may be realized by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication device includes: a processor, where the processor is configured to support the communication device to perform corresponding functions in the methods shown above.
  • the communication device may also include a memory, which may be coupled to the processor, which holds program instructions and data necessary for the communication device.
  • the communication device further includes an interface circuit, which is used to support communication between the communication device and other devices.
  • the communication device may be a core network device, or a chip or a module in the core network device.
  • the communication device includes corresponding functional modules, respectively configured to implement the steps in the above method.
  • the functions may be implemented by hardware, or may be implemented by executing corresponding software through hardware.
  • Hardware or software includes one or more modules corresponding to the above-mentioned functions.
  • the structure of the communication device includes a processing unit and a communication unit, and these units can perform corresponding functions in the above method examples.
  • these units can perform corresponding functions in the above method examples.
  • a communication device including a processor and an interface circuit, and optionally, a memory.
  • the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or send signals from the processor to other communication devices other than the communication device, and the processor is used to execute the described
  • the computer program or instruction stored in the memory implements the method in any possible implementation manner of the aforementioned first aspect.
  • a communication device including a processor and an interface circuit, and optionally, a memory.
  • the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or send signals from the processor to other communication devices other than the communication device, and the processor is used to execute the The computer program or instruction stored in the memory implements the method in any possible implementation manner of the aforementioned second aspect.
  • a computer-readable storage medium in which a computer program or an instruction is stored, and when the computer program or instruction is run on a computer, the computer is enabled to implement the aforementioned first aspect A method in any possible implementation of .
  • a computer-readable storage medium in which a computer program or instruction is stored, and when the computer program or instruction is run on a computer, the computer realizes the aforementioned second aspect A method in any possible implementation of .
  • a computer program product storing computer-readable instructions.
  • the computer-readable instructions When the computer-readable instructions are run on a computer, the computer is made to implement the method in any possible implementation manner in the foregoing first aspect. .
  • a computer program product storing computer-readable instructions, and when the computer-readable instructions are run on a computer, the computer is made to implement the method in any possible implementation manner of the aforementioned second aspect .
  • a chip in an eleventh aspect, includes a processor, and may further include a memory, configured to execute computer programs or instructions stored in the memory, so that the chip implements any of the possible implementations in the foregoing first aspect. method.
  • a chip in a twelfth aspect, includes a processor, and may also include a memory for executing computer programs or instructions stored in the memory, so that the chip implements any of the possible implementations of the aforementioned second aspect method.
  • a communication device including a module for implementing the method in any possible implementation manner in the foregoing first aspect.
  • a communication device including a module for implementing the method in any possible implementation manner of the foregoing second aspect.
  • a fifteenth aspect provides a communication system, where the system includes the device described in the second aspect (such as the access network device) and the device described in the fourth aspect (such as the first core network device).
  • FIG. 1 is a schematic diagram of a network architecture applicable to the present application
  • FIGS. 1(a) to Figure 2(c) are schematic diagrams of the protocol architecture provided by the embodiment of the present application.
  • FIG. 3 is a schematic flow diagram of a terminal device joining a multicast session
  • FIG. 4 is a schematic diagram of service data transmission provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of service data transmission provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of a data packet transmission provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Embodiments of the present application can be applied to various mobile communication systems, such as: NR system, global system of mobile communications (GSM) system, long term evolution (long term evolution, LTE) system, and other communication systems such as future communication systems , without limitation here.
  • GSM global system of mobile communications
  • LTE long term evolution
  • future communication systems without limitation here.
  • the interaction between the terminal device, the access network device, and the core network device is used as an example to describe. It should be noted that the method provided in the embodiment of the present application can not only be applied The interaction between devices can also be applied to the interaction between any two devices, such as device-to-device (device-to-device, D2D) communication, which is not limited in this embodiment of the present application.
  • device-to-device device-to-device, D2D
  • a terminal device may be referred to as a terminal for short, and is a device with a wireless transceiver function or a chip that may be provided in the device.
  • the terminal equipment may also be called user equipment (user equipment, UE), access terminal, and so on.
  • the terminal device in the embodiment of the present application may be a mobile phone, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal, an augmented reality (augmented reality) , AR) terminals, wireless terminals in industrial control (industrial control), etc.
  • VR virtual reality
  • AR augmented reality
  • the device for realizing the function of the terminal device may be a terminal device; it may also be a device capable of supporting the terminal device to realize the function, such as a chip system, and the device may be installed in the terminal device or connected with the terminal device Matching is used.
  • Access network equipment It can be wireless access equipment under various standards in the wireless network.
  • the access network equipment can be a RAN node that connects terminal equipment to the wireless network, and can also be called RAN equipment or base station.
  • Some examples of access network equipment are: next generation base station (generation Node B, gNodeB), transmission reception point (transmission reception point, TRP), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC) and so on.
  • the access network device may include a centralized unit (centralized unit, CU) node or a distributed unit (distributed unit, DU) node, or include a CU node and a DU node.
  • the access network device When the access network device includes a CU and a DU, multiple DUs can be centrally controlled by one CU.
  • the device for implementing the function of the access network device may be the access network device; it may also be a device capable of supporting the access network device to realize the function, such as a chip system, and the device may be installed on the access network It can be used in network access equipment or matched with access network equipment.
  • the core network device may be a device used to manage the access and mobility of the terminal device, for example, it may be an access and mobility management (Access and Mobility Management Function, AMF) network element or a session management function (Session Management Function) , SMF) network element or multicast broadcast (multicast broadcast, MB)-SMF network element or user plane function (user plane function, UPF) or MB-UPF, can also be a mobility management entity (mobility management entity, MME) network Yuan etc., this application is not limited to this.
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • MME mobility management entity
  • MME mobility management entity
  • This application can be applied in the scenario of RAN sharing, in which the radio access network or the radio access network and part of the core network can be shared with multiple operators.
  • RAN sharing in which the radio access network or the radio access network and part of the core network can be shared with multiple operators.
  • This application mainly relates to multi-operator core network (multi-operator core network, MOCN) architecture.
  • MOCN multi-operator core network
  • FIG. 1 it is a schematic diagram of a network architecture applicable to this application.
  • one RAN can be connected to core network nodes of at least two operators, that is, shared by at least two operators.
  • the RAN shared by operator A and operator B is taken as an example for description.
  • multiple operators share the use of access network equipment and share the cells of the access network equipment, but each operator has its own independent core network.
  • the access network equipment establishes an S1 interface connection or a next generation (next generation, NG) interface connection with each operator's core network, and the access network equipment can provide services for terminal equipment of multiple operators.
  • NG next generation
  • the core network is independent; configuration management, alarm management, performance indicators, etc. all need to be managed by the main operator, and some performance indicators can be distinguished from public land mobile networks (PLMN).
  • PLMN public land mobile networks
  • RAN sharing technology multiple operators can use access network equipment at the same time, and access network equipment can share a certain segment or several segments of carriers of different operators to form a continuous large-bandwidth shared carrier, which can reduce infrastructure and equipment costs. cost.
  • the multicast service may be transmitted to terminal devices of different operators through the access network device.
  • Multicast services may include multicast/broadcast services (multicast broadcast service, MBS), which are mainly applicable to services for multiple terminal devices, such as live broadcasts, scheduled broadcast programs, weather warnings, and Internet of Vehicles communications.
  • MBS multicast broadcast service
  • a dedicated bearer may be established for the terminal device to transmit data to the terminal device in the form of unicast; another In a possible implementation manner, a dedicated bearer for the multicast service can be established to transmit data to multiple terminal devices in the form of multicast, which can save air interface resources, improve spectrum utilization, and improve transmission efficiency.
  • FIG. 2(a) to FIG. 2(c) are schematic diagrams of the protocol architecture provided by the embodiment of the present application.
  • the data packets in the packet data convergence protocol (PDCP) entity pass through a radio link control (radio link control, RLC) entity to the media access control (media access control, MAC) entity, and then send the data packet through the physical layer, and multiple terminal devices receive the data packet.
  • PDCP packet data convergence protocol
  • RLC radio link control
  • media access control media access control
  • the terminal device can monitor the group radio network temporary identifier (G-RNTI), and the data packets pass through the PTM path or PTM branch or PTM leg (leg) or the entity used for PTM transmission is sent to the terminal device.
  • G-RNTI group radio network temporary identifier
  • the terminal device can monitor the cell radio network temporary identifier (C-RNTI), and the data packet passes through the PTP path or PTP branch or PTP leg (leg) Or the entity used for PTP transmission is sent to the terminal device.
  • C-RNTI cell radio network temporary identifier
  • the path, branch, leg, or entity is a schematic description of the transmission path of the corresponding transmission mode, which is not limited in the present application.
  • Fig. 2(a) to Fig. 2(c) are only examples for illustration, and do not mean to limit them.
  • the terminal device is configured with a split MRB (split-MRB).
  • the PDCP entity of terminal device 1 is connected to the RLC1 entity and the RLC2 entity.
  • the RLC1 entity can correspond to the PTP path
  • the RLC2 entity can Corresponding to the PTM path, the PTP path may include the PDCP entity of the access network device, the RLC1 entity of the access network device, the MAC entity of the access network device, the MAC entity of the terminal device, the RLC1 entity of the terminal device, and the PDCP entity of the terminal device.
  • the PTM path may include the PDCP entity of the access network device, the RLC2 entity of the access network device, the MAC entity of the access network device, the MAC entity of the terminal device, the RLC2 entity of the terminal device, and the PDCP entity of the terminal device.
  • the PTP path may include the PDCP entity of the access network device, the RLC3 entity of the access network device, the MAC entity of the access network device, the MAC entity of the terminal device, the RLC1 entity of the terminal device, and the PDCP entity of the terminal device ;
  • the PTM path may be similar to the terminal device 1, and will not be repeated here.
  • the terminal device is only configured with a PTM path MRB (MRB with PTM leg only), which can be used to receive multicast data.
  • the PTM path may include the PDCP entity of the access network device, the RLC2 entity of the access network device, the MAC entity of the access network device, the MAC entity of the terminal device, the RLC entity of the terminal device, and the PDCP entity of the terminal device.
  • the access network device may include the RLC1 entity and the RLC3 entity, it is not associated with the PTM path, may not use the RLC1 entity and the RLC3 entity, or may not configure the RLC1 entity and the RLC3 entity, without limitation.
  • the terminal device is only configured with PTP path MRB (MRB with PTP leg only).
  • the multicast service process is the same as the process in the RAN non-shared scenario.
  • the multicast service session establishment process may include the following processes:
  • S301 The terminal device sends a protocol data unit (protocol data unit, PDU) session modification request (Session Modification Request) message.
  • protocol data unit protocol data unit, PDU
  • Session Modification Request Session Modification Request
  • the message includes an MBS session identity (session identity), the MBS session identity corresponds to a multicast service session (MBS session), and a multicast service session corresponds to a multicast service.
  • MBS session identity corresponds to a multicast service session (MBS session)
  • MBS session identifier can be obtained by the terminal device through a service announcement message.
  • the MBS session ID can indicate the multicast service (i.e., the multicast group) that the terminal device wishes to join, that is, the message can be used to request to join the multicast service session corresponding to the MBS session ID, and the message is a non-access layer (non access stratum, NAS) message is forwarded by AMF to SMF.
  • the multicast service i.e., the multicast group
  • the message can be used to request to join the multicast service session corresponding to the MBS session ID
  • the message is a non-access layer (non access stratum, NAS) message is forwarded by AMF to SMF.
  • NAS non access stratum
  • the SMF sends a PDU session update session management (session management, SM) context request (PDU session update SM context request) message to the AMF.
  • PDU session update session management session management, SM
  • PDU session update SM context request PDU session update SM context request
  • the message may include the MBS session identifier, N2SM information (information) and N1SM container (container).
  • N2SM information can include PDU session identification, MBS session identification, update PDU session information, unicast quality of service (quality of service, QoS) flow and corresponding information of multicast QoS flow;
  • N1SM container includes PDU session modification command (PDU Session Modification Command).
  • the AMF sends an N2 message to the RAN.
  • the N2 message includes a PDU session modification request, and the PDU session modification request includes multicast service session information and PDU session modification information. If the RAN does not support multicast transmission between the core network and the RAN, the NG interface will use the 5G core network (5G core, 5GC) for independent transmission, otherwise, the 5GC shared transmission will be used.
  • 5G core 5G core, 5GC
  • Optional S304 If the shared transmission channel has not been established, a 5GC shared transmission channel will be established.
  • the process of establishing a 5GC shared transmission channel may include the following steps:
  • Step a RAN sends N2MBS session request message (session request message) to AMF.
  • the message includes the MBS session identifier and N2SM information. If the RAN uses point-to-point shared transmission, the RAN provides the downlink address identifier in this message, that is, the access network (access network, AN) tunnel information (AN Tunnel Info).
  • the access network access network, AN
  • AN Tunnel Info the access network tunnel information
  • Step b AMF sends N2MBS session response message to RAN.
  • the message includes the MBS session identifier and N2SM information, and the N2SM information includes the MBS session identifier, and if the downlink address is not provided in step a, it also includes the downlink data transmission address for multicast shared transmission between MB-UPF and RAN.
  • the RAN sends a radio resource control (radio resource control, RRC) message to the terminal device.
  • RRC radio resource control
  • the RRC message is used to establish a radio resource bearer for the MBS session, and the RRC message includes the N1SM container.
  • the terminal device joins the multicast service session corresponding to the multicast service, and the network side can transmit the service data of the multicast service to the terminal device.
  • the terminal device does not need to receive the service data of the multicast service, it can also initiate a process of leaving the session corresponding to the multicast service, and the specific process will not be repeated here.
  • multicast service identification service identity
  • multicast service identification can be used to mark multicast services, that is, each multicast service has a unique multicast service identification or multicast service service.
  • the identifier is used to represent, and there is a one-to-one mapping relationship between the multicast/multicast service identifier and the multicast/multicast session identifier, so the multicast/multicast session identifier can also be used to refer to the multicast/multicast service The multicast service indicated by the service identifier.
  • the multicast/multicast service session identifier may be an Internet protocol (internet protocol, IP) multicast group address or a temporary mobile group identity (TMGI), where the TMGI may include a PLMN identifier and a group
  • IP Internet protocol
  • TMGI temporary mobile group identity
  • the PLMN identifier is used to indicate which PLMN the TMGI belongs to
  • the multicast/multicast service identifier is used to mark the specific multicast service in the PLMN
  • the multicast/multicast service identifier It can also be referred to simply as a service ID.
  • the multicast service identifier and the multicast session identifier are mainly used as examples for description. If not explicitly stated, the multicast service identifier can also be replaced by the multicast service identifier.
  • the service session identifier can also be replaced by a multicast service session identifier.
  • the core networks (core networks, CN) corresponding to different operators allocate TMGI independently, That is to say, for the same multicast service, the corresponding multicast service session identifiers in the CNs of different operators are not related, and may be the same or different.
  • the access network equipment is shared by PLMN1 of operator 1 and PLMN2 of operator 2.
  • core network device 1 in operator 1 allocates TMGI 1 for the multicast service
  • core network device 2 in operator 2 allocates TMGI 2 for the multicast service.
  • the access network device needs to establish a transmission channel and a radio bearer for the multicast service session corresponding to the multicast service, so as to transmit the data of the multicast service for the terminal equipment in PLMN1.
  • the access network device also needs to establish a transmission channel and a radio bearer for the multicast service session corresponding to the multicast service, so as to transmit the data of the multicast service for the terminal equipment in PLMN2.
  • the access network device cannot identify whether the service corresponding to TMGI 1 and the service corresponding to TMGI 2 are the same service, and the access network device will provide the multicast service in the two networks Different resources are allocated respectively, and the access network equipment will send the service data of the multicast service through the resources allocated in PLMN1, and at the same time, send the service data of the multicast service through the resources allocated in PLMN2, thus resulting in NG resources and waste of air interface resources, affecting transmission efficiency.
  • this application provides a method.
  • the access network equipment shared by multiple operators can identify whether the multicast services transmitted in different core networks are the same service. For the same multicast services of different core networks, they share the same NG resources and air interface resources, thereby saving transmission resources, improving resource utilization, and improving transmission efficiency.
  • the network architecture and business scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.
  • the interaction between core network equipment, access network equipment, and terminal equipment is used as an example for illustration.
  • the operations performed by the core network equipment can also be performed by chips or modules inside the core network equipment, and the operations performed by the access network equipment It may also be performed by a chip or module inside the access network device, and operations performed by the terminal device may also be performed by a chip or module inside the terminal device.
  • the access network device is an access network device shared by the first core network device and the second core network device.
  • the first core network device belongs to the core network device in the first core network
  • the first core network may belong to the first PLMN of the first operator
  • the second core network device belongs to the core network device in the second core network
  • the second The core network may belong to the second PLMN of the second operator.
  • the network where the first core network is located may also be referred to as a first network
  • the network where the second core network is located may also be referred to as a second network.
  • first operator and the second operator can also share the same core network equipment, that is to say, the first core network equipment and the second core network equipment can also be the same core network equipment, and the core network equipment can simultaneously Serving the first PLMN of the first operator and the second PLMN of the second operator.
  • FIG. 5 it is a schematic flowchart of a communication method provided in the embodiment of the present application, and the method includes:
  • S501 Establish a second multicast service session corresponding to the second multicast service between the access network device and the second core network device.
  • a second data transmission channel for transmitting the service data of the second multicast service between the access network device and the second core network device will be established, and a second data transmission channel for transmitting the service data of the second multicast service during the access
  • a second multicast radio bearer (multicast radio bearer, MRB) for transmitting service data of the second multicast service between the network device and the terminal device.
  • the data transmission channel may refer to a general packet radio service (general packet radio service, GPRS) tunneling protocol user plane (GPRS tunneling protocol user plane, GTP-U) tunnel or an IP multicast group tunnel.
  • GPRS general packet radio service
  • GTP-U general packet radio service tunneling protocol user plane
  • this step S501 is optional.
  • S502 The access network device sends second configuration information to the second terminal device.
  • the second terminal device receives the second configuration information.
  • the second terminal device belongs to the second core network device, that is, the second terminal device accesses the second core network device through the wireless access network.
  • the second configuration information may be sent through one or more RRC messages.
  • the second configuration information may include the configuration information of the MRB corresponding to the second multicast service, and the multicast radio bearer may be an enhanced data radio bearer (data radio bearer, DRB), or a newly defined MRB, wherein the multicast Including two data transmission methods: point-to-multipoint mode and point-to-point mode, among them, in point-to-multipoint mode, the corresponding user ID is G-RNTI; in point-to-point mode, the corresponding user ID is C-RNTI, in point-to-point mode , the second configuration information may not include its corresponding C-RNTI.
  • DRB data radio bearer
  • the second configuration information may include the second user identifier (for example, the second (2) G-RNTI), second multicast service service identifier, second multicast service session identifier, MRB identifier (or MRB label), PDCP configuration, RLC configuration, logical channel identifier, security configuration (security config), etc.
  • a second C-RNTI may also be included, and the second C-RNTI is used to scramble the scheduling information of the service data during point-to-point.
  • the second user identifier is used to scramble the first scheduling information
  • the first scheduling information is used to schedule the service data of the second multicast service
  • the second user identifier may be the second G-RNTI
  • the first scheduling information may be Downlink control information (DCI).
  • DCI Downlink control information
  • the second configuration information may include the second user identifier, the second multicast service identifier of the second multicast service, the second group The second multicast service session identifier, MRB identifier (or MRB mark), PDCP configuration, RLC configuration, logical channel identifier, security configuration (security config), etc. of the broadcast service session.
  • the second configuration information may include the second multicast service service identifier, the second multicast service session identifier, the MRB identifier (or MRB label), PDCP Configuration, RLC configuration, logical channel identification, security configuration, etc.
  • a second user identifier may also be included, and the second user identifier may be a second C-RNTI.
  • the second configuration information may include two parts: a radio bearer configuration information element (radio bearer config information element) and an RLC bearer configuration information element (RLC-bearer config information element).
  • the radio bearer configuration information element may include MRB identifier (or MRB label), PDCP configuration and security configuration, or include DRB identifier, PDCP configuration and security configuration; the RLC bearer configuration information element may include RLC configuration and the second user identifier.
  • the second multicast service service identifier and the second multicast service session identifier may be located in the radio bearer configuration information element, or in the RLC bearer configuration information element.
  • the radio bearer configuration information element may be as follows:
  • the DRB-ToReleaseList includes the DRB ID
  • SecurityConfig indicates the security configuration
  • the RLC bearer configuration information element may be as follows:
  • RLC-BearerConfig includes RLC bearer configuration.
  • corresponding configuration information can be obtained by modifying the above radio bearer configuration information element and RLC bearer configuration information element.
  • the MRB information is added to the radio bearer configuration information element in the above example, that is, the MRB addition or modification list (mrb-ToAddModList) and the MRB release list (mrb-ToReleaseList) are added, and the MRB addition or modification list is used
  • the MRB release list is used to release MRBs.
  • the MRB addition or modification list, and the MRB release list include the MRB identity (mrb-Identity);
  • the g-RNTI may also be added in the RLC bearer configuration information element, and the g-RNTI is used to indicate the second user identity.
  • Implementation method 2 add mrb-Flag in the DRB-ToAddModList of the radio bearer configuration information element, where mrb-Flag is used to indicate that the DRB corresponding to the radio bearer configuration information element is used as the MRB; optionally, if the access network device is When the second terminal device configures the MRB including the point-to-multipoint RLC entity, g-RNTI is added to the RLC bearer configuration information element, where the g-RNTI is used to indicate the identity of the second user.
  • the second configuration information may include a second user identifier (for example, a second G-RNTI), a second multicast service service identifier, a second multicast service session identifier, an MRB identifier (or MRB flag), PDCP configuration, RLC configuration, logic Channel identification, security configuration (security config), etc.
  • a second C-RNTI may also be included.
  • the access network device can establish a radio bearer for the multicast service for the terminal device, and multiple RLC entities can be configured.
  • step S502 is optional.
  • the first terminal device sends a session service request message to the first core network device, and the first core network device receives the session service request message of the first terminal device.
  • the first terminal device belongs to the first core network device, that is, the first terminal device accesses the radio access network corresponding to the first core network device.
  • the first core network device may be an AMF.
  • the session service request message may include the session identifier of the first multicast service, and the session service request message is used to request to acquire service data of the first multicast service.
  • the terminal device can obtain the first multicast service session identifier through a broadcast message from the access network device.
  • the first multicast service session identifier is a session identifier corresponding to the first multicast service in the first core network device, and the first multicast service session identifier is allocated by the core network side to which the first core network device belongs, such as 5G
  • the SMF may assign the first multicast service session identifier to the first multicast service.
  • the first multicast service session identifier may be the first IP multicast group address or the first TMGI.
  • the access network device in the network to which the first core network device belongs, before the first terminal device sends a session service request message, the access network device has not allocated NG resources and air interface resources for the first multicast service, that is, access The network device has not yet established a data transmission channel for transmitting service data of the first multicast service with the core network side, and has not established an MRB corresponding to the first multicast service.
  • the session service request message may be a NAS message, which is sent by the first terminal device to the first core network device through the access network device.
  • the first multicast service also corresponds to a first multicast service service identifier, and there is a mapping relationship between the first multicast service service identifier and the first multicast service session identifier.
  • step S503 is optional.
  • the first core network device sends the first information to the access network device, and the access network device acquires the first information from the first core network device.
  • the first information is used to request the first terminal device to join the multicast service session corresponding to the first multicast service.
  • the multicast service session corresponding to the first multicast service may be referred to as the first multicast service session
  • the multicast service session corresponding to the second multicast service may be referred to as the second multicast service session for short.
  • the first information may be carried by the PDU session modification request message, and the first information may include the first identifier corresponding to the first multicast service, the first QoS flow information of the first multicast service, the first multicast service session identifier, and the first Multicast service service identifier.
  • the first identifier may be the first multicast service identifier corresponding to the first multicast service in the first core network device .
  • the first identifier may be a first multicast service session identifier corresponding to the first multicast service in the first core network device.
  • the first identifier when the first multicast service session identifier is the first IP multicast group address, the first identifier may be the first IP multicast group address; when the first multicast service session identifier is the first TMGI, the first An identifier may be the first TMGI, or the first identifier may be the first service identifier in the first TMGI.
  • the first identifier may be an identifier corresponding to the first multicast service in the service server, or may be an identifier allocated by the service server.
  • the service server can assign an identifier to each multicast service, so that the identifier assigned by the service server can be used as the first identifier.
  • the first condition includes that the first multicast service and the second multicast service are the same multicast service, and the second multicast service is a multicast service provided by the second core network device.
  • How the access network device determines whether the first multicast service and the second multicast service are the same multicast service is not limited by this embodiment of the present application. In an implementation manner, if the first identifier corresponding to the first multicast service matches the second identifier corresponding to the second multicast service, the first multicast service and the second multicast service are the same multicast service.
  • the match between the first identifier and the second identifier may mean that the first identifier is the same as the second identifier, or may mean that there is a mapping relationship between the first identifier and the second identifier.
  • the following describes how the access network device determines whether the first multicast service is the same as the second multicast service according to the first identifier and the second identifier.
  • the first identifier is the first multicast service identifier corresponding to the first multicast service in the first core network device
  • the second identifier is the second multicast service in the second core network device The corresponding second multicast service service identifier.
  • the following situations may exist: in case one, it is pre-agreed to assign the same multicast service identifier to the same multicast service in different PLMNs (or different networks); in case two, the multicast service and The mapping relationship of multicast service identifiers.
  • the service identifiers of multicast services corresponding to multicast services in different PLMNs may be different, in the embodiment of this application, for the same multicast service, it can be pre-agreed to configure the same service ID in different PLMNs.
  • the multicast service identifier so that the access network device can uniquely determine the multicast service corresponding to the multicast service identifier in different PLMNs.
  • the first core network device and the second core network device can identify, according to the relevant information of the multicast service, that both the first PLMN where the first core network device is located and the second PLMN where the second core network device is located
  • the multicast service that exists in both the first PLMN and the second PLMN corresponds to the same multicast service identifier.
  • the relevant information of the multicast service may include but not limited to information provided by the service server, port information of the multicast service, and the like.
  • the multicast service identifiers of the multicast services existing in both the first PLMN and the second PLMN may be as shown in Table 1.
  • the access network device When the access network device acquires the first multicast service identifier (i.e. the first identifier), it determines the second multicast service identifier corresponding to the second multicast service provided by the second core network device, which is the same as the first multicast service identifier. If the business service identifiers are the same, it can be determined that the first multicast service and the second multicast service are the same multicast service.
  • the first multicast service identifier i.e. the first identifier
  • an identity distribution range may be pre-configured, and the identity distribution range includes multiple identities, and multicast service service identities of multicast services existing in multiple PLMNs may be located within the identity distribution range.
  • the ID allocation range may be 000010 to 0000FF.
  • the access network device when the access network device obtains the first multicast service service identifier (that is, the first identifier), it may first determine whether the first identifier is within the identifier allocation range, and then determine whether the first identifier is within the identifier allocation range. Whether the first identifier matches the second identifier. If the first identifier is not within the identifier allocation range, it may be determined that there is no identifier matching the first identifier.
  • the access network device may pre-establish a first mapping relationship, and the first mapping relationship includes a mapping relationship between multicast services and multicast service identifiers in PLMNs of different operators.
  • the first core network device or the second core network device may establish the first mapping relationship, and then send the first mapping relationship to the access network device.
  • the access network device can identify the multicast service identifier of each multicast service in different PLMNs according to the relevant information of the multicast service, so that the multicast service can be distributed in different PLMNs.
  • the multicast service identifiers in different PLMNs are saved to obtain the first mapping relationship.
  • the multicast service identifiers of the multicast services that exist in multiple PLMNs may be as shown in Table 2.
  • a multicast service may have multiple multicast service identifiers in one PLMN.
  • the access network device can determine the multicast service identifier corresponding to each multicast service in different PLMNs.
  • the access network device When the access network device acquires the first multicast service identifier (namely the first identifier), it can determine the first multicast service corresponding to the first identifier according to the first mapping relationship, and determine the corresponding service identifier of the second identifier according to the first mapping relationship. the second multicast service; if the first multicast service and the second multicast service are the same multicast service, it may be determined that the first identifier matches the second identifier. If the first multicast service and the second multicast service are different multicast services, it may be determined that the first identifier does not match the second identifier.
  • the first identifier obtained by the access network device from the first core network device in PLMN 1 is the identifier 1-1
  • the second identifier obtained from the second core network device in PLMN 2 For identification 1-3.
  • the access network device can determine that the first identifier corresponds to multicast service 1 in PLMN 1, and determine that the second identifier also corresponds to multicast service 1 in PLMN 2, so that the second identifier can be determined.
  • the first identifier and the second identifier correspond to the same multicast service, that is, the first identifier matches the second identifier.
  • the first identifier obtained by the access network device from the first core network device in PLMN 1 is the identifier 2-1
  • the second identifier obtained from the second core network device in PLMN 2 IDs are IDs 1-3.
  • the access network device can determine that the first identifier corresponds to multicast service 2 in PLMN 1, and determine that the second identifier corresponds to multicast service 1 in PLMN 2, so that the first identifier can be determined.
  • the identifier and the second identifier correspond to different multicast services, that is, the first identifier does not match the second identifier.
  • the access network device when it obtains the first identifier, it may first determine whether the first identifier is included in the first mapping relationship, and if it is determined that the first identifier is within the first mapping relationship, then determine the second identifier according to the first mapping relationship. Whether the first identifier matches the second identifier.
  • the access network device may consider that no session has been established in any PLMN for the first multicast service corresponding to the first identifier. In this way, session establishment efficiency can be improved.
  • the second possible implementation mode the first identifier is the first multicast service session identifier corresponding to the first multicast service in the first core network device, and the second identifier is the second multicast service in the second core network device The corresponding second multicast service session identifier.
  • Case 1 it is pre-agreed to assign the same multicast service session identifier to the same multicast service in different PLMNs (or different networks);
  • the mapping relationship between the multicast service and the session identifier of the multicast service may be established in advance.
  • Case 1 for the same multicast service, it can be pre-agreed to configure the same multicast service session identifier in different PLMNs, so that the access network device can uniquely determine the corresponding multicast service session identifier in different PLMNs. multicast service.
  • the first core network device and the second core network device can identify, according to the relevant information of the multicast service, that both the first PLMN where the first core network device is located and the second PLMN where the second core network device is located.
  • the multicast service that exists in both the first PLMN and the second PLMN corresponds to the same multicast service session identifier.
  • the access network device When the access network device obtains the first multicast service session identifier, it determines that the second multicast service session identifier corresponding to the second multicast service provided by the second core network device is the same as the first multicast service session identifier, then It may be determined that the first multicast service and the second multicast service are the same multicast service.
  • an identity allocation range may be pre-configured, and the identity allocation range includes multiple identities, and multicast service session identities of multicast services that exist in multiple PLMNs may be located within the identity allocation range.
  • the ID allocation range may be 000010 to 0000FF.
  • the access network device when the access network device acquires the first multicast service session identifier (that is, the first identifier), it may first determine whether the first identifier is within the identifier allocation range, and then determine whether the first identifier is within the identifier allocation range. Whether the first identifier matches the second identifier. If the first identifier is not within the identifier allocation range, it may be determined that there is no identifier matching the first identifier.
  • the access network device may pre-establish a second mapping relationship, and the second mapping relationship includes a mapping relationship between multicast services and multicast service session identifiers in PLMNs of different operators.
  • the first core network device or the second core network device may establish the second mapping relationship, and then send the second mapping relationship to the access network device.
  • the access network device can identify the multicast service session identifier of each multicast service in different PLMNs according to the relevant information of the multicast service, so that the multicast service can be distributed in different PLMNs.
  • the multicast service session identifiers in different PLMNs are saved to obtain the second mapping relationship.
  • the access network device When the access network device acquires the first multicast service session identifier (that is, the first identifier), it may determine the first multicast service corresponding to the first identifier according to the second mapping relationship, and determine the corresponding session identifier of the second identifier according to the second mapping relationship. the second multicast service; if the first multicast service and the second multicast service are the same multicast service, it may be determined that the first identifier matches the second identifier. If the first multicast service and the second multicast service are different multicast services, it may be determined that the first identifier does not match the second identifier.
  • the access network device when it obtains the first identifier, it may first determine whether the first identifier is included in the second mapping relationship, and if it is determined that the first identifier is in the second mapping relationship, then determine the second mapping relationship according to the first mapping relationship. Whether the first identifier matches the second identifier.
  • the access network device may consider that no session has been established in any PLMN for the first multicast service corresponding to the first identifier. In this way, session establishment efficiency can be improved.
  • the first identifier is a service identifier or a TMGI or an IP multicast group address
  • the above method may also be used, and will not be repeated here.
  • the first identifier may be a first public identifier assigned by the service server, and the second identifier may be a second public identifier assigned by the service server.
  • the first identifier is referred to as a first public identifier
  • the second identifier is referred to as a second public identifier.
  • the service server can allocate the same public identifier for the same multicast service in different PLMNs, that is, the public identifiers of the same multicast service are the same in different PLMNs.
  • the public identifier can exist independently, that is to say, the public identifier can be carried in an independent field.
  • the public identifier may also be located in the multicast session identifier or the multicast service identifier, that is, the public identifier may be a part of the multicast session identifier or the multicast service identifier.
  • the TMGI may include the PLMN identity, service identity and public identity.
  • the information sent by the first core network device to the access network device during the first session establishment process includes the identifier of the first PLMN, the first multicast service session identifier and the first public identifier ;
  • the information sent by the second core network device to the access network device during the establishment of the second session includes the identifier of the second PLMN, the identifier of the second multicast service session, and the second public identifier.
  • the access network device determines that the first public identifier is the same as the second public identifier, it can be determined that the first identifier matches the second identifier, that is, it is determined that the second session corresponds to the same multicast service as the first session; the access network device determines that If the first public identifier is different from the second public identifier, it may be determined that the first identifier does not match the second identifier, that is, it is determined that the second session corresponds to a different multicast service than the first session.
  • the access network device determines that the first multicast service and the second multicast service are the same multicast service, and may add the first terminal device to the multicast service session corresponding to the second multicast service. Further, since the first multicast service and the second multicast service are the same multicast service, the service data of the second multicast service can be used as the service data of the first multicast service, so the access network device can no longer The service data of the first multicast service is acquired from the network where the first core network device is located, and correspondingly, the network where the first core network device is located may no longer send the service data of the first multicast service to the access network device.
  • the access network device since the access network device may not acquire the service data of the first multicast service, the access network device may pass the second core network side between the access network device and the second core network device.
  • the second data transmission channel acquires service data of the first multicast service.
  • a first data transmission channel for transmitting service data of the first multicast service may be established, or the first data transmission channel may not be established.
  • the data transmission channel may refer to a GTP-U tunnel or an IP multicast group tunnel.
  • the access network device may send second information to the first core network device; where the second information is used to indicate not to communicate with the first core network device Establish the first data transmission channel between.
  • the access network device may send a channel establishment message to the first core network device, where the channel establishment message is used to indicate the establishment of the first data transmission channel, and instruct the first core network device to suspend the transmission of the first group service data of the multicast service or instruct the first core network device to suspend transmission of the service data of the first multicast service.
  • the access network device may also send third information to the first core network device, and the third information is used to indicate that the first data transmission channel is in an inactive state , or the third information is used to indicate that the service data of the first multicast service is suspended through the first data transmission channel, or the third information may be used to instruct the first core network device to suspend the transmission of the service data of the first multicast service.
  • the establishment process of the first data transmission channel is not limited in this application, and will not be repeated here.
  • the access network device may no longer allocate air interface resources for transmitting service data of the first multicast service.
  • the access network device may no longer configure the first MRB for the first multicast service, and the first MRB is used for communication between the access network device and the first terminal device The service data of the first multicast service is transmitted.
  • the access network device may multiplex the second MRB, and transmit the service data of the first multicast service to the first terminal device through the second MRB, wherein the second MRB is used to bear the service data of the second multicast service on the air interface. That is to say, the second multicast radio bearer is used to transmit the service data of the second multicast service with the second terminal device, and the second MRB is also used to transmit the second multicast service ( That is, the service data of the first multicast service).
  • the access network device may send the first configuration information to the first terminal device.
  • the content included in the first configuration information may be all the same as the content included in the second configuration information, that is, the first configuration information includes configuration information of the second MRB.
  • the content included in the first configuration information may be partly the same as the content included in the second configuration information, that is, the first configuration information includes a part of the configuration information of the second MRB.
  • the first configuration information includes the first user ID
  • the first user ID is the same as the second user ID included in the second configuration information, that is, the first configuration information includes the second user ID.
  • the security configuration included in the first configuration information is the same as the security configuration included in the second configuration information, where the security configuration includes a security algorithm and a secret key.
  • the MRB identifier, PDCP configuration, and RLC configuration included in the first configuration information are the same as the MRB identifier, PDCP configuration, and RLC configuration included in the second configuration information.
  • the radio bearer configuration information element included in the first configuration message is the same as the radio bearer configuration information element included in the second configuration message.
  • the RLC bearer configuration information element included in the first configuration message is the same as the RLC bearer configuration information element included in the second configuration message.
  • the RLC bearer configuration information element for point-to-multipoint transmission included in the first configuration message is the same as the RLC bearer configuration information element for point-to-multipoint transmission included in the second configuration message.
  • the first user identifier is used to scramble the first scheduling information, and the first scheduling information is used to schedule the service data of the second multicast service; the first user identifier may be the first G-RNTI. Since the first multicast service is the same as the second multicast service, the first scheduling information here can also be regarded as service data for scheduling the first multicast service.
  • the first configuration information that the access network device may send to the first terminal device may not include the first G-RNTI, and the first G-RNTI at this time
  • the configuration information may include the first C-RNTI, and the first C-RNTI may also be obtained in other ways, which is not limited in this embodiment of the present application.
  • the first C-RNTI is used to scramble the scheduling information of the service data of the second multicast service when the service data of the second multicast service is transmitted in a point-to-point manner.
  • the access network device configures for the first terminal device an MRB containing an RLC entity for point-to-point transmission, in the first configuration information sent by the access network device, except for the RLC bearer configuration and the RLC bearer configuration in the second configuration information
  • Other information may be the same as the information in the second configuration information. That is to say, at least one of the second multicast service identifier, the second multicast session identifier, PDCP configuration, and security configuration in the first configuration information may be the same as the corresponding information in the second configuration information.
  • FIG. 6 it is a schematic diagram of service data transmission provided by the embodiment of the present application.
  • the service server can transmit the second multicast service to the first core network device and the second core network device (the second multicast service at this time
  • the second multicast service is the service data of the first multicast service)
  • the first core network device no longer transmits the service data of the first multicast service to the access network device.
  • the access network device receives the service data of the second multicast service from the second core network device, it can transmit the service data to the first terminal device and the second terminal device in a multicast manner.
  • the access network device only needs to transmit service data once in the two networks, which can save NG resources and air interface resources, Improve data transmission efficiency and reduce resource overhead.
  • the first terminal device may monitor a physical downlink control channel (physical downlink control channel, PDCCH), and use the first user identifier (the first G-RNTI or the first C-RNTI) descrambles the cyclic redundancy code (cyclic redundancy code, CRC) of the PDCCH, and receives service data after successful descrambling, and the specific process will not be described again.
  • PDCCH physical downlink control channel
  • CRC cyclic redundancy code
  • the access network device when the access network device determines that the first multicast service and the second multicast service are the same multicast service, the access network device can use the related resources of the established second multicast service to send
  • the terminal devices in the two networks provide the service data of the second multicast service, so that the same multicast service from the two core networks can share the same NG resources and air interface resources, saving resources and improving data transmission efficiency.
  • the access network device may receive the first release information from the second core network device,
  • the first release information is used to indicate the release of the second data transmission channel, and optionally, the first release information may also be used to indicate the release of the second MRB.
  • the access network device may send the fifth information to the first core network device , the fifth information is used to trigger establishment of the first data transmission channel.
  • the access network device may send the sixth information to the first core network device , the sixth information is used to activate the first data transmission channel, or the sixth information is used to indicate to transmit the service data of the first multicast service through the first data transmission channel.
  • the first release information may include a release reason, and the release reason may include any of the following reasons:
  • the service server stops transmitting the service data of the second multicast service
  • the number of terminal devices receiving the service data of the second multicast service is less than or equal to the threshold.
  • the access network device can determine that the service data of the second multicast service and the service data of the first multicast service cannot be obtained, and the access network device can instruct the terminal device to release Second MRB.
  • the access network device sends a configuration message to the terminal device including mrb-ToReleaseList, where mrb-ToReleaseList includes the MRB identifier.
  • the configuration message sent by the access network device to the terminal device includes drb-ToReleaseList, where the drb-ToReleaseList includes the DRB identifier associated with the MRB.
  • the access network device may determine that the service data of the first multicast service needs to be obtained through the network where the first core network device is located, so as to send the fifth information or the first Six information.
  • the access network device may also establish the corresponding information of the first multicast service according to the first QoS flow information.
  • the first MRB or, the access network device can also update the second MRB according to the first QoS flow information, and the updated second MRB is used to transmit the service data of the first multicast service with the first terminal device.
  • the updated second MRB may be called the first MRB.
  • the specific process of establishing the first MRB according to the first QoS flow information is not limited by the embodiment of the present application, and will not be repeated here.
  • the security configuration corresponding to the second MRB may be updated, and other information of the second MRB may not be updated, such as the MRB identifier, PDCP configuration, second user identifier, and RLC configuration of the second MRB. Not updated.
  • the access network device may send third configuration information to the first terminal device, where the third configuration information includes configuration information of the first MRB, for example, may include at least one of the following information corresponding to the first MRB: the third User ID, MRB ID, PDCP configuration, RLC configuration, security configuration, etc.
  • the third user identifier is used for scrambling the second scheduling information
  • the second scheduling information is used for scheduling the service data of the first multicast service transmitted in the first MRB.
  • the third configuration information sent by the access network device to the first terminal device includes updated securityConfig, and this implementation manner is used to update the security configuration of the MRB.
  • the RLC bearer configuration information element in the third configuration information sent by the access network device to the first terminal device includes the updated third user identifier, that is, the g-RNTI, and this implementation is used to update The third user ID.
  • the third configuration information needs to be sent from the CU to the DU through the UE context establishment request (UE CONTEXT SETUP REQUEST) or UE context modification request (UE CONTEXT MODIFICATION REQUEST).
  • UE context establishment request UE CONTEXT SETUP REQUEST
  • UE context modification request UE CONTEXT MODIFICATION REQUEST
  • the access network device may also indicate the packet number of the data packet initially transmitted by the core network side.
  • the access network device may send the first packet number to the first core network device, where the first packet number is the last packet of the data packet belonging to the first multicast service sent to the first terminal device or, the first packet number is the largest packet number among at least one packet number corresponding to at least one data packet cached by the access network device, and at least one data packet is to be sent to the first terminal device and belongs to the first multicast Business packets.
  • the packet number may be a GTP-U serial number (serial number, SN) or a user datagram protocol (user datagram protocol, UDP)/IP packet serial number.
  • the first core network device may determine the initial data packet to be sent to the first terminal device according to the first packet number, for example, use the data packet corresponding to the first packet number as the initial data packet to be sent to the first terminal device, or use the first packet number as the initial data packet to be sent to the first terminal device, or The first data packet following the data packet with a packet number pair is used as the initial data packet sent to the first terminal device.
  • the packet numbers of the data packets sent by the service server are 1, 2, 3, 4, 5, and 6 in sequence; the packet numbers of the data packets received by the first core network device are 1, 2, 3, 4, 5; the packet number of the data packet received by the second core network device is 1, 2, 3, 4, 5 in sequence; the packet number of the data packet received by the access network device from the second core network device
  • the numbers are 1, 2, 3, and 4 in sequence.
  • the packet number of the data packet that has been sent to the terminal device is 1, but has not yet been sent to the terminal device, but the packet numbers of the cached data packets are 2, 3, and 4 in sequence.
  • the access network device can send packet number 1 (that is, as the first packet number) to the second core network device, and the second core network device starts from packet number 1 or packet number 2 start, continue to send data packets to the access network device; or, the access network device can send the packet number 4 (that is, as the first packet number) to the second core network device, and the second core network device will start from the packet number 4 or the packet number 4 Starting from No. 5, continue to send data packets to the access network device.
  • the access network device may indicate N to the first core network device, where N is an integer greater than 0.
  • the data packet obtained from the service server is the third data packet
  • the third data packet belongs to the first multicast service
  • the third data packet belongs to the first multicast service.
  • a core network device obtains N the second data packet located before the third data packet and separated by N data packets from the third data packet can be used as the initial data packet, and the first core network device sends the first terminal
  • the initial data packet sent by the device is the second data packet.
  • N is equal to 10, and the packet number of the third data packet is x, then the data packet with the packet number x-10 can be used as the initial data packet.
  • N may also be independently determined by the first core network device.
  • the first core network device uses the second data packet before the third data packet and the time interval corresponding to the third data packet as a preset duration as the initial data packet, and the first core network The initial data packet sent by the network device to the first terminal device is the second data packet.
  • the third data packet is y and the preset duration is T
  • the data packet before y and with a time interval of T between y can be used as the initial data packet.
  • the preset duration can be configured for the access network device, or the preset duration can be determined for the first core network device; the preset duration can also be determined according to the first delay and the second delay, and the first delay is the access network The transmission delay between the device and the first core network device, and the second delay is the transmission delay between the access network device and the second core network device.
  • the preset delay can satisfy the following form:
  • T ⁇ delay1+ ⁇ delay2+ ⁇
  • T is the preset time length
  • ⁇ is a number greater than 0
  • ⁇ is a number greater than 1
  • delay1 is the first delay
  • delay2 is the second delay
  • A is a preset value.
  • the first delay and the second delay may be indicated by the access network device to the first core network device; or the second delay may be indicated by the access network device to the first core network device, and the first delay It is calculated by the first core network device by receiving the time information carried in the data packet from the access network device, and the time information indicates the sending time of the data packet.
  • the access network device, the terminal device or the above-mentioned communication device may include a hardware structure and/or a software module, and a combination of a hardware structure, a software module, or a hardware structure plus a software module form to achieve the above functions. Whether one of the above-mentioned functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
  • each functional module in each embodiment of the present application may be integrated into one processor, or physically exist separately, or two or more modules may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules.
  • the embodiment of the present application further provides a communication device 800 .
  • the communication apparatus 800 may be the access network device in FIG. 1 , and is configured to implement the method for the access network device in the foregoing method embodiments.
  • the communication device may also be the core network device in FIG. 1 , and is used to implement the method corresponding to the core network device in the foregoing method embodiments.
  • the communication device 800 may include: a processing unit 801 and a communication unit 802 .
  • the communication unit may also be referred to as a transceiver unit, and may include a sending unit and/or a receiving unit, respectively configured to perform the steps of sending and receiving by the access network device or the terminal device in the method embodiments above.
  • the communication device provided by the embodiment of the present application will be described in detail with reference to FIG. 8 to FIG. 9 .
  • the behaviors and functions of the access network device in the foregoing method embodiments may be implemented by the communication apparatus 800, for example, implementing the method performed by the access network device in the embodiment in FIG. 5 .
  • the communication device 800 may be an access network device, or a component (such as a chip or a circuit) applied in an access network device, or a chip or a chipset in an access network device, or a chip used to perform correlation part of the method function.
  • the communication unit 802 may be used to perform the receiving or sending operation performed by the access network device in the embodiment shown in FIG. 5, and the processing unit 801 may be used to perform the receiving or sending operation performed by the access network device in the embodiment shown in FIG. Operations performed other than send and receive operations.
  • the communication unit is configured to obtain first information from the first core network device, where the first information is used to request that the first terminal device join the multicast service session corresponding to the first multicast service;
  • the processing unit is configured to add the first terminal device to the multicast service session corresponding to the second multicast service when the first condition is met, wherein the first condition includes that the first multicast service and the second multicast service are in the same group broadcast service, and the second multicast service is provided by the second core network equipment.
  • the communication unit is further configured to: send second information to the first core network device; where the second information is used to indicate not to establish the first data transmission channel with the first core network device, and the first A data transmission channel is used to transmit service data of the first multicast service.
  • the communication unit is further configured to: send third information to the first core network device, where the third information is used to indicate that the first data transmission channel established with the first core network device is in an inactive state , the first data transmission channel is used to transmit service data of the first multicast service.
  • the communication unit is further configured to: send a first user identifier to the first terminal device, where the first user identifier is used to scramble the first scheduling information, and the first scheduling information is used to schedule the second multicast service business data;
  • the first user identifier is the same as the second user identifier
  • the second user identifier is a user identifier sent to the second terminal device
  • the second terminal device belongs to the second core network device.
  • the communication unit is further configured to: send first configuration information to the first terminal device, where the first configuration information includes configuration information of a second multicast radio bearer, and the second multicast radio bearer is used to communicate with the first terminal device.
  • the service data of the second multicast service is transmitted between the two terminal devices, and the second multicast radio bearer is also used to transmit the service data of the second multicast service with the first terminal device.
  • the first information includes a first identifier corresponding to the first multicast service; the first condition includes that the first multicast service and the second multicast service are the same multicast service, including: the first identifier If it matches the second identifier corresponding to the second multicast service, the first multicast service and the second multicast service are the same multicast service.
  • the first identifier is the service identifier of the first multicast service corresponding to the first multicast service in the first core network device; or, the first identifier is the service identifier of the first multicast service in the first core network
  • the corresponding first multicast service session identifier in the device; or, the first identifier is the first Internet Protocol IP multicast group address or temporary mobile group identifier corresponding to the first multicast service in the first core network device; or
  • the first identifier is an identifier corresponding to the first multicast service in the service server or another identifier allocated by the service server for the first multicast service.
  • the communication unit is further configured to: receive first release information from the second core network device, where the first release information is used to indicate the release of the second data transmission channel, where the second data transmission channel is used for Transmitting service data of the second multicast service; sending fifth information or sixth information to the first core network device; the fifth information is used to trigger establishment of the first data transmission channel, and the sixth information is used to activate the first data transmission channel.
  • the first release information includes a release reason; before sending the fifth information or the sixth information to the first core network device, the processing unit is further configured to: determine that the release reason is any of the following: request to release the first
  • the second multicast service is converted from multicast transmission to unicast transmission; request to convert the second multicast service to unicast service; there is no terminal receiving the service data of the second multicast service in the network corresponding to the second core network device
  • the device in the network corresponding to the second core network device, the number of terminal devices receiving the service data of the second multicast service is less than or equal to the threshold.
  • the processing unit is further configured to: establish a first multicast radio bearer corresponding to the first multicast service according to the first quality of service flow information; or update the second multicast radio bearer according to the first quality of service flow information Radio bearer; the first multicast radio bearer is used to transmit the business data of the first multicast service with the first terminal device, and the first quality of service flow information comes from the first core network device; the second multicast radio bearer is used to communicate with the first terminal device The service data of the second multicast service is transmitted between the second terminal devices, and the updated second multicast radio bearer is used to transmit the service data of the first multicast service with the first terminal device.
  • the communication unit is further configured to: send third configuration information to the first terminal device, where the third configuration information includes a third user identifier, and the third user identifier is used to scramble the second scheduling information, and the second The scheduling information is used to schedule service data of the first multicast service.
  • the third configuration information further includes configuration information of the first multicast radio bearer.
  • the communication unit is further configured to: send the first packet number to the first core network device, where the first packet number is the last data packet belonging to the first multicast service sent to the first terminal device The packet number, or the first packet number is the largest packet number among at least one packet number corresponding to at least one cached data packet, and the at least one data packet is data to be sent to the first terminal device and belongs to the first multicast service Bag.
  • the communication unit is further configured to: receive a data packet belonging to the first multicast service from the first core network device; wherein, the initial data packet in the received data packet is the second data packet , the interval between the second data packet and the third data packet is N data packets, and the third data packet is a data packet obtained from the service server when the first core network device receives the fifth information or the sixth information; N is An integer greater than 0; or, the corresponding time interval between the second data packet and the third data packet is preset.
  • the preset duration is configured by the access network device, or the preset duration is determined by the first core network device, or the preset duration is determined according to the first delay and the second delay, and the first The delay is the transmission delay between the access network device and the first core network device, and the second delay is the transmission delay between the access network device and the second core network device.
  • the communication unit is configured to send first information to the access network device, where the first information is used to request that the first terminal device join a multicast service session corresponding to the first multicast service; the first When the terminal device joins the multicast service session corresponding to the second multicast service, it receives the second information or the third information from the access network device; wherein, the first multicast service and the second multicast service belong to the same group
  • the second multicast service is provided by the second core network device; the second information is used to indicate that the first data transmission channel is not established with the first core network device, and the first data transmission channel is used to transmit the first group
  • the service data of the multicast service; the third information is used to indicate that the first data transmission channel established with the first core network device is in an inactive state, and the first data transmission channel is used to transmit the service data of the first multicast service.
  • the communication unit is further configured to: receive fifth information or sixth information from the access network device; the fifth information is used to trigger establishment of the first data transmission channel, and the sixth information is used to activate the first Data transmission channel.
  • the communication unit is also used to: receive the first packet number from the access network device, where the first packet number is the last packet sent by the access network device to the first terminal device and belongs to the first multicast service
  • the packet number of the data packet, or the first packet number is the largest packet number among at least one packet number corresponding to at least one data packet cached by the access network device, at least one data packet is to be sent to the first terminal device, and A data packet belonging to the first multicast service; using the data packet corresponding to the first packet number as the initial data packet sent to the first terminal device.
  • the communication unit is further configured to: send a data packet belonging to the first multicast service to the access network device; wherein, the initial data packet in the data packet is the second data packet, and the second data packet N data packets are separated from the third data packet, and the third data packet is a data packet obtained from the service server when the first core network device receives the fifth information or the sixth information; N is an integer greater than 0; Alternatively, the corresponding time interval between the second data packet and the third data packet is a preset duration.
  • the preset duration is configured by the access network device, or the preset duration is determined by the first core network device, or the preset duration is determined according to the first delay and the second delay, and the first The delay is the transmission delay between the access network device and the first core network device, and the second delay is the transmission delay between the access network device and the second core network device.
  • processing unit 801 and the communication unit 802 may also perform other functions.
  • processing unit 801 and the communication unit 802 may also perform other functions.
  • FIG. 9 shows a communication device 900 provided in the embodiment of the present application.
  • the communication device shown in FIG. 9 may be an implementation manner of a hardware circuit of the communication device shown in FIG. 8 .
  • the communication device may be applicable to the flow chart shown above, and execute the functions of the terminal device or the access network device in the above method embodiments. For ease of illustration, FIG. 9 only shows the main components of the communication device.
  • a communication device 900 includes a processor 910 and an interface circuit 920 .
  • the processor 910 and the interface circuit 920 are coupled to each other.
  • the interface circuit 920 may be a transceiver or an input-output interface.
  • the communication device 900 may further include a memory 930 for storing instructions executed by the processor 910 or storing input data required by the processor 910 to execute the instructions or storing data generated after the processor 910 executes the instructions.
  • the processor 910 is used to implement the functions of the above processing unit 801
  • the interface circuit 920 is used to implement the functions of the above communication unit 802 .
  • the terminal device chip implements the functions of the terminal device in the above method embodiment.
  • the terminal device chip receives information from other modules in the terminal device (such as radio frequency modules or antennas), and the information is sent to the terminal device by the access network device; or, the terminal device chip sends information to other modules in the terminal device (such as radio frequency modules) module or antenna) to send information, which is sent by the terminal device to the access network device.
  • the access network equipment chip implements the functions of the access network equipment in the above method embodiments.
  • the access network device chip receives information from other modules (such as radio frequency modules or antennas) in the access network device, and the information is sent by the terminal device to the access network device; or, the access network device chip sends information to the access network device Other modules in the device (such as radio frequency modules or antennas) send information, which is sent by the access network device to the terminal device.
  • the processor in the embodiments of the present application can be a central processing unit (Central Processing Unit, CPU), and can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices.
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • memory can be random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable Programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), registers, hard disk, mobile hard disk or any other form of storage medium known in the art.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC may be located in the access network device or the terminal device.
  • the processor and the storage medium may also exist in the access network device or the terminal device as discrete components.
  • the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, optical storage, etc.) having computer-usable program code embodied therein.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

Landscapes

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

Abstract

本申请提供一种通信方法及装置，其中方法包括：获取来自第一核心网设备的第一信息，所述第一信息用于请求将第一终端设备加入第一组播业务对应的组播业务会话；满足第一条件时，将所述第一终端设备加入第二组播业务对应的组播业务会话，其中，所述第一条件包括所述第一组播业务与所述第二组播业务为相同的组播业务，所述第二组播业务为第二核心网设备提供的。通过将第一终端设备加入第二组播业务对应的组播业务会话，从而可以采用已经建立的第二组播业务的相关资源，同时向两个网络中的终端设备提供第二组播业务的业务数据，实现对来自两个核心网的相同组播业务共用相同的NG资源和空口资源，节省了资源，提高数据传输效率。

Description

一种通信方法及装置
相关申请的交叉引用
本申请要求在2021年08月05日提交中国专利局、申请号为202110897090.9、申请名称为“一种通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及装置。
背景技术
在5G的新无线(new radio，NR)系统中，可以采用网络共建共享技术使得多个运营商共享网络基础设施，网络共建共享技术主要的应用包括无线接入网(radio access network，RAN)共享(sharing)。RAN sharing是指一个RAN可以连接到多个运营商核心网节点，可以由多个运营商合作共建RAN，也可以是其中一个运营商单独建设RAN，而其他运营商租用该运营商的RAN网络。
在RAN sharing场景下，如何节约网络资源，提高传输效率，是一个亟待解决的问题。
发明内容
本申请提供一种通信方法及装置，用以节约资源，提高传输效率。
第一方面，本申请提供一种通信方法，该方法适用于接入网设备与终端设备之间执行会话建立的场景。该方法的执行主体为接入网设备或接入网设备中的芯片或一个模块，这里以接入网设备为执行主体为例进行描述。该方法包括：接入网设备获取来自第一核心网设备的第一信息，第一信息用于请求将第一终端设备加入第一组播业务对应的组播业务会话；满足第一条件时，将第一终端设备加入第二组播业务对应的组播业务会话，其中，第一条件包括第一组播业务与第二组播业务为相同的组播业务，第二组播业务为第二核心网设备提供的。
通过上面的方法可知，第一组播业务与第二组播业务为同一个组播业务时，将第一终端设备加入第二组播业务对应的组播业务会话，从而可以采用已经建立的第二组播业务的相关资源，同时向两个网络中的终端设备提供第二组播业务的业务数据，实现对来自两个核心网的相同组播业务共用相同的NG资源和空口资源，节省了资源，提高数据传输效率。
在一种可能的设计中，还包括：向第一核心网设备发送第二信息；其中，第二信息用于指示不与第一核心网设备之间建立第一数据传输通道，第一数据传输通道用于传输第一组播业务的业务数据。
在一种可能的设计中，还包括：向第一核心网设备发送第三信息，第三信息用于指示与第一核心网设备之间建立的第一数据传输通道为非激活态，第一数据传输通道用于传输第一组播业务的业务数据。
采用上面的方法可以可先不通过第一核心网获取业务数据，接入网设备只接收来自第 二核心网的数据，节省了NG接口资源，提高数据传输效率。
在一种可能的设计中，还包括：向第一终端设备发送第一用户标识，第一用户标识用于加扰第一调度信息，第一调度信息用于调度第二组播业务的业务数据；
第一用户标识和第二用户标识相同，第二用户标识为向第二终端设备发送的用户标识，第二终端设备属于第二核心网设备。
在一种可能的设计中，还包括：向第一终端设备发送第一配置信息，第一配置信包括第二组播无线承载的配置信息，第二组播无线承载用于与第二终端设备之间传输第二组播业务的业务数据，第二组播无线承载还用于与第一终端设备之间传输第二组播业务的业务数据。
采用上面的方法，第一终端设别和第二终端设备可以用相同的组播无线承载接收数据，节省了空口资源，提升数据传输效率。
在一种可能的设计中，第一信息包括第一组播业务对应的第一标识；第一条件包括第一组播业务与第二组播业务为相同的组播业务，包括：第一标识与第二组播业务对应的第二标识相匹配，则第一组播业务与第二组播业务为相同的组播业务。
在一种可能的设计中，第一标识为第一组播业务在第一核心网设备中对应的第一组播业务服务标识；或者，第一标识为第一组播业务在第一核心网设备中对应的第一组播业务会话标识；或者，第一标识为第一组播业务在所述第一核心网设备中对应的第一互联网协议IP组播组地址或临时移动组标识；或者，所述第一标识为所述第一组播业务在业务服务器中对应的标识或者业务服务器为第一组播业务分配的其他标识。
采用上面的方法，接入网设备可以识别第一组播业务和第二组播业务为相同的组播业务，从而可以进一步实现对来自两个核心网的相同组播业务共用相同的NG资源和/或空口资源。
在一种可能的设计中，还包括：接收来自第二核心网设备的第一释放信息，第一释放信息用于指示释放第二数据传输通道，其中，第二数据传输通道用于传输第二组播业务的业务数据；向第一核心网设备发送第五信息或第六信息；第五信息用于触发建立第一数据传输通道，第六信息用于激活第一数据传输通道。
在一种可能的设计中，第一释放信息包括释放原因；向第一核心网设备发送第五信息或第六信息之前，方法还包括：确定释放原因为以下任一种：请求将第二组播业务由组播方式传输转换为单播方式传输；请求将第二组播业务转换为单播业务；第二核心网设备对应的网络中没有接收第二组播业务的业务数据的终端设备；第二核心网设备对应的网络中，接收第二组播业务的业务数据的终端设备的数量小于或等于阈值。
采用上面的方法，第一核心网设备可以获取接入网设备释放第二组播业务的原因，从而判断为第一终端设备提供业务的方式。
在一种可能的设计中，还包括：根据第一服务质量流信息建立第一组播业务对应的第一组播无线承载；或者，根据第一服务质量流信息更新第二组播无线承载；第一组播无线承载用于与第一终端设备之间传输第一组播业务的业务数据，第一服务质量流信息来自第一核心网设备；第二组播无线承载用于与第二终端设备之间传输第二组播业务的业务数据，更新后的第二组播无线承载用于与第一终端设备之间传输第一组播业务的业务数据。
在一种可能的设计中，还包括：向第一终端设备发送第三配置信息，第三配置信息包括第三用户标识，第三用户标识用于加扰第二调度信息，第二调度信息用于调度第一组播 业务的业务数据。
在一种可能的设计中，第三配置信息还包括第一组播无线承载的配置信息。
采用上面的方法，当第一核心网继续第一组播业务时，第一终端设备将第二组播无线承载重建或更新为第一组播无线承载。
在一种可能的设计中，还包括：向第一核心网设备发送第一包号，第一包号为向第一终端设备发送的最后一个属于第一组播业务的数据包的包号，或者，第一包号为缓存的至少一个数据包对应的至少一个包号中最大的包号，至少一个数据包为待发送至第一终端设备、且属于第一组播业务的数据包。
可以理解的，由于数据包编号的限制，当数据包编号到一个最大值，比如4095(对应10比特的编号长度)，后面的包会重新从0开始，所以上述最大的包号实质是指最晚编号的包。比如三个数据包中，第一个数据包编号为4094，第二个数据包编号为4095，第三个数据包编号为0((4095+1)Mod 4096，Mod代表取模)，则第三个数据包的包号认为是最大的包号。
在一种可能的设计中，还包括：接收来自第一核心网设备的属于第一组播业务的数据包；其中，接收到的数据包中的起始数据包为第二数据包，第二数据包与第三数据包之间间隔N个数据包，第三数据包为第一核心网设备接收到第五信息或第六信息时，从业务服务器获取到的数据包；N为大于0的整数；或者，第二数据包与第三数据包之间对应的时间间隔预设时长。
在一种可能的设计中，预设时长为接入网设备配置的，或者预设时长为第一核心网设备确定的，或者预设时长根据第一时延和第二时延确定，第一时延为接入网设备与第一核心网设备之间的传输时延，第二时延为接入网设备与第二核心网设备之间的传输时延。
采用上面的设计，当提供第一组播业务的数据的核心网设备由第二核心网设备更改为第一核心网设备时，可以避免丢包的情况发生，保证业务连续性。
第二方面，本申请还提供一种通信装置，该通信装置具有实现上述第一方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括接口电路，该接口电路用于支持该通信装置与其它设备之间的通信。
在一种可能的实现方式中，该通信装置可以为接入网设备，或者接入网设备中的芯片或一个模块。
在一种可能的实现方式中，该通信装置包括相应的功能模块，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的实施方式中，通信装置的结构中包括处理单元和通信单元，这些单元可以执行上述方法示例中相应功能，具体参见第一方面提供的方法中的描述，此处不做赘述。
第三方面，本申请提供一种通信方法，该方法适用于接入网设备与终端设备之间执行会话建立的场景。该方法的执行主体为第一核心网设备或第一核心网设备中的芯片或一个模块，这里以第一核心网设备为执行主体为例进行描述。该方法包括：第一核心网设备向 接入网设备发送第一信息，第一信息用于请求将第一终端设备加入第一组播业务对应的组播业务会话；第一终端设备加入第二组播业务对应的组播业务会话的情况下，接收来自接入网设备的第二信息或第三信息；其中，第一组播业务与第二组播业务为相同的组播业务，第二组播业务为第二核心网设备提供的；第二信息用于指示不与第一核心网设备之间建立第一数据传输通道，第一数据传输通道用于传输第一组播业务的业务数据；第三信息用于指示与第一核心网设备之间建立的第一数据传输通道为非激活态，第一数据传输通道用于传输第一组播业务的业务数据。
在一种可能的设计中，还包括：接收来自接入网设备的第五信息或第六信息；第五信息用于触发建立第一数据传输通道，第六信息用于激活第一数据传输通道。
在一种可能的设计中，还包括：接收来自接入网设备的第一包号，第一包号为接入网设备向第一终端设备发送的最后一个属于第一组播业务的数据包的包号，或者，第一包号为接入网设备缓存的至少一个数据包对应的至少一个包号中最大的包号，至少一个数据包为待发送至第一终端设备、且属于第一组播业务的数据包；将第一包号对应的数据包作为向第一终端设备发送的起始数据包。
在一种可能的设计中，还包括：向接入网设备发送属于第一组播业务的数据包；其中，数据包中的起始数据包为第二数据包，第二数据包与第三数据包之间间隔N个数据包，第三数据包为第一核心网设备接收到第五信息或第六信息时，从业务服务器获取到的数据包；N为大于0的整数；或者，第二数据包与第三数据包之间对应的时间间隔预设时长。
在一种可能的设计中，预设时长为接入网设备配置的，或者预设时长为第一核心网设备确定的，或者预设时长根据第一时延和第二时延确定，第一时延为接入网设备与第一核心网设备之间的传输时延，第二时延为接入网设备与第二核心网设备之间的传输时延。
第四方面，本申请还提供一种通信装置，该通信装置具有实现上述第二方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括接口电路，该接口电路用于支持该通信装置与其它设备之间的通信。
在一种可能的实现方式中，该通信装置可以为核心网设备，或者核心网设备中的芯片或一个模块。
在一种可能的实现方式中，该通信装置包括相应的功能模块，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的模块。
在一种可能的实施方式中，通信装置的结构中包括处理单元和通信单元，这些单元可以执行上述方法示例中相应功能，具体参见第二方面提供的方法中的描述，此处不做赘述。
第五方面，提供了一种通信装置，包括处理器和接口电路，可选地，还包括存储器。接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器用于执行所述存储器中存储的计算机程序或指令，实现前述第一方面中任意可能的实现方式中的方法。
第六方面，提供了一种通信装置，包括处理器和接口电路，可选地，还包括存储器。 接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器用于执行所述存储器中存储的计算机程序或指令，实现前述第二方面中任意可能的实现方式中的方法。
第七方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得所述计算机实现前述第一方面中任意可能的实现方式中的方法。
第八方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得所述计算机实现前述第二方面中任意可能的实现方式中的方法。
第九方面，提供了一种存储有计算机可读指令的计算机程序产品，当所述计算机可读指令在计算机上运行时，使得所述计算机实现前述第一方面中任意可能的实现方式中的方法。
第十方面，提供了一种存储有计算机可读指令的计算机程序产品，当所述计算机可读指令在计算机上运行时，使得所述计算机实现前述第二方面中任意可能的实现方式中的方法。
第十一方面，提供一种芯片，该芯片包括处理器，还可以包括存储器，用于执行所述存储器中存储的计算机程序或指令，使得芯片实现前述第一方面中任意可能的实现方式中的方法。
第十二方面，提供一种芯片，该芯片包括处理器，还可以包括存储器，用于执行所述存储器中存储的计算机程序或指令，使得芯片实现前述第二方面中任意可能的实现方式中的方法。
第十三方面，提供了一种通信装置，包括用于实现前述第一方面中任意可能的实现方式中方法的模块。
第十四方面，提供了一种通信装置，包括用于实现前述第二方面中任意可能的实现方式中方法的模块。
第十五方面，提供一种通信系统，所述系统包括第二方面所述的装置(如接入网设备)、以及第四方面所述的装置(如第一核心网设备)。
附图说明
图1为本申请适用的一种网络架构示意图；
图2(a)至图2(c)为本申请实施例提供的协议架构示意图；
图3为终端设备加入组播会话的流程示意图；
图4为本申请实施例提供的一种业务数据传输示意图；
图5为本申请实施例提供的一种通信方法流程示意图；
图6为本申请实施例提供的一种业务数据传输示意图；
图7为本申请实施例提供的一种数据包传输示意图；
图8为本申请实施例提供的一种通信装置结构示意图；
图9为本申请实施例提供的一种通信装置结构示意图。
具体实施方式
下面结合说明书附图对本申请实施例做详细描述。
本申请实施例可以应用于各种移动通信系统，例如：NR系统、全球移动通讯(global system of mobile communications，GSM)系统、长期演进(long term evolution，LTE)系统以及未来通信系统等其它通信系统，在此不做限制。
本申请实施例中，以终端设备、接入网设备以及核心网设备之间的交互为例进行描述，需要说明的是，本申请实施例提供的方法，不仅可以应用于终端设备与网络侧之间的交互，还可以应用于任意两个设备之间的交互中，例如设备到设备(device-to-device，D2D)通信中，本申请实施例对此并不限定。
本申请实施例中，终端设备可以简称为终端，为具有无线收发功能的设备或可设置于该设备的芯片。其中，终端设备也可以称为用户设备(user equipment，UE)、接入终端等。在实际应用中，本申请的实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端等。本申请实施例中，用于实现终端设备的功能的装置可以是终端设备；也可以是能够支持终端设备实现该功能的装置，例如芯片系统，该装置可以被安装在终端设备中或者与终端设备匹配使用。
接入网设备：可以是无线网络中各种制式下无线接入设备，例如接入网设备可以是将终端设备接入到无线网络的RAN节点，又可以称为RAN设备或基站。一些接入网设备的举例为：下一代基站(generation Node B，gNodeB)、传输接收点(transmission reception point，TRP)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)等。在一种网络结构中，接入网设备可以包括集中单元(centralized unit，CU)节点或分布单元(distributed unit，DU)节点，或包括CU节点和DU节点。接入网设备包括CU和DU时，多个DU可以由一个CU集中控制。本申请实施例中，用于实现接入网设备的功能的装置可以是接入网设备；也可以是能够支持接入网设备实现该功能的装置，例如芯片系统，该装置可以被安装在接入网设备中或者与接入网设备匹配使用。
核心网设备，可以是用于对终端设备的接入和移动性进行管理的设备，例如可以是接入和移动性管理(Access and Mobility Management Function,AMF)网元或者会话管理功能(Session Management Function，SMF)网元或者多播广播(multicast broadcast，MB)-SMF网元或者用户面功能(user plane function，UPF)或者MB-UPF，还可以是移动性管理实体(mobility management entity，MME)网元等，本申请对此并不限定。
本申请可以应用于RAN共享的场景中，在RAN共享场景中，无线接入网或无线接入网和部分核心网可以共享给多个运营商。RAN共享存在多种架构，本申请主要涉及多运营商核心网(multi-operator core network，MOCN)架构。
具体的，如图1所示，为本申请适用的一种网络架构示意图。图1中，一个RAN可以连接到至少两个运营商的核心网节点，即被至少两个运营商共享使用。图1中以运营商A和运营商B共享RAN为例进行描述。图1所示的网络架构中，多家运营商共享使用接入网设备，共享接入网设备的小区，但每个运营商拥有各自独立的核心网。接入网设备与各运营商的核心网分别建立S1接口连接或下一代(next generation，NG)接口连接，接入网设备可以为多个运营商的终端设备提供服务。这种共享方式下核心网独立；配置管理、告警管理、性能指标等都需要主运营商管理，部分性能指标可区分公用陆地移动网(public  land mobile network，PLMN)。通过RAN sharing技术，多个运营商可以同时使用接入网设备，接入网设备可以共享不同运营商的某段或某几段载波，形成一个连续大带宽的共享载波，可以降低基础设施和设备费用。
本申请实施例中，在RAN共享的场景中，可以通过接入网设备向不同运营商的终端设备传输多播业务。多播业务可以包括组播/广播业务(multicast broadcast service，MBS)，主要适用于面向多个终端设备的业务，例如现场直播、定时播放节目、天气预警以及车联网通信等。
接入网设备在传输多播业务的业务数据时，一种可能的实现方式中，可以通过为终端设备建立专用的承载，从而以单播(unicast)的形式向终端设备传输数据；另一种可能的实现方式中，可以通过建立多播业务专用的承载，从而以组播(multicast)的形式向多个终端设备传输数据，这样可以节约空口资源，提高频谱利用率，提高传输效率。
图2(a)至图2(c)为本申请实施例提供的协议架构示意图。结合图2(a)至图2(c)，接入网设备进行多播传输时，分组数据汇聚层协议(packet data convergence protocol，PDCP)实体中的数据包通过一个无线链路控制(radio link control，RLC)实体传输到媒体接入控制(media access control，MAC)实体，然后通过物理层将数据包发送出去，多个终端设备对此数据包进行接收。若采用的是点对多点(point to multipoint，PTM)传输方式，终端设备可以监听组无线网络临时标识(group radio network temporary identifier，G-RNTI)，数据包通过PTM路径或PTM分支或PTM腿(leg)或用于PTM传输的实体发送至终端设备。若采用的是点对点(point to point，PTP)传输方式，终端设备可以监听小区无线网络临时标识(cell radio network temporary identifier，C-RNTI)，数据包通过PTP路径或PTP分支或PTP腿(leg)或用于PTP传输的实体发送至终端设备。其中路径，分支，腿，或实体是相应传输方式的传输路径示意性描述，本申请不做限制。本申请实施例中，对于接入网设备内部的协议栈结构并不限制，图2(a)至图2(c)中只是举例说明，并不代表对其限定。
图2(a)中，终端设备配置分割形式的MRB(split-MRB)，以终端设备1为例，终端设备1的PDCP实体连接RLC1实体和RLC2实体，RLC1实体可以对应PTP路径，RLC2实体可以对应PTM路径，PTP路径可以包括接入网设备的PDCP实体、接入网设备的RLC1实体、接入网设备的MAC实体、终端设备的MAC实体、终端设备的RLC1实体、终端设备的PDCP实体。PTM路径可以包括接入网设备的PDCP实体、接入网设备的RLC2实体、接入网设备的MAC实体、终端设备的MAC实体、终端设备的RLC2实体、终端设备的PDCP实体。对于终端设备2，PTP路径可以包括接入网设备的PDCP实体、接入网设备的RLC3实体、接入网设备的MAC实体、终端设备的MAC实体、终端设备的RLC1实体、终端设备的PDCP实体；PTM路径可以和终端设备1类似，在此不再赘述。
图2(b)中，终端设备只配置PTM路径MRB(MRB with PTM leg only)，可用于接收组播数据。PTM路径可以包括接入网设备的PDCP实体、接入网设备的RLC2实体、接入网设备的MAC实体、终端设备的MAC实体、终端设备的RLC实体、终端设备的PDCP实体。其中，接入网设备虽然可以包括RLC1实体和RLC3实体，但与PTM路径没有关联，可以不使用RLC1实体和RLC3实体，也可以不配置RLC1实体和RLC3实体，不做限定。
图2(c)中，终端设备只配置PTP路径MRB(MRB with PTP leg only)。
在RAN共享的场景中，多播业务过程和RAN非共享的场景中的过程是一样的，具体 的，如图3所示，多播业务会话建立过程可以包括以下流程：
S301：终端设备发送协议数据单元(protocol data unit，PDU)会话修改请求(Session Modification Request)消息。
其中，该消息包括MBS会话标识(session identity)，MBS会话标识对应一个多播业务会话(MBS会话)，一个组播业务会话对应一个组播业务。MBS会话标识可以是终端设备通过服务公告消息获得的。
通过MBS会话标识，可以指示终端设备希望加入的组播业务(即组播组)，即该消息可以用于请求加入MBS会话标识对应的组播业务会话，该消息为非接入层(non access stratum，NAS)消息，由AMF转发至SMF。
需要说明的是，在5G等网络中，在进行组播业务数据传输之前，需要先建立一个相应的PDU会话，后续的需要传输的组播数据需要通过PDU会话来承载。
S302：SMF向AMF发送PDU会话更新会话管理(session management，SM)上下文请求(PDU session update SM context request)消息。
该消息可以包括MBS会话标识，N2SM信息(information)以及N1SM容器(container)。其中N2SM信息可以包括PDU会话标识,MBS会话标识，更新PDU会话信息，单播服务质量(quality of service，QoS)流和多播QoS流的对应信息；N1SM容器包括PDU会话修改命令(PDU Session Modification Command)。
S303：AMF向RAN发送N2消息。
N2消息包括PDU会话修改请求,PDU会话修改请求包含组播业务会话信息和PDU会话修改信息。如果RAN不支持核心网和RAN之间的多播传输，NG接口上将会采用5G核心网(5G core，5GC)独立传输，否则，采用5GC共享传输。
可选的S304：如果共享传输通道没有被建立，将建立5GC共享传输通道。
建立5GC共享传输通道的过程可以包括以下步骤：
步骤a：RAN向AMF发送N2MBS会话请求消息(session request message)。
该消息包含MBS会话标识,N2SM信息。如果RAN使用点对点的共享传输，RAN在此消息中提供下行地址标识，即接入网(access network，AN)隧道信息(AN Tunnel Info)。
步骤b：AMF向RAN发送N2MBS会话响应消息。
该消息包括MBS会话标识和N2SM信息，N2SM信息包括MBS会话标识，如果步骤a中未提供下行地址，还包括用于MB-UPF和RAN之间多播共享传输的下行数据传输地址。
通过上述过程，完成建立5GC共享传输通道。
S305：RAN向终端设备发送无线资源控制(radio resource control，RRC)消息。
该RRC消息用于为MBS会话建立无线资源承载，该RRC消息中包括N1SM容器。
通过上述过程，终端设备加入多播业务对应的多播业务会话，网络侧可以向终端设备传输该多播业务的业务数据。终端设备不需要接收该多播业务的业务数据时，还可以发起离开多播业务对应的会话的流程，具体过程不再赘述。
本申请实施例主要涉及组播业务，组播业务有时也被称为多播业务，本申请实施例中，均统称为组播业务。本申请实施例中，可以采用组播业务服务标识(service identity)或多播业务服务标识来标记组播业务，即每个组播业务都有一个唯一的组播业务服务标识或多播业务服务标识用来表征，而组播/多播业务服务标识与组播/多播业务会话标识存在一一 映射关系，因此组播/多播业务会话标识也可以用来指代组播/多播业务服务标识所指代的组播业务。一种实现方式中，组播/多播业务会话标识可以为互联网协议(internet protocol，IP)组播组地址或者临时移动组标识(temporary mobile group identity，TMGI)，其中TMGI可以包括PLMN标识和组播/多播业务服务标识，PLMN标识用于表征该TMGI是属于哪个PLMN内的，组播/多播业务服务标识用于标记该PLMN内具体的多播业务，组播/多播业务服务标识也可以简称为服务标识。本申请实施例中，为了描述方便，主要以组播业务服务标识、组播业务会话标识为例进行描述，如果没有明确说明，组播业务服务标识也可以替换为多播业务服务标识，组播业务会话标识也可以替换为多播业务会话标识。
进一步的，结合前面的描述，对于RAN共享场景，当同一个业务服务器，通过不同运营商传输组播业务的数据时，不同运营商对应的核心网(core network，CN)相互独立的分配TMGI，也就是说，对于同一个组播业务，在不同运营商的CN中对应的组播业务会话标识没有关联，可能相同，也可能不同。如图4所示，接入网设备被运营商1的PLMN1和运营商2的PLMN2共享，当同一个业务服务器同时通过运营商1的网络和运营商2的网络发送传输组播业务的数据时，运营商1中的核心网设备1为该组播业务分配的TMGI 1，运营商2中的核心网设备2为该组播业务分配TMGI 2。
对于同一个组播业务，在PLMN1中，接入网设备需要为此组播业务对应的组播业务会话建立传输通道和无线承载，从而为PLMN1中的终端设备传输该组播业务的数据。同样的，在PLMN2中，接入网设备也需要为此组播业务对应的组播业务会话建立传输通道和无线承载，从而为PLMN2中的终端设备传输该组播业务的数据。
通过上面的过程可知，在RAN共享场景下，接入网设备无法识别TMGI 1对应的业务和TMGI 2对应的业务是否是相同的业务，接入网设备会为该组播业务在两个网络中分别分配不同的资源，接入网设备会通过在PLMN1中分配的资源发送该组播业务的业务数据，同时，通过在PLMN2中分配的资源发送该组播业务的业务数据，从而，导致NG资源和空口资源的浪费，影响传输效率。
为此，本申请提供一种方法，被多个运营商共享的接入网设备，可以识别不同核心网中传输的组播业务是否为同一个业务，对于不同核心网的相同组播业务共用相同的NG资源和空口资源，从而节约传输资源，提高资源利用率，提高传输效率。
本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请中，以核心网设备、接入网设备以及终端设备之间交互为例进行说明，核心网设备执行的操作也可以由核心网设备内部的芯片或模块执行，接入网设备执行的操作也可以由接入网设备内部的芯片或模块执行，终端设备执行的操作也可以由终端设备内部的芯片或模块执行。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。
本申请实施例中，接入网设备为第一核心网设备和第二核心网设备共享的接入网设备。其中第一核心网设备属于第一核心网中的核心网设备，第一核心网可以属于第一运营商的 第一PLMN，第二核心网设备属于第二核心网中的核心网设备，第二核心网可以属于第二运营商的第二PLMN。第一核心网所处的网络也可以称为第一网络，第二核心网所处的网络也可以称为第二网络。
另外，第一运营商和第二运营商也可以共享同一个核心网设备，也就是说，第一核心网设备和第二核心网设备也可以为同一个核心网设备，该核心网设备可以同时为第一运营商的第一PLMN和第二运营商的第二PLMN服务。
如图5所示，为本申请实施例提供的一种通信方法流程示意图，该方法包括：
S501：接入网设备与第二核心网设备之间建立第二组播业务对应的第二组播业务会话。
第二组播业务会话建立的具体过程，本申请实施例并不限定，在此不再赘述。
在建立第二组播业务会话的过程中，会建立在接入网设备与第二核心网设备之间传输第二组播业务的业务数据的第二数据传输通道，以及建立用于在接入网设备与终端设备之间传输第二组播业务的业务数据的第二组播无线承载(multicast radio bearer，MRB)。
其中，数据传输通道可以是指通用分组无线服务(general packet radio service，GPRS)隧道协议用户面(GPRS tunnelling protocol user plane，GTP-U)隧道或者IP组播组隧道。
其中，该步骤S501可选。
S502：接入网设备向第二终端设备发送第二配置信息。第二终端设备接收第二配置信息。
其中，第二终端设备属于第二核心网设备，即第二终端设备通过无线接入网接入到第二核心网设备。第二配置信息可以通过一个或多个RRC消息发送。
第二配置信息可以包括第二组播业务对应的MRB的配置信息，组播无线承载可以是增强型的数据无线承载(data radio bearer，DRB)，也可以是新定义的MRB，其中，组播包括两种数据传输方式：点对多点方式和点对点方式，其中，点对多点方式时，对应的用户标识为G-RNTI；点对点方式时，对应的用户标识为C-RNTI，点对点方式时，第二配置信息可以不包括其对应的C-RNTI。
具体的，当接入网设备为第二终端设备配置包含点对多点的RLC实体，和点对点的RLC实体的分割形式的(split)MRB，第二配置信息可以包括第二用户标识(例如第二G-RNTI)、第二组播业务服务标识、第二组播业务会话标识、MRB标识(或者MRB标记)、PDCP配置、RLC配置、逻辑信道标识、安全配置(security config)等。可选地，还可以包括第二C-RNTI，第二C-RNTI用于在点对点时加扰业务数据的调度信息。
其中，第二用户标识用于加扰第一调度信息，第一调度信息用于调度第二组播业务的业务数据，例如第二用户标识可以为第二G-RNTI，第一调度信息可以为下行控制信息(downlink control information，DCI)。
如果接入网设备为第二终端设备配置包含点对多点的RLC实体的MRB，第二配置信息可以包括第二用户标识、第二组播业务的第二组播业务服务标识、第二组播业务会话的第二组播业务会话标识、MRB标识(或者MRB标记)、PDCP配置、RLC配置、逻辑信道标识、安全配置(security config)等。
如果接入网设备为第二终端设备配置包含点对点的RLC实体的MRB，第二配置信息可以包括第二组播业务服务标识、第二组播业务会话标识、MRB标识(或者MRB标记)、PDCP配置、RLC配置、逻辑信道标识、安全配置等。可选地，还可以包括第二用户标识，第二用户标识可以为第二C-RNTI。
一种可能的实现方式中，第二配置信息可以包括两个部分：无线承载配置信息元素(radio bearer config information element)和RLC承载配置信息元素(RLC-bearer config information element)。
其中，无线承载配置信息元素可以包括MRB标识(或者MRB标记)、PDCP配置以及安全配置，或者包括DRB标识、PDCP配置以及安全配置；RLC承载配置信息元素可以包括RLC配置以及第二用户标识。第二组播业务服务标识、第二组播业务会话标识可以位于无线承载配置信息元素，也可以位于RLC承载配置信息元素。
举例来说，无线承载配置信息元素可以如下所示：
Figure PCTCN2022105769-appb-000001
Figure PCTCN2022105769-appb-000002
其中，DRB-ToReleaseList中包括DRB标识，SecurityConfig表示安全配置。
如果接入网设备为第二终端设备配置MRB的RLC配置时，RLC承载配置信息元素可以如下所示：
Figure PCTCN2022105769-appb-000003
Figure PCTCN2022105769-appb-000004
其中，RLC-BearerConfig包括RLC承载配置。
本申请实施例中，为第二终端设备配置MRB时，可以通过对上面的无线承载配置信息元素和RLC承载配置信息元素进行修改，获得相应的配置信息。具体的，实现方式一，分别在上面示例的无线承载配置信息元素中增加MRB信息，即增加MRB添加或修改列表(mrb-ToAddModList)和MRB释放列表(mrb-ToReleaseList)，MRB添加或修改列表用于添加或修改MRB，MRB释放列表用于释放MRB。MRB添加或修改列表、以及MRB释放列表中包括MRB标识(mrb-Identity)；
在RLC承载配置信息元素中增加mrb-Identity，mrb-Identity用于指示于添加或修改的MRB的标识；可选地，如果接入网设备为第二终端设备配置包含点对多点的RLC实体的MRB时，在RLC承载配置信息元素中还可以增加g-RNTI，g-RNTI用于指示第二用户标识。
实现方式二，在无线承载配置信息元素的DRB-ToAddModList中增加mrb-Flag，其中，mrb-Flag用于指示该无线承载配置信息元素对应的DRB作为MRB；可选地，如果接入网设备为第二终端设备配置包含点对多点的RLC实体的MRB时，在RLC承载配置信息元素中增加g-RNTI，g-RNTI用于指示第二用户标识。
示例性的，对于接入网设备为第二终端设备配置包含点对多点的RLC实体，和点对点的RLC实体的分割形式的(split)MRB，实现方式一可以是，第二配置信息可以包括无线承载配置信息元素中MRB添加或修改列表包含第一MRB标识和MRB相关的PDCP配置信息；第一RLC承载配置信息元素中包含第一MRB标识，MRB相关的用于点对多点的RLC配置信息，以及第二用户标识,也就是g-RNTI；第二RLC承载配置信息元素中包含第一MRB标识，MRB相关的用于点对点的RLC配置信息，其中第一MRB标识用于关联无线承载配置信息元素和RLC承载配置信息元素；实现方式二可以是，第二配置信息可以包括无线承载配置信息元素中DRB-ToAddModList中包含mrb-Flag，第一DRB标识和PDCP配置信息；第一RLC承载配置信息元素中包含第一DRB标识，MRB相关的用于点对多点的RLC配置信息，以及第二用户标识,也就是g-RNTI；第二RLC承载配置信息元素中包含第一DRB标识，MRB相关的用于点对点的RLC配置信息，其中第一DRB标识用于关联无线承载配置信息元素和RLC承载配置信息元素。
第二配置信息可以包括第二用户标识(例如第二G-RNTI)、第二组播业务服务标识、第二组播业务会话标识、MRB标识(或者MRB标记)、PDCP配置、RLC配置、逻辑信道标识、安全配置(security config)等。可选地，还可以包括第二C-RNTI。基于本方法可以实现接入网设备为终端设备建立用于组播业务的无线承载，且可以配置多个RLC实体。
其中，该步骤S502可选。
S503：第一终端设备向第一核心网设备发送会话服务请求消息，第一核心网设备接收第一终端设备的会话服务请求消息。
第一终端设备属于第一核心网设备，即第一终端设备接入第一核心网设备对应的无线接入网。第一核心网设备可以为AMF。
会话服务请求消息可以包括第一组播业务会话标识，会话服务请求消息用于请求获取第一组播业务的业务数据。终端设备可以通过来自接入网设备的广播消息获取到第一组播业务会话标识。
其中，第一组播业务会话标识为第一组播业务在第一核心网设备中对应的会话标识，第一组播业务会话标识为第一核心网设备所属的核心网侧分配的，例如5G系统中，可以由SMF为第一组播业务分配第一组播业务会话标识。举例来说，第一组播业务会话标识可以为第一IP组播组地址或者第一TMGI。
本申请实施例中，在第一核心网设备所属的网络中，第一终端设备发送会话服务请求消息之前，接入网设备还没有为第一组播业务分配NG资源和空口资源，即接入网设备还没有与核心网侧建立用于传输第一组播业务的业务数据的数据传输通道，以及没有建立第一组播业务对应的MRB。
另外，会话服务请求消息可以为NAS消息，由第一终端设备通过接入网设备发送至第一核心网设备。在第一核心网设备所属的网络中，第一组播业务还对应一个第一组播业务服务标识，第一组播业务服务标识与第一组播业务会话标识存在映射关系。
其中，该步骤S503可选。
S504：第一核心网设备向接入网设备发送第一信息，接入网设备获取来自第一核心网设备的第一信息。
其中，第一信息用于请求将第一终端设备加入第一组播业务对应的组播业务会话。
为了描述方便，以下可以将第一组播业务对应的组播业务会话简称为第一组播业务会话，将第二组播业务对应的组播业务会话简称为第二组播业务会话。
第一信息可以通过PDU会话修改请求消息携带，第一信息可以包括第一组播业务对应的第一标识，第一组播业务的第一QoS流信息，第一组播业务会话标识以及第一组播业务服务标识。
本申请实施例中，第一标识可能存在多种实现方式，举例来说：实现方式一，第一标识可以为第一组播业务在第一核心网设备中对应的第一组播业务服务标识。
实现方式二，第一标识可以为第一组播业务在第一核心网设备中对应的第一组播业务会话标识。
在实现方式二中，第一组播业务会话标识为第一IP组播组地址时，第一标识可以为第一IP组播组地址；第一组播业务会话标识为第一TMGI时，第一标识可以为第一TMGI，或者第一标识可以为第一TMGI中的第一服务标识。
实现方式三，第一标识可以为第一组播业务在业务服务器中对应的标识，也可以为业务服务器分配的标识。业务服务器可以为每个组播业务分配一个标识，从而可以将业务服务器分配的标识作为第一标识。
S505：满足第一条件时，接入网设备将第一终端设备加入第二组播业务对应的组播业务会话。
其中，第一条件包括第一组播业务与第二组播业务为相同的组播业务，第二组播业务为第二核心网设备提供的组播业务。
接入网设备如何确定第一组播业务与第二组播业务是否为相同的组播业务，本申请实施例并不限定。一种实现方式中，如果第一组播业务对应的第一标识与第二组播业务对应的第二标识相匹配，则第一组播业务与第二组播业务为相同的组播业务。
其中，第一标识与第二标识相匹配，可以是指第一标识与第二标识相同，也可以是指第一标识与第二标识存在映射关系。
下面分别描述接入网设备如何根据第一标识和第二标识确定第一组播业务与第二组播业务是否相同。
第一种可能的实现方式：第一标识为第一组播业务在第一核心网设备中对应的第一组播业务服务标识，第二标识为第二组播业务在第二核心网设备中对应的第二组播业务服务标识。
在该实现方式中，可能存在以下情况：情况一，预先约定在不同PLMN(或不同网络)中为相同的组播业务分配相同的组播业务服务标识；情况二，可以预先建立组播业务与组播业务服务标识的映射关系。
具体的，情况一中，由于组播业务在不同PLMN中对应的组播业务服务标识可能不同，为此本申请实施例中，对于同一个组播业务，可以预先约定在不同PLMN中配置相同的组播业务服务标识，这样可以使得接入网设备能够在不同PLMN中唯一确定组播业务服务标识对应的组播业务。
第一核心网设备和第二核心网设备可以分别根据组播业务的相关信息，识别出在第一核心网设备所处的第一PLMN和第二核心网设备所处的第二PLMN中均存在的组播业务，在第一PLMN和第二PLMN中均存在的组播业务，对应相同的组播业务服务标识。其中，组播业务的相关信息可以包括但不限于业务服务器提供的信息，组播业务的端口信息等。
举例来说，在第一PLMN和第二PLMN中均存在的组播业务的组播业务服务标识可以如表1所示。
表1
Figure PCTCN2022105769-appb-000005
表1中，组播业务1存在于第一PLMN和第二PLMN，那么其在第一PLMN和第二PLMN中的组播业务服务标识均为标识1。其他情况以此类推，不再赘述。
接入网设备在获取到第一组播业务服务标识(即第一标识)时，确定第二核心网设备提供的第二组播业务对应的第二组播业务服务标识，与第一组播业务服务标识相同，则可以确定第一组播业务与第二组播业务为相同的组播业务。
可选地，可以预配置一个标识分配范围，标识分配范围包括多个标识，多个PLMN中均存在的组播业务的组播业务服务标识，可以位于该标识分配范围内。例如，标识分配范围可以为000010至0000FF。
可选地，接入网设备获取到第一组播业务服务标识(即第一标识)时，可以先确定第一标识是否位于标识分配范围内，如果第一标识位于标识分配范围内，再确定第一标识与第二标识是否匹配。如果第一标识不位于标识分配范围内，则可以确定不存在与第一标识匹配的标识。
情况二，接入网设备可以预先建立第一映射关系，第一映射关系包括不同运营商的PLMN中的组播业务与组播业务服务标识的映射关系。或者，也可以由第一核心网设备或第二核心网设备建立第一映射关系，再将第一映射关系发送至接入网设备。
由接入网设备建立第一映射关系时，接入网设备可以根据组播业务的相关信息，识别出每个组播业务在不同PLMN中的组播业务服务标识，从而可以将组播业务在不同PLMN中的组播业务服务标识进行保存，获得第一映射关系。
举例来说，在多个PLMN中均存在的组播业务的组播业务服务标识可以如表2所示。表2中，一个组播业务在一个PLMN中可能存在多个组播业务服务标识。
表2
Figure PCTCN2022105769-appb-000006
根据第一映射关系，接入网设备可以确定每个组播业务分别在不同PLMN中对应的组播业务服务标识。
接入网设备获取到第一组播业务服务标识(即第一标识)时，可以根据第一映射关系确定第一标识对应的第一组播业务，并根据第一映射关系确定第二标识对应的第二组播业务；如果第一组播业务与第二组播业务为相同的组播业务，则可以确定第一标识与第二标识相匹配。如果第一组播业务与第二组播业务为不同的组播业务，则可以确定第一标识与第二标识不匹配。
举例来说，结合表2，接入网设备从PLMN 1中的第一核心网设备获取到的第一标识为标识1-1，从PLMN 2中的第二核心网设备获取到的第二标识为标识1-3。接入网设备根据表2所示的第一映射关系，可以确定第一标识在PLMN 1中对应组播业务1，并确定第二标识在PLMN 2中也对应组播业务1，从而可以确定第一标识与第二标识对应相同的组播业务，即第一标识与第二标识相匹配。
再举例来说，结合表2，接入网设备从PLMN 1中的第一核心网设备获取到的第一标识为标识2-1，从PLMN 2中的第二核心网设备获取到的第二标识为标识1-3。接入网设备根据表2所示的第一映射关系，可以确定第一标识在PLMN 1中对应组播业务2，并确定第二标识在PLMN 2中对应组播业务1，从而可以确定第一标识与第二标识对应不同的组播业务，即第一标识与第二标识不匹配。
可选地，接入网设备在获取到第一标识时，可以先确定第一映射关系中是否包括第一标识，如果确定第一标识位于第一映射关系内，再根据第一映射关系确定第一标识与第二标识是否匹配。
如果确定第一标识不位于第一映射关系内，接入网设备则可以认为还没有为第一标识对应的第一组播业务在任何PLMN中建立会话。通过这种方法，可以提高会话建立效率。
第二种可能的实现方式：第一标识为第一组播业务在第一核心网设备中对应的第一组播业务会话标识，第二标识为第二组播业务在第二核心网设备中对应的第二组播业务会话标识。
和第一种可能的实现方式类似，在该实现方式中，可能存在以下情况：情况一，预先 约定在不同PLMN(或不同网络)中为相同的组播业务分配相同的组播业务会话标识；情况二，可以预先建立组播业务与组播业务会话标识的映射关系。
具体的，情况一中，对于同一个组播业务，可以预先约定在不同PLMN中配置相同的组播业务会话标识，这样可以使得接入网设备能够在不同PLMN中唯一确定组播业务会话标识对应的组播业务。
第一核心网设备和第二核心网设备可以分别根据组播业务的相关信息，识别出在第一核心网设备所处的第一PLMN和第二核心网设备所处的第二PLMN中均存在的组播业务，在第一PLMN和第二PLMN中均存在的组播业务，对应相同的组播业务会话标识。
接入网设备在获取到第一组播业务会话标识时，确定第二核心网设备提供的第二组播业务对应的第二组播业务会话标识，与第一组播业务会话标识相同，则可以确定第一组播业务与第二组播业务为相同的组播业务。
可选地，可以预配置一个标识分配范围，标识分配范围包括多个标识，多个PLMN中均存在的组播业务的组播业务会话标识，可以位于该标识分配范围内。例如，标识分配范围可以为000010至0000FF。
可选地，接入网设备获取到第一组播业务会话标识(即第一标识)时，可以先确定第一标识是否位于标识分配范围内，如果第一标识位于标识分配范围内，再确定第一标识与第二标识是否匹配。如果第一标识不位于标识分配范围内，则可以确定不存在与第一标识匹配的标识。
情况二，接入网设备可以预先建立第二映射关系，第二映射关系包括不同运营商的PLMN中的组播业务与组播业务会话标识的映射关系。或者，也可以由第一核心网设备或第二核心网设备建立第二映射关系，再将第二映射关系发送至接入网设备。
由接入网设备建立第二映射关系时，接入网设备可以根据组播业务的相关信息，识别出每个组播业务在不同PLMN中的组播业务会话标识，从而可以将组播业务在不同PLMN中的组播业务会话标识进行保存，获得第二映射关系。
接入网设备获取到第一组播业务会话标识(即第一标识)时，可以根据第二映射关系确定第一标识对应的第一组播业务，并根据第二映射关系确定第二标识对应的第二组播业务；如果第一组播业务与第二组播业务为相同的组播业务，则可以确定第一标识与第二标识相匹配。如果第一组播业务与第二组播业务为不同的组播业务，则可以确定第一标识与第二标识不匹配。
可选地，接入网设备在获取到第一标识时，可以先确定第二映射关系中是否包括第一标识，如果确定第一标识位于第二映射关系内，再根据第一映射关系确定第一标识与第二标识是否匹配。
如果确定第一标识不位于第二映射关系内，接入网设备则可以认为还没有为第一标识对应的第一组播业务在任何PLMN中建立会话。通过这种方法，可以提高会话建立效率。
同样的，当第一标识为服务标识或者TMGI或者IP组播组地址时，也可以采用上面的方法，在此不再赘述。
第三种可能的实现方式，第一标识可以为业务服务器分配的第一公共标识，第二标识可以为业务服务器分配的第二公共标识。为了描述方便，在第三种可能的实现方式中，将第一标识称为第一公共标识，第二标识称为第二公共标识。
业务服务器可以在不同PLMN中，为同一个组播业务分配相同的公共标识，即在不同 PLMN中，同一个组播业务的公共标识相同。
本申请实施例中，公共标识可以独立存在，也就是说公共标识可以位于一个独立的字段中携带。公共标识也可以位于组播业务会话标识或者组播业务服务标识中，即公共标识可以是组播业务会话标识或者组播业务服务标识的一部分。例如公共标识是TMGI的一部分时，TMGI可以包括PLMN标识、业务标识和公共标识。
在第三种可能的实现方式中，第一核心网设备在第一会话建立过程中，向接入网设备发送的信息包括第一PLMN的标识、第一组播业务会话标识和第一公共标识；第二核心网设备在第二会话建立过程中，向接入网设备发送的信息包括第二PLMN的标识、第二组播业务会话标识和第二公共标识。
接入网设备确定第一公共标识与第二公共标识相同，则可以确定第一标识与第二标识相匹配，即确定第二会话与第一会话对应相同的组播业务；接入网设备确定第一公共标识与第二公共标识不相同，则可以确定第一标识与第二标识不匹配，即确定第二会话与第一会话对应不同的组播业务。
结合前面的描述可知，接入网设备确定第一组播业务与第二组播业务为相同的组播业务，可以将第一终端设备加入第二组播业务对应的组播业务会话。进一步的，由于第一组播业务与第二组播业务为同一个组播业务，第二组播业务的业务数据，可以作为第一组播业务的业务数据，因此接入网设备可以不再从第一核心网设备所处的网络获取第一组播业务的业务数据，相应的，第一核心网设备所处的网络可以不再向接入网设备发送第一组播业务的业务数据。
本申请实施例中，由于接入网设备可以不获取第一组播业务的业务数据，那么接入网设备可以通过接入网设备与第二核心网设备所处的核心网侧之间的第二数据传输通道获取第一组播业务的业务数据。
而接入网设备与第一核心网设备所处的核心网侧之间，可以建立用于传输第一组播业务的业务数据的第一数据传输通道，也可以不建立第一数据传输通道。其中，数据传输通道可以是指GTP-U隧道或者IP组播组隧道。
一种可能的实现方式中，当不建立第一数据传输通道时，接入网设备可以向第一核心网设备发送第二信息；其中，第二信息用于指示不与第一核心网设备之间建立第一数据传输通道。
另一种可能的实现方式中，接入网设备可以向第一核心网设备发送通道建立消息，通道建立消息用于指示建立第一数据传输通道，并指示第一核心网设备暂停传输第一组播业务的业务数据或者指示第一核心网设备暂停传输第一组播业务的业务数据。
另一种可能的实现方式中，在第一数据传输通道建立完成，接入网设备还可以向第一核心网设备发送第三信息，第三信息用于指示第一数据传输通道为非激活态，或者第三信息用于指示暂停通过第一数据传输通道传输第一组播业务的业务数据，或者第三信息可以用于指示第一核心网设备暂停传输第一组播业务的业务数据。第一数据传输通道的建立过程，本申请并不限定，在此不再赘述。
同样的，在接入网设备与第一终端设备之间，接入网设备可以不再分配用于传输第一组播业务的业务数据的空口资源。具体的，在第一核心网设备所处的网络中，接入网设备可以不再为第一组播业务配置第一MRB，第一MRB用于在接入网设备与第一终端设备之间传输第一组播业务的业务数据。
接入网设备可以复用第二MRB，通过第二MRB向第一终端设备传输第一组播业务的业务数据，其中，第二MRB用于在空口承载第二组播业务的业务数据。也就是说，第二组播无线承载除了用于与第二终端设备之间传输第二组播业务的业务数据，第二MRB还用于与第一终端设备之间传输第二组播业务(即第一组播业务)的业务数据。
如果接入网设备复用第二MRB向第一终端设备传输第一组播业务的业务数据，接入网设备可以向第一终端设备发送第一配置信息。
一种可能的实现方式中，第一配置信息包括的内容可以和第二配置信息包括的内容全部相同，也就是说第一配置信息包括第二MRB的配置信息。
另一种可能的实现方式中，第一配置信息包括的内容可以和第二配置信息包括的内容部分相同，也就是说第一配置信息包括第二MRB的配置信息的一部分。
例如，第一配置信息包括第一用户标识，该第一用户标识和第二配置信息包括的第二用户标识相同，也就是说第一配置信息包括第二用户标识。
再例如，第一配置信息包括的安全配置和第二配置信息包括的安全配置相同，其中安全配置包括安全算法及秘钥。
再例如，第一配置信息包括的MRB标识、PDCP配置、RLC配置，和第二配置信息包括的MRB标识、PDCP配置、RLC配置相同。
再例如，第一配置消息包括的无线承载配置信息元素与第二配置消息包括的无线承载配置信息元素相同。
再例如，第一配置消息包括的RLC承载配置信息元素和第二配置消息包括的RLC承载配置信息元素相同。
再例如，第一配置消息包括的用于点对多点传输的RLC承载配置信息元素和第二配置消息包括的点对多点传输的RLC承载配置信息元素相同。
其中，第一用户标识于加扰第一调度信息，第一调度信息用于调度第二组播业务的业务数据；第一用户标识可以为第一G-RNTI。由于第一组播业务和第二组播业务相同，这里的第一调度信息也可以认为用于调度第一组播业务的业务数据。
当接入网设备为第一终端设备配置用于点对点传输方式的RLC实体时，接入网设备可以向第一终端设备发送的第一配置信息可以不包括第一G-RNTI，此时的第一配置信息可以包括第一C-RNTI，该第一C-RNTI也可以通过其他方式获得，本申请实施例对此并不限定。第一C-RNTI用于在第二组播业务的业务数据采用点对点方式传输时，加扰该业务数据的调度信息。
当接入网设备为第一终端设备配置包含用于点对点传输方式的RLC实体的MRB时，接入网设备发送的第一配置信息中，除了RLC承载配置和第二配置信息中的RLC承载配置不一样之外，其他信息可以和第二配置信息中的信息相同。也就是说，第一配置信息中的第二组播业务服务标识、第二组播业务会话标识、PDCP配置、安全配置中的至少一项，可以和第二配置信息中的相应信息相同。
结合前面的描述，如图6所示，为本申请实施例提供的一种业务数据传输示意图。接入网设备将第一终端设备加入第二组播业务对应的组播业务会话之后，业务服务器虽然可以向第一核心网设备和第二核心网设备传输第二组播业务(此时的第二组播业务就是第一组播业务)的业务数据，但是第一核心网设备不再向接入网设备传输第一组播业务的业务数据。接入网设备从第二核心网设备接收到第二组播业务的业务数据时，可以通过组播方 式向第一终端设备和第二终端设备传输该业务数据。虽然第一终端设备和第二终端设备不属于同一个网络，或者不属于同一个核心网设备，但是接入网设备只需要在两个网络中传输一次业务数据，可以节省NG资源和空口资源，提高数据传输效率，降低资源开销。
另外，当接入网设备向第一终端设备传输业务数据时，第一终端设备可以监听物理下行控制信道(physical downlink control channel，PDCCH)，并用第一用户标识(第一G-RNTI或第一C-RNTI)解扰PDCCH的循环冗余码(cyclic redundancy code，CRC)，解扰成功后接收业务数据，具体过程不再赘述。
通过上面的方法可知，接入网设备确定第一组播业务与第二组播业务为同一个组播业务时，接入网设备可以采用已经建立的第二组播业务的相关资源，同时向两个网络中的终端设备提供第二组播业务的业务数据，实现对来自两个核心网的相同组播业务共用相同的NG资源和空口资源，节省了资源，提高数据传输效率。
进一步的，本申请实施例中，如果由第二核心网设备所处的网络停止传输第二组播业务的业务数据，接入网设备则可以接收来自第二核心网设备的第一释放信息，第一释放信息用于指示释放第二数据传输通道，可选的，第一释放信息还可以用于指示释放第二MRB。
一种可能的实现方式中，如果接入网设备与第一核心网设备所处的核心网之间没有建立第一数据传输通道，接入网设备则可以向第一核心网设备发送第五信息，第五信息用于触发建立第一数据传输通道。
一种可能的实现方式中，如果接入网设备与第一核心网设备所处的核心网之间已经建立第一数据传输通道，接入网设备则可以向第一核心网设备发送第六信息，第六信息用于激活第一数据传输通道，或者第六信息用于指示通过第一数据传输通道传输第一组播业务的业务数据。
第一释放信息中可以包括释放原因，释放原因可以包括以下任一原因：
原因1：核心网侧在指定时长内无第二组播业务的业务数据到达；
原因2：业务服务器停止传输第二组播业务的业务数据；
原因3：请求将第二组播业务由组播方式传输转换为单播方式传输；
原因4：请求将所述第二组播业务转换为单播业务；
原因5：第二核心网设备对应的网络中没有接收第二组播业务的业务数据的终端设备；
原因6：第二核心网设备对应的网络中，接收第二组播业务的业务数据的终端设备的数量小于或等于阈值。
如果释放原因为原因1或原因2，接入网设备可以确定无法获取到第二组播业务的业务数据，也无法获取到第一组播业务的业务数据，接入网设备可以指示终端设备释放第二MRB。
具体如何释放第二MRB，可能存在多种实现方式，一种实现方式，接入网设备向终端设备发送配置消息包含mrb-ToReleaseList，其中mrb-ToReleaseList包含MRB标识。
另一种实现方式，接入网设备向终端设备发送配置消息包含drb-ToReleaseList，其中drb-ToReleaseList包含MRB关联的DRB标识。
如果释放原因为原因3或原因4或原因5或原因6，接入网设备可以确定需要通过第一核心网设备所处的网络获取第一组播业务的业务数据，从而发送第五信息或第六信息。
进一步的，如果接入网设备确定需要通过第一核心网设备所处的网络获取第一组播业务的业务数据，接入网设备还可以根据第一QoS流信息建立第一组播业务对应的第一MRB， 或者，接入网设备还可以根据第一QoS流信息更新第二MRB，更新后的第二MRB用于与第一终端设备之间传输第一组播业务的业务数据，为了描述方便，更新后的第二MRB可以称为第一MRB。
其中，根据第一QoS流信息建立第一MRB的具体过程，本申请实施例并不限定，在此不再赘述。更新第二MRB时，可以将第二MRB对应的安全配置进行更新，第二MRB的其他信息可以不更新，例如第二MRB的MRB标识、PDCP配置、第二用户标识以及RLC配置等，都可以不更新。
一种实现方式中，接入网设备可以向第一终端设备发送第三配置信息，第三配置信息包括第一MRB的配置信息，例如可以包括第一MRB对应的以下至少一项信息：第三用户标识，MRB标识、PDCP配置、RLC配置以及安全配置等。其中，第三用户标识用于加扰第二调度信息，第二调度信息用于调度在第一MRB中传输的第一组播业务的业务数据。
一种可能的实现方式，接入网设备向第一终端设备发送的第三配置信息中包含更新的securityConfig，此实现方式用于更新MRB的安全配置。
另一种可能的实现方式，接入网设备向第一终端设备发送的第三配置信息中RLC承载配置信息元素包含更新后的第三用户标识，也就是g-RNTI，此实现方式用于更新第三用户标识。
另外，如果接入网设备是CU-DU分离架构，第三配置信息需要通过UE上下文建立请求(UE CONTEXT SETUP REQUEST)或UE上下文修改请求(UE CONTEXT MODIFICATION REQUEST)从CU发送给DU。
为了保证业务数据的连续性，接入网设备还可以指示核心网侧起始传输的数据包的包号。一种可能的实现方式中，接入网设备可以向第一核心网设备发送第一包号，第一包号为向第一终端设备发送的最后一个属于第一组播业务的数据包的包号，或者，第一包号为接入网设备缓存的至少一个数据包对应的至少一个包号中最大的包号，至少一个数据包为待发送至第一终端设备、且属于第一组播业务的数据包。其中，包号可以是GTP-U序列号(serial number，SN)或用户数据报协议(user datagram protocol，UDP)/IP数据包序列号。
第一核心网设备可以根据第一包号确定向第一终端设备发送的起始数据包，例如将第一包号对于的数据包作为向第一终端设备发送的起始数据包，或者将第一包号对于的数据包之后的第一个数据包作为向第一终端设备发送的起始数据包。
举例来说，如图7所示，业务服务器发送的数据包的包号依次为1、2、3、4、5、6；第一核心网设备接收到的数据包的包号依次为1、2、3、4、5；第二核心网设备接收到的数据包的包号依次为1、2、3、4、5；接入网设备从第二核心网设备接收到的数据包的包号依次为1、2、3、4，已经发送给终端设备的数据包的包号为1，还未发送至终端设备，但缓存的数据包的包号依次为2、3、4。
第二核心网设备停止传输数据包时，接入网设备可以将包号1(即作为第一包号)发送至第二核心网设备，第二核心网设备从包号1或包号2起始，继续向接入网设备发送数据包；或者，接入网设备可以将包号4(即作为第一包号)发送至第二核心网设备，第二核心网设备从包号4或包号5起始，继续向接入网设备发送数据包。另一种可能的实现方式中，接入网设备可以向第一核心网设备指示N，N为大于0的整数。第一核心网设备接收到第五信息或第六信息或第一数据传输通道建立完成时，从业务服务器获取到的数据包为第三数据包，第三数据包属于第一组播业务，第一核心网设备获取到N时，可以将位于 第三数据包之前，与第三数据包之间间隔N个数据包的第二数据包作为起始数据包，第一核心网设备向第一终端设备发送的起始数据包为第二数据包。
例如，N等于10，第三数据包的包号为x，那么可以将包号为x-10的数据包作为起始数据包。其中，N也可以是由第一核心网设备自主确定的。
另一种可能的实现方式中，第一核心网设备将第三数据包之前，与第三数据包之间对应的时间间隔为预设时长的第二数据包作为起始数据包，第一核心网设备向第一终端设备发送的起始数据包为第二数据包。
例如，第三数据包为y，预设时长为T，那么可以将y之前、且与y之间的时间间隔为T的数据包作为起始数据包。
预设时长可以为接入网设备配置的，或者预设时长为第一核心网设备确定的；预设时长也可以根据第一时延和第二时延确定，第一时延为接入网设备与第一核心网设备之间的传输时延，第二时延为接入网设备与第二核心网设备之间的传输时延。
举例来说，预设时延可以满足以下形式：
T＝α×delay1+β×delay2+Α；
其中T为预设时长，α为大于0的数，β为大于0的数，delay1为第一时延，delay2为第二时延，A为预设取值。
其中，第一时延和第二时延可以为接入网设备向第一核心网设备指示的；或者第二时延可以为接入网设备向第一核心网设备指示的，第一时延是在第一核心网设备通过接收来自接入网设备的数据包中携带的时间信息计算得出，该时间信息指示出该数据包的发送时间。
为了实现上述本申请实施例提供的方法中的各功能，接入网设备、终端设备或上述通信装置可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
与上述构思相同，如图8所示，本申请实施例还提供一种通信装置800。所述通信装置800可以是图1中的接入网设备，用于实现上述方法实施例中对于接入网设备的方法。所述通信装置也可以是图1中的核心网设备，用于实现上述方法实施例中对应于核心网设备的方法。具体的功能可以参见上述方法实施例中的说明。
具体的，通信装置800可以包括：处理单元801和通信单元802。本申请实施例中，通信单元也可以称为收发单元，可以包括发送单元和/或接收单元，分别用于执行上文方法实施例中接入网设备或终端设备发送和接收的步骤。以下，结合图8至图9详细说明本申请实施例提供的通信装置。
一些可能的实施方式中，上述方法实施例中接入网设备的行为和功能可以通过通信装置800来实现，例如实现图5的实施例中接入网设备执行的方法。例如通信装置800可以为接入网设备，也可以为应用于接入网设备中的部件(例如芯片或者电路)，也可以是接入网设备中的芯片或芯片组或芯片中用于执行相关方法功能的一部分。通信单元802可以 用于执行图5所示的实施例中由接入网设备所执行的接收或发送操作，处理单元801可以用于执行如图5所示的实施例中由接入网设备所执行的除了收发操作之外的操作。
在一种可能的设计中，通信单元，用于获取来自第一核心网设备的第一信息，第一信息用于请求将第一终端设备加入第一组播业务对应的组播业务会话；
处理单元，用于满足第一条件时，将第一终端设备加入第二组播业务对应的组播业务会话，其中，第一条件包括第一组播业务与第二组播业务为相同的组播业务，第二组播业务为第二核心网设备提供的。
在一种可能的设计中，通信单元还用于：向第一核心网设备发送第二信息；其中，第二信息用于指示不与第一核心网设备之间建立第一数据传输通道，第一数据传输通道用于传输第一组播业务的业务数据。
在一种可能的设计中，通信单元还用于：向第一核心网设备发送第三信息，第三信息用于指示与第一核心网设备之间建立的第一数据传输通道为非激活态，第一数据传输通道用于传输第一组播业务的业务数据。
在一种可能的设计中，通信单元还用于：向第一终端设备发送第一用户标识，第一用户标识用于加扰第一调度信息，第一调度信息用于调度第二组播业务的业务数据；
第一用户标识和第二用户标识相同，第二用户标识为向第二终端设备发送的用户标识，第二终端设备属于第二核心网设备。
在一种可能的设计中，通信单元还用于：向第一终端设备发送第一配置信息，第一配置信包括第二组播无线承载的配置信息，第二组播无线承载用于与第二终端设备之间传输第二组播业务的业务数据，第二组播无线承载还用于与第一终端设备之间传输第二组播业务的业务数据。
在一种可能的设计中，第一信息包括第一组播业务对应的第一标识；第一条件包括第一组播业务与第二组播业务为相同的组播业务，包括：第一标识与第二组播业务对应的第二标识相匹配，则第一组播业务与第二组播业务为相同的组播业务。
在一种可能的设计中，第一标识为第一组播业务在第一核心网设备中对应的第一组播业务服务标识；或者，第一标识为第一组播业务在第一核心网设备中对应的第一组播业务会话标识；或者，第一标识为第一组播业务在所述第一核心网设备中对应的第一互联网协议IP组播组地址或临时移动组标识；或者，所述第一标识为所述第一组播业务在业务服务器中对应的标识或者业务服务器为第一组播业务分配的其他标识。
在一种可能的设计中，通信单元还用于：接收来自第二核心网设备的第一释放信息，第一释放信息用于指示释放第二数据传输通道，其中，第二数据传输通道用于传输第二组播业务的业务数据；向第一核心网设备发送第五信息或第六信息；第五信息用于触发建立第一数据传输通道，第六信息用于激活第一数据传输通道。
在一种可能的设计中，第一释放信息包括释放原因；向第一核心网设备发送第五信息或第六信息之前，处理单元还用于：确定释放原因为以下任一种：请求将第二组播业务由组播方式传输转换为单播方式传输；请求将第二组播业务转换为单播业务；第二核心网设备对应的网络中没有接收第二组播业务的业务数据的终端设备；第二核心网设备对应的网络中，接收第二组播业务的业务数据的终端设备的数量小于或等于阈值。
在一种可能的设计中，处理单元还用于：根据第一服务质量流信息建立第一组播业务对应的第一组播无线承载；或者，根据第一服务质量流信息更新第二组播无线承载；第一 组播无线承载用于与第一终端设备之间传输第一组播业务的业务数据，第一服务质量流信息来自第一核心网设备；第二组播无线承载用于与第二终端设备之间传输第二组播业务的业务数据，更新后的第二组播无线承载用于与第一终端设备之间传输第一组播业务的业务数据。
在一种可能的设计中，通信单元还用于：向第一终端设备发送第三配置信息，第三配置信息包括第三用户标识，第三用户标识用于加扰第二调度信息，第二调度信息用于调度第一组播业务的业务数据。
在一种可能的设计中，第三配置信息还包括第一组播无线承载的配置信息。
在一种可能的设计中，通信单元还用于：向第一核心网设备发送第一包号，第一包号为向第一终端设备发送的最后一个属于第一组播业务的数据包的包号，或者，第一包号为缓存的至少一个数据包对应的至少一个包号中最大的包号，至少一个数据包为待发送至第一终端设备、且属于第一组播业务的数据包。
在一种可能的设计中，通信单元还用于：接收来自第一核心网设备的属于第一组播业务的数据包；其中，接收到的数据包中的起始数据包为第二数据包，第二数据包与第三数据包之间间隔N个数据包，第三数据包为第一核心网设备接收到第五信息或第六信息时，从业务服务器获取到的数据包；N为大于0的整数；或者，第二数据包与第三数据包之间对应的时间间隔预设时长。
在一种可能的设计中，预设时长为接入网设备配置的，或者预设时长为第一核心网设备确定的，或者预设时长根据第一时延和第二时延确定，第一时延为接入网设备与第一核心网设备之间的传输时延，第二时延为接入网设备与第二核心网设备之间的传输时延。
在一种可能的实现方式中，通信单元，用于向接入网设备发送第一信息，第一信息用于请求将第一终端设备加入第一组播业务对应的组播业务会话；第一终端设备加入第二组播业务对应的组播业务会话的情况下，接收来自接入网设备的第二信息或第三信息；其中，第一组播业务与第二组播业务为相同的组播业务，第二组播业务为第二核心网设备提供的；第二信息用于指示不与第一核心网设备之间建立第一数据传输通道，第一数据传输通道用于传输第一组播业务的业务数据；第三信息用于指示与第一核心网设备之间建立的第一数据传输通道为非激活态，第一数据传输通道用于传输第一组播业务的业务数据。
在一种可能的设计中，通信单元还用于：接收来自接入网设备的第五信息或第六信息；第五信息用于触发建立第一数据传输通道，第六信息用于激活第一数据传输通道。
在一种可能的设计中，通信单元还用于：接收来自接入网设备的第一包号，第一包号为接入网设备向第一终端设备发送的最后一个属于第一组播业务的数据包的包号，或者，第一包号为接入网设备缓存的至少一个数据包对应的至少一个包号中最大的包号，至少一个数据包为待发送至第一终端设备、且属于第一组播业务的数据包；将第一包号对应的数据包作为向第一终端设备发送的起始数据包。
在一种可能的设计中，通信单元还用于：向接入网设备发送属于第一组播业务的数据包；其中，数据包中的起始数据包为第二数据包，第二数据包与第三数据包之间间隔N个数据包，第三数据包为第一核心网设备接收到第五信息或第六信息时，从业务服务器获取到的数据包；N为大于0的整数；或者，第二数据包与第三数据包之间对应的时间间隔预设时长。
在一种可能的设计中，预设时长为接入网设备配置的，或者预设时长为第一核心网设 备确定的，或者预设时长根据第一时延和第二时延确定，第一时延为接入网设备与第一核心网设备之间的传输时延，第二时延为接入网设备与第二核心网设备之间的传输时延。
以上只是示例，处理单元801和通信单元802还可以执行其他功能，更详细的描述可以参考图5所示的方法实施例中相关描述，这里不加赘述。
如图9所示为本申请实施例提供的通信装置900，图9所示的通信装置可以为图8所示的通信装置的一种硬件电路的实现方式。该通信装置可适用于前面所示出的流程图中，执行上述方法实施例中终端设备或者接入网设备的功能。为了便于说明，图9仅示出了该通信装置的主要部件。
如图9所示，通信装置900包括处理器910和接口电路920。处理器910和接口电路920之间相互耦合。可以理解的是，接口电路920可以为收发器或输入输出接口。可选的，通信装置900还可以包括存储器930，用于存储处理器910执行的指令或存储处理器910运行指令所需要的输入数据或存储处理器910运行指令后产生的数据。
当通信装置900用于实现图5所示的方法时，处理器910用于实现上述处理单元801的功能，接口电路920用于实现上述通信单元802的功能。
当上述通信装置为应用于终端设备的芯片时，该终端设备芯片实现上述方法实施例中终端设备的功能。该终端设备芯片从终端设备中的其它模块(如射频模块或天线)接收信息，该信息是接入网设备发送给终端设备的；或者，该终端设备芯片向终端设备中的其它模块(如射频模块或天线)发送信息，该信息是终端设备发送给接入网设备的。
当上述通信装置为应用于接入网设备的芯片时，该接入网设备芯片实现上述方法实施例中接入网设备的功能。该接入网设备芯片从接入网设备中的其它模块(如射频模块或天线)接收信息，该信息是终端设备发送给接入网设备的；或者，该接入网设备芯片向接入网设备中的其它模块(如射频模块或天线)发送信息，该信息是接入网设备发送给终端设备的。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中存储器可以是随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于接入网设备或终端设备中。处理器和存储介质也可以作为分立组件存在于接入网设备或终端设备中。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形 式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (26)

  1. 一种通信方法，其特征在于，应用于接入网设备，包括：
    获取来自第一核心网设备的第一信息，所述第一信息用于请求将第一终端设备加入第一组播业务对应的组播业务会话；
    满足第一条件时，将所述第一终端设备加入第二组播业务对应的组播业务会话，其中，所述第一条件包括所述第一组播业务与所述第二组播业务为相同的组播业务，所述第二组播业务为第二核心网设备提供的。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    向所述第一核心网设备发送第二信息；
    其中，所述第二信息用于指示不与所述第一核心网设备之间建立第一数据传输通道，所述第一数据传输通道用于传输所述第一组播业务的业务数据。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    向所述第一核心网设备发送第三信息，所述第三信息用于指示与所述第一核心网设备之间建立的第一数据传输通道为非激活态，所述第一数据传输通道用于传输所述第一组播业务的业务数据。
  4. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括：
    向所述第一终端设备发送第一用户标识，所述第一用户标识用于加扰第一调度信息，所述第一调度信息用于调度所述第二组播业务的业务数据；
    所述第一用户标识和第二用户标识相同，所述第二用户标识为向第二终端设备发送的用户标识，所述第二终端设备属于所述第二核心网设备。
  5. 根据权利要求1至3任一所述的方法，其特征在于，所述方法还包括：
    向所述第一终端设备发送第一配置信息，所述第一配置信包括第二组播无线承载的配置信息，所述第二组播无线承载用于与所述第二终端设备之间传输所述第二组播业务的业务数据，所述第二组播无线承载还用于与所述第一终端设备之间传输所述第二组播业务的业务数据。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述第一信息包括所述第一组播业务对应的第一标识；
    所述第一条件包括所述第一组播业务与所述第二组播业务为相同的组播业务，包括：
    所述第一标识与所述第二组播业务对应的第二标识相匹配。
  7. 根据权利要求6所述的方法，其特征在于，所述第一标识为所述第一组播业务在所述第一核心网设备中对应的第一组播业务服务标识；
    或者，所述第一标识为所述第一组播业务在所述第一核心网设备中对应的第一组播业务会话标识；
    或者，所述第一标识为所述第一组播业务在所述第一核心网设备中对应的第一互联网协议IP组播组地址或临时移动组标识；
    或者，所述第一标识为所述第一组播业务在业务服务器中对应的标识或者业务服务器为第一组播业务分配的其他标识。
  8. 根据权利要求2或3所述的方法，其特征在于，所述方法还包括：
    接收来自所述第二核心网设备的第一释放信息，所述第一释放信息用于指示释放第二 数据传输通道，其中，所述第二数据传输通道用于传输所述第二组播业务的业务数据；
    向所述第一核心网设备发送第五信息或第六信息；
    所述第五信息用于触发建立所述第一数据传输通道，所述第六信息用于激活所述第一数据传输通道。
  9. 根据权利要求8所述的方法，其特征在于，所述第一释放信息包括释放原因；
    其中，所述释放原因为以下任一种：
    请求将所述第二组播业务由组播方式传输转换为单播方式传输；
    请求将所述第二组播业务转换为单播业务；
    所述第二核心网设备对应的网络中没有接收所述第二组播业务的业务数据的终端设备；
    所述第二核心网设备对应的网络中，接收所述第二组播业务的业务数据的终端设备的数量小于或等于阈值。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    根据第一服务质量流信息建立所述第一组播业务对应的第一组播无线承载；
    或者，根据第一服务质量流信息更新所述第二组播无线承载；
    所述第一组播无线承载用于与所述第一终端设备之间传输所述第一组播业务的业务数据，所述第一服务质量流信息来自所述第一核心网设备；所述第二组播无线承载用于与所述第二终端设备之间传输所述第二组播业务的业务数据，更新后的所述第二组播无线承载用于与所述第一终端设备之间传输所述第一组播业务的业务数据。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    向所述第一终端设备发送第三配置信息，所述第三配置信息包括第三用户标识，所述第三用户标识用于加扰第二调度信息，所述第二调度信息用于调度所述第一组播业务的业务数据。
  12. 根据权利要求11所述的方法，其特征在于，所述第三配置信息还包括所述第一组播无线承载的配置信息。
  13. 根据权利要求8至12任一所述的方法，其特征在于，所述方法还包括：
    向所述第一核心网设备发送第一包号，所述第一包号为向所述第一终端设备发送的最后一个属于所述第一组播业务的数据包的包号，或者，所述第一包号为缓存的至少一个数据包对应的至少一个包号中最大的包号，所述至少一个数据包为待发送至所述第一终端设备、且属于所述第一组播业务的数据包。
  14. 根据权利要求8至12任一所述的方法，其特征在于，所述方法还包括：
    接收来自所述第一核心网设备的属于所述第一组播业务的数据包；
    其中，接收到的数据包中的起始数据包为第二数据包，所述第二数据包与第三数据包之间间隔N个数据包，所述第三数据包为所述第一核心网设备接收到所述第五信息或所述第六信息时，从业务服务器获取到的数据包；N为大于0的整数；
    或者，所述第二数据包与第三数据包之间对应的时间间隔预设时长。
  15. 根据权利要求14所述的方法，其特征在于，所述预设时长为所述接入网设备配置的，或者所述预设时长为所述第一核心网设备确定的，或者所述预设时长根据第一时延和第二时延确定，所述第一时延为所述接入网设备与所述第一核心网设备之间的传输时延，所述第二时延为所述接入网设备与所述第二核心网设备之间的传输时延。
  16. 一种通信方法，其特征在于，应用于第一核心网设备，包括：
    向接入网设备发送第一信息，所述第一信息用于请求将第一终端设备加入第一组播业务对应的组播业务会话；
    所述第一终端设备加入第二组播业务对应的组播业务会话的情况下，接收来自所述接入网设备的第二信息或第三信息；
    其中，所述第一组播业务与所述第二组播业务为相同的组播业务，所述第二组播业务为第二核心网设备提供的；所述第二信息用于指示不与所述第一核心网设备之间建立第一数据传输通道，所述第一数据传输通道用于传输所述第一组播业务的业务数据；所述第三信息用于指示与所述第一核心网设备之间建立的第一数据传输通道为非激活态，所述第一数据传输通道用于传输所述第一组播业务的业务数据。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的第五信息或第六信息；
    所述第五信息用于触发建立所述第一数据传输通道，所述第六信息用于激活所述第一数据传输通道。
  18. 根据权利要求16或17所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的第一包号，所述第一包号为所述接入网设备向所述第一终端设备发送的最后一个属于所述第一组播业务的数据包的包号，或者，所述第一包号为所述接入网设备缓存的至少一个数据包对应的至少一个包号中最大的包号，所述至少一个数据包为待发送至所述第一终端设备、且属于所述第一组播业务的数据包；
    将所述第一包号对应的数据包作为向所述第一终端设备发送的起始数据包。
  19. 根据权利要求16或17所述的方法，其特征在于，所述方法还包括：
    向所述接入网设备发送属于所述第一组播业务的数据包；
    其中，所述数据包中的起始数据包为第二数据包，所述第二数据包与第三数据包之间间隔N个数据包，所述第三数据包为所述第一核心网设备接收到所述第五信息或所述第六信息时，从业务服务器获取到的数据包；N为大于0的整数；
    或者，所述第二数据包与第三数据包之间对应的时间间隔预设时长。
  20. 根据权利要求19所述的方法，其特征在于，所述预设时长为所述接入网设备配置的，或者所述预设时长为所述第一核心网设备确定的，或者所述预设时长根据第一时延和第二时延确定，所述第一时延为所述接入网设备与所述第一核心网设备之间的传输时延，所述第二时延为所述接入网设备与所述第二核心网设备之间的传输时延。
  21. 一种通信装置，其特征在于，用于实现权利要求1至15中任一项所述的方法。
  22. 一种通信装置，其特征在于，用于实现权利要求16至20中任一项所述的方法。
  23. 一种通信装置，其特征在于，包括处理器，所述处理器和存储器耦合；
    所述处理器，用于执行所述存储器中存储的计算机程序或指令，使得所述通信装置实现权利要求1至15中任意一项所述的方法。
  24. 一种通信装置，其特征在于，包括处理器，所述处理器和存储器耦合；
    所述处理器，用于执行所述存储器中存储的计算机程序或指令，使得所述通信装置实现权利要求16至20中任意一项所述的方法。
  25. 一种计算机可读存储介质，其特征在于，存储有计算机程序或指令，当所述计算机程序或指令在计算机上运行时，使得所述计算机实现如权利要求1至15中任意一项所述 的方法，或者使得所述计算机实现如权利要求16至20中任意一项所述的方法。
  26. 一种计算机程序产品，其特征在于，包括指令，当所述指令在计算机上运行时，使得所述计算机实现如权利要求1至15中任意一项所述的方法，或者使得所述计算机实现如权利要求16至20中任意一项所述的方法。
PCT/CN2022/105769 2021-08-05 2022-07-14 一种通信方法及装置 WO2023011137A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP22851851.0A EP4369745A1 (en) 2021-08-05 2022-07-14 Communication method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110897090.9 2021-08-05
CN202110897090.9A CN115706930A (zh) 2021-08-05 2021-08-05 一种通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/432,194 Continuation US20240188104A1 (en) 2021-08-05 2024-02-05 Communication method and apparatus

Publications (1)

Publication Number Publication Date
WO2023011137A1 true WO2023011137A1 (zh) 2023-02-09

Family

ID=85155110

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/105769 WO2023011137A1 (zh) 2021-08-05 2022-07-14 一种通信方法及装置

Country Status (3)

Country Link
EP (1) EP4369745A1 (zh)
CN (1) CN115706930A (zh)
WO (1) WO2023011137A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210105606A1 (en) * 2019-10-04 2021-04-08 At&T Intellectual Property I, L.P. Facilitation of multiple subscriber identity module coordination for 5g or other next generation network
CN112788542A (zh) * 2019-11-07 2021-05-11 华为技术有限公司 通信方法、设备及系统

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210105606A1 (en) * 2019-10-04 2021-04-08 At&T Intellectual Property I, L.P. Facilitation of multiple subscriber identity module coordination for 5g or other next generation network
CN112788542A (zh) * 2019-11-07 2021-05-11 华为技术有限公司 通信方法、设备及系统

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Leftover issue for MBS session activation and deactivation", 3GPP DRAFT; S2-2107475, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. E (e-meeting); 20211018 - 20211022, 11 October 2021 (2021-10-11), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052062349 *
HUAWEI, HISILICON: "NR multicast broadcast enhancements", 3GPP DRAFT; RWS-210446, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. TSG RAN, no. Electronic Meeting; 20210628 - 20210702, 7 June 2021 (2021-06-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP052025998 *
HUAWEI: "New SID: Architectural enhancements for 5G multicast-broadcast services Phase 2", 3GPP DRAFT; S2-2106086, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20210816 - 20210827, 10 August 2021 (2021-08-10), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052053822 *
RAN3 CHAIRMAN: "List of E-mail Discussions", 3GPP TSG-RAN WG3 #112-E DRAFT R3-211559, 3GPP, 27 May 2021 (2021-05-27), XP009544400 *

Also Published As

Publication number Publication date
CN115706930A (zh) 2023-02-17
EP4369745A1 (en) 2024-05-15

Similar Documents

Publication Publication Date Title
US11700509B2 (en) Communication system, communication method, and apparatus thereof
US11546811B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
EP3965440A1 (en) Sidelink communication method and apparatus, and storage medium
EP3509371B1 (en) Method and device for transmitting message
WO2021077434A1 (zh) 一种通信方法及装置
US20200221538A1 (en) Data transmission method, terminal device, and network device
WO2021164564A1 (zh) 传输组播业务的方法和装置
US11395256B2 (en) Communication method, device, and system
WO2011018037A1 (zh) 一种配置mbms控制信息的方法、设备和系统
WO2015018232A1 (zh) 设备到设备连接管理方法、装置及基站
WO2021097858A1 (zh) 一种通信方法及装置
US20230067900A1 (en) Communication method and apparatus, and storage medium
WO2023011137A1 (zh) 一种通信方法及装置
US11843997B2 (en) Network slicing framework for time-sensitive peer-to-peer networking
WO2018054336A1 (zh) 消息的发送方法和装置
WO2021018213A1 (zh) 一种通信方法及装置
US20240188104A1 (en) Communication method and apparatus
WO2022262589A1 (zh) 一种会话建立方法及装置
WO2022205444A1 (zh) 广播消息的发送方法、接收方法、装置、设备及存储介质
CN114979964B (zh) 一种通信方法及装置
WO2022266961A1 (zh) 一种变量的维护方法及装置、终端设备
WO2023272619A1 (zh) 一种传输方式的确定方法及装置、终端设备、网络设备
WO2023056641A1 (zh) 一种头压缩方法及装置、终端设备、网络设备
WO2024093914A1 (zh) 数据传输方法、装置及系统
WO2024027412A1 (zh) 通信方法、通信装置及通信系统

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022851851

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022851851

Country of ref document: EP

Effective date: 20240208

NENP Non-entry into the national phase

Ref country code: DE