WO2023273355A1 - 一种多播业务的通信方法、装置及系统 - Google Patents

一种多播业务的通信方法、装置及系统 Download PDF

Info

Publication number
WO2023273355A1
WO2023273355A1 PCT/CN2022/075884 CN2022075884W WO2023273355A1 WO 2023273355 A1 WO2023273355 A1 WO 2023273355A1 CN 2022075884 W CN2022075884 W CN 2022075884W WO 2023273355 A1 WO2023273355 A1 WO 2023273355A1
Authority
WO
WIPO (PCT)
Prior art keywords
access network
network device
information
terminal
multicast service
Prior art date
Application number
PCT/CN2022/075884
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 华为技术有限公司
Publication of WO2023273355A1 publication Critical patent/WO2023273355A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/02—Selection of wireless resources by user or terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a communication method, device, and system for multicast services.
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • 3rd generation partnership project 3rd generation partnership project, 3GPP
  • the data requirements of the multicast service that is, the point-to-multipoint data transmission requirements, the multicast in this paper can also be called multicast.
  • Joining a multicast group in this article can also be called joining a multicast broadcast service session (MBS session), and can also be called participating in a multicast broadcast service session (involved in the MBS session).
  • MBS session multicast broadcast service session
  • participating in a multicast broadcast service session involved in the MBS session
  • the terminal can be in connection management (connection management (connection management, CM)-connected state (CM-CONNECTED) or connection management-idle state (CM-IDLE) or inactive state (which can be referred to as including CM connection RRC inactive state (CM-CONNECTED with RRC-inactive)).
  • connection management connection management
  • CM-CONNECTED connection management
  • CM-IDLE connection management-idle state
  • inactive state which can be referred to as including CM connection RRC inactive state (CM-CONNECTED with RRC-inactive)
  • Embodiments of the present application provide a multicast service communication method, device, and system to solve the problem that the access network equipment cannot perceive that a terminal that is in an inactive state and joins a multicast group leaves the access network equipment, causing the access network equipment to The problem that the number of terminals joining the multicast group cannot be updated in time.
  • a communication method for a multicast service can be applied to a terminal in the RRC inactive state moving from a first access network device to a second access network device, and the terminal passes through the first access network
  • the device joins the multicast group corresponding to the multicast service; the method may include that the terminal determines that it is located outside the service area of the first access network device (which may be referred to as the first area herein), and the terminal sends a request to the second access network device sending the first information, the first information can be used to notify the terminal to move out of the first area, and trigger the second access network device to send the second information updating the context of the multicast service to the first access network device, so that the first access
  • the network device updates the number of terminals joining the multicast group in the context of the multicast service, or triggers the second access network device to send to the first access network device the user equipment ( user equipment (UE) context, so that the first access network device perceives that the UE context of the terminal is extracted, and updates the number
  • the terminal After the terminal finds that it has moved out of the service area of the source access network device, it promptly notifies the target access network device (or called the new access network device or the second access network device) that the terminal has moved out of the service area.
  • the service area of the source access network device is triggered, and the target access network device is triggered to notify the source access network device to update the context of the multicast service or extract the UE context of the terminal from the source access network device.
  • the terminal leaves the multicast group corresponding to the multicast service under the management of the source access network device, and the source access network device updates the number of terminals joining the multicast group in time, according to The updated number of terminals joining the multicast group adjusts the resources for transmitting the data of the multicast service in time to improve resource utilization.
  • the first information includes identification information of the multicast service
  • the first information may also include a temporary wireless network identifier of the terminal, where the temporary wireless network identifier includes an identifier of the first access network device, and the wireless network information of the terminal is analyzed
  • the temporary identifier can know the identifier of the first access network device, and then send the second information or the third information to the first access network device according to the identifier of the first access network device, and the second information can be obtained through the wireless network temporary identifier of the terminal.
  • An access network device simplifies system design.
  • the first information is carried in a first RRC message used to request a resume (resume) RRC connection of the terminal, and the first RRC message may be an RRC resume request (RRC resume request) message; or, the first An RRC message is an RRC message, and the first RRC message may be used to restore the RRC connection of the terminal, or the first RRC message is used to trigger the second access network device to send the second information or the third information.
  • the carrying manner of the first information can be flexibly and effectively designed, and at the same time, when the first RRC message is an RRC recovery request message, system design can be simplified and signaling overhead can be saved.
  • the terminal sending the first information to the second access network device includes: the terminal sending the first information to the second access network device through a signaling radio bearer.
  • the signaling radio bearer may be SRB0.
  • the method further includes: the terminal receives information about the first area from the first access network device; where the information about the first area can be used to indicate the first area, for example, the information of the first area
  • the information may be one or more of the following: the identifier of the first access network device, the identifiers (cell ID(s)) of one or more cells included in the first access network device, and the cell ID(s) included in the first access network device.
  • a list of cells (cell ID list), one or more tracking area identifiers (tracking area ID(s), TAI(s)) supported/included/belonging to by the first access network equipment, first access network One or more tracking area lists (TA List) that the device supports/includes/belongs to, the name of the first access network device (RAN Node Name), and one or more physical cells included in the first access network device
  • An identifier (physical cell identifier, PCI(s)), a list of physical cell identifiers (PCI list) included in the first access network device, geographic information of the location of the first access network device (such as a global positioning system (global positioning system) , GPS) information, one or more central units (Central Unit, CU(s)) and/or distribution (distributed unit, DU(s)) identifiers included in the first access network device, the first access network device Included CU list and/or DU list, etc. Based on this possible design, the first access network device can indicate the first
  • the information in the first area is carried in the second RRC message used to suspend the RRC connection of the terminal.
  • the second RRC message may be one or more of the following: RRC connection suspend (RRC connection suspend)
  • RRC connection suspend RRC connection suspend
  • the information of the first area can be sent to the terminal during the RRC connection suspension process, which simplifies system design and saves signaling overhead.
  • the present application provides a multicast service communication method, the method can be applied to a scenario where a terminal moves from a first access network device to a second access network device, and the terminal is in the RRC inactive state , the method may include: the second access network device receives first information from the terminal, the first information may be used to notify the terminal to move out of the first area (herein may be referred to as the service area of the first access network device), According to the first information, the second access network device sends second information for updating the context of the multicast service to the first access network device, so that the first access network device updates the context of the multicast service according to the second information ; or send the third information for extracting the UE context of the terminal from the first access network device to the first access network device, so that the first access network device can join through the first access network device according to the third information update The number of endpoints in the multicast group.
  • the second access network device may send the second information to the first access network device to trigger the first access network device to
  • the network access device updates the context of the multicast service, or sends third information to the first access network device to extract the UE context of the terminal.
  • the source access network device such as the first access network device
  • the source access network device can adjust in time According to the number of terminals joining the multicast group, resources for transmitting data of the multicast service are adjusted in time according to the number of terminals joining the multicast group, so as to improve resource utilization.
  • the first information includes identification information of the multicast service, and further includes a temporary wireless network identifier of the terminal, where the temporary wireless network identifier includes an identifier of the first access network device.
  • the second access network device sending the second information or the third information to the first access network device according to the first information includes: the second access network device sending the first access network device The device sends the second information or the third information. In this way, the first access network device can be known through the wireless network temporary identifier of the terminal, which simplifies system design.
  • the second information includes identification information of the multicast service, so that the first access network device can update the context of the multicast service in time according to the identification information of the multicast service, for example, update the context of the multicast service by The number of terminals that the first access network device joins in the multicast group simplifies system design.
  • the second information or the third information is carried in the request to extract the UE context; or the second information or the third information is carried in the Xn message. Based on this possible design, the second information or the third information is carried in the existing signaling message or in other Xn messages carried on the Xn interface between access network devices, which saves signaling overhead and implements effectively and flexibly Sending of the second information or the third information.
  • the embodiment of the present application further provides a multicast service communication method, the method is applied to a terminal in the RRC inactive state moving from the first access network device to the second access network device, and the terminal passes through the first access network device
  • An access network device joins a multicast group corresponding to the multicast service the method may include: the first access network device receives second information for updating the context of the multicast service from the second access network device, The context of the multicast service is updated according to the second information.
  • the first access network device may update the context of the multicast service so that it records that it joins the multicast through the first access network device
  • the number of terminals in the group is consistent with the actual number, so that the first access network device can timely adjust resources for transmitting data of the multicast service according to the updated number of terminals joining the multicast group, thereby improving resource utilization.
  • the second information includes identification information of the multicast service, that is, the second access network device indicates the identification information of the multicast service to the first access network device, so that the first access network device Find the context of the multicast service based on the identification information of the broadcast service, and update the context of the multicast service to simplify system design.
  • updating the context of the multicast service by the first access network device according to the second information includes: updating the context of the multicast service by the first access network device according to the second information The number of terminals that the device joins in the multicast group, such as subtracting 1 from the number of terminals.
  • the second information also includes identification information of the terminal
  • updating the context of the multicast service by the first access network device according to the second information may also include: deleting the multicast service context by the first access network device according to the second information.
  • the identification information of the terminal in the context of the broadcast service may also include: deleting the multicast service context by the first access network device according to the second information.
  • the second information includes the temporary wireless network identifier of the terminal; updating the context of the multicast service by the first access network device according to the second information includes: the first access network device according to the temporary wireless network identifier of the terminal, Obtain the identification information of the multicast service in the UE context of the terminal, delete the identification information of the terminal in the context of the multicast service according to the obtained identification information of the multicast service, or update the multicast service context through the first access network The number of terminals that the device joins the multicast group.
  • the context of the multicast service can be obtained, and then the identification information of the terminal in the context of the multicast service can be deleted or the number of terminals joining the multicast group through the first access network device can be updated in the context of the multicast service , reducing the number of terminals joining the multicast group by 1, so that the first access network device can timely adjust resources for transmitting data of the multicast service according to the number of terminals joining the multicast group, thereby improving resource utilization.
  • the second information is carried in the extract UE context request or Xn message, which saves signaling overhead, and at the same time, effectively and flexibly sends the second information to the first access network device.
  • the embodiment of the present application also provides a multicast service communication method, which can be applied to a terminal in the RRC inactive state moving from the first access network device to the second access network device, and the terminal passes through the first access network device
  • An access network device joins a multicast group corresponding to a multicast service the method includes: the first access network device receives UE context for extracting a terminal from the first access network device from the second access network device According to the third information, the number of terminals joining the multicast group through the first access network device is updated.
  • the second access network device extracts the UE context of the terminal from the first access network device, if the terminal joins the multicast group through the first access network device, then Since the UE context of the terminal is extracted, it is determined to update the number of terminals that join the multicast group through the first access network device, such as reducing the number of terminals by 1, etc., to ensure that the first access network device records through the first access network device.
  • the number of terminals that the access network device joins the multicast group is consistent with the actual number, so that the first access network device can timely adjust resources for transmitting data of the multicast service according to the updated number of terminals joining the multicast group, Improve resource utilization.
  • the method further includes: the first access network device deleting the identification information of the multicast service in the UE context of the terminal. Based on this possible design, the identification information of the multicast service can be deleted from the UE context, so as to determine the number of terminals joining the multicast group by counting which UE contexts include the identification information of the multicast service.
  • the third information includes identification information of the multicast service.
  • the second access network device indicates the identification information of the multicast service to the first access network device, so that the first access network device finds the context of the multicast service according to the identification information of the multicast service, and updates the context of the multicast service , to simplify system design.
  • the first access network device updating the number of terminals joining the multicast group through the first access network device according to the third information includes: the first access network device obtaining the terminal
  • the UE context of the terminal includes the identification information of the multicast service, and according to the identification information of the multicast service, the number of terminals that join the multicast group through the first access network device in the context of the multicast service is updated, for example, the The number of terminals joining the multicast group is reduced by 1, which facilitates the first access network device to timely adjust resources for transmitting data of the multicast service according to the number of terminals joining the multicast group, thereby improving resource utilization.
  • the method further includes: the first access network device sending information about a first area to the terminal, where the first area is a service area of the first access network device. Based on this possible design, the first access network device can indicate its own service area to the terminal, which simplifies system design.
  • the embodiment of the present application further provides a multicast service communication method, the method comprising: the access network device allocates a wireless network temporary identifier of the multicast service according to the multicast service identification information, and according to the multicast service obtain the scrambled downlink control information of the wireless network temporary identifier, and send the fourth information including the identifier information of the multicast service and the wireless network temporary identifier of the multicast service, and the scrambled downlink control information, so that the receiving/monitoring of the fourth
  • the information terminal obtains descrambled downlink control information according to the wireless network temporary identifier of the multicast service, and receives data of the multicast service according to the descrambled downlink control information.
  • the access network device sends the identification information of the multicast service and the temporary wireless network identification of the multicast service, so that when there is a terminal in an idle state or an inactive state in the multicast group, the multicast
  • the terminals in the group receive the identification information of the multicast service and the wireless network temporary identification of the multicast service, and when they are interested in the multicast service, use the wireless network temporary identification of the multicast service to obtain the descrambling downlink Control information, receiving descrambled downlink control information and scheduled multicast service data, solving the problem that a terminal in an idle state or inactive state cannot receive multicast service data due to disconnecting the RRC connection with the access network device question.
  • the fourth information is carried in a system information block (system information block, SIB); or, the fourth information is carried in a master information block (master information block, MIB); or, the fourth information is carried in In the paging message.
  • SIB system information block
  • MIB master information block
  • the access network device effectively and flexibly broadcasts/sends the fourth information to the terminals in the cell in various ways, so that even terminals disconnected from the RRC connection can receive the fourth information.
  • the access network device sending the fourth information includes: the access network device sending an RRC message through a signaling radio bearer (signal radio bearer, SRB). Based on this possible design, the access network device broadcasts/sends the fourth information to terminals in the cell through the SRB corresponding to the cell at the granularity of the cell, so that even terminals disconnected from the RRC connection can receive the fourth information.
  • SRB signaling radio bearer
  • the embodiment of the present application further provides a communication method for a multicast service, the method including: the terminal receives from the access network device the first information including the identification information of the multicast service and the wireless network temporary identifier of the multicast service. Four information, scrambled downlink control information, receiving multicast service data from the access network device according to the fourth information and scrambled downlink control information.
  • the terminal can be in an idle state or an inactive state.
  • a terminal joining a multicast group even if the terminal disconnects the RRC connection and is in an idle state or an inactive state, it can also receive the identification information of the multicast service sent by the access network device and The wireless network temporary identifier of the multicast service, and in the case of interest in the multicast service, use the wireless network temporary identifier of the multicast service to obtain descrambled downlink control information, and receive the multicast scheduled by the descrambled downlink control information
  • the data of the service solves the problem that the terminal in the idle state or the inactive state cannot receive the data of the multicast service because the RRC connection is disconnected.
  • the terminal receives the data of the multicast service from the access network device according to the fourth information and the scrambled downlink control information, including: when the terminal is interested in the multicast service, the terminal receives the multicast service data according to the multicast service obtain the descrambled downlink control information, and receive the data of the multicast service from the access network device according to the descrambled downlink control information.
  • the wireless network temporary identifier of the multicast service to scramble and schedule the downlink control information of the data of the multicast service, and only the data of the multicast service has the scrambled downlink control information scheduling to ensure the The security of data transmission simplifies system design.
  • the fourth information is carried in the SIB; or, the fourth information is carried in the MIB; or, the fourth information is carried in the paging message. Based on this possible design, the fourth information is effectively and flexibly broadcast/sent to terminals in the cell in multiple ways, so that even terminals disconnected from the RRC connection can receive the fourth information.
  • the terminal receiving the fourth information from the access network device includes: the terminal receiving the fourth information from the access network device through the SRB. Based on this possible design, the fourth information is received through the signaling radio bearer (such as SRBO) corresponding to the cell at the granularity of the cell, so that even a terminal disconnected from the RRC connection can receive the fourth information, which simplifies the system design.
  • the signaling radio bearer such as SRBO
  • the present application provides a communication device.
  • the communication device may be a terminal or a chip or a system-on-a-chip in the terminal, and may also be a communication device used to implement the first aspect or any possible design of the first aspect.
  • the communication device can realize the above aspects or the functions performed by the communication device in each possible design, and the functions can be realized by executing corresponding software through hardware.
  • the hardware or software includes one or more modules with corresponding functions above.
  • the communication device may include: a processing unit, a receiving unit, and a sending unit.
  • the terminal is in an inactive state, and the terminal joins the multicast group corresponding to the multicast service through the first access network device, and moves from the first access network device to the second access network device
  • the processing unit is configured to determine that the terminal is located outside the service area of the first access network device.
  • a sending unit configured to send first information including identification information of a multicast service to a second access network device, where the first information is used to notify the terminal to move out of the first area, and trigger the second access network device to send a message to the first access network device.
  • the device sends second information for updating the context of the multicast service, or sends third information for extracting the UE context of the terminal from the first access network device to the first access network device.
  • the receiving unit is configured to receive fourth information including identification information of the multicast service and wireless network temporary identification of the multicast service, and scrambled downlink control information from the access network device, according to the first The four information and the scrambled downlink control information receive the data of the multicast service from the access network equipment.
  • the terminal can be in an idle state or an inactive state.
  • the specific implementation of the communication device may refer to the first aspect or any possible design of the first aspect or the sixth aspect or any possible design of the sixth aspect.
  • the present application provides a communication device.
  • the communication device may be a second access network device or a chip or a system-on-chip in the second access network device, and may also be a communication device used to implement the second aspect or
  • the communication device can realize the functions performed by the communication device in the above aspects or each possible design, and the functions can be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules with corresponding functions above.
  • the communication device may include: a receiving unit and a sending unit.
  • the receiving unit is configured to receive first information from the terminal that includes identification information of the multicast service, the first information may be used to notify the terminal to move out of the first area (herein may be referred to as the service area of the first access network device) .
  • a sending unit configured to send second information for updating the context of the multicast service to the first access network device according to the first information, so that the first access network device updates the context of the multicast service according to the second information; Or send the third information for extracting the UE context of the terminal from the first access network device to the first access network device, so that the first access network device updates the multi-user access through the first access network device according to the third information.
  • the present application provides a communication device.
  • the communication device may be the first access network device or a chip or a system-on-chip in the first access network device, and may also be a communication device used to implement the third aspect or Any possible design of the third aspect is a functional module of the described method, or a functional module for realizing the fourth aspect or any possible design of the fourth aspect.
  • the communication device can realize the above aspects or the functions performed by the communication device in each possible design, and the functions can be realized by executing corresponding software through hardware.
  • the hardware or software includes one or more modules with corresponding functions above.
  • the communication device may include: a processing unit and a receiving unit.
  • the receiving unit is configured to receive second information for updating the context of the multicast service from the second access network device.
  • a processing unit configured to update the context of the multicast service according to the second information.
  • the receiving unit is configured to receive third information for extracting the UE context of the terminal from the second access network device.
  • a processing unit configured to update the number of terminals joining the multicast group through the first access network device according to the third information.
  • the communication device refers to the behavior function of the first access network device in the third aspect or any possible design of the third aspect, or refer to the fourth aspect or any possible design of the fourth aspect
  • the behavior and function of the first access network device in the design of will not be repeated here.
  • the present application provides a communication device.
  • the communication device may be an access network device or a chip or a system-on-a-chip in the access network device, and may also be a communication device used to implement the fifth aspect or the fifth aspect.
  • the communication device may implement the above aspects or the functions performed by the communication device in each possible design, and the functions may be implemented by executing corresponding software through hardware.
  • the hardware or software includes one or more modules with corresponding functions above.
  • the communication device may include: a processing unit and a sending unit.
  • the processing unit is configured to allocate a wireless network temporary identifier of the multicast service according to the identification information of the multicast service, and obtain scrambled downlink control information according to the wireless network temporary identifier of the multicast service.
  • a sending unit configured to send fourth information including the identification information of the multicast service and the wireless network temporary identifier of the multicast service, and scrambled downlink control information, so that the terminal receiving/monitoring the fourth information
  • the wireless network temporary identifier obtains descrambled downlink control information, and receives multicast service data according to the descrambled downlink control information.
  • a communication device in an eleventh aspect, includes one or more processors and one or more memories.
  • the one or more memories are coupled to the one or more processors, the one or more memories are used to store computer program codes, the computer program codes include computer instructions, and when the one or more processors execute the
  • the communication device is made to execute the method steps performed by the terminal in the first aspect or in any possible design of the first aspect; or to execute the method steps in the second aspect or in any possible design of the second aspect Method steps executed by the second access network device; or executed by the first access network device as in the third aspect or in any possible design of the third aspect or in the fourth aspect or in any possible design of the fourth aspect or execute the method steps performed by the access network device in the fifth aspect or any possible design of the fifth aspect; or execute the terminal in any possible design as described in the sixth aspect or the sixth aspect The method steps performed.
  • a computer program product including instructions, which, when run on a computer, cause the computer to perform the method steps performed by the terminal in any possible design of the first aspect or the first aspect; Or execute the method steps performed by the second access network device in the second aspect or any possible design of the second aspect; or execute the third aspect or any possible design of the third aspect or the fourth aspect or the method steps performed by the first access network device in any possible design of the fourth aspect; or perform the method steps performed by the access network device in the fifth aspect or any possible design of the fifth aspect; or perform The method steps performed by the terminal in the sixth aspect or any possible design described in the sixth aspect.
  • a computer-readable storage medium may be a readable non-volatile storage medium. Instructions are stored in the computer-readable storage medium.
  • the computer-readable storage medium When the computer-readable storage medium is run on a computer , make the computer perform the method steps performed by the terminal in the first aspect or in any possible design of the first aspect; or execute the second access in the second aspect or in any possible design of the second aspect.
  • a fourteenth aspect there is also provided a communication system, which may include the terminal as described in the first aspect or any possible design of the first aspect, such as the second aspect or any of the second aspects
  • the communication system may include the access network device according to the fifth aspect or any possible design of the fifth aspect, and the terminal according to the sixth aspect or any possible design of the sixth aspect.
  • FIG. 1 is a flowchart of a terminal joining a multicast group corresponding to a multicast service provided by an embodiment of the present application;
  • FIG. 2 is a schematic diagram of a network architecture provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a 5G communication system provided by an embodiment of the present application.
  • FIG. 4 is a schematic diagram of the composition of a communication device 400 provided in an embodiment of the present application.
  • FIG. 5a is a flow chart of a communication method for a multicast service provided by an embodiment of the present application.
  • FIG. 5b is a flowchart of a communication method for a multicast service provided by an embodiment of the present application.
  • FIG. 6 is a flowchart of a communication method for a multicast service provided in an embodiment of the present application.
  • FIG. 7 is a schematic diagram of sending fourth information provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of the composition of a communication device 80 provided in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of the composition of a communication device 90 provided in an embodiment of the present application.
  • FIG. 10 is a schematic diagram of the composition of a communication device 100 provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of the composition of a communication system provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • the terminal can establish a radio resource control (radio resource control, RRC) connection with the access network device in the RRC connection state, and pass the connection in the RRC connection state.
  • RRC radio resource control
  • the network access device joins the multicast group corresponding to the multicast service, and receives the data of the multicast service sent by the access network device for the multicast group.
  • the access network device may provide network services (such as providing multicast service data to the terminal) for the terminal, and the terminal currently resides in the service area of the access network device.
  • the multicast group corresponding to joining the multicast service described in this application can be described as joining a multicast service, or joining a multicast group, or joining a multicast broadcast service (multicast broadcast service, MBS), Either join a multicast session (multicast session) corresponding to the multicast service or join a multicast broadcast service session (multicast broadcast service session, MBS session) corresponding to the multicast service, or join a multicast group corresponding to the multicast session.
  • MBS multicast broadcast service
  • the multicast described in this application may refer to a communication method for sending the same data to multiple terminals.
  • This application does not limit the naming of multicast, and the multicast described in this application may be replaced by multicast or broadcast Or multicast/broadcast (multicast/broadcast).
  • Multicast in this application is a concept in a broad sense, and may include multicast or broadcast. That is, the embodiments of this application may be applied to both multicast service transmission and broadcast service transmission.
  • “Multicast” mentioned in this application can be replaced with "multicast or broadcast”.
  • the multicast session (multicast session) in this application can be replaced by a multicast service session (multicast service session) or a multicast broadcast service session (multicast broadcast service session, MBS session), which is not limited.
  • Figure 1 is a flowchart of a terminal joining a multicast group corresponding to a multicast service through an access network device, and the process may include:
  • join request After the terminal establishes an RRC connection with the access network device and is in the connected state, the terminal can send a join request (join request) to the core network device through the access network device.
  • the join request can be used to request to join the multicast corresponding to the multicast service group, the join request may carry identification information of the multicast service.
  • the core network device may send a request to the access network device
  • the identification information of the multicast service and the quality of service (QoS) information of the multicast service (such as the quality of service identifier (QoS identifier, QFI) of the multicast service, the quality of service policy (QoS profile) of the multicast service, etc.)
  • QoS flow, QF the relevant information of the unicast QF mapped to the multicast QoS flow (QoS flow, QF), such as the unicast QFI corresponding to the unicast QF, the unicast
  • the access network device can store the relevant information of the multicast service in the context of the multicast service, and add 1 to the number of terminals added to the multicast group in the context of the multicast service, or Add the identification information of the terminal to the context of the multicast service, or store the identification information of the multicast service in the UE context of the terminal (for example, the new generation application protocol (new generation application protocol, NGAP) of the terminal in the access network device UE context (NGAP UE context)), and configure the air interface radio bearer (such as data radio bearer (DRB) or multiple multicast radio bearer (multicast radio bearer, MRB, etc.), and configure the wireless network temporary identity of the multicast service, such as the group-radio network temporary identity (group-radio network temporary identity, G-RNTI) corresponding to the multicast service.
  • the access network device may also store the identification information of the multicast service in the context of the user equipment (user equipment, UE) of the terminal, so as to indicate that
  • the access network device sends information such as the radio network temporary identifier of the multicast service (such as the G-RNTI of the multicast service) to the terminals in the multicast group.
  • the terminal receives information such as the wireless network temporary identifier of the multicast service from the access network device.
  • the terminal can receive the data of the multicast service transmitted by the access network device through the wireless bearer of the air interface according to the wireless network temporary identifier of the multicast service.
  • the access network The device can use the G-RNTI to scramble the downlink control information (DCI) to obtain scrambled DCI, which can be used to schedule multicast service data, and the access network device sends the scrambled DCI and the DCI indicated in the DCI After successfully descrambling the scrambled DCI by using the G-RNTI, the terminal receives data of the multicast service on a physical downlink shared channel (physical downlink shared channel, PDSCH) indicated by the DCI.
  • DCI downlink control information
  • the context of multicast service can be described as multicast broadcast service session context (MBS session context), or multicast broadcast context (MBS context), or multicast broadcast group context (MBS group context), or multicast broadcast service context (MBS service context), etc.
  • MBS session context multicast broadcast service session context
  • MMS context multicast broadcast context
  • MMS group context multicast broadcast group context
  • MS service context multicast broadcast service context
  • the context of the multicast service may include identification information of the multicast service, QoS information of the multicast service, Information about terminals joining a multicast group through an access network device, etc.
  • the information of the terminal joining the multicast group through the access network device may include the number of the terminal joining the multicast group through the access network device, and may also include the identification of the terminal joining the multicast group through the access network device information.
  • UE1-UE4 join the multicast group corresponding to the multicast service through base station 1
  • the context of the multicast service may include the number 4 of terminals joining the multicast group, or the number of terminals joining the multicast group 4 and terminal identification information ⁇ UE1, UE2, UE3, UE4 ⁇ .
  • the identification information of the multicast service may be used to identify the multicast service.
  • the identification information of the multicast service can be configured by the application layer of the terminal.
  • the identification information of the multicast service can be equivalently replaced with the identification information of the multicast group corresponding to the multicast service (such as a temporary multicast group identifier (TMGI)), or an application that provides multicast service data
  • TMGI temporary multicast group identifier
  • IP Internet protocol
  • IP Internet protocol
  • service identifier service identifier, service ID
  • packet filter packet filter
  • the identification information of the multicast session used to transmit the data of the multicast service or the multicast/broadcast service identifier (MBS ID), or the multicast/broadcast service session Identifier (MBS session ID), or multicast/broadcast service identifier, or source specific IP multicast address (source
  • the PDR is a collection of filters, each filter is a quintuple, and each filter includes the source address, destination address, source port number, destination port number, and protocol number of the multicast service, and the PDR is used for The data of the multicast service is filtered.
  • the identification information of the terminal may be used to identify the terminal.
  • the identification information of the terminal may be referred to as identity information of the terminal, and the identification information of the terminal may be network-wide identification information of the terminal.
  • the identification information of the terminal may be an Internet protocol (internet protocol, IP) address of the terminal or a media access control (media access control, MAC) address of the terminal or an international mobile subscriber identity (international mobile subscriber identity, IMSI) of the terminal.
  • IP Internet protocol
  • MAC media access control
  • IMSI international mobile subscriber identity
  • the terminal’s permanent identifier subscriber permanent identifier, SUPI
  • the terminal’s 5G global user temporary identifier 5G-GUTI
  • the terminal’s subscriber concealed identifier SUCI
  • the terminal's general public subscription identifier generator public subscription identifier, GPSI
  • the terminal's 5G short temporary mobile subscriber identity 5G S-temporary mobile subscriber identity, 5G-S-TMSI
  • the terminal's permanent equipment identifier permanent equipment identifier, PEI
  • the identification information of the terminal may be the wireless network temporary identifier of the terminal, such as the RNTI of the terminal, where the granularity of the cell or the access network device is used as the granularity.
  • the wireless network temporary identifier of the terminal may be used to identify a certain For a terminal in the service area of a cell or an access network device, the RNTI of the terminal corresponds to the cell/access network device. RNTIs are different when the terminal is located in the service area of different access network devices.
  • the access network device may decide to suspend the RRC connection of the terminal and send the RRC connection to the terminal.
  • Suspend (RRC connection suspend) message After receiving the RRC connection suspend message, the terminal disconnects the RRC connection with the access network device, and switches from the connected state to the inactive (inactive) state or the idle state.
  • the terminals in the inactive or idle state cannot receive any data through the access network equipment, such as multicast service data, and the access network equipment cannot know/monitor the location information of the terminals in the inactive or idle state.
  • base station 1 can suspend the RRC connection with UE1. At this time, UE1 cannot receive Data of the multicast service sent by base station 1.
  • the connected state may be referred to as the RRC connected state.
  • the connected state there is an RRC connection between the terminal and the access network equipment, and there is a non-access layer (non- access stratum (NAS) signaling connection, there is a per UE granular N2 interface connection between the access network device and the mobility management network element.
  • NAS non-access stratum
  • both the access network device and the mobility management network element store the UE context of the terminal.
  • the UE context of the terminal saved on the access network device is different from the UE context of the terminal saved on the mobility management network element.
  • the UE context of the terminal saved by the access network device is related to the data transmission of the terminal.
  • the access network device can The stored UE context of the terminal knows that the terminal is within the service area of the access network device or within the service area of the access network device.
  • the UE context of the terminal saved by the mobility management network element may include the identification information of the terminal, the location information of the terminal, the registration area of the terminal, the current connection management (connection management, CM) connection status of the terminal, etc., and the mobility management network element may according to The UE context of the terminal knows through which access network device the terminal can be located or found.
  • the inactive state can be referred to as the radio access control inactive state (RRC_inactive state (RRC_inactive state).
  • RRC_inactive state the radio access control inactive state
  • the RRC connection is disconnected between the terminal and the access network device, and the access There is an N2 interface connection with UE as the granularity (such as per UE) between the network equipment and the mobile management network element.
  • the UE context of the terminal is stored in the access network equipment, and the UE context of the terminal can be stored in the mobile management network element.
  • the network access device does not know the specific cell where the terminal resides in the service area of the access network device or whether it is within the management range of the access network device, and the mobility management network element knows which access network device the terminal is in. Within or within the management range, the mobility management network element knows which access network device can locate or find the terminal.
  • the idle (idle) state may mean that there is no RRC connection between the terminal and the access network device.
  • the idle state may be called an RRC_idle state.
  • the UE context of the terminal is not saved in the access network device, there is no NAS signaling connection between the terminal and the mobility management network element (such as AMF), and there is no per UE between the access network device and the mobility management network element
  • the N2 interface of the terminal is connected, and the mobility management network element stores the UE context of the terminal.
  • the access network device does not know whether the terminal is within the service area of the access network device.
  • the mobile management network element does not know which access network device the terminal is in the service area or management range, and the access network device does not know which access network device can locate or find the terminal.
  • the UE context of the terminal stored on the access network device is related to the data transmission of the terminal.
  • the UE context of the terminal saved on the access network device may include the information of the protocol data unit (protocol data unit, PDU) session of the terminal, and the information of the PDU session includes unicast QoS parameters (such as the QoS profile of unicast QF) .
  • PDU protocol data unit
  • unicast QoS parameters such as the QoS profile of unicast QF
  • the UE context of the terminal may also include information related to the multicast service, for example, the UE context of the terminal may include information about the multicast service Identification information, the QoS profile of the multicast QF corresponding to the multicast service, the mapping relationship between the multicast QF and the unicast QF, etc.
  • the access network device that provides network services for the terminal does not know whether the terminal is still in the service area of the access network device, and does not know where the terminal is currently. district.
  • the access network device does not Knowing the movement track of the terminal, mistakenly thinking that the terminal is still in the service area of the access network device, causing the access network device not to update the number of terminals joining the multicast group, so that the access network device joins the multicast group
  • the number of terminals in the multicast group is inconsistent with the actual number, and the access network device mistakenly thinks that the number of terminals in the multicast group remains unchanged and does not adjust the resources for transmitting data of the multicast service, resulting in waste of resources.
  • UE1 and UE2 have no data service demand for a long time, and the RRC connection with UE1 and UE2 is suspended, and they are in an inactive state. At this time, it is assumed that UE1 and UE2 also leave the service area of base station 1 and no longer accept network services provided by base station 1 . However, as far as base station 1 is concerned, the location information of UEs in the inactive state cannot be obtained, and it is still considered that the number of terminals joining the multicast group through base station 1 is 4, so the transmission of multicast service data is not adjusted. In fact, the number of terminals joining the multicast group through base station 1 is reduced to two. At this time, base station 1 could have adjusted/reduced the resources for transmitting multicast service data to the resources corresponding to these two UEs. save resources.
  • an embodiment of the present application provides a multicast service communication method, which can be applied to a terminal in an inactive state moving from a first access network device to a second access network device, and the terminal In the scenario of joining a multicast group corresponding to the multicast service through the first access network device.
  • the method may include: when the terminal determines that it is located outside the service area of the first access network device (which may be referred to as the first area in this application), the terminal sends a message including identification information of the multicast service to the second access network device
  • the first information triggers the second access network device to send the second information for updating the context of the multicast service to the first access network device, so that the first access network device updates the multicast service according to the received second information context, such as reducing the number of terminals joining the multicast group in the context of the multicast service by 1, etc.; or triggering the second access network device to send a message to the first access network device for extracting
  • the third information of the UE context of the terminal so that the first access network device updates the number of terminals joining the multicast group through the first access network device according to the third information.
  • the context of the multicast service or the number of terminals joining the multicast group can be updated in time according to the movement of the terminal in the inactive state, preventing the access network device from not updating the number of terminals joining the multicast group, so that The number of terminals joining the multicast group through the access network device is inconsistent with the actual number, causing the access network device to mistakenly think that the number of terminals in the multicast group remains unchanged and not to adjust the resources for transmitting multicast service data , resulting in a waste of resources.
  • the first access network device described in this application may be an access network device that provides network services for the terminal before the terminal moves (before camping/moving to the cell corresponding to the second access network device),
  • the second access network device may be an access network device corresponding to the cell where the terminal currently resides/resides.
  • the first access network device may be called a source access network device, and the second access network device may be called a target access network device.
  • the service area of the first access network device described in this application may be replaced by a signal coverage area of the first access network device or a cell included in the first access network device.
  • Terminals or other devices located in the service area of the first access network device can establish an RRC connection with the first access network device, and receive network services provided by the first access network device through the RRC connection, such as receiving The data of the multicast service of the network equipment, etc.
  • the multicast service communication method provided by the embodiment of the present application can be applied to the communication system shown in FIG. 2.
  • the communication system may include multiple terminals, a first access network device, and a second access network equipment. Further, it may also include core network equipment (such as a mobility management network element, a session management network element, etc.), a user plane network element, and a data network (data network, DN).
  • core network equipment such as a mobility management network element, a session management network element, etc.
  • a user plane network element such as a user plane network element, and a data network (data network, DN).
  • DN data network
  • a terminal may be a device for implementing a wireless communication function, such as a terminal or a chip that may be used in a terminal.
  • the terminal can be a UE, an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a terminal agent or a terminal in a 5G network or a future evolved communication system device etc.
  • An access terminal may be a cellular telephone, a cordless telephone, a session initiation protocol (SIP) telephone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices or wearable devices, virtual reality (virtual reality, VR) terminal devices, augmented reality (augmented reality, AR) terminal devices, industrial control (industrial Wireless terminals in control, wireless terminals in self driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety Terminals, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal may be mobile, and may move from the first access network device to the second access network device. It should be understood that moving from the first access device to the second access network device in this embodiment of the present application may refer to moving from the service area of the first access network device to the service area of the second access network device, and the like.
  • the first access network device and the second access network device may be collectively referred to as access network devices, and are mainly used to implement functions such as physical layer functions, resource scheduling and management, terminal access control, and mobility management.
  • the access network device may be a device supporting wired access, or a device supporting wireless access.
  • the access network device may be an access network (access network, AN)/radio access network (radio access network, RAN), which is composed of multiple 5G-AN/5G-RAN nodes.
  • 5G-AN/5G-RAN nodes can be: access point (access point, AP), base station (nodeB, NB), enhanced base station (enhance nodeB, eNB), next-generation base station (NR nodeB, gNB), transmission and reception point (transmission reception point, TRP), transmission point (transmission point, TP) or some other access node.
  • the mobile management network element is mainly responsible for terminal access authentication, mobility management, and signaling interaction between various functional network elements, such as: user registration status, user connection status, user registration and network access, tracking area update , cell handover user authentication and key security management.
  • the session management network element is mainly used to implement user plane transmission logic channels, such as session management functions such as establishment, release, and modification of PDU sessions.
  • the user plane network element can be used as the anchor point on the user plane transmission logical channel, and is used to complete functions such as routing and forwarding of user plane data, such as: establishing a channel with the terminal (that is, the user plane transmission logical channel), and on this channel Forwarding data packets between terminal and DN, responsible for terminal data packet filtering, data forwarding, rate control, and generating billing information.
  • DN is an operator network that can provide users with data transmission services, such as: an operator network that can provide users with Internet Protocol (internet protocol, IP) multimedia services (IP multi-media service, IMS).
  • IP Internet Protocol
  • IMS IP multi-media service
  • An AS may be deployed in the DN, and the application server may provide data transmission services to users.
  • the DN may include an application server (application server, AS).
  • FIG. 2 is only an exemplary architecture diagram.
  • the system may also include other functional network elements, such as: operation and management (operation and management, O&M) network elements, etc.
  • O&M operation and management
  • This embodiment of the present application does not limit it.
  • the name of each device in Figure 2 is not limited.
  • each device can also be named other names, such as replacing it with the name of a network element with the same or similar functions, there is no limit.
  • the system shown in Figure 2 may be a third generation partnership project (3rd generation partnership project, 3GPP) communication system, such as a 4th generation (4th generation, 4G) communication system, a long term evolution (long term evolution, LTE) system, It can also be a fifth generation (5th generation, 5G) communication system, a new radio interface (new radio, NR) system, a next generation communication system, etc., or a non-3GPP communication system, without limitation.
  • 3GPP third generation partnership project
  • the network element or entity corresponding to the access network device can be NG-RAN, and the above session management network element corresponds to
  • the network element or entity can be the session management function (session management function, SMF) in the 5G communication system
  • the mobility management network element corresponds to the access and mobility management function (access and mobility management function, AMF)
  • the user plane network element corresponds
  • the network element or entity in the 5G communication system may be the user plane function (user plane function, UPF)
  • the network element or entity corresponding to the access network device may be the radio access network (radio access network, RAN) in the 5G communication system.
  • radio access network radio access network
  • the network element or entity corresponding to the mobile management network element may be the access and mobility management function (access and mobility management function, AMF) in the 5G communication system.
  • AMF access and mobility management function
  • PCF policy control function
  • NEF network exposure function
  • UDR UDR or UDM, etc.
  • the first access network device, terminal, etc. in the embodiment of the present application may also be referred to as a communication device, which may be a general-purpose device or a dedicated device, which is not specifically limited in the embodiment of the present application.
  • the related functions of the first access network device and the terminal in the embodiment of the present application may be implemented by one device, or by multiple devices, or by one or more functions in one device.
  • Module implementation which is not specifically limited in this embodiment of the present application. It can be understood that the above-mentioned functions can be network elements in hardware devices, software functions running on dedicated hardware, or a combination of hardware and software, or instantiated virtualization on a platform (for example, a cloud platform) Function.
  • each device shown in FIG. 2 may adopt the composition structure shown in FIG. 4 , or include the components shown in FIG. 4 .
  • FIG. 4 is a schematic diagram of a composition of a communication device 400 provided by an embodiment of the present application.
  • the communication device 400 may include a processor 401 and a memory 404 . Further, the communication device 400 may further include a communication line 402 and a communication interface 403 . Wherein, the processor 401 , the memory 404 and the communication interface 403 may be connected through a communication line 402 .
  • the processor 401 can be a central processing unit (central processing unit, CPU), a general purpose processor, a network processor (network processor, NP), a digital signal processor (digital signal processing, DSP), a microprocessor, a microcontroller , programmable logic device (programmable logic device, PLD) or any combination thereof.
  • the processor 401 may also be other devices with processing functions, such as circuits, devices or software modules, without limitation.
  • the communication line 402 is used to transmit information between the components included in the communication device 400 .
  • the communication interface 403 is used for communicating with other devices or other communication networks.
  • the other communication network may be an Ethernet, a radio access network (radio access network, RAN), a wireless local area network (wireless local area networks, WLAN), and the like.
  • the communication interface 403 may be a module, a circuit, a transceiver or any device capable of realizing communication.
  • the memory 404 is used for storing instructions.
  • the instruction may be a computer program.
  • the memory 404 can be a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and/or instructions, and can also be a random access memory (random access memory, RAM) or a Other types of dynamic storage devices that store information and/or instructions can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD- ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs), magnetic disc storage media, and other magnetic storage devices, without limitation.
  • EEPROM electrically erasable programmable read-only memory
  • CD- ROM compact disc read-only memory
  • optical disc storage including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs
  • magnetic disc storage media and other magnetic storage devices, without limitation.
  • the memory 404 may exist independently of the processor 401 or may be integrated with the processor 401 .
  • the memory 404 can be used to store instructions or program codes or some data, etc.
  • the memory 404 may be located in the communication device 400 or outside the communication device 400, without limitation.
  • the processor 401 is configured to execute instructions stored in the memory 404, so as to implement the multicast service communication method provided by the following embodiments of the present application. For example, when the communication device 400 is a terminal or a chip in the terminal or a system on chip, the processor 401 executes instructions stored in the memory 404 to implement the steps performed by the terminal in the following embodiments of the present application. For another example, when the communication device 400 is the first access network device or a chip or a system-on-chip in the first access network device, the processor 401 may execute instructions stored in the memory 404 to implement the following embodiments of the present application. Steps performed by the first access network device.
  • the processor 401 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 4 .
  • the communications apparatus 400 includes multiple processors, for example, in addition to the processor 401 in FIG. 4 , it may further include a processor 407 .
  • the communication apparatus 400 further includes an output device 405 and an input device 406 .
  • the input device 406 is a device such as a keyboard, a mouse, a microphone, or a joystick
  • the output device 405 is a device such as a display screen and a speaker (speaker).
  • the communication device 400 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a device having a structure similar to that shown in FIG. 4 .
  • the composition structure shown in FIG. 4 does not constitute a limitation to the communication device.
  • the communication device may include more or less components than those shown in the illustration, or combine certain components , or different component arrangements.
  • system-on-a-chip may be composed of chips, or may include chips and other discrete devices.
  • FIG. 2 The architecture shown in FIG. 2 is taken as an example below to describe the communication method for the multicast service provided by the embodiment of the present application.
  • Each network element in the following embodiments may have components shown in FIG. 4 , which will not be described in detail.
  • the actions and terms involved in the various embodiments of the present application may refer to each other without limitation.
  • the names of messages exchanged between various devices or the names of parameters in messages are just examples, and other names may also be used in specific implementations, which are not limited.
  • the multicast in the embodiment of the present application may be replaced by terms such as broadcast, multicast, multicast communication, multicast/broadcast, or multicast/broadcast.
  • the determination in the embodiment of the present application can also be understood as creating (create) or generating (generate), the "include” in the embodiment of the present application can also be understood as “carry” or “include”, etc., the “include” in the embodiment of the present application “Disconnect” can also be understood as “release” or “stop” or “pause”. It is described uniformly here, and this embodiment of the present application does not specifically limit it.
  • Figure 5a is a multicast service communication method provided by the embodiment of the present application, which can be applied in the following scenario: when a terminal joining a multicast group through a certain access network device is in an inactive state , and move from the access network device to other access network devices. For example, taking the terminal in FIG. 2 as an example, the terminal moves from the first access network device to the second access network device, the terminal joins the multicast group through the first access network device and the terminal is in an inactive state.
  • the method may include:
  • S501 The terminal determines that the terminal is located outside the first area.
  • the terminal is located outside the first area can also be alternatively described as the terminal is not in the first area, or the terminal leaves the first area, or the terminal leaves the signal coverage area of the first access network device, or is not in the first access network device
  • the signal coverage area, etc., are not limited.
  • the terminal may be any terminal that joins the multicast group corresponding to the multicast service through the first access network device in Figure 2, and the terminal may be in an inactive state.
  • the first access network device may be an access network device corresponding to the cell where the terminal resides, and the first access network device can establish an RRC connection with the terminal, and provide network services for the terminal through the RRC connection.
  • the first access network device may be referred to as a source access network device.
  • the first access network device may have the UE context of the terminal and the context of the multicast service.
  • the context of the multicast service may include information about terminals joining the multicast group, for example, it may include the number of terminals joining the multicast group, or include the number of terminals joining the multicast group and the terminals joining the multicast group identification information, etc.
  • the UE context of the terminal may include identification information of the multicast service.
  • the process for the terminal to join the multicast group corresponding to the multicast service through the first access network device may refer to the process shown in FIG. 1 , which will not be described again.
  • the multicast service may refer to a service for multiple terminals, for example, the multicast service may be a TV program, a file transmission service, voice or video communication within a group, and a broadcast service within a vehicle fleet.
  • Multiple terminals targeted by the multicast service can join a group, which can be referred to as a multicast group corresponding to the multicast service, and all terminals in the multicast group can be authorized or need not be authorized to receive this Multicast service data. That is, the multicast group corresponding to the multicast service can be a combination of multiple terminals receiving data from the multicast service, for example, the multicast group can be a fleet receiving orders from the same command center or a user group receiving the same TV program group etc.
  • the first area may be the service area of the first access network device, or the signal coverage area of the first access network device, or one or more cells corresponding to the first access network device.
  • the area may be referred to as a radio access network-based notification area (RAN-based notification area, RNA) of the first access network device.
  • Terminals in the first area can receive network services provided by the first access network device and perform business data transmission with the first access network device. For example, the terminal can receive multicast messages from the first access network device in the first area. business data.
  • the first area may be obtained by dividing the signal coverage area of the access network device at the granularity of the access network device or cell.
  • the first area may be the entire signal coverage area of the first access network device.
  • the first area includes all cells under the signal coverage of the first access network device by default.
  • the first area may include one or more cells that can provide multicast service under the coverage of the first access network device, and the cells may be described as sectors instead.
  • one cell may correspond to one or multiple carriers, the first access network device may transmit multicast service data to the terminal on the carrier corresponding to the cell.
  • the first area may be called a multicast service service area/multicast service reception area .
  • a cell capable of providing a multicast service may refer to a cell capable of performing data transmission of a multicast service on a carrier corresponding to the cell.
  • the first area may be the entire signal coverage area of the base station 1, and the first area may include cell 1, cell 2, and cell 3 when access network equipment is used as the granularity. In the case of using cells as the granularity, the first area may include cell 1 and cell 2 .
  • the first area may be indicated/configured to the terminal by the first access network device, for example, the terminal may receive the information of the first area from the first access network device, and the information of the first area may indicate the
  • the information of the first area may be one or more of the following: the identifier of the first access network device, one or more information contained in the first access network device An identification (cell ID(s)) of a cell, a list of cells included in the first access network device (cell ID list), and one or more tracking areas supported/included/belonging to by the first access network device Identification (tracking area ID(s), TAI(s)), one or more tracking area lists (TA List) supported/included/belonging to by the first access network device, name of the first access network device (RAN Node Name), one or more physical cell identifiers (physical cell identifier, PCI(s)) included in the first access network device, a list of physical
  • the identification of access network equipment can be the global access network of the first access network equipment
  • the device identification (global gNB ID) or the radio access network node name (RAN node name) of the first access network device or the global radio access network node identification (global RAN Node ID) of the first access network device, or the first access network device
  • a radio access network node identifier (RAN Node ID, etc.) of an access network device.
  • the information of the first area may include information that can provide multicast services under the signal coverage of the first access network device.
  • the cell identifier may be a physical cell identifier (physical cell identifier, PCI) or a global cell identity (cell global identity, CGI), etc. of the cell.
  • the information of the first area is carried in a newly added signaling message and sent to the terminal, for example, it may be carried in a newly added RRC message and sent to the terminal.
  • the information of the first area may be carried in the second RRC message and sent to the terminal, The second RRC message can be used to suspend the RRC connection of the terminal, so that the terminal is in an inactive state.
  • the second RRC message can be an RRC connection suspend (RRC connection suspend) message, or an RRC release message carrying a suspension configuration (release with suspend configuration ), or an RRC message used to suspend/suspend/deactivate the RRC connection, etc., are not limited.
  • the first area can be indicated to the terminal during the process of suspending the RRC connection of the terminal, saving signaling overhead.
  • the second RRC message may also carry the wireless network temporary identifier of the terminal (such as an inactive radio network temporary identifier (I-RNTI) of the terminal), the Wireless network temporary identification and other information are not limited.
  • I-RNTI inactive radio network temporary identifier
  • the temporary wireless network identifier of the terminal may include a plurality of binary bits, and the temporary wireless network identifier of the terminal may be the identity of the terminal when it is in the signal coverage area (or cell) of the first access network device.
  • the terminal The wireless network temporary identity of the terminal can be used to identify the terminal in the signal coverage area/cell of the first access network device, and the wireless network temporary identity of the terminal is only applicable to the signal of the access network device that assigns the wireless network temporary identity to the terminal In the coverage area/cell, the identifier is at the granularity of a certain access network device/cell, not at the granularity of the entire communication network.
  • the wireless network temporary identifier of the terminal is assigned by the access network device that currently provides network services for the terminal.
  • the wireless network temporary identifier of the terminal is assigned by the first access network device.
  • the wireless network temporary identifier of the terminal may include the identifier of the first access network device, or may alternatively be described as being able to resolve/obtain the identifier of the first access network device from the wireless network temporary identifier of the terminal.
  • the first access network device may calculate the identifier of the cell where the terminal is located and the identifier information of the terminal according to a preset algorithm to obtain the temporary wireless network identifier of the terminal, or calculate the identifier and the identifier of the first access network device according to a preset algorithm.
  • the identification information of the terminal is calculated to obtain the temporary wireless network identification of the terminal.
  • the design form of the wireless network temporary identifier of the terminal refers to what is described in 3GPP communication protocol 38.300, and is not limited.
  • the wireless network temporary identifier of the multicast service corresponds to the multicast service
  • the identification information of the multicast service can be used to add downlink control information (such as DCI) for scheduling data of the multicast service.
  • the identification information can descramble the downlink control information, and obtain the data of the multicast service according to the descrambled downlink control information, so as to ensure the security of the data transmission of the multicast service.
  • the radio network temporary identifier of the multicast service may be a G-RNTI of the multicast service or a multicast radio network temporary identifier (multicast RNTI, M-RNTI).
  • the wireless network temporary identifier of the multicast service can be obtained/assigned according to the identification information of the multicast service, for example, the wireless network temporary identifier of the multicast service can be obtained by calculating the identification information of the multicast service according to a preset algorithm.
  • the first access network device may determine to suspend the RRC connection of the terminal in any of the following ways:
  • the first access network device receives an N2 suspend response (N2 suspend response) sent by the mobility management network element (such as AMF), and the N2 suspend response can be used to indicate the suspension of communication between the mobility management network element and the first access network device.
  • N2 suspend response sent by the mobility management network element (such as AMF)
  • the N2 suspend response can be used to indicate the suspension of communication between the mobility management network element and the first access network device.
  • the first access network device determines to suspend the RRC connection of the terminal.
  • the first access network device receives the path switch request response (path switch request response) sent by the mobility management network element, and the path switch request response can be used to instruct to switch the transmission path of the terminal from the first access network device to another
  • the access network device determines to suspend the RRC connection of the terminal.
  • the first access network device determines that the inactivity timer corresponding to the terminal expires (inactivity timer)/overtime, then the first access network device determines that the terminal has not received data for a long time, and determines to disconnect the RRC between the terminal and it connect.
  • the inactivity timer may be used to determine whether the terminal has not transmitted service data for a long time.
  • the inactivity timer is correspondingly set with a preset working duration.
  • the inactivity timer can start working/running when the terminal stops business data transmission (such as receiving/sending business data). Within the preset working time, if the terminal is transmitting business data, it will stop working/no longer running, and it will run at this time The time is less than the preset working time, otherwise, within the preset working time, if the terminal does not transmit service data, the inactivity timer works/runs until the preset working time ends. For example, when the terminal starts to stop business data transmission (such as receiving/sending business data), start/run the inactivity timer.
  • the inactivity timer runs for a preset working time, it indicates that the terminal has not performed business for a long time For data transmission, its RRC connection can be disconnected/suspended to save power consumption of the terminal.
  • the preset duration of the inactive timer can be set as required without limitation.
  • the terminal may determine the first area according to the information of the first area. Subsequently, if the terminal disconnected from the RRC connection has a business transmission requirement during the movement, the terminal can periodically detect whether there is a suitable access network device around it that can provide network services, for example, the terminal can detect the surrounding access network
  • a synchronization signal (synchronize signal, SS) sent by a device (such as a primary synchronization signal (primary synchronization signal, PSS)/secondary synchronization signal (secondary synchronization signal, SSS)
  • the SS may include a cell identifier.
  • the terminal selects the SS with higher signal quality, obtains the cell identifier according to the selected SS, and determines to access the cell identified by the cell identifier, and the access network device (such as the second access network device) corresponding to the cell provides it Provide network services.
  • the terminal finds that the cell identified by the obtained cell identifier is not included in the first area, it determines that the terminal leaves the first area, is outside the first area, and leaves the first access network device. Signal coverage area.
  • the terminal can check whether the calculated identifiers of the cells are included in the information of the first area, and if not, determine the cell identified by the cell Not included in the first zone.
  • the terminal may calculate an identifier of an access network device according to the acquired identifier of the cell, if the calculated identifier of the access network device If the identifiers of the network access devices are different, it is determined that the cell identified by the cell is not included in the first area.
  • the calculation relationship between the identifier of the cell and the identifier of the access network device corresponding to the cell can refer to the prior art, and will not be repeated here.
  • S502 The terminal sends the first information to the second access network device.
  • the second access network device receives the first information.
  • the second access network device may be an access network device to which the terminal currently resides/belongs to/corresponds to a cell.
  • the second access network device is different from the first access network device, and the cell where the terminal currently resides/is located is outside the first area.
  • the first information may be used to notify the terminal to move out of the first area, and the first information may include identification information of the multicast service, and may also include other information, such as a temporary wireless network identification of the terminal.
  • identification information of the multicast service and the temporary wireless network identification of the terminal, reference may be made to the above, and details are not repeated here.
  • the terminal may carry the first information in the first RRC message, and send the first RRC message to the second access network device through a signaling radio bearer (such as SRBO).
  • a signaling radio bearer such as SRBO
  • the first RRC message is sent to the second access network device through other signaling messages, which is not limited.
  • the first RRC message may be used to request to resume the RRC connection of the terminal.
  • the first RRC message may be an RRC resume request (RRC resume request), that is, the first information is sent to the second access network device through the RRC resume process, so as to reduce signaling overhead.
  • RRC resume request RRC resume request
  • the first RRC message may be a special RRC message, and the RRC message may be used to trigger the second access network device to send the first access network device to update the context of the multicast service.
  • Two information, or the RRC message may be used to trigger the second access network device to send the third information for extracting the UE context of the terminal from the first access network device to the first access network device.
  • S503 The second access network device sends second information to the first access network device according to the first information.
  • the first access network device receives the second information, and performs S504a.
  • the second access network device sends third information to the first access network device according to the first information, and correspondingly, the first access network device receives the third information, and performs S504b.
  • the second information may be used to update the context of the multicast service
  • the third information may be used to extract the UE context of the terminal from the first access network device.
  • the second information and the third information may include identification information of the multicast service, and may also include other information, for example, may also include identification information of a terminal.
  • the first information includes the temporary wireless network identifier of the terminal
  • the second information and the third information may include the temporary wireless network identifier of the terminal (such as the I-RNTI of the terminal), and/or Identification information of the terminal.
  • the second information and the third information may be carried in a retrieve UE context request (retrieve UE context request), and the retrieve UE context request may be used to request provision of UE context of the terminal.
  • the second information and the third information may be carried in a newly added message, for example, may be carried in an Xn message.
  • the second information and the third information may be carried in a UE context release (UE context request) request, and the UE context release request may be used to request to release the UE context of the terminal.
  • the temporary wireless network identification of the terminal and the identification information of the terminal, reference may be made to the above, and details are not repeated here.
  • the first information includes identification information of the multicast service
  • the second access network device may determine to send the second Information or the third information, because it is not known which access network device it is, the second access network device sends the second information or the third information to one or more access network devices around it and establishes an Xn connection with it
  • the one or more access network devices include a first access network device.
  • the first information includes identification information of the multicast service and a temporary wireless network identifier of the terminal
  • the temporary wireless network identifier of the terminal includes identification information of the first access network device
  • the first access network device may The wireless network temporary identifier acquires the identifier of the first access network device, and sends the second information or the third information to the first access network device according to the identifier of the first access network device.
  • S504a The first access network device updates the context of the multicast service according to the second information.
  • the second information includes identification information of the multicast service
  • updating the context of the multicast service by the first access network device according to the second information may include: the first access network device finds the multicast service according to the identification information of the multicast service If the context of the multicast service includes the number of terminals that join the multicast group through the first access network device, update the context of the multicast service to join the multicast group through the first access network device The number of terminals, such as subtracting 1 from the number of terminals. For example, suppose the multicast service is MBS1, the first access network device is base station 1, and the second access network device is base station 2.
  • the terminals that join the multicast group corresponding to MBS1 through base station 1 include UE1-UE4, and the context of MBS1
  • the number of terminals that join the multicast group through base station 1 included in is 4.
  • base station 1 receives the second information ⁇ MBS1 ⁇ from base station 2, then base station 1 finds the context of MBS1, and passes the context of MBS1 to The number of terminals joined by base station 1 to the multicast group is updated to 3.
  • the second information includes identification information of the multicast service and identification information of the terminal
  • updating the context of the multicast service by the first access network device according to the second information may include: the first access network device updates the context of the multicast service according to the multicast
  • the identification information of the multicast service is used to find the context of the multicast service. If the context of the multicast service includes the number of terminals joining the multicast group through the first access network device, update the context of the multicast service through the first access network device.
  • the network device adds the number of terminals to the multicast group, for example, the number of terminals is reduced by 1, etc.
  • the first access network device may delete the terminal according to the identification information of the terminal included in the second information The identification information of the terminal in the context of the multicast service.
  • the first access network device is base station 1
  • the second access network device is base station 2.
  • the terminals that join the multicast group corresponding to MBS1 through base station 1 include UE1-UE4, and the context of MBS1
  • the number of terminals that join the multicast group through base station 1 included in is 4, and the identification information ⁇ UE1, UE2, UE3, UE4 ⁇ of the terminals that join the multicast group through base station 1, at this time, if base station 1 receives a message from For the second information ⁇ MBS1, UE1 ⁇ of base station 2, base station 1 finds the context of MBS1, updates the number of terminals joining the multicast group through base station 1 in the context of MBS1 to 3, and deletes UE1 in the context of MBS1, The identification information of the terminals joining the multicast group through the base station 1 is updated to ⁇ UE2, UE3, UE4 ⁇ .
  • the second information includes the wireless network temporary identifier of the terminal and/or the identification information of the terminal
  • the updating of the context of the multicast service by the first access network device according to the second information may include: the first access network device Find the UE context of the terminal according to the wireless network temporary identifier of the terminal and/or the terminal's identification information, obtain the identification information of the multicast service from the UE context, find the context of the multicast service according to the identification information of the multicast service, and update the multicast
  • the number of terminals joining the multicast group through the first access network device for example, the number of terminals is reduced by 1, and so on. And/or, delete the identification information of the terminal in the context of the multicast service.
  • the first access network device is base station 1
  • the second access network device is base station 2.
  • the terminals that join the multicast group corresponding to MBS1 through base station 1 include UE1-UE4, and the context of MBS1
  • the number of terminals that join the multicast group through base station 1 included in is 4, and the identification information ⁇ UE1, UE2, UE3, UE4 ⁇ of the terminals that join the multicast group through base station 1, at this time, if base station 1 receives a message from The second information of base station 2 ⁇ UE1 and/or UE1's I-RNTI ⁇ , then base station 1 finds UE1's UE context according to ⁇ UE1 and/or UE1's I-RNTI ⁇ , and obtains MBS1 from UE1's UE context, according to MBS1 Find the context of MBS1, update the number of terminals joining the multicast group through base station 1 in the context of MBS1 to 3, and in the case that the second information includes UE1, delete UE
  • the first access network device updates the number of terminals joining the multicast group through the first access network device according to the third information.
  • the third information includes terminal identification information
  • the first access network device updating the number of terminals joining the multicast group through the first access network device according to the third information may include: the first access network device according to The UE context of the terminal is found by the identification information of the terminal, and the UE context of the terminal is extracted to the second access network device.
  • the first access network device may no longer have/exist/release the UE context of the terminal.
  • the third information is carried in the UE context release request
  • the first access network device releases the UE context of the terminal according to the UE context release request, and can further return a UE context release response to the second access network device, and the UE context release response It can be used to indicate that the UE context of the terminal has been released.
  • the first access network device extracts the UE context of the terminal to the second access network device, it can still be saved as the UE context of the terminal, except that there is no identification information of the multicast service in the UE context of the terminal, that is, the UE context of the terminal is deleted.
  • Identification information of the multicast service in the UE context of the terminal For the first access network device, the number of UE contexts including the identification information of the multicast service stored in the first access network device is reduced by 1, so the number determined according to the number of UE contexts of the identification information of the multicast service The number of terminals joining the multicast group through the first access network device is also reduced by 1, and the number of terminals joining the multicast group through the first access network device is updated.
  • UE1-UE5 joins a multicast group through base station 1
  • the five UE contexts corresponding to UE1-UE5 all have multicast service identification information
  • UE1 no longer accepts the multicast service provided by base station 1.
  • Base station 1 no longer has UE context of UE1, but there are four UE contexts corresponding to UE2-UE5.
  • UE context; or, base station 1 retains the UE context of UE1, but deletes the identification information of the multicast service in the UE context of UE1.
  • the number of UE contexts including the identification information of the multicast service is 4 UE contexts corresponding to UE2-UE5, and the number of UE contexts including the identification information of the multicast service is determined by base station 1 to join the multicast group
  • the number of terminals also becomes 4.
  • the third information may also include identification information of the multicast service
  • the first access network device updating the number of terminals joining the multicast group through the first access network device according to the third information may also include: the first access network device The network access device finds the context of the multicast service according to the identification information of the multicast service, and updates the number of terminals joining the multicast group through the first access network device in the context of the multicast service, for example, subtracting 1 from the number of terminals.
  • the first access network device may carry the UE context of the terminal in the response message corresponding to the third information and send it to the second access network device, for example, carry it in the UE context extraction response and send it to the second access network device.
  • network equipment may carry the UE context of the terminal in the response message corresponding to the third information and send it to the second access network device, for example, carry it in the UE context extraction response and send it to the second access network device.
  • the method may also include S505-S514:
  • the second access network device interacts with the terminal to complete RRC recovery, for example, the second access network device sends RRC resume (RRC resume) to the terminal, and the terminal sends RRC resume complete (RRC resume complete) to the access network device.
  • RRC resume RRC resume
  • RRC resume complete RRC resume complete
  • the second access network device sends an N2 Path Switch Request (N2 Path Switch Request) to the mobility management network element.
  • N2 Path Switch Request N2 Path Switch Request
  • the mobility management network element receives the N2 path switching request.
  • the N2 path switching request may include the QFI of the unicast QF that is successfully allocated to the radio bearer among the unicast QF included in the PDU session of the terminal, and/or the unsuccessful The QFI of the unicast QF that allocates the radio bearer; it can also include the QFI of the multicast QF that has successfully allocated the radio bearer among the multicast QF of the multicast service, and/or the QFI of the unsuccessful allocation of the radio bearer (or the failure to establish the radio bearer) QFI for multicast QF.
  • the N2 path switching request may include the QFI of the unicast QF that is successfully allocated to the radio bearer among the unicast QFs included in the PDU session of the terminal, and/or the unsuccessful Allocate the QFI of the unicast QF of the radio bearer, wherein the unicast QF includes the unicast QF corresponding/mapped by the multicast QF.
  • the N2 path switching request may be encapsulated in an N2 SM message.
  • the N2 path switch request may also include tunnel endpoint identification information allocated by the second access network device.
  • the N2 path switching request also includes location information (location information) of the terminal and the like.
  • S507 The mobility management network element sends a PDU session context update request to the session management network element according to the N2 path switching request.
  • the session management network element receives the PDU session context update request.
  • the PDU session context update request may include the information included in the N2 SM message in S506.
  • location information of the terminal and the like are also included.
  • the session management network element modifies the N4 session with the user plane network element according to the PDU session context update request. For example, the session management network element sends an N4 session modification request to the user plane network element.
  • the user plane network element receives the N4 session modification request, returns the N4 session modification response to the session management network element, and the session management network element receives the N4 session modification response.
  • the N4 session modification request (N4 session modification request) may carry the tunnel endpoint identification information allocated by the second access network device.
  • the N4 session update request may also include the tunnel endpoint identifier information allocated to the user plane network element by the session management network element. If the tunnel endpoint identifier information of the user plane network element is allocated by the user plane network element, the N4 session modification response carries the tunnel endpoint identifier information of the user plane network element.
  • the tunnel endpoint identifier information of the second access network device and the tunnel endpoint identifier of the user plane network element are used to establish a PDU session between the second access network device and the user plane network element.
  • message 01 may be used to instruct MB-SMF to notify MB-UPF to establish a tunnel with UPF.
  • Message 01 may include the tunnel endpoint identification information of the user plane network element, and the tunnel endpoint identification information of the user plane network element may be used to establish a tunnel for transmitting multicast service data between the user plane network element and the MB-UPF.
  • the tunnel endpoint identification information of the plane network element may be allocated by the session management network element.
  • MB-SMF sends message 02 to MB-UPF according to message 01.
  • MB-UPF receives message 02.
  • the message 02 may include the tunnel endpoint identifier information assigned by the MB-SMF to the MB-UPF and the tunnel endpoint identifier information of the user plane network element described in S509.
  • S511 The MB-SMF sends message 03 to the session management network element.
  • the session management network element receives message 03.
  • message 03 may include MB-UPF tunnel endpoint identification information.
  • the session management network element may modify the N4 session with the user plane network element after receiving the message 03.
  • the session management network element sends an N4 session modification request carrying the MB-UPF tunnel endpoint identification information to the user plane network element UPF,
  • the user plane network element receives the N4 session modification request, and returns an N4 session modification response to the session management network element.
  • the session management network element sends a PDU session context update response to the mobility management network element.
  • the mobility management network element receives the PDU session context update response.
  • the PDU session context update response (Nsmf_PDUSession_UpdateSMContext response) may carry the tunnel endpoint identification information assigned by the session management network element to the user plane network element.
  • the mobility management network element sends an N2 path switching request response to the second access network device.
  • the N2 path switch response may include the tunnel endpoint identification information assigned by the session management network element to the user plane network element, and the like.
  • the second access network device sends a UE context release (UE context release) request to the first access network device.
  • the first access network device receives the UE context release request, and releases the UE context of the terminal and other resources corresponding to the terminal, such as the PDU session of the terminal, according to the UE context release request.
  • UE context release UE context release
  • the source access network device (such as the first access network device) is triggered in time to update the number of terminals joining the multicast group through the first access network device, so that The number of terminals that the network access device joins the multicast group conforms to the current actual situation of the terminals that join the multicast group through the first access network device, so that the first access network device joins the multicast group through the first access network device according to the actual situation.
  • the number of terminals in the group adjusts the transmission resources of the multicast service in time to improve resource utilization and the like.
  • the terminal can also establish an RRC connection with the second access network device, and the second access network device interacts with the core network device to establish resources for transmitting multicast service data for the terminal again, so as to ensure that the terminal passes through the second access network device.
  • the network equipment receives the data of the multicast service.
  • the multicast group includes Terminal 1, Terminal 2, and Terminal 3, wherein Terminal 2 and Terminal 3 are in the idle state, and Terminal 1 is in the RRC connection state. At this time, only Terminal 1 can receive the multicast service sent by the access network device. data, while Terminal 2 and Terminal 3 cannot receive data of the multicast service because they are in an idle state.
  • the embodiment of the present application also provides a multicast communication method, which may include: the access network device allocates the multicast service according to the identification information of the multicast service The wireless network temporary identifier of the multicast service, obtaining the scrambled downlink control information according to the wireless network temporary identifier of the multicast service, and sending the fourth information and the scrambled downlink control information, the fourth information includes the identification information of the multicast service and The wireless network temporary identifier of the multicast service.
  • the terminal in the cell covered by the access network device can receive the fourth information, descramble the downlink control information according to the fourth information, and receive the multicast service data from the access network device according to the descrambled downlink control information.
  • the manner may be described with reference to the embodiment corresponding to FIG. 6 .
  • FIG. 6 is a communication method for a multicast service provided by an embodiment of the present application. As shown in FIG. 6, the method may include:
  • the access network device allocates a wireless network temporary identifier of the multicast service according to the identifier information of the multicast service.
  • the access network device may be any access network device in FIG. 2 , such as the first access network device or the second access network device, etc., without limitation.
  • the wireless network temporary identifier of the multicast service corresponds to the multicast service
  • the wireless network temporary identifier of the multicast service is used for scrambling and scheduling the downlink control information (DCI) of the data of the multicast service to ensure that the multicast Security of business data transmission.
  • the access network device may use a preset algorithm to calculate the identification information of the multicast service to obtain the wireless network temporary identification of the multicast service. Specifically, for the related description of the identification information of the multicast service and the wireless network temporary identification of the multicast service, reference may be made to the above, and details are not repeated here.
  • the access network device obtains scrambled downlink control information according to the wireless network temporary identifier of the multicast service.
  • the downlink control information may be used to schedule a physical downlink shared channel (physical downlink shared channel, PDSCH) carrying multicast service data, and the downlink control information may indicate the time-frequency resource position of the PDSCH carrying multicast service data.
  • PDSCH physical downlink shared channel
  • the downlink control information may include multiple parity bits, the length of the multiple parity bits is the same as the length of the wireless network temporary identifier of the multicast service, and the access network device may Scramble processing is performed on the parity bit to obtain scrambled downlink control information.
  • the scrambling processing method may be a preset calculation rule, and the method may refer to the prior art, and details are not repeated here.
  • the access network device sends fourth information and scrambled downlink control information.
  • the terminal receives the fourth information and the scrambled downlink control information from the access network device.
  • the fourth information may include identification information of the multicast service and a temporary wireless network identification of the multicast service.
  • identification information of the multicast service and the temporary wireless network identifier of the multicast service reference may be made to the above, and details are not repeated here.
  • the embodiment of the present application does not limit the order of sending the fourth information and the scrambled downlink control information, the fourth information may be sent first, and then the scrambled downlink control information may be sent at the same time, without limitation.
  • the terminal may store the received fourth information, for example, correspondingly store the identification information of the multicast service included in the fourth information and the temporary wireless network identifier of the multicast service in the terminal. So that when the subsequent terminal is interested in the multicast service, it can descramble the downlink control information according to the wireless network temporary identifier of the multicast service, and receive the data of the multicast service.
  • the access network device may send the scrambled downlink control information on a resource (such as a control resource set (CORESET)) corresponding to the downlink control information.
  • a resource such as a control resource set (CORESET)
  • the resource corresponding to the downlink control information can be configured by the access network device and indicated to the terminal in the signal coverage area of the access network device.
  • the specific configuration method can refer to the prior art, and will not be described in detail.
  • the access network device may broadcast the fourth information, so that multiple terminals within the signal coverage area of the access network device may receive the fourth information by broadcast.
  • the process of sending the fourth information by broadcast is shown in Figure 7, which may include any of the following three ways:
  • Mode 1 carry the fourth information in a system information block (system information block, SIB) and broadcast it.
  • SIB system information block
  • the access network device may generate fourth information, and submit the fourth information to the radio resource control (radio resource control, RRC) layer of the access network device, and the RRC of the access network device may obtain the
  • the received fourth information is carried in the system information block (symbol information block, SIB) and submitted downward to the radio link control (radio link control, RLC) layer of the access network device, and the RLC layer of the access network device will carry the first
  • the four-information SIB is sent to the downlink-shared channel (DL-SCH) of the media access control (media access control, MAC) layer of the access network device through the broadcast control channel (broadcast control channel, BCCH) in the logical channel ), transmitted to the physical downlink shared channel (physical downlink shared channel, PDSCH) in the physical layer through the DL-SCH, and broadcasted through the PDSCH.
  • DL-SCH downlink-shared channel
  • BCCH broadcast control channel
  • Method 2 Carry the fourth information in a master information block (master information block, MIB) and send it out.
  • MIB master information block
  • the RRC layer of the access network device may carry the obtained fourth information in the MIB, and send the MIB to the RLC layer of the access network device, and the RLC layer of the access network device passes
  • the BCCH is sent to the broadcast channel (broadcast channel, BCH) in the MAC layer of the access network device, transmitted to the physical broadcast channel (physical broadcast channel, PBCH) through the BCH, and broadcasted through the PBCH.
  • BCH broadcast channel
  • PBCH physical broadcast channel
  • Manner 3 Carry the fourth information in a paging (paging) message and broadcast it.
  • the RRC layer of the access network device may carry the acquired fourth information in a paging (paging) message, and send the paging message to the paging control of the RLC layer of the access network device
  • the channel (paging control channel, PCCH) is sent to the paging channel (paging channel, PCH) of the MAC layer of the access network device through the PCCH, transmitted to the PDSCH through the PCH, and broadcasted through the PDSCH.
  • Mode 4 Carry the fourth information in the RRC message, and broadcast the RRC message through the signaling radio bearer.
  • the signaling radio bearer may be SRBO.
  • the RRC layer of the access network device may carry the acquired fourth information in a downlink common control channel-message (DL-CCCH-message) , sending the DL-CCCH-message carrying the fourth information to the common control channel (common control channel, CCCH) in the RLC layer of the access network device through SRB0, sending the fourth information to the DL-SCH through the CCCH, and passing the DL - The SCH is transmitted to the PDSCH and broadcasted through the PDSCH.
  • DL-CCCH-message downlink common control channel-message
  • CCCH common control channel
  • the terminal may receive the PDSCH carrying the fourth information, and obtain the fourth information from the PDSCH; or, in the situation shown in the above method 2, the terminal may Receive the PBCH, and acquire fourth information from the PBCH.
  • S604 The terminal receives data of the multicast service from the access network device according to the fourth information and the scrambled downlink control information.
  • the terminal may determine that the terminal is interested in the multicast service according to the identification information of the multicast service carried in the fourth information, and then the terminal uses the wireless network temporary identifier of the multicast service carried in the fourth information to scramble the received If the descrambling is successful, the PDSCH from the access network device is received at the time-frequency resource position indicated by the descrambled downlink control information, and the data of the multicast service is obtained from the PDSCH.
  • the embodiment of the present application does not limit the execution order of each step in the process.
  • Information you can also use the wireless network temporary identifier of the multicast service to obtain the descrambled downlink control information first, and then determine that the terminal is interested in the multicast service, and then receive the data of the multicast service according to the descrambled downlink control information, without limitation .
  • the terminal is interested in the multicast service, it can be replaced by describing that the terminal has a need to receive multicast service data, or the terminal expects to receive multicast service data, or the terminal has a multicast service need.
  • the identification information of the multicast service and the wireless network temporary identifier of the multicast service are sent, so that the terminals in the multicast group Receive the identification information of the multicast service and the wireless network temporary identification of the multicast service, and in the case of being interested in the multicast service, use the wireless network temporary identification of the multicast service to receive the data of the multicast service, and solve the problem of being idle
  • a terminal in an active state or an inactive state cannot receive data of a multicast service because the RRC connection with the access network device is disconnected.
  • each node such as a terminal, an access network device, etc.
  • each node includes a corresponding hardware structure and/or software module for performing each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. middle.
  • the above-mentioned integrated modules can be implemented in the form of hardware or in the form of software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic, and is only a logical function division, and there may be other division methods in actual implementation.
  • Fig. 8 shows a structural diagram of a communication device 80
  • the communication device 80 may be a terminal, a chip in the terminal, a system on chip, or other devices capable of realizing the functions of the terminal in the above method.
  • the communication device 80 may be used to execute the functions of the terminal involved in the foregoing method embodiments.
  • the communication device 80 shown in FIG. 8 includes: a processing unit 801 , a receiving unit 802 , and a sending unit 803 .
  • the processing unit 801 is configured to determine that the terminal is located outside the service area of the first access network device. For example, the processing unit 801 may be used to support the communication device 80 to execute S501.
  • the sending unit 803 is configured to send first information for notifying the terminal to move out of the first area to the second access network device.
  • the sending unit 803 may support the communication device 80 to execute S502.
  • the receiving unit 802 is configured to receive the fourth information including the identification information of the multicast service and the wireless network temporary identifier of the multicast service from the access network device, and the scrambled downlink control information, according to the The fourth information and the scrambled downlink control information are used to receive the data of the multicast service from the access network device.
  • the receiving unit 802 may support the terminal to perform S603 and S604.
  • the specific implementation of the communication device may refer to the first aspect or any possible design of the first aspect or the fifth aspect or any possible design of the fifth aspect, the behavior function of the terminal in the method described above, I won't repeat it.
  • the communication device 80 is used to perform the function of a terminal in the multicast service communication method shown in the methods shown in FIGS.
  • the communication device 80 shown in FIG. 8 includes: a processing module and a communication module.
  • the processing module is used to control and manage the actions of the communication device 80 , for example, the processing module may integrate functions of the processing unit 801 .
  • the communication module may integrate the functions of the sending unit 803 and the receiving unit 802, and perform S502, S603, S604 and communicate with other network entities, such as communication with the functional modules or network entities shown in FIG. 3 .
  • the communication device 80 may also include a storage module for storing instructions and/or data. When the instruction is executed by the processing module, the processing module is made to implement the above method on the terminal side.
  • the processing module may be a processor, a controller, a module or a circuit. It can realize or execute various exemplary logic blocks described in conjunction with the disclosed content of the embodiments of the present application.
  • the communication module may be a transceiver circuit, a pin, an interface circuit, a bus interface, or a communication interface.
  • the storage module may be a memory.
  • the processing module is a processor
  • the communication module is a communication interface
  • the storage module is a memory
  • the communication device 80 involved in this embodiment of the present application may be the communication device 400 shown in FIG. 4 .
  • FIG. 9 shows a structural diagram of a communication device 90, which may be a second access network device, a chip in the second access network device, a system on chip, or other devices capable of implementing the second access network in the above method.
  • the communication device 90 may be used to execute the functions of the second access network device involved in the foregoing method embodiments.
  • the communication device 90 shown in FIG. 9 includes: a receiving unit 901 and a sending unit 902 .
  • the receiving unit 901 is configured to receive first information from the terminal for notifying the terminal to move out of the first area.
  • the receiving unit 901 may support the communication device 90 to execute S502.
  • the sending unit 902 is configured to send second information or third information to the first access network device according to the first information, where the second information is used to notify the update of the context of the multicast service, and the third information is used to obtain
  • the access network device extracts the UE context of the terminal.
  • the sending unit 902 may support the communication device 90 to execute S503.
  • the communication device 90 is used to execute the function of the second access network device in the multicast service communication method shown in the method shown in FIG. 5 a , so the same effect as the above multicast service communication method can be achieved.
  • the communication device 90 shown in FIG. 9 includes: a processing module and a communication module.
  • the processing module is used to control and manage the actions of the communication device 90 .
  • the communication module can integrate the functions of the receiving unit 901 and the sending unit 902, such as performing S502, S503, etc., and communicating with other network entities, such as communication with the functional modules or network entities shown in FIG. 4 or FIG. 5a.
  • the communication device 90 may also include a storage module for storing instructions and/or data. When the instruction is executed by the processing module, the processing module is made to implement the method on the second access network device side.
  • the processing module may be a processor, a controller, a module or a circuit. It can realize or execute various exemplary logic blocks described in conjunction with the disclosed content of the embodiments of the present application.
  • the communication module may be a transceiver circuit, a pin, an interface circuit, a bus interface, or a communication interface.
  • the storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 90 involved in this embodiment of the present application may be the communication device 400 shown in FIG. 4 .
  • FIG. 10 shows a structural diagram of a communication device 100.
  • the communication device 100 may be the first access network device, a chip in the first access network device, a system-on-chip, or other devices capable of implementing the first access network in the above method.
  • the device of the function of the network equipment, etc. may be an access network device, a chip in the access network device, a system on chip, or other devices capable of realizing the functions of the access network device in the above method.
  • the communications apparatus 100 may be configured to execute the functions of the first access network device/access network device involved in the foregoing method embodiments.
  • the communication device 100 shown in FIG. 10 includes: a processing unit 1001 , a receiving unit 1002 , and a sending unit 1003 .
  • the receiving unit 1002 is configured to receive second information from the second access network device for updating the context of the multicast service, or receive from the second access network device
  • the access network device extracts the third information of the user equipment UE context of the terminal.
  • the receiving unit 1002 may support the communication device 100 to execute S503.
  • the processing unit 1001 is configured to update the context of the multicast service according to the second information; or update the number of terminals joining the multicast group through the first access network device according to the third information.
  • the processing unit 1001 and/or the sending unit 1003 may support the communication device to execute S504a and S504b.
  • the communication device 100 is used to execute the function of the first access network device in the multicast service communication method shown in the method shown in Fig. 5a-5b, so it can achieve the same effect as the above multicast service communication method.
  • the processing unit 1001 is configured to allocate a wireless network temporary identifier of the multicast service according to the identification information of the multicast service, and obtain scrambled downlink control information according to the wireless network temporary identifier of the multicast service.
  • the processing unit 1001 can be used to support the communication device 100 to execute S601 and S602.
  • the sending unit 1003 is configured to send fourth information and scrambled downlink control information.
  • the sending unit 1003 may support the communication device 100 to execute S603.
  • the communication device 100 is used to perform the function of the access network device in the multicast service communication method shown in the method shown in FIG. 6 , so it can achieve the same effect as the above multicast service communication method.
  • the communication device 100 shown in FIG. 10 includes: a processing module and a communication module.
  • the processing module is used to control and manage the actions of the communication device 100, and execute S504a, S504b, S601, S602 and so on.
  • the communication module may integrate the functions of the receiving unit 1002 and the sending unit 1003, such as performing S603, etc., and communicating with other network entities, such as communication with the functional modules or network entities shown in FIG. 4 or FIG. 5a.
  • the communication device 100 may also include a storage module for storing instructions and/or data. When the instruction is executed by the processing module, the processing module is made to implement the above method of the first access network device/access network device.
  • the processing module may be a processor, a controller, a module or a circuit. It can realize or execute various exemplary logic blocks described in conjunction with the disclosed content of the embodiments of the present application.
  • the communication module may be a transceiver circuit, a pin, an interface circuit, a bus interface, or a communication interface.
  • the storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 100 involved in this embodiment of the present application may be the communication device 400 shown in FIG. 4 .
  • the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or Execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
  • a general purpose processor may be a microprocessor or any conventional processor or the like. The steps of the methods disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.
  • the memory may be a non-volatile memory, such as a hard disk (hard disk drive, HDD) or a solid-state drive (solid-state drive, SSD), etc., and may also be a volatile memory (volatile memory), such as Random-access memory (RAM).
  • a memory is, but is not limited to, any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • the memory in the embodiment of the present application may also be a circuit or any other device capable of implementing a storage function, and is used for storing instructions and/or data.
  • FIG. 11 is a structural diagram of a communication system provided by an embodiment of the present application.
  • the communication system may include: a terminal 110 , a first access network device 111 and a second access network device 112 .
  • Terminal 110 may be in an inactive state.
  • FIG. 11 is only an exemplary drawing, and this embodiment of the present application does not limit the network elements and the number of network elements included in the communication system shown in FIG. 11 .
  • the terminal 110 has the function of the terminal in the method shown in the above-mentioned Fig. 5a to Fig. 5b.
  • the first access network device 111 has the function of the first access network device in the method shown in Fig. 5a to Fig. 5b above.
  • the second access network device 112 has the function of the second access network device in the method shown in Fig. 5a to Fig. 5b above.
  • FIG. 12 is a structural diagram of a communication system provided by an embodiment of the present application. As shown in FIG. 12 , the communication system may include: multiple terminals 120 and an access network device 121 . There are terminals in an inactive state or an idle state among the plurality of terminals 120 . It should be noted that FIG. 12 is only an exemplary drawing, and the embodiment of the present application does not limit the network elements and the number of network elements included in the communication system shown in FIG. 12 .
  • the terminal 120 has the function of the terminal in the method shown in FIG. 6 above.
  • the access network device 121 has the functions of the access network device in the above method in FIG. 6 .
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations, and any embodiment or design described as “exemplary” or “for example” should not be interpreted It is more preferred or more advantageous than other embodiments or design solutions.
  • the use of words such as “exemplary” or “for example” is intended to present related concepts in a specific manner for easy understanding.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc.
  • the technical features described in the “first”, “second”, “third”, “A”, “B”, “C” and “D” have no sequence or order of magnitude among the technical features described.
  • B corresponding to A means that B is associated with A.
  • B can be determined from A.
  • determining B according to A does not mean determining B only according to A, and B may also be determined according to A and/or other information.
  • connection in the embodiment of the present application refers to various connection methods such as direct connection or indirect connection to realize communication between devices, which is not limited in the embodiment of the present application.
  • Transmit in the embodiments of the present application refers to two-way transmission, including actions of sending and/or receiving, unless otherwise specified.
  • transmission in the embodiments of the present application includes sending data, receiving data, or sending data and receiving data.
  • the data transmission here includes uplink and/or downlink data transmission.
  • Data may include channels and/or signals, uplink data transmission means uplink channel and/or uplink signal transmission, and downlink data transmission means downlink channel and/or downlink signal transmission.
  • Network and “system” in the embodiments of the present application express the same concept, and the communication system is the communication network.
  • each functional module in each embodiment of the present application can be integrated into a processing In the controller, it can also be physically present separately, or two or more modules can 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 technical solutions provided by the embodiments of the present application may be fully or partially implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer may be a general computer, a dedicated computer, a computer network, a wireless control device, an access network device, a terminal or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a digital video disc (digital video disc, DVD)), or a semiconductor medium.
  • the various embodiments may refer to each other, for example, the methods and/or terms between the method embodiments may refer to each other, such as the functions and/or terms between the device embodiments Or terms may refer to each other, for example, functions and/or terms between the apparatus embodiment and the method embodiment may refer to each other.

Abstract

本申请实施例公开了一种多播业务的通信方法、装置及系统，解决处于RRC inactive态RRC inactive的终端从第一接入网设备移动到第二接入网设备的场景下，源接入网设备无法获知终端是否离开多播业务对应的多播群组，导致无法及时更新加入多播群组的终端的数量的问题。该方法可以包括：处于RRC inactive态的终端确定位于第一接入网设备的服务区域之外时，通知第二接入网设备终端离开第一区域，触发第二接入网设备通知第一接入网设备更新多播业务的上下文的第二信息，或者从第一接入网设备提取终端的UE上下文，以触发第一接入网设备更新加入多播群组的终端的数量。该方法应用于加入多播群组的终端在接入网设备之间移动的场景中。

Description

一种多播业务的通信方法、装置及系统
本申请要求于2021年06月30日提交国家知识产权局、申请号为202110745567.1、申请名称为“一种多播业务的通信方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，尤其涉及一种多播业务的通信方法、装置及系统。
背景技术
第三代合作伙伴计划(3rd generation partnership project，3GPP)网络中，存在多个终端通过接入网设备加入多播业务对应的多播群组，网络侧设备通过同一通信连接向这多个终端发送多播业务的数据的需求，即点对多点的数据传输需求，本文的多播也可以叫做组播。本文的加入多播群组也可以成为加入组播广播业务会话(MBS session)，也可以叫做参与组播广播业务会话(involved in the MBS session)。
然而，通信过程中，终端可以处于连接管理(连接管理(connection management，CM)-连接态(CM-CONNECTED)或者连接管理-空闲态(CM-IDLE)或者非激活态(可以称为包括CM连接态的RRC非激活态(CM-CONNECTED with RRC-inactive))。当终端处于非激活态时，该终端与接入网设备之间的RRC连接处于非激活态，导致接入网设备无法获知终端当前的位置，进而无法判断终端是否已离开该接入网设备的服务区域，即离开多播业务的数据对应的接收区域，无法及时更新通过该接入网设备加入该多播群组的终端的数量，无法根据通过该接入网设备加入该多播群组的终端的数量调整传输多播业务的数据的资源。
发明内容
本申请实施例提供一种多播业务的通信方法、装置及系统，以解决接入网设备无法感知处于非激活态且加入多播群组的终端离开接入网设备，导致的接入网设备无法及时更新加入多播群组的终端的数量的问题。
为达到上述目的，本申请实施例采用如下技术方案。
第一方面，提供一种多播业务的通信方法，该方法可以应用于处于RRC inactive态的终端从第一接入网设备移动到第二接入网设备，且该终端通过第一接入网设备加入多播业务对应的多播群组；该方法可以包括终端确定自己位于第一接入网设备的服务区域(本文中可以称为第一区域)之外，终端向第二接入网设备发送第一信息，第一信息可以用于通知终端移出第一区域，触发第二接入网设备向第一接入网设备发送更新多播业务的上下文的第二信息，以便于第一接入网设备更新多播业务的上下文中加入多播群组的终端的数量，或触发第二接入网设备向第一接入网设备发送用于从第一接入网设备提取终端的用户设备(user equipment，UE)上下文的第三信息，以便于第一接入网设备感知终端的UE上下文被提取，基于该提取操作更新加入多播群组的 终端的数量。
基于第一方面所述的方法，终端在发现自己移出源接入网设备的服务区域后，及时通知目标接入网设备(或者称为新接入网设备或第二接入网设备)终端移出了源接入网设备的服务区域，触发目标接入网设备根据该通知告知源接入网设备更新多播业务的上下文或者从源接入网设备提取终端的UE上下文，对于源接入网设备(比如第一接入网设备)而言，该终端离开源接入网设备管理下多播业务对应的多播群组，源接入网设备及时更新加入多播群组的终端的数量，根据更新后的加入多播群组的终端的数量及时调整传输多播业务的数据的资源，提高资源利用率。
一种可能的设计中，第一信息包括多播业务的标识信息，第一信息还可以包括终端的无线网络临时标识，无线网络临时标识包括第一接入网设备的标识，解析终端的无线网络临时标识可以获知第一接入网设备的标识，进而根据第一接入网设备的标识向第一接入网设备发送第二信息或者第三信息，通过终端的无线网络临时标识即可获知第一接入网设备，简化系统设计。
一种可能的设计中，第一信息携带在用于请求恢复(resume)终端的RRC连接的第一RRC消息中，该第一RRC消息可以是RRC恢复请求(RRC resume request)消息；或者，第一RRC消息是一条RRC消息，该第一RRC消息可以用于恢复终端的RRC连接，或者第一RRC消息用于触发第二接入网设备向第一接入网设备发送第二信息或第三消息。
基于该可能的设计，可以灵活且有效的设计第一信息的携带方式，同时在第一RRC消息为RRC恢复请求消息的情况下，可以简化系统设计且节省信令开销。
一种可能的设计中，终端向第二接入网设备发送第一信息，包括：终端通过信令无线承载向第二接入网设备发送第一信息。可选的，该信令无线承载可以是SRB0。基于该可能的设计，在终端断开RRC连接的情况下，可以通过与终端所在小区对应的信令无线承载向第二接入网设备发送第一信息，即将第一信息携带在以小区为粒度的信令无线承载上，保证该小区内包括该终端的所有终端可以成功接收到第一信息，同时简化系统设计。
一种可能的设计中，所述方法还包括：终端接收来自第一接入网设备的第一区域的信息；其中，第一区域的信息可以用于指示第一区域，比如，第一区域的信息可以是以下一种或多种：第一接入网设备的标识、第一接入网设备包括的一个或多个小区的标识(cell ID(s))、第一接入网设备包括的小区的列表(cell ID list)、第一接入网设备支持(supported)/包括/属于的一个或多个跟踪区域标识(tracking area ID(s),TAI(s))、第一接入网设备支持(supported)/包括/属于的一个或多个跟踪区域列表(TA List)、第一接入网设备的名称(RAN Node Name)、第一接入网设备包括的一个或多个物理小区标识(physical cell identifier，PCI(s))、第一接入网设备包括的物理小区标识列表(PCI list)、第一接入网设备所处位置的地理信息(例如全球定位系统(global positioning system，GPS)信息、第一接入网设备包括的一个或多个中心单元(Central Unit，CU(s))和/或分布(distributed unit，DU(s))的标识、第一接入网设备包括的CU list和/或DU list等。基于该可能的设计，可以由第一接入网设备将第一区域指示给终端，简化系统设计。
一种可能的设计中，第一区域的信息携带用于暂停终端的RRC连接的第二RRC消息中，比如，第二RRC消息可以是以下一种或多种：RRC连接暂停(RRC connection suspend)消息、携带暂停配置的RRC释放消息(release with suspend configuration)、或者是一条用于暂停(suspend)/挂起/去激活RRC连接的RRC消息等，不予限定。基于该可能的设计，可以在RRC连接暂停流程中将第一区域的信息发送给终端，简化系统设计且节省信令开销。
第二方面，本申请提供一种多播业务的通信方法，所述方法可以应用于终端从第一接入网设备移动到第二接入网设备，且所述终端处于RRC inactive态的场景中，该方法可以包括：第二接入网设备接收来自终端的第一信息，该第一信息可以用于通知终端移出第一区域(本文中可以称为第一接入网设备的服务区域)，根据第一信息，第二接入网设备向第一接入网设备发送用于更新多播业务的上下文的第二信息，以使得第一接入网设备根据第二信息更新多播业务的上下文；或向第一接入网设备发送用于从第一接入网设备提取终端的UE上下文的第三信息，以使得第一接入网设备根据第三信息更新通过第一接入网设备加入多播群组的终端的数量。
基于第二方面所述的方法，第二接入网设备可以在接收到终端发送的第一信息，获知终端离开第一区域后，向第一接入网设备发送第二信息，触发第一接入网设备更新多播业务的上下文，或向第一接入网设备发送第三信息，将终端的UE上下文提取出来。如此，对于源接入网设备(比如第一接入网设备)而言，可以获知该终端离开源接入网设备管理下多播业务对应的多播群组，源接入网设备可以及时调整加入多播群组的终端的数量，根据加入多播群组的终端的数量及时调整传输多播业务的数据的资源，提高资源利用率。
一种可能的设计中，第一信息包括多播业务的标识信息，还包括终端的无线网络临时标识，无线网络临时标识包括第一接入网设备的标识。第二接入网设备根据第一信息，向第一接入网设备发送第二信息或第三信息包括：第二接入网设备根据第一接入网设备的标识，向第一接入网设备发送第二信息或第三信息。如此，通过终端的无线网络临时标识即可获知第一接入网设备，简化系统设计。
一种可能的设计中，第二信息包括多播业务的标识信息，以便第一接入网设备可以根据多播业务的标识信息及时更新多播业务的上下文，比如更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量，简化系统设计。
一种可能的设计中，第二信息或第三信息携带在提取UE上下文请求中；或第二信息或第三信息携带在Xn消息中。基于该可能的设计，将第二信息或者第三信息携带在现有信令消息中或者携带在接入网设备之间Xn接口上的其他Xn消息中，节省信令开销，有效且灵活地实现第二信息或第三信息的发送。
第三方面，本申请实施例又提供一种多播业务的通信方法，所述方法应用于处于RRC inactive态的终端从第一接入网设备移动到第二接入网设备，且终端通过第一接入网设备加入多播业务对应的多播群组，所述方法可以包括：第一接入网设备接收来自第二接入网设备的用于更新多播业务的上下文的第二信息，根据第二信息，更新多播业务的上下文。
基于第三方面所述的方法，第一接入网设备可以在接收到第二接入网设备的指示 之后，更新多播业务的上下文，使其记录的通过第一接入网设备加入多播群组的终端的数量与实际保持一致，便于第一接入网设备根据更新后的加入多播群组的终端的数量及时调整传输多播业务的数据的资源，提高资源利用率。
一种可能的设计中，第二信息包括多播业务的标识信息，即第二接入网设备将多播业务的标识信息指示给第一接入网设备，以便第一接入网设备根据多播业务的标识信息找到多播业务的上下文，并更新多播业务的上下文，简化系统设计。
一种可能的设计中，第一接入网设备根据第二信息，更新多播业务的上下文，包括：第一接入网设备根据第二信息更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量，比如将终端的数量减1等。
一种可能的设计中，第二信息还包括终端的标识信息，第一接入网设备根据第二信息更新多播业务的上下文还可以包括：第一接入网设备根据第二信息，删除多播业务的上下文中终端的标识信息。
一种可能的设计中，第二信息包括终端的无线网络临时标识；第一接入网设备根据第二信息更新多播业务的上下文包括：第一接入网设备根据终端的无线网络临时标识，获取终端的UE上下文中多播业务的标识信息，根据获取到的多播业务的标识信息，删除多播业务的上下文中终端的标识信息，或者更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量。
基于该可能的设计，可以获取多播业务的上下文，进而删除多播业务的上下文中终端的标识信息或者更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量，使得加入多播群组的终端的数量减1，便于第一接入网设备根据加入多播群组的终端的数量及时调整传输多播业务的数据的资源，提高资源利用率。
一种可能的设计中，第二信息携带在提取UE上下文请求中或Xn消息中，节省信令开销，同时，有效且灵活地向第一接入网设备发送第二信息。
第四方面，本申请实施例还提供一种多播业务的通信方法，该方法可以应用于处于RRC inactive态的终端从第一接入网设备移动到第二接入网设备，且终端通过第一接入网设备加入多播业务对应的多播群组，所述方法包括：第一接入网设备接收来自第二接入网设备的用于从第一接入网设备提取终端的UE上下文的第三信息，根据第三信息，更新通过第一接入网设备加入多播群组的终端的数量。
基于第四方面所述的方法，可以在第二接入网设备从第一接入网设备提取终端的UE上下文的过程中，如果该终端通过第一接入网设备加入多播群组，则因该终端的UE上下文被执行提取操作，确定更新通过第一接入网设备加入多播群组的终端的数量，比如将终端的数量减1等，保证第一接入网设备记录的通过第一接入网设备加入多播群组的终端的数量与实际保持一致，便于第一接入网设备根据更新后的加入多播群组的终端的数量及时调整传输多播业务的数据的资源，提高资源利用率。
一种可能的设计中，所述方法还包括：第一接入网设备删除终端的UE上下文中多播业务的标识信息。基于该可能的设计，可以将多播业务的标识信息从UE上下文中删除，便于通过统计哪些UE上下文包括多播业务的标识信息来确定加入多播群组的终端的数量。
一种可能的设计中，第三信息包括多播业务的标识信息。第二接入网设备将多播 业务的标识信息指示给第一接入网设备，以便第一接入网设备根据多播业务的标识信息找到多播业务的上下文，并更新多播业务的上下文，简化系统设计。
一种可能的设计中，第一接入网设备根据第三信息，更新通过第一接入网设备加入多播群组的终端的数量包括：第一接入网设备根据第三信息，获取终端的UE上下文，终端的UE上下文包括多播业务的标识信息，根据多播业务的标识信息，更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量，比如将加入多播群组的终端的数量减1，便于第一接入网设备根据加入多播群组的终端的数量及时调整传输多播业务的数据的资源，提高资源利用率。
一种可能的设计中，所述方法还包括：第一接入网设备向终端发送第一区域的信息，第一区域为第一接入网设备的服务区域。基于该可能的设计，可以由第一接入网设备将自己的服务区域指示给终端，简化系统设计。
第五方面，本申请实施例还提供了一种多播业务的通信方法，所述方法包括：接入网设备根据多播业务的标识信息分配多播业务的无线网络临时标识，根据多播业务的无线网络临时标识获得加扰的下行控制信息，发送包括多播业务的标识信息以及多播业务的无线网络临时标识的第四信息、加扰的下行控制信息，以使得接收/监听到第四信息的终端根据多播业务的无线网络临时标识获得解扰的下行控制信息，根据解扰的下行控制信息接收多播业务的数据。
基于第五方面所述方法，接入网设备发送多播业务的标识信息以及多播业务的无线网络临时标识，便于当多播群组中存在处于空闲态或者非激活态的终端时，多播群组中的终端接收到多播业务的标识信息以及多播业务的无线网络临时标识，并在对该多播业务感兴趣的情况下，利用多播业务的无线网络临时标识获取解扰的下行控制信息，接收解扰的下行控制信息的调度的多播业务的数据，解决处于空闲态或者非激活态的终端，因与接入网设备断开RRC连接而无法接收到多播业务的数据的问题。
一种可能的设计中，第四信息携带在系统信息块(system information block，SIB)中；或者，第四信息携带在主信息块(master information block，MIB)中；或者，第四信息携带在寻呼(paging)消息中。基于该可能的设计，接入网设备通过多种方式有效且灵活的向小区中的终端广播/发送第四信息，使得即便断开RRC连接的终端也能够接收到第四信息。
一种可能的设计中，接入网设备发送第四信息，包括：接入网设备通过信令无线承载(signal radio bearer，SRB)发送RRC消息。基于该可能的设计，以小区为粒度，接入网设备通过小区对应的SRB向小区中的终端广播/发送第四信息，使得即便断开RRC连接的终端也能够接收到第四信息。
第六方面，本申请实施例还提供一种多播业务的通信方法，所述方法包括：终端接收来自接入网设备的包括多播业务的标识信息以及多播业务的无线网络临时标识的第四信息、加扰的下行控制信息，根据第四信息以及加扰的下行控制信息接收来自接入网设备的多播业务的数据。该终端可以处于空闲态或者非激活态。
基于第六方面所述的方法，对于加入多播群组的终端，即使该终端断开RRC连接，处于空闲态或者非激活态，也可以接收接入网设备发送的多播业务的标识信息以及多播业务的无线网络临时标识，并在对该多播业务感兴趣的情况下，利用多播业务的无 线网络临时标识获取解扰的下行控制信息，接收解扰的下行控制信息调度的多播业务的数据，解决处于空闲态或者非激活态的终端，因断开RRC连接而无法接收到多播业务的数据的问题。
一种可能的设计中，终端根据第四信息和加扰的下行控制信息，接收来自接入网设备的多播业务的数据，包括：当终端对多播业务感兴趣时，终端根据多播业务的无线网络临时标识，获得解扰的下行控制信息，根据解扰的下行控制信息接收来自接入网设备的多播业务的数据。基于该可能的设计，利用多播业务的无线网络临时标识加扰调度多播业务的数据的下行控制信息，只有该多播业务的数据才有该加扰的下行控制信息调度，保证多播业务的数据的传输的安全性，简化系统设计。
一种可能的设计中，第四信息携带在SIB中；或者，第四信息携带在MIB中；或者，第四信息携带在paging消息中。基于该可能的设计，通过多种方式有效且灵活的向小区中的终端广播/发送第四信息，使得即便断开RRC连接的终端也能够接收到第四信息。
一种可能的设计中，终端接收来自接入网设备的第四信息，包括：终端通过SRB接收来自接入网设备的第四信息。基于该可能的设计，以小区为粒度，通过小区对应的信令无线承载(比如SRB0)接收第四信息，使得即便断开RRC连接的终端也能够接收到第四信息，简化系统设计。
第七方面，本申请提供一种通信装置，该通信装置可以为终端或者终端中的芯片或者片上系统，还可以为通信装置中用于实现第一方面或第一方面的任一可能的设计所述的方法的功能模块，或者实现第六方面或第六方面的任一可能的设计所述的方法的功能模块。该通信装置可以实现上述各方面或者各可能的设计中通信装置所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。一种可能的设计中，该通信装置可以包括：处理单元，接收单元以及发送单元。
一种可能的设计中，该终端处于非激活态，且该终端通过第一接入网设备加入多播业务对应的多播群组，并从第一接入网设备移动到第二接入网设备，在该场景下，处理单元，用于确定终端位于第一接入网设备的服务区域之外。发送单元，用于向第二接入网设备发送包括多播业务的标识信息的第一信息，第一信息用于通知终端移出第一区域，触发第二接入网设备向第一接入网设备发送更新多播业务的上下文的第二信息，或向第一接入网设备发送用于从第一接入网设备提取终端的UE上下文的第三信息。
又一种可能的设计中，接收单元，用于接收来自接入网设备的包括多播业务的标识信息以及多播业务的无线网络临时标识的第四信息、加扰的下行控制信息，根据第四信息以及加扰的下行控制信息接收来自接入网设备的多播业务的数据。该可能的设计中，终端可以处于空闲态或者非激活态。
具体的，该通信装置的具体实现方式可以参考第一方面或第一方面的任一种可能的设计或第六方面或第六方面的任一可能的设计所述的方法中终端的行为功能，不再重复赘述。
第八方面，本申请提供一种通信装置，该通信装置可以为第二接入网设备或者第 二接入网设备中的芯片或者片上系统，还可以为通信装置中用于实现第二方面或第二方面的任一可能的设计所述的方法的功能模块，该通信装置可以实现上述各方面或者各可能的设计中通信装置所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。该通信装置可以包括：接收单元以及发送单元。
接收单元，用于接收来自终端的包括多播业务的标识信息的第一信息，该第一信息可以用于通知终端移出第一区域(本文中可以称为第一接入网设备的服务区域)。
发送单元，用于根据第一信息，向第一接入网设备发送用于更新多播业务的上下文的第二信息，以使得第一接入网设备根据第二信息更新多播业务的上下文；或向第一接入网设备发送用于从第一接入网设备提取终端的UE上下文的第三信息，以使得第一接入网设备根据第三信息更新通过第一接入网设备加入多播群组的终端的数量。
具体的，该通信装置的具体实现方式可以参考第二方面或第二方面的任一种可能的设计中第二接入网设备的行为功能，不再重复赘述。
第九方面，本申请提供一种通信装置，该通信装置可以为第一接入网设备或者第一接入网设备中的芯片或者片上系统，还可以为通信装置中用于实现第三方面或第三方面的任一可能的设计所述的方法的功能模块，或者用于实现第四方面或第四方面的任一可能的设计所述的方法的功能模块。该通信装置可以实现上述各方面或者各可能的设计中通信装置所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。该通信装置可以包括：处理单元，接收单元。
一种可能的设计中，接收单元，用于接收来自第二接入网设备的用于更新多播业务的上下文的第二信息。处理单元，用于根据第二信息，更新多播业务的上下文。
一种可能的设计中，接收单元，用于接收来自第二接入网设备的用于提取终端的UE上下文的第三信息。处理单元，用于根据第三信息，更新通过第一接入网设备加入多播群组的终端的数量。
具体的，该通信装置的具体实现方式可以参考第三方面或第三方面的任一种可能的设计中第一接入网设备的行为功能，或者参考第四方面或第四方面的任一可能的设计中第一接入网设备的行为功能，在此不再重复赘述。
第十方面，本申请提供一种通信装置，该通信装置可以为接入网设备或者接入网设备中的芯片或者片上系统，还可以为通信装置中用于实现第五方面或第五方面的任一可能的设计所述的方法的功能模块，该通信装置可以实现上述各方面或者各可能的设计中通信装置所执行的功能，所述功能可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个上述功能相应的模块。该通信装置可以包括：处理单元以及发送单元。
处理单元，用于根据多播业务的标识信息分配多播业务的无线网络临时标识，根据多播业务的无线网络临时标识获得加扰的下行控制信息。
发送单元，用于发送包括多播业务的标识信息以及多播业务的无线网络临时标识的第四信息、加扰的下行控制信息，以使得接收/监听到第四信息的终端根据多播业务的无线网络临时标识获得解扰的下行控制信息，根据解扰的下行控制信息接收多播业 务的数据。
具体的，该通信装置的具体实现方式可以参考第五方面或第五方面的任一种可能的设计中接入网设备的行为功能，不再重复赘述。
第十一方面，提供了一种通信装置，该通信装置包括一个或多个处理器、一个或多个存储器。所述一个或多个存储器与所述一个或多个处理器耦合，所述一个或多个存储器用于存储计算机程序代码，所述计算机程序代码包括计算机指令，当一个或多个处理器执行所述计算机指令时，使通信装置执行如第一方面或第一方面的任一种可能的设计中终端所执行的方法步骤；或者执行如第二方面或第二方面的任一种可能的设计中第二接入网设备执行的方法步骤；或者执行如第三方面或第三方面的任一可能的设计中或第四方面或第四方面的任一可能的设计中第一接入网设备执行的方法步骤；或者执行如第五方面或第五方面的任一可能的设计中接入网设备执行的方法步骤；或者执行如第六方面或第六方面所述的任一可能的设计中终端执行的方法步骤。
第十二方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如第一方面或第一方面的任一种可能的设计中终端所执行的方法步骤；或者执行如第二方面或第二方面的任一种可能的设计中第二接入网设备执行的方法步骤；或者执行如第三方面或第三方面的任一可能的设计中或第四方面或第四方面的任一可能的设计中第一接入网设备执行的方法步骤；或者执行如第五方面或第五方面的任一可能的设计中接入网设备执行的方法步骤；或者执行如第六方面或第六方面所述的任一可能的设计中终端执行的方法步骤。
第十三方面，提供了一种计算机可读存储介质，该计算机可读存储介质可以为可读的非易失性存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行如第一方面或第一方面的任一种可能的设计中终端所执行的方法步骤；或者执行如第二方面或第二方面的任一种可能的设计中第二接入网设备执行的方法步骤；或者执行如第三方面或第三方面的任一可能的设计中或第四方面或第四方面的任一可能的设计中第一接入网设备执行的方法步骤；或者执行如第五方面或第五方面的任一可能的设计中接入网设备执行的方法步骤；或者执行如第六方面或第六方面所述的任一可能的设计中终端执行的方法步骤。
第十四方面，还提供一种通信系统，该通信系统可以包括如第一方面或第一方面的任一种可能的设计中所述的终端、如第二方面或第二方面的任一种可能的设计中所述的第二接入网设备、以及如第三方面或第三方面的任一可能的设计中或第四方面或者第四方面的任一可能的设计中所述的第一接入网设备；或者，
该通信系统可以包括如第五方面或第五方面的任一可能的设计中的接入网设备以及如第六方面或第六方面所述的任一可能的设计中的终端。
附图说明
图1为本申请实施例提供的终端加入多播业务对应的多播群组的流程图；
图2为本申请实施例提供的网络架构示意图；
图3为本申请实施例提供的5G通信系统示意图；
图4为本申请实施例提供的一种通信装置400的组成示意图；
图5a为本申请实施例提供的一种多播业务的通信方法的流程图；
图5b为本申请实施例提供的一种多播业务的通信方法的流程图；
图6为本申请实施例提供的一种多播业务的通信方法的流程图；
图7为本申请实施例提供的一种发送第四信息的示意图；
图8为本申请实施例提供的一种通信装置80的组成示意图；
图9为本申请实施例提供的一种通信装置90的组成示意图；
图10为本申请实施例提供的一种通信装置100的组成示意图；
图11为本申请实施例提供的一种通信系统的组成示意图；
图12为本申请实施例提供的一种通信系统的组成示意图。
具体实施方式
通信系统中，如果某个终端存在多播业务的需求，则该终端可以与接入网设备建立无线资源控制(radio resource control，RRC)连接处于RRC连接态，并在RRC连接态下通过该接入网设备加入多播业务对应的多播群组，接收该接入网设备面向多播群组发送的多播业务的数据。其中该接入网设备可以为终端提供网络服务(比如为终端提供多播业务的数据)，该终端当前驻留在该接入网设备的服务区域中。
需要说明的是，本申请所述的加入多播业务对应的多播群组可替换描述为加入多播业务，或者加入多播群组，或者加入组播广播业务(multicast broadcast service，MBS)，或者加入多播业务对应的多播会话(multicast session)或者加入多播业务对应的多播广播业务会话(multicast broadcast service session，MBS session)，或者加入组播会话对应的组播群组等。
需要说明的是，本申请所述的多播可以指面向多个终端发送相同数据的一种通信方式，本申请不限定多播的命名，本申请所述的多播可以替换为组播或者广播或者多播/广播(multicast/broadcast)。本申请的“多播”是广义上的概念，可以包括组播(multicast)或广播(broadcast)，即本申请实施例既可以应用于组播业务传输，也可以应用于广播业务传输。本申请中提及的“多播”可以替换为“组播或广播”。此外，本申请中的多播会话(multicast session)可以替换为多播业务会话(multicast service session)或多播广播业务会话(multicast broadcast service session，MBS session)，不予限定。
图1为终端通过接入网设备加入多播业务对应的多播群组的流程图，该过程可以包括：
S1、终端与接入网设备建立RRC连接处于连接态后，终端可以通过接入网设备向核心网设备发送加入请求(join request)，该加入请求可以用于请求加入多播业务对应的多播群组，该加入请求可以携带多播业务的标识信息。
S2、核心网设备接收终端发送的加入请求并授权该终端加入多播业务对应的多播群组后，核心网设备(例如会话管理功能(session management function，SMF)可以向接入网设备发送针对该加入请求的N2会话管理(session management，SM)信息(N2 SM Info)，该N2 SM信息可以通知接入网设备该终端可以加入多播业务对应的多播群组，该N2 SM信息可以携带多播业务的标识信息以及多播业务的服务质量(quality of service，QoS)信息(比如多播业务的服务质量标识(QoS identifier，QFI)、多播业务的服务质量策略(QoS profile)等)，还可以携带多播服务质量流(QoS flow，QF) 所映射的单播QF的相关信息，比如单播QF对应的单播QFI，单播QoS Profile等，还可以携带终端的标识信息等。
S3、接入网设备接收到N2 SM信息后，可以将多播业务的相关信息存储在多播业务的上下文中，将多播业务的上下文中加入多播群组的终端的数量加1，或者将终端的标识信息加入多播业务的上下文中，或者将组播业务的标识信息存储到该终端的UE上下文(例如接入网设备中该终端的新一代应用协议(new generation application protocol，NGAP)UE上下文(NGAP UE context))中，并根据N2 SM消息携带的多播业务的相关信息配置用于传输多播业务的数据的空口无线承载(比如数据无线承载(data radio bearer，DRB)或者多播无线承载(multicast radio bearer，MRB)等)、以及配置多播业务的无线网络临时标识，比如多播业务对应的组-无线网络临时标识(group-radio network tempory identity，G-RNTI)等。可选的，接入网设备还可以将多播业务的标识信息保存在终端的用户设备(user equipment，UE)上下文中，以表示该终端加入该多播业务对应的多播群组。
S4、接入网设备将多播业务的无线网络临时标识(比如多播业务的G-RNTI)等信息发送给多播群组中的终端。相应的，终端接收来自接入网设备的多播业务的无线网络临时标识等信息。后续，终端可以根据多播业务的无线网络临时标识接收接入网设备通过空口无线承载传输的多播业务的数据，比如以多播业务的无线网络临时标识为G-RNTI为例，接入网设备可以利用G-RNTI加扰下行控制信息(downlink control information，DCI)得到加扰的DCI，该DCI可以用于调度多播业务的数据，接入网设备发送加扰的DCI以及在DCI所指示的终端利用G-RNTI成功解扰加扰的DCI后，在DCI所指示的物理下行共享信道(physical downlink shared channel，PDSCH)上接收多播业务的数据。
本申请实施例中，多播业务的上下文(multicast service context)可以替换描述为多播广播业务会话上下文(MBS session context)，或多播广播上下文(MBS context)，或者多播广播组上下文(MBS group context)，或者多播广播业务上下文(MBS service context)等。终端通过接入网设备加入多播业务对应的多播群组后，该多播业务的上下文可以存储在接入网设备中。多播业务的上下文与多播业务对应/关联，多播业务的上下文中可以包括多播业务的相关信息，比如多播业务的上下文可以包括多播业务的标识信息、多播业务的QoS信息、通过接入网设备加入多播群组的终端的信息等。其中，通过接入网设备加入多播群组的终端的信息可以包括通过接入网设备加入多播群组的终端的数量、还可以包括通过接入网设备加入多播群组的终端的标识信息。比如UE1-UE4通过基站1加入多播业务对应的多播群组，则该多播业务的上下文中可以包括加入多播群组的终端的数量4，或者包括加入多播群组的终端的数量4以及终端的标识信息{UE1，UE2，UE3，UE4}。
本申请实施例中，多播业务的标识信息可以用于标识多播业务。多播业务的标识信息可以由终端的应用层配置。多播业务的标识信息可以等价替换为多播业务对应的多播群组的标识信息(比如临时多播群组标识(temporary multicast group identifier，TMGI))，或者，提供多播业务据的应用服务器的因特网协议(internet protocol，IP)多播地址，或者，多播业务的业务标识(service identifier，service ID)，或者，多播 业务的分组过滤(packet filter)信息，或者，多播业务的业务数据流(service data flow，SDF)识别规则，或者，用于传输多播业务的数据的多播会话的标识信息，或者多播/广播业务标识(MBS ID)，或者多播/广播业务会话标识(MBS session ID)，或者多播/广播业务标识，或者源特定的IP组播地址(source specific IP address)，或者组播业务的包检测规则(packets detection rule，PDR)中的一种或者多种，此处不限定。应理解，PDR是过滤器的集合，每一个过滤器是一个五元组，每一个过滤器包含组播业务的源地址、目的地址、源端口号、目标端口号、协议号，PDR用于对组播业务的数据进行过滤。
本申请实施例中，终端的标识信息可以用于标识终端。一种可能的设计中，终端的标识信息可以称为终端的身份信息，终端的标识信息可以是终端的全网识别信息。具体的，终端的标识信息可以为终端的因特网协议(internet protocol，IP)地址或者终端的媒体接入控制(media access control，MAC)地址或者终端的国际移动用户识别码(international mobile subscriber identity，IMSI)，或者终端的永久标识信息(subscriber permanent identifier，SUPI)，或者终端的5G全球唯一临时标识(5G global user temporary identifier，5G-GUTI)，或者终端的用户隐藏标识(subscription concealed identifier，SUCI)、终端的一般公共订阅标识符(generic public subscription identifier，GPSI)、终端的5G短临时移动用户标识(5G S-temporary mobile subscriber identity,5G-S-TMSI)、终端的永久设备标识(permanent equipment identifier，PEI)等等。又一种可能的设计，以小区为粒度或者以接入网设备为粒度，终端的标识信息可以是终端的无线网络临时标识，比如终端的RNTI，终端的无线网络临时标识可以用于标识某个小区或接入网设备的服务区域中的终端，终端的RNTI与小区/接入网设备对应。终端位于不同接入网设备的服务区域时的RNTI是不同的。
在某种场景下，如果与接入网设备建立RRC连接，处于RRC连接态的终端长时间内没有数据业务需求，接入网设备可能确定暂停(suspend)终端的RRC连接，向终端发送RRC连接暂停(RRC connection suspend)消息，终端接收到RRC connection suspend消息后，断开与接入网设备的RRC连接，从连接态切换到非激活(inactive)态或空闲态。其中处于非激活态或空闲态的终端无法通过接入网设备接收任何数据，比如多播业务的数据等，接入网设备也无法获知/监测处于非激活态或空闲态的终端的位置信息。比如，以UE1-UE4通过基站1加入多播业务对应的多播群组为例，UE1长时间内没有数据业务需求，则基站1可以暂停与UE1之间的RRC连接，此时，UE1无法接收基站1发送的多播业务的数据。
本申请实施例中，连接态可以称为RRC连接态。连接态下，终端和接入网设备之间存在RRC连接，终端与移动管理网元(如接入和移动管理功能(access and mobility management function，AMF))之间存在非接入层(non-access stratum，NAS)信令连接，接入网设备与移动管理网元之间存在per UE粒度的N2接口连接。此时，接入网设备以及移动管理网元都保存有终端的UE上下文。接入网设备上保存的终端的UE上下文与移动管理网元上保存的终端的UE上下文不同，比如接入网设备保存的终端的UE上下文与终端的数据传输有关，接入网设备可以根据其保存的终端的UE上下文知道该终端在接入网设备的服务区域内或者在该接入网设备的服务区域内。移动管 理网元保存的终端的UE上下文中可以包括终端的标识信息、终端的位置信息、终端的注册区域、终端当前的连接管理(connection management，CM)连接状态等等，移动管理网元可以根据终端的UE上下文知道通过哪个接入网设备可以定位到或者找到该终端。
本申请实施例中，非激活(inactive)态：可以称为无线接入控制非激活态(RRC_inactive态(RRC_inactive态)。非激活态下，终端和接入网设备之间断开RRC连接，接入网设备与移动管理网元之间存在以UE为粒度(比如per UE)的N2接口连接。接入网设备中保存有终端的UE上下文，移动管理网元中可以保存有终端的UE上下文。接入网设备不知道该终端驻留在该接入网设备的服务区域内的具体小区或者否在该接入网设备的管理范围内，移动管理网元知道终端在哪个接入网设备的服务区域内或者管理范围内，移动管理网元知道通过哪个接入网设备可以定位或者找到该终端。
本申请实施例中，空闲(idle)态可以指终端和接入网设备之间没有RRC连接。空闲态可以称为RRC_idle态。空闲态时，接入网设备中未保存终端的UE上下文，终端与移动管理网元(如AMF)之间不存在NAS信令连接，接入网设备与移动管理网元之间不存在per UE的N2接口连接，移动管理网元保存有终端的UE上下文。接入网设备不知道该终端是否在该接入网设备的服务区域内。移动管理网元不知道终端在哪个接入网设备的服务区域内或者管理范围内，接入网设备不知道通过哪个接入网设备可以定位到或者找到终端。
本申请实施例中，接入网设备上保存的终端的UE上下文与终端的数据传输有关。比如，接入网设备上保存的终端的UE上下文可以包括该终端的协议数据单元(protocol data unit，PDU)会话的信息，PDU会话的信息包括单播QoS参数(例如单播QF的QoS profile)。可选的，如果终端通过接入网设备加入多播业务对应的多播群组，则终端的UE上下文中还可以包括多播业务相关的信息，例如终端的UE上下文中可以包括多播业务的标识信息、多播业务所对应的多播QF的QoS profile、多播QF与单播QF的映射关系等。
由上可知，终端处于非激活态或者空闲态时，为该终端提供网络服务的接入网设备不知道该终端是否还驻留在该接入网设备的服务区域内，不知道终端当前在哪个小区。此时，可能会存在终端驻留在接入网设备的服务区域之外的区域，终端已离开了该接入网设备管理下的多播业务对应的多播群组，但接入网设备不知道终端的移动轨迹，误认为该终端仍处于接入网设备的服务区域中，导致接入网设备不去更新加入多播群组的终端的数量，使得通过接入网设备加入多播群组的终端的数量与实际数量不一致，接入网设备误以为多播群组中的终端的数量不变而不去调整传输多播业务的数据的资源，造成资源浪费等。
比如，以UE1-UE4通过基站1加入多播业务对应的多播群组为例，UE1、UE2长时间内没有数据业务需求，暂停与UE1、UE2之间的RRC连接，处于非激活态。此时，假设UE1、UE2也离开基站1的服务区域，不再接受基站1提供的网络服务。然而，对应基站1而言，无法获知到处于非激活态的UE的位置信息等，仍认为通过基站1加入多播群组的终端的数量为4个，故不调整传输多播业务的数据的资源，而实际是 通过基站1加入多播群组的终端减少为2个，此时，基站1本可以通过将传输多播业务的数据的资源调整为/减少为对应这2个UE的资源来节省资源。
为解决该技术问题，本申请实施例提供一种多播业务的通信方法，该方法可以应用于处于非激活态的终端从第一接入网设备移动到第二接入网设备，且该终端通过第一接入网设备加入多播业务对应的多播群组的场景中。该方法可以包括：终端确定自己位于第一接入网设备的服务区域(本申请中可以称为第一区域)之外时，终端向第二接入网设备发送包括多播业务的标识信息的第一信息，触发第二接入网设备向第一接入网设备发送用于更新多播业务的上下文的第二信息，以便第一接入网设备根据接收到的第二信息更新多播业务的上下文，比如将多播业务的上下文中加入多播群组的终端的数量减1等；或触发第二接入网设备向第一接入网设备发送用于从第一接入网设备提取终端的UE上下文的第三信息，以便第一接入网设备根据第三信息更新通过第一接入网设备加入多播群组的终端的数量。如此，可以根据处于非激活态的终端的移动情况及时更新多播业务的上下文或加入多播群组的终端的数量，避免接入网设备不去更新加入多播群组的终端的数量，使得通过接入网设备加入多播群组的终端的数量与实际数量不一致，导致的接入网设备误以为多播群组中的终端的数量不变而不去调整传输多播业务的数据的资源，造成资源浪费的问题。
应理解，本申请所述的第一接入网设备可以是终端发生移动前(驻留到/移动到第二接入网设备所对应的小区之前)为终端提供网络服务的接入网设备，第二接入网设备可以是终端当前所处/驻留小区对应的接入网设备。第一接入网设备可以称为源接入网设备，第二接入网设备可以称为目标接入网设备。
应理解，本申请所述的第一接入网设备的服务区域可以替换描述为第一接入网设备的信号覆盖区域或第一接入网设备包括的小区等。位于第一接入网设备的服务区域的终端或其他设备可以与第一接入网设备建立RRC连接，通过该RRC连接接收第一接入网设备提供的网络服务，比如接收来自第一接入网设备的多播业务的数据等。
下面结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
本申请实施例提供的多播业务的通信方法可应用于图2所示的通信系统，如图2所示，该通信系统可以包括多个终端、第一接入网设备、第二接入网设备。进一步的，还可以包括核心网设备(比如移动管理网元、会话管理网元等)、用户面网元、以及数据网络(data network，DN)等。图2中的多个终端可以通过第一接入网设备加入多播业务对应的多播群组。下面对图2所示架构中涉及的网元或设备进行介绍。
终端，可以是用于实现无线通信功能的设备，例如终端或者可用于终端中的芯片等。其中，终端可以是5G网络或者未来演进的通信系统中的UE、接入终端、终端单元、终端站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、终端代理或终端装置等。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备或可穿戴设备，虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical) 中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。终端可以是移动的，可以从第一接入网设备移动到第二接入网设备。应理解，本申请实施例所述的从第一接入设备移动到第二接入网设备可以指从第一接入网设备的服务区域移动到第二接入网设备的服务区域等。
第一接入网设备、第二接入网设备可以统称为接入网设备，主要用于实现物理层功能、资源调度和管理、终端的接入控制以及移动性管理等功能。接入网设备可以为支持有线接入的设备，也可以为支持无线接入的设备。示例性，接入网设备可以为接入网(access network，AN)/无线接入网(radio access network，RAN)，由多个5G-AN/5G-RAN节点组成。5G-AN/5G-RAN节点可以为：接入点(access point，AP)、基站(nodeB，NB)、增强型基站(enhance nodeB，eNB)、下一代基站(NR nodeB，gNB)、传输接收点(transmission reception point，TRP)、传输点(transmission point，TP)或某种其它接入节点等。
移动管理网元，主要负责终端的接入认证、移动性管理、各个功能网元之间的信令交互等工作，如：对用户的注册状态、用户的连接状态、用户注册入网、跟踪区更新、小区切换用户认证和密钥安全等进行管理。
会话管理网元，主要用于实现用户面传输逻辑通道，如PDU会话的建立、释放和更改等会话管理功能。
用户面网元，可以作为用户面传输逻辑通道上的锚点，用于完成用户面数据的路由转发等功能，如：与终端之间建立通道(即用户面传输逻辑通道)，在该通道上转发终端和DN间的数据包、负责对终端的数据报文过滤、数据转发、速率控制、生成计费信息。
DN，可以为用户提供数据传输服务的运营商网络，如：可以为向用户提供因特网协议(internet protocol，IP)多媒体业务(IP multi-media service，IMS)的运营商网络等。DN中可以部署有AS，该应用服务器可以向用户提供数据传输服务。DN可以包括应用服务器(application server，AS)。
需要说明的是，图2仅为示例性架构图，除图2中所示功能单元外，该系统还可以包括其他功能网元，如：操作和管理(operation and management，O&M)网元等，本申请实施例对此不进行限定。此外，图2中各个设备的名称不受限制，除图2所示名称之外，各个设备还可以命名为其他名称，如替换成具备相同或相似功能的网元名称，不予限制。
其中，图2所示系统可以为第三代合作伙伴计划(3rd generation partnership project，3GPP)通信系统，如第4代(4th generation，4G)通信系统、长期演进(long term evolution，LTE)系统，又可以为第五代(5th generation，5G)通信系统或者新空口(new radio，NR)系统、下一代通信系统等，也可以为非3GPP通信系统，不予限制。
以图2所示的通信系统为图3所示的5G通信系统为例，如图3所示，接入网设备对应的网元或者实体可以为NG-RAN，上述会话管理网元所对应的网元或者实体可以为5G通信系统中的会话管理功能(session management function，SMF)，移动管理网元对应接入与移动管理功能(access and mobility management function，AMF)，上 述用户面网元所对应的网元或者实体可以为5G通信系统中的用户面功能(user plane function，UPF)，接入网设备对应的网元或者实体可以为5G通信系统中的无线接入网(radio access network，RAN)、移动管理网元对应的网元或者实体可以为5G通信系统中的接入和移动性管理功能(access and mobility management function，AMF)。此外还包括策略控制功能(policy control function，PCF)、网络开放功能(network exposure function，NEF)、NRF或者UDR或者UDM等。
可选的，本申请实施例中的第一接入网设备、终端等也可以称之为通信装置，其可以是一个通用设备或者一个专用设备，本申请实施例对此不作具体限定。
可选的，本申请实施例中的第一接入网设备、终端等的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者硬件与软件的结合，或者平台(例如，云平台)上实例化的虚拟化功能。
在具体实现时，图2所示各设备，比如终端、第一接入网设备、第二接入网设备等，可以采用图4所示的组成结构，或者包括图4所示的部件。图4为本申请实施例提供的一种通信装置400的组成示意图，该通信装置400可以包括处理器401和存储器404。进一步的，该通信装置400还可以包括通信线路402以及通信接口403。其中，处理器401，存储器404以及通信接口403之间可以通过通信线路402连接。
处理器401，可以是中央处理器(central processing unit，CPU)、通用处理器、网络处理器(network processor，NP)、数字信号处理器(digital signal processing，DSP)、微处理器、微控制器、可编程逻辑器件(programmable logic device，PLD)或它们的任意组合。处理器401还可以是其它具有处理功能的装置，如电路、器件或软件模块，不予限制。
通信线路402，用于在通信装置400所包括的各部件之间传送信息。
通信接口403，用于与其他设备或其它通信网络进行通信。该其它通信网络可以为以太网，无线接入网(radio access network，RAN)，无线局域网(wireless local area networks，WLAN)等。通信接口403可以是模块、电路、收发器或者任何能够实现通信的装置。
存储器404，用于存储指令。其中，指令可以是计算机程序。
其中，存储器404可以是只读存储器(read-only memory，ROM)或可存储静态信息和/或指令的其他类型的静态存储设备，也可以是随机存取存储器(random access memory，RAM)或可存储信息和/或指令的其他类型的动态存储设备，还可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟)、磁盘存储介质、其他磁存储设备，不予限制。
需要说明的是，存储器404可以独立于处理器401存在，也可以和处理器401集成在一起。存储器404可以用于存储指令或者程序代码或者一些数据等。存储器404可以位于通信装置400内，也可以位于通信装置400外，不予限制。
处理器401，用于执行存储器404中存储的指令，以实现本申请下述实施例提供的多播业务的通信方法。例如，当通信装置400为终端或者终端中的芯片或者片上系统时，处理器401执行存储器404中存储的指令，以实现本申请下述实施例中终端所执行的步骤。又例如，当通信装置400为第一接入网设备或者第一接入网设备中的芯片或者片上系统时，处理器401可以执行存储器404中存储的指令，以实现本申请下述实施例中第一接入网设备所执行的步骤。
在一种示例中，处理器401可以包括一个或多个CPU，例如图4中的CPU0和CPU1。
作为一种可选的实现方式，通信装置400包括多个处理器，例如，除图4中的处理器401之外，还可以包括处理器407。
作为一种可选的实现方式，通信装置400还包括输出设备405和输入设备406。示例性地，输入设备406是键盘、鼠标、麦克风或操作杆等设备，输出设备405是显示屏、扬声器(speaker)等设备。
需要说明的是，通信装置400可以是台式机、便携式电脑、网络服务器、移动手机、平板电脑、无线终端、嵌入式设备、芯片系统或有图4中类似结构的设备。此外，图4中示出的组成结构并不构成对该通信装置的限定，除图4所示部件之外，该通信装置可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。
本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
此外，本申请的各实施例之间涉及的动作，术语等均可以相互参考，不予限制。本申请的实施例中各个设备之间交互的消息名称或消息中的参数名称等只是一个示例，具体实现中也可以采用其他的名称，不予限制。
下面以图2所示架构为例，对本申请实施例提供的多播业务的通信方法进行描述。下述实施例中的各网元可以具备图4所示部件，不予赘述。需要说明的是，本申请的各实施例之间涉及的动作，术语等均可以相互参考，不予限制。本申请的实施例中各个设备之间交互的消息名称或消息中的参数名称等只是一个示例，具体实现中也可以采用其他的名称，不予限制。例如：本申请实施例所述的多播可以替换为广播、组播、多播通信、多播/广播或者组播/广播等术语。本申请实施例中的确定也可以理解为创建(create)或生成(generate)，本申请实施例中的“包括”也可以理解为“携带”或者“包含”等，本申请实施例中的“断开”也可以理解为“释放”或者“停止”或者“暂停”等。在此统一说明，本申请实施例对此不作具体限定。
图5a为本申请实施例提供的一种多播业务的通信方法，该方法可以应用于下述场景中：通过某个接入网设备加入多播群组的终端在处于非激活态的情况下，从该接入网设备移动到其他接入网设备。比如以图2中终端为例，该终端从第一接入网设备移动到第二接入网设备，该终端通过第一接入网设备加入多播群组且该终端处于非激活态。下面以图2所示系统为例对该方法进行描述，如图5a所示，该方法可以包括：
S501：终端确定终端位于第一区域之外。
其中，终端位于第一区域之外还可以替换描述为终端不在第一区域内，或者终端离开第一区域，或者终端离开第一接入网设备的信号覆盖区域，或者不在第一接入网设备的信号覆盖区域等，不予限制。
其中，该终端可以为图2中通过第一接入网设备加入多播业务对应的多播群组的 任一终端，该终端可以处于非激活态。第一接入网设备可以为终端驻留小区对应的接入网设备，第一接入网设备能够与终端建立RRC连接，通过RRC连接为终端提供网络服务。本申请实施例中，第一接入网设备可以称为源接入网设备。终端通过第一接入网设备加入多播群组后，第一接入网设备中可以有终端的UE上下文、多播业务的上下文。多播业务的上下文中可以包括加入多播群组的终端的信息，比如可以包括加入多播群组的终端的数量，或者包括加入多播群组的终端的数量以及加入多播群组的终端的标识信息等。终端的UE上下文中可以包括多播业务的标识信息。具体的，终端通过第一接入网设备加入多播业务对应的多播群组的过程可以参照图1所示流程，不再赘述。
本申请实施例中，多播业务可以指面向多个终端的业务，如多播业务可以为电视节目、文件传输服务、组内语音或视频通信、车队内部的广播业务等。多播业务所面向的多个终端可以加入一个群组，该群组可以称为多播业务对应的多播群组，多播群组中的所有终端可以被授权或者无需得到授权即可接收此多播业务的数据。即多播业务对应的多播群组可以为接收多播业务的数据的多个终端的组合，如多播群组可以为接收同一指挥中心发出的命令的车队或者为接收同一电视节目的用户群组等。
本申请实施例中，第一区域可以为第一接入网设备的服务区域、或第一接入网设备的信号覆盖区域、或者第一接入网设备对应的一个或者多个小区，第一区域可以称为第一接入网设备的基于无线接入网的通知区域(RAN-based notification area，RNA)。第一区域中的终端可以接收第一接入网设备提供的网络服务、与第一接入网设备进行业务数据传输，比如终端可以在第一区域内接收来自第一接入网设备的多播业务的数据。本申请实施例中，可以以接入网设备或者小区为粒度对接入网设备的信号覆盖区域进行划分得到第一区域。比如，以接入网设备为粒度的情况下，第一区域可以是第一接入网设备的整个信号覆盖区域，此时默认第一区域包括第一接入网设备信号覆盖下的所有小区。以小区为粒度的情况下，第一区域可以包括第一接入网设备覆盖下能够提供多播业务服务的一个或者多个小区，该小区可以替换描述为扇区，此时一个小区可以对应一个或者多个载波，第一接入网设备可以在小区对应的载波上向终端传输多播业务的数据，该场景下，第一区域可以称为多播业务的服务区域/多播业务的接收区域。应理解，本申请实施例中，能够提供多播业务服务的小区可以指能够在该小区对应的载波上进行多播业务的数据传输的小区。
例如，假设第一接入网设备为基站1，基站1下存在小区1、小区2以及小区3，其中第一接入网设备可以在小区1以及小区2对应的载波上传输多播业务的数据，则在以接入网设备为粒度的情况下，第一区域可以是基站1的整个信号覆盖区域，第一区域可以包括小区1、小区2和小区3。在以小区为粒度的情况下，第一区域可以包括小区1以及小区2。
本申请实施例中，第一区域可以由第一接入网设备指示给/配置给终端，比如终端可以接收来自第一接入网设备的第一区域的信息，第一区域的信息可以指示第一区域，比如在以接入网设备为粒度的情况下，第一区域的信息可以是以下一种或多种：第一接入网设备的标识、第一接入网设备包括的一个或多个小区的标识(cell ID(s))、第一接入网设备包括的小区的列表(cell ID list)、第一接入网设备支持(supported)/包括/属于的 一个或多个跟踪区域标识(tracking area ID(s),TAI(s))、第一接入网设备支持(supported)/包括/属于的一个或多个跟踪区域列表(TA List)、第一接入网设备的名称(RAN Node Name)、第一接入网设备包括的一个或多个物理小区标识(physical cell identifier，PCI(s))、第一接入网设备包括的物理小区标识列表(PCI list)、第一接入网设备所处位置的地理信息(例如全球定位系统(global positioning system，GPS)信息、第一接入网设备包括的一个或多个中心单元(Central Unit，CU(s))和/或分布(distributed unit，DU(s))的标识、第一接入网设备包括的CU list和/或DU list等。接入网设备的标识可以是第一接入网设备的全球接入网设备标识(global gNB ID)或第一接入网设备的无线接入网络节点名称(RAN node name)或第一接入网设备的全球无线接入网节点标识(global RAN Node ID)，或第一接入网设备的无线接入网络节点标识(RAN Node ID等。在以小区为粒度的情况下，第一区域的信息可以包括第一接入网设备信号覆盖下能够提供多播业务服务的一个或者多个小区的标识，小区的标识可以是小区的物理小区标识(physical cell identifier，PCI)或者全球小区识别码(cell global identity，CGI)等。
一种示例中，第一区域的信息携带在新增信令消息中发送给终端，比如可以携带在新增的RRC消息中发送给终端。又一种示例中，为了节省信令开销，可以在第一接入网设备确定暂停((suspend))终端的RRC连接时，将第一区域的信息携带在第二RRC消息中发送给终端，第二RRC消息可以用于暂停终端的RRC连接，使终端处于非激活态，比如第二RRC消息可以是RRC连接暂停(RRC connection suspend)消息、或者携带暂停配置的RRC释放消息(release with suspend configuration)、或者是一条用于暂停(suspend)/挂起/去激活RRC连接的RRC消息等，不予限定。如此可以在暂停终端的RRC连接过程中将第一区域指示给终端，节省信令开销。除包括第一区域的信息外，第二RRC消息还可以携带终端的无线网络临时标识(比如终端的非激活态无线网络临时标识(inactive radio network temporary identifier，I-RNTI))、多播业务的无线网络临时标识以及其他信息，不予限制。
本申请实施例中，终端的无线网络临时标识可以包括多个二进制比特，终端的无线网络临时标识可以是该终端在第一接入网设备的信号覆盖区域(或者小区)时的身份标识，终端的无线网络临时标识可以用于标识第一接入网设备的信号覆盖区域/小区中的该终端，终端的无线网络临时标识仅适用于为该终端分配无线网络临时标识的接入网设备的信号覆盖区域/小区中，是以某个接入网设备/小区为粒度的标识，不是以整个通信网络为粒度的标识。终端的无线网络临时标识由当前为终端提供网络服务的接入网设备服务的分配，比如当前情况下，终端的无线网络临时标识由第一接入网设备分配。终端的无线网络临时标识可以包括第一接入网设备的标识、或者可以替换描述为从终端的无线网络临时标识中可以解析/获取第一接入网设备的标识。具体的，第一接入网设备可以根据预设算法对终端所在小区的标识以及终端的标识信息进行计算得到终端的无线网络临时标识，或者根据预设算法对第一接入网设备的标识和终端的标识信息进行计算得到终端的无线网络临时标识。具体的，终端的无线网络临时标识的设计形式参照3GPP通信协议38.300中所述，不予限制。
本申请实施例中，多播业务的无线网络临时标识与多播业务对应，多播业务的标识信息可以用于加入调度多播业务的数据的下行控制信息(比如DCI)，根据多播业 务的标识信息可以解扰下行控制信息，根据解扰的下行控制信息获取多播业务的数据，以保证多播业务的数据传输的安全性。多播业务的无线网络临时标识可以是多播业务的G-RNTI或者多播无线网络临时标识(multicast RNTI，M-RNTI)。多播业务的无线网络临时标识可以根据多播业务的标识信息得到/分配，比如可以根据预设算法对多播业务的标识信息进行计算得到多播业务的无线网络临时标识。
本申请实施例中，第一接入网设备可以通过下述任一方式确定暂停终端的RRC连接：
一、第一接入网设备接收到移动管理网元(比如AMF)发送的N2停止回复(N2 suspend response)，N2停止回复可以用于指示停止移动管理网元与第一接入网设备之间的针对该终端的N2接口连接，则第一接入网设备确定暂停终端的RRC连接。
二、第一接入网设备收到移动管理网元发送的路径切换请求回应(path switch request response)，路径切换请求回应可以用于指示将终端的传输路径从第一接入网设备切换到其他接入网设备，第一接入网设备确定暂停终端的RRC连接。
三、第一接入网设备确定终端对应的非活动计时器过期(inactivity timer)/超时，则第一接入网设备确定该终端长时间内未接收数据，确定断开终端与其之间的RRC连接。
其中，非活动计时器可以用于确定终端是否在长时间内未进行业务数据传输。该非活动计时器对应设置有预设工作时长。非活动计时器可以在终端停止业务数据传输(比如接收/发送业务数据)时开始工作/运行，在预设工作时长内，如果终端进行业务数据传输，则停止工作/不再运行，此时运行时间小于预设工作时长，反之，在预设工作时长内，如果终端未进行业务数据传输，则非活动计时器一直工作/运行至预设工作时长结束。比如当终端开始停止业务数据传输(比如接收/发送业务数据)时，开启/运行非活动计时器，如果该非活动计时器运行预设工作时长，则预示着该终端较长时间内未进行业务数据传输，可以断开/暂停其RRC连接，以节省该终端的功率消耗。其中非活动计时器的预设时长可以根据需要设置，不予限制。
终端接收到来自第一接入网设备的第一区域的信息之后，可以根据第一区域的信息确定第一区域。后续，如果断开RRC连接的终端在移动过程中存在业传输需求，则该终端可以周期性地检测其周围有没有合适的接入网设备可以提供网络服务，比如终端可以检测其周围接入网设备发送的同步信号(synchronize signal，SS)(比如主同步信号(primary synchronization signal，PSS)/辅同步信号(secondary synchronization signal，SSS))，SS中可以包括小区的标识。终端选择信号质量较高的SS，根据选择的SS获取小区的标识，确定接入该小区的标识所标识的小区，由该小区对应的接入网设备(比如第二接入网设备)为其提供网络服务。在这个过程中，如果终端发现其获取到的小区的标识所标识的小区不包括在第一区域中，则确定终端离开第一区域，处于第一区域之外，离开第一接入网设备的信号覆盖区域。
具体的，当第一区域的信息包括一个或者多个小区的标识时，终端可以查看计算得到的小区的标识是否包括在第一区域的信息中，如果不包括，则确定该小区所标识的小区不包括在第一区域中。当第一区域的信息包括第一接入网设备的标识时，终端可以根据获取到的小区的标识计算得到一个接入网设备的标识，如果计算得到的接入网设备的标识与第一接入网设备的标识不同，则确定该小区所标识的小区不包括在第 一区域中。其中小区的标识与该小区对应的接入网设备的标识之间的运算关系可参照现有技术，在此不予赘述。
S502：终端向第二接入网设备发送第一信息。相应的，第二接入网设备接收第一信息。
其中，第二接入网设备可以是终端当前驻留/所在小区所属/所对应的接入网设备。第二接入网设备与第一接入网设备不同，终端当前驻留/所在小区在第一区域之外。
其中，第一信息可以用于通知终端移出第一区域，第一信息可以包括多播业务的标识信息，还可以包括其他信息，比如终端的无线网络临时标识等。其中，第一区域、多播业务的标识信息以及终端的无线网络临时标识的相关描述可以参照上文，不予赘述。
示例性的，终端可以将第一信息携带在第一RRC消息中，通过信令无线承载(signal radio bearer)(比如SRB0)向第二接入网设备发送第一RRC消息。或者将第一RRC消息通过其他信令消息发送给第二接入网设备，不予限制。
其中，一种可能的设计中，第一RRC消息可以用于请求恢复终端的RRC连接。比如第一RRC消息可以是RRC恢复请求(RRC resume request)，即通过RRC恢复流程将第一信息发送给第二接入网设备，以降低信令开销。或者，又一种可能的设计中，第一RRC消息可以是一个专门RRC消息，该RRC消息可以用于触发第二接入网设备向第一接入网设备发送更新多播业务的上下文的第二信息，或者该RRC消息可以用于触发第二接入网设备向第一接入网设备发送用于从第一接入网设备提取终端的UE上下文的第三信息。
S503：第二接入网设备根据第一信息，向第一接入网设备发送第二信息。相应的，第一接入网设备接收第二信息，执行S504a。或者第二接入网设备根据第一信息向第一接入网设备发送第三信息，相应的，第一接入网设备接收第三信息，执行S504b。
其中，第二信息可以用于更新多播业务的上下文，第三信息可以用于从第一接入网设备提取终端的UE上下文。一种可能的设计中，第二信息、第三信息可以包括多播业务的标识信息，还可以包括其他信息，比如还可以包括终端的标识信息等。又一种可能的设计中，在第一信息包括终端的无线网络临时标识的情况下，第二信息、第三信息可以包括终端的无线网络临时标识(如终端的I-RNTI)、和/或终端的标识信息。第二信息、第三信息可以携带在提取UE上下文请求(retrieve UE context request)中，提取UE上下文请求可以用于请求提供终端的UE上下文。或者，第二信息、第三信息可以携带在新增的消息中，比如可以携带在Xn消息中。或者，第二信息、第三信息可以携带在UE上下文释放(UE context request)请求中，UE上下文释放请求可以用于请求释放终端的UE上下文。
其中，多播业务的标识信息、终端的无线网络临时标识、终端的标识信息的相关描述可参照上文，在此不予赘述。
一种示例中，第一信息包括多播业务的标识信息，第二接入网设备可以根据多播业务的标识信息确定向该终端加入多播群组时所对应的接入网设备发送第二信息或第三信息，因不知道具体是哪个接入网设备，则第二接入网设备向其周围、与其建立Xn连接的一个或多个接入网设备发送第二信息或者第三信息，一个或多个接入网设备包 括第一接入网设备。
又一种示例中，第一信息包括多播业务的标识信息以及终端的无线网络临时标识，终端的无线网络临时标识包括第一接入网设备的标识信息，第一接入网设备可以根据终端的无线网络临时标识获取第一接入网设备的标识，根据第一接入网设备的标识向第一接入网设备发送第二信息或者第三信息。
S504a：第一接入网设备根据第二信息更新多播业务的上下文。
一种示例中，第二信息包括多播业务的标识信息，第一接入网设备根据第二信息更新多播业务的上下文可以包括：第一接入网设备根据多播业务的标识信息找到多播业务的上下文，如果多播业务的上下文中包括通过第一接入网设备加入多播群组的终端的数量，则更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量，比如将终端的数量减1。例如，假设多播业务为MBS1，第一接入网设备为基站1，第二接入网设备为基站2，通过基站1加入MBS1对应的多播群组的终端有UE1-UE4，MBS1的上下文中包括的通过基站1加入多播群组的终端的数量为4，此时如果基站1接收到来自基站2的第二信息{MBS1}，则基站1找到MBS1的上下文，将MBS1的上下文中通过基站1加入多播群组的终端的数量更新为3。
又一种示例中，第二信息包括多播业务的标识信息以及终端的标识信息，则第一接入网设备根据第二信息更新多播业务的上下文可以包括：第一接入网设备根据多播业务的标识信息找到多播业务的上下文，如果多播业务的上下文中包括通过第一接入网设备加入多播群组的终端的数量，则更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量，比如将终端的数量减1等。和/或，如果多播业务的上下文中包括通过第一接入网设备加入多播群组的终端的标识信息，则第一接入网设备可以根据第二信息包括的终端的标识信息，删除多播业务的上下文中该终端的标识信息。
例如，假设多播业务为MBS1，第一接入网设备为基站1，第二接入网设备为基站2，通过基站1加入MBS1对应的多播群组的终端有UE1-UE4，MBS1的上下文中包括的通过基站1加入多播群组的终端的数量为4、以及通过基站1加入多播群组的终端的标识信息{UE1，UE2，UE3，UE4}，此时如果基站1接收到来自基站2的第二信息{MBS1，UE1}，则基站1找到MBS1的上下文，将MBS1的上下文中通过基站1加入多播群组的终端的数量更新为3，以及删除MBS1的上下文中的UE1，使得通过基站1加入多播群组的终端的标识信息更新为{UE2，UE3，UE4}。
再一种示例中，第二信息包括终端的无线网络临时标识和/或终端的标识信息，则第一接入网设备根据第二信息更新多播业务的上下文可以包括：第一接入网设备根据终端的无线网络临时标识和/或终端的标识信息找到终端的UE上下文，从UE的上下文中获取多播业务的标识信息，根据多播业务的标识信息找到多播业务的上下文，更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量，比如将终端的数量减1等。和/或，删除多播业务的上下文中该终端的标识信息。
例如，假设多播业务为MBS1，第一接入网设备为基站1，第二接入网设备为基站2，通过基站1加入MBS1对应的多播群组的终端有UE1-UE4，MBS1的上下文中包括的通过基站1加入多播群组的终端的数量为4、以及通过基站1加入多播群组的终端的标识信息{UE1，UE2，UE3，UE4}，此时如果基站1接收到来自基站2的第二信 息{UE1和/或UE1的I-RNTI}，则基站1根据{UE1和/或UE1的I-RNTI}找到UE1的UE上下文，从UE1的UE上下文中获取MBS1，根据MBS1找到MBS1的上下文，将MBS1的上下文中通过基站1加入多播群组的终端的数量更新为3，以及在第二信息包括UE1的情况下，删除MBS1的上下文中的UE1，使得通过基站1加入多播群组的终端的标识信息更新为{UE2，UE3，UE4}。
S504b：第一接入网设备根据第三信息，更新通过第一接入网设备加入多播群组的终端的数量。
示例性的，第三信息包括终端的标识信息，第一接入网设备根据第三信息更新通过第一接入网设备加入多播群组的终端的数量可以包括：第一接入网设备根据终端的标识信息找到终端的UE上下文，将终端的UE上下文提取给第二接入网设备。
该场景下，第一接入网设备将终端的UE上下文提取给第二接入网设备之后，第一接入网设备中可以不再有/存在/释放终端的UE上下文。比如第三信息携带在UE上下文释放请求中，则第一接入网设备根据UE上下文释放请求释放终端的UE上下文，进一步的可以向第二接入网设备返回UE上下文释放响应，UE上下文释放响应可以用于指示已释放终端的UE上下文。或者，第一接入网设备将终端的UE上下文提取给第二接入网设备之后，仍可以保存成终端的UE上下文，只不过终端的UE上下文中不存在多播业务的标识信息，即删除终端的UE的上下文中多播业务的标识信息。对于第一接入网设备而言，第一接入网设备中存储的包括有多播业务的标识信息的UE上下文的数量减1，故而根据多播业务的标识信息的UE上下文的数量确定的通过第一接入网设备加入多播群组的终端的数量也减1，通过第一接入网设备加入多播群组的终端的数量得到更新。
例如，假设UE1-UE5通过基站1加入多播群组，UE1-UE5对应的五个UE上下文中均有多播业务的标识信息，此时，如果UE1离开基站1的服务区域到达基站2的服务区域，UE1不再接受基站1提供的多播业务服务。对应基站1而言，可以在接收到基站2发送的第三信息后，将UE1的UE上下文发送给基站2，基站1中不再有UE1的UE上下文，而是存在UE2-UE5对应的四个UE上下文；或者，基站1中保留UE1的UE上下文，只不过删除UE1的UE上下文中多播业务的标识信息。此时包括多播业务的标识信息的UE上下文的数量为UE2-UE5对应的4个UE上下文，根据包括多播业务的标识信息的UE上下文的数量确定得到的通过基站1加入多播群组的终端的数量也变为4。
进一步的，第三信息还可以包括多播业务的标识信息，第一接入网设备根据第三信息更新通过第一接入网设备加入多播群组的终端的数量还可以包括：第一接入网设备根据多播业务的标识信息找到多播业务的上下文，更新多播业务的上下文中通过第一接入网设备加入多播群组的终端的数量，比如将终端的数量减1等。
本申请实施例中，第一接入网设备可以将终端的UE上下文携带在第三信息对应的响应消息发送给第二接入网设备，比如携带在提取UE上下文响应中发送给第二接入网设备。
进一步的，如果第一信息携带在RRC恢复请求中，终端请求与第二接入网设备建立RRC连接，由第二接入网设备为且提供网络服务，通过第二接入网设备接收多播业 务的数据，则如图5b所示，所述方法还可以包括S505-S514：
S505：第二接入网设备与终端交互完成RRC的恢复，例如，第二接入网设备向终端发送RRC恢复(RRC resume)，终端向接入网设备发送RRC恢复完成(RRC resume complete)。
S506：第二接入网设备向移动管理网元发送N2路径切换请求(N2 Path Switch Request)。相应的，移动管理网元接收N2路径切换请求。
其中，若第二接入网设备支持多播功能，该N2路径切换请求中可以包括终端的PDU会话包括的单播QF中，被成功分配无线承载的单播QF的QFI，和/或未成功分配无线承载的单播QF的QFI；还可以包括多播业务的多播QF中，被成功分配无线承载的多播QF的QFI，和/或未成功分配无线承载(或者无线承载建立失败)的多播QF的QFI。若第二接入网设备不支持多播功能，该N2路径切换请求中可以包括终端的PDU会话中包括的单播QF中，被成功分配无线承载的单播QF的QFI，和/或未成功分配无线承载的单播QF的QFI，其中所述单播QF包括了由多播QF对应/映射的单播QF。该N2路径切换请求可以封装在N2 SM消息中。
进一步的，该N2路径切换请求还可以包括第二接入网设备分配的隧道端点标识信息。该N2路径切换请求中还包括终端的位置信息(location information)等。
S507：移动管理网元根据N2路径切换请求向会话管理网元发送PDU会话上下文更新请求。相应的，会话管理网元接收PDU会话上下文更新请求。
其中，PDU会话上下文更新请求(Nsmf_PDUSession_UpdateSMContext request)可以包括S506中N2 SM消息所包括的信息。可选的，还包括终端的位置信息等。
S508：会话管理网元根据PDU会话上下文更新请求，与用户面网元进行N4会话修改。比如会话管理网元向用户面网元发送N4会话修改请求。相应的，用户面网元接收N4会话修改请求，向会话管理网元返回N4会话修改响应，会话管理网元接收N4会话修改响应。
其中，N4会话更新请求(N4 session modification request)可以携带第二接入网设备分配的隧道端点标识信息。可选的，如果用户面网元的隧道端点标识信息由会话管理网元分配，则N4会话更新请求还可以包括会话管理网元分配给用户面网元的隧道端点标识信息。如果用户面网元的隧道端点标识信息由用户面网元分配，则N4会话修改响应中携带用户面网元的隧道端点标识信息。
本申请实施例中，第二接入网设备的隧道端点标识信息、用户面网元的隧道端点标识用于建立第二接入网设备与用户面网元之间的PDU会话。
S509：若会话管理网元确定第二接入网设备不支持多播功能，并且MB-UPF到UPF之间的用于传输多播业务的数据的隧道还未建立，则会话管理网元向MB-SMF发送消息01。，相应的，MB-SMF接收消息01。
其中，消息01可以用于指示MB-SMF通知MB-UPF建立与UPF之间的隧道。消息01可以包括用户面网元的隧道端点标识信息，该用户面网元的隧道端点标识信息可以用于建立用户面网元与MB-UPF之间用于传输多播业务的数据的隧道，用户面网元的隧道端点标识信息可以由会话管理网元分配。
S510：MB-SMF根据消息01向MB-UPF发送消息02。相应的，MB-UPF接收消 息02。
其中，消息02可以包括MB-SMF为MB-UPF分配的隧道端点标识信息和S509中所述的用户面网元的隧道端点标识信息。
S511：MB-SMF向会话管理网元发送消息03。相应的，会话管理网元接收消息03。
其中，消息03可以包括MB-UPF的隧道端点标识信息。
进一步的，会话管理网元接收到消息03后可以与用户面网元进行N4会话修改，比如会话管理网元向用户面网元UPF发送携带MB-UPF的隧道端点标识信息的N4会话修改请求，相应的，用户面网元接收N4会话修改请求，向会话管理网元返回N4会话修改响应。
S512：会话管理网元向移动管理网元发送PDU会话上下文更新响应。相应的，移动管理网元接收PDU会话上下文更新响应。
其中，PDU会话上下文更新响应(Nsmf_PDUSession_UpdateSMContext response)可以携带会话管理网元分配给用户面网元的隧道端点标识信息。
S513：移动管理网元向第二接入网设备发送N2路径切换请求响应。
其中，N2路径切换响应(N2 path switch request ACK)可以包括会话管理网元分配给用户面网元的隧道端点标识信息等。
S514：第二接入网设备向第一接入网设备发送UE上下文释放(UE context release)请求。相应的，第一接入网设备接收UE上下文释放请求，根据UE上下文释放请求释放终端的UE上下文以及该终端对应的其他资源，比如终端的PDU会话等。
基于上述方法，当终端离开第一区域时及时触发源接入网设备(比如第一接入网设备)更新通过第一接入网设备加入多播群组的终端的数量，使得通过第一接入网设备加入多播群组的终端的数量符合当前通过第一接入网设备加入多播群组的终端的实际情况，便于第一接入网设备根据通过第一接入网设备加入多播群组的终端的数量及时调整多播业务的传输资源，提高资源利用率等。进一步的，终端还可以与第二接入网设备建立RRC连接，第二接入网设备与核心网设备进行交互，再次为终端建立传输多播业务的数据的资源，保证终端通过第二接入网设备接收多播业务的数据。
在多播通信场景中，对于多播群组中存在处于非激活态或者空闲态的终端，即使这些终端有多播业务的数据需求，也会因与接入网设备断开RRC连接而无法接收到多播业务的数据，无法实现多播群组中所有终端均接收到多播业务的数据。例如，多播群组包括终端1、终端2以及终端3，其中终端2、终端3处于空闲态，终端1处于RRC连接态，此时只有终端1可以接收接入网设备发送的多播业务的数据，而终端2以及终端3因处于空闲态而无法接收多播业务的数据。
为满足多播群组中的所有终端均接收到多播业务的数据，本申请实施例还提供一种多播的通信方法，该方法可以包括：接入网设备根据多播业务的标识信息分配多播业务的无线网络临时标识，根据多播业务的无线网络临时标识获得加扰的下行控制信息，并发送第四信息以及加扰的下行控制信息，第四信息包括多播业务的标识信息以及多播业务的无线网络临时标识。如此，接入网设备覆盖下的小区内的终端可以接收第四信息，根据第四信息解扰下行控制信息，根据解扰后的下行控制信息接收来自接 入网设备的多播业务的数据。具体的，该方式可以参照图6对应的实施例中所述。
图6为本申请实施例提供的一种多播业务的通信方法，如图6所示，该方法可以包括：
S601：接入网设备根据多播业务的标识信息，分配多播业务的无线网络临时标识。
应理解，本申请实施例中的术语等只是一个示例，不对本申请方案进行限制，比如本申请实施例中的“分配”可以替换描述为“配置”等。
其中，接入网设备可以是图2中任一接入网设备，比如可以是第一接入网设备或者第二接入网设备等，不予限制。接入网设备的信号覆盖区域中/服务区域中存在通过接入网设备加入多播群组的多个终端，这多个终端中存在处于空闲态或者非激活态的终端。
其中，多播业务的无线网络临时标识与多播业务对应，多播业务的无线网络临时标识用于加扰调度多播业务的数据的下行控制信息(downlink control information，DCI)，以保证多播业务的数据的传输的安全性。接入网设备可以采用预设算法对多播业务的标识信息进行计算得到多播业务的无线网络临时标识。具体的，多播业务的标识信息、以及多播业务的无线网络临时标识的相关描述可参照上文，在此不予赘述。
S602：接入网设备根据多播业务的无线网络临时标识，获得加扰的下行控制信息。
其中，下行控制信息可以用于调度携带多播业务的数据的物理下行共享信道(physical downlink shared channel，PDSCH)，下行控制信息可以指示携带多播业务的数据的PDSCH的时频资源位置。
示例性的，下行控制信息可以包括多个校验位，该多个校验位的长度与多播业务的无线网络临时标识的长度相同，接入网设备可以根据多播业务的无线网络临时标识对该校验位进行加扰处理得到加扰的下行控制信息。其中加扰处理方式可以是预设的计算规则，该方式可以参照现有技术，不予赘述。
S603：接入网设备发送第四信息以及加扰的下行控制信息。相应的，终端接收来自接入网设备的第四信息以及加扰的下行控制信息。
其中，第四信息可以包括多播业务的标识信息以及多播业务的无线网络临时标识。多播业务的标识信息、多播业务的无线网络临时标识的相关描述可参照上文，在此不予赘述。
应理解，本申请实施例不限定第四信息以及加扰的下行控制信息的发送顺序，可以先发送第四信息，再发送加扰的下行控制信息，也可以同时发送，不予限制。进一步的，终端可以存储接收到的第四信息，比如将第四信息包括的多播业务的标识信息以及多播业务的无线网络临时标识对应存储在终端中。以便后续终端可以在对多播业务感兴趣的情况下，根据多播业务的无线网络临时标识解扰下行控制信息，接收多播业务的数据。
示例性的，接入网设备可以在下行控制信息对应的资源(比如控制资源集(control resource set，CORESET))上发送加扰的下行控制信息。其中下行控制信息对应的资源可以由接入网设备配置并指示给接入网设备的信号覆盖区域中的终端，具体的该配置方式可以参照现有技术，不予赘述。
示例性的，接入网设备可以以广播方式发送第四信息，以使得接入网设备的信号 覆盖区域内的多个终端可以通过广播方式接收到第四信息。具体的，以广播方式发送第四信息的过程如图7所示，可以包括下述三种方式中任一方式：
方式一、将第四信息携带在系统信息块(system information block，SIB)中广播出去。
例如，如图7所示，接入网设备可以生成第四信息，将第四信息递交给接入网设备的无线资源控制(radio resource control，RRC)层，接入网设备的RRC可以将获取到的第四信息携带在系统消息块(symbol information block，SIB)中向下递交该接入网设备的无线链路控制(radio link control，RLC)层，接入网设备的RLC层将携带第四信息SIB通过逻辑信道中的广播控制信道(broadcast control channel，BCCH)发送给接入网设备的媒体接入控制(media access control，MAC)层的下行共享信道(downlink-shared channel，DL-SCH)，通过DL-SCH传输给物理层中的物理下行共享信道(physical downlink shared channel，PDSCH)，通过PDSCH广播出去。
方式二、将第四信息携带在主信息块(master information block，MIB)中发送出去。
例如，如图7所示，接入网设备的RRC层可以将获取到的第四信息携带在MIB中，并将MIB发送给接入网设备的RLC层，由接入网设备的RLC层通过BCCH发送给接入网设备的MAC层中的广播信道(broadcast channel，BCH)，经过BCH传输给物理广播信道(physical broadcast channel，PBCH)，通过PBCH广播出去。
方式三、将第四信息携带在寻呼(paging)消息中广播出去。
例如，如图7所示，接入网设备的RRC层可以将获取到的第四信息携带在寻呼(paging)消息中，并将paging消息发送给接入网设备的RLC层的寻呼控制信道(paging control channel，PCCH)，通过PCCH发送给接入网设备的MAC层的寻呼信道(paging channel，PCH)，经过PCH传输给PDSCH，通过PDSCH广播出去。
方式四、将第四信息携带在RRC消息中，通过信令无线承载广播RRC消息。
其中，信令无线承载可以是SRB0。以SRB0为例，例如，如图7所示，接入网设备的RRC层可以将获取到的第四信息携带在下行公共控制信道消息(downlink common control channel-message，DL-CCCH-message)中，将携带第四信息的DL-CCCH-message通过SRB0发送给接入网设备的RLC层中的公共控制信道(common control channel，CCCH)，通过CCCH将第四信息发送给DL-SCH，经过DL-SCH传输给PDSCH，通过PDSCH广播出去。
示例性的，在上述方式一、方式三、方式四所示情况下，终端可以接收携带第四信息的PDSCH，从PDSCH中获取第四信息；或者，在上述方式二所示情况下，终端可以接收PBCH，从PBCH中获取第四信息。
S604：终端根据第四信息和加扰的下行控制信息，接收来自接入网设备的多播业务的数据。
示例性的，终端可以根据第四信息携带的多播业务的标识信息确定终端对该多播业务感兴趣，则终端利用第四信息携带的多播业务的无线网络临时标识对接收到的加扰的下行控制信息进行解扰，如果解扰成功，则在解扰的下行控制信息指示的时频资源位置上接收来自接入网设备的PDSCH，从PDSCH中获取多播业务的数据。
应理解，本申请实施例不限定该过程中各个步骤的执行顺序，可以如前所述，先确定终端对多播业务感兴趣，再利用多播业务的无线网络临时标识得到解扰的下行控制信息，也可以先利用多播业务的无线网络临时标识得到解扰的下行控制信息，再确定终端对多播业务感兴趣，进而根据解扰的下行控制信息接收多播业务的数据，不予限制。
其中终端对多播业务感兴趣可以替换描述为终端存在接收多播业务的数据的需求，或者终端期望接收多播业务的数据，或者终端存在多播业务需求等。
基于图6所示方法，当多播群组中存在处于空闲态或者非激活态的终端时，发送多播业务的标识信息以及多播业务的无线网络临时标识，便于多播群组中的终端接收到多播业务的标识信息以及多播业务的无线网络临时标识，并在对该多播业务感兴趣的情况下，利用多播业务的无线网络临时标识接收多播业务的数据，解决处于空闲态或者非激活态的终端，因与接入网设备断开RRC连接而无法接收到多播业务的数据的问题。
上述主要从各个节点之间交互的角度对本申请实施例提供的方案进行了介绍。可以理解的是，各个节点，例如终端、接入网设备等为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对终端、接入网设备等进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
图8示出了一种通信装置80的结构图，该通信装置80可以为终端、终端中的芯片、片上系统或者其他能够实现上述方法中终端的功能的装置等。该通信装置80可以用于执行上述方法实施例中涉及的终端的功能。作为一种可实现方式，图8所示通信装置80包括：处理单元801、接收单元802以及发送单元803。
一种可能的设计中，处理单元801，用于确定终端位于第一接入网设备的服务区域之外。例如处理单元801可以用于支持通信装置80执行S501。
发送单元803，用于向第二接入网设备发送用于通知终端移出第一区域的第一信息。例如，发送单元803可以支持通信装置80执行S502。
一种可能的设计中，接收单元802，用于接收来自接入网设备的包括多播业务的标识信息以及多播业务的无线网络临时标识的第四信息、加扰的下行控制信息，根据所述第四信息和所述加扰的下行控制信息，接收来自所述接入网设备的所述多播业务的数据。例如，接收单元802可以支持终端执行S603以及S604。
具体的，该通信装置的具体实现方式可以参考第一方面或第一方面的任一种可能的设计或第五方面或第五方面的任一可能的设计所述的方法中终端的行为功能，不再 重复赘述。
具体的，上述图5a-图6所示方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。通信装置80用于执行图5a-图6所示方法所示多播业务的通信方法中终端的功能，因此可以达到与上述多播业务的通信方法相同的效果。
作为又一种可实现方式，图8所示通信装置80包括：处理模块和通信模块。处理模块用于对通信装置80的动作进行控制管理，例如，处理模块可以集成处理单元801的功能。通信模块可以集成发送单元803和接收单元802的功能，执行S502、S603、S604以及与其他网络实体的通信，例如与图3示出的功能模块或网络实体之间的通信。进一步的，该通信装置80还可以包括存储模块，用于存储指令和/或数据。该指令被处理模块执行时，使得处理模块实现上述终端侧的方法。
其中，处理模块可以是处理器、控制器、模块或电路。其可以实现或执行结合本申请实施例公开内容所描述的各种示例性的逻辑方框。通信模块可以是收发电路、管脚、接口电路、总线接口、或通信接口等。存储模块可以是存储器。当处理模块为处理器，通信模块为通信接口，存储模块为存储器时，本申请实施例涉及的通信装置80可以为图4所示通信装置400。
图9示出了一种通信装置90的结构图，该通信装置90可以为第二接入网设备、第二接入网设备中的芯片、片上系统或者其他能够实现上述方法中第二接入网设备的功能的装置等。该通信装置90可以用于执行上述方法实施例中涉及的第二接入网设备的功能。作为一种可实现方式，图9所示通信装置90包括：接收单元901、发送单元902。
接收单元901，用于接收来自终端的用于通知终端移出第一区域的第一信息。例如，接收单元901可以支持通信装置90执行S502。
发送单元902，用于根据第一信息，向第一接入网设备发送第二信息或者第三信息，其中，第二信息用于通知更新多播业务的上下文，第三信息用于从第一接入网设备提取终端的UE上下文。例如，发送单元902可以支持通信装置90执行S503。
具体的，上述图5a所示方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。通信装置90用于执行图5a所示方法所示多播业务的通信方法中第二接入网设备的功能，因此可以达到与上述多播业务的通信方法相同的效果。
作为又一种可实现方式，图9所示通信装置90包括：处理模块和通信模块。处理模块用于对通信装置90的动作进行控制管理。通信模块可以集成接收单元901、发送单元902的功能，如执行S502、S503等以及与其他网络实体的通信，例如与图4或图5a示出的功能模块或网络实体之间的通信。进一步的，该通信装置90还可以包括存储模块，用于存储指令和/或数据。该指令被处理模块执行时，使得处理模块实现第二接入网设备侧的方法。
其中，处理模块可以是处理器、控制器、模块或电路。其可以实现或执行结合本申请实施例公开内容所描述的各种示例性的逻辑方框。通信模块可以是收发电路、管脚、接口电路、总线接口、或通信接口等。存储模块可以是存储器。当处理模块为处 理器，通信模块为通信接口，存储模块为存储器时，本申请实施例涉及的通信装置90可以为图4所示通信装置400。
图10示出了一种通信装置100的结构图，该通信装置100可以为第一接入网设备、第一接入网设备中的芯片、片上系统或者其他能够实现上述方法中第一接入网设备的功能的装置等。或者可以为接入网设备、接入网设备中的芯片、片上系统或者其他能够实现上述方法中接入网设备的功能的装置等。该通信装置100可以用于执行上述方法实施例中涉及的第一接入网设备/接入网设备的功能。作为一种可实现方式，图10所示通信装置100包括：处理单元1001、接收单元1002以及发送单元1003。
一种可能的设计中，接收单元1002，用于接收来自第二接入网设备的用于更新多播业务的上下文的第二信息，或接收来自第二接入网设备的用于从第一接入网设备提取终端的用户设备UE上下文的第三信息。例如，接收单元1002可以支持通信装置100执行S503。
处理单元1001，用于根据第二信息，更新多播业务的上下文；或，根据第三信息更新通过第一接入网设备加入多播群组的终端的数量。例如，处理单元1001和/或发送单元1003可以支持通信装置执行S504a以及S504b。
具体的，上述图5a-图5b所示方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。通信装置100用于执行图5a-图5b所示方法所示多播业务的通信方法中第一接入网设备的功能，因此可以达到与上述多播业务的通信方法相同的效果。
又一种可能的设计中，处理单元1001，用于根据多播业务的标识信息分配多播业务的无线网络临时标识，根据多播业务的无线网络临时标识，获得加扰的下行控制信息。例如，处理单元1001可以用于支持通信装置100执行S601以及S602。
发送单元1003，用于发送第四信息以及加扰的下行控制信息。例如发送单元1003可以支持通信装置100执行S603。
具体的，上述图6所示方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。通信装置100用于执行图6所示方法所示多播业务的通信方法中接入网设备的功能，因此可以达到与上述多播业务的通信方法相同的效果。
作为又一种可实现方式，图10所示通信装置100包括：处理模块和通信模块。处理模块用于对通信装置100的动作进行控制管理，执行S504a、S504b、S601以及S602等。通信模块可以集成接收单元1002、发送单元1003的功能，如执行S603等以及与其他网络实体的通信，例如与图4或图5a示出的功能模块或网络实体之间的通信。进一步的，该通信装置100还可以包括存储模块，用于存储指令和/或数据。该指令被处理模块执行时，使得处理模块实现上述第一接入网设备/接入网设备的方法。
其中，处理模块可以是处理器、控制器、模块或电路。其可以实现或执行结合本申请实施例公开内容所描述的各种示例性的逻辑方框。通信模块可以是收发电路、管脚、接口电路、总线接口、或通信接口等。存储模块可以是存储器。当处理模块为处理器，通信模块为通信接口，存储模块为存储器时，本申请实施例涉及的通信装置100可以为图4所示通信装置400。
在本申请实施例中，处理器可以是通用处理器、数字信号处理器、专用集成电路、现场可编程门阵列或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。
在本申请实施例中，存储器可以是非易失性存储器，比如硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)等，还可以是易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)。存储器是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。本申请实施例中的存储器还可以是电路或者其它任意能够实现存储功能的装置，用于存储指令和/或数据。
图11为本申请实施例提供的一种通信系统的结构图，如图11所示，该通信系统可以包括：终端110、第一接入网设备111以及第二接入网设备112。终端110可以处于非激活态。需要说明的是，图11仅为示例性附图，本申请实施例不限定图11所示通信系统包括的网元以及网元的个数。
其中，终端110具有上述图5a至图5b所示方法中终端的功能。第一接入网设备111具有上述图5a至图5b所示方法中第一接入网设备的功能。第二接入网设备112具有上述图5a至图5b所示方法中第二接入网设备的功能。
图12为本申请实施例提供的一种通信系统的结构图，如图12所示，该通信系统可以包括：多个终端120、接入网设备121。多个终端120中存在处于非激活态或空闲态的终端。需要说明的是，图12仅为示例性附图，本申请实施例不限定图12所示通信系统包括的网元以及网元的个数。
其中，终端120具有上述图6所示方法中终端的功能。接入网设备121具有上述图6方法中接入网设备的功能。
在本申请实施例中，“/”可以表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；“和/或”可以用于描述关联对象存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。为了便于描述本申请实施例的技术方案，在本申请实施例中，可以采用“第一”、“第二”等字样对功能相同或相似的技术特征进行区分。该“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。在本申请实施例中，“示例性的”或者“例如”等词用于表示例子、例证或说明，被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
在本申请实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
应理解，在本申请实施例中，“与A对应的B”表示B与A相关联。例如，可以根据A可以确定B。还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。此外，本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式，以实现设备间的通信，本申请实施例对此不做任何限定。
本申请实施例中出现的“传输”(transmit/transmission)如无特别说明，是指双向传输，包含发送和/或接收的动作。具体地，本申请实施例中的“传输”包含数据的发送，数据的接收，或者数据的发送和数据的接收。或者说，这里的数据传输包括上行和/或下行数据传输。数据可以包括信道和/或信号，上行数据传输即上行信道和/或上行信号传输，下行数据传输即下行信道和/或下行信号传输。本申请实施例中出现的“网络”与“系统”表达的是同一概念，通信系统即为通信网络。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
本申请实施例提供的技术方案可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、无线控制装置、接入网设备、终端或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机可以存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，数字视频光盘(digital video disc，DVD))、或者半导体介质等。
在本申请实施例中，在无逻辑矛盾的前提下，各实施例之间可以相互引用，例如方法实施例之间的方法和/或术语可以相互引用，例如装置实施例之间的功能和/或术语可以相互引用，例如装置实施例和方法实施例之间的功能和/或术语可以相互引用。
以上所述，仅为本申请实施例的具体实施方式，但本申请实施例的保护范围并不局限于此，任何在本申请实施例揭露的技术范围内的变化或替换，都应涵盖在本申请实施例的保护范围之内。因此，本申请实施例的保护范围应以所述权利要求的保护范围为准。

Claims (37)

  1. 一种多播业务的通信方法，其特征在于，所述方法应用于处于无线资源控制非激活RRC inactive态的终端从第一接入网设备移动到第二接入网设备，且所述终端通过所述第一接入网设备加入多播业务对应的多播群组，所述方法包括：
    当所述终端确定所述终端位于第一区域之外时，所述终端向所述第二接入网设备发送第一信息，所述第一信息用于通知所述终端移出所述第一区域，所述第一区域为所述第一接入网设备的服务区域。
  2. 根据权利要求1所述的方法，其特征在于，
    所述第一信息包括组播业务的标识信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一信息还包括所述终端的无线网络临时标识，所述终端的无线网络临时标识包括所述第一接入网设备的标识。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述第一信息携带在第一无线资源控制RRC消息中；
    其中，所述第一RRC消息用于请求恢复所述终端的RRC连接；或者，所述第一RRC消息用于触发所述第二接入网设备向所述第一接入网设备发送第二信息或者第三信息；
    所述第二信息用于更新所述多播业务的上下文，所述第三信息用于从所述第一接入网设备提取所述终端的用户设备UE上下文。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述终端向第二接入网设备发送第一信息，包括：
    所述终端通过信令无线承载向所述第二接入网设备发送所述第一信息。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述终端接收来自所述第一接入网设备的所述第一区域的信息。
  7. 根据权利要求6所述的方法，其特征在于，所述第一区域的信息携带在第二RRC消息中；其中，所述第二RRC消息用于暂停所述终端的RRC连接。
  8. 一种多播业务的通信方法，其特征在于，所述方法应用于终端从第一接入网设备移动到第二接入网设备，且所述终端处于无线资源控制非激活RRC inactive态，所述方法包括：
    第二接入网设备接收来自终端的第一信息，其中，所述第一信息用于通知所述终端移出所述第一区域，所述第一区域为所述第一接入网设备的服务区域；
    所述第二接入网设备根据所述第一信息，向所述第一接入网设备发送第二信息或第三信息，其中，所述第二信息用于更新所述多播业务的上下文，所述第三信息用于从所述第一接入网设备提取所述终端的用户设备UE上下文。
  9. 根据权利要求8所述的方法，其特征在于，
    所述第一信息包括多播业务的标识信息。
  10. 根据权利要求8或9所述的方法，其特征在于，
    所述第一信息还包括所述终端的无线网络临时标识，
    所述终端的无线网络临时标识包括所述第一接入网设备的标识。
  11. 根据权利要求10所述的方法，其特征在于，所述第二接入网设备根据所述第 一信息，向所述第一接入网设备发送第二信息或第三信息，包括：
    所述第二接入网设备根据所述第一接入网设备的标识，向所述第一接入网设备发送所述第二信息或第三信息。
  12. 根据权利要求8-11任一项所述的方法，其特征在于，
    所述第二信息包括所述多播业务的标识信息。
  13. 根据权利要求8-12任一项所述的方法，其特征在于，
    所述第二信息、所述第三信息携带在提取UE上下文请求中；或者，
    所述第二信息、所述第三信息携带在Xn消息中。
  14. 一种多播业务的通信方法，其特征在于，所述方法应用于处于无线资源控制非激活RRC inactive态的终端从第一接入网设备移动到第二接入网设备，且所述终端通过所述第一接入网设备加入多播业务对应的多播群组，所述方法包括：
    第一接入网设备接收来自第二接入网设备的第二信息；其中，所述第二信息用于更新所述多播业务的上下文；
    所述第一接入网设备根据所述第二信息，更新所述多播业务的上下文。
  15. 根据权利要求14所述的方法，其特征在于，
    所述第二信息包括所述多播业务的标识信息。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第一接入网设备根据所述第二信息，更新所述多播业务的上下文，包括：
    所述第一接入网设备根据所述第二信息，更新所述多播业务的上下文中通过所述第一接入网设备加入所述多播群组的终端的数量。
  17. 根据权利要求15或16所述的方法，其特征在于，所述第二信息还包括所述终端的标识信息，所述第一接入网设备根据所述第二信息，更新所述多播业务的上下文，包括：
    所述第一接入网设备根据所述第二信息，删除所述多播业务的上下文中所述终端的标识信息。
  18. 根据权利要求14所述的方法，其特征在于，所述第二信息包括所述终端的无线网络临时标识；所述第一接入网设备根据所述第二信息，更新所述多播业务的上下文，包括：
    所述第一接入网设备根据所述终端的无线网络临时标识，获取所述终端的用户设备UE上下文中所述多播业务的标识信息；
    所述第一接入网设备根据所述获取的所述多播业务的标识信息，删除所述多播业务的上下文中所述终端的标识信息，或者，更新所述多播业务的上下文中通过所述第一接入网设备加入所述多播群组的终端的数量。
  19. 根据权利要求14-18任一项所述的方法，其特征在于，
    所述第二信息携带在提取UE上下文请求中或Xn消息中。
  20. 一种多播业务的通信方法，其特征在于，所述方法应用于处于无线资源控制非激活RRC inactive态的终端从第一接入网设备移动到第二接入网设备，且所述终端通过所述第一接入网设备加入多播业务对应的多播群组，所述方法包括：
    所述第一接入网设备接收来自第二接入网设备的第三信息；其中，所述第三信息 用于从所述第一接入网设备提取终端的用户设备UE上下文；
    所述第一接入网设备根据所述第三信息，更新通过所述第一接入网设备加入所述多播群组的终端的数量。
  21. 根据权利要求20所述的方法，其特征在于，所述方法还包括：
    所述第一接入网设备删除所述终端的用户设备UE上下文中所述多播业务的标识信息。
  22. 根据权利要求20或21所述的方法，其特征在于，
    所述第三信息包括所述多播业务的标识信息。
  23. 根据权利要求20-22任一项所述的方法，其特征在于，所述第一接入网设备根据所述第三信息，更新通过所述第一接入网设备加入所述多播群组的终端的数量包括：
    所述第一接入网设备根据所述第三信息，获取所述终端的UE上下文，所述终端的UE上下文包括所述多播业务的标识信息；
    所述第一接入网设备根据所述多播业务的标识信息，更新所述多播业务的上下文中通过所述第一接入网设备加入所述多播群组的终端的数量。
  24. 根据权利要求14-23中任一项的方法，其特征在于，所述方法还包括：
    所述第一接入网设备向所述终端发送第一区域的信息，所述第一区域为所述第一接入网设备的服务区域。
  25. 一种多播业务的通信方法，其特征在于，所述方法包括：
    接入网设备根据多播业务的标识信息，分配所述多播业务的无线网络临时标识；
    所述接入网设备根据所述多播业务的无线网络临时标识，获得加扰的下行控制信息；
    所述接入网设备发送第四信息和所述加扰的下行控制信息，所述第四信息包括所述多播业务的标识信息以及所述多播业务的无线网络临时标识。
  26. 根据权利要求25所述的方法，其特征在于，
    所述第四信息携带在系统信息块SIB中；或者，
    所述第四信息携带在主信息块MIB中；或者，
    所述第四信息携带在寻呼paging消息中。
  27. 根据权利要求25所述的方法，其特征在于，所述接入网设备发送所述第四信息包括：
    所述接入网设备通过信令无线承载SRB，发送所述第四信息。
  28. 一种多播业务的通信方法，其特征在于，所述方法包括：
    终端接收来自接入网设备的第四信息和加扰的下行控制信息，所述第四信息包括多播业务的标识信息以及所述多播业务的无线网络临时标识；
    所述终端根据所述第四信息和所述加扰的下行控制信息，接收来自所述接入网设备的所述多播业务的数据。
  29. 根据权利要求28所述的方法，其特征在于，所述终端根据所述第四信息和所述加扰的下行控制信息，接收来自所述接入网设备的所述多播业务的数据，包括：
    当所述终端对所述多播业务感兴趣时，所述终端根据所述多播业务的无线网络临时标识，获得解扰的下行控制信息；
    所述终端根据所述解扰的下行控制信息，接收来自所述接入网设备的所述多播业务的数据。
  30. 根据权利要求28或29所述的方法，其特征在于，
    所述第四信息携带在系统信息块SIB中；或者，
    所述第四信息携带在主信息块MIB中；或者，
    所述第四信息携带在寻呼paging消息中。
  31. 根据权利要求28或29所述的方法，其特征在于，所述终端接收来自接入网设备的第四信息，包括：
    所述终端通过信令无线承载SRB，接收来自所述接入网设备的所述第四信息。
  32. 一种通信系统，其特征在于，所述通信系统应用于处于无线资源控制非激活RRC inactive态的终端从第一接入网设备移动到第二接入网设备，且所述终端通过所述第一接入网设备加入多播业务对应的多播群组，所述通信系统包括：
    终端，用于当确定所述终端位于第一区域之外时，向所述第二接入网设备发送第一信息，所述第一信息用于通知所述终端移出所述第一区域，所述第一区域为所述第一接入网设备的服务区域；
    所述第二接入网设备，用于接收来自所述终端的所述第一信息，根据所述第一信息，向所述第一接入网设备发送第二信息或第三信息，其中，所述第二信息用于更新所述多播业务的上下文，所述第三信息用于从所述第一接入网设备提取所述终端的用户设备UE上下文；
    所述第一接入网设备，用于接收来自所述第二接入网设备的所述第二信息，根据所述第二信息更新所述多播业务的上下文；或者接收来自所述第二接入网设备的所述第三信息，根据所述第三信息，更新通过所述第一接入网设备加入所述多播群组的终端的数量。
  33. 一种通信系统，其特征在于，所述通信系统包括：
    接入网设备，用于根据多播业务的标识信息，分配所述多播业务的无线网络临时标识，根据所述多播业务的无线网络临时标识，获得加扰的下行控制信息，发送第四信息和所述加扰的下行控制信息，所述第四信息包括所述多播业务的标识信息以及所述多播业务的无线网络临时标识；
    终端，用于接收来自所述接入网设备的所述第四信息和所述加扰的下行控制信息，根据所述第四信息和所述加扰的下行控制信息，接收来自所述接入网设备的所述多播业务的数据。
  34. 一种通信装置，其特征在于，所述通信装置包括处理器和存储器，
    所述存储器，用于存储计算机程序代码，所述计算机程序代码包括计算机指令；
    所述处理器，用于当所述处理器执行所述计算机指令时，执行如权利要求1-7任一项所述的通信方法，或者执行如权利要求8-13任一项所述的通信方法，或者执行如权利要求14-19任一项所述的通信方法，或者如权利要求20-24任一项所述的通信方法，或者如权利要求25-27任一项所述的通信方法，或者如权利要求28-31任一项所述的通信方法。
  35. 一种计算机可读存储介质，其中，所述计算机可读存储介质存储计算机指令， 当所述计算机指令在计算机上运行时，使得计算机执行如权利要求1-7任一项所述的通信方法，或者执行如权利要求8-13任一项所述的通信方法，或者执行如权利要求14-19任一项所述的通信方法，或者如权利要求20-24任一项所述的通信方法，或者如权利要求25-27任一项所述的通信方法，或者如权利要求28-31任一项所述的通信方法。
  36. 一种计算机程序产品，其中，所述计算机程序产品包括计算机指令，当所述计算机指令在计算机上运行时，使得计算机执行如权利要求1-7任一项所述的通信方法，或者执行如权利要求8-13任一项所述的通信方法，或者执行如权利要求14-19任一项所述的通信方法，或者如权利要求20-24任一项所述的通信方法，或者如权利要求25-27任一项所述的通信方法，或者如权利要求28-31任一项所述的通信方法。
  37. 一种芯片，其特征在于，所述芯片与存储器耦合，用于读取并执行所述存储器中存储的程序指令，以实现如权利要求1-7任一项所述的通信方法，或者执行如权利要求8-13任一项所述的通信方法，或者执行如权利要求14-19任一项所述的通信方法，或者如权利要求20-24任一项所述的通信方法，或者如权利要求25-27任一项所述的通信方法，或者如权利要求28-31任一项所述的通信方法。
PCT/CN2022/075884 2021-06-30 2022-02-10 一种多播业务的通信方法、装置及系统 WO2023273355A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110745567.1A CN115551082A (zh) 2021-06-30 2021-06-30 一种多播业务的通信方法、装置及系统
CN202110745567.1 2021-06-30

Publications (1)

Publication Number Publication Date
WO2023273355A1 true WO2023273355A1 (zh) 2023-01-05

Family

ID=84689875

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/075884 WO2023273355A1 (zh) 2021-06-30 2022-02-10 一种多播业务的通信方法、装置及系统

Country Status (2)

Country Link
CN (1) CN115551082A (zh)
WO (1) WO2023273355A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010071830A1 (en) * 2008-12-19 2010-06-24 Qualcomm Incorporated Managing a multicast group membership table at an access network within a wireless communications system
CN110786047A (zh) * 2017-09-04 2020-02-11 Oppo广东移动通信有限公司 用于无线通信的方法和设备
CN111615167A (zh) * 2019-02-26 2020-09-01 电信科学技术研究院有限公司 一种位置报告的方法、无线接入网实体及计算机存储介质
WO2021077434A1 (zh) * 2019-10-26 2021-04-29 华为技术有限公司 一种通信方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2010071830A1 (en) * 2008-12-19 2010-06-24 Qualcomm Incorporated Managing a multicast group membership table at an access network within a wireless communications system
CN110786047A (zh) * 2017-09-04 2020-02-11 Oppo广东移动通信有限公司 用于无线通信的方法和设备
CN111615167A (zh) * 2019-02-26 2020-09-01 电信科学技术研究院有限公司 一种位置报告的方法、无线接入网实体及计算机存储介质
WO2021077434A1 (zh) * 2019-10-26 2021-04-29 华为技术有限公司 一种通信方法及装置

Also Published As

Publication number Publication date
CN115551082A (zh) 2022-12-30

Similar Documents

Publication Publication Date Title
WO2021077434A1 (zh) 一种通信方法及装置
CN107211297B (zh) 一种由远端无线发射/接收单元执行的用于选择中继节点的方法及无线发射/接收单元
US10015715B2 (en) Method of receiving MBMS service in wireless communication system and apparatus thereof
US9294886B2 (en) Evolved multimedia broadcast/multicast services (eMBMS) geo-location based group call
EP3592008A1 (en) Method and device for using ladn in wireless communication system
US20150079979A1 (en) Seamless and resource efficient roaming for group call services on broadcast/multicast networks
US20150341494A1 (en) Method, system, base station and cluster EPC for establishing group call context
WO2022205381A1 (zh) 广播多播业务传输方法、装置及存储介质
US20230096763A1 (en) Ran-5gc interactions for session join, session start, session leave, session stop, and session delete for 5g multicast broadcast services
WO2022017527A1 (zh) 一种数据传输方法、装置以及系统
WO2016107205A1 (zh) 中继通信的数据传输方法和装置
WO2014166439A1 (zh) 集群多播决策方法、集群终端、集群服务器及存储介质
US20230018974A1 (en) Multicast communication method and communication apparatus
WO2014166440A1 (zh) 集群中继方法、装置、系统及存储介质
US20230188949A1 (en) Communication method, apparatus, and system
US20200015194A1 (en) Paging method and apparatus for wireless communication
WO2018010583A1 (zh) 网络系统
US20230156436A1 (en) Data Transmission Method, Apparatus, and System
TW201804838A (zh) 數據傳輸的方法、接入網設備、終端設備和網絡實體
WO2022253291A1 (zh) 一种信息处理方法、装置、设备、介质和芯片
WO2023273355A1 (zh) 一种多播业务的通信方法、装置及系统
US20210352443A1 (en) Multicast Broadcast Service for 5G New Radio
US20240080931A1 (en) Communication method and apparatus
WO2023185328A1 (zh) 一种通信方法及装置
WO2017000591A1 (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: 22831188

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE