WO2024027403A1 - 通信方法和通信装置 - Google Patents

通信方法和通信装置 Download PDF

Info

Publication number
WO2024027403A1
WO2024027403A1 PCT/CN2023/103974 CN2023103974W WO2024027403A1 WO 2024027403 A1 WO2024027403 A1 WO 2024027403A1 CN 2023103974 W CN2023103974 W CN 2023103974W WO 2024027403 A1 WO2024027403 A1 WO 2024027403A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
cell
terminal device
multicast service
connected state
Prior art date
Application number
PCT/CN2023/103974
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 WO2024027403A1 publication Critical patent/WO2024027403A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • 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/0055—Transmission or use of information for re-establishing the radio link
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the embodiments of the present application relate to the field of communication, and more specifically, to a communication method and a communication device.
  • Multicast and Broadcast Service is a service for multiple terminal equipment (User Equipment, UE), such as live broadcast service, public safety service, batch software update service, etc.
  • MBS services come from data servers. Among them, the data server sends the MBS data to the core network device, then the core network device sends the MBS data to the base station, and finally the base station sends the MBS data to at least one terminal device that receives the MBS service.
  • the MBS service is transmitted through a common transmission channel MBS session, and each MBS session can contain at least one MBS QoS flow.
  • the base station sends MBS data to the terminal device, the data packet is transmitted through the MBS wireless bearer.
  • MBS wireless bearer There are two transmission modes for an MBS wireless bearer: the first one can use point to multi-point (PTM) Transmission method; the second one can use point to point (PTP) transmission method.
  • PTM point to multi-point
  • PTP point to point
  • Multicast services are designed for services with high QoS requirements. They require group management for multicast services and can provide the same QoS level as unicast services.
  • the core network needs to manage the joining and exiting of terminal devices.
  • For transmission between the core network and the base station a new MBS QoS flow is introduced based on PDU session.
  • RAN radio access network
  • PTP and PTM transmission methods are supported to send data to terminal devices, and dynamic switching between PTP and PTM controlled by RAN is supported.
  • multicast services can only be provided to terminal devices in the radio resource control (RRC) connected state, and the access network and core network need to maintain information about the terminal devices corresponding to the multicast service group.
  • RRC radio resource control
  • Embodiments of the present application provide a communication method that can avoid the terminal device from initiating unnecessary request information to establish a connection or restore a connection when switching or reselecting from the first cell, thereby reducing resource consumption.
  • a communication method including: a terminal device receiving first information, the first information being related to the status of the first multicast service, and/or the first information being related to the first group in the second cell.
  • the terminal equipment is related to the configuration information of the multicast service; the terminal equipment determines whether to send the first request information to the second cell based on the first information.
  • the first request information is used for the terminal equipment to establish or restore the RRC connection, where the terminal equipment is to receive the first multicast
  • the terminal equipment of the service is a terminal equipment in the radio resource control RRC non-connected state, and the terminal equipment is a terminal equipment that switches from the first cell or is reselected to the second cell.
  • the terminal device receives the first information and determines whether to send the first request information to the second cell based on the first information.
  • the first request information is used for the terminal device to switch from the first cell or Reselect to the second cell to establish or restore the RRC connection.
  • the first information is related to the status of the first multicast service, and/or the first information is related to the configuration information of the first multicast service in the second cell, thereby preventing the terminal equipment from switching or resetting from the first cell.
  • unnecessary request information for establishing a connection or resuming a connection is initiated, reducing resource consumption.
  • the method provided by this application can also avoid aggravating network congestion.
  • the terminal device determines whether to send the first request information to the second cell based on the first information, including: when the status of the first multicast service is active, the terminal device sends the first request information to the second cell.
  • the second cell sends the first request information, or when the status of the first multicast service is an inactive state, the terminal device remains in a non-connected state.
  • the terminal device determines whether to send the first request information to the second cell according to the status of the first multicast service, or the terminal device continues to remain non-
  • the connection status prevents the terminal device from initiating access without judging the service status. After the second cell accesses the connected status, the service is deactivated and released, resulting in a waste of resources.
  • the terminal device determines whether to send the first request information to the second cell based on the first information, including: when the first multicast service configuration information is between the first cell and the second cell At the same time, the terminal device sends the first request information to the second cell, or when the configuration information of the first multicast service in the first cell and the second cell is the same, the terminal device remains in a non-connected state.
  • the terminal device determines whether to send the first request to the second cell according to the configuration information of the first multicast service in the second cell. information, or the terminal device continues to remain in a non-connected state to prevent the terminal device from initiating access without knowing whether the configuration is the same. After the second cell accesses the connected state, it is released again, which may cause unnecessary access due to the same configuration. , causing a waste of resources.
  • the terminal device determines whether to send the first request information to the second cell based on the first information, including: when the configuration information of the first multicast service in the first cell and the second cell When the configuration information of the first multicast service in the first cell and the second cell is the same, and the status of the first multicast service is active, the terminal device sends the first request information to the second cell. When the status of the multicast service is deactivated, the terminal device remains in the non-connected state.
  • the terminal device determines the status of the first multicast service and the configuration information of the first multicast service in the second cell.
  • the configuration information of the broadcast service is used to determine whether to send the first request information to the second cell, or the terminal device continues to remain in a non-connected state to prevent the terminal device from being released again after the second cell accesses the connected state, causing resource degradation. waste.
  • the terminal device receives a first paging message, and the first paging message includes an identifier of the first multicast service.
  • the terminal device determines that the first multicast service is activated, Or need to enter the connected state. For example, the terminal device sends the first request information to the second cell according to the first paging message and enters the connected state.
  • the terminal device receives second information, and the second information is used to determine that the second cell does not provide the first multicast service to the terminal device in the non-connected state.
  • the terminal device receives second information.
  • the second information may come from the first cell or the second cell.
  • the second information is used to determine that the second cell does not provide the first multicast service to the non-connected terminal device.
  • the terminal device further determines whether to send the first request information to the second cell according to the status of the first multicast service and/or the configuration information of the first multicast service in the second cell.
  • the second information may directly indicate that the second cell does not support the non-connected multicast service, or the second information may indicate that the second cell supports the non-connected multicast service, but the non-connected multicast service provided by the second cell
  • the multicast service in the connected state does not include the first multicast service, and this application does not limit this.
  • the terminal device when the second information includes the configuration information of the multicast control channel MCCH of the second cell, the terminal device obtains the third information according to the configuration information of the MCCH, and the third information includes the second MCCH information of the cell, and the MCCH information does not include the identifier of the first multicast service, or the terminal device does not obtain the third information according to the MCCH configuration information.
  • the second information includes the MCCH configuration information of the second cell, it indicates that the second cell supports the non-connected multicast service.
  • the terminal device obtains the third information based on the MCCH configuration information.
  • the third information includes MCCH information.
  • the MCCH information does not include the identifier of the first multicast service, it means that the second cell supports the non-connected state multicast service, but the second cell does not provide the first multicast service to the terminal equipment in the non-connected state.
  • the second information received by the terminal equipment includes MCCH configuration information, but the terminal equipment does not obtain the third information based on the MCCH configuration information, which indicates that the second cell does not provide the non-connected terminal with The device provides multicast services.
  • the first information is carried in at least one of the following messages: paging message, system information block SIB, and MCCH information. Based on the above solution, the first information is carried in at least one of the paging message, the system information block SIB, and the MCCH information and is sent to the terminal device. The terminal device can receive the first information without entering the connected state.
  • the terminal device obtains the first information, which may be obtained when the terminal device is in the connected state, or the first information may be obtained through an RRC release message (RRC release message), which is not limited in this application.
  • RRC release message RRC release message
  • the first information when the first information is related to the configuration information of the first multicast service in the second cell, the first information includes PDCP synchronization information of the second cell and/or PDCP synchronization information of the first cell.
  • the synchronization information includes PDCP synchronization or non-synchronization.
  • the first information when the first information is related to the configuration information of the first multicast service in the second cell, the first information may also include
  • the synchronization information includes the PDCP synchronization information of the second cell and/or the PDCP synchronization information of the first cell.
  • the synchronization information includes the PDCP synchronization information of the second cell and/or the PDCP synchronization of the first cell.
  • the terminal device further determines the processing method of the PDCP layer according to the PDCP synchronization information of the second cell and/or the PDCP synchronization information of the first cell.
  • the terminal device when the PDCP of the second cell and/or the PDCP of the first cell included in the synchronization information are out of synchronization, the terminal device resets the PDCP entity or PDCP variable, and/or, the terminal device Discard the cached PDCP packets or submit them to higher layers.
  • the terminal device can reset the PDCP entity or PDCP variable, and/or the terminal device discards or submits the cached PDCP data packet. High-rise.
  • the terminal device when the PDCP of the first cell is out of synchronization and/or the PDCP of the second cell is out of synchronization, the terminal device sends the first request information to the second cell. After the terminal device and the second cell enter the connected state, in the second cell Receive PDCP configuration.
  • a communication method which method includes: a first cell determines first information, and the first information is related to the status of the first multicast service; and the first cell sends the first information to a terminal device, and the first information It is used to determine whether the terminal equipment sends the first request information to the second cell.
  • the first request information is used for the terminal equipment to establish or restore the RRC connection, wherein the terminal equipment is a terminal equipment that receives the first multicast service, and the terminal equipment is in a wireless state.
  • the resource controls the terminal equipment in the RRC non-connected state, and the terminal equipment is a terminal equipment that is switched or reselected from the first cell to the second cell.
  • the state of the first multicast service includes an activated state or a deactivated state.
  • the first cell sends second information to the terminal device, and the second information is used to determine that the second cell does not provide the first multicast service to the non-connected terminal device.
  • the first information is carried in at least one of the following messages: paging message, system information block SIB, and MCCH information.
  • the first information is carried in at least one of the paging message, the system information block SIB, and the MCCH information and is sent to the terminal device.
  • the terminal device can receive the first information without entering the connected state.
  • the terminal device obtains the first information, which may be obtained when the terminal device is in the connected state, or the first information may be obtained through an RRC release message (RRC release message), which is not limited in this application.
  • RRC release message RRC release message
  • a communication method which method includes: the second cell determines second information, and the second information is used to determine that the second cell does not provide the first multicast service to a terminal device in a non-connected state; the second cell Send the second information to the terminal device, where the terminal device is a terminal device that receives the first multicast service, the terminal device is a terminal device in the radio resource control RRC non-connected state, and the terminal device is switched or reselected from the first cell to the terminal equipment of the second cell.
  • the second cell sends third information to the terminal device, where the third information includes MCCH information of the second cell, and the MCCH information does not include the identifier of the first multicast service.
  • the second cell sends configuration information of the first multicast service in the second cell to the first network device, and the configuration information is used to determine the first information, where the first cell It is an adjacent cell to the second cell, or the second cell is a cell within a certain range of the first cell, or the first cell and the second cell are cells within the same RNA.
  • the second cell sends PDCP synchronization information of the second cell to the first network device, and the synchronization information includes PDCP synchronization or desynchronization.
  • a communication method includes: a first network device determines first information, and the first information is related to the configuration information of the first multicast service in the second cell; the first network device sends a message to the terminal The device sends first information.
  • the first information is used to determine whether the terminal device sends first request information to the second cell.
  • the first request information is used for the terminal device to establish or restore an RRC connection, where the terminal device is to receive the first multicast service.
  • the terminal equipment is a terminal equipment in a radio resource control (RRC) non-connected state, and the terminal equipment is a terminal equipment that switches from the first cell or is reselected to the second cell.
  • RRC radio resource control
  • the first network device receives configuration information from the first multicast service in the second cell, and the configuration information is used to determine the first information.
  • the first information includes PDCP synchronization information of the second cell, and the synchronization information Including PDCP synchronization or non-synchronization.
  • the first information is carried in at least one of the following messages: paging message, system information block SIB, and MCCH information.
  • the first information is carried in at least one of the paging message, the system information block SIB, and the MCCH information and is sent to the terminal device.
  • the terminal device can receive the first information without entering the connected state.
  • the terminal device obtains the first information, which may be obtained when the terminal device is in the connected state, or the first information may be obtained through an RRC release message (RRC release message), which is not limited in this application.
  • RRC release message RRC release message
  • a communication device receives first information, and the first information is related to the status of the first multicast service, and/or the first information is related to the first multicast service in the second cell. related to the configuration information; the processing unit determines whether to send the first request information to the second cell based on the first information.
  • the first request information is used for the terminal device to establish or restore the RRC connection, where the transceiver unit is a device that receives the first multicast service.
  • the transceiver unit, the transceiver unit and the processing unit belong to the terminal equipment in the radio resource control RRC non-connected state, and the terminal equipment is a terminal equipment that switches or reselects from the first cell to the second cell.
  • the processing unit determines whether to send the first request information to the second cell based on the first information, including: when the status of the first multicast service is active, the transceiver unit sends the first request information to the second cell.
  • the second cell sends the first request information, or when the status of the first multicast service is an inactive state, the processing unit remains in a non-connected state.
  • the processing unit determines whether to send the first request information to the second cell based on the first information, including: when the first multicast service in the first cell and the second cell When the configuration information is different, the transceiver unit sends the first request information to the second cell, or when the configuration information of the first multicast service in the first cell and the second cell is the same, the processing unit remains in a non-connected state.
  • the processing unit determines whether to send the first request information to the second cell based on the first information, including: when the configuration of the first multicast service in the first cell and the second cell When the information is the same and the status of the first multicast service is active, the transceiver unit sends the first request information to the second cell, or when the configuration information of the first multicast service in the first cell and the second cell is the same , and when the status of the first multicast service is deactivated, the processing unit remains in the non-connected state.
  • the transceiver unit receives a first paging message, and the first paging message includes an identifier of the first multicast service.
  • the transceiver unit receives second information, and the second information is used to determine that the second cell does not provide the first multicast service to the non-connected terminal device.
  • the processing unit when the second information includes the configuration information of the multicast control channel MCCH of the second cell, the processing unit obtains the third information according to the configuration information of the MCCH, and the third information includes the second MCCH information of the cell, and the MCCH information does not include the identifier of the first multicast service, or the terminal device does not obtain the third information according to the MCCH configuration information.
  • the first information is carried in at least one of the following messages: paging message, system information block SIB, and MCCH information.
  • the first information when the first information is related to the configuration information of the first multicast service in the second cell, the first information includes PDCP synchronization information of the first cell and/or PDCP synchronization information of the second cell.
  • the synchronization information includes PDCP synchronization or non-synchronization.
  • the processing unit when the PDCP of the first cell and/or the PDCP of the second cell included in the synchronization information are out of synchronization, the processing unit resets the PDCP entity or PDCP variable, and/or, the processing unit Discard the cached PDCP packets or submit them to higher layers.
  • a communication device determines first information, and the first information is related to the status of the first multicast service; the transceiver unit sends the first information to the terminal device, and the first information is used to determine whether the terminal device Send the first request information to the second cell.
  • the first request information is used for the terminal equipment to establish or restore the RRC connection, where the terminal equipment is a terminal equipment that receives the first multicast service, and the terminal equipment is in the radio resource control RRC non-connected state.
  • the terminal equipment is a terminal equipment that is switched or reselected from the first cell to the second cell.
  • the state of the first multicast service includes an activated state or a deactivated state.
  • the processing unit sends second information to the terminal device, and the second information is used to determine that the second cell does not provide the first multicast service to the non-connected terminal device.
  • the second information includes configuration information of the multicast control channel MCCH of the second cell. interest.
  • the first information is carried in at least one of the following messages: paging message, system information block SIB, and MCCH information.
  • the transceiver unit obtains the first information, which may also be obtained when in the connected state, or obtained through an RRC release message, which is not limited in this application.
  • a communication device determines second information, and the second information is used to determine that the second cell does not provide the first multicast service to the terminal equipment in the non-connected state; the transceiver unit sends the second multicast service to the terminal equipment.
  • Information wherein the terminal device is a terminal device that receives the first multicast service, the terminal device is a terminal device in the radio resource control RRC non-connected state, and the terminal device is a terminal that switches or reselects from the first cell to the second cell. equipment.
  • the processing unit sends third information to the terminal device, where the third information includes MCCH information of the second cell, and the MCCH information does not include the identifier of the first multicast service.
  • the processing unit sends configuration information of the first multicast service in the second cell to the first network device, and the configuration information is used to determine the first information, wherein the first cell and The second cell is an adjacent cell.
  • the processing unit sends PDCP synchronization information of the second cell to the first network device, where the synchronization information includes PDCP synchronization or desynchronization.
  • a communication method which method includes: the processing unit determines first information, the first information is related to the configuration information of the first multicast service in the second cell; and the transceiver unit sends the first information to the terminal device.
  • Information the first information is used to determine whether the terminal device sends the first request information to the second cell, and the first request information is used for the terminal device to establish or restore the RRC connection, where the terminal device is a terminal device that receives the first multicast service,
  • the terminal equipment is a terminal equipment in a radio resource control (RRC) non-connected state, and the terminal equipment is a terminal equipment that is switched or reselected from the first cell to the second cell.
  • RRC radio resource control
  • the transceiver unit receives configuration information from the first multicast service in the second cell, and the configuration information is used to determine the first information.
  • the first information includes PDCP synchronization information of the first cell and/or PDCP synchronization information of the second cell
  • the synchronization information includes PDCP synchronization or non-synchronization
  • the first information is carried in at least one of the following messages: paging message, system information block SIB, and MCCH information.
  • a communication device in a ninth aspect, is provided.
  • the present application provides a communication device.
  • the communication device may be a network device or a terminal device, wherein the communication device includes a transceiver, a processor, and a memory.
  • the processor is used to control the transceiver to send and receive signals
  • the memory is used to store computer programs
  • the processor is used to call and run the computer program stored in the memory, so that the terminal device executes the method in any possible implementation manner in the first aspect, and the network device executes the method in the first aspect.
  • the method in any possible implementation manner in the second aspect, or the network device performs the method in any possible implementation manner in the third aspect, or the network device performs the method in any possible implementation manner in the fourth aspect.
  • the terminal device executes the communication method in the first aspect and any possible implementation thereof to send the information and/or data that needs to be sent.
  • the network device serves as the receiving end of information and/or data
  • the network device performs the communication method in any possible implementation manner of the above-mentioned second to fourth aspects.
  • the present application provides a computer-readable storage medium that stores instructions that, when run on a computer, cause the computer to execute any one of the possible methods of the first to fourth aspects. Methods in the implementation.
  • the present application provides a computer program product.
  • the computer program product includes a computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute any one of the possible methods of the first to fourth aspects. Methods in the implementation.
  • this application provides a chip including a processor.
  • the processor is configured to read and execute the computer program stored in the memory to execute the method in any one of the possible implementations of the first to fourth aspects.
  • the chip further includes a memory, and the memory and the processor are connected to the memory through circuits or wires.
  • FIG. 1 is a schematic diagram of an MBS service transmission process provided by an embodiment of the present application.
  • Figure 2 is a schematic flowchart of a terminal device receiving broadcast data provided by an embodiment of the present application.
  • Figure 3 is a schematic flowchart of RRC establishment/recovery of a terminal device provided by an embodiment of the present application.
  • Figure 4 is a schematic diagram of a terminal switching scenario provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of another terminal switching scenario provided by an embodiment of the present application.
  • Figure 6 is a schematic diagram of a communication method provided by an embodiment of the present application.
  • Figure 7 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • Figure 8 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • Figure 9 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • Figure 10 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • Figure 11 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • Figure 12 is a schematic diagram of a communication architecture applicable to the embodiment of the present application.
  • Figure 13 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • Figure 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 15 is a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA broadband code division multiple access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • FDD Frequency Division Duplex
  • TDD Time Division Duplex
  • UMTS Universal Mobile Telecommunication System
  • WiMAX Worldwide Interoperability for Microwave Access
  • the terminal equipment in the embodiment of this application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or User device.
  • the terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or a device with wireless communications Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in future 5G networks or future evolved Public Land Mobile Communications Networks (Public Land Mobile Network, PLMN) Terminal equipment, etc., the embodiments of this application are not limited to this.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the terminal device may be a device for realizing the function of the terminal device, or a device that can support the terminal device to realize the function, such as a chip system, and the device may be installed in the terminal.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the network device in the embodiment of the present application may be a device used to communicate with a terminal device.
  • the network device may be a Global System of Mobile communication (GSM) system or a Code Division Multiple Access (CDMA) system. It can be a base station (Base Transceiver Station, BTS) in a wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system (NodeB, NB), or an evolutionary base station (Evolutional) in an LTE system.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • BTS Base Transceiver Station
  • WCDMA Wideband Code Division Multiple Access
  • NodeB NodeB
  • Evolutional evolutionary base station
  • NodeB, eNB or eNodeB or a wireless controller in a Cloud Radio Access Network (CRAN) scenario
  • the network device can be a relay station, access point, vehicle-mounted device, wearable device, and in the future
  • the embodiments of this application are not limited to network equipment in the 5G network or network equipment in the future evolved PLMN network.
  • the network device may be a device used to implement the function of the network device, or may be a device capable of supporting the network device to implement the function, such as a chip system, and the device may be installed in the network device.
  • the embodiments shown below do not specifically limit the specific structure of the execution body of the method provided by the embodiment of the present application, as long as the program that records the code of the method provided by the embodiment of the present application can be run according to the present application. It is sufficient to communicate using the method provided in the embodiment of the application.
  • the execution subject of the method provided in the embodiment of the application may be a terminal device or a network device, or a functional module in the terminal device or network device that can call a program and execute the program.
  • the embodiments shown in this application may be partially implemented, or may be partially implemented or fully implemented after the various embodiments are combined with each other, and this application is not limited to this.
  • Multicast and broadcast service (MBS)
  • Multicast broadcast service MBS is a service for multiple terminal devices (for example, live broadcast service, public safety service, batch software update service, etc.).
  • the MBS service comes from the data server.
  • the data server sends the MBS data to the core network device.
  • the core network device sends the MBS data to the access network device.
  • the access network device sends the MBS data to the access network device.
  • the MBS data is sent to at least one terminal device that receives the MBS service.
  • the MBS service is transmitted through a common transmission channel MBS session.
  • Each MBS session can contain at least one MBS QoS flow.
  • the MBS data packet is transmitted through the MBS wireless bearer. There are two transmission modes for an MBS wireless bearer:
  • the first one using point to multi-point (PTM) transmission method;
  • the second type using point to point (PTP) transmission method.
  • PTP point to point
  • Multicast service (multicast)
  • Multicast services are designed for services with high quality of service (QoS) requirements. They require group management for multicast services and can provide the same QoS level as unicast services.
  • the core network needs to manage the joining and exiting of terminal devices.
  • a new MBS QoS flow data flow is introduced based on PDU session.
  • the PTP transmission method and PTM transmission method are supported to send data to the terminal equipment, and dynamic switching between PTP and PTM controlled by the access network equipment is supported.
  • multicast services can only be provided to terminal devices in the RRC connected state, and access network equipment and core network equipment need to maintain information about terminal equipment corresponding to the multicast service group.
  • multicast services also support MBS session deactivation/activation triggered by the core network, and the terminal device does not perceive the status of the service.
  • the MBS session deactivation process only applies to multicast services.
  • the MBS session deactivation process is triggered by the multicast/broadcast session management function (MB-SMF).
  • M-SMF multicast/broadcast session management function
  • the multicast broadcast user receives
  • MB-UPF multicast/broadcast user plane function
  • AF application function
  • NEF network exposure function
  • the MBS Session deactivation process is used to deactivate the MBS data resources of the NG-RAN node.
  • the RAN releases the radio resources of the multicast session and stops transmitting multicast session data to the terminal device.
  • the network device can release the idle state or inactive state (idle/inactive) or not release the RRC to the terminal device. There is no explicit deactivation notification to the end device.
  • the MBS session activation process is only applicable to multicast services.
  • the MBS session activation process is triggered by MB-SMF when MB-SMF receives notification from MB-UPF about downlink MBS data, or when MB-SMF receives a request from AF directly or through NEF.
  • the MBS Session activation process is used to activate the MBS data resources of the NG-RAN node.
  • 5GC the wireless resources of the multicast session are established, and the multicast session data begins to be transmitted to the terminal device.
  • terminal devices in the RRC-IDLE state and RRC Inactive state that join the multicast session will be paged.
  • the broadcast technology of NR MBS introduces two logical channels, multicast control channel (MBS control channel, MCCH) and multicast traffic channel (MBS traffic channel, MTCH).
  • MCCH is used to transmit control information, including MTCH configuration information. .
  • MCCH is sent periodically.
  • the MTCH logical channel carries the user data of the broadcast service, and the MTCH is scheduled through the MCCH.
  • the configuration of MTCH is per G-RNTI level, which can also be said to be per MBS service level.
  • the access network device uses a group radio network temporary identifier (G-RNT) to schedule service data to multiple terminal devices at the same time.
  • G-RNTI can be associated with at least one broadcast service.
  • FIG. 2 is a schematic flowchart of a terminal device receiving broadcast data.
  • the process for the terminal device to receive the broadcast service is to first obtain the system.
  • the system message contains the control information for transmitting the broadcast service (that is, the configuration information of the MCCH).
  • the terminal knows how to transmit the broadcast service through the system message. to receive MCCH messages.
  • the terminal device reads the MCCH message content according to the MCCH configuration information.
  • the MCCH message includes the MBS broadcast configuration message.
  • the MBS broadcast configuration information is the MTCH configuration information, G-RNTI, temporary multicast group identifier (temporary multicast group identifier). , TMGI), etc. to accept the necessary configurations for broadcast services.
  • the terminal device receives broadcast service data on the MTCH according to the configuration information.
  • the radio resource control (RRC) state of the terminal device includes RRC-connected state, RRC-idle state and RRC-inactive state.
  • the RRC non-connected state in the following embodiments may include at least one of the RRC idle state or the RRC inactive state. Among them, the RRC non-connected state can be referred to as the non-connected state.
  • the RRC connection state can be referred to as the connection state.
  • the RRC idle state can be referred to as the idle state.
  • the RRC inactive state can be referred to as the inactive state. In the embodiments of this application, at least one may be one or more. The variety can be 2, 3 or more, without limitation.
  • network equipment or access network equipment is used as a base station as an example.
  • the terminal device can perform an RRC establishment process with the base station.
  • S310 The terminal device sends RRC establishment/recovery request information to the network device.
  • step S310 is for the terminal device to initiate request information to enter the connected state (for example, the first request information sent by the terminal device to the second cell in the embodiment of the present application).
  • S320 The network device sends RRC establishment/recovery response information to the terminal device.
  • the network device receives RRC establishment request information from the terminal device, and the network device sends RRC establishment response information to the terminal device according to the RRC establishment request information.
  • the network device receives RRC recovery request information from the terminal device, and the network device sends RRC recovery response information to the terminal device according to the RRC recovery request information; or, the network device receives the RRC recovery request information from the terminal device, and the network device recovers according to the RRC recovery request information.
  • the request information sends RRC establishment response information to the terminal device, so that the terminal device re-establishes the RRC connection.
  • the terminal device sends RRC establishment/recovery completion information to the network device.
  • the terminal device receives the RRC establishment response information from the network device, and performs RRC establishment based on the RRC establishment response information. After the terminal device determines that the RRC establishment is completed, it sends the RRC establishment completion information to the network device.
  • the terminal device receives the RRC recovery response information from the network device and performs RRC establishment based on the RRC recovery response information. After the terminal device determines that the RRC recovery is completed, it sends the RRC recovery completion information to the network device.
  • the RRC state of the terminal device is the RRC connected state. Subsequently, the RRC state of the terminal device can be transitioned among the following states: RRC idle state, RRC connected state and RRC inactive state.
  • Standard R18 has decided to study that multicast services can be provided to RRC non-connection terminal devices to support terminal devices in network congestion scenarios to receive multicast services as much as possible. Because multicast services can provide services to multiple terminal devices through PTM in the connected state, the network only sends one copy of data, and multiple terminal devices receive the data together. That is, the multicast service is provided to all non-connected terminal devices, and only one copy of data is sent without occupying too many additional resources.
  • Method 1 The terminal device obtains the configuration information of the multicast service in the connected state and uses it to continue receiving multicast services in the non-connected state after RRC release;
  • Method 2 Similar to the broadcast technology method, the network device provides the configuration information of the non-connection multicast service in the MCCH. This configuration information is used by the terminal device to receive data.
  • the MCCH can be shared with the existing MCCH for broadcast, or it can be an MCCH designed for multicast (for example, MC-MCCH), which is not limited in this application.
  • the MCCH is used to contain multicast configuration information, and its name is not limited in this application. All MCCHs mentioned in the embodiments of this application refer to logical channels used to include multicast configuration.
  • Both of the above methods can enable terminal devices in a non-connected state to receive multicast services.
  • the service received by the terminal device in the non-connected state cannot directly change the configuration information of its service.
  • method two is more flexible than the technical solution in method one.
  • Method two can support the terminal device to obtain configuration information at any time.
  • the network device can be considered to be in the non-connected state.
  • the corresponding services in the non-connected mode are provided in the connected mode, otherwise the opposite is true.
  • the activation/deactivation status of the multicast service is only notified to the access network equipment by the core network equipment and not to the terminal equipment.
  • the network can decide to release the RRC connection of the terminal device to the RRC idle state or RRC inactive state.
  • the terminal device in the non-connected mode only needs to perform the specified operations that the non-connected terminal device needs to perform, such as measuring, receiving paging, system messages and other operations, and does not need to receive additional service data.
  • R18 it is discussed in the context of receiving multicast services when the network is in the non-connected state.
  • the terminal device If the terminal device is released to the non-connected state to receive multicast services, the terminal device must always use G-RNTI to listen to the PDCCH to read the multicast service. data.
  • the network device In the scenario of multicast service deactivation, if the core network device triggers the multicast service deactivation process to the access network device, the network device will stop sending data for a long period of time, but if the terminal device has been monitoring the PDCCH at this time, Will cause a lot of unnecessary energy consumption. Therefore, when the network is in non-connected mode and provides multicast services, if the multicast service is deactivated, the terminal device needs to be notified of the status of the corresponding service. For specific reference methods, the following solutions can be considered:
  • Solution 1 Corresponding to the above methods 1 and 2, the network device pages the terminal device into the connected state and then releases it. When releasing, the non-connected state multicast is not indicated.
  • the terminal device does not sense the multicast service status.
  • the terminal device deactivates the multicast service according to the network instructions whether to accept the multicast service in the non-connected state, thus achieving the purpose of power saving.
  • the terminal device is released immediately after entering the connected state, which will cause a waste of access resources. It only realizes that the terminal device does not continue to receive non-connected state multicast services.
  • the terminal device still needs to page into the connected state and obtain the configuration information of the multicast service again. This is very important for introducing terminals in the non-connected state.
  • Equipment the original intention of receiving multicast is to alleviate network congestion, which is contrary to the fact that this solution requires frequent access of terminal equipment.
  • Solution 2 For the above methods 1 and 2, the network device indicates that the multicast service status is active/deactivated in RRC release/connection state/paging message paging.
  • the network device when the terminal device is in the connected state, the network device indicates the multicast service status, which is used to determine whether to receive data when the network is in the RRC non-connected state. If the network indicates that the multicast service status is deactivated, the terminal device does not need to monitor data. When the subsequent multicast service status is activated, the terminal device can determine whether it is a multicast service activation scenario (or whether it needs to enter the connected state) based on the paging message sent by the network. If the corresponding multicast service is activated or does not need to enter the connected state, the terminal device needs to start receiving data. The operation of the terminal device to receive data also needs to be divided into different modes.
  • the first category is that all cells in the RNA can provide the corresponding received services to the terminal device and can provide the same configuration
  • the second category is that all cells in the RNA do not limit whether they need to provide the same services and the same configuration.
  • the network device indicates in the MCCH that the corresponding status of the multicast service is activated or deactivated.
  • the terminal device can obtain the status of the multicast service at any time.
  • the terminal device reads that the status of the multicast service is deactivated, the terminal device does not monitor data.
  • the terminal device monitors data.
  • This solution is not restricted by whether RNA provides the same services or configuration.
  • the terminal equipment determines the information of the current cell and has nothing to do with the information of other cells.
  • the indication mode is display indication, for example: MCCH message content: TMGI 1, TMGI 2-deactivation, TMGI 3. It can be seen that the status of service TMGI 2 is directly indicated in the MCCH information as deactivated. activation.
  • the indication method is implicit indication, for example: MCCH message content: TMGI 1, TMGI 2 (indicated to be received when released, but not reflected in MCCH due to deactivation), TMGI 3, you can See that TMGI 2 is not reflected in the MCCH message, that is, the status of the service is deactivated; MCCH message content: TMGI 1 (contains all configurations), TMGI 2 (due to deactivation, only contains part of the configuration), TMGI 3 (contains all configurations) ), it can be seen that TMGI 2 only contains part of the configuration in MCCH, so the status of the service is deactivated.
  • the terminal device Based on the implementation of the first method of providing the configuration of the non-connection mode multicast service to the terminal device, as shown in the schematic diagram of the terminal device switching scenario in Figure 4, the terminal device receives the non-connection mode multicast service 1 in the first cell , the terminal device moves from the first cell to the second cell.
  • the first cell is the source serving cell of the terminal device
  • the second cell is the target serving cell of the terminal device.
  • Scenario 1 If the second cell is a cell outside the RNA of the first cell, or the second cell and the first cell belong to the same RNA, but there is no guarantee that the same RNA can provide the same services to different cells, and it is not certain whether the second cell Whether it can provide services to terminal equipment. Since the terminal device is not sure whether the target serving cell provides the corresponding service, the terminal device switches or reselects to the second smallest cell. After entering the zone, the terminal device enters the connected state and receives the corresponding multicast service or the configuration information of the corresponding service.
  • Scenario 2 If the second cell and the first cell belong to the same RNA, and the RAN provides the same services to the first cell and the second cell, but it is not sure whether the configurations provided by the RAN to the first cell and the second cell are the same. Since the terminal device has no configuration information, after switching or reselecting to the second cell, the terminal device needs to enter the connected state to obtain the configuration information corresponding to the first multicast service (for example, TMGI1) of the second cell.
  • the first multicast service for example, TMGI1
  • Scenario 3 If the second cell and the first cell belong to the same RNA, and the RAN provides the same services and the same configuration for the first cell and the second cell. After the terminal device switches or is reselected from the first cell to the second cell, it does not need to enter the connected state and can continue to receive services in the non-connected state.
  • the terminal device obtains the TMGI 1 it wants to receive through MCCH in the first cell.
  • the configuration information is then moved from the first cell to the second cell.
  • Scenario 4 There is no TMGI 1 in the MCCH of the second cell, or the second cell does not have MCCH.
  • the terminal device can be regarded as that the second cell does not provide the service TMGI in the non-connected state, so the terminal device needs to enter the connected state to obtain service data.
  • Scenario 5 There is TMGI 1 in the MCCH of the second cell. After the terminal device switches or reselects from the first cell to the second cell, it does not need to enter the connected state and can remain in the non-connected state.
  • This application is based on the above technical problems discovered in Scenario 1, Scenario 2 and Scenario 4.
  • the embodiments of this application provide a communication method to solve the problem of how to avoid terminal equipment receiving multicast services in non-connected mode from serving the source Unnecessary access during cell handover or reselection to the target serving cell.
  • the terminal device receives first information, where the first information is related to the status of the first multicast service, and/or the first information is related to the configuration information of the first multicast service in the second cell.
  • the state of the first multicast service includes an activated state or a deactivated state.
  • the first cell and the second cell are adjacent cells, or the second cell is an RNA or tracking area (TA). ), or the second cell is a cell within a specific area.
  • the first information may be an information list of cells, or the first information may be a cell list of information, which includes relevant information of the second cell.
  • configuration information of the first multicast service in this application may be multicast service configuration information, radio bearer configuration information or PTM configuration information, which is not limited in this application.
  • the first information may also come from the first cell and/or the network device serving the first cell (referred to as the first network device in this application).
  • the first network device is a network device that provides services for the first cell.
  • the first information is carried in at least one of the following messages: paging message, system information block SIB, and MCCH information.
  • the first information may also be carried in an RRC release message or an RRC reconfiguration message, which is not limited in this application.
  • the RRC release message is used to release the terminal device to a non-connected state.
  • the terminal device determines whether to send first request information to the second cell based on the first information.
  • the first request information is used to establish or restore the RRC connection.
  • the terminal device determines whether to send the first request to the second cell based on the first information. Asking for information.
  • the terminal device when the status of the first multicast service in the first information is an active state, the terminal device sends the first request information to the second cell, and the first request information is used by the terminal device to request to establish or restore the RRC connection.
  • the terminal device when the status of the first multicast service in the first information is a deactivated state, the terminal device remains in a non-connected state.
  • the terminal device when the configuration information of the first multicast service in the first cell and the second cell in the first information is different, the terminal device sends the first request information to the second cell.
  • the terminal device when the configuration information of the first multicast service in the first cell and the second cell in the first information is the same, the terminal device remains in a non-connected state.
  • the terminal device when the configuration information of the first multicast service in the first cell and the second cell in the first information is the same, and the status of the first multicast service is active, the terminal device sends the first request to the second cell. information.
  • the terminal device remains in the non-connected state.
  • the terminal device may also receive the first paging message, and the first paging message includes the first multicast message.
  • the terminal device determines that the first multicast service is activated or needs to enter the connected state. For example, the terminal device sends first request information to the second cell according to the first paging message for entering the connected state.
  • the method may also include:
  • the terminal device receives second information, and the second information is used to determine that the second cell does not provide the first multicast service to the terminal device in a non-connected state.
  • the second cell may also directly instruct the terminal device that the second cell does not provide the first multicast service to the terminal device in the non-connected state, and the terminal device further determines whether to enter the connected state based on the second information.
  • the terminal device may receive the second information before the terminal device receives the first information, or the terminal device may receive the second information after the terminal device receives the first information, which is not limited in this application.
  • the terminal device obtains the third information according to the MCCH configuration information.
  • the third information includes the MCCH information of the second cell, and the MCCH information does not include the first The identifier of the multicast service.
  • the terminal device determines that the second cell does not provide the first multicast service to the terminal device in the non-connected state.
  • the terminal device when the second information includes the MCCH configuration information of the second cell, and the terminal device does not obtain the third information according to the MCCH configuration information, it indicates that the MCCH information in the second cell is empty or does not exist. MCCH information.
  • the terminal equipment determines that the second cell supports zero non-connected state multicast services.
  • MCCH/MCCH configuration information in this application is used for multicast transmission.
  • first information may also include PDCP synchronization information of the first cell and/or PDCP synchronization information of the second cell.
  • the synchronization information includes the PDCP of the first cell and/or the PDCP of the second cell or not. Synchronize.
  • PDCP synchronization in this application means that the network device (such as a base station) corresponding to the first cell or the second cell generates a PDCP number using the number in the data packet sent by the core network.
  • Out-of-synchronization means that the network equipment (such as a base station) corresponding to the first cell or the second cell does not use the number of the data packet sent by the core network to generate a PDCP number.
  • the number in the data packet sent by the core network can be MBS QFI SN.
  • the terminal equipment rebuilds the PDCP entity or resets/initializes the PDCP variable, and/or the terminal equipment
  • the data packet is discarded or submitted to the upper layer, and/or the terminal device sends the first request information to the first cell and/or the second cell for establishing or restoring the RRC connection.
  • the terminal device After the terminal device enters the connected state, the terminal device /Or the second cell receives the configuration of PDCP.
  • the second cell may not adopt the PDCP synchronization mechanism.
  • the terminal device switches or reselects to the second cell, it is necessary to further determine the PDCP layer processing.
  • the first information is also used to indicate the PDCP synchronization information of the second cell, and is further used by the terminal device to determine the processing of the PDCP layer or PDCP entity.
  • the terminal equipment in the RRC non-connected state switches or reselects from the first cell to the second cell
  • the terminal equipment receives the first information and determines whether it needs to transfer to the third cell based on the first information.
  • the second cell sends the first request information to request to enter the connected state.
  • the first information is related to the status of the first multicast service and/or the configuration of the second cell
  • the terminal device further Determine whether to continue to maintain the non-connected state or send the first request information to the second cell. This avoids the terminal equipment switching or retransmitting from the first cell to the second cell, and the terminal equipment directly sends the first request information to the second cell to request the establishment or restoration of the RRC connection state.
  • the terminal device needs to determine whether to send the first request information to the second cell based on the received first information and the first condition. This avoids the terminal device from initiating a request to the second cell and entering the connected state. The problem is quickly released to a non-connected state, reducing resource consumption.
  • FIG. 7 shows a schematic diagram of another communication method provided by an embodiment of the present application. The method includes the following steps:
  • the terminal device receives the first information from the first cell.
  • the first cell sends the first information to the terminal device.
  • the terminal device when the terminal device in the non-connected state switches or reselects from the first cell to the second cell, the terminal device receives the first information from the first cell, and the first information is used to indicate the first multicast service. state.
  • the first multicast service is a multicast service received in a non-connected state when the terminal device is in the first cell, and the state of the first multicast service includes an active state or an inactive state.
  • the first cell is the source serving cell of the terminal device
  • the second cell is the target serving cell for handover or reselection of the terminal device.
  • the terminal device obtains the first information through paging message, system information block SIB, and MCCH message.
  • the terminal device obtains the first information by releasing the information through RRC or entering the connected state.
  • the terminal device determines whether to send the first request information to the second cell based on the first information.
  • the specific judgment basis is based on whether the state of the first multicast service is an activated state or a deactivated state. Details are as follows:
  • Scenario 1 The status of the first multicast service in the first information is active.
  • the method also includes:
  • S720 The terminal device sends the first request information to the second cell according to the first information.
  • the second cell receives the first request information from the terminal device.
  • the state of the first multicast service is an active state
  • the terminal device sends the first request information to the second cell.
  • the terminal device receives the first multicast service from the first cell, and the state of the first multicast service may be an active state or an inactive state. Wherein, when the state of the first multicast service is an active state, the terminal device switches or is reselected from the first cell to the second cell, and the terminal device sends the first request information to the second cell.
  • the terminal device initiates the RRC recovery/establishment process to enter the connected state.
  • the second cell only provides the first multicast service in the connected state, or the second cell has not yet provided the first multicast service and needs to trigger the establishment of the service after entering the connected state.
  • the terminal device when the terminal device is not sure whether the second cell provides the corresponding multicast service and/or the same configuration, the terminal device directly determines whether to provide the second cell with the corresponding multicast service based on the status of the first multicast service.
  • the first request information is sent to establish/restore the RRC connection.
  • Scenario 2 The status of the first multicast service in the first information is deactivated.
  • the method also includes:
  • the terminal device determines to maintain the non-connected state according to the first information.
  • the terminal device receives the first information from the first cell, and the first information indicates that the status of the first multicast service is an active state or an inactive state. Wherein, when the status of the first multicast service is in the deactivated state, the terminal device switches or is reselected from the first cell to the second cell, and the terminal device continues to remain in the non-connected state.
  • the terminal device does not initiate the RRC recovery/establishment process to avoid being released after entering the connected state.
  • the terminal device remains in a non-connected state and waits for the subsequent activation process to initiate a paging request, as shown in Figure 7.
  • the method also includes:
  • the terminal device receives the first paging message.
  • the terminal device determines whether to enter the connected state according to the first paging message.
  • the terminal device determines whether to enter the connected state according to the first paging message.
  • the terminal device does not send the first request information to the second cell;
  • the terminal device determines The first multicast service is activated or needs to enter the connected state. For example, the terminal device sends first request information to the second cell according to the first paging message for entering the connected state.
  • the terminal device when subsequent paging reaches the terminal device, the terminal device is not sure whether the second cell and the first cell have the same For the configuration information of the first multicast service, the terminal device needs to initiate an RRC recovery/establishment process to enter the connected state, and obtain the configuration information of the first multicast service of the second cell.
  • the terminal device determines that the configuration information of the first multicast service of the second cell is the same as the configuration information of the first multicast service of the first cell, the terminal device performs the method shown in Figure 8. For details, please refer to Figure 8 Detailed introduction will not be repeated here.
  • the received services may include multiple services.
  • the multiple services include active services
  • the terminal device needs to send the first request information to the second cell.
  • the method also includes:
  • the terminal device sends the first request information to the second cell.
  • the second cell receives the first request information from the terminal device.
  • the first request information is used to establish or restore an RRC connection.
  • the terminal equipment in the non-connected state switches or reselects from the first cell to the second cell, it is not necessary to determine whether the second cell belongs to the same RAN as the second cell, and/or the second cell. Whether the service supported by the cell is the same as that of the first cell, and/or whether the configuration information of the corresponding services of the second cell is the same as that of the first cell, to determine whether it needs to enter the connected state, the terminal device directly based on the first group in the first information Determine whether to send the first request information to the second cell based on the status of the broadcast service.
  • the terminal device when the status of the first multicast service is the active state, the terminal device sends the first request information to the second cell; when the status of the first multicast service is the inactive state, the terminal device remains in the non-connected state and waits. Wake up by paging, and then send the first request information to the second cell.
  • the method shown in Figure 7 avoids the terminal equipment from determining whether the first cell and the second cell belong to the same RAN, and/or whether the services supported are the same, and/or the configuration information of the corresponding services are the same. After the cell enters the connected state, it will be quickly released to the non-connected state, which reduces resource consumption.
  • Figure 8 is a schematic diagram of another communication method provided by the embodiment of the present application. As shown in Figure 8, the method may include the following steps:
  • the terminal device receives the first information.
  • This first information comes from the first cell.
  • the first information includes the status of the first multicast service.
  • This step S810 is similar to the above-mentioned step S710 shown in FIG. 7. For details, please refer to the description in the above-mentioned S710 and will not be described again here.
  • the terminal device may also receive second information from the second cell, where the second information is used to indicate that the second cell does not provide the first multicast service to the terminal device in a non-connected state.
  • the second information can be directly used to indicate that the second cell does not provide the first multicast service to the terminal equipment in the non-connected state, or the second information can indirectly indicate that the second cell does not provide the non-connected state.
  • the first multicast service that is, the second cell supports the non-connection state multicast service, but the supported non-connection state multicast service does not include the first multicast service.
  • the second message does not include relevant information that does not include MCCH in the second information (for example: MCCH configuration information), that is, the second information indicates that the second cell does not send data to terminal equipment in a non-connected state.
  • the second information includes MCCH configuration information of the second cell, the first cell obtains third information based on the MCCH configuration information, the third information includes the MCCH information of the second cell, and the second cell
  • the MCCH information does not include the identification of the first multicast service, that is, the second cell does not provide the first multicast service in a non-connected state
  • the second information includes the MCCH configuration information of the second cell, and the first cell configures it according to the MCCH If the third information cannot be obtained, it is considered that the second cell does not provide the first multicast service to the non-connected terminal equipment.
  • the second cell may directly indicate that the second cell does not provide the first multicast service to the non-connected terminal device based on the above-mentioned second information.
  • the second information may indirectly indicate that the second cell does not provide the non-connection state.
  • S820 The terminal device receives the second information from the second cell.
  • the second cell sends the second information to the terminal device.
  • the second information is used to indicate that the second cell does not provide the first multicast service to terminal equipment in a non-connected state.
  • the second information may be directly used to indicate that the second cell does not provide the first multicast service to terminal equipment in a non-connected state, or the second information may indicate that the second cell does not provide a non-connected state terminal device.
  • the first multicast service may be directly used to indicate that the second cell does not provide the first multicast service to terminal equipment in a non-connected state, or the second information may indicate that the second cell does not provide a non-connected state terminal device.
  • the terminal device determines, based on the second information, that the second cell does not provide the first multicast service to the non-connected terminal device.
  • the terminal device determines based on the second information that the second cell does not provide The first multicast service in non-connected state. As shown in Figure 8, the method also includes:
  • S840 The terminal device determines whether to send the first request information to the second cell based on the first information.
  • the terminal device determines whether to send the first request information to the second cell based on the first information.
  • the first request information is To establish or restore RRC connection.
  • step S840 the terminal device determines whether to send the first request information to the second cell based on the first information.
  • the terminal device determines whether to send the first request information to the second cell based on the first information.
  • the terminal device receives the second information from the second cell.
  • the second cell sends the second information to the terminal device.
  • the second information is used to indicate that the second cell does not provide the first multicast service to terminal equipment in a non-connected state.
  • the second information includes MCCH configuration information of the second cell.
  • the terminal device sends the second request information to the second cell.
  • the terminal device when the terminal device receives the second information of the second cell, and the second information includes the MCCH configuration information of the second cell, the terminal device sends second request information to the second cell, and the second request information is used. Obtaining the MCCH information of the second cell according to the MCCH configuration information.
  • the method when the second cell includes MCCH information, that is, the method shown in Figure 8, the method also includes:
  • the terminal device receives the third information from the second cell, or the second cell sends the third information to the terminal device.
  • the second cell when the second cell receives the second request information from the terminal device, the second cell sends the third information to the terminal device according to the second request information.
  • the third information includes MCCH information of the second cell.
  • the terminal device determines that the second cell does not provide the first multicast service to the non-connected terminal device.
  • the terminal device determines, based on the third information, that the second cell does not provide the first multicast service to the non-connected terminal device.
  • the terminal equipment sends the second request information to the second cell, and the terminal equipment may not receive the third information, that is, the MCCH information of the second cell is empty or has no MCCH information, that is, step S840' and step 850' are optionally.
  • the terminal device determines whether to send the first request information to the second cell based on the first information.
  • the terminal device determines whether to send the first request information to the second cell based on the first information, and the first request information is used to Establish or restore an RRC connection.
  • step S860' the terminal device determines whether to send the first request information to the second cell based on the first information.
  • the terminal device determines whether to send the first request information to the second cell based on the first information.
  • steps S820 and S820' shown in Figure 8 are not limited to following step S810. Steps S820 and S820' may also precede S810, and this application does not limit this.
  • the terminal device when the terminal device in the non-connected state switches or retransmits from the first cell to the second cell, the terminal device receives the second information from the second cell, and the second information is used to determine the second cell.
  • the second cell does not provide the first multicast service to the terminal equipment in the non-connected state.
  • the terminal device determines whether to send the first request information to the second cell according to the status of the first multicast service.
  • the terminal device obtains the MCCH service information of the second cell based on the MCCH configuration information.
  • the terminal device further determines whether the second cell supports the connectionless first multicast service according to the service information.
  • the terminal device determines that the second cell does not provide the first multicast service to the terminal device in the non-connected state, or the second cell does not provide multicast in the non-connected state, the terminal device determines that the first multicast service is not provided by the terminal device according to the status of the first multicast service.
  • the second cell sends the first request information for establishing or restoring the RRC connection, or the terminal equipment waits for paging to wake up.
  • Figure 9 shows a schematic flow chart of another communication method provided by the embodiment of the present application, which is applicable to any one of the above scenarios one to five.
  • the terminal device determines whether to send the first request information to the second cell based on the first information.
  • the method includes:
  • the first network device receives the configuration information of the first multicast service in the second cell.
  • the second cell sends the configuration information of the first multicast service in the second cell to the first network device.
  • the information exchange between the first network device and the second cell so far can be carried out through the Xn interface.
  • the first network device determines, based on the configuration information of the first multicast service in the second cell, whether the configuration information of the first cell is the same as or different from the configuration of the second cell.
  • the first network device determines the first information according to the configuration information of the first multicast service in the second cell,
  • the first information is sent to the terminal device for the terminal device to determine whether to send the first request information to the second cell.
  • the first network device is a network device serving the first cell, the first cell and the second cell are adjacent cells, or the second cell is a cell within a certain range of the first cell, or the first cell and the second cell are adjacent cells.
  • Cells are cells within the same RNA.
  • the configuration information of the first multicast service in the second cell may include the PTM configuration of the second cell, and the PTM configuration may include G-RNTI, logical channel ID (LCID), discontinuous reception (discontinuous reception) reception, DRX), downlink shared channel (physical downlink shared channel, PDSCH) configuration and other information.
  • PTM configuration may include G-RNTI, logical channel ID (LCID), discontinuous reception (discontinuous reception) reception, DRX), downlink shared channel (physical downlink shared channel, PDSCH) configuration and other information.
  • the configuration information of the first multicast service in the second cell includes one or more of the following: first multicast service identification information (for example, TMGI1), configuration information of the first multicast service in the second cell ( This configuration information can be carried in radio bearer configuration information, PTM configuration information, multicast service configuration information, etc.), PDCP synchronization or PDCP desynchronization.
  • first multicast service identification information for example, TMGI1
  • configuration information of the first multicast service in the second cell This configuration information can be carried in radio bearer configuration information, PTM configuration information, multicast service configuration information, etc.
  • PDCP synchronization for example, PDCP desynchronization.
  • the configuration information of the first multicast service in the second cell may also include the PDCP SN generated by the second cell using a synchronization mechanism, or the second cell may not use a synchronization mechanism.
  • the terminal device may cause processing abnormalities (for example, packet loss, data packet confusion, etc.) according to the existing PDCP mechanism.
  • the first information may also be Whether PDCP is synchronized is notified to the terminal device, which is used by the terminal device to determine the processing of the PDCP layer/PDCP entity.
  • the first network device may send third request information to the second cell through the Xn interface.
  • the third request information is used to request to obtain the configuration of the second cell.
  • the third request information may include the following: One or more items: the first multicast service identifier, the second cell identifier, the configuration query instruction information of the first multicast service in the second cell, the PDCP synchronization query instruction letter, etc.
  • the second cell sends the configuration information of the first multicast service in the second cell to the first network device according to the third request information.
  • the configuration information of the first multicast service in the second cell includes one or more of the following: first multicast service identification information (for example, TMGI1), second cell configuration information, PTM configuration information, PDCP synchronization or PDCP Out of sync.
  • first multicast service identification information for example, TMGI1
  • second cell configuration information for example, PTM configuration information
  • PTM configuration information for example, PTM configuration information
  • the PDCP synchronization or non-synchronization may be at a service level, a cell level, or a base station level, which is not limited in this application.
  • step S910 is an optional step.
  • S920 The terminal device receives the first information from the first network device.
  • the first network device sends the first information to the terminal device.
  • the terminal device when the terminal device in the non-connected state switches or reselects from the first cell to the second cell, the terminal device receives the first information from the first network device, and the first information is related to the first group in the second cell. related to the configuration information of the broadcast service.
  • the terminal device determines whether to send the first request information to the second cell based on the first information.
  • the terminal device when the configuration information of the first multicast service in the first cell and the second cell in the first information is different, the terminal device sends the first request information to the second cell;
  • the terminal device when the configuration information of the first multicast service in the first cell and the second cell in the first information is the same, the terminal device remains in a non-connected state. Details are as follows:
  • Scenario 1 The configuration information of the first multicast service in the first cell and the second cell in the first information is different.
  • the method also includes:
  • S930 The terminal device sends the first request information to the second cell according to the first information.
  • the second cell receives the first request information from the terminal device.
  • the configuration information of the first multicast service in the first cell and the second cell in the first information is different, and the terminal device sends the first request information to the second cell.
  • Scenario 2 The configuration information of the first multicast service in the first cell and the second cell is the same
  • the method also includes:
  • the terminal device determines to maintain the non-connected state according to the first information.
  • the terminal device receives the first information from the first cell, in which the configuration information of the first multicast service in the first cell and the second cell is the same.
  • the terminal equipment switches or is reselected from the first cell to the second cell, and the terminal equipment continues to remain in a non-connected state.
  • the terminal device sends the first request information to the second cell.
  • the terminal device receives the first paging message.
  • the terminal device determines whether to enter the connected state according to the first paging message.
  • the terminal device does not send the first request information to the second cell;
  • the terminal device determines The first multicast service is activated or needs to enter the connected state.
  • the method also includes:
  • the terminal device sends the first request information to the second cell.
  • the second cell receives the first request information from the terminal device.
  • the first request information is used to establish or restore an RRC connection.
  • the terminal device in the RRC non-connected state when the terminal device in the RRC non-connected state switches or reselects from the first cell to the second cell, it receives the first information determined from the first network device.
  • the first information is related to the configuration information of the first multicast service in the second cell.
  • the terminal device further determines whether to send the first request information to the second cell based on the first information.
  • the method shown in Figure 9 avoids the terminal device from determining whether the first cell and the second cell belong to the same RAN, and/or whether the services supported are the same, and/or the configuration information of the corresponding services are the same. After the cell enters the connected state, it will be quickly released to the non-connected state, which reduces resource consumption.
  • the first information is related to the configuration information of the first multicast service in the second cell
  • the terminal device determines the configuration information of the first multicast service in the first cell and the second cell based on the first information. If the configuration information is the same or different, it is further determined to send the first request information to the second cell, or to maintain the non-connected state.
  • the terminal device when the terminal device receives the first information from the first network device as neighbor cell information, the terminal device further determines whether to send the first request information to the second cell based on the neighbor cell information, as shown in the method in Figure 10, The method includes:
  • the first network device receives configuration information of services in the second cell.
  • the second cell sends the configuration information of the service in the second cell to the first network device.
  • the information interaction between the first network device and the second cell can be carried out through the Xn interface.
  • the configuration information of the service includes the configuration information of all services in the second cell, or the configuration information of the service includes the configuration information of the first multicast service.
  • the first network device sends neighbor cell information to the terminal device.
  • the terminal device receives neighbor cell information from the first network device.
  • the neighbor cell information may also be carried in an RRC release message, which is used to release the terminal device to the non-connected state.
  • the first network device sends an RRC release message to the terminal device, and the RRC release message releases the terminal device to the non-connected state.
  • the neighbor cell information may be carried in an RRC release message sent by the first network device to the terminal device.
  • the first network device determines the neighboring cell information according to the configuration information of the service in the second cell.
  • the neighboring cell information includes configuration information of all services of the second cell.
  • S1030 The terminal device determines to remain in a non-connected state according to the neighbor cell information.
  • the terminal device when the terminal device receives neighbor cell information from the first network device, the neighbor cell information includes the configuration information of all services in the second cell, or the neighbor cell information includes configuration information about the first multicast service in the second cell.
  • the terminal device When configuring information, the terminal device remains unconnected.
  • the terminal device when the neighbor cell information does not include relevant information of the second cell, and the terminal device switches or reselects from the first cell to the second cell, the terminal device needs to send the first request information to the second cell to enter the connection state. .
  • the terminal device receives the first paging message.
  • the terminal device receives the first paging message.
  • the terminal device determines whether to enter the connected state according to the first paging message.
  • the terminal device determines that the first multicast service is activated or needs to enter the connected state. For example, the terminal device sends first request information to the second cell according to the first paging message for entering the connected state.
  • the method also includes:
  • S1050 The terminal device sends the first request information to the second cell.
  • the second cell receives the first request information from the terminal device.
  • the first request information is used to establish or restore an RRC connection.
  • the terminal device when the terminal device receives the neighbor cell information from the first network device, where the neighbor cell information includes the configuration information of all services in the second cell, the terminal device determines to remain non-connected based on the neighbor cell information. state.
  • the first information sent by the first network device shown in Figure 10 to the terminal device is neighbor cell information.
  • the neighbor cell information is not limited to neighbor cells within the cell range.
  • the neighbor cell information in this application The relevant information of all cells that the first network device can obtain may be called neighbor cell information. Therefore, the neighbor cell information only represents the name of the information, but is not limited to the relevant information of the neighbor cells of the first cell. As long as the first network device can obtain the relevant information of the cell, it can be called neighbor cell information. This application is not limited.
  • the terminal device after the terminal device receives the configuration information of all services from the second cell or the configuration information of the first multicast service, the terminal device remains in a non-connected state. After the terminal device receives the first paging message including the first multicast service identifier, the terminal device sends first request information to the second cell. The first request information is used to establish or restore the RRC connection.
  • FIG. 11 is a schematic diagram of another communication method provided by an embodiment of the present application.
  • the method includes:
  • the first network device sends the third request information to the second cell.
  • the second cell receives the third request information from the first network device.
  • the third request information is used to obtain PDCP synchronization information of the second cell.
  • the third request information includes one or more of the following: a first multicast service identifier, a second cell identifier, PTM configuration query instruction information, PDCP synchronization query instruction information, etc.
  • the first network device receives PDCP synchronization information from the second cell.
  • the second cell sends the PDCP synchronization information of the second cell to the first network device.
  • the second cell sends the PDCP synchronization information of the second cell to the first network device.
  • the PDCP synchronization information includes PDCP synchronization or PDCP desynchronization of the second cell.
  • the PDCP synchronization or non-synchronization may be at a service level, a cell level, or a base station level, which is not limited in this application.
  • information interaction between the first network device and the second cell can be implemented through the Xn interface.
  • the first network device determines the first information according to the configuration information of the first multicast service in the second cell.
  • the first network device determines the first information according to the configuration information of the first multicast service in the second cell.
  • the first information may be called a neighbor cell information list or other information, which is not limited in this application.
  • the first information includes one or more of the following: configuration information of the first multicast service in the second cell, service information of the second cell, and PDCP synchronization or desynchronization of the second cell.
  • the first information may also include relevant information and public information of each business, and the specific embodiment is not limited in this application.
  • the first network device sends the first information to the terminal device.
  • the terminal device receives the first information from the first network device.
  • the first network device may send the first information to the terminal device in an RRC release message, or send the first information to the terminal device in an MCCH message, or, The first information is sent to the terminal device in a SIB message.
  • RRC release message or send the first information to the terminal device in an MCCH message
  • SIB message or, The first information is sent to the terminal device in a SIB message.
  • the terminal device determines the processing operation of the PDCP layer based on the first information.
  • the terminal device determines whether to initialize PDCP according to whether the PDCP of the second cell in the first information is synchronized.
  • the terminal device may reset the PDCP entity or PDCP variable, and/or clear or submit the data packets in the high-layer cache, and/or the terminal device may send the first request to the second cell.
  • Information, the first request information is used to establish or restore the RRC connection state. After the terminal device enters the connection state, it receives the PDCP configuration in the second cell.
  • the terminal device can reset the PDCP entity or PDCP variable, and/or clear or submit the data packets in the high-level buffer, and/or the terminal device sends a request to the first cell.
  • the cell and/or the second cell send first request information, which is used to establish or restore the RRC connection state. After the terminal device enters the connection state, it receives the PDCP configuration in the first cell and/or the second cell.
  • the method shown in Figure 11 above provides a method for the terminal device to process the PDCP layer/PDCP entity.
  • the terminal device can further determine the processing operation of the PDCP layer based on the PDCP synchronization information of the second cell in the first information. .
  • Figure 12 shows a communication architecture applicable to the embodiment of the present application.
  • Figure 12 shows the separation architecture of CP-UP in network equipment.
  • This method takes the network device as a base station (such as gNB) as an example to explain the method shown in Figure 12 in detail.
  • gNB can be composed of gNB-CU-CP, multiple gNB-CU-UP and multiple gNB-DU.
  • gNB-CU-CP is connected to gNB-DU through F1-C interface
  • gNB-CU-UP is connected to gNB-DU through F1-U interface
  • gNB-CU-UP is connected to gNB-CU-CP through E1 interface.
  • one gNB-DU is only connected to one gNB-CU-CP
  • one gNB-CU-UP is only connected to one gNB-CU-CP.
  • the base station's gNB-CU-CP needs to retrieve the MRB progress from gNB-CU-UP.
  • the terminal device switches from the source base station to the target base station, different from the unicast service, the last data packet that the MRB on the source base station side has sent to the terminal device cannot be determined.
  • the establishment of F1-U is not necessarily based on the terminal equipment level. It is most likely at the distributed unit DU level or the cell level. Therefore, how does gNB-CU-CP query the progress of gNB-CU-UP for terminal equipment? is a problem that needs to be solved.
  • the target gNB needs to provide the PDCP SN information of the oldest data packet available to the target NG-RAN node to the MRB, so the target gNB-CU-UP only needs to provide the source gNB-CU-UP
  • the SN of the oldest data packet includes each MRB information and is not specific information of the terminal device. Therefore, you can directly query the MRB information in the source base station.
  • MRB progress information needs to be retrieved for some terminal devices. This includes the PDCP SN information of the last data packet that has been delivered to the terminal device by the MRB. From the perspective of the target base station gNB-CU-UP, for some terminal devices, the data packet is transmitted from the F1-U tunnel through the DU/Cell level (the progress of its transmission represents the progress of multiple terminal devices), and for some other terminal devices Device, data packets are transmitted through the level F1-U tunnel of the terminal device. Therefore, the MRB progress information of the source gNB is specific information of the terminal device. Therefore, how to query the progress information of the MRB is a technical problem that needs to be solved.
  • the method includes the following steps:
  • the source gNB-CU-CP sends the third indication information to the source gNB-CU-UP.
  • the source gNB-CU-UP receives the third indication information from the source gNB-CU-CP.
  • the third indication information is used to determine the MRB progress information corresponding to the terminal device.
  • the third indication information includes MBS Multicast F1-U Context Descriptor information element.
  • the third indication information is included in the MC context Modification Request message.
  • the MC context Modification Request message may specifically include one or more of the following: gNB-CU-CP MBS E1AP ID, gNB-CU-UP MBS E1AP ID, multicast bearer context modification information, MRB list.
  • the source gNB-CU-CP needs to provide the following information to the source gNB-CU-UP:
  • the source gNB-CU-CP needs to provide information about the DU-level F1-U shared tunnel.
  • the information about the shared tunnel may be displayed or implicit. For example, it can be a branch of choice directly used to indicate the information of the F1-U shared tunnel at the DU level. It can be the identification ID of the DU, or it can be the source gNB-CU-CP MBS E1AP ID and source gNB-CU. -UP MBS E1AP ID, etc.
  • the source gNB-CU-CP needs to provide cell information.
  • it can be CGI or CGI+DU-ID.
  • the source gNB-CU-CP needs to provide the terminal device information.
  • it can be C-RNTI+DU ID or gNB-CU UE F1AP ID+gNB-DU UE F1AP ID.
  • MBS Multicast F1-U Context Descriptor any type of tunnel can be represented by MBS Multicast F1-U Context Descriptor.
  • this field is the third indication information.
  • an identifier is introduced, which can be used to identify tunnel information, such as F1 tunnel No. 1, tunnel No. 2, etc.
  • the relevant identification information can be directly carried without distinguishing the category. Just make an inquiry.
  • S1320 The source gNB-CU-UP sends progress response information to the source gNB-CU-CP.
  • the source gNB-CU-CP receives the progress response information from the source gNB-CU-UP.
  • the progress response information is used to indicate the MRB progress information of each terminal device.
  • the progress response information can also be other information names, which this application does not limit.
  • the progress response information is included in the MC context Modification Response message, which also includes at least one of the following: gNB-CU-CP MBS E1AP ID, gNB-CU-UP MBS E1AP ID, multicast Bearer context modification response information, MRB list.
  • the source gNB-CU-CP sends third indication information to the source gNB-CU-UP.
  • the third indication information is used to determine the MRB progress information corresponding to the terminal device.
  • the source gNB-CU-UP Send progress response information to the source gNB-CU-CP, where the progress response information is used to indicate the MRB progress information of each terminal device.
  • the source gNB-CU-CP can determine the progress of the MRB corresponding to each terminal device through the method shown in Figure 13 above.
  • the progress corresponding to the specific MRB in Figure 13 above may also be the slowest transmission progress in the F1 transmission tunnels of different levels corresponding to the MRB.
  • the progress of DU-level tunnel feedback is No. 5
  • the progress of terminal device-level tunnel feedback is No. 6. Since the source gNB-CU-UP does not know which tunnel data the terminal device receives, the source gNB-CU-UP selects The slowest progress is sent to the source gNB-CU-CP. This method adopts this conservative MRB progress to forward data between the source base station and the target base station without forwarding data packets.
  • the data packets sent by the target base station to the terminal device are determined based on the PDCP status report reported by the terminal device on the target base station side. . Although some more data packets may be forwarded, at least there will be no less transmission and no errors.
  • Embodiments of the present application can divide the transmitting end device or the receiving end device into functional modules according to the above method examples.
  • 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 integrated modules can be implemented in the form of hardware or 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. In actual implementation, there may be other division methods. The following is an example of dividing each functional module according to each function.
  • FIG 14 is a schematic block diagram of an information transmission device 1400 provided by this application. Any equipment involved in any of the above methods in Figures 6 to 13, such as terminal equipment and network equipment, can be implemented by the communication equipment shown in Figure 14.
  • the information transmission device 1400 may be a physical device, a component of the physical device (for example, an integrated circuit, a chip, etc.), or a functional module in the physical device.
  • the communication device 1400 includes: one or more processors 1413.
  • the processor 1413 can call an interface to implement the receiving and sending functions.
  • the interface may be a logical interface or a physical interface, which is not limited.
  • the interface may be a transceiver circuit, an input-output interface, or an interface circuit.
  • Transceiver circuits, input and output interfaces or interface circuits used to implement receiving and transmitting functions can be separate or integrated together.
  • the above-mentioned transceiver circuit or interface circuit can be used for reading and writing code/data, or the above-mentioned transceiver circuit or interface circuit can be used for signal transmission or transfer.
  • the interface can be implemented via transceivers.
  • the information transmission device 1400 may also include a transceiver 1430.
  • the transceiver 1430 may also be called a transceiver unit, a transceiver, a transceiver circuit, etc., and is used to implement transceiver functions.
  • the communication device 1400 may also include a memory 1420.
  • the embodiment of the present application does not specifically limit the specific deployment location of the memory 1420.
  • the memory may be integrated in the processor or independent of the processor.
  • the device 1400 is not included In the case of storage, the device 1400 only needs to have processing functions, and the storage can be deployed in other locations (such as a cloud system).
  • the processor 1410, the memory 1420 and the transceiver 1430 communicate with each other through internal connection paths to transmit control and/or data signals.
  • the device 1400 may also include other devices, such as input devices, output devices, batteries, and the like.
  • the memory 1420 may store execution instructions for executing the methods of embodiments of the present application.
  • the processor 1410 can execute the instructions stored in the memory 1420 and combine with other hardware (such as the transceiver 1430) to complete the steps of the method shown below.
  • other hardware such as the transceiver 1430
  • the method disclosed in the embodiment of this application can be applied to the processor 1410 or implemented by the processor 1410.
  • the processor 1410 may be an integrated circuit chip with signal processing capabilities.
  • each step of the method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA), or other available processors.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • programmed logic devices discrete gate or transistor logic devices, discrete hardware components.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • Software modules can be located in random access memory (random access memory, RAM), flash memory, read-only memory (read-only memory, ROM), programmable read-only memory or electrically erasable programmable memory, registers, etc. that are mature in this field. in the storage medium.
  • the storage medium is located in the memory, and the processor reads the instructions in the memory and completes the steps of the above method in combination with its hardware.
  • memory 1420 may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • non-volatile memory can be read-only memory ROM, programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory RAM, which acts as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • FIG. 15 is a schematic block diagram of a communication device 1500 provided by this application.
  • the device 1500 includes a transceiver unit 1520, which may be used to implement corresponding communication functions.
  • the transceiver unit 1520 may also be called a communication interface or communication unit.
  • the device 1500 may also include a processing unit 1510, which may be used for data processing.
  • a processing unit 1510 which may be used for data processing.
  • the specific form of the device 1500 for information transmission may be a general computer device or a chip in a general computer device, which is not limited in the embodiment of the present application.
  • the device includes a processing unit 1510 and a transceiver unit 1520.
  • the device 1500 can be any device involved in this application, and can implement the functions that the device can implement. It should be understood that the device 1500 may be a physical device, a component of the physical device (for example, an integrated circuit, a chip, etc.), or a functional module in the physical device.
  • the device 1500 may be the terminal device (eg, terminal device) in the above method embodiment, or may be used to implement the terminal device (eg, terminal device) in the above method embodiment.
  • Functional chip e.g.
  • the device 1500 also includes a storage unit, which can be used to store instructions and/or data, and the processing unit 1510 can read the instructions and/or data in the storage unit, so that the device implements each of the foregoing method embodiments.
  • the actions of different terminal devices in the network for example, controlling the actions of network elements or terminal devices.
  • the device 1500 can be used to perform the actions performed by the control network element or terminal equipment in each of the above method embodiments.
  • the device 1500 can be a control network element or terminal equipment, or a component of the control network element or terminal equipment.
  • the transceiver unit 1520 is configured to perform operations related to the transceiver of the control network element or terminal equipment in the above method embodiment
  • the processing unit 1510 is used to perform operations related to the processing of the control network element or terminal equipment in the above method embodiment.
  • the device 1500 can be used to perform the actions performed by controlling network elements or network equipment in each of the above method embodiments.
  • the transceiver unit 1520 in the device 1500 can be implemented through a communication interface (such as a transceiver or an input/output interface), for example, it can correspond to the communication interface 1430 shown in FIG. 14
  • the processing unit 1510 in the device 1500 can be implemented through At least one processor implementation, for example, may correspond to processor 1410 shown in FIG. 14 .
  • the device 1500 may also include a storage unit, which may be used to store instructions or data, and the processing unit may call the instructions or data stored in the storage unit to implement corresponding operations.
  • a storage unit which may be used to store instructions or data
  • the processing unit may call the instructions or data stored in the storage unit to implement corresponding operations.
  • the communication device 1500 is presented in the form of a functional module.
  • Module here may refer to an application specific integrated circuit (ASIC), a circuit, a processor and memory that executes one or more software or firmware programs, an integrated logic circuit, and/or other devices that can provide the above functions.
  • ASIC application specific integrated circuit
  • the processing unit 1510 may be implemented by the processor 1410 shown in FIG. 14 .
  • the computer device shown in FIG. 14 includes a memory 1400
  • the processing unit 1510 may be implemented by the processor 1415 and the memory 1400.
  • the transceiver unit 1520 may be implemented by the transceiver 1430 shown in FIG. 14 .
  • the transceiver 1430 includes a receive function and a transmit function.
  • the processor is implemented by executing the computer program stored in the memory.
  • the functions and/or implementation processes of the transceiver unit 1520 can also be implemented through pins or circuits.
  • the memory may be a storage unit within the chip, such as a register, cache, etc., or the storage unit may be a storage unit located outside the chip within the device, such as the memory 1420 shown in Figure 14, Alternatively, it may also be a storage unit deployed in other systems or devices, not within the computer device.
  • computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, tapes, etc.), optical disks (e.g., compact discs (CD), digital versatile discs (DVD)) etc.), smart cards and flash memory devices (e.g. erasable programmable read-only memory (EPROM), cards, sticks or key drives, etc.).
  • the various storage media described herein may represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, various other media capable of storing, containing and/or carrying instructions and/or data.
  • the present application also provides a computer program product.
  • the computer program product includes: a computer program or a set of instructions.
  • the computer program or a set of instructions When the computer program or a set of instructions is run on a computer, the computer causes the computer to execute The method of any one of the embodiments shown in Figures 5 to 8.
  • the present application also provides a computer-readable storage medium.
  • the computer-readable medium stores a program or a set of instructions.
  • the program or a set of instructions is run on a computer, the computer The method of any one of the embodiments shown in FIG. 5 to FIG. 8 is executed.
  • the present application also provides a communication system, which includes the aforementioned device or equipment.
  • a component may be, but is not limited to, a process, a processor, an object, an executable file, a thread of execution, a program and/or a computer running on a processor.
  • applications running on the computing device and the computing device may be components.
  • One or more components can reside in a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. Additionally, these components can execute from various computer-readable media having various data structures stored thereon.
  • a component may pass a signal based on a signal having one or more data packets (e.g., data from two components interacting with another component on a local system, a distributed system, and/or on a network, such as the Internet, which interacts with other systems via signals).
  • data packets e.g., data from two components interacting with another component on a local system, a distributed system, and/or on a network, such as the Internet, which interacts with other systems via signals.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (Random Access Memory, RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

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

Abstract

本申请实施例提供了一种通信方法和通信装置。该方法包括：终端设备接收第一信息，第一信息与第一组播业务的状态相关，和/或，第一信息与第二小区中第一组播业务的配置信息相关；终端设备根据第一信息，判断是否向第二小区发送第一请求信息，第一请求信息用于终端设备建立或恢复RRC连接，其中，终端设备为接收第一组播业务的终端设备，终端设备为处于无线资源控制RRC非连接态的终端设备，且终端设备是从所述第一小区切换或者重选至所述第二小区的终端设备。本申请提供的技术方案，避免了终端设备在切换或者重选的过程中，不必要的进入连接态，导致资源的浪费。

Description

通信方法和通信装置
本申请要求于2022年08月05日提交中国专利局、申请号为202210939716.2、申请名称为“通信方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且更具体地，涉及一种通信方法和通信装置。
背景技术
多播广播业务(Multicast and Broadcast Service，MBS)是面向多个终端设备(User Equipment，UE)的业务，例如直播业务、公共安全业务、批量软件更新业务等。MBS业务来自数据服务器。其中，数据服务器将MBS数据发送给核心网设备，然后核心网设备将MBS数据发送给基站，最后基站将MBS数据发送给接收MBS业务的至少一个终端设备。
其中，在核心网向基站发送MBS数据时，MBS业务通过一个公共的传输通道MBS会话进行传输，每个MBS会话中可以包含至少一个MBS QoS流。而在基站向终端设备发送MBS数据时，数据包通过MBS无线承载传输，对于一个MBS无线承载来说有两种传输模式：第一种可以采用点到多点(point to multi-point，PTM)传输方式；第二种可以采用点到点(point to point，PTP)传输方式。
组播业务是针对高Qos需求业务设计的，需要针对组播业务进行组管理，可以提供和单播业务相同的QoS等级。具体地，针对组播业务，核心网需要管理终端设备的加入和退出。对于核心网和基站之间的传输依托于PDU session，引入新的MBS QoS flow。对于无线接入网(radio access network，RAN)，支持PTP和PTM传输方式向终端设备发送数据，并且支持由RAN控制的PTP和PTM之间的动态切换。在3GPP协议的版本17中，组播业务只能提供给无线资源控制(radio resource control，RRC)连接态的终端设备，需要接入网和核心网维护多播业务组对应的终端设备的信息。
发明内容
本申请实施例提供一种通信方法，能够避免了终端设备在从第一小区切换或者重选至时，发起不必要的建立连接或者恢复连接的请求信息，降低了资源的消耗。
第一方面，提供了一种通信方法，包括：终端设备接收第一信息，第一信息与第一组播业务的状态相关，和/或，第一信息与第二小区中所述第一组播业务的配置信息相关；终端设备根据第一信息，判断是否向第二小区发送第一请求信息，第一请求信息用于终端设备建立或恢复RRC连接，其中，终端设备为接收第一组播业务的终端设备，终端设备为处于无线资源控制RRC非连接态的终端设备，且终端设备是从第一小区切换或者重选至第二小区的终端设备。根据本申请提供的一种通信方法，终端设备接收第一信息，并根据该第一信息判断是否向第二小区发送第一请求信息，该第一请求信息用于终端设备从第一小区切换或者重选至第二小区建立或者恢复RRC连接。其中，该第一信息与第一组播业务的状态相关，和/或，第一信息与第二小区中第一组播业务的配置信息相关，从而避免终端设备在从第一小区切换或者重选至时，发起不必要的建立连接或者恢复连接的请求信息，降低了资源的消耗。
应理解，在终端设备从第一小区切换或者重选至第二小区时，终端设备直接接入可能会占用网络的接入资源，因此本申请提供的方法还可以避免加重网络拥塞的程度。
结合第一方面，在一些可能实现方式中，终端设备根据第一信息，判断是否向第二小区发送第一请求信息，包括：当第一组播业务的状态为激活态时，终端设备向第二小区发送第一请求信息，或者，当第一组播业务的状态为非激活态时，终端设备保持非连接态。
基于上述方案，当第一信息与第一组播业务的状态相关时，终端设备根据第一组播业务的状态判断是否向第二小区发送该第一请求信息，或者，该终端设备继续保持非连接的状态，避免终端设备不判断业务状态就发起接入，在第二小区接入连接态之后，由于业务去激活又被释放，造成资源的浪费。
结合第一方面，在一些可能实现方式中，终端设备根据第一信息，判断是否向第二小区发送第一请求信息，包括：当第一小区与第二小区的中第一组播业务配置信息不同时，终端设备向第二小区发送第一请求信息，或者，当第一小区与第二小区中第一组播业务的配置信息相同时，终端设备保持非连接态。
基于上述方案，当第一信息与第二小区中第一组播业务的配置信息相关时，终端设备根据第二小区中第一组播业务的配置信息判断是否向第二小区发送该第一请求信息，或者，该终端设备继续保持非连接的状态，避免终端设备不确定配置是否相同就发起接入，在第二小区接入连接态之后，又被释放，由于配置相同引发不必要的接入，造成资源的浪费。
结合第一方面，在一些可能实现方式中，终端设备根据第一信息，判断是否向第二小区发送第一请求信息，包括：当第一小区与第二小区中第一组播业务的配置信息相同，且第一组播业务的状态为激活态时，终端设备向第二小区发送第一请求信息，或者，当第一小区与第二小区中第一组播业务的配置信息相同，且第一组播业务的状态为去激活态时，终端设备保持非连接态。
基于上述方案，当第一信息与第一组播业务的状态和第二小区中第一组播业务的配置信息相关时，终端设备根据第一组播业务的状态和第二小区中第一组播业务的配置信息判断是否向第二小区发送该第一请求信息，或者，该终端设备继续保持非连接的状态，避免终端设备在第二小区接入连接态之后，又被释放，造成资源的浪费。
结合第一方面，在一些可能实现方式中，终端设备接收第一寻呼消息，第一寻呼消息包括第一组播业务的标识。
基于上述方案，终端设备在保持非连接态时，当终端设备接收到第一寻呼消息，该第一寻呼消息包括第一组播业务的标识，则终端设备确定第一组播业务激活，或者需要进入连接态。举例来说，终端设备根据该第一寻呼消息向第二小区发送第一请求信息，进入连接态。
结合第一方面，在一些可能实现方式中，终端设备接收第二信息，第二信息用于确定第二小区未向所述非连接态的终端设备提供所述第一组播业务。
基于上述方案，终端设备接收第二信息，该第二信息可以来自第一小区或者第二小区，第二信息用于确定第二小区未向所述非连接态的终端设备提供第一组播业务，则终端设备进一步地根据第一组播业务的状态和/或第二小区中第一组播业务的配置信息判断是否向第二小区发送第一请求信息。
应理解，该第二信息可以直接指示第二小区不支持非连接态的组播业务，或者，该第二信息可以指示第二小区支持非连接态的组播业务，但第二小区提供的非连接态的组播业务中不包括第一组播业务，对此本申请不做限定。
结合第一方面，在一些可能实现方式中，当第二信息包括第二小区的多播控制信道MCCH的配置信息时，终端设备根据MCCH的配置信息，获取第三信息，第三信息包括第二小区的MCCH信息，且MCCH信息不包括第一组播业务的标识，或者，终端设备根据MCCH的配置信息，未获取到第三信息。基于上述方案，第二信息包括第二小区的MCCH的配置信息，则表明该第二小区支持非连接态的组播业务，终端设备根据该MCCH的配置信息获取第三信息，该第三信息包括MCCH信息，该MCCH信息不包括第一组播业务的标识，则表示该第二小区支持非连接态的组播业务，但该第二小区未向非连接态的终端设备提供第一组播业务。或者，终端设备接收的第二信息包括MCCH的配置信息，但该终端设备根据该MCCH配置信息，并未获取到该第三信息，则表明，该第二小区未向所述非连接态的终端设备提供组播业务。
结合第一方面，在一些可能实现方式中，第一信息携带在如下至少一项消息中：寻呼paging消息、系统信息块SIB、MCCH信息。基于上述方案，第一信息携带在寻呼paging消息、系统信息块SIB、MCCH信息中至少一项消息中发送给终端设备。终端设备无需进入连接态，就能够接收到第一信息。
可选地，终端设备获取第一信息，也可能是终端设备在连接态的时候获取得到的，或者，通过RRC释放消息(RRC release消息)获得第一信息，对此本申请不做限定。
结合第一方面，在一些可能实现方式中，在第一信息与第二小区中所述第一组播业务的配置信息相关的情况下，第一信息包括第二小区的PDCP同步信息和/或第一小区的PDCP同步信息，同步信息包括PDCP同步或者不同步。
基于上述方案，当第一信息与第二小区中第一组播业务的配置信息相关时，该第一信息还可以包 括第二小区的PDCP同步信息和/或第一小区的PDCP同步信息，该同步信息包括第二小区的PDCP和/或第一小区的PDCP同步或者不同步。终端设备根据第二小区的PDCP同步信息和/或第一小区的PDCP同步信息，进一步地确定PDCP层的处理方法。
结合第一方面，在一些可能实现方式中，当同步信息包括的第二小区的PDCP和/或第一小区的PDCP不同步时，终端设备重置PDCP实体或者PDCP变量，和/或，终端设备对缓存的PDCP数据包进行丢弃或者递交高层。
基于上述方案，第一小区的PDCP不同步和/或第二小区的PDCP不同步时，终端设备可以重置PDCP实体或者PDCP变量，和/或，终端设备对缓存的PDCP数据包进行丢弃或者递交高层。
可选地，第一小区的PDCP不同步和/或第二小区的PDCP不同步时，终端设备向第二小区发送第一请求信息，终端设备与第二小区进入连接态之后，在第二小区接收PDCP的配置。
第二方面，提供了一种通信方法，该方法包括：第一小区确定第一信息，第一信息与第一组播业务的状态相关；第一小区向终端设备发送第一信息，第一信息用于判断终端设备是否向第二小区发送第一请求信息，第一请求信息用于终端设备建立或恢复RRC连接，其中，终端设备为接收第一组播业务的终端设备，终端设备为处于无线资源控制RRC非连接态的终端设备，且终端设备是从第一小区切换或者重选至第二小区的终端设备。
应理解，本申请中的第一小区的所有步骤以及处理过程，服务与第一小区的第一网络设备都可以执行。
结合第二方面，在一些可能实现方式中，第一组播业务的状态包括激活态，或者去激活态。
结合第二方面，在一些可能实现方式中，第一小区向终端设备发送第二信息，第二信息用于确定第二小区未向所述非连接态的终端设备提供所述第一组播业务。
结合第二方面，在一些可能实现方式中，第一信息携带在如下至少一项消息中：寻呼paging消息、系统信息块SIB、MCCH信息。
基于上述方案，第一信息携带在寻呼paging消息、系统信息块SIB、MCCH信息中至少一项消息中发送给终端设备。终端设备无需进入连接态，就能够接收到第一信息。
可选地，终端设备获取第一信息，也可能是终端设备在连接态的时候获取得到的，或者，通过RRC释放消息(RRC release消息)获得第一信息，对此本申请不做限定。
第三方面，提供了一种通信方法，该方法包括：第二小区确定第二信息，第二信息用于确定第二小区未向非连接态的终端设备提供第一组播业务；第二小区向终端设备发送第二信息，其中，终端设备为接收第一组播业务的终端设备，终端设备为处于无线资源控制RRC非连接态的终端设备，且终端设备是从第一小区切换或者重选至第二小区的终端设备。
应理解，本申请中的第二小区的所有步骤以及处理过程，服务与第二小区的第二网络设备都可以执行。
结合第三方面，在一些可能实现方式中，第二小区向终端设备发送第三信息，第三信息包括第二小区的MCCH信息，且MCCH信息不包括第一组播业务的标识。
结合第三方面，在一些可能实现方式中，第二小区向第一网络设备发送第二小区中所述第一组播业务的配置信息，配置信息用于确定第一信息，其中，第一小区与第二小区为相邻小区，或者该第二小区是第一小区一定范围内的小区，或者第一小区与第二小区是同一RNA内的小区。
结合第三方面，在一些可能实现方式中，第二小区向第一网络设备发送第二小区的PDCP同步信息，同步信息包括PDCP同步或者不同步。
第四方面，提供了一种通信方法，该方法包括：第一网络设备确定第一信息，第一信息与第二小区中所述第一组播业务的配置信息相关；第一网络设备向终端设备发送第一信息，第一信息用于判断终端设备是否向第二小区发送第一请求信息，第一请求信息用于终端设备建立或恢复RRC连接，其中，终端设备为接收第一组播业务的终端设备，终端设备为处于无线资源控制RRC非连接态的终端设备，且终端设备是从第一小区切换或者重选至第二小区的终端设备。
结合第四方面，在一些可能实现方式中，第一网络设备接收来自第二小区中所述第一组播业务的配置信息，配置信息用于确定第一信息。
结合第四方面，在一些可能实现方式中，述第一信息包括第二小区的PDCP同步信息，同步信息 包括PDCP同步或者不同步。
结合第四方面，在一些可能实现方式中，第一信息携带在如下至少一项消息中：寻呼paging消息、系统信息块SIB、MCCH信息。
基于上述方案，第一信息携带在寻呼paging消息、系统信息块SIB、MCCH信息中至少一项消息中发送给终端设备。终端设备无需进入连接态，就能够接收到第一信息。
可选地，终端设备获取第一信息，也可能是终端设备在连接态的时候获取得到的，或者，通过RRC释放消息(RRC release消息)获得第一信息，对此本申请不做限定。
第五方面，提供了一种通信装置，收发单元接收第一信息，第一信息与第一组播业务的状态相关，和/或，第一信息与第二小区中所述第一组播业务的配置信息相关；处理单元根据第一信息，判断是否向第二小区发送第一请求信息，第一请求信息用于终端设备建立或恢复RRC连接，其中，收发单元为接收第一组播业务的收发单元，收发单元和处理单元属于处于无线资源控制RRC非连接态的终端设备，且终端设备是从第一小区切换或者重选至第二小区的终端设备。
结合第五方面，在一些可能实现方式中，处理单元根据第一信息，判断是否向第二小区发送第一请求信息，包括：当第一组播业务的状态为激活态时，收发单元向第二小区发送第一请求信息，或者，当第一组播业务的状态为非激活态时，处理单元保持非连接态。
结合第五方面，在一些可能实现方式中，处理单元根据第一信息，判断是否向第二小区发送第一请求信息，包括：当第一小区与第二小区中所述第一组播业务的配置信息不同时，收发单元向第二小区发送第一请求信息，或者，当第一小区与第二小区中所述第一组播业务的配置信息相同时，处理单元保持非连接态。
结合第五方面，一些可能实现方式中，处理单元根据第一信息，判断是否向第二小区发送第一请求信息，包括：当第一小区与第二小区中所述第一组播业务的配置信息相同，且第一组播业务的状态为激活态时，收发单元向第二小区发送第一请求信息，或者，当第一小区与第二小区中所述第一组播业务的配置信息相同，且第一组播业务的状态为去激活态时，处理单元保持非连接态。
结合第五方面，在一些可能实现方式中，收发单元接收第一寻呼消息，第一寻呼消息包括第一组播业务的标识。
结合第五方面，在一些可能实现方式中，收发单元接收第二信息，第二信息用于确定第二小区未向所述非连接态的终端设备提供第一组播业务。
结合第五方面，在一些可能实现方式中，当第二信息包括第二小区的多播控制信道MCCH的配置信息时，处理单元根据MCCH的配置信息，获取第三信息，第三信息包括第二小区的MCCH信息，且MCCH信息不包括第一组播业务的标识，或者，终端设备根据MCCH的配置信息，未获取到第三信息。
结合第五方面，在一些可能实现方式中，第一信息携带在如下至少一项消息中：寻呼paging消息、系统信息块SIB、MCCH信息。
结合第五方面，在一些可能实现方式中，在第一信息与第二小区中所述第一组播业务的配置信息相关的情况下，第一信息包括第一小区的PDCP同步信息和/或第二小区的PDCP同步信息，同步信息包括PDCP同步或者不同步。
结合第五方面，在一些可能实现方式中，当同步信息包括的第一小区的PDCP和/或第二小区的PDCP不同步时，处理单元重置PDCP实体或者PDCP变量，和/或，处理单元对缓存的PDCP数据包进行丢弃或者递交高层。
第六方面，提供了一种通信装置，处理单元确定第一信息，第一信息与第一组播业务的状态相关；收发单元向终端设备发送第一信息，第一信息用于判断终端设备是否向第二小区发送第一请求信息，第一请求信息用于终端设备建立或恢复RRC连接，其中，终端设备为接收第一组播业务的终端设备，终端设备为处于无线资源控制RRC非连接态的终端设备，且终端设备是从第一小区切换或者重选至第二小区的终端设备。
结合第六方面，在一些可能实现方式中，第一组播业务的状态包括激活态，或者去激活态。
结合第六方面，在一些可能实现方式中，处理单元向终端设备发送第二信息，第二信息用于确定第二小区未向所述非连接态的终端设备提供第一组播业务。
结合第六方面，在一些可能实现方式中，第二信息包括第二小区的多播控制信道MCCH的配置信 息。
结合第六方面，在一些可能实现方式中，第一信息携带在如下至少一项消息中：寻呼paging消息、系统信息块SIB、MCCH信息。
可选地，收发单元获取第一信息，也可能是在连接态的时候获取得到的，或者，通过RRC释放消息获得，对此本申请不做限定。
第七方面，提供了一种通信装置，处理单元确定第二信息，第二信息用于确定第二小区未向非连接态的终端设备提供第一组播业务；收发单元向终端设备发送第二信息，其中，终端设备为接收第一组播业务的终端设备，终端设备为处于无线资源控制RRC非连接态的终端设备，且终端设备是从第一小区切换或者重选至第二小区的终端设备。
结合第七方面，在一些可能实现方式中，处理单元向终端设备发送第三信息，第三信息包括第二小区的MCCH信息，且MCCH信息不包括第一组播业务的标识。
结合第七方面，在一些可能实现方式中，处理单元向第一网络设备发送第二小区中所述第一组播业务的配置信息，配置信息用于确定第一信息，其中，第一小区与第二小区为相邻小区。
结合第七方面，在一些可能实现方式中，处理单元向第一网络设备发送第二小区的PDCP同步信息，同步信息包括PDCP同步或者不同步。
第八方面，提供了一种通信方法，该方法包括：处理单元确定第一信息，第一信息与第二小区中所述第一组播业务的配置信息相关；收发单元向终端设备发送第一信息，第一信息用于判断终端设备是否向第二小区发送第一请求信息，第一请求信息用于终端设备建立或恢复RRC连接，其中，终端设备为接收第一组播业务的终端设备，终端设备为处于无线资源控制RRC非连接态的终端设备，且终端设备是从第一小区切换或者重选至第二小区的终端设备。
结合第八方面，在一些可能实现方式中，收发单元接收来自第二小区中所述第一组播业务的配置信息，配置信息用于确定第一信息。
结合第八方面，在一些可能实现方式中，述第一信息包括第一小区的PDCP同步信息和/或第二小区的PDCP同步信息，同步信息包括PDCP同步或者不同步。
结合第八方面，在一些可能实现方式中，第一信息携带在如下至少一项消息中：寻呼paging消息、系统信息块SIB、MCCH信息。
第九方面，提供一种通信装置，本申请提供一种通信设备，该通信设备可以是网络设备或者终端设备，其中，该通信设备包括收发器、处理器和存储器。处理器用于控制收发器收发信号，存储器用于存储计算机程序，处理器用于调用并运行存储器中存储的计算机程序，使得终端设备执行第一方面中任意可能的实现方式中的方法，网络设备执行第二方面中任意可能的实现方式中的方法，或者，网络设备执行第三方面中任意可能的实现方式中的方法，或者，网络设备执行第四方面中任意可能的实现方式中的方法。
具体地，在终端设备作为信息和/或数据的发送端时，终端设备执行上述第一方面及其任意可能的实现方式中的通信方法，对需要发送的信息和/或数据进行发送。在网络设备作为信息和/或数据的接收端时，网络设备以执行上述第二方面至第四方面的任一可能的实现方式中的通信方法。
第十方面，本申请提供一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行第一方面至第四方面中任意一种可能的实现方式中的方法。
第十一方面，本申请提供一种计算机程序产品，该计算机程序产品包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行上述第一方面至第四方面中任意一种可能的实现方式中的方法。
第十二方面，本申请提供一种芯片，包括处理器。处理器用于读取并执行存储器中存储的计算机程序，以执行上述第一方面至第四方面中任意一种可能的实现方式中的方法。可选地，该芯片还包括存储器，该存储器与该处理器通过电路或电线与存储器连接。
附图说明
图1是本申请实施例提供的一种MBS业务传输过程的示意图。
图2是本申请实施例提供的一种终端设备接收广播数据的流程示意图。
图3是本申请实施例提供的一种终端设备RRC建立/恢复的流程性示意图。
图4是本申请实施例提供的一种终端切换场景的示意图。
图5是本申请实施例提供的另一种终端切换场景的示意图。
图6是本申请实施例提供的一种通信方法的示意图。
图7是本申请实施例提供的另一种通信方法的示意图。
图8是本申请实施例提供的另一种通信方法的示意图。
图9是本申请实施例提供的另一种通信方法的示意图。
图10是本申请实施例提供的另一种通信方法的示意图。
图11是本申请实施例提供的另一种通信方法的示意图。
图12是本申请实施例适用的一种通信架构示意图。
图13是本申请实施例提供的另一种通信方法的示意图。
图14是本申请实施例提供的一种通信装置的示意性结构图。
图15是本申请实施例提供的另一种通信装置的示意性结构图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、LTE频分双工(Frequency Division Duplex，FDD)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、全球互联微波接入(Worldwide Interoperability for Microwave Access，WiMAX)通信系统、未来的第五代(5th Generation，5G)系统或新无线(New Radio，NR)等。
本申请实施例中的终端设备可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。
应理解，本申请实施例中，终端设备可以是用于实现终端设备功能的装置，也可以是能够支持终端设备实现该功能的装置，例如芯片系统，该装置可以被安装在终端中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备可以是全球移动通讯(Global System of Mobile communication，GSM)系统或码分多址(Code Division Multiple Access，CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统中的基站(NodeB，NB)，还可以是LTE系统中的演进型基站(Evolutional NodeB，eNB或eNodeB)，还可以是云无线接入网络(Cloud Radio Access Network，CRAN)场景下的无线控制器，或者该网络设备可以为中继站、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备等，本申请实施例并不限定。
应理解，本申请实施例中，网络设备可以是用于实现网络设备功能的装置，也可以是能够支持网络设备实现该功能的装置，例如芯片系统，该装置可以被安装在网络设备中。
还应理解，下文示出的实施例并未对本申请实施例提供的方法的执行主体的具体结构特别限定，只要能够通过运行记录有本申请实施例的提供的方法的代码的程序，以根据本申请实施例提供的方法进行通信即可，例如，本申请实施例提供的方法的执行主体可以是终端设备或网络设备，或者，是终端设备或网络设备中能够调用程序并执行程序的功能模块。其中，本申请示出的实施例可以部分实施，也可以各个实施例之间相互组合完成之后，部分实施或者全部实施，对此本申请不做限定。
需要说明的是，本申请中的第一小区的所有步骤以及处理过程，可以是第一小区提供服务的第一网络设备执行的；类似地，本申请中的第二小区的所有步骤以及处理过程，可以是第二小区提供服务的第二网络设备执行的。
为了便于理解，首先对本申请实施例所涉及的通信名词或术语进行解释说明，该通信名词或术语，也作为本申请发明内容的一部分。
1.多播广播业务(multicast and broadcast service，MBS)
多播广播业务MBS是面向多个终端设备业务(例如，直播业务、公共安全业务、批量软件更新业务等)。
如图1所示的MBS业务传输过程示意图，MBS业务来自数据服务器，首先数据服务器将MBS数据发送给核心网设备，然后核心网设备将MBS数据发送给接入网设备，最后接入网设备将MBS数据发送给接收MBS业务的至少一个终端设备。从核心网向接入网设备发送的时候，MBS业务通过一个公共的传输通道MBS会话进行传输，每个MBS会话中可以包含至少一个MBS QoS流。而从接入网设备向终端设备发送的时候，MBS数据包通过MBS无线承载传输，对于一个MBS无线承载来说可以有两种传输模式：
第一种：采用点到多点(point to multi-point，PTM)传输方式；
第二种：采用点到点(point to point，PTP)传输方式。
2.组播业务(multicast)
组播业务是针对高服务质量(quality of service，QoS)需求业务设计的，需要针对组播业务进行组管理，可以提供和单播业务相同的QoS等级。具体的对于组播业务，核心网需要管理终端设备的加入和退出。对于核心网和接入网设备之间的传输依托于PDU会话(PDU session)，引入新的MBS QoS flow数据流。对于接入网设备，支持PTP传输方式和PTM传输方式向终端设备发送数据，并且支持由接入网设备控制的PTP和PTM之间的动态切换。在R17协议中，组播业务只能提供给RRC处于连接态的终端设备，需要接入网设备和核心网设备维护多播业务组对应的终端设备的信息。现有技术中，对于组播业务还支持由核心网触发的MBS session去激活/激活，终端设备不感知业务的状态。
3.组播业务的激活/去激活流程
MBS会话去激活过程仅适用于组播业务。MBS会话去激活流程由多播广播会话管理功能(multicast/broadcast session management function，MB-SMF)触发，其中当MB-SMF在一段时间内没有下行数据可传输的情况下，收到多播广播用户面功能(multicast/broadcast user plane function，MB-UPF)的通知时，或者当MB-SMF直接收到应用功能(application function，AF)或通过网络开放功能(network exposure function，NEF)的请求时。MBS Session去激活流程用于去激活NG-RAN节点的MBS数据资源。在5GC的触发下，RAN释放组播会话的无线资源，停止向终端数设备传输组播会话数据，网络设备可以对终端设备连接RRC释放空闲态或者非激活态(idle/inactive)或者不释放，并没有显式的去激活通知到终端设备。
MBS会话激活过程仅适用于组播业务。MBS会话激活过程由MB-SMF触发，当MB-SMF收到MB-UPF关于下行MBS数据的通知时，或者当MB-SMF直接收到AF或通过NEF的请求时。MBS Session激活流程用于激活NG-RAN节点的MBS数据资源。在5GC的触发下，组播会话的无线资源建立，组播会话数据开始传输给终端设备。其中，加入组播会话的RRC-IDLE状态和RRC Inactive状态的终端设备会被寻呼。
4.广播技术(broadcast)
NR MBS的广播技术中引入了两个逻辑信道，多播控制信道(MBS control channel，MCCH)和多播业务信道(MBS traffic channel，MTCH)，其中MCCH用于传输控制信息，包含MTCH的配置信息。举例来说，MTCH对应的G-RNTI以及DRX参数。MCCH以周期的方式进行发送。MTCH逻辑信道承载广播业务的用户数据，通过MCCH调度MTCH。MTCH的配置为per G-RNTI级别，也可说是per MBS service级别。其中，接入网设备通过组无线网络临时标识(group radio network temporary identifier，G-RNT)来同时向多个终端设备调度业务数据，每个G-RNTI可以关联至少一个广播业务。
如图2所示的终端设备接收广播数据的流程示意图。终端设备接收广播业务的流程是首先获取系统，系统消息中包含传输广播业务的控制信息(即MCCH的配置信息)，终端通过系统消息知晓如何 来接收MCCH消息。终端设备根据MCCH的配置信息读取MCCH的消息内容，其中MCCH消息中包括MBS广播配置消息，MBS广播配置信息即为MTCH的配置信息，G-RNTI，临时多播组播标识(temporary multicast group identifier，TMGI)等接受广播业务必要的配置。最后，终端设备根据配置信息在MTCH上接收广播业务数据。
5.非连接态
终端设备的无线资源控制(radio resource control，RRC)状态包括RRC连接(RRC-connected)态、RRC空闲(RRC-idle)态和RRC非活跃(RRC-inactive)态。以下实施例中的RRC非连接态，可包括RRC空闲态或RRC非活跃态中的至少一种。其中，RRC非连接态可以简称为非连接态。RRC连接态可以简称为连接态。RRC空闲态可以简称为空闲态。RRC非活跃态可以简称为非活跃态。本申请实施例中，至少一种可以是一种或多种。多种可以是2种、3种或更多种，不做限制。
在以下描述中，以网络设备或接入网设备为基站为例进行描述。具体的，终端设备在接入基站的过程中或者接入基站后，终端设备可以和基站进行RRC建立过程。
其中，终端设备与基站RRC建立或者恢复的过程如图3所示。
S310，终端设备向网络设备发送RRC建立/恢复请求信息。
应理解，该步骤S310为终端设备发起进入连接态的请求信息(例如，本申请实施例中终端设备向第二小区发送的第一请求信息)。
S320，网络设备向终端设备发送RRC建立/恢复响应信息。
具体地，网络设备接收来自终端设备的RRC建立请求信息，网络设备根据RRC建立请求信息向终端设备发送RRC建立响应信息。
应理解，网络设备接收来自终端设备的RRC恢复请求信息，网络设备根据RRC恢复请求信息向终端设备发送RRC恢复响应信息；或者，网络设备接收来自终端设备的RRC恢复请求信息，网络设备根据RRC恢复请求信息向终端设备发送RRC建立响应信息，使其终端设备重新建立RRC连接。
S330，终端设备向网络设备发送RRC建立/恢复完成信息。
具体地，终端设备接收来自网络设备的RRC建立响应信息，并根据该RRC建立响应信息进行RRC的建立，终端设备确定RRC建立完成之后，向网络设备发送该RRC建立完成信息。
应理解，终端设备接收来自网络设备的RRC恢复响应信息，并根据该RRC恢复响应信息进行RRC的建立，终端设备确定RRC恢复完成之后，向网络设备发送该RRC恢复完成信息。
上述图3中，介绍了终端设备与网络设备进行RRC建立/恢复的简单过程，具体详细介绍请参见现有技术。
终端设备和基站建立RRC连接后，该终端设备的RRC状态为RRC连接态。随后，终端设备的RRC状态可以在以下状态中进行转换：RRC空闲态、RRC连接态和RRC非活跃态。
标准R18已经立项决定研究组播业务可以提供给RRC非连接态终端设备，用于支持网络拥塞场景下终端设备尽量的接收组播业务。因为组播业务在连接态就可以通过PTM方式提供业务给多个终端设备，网络只发送一份数据，多个终端设备共同接收该数据。即，将组播业务提供给所有非连接态的终端设备，只发送了一份数据，不用占用过多的额外的资源。
其中，如何将非连接态模式的组播业务的配置信息提供给终端设备有一下两种参考方式：
方式一：终端设备在连接态时获取组播业务的配置信息，用于RRC release后继续在非连接态接收组播业务；
方式二：类似于广播技术的方式，网络设备在MCCH中提供非连接态组播业务的配置信息，该配置信息用于终端设备接收数据。
应理解，该MCCH可以和广播的现有的MCCH共用，也可以是为组播设计的MCCH(例如MC-MCCH)，对此本申请不做限定。其中，该MCCH用于包含组播的配置信息，其名称本申请不做限定。本申请实施例中所有提及的MCCH都是指用于包含组播配置的逻辑信道。
上述两种方式均可以实现处于非连接态的终端设备接收组播业务。在方式一中，处于非连接态的终端设备接收的业务不能直接变更其业务的配置信息。其中，方式二相较于方式一中的技术方案，更为灵活，方式二可以支持终端设备随时获取配置信息。对于方式二中的方案来说，终端设备如果在非连接态时，读取到的MCCH中包含接收的业务的标识(例如：TMGI)，即可认为该网络设备在非连 接态下提供了非连接态模式的对应业务，否则反之。
在现有标准R17技术中，组播业务的激活/去激活状态只由核心网设备通知给了接入网设备，不通知终端设备。当组播业务去激活后，长时间没有数据，网络可以决定将终端设备的RRC连接释放到RRC空闲态或者RRC非活跃态。此时处于非连接态模式的终端设备只需要执行规定的非连接态终端设备需要执行的操作，比如测量、接收寻呼、系统消息等操作，不需要额外的接收业务数据。在R18中讨论网络在非连接态时，接收组播业务的背景下，终端设备如果被释放到非连接态接收组播业务，那么终端设备要一直用G-RNTI监听PDCCH以读取组播业务数据。在组播业务去激活的场景下，如果核心网设备向接入网设备触发了组播业务去激活流程，网络设备将停止发送数据很长的一段时间，但如果此时终端设备一直监听PDCCH也将造成大量不必要的能量消耗。因此，在网络在非连接态模式的场景下，提供组播业务，如果组播业务为去激活状态，则需要通知终端设备对应业务的状态，具体的参考的方式可以考虑以下方案：
方案一：对应上述方式一和二，网络设备将终端设备寻呼进连接态再进行释放，释放时，不指示非连接态组播。
在方案一中，终端设备不感知组播业务状态，终端设备根据网络指示是否在非连接态下接受组播业务实现去激活，已达到节电的目的。对方案一来说，终端设备进入连接态后马上被释放，会造成接入资源的浪费。其只是实现了终端设备不继续接收非连接态组播业务，当业务再次激活时，终端设备还需要寻呼进入连接态，再次获取组播业务的配置信息，这对于引入处于非连接态的终端设备，接收组播的初衷是为了缓解网络拥塞是相反的，该方案一反而需要终端设备频繁的接入。
方案二：对于上述方式一和二，网络设备在RRC release/连接态中/寻呼消息paging指示多播业务状态为激活态/去激活态。
在方案二中，网络设备在终端设备处于连接态时，就指示组播业务状态用于网络在RRC非连接态的情况下，判断是否接收数据。如果网络指示组播业务状态为去激活态，终端设备可以不监听数据。后续组播业务状态为激活态时，终端设备可以基于网络发送的寻呼消息判断是否是组播业务激活场景(或者是否需要进入连接态)。如果是对应的组播业务激活或者不需要进入连接态，则终端设备需要开始接收数据。终端设备接收数据的操作也需要划分不同的模式，基于现有讨论的场景有两类：第一类为RNA内所有的小区均可以提供给终端设备对应接收的业务，并且可以提供相同的配置；第二类为RNA内所有的小区不限制是否需要提供相同业务和相同的配置。
方案三：对应上述方式二，网络设备在MCCH中指示组播业务对应状态为激活态或者去激活态。
在方案三中，终端设备可以随时获取组播业务的状态。当终端设备读取到组播业务的状态为去激活，则终端设备不监听数据。当组播业务的状态为激活时，则终端数设备监听数据。此方案不受RNA是否提供相同的业务以及配置限制，终端设备都判断当前小区的信息，与其他小区的信息无关。
作为一种示例，当指示方式为显示指示时，举例来说：MCCH消息内容：TMGI 1、TMGI 2-去激活、TMGI 3，可以看出，在MCCH信息中直接指示业务TMGI 2的状态为去激活。
作为另一种示例，当指示方式为隐式指示时，举例来说:MCCH消息内容：TMGI 1、TMGI 2(释放时指示要接收，但因为去激活在MCCH中不体现)、TMGI 3，可以看TMGI 2在MCCH消息中不体现，即该业务的状态为去激活；MCCH消息内容：TMGI 1(包含全部配置)、TMGI 2(因为去激活，仅包含部分配置)、TMGI 3(包含全部配置)，可以看出，TMGI 2在MCCH中只包含部分配置，则该业务的状态为去激活。
基于上述将非连接态模式的组播业务的配置提供给终端设备的方式一的实现中，如图4终端设备切换场景示意图所示，终端设备在第一小区接收到非连接态组播业务1，终端设备从第一小区移动到第二小区。
应理解，该第一小区为终端设备的源服务小区，第二小区为终端设备的目标服务小区。
还应理解，在方式一的实现中，终端设备从第一小区移动到第二小区的过程中，可能存在以下几种场景可能：
场景一：如果第二小区为第一小区的RNA外的小区，或者，第二小区与第一小区属于同一RNA，但不保证同一RNA为不同小区能够提供相同的业务，同时不确定第二小区是否为能够为终端设备提供业务。由于终端设备不确定目标服务小区是否提供了对应的业务，因此终端设备切换或重选至第二小 区后，终端设备进入连接态，并接收对应的组播业务或者对应业务的配置信息。
场景二：如果第二小区与第一小区属于同一RNA，且RAN为第一小区和第二小区提供相同的业务，但不确定RAN为第一小区和第二小区提供的配置是否相同。由于终端设备没有配置信息因此终端设备切换或重选至第二小区后，需要进入连接态，获取第二小区的第一组播业务(例如TMGI1)对应的配置信息。
场景三：如果第二小区与第一小区属于同一RNA，且RAN为第一小区和第二小区提供相同的业务以及相同的配置。终端设备从第一小区切换或重选至第二小区之后，不需要进入连接态，继续处于非连接态接收业务即可。
基于上述将非连接态模式的组播业务的配置提供给终端设备的方式二的实现中，如图5所示的终端设备切换示意图，终端设备在第一小区通过MCCH获取到想接收的TMGI 1的配置信息，再从第一小区移动到第二小区。
应理解，在方式二的实现中，终端设备从第一小区移动到第二小区的过程中，可能存在以下几种场景可能：
场景四：第二小区的MCCH中没有TMGI 1，或者第二小区没有MCCH。终端设备可以视为第二小区没有在非连接态下提供业务TMGI，因此终端设备需要进入连接态获取业务数据。
场景五：第二小区的MCCH中有TMGI 1，则终端设备从第一小区切换或重选至第二小区之后，无需进入连接态，保持非连接态即可。
根据上述场景可以看出，场景一、场景二和场景四中，终端设备从第一小区切换至或重选至第二小区，终端设备均需要进入连接态。基于现有的去激活流程可以看出，网络设备可以将去激活业务对应的终端设备释放RRC连接。上述场景中的业务TMGI 1如果是去激活的业务时，终端设备切换或重选至第二小区进入连接态之后，很有可能又会被释放到非连接态。这就导致终端设备切换或重选至目标服务小区，产生不必要的接入，造成资源的浪费。
本申请基于上述在场景一、场景二和场景四中发现的技术问题，本申请实施例提供了一种通信方法，解决如何避免在非连接态模式下接收组播业务的终端设备，从源服务小区切换或者重选至目标服务小区时不必要的接入。
其中，针对上述场景一、场景二和场景四，处于RRC非连接态的终端设备从第一小区切换或者重选至第二小区时，本申请实施例提供了如图6所示的一种通信方法的示意性图，该方法可以包括如下步骤：
S610，终端设备接收第一信息，该第一信息与第一组播业务的状态相关，和/或，第一信息与第二小区中第一组播业务的配置信息相关。
可选地，该第一组播业务的状态包括激活态，或者去激活态。
可选地，当第一信息与第二小区中第一组播业务的配置信息相关时，第一小区与第二小区为相邻小区，或者第二小区为RNA或跟踪区(tracking area，TA)内的小区，或者第二小区为特定区域内的小区。其中，第一信息可以为小区的信息列表，或者第一信息为信息的小区列表，其中包括第二小区的相关信息。
应理解，本申请中的第一组播业务的配置信息可以是多播业务配置信息、无线承载配置信息或者PTM配置信息，对此本申请不做限定。
其中，该第一信息也可能来自于第一小区和/或服务第一小区的网络设备(本申请中称为第一网络设备)。
应理解，第一网络设备是为第一小区提供服务的网络设备。
可选地，该第一信息携带在如下至少一项消息中：寻呼paging消息、系统信息块SIB、MCCH信息。
可选地，该第一信息还可以携带在RRC释放消息或者RRC重配消息中，对此本申请不做限定，该RRC释放消息是用于将终端设备释放到非连接态。
S620，终端设备根据第一信息，判断是否向第二小区发送第一请求信息，第一请求信息用于建立或恢复RRC连接。
具体地，当终端设备接收第一信息之后，终端设备根据第一信息判断是否向第二小区发送第一请 求信息。
可选地，当第一信息中的第一组播业务的状态为激活态时，终端设备向第二小区发送第一请求信息，第一请求信息用于终端设备请求建立或恢复RRC连接。
可选地，当第一信息中的第一组播业务的状态为去激活态时，终端设备保持非连接态。
可选地，当第一信息中的第一小区与第二小区中第一组播业务的配置信息不同时，终端设备向第二小区发送第一请求信息。
可选地，当第一信息中的第一小区与第二小区中第一组播业务的配置信息相同时，终端设备保持非连接态。
可选地，当第一信息中第一小区与第二小区中第一组播业务的配置信息相同，且第一组播业务的状态为激活态时，终端设备向第二小区发送第一请求信息。
可选地，当第一信息中第一小区与第二小区中第一组播业务的配置信息相同，且第一组播业务的状态为去激活态，终端设备保持非连接态。
应理解，在上述终端设备从第一小区切换或者重选至第二小区，继续保持非连接态的情况下，终端设备还可能接收第一寻呼消息，第一寻呼消息包括第一组播业务的标识，则终端设备确定第一组播业务激活，或者需要进入连接态。举例来说，终端设备根据该第一寻呼消息向第二小区发送第一请求信息，用于进入连接态。
根据图6所示的方法，该方法还可能包括：
终端设备接收第二信息，该第二信息用于确定第二小区未向非连接态的终端设备提供第一组播业务。
应理解，第二小区还可能直接指示终端设备该第二小区未向非连接态的终端设备提供第一组播业务，终端设备进一步地根据第二信息判断是否进入连接态。
还应理解，该终端设备接收第二信息可以在终端设备接收第一信息之前，或者，该终端设备接收第二信息还可以在终端设备接收第一信息之后，对此本申请不做限定。
可选地，当第二信息包括第二小区的MCCH的配置信息时，终端设备根据MCCH的配置信息，获取第三信息，第三信息包括第二小区的MCCH信息，且MCCH信息不包括第一组播业务的标识。终端设备确定该第二小区未向非连接态的终端设备提供第一组播业务。
可选地，当第二信息包括第二小区的MCCH的配置信息时，终端设备根据MCCH的配置信息，未获取到第三信息，则表明该第二小区中MCCH信息为空的，或者不存在MCCH信息。
终端设备确定该第二小区支持非连接态的组播业务为零。
应理解，本申请中的MCCH/MCCH的配置信息是用于组播传输的。
需要说明的是，上述第一信息还可以包括第一小区的PDCP同步信息和/或第二小区的PDCP同步信息，同步信息包括该第一小区的PDCP和/或第二小区的PDCP同步或者不同步。
应理解，本申请中的PDCP同步是指第一小区或者第二小区对应的网络设备(例如基站)使用核心网发送的数据包中的编号生成PDCP编号。不同步是指第一小区或者第二小区对应的网络设备(例如基站)没有使用核心网发送的数据包的编号生成PDCP编号。其中核心网发送的数据包中的编号可以是MBS QFI SN。
其中，当第一信息包括的第一小区的PDCP不同步和/或第二小区的PDCP不同步时，终端设备重建PDCP实体或者重置/初始化PDCP变量，和/或，终端设备对缓存的PDCP数据包进行丢弃或者递交高层，和/或，终端设备向第一小区和/或第二小区发送第一请求信息，用于建立或者恢复RRC连接，终端设备进入连接态之后，在第一小区和/或第二小区接收PDCP的配置。
应理解，当终端设备从第一小区切换或者重选至第二小区时，可能存在第二小区不采用PDCP同步机制，终端设备切换或者重选至第二小区时，需要进一步地确定PDCP层处理机制是否可以连续，第一信息还用于指示第二小区的PDCP的同步信息，进一步地用于终端设备判断对PDCP层或者PDCP实体的处理。
上述图6所示的方法中，处于RRC非连接态的终端设备从第一小区切换或者重选到第二小区时，终端设备通过接收第一信息，并根据该第一信息判断是否需要向第二小区发送第一请求信息用于请求进入连接态。其中，该第一信息与第一组播业务的状态和/或第二小区的配置相关，终端设备进一步地 判断是否继续保持非连接态，或者向第二小区发送第一请求信息。从而避免了终端设备从第一小区切换或者重传至第二小区，终端设备直接向第二小区发送第一请求信息，用于请求建立或者恢复RRC连接态。本申请中终端设备需要根据接收的第一信息和第一条件进行判断，是否向第二小区发送第一请求信息，避免了终端设备向第二小区发起请求，并进入连接态之后，又会被很快释放为非连接态的问题，降低了资源的消耗。
接下来，详细介绍，在上述场景一和场景二的情况下，当第一信息与第一组播业务的状态相关时，终端设备根据第一信息，判断是否向第二小区发送第一请求信息的具体方法。如图7示出了本申请实施例提供的另一种通信方法的示意图，该方法包括如下步骤：
S710，终端设备接收来自第一小区的第一信息。
相应地，第一小区向终端设备发送该第一信息。
具体地，处于非连接态的终端设备从第一小区切换或者重选至第二小区时，终端设备接收来自第一小区的第一信息，该第一信息用于指示该第一组播业务的状态。其中，该第一组播业务为终端设备设备在第一小区时的非连接态接收的组播业务，其中，该第一组播业务的状态包括激活态，或者非激活态。
其中，该第一小区为终端设备的源服务小区，第二小区为终端设备切换或者重选的目标服务小区。
可选地，终端设备通过寻呼paging消息、系统信息块SIB、MCCH消息获取该第一信息。
可选地，终端设备通过RRC释放信息或者进入连接态获取该第一信息。
终端设备根据第一信息，判断是否向第二小区发送第一请求信息。其中，具体判断依据根据第一组播业务的状态为激活态或者去激活态。具体情况如下：
情况一：第一信息中第一组播业务的状态为激活态的情况
如图7所示的方法，该方法还包括：
S720，终端设备根据第一信息，向第二小区发送第一请求信息。
相应地，第二小区接收来自终端设备的第一请求信息。
其中，该第一组播业务的状态为激活态，终端设备向第二小区发送第一请求信息。
具体地，终端设备接收到来自第一小区的第一组播业务，该第一组播业务的状态可能为激活态或者非激活态。其中，当第一组播业务的状态为激活态时，终端设备从第一小区切换或者重选至第二小区，该终端设备向第二小区发送第一请求信息。
举例来说，终端设备发起RRC恢复/建立流程进入连接态。基于上述场景一和场景二，第二小区只在连接态的情况下提供第一组播业务，或者该第二小区尚未提供第一组播业务，需要进入连接态之后触发该业务的建立。
在上述场景一和场景二中，当终端设备不确定第二小区是都提供对应的组播业务和/或相同的配置时，终端设备直接根据第一组播业务的状态判断是否向第二小区发送第一请求信息用于建立/恢复RRC连接。
情况二：第一信息中第一组播业务的状态为去激活态的情况
如图7所示的方法，该方法还包括：
S720’，终端设备根据第一信息，确定保持非连接态。
具体地，终端设备接收到来自第一小区的第一信息，该第一信息指示第一组播业务的状态为激活态或者非激活态。其中，当第一组播业务的状态为去激活态时，终端设备从第一小区切换或者重选至二小区，该终端设备继续保持非连接态。
举例来说，终端设备不发起RRC恢复/建立流程，避免进入连接态之后又被释放。终端设备保持非连接态，等待后续的激活流程发起寻呼请求，如图7所示的方法，该方法还包括：
S730’，终端设备接收第一寻呼消息。
其中，当终端设备接收到第一寻呼消息时，终端设备根据第一寻呼消息判断是否进入连接态。当该第一寻呼消息是针对业务激活的寻呼，则终端设备不向第二小区发送第一请求信息；当该第一寻呼消息包括第一组播业务的标识时，则终端设备确定第一组播业务激活，或者需要进入连接态。举例来说，终端设备根据该第一寻呼消息向第二小区发送第一请求信息，用于进入连接态。
具体地，当后续寻呼达到终端设备后，终端设备由于不确定第二小区和第一小区是否具有相同的 第一组播业务的配置信息，终端设备需要发起RRC恢复/建立流程进入连接态，并获取第二小区的第一组播业务的配置信息。当终端设备确定第二小区的第一组播业务的配置信息与第一小区的第一组播业务的配置信息相同时，终端设备执行如图8所示的方法，具体请参见图8中的详细介绍，此处不再赘述。
应理解，当终端设备在第一小区处于非连接态时，接收的业务中可以包括多个业务，该多个业务存在激活态的业务时，终端设备需要向第二小区发送第一请求信息，用于恢复或者建立RRC连接，如图7所示的方法，该方法还包括：
S740’，终端设备向第二小区发送第一请求信息。
相应地，第二小区接收来自终端设备的第一请求信息。
其中，该第一请求信息用于建立或者恢复RRC连接。
上述图7所示的方法中，处于非连接态的终端设备从第一小区切换或者重选到第二小区时，无需根据第二小区是否与第二小区属于同一RAN，和/或，第二小区是否与第一小区支持的业务是否相同，和/或，第二小区与第一小区对应业务的配置信息是否相同，判断是否需要进入连接态，终端设备直接基于第一信息中的第一组播业务的状态判断是否向第二小区发送第一请求信息。其中，当第一组播业务的状态为激活态时，终端设备向第二小区发送第一请求信息；当第一组播业务的状态为非激活态时，终端设备保持非连接态，并等待寻呼唤醒，再向第二小区发送第一请求信息。图7所示的方法，避免了终端设备根据第一小区和第二小区是否属于同一RAN，和/或，支持的业务是否相同，和/或，对应业务的配置信息是否相同，确定在第二小区进入连接态之后，又会被很快释放为非连接态的问题，降低了资源的消耗。
其中，针对上述场景四，图8是本申请实施例提供的另一种通信方法的示意图，如图8所示，该方法可以包括如下步骤：
S810，终端设备接收第一信息。
该第一信息来自第一小区。其中，第一信息包括第一组播业务的状态。
该步骤S810与上述图7中所示的步骤S710类似，详情请参见上述S710中的描述，此处不在赘述。
终端设备还可能接收来自第二小区的第二信息，该第二信息用于指示该第二小区未向非连接态的终端设备提供所述第一组播业务。
应理解，该第二信息可以直接用于指示该第二小区未向非连接态的终端设备提供第一组播业务，或者，该第二信息可以间接地指示该第二小区未提供非连接态的第一组播业务(即第二小区支持非连接态的组播业务，但是支持的非连接态的组播业务中不包括该第一组播业务)。举例来说，该第二消息中不包括该第二信息中不包括MCCH的相关信息(例如：MCCH的配置信息)，即该第二信息指示了该第二小区未向非连接态的终端设备提供第一组播业务；该第二信息中包括第二小区的MCCH的配置信息，第一小区根据MCCH配置信息获取到第三信息，第三信息包括第二小区的MCCH信息，且第二小区的MCCH信息不包括第一组播业务的标识，即第二小区未提供非连接态的第一组播业务；该第二信息中包括第二小区的MCCH的配置信息，第一小区根据MCCH配置信息未能获取到第三信息，则认为该第二小区未向非连接态的终端设备提供第一组播业务。
根据上述第二信息的可能情况，接下来分别基于上述第二信息直接指示第二小区未向非连接态的终端设备提供第一组播业务、第二信息可以间接指示第二小区未提供非连接态的第一组播业务情况，进行详细地介绍：
情况一：
S820，终端设备接收来自第二小区的第二信息。
相应地，第二小区向终端设备发送该第二信息。
其中，该第二信息用于指示该第二小区未向非连接态的终端设备提供所述第一组播业务。
可选地，该第二信息可以直接用于指示该第二小区未向非连接态的终端设备提供第一组播业务，或者，该第二信息可以指示该第二小区未提供非连接态的第一组播业务。
S830，终端设备根据第二信息，确定第二小区未向非连接态的终端设备提供第一组播业务。
具体地，终端设备接收到来自第二小区的第二信息之后，并根据该第二信息确定第二小区未提供 非连接态的第一组播业务。如图8所示的方法，该方法还包括：
S840，终端设备根据第一信息，判断是否向第二小区发送第一请求信息。
具体地，终端设备确定第二小区未向非连接态的终端设备提供第一组播业务时，终端设备根据第一信息，判断是否向第二小区发送第一请求信息，该第一请求信息用于建立或者恢复RRC连接。
应理解，步骤S840中终端设备根据第一信息，判断是否向第二小区发送第一请求信息，具体可以参见上述图7中所示的情况一和情况二的详细描述，为了避免冗余，此处不再赘述。
情况二：
S820’，终端设备接收来自第二小区的第二信息。
相应地，第二小区向终端设备发送该第二信息。
其中，该第二信息用于指示该第二小区未向非连接态的终端设备提供所述第一组播业务。
可选地，该第二信息中包括第二小区的MCCH的配置信息。
S830’，终端设备向第二小区发送第二请求信息。
具体地，当终端设备接收到第二小区的第二信息，该第二信息包括第二小区的MCCH的配置信息时，该终端设备向第二小区发送第二请求信息，该第二请求信息用于根据MCCH的配置信息获取第二小区的MCCH信息。
可选地，当第二小区中包括MCCH信息，即如图8所示的方法，该方法还包括：
S840’，终端设备接收来自第二小区的第三信息，或者说，第二小区向终端设备发送第三信息。
具体地，当第二小区接收到来自终端设备的第二请求信息时，第二小区根据第二请求信息向终端设备发送该第三信息。该第三信息包括第二小区的MCCH信息。
可选地，当第三信息中的MCCH信息中不包括第一组播业务的标识时，则终端设备确定该第二小区未向非连接态的终端设备提供第一组播业务。
S850’，终端设备根据第三信息，确定第二小区未向非连接态的终端设备提供第一组播业务。
应理解，终端设备向第二小区发送第二请求信息，终端设备可能未接收到该第三信息，即第二小区的MCCH信息为空或者没有MCCH信息，即该步骤S840’，步骤850’为可选地。
S860’，终端设备根据第一信息，判断是否向第二小区发送第一请求信息。
具体地，终端设备确定第二小区未向非连接态的终端设备提供第一组播业务时，终端设备根据第一信息判断是否向第二小区发送第一请求信息，该第一请求信息用于建立或者恢复RRC连接。
应理解，步骤S860’中终端设备根据第一信息，判断是否向第二小区发送第一请求信息，具体可以参见上述图7中所示的情况一和情况二的详细描述，为了避免冗余，此处不再赘述。
需要说明的是，图8中所示的步骤S820，S820’，不限定在步骤S810之后。该步骤S820，S820’也可能在S810之前，对此本申请不做限定。
上述图8所示的方法，处于非连接态的终端设备从第一小区切换或者重传到第二小区时，终端设备接收来自第二小区的第二信息，该第二信息用于确定该第二小区未向非连接态的终端设备提供所述第一组播业务。终端设备根据第一组播业务的状态判断是否向第二小区发送第一请求信息。其中，当终端设备接收的第二信息中，包括第二小区的MCCH配置信息时，终端设备基于MCCH配置信息获取到第二小区的MCCH的业务信息。终端设备根据业务信息进一步地确定该第二小区是否支持无连接态的第一组播业务。当终端设备确定第二小区未向非连接态的终端设备提供第一组播业务，或者，该第二小区未提供非连接态的组播时，终端设备根据第一组播业务的状态，向第二小区发送第一请求信息，用于建立或者恢复RRC连接，或者终端设备等待寻呼唤醒。
图9示出了本申请实施例提供的另一种通信方法的示意性流程图，适用于上述场景一至场景五中任意一个场景，当第一信息与第二小区中第一组播业务的配置信息相关，终端设备根据第一信息，判断是否向第二小区发送第一请求信息的具体方法。如图9所示的方法，该方法包括：
S910，第一网络设备接收第二小区中第一组播业务的配置信息。
相应地，第二小区向第一网络设备发送该第二小区中第一组播业务的配置信息。
其中，第一网络设备与第二小区至今的信息交互，可以通过Xn接口进行交互。
具体地，第一网络设备根据该第二小区中第一组播业务的配置信息确定第一小区的配置信息与第二小区的配置相同或者不同。第一网络设备根据该第二小区中第一组播业务的配置信息确定第一信息， 并将该第一信息发送给终端设备，用于终端设备判断是否向第二小区发送第一请求信息。
其中，第一网络设备是为第一小区服务的网络设备，第一小区与第二小区为相邻小区，或者该第二小区是第一小区一定范围内的小区，或者第一小区与第二小区是同一RNA内的小区。
可选地，第二小区中第一组播业务的配置信息可以包括第二小区的PTM配置，该PTM配置可以包括G-RNTI，逻辑信道标识(logical channel ID，LCID)，不连续接收(discontinuous reception，DRX)，下行共享信道(physical downlink shared channel，PDSCH)配置等信息。
可选地，该第二小区中第一组播业务的配置信息包括以下一项或多项：第一组播业务标识信息(例如TMGI1)，第二小区中第一组播业务的配置信息(该配置信息可以承载在无线承载配置信息、PTM配置信息、多播业务配置信息等信息中)，PDCP同步或者PDCP不同步。
可选地，第二小区中第一组播业务的配置信息中还可以包括第二小区采用同步机制生成的PDCP SN，或者第二小区不采用同步机制。其中，当第一小区和/或第二小区的PDCP不同步时，终端设备按照现有的PDCP机制，会导致处理异常(例如，丢包、数据包错乱等)，该第一信息还可以将PDCP是否同步的情况通知给终端设备，用于终端设备判断对于PDCP层/PDCP实体的处理。
需要说明是的，在步骤S910之前，第一网络设备可以通过Xn接口向第二小区发送第三请求信息，该第三请求信息用于请求获取第二小区的配置，第三请求信息可以包括以下一项或多项：第一组播业务标识，第二小区标识，第二小区中第一组播业务的配置查询指示信息，PDCP同步查询指示信等。第二小区根据第三请求信息，向第一网络设备发送第二小区中第一组播业务的配置信息。
可选地，第二小区中第一组播业务的配置信息包括以下一项或多项：第一组播业务标识信息(例如TMGI1)，第二小区配置信息，PTM配置信息，PDCP同步或者PDCP不同步。其中，该PDCP同步或者不同步的情况可以是业务级别，或者小区级别，或者基站级别，对此本申请不做限定。
还需要说明的是，当第二小区与第一小区的服务网络设备均为第一网络设备时，则上述步骤S910为可选步骤。
S920，终端设备接收来自第一网络设备的第一信息。
相应地，第一网络设备向终端设备发送该第一信息。
具体地，处于非连接态的终端设备从第一小区切换或者重选至第二小区时，终端设备接收来自第一网络设备的第一信息，该第一信息与该第二小区中第一组播业务的配置信息相关。
终端设备根据第一信息，判断是否向第二小区发送第一请求信息。
可选地，当第一信息中第一小区与第二小区中第一组播业务的配置信息不同时，终端设备向第二小区发送第一请求信息；
可选地，当第一信息中第一小区与第二小区中第一组播业务的配置信息相同时，终端设备保持非连接态。具体情况如下：
情况一：第一信息中第一小区与第二小区中第一组播业务的配置信息不同的情况
如图9所示的方法，该方法还包括：
S930，终端设备根据第一信息，向第二小区发送第一请求信息。
相应地，第二小区接收来自终端设备的第一请求信息。
其中，该第一信息中第一小区与第二小区中第一组播业务的配置信息不同，终端设备向第二小区发送第一请求信息。
情况二：第一小区与第二小区中第一组播业务的配置信息相同的情况
如图9所示的方法，该方法还包括：
S930’，终端设备根据第一信息，确定保持非连接态。
具体地，终端设备接收到来自第一小区的第一信息，该第一信息中第一小区与第二小区中第一组播业务的配置信息相同。终端设备从第一小区切换或者重选至第二小区，该终端设备继续保持非连接态。
应理解，当第一信息与第一组播业务的状态和第二小区中第一组播业务的配置信息相关时，当第一信息中第一小区与第二小区中第一组播业务的配置信息相同，且第一组播业务的状态为去激活态，终端设备向第二小区发送第一请求信息。
还应理解，当第一信息中第一小区与第二小区中第一组播业务的配置信息相同，且第一组播业务 的状态为去激活态，终端设备保持非连接态。
S940’，终端设备接收第一寻呼消息。
其中，当终端设备接收到第一寻呼消息时，终端设备根据第一寻呼消息判断是否进入连接态。当该第一寻呼消息是针对业务激活的寻呼，则终端设备不向第二小区发送第一请求信息；当该第一寻呼消息包括第一组播业务的标识时，则终端设备确定第一组播业务激活，或者需要进入连接态。如图9所示的方法，该方法还包括：
S950’，终端设备向第二小区发送第一请求信息。
相应地，第二小区接收来自终端设备的第一请求信息。
其中，该第一请求信息用于建立或者恢复RRC连接。
上述图9所示的方法中，处于RRC非连接态的终端设备从第一小区切换或者重选到第二小区时，接收来自第一网络设备确定的第一信息。该第一信息与第二小区中第一组播业务的配置信息相关。终端设备根据第一信息，进一步地判断是否向第二小区发送第一请求信息。图9所示的方法，避免了终端设备根据第一小区和第二小区是否属于同一RAN，和/或，支持的业务是否相同，和/或，对应业务的配置信息是否相同，确定在第二小区进入连接态之后，又会被很快释放为非连接态的问题，降低了资源的消耗。
其中，上述图9所示的方法中，第一信息与第二小区中第一组播业务的配置信息相关，终端设备根据第一信息确定第一小区和第二小区中第一组播业务的配置信息相同或者不同，进一步地确定向第二小区发送第一请求信息，或者保持非连接态。
其中，当终端设备接收来自第一网络设备的第一信息为邻区信息时，终端设备根据该邻区信息进一步地确定是否向第二小区发送第一请求信息，如图10所示的方法，该方法包括：
S1010，第一网络设备接收第二小区中业务的配置信息。
相应地，第二小区向第一网络设备发送该第二小区中业务的配置信息。
其中，第一网络设备与第二小区之间的信息交互，可以通过Xn接口进行交互。
应理解，该业务的配置信息包括第二小区全部业务的配置信息，或者，该业务的配置信息包括第一组播业务的配置信息。
S1020，第一网络设备向终端设备发送邻区信息。
相应地，终端设备接收来自第一网络设备的邻区信息。
可选地，该邻区信息还可以携带在RRC释放消息中，该RRC释放消息是用于将终端设备释放到非连接态。
应理解，该第一网络设备向终端设备发送RRC释放消息，该RRC释放消息将终端设备释放到非连接态。其中，该邻区信息可以携带在该第一网络设备发送给终端设备的RRC释放消息中。
具体地，第一网络设备接收来自第二小区中业务的配置信息之后，并根据第二小区中业务的配置信息确定邻区信息。其中，该邻区信息中包括第二小区的全部业务的配置信息。
S1030，终端设备根据邻区信息，确定保持非连接态。
具体地，当终端设备接收来自第一网络设备的邻区信息，该邻区信息包括第二小区全部业务的配置信息时，或者，该邻区信息包括第二小区中关于第一组播业务的配置信息时，终端设备保持非连接态。
其中，当邻区信息中不包括第二小区的相关信息时，终端设备从第一小区切换或者重选至第二小区，终端设备需要向第二小区发送第一请求信息，用于进入连接态。
S1040，终端设备接收第一寻呼消息。
终端设备接收第一寻呼消息。
其中，当终端设备接收到第一寻呼消息时，终端设备根据第一寻呼消息判断是否进入连接态。当该第一寻呼消息包括第一组播业务的标识时，则终端设备确定第一组播业务激活，或者需要进入连接态。举例来说，终端设备根据该第一寻呼消息向第二小区发送第一请求信息，用于进入连接态。如图10所示的方法，该方法还包括：
S1050，终端设备向第二小区发送第一请求信息。
相应地，第二小区接收来自终端设备的第一请求信息。
其中，该第一请求信息用于建立或者恢复RRC连接。
上述图10所示的方法，当终端设备接收到来自第一网络设备的邻区信息，其中，该邻区信息包括第二小区中全部业务的配置信息，终端设备根据邻区信息确定保持非连接态。
需要说明的是，上述图10中所示的第一网络设备向终端设备发送的第一信息为邻区信息，该邻区信息不限定是小区范围内的邻区，本申请中的邻区信息包括第一网络设备能够获得所有小区的相关信息都可以称为邻区信息。所以，邻区信息只代表信息名称，但并不限定是第一小区的邻区的相关信息，只要第一网络设备能够获得的小区的相关信息，都可以称为邻区信息。本申请不做限定。
根据上述所示的方法，终端设备接收到来自第二小区的全部业务的配置信息或者第一组播业务的配置信息之后，终端设备保持非连接态。终端设备接收到包括第一组播业务标识的第一寻呼消息之后，终端设备向第二小区发送第一请求信息，该第一请求信息用于建立或者恢复RRC连接。
在终端设备根据接收第一网络设备的信息判断是否进入连接态时，第一小区和/或第二小区的PDCP窗口处理机制也可能存在异常，因此第一网络设备还可以将第一小区和/或第二小区的PDCP是否同步的情况通知给终端设备，用于终端设备判断对于PDCP层/PDCP实体的处理。如图11是本申请实施例提供的另一种通信方法的示意图。
如图11所示，该方法包括：
S1110，第一网络设备向第二小区发送第三请求信息。
相应地，第二小区接收来自第一网络设备的第三请求信息。
具体地，其中该第三请求信息用于获取第二小区的PDCP同步信息。
可选地，该第三请求信息包括以下一项或多项：第一组播业务标识，第二小区标识，PTM配置查询指示信息，PDCP同步查询指示信等。
S1120，第一网络设备接收来自第二小区中PDCP同步信息。
相应地，第二小区向第一网络设备发送该第二小区的PDCP同步信息。
具体地，第一网络设备向第二小区发送第三请求信息之后，第二小区向第一网络设备发送该第二小区的PDCP同步信息。
可选地，PDCP同步信息包括该第二小区的PDCP同步或者PDCP不同步。
其中，该PDCP同步或者不同步的情况可以是业务级别，或者小区级别，或者基站级别，对此本申请不做限定。
需要说明的是，该第一网络设备与第二小区之间的信息交互(例如，第三请求信息)可以通过Xn接口进行实现。
S1130，第一网络设备根据第二小区中第一组播业务的配置信息，确定第一信息。
具体地，第一网络设备接收到来自第二小区中第一组播业务的配置信息之后，并根据该第二小区中第一组播业务的配置信息确定第一信息。该第一信息可以称为邻区信息列表，或者称为其他信息，对此本申请不做限定。
可选地，该第一信息包括以下一项或多项：第二小区中第一组播业务的配置信息、第二小区的业务信息、第二小区的PDCP同步或者不同步。
其中，第一信息还可以包括各个业务的相关信息和公共信息，具体体现形式本申请不做限定。
S1140，第一网络设备向终端设备发送该第一信息。
相应地，终端设备接收来自第一网络设备的第一信息。
第一网络设备在向终端设备发送该第一信息的过程中，可以是在RRC释放消息中向终端设备发送该第一信息，或者，在MCCH消息中向终端设备发送该第一信息，或者，在SIB消息中向终端设备发送该第一信息。对此本申请不做限定。
S1150，终端设备根据第一信息，判断PDCP层的处理操作。
可选地，终端设备根据第一信息中第二小区的PDCP是否同步，判断是否初始化PDCP。当第二小区的PDCP不同步时，终端设备可以重置PDCP实体或者PDCP变量，和/或，清掉或者递交高层缓存中的数据包，和/或，终端设备向第二小区发送第一请求信息，该第一请求信息用于建立或者恢复RRC连接态，终端设备进入连接态之后，在第二小区接收PDCP的配置。
需要说明的是，图11中所示的方法，当第二小区与第一小区的网络设备为同一网络设备时，则 直接执行步骤S1130至S1150即可。
还需要说明的是，当第一小区的PDCP不同步时，也可以执行上述步骤S1130～步骤S1150。第一小区或者第二小区的PDCP不同步时，终端设备都可以通过重置PDCP实体或者PDCP变量，和/或，清掉或者递交高层缓存中的数据包，和/或，终端设备向第一小区和/或第二小区发送第一请求信息，该第一请求信息用于建立或者恢复RRC连接态，终端设备进入连接态之后，在第一小区和/或第二小区接收PDCP的配置。
上述图11所示的方法，提供了一种终端设备对PDCP层/PDCP实体的处理方法，终端设备可以根据第一信息中的第二小区的PDCP的同步信息，进一步地判断PDCP层的处理操作。
图12示出了本申请实施例适用的一种通信架构。图12示出了网络设备中的CP-UP的分离架构。该方法将网络设备以基站(例如gNB)为例，详细说明图12所示的额方法。其中，gNB可以由gNB-CU-CP、多个gNB-CU-UP和多个gNB-DU组成。其中gNB-CU-CP通过F1-C接口与gNB-DU相连；gNB-CU-UP通过F1-U接口与gNB-DU相连；gNB-CU-UP通过E1接口与gNB-CU-CP相连。
具体地，如图12可以看出，一个gNB-DU只连接一个gNB-CU-CP，一个gNB-CU-UP只连接一个gNB-CU-CP。在基站侧是CP-UP分离架构的情况下，如果需要交互MRB，基站的gNB-CU-CP需要从gNB-CU-UP检索MRB进度。
其中，在终端设备从源基站切换至目标基站的环境下，与单播业务不同的是源基站侧的MRB已经发送给终端设备的最后一个数据包是无法确定的。对于MRB来说F1-U建立的不一定是基于终端设备级别的，大概率是分布单元DU级或者小区cell级别的，因此gNB-CU-CP如何查询gNB-CU-UP的对于终端设备的进展是需要解决的问题。
应理解，从目标gNB的角度来看，目标gNB需要向MRB提供目标NG-RAN节点可用的最老数据包的PDCP SN信息，因此目标gNB-CU-UP只需要向源gNB-CU-UP提供目标gNB-CU-UP侧可用的最老数据包的SN，该最老数据包的SN包括每个MRB信息，不是终端设备的特定信息。因此可以直接查询源基站中的MRB的信息即可。
但是从源gNB-CU-CP的角度来看，对于某些终端设备需要检索MRB进度信息。其中包括已经为MRB下发到终端设备的最后一个数据包的PDCP SN信息。从目标基站gNB-CU-UP的角度来看，对于某些终端设备，数据包通过DU/Cell级别从F1-U隧道传输(其传输的进展代表多个终端设备的进展)，对于一些其他终端设备，数据包通过终端设备的级别F1-U隧道传输，因此，源gNB的MRB进度信息是终端设备的特定信息，因此，如何查询MRB的进度信息是需要解决的技术问题。
针对上述技术问题，如图13本申请实施例提供了另一种通信方法的示意图，接下来将结合图13中的方法，详细说明本申请针对上述技术问题提出的解决方案。
如图13所示的方法，该方法包括如下步骤：
S1310，源gNB-CU-CP向源gNB-CU-UP发送第三指示信息。
相应地，源gNB-CU-UP接收来自源gNB-CU-CP的第三指示信息。
其中，该第三指示信息用于确定终端设备对应的MRB进度信息。
可选地，第三指示信息包括MBS Multicast F1-U Context Descriptor信元。
可选的，该第三指示信息包括在MC context Modification Request消息中，该MC context Modification Request消息具体地可能包含以下一项或多项：gNB-CU-CP MBS E1AP ID，gNB-CU-UP MBS E1AP ID，组播承载上下文修改信息，MRB列表。
作为一种示例，源gNB-CU-CP为了检索到终端设备的MRB进度信息，需要向源gNB-CU-UP提供如下信息：
1.如果源gNB-CU-CP发送给终端设备的数据包是通过DU级别的F1-U共享隧道进行发送，则源gNB-CU-CP需要提供关于DU级别的F1-U共享隧道的信息。其中，该共享隧道的信息可以是显示的，也可以是隐式的。举例来说，可以是choice的一个分支直接用于指示该DU级别的F1-U共享隧道的信息，可以是DU的标识ID，也可以是源gNB-CU-CP MBS E1AP ID和源gNB-CU-UP MBS E1AP ID等。
2.如果源gNB-CU-CP传输到终端设备的数据包通过小区级别的F1-U共享隧道进行传递，源gNB-CU-CP需要提供小区信息。举例来说，可以是CGI或者CGI+DU-ID.
3.如果源gNB-CU-CP传输到终端设备的数据包是通过终端设备级别的F1隧道传递的，源gNB-CU-CP需要提供终端设备信息。举例来说，可以是C-RNTI+DU ID或gNB-CU UE F1AP ID+gNB-DU UE F1AP ID。
应理解，无论什么类型的tunnel都可以用MBS Multicast F1-U Context Descriptor进行体现。相应地，也可以理解为这个字段就是第三指示信息。
还应理解，在每一次建立F1隧道时，引入一个标识，该标识可以用于标识隧道信息，比如1号F1隧道，2号隧道等等，查询时可以不区分类别，直接携带相关的标识信息进行查询即可。
S1320，源gNB-CU-UP向源gNB-CU-CP发送进度响应信息。
相应地，源gNB-CU-CP接收来自源gNB-CU-UP的进度响应信息。
其中，该进度响应信息用于指示每个终端设备的MRB进度信息。该进度响应信息还可以是其他信息名称，对此本申请不做限定。
可选的，进度响应信息包括在MC context Modification Response消息中，所述MC context Modification Response消息还包含如下至少一项：gNB-CU-CP MBS E1AP ID，gNB-CU-UP MBS E1AP ID,组播承载上下文修改响应信息，MRB列表。
上述图13所示的方法中，源gNB-CU-CP向源gNB-CU-UP发送第三指示信息，该第三指示信息用于确定终端设备对应的MRB进度信息，源gNB-CU-UP向源gNB-CU-CP发送进度响应信息，该进度响应信息用于指示每个终端设备的MRB进度信息。源gNB-CU-CP通过上述图13所示的方法，能够确定每个终端设备对应的MRB的进展。
需要说明的是，上述图13中具体的MRB对应的进展还可以是MRB对应的不同级别的F1传输隧道中传输进展最慢的进展。例如，DU级别隧道反馈的进展到5号，终端设备级别的隧道反馈的进展是6号，由于源gNB-CU-UP不知道终端设备接收的是哪个隧道的数据，源gNB-CU-UP选择最慢的进展发送给源gNB-CU-CP。这种方式采取这种保守的MRB进展在源基站和目标基站之间做数据转发不会少转发数据包，基于终端设备在目标基站侧上报的PDCP状态报告确定目标基站向终端设备发送的数据包。虽然可能多转发了一部分数据包但是至少不会少传也不会出错误。
上面结合图6-图13详细介绍了本申请实施例提供的一种通信方法，下面结合图14-图15详细介绍本申请实施例提供的通信装置。
以下，结合图14和图15详细说明本申请实施例提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，部分内容不再赘述。
本申请实施例可以根据上述方法示例对发射端设备或者接收端设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。下面以采用对应各个功能划分各个功能模块为例进行说明。
图14是本申请提供的信息传输设备1400的一例示意性框图。上述图6至图13中任一方法所涉及的任一设备，如终端设备和网络设备等都可以由图14所示的通信设备来实现。
应理解，信息传输设备1400可以是实体设备，也可以是实体设备的部件(例如，集成电路，芯片等等)，还可以是实体设备中的功能模块。
如图14所示，该通信设备1400包括：一个或多个处理器1413。可选地，处理器1413中可以调用接口实现接收和发送功能。所述接口可以是逻辑接口或物理接口，对此不作限定。例如，接口可以是收发电路，输入输出接口，或是接口电路。用于实现接收和发送功能的收发电路、输入输出接口或接口电路可以是分开的，也可以集成在一起。上述收发电路或接口电路可以用于代码/数据的读写，或者，上述收发电路或接口电路可以用于信号的传输或传递。
可选地，接口可以通过收发器实现。可选地，该信息传输设备1400还可以包括收发器1430。所述收发器1430还可以称为收发单元、收发机、收发电路等，用于实现收发功能。
可选地，该通信设备1400还可以包括存储器1420。本申请实施例对存储器1420的具体部署位置不作具体限定，该存储器可以集成于处理器中，也可以是独立于处理器之外。对于该设备1400不包括 存储器的情形，该设备1400具备处理功能即可，存储器可以部署在其他位置(如，云系统)。
处理器1410、存储器1420和收发器1430之间通过内部连接通路互相通信，传递控制和/或数据信号。
可以理解的是，尽管并未示出，设备1400还可以包括其他装置，例如输入装置、输出装置、电池等。
可选地，在一些实施例中，存储器1420可以存储用于执行本申请实施例的方法的执行指令。处理器1410可以执行存储器1420中存储的指令结合其他硬件(例如收发器1430)完成下文所示方法执行的步骤，具体工作过程和有益效果可以参见上文方法实施例中的描述。
本申请实施例揭示的方法可以应用于处理器1410中，或者由处理器1410实现。处理器1410可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存取存储器(random access memory，RAM)、闪存、只读存储器(read-only memory，ROM)、可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的指令，结合其硬件完成上述方法的步骤。
可以理解，存储器1420可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器ROM、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器RAM，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图15是本申请提供的一种通信装置1500的示意性框图。该装置1500包括收发单元1520，收发单元1520可以用于实现相应的通信功能。收发单元1520还可以称为通信接口或通信单元。
可选地，该装置1500还可以包括处理单元1510，处理单元1510可以用于进行数据处理。
可选地，该用于信息传输的装置1500的具体形态可以是通用计算机设备或通用计算机设备中的芯片，本申请实施例对此不作限定。如图15所示，该装置包括处理单元1510和收发单元1520。
具体而言，装置1500可以是本申请涉及的任一设备，并且可以实现该设备所能实现的功能。应理解，该装置1500可以是实体设备，也可以是实体设备的部件(例如，集成电路，芯片等等)，还可以是实体设备中的功能模块。
在一种可能的设计中，该装置1500可以是上文方法实施例中的终端设备(如，终端设备)，也可以是用于实现上文方法实施例中终端设备(如，终端设备)的功能的芯片。
可选地，该装置1500还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1510可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中不同的终端设备的动作，例如，控制网元或终端设备的动作。
该装置1500可以用于执行上文各个方法实施例中控制网元或终端设备所执行的动作，这时，该装置1500可以为控制网元或终端设备，或者控制网元或终端设备的组成部件，收发单元1520用于执行上文方法实施例中控制网元或终端设备的收发相关的操作，处理单元1510用于执行上文方法实施例中控制网元或终端设备的处理相关的操作。
应理解，该装置1500可以用于执行上文各个方法实施例中控制网元或网络设备所执行的动作，这 时，该装置1500中的收发单元1520可通过通信接口(如收发器或输入/输出接口)实现，例如可对应于图14中示出的通信接口1430，该装置1500中的处理单元1510可通过至少一个处理器实现，例如可对应于图14中示出的处理器1410。
可选地，装置1500还可以包括存储单元，该存储单元可以用于存储指令或者数据，处理单元可以调用该存储单元中存储的指令或者数据，以实现相应的操作。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
应理解，各单元执行上述相应步骤的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
另外，在本申请中，通信装置1500是以功能模块的形式来呈现。这里的“模块”可以指特定应用集成电路ASIC、电路、执行一个或多个软件或固件程序的处理器和存储器、集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到装置1500可以采用图15所示的形式。处理单元1510可以通过图14所示的处理器1410来实现。可选地，如果图14所示的计算机设备包括存储器1400，处理单元1510可以通过处理器1415和存储器1400来实现。收发单元1520可以通过图14所示的收发器1430来实现。所述收发器1430包括接收功能和发送功能。具体的，处理器通过执行存储器中存储的计算机程序来实现。可选地，当所述装置1500是芯片时，那么收发单元1520的功能和/或实现过程还可以通过管脚或电路等来实现。可选地，所述存储器可以为所述芯片内的存储单元，比如寄存器、缓存等，所述存储单元还可以是装置内的位于所述芯片外部的存储单元，如图14所的存储器1420，或者，也可以是部署在其他系统或设备中的存储单元，不在所述计算机设备内。
本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。例如，计算机可读介质可以包括，但不限于:磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(compact disc，CD)、数字通用盘(digital versatile disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(erasable programmable read-only memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，能够存储、包含和/或承载指令和/或数据的各种其它介质。
根据本申请实施例提供的方法，本申请还提供一种计算机程序产品，该计算机程序产品包括：计算机程序或一组指令，当该计算机程序或一组指令在计算机上运行时，使得该计算机执行图5至图8所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种计算机可读存储介质，该计算机可读介质存储有程序或一组指令，当该程序或一组指令在计算机上运行时，使得该计算机执行图5至图8所示实施例中任意一个实施例的方法。
根据本申请实施例提供的方法，本申请还提供一种通信系统，其包括前述的装置或设备。
在本说明书中使用的术语“部件”、“模块”、“系统”等用于表示计算机相关的实体、硬件、固件、硬件和软件的组合、软件、或执行中的软件。例如，部件可以是但不限于，在处理器上运行的进程、处理器、对象、可执行文件、执行线程、程序和/或计算机。通过图示，在计算设备上运行的应用和计算设备都可以是部件。一个或多个部件可驻留在进程和/或执行线程中，部件可位于一个计算机上和/或分布在两个或更多个计算机之间。此外，这些部件可从在上面存储有各种数据结构的各种计算机可读介质执行。部件可根据具有一个或多个数据分组(例如来自与本地系统、分布式系统和/或网络间的另一部件交互的二个部件的数据，例如通过信号与其它系统交互的互联网)的信号通过本地和/或远程进程来通信。
还应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
还应理解，本申请实施例中引入编号“第一”、“第二”等只是为了区分不同的对象，比如，区分不同的“信息”，或，“设备”，或，“单元”，对具体对象以及不同对象间的对应关系的理解应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤， 能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (26)

  1. 一种通信方法，其特征在于，包括：
    终端设备接收第一信息，所述第一信息与第一组播业务的状态相关，和/或，所述第一信息与第二小区中所述第一组播业务的配置信息相关；
    所述终端设备根据所述第一信息，判断是否向所述第二小区发送第一请求信息，所述第一请求信息用于所述终端设备建立或恢复RRC连接，
    其中，所述终端设备为接收所述第一组播业务的终端设备，所述终端设备为处于无线资源控制RRC非连接态的终端设备，且所述终端设备是从所述第一小区切换或者重选至所述第二小区的终端设备。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备根据所述第一信息，判断是否向所述第二小区发送第一请求信息，包括：
    当所述第一组播业务的状态为激活态时，所述终端设备向所述第二小区发送所述第一请求信息，
    或者，
    当所述第一组播业务的状态为非激活态时，所述终端设备保持所述非连接态。
  3. 根据权利要求1所述的方法，其特征在于，所述终端设备根据所述第一信息，判断是否向所述第二小区发送第一请求信息，包括：
    当所述第一小区与所述第二小区的所述配置信息不同时，所述终端设备向第二小区发送所述第一请求信息，
    或者，
    当所述第一小区与所述第二小区的所述配置信息相同时，所述终端设备保持所述非连接态。
  4. 根据权利要求1所述的方法，其特征在于，所述终端设备根据所述第一信息，判断是否向所述第二小区发送第一请求信息，包括：
    当所述第一小区与所述第二小区的所述配置信息相同，且所述第一组播业务的状态为激活态时，所述终端设备向所述第二小区发送所述第一请求信息，
    或者，
    当所述第一小区与所述第二小区的所述配置信息相同，且所述第一组播业务的状态为去激活态时，所述终端设备保持所述非连接态。
  5. 根据权利要求2至4中任一项所述的方法，其特征在于，在所述终端设备保持所述非连接态的情况下，所述方法还包括：
    所述终端设备接收第一寻呼消息，所述第一寻呼消息包括所述第一组播业务的标识。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述终端设备接收第二信息，所述第二信息用于确定所述第二小区未向所述非连接态的终端设备提供所述第一组播业务。
  7. 根据权利要求6所述的方法，其特征在于，当所述第二信息包括所述第二小区的多播控制信道MCCH的配置信息时，所述方法还包括：
    所述终端设备根据所述MCCH的配置信息，获取第三信息，所述第三信息包括所述第二小区的MCCH信息，且所述MCCH信息不包括所述第一组播业务的标识，
    或者，
    所述终端设备根据所述MCCH的配置信息，未获取到所述第三信息。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述第一信息携带在如下至少一项消息中：
    寻呼paging消息、系统信息块SIB、MCCH信息。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，在所述第一信息与所述第二小区中所述第一组播业务的配置信息相关的情况下，所述第一信息包括所述第二小区的PDCP同步信息和/或所述第一小区的PDCP同步信息，所述同步信息包括所述PDCP同步或者不同步。
  10. 根据权利要求9所述的方法，其特征在于，当所述同步信息包括的所述第二小区的PDCP不 同步和/或所述第一小区的PDCP不同步时，所述方法还包括：
    所述终端设备重置所述PDCP实体或者所述PDCP变量，
    和/或，
    所述终端设备对缓存的PDCP数据包进行丢弃或者递交高层。
  11. 一种通信方法，其特征在于，包括：
    第一小区确定第一信息，所述第一信息与第一组播业务的状态相关；
    所述第一小区向所述终端设备发送所述第一信息，所述第一信息用于判断所述终端设备是否向第二小区发送第一请求信息，所述第一请求信息用于所述终端设备建立或恢复RRC连接，
    其中，所述终端设备为接收所述第一组播业务的终端设备，所述终端设备为处于无线资源控制RRC非连接态的终端设备，且所述终端设备是从所述第一小区切换或者重选至所述第二小区的终端设备。
  12. 根据权利要求11所述的方法，其特征在于，所述第一组播业务的状态包括激活态，或者去激活态。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    所述第一小区向所述终端设备发送第二信息，所述第二信息用于确定所述第二小区未向所述非连接态的终端设备提供所述第一组播业务。
  14. 根据权利要求11至13中任一项所述的方法，其特征在于，所述第一信息携带在如下至少一项消息中：
    寻呼paging消息、系统信息块SIB、MCCH信息。
  15. 一种通信方法，其特征在于，包括：
    第二小区确定第二信息，所述第二信息用于确定所述第二小区未向非连接态的终端设备提供第一组播业务；
    所述第二小区向所述终端设备发送所述第二信息，
    其中，所述终端设备为接收所述第一组播业务的终端设备，所述终端设备为处于无线资源控制RRC非连接态的终端设备，且所述终端设备是从所述第一小区切换或者重选至所述第二小区的终端设备。
  16. 根据权利要求15所述的方法，其特征在于，当所述第二信息包括所述第二小区的多播控制信道MCCH的配置信息时，所述方法还包括：
    所述第二小区向所述终端设备发送第三信息，所述第三信息包括所述第二小区的MCCH信息，且所述MCCH信息不包括所述第一组播业务的标识。
  17. 根据权利要求15或16所述的方法，其特征在于，所述方法还包括：
    所述第二小区向第一网络设备发送所述第二小区中所述第一组播业务的配置信息，所述配置信息用于确定第一信息，所述第一信息用于判断所述终端设备是否向第二小区发送第一请求信息，所述第一请求信息用于所述终端设备建立或恢复RRC连接，
    其中，所述第一小区与所述第二小区为相邻小区，所述第一网络设备是为所述第一小区提供服务的网络设备。
  18. 根据权利要求15至17中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二小区向所述第一网络设备发送所述第二小区的PDCP同步信息，所述同步信息包括所述PDCP同步或者不同步。
  19. 一种通信方法，其特征在于，包括：
    第一网络设备确定第一信息，所述第一信息与第二小区中第一组播业务的配置信息相关；
    所述第一网络设备向所述终端设备发送所述第一信息，所述第一信息用于判断所述终端设备是否向第二小区发送第一请求信息，所述第一请求信息用于所述终端设备建立或恢复RRC连接，
    其中，所述终端设备为接收所述第一组播业务的终端设备，所述终端设备为处于无线资源控制RRC非连接态的终端设备，且所述终端设备是从第一小区切换或者重选至所述第二小区的终端设备，所述第一网络设备是为所述第一小区提供服务的网络设备。
  20. 根据权利要求19所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自所述第二小区中所述第一组播业务的配置信息，所述配置信息用于确定所述第一信息。
  21. 根据权利要求19或20所述的方法，其特征在于，所述第一信息包括所述第二小区的PDCP同步信息，所述同步信息包括所述PDCP同步或者不同步。
  22. 根据权利要求19至21中任一项所述的方法，其特征在于，所述第一信息携带在如下至少一项消息中：
    寻呼paging消息、系统信息块SIB、MCCH信息。
  23. 一种通信装置，其特征在于，包括至少一个处理器，所述至少一个处理器与至少一个存储器耦合，所述至少一个处理器用于执行所述至少一个存储器中存储的计算机程序或指令，以使所述通信装置执行如权利要求1至10中任一项所述的方法，或者，以使所述通信装置执行如权利要求11至14中任一项所述的方法，或者，以使所述通信装置执行如权利要求15至18中任一项所述的方法，或者，以使所述通信装置执行如权利要求19至22中任一项所述的方法。
  24. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述计算机指令在计算机上运行时，使得所述计算机执行如权利要求1至10中任一项所述的方法，或者，以使所述计算机执行如权利要求11至14中任一项所述的方法，或者，以使所述计算机执行如权利要求15至18中任一项所述的方法，或者，以使所述计算机执行如权利要求19至22中任一项所述的方法。
  25. 一种芯片，其特征在于，包括：
    存储器，用于存储计算机程序；
    处理器，用于读取并执行所述存储器中存储的所述计算机程序，当所述计算机程序被执行时，所述处理器执行如权利要求1至10中任一项所述的方法，或者，以使所述处理器执行如权利要求11至14中任一项所述的方法，或者，以使所述处理器执行如权利要求15至18中任一项所述的方法，或者，以使所述处理器执行如权利要求19至22中任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，所述计算机程序产品包括计算机程序代码，当所述计算机程序代码在计算机上执行时，使得计算机执行如权利要求1至10中任一项所述的方法，或者，以使所述计算机执行如权利要求11至14中任一项所述的方法，或者，以使所述计算机执行如权利要求15至18中任一项所述的方法，或者，以使所述计算机执行如权利要求19至22中任一项所述的方法。
PCT/CN2023/103974 2022-08-05 2023-06-29 通信方法和通信装置 WO2024027403A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210939716.2A CN117560733A (zh) 2022-08-05 2022-08-05 通信方法和通信装置
CN202210939716.2 2022-08-05

Publications (1)

Publication Number Publication Date
WO2024027403A1 true WO2024027403A1 (zh) 2024-02-08

Family

ID=89821047

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/103974 WO2024027403A1 (zh) 2022-08-05 2023-06-29 通信方法和通信装置

Country Status (2)

Country Link
CN (1) CN117560733A (zh)
WO (1) WO2024027403A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102932744A (zh) * 2011-08-12 2013-02-13 华为技术有限公司 一种重选或切换到广播组播小区的方法、基站和系统
WO2022006746A1 (zh) * 2020-07-07 2022-01-13 Oppo广东移动通信有限公司 接收本地mbs业务的方法及装置、终端设备、网络设备
CN114390440A (zh) * 2020-10-16 2022-04-22 维沃移动通信有限公司 业务处理方法、装置及相关设备
US20220132467A1 (en) * 2020-10-22 2022-04-28 Samsung Electronics Co., Ltd. Method and system for handling service notification and configuration for mbs in 5g communication network
CN116017311A (zh) * 2021-10-22 2023-04-25 华为技术有限公司 一种通信方法、装置和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102932744A (zh) * 2011-08-12 2013-02-13 华为技术有限公司 一种重选或切换到广播组播小区的方法、基站和系统
WO2022006746A1 (zh) * 2020-07-07 2022-01-13 Oppo广东移动通信有限公司 接收本地mbs业务的方法及装置、终端设备、网络设备
CN114390440A (zh) * 2020-10-16 2022-04-22 维沃移动通信有限公司 业务处理方法、装置及相关设备
US20220132467A1 (en) * 2020-10-22 2022-04-28 Samsung Electronics Co., Ltd. Method and system for handling service notification and configuration for mbs in 5g communication network
CN116017311A (zh) * 2021-10-22 2023-04-25 华为技术有限公司 一种通信方法、装置和存储介质

Also Published As

Publication number Publication date
CN117560733A (zh) 2024-02-13

Similar Documents

Publication Publication Date Title
US11395256B2 (en) Communication method, device, and system
WO2021164564A1 (zh) 传输组播业务的方法和装置
JP4877841B2 (ja) 移動通信システムにおける方法及び通信装置
WO2022001495A1 (zh) 状态转换方法及链接态mtch的指示方法、装置、存储介质、终端、基站
CN116602003A (zh) 多播-广播服务移动性和服务连续性
WO2021051321A1 (zh) 一种业务数据传输方法及装置、终端设备
WO2021051320A1 (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2022007484A1 (zh) 重定向方法、网络设备、终端设备及可读存储介质
JP2023533342A (ja) 通信方法及び通信装置
US20240206010A1 (en) Service data transmission method and communication apparatus
WO2023000334A1 (zh) Pdcch监听方法、装置、设备及存储介质
WO2022141255A1 (zh) 一种mbs业务的配置方法及装置、网络设备、终端设备
WO2024027403A1 (zh) 通信方法和通信装置
WO2022037441A1 (zh) Mbms业务的传输模式指示方法、装置及存储介质
WO2024153083A1 (zh) 一种邻小区信息指示方法、装置、终端及网络侧设备
WO2024208022A1 (zh) 一种通信方法及装置
US20240365177A1 (en) Method for determining configuration information, terminal device and chip
WO2024208347A1 (zh) 多播业务处理方法、装置、终端及网络侧设备
WO2024066858A1 (zh) 一种通信的方法和装置
WO2024207195A1 (zh) 多路径的通信方法以及装置
WO2024207316A1 (zh) 多路径的通信方法以及装置
WO2024146531A1 (zh) 一种通信的方法和装置
US20240057196A1 (en) Broadcast-multicast service session transmission control method and device
WO2023202459A1 (zh) 传输处理方法、装置、终端、及网络侧设备
US20230371049A1 (en) Ulticast service transmission method and apparatus

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

Country of ref document: EP

Kind code of ref document: A1