WO2024066901A1 - 一种通信的方法和装置 - Google Patents

一种通信的方法和装置 Download PDF

Info

Publication number
WO2024066901A1
WO2024066901A1 PCT/CN2023/116145 CN2023116145W WO2024066901A1 WO 2024066901 A1 WO2024066901 A1 WO 2024066901A1 CN 2023116145 W CN2023116145 W CN 2023116145W WO 2024066901 A1 WO2024066901 A1 WO 2024066901A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast
information
configuration information
network device
session
Prior art date
Application number
PCT/CN2023/116145
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
Priority claimed from CN202211378635.6A external-priority patent/CN117835163A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024066901A1 publication Critical patent/WO2024066901A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services

Definitions

  • the present application relates to the field of communications, and more specifically, to a communication method and device.
  • Multicast and broadcast service can provide data to a large number of users with the same needs at the same time with fewer resources, so that network resources can be shared.
  • 3GPP 3rd generation partnership project
  • R 3rd generation partnership project
  • the terminal device receives MBS in the connected state.
  • the network device can first send the MBS configuration to the terminal device, and further, the terminal device can receive the MBS according to the MBS configuration.
  • R18 proposes to support terminal devices to receive MBS in the RRC inactive state. For example, when the terminal device has no unicast service and only has MBS, the network can release the terminal device to the RRC inactive state, and the terminal device can receive MBS in the RRC inactive state. In this way, the number of terminal devices in the RRC connected state in the network can be reduced, which is conducive to alleviating network congestion and energy saving of terminal devices.
  • the present application provides a communication method and apparatus, which enables a terminal device to receive MBS in an RRC inactive state, which is helpful for alleviating network congestion and also helps the terminal device to save energy.
  • a communication method is provided.
  • the method may be executed by a terminal device, or may be executed by a component of the terminal device (eg, a chip or a circuit), which is not limited in the present application.
  • the method may include: a terminal device receives first information from a first network device, the first information includes at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, the at least one multicast configuration information includes the first multicast configuration information, and the index information corresponding to the at least one multicast configuration information includes the first index information; the terminal device receives second information from a second network device, the second information is used to indicate that the first multicast session is associated with the first index information, and the first index information indicates the first multicast configuration information; the terminal device receives the first multicast session from the second network device in an inactive state or an idle state of a radio resource control RRC according to the first multicast configuration information.
  • the first network device pre-configures the multicast configuration resource pool to the terminal device, and the multicast configuration resource pool may include multiple multicast configuration information associated with the first multicast session, and then the second network device may indicate to the terminal device through the second information to receive the first multicast configuration information required for the first multicast session.
  • the first network device pre-configures the multicast configuration resource pool to the terminal device, and the multicast configuration resource pool may include multiple multicast configuration information associated with the first multicast session, and then the second network device may indicate to the terminal device through the second information to receive the first multicast configuration information required for the first multicast session.
  • the first information further includes identification information of a cell or a network device corresponding to at least one multicast configuration information.
  • the method also includes: the terminal device obtains a first identifier, the first identifier is an identifier of a cell where the terminal device resides or an identifier of a network device corresponding to the cell where the terminal device resides, and there is a corresponding relationship between the first identifier and the first multicast configuration information; the terminal device determines the first multicast configuration information based on the first identifier and the first index information.
  • the method further includes: the terminal device receives third information from the first network device, and the third information is used to indicate an effective area of at least one multicast configuration information.
  • the method further includes: the terminal device receives a signal from the first network device.
  • the fourth information of the terminal device or the second network device is used to indicate the first G-RNTI corresponding to the first multicast session; the terminal device descrambles the first multicast session according to the first G-RNTI.
  • the fourth information is information of the first G-RNTI; or, the fourth information is index information of the first G-RNTI, and the index information of the first G-RNTI has a corresponding relationship with the first G-RNTI; or, the fourth information is information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • the first index information includes one or more of the following: multicast radio bearer MRB configuration index, physical channel configuration index, discontinuous reception DRX configuration index, neighbor cell configuration index, common frequency domain resource CFR configuration index, semi-persistent scheduling (SPS) configuration index.
  • multicast radio bearer MRB configuration index physical channel configuration index
  • discontinuous reception DRX configuration index neighbor cell configuration index
  • common frequency domain resource CFR configuration index common frequency domain resource CFR configuration index
  • SPS semi-persistent scheduling
  • the terminal device receives the second information: the terminal device reselects to a cell managed by the second network device; or the terminal device receives the fifth information, wherein the fifth information is used to notify a system message change; or the fifth information is used to notify a multicast control channel message change; or the fifth information is used to notify the activation of the first multicast session; the fifth information is used to instruct the terminal device to receive the multicast session in an RRC inactive state or an idle state;
  • the system change notification message or the notification multicast control channel message change is used for:
  • the method also includes: the terminal device receives a first message from a second network device, the first message is a system message or a multicast control channel message, and the first message is used to indicate that the reception of the first multicast session is stopped or the cell managed by the second network device stops providing the first multicast session in an inactive state.
  • the method also includes: the terminal device determines whether to restore the RRC connection based on the first message.
  • the first message indicates that the first multicast session is deactivated, and the terminal device remains in an RRC inactive state or an idle state and stops receiving the first multicast session.
  • the terminal device receives the first message, and the first message does not include an identifier of the first multicast session.
  • the terminal device receives the first message, where the first message includes an identifier of the first multicast session but does not include the first index information.
  • the terminal device stops receiving the first multicast session; or, if the first message does not include the identifier of the first multicast session, the terminal device sends an RRC recovery request message to the second network device and enters the RRC connection state to receive the first multicast session.
  • the second information is carried in any one of the following: a system message, a multicast control channel message, and an RRC release message.
  • a communication method is provided, which can be performed by a third network device, or can also be performed by a component (such as a chip or circuit) of the third network device, and this application does not limit this.
  • the third network device can be the first network device in the first aspect, or the second network device in the first aspect.
  • the method may include: a third network device sending second information, the second information is used to indicate that the first multicast session is associated with first index information, the first index information indicates first multicast configuration information; the third network device sends the first multicast session according to the first multicast configuration information.
  • the third network device can indicate to the terminal device through the second information that the first multicast configuration information required for receiving the first multicast session is received.
  • the security risks caused by receiving the multicast configuration information in the form of broadcasting can be avoided, and on the other hand, the signaling overhead and delay caused by the terminal device entering the RRC connection state to receive the multicast configuration information can be avoided.
  • the method further includes: a third network device sending first information to a terminal device, the first information including at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, the at least one multicast configuration information including the first multicast configuration information, and the index information corresponding to the at least one multicast configuration information including the first index information;
  • the first information further includes identification information of a cell or a network device corresponding to at least one multicast configuration information.
  • the method further includes: the third network device sends a first identifier, where the first identifier is an identifier of the third network device or an identifier of a cell corresponding to the second information.
  • the method further includes: a third network device obtains the first information.
  • the third network device obtains the first information, including: the third network device receives sixth information from the fourth network device, the sixth information including M multicast configuration information and index information corresponding to the M multicast configuration information; the third network device determines N multicast configuration information and index information corresponding to the N multicast configuration information; wherein at least one The multicast configuration information includes M multicast configuration information and N configuration information, where M and N are both positive integers.
  • the third network device obtains the first information, including: the third network device determines N multicast configuration information; the third network device receives sixth information from the fourth network device, and the sixth information includes M multicast configuration information; the third network device determines the M multicast configuration information and the index information corresponding to the N multicast configuration information based on the M configuration information and the N multicast configuration information; wherein, at least one multicast configuration information includes M multicast configuration information and N configuration information, and M and N are both positive integers.
  • the sixth information further includes identification information of cells corresponding to the M multicast configuration information.
  • the method further includes: the third network device sends the first information to the fourth network device.
  • the method further includes: a third network device sends third information to the terminal device, where the third information is used to indicate an effective area of at least one multicast configuration information.
  • the method further includes: a third network device sends fourth information to the terminal device, the fourth information is used to indicate the first G-RNTI, and the first G-RNTI is used to scramble the first multicast session.
  • the fourth information is the information of the first G-RNTI; or, the fourth information is the index information of the first G-RNTI, and the index information of the first G-RNTI has a corresponding relationship with the first G-RNTI; or, the fourth information is the information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • the fourth information is information of the first G-RNTI
  • the method also includes: the third network device receives the first G-RNRI from the core network device; or, the third network device determines the first G-RNTI based on the identifier of the first multicast session.
  • the first index information includes one or more of the following: multicast radio bearer MRB configuration index, physical channel configuration index, discontinuous reception DRX configuration index, neighbor cell configuration index, common frequency domain resource CFR configuration index, semi-continuous scheduling SPS configuration index.
  • the method also includes: a third network device sends fifth information, the fifth information is used to notify system message changes or to notify multicast control channel message changes, and the fifth information is used by the terminal device to receive the second information.
  • the third network device sends fifth information to the terminal device: the multicast configuration information of the first multicast session is changed to the first multicast configuration information; or, the cell managed by the third network device starts to provide the first multicast session in an inactive state or an idle state.
  • the method also includes: a third network device sends a first message, the first message is a system message, a multicast control channel message, the first message is used to indicate that the first multicast session is in a deactivated state or is released, or is used to indicate that the cell managed by the second network device stops providing the first multicast session in an inactive state.
  • the method also includes: a third network device sends a first message, the first message is a system message, a multicast control channel message, the first message is used to indicate that the first multicast session is in a deactivated state or is released, or is used to indicate that the cell managed by the second network device stops providing the first multicast session in an inactive state.
  • the third network device determines that the first multicast session is in a deactivated state or is released, and the third network device sends a first message, the first message includes an identifier of the first multicast session, and the first message does not include first index information; or, the cell managed by the third network device stops providing the first multicast session in an RRC inactive state or an idle state, and the third network device sends a first message, and the first message does not include an identifier of the first multicast session.
  • a communication method is provided.
  • the method may be executed by a fourth network device, or may be executed by a component (such as a chip or circuit) of the fourth network device, and the present application does not limit this.
  • the method may include: the fourth network device sends sixth information to the third network device, the sixth information includes M multicast configuration information and index information corresponding to the M multicast configuration information; or, the sixth information includes M multicast configuration information, M is a positive integer; the fourth network device receives first information from the third network device, the first information includes at least one multicast configuration information and index information corresponding to at least one multicast configuration information, and the at least one multicast configuration information includes M multicast configuration information.
  • the fourth network device can send the M multicast configuration information determined by it to the third network device.
  • the third network device can determine the first information.
  • the third network device can indicate the multicast configuration to the terminal device through the first information and the index information, which can avoid the security risks caused by receiving the multicast configuration information in the form of broadcasting on the one hand, and on the other hand, avoid When a terminal device enters the RRC connection state and receives multicast configuration information, signaling overhead and delay are incurred.
  • the method also includes: the fourth network device sends seventh information, the seventh information is used to indicate that the first multicast session is associated with second index information, the second index information indicates second multicast configuration information, at least one multicast configuration information includes the second multicast configuration information, and the index information corresponding to at least one multicast configuration information includes the second index information; the fourth network device sends the first multicast session according to the second multicast configuration information.
  • a communication method is provided.
  • the method can be executed by a terminal device, or can also be executed by a component of the terminal device (such as a chip or circuit), which is not limited in this application.
  • the method may include: a terminal device receives eighth information from a first network device, the eighth information includes first multicast configuration information and information of a cell corresponding to the first multicast configuration information, the first multicast configuration corresponds to a first multicast session, and the cell information corresponding to the first multicast configuration information includes a first cell; the terminal device receives a second message from a second network device, the second message includes first indication information, and the first indication information is used to indicate a status of a first multicast session provided by the first cell; when the first cell is a resident cell of the terminal device, the terminal device receives the first multicast session according to the first multicast configuration information.
  • the first network device pre-configures the information of the cell corresponding to the first multicast configuration information to the terminal device, and the second network device can indicate the status of the multicast session of each cell to the terminal device through the first indication information in the second message.
  • the terminal device can use the first multicast configuration information to receive the multicast session. In this way, on the one hand, it can avoid the security risks caused by receiving the multicast configuration information in the form of broadcasting, and on the other hand, it can avoid the signaling overhead and delay caused by the terminal device entering the RRC connection state to receive the multicast configuration information.
  • the status of the first multicast session includes: the first cell is providing or not providing the first multicast session in the RRC inactive state or idle state, or the first cell starts or stops providing the first multicast session in the RRC inactive state or idle state; or the multicast configuration information corresponding to the first multicast session changes.
  • the terminal device receives the first multicast session according to the first multicast configuration information, including: when the first indication information indicates that the first cell starts to provide the first multicast session in the RRC inactive state or the idle state, the terminal device receives the first multicast session in the RRC inactive state or the idle state according to the first multicast configuration information; or, when the first indication information indicates that the first cell stops providing the first multicast session in the RRC inactive state or the idle state, the terminal device sends an RRC recovery request message to the network device corresponding to the first cell.
  • the second message is a paging message or an RRC release message.
  • the RRC release message instructs the UE to enter the inactive state to receive multicast, and the UE uses the first multicast configuration to receive multicast; or, the RRC release message instructs the EU to enter the inacitve state to receive multicast, and the RRC release message carries an updated multicast configuration, and the UE receives multicast according to the updated multicast configuration.
  • the eighth information is carried in an RRC release message or an RRC reconfiguration message.
  • the first indication information is a bit map, and at least one bit in the bit map is associated with the first cell.
  • the cell information corresponding to the first multicast configuration information includes Q cells
  • the bit map includes Q bits
  • the Q bits correspond to the Q cells one-to-one.
  • the eighth information also includes at least one multicast configuration information, index information corresponding to at least one multicast configuration information, and cell information corresponding to at least one multicast configuration information, at least one multicast configuration information includes first multicast configuration information, at least one index information corresponding to the multicast configuration information includes first index information, and at least one cell information corresponding to the multicast configuration information includes a first cell.
  • the second message also includes second information, the second information is used to indicate that the first multicast session is associated with first index information, and the first index information indicates the first multicast configuration information.
  • the first index information includes one or more of the following: MRB configuration index, physical channel configuration index, discontinuous reception DRX configuration index, neighbor cell configuration index, CFR configuration index, SPS configuration index.
  • the method also includes: the terminal device receives fourth information from the first network device or the second network device, the fourth information being used to indicate the first G-RNTI corresponding to the first multicast session; the terminal device de-jamming the first multicast session according to the first G-RNTI.
  • the fourth information is information of the first G-RNTI; or, the fourth information is index information of the first G-RNTI, and the index information of the first G-RNTI has a corresponding relationship with the first G-RNTI; or, the fourth information is information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • a communication method is provided, which can be performed by a third network device, or can also be performed by a component (such as a chip or circuit) of the third network device, and this application does not limit this.
  • the third network device can be the first network device in the fourth aspect, or the second network device in the fourth aspect.
  • the method may include: a third network device sends a second message, the second message includes first indication information, and the first indication information is used to indicate that the state of a first multicast session provided by the first cell has changed; the third network device sends the first multicast session according to the first multicast configuration information.
  • the third network device when the terminal device is in a connected state, the third network device preconfigures the information of the cell corresponding to the first multicast configuration information to the terminal device, and the third network device can also indicate the state of the multicast session of each cell to the terminal device through the first indication information in the second message, so that: when a certain cell is the service cell of the terminal device, and the cell starts to provide a multicast session in an inactive state or an idle state, the terminal device can use the first multicast configuration information to receive the multicast session.
  • the status of the first multicast session includes: the first cell is providing or not providing the first multicast session in the RRC inactive state or idle state, or the first cell starts or stops providing the first multicast session in the RRC inactive state or idle state; or the multicast configuration information corresponding to the first multicast session changes.
  • the third network device is the first network device in the fourth aspect, or is the second network device in the fourth aspect.
  • the method also includes: the third network device sends eighth information to the terminal device, the eighth information includes first multicast configuration information and cell information corresponding to the first multicast configuration information, the first multicast configuration corresponds to the first multicast session, and the cell information corresponding to the first multicast configuration information includes the first cell.
  • the eighth information is carried in an RRC release message or an RRC reconfiguration message.
  • the method also includes: the third network device receives ninth information from the fourth network device, the ninth information is used to indicate the identifiers of R cells corresponding to the first multicast configuration information, and the cell information corresponding to the first multicast configuration information includes R cells, where R is a positive integer.
  • the first indication information is a bit map, and at least one bit in the bit map is associated with the first cell.
  • the cell information corresponding to the first multicast configuration information includes Q cells
  • the bitmap includes Q bits
  • the Q bits correspond to the Q cells one-to-one.
  • the eighth information also includes at least one multicast configuration information, index information corresponding to at least one multicast configuration information, and cell information corresponding to at least one multicast configuration information, at least one multicast configuration information includes first multicast configuration information, at least one index information corresponding to the multicast configuration information includes first index information, and at least one cell information corresponding to the multicast configuration information includes a first cell.
  • the method further includes: the third network device receives sixth information from the fourth network device, the sixth information including M multicast configuration information and index information corresponding to the M multicast configuration information; the third network device determines N multicast configuration information and index information corresponding to the N multicast configuration information;
  • the at least one multicast configuration information includes M multicast configuration information and N configuration information, where M and N are both positive integers.
  • the third network device obtains the first information, including:
  • the third network device determines N multicast configuration information; the third network device receives sixth information from the fourth network device, the sixth information including M multicast configuration information; the third network device determines the M multicast configuration information and the index information corresponding to the N multicast configuration information according to the M configuration information and the N multicast configuration information;
  • the at least one multicast configuration information includes M multicast configuration information and N configuration information, where M and N are both positive integers.
  • the sixth information further includes identification information of cells corresponding to the M multicast configuration information.
  • the method further includes: the third network device sends a Send the eighth message.
  • the second message also includes second information, the second information is used to indicate that the first multicast session is associated with first index information, and the first index information indicates the first multicast configuration information.
  • the first index information includes one or more of the following:
  • MRB configuration index physical channel configuration index, discontinuous reception DRX configuration index, neighbor cell configuration index, CFR configuration index, SPS configuration index.
  • the method also includes: the third network device sends fourth information to the terminal device, the fourth information is used to indicate the first G-RNTI, and the first G-RNTI is used to scramble the first multicast session.
  • the fourth information is information of the first G-RNTI; or, the fourth information is index information of the first G-RNTI, and the index information of the first G-RNTI has a corresponding relationship with the first G-RNTI; or, the fourth information is information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • the fourth information is information of the first G-RNTI
  • the method also includes: the third network device receives the first G-RNRI from the core network device; or, the third network device determines the first G-RNTI based on the identifier of the first multicast session.
  • the first cell is a cell managed by a third network device.
  • the method before the third network device sends a second message to the terminal device, the method also includes: the third network device receives second indication information from the fourth network device, the second indication information is used to indicate a change in the status sending of a first multicast session provided by the first cell, and the first cell is a cell managed by the fourth network device.
  • a communication method is provided.
  • the method can be executed by a fourth network device, or can also be executed by a component (such as a chip or circuit) of the fourth network device, and the present application does not limit this.
  • the method may include: the fourth network device sends second indication information to the third network device, the second indication information is used to indicate the state of a first multicast session in a non-connected state or an idle state provided by a first cell, and the first cell is a cell managed by the second network device; the fourth network device sends a second message, the second message includes first indication information, and the first indication information is used to indicate the state of a first multicast session in a non-connected state or an idle state provided by the first cell.
  • the fourth network device can send the status of the first multicast session in a non-connected state or an idle state provided by the cell it manages to the third network device.
  • the fourth network device can also send a second message to indicate the status of the multicast session of each cell to the terminal device through the first indication information, so that: when a certain cell is a service cell for the terminal device and the cell starts to provide a multicast session in an inactive state or an idle state, the terminal device can use the first multicast configuration information to receive the multicast session.
  • it can avoid the security risks caused by receiving the multicast configuration information in the form of broadcasting, and on the other hand, it can avoid the signaling overhead and delay caused by the terminal device entering the RRC connection state to receive the multicast configuration information.
  • the status of the first multicast session includes: the first cell is providing or not providing the first multicast session in the RRC inactive state or idle state, or the first cell starts or stops providing the first multicast session in the RRC inactive state or idle state; or the multicast configuration information corresponding to the first multicast session changes.
  • the method also includes: the fourth network device sends sixth information to the third network device, the sixth information includes M multicast configuration information and index information corresponding to the M multicast configuration information; or, the sixth information includes M multicast configuration information, M is a positive integer; the fourth network device receives eighth information from the third network device, the first information includes at least one multicast configuration information and index information corresponding to at least one multicast configuration information, and the at least one multicast configuration information includes M multicast configuration information.
  • a communication method is provided.
  • the method can be executed by a terminal device, or can also be executed by a component of the terminal device (such as a chip or circuit), and the present application does not limit this.
  • the method may include: a terminal device receives first multicast configuration information and tenth information from a fifth network device, the first multicast configuration information is used to configure a first multicast session, and the tenth information is used to indicate an effective area of the first multicast configuration information; the terminal device receives the first multicast session in an inactive state or an idle state of a wireless resource control RRC according to the first multicast configuration information within the effective area.
  • the terminal device can obtain the first multicast configuration information for receiving the first multicast session, and can also obtain the effective area of the first multicast configuration information.
  • the terminal device can continue to use the multicast configuration information to receive the multicast session, thereby ensuring the continuity of the terminal device receiving the multicast service.
  • the terminal device triggering RRC connection recovery every time the cell reselects to a new cell can save the terminal device time. It can not only reduce the energy consumption of equipment, but also save the air interface signaling overhead.
  • a communication method is provided, which can be executed by a fifth network device, or can also be executed by a component (such as a chip or circuit) of the fifth network device, and the present application does not limit this.
  • the method may include: a fifth network device sends a third message to a first device, the third message is used to request multicast configuration information of a first multicast session; the fifth network device receives first multicast configuration information from the first device, the first multicast configuration information is determined according to the third message and a value range of a multicast configuration parameter, and the first multicast configuration information is used to configure the terminal device to receive the first multicast session in an inactive state or an idle state of a radio resource control RRC.
  • the first device can determine the first multicast configuration information for the first multicast session provided by one or more fifth network devices.
  • the first device can determine the first multicast configuration information that can be used by one or more fifth network devices for the first multicast session, so that for the same multicast session, different network devices supporting the first multicast session in a region can use the same multicast configuration information.
  • the multicast configuration information within the region can be synchronized.
  • the terminal device can continue to use the multicast configuration information to receive the multicast session, thereby ensuring the continuity of the terminal device receiving the multicast service.
  • the method further includes: a fifth network device sending first multicast configuration information to the terminal device.
  • the value range of the multicast configuration parameter includes at least one of the following: the value range of G-RNTI, the value range of the multicast radio bearer MRB identifier, the value range of the logical channel LCH identifier, the value range of the physical channel configuration parameter, the value range of the discontinuous reception DRX configuration parameter, and the value range of the common frequency domain resource CFR configuration parameter.
  • the third message includes at least one of the following: an identifier of the first multicast session, the number of MRBs required for the first multicast session, and the number of logical channels LCH required for the first MRB of the first multicast session.
  • the third message includes an identifier of a second cell
  • the second cell is a cell managed by a fifth network device and providing a first multicast session in an RRC inactive state or an idle state.
  • the method further includes: the fifth network device receives tenth information from the first device, and the tenth information indicates an effective area of the first multicast configuration information.
  • the method further includes: the fifth network device sends a fourth message to the first device, and the fourth message includes a value range of the multicast configuration parameter.
  • the fourth message also includes identification information of a second area, and the second area is an effective area of a value range of the multicast configuration parameter.
  • the cell within the second area provides at least one multicast session, at least one multicast session includes a first multicast session, the multicast configuration information of other multicast sessions in the at least one multicast session except the first multicast session is different from the first multicast configuration information, and the multicast configuration information of at least one multicast session is different from each other.
  • the second area is a notification area RNA based on a wireless access network where the fifth network device is located.
  • the method also includes: the fifth network device sends eleventh information to the first device, and the eleventh information is used to instruct the third cell managed by the fifth network device to stop providing the first multicast session in the radio resource control RRC inactive state or idle state.
  • a communication method is provided, which can be executed by a fourth network device, or can also be executed by a component (such as a chip or circuit) of the fourth network device, and the present application does not limit this.
  • the method may include: a first device receives a third message from a fifth network device, the third message is used to request multicast configuration information of a first multicast session; the first device determines first multicast configuration information based on the third message and a value range of a multicast configuration parameter, the first multicast configuration information is used to configure a terminal device to receive the first multicast session in an inactive or idle state of a radio resource control RRC; the first device sends the first multicast configuration information to the fifth network device.
  • the first device can determine the first multicast configuration information for the first multicast session provided by one or more fifth network devices.
  • the first device can determine the first multicast configuration information that can be used by one or more fifth network devices for the first multicast session, so that for the same multicast session, different network devices supporting the first multicast session in a region can use the same multicast configuration information.
  • the multicast configuration information within the region can be synchronized.
  • the terminal device can continue to use the multicast configuration information to receive the multicast session, thereby ensuring the continuity of the terminal device receiving the multicast service.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the G-RNTI
  • the first device determines the first multicast configuration information based on the third message and the value range of the multicast configuration parameter, including: the first device selects a value from the value range of the G-RNTI as the G-RNTI of the first multicast session, and the first multicast configuration information includes the G-RNTI of the first multicast session.
  • the third message includes an identifier of the first multicast session and the number X of multicast radio bearer MRBs required for the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the MRB identifier
  • the first device determines the first multicast configuration information based on the third message and the value range of the multicast configuration parameter, including: the first device selects X values from the value range of the MRB identifier as the MRB identifier of the first multicast session, the first multicast configuration information includes the MRB identifier of the first multicast session, and X is a positive integer.
  • the third message includes an identifier of the first multicast session and the number Y of logical channels LCH required by the first MRB of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the LCH identifier
  • the first device determines the first multicast configuration information based on the third message and the value range of the multicast configuration parameter, including: the first device selects Y values from the value range of the LCH identifier as the LCH identifier of the first MRB, the first multicast configuration information includes the LCH identifier of the first MRB, and Y is a positive integer.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the physical channel configuration parameter
  • the first device determines the first multicast configuration information based on the third message and the value range of the multicast configuration parameter, including: the first device selects at least one value from the value range of the physical channel configuration parameter as the physical channel configuration parameter of the first multicast session, and the first multicast configuration information includes the physical channel configuration parameter of the first multicast session.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the discontinuous reception DRX configuration parameter
  • the first device determines the first multicast configuration information based on the third message and the value range of the multicast configuration parameter, including: the first device selects at least one value from the value range of the DRX configuration parameter as the DRX configuration parameter of the first multicast session, and the first multicast configuration information includes the DRX configuration parameter of the first multicast session.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the common frequency domain resource CFR configuration parameter
  • the first device determines the first multicast configuration information based on the third message and the value range of the multicast configuration parameter, including: the first device selects at least one value from the value range of the CFR configuration parameter as the CFR configuration parameter of the first multicast session, and the first multicast configuration information includes the CFR configuration parameter of the first multicast session.
  • the third message includes an identifier of a second cell
  • the second cell is a cell managed by a fifth network device and providing a first multicast session in an RRC inactive state or an idle state.
  • the method also includes: the first device determines tenth information based on the third message from one or more fifth network devices, and the tenth information is used to indicate an effective area of the first multicast configuration information.
  • the method further includes: the first device sends tenth information to the fifth network device.
  • the method further includes: the first device receives a fourth message from a fifth network device, and the fourth message includes a value range of a multicast configuration parameter.
  • the fourth message also includes identification information of a second area, and the second area is an effective area of a value range of the multicast configuration parameter.
  • the cell within the second area provides at least one multicast session
  • the at least one multicast session includes a first multicast session
  • the method further includes: the first device determines mutually different multicast configuration information for the at least one multicast session.
  • the multicast configuration information of the other multicast sessions except the first multicast session in the at least one multicast session is different from the first multicast configuration information.
  • the second area is a notification area RNA based on a wireless access network where the fifth network device is located.
  • the method also includes: the first device receives eleventh information from the fifth network device, the eleventh information is used to instruct the third cell managed by the fifth network device to stop providing the first multicast session in the radio resource control RRC inactive state or idle state; the first device removes the third cell from the effective area of the first multicast configuration information.
  • the first multicast configuration information includes at least one of the following: G-RNTI, MRB configuration, CFR configuration, DRX configuration, and physical channel configuration of the first multicast session.
  • a communication device which may be executed by a terminal device, or may be a component of the terminal device (such as a chip or circuit), which is not limited in the present application.
  • the apparatus may include: a transceiver unit, configured to receive first information from a first network device, the first information including at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, the at least one multicast configuration information including the first multicast configuration information, and the index information corresponding to the at least one multicast configuration information including the first index information; the transceiver unit is also configured to: receive second information from a second network device, the second information is used to indicate that the first multicast session is associated with the first index information, and the first index information indicates the first multicast configuration information; a processing unit, configured to: receive the first multicast session from the second network device in an inactive state or an idle state of a radio resource control RRC according to the first multicast configuration information.
  • a transceiver unit configured to receive first information from a first network device, the first information including at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, the at least one multicast configuration information including the first multicast configuration information including the first index
  • the first information further includes identification information of a cell or a network device corresponding to at least one multicast configuration information.
  • the transceiver unit is also used to: obtain a first identifier, the first identifier is an identifier of a resident cell of the terminal device or an identifier of a network device corresponding to the resident cell, and there is a corresponding relationship between the first identifier and the first multicast configuration information; the processing unit is also used to: determine the first multicast configuration information based on the first identifier and the first index information.
  • the transceiver unit is further used to: receive third information from the first network device, where the third information is used to indicate an effective area of at least one multicast configuration information.
  • the transceiver unit is also used to: receive fourth information from the first network device or the second network device, the fourth information being used to indicate the first G-RNTI corresponding to the first multicast session; and the terminal device de-jamming the first multicast session according to the first G-RNTI.
  • the fourth information is information of the first G-RNTI; or, the fourth information is index information of the first G-RNTI, and the index information of the first G-RNTI has a corresponding relationship with the first G-RNTI; or, the fourth information is information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • the first index information includes one or more of the following: multicast radio bearer MRB configuration index, physical channel configuration index, discontinuous reception DRX configuration index, neighbor cell configuration index, common frequency domain resource CFR configuration index, semi-persistent scheduling (SPS) configuration index.
  • multicast radio bearer MRB configuration index physical channel configuration index
  • discontinuous reception DRX configuration index neighbor cell configuration index
  • common frequency domain resource CFR configuration index common frequency domain resource CFR configuration index
  • SPS semi-persistent scheduling
  • the processing unit is further used to: receive the second information when any of the following conditions is met: the condition includes: the terminal device reselects to a cell managed by the second network device; or, the terminal device receives the fifth information, wherein the fifth information is used to notify the system message change; or, the fifth information is used to notify the multicast control channel message change; or, the fifth information is used to notify the activation of the first multicast session; the fifth information is used to instruct the terminal device to receive the multicast session in the RRC inactive state or idle state;
  • the system change notification message or the notification multicast control channel message change is used for:
  • the transceiver unit is also used to: receive a first message from a second network device, the first message being a system message or a multicast control channel message, the first message being used to indicate to stop receiving the first multicast session or the cell managed by the second network device to stop providing the first multicast session in an inactive state.
  • the processing unit is further used to determine whether to restore the RRC connection according to the first message.
  • the first message indicates that the first multicast session is deactivated, and the terminal device remains in an RRC inactive state or an idle state and stops receiving the first multicast session.
  • the terminal device receives the first message, and the first message does not include an identifier of the first multicast session.
  • the terminal device receives the first message, where the first message includes an identifier of the first multicast session but does not include the first index information.
  • the terminal device stops receiving the first multicast session; or, if the first message does not include the identifier of the first multicast session, the terminal device sends an RRC recovery request message to the second network device and enters the RRC connection state to receive the first multicast session.
  • the second information is carried in any one of the following: a system message, a multicast control channel message, and an RRC release message.
  • a communication device which may be a third network device, or may be a third network device.
  • the third network device may be a component of the first network device in the first aspect, or may be a second network device in the first aspect.
  • the device may include: a transceiver unit, configured to send second information, the second information is used to indicate that a first multicast session is associated with first index information, the first index information indicates first multicast configuration information; and a processing unit, configured to send the first multicast session according to the first multicast configuration information.
  • the transceiver unit is also used to: send first information to the terminal device, the first information including at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, at least one multicast configuration information including the first multicast configuration information, and the index information corresponding to the at least one multicast configuration information including the first index information.
  • the first information also includes identification information of a cell or a network device corresponding to at least one multicast configuration information.
  • the transceiver unit is further used to: send a first identifier, where the first identifier is an identifier of a third network device or an identifier of a cell corresponding to the second information.
  • the transceiver unit is further used to: obtain first information.
  • the transceiver unit is specifically used to: receive sixth information from a fourth network device, the sixth information including M multicast configuration information and index information corresponding to the M multicast configuration information; the processing unit is also used to: determine N multicast configuration information and index information corresponding to the N multicast configuration information; wherein at least one multicast configuration information includes M multicast configuration information and N configuration information, and M and N are both positive integers.
  • the transceiver unit is specifically used to: determine N multicast configuration information; receive sixth information from a fourth network device, the sixth information including M multicast configuration information; the processing unit is also used to: determine the index information corresponding to the M multicast configuration information and the N multicast configuration information based on the M configuration information and the N multicast configuration information; wherein at least one multicast configuration information includes M multicast configuration information and N configuration information, and M and N are both positive integers.
  • the sixth information further includes identification information of cells corresponding to the M multicast configuration information.
  • the transceiver unit is further used to: send the first information to the fourth network device.
  • the transceiver unit is further used for: the terminal device sends third information, and the third information is used to indicate an effective area of at least one multicast configuration information.
  • the transceiver unit is further used to: send fourth information to the terminal device, the fourth information is used to indicate the first G-RNTI, and the first G-RNTI is used to scramble the first multicast session.
  • the fourth information is the information of the first G-RNTI; or, the fourth information is the index information of the first G-RNTI, and the index information of the first G-RNTI has a corresponding relationship with the first G-RNTI; or, the fourth information is the information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • the fourth information is information of the first G-RNTI
  • the transceiver unit is also used to: receive the first G-RNRI from the core network device; or, the processing unit is also used to: determine the first G-RNTI based on the identifier of the first multicast session.
  • the first index information includes one or more of the following: multicast radio bearer MRB configuration index, physical channel configuration index, discontinuous reception DRX configuration index, neighbor cell configuration index, common frequency domain resource CFR configuration index, semi-continuous scheduling SPS configuration index.
  • the transceiver unit is also used to: send fifth information, the fifth information is used to notify system message changes or to notify multicast control channel message changes, and the fifth information is used for the terminal device to receive second information.
  • the processing unit is also used to: send fifth information to the terminal device when any of the following conditions is met, the condition including: the multicast configuration information of the first multicast session is changed to the first multicast configuration information; or, the cell managed by the third network device starts to provide the first multicast session in an inactive state or an idle state.
  • the transceiver unit is also used to: send a first message, the first message is a system message, a multicast control channel message, the first message is used to indicate that the first multicast session is in a deactivated state or is released, or is used to indicate that the cell managed by the second network device stops providing the first multicast session in an inactive state.
  • the transceiver unit is further used to: send a first message, the first message is a system message, a multicast control channel message, the first message is used to indicate that the first multicast session is in a deactivated state or is released, or Instructing the cell managed by the second network device to stop providing the first multicast session in an inactive state.
  • the third network device determines that the first multicast session is in a deactivated state or is released, and the third network device sends a first message, the first message includes an identifier of the first multicast session, and the first message does not include first index information; or, the cell managed by the third network device stops providing the first multicast session in an RRC inactive state or an idle state, and the third network device sends a first message, and the first message does not include an identifier of the first multicast session.
  • a communication device which may be a fourth network device, or may be a component (such as a chip or circuit) of the fourth network device, and this application does not limit this.
  • the device may include: a transceiver unit, used to send sixth information to a third network device, the sixth information including M multicast configuration information and index information corresponding to the M multicast configuration information; or, the sixth information including M multicast configuration information, M is a positive integer; the transceiver unit is also used to: receive first information from the third network device, the first information including at least one multicast configuration information and index information corresponding to at least one multicast configuration information, and the at least one multicast configuration information includes M multicast configuration information.
  • the transceiver unit is also used to: send seventh information, the seventh information is used to indicate that the first multicast session is associated with second index information, the second index information indicates second multicast configuration information, at least one multicast configuration information includes the second multicast configuration information, and the index information corresponding to at least one multicast configuration information includes the second index information;
  • the device may also include a processing unit, the processing unit is used to send the first multicast session according to the second multicast configuration information.
  • a communication device which may be executed by a terminal device, or may be a component of the terminal device (such as a chip or circuit), which is not limited in the present application.
  • the apparatus may include: a transceiver unit, configured to receive eighth information from a first network device, the eighth information including first multicast configuration information and information of a cell corresponding to the first multicast configuration information, the first multicast configuration corresponding to a first multicast session, and the cell information corresponding to the first multicast configuration information including a first cell; the transceiver unit is also configured to: receive a second message from a second network device, the second message including first indication information, the first indication information being used to indicate a status of a first multicast session provided by the first cell; the transceiver unit is configured to receive the first multicast session according to the first multicast configuration information when the first cell is a resident cell of the terminal device.
  • the status of the first multicast session includes: the first cell is providing or not providing the first multicast session in the RRC inactive state or idle state, or the first cell starts or stops providing the first multicast session in the RRC inactive state or idle state; or the multicast configuration information corresponding to the first multicast session changes.
  • the transceiver unit is specifically used to: when the first indication information indicates that the first cell starts to provide the first multicast session in the RRC inactive state or idle state, receive the first multicast session in the RRC inactive state or idle state according to the first multicast configuration information; or, when the first indication information indicates that the first cell stops providing the first multicast session in the RRC inactive state or idle state, send an RRC recovery request message to the network device corresponding to the first cell.
  • the second message is a paging message or an RRC release message.
  • the RRC release message instructs the UE to enter the inactive state to receive multicast, and the UE uses the first multicast configuration to receive multicast; or, the RRC release message instructs the EU to enter the inacitve state to receive multicast, and the RRC release message carries an updated multicast configuration, and the UE receives multicast according to the updated multicast configuration.
  • the eighth information is carried in an RRC release message or an RRC reconfiguration message.
  • the first indication information is a bit map, and at least one bit in the bit map is associated with the first cell.
  • the cell information corresponding to the first multicast configuration information includes Q cells
  • the bit map includes Q bits
  • the Q bits correspond to the Q cells one-to-one.
  • the eighth information also includes at least one multicast configuration information, index information corresponding to at least one multicast configuration information, and cell information corresponding to at least one multicast configuration information, at least one multicast configuration information includes first multicast configuration information, at least one index information corresponding to the multicast configuration information includes first index information, and at least one cell information corresponding to the multicast configuration information includes a first cell.
  • the second message also includes second information, the second information is used to indicate that the first multicast session is associated with first index information, and the first index information indicates first multicast configuration information.
  • the first index information includes one or more of the following: an MRB configuration index, a physical channel configuration index, a discontinuous reception DRX configuration index, a neighboring cell configuration index, a CFR configuration index, an SPS configuration index, index.
  • the transceiver unit is also used to: receive fourth information from the first network device or the second network device, the fourth information being used to indicate the first G-RNTI corresponding to the first multicast session; and the terminal device de-jamming the first multicast session according to the first G-RNTI.
  • the fourth information is information of the first G-RNTI; or, the fourth information is index information of the first G-RNTI, and the index information of the first G-RNTI has a corresponding relationship with the first G-RNTI; or, the fourth information is information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • a communication device which may be a third network device, or may be a component (such as a chip or circuit) of the third network device, which is not limited in this application.
  • the third network device may be the first network device in the fourth aspect, or may be the second network device in the fourth aspect.
  • the device may include: a transceiver unit, configured to send a second message, the second message including first indication information, the first indication information being used to indicate that a state of a first multicast session provided by a first cell has changed; and a processing unit, configured to send the first multicast session according to the first multicast configuration information.
  • the status of the first multicast session includes: the first cell is providing or not providing the first multicast session in the RRC inactive state or idle state, or the first cell starts or stops providing the first multicast session in the RRC inactive state or idle state; or the multicast configuration information corresponding to the first multicast session changes.
  • the third network device is the first network device in the tenth aspect, or is the second network device in the tenth aspect.
  • the transceiver unit is also used to: send eighth information to the terminal device, the eighth information includes first multicast configuration information and cell information corresponding to the first multicast configuration information, the first multicast configuration corresponds to the first multicast session, and the cell information corresponding to the first multicast configuration information includes the first cell.
  • the eighth information is carried in an RRC release message or an RRC reconfiguration message.
  • the transceiver unit is also used to: receive ninth information from a fourth network device, the ninth information being used to indicate the identifiers of R cells corresponding to the first multicast configuration information, the cell information corresponding to the first multicast configuration information including R cells, where R is a positive integer.
  • the first indication information is a bit map, and at least one bit in the bit map is associated with the first cell.
  • the cell information corresponding to the first multicast configuration information includes Q cells
  • the bitmap includes Q bits
  • the Q bits correspond to the Q cells one-to-one.
  • the eighth information also includes at least one multicast configuration information, index information corresponding to at least one multicast configuration information, and cell information corresponding to at least one multicast configuration information, at least one multicast configuration information includes first multicast configuration information, at least one index information corresponding to the multicast configuration information includes first index information, and at least one cell information corresponding to the multicast configuration information includes a first cell.
  • the transceiver unit is further used to: receive sixth information from a fourth network device, the sixth information including M multicast configuration information and index information corresponding to the M multicast configuration information; the processing unit is further used to: determine N multicast configuration information and index information corresponding to the N multicast configuration information;
  • the at least one multicast configuration information includes M multicast configuration information and N configuration information, where M and N are both positive integers.
  • the processing unit is specifically used to: determine N multicast configuration information; the transceiver unit is specifically used to: receive sixth information from a fourth network device, the sixth information including M multicast configuration information; the processing unit is specifically used to: determine the M multicast configuration information and the index information corresponding to the N multicast configuration information according to the M configuration information and the N multicast configuration information;
  • the at least one multicast configuration information includes M multicast configuration information and N configuration information, where M and N are both positive integers.
  • the sixth information also includes identification information of the cell corresponding to the M multicast configuration information.
  • the transceiver unit is further used to: send eighth information to the fourth network device.
  • the second message further includes second information, and the second information is used to indicate The first index information indicates that the first multicast session is associated with the first index information, and the first index information indicates the first multicast configuration information.
  • the first index information includes one or more of the following:
  • MRB configuration index physical channel configuration index, discontinuous reception DRX configuration index, neighbor cell configuration index, CFR configuration index, SPS configuration index.
  • the transceiver unit is also used to: send fourth information to the terminal device, the fourth information is used to indicate the first G-RNTI, and the first G-RNTI is used to scramble the first multicast session.
  • the fourth information is information of the first G-RNTI; or, the fourth information is index information of the first G-RNTI, and the index information of the first G-RNTI has a corresponding relationship with the first G-RNTI; or, the fourth information is information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • the fourth information is information of the first G-RNTI
  • the transceiver unit is also used for: the third network device receives the first G-RNRI from the core network device; or, the processing unit is also used for: determining the first G-RNTI based on the identifier of the first multicast session.
  • the first cell is a cell managed by a third network device.
  • the transceiver unit is also used to: receive second indication information from a fourth network device, the second indication information being used to indicate a change in the status of a first multicast session provided by a first cell, the first cell being a cell managed by the fourth network device.
  • a communication device which may be a fourth network device, or may be a component (such as a chip or circuit) of the fourth network device, and this application does not limit this.
  • the device may include: a transceiver unit, used to send second indication information to a third network device, the second indication information is used to indicate the status of a first multicast session in a non-connected state or an idle state provided by a first cell, and the first cell is a cell managed by a second network device; the transceiver unit is also used to: send a second message, the second message includes the first indication information, and the first indication information is used to indicate the status of a first multicast session in a non-connected state or an idle state provided by the first cell.
  • the status of the first multicast session includes: the first cell is providing or not providing the first multicast session in the RRC inactive state or idle state, or the first cell starts or stops providing the first multicast session in the RRC inactive state or idle state; or the multicast configuration information corresponding to the first multicast session changes.
  • the transceiver unit is also used to: send sixth information to a third network device, the sixth information including M multicast configuration information and index information corresponding to the M multicast configuration information; or, the sixth information including M multicast configuration information, M is a positive integer; receive eighth information from the third network device, the first information including at least one multicast configuration information and index information corresponding to at least one multicast configuration information, and the at least one multicast configuration information including M multicast configuration information.
  • a communication apparatus which may be executed by a terminal device, or may be a component of the terminal device (such as a chip or circuit), which is not limited in the present application.
  • the apparatus may include: a transceiver unit, configured to receive first multicast configuration information and tenth information from a fifth network device, the first multicast configuration information being used to configure a first multicast session, and the tenth information being used to indicate an effective area of the first multicast configuration information; and a processing unit, configured to receive the first multicast session in an inactive state or an idle state of a wireless resource control RRC according to the first multicast configuration information within the effective area.
  • a transceiver unit configured to receive first multicast configuration information and tenth information from a fifth network device, the first multicast configuration information being used to configure a first multicast session, and the tenth information being used to indicate an effective area of the first multicast configuration information
  • a processing unit configured to receive the first multicast session in an inactive state or an idle state of a wireless resource control RRC according to the first multicast configuration information within the effective area.
  • a communication device which may be a fifth network device, or may be a component (such as a chip or circuit) of the fifth network device, and this application does not limit this.
  • the device may include: a transceiver unit, used to send a third message to the first device, the third message is used to request multicast configuration information of the first multicast session; the transceiver unit is also used to: receive first multicast configuration information from the first device, the first multicast configuration information is determined according to the third message and the value range of the multicast configuration parameter, the first multicast configuration information is used to configure the terminal device to receive the first multicast session in the wireless resource control RRC inactive state or idle state.
  • a transceiver unit used to send a third message to the first device, the third message is used to request multicast configuration information of the first multicast session
  • the transceiver unit is also used to: receive first multicast configuration information from the first device, the first multicast configuration information is determined according to the third message and the value range of the multicast configuration parameter, the first multicast configuration information is used to configure the terminal device to receive the first multicast session in the wireless resource control RRC inactive state or idle state.
  • the transceiver unit is further used to: send first multicast configuration information to the terminal device.
  • the value range of the multicast configuration parameter includes at least one of the following: the value range of G-RNTI, the value range of the multicast radio bearer MRB identifier, the value range of the logical channel LCH identifier, the value range of the physical channel configuration parameter, the value range of the discontinuous reception DRX configuration parameter, and the value range of the common frequency domain resource CFR configuration parameter.
  • the third message includes at least one of the following: an identifier of the first multicast session, the number of MRBs required for the first multicast session, and the number of logical channels LCH required for the first MRB of the first multicast session.
  • the third message includes an identifier of a second cell
  • the second cell is a cell managed by a fifth network device and providing a first multicast session in an RRC inactive state or an idle state.
  • the transceiver unit is further used to: receive tenth information from the first device, the tenth information indicating an effective area of the first multicast configuration information.
  • the transceiver unit is further used to: send a fourth message to the first device, the fourth message including a value range of the multicast configuration parameter.
  • the fourth message also includes identification information of the second area, and the second area is an effective area of the value range of the multicast configuration parameter.
  • the cell within the second area provides at least one multicast session, at least one multicast session includes a first multicast session, the multicast configuration information of other multicast sessions in the at least one multicast session except the first multicast session is different from the first multicast configuration information, and the multicast configuration information of at least one multicast session is different from each other.
  • the second area is a notification area RNA based on a wireless access network where the fifth network device is located.
  • the transceiver unit is also used to: send an eleventh message to the first device, and the eleventh message is used to instruct the third cell managed by the fifth network device to stop providing the first multicast session in the radio resource control RRC inactive state or idle state.
  • a communication apparatus which may be a first device, or may be a component of the first device (such as a chip or circuit), which is not limited in the present application.
  • the apparatus may include: a transceiver unit, configured to receive a third message from a fifth network device, the third message being used to request multicast configuration information of a first multicast session; a processing unit, configured to determine first multicast configuration information based on the third message and a value range of a multicast configuration parameter, the first multicast configuration information being used to configure a terminal device to receive the first multicast session in an inactive or idle state of a radio resource control RRC; the transceiver unit is further configured to send the first multicast configuration information to the fifth network device.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the G-RNTI
  • the processing unit is specifically used to: select a value from the value range of the G-RNTI as the G-RNTI of the first multicast session, and the first multicast configuration information includes the G-RNTI of the first multicast session.
  • the third message includes an identifier of the first multicast session and the number X of multicast radio bearer MRBs required for the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the MRB identifier
  • the processing unit is specifically used to: select X values from the value range of the MRB identifier as the MRB identifier of the first multicast session, the first multicast configuration information includes the MRB identifier of the first multicast session, and X is a positive integer.
  • the third message includes an identifier of the first multicast session and the number Y of logical channels LCH required by the first MRB of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the LCH identifier
  • the processing unit is specifically used to: select Y values from the value range of the LCH identifier as the LCH identifier of the first MRB
  • the first multicast configuration information includes the LCH identifier of the first MRB
  • Y is a positive integer.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the physical channel configuration parameter
  • the processing unit is specifically used to: select at least one value from the value range of the physical channel configuration parameter as the physical channel configuration parameter of the first multicast session, and the first multicast configuration information includes the physical channel configuration parameter of the first multicast session.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the discontinuous reception DRX configuration parameter
  • the processing unit is specifically used to: select at least one value from the value range of the DRX configuration parameter as the DRX configuration parameter of the first multicast session, and the first multicast configuration information includes the DRX configuration parameter of the first multicast session.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes a value range of a common frequency domain resource CFR configuration parameter
  • the processing unit is specifically used to: select at least one value from the value range of the CFR configuration parameter as the CFR configuration parameter of the first multicast session, and the first multicast configuration information includes the first group CFR configuration parameters for the broadcast session.
  • the third message includes an identifier of a second cell
  • the second cell is a cell managed by a fifth network device and provides a first multicast session in an RRC inactive state or idle state
  • the processing unit is also used to: determine the tenth information based on the third message from one or more fifth network devices, and the tenth information is used to indicate the effective area of the first multicast configuration information.
  • the transceiver unit is further used to: send tenth information to the fifth network device.
  • the transceiver unit is further used to: receive a fourth message from a fifth network device, the fourth message including a value range of a multicast configuration parameter.
  • the fourth message also includes identification information of the second area, and the second area is an effective area of the value range of the multicast configuration parameter.
  • the cell within the second area provides at least one multicast session
  • the at least one multicast session includes a first multicast session
  • the processing unit is further used to: determine different multicast configuration information for the at least one multicast session.
  • the multicast configuration information of the other multicast sessions in the at least one multicast session except the first multicast session is different from the first multicast configuration information.
  • the second area is a notification area RNA based on a wireless access network where the fifth network device is located.
  • the transceiver unit is also used to: receive an eleventh information from a fifth network device, the eleventh information being used to instruct the third cell managed by the fifth network device to stop providing the first multicast session in an inactive or idle state of the radio resource control RRC; the processing unit is also used to: remove the third cell from the effective area of the first multicast configuration information.
  • the first multicast configuration information includes at least one of the following: G-RNTI, MRB configuration, CFR configuration, DRX configuration, and physical channel configuration of the first multicast session.
  • a communication device comprising: at least one processor, configured to execute a computer program or instruction stored in a memory, so as to execute the method in any possible implementation of the first aspect to the ninth aspect.
  • the device further comprises a memory, configured to store a computer program or instruction.
  • the device further comprises a communication interface, and the processor reads the computer program or instruction stored in the memory through the communication interface.
  • the apparatus is a terminal device or a first network device.
  • the apparatus is a chip, a chip system or a circuit for a terminal device or a first network device.
  • the present application provides a processor for executing the methods provided in the first to ninth aspects above.
  • a computer-readable storage medium which stores a program code for execution by a device, and the program code includes a method for executing any possible implementation of the first to ninth aspects above.
  • a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute a method in any possible implementation of the first to ninth aspects above.
  • a communication system comprising the third network device of the eleventh aspect and the fourth network device of the twelfth aspect, or comprising the third network device of the fourteenth aspect and the fourth network device of the fifteenth aspect.
  • a communication method comprising the method executed by the fifth network device of the eighth aspect and the method executed by the first device of the ninth aspect.
  • the method includes: the fifth network device sends a third message to the first device, the third message is used to request multicast configuration information of the first multicast session; the first device determines the first multicast configuration information based on the third message and the value range of the multicast configuration parameter, the first multicast configuration information is used to configure the terminal device to receive the first multicast session in the radio resource control RRC inactive state or idle state; the first device sends the first multicast configuration information to the fifth network device.
  • FIG1 shows a schematic diagram of a wireless communication system applicable to an embodiment of the present application.
  • FIG. 2 shows schematic diagrams of several architectures applicable to embodiments of the present application.
  • FIG. 3 shows another schematic diagram of a scenario applicable to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of transmission resources for information of a multicast broadcast session.
  • FIG5 is a schematic diagram of a communication method 200 provided in an embodiment of the present application.
  • FIG. 6 is a schematic diagram of the structure of TMGI.
  • FIG. 7 is a schematic diagram of a communication method 300 provided in an embodiment of the present application.
  • FIG8 is a schematic diagram of a communication method 400 provided in an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a communication method 500 provided in an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a communication method 600 provided in an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a communication method 700 provided in an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a communication method 800 provided in an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a communication method 900 provided in an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a communication device 2800 provided in an embodiment of the present application.
  • FIG. 15 is a schematic diagram of another communication device 2900 provided in an embodiment of the present application.
  • FIG. 16 is a schematic diagram of a chip system 3000 provided in an embodiment of the present application.
  • the technical solution provided in this application can be applied to various communication systems, such as: the fifth generation (5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • the technical solution provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solution provided in this application can also be applied to device to device (D2D) communication, vehicle to everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of things (IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle to everything
  • M2M machine to machine
  • MTC machine type communication
  • IoT Internet of things
  • V2X may include vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), and vehicle-to-infrastructure (V2I), where the infrastructure is, for example, a road side unit (RSU) or a network device.
  • V2V vehicle-to-vehicle
  • V2P vehicle-to-pedestrian
  • V2I vehicle-to-infrastructure
  • RSU road side unit
  • network device for example, a network device.
  • the method provided in the embodiments of the present application is applicable to but not limited to the following fields: MBMS, SC-PTM, multicast broadcast service, MBSFN, dual-channel intelligent unicast (DC-IU), Broadcast, Multicast, Multicast Broadcast, Groupcast, V2X, public safety, mission critical, transparent IPv4/IPv6 multicast delivery, IPTV, software delivery over wireless, group communication, etc. ications), Internet of things (IoT), TV Video, TV, linear TV, Live, radio services, device to device (D2D), unmanned driving, automated driving (ADS), driver assistance (ADAS), intelligent driving, connected driving, intelligent network driving, car sharing, etc.
  • IoT Internet of things
  • TV Video TV, linear TV, Live, radio services, device to device (D2D), unmanned driving, automated driving (ADS), driver assistance (ADAS), intelligent driving, connected driving, intelligent network driving, car sharing, etc.
  • the terminal devices in the embodiments of the present application include various devices with wireless communication functions, which can be used to connect people, objects, machines, etc.
  • the terminal devices can be widely used in various scenarios, such as: cellular communication, D2D, V2X, peer to peer (P2P), M2M, MTC, IoT, virtual reality (VR), augmented reality (AR), industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery, etc.
  • the terminal device can be a terminal in any of the above scenarios, such as an MTC terminal, an IoT terminal, etc.
  • the terminal device may be a user equipment (UE), terminal, fixed device, mobile station device or mobile device of the third generation partnership project (3GPP) standard, a subscriber unit, a handheld device, a vehicle-mounted device, a wearable device, a cellular phone, a smart phone, a SIP phone, a wireless data card, a personal digital assistant (PDA), a computer, a tablet computer, a notebook computer, a wireless modem, a handheld device (handset), a laptop computer, a computer with wireless transceiver function, a smart book, a vehicle, a satellite, a global positioning system (GPS), or a wireless communication device.
  • 3GPP third generation partnership project
  • GPS Global System for Mobile Communications
  • target tracking equipment aircraft (such as drones, helicopters, multi-copters, quadcopters, or airplanes, etc.), ships, remote control equipment, smart home equipment, industrial equipment, or devices built into the above equipment (for example, communication modules, modems or chips in the above equipment, etc.), or other processing devices connected to wireless modems.
  • aircraft such as drones, helicopters, multi-copters, quadcopters, or airplanes, etc.
  • remote control equipment smart home equipment
  • industrial equipment for example, communication modules, modems or chips in the above equipment, etc.
  • devices built into the above equipment for example, communication modules, modems or chips in the above equipment, etc.
  • other processing devices connected to wireless modems for the convenience of description, the terminal device is described below by taking the terminal or UE as an example.
  • the UE can also be used to act as a base station.
  • the UE can act as a scheduling entity that provides sidelink signals between UEs in scenarios such as V2X, D2D or P2P.
  • the device for realizing the function of the terminal device can be the terminal device, or a device that can support the terminal device to realize the function, such as a chip system or a chip, which can be installed in the terminal device.
  • the chip system can be composed of a chip, or it can include a chip and other discrete devices.
  • the network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may also be referred to as an access network device or a wireless access network device, such as a base station.
  • the network device in the embodiment of the present application may refer to a wireless access network (RAN) node (or device) that connects a terminal device to a wireless network.
  • RAN wireless access network
  • Base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting point (TRP), transmitting point (TP), master station, auxiliary station, multi-standard wireless (motor slide retainer, MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc.
  • NodeB evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting point (TRP), transmitting point (TP), master station, auxiliary station, multi-standard wireless (motor slide retainer, MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node,
  • the base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof.
  • the base station may also refer to a communication module, modem or chip used to be set in the aforementioned equipment or device.
  • the base station may also be a mobile switching center and a device that performs the base station function in D2D, V2X, and M2M communications, a network-side device in a 6G network, and a device that performs the base station function in a future communication system.
  • the base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form used by the network equipment.
  • Base stations can be fixed or mobile.
  • a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station.
  • a helicopter or drone can be configured to act as a device that communicates with another base station.
  • the network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on aircraft, balloons and satellites in the air.
  • the embodiments of the present application do not limit the scenarios in which the network equipment and terminal equipment are located.
  • the network device in the embodiments of the present application may also be a module or unit that performs part of the functions of the base station, for example, it may be a CU in a cloud radio access network (C-RAN) system, or it may be a DU.
  • C-RAN cloud radio access network
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the network device. All or part of the functions of the network device may also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform). In this application, unless otherwise specified, the network device refers to a radio access network device.
  • CU can decouple the user plane and control plane to form CU-Control Plane (CU-CP) and CU-User Plane (CU-UP).
  • CU-CP and CU-UP support flexible deployment.
  • wireless communication may also be referred to as “communication”
  • communication may also be described as “data transmission”, “information transmission” or “transmission”.
  • terminal equipment is also referred to as “terminal device”, “terminal”, etc.
  • network equipment is also referred to as “network device”, “network side”, etc.
  • core network equipment is also referred to as “core network device”, “core network”, etc.
  • FIG1 shows a schematic diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system 100 may include at least one network device, such as the network device 110 shown in FIG1 , and the wireless communication system may also include at least one terminal device, such as the terminal device 120 and the terminal device 130 shown in FIG1 .
  • Both the network device and the terminal device may be configured with multiple antennas, and the network device and the terminal device may communicate using multi-antenna technology.
  • the terminal device 120 and the terminal device 130 may communicate directly or through the network device 110.
  • the network device can manage one or more cells.
  • a cell can have one or multiple terminal devices.
  • the network device and the terminal device form a single-cell communication system, and without loss of generality, the cell is referred to as cell #1.
  • the network device 110 in FIG. 1 may be a network device in cell #1, or the network device 110 may serve a terminal device (e.g., terminal device 120) in cell #1.
  • a cell can be understood as an area within the coverage of wireless signals of network equipment.
  • the present application can also be used in dual connectivity (DC) scenarios, including but not limited to the evolved universal terrestrial radio access network (EUTRAN) and NR network dual connectivity (EUTRAN-NR dual connectivity, EN-DC) scenarios, and NR network dual connectivity (NR-NR dual connectivity, NR-DC or NR-NR-DC) scenarios.
  • DC dual connectivity
  • EUTRAN evolved universal terrestrial radio access network
  • EUTRAN-NR dual connectivity EN-DC
  • NR network dual connectivity NR-NR dual connectivity, NR-DC or NR-NR-DC
  • FIG2 shows another schematic diagram of several architectures applicable to the embodiments of the present application.
  • the scenario is a 5G system architecture diagram.
  • the RAN in 5G can be called the next generation RAN (NG-RAN).
  • NG-RAN includes two types, namely gNB and the next generation eNB (NG-eNB) based on LTE evolution.
  • Both types of access network devices can be connected to the 5G core network (5G core, 5GC).
  • 5GC includes multiple network elements, including but not limited to access and mobility management function (AMF) and user plane function (UPF).
  • AMF access and mobility management function
  • UPF user plane function
  • access network devices can communicate with each other through the Xn interface
  • access network devices and 5G core network can communicate with each other through the NG interface.
  • the protocol definition For details of the relevant architecture, please refer to the protocol definition.
  • CA carrier aggregation
  • multiple cell groups can serve terminal devices, that is, multiple component carriers (CCs) can be aggregated together to improve the terminal peak rate and system capacity to meet the increasingly high network rate requirements of terminals.
  • CA has two important concepts: the primary component carrier under the primary cell (Pcell) and the secondary component carrier under the secondary cell (Scell).
  • RRC radio resource control
  • the secondary cell may be configured to provide additional wireless resources for data transmission to improve system capacity.
  • this scenario is a scenario in which CU and DU are deployed separately.
  • the network device includes CU and DU, CU is used to communicate with the core network, and DU is used to communicate with the terminal device.
  • this scenario is a scenario in which CU-CP, CI-UP, and DU are deployed separately.
  • the network equipment includes CU-CP, CI-UP, and DU.
  • CU-CP is used to communicate with the control plane of the core network
  • CU-UP is used to communicate with the user plane of the core network
  • DU is used to communicate with the terminal device.
  • Figure 3 shows another schematic diagram of a scenario applicable to an embodiment of the present application.
  • a network device can manage multiple cells, wherein cell #1 is a primary cell of a terminal device, and cells #2, #3, and #4 are secondary cells of the terminal device, and CCs of cells #1, #2, #3, and #4 can jointly provide services for the terminal device through CA technology.
  • RRC idle state There are three RRC states for terminal devices in NR: RRC idle state, RRC inactive state and RRC connected state.
  • RRC connected state (referred to as the connected state) an RRC connection is established between the terminal device and the network device.
  • the network device can release the terminal device to the RRC idle state (referred to as the idle state), or release the terminal device to the RRC inactive state and suspend the RRC connection.
  • the RRC idle state no RRC connection is established between the network device and the terminal device (referred to as the inactive state).
  • the network device still maintains the context information of the terminal device.
  • the advantage of introducing the RRC inactive state is that compared to the RRC idle state, since the network device still retains the terminal device context in the RRC inactive state, the RRC connection can be restored more quickly, and when a service arrives, the latency can be reduced.
  • CN core network
  • TA tracking area identity
  • CN-initiated paging can be referred to as CN paging.
  • a range smaller than the TA range is introduced for terminal devices in the RRC inactive state, namely, the RAN-based Notification Area (RNA).
  • RNA RAN-based Notification Area
  • a TA range can include multiple RNAs, and an RNA can include multiple cells.
  • the RNA is managed by the network device, and the network device can send paging messages to cells within the RNA range.
  • the network device-initiated paging (RAN-initiated paging) can be referred to as RAN paging.
  • RAN paging when the last serving gNB of the terminal device receives downlink data from UPF or downlink signaling from AMF, it will page the terminal device in the cell within the RNA area, and if the RNA area includes the cell of the neighboring network device, the last serving gNB will transmit the RAN paging to the neighboring network device through the Xn interface, and the neighboring network device will page the terminal device in its cell.
  • the terminal device in the RRC inactive state or RRC idle state will trigger RRC resume or RRC connection establishment.
  • Multicast and broadcast service (MBS)
  • MBS can provide data to a large number of users with the same needs at the same time with fewer resources, so that network resources can be shared.
  • MBS includes multicast services and broadcast services.
  • Broadcast services refer to communication services in which network devices provide the same specific content data to all terminal devices in a certain geographical area at the same time.
  • Multicast services refer to communication services provided by network devices to a group of terminal devices that join a multicast session. Multicast services can be sent to terminal devices through multicast sessions. Terminal devices that receive multicast can only receive multicast services after performing an authentication process with the core network. The authentication process can also be understood as the process of terminal devices joining a multicast session. Therefore, receiving multicast services can also be said to receive multicast sessions or MBS sessions (MBS sessions).
  • MBS sessions MBS sessions
  • MBS sessions can be identified by temporary mobile group identities (TMGI).
  • Multicast services can also be called multicast services.
  • “multicast” and “multicast” can be replaced with each other, multicast sessions and multicast services can be replaced with each other, and the identification of multicast services, the identification of multicast sessions, and TMGI can be replaced with each other without restriction.
  • MBS control channel MCCH
  • MBS traffic channel MTCH
  • MCCH is used to transmit control information, including the configuration information of MTCH, such as the group radio network temporary identifier (G-RNTI) and discontinuous reception (DRX) parameters corresponding to MTCH.
  • G-RNTI group radio network temporary identifier
  • DRX discontinuous reception
  • MCCH is sent in a periodic manner.
  • the MTCH logical channel is used to carry user data of broadcast services.
  • MTCH is scheduled through MCCH.
  • MTCH is configured at the level of per g-RNTI, or per MBS service.
  • the base station schedules service data to multiple UEs at the same time through g-RNTI, and each g-RNTI can be associated with at least one broadcast service.
  • the above channels may correspond to different names.
  • the multicast broadcast service control channel may be a single cell multicast broadcast service control channel (single cell MCCH, SC-MCCH).
  • the multicast broadcast service control channel may be MC-MCCH.
  • channels with similar functions to the multicast broadcast service control channel may have other names, or, in different communication environments, communication scenarios or communication technologies, channels with the same functions may also have different names, but the different names of channels with similar or identical functions in different systems do not limit the channel content and function.
  • the multicast broadcast control channel in this application can be used to transmit control information, and the multicast broadcast service channel can be used to transmit user data.
  • MCCH is used in this application to represent a multicast broadcast service control channel
  • MTCH is used to represent a multicast broadcast service channel
  • MCCH is repeatedly transmitted in each modification period (MP), including the repetition period (RP).
  • MP modification period
  • RP repetition period
  • the content of MCCH is the same, that is, the same MCCH will be repeatedly transmitted several times according to the scheduled repetition period.
  • the network device sends a PDCCH containing an MCCH change notification.
  • the UE detects the field corresponding to MCCH change Notification on the PDCCH, such as 2 bits, it is considered that a change notification is detected, and the UE re-acquires the MCCH.
  • the UE needs to detect the PDCCH scrambled by MCCH-RNTI to obtain the scheduling information of the MCCH.
  • the first bit in the MCCH change notification indicates that the reason for the MCCH modification is the start of a session
  • the second bit in the MCCH change notification indicates that the reason for the MCCH modification is a session modification, a session stop, or an update of the neighboring cell list.
  • the MCCH change period is greater than or equal to the MCCH repetition period.
  • the protocol data unit (PDU) session includes a PDU session for transmitting unicast and a PDU session for transmitting MBS.
  • the PDU session for transmitting MBS can also be called an MBS session.
  • the core network When the core network establishes a PDU session, in order to ensure the quality of service provided by the PDU session, it will establish one or more QoS flows.
  • Each QoS flow has corresponding QoS parameters (such as 5G QoS Identifier (5G QoS Identifier, 5QI), Allocation and Retention Priority (Allocation and Retention Priority, ARP), etc.).
  • NG-RAN determines the QoS flow and radio bearer (including DRB) according to the QoS parameters (QoS profiles and QFI). and MRB).
  • a PDU session can correspond to one or more QoS flows, and a QoS flow can correspond to one or more radio bearers, which is determined by the implementation strategy of NG-RAN.
  • the Service Data Adaptation Protocol (SDAP) layer handles the mapping of QoS flows and radio bearers on the downlink sending side (NG-RAN).
  • SDAP Service Data Adaptation Protocol
  • the data packets on a radio bearer are processed by the Packet Data Convergence Control (PDCP) layer (for example, header compression, integrity protection, encryption/decryption, etc.) and come to the Radio Link Control (RLC) layer.
  • PDCP Packet Data Convergence Control
  • RLC Radio Link Control
  • a PDCP entity can correspond to one, two or four RLC entities.
  • the RLC entity will segment and reassemble the RLC service data unit (SDU) from the PDCP layer, form an RLC PDU and put it into the corresponding logical channel.
  • One RLC entity corresponds to one logical channel.
  • the MAC layer multiplexes the RLC PDU (also called MAC SDU) from one or more logical channels into a data block (TB) and submits it to the physical channel for physical layer transmission.
  • the MAC header includes the logical channel identifier for receiving the RLC PDU.
  • the receiving side (UE) will process in the opposite way. After receiving the TB, the MAC layer will be responsible for demultiplexing the TB.
  • the logical channel identifiers corresponding to the one or more MAC SDUs can be obtained.
  • the UE can obtain the identifier of the logical channel corresponding to a wireless bearer to ensure that the UE's MAC layer will deliver the RLC PDU obtained from a certain logical channel to the correct RLC entity, corresponding to the corresponding PDCP entity and wireless bearer.
  • MBS broadcast configuration adopts a two-step configuration method.
  • the network device indicates the MCCH configuration for MBS broadcast in the system message, such as system information block (SIB) 20, including the repetition period and offset of MCCH, the duration of MCCH window, the starting time slot of MCCH window, and the MCCH change period.
  • SIB system information block
  • MCCH can be received.
  • MCCH (or the information sent through the MCCH channel) is transmitted periodically, with a configured repetition period, and within the configured MCCH transmission window.
  • MCCH includes the configuration information of the broadcast session and the MTCH scheduling information.
  • the configuration information of the broadcast session includes the identifier of the broadcast session, the MBS radio bearer (MRB) configuration, G-RNTI, etc.
  • MBS radio bearer (MRB) configuration After reading the configuration information and MTCH scheduling information of the broadcast session, the terminal device can correctly receive the MBS broadcast session.
  • MBS radio bearer (MRB) configuration After reading the configuration information and MTCH scheduling information of the broadcast session, the terminal device can correctly receive the MBS broadcast session.
  • a terminal device that is interested in receiving MBS broadcast services should perform the MCCH information acquisition process.
  • a terminal device that is interested in receiving MBS broadcast services should perform the MCCH information acquisition process when entering a cell that provides SIB20. For example, when a terminal device that is receiving or interested in receiving MBS broadcast services receives a change notification, it will re-acquire SIB 20 to obtain a new MCCH. Before the terminal device obtains new MCCH information, the terminal device will apply the previously acquired MCCH information. For another example, since MCCH is configured per cell, the MBS configuration carried by the MCCH of each cell may be different.
  • MBS broadcast supports the use of MCCH change notifications to notify the UE of the start of a broadcast session, as well as changes to the MCCH information of an ongoing broadcast session, including the termination of an MBS session.
  • the terminal device receives the multicast session in the RRC connected state.
  • the network device sends the MBS multicast configuration to the terminal device through dedicated signaling, such as RRC reconfiguration message (RRCReconfiguration message), for example, including multicast MRB configuration, multicast common frequency resource (CFR) configuration, physical layer configuration (also called layer 1/L1 configuration), multicast G-RNTI, etc.
  • RRC reconfiguration message RRCReconfiguration message
  • multicast MRB configuration multicast common frequency resource (CFR) configuration
  • CFR multicast common frequency resource
  • PCRF physical layer configuration
  • multicast G-RNTI multicast G-RNTI
  • Rel-18 supports terminal devices receiving multicast in the RRC inactive state. For example, when the terminal device has no unicast service but only multicast service, the network can release the terminal device to the RRC inactive state to receive multicast. In this way, the number of terminal devices in the RRC connected state in the network can be reduced, which is beneficial to alleviate network congestion and energy saving of terminal devices.
  • the protocol does not define how a terminal device obtains the MBS configuration in the RRC inactive state.
  • the terminal device needs to obtain a multicast configuration so that it can receive the multicast session according to the multicast configuration.
  • the multicast configuration is provided to the terminal device through the system message broadcast by the cell.
  • the multicast configuration is sent to the terminal device in MCCH in a similar way to the above broadcast session.
  • the MCCH configuration can still indicate MCCH in SIB.
  • the terminal device that has not joined the multicast session can also receive the multicast configuration, which poses a potential security risk.
  • the terminal device when the terminal device reselects the cell, it needs to re-read the MCCH to obtain the multicast configuration before it can continue to receive the multicast service. There is a certain delay in the configuration and interpretation, which is not conducive to the continuity of multicast service reception.
  • the network device sends the multicast configuration to the terminal device through dedicated signaling (such as RRC reconfiguration message or RRC release message, etc.).
  • the terminal device needs to restore the RRC connection.
  • the network device can send the multicast configuration to the terminal device through dedicated signaling.
  • the terminal device enters the RRC connection state to receive the multicast configuration, which will increase the energy consumption of the terminal device and also increase the air interface signaling overhead.
  • the present application provides a communication method and apparatus, which can prevent the terminal device from entering the RRC connection state or triggering RRC recovery in scenarios such as cell reselection or multicast configuration update, thereby reducing the energy consumption of the terminal device and reducing signaling overhead.
  • indication can include direct indication, indirect indication, explicit indication, implicit indication.
  • indication information can include direct indication, indirect indication, explicit indication, implicit indication.
  • correlate and “association” in this application refer to a corresponding relationship or mapping relationship between the two.
  • the corresponding relationship can also be one-to-one, one-to-many, or many-to-one.
  • the information indicated by the indication information is referred to as the information to be indicated.
  • the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated.
  • the information to be indicated can also be indirectly indicated by indicating other information, wherein there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance.
  • the indication of specific information can also be achieved with the help of the arrangement order of each information agreed in advance (such as specified by the protocol), thereby reducing the indication overhead to a certain extent.
  • Fig. 5 is a schematic diagram of a communication method 200 provided in an embodiment of the present application.
  • the method 200 may include the following steps.
  • the first network device sends first information to the terminal device, and correspondingly, the terminal device receives the first information.
  • the first information includes at least one multicast configuration information and index information corresponding to the at least one multicast configuration information, the at least one multicast configuration information includes the first multicast configuration information, and the index information corresponding to the at least one multicast configuration information includes the first index information.
  • the multicast configuration information and the corresponding index information are shown in Table 1 below.
  • Table 1 shows a mapping relationship between multicast configuration and index
  • Table 1 takes three configurations as an example, and the actual number is not limited. What is shown here is the logical correspondence between the configuration and the index.
  • the index information corresponding to at least one multicast configuration information can be indicated in an explicit or implicit manner.
  • the multicast configuration and the corresponding index are indicated in the first information at the same time, for example, according to the above table, multicast configuration 1, index 1, multicast configuration 2, index 2, multicast configuration 3, index 3 are indicated;
  • the first information only indicates a list of multicast configurations, and the index of the multicast configuration is obtained according to the order of at least one multicast configuration in the multicast configuration list, for example, the multicast configuration in the first row of the multicast configuration list corresponds to index 1, and the multicast configuration in the second row corresponds to index 2.
  • the value of the index information corresponding to the multicast configuration may be any value, and the present invention does not limit the value range of the index information, nor does it limit the value of the index information to be continuous.
  • the first network device when determining the index associated with each multicast configuration, may not arrange them in order, but randomly assign them within a certain index range. For example, if the first network device needs to determine indexes for 10 multicast configurations, then these 10 indexes may be discontinuous, that is, not 10 consecutive numbers such as 1 to 10 or 0 to 9, but 10 numbers can be selected at random within a range greater than 10, for example, 10 numbers can be selected at random from 1 to 100000, as shown in Table 2. This can make the index of the multicast configuration random.
  • Table 2 shows a mapping relationship between multicast configuration and index
  • Table 2 takes three configurations as an example, and the actual number is not limited. What is shown here is the logical correspondence between the configuration and the index.
  • the terminal device can compare the index in the second information with the index in the first information. If the index indicated in the second information does not exist in the first information, the second information can be confirmed to be invalid. Based on the above scheme, when there is a fake base station sending the second information and indicating an index, the terminal device can recognize that the index is invalid. For example, the mapping relationship between the multicast configuration indicated in the first information obtained by the terminal device through dedicated signaling and the index is shown in Table 2.
  • cell 1 When the UE resides in cell 1, cell 1 sends the second information indicating that the first multicast session is associated with index 4997, corresponding to multicast configuration 1; when there is a fake base station in the area, indicating that cell 1 has changed the multicast configuration of the first multicast session, and sends the second information indicating that the first multicast session is associated with index 1, the terminal device can determine that index 1 is not the index indicated in the first information, and therefore determines that the multicast configuration of cell 1 has not changed, and still receives the first multicast session according to the multicast configuration associated with index 4997. Through this method, communication security can be improved.
  • the fixed offset value is 500
  • the fixed offset value can be sent to the terminal device through the first information.
  • the fixed offset value can be configured for each multicast session, and different multicast sessions can be configured with different fixed offset values.
  • Table 3 shows a mapping relationship between multicast configuration and index
  • Table 3 takes three configurations as an example, and the actual number is not limited. What is shown here is the logical correspondence between the configuration and the index.
  • the multicast configuration information is also called MBS multicast configuration information or multicast configuration, which refers to the configuration parameters for receiving multicast sessions in MBS.
  • the multicast configuration information in this application refers to the multicast configuration of the terminal device in the RRC inactive state or idle state, which is used for the terminal device to receive multicast sessions in the RRC inactive state or idle state.
  • the multicast configuration information may include one or more of the following: multicast MRB configuration, physical channel configuration, discontinuous reception DRX configuration, G-RNTI configuration, neighboring cell configuration, common frequency resource (CFR) configuration, and each of the multicast MRB configuration, physical channel configuration, discontinuous reception DRX configuration, G-RNTI configuration, neighboring cell configuration, CFR configuration, and semi-persistent scheduling (SPS) configuration may be referred to as a sub-configuration.
  • the physical channel configuration includes one or more of the following: physical downlink control channel (PDCCH) configuration, physical downlink shared channel (PDSCH) configuration, PDCCH occasion configuration, SSB mapping window configuration, search space configuration, and common control resource set configuration.
  • MRB configuration includes one or more of the following: MRB identification, Packet Data Convergence Protocol (PDCP) configuration, Radio Link Control (RLC) bearer configuration.
  • CFR configuration includes: CFR bandwidth and location.
  • Index information is also called identification information (identifier, ID) or index.
  • An index information can be an index or an index set.
  • An index set includes one or more sub-indexes.
  • an index information is composed of one or more of the MRB configuration index, physical channel configuration index, DRX configuration index, neighbor cell configuration index, CFR configuration index, and SPS configuration index, wherein each of the MRB configuration index, physical channel configuration index, DRX configuration index, neighbor cell configuration index, CFR configuration index, and SPS configuration index can be called a sub-index.
  • the above multiple indexes can be flexibly combined, which has greater flexibility.
  • An index information is an index set, including one or more sub-indexes.
  • at least one multicast configuration includes ⁇ group multicast configuration A, multicast configuration B, multicast configuration C ⁇ ; wherein the first multicast configuration information is multicast configuration A, and the configuration information of multicast configuration A can be a configuration information list, the list including ⁇ multicast configuration A_multicast MRB configuration list, multicast configuration A_physical channel configuration list, multicast configuration A_DRX configuration list, multicast configuration A_G-RNTI configuration list, multicast configuration A_neighboring cell configuration list, multicast configuration A_CFR configuration list, multicast configuration A_SPS configuration list ⁇ or a combination including at least one of them.
  • the first index information corresponding to the first multicast configuration information includes ⁇ multicast configuration A_multicast MRB configuration index, multicast configuration A_physical channel configuration index, multicast configuration A_DRX configuration index, multicast configuration A_G-RNTI configuration, multicast configuration A_neighboring cell configuration index, multicast configuration A_CFR configuration index, multicast configuration A_SPS configuration index ⁇ .
  • An index information is an index.
  • at least one multicast configuration includes ⁇ multicast configuration A, multicast configuration B, multicast configuration C ⁇ ; wherein the first multicast configuration information is multicast configuration A, corresponding to the first index information; the configuration information of multicast configuration A includes ⁇ multicast configuration A_multicast MRB configuration, multicast configuration A_physical channel configuration, multicast configuration A_DRX configuration, multicast configuration A_G-RNTI configuration, multicast configuration A_neighboring cell configuration, multicast configuration A_CFR configuration, multicast configuration A_SPS configuration ⁇ .
  • the first information includes at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, that is, the first information includes a multicast configuration list.
  • each multicast configuration information corresponds to an index information.
  • one or more multicast configuration information includes the first multicast configuration information
  • the first multicast configuration information corresponds to the first index information.
  • the index information corresponding to the one or more multicast configuration information includes the first index information.
  • the multicast configuration list may be a list, and the multiple items in the list correspond to one item in the multicast configuration information.
  • the multicast configuration list may also be composed of multiple sub-lists, for example, the multicast configuration list includes one or more items in the MRB configuration list, the physical channel configuration list, the DRX configuration list, the neighbor cell configuration list, the CFR configuration list, and the SPS configuration list.
  • each sub-list may correspond to a sub-index, that is, one index information is composed of multiple sub-indexes, and through the multiple sub-indexes, one multicast configuration information may correspond.
  • the multicast configuration information can be associated with a specific multicast session, and each multicast configuration information can also be associated with one or more multicast sessions, that is, multiple multicast sessions can share the same multicast configuration information.
  • each multicast session can be associated with one or more multicast configurations, that is, each session can have multiple multicast configurations to apply to different scenarios.
  • At least one multicast configuration in the first information is a configuration associated with a multicast session joined by the terminal device, that is, the multicast configuration resource pool provided by the first network device to the terminal device includes the multicast configuration resource pool of the multicast session joined by the terminal device.
  • the terminal device when the terminal device joins a new multicast session, the terminal device requests the network device to restore the RRC connection state, and the network device sends updated first information to the terminal device based on the multicast session currently joined by the terminal device.
  • part of the configuration may be a regional common configuration, such as an MRB configuration, and the common configuration may be pre-configured through OAM; part of the configuration may be a Per network device or Per cell configuration, that is, different cells may have different configurations.
  • the network devices within the area need to synchronize the mapping relationship between the multicast configuration information and the index information of the cells within the area.
  • the terminal device may determine the first configuration information through the first index information.
  • the terminal device may determine the first configuration information through the first index information and other information.
  • the other information may be a first identifier
  • the first identifier may be a cell identifier or an identifier of a network device.
  • the terminal device accesses a first multicast session, and the at least one multicast configuration information in the first information includes one or more multicast configuration information of the first multicast session.
  • the first information may be referred to as a multicast configuration resource pool. After receiving the first information, the terminal device may save the first information.
  • the first information is sent by the network device through dedicated signaling when the terminal device is in a connected state.
  • the dedicated signaling can also be called encrypted signaling.
  • the dedicated signaling can be an RRC release message or an RRC reconfiguration message.
  • the second network device sends second information to the terminal device, and correspondingly, the terminal device receives the second information.
  • the second information is used to indicate that the first multicast session is associated with the first index information, and the first index information indicates the first multicast configuration information.
  • the second information is used to indicate that the first multicast session is associated with the first index information.
  • the second information may include an identifier of the first multicast session and the first index information.
  • the identifier of the multicast session may also be called a session ID, which may be a TMGI.
  • the terminal device may obtain the corresponding first multicast configuration information.
  • the second information is sent by the second network device to the terminal device in the managed cell.
  • Each cell may have a corresponding The same or different second information.
  • the second information may be carried in a cell public signaling, and the public signaling is sent in a broadcast form, that is, in an unencrypted form.
  • the public signaling may be a system message of the cell, and the system message may be a system information block (SI) or a system information block (SIB) message, for example, SIB 20, or any other SIB except SIB 20.
  • SIB system information block
  • the public signaling may also be MCCH, that is, a message sent via MCCH.
  • the second information may also be carried in a dedicated signaling, for example, an RRC release message.
  • the MCCH used to send the second information may use the same MCCH-RNTI as the MCCH currently used to indicate the broadcast configuration information, but the two are associated with different logical channels and logical channel identifiers (logical channel, LCID or LCH ID).
  • the MCCH used to send the second information and the MCCH indicating the broadcast configuration information use the same logical channel and logical channel identifier, but are scrambled using different MCCH-RNTIs.
  • the second information and the broadcast configuration information are carried in the same RRC message and on the same MCCH, and an indication that the second information is for multicast is displayed in the message.
  • the RRC release message when the second information is sent via an RRC release message, the RRC release message also instructs the terminal device to enter an RRC inactive state or an idle state to receive the first multicast session.
  • the terminal device before entering the RRC inactive state or the idle state, the terminal device can obtain the first multicast configuration of the resident cell for the first multicast session without obtaining the first multicast configuration by obtaining cell public signaling (such as a system message or an MCCH message), which can reduce the interruption of the terminal device receiving multicast services during the process of switching from the RRC connected state to the RRC inactive state, and improve the continuity of receiving multicast services.
  • cell public signaling such as a system message or an MCCH message
  • the granularity of the second information may also be per multicast session per MRB.
  • the first multicast session is associated with M MRBs, each MRB may be associated with one index information (optionally, including multiple sub-index information), corresponding to the corresponding MBS configuration, and different MRBs may correspond to different index information.
  • the granularity of the second information may also be per multicast session, one multicast session corresponds to one index information, that is, one or more MRBs associated with the multicast session correspond to one index information (optionally, including multiple sub-index information), corresponding to the corresponding MBS configuration.
  • a possible mapping relationship between a multicast session provided by a cell, a configuration of the multicast session, and the index information of the configuration is shown in Table 4.
  • Table 4 shows a mapping relationship between cells, multicast sessions, multicast configurations and indexes
  • S230 The second network device sends the first multicast session to the terminal device according to the first multicast configuration.
  • step S220a in method 200 If step S220a in method 200 is executed, then after S230, the terminal device receives the first multicast session in the RRC inactive state or idle state according to the first multicast configuration.
  • the terminal device can determine the first multicast configuration information corresponding to the first multicast session according to the second information, and then receive the first multicast session according to the first multicast configuration.
  • the first network device pre-configures the multicast configuration resource pool to the terminal device, and the multicast configuration resource pool may include multiple multicast configuration information associated with the first multicast session, and then the second network device may indicate to the terminal device through the second information to receive the first multicast configuration information required for the first multicast session.
  • the first network device pre-configures the multicast configuration resource pool to the terminal device, and the multicast configuration resource pool may include multiple multicast configuration information associated with the first multicast session, and then the second network device may indicate to the terminal device through the second information to receive the first multicast configuration information required for the first multicast session.
  • the common signaling that carries the second information may also include information #A, which may indicate a list of neighboring cells that provide the same multicast session as the current cell, and indicate whether the neighboring cells have the same multicast configuration as the current cell, where the multicast configuration is a configuration for a terminal device to receive the multicast session in an RRC inactive state.
  • information #A may indicate a list of neighboring cells that provide the same multicast session as the current cell, and indicate whether the neighboring cells have the same multicast configuration as the current cell, where the multicast configuration is a configuration for a terminal device to receive the multicast session in an RRC inactive state.
  • the information #A may be indicated for each multicast session (per MBS session) provided by the current cell, for example, for each multicast session TMGI provided by the current cell, information #A indicates a list of cells that provide the multicast session and have the same multicast configuration; or, for each multicast session TMGI, information A# indicates a list of cells that provide the multicast session, and also includes information #B indicating whether each cell in the above cell list has the same multicast configuration. If the configurations of the neighboring cells are the same, the UE reselects the cell to that cell. When a neighboring cell is detected, the UE does not need to re-acquire the SIB or MCCH of the cell. The UE can obtain the configuration information of the neighboring cell in advance, thereby reducing the delay caused by obtaining the configuration and improving the continuity of receiving multicast services.
  • the second network device may be a network device corresponding to the resident cell of the terminal device, that is, the second network device may be a service base station of the terminal device, and the first network device may be understood as an anchor base station of the terminal device, and the first network device stores the context of the terminal device and the core network.
  • the first network device and the second network device may also be the same.
  • the terminal device After receiving the first information, the terminal device performs cell reselection, and the reselected cell is still managed by the first network device.
  • the second network device is the same as the first network device.
  • the steps performed by the first network device described in method 200 may also be performed by the second network device, and the steps performed by the second network device may also be performed by the first network device.
  • the method 200 further includes: the first network device acquires first information.
  • the first information may have an effective area, indicating that within the area, the pre-configured first information is valid, which can be understood as at least one multicast configuration in the first information is valid within the area, or the correspondence between at least one multicast configuration in the first information and the index information of the at least one multicast configuration information is valid.
  • the present application does not limit the cells outside the effective area to provide the same multicast configuration as the cells within the effective area. For cells outside the effective area, the same multicast configuration can be mapped to the same index information, or different index information.
  • the effective area can be a geographical area range, and the effective area can be composed of multiple cells; the effective area can be configured by the open mobile alliance (open mobile alliance, OAM). Multiple network devices within the effective area can coordinate to determine the first information.
  • the first network device obtaining the first information is taken as an example for explanation.
  • the first network device obtaining the first information can be achieved in the following way.
  • the first network device receives the sixth information from the fourth network device, and the sixth information includes M multicast configuration information and index information corresponding to the M multicast configuration information.
  • the first network device determines N multicast configuration information and index information corresponding to the N multicast configuration information.
  • at least one multicast configuration information includes M multicast configuration information and N configuration information, and M and N are both positive integers.
  • the first information includes the sixth information.
  • the sixth information may include identification information of cells or network devices corresponding to the M multicast configuration information.
  • each gNB or a cell of a gNB in the effective area can determine at least one multicast configuration information and index information corresponding to the multicast configuration information.
  • the gNB sends the multicast configuration information, index information, gNB identifier or cell identifier corresponding to each multicast session determined by it to the neighboring gNB through the Xn interface, so that the first information of each gNB in the effective area includes the received multicast configuration information and index information, as well as the multicast configuration information and index information determined by itself.
  • the cell identifier can be an NR cell global identifier (NR cell global identifier, NCGI) or a physical cell identifier (physical cell identifier, PCI), and the cell identifier can also be a cell identifier allocated in the effective area. For example, if there are 32 cells in the effective area, the length of the cell identifier can be 5 bits (bit) to indicate 32 cells.
  • the cell identifier in the effective area can be configured by the open mobile alliance (open mobile alliance, OAM) or allocated by a gNB in the effective area.
  • gNB_1 determines 2 multicast configurations and identifies them as index_1 and index_2 respectively; gNB_2 determines 3 multicast configurations and identifies them as index_1, index_2, and index_3 respectively.
  • gNB_1 can send the gNB_1 identifier, multicast session 1, index_1, index_2, and the multicast configurations corresponding to index_1 and index_2 to gNB_2;
  • gNB_2 can send the gNB_2 identifier, multicast session 1, index_1, index_2, index_3, and index_1, index_2, index_3 to gNB_1.
  • multicast session 1 includes 5 multicast configurations.
  • the gNB identifier and index can uniquely identify a multicast configuration. This is just an example, and the granularity of the index is not limited. It can be per multicast session or per MRB, or different sub-configurations can have different sub-indexes.
  • the first network device determines N multicast configuration information, and the first network device receives sixth information from the fourth network device, and the sixth information includes M multicast configuration information.
  • the first network device determines the index information corresponding to the M multicast configuration information and the N multicast configuration information based on the M configuration information and the N multicast configuration information.
  • at least one multicast configuration information includes M multicast configuration information and N configuration information, and M and N are both positive integers.
  • the first information includes the sixth information.
  • the first network device can coordinate the configuration of the first information for the network devices in the effective area, which can be understood as the central gNB in the effective area.
  • the gNB in the effective area sends at least one multicast configuration determined or supported by it to the central gNB, and the central gNB determines the indexes corresponding to these multicast configurations, that is, the central gNB determines the mapping relationship between the multicast configuration and the index, and sends the mapping relationship to the network devices in the effective area.
  • gNB_1 indicates to the central gNB the multicast configuration_1 and multicast configuration_2 it has determined.
  • gNB_1 also indicates each group gNB2 indicates to the central gNB the multicast configuration_1, multicast configuration_2, and multicast configuration_3 it has determined.
  • gNB_2 also indicates the multicast session TMGI associated with each multicast configuration.
  • the central gNB determines that there are 5 multicast configurations in total, and identifies them as index_1, index_2, index_3, index_4, and index_5.
  • the central gNB sends the allocated multicast configuration and index to other gNBs in the effective area. This is just an example, and the granularity of the index is not limited. It can be per multicast session, or per MRB, or different sub-configurations can have different sub-indexes.
  • the central gNB determines that the multicast configuration of multicast session_1 will be less than 5. For example, if the central gNB determines that the multicast configuration_1 sent by gNB_1 and the multicast configuration 2 sent by gNB_2 are the same configuration, the central gNB determines that there are 4 multicast configurations in total, and identifies them as index_1, index_2, index_3, and index_4 respectively, and the central gNB sends the allocated multicast configuration and index to other gNBs in the effective area.
  • gNB_1 and gNB_2 are two network devices with an Xn interface, and the above configuration information is sent to the neighboring network device through the Xn interface message. It can be understood that gNB_1 and gNB_2 are only examples, and the access network devices in the area can be one or more. Here, only the configuration interaction method between any two gNBs is described. When there are multiple access network devices in the area, the above method can be applied to any two gNBs with an Xn interface in the area.
  • the method 200 further includes: the first network device sends the first information to the fourth network device.
  • Method 3 The first network device determines N multicast configuration information, sends the N multicast configuration information to the fourth network device, and receives first information from the fourth network device, where the first information includes the N multicast configuration information and index information corresponding to the N multicast configuration information.
  • Method 3 is similar to Method 2, except that in Method 3, the fourth network device is a central gNB and the first network device is a non-central gNB.
  • the network equipment coordinates to determine the first information so that there is a unified understanding of the mapping relationship between the first multicast configuration and the index information of the first multicast configuration between the cells in an area, and allows different cells in the area to have different multicast configurations, and also allows a cell to have one or more multicast configurations; in this way, when the terminal device moves between cells in the area, or when the multicast configuration of the cell for a multicast session changes, the corresponding multicast configuration is determined according to the index information indicated by the cell for a multicast session, and the terminal device can remain in the RRC inactive state or idle state to receive the multicast session according to the multicast configuration, avoiding the terminal device from entering the RRC connected state in order to obtain the multicast configuration of the cell. In this way, the energy consumption of the terminal device can be reduced, and it also helps to ensure the continuity of the terminal device receiving the multicast session.
  • the fourth network device generally refers to a network device that coordinates with the first network device to determine the first information, and it can be any network device within the effective area.
  • the method 200 further includes: the fourth network device sends seventh information, the seventh information is used to indicate that the first multicast session is associated with the second index information, the second index information indicates the second multicast configuration information, at least one multicast configuration information includes the second multicast configuration information, and the index information corresponding to at least one multicast configuration information includes the second index information.
  • the second network device sends the first multicast session according to the second multicast configuration information.
  • the terminal device can receive the seventh information sent by the fourth network device in the RRC inactive state or idle state, and determine the second multicast configuration through the seventh information, and then continue to receive the first multicast session in the RRC inactive state or idle state according to the second multicast configuration.
  • the seventh information can be carried in the system message or MCCH. In this way, the terminal device can be prevented from entering the RRC connected state to receive the multicast configuration information, which can reduce the energy consumption of the terminal device and help ensure the continuity of the terminal device receiving the multicast session.
  • the first information further includes identification information of a cell or a network device corresponding to at least one multicast configuration information.
  • the method 200 further includes: the second network device sends a first identifier to the terminal device, the first identifier is the identifier of the second network device or the identifier of the cell corresponding to the second information, that is, the first identifier is the identifier of the resident cell of the terminal device or the identifier of the network device corresponding to the resident cell, and there is a corresponding relationship between the first identifier and the first multicast configuration information.
  • the terminal device can determine the first multicast configuration information based on the first identifier and the first index information.
  • the second network device may send the first identifier and the second information to the terminal device at the same time, or the terminal device may obtain the first identifier from other system messages.
  • the first multicast configuration information corresponding to the first multicast session can be uniquely determined based on the first identifier and the first index information.
  • the information improves the flexibility of the cell in providing RRC non-activated multicast service configuration.
  • Different cells in the area can have different multicast configurations, and a cell can also have one or more multicast configurations.
  • the cell can indicate the change of the configuration information corresponding to the multicast session by changing the index information corresponding to the multicast session indicated by the second information.
  • the terminal device When the terminal device moves between cells in the area, or when the cell changes the multicast configuration of the multicast session, the terminal device can remain in the RRC non-activated state or idle state to receive the multicast session according to the multicast configuration, avoiding the energy consumption overhead and signaling overhead caused by entering the RRC connected state.
  • Table 5 A mapping relationship between cell identification, index information and multicast configuration
  • the method 200 further includes: the first network device sends third information to the terminal device, and accordingly, the terminal device receives the third information, where the third information is used to indicate an effective area of at least one multicast configuration information.
  • the effective area of at least one multicast configuration information can be understood as the effective area of at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, or the effective area of the first information.
  • the third information may be a list of cells constituting the effective area.
  • the cell identifier may be PCI, NCGI, etc.
  • the scope of the effective area may be smaller than or equal to RNA.
  • the third information may be sent simultaneously with the first information, for example, in the same message.
  • the third information is carried in an RRC reconfiguration message or an RRC release message.
  • the terminal device learns the effective area through an application layer message.
  • the first network device can indicate the effective area of the first information to the terminal device, so that when the terminal device moves within the effective area, it can continue to use the first information to determine the required multicast configuration information without repeatedly receiving the first information. In this way, the energy consumption of the terminal device can be reduced, and it also helps to ensure the continuity of the terminal device receiving the multicast session.
  • the method 200 also includes: the first network device or the second network device sends fourth information to the terminal device, and accordingly, the terminal device receives the fourth information, the fourth information is used to indicate the first G-RNTI corresponding to the first multicast session, the second network device can scramble the first multicast session through the first G-RNTI, and the terminal device can descramble the received first multicast session through the first G-RNTI.
  • the first G-RNTI associated with the first multicast session can be configured in the following ways.
  • the first network device receives a first G-RNRI from a core network device; or, the first network device determines the first G-RNTI according to an identifier of the first multicast session.
  • the core network can allocate a corresponding G-RNTI to each multicast session, so the core network can send the identifier of the first multicast session and the first G-RNTI to the first network device.
  • the core network only sends the identifier of the first multicast session to the terminal device, the first network device determines the first G-RNTI according to the identifier of the first multicast session, and the first network device can send the correspondence between the multicast session identifier and the first G-RNTI to the second network device.
  • the fourth information may be information of the first G-RNTI.
  • the network device may send the first G-RNTI to the terminal device through dedicated signaling, and the dedicated signaling may be an RRC reconfiguration message or an RRC release message.
  • the first information may not include the first G-RNTI.
  • the first multicast configuration information may include the first G-RNTI, indicated by the fourth information.
  • the following describes a method in which the first network device determines the first G-RNTI according to the identifier of the first broadcast session in configuration mode 1.
  • FIG6 is a schematic diagram of the structure of TMGI.
  • TGMI includes an MBS service identifier, a mobile country code (MCC), and a mobile network code (MNC).
  • MBS service identifier is composed of a 6-digit fixed-length hexadecimal number (digit) between 000000 and FFFFFF, and the MCC is composed of a 3-digit fixed-length hexadecimal number (digit).
  • the MBS service identifier is composed of a hexadecimal number of length, and the MBS service identifier is composed of 2 or 3 hexadecimal digits.
  • a specific bit string in the TMGI can be used as a G-RNTI reference value (G-RNTI-reference).
  • the G-RNTI reference value is a bit string consisting of the xth bit to the yth bit starting from the leftmost bit in the TMGI.
  • the G-RNTI reference value can be composed of some or all of the bits in the TMGI used to indicate the MBS service identifier.
  • the starting bit position and the ending bit position of the G-RNTI reference value are configurable, for example, they can be configured through OAM or indicated by the core network.
  • the G-RNTI associated with the multicast session may be G-RNTI-reference.
  • the G-RNTI associated with the multicast session may also be associated with the public land mobile network (PLMN) providing the multicast session.
  • PLMN public land mobile network
  • the PLMN providing the multicast session may be associated with an offset value, denoted as G-RNTI-base, which may be configured through OAM.
  • G-RNTI-base an offset value, denoted as G-RNTI-base, which may be configured through OAM.
  • G-RNTI-base an offset value
  • the first network device may send the first information and the fourth information simultaneously, for example, the first information and the fourth information are both carried in the RRC release message.
  • the second network device determines a first G-RNTI for the first multicast session.
  • the gNB or the gNB cell may allocate a G-RNTI for each multicast session and determine an index of the G-RNTI.
  • the gNB may send a gNB ID or a cell ID, a TMGI, a G-RNTI, and a G-RNTI index to a neighboring gNB (an example of the first network device).
  • a G-RNTI may be uniquely identified by the gNB ID or the cell ID and the G-RNTI index.
  • the first network device is a central gNB in the effective area
  • the central gNB receives the G-RNTI determined by other gNBs (an example of the second network device) in the effective area
  • the central gNB can determine the mapping relationship between all G-RNTIs and G-RNTI indexes of a multicast session.
  • the central gNB can send the mapping relationship to other gNBs (an example of the second network device) in the effective area.
  • the G-RNTI index can uniquely identify a G-RNTI.
  • the fourth information is the index of the G-RNTI or the index information of the G-RNTI, and the index information of the G-RNTI corresponds to the G-RNTI.
  • the first network device may preconfigure the G-RNTI configuration list to the terminal device first.
  • the second network device may broadcast the index of the G-RNTI, so that when the terminal device needs to receive a multicast session, the first G-RNTI actually used may be determined according to the index of the G-RNTI and the preconfigured G-RNTI configuration list.
  • the G-RNTI configuration list and the first information may be sent simultaneously, or in other words, the first information may include the G-RNTI configuration list.
  • the second network device determines the second G-RNTI of the first multicast session.
  • G-RNTI-common G-RNTI-common
  • the G-RNTI common value can be per multicast session, that is, different multicast sessions can have different initial offset values.
  • the G-RNTI common value can be configured to the gNB in the effective area by means of OAM.
  • the G-RNTI actually used by each network device or cell for a multicast session has an association with the G-RNTI common value.
  • G-RNTI G-RNTI common value +/- second G-RNTI
  • the second G-RNTI can be recorded as G-RNTI-additional, which is a G-RNTI determined autonomously by the network device or the cell of the network device (an example of the second network device).
  • the first network device can first preconfigure the G-RNTI common value to the terminal device.
  • the second network device can broadcast the second G-RNTI, so that when the terminal device needs to receive a multicast session, the first G-RNTI actually used can be determined according to the second G-RNTI and the preconfigured G-RNTI common value.
  • the fourth information is information of the second G-RNTI, and the second G-RNTI has a corresponding relationship with the first G-RNTI.
  • the G-RNTI common value and the first information may be sent simultaneously, or in other words, the first information may include the G-RNTI common value.
  • the second network device may send the fourth information together with the second information to the terminal device, and the terminal device may determine the first multicast configuration according to the second information and the fourth information, and the first multicast configuration information includes the determined first G-RNTI.
  • the fourth information and the second information are both carried in the SIB, and for another example, the fourth information and the second information are both carried in the MCCH message.
  • the network device can indicate the first G-RNTI used for scrambling and descrambling to the terminal device through the fourth information. Since the fourth information is sent through a dedicated method, or the fourth information is an index of the first G-RNTI or the second G-RNTI, this can prevent terminal devices that have not joined the first multicast session from obtaining the first G-RNTI, thereby helping to ensure communication security.
  • S210 and S220a may be executed simultaneously.
  • the first network device releases the terminal device to an idle state or an inactive state, and instructs the terminal device to receive a multicast session in the idle state or the inactive state.
  • the first network device may send the first information and the second information to the terminal device through an RRC release message.
  • the terminal device enters an idle state or an inactive state according to the RRC release message, determines a first multicast configuration according to the first information and the second information, and then receives the first multicast session according to the first multicast configuration.
  • the trigger condition for the terminal device to receive the second information may be any one of the following: the terminal device reselects to a cell managed by the second network device; or, the terminal device receives fifth information from the second network device, wherein the fifth information is used to notify a system message change; or, the fifth information is used to notify a multicast control channel message change; or, the fifth information is used to notify the activation of the first multicast session; or, the fifth information is used to indicate that the terminal device receives a multicast session in an RRC inactive state or an idle state.
  • the terminal device when the terminal device reselects to a cell managed by the second network device, the terminal device will obtain system information and/or MCCH, thereby obtaining the second information.
  • the terminal device can obtain the index information corresponding to the multicast session through the cell broadcast message, and determine the multicast configuration corresponding to the multicast session through the index information, so as to continue to receive the multicast session in the RRC inactive state or idle state. In this way, it can not only avoid the terminal device entering the RRC connected state to increase energy consumption, but also avoid the delay in the RRC state transition process, so that the terminal device can quickly start receiving the multicast session and avoid service interruption.
  • the second network device when the multicast configuration information of the first multicast session is changed to the first multicast configuration information; or when the cell managed by the second network device starts to provide the first multicast session in an inactive state or an idle state, the second network device sends fifth information to the terminal device, and the fifth information is used to notify the system information change, or to notify the multicast control channel message change.
  • the terminal device can obtain the system information and/or MCCH under the triggering of the fifth information, thereby obtaining the second information.
  • starting to provide multicast sessions in an inactive state or an idle state means that the cell starts to provide multicast sessions in an idle state or an inactive state, or the cell starts to send multicast sessions to the terminal device when the terminal device is in an inactive state or an idle state, or the cell turns on the switch for sending multicast sessions in an inactive state or an idle state.
  • the terminal device that supports receiving multicast sessions in an inactive state or an idle state will receive the multicast sessions in an inactive state or an idle state. If the cell stops providing multicast sessions in an inactive state or an idle state, then even if the terminal device supports receiving multicast sessions in an inactive state or an idle state, the terminal device cannot receive the multicast sessions in an inactive state or an idle state.
  • the terminal device can quickly obtain the updated multicast configuration information, or when a cell starts to provide a multicast session in an inactive state or an idle state, according to method 200, the terminal device can quickly obtain the multicast configuration information of the multicast session that needs to be received, thereby quickly receiving the multicast session. In this way, the terminal device can quickly start receiving the multicast session and avoid service interruption.
  • the second network device can send the fifth information to the terminal device, and the fifth information is used to notify the activation of the first multicast session; or, when the second network device requires the terminal device to receive the multicast session in the RRC inactive state or idle state, the second network device can send the fifth information to the terminal device, and the fifth information is used to indicate that the terminal device receives the multicast session in the RRC inactive state or idle state, or in other words, the fifth information indicates that the terminal device is allowed to receive the multicast session in the RRC inactive state or idle state.
  • the terminal device can obtain the system information and/or MCCH under the triggering of the fifth information, thereby obtaining the second information.
  • the terminal device can quickly obtain the multicast configuration information of the multicast session to be received, thereby quickly receiving the multicast session. In this way, the terminal device can quickly start receiving the multicast session and avoid service interruption.
  • the fifth information when the fifth information is used to indicate that the terminal device receives a multicast session in an RRC inactive state or an idle state, it can also be understood that the fifth information indicates that the purpose of allowing the terminal device to enter the RRC inactive state or the idle state is to receive the multicast session.
  • the fifth information is carried in an RRC release message. After receiving the fifth information, the terminal device starts to obtain system information and/or MCCH, thereby obtaining the second information.
  • step S220a in method 200 is replaced by: S220b, the second network device sends a first message, the first message includes an identifier of the first multicast session, and the first message does not include first index information.
  • the first message is a system message, a multicast control channel message, or an RRC release message.
  • the system message, multicast control channel message or RRC release message sent by the cell includes the identifier of the first multicast session but does not include the index information of the multicast configuration, it indicates that the multicast session is in a deactivated state or has been released.
  • the terminal device can stop receiving the first multicast session to avoid unnecessary energy consumption.
  • the second network device when the second network device determines that the state of the first multicast session in the cell it manages has changed, it sends a system message change notification or an MCCH change notification. After receiving the system message change notification or the MCCH change notification, the terminal device residing in the cell obtains the first message.
  • the terminal device learns that the first multicast session is deactivated by obtaining a first message sent by the cell of the second network device.
  • the terminal device stops receiving the first multicast session, and the terminal device can remain in the RRC inactive state or idle state without entering the RRC connected state because the multicast configuration for the RRC inactive state cannot be obtained on the cell of the second network device where it resides. Because the terminal device has determined that the first multicast session has been deactivated or released, it is not necessary to enter the RRC connected state for the purpose of receiving the first multicast session, which can save energy consumption and signaling overhead of entering the RRC connected state.
  • the cell managed by the second network device stops providing the first multicast session in an inactive state or an idle state, and step S220a in method 200 is replaced by: S220c, the second network device sends a first message, the first message does not include an identifier of the first multicast session.
  • the first message is a system message, a multicast control channel message, or an RRC release message.
  • the terminal device can request the network device corresponding to the resident cell to restore the RRC connection, so as to request to receive the first multicast session in the RRC connection state.
  • the terminal device determines whether the first multicast session is in an activated state to determine whether to restore the RRC connection: if the first multicast session is still in an activated state, the terminal device requests the network device corresponding to the resident cell to restore the RRC connection; if the first multicast session is in a deactivated state, the terminal device does not request the network device to restore the RRC connection. For example, if the terminal device has previously received a deactivation/release notification of the first multicast session, after the cell is reselected, if the identifier of the first multicast session is not included in the first message, the terminal device may not trigger the RRC connection recovery.
  • the terminal device can wait for the network to send an indication for notifying the activation of the first multicast session.
  • the cell may be a cell indicating that the multicast session is provided to terminal devices in an inactive state or an idle state, for example, the cell is a cell in the effective area of the multicast configuration indicated in the third information.
  • the terminal device receives the third information, the cell may be providing the first multicast session in the RRC inactive state; however, at some later moment, the state of the cell may change and stop providing the first multicast session in the RRC inactive state.
  • the cell may only provide the first multicast session in the RRC connected state; or when the number of terminal devices in the RRC inactive state receiving the first multicast session on the cell is small, the cell stops providing the first multicast session in the RRC inactive state.
  • the cell itself is a cell that can provide multicast sessions in RRC inactive state or idle state.
  • the cell provides the first multicast session in RRC inactive state at time 1, but stops providing the first multicast session at time 2.
  • the cell can send a system message change notification or MCCH change notification.
  • the terminal device After the terminal device receives the change notification, it obtains the first message sent by the cell to learn that the cell stops providing the first multicast session. In this way, the terminal device can promptly request the second network device to restore to the RRC connected state to continue receiving the first multicast session.
  • method 200 also includes: if the cell managed by the second network device does not support providing multicast sessions in an inactive state or an idle state, or if the cell managed by the second network device does not support multicast sessions, the second network device sends a first message, and the first message does not include an identifier of the multicast session.
  • the system message, multicast control channel message or RRC release message sent by the cell does not include a multicast session identifier
  • the network device corresponding to the cell may be a network device that does not support idle or inactive state multicast sessions, but the network device may support connected state multicast, for example, the network device is an R17 network device.
  • the present application can not only instruct the terminal device to receive the multicast configuration information of the multicast session, but also instruct the multicast session to be deactivated or released, which has higher efficiency and can avoid unnecessary energy consumption.
  • the method 200 also includes: when the first information changes, the second network device notifies other network devices in the effective area through the Xn interface, the network devices in the area send a group notification or group paging to the terminal devices that join the multicast session, and after monitoring the group notification or group paging message including the identifier of the first multicast session, the terminal device triggers RRC connection recovery, and the second network device sends dedicated signaling (for example, an RRC reconfiguration message or an RRC release message) to the terminal device to indicate the updated first information.
  • dedicated signaling for example, an RRC reconfiguration message or an RRC release message
  • the change in the first information includes a change in at least one multicast configuration indicated by the first information, or it can be understood as a change in the resource pool of the multicast configuration, such as adding, modifying or deleting a multicast configuration; it can also include a change in the effective area of the at least one multicast configuration, that is, a change in the third information, such as adding or deleting a cell to which the at least one multicast configuration is applicable.
  • Fig. 7 is a schematic diagram of a communication method 300 provided in an embodiment of the present application, and the method 300 can be regarded as a specific implementation of the method 200.
  • the method 300 may include the following steps. In the method 300, it is assumed that the second information in the method 200 is carried in the SIB.
  • S301, gNB#1 (an example of a first network device) obtains and determines information #1 (an example of first information).
  • gNB#2 (an example of the second network device) can send one or more multicast configurations determined by gNB#2 to gNB#1, and gNB#1 determines different indexes for different multicast configurations of the same multicast session based on the one or more multicast configurations determined by itself and the one or more multicast configurations from gNB#2, and information #1 includes the correspondence between the session, the multicast configuration and the index.
  • gNB#2 sends one or more multicast configurations determined by gNB#2 and the index corresponding to the multicast configuration to gNB#1, and gNB#1 uses the one or more multicast configurations determined by itself and the index corresponding to the multicast configuration and the one or more multicast configurations received and the index corresponding to the multicast configuration as information #1.
  • gNB#1 sends information #1 to UE.
  • Information #1 may be sent via an RRC release message or an RRC reconfiguration message.
  • the signaling format of information #1 is as follows:
  • the "Multicast-AreaCell” information element includes the cell identifier that provides the multicast session in the inactive state or idle state.
  • “MRB-ConfigList” represents multiple MRB configurations
  • “drx-Config-List” represents multiple DRX configurations
  • “pdsch-ConfigList” represents multiple PDSCH configurations
  • “ssb-MappingWindowList” represents the mapping window configuration of PDCCH timing and SSB. It should be understood that this signaling format is only an example.
  • information #1 includes configurations of multicast session #1 and multicast session #2.
  • gNB#1 can release the UE to an inactive state.
  • the UE When the UE is in an inactive state, it can obtain the SIB, which includes information #2 (an example of the second information).
  • Information #2 includes the index #1 associated with the multicast session #1.
  • the UE According to the multicast session #1, the index #1 and the information #1, the UE can determine the multicast configuration #1 corresponding to the multicast session #1, so that the UE can receive the multicast session #1 according to the multicast configuration #1.
  • S304 The UE reselects a cell and moves to the cell managed by gNB#2.
  • the multicast configuration of the UE's reselected cell is multicast configuration #2.
  • gNB #2 can carry information #3 (an example of the seventh information) of multicast session #1 and index #2 through the broadcast SIB.
  • the UE can obtain the SIB of the new cell and thus obtain information #3.
  • the UE can determine the multicast configuration #2 corresponding to multicast session #1, so that the UE can continue to receive multicast session #1 according to multicast configuration #2.
  • gNB#2 starts to provide multicast session #2 in the inactive state.
  • gNB#2 sends a system message change notification.
  • the UE can obtain the SIB according to the system change message.
  • gNB#2 When gNB#2 starts to provide multicast session #2 in an inactive state or an idle state, gNB#2 can carry information #4 (another example of the seventh information) of index #1 associated with multicast session #2 through a broadcast SIB.
  • the UE can obtain the SIB according to the system change message, thereby obtaining information #4.
  • the UE According to multicast session #2 and index #1, the UE can determine the multicast configuration #1 corresponding to multicast session #2, so that the UE can receive multicast session #2 according to multicast configuration #1.
  • the terminal device can obtain the multicast configuration corresponding to the multicast session to be received without entering the connected state, which can reduce the energy consumption of the UE and avoid service interruption.
  • Fig. 8 is a schematic diagram of a communication method 400 provided in an embodiment of the present application.
  • the method 400 may include the following steps.
  • the first network device sends the eighth information to the terminal device, and correspondingly, the terminal device receives the eighth information.
  • the eighth information includes the first multicast configuration information and information of a cell corresponding to the first multicast configuration information, and the cell corresponding to the first multicast configuration information includes the first cell.
  • different cells in the first area can use the same multicast configuration information to send the multicast session.
  • different cells in the first area can all use the first multicast configuration to send the first multicast session. Therefore, when the first network device sends the multicast configuration information to the terminal device, it can further indicate to the terminal device the information of the cell corresponding to the multicast configuration information.
  • the cell information can be a list of cells in the first area, or the cell information is an identifier of the first area, and the first area is associated with a cell list.
  • the terminal device can learn a group of cells associated with the first area, that is, the cells corresponding to the cell list, through application layer messages or preset information.
  • the first multicast configuration corresponds to the first multicast session.
  • the first region may be equal to or smaller than RNA.
  • the eighth information may be carried in dedicated signaling, such as an RRC release message or an RRC reconfiguration message.
  • the first network device may pre-configure the eighth information for the terminal device when the terminal device is in an RRC connected state.
  • the second network device sends a second message to the terminal device, where the second message includes the first indication information.
  • the first indication information may be a bitmap, and each bit in the bitmap is associated with a cell. For example, if the first multicast configuration information corresponds to Q cells, the bitmap includes Q bits, and Q bits correspond to Q cells one by one, where Q is a positive integer.
  • each multicast session corresponds to a bitmap
  • each bit in the bitmap corresponds to a cell.
  • the order of the bits corresponds to the cells in the cell list in the first area.
  • the first area includes 32 cells
  • the length of the bitmap is 32 bits, which corresponds to the 32 cells in the first area.
  • the first indication information is used to indicate the state of the first multicast session provided by the cell corresponding to the first multicast configuration information.
  • the cell corresponding to the first multicast configuration information includes the first cell, that is, the first indication information is used to indicate the state of the first multicast session provided by the first cell.
  • the state of the first multicast session provided by the cell corresponding to the first multicast configuration information may include: the cell corresponding to the first multicast configuration information is providing or not providing the first multicast session in RRC inactive state or idle state.
  • bit position 1 indicates that the cell corresponding to the bit currently supports the provision of multicast session #1 in the inactive state or idle state, or in other words, the cell is currently providing the inactive state or idle state multicast session #1.
  • Bit position 0 indicates that the cell corresponding to the bit currently does not support the provision of the multicast session #1 in the inactive state or idle state, or in other words, the cell is not currently providing the inactive state or idle state multicast session #1.
  • the cells corresponding to the first multicast configuration information may constitute a valid area of the first multicast configuration information.
  • the second network device when the first cell starts or stops providing the first multicast session in the RRC inactive state or idle state, the second network device sends a second message to the terminal device, and the second message includes the first indication information.
  • the terminal device can know which cell or cells are currently providing the inactive or idle multicast session #1. Assuming that the cells providing the inactive or idle multicast session #1 include cell #2, if the terminal device joins the multicast session #1 and cell #2 is the service cell of the terminal device, the terminal device can use the first multicast configuration information to receive the multicast session #1.
  • the first indication information is used to indicate that the state of the first multicast session provided by the cell corresponding to the first multicast configuration information changes. Specifically, it may include: the cell corresponding to the first multicast configuration information starts or stops providing the first multicast session in RRC inactive or idle state.
  • bit position 1 indicates that the cell corresponding to the bit currently starts to provide inactive or idle multicast session #1.
  • Bit position 0 indicates that the cell corresponding to the bit currently stops providing the multicast session #1 in inactive or idle state, or in other words, for the multicast session of the cell, the terminal device can only receive it in connected state.
  • the terminal device can know which cell or cells are currently starting to provide the inactive or idle multicast session #1. Assuming that the cell that starts to provide the inactive or idle multicast session #1 includes cell #2, if the terminal device joins the multicast session #1 and cell #2 is the service cell of the terminal device, the terminal device can use the first multicast configuration. Information received multicast session #1.
  • the second message is a paging message or an RRC release message.
  • the terminal device is in an idle state or an inactive state when executing S420.
  • S430 The second network device sends the first multicast session according to the first multicast configuration.
  • the terminal device receives the first multicast session according to the first multicast configuration information.
  • the first cell may be a cell that is currently providing a multicast session #1 in an inactive state or an idle state, or may be a cell that starts to provide a multicast session #1 in an inactive state or an idle state.
  • the terminal device receives the first multicast session according to the first multicast configuration information, including: when the first indication information indicates that the first cell starts to provide the first multicast session in an inactive state or an idle state, the terminal device receives the first multicast session in a wireless resource control inactive state or an idle state according to the first multicast configuration information.
  • the terminal device sends an RRC recovery request message to the network device corresponding to the first cell.
  • the network device corresponding to the first cell can send an RRC release message or an RRC recovery message to the terminal device according to the RRC recovery request message.
  • the network device corresponding to the first cell can send an RRC release message to the terminal device according to the RRC recovery request message, and the terminal device can continue to maintain the RRC inactive state or the idle state according to the RRC release message, and receive the first multicast session according to the first multicast configuration information.
  • the network device corresponding to the first cell can send an RRC recovery message to the terminal device based on the RRC recovery request message. Further, the terminal device can enter a connected state based on the RRC recovery message, and receive the first multicast session based on the first multicast configuration information in the RRC connected state.
  • the network device corresponding to the first cell refers to the network device that manages the first cell, which may be the first network device, the second network device, or other network devices in the first area.
  • the first network device pre-configures the information of the cell corresponding to the first multicast configuration information to the terminal device, and the second network device can indicate the status of the multicast session of each cell to the terminal device through the first indication information in the second message.
  • the terminal device can use the first multicast configuration information to receive the multicast session. In this way, on the one hand, it can avoid the security risks caused by receiving the multicast configuration information in the form of broadcasting, and on the other hand, it can avoid the signaling overhead and delay caused by the terminal device entering the RRC connection state to receive the multicast configuration information.
  • the first cell is a cell managed by a fourth network device.
  • the method further includes: before the second network device sends a second message to the terminal device, the second network device receives second indication information from the fourth network device, the second indication information being used to instruct the first cell to start or stop providing the first multicast session in an inactive state or an idle state.
  • gNB2 when any cell in the first area stops or starts providing an inactive or idle multicast session, assuming that the cell is the cell of gNB2, gNB2 sends a multicast configuration change indication message to the adjacent base station through the Xn interface, including the cell identifier of the gNB's cell that stops or starts providing an inactive multicast session, and the identifier of the multicast session that is stopped or started.
  • all gNBs in the area will trigger group paging, and the paging message indicates the identifier of the multicast session and the first indication information corresponding to the multicast session.
  • the network equipment in the first area will trigger group paging, so that no matter which cell the terminal device moves to in the first area, it can quickly obtain the start or stop of the multicast session in the area.
  • the terminal device can also receive the multicast session in time, so it has higher communication efficiency.
  • the method also includes: the first network device receives ninth information from the fourth network device, the ninth information is used to indicate the identifiers of R cells corresponding to the first multicast configuration information, the cell information corresponding to the first multicast configuration information includes R cells, and R is a positive integer.
  • the network devices in the first area may coordinate to determine a cell list included in the first area.
  • the second message only indicates the cell whose multicast session status has changed. If the cell associated with the multicast session has not changed, the multicast session and the associated cell are not included in the second message. If the terminal device does not receive the second message, it is considered that the multicast session provided by the cell has not changed.
  • the second network device when sending a group paging, calculates the position of a paging occasion (PO) according to the identification of a terminal device that has joined the multicast session, and sends the group paging on a corresponding PO.
  • PO paging occasion
  • FIG9 is a schematic diagram of a communication method 500 provided in an embodiment of the present application.
  • the method 500 can be regarded as a method 200 and a method 400.
  • method 500 may include the following steps.
  • the first network device sends the eighth information to the terminal device, and correspondingly, the terminal device receives the eighth information.
  • the eighth information includes at least one multicast configuration information and index information corresponding to at least one multicast configuration information, the eighth information also includes cell information corresponding to at least one multicast configuration information, at least one multicast configuration information includes first multicast configuration information, the index information corresponding to at least one multicast configuration information includes first index information, the cell information corresponding to at least one multicast configuration information includes cell information corresponding to the first multicast configuration information, and the cell information corresponding to the first configuration information includes the first cell.
  • the first network device can pre-configure the multicast configuration information and the index information and cell information corresponding to the multicast configuration information to the terminal device.
  • the index of the multicast configuration_1 of TMGI_1 is index1, and the corresponding cells are cell_1, cell_2, and cell_3;
  • the index of the multicast configuration_1 corresponding to TMGI_1 is index2, and the corresponding cells are cell_1, cell_2, cell_3, and cell_4.
  • the second network device sends a second message to the terminal device, the second message including first indication information and second information, the first indication information is used to indicate the state of the first multicast session provided by the first cell, the second information is used to indicate that the first multicast session is associated with first index information, and the first index information indicates first configuration information.
  • the second network device when a first cell within a first area starts or stops providing a first multicast session in an inactive state or an idle state, or when the multicast configuration information of the first cell within the first area changes, the second network device sends a second message to the terminal device, and the second message includes first indication information and second information.
  • the first indication information is used to indicate that the first cell starts or stops providing a first multicast session in an inactive state or an idle state
  • the second information is used to indicate the first multicast configuration.
  • the terminal device may determine first configuration information according to the first indication information and the first index information.
  • first indication information For a detailed description of the first indication information and the first index information, reference may be made to method 200 and method 400 .
  • the second network device sends a first multicast session according to the first multicast configuration.
  • the terminal device receives the first multicast session according to the first multicast configuration information.
  • the first network device pre-configures the cell information corresponding to the first multicast configuration information to the terminal device, and the second network device can obtain the status of the multicast session of each cell through the first indication information in the second message, and indicate the first multicast configuration information to the terminal device through the second information.
  • the terminal device can use the first multicast configuration information to receive the multicast session. In this way, on the one hand, the security risks caused by receiving multicast configuration information in the form of broadcasting can be avoided, and on the other hand, the signaling overhead and delay caused by the terminal device entering the RRC connection state to receive multicast configuration information can be avoided.
  • method 500 for the same multicast session, different cells in the first area can use different multicast configuration information, and therefore, the method has greater flexibility.
  • the method 400 further includes: the first network device determines to obtain eighth information. Specifically, reference may be made to the method in which the first network device obtains the first information in the method 200.
  • method 400 also includes: the first network device or the second network device sends fourth information to the terminal device, and accordingly, the terminal device receives the fourth information, the fourth information being used to indicate the first G-RNTI corresponding to the first multicast session, the first network device can scramble the first multicast session through the first G-RNTI, and the terminal device can descramble the received first multicast session through the first G-RNTI.
  • method 400 may refer to method 200 and method 300 .
  • the present application also provides a communication method, which can be used to solve the problem of how to synchronize multicast configuration information between network devices in a region. Through this method, for the same multicast session, different cells in the region can use the same multicast configuration information to send the multicast session.
  • FIG. 10 is a schematic diagram of a communication method 600 provided in an embodiment of the present application, and the method includes the following steps.
  • the fifth network device sends a third message to the first device.
  • the third message is used to request the multicast configuration information of the first multicast session, or in other words, the third message is used to request the multicast configuration information corresponding to the first multicast session, and the multicast configuration information corresponding to the first multicast session can be used to configure the first multicast session.
  • the multicast configuration information is also called MBS multicast configuration information or multicast configuration, which refers to the configuration parameters for receiving the multicast session in the MBS, and the multicast configuration information consists of multicast configuration parameters.
  • the multicast configuration information may include one or more of the following: multicast MRB configuration, physical channel configuration, DRX configuration, G-RNTI configuration, neighbor cell configuration, CFR configuration, each of which can be understood as a multicast configuration parameter.
  • the multicast configuration information please refer to method 200, which will not be repeated here.
  • the third message includes the identifier of the first multicast session, and the identifier of the first multicast session may be a TMGI.
  • the first device refers to a device on the non-terminal side.
  • the function performed by the first device may be performed by a functional module or a network element of a certain physical device.
  • the first device may refer to a functional module or a network element of a certain physical device.
  • the first device may be a core network device.
  • the first device refers to an access and mobility management function (AMF) network element or a session management function (SMF) network element in the core network device.
  • AMF access and mobility management function
  • SMF session management function
  • the first device may also be the sixth network device, for example, the fifth network device may directly send the third message to the sixth network device.
  • the fifth network device may also send the third message to the sixth network device through forwarding by other devices, wherein the other devices may be core network devices.
  • the fifth network device and the sixth network device may communicate directly or indirectly through the core network.
  • the triggering condition of S610 may be that the cell managed by the fifth network device starts to provide the first multicast session for terminal devices in an inactive or idle state, or that there is a terminal device in the cell managed by the fifth network device joining the first multicast session.
  • providing a multicast session for a terminal device in an inactive state or an idle state can also be said to be starting to provide a multicast session in an inactive state or an idle state, or the cell starts to provide a multicast session in an idle state or an inactive state, or the cell starts to send a multicast session to the terminal device when the terminal device is in an inactive state or an idle state, or the cell turns on a switch for sending a multicast session in an inactive state or an idle state.
  • a terminal device that supports receiving a multicast session in an inactive state or an idle state will receive the multicast session in an inactive state or an idle state. If the cell stops providing a multicast session in an inactive state or an idle state, then even if the terminal device supports receiving a multicast session in an inactive state or an idle state, the terminal device cannot receive the multicast session in an inactive state or an idle state.
  • the fifth network device executing S610 can be one or more, and the multiple fifth network devices can belong to the same area. For any network device in the area, if the cell it manages meets the above-mentioned trigger condition, it can send a third message to the first device to request the multicast configuration information of the first multicast session.
  • S620 The first device determines first multicast configuration information according to the third message and a value range of the multicast configuration parameter.
  • the first multicast configuration information may be used to configure the terminal device to receive the first multicast session in an RRC inactive state or an idle state.
  • the value range of the multicast configuration parameter may include at least one of the following: the value range of G-RNTI, the value range of MRB identifier, the value range of LCH identifier, the value range of physical channel configuration parameters, the value range of discontinuous reception DRX configuration parameters, and the value range of common frequency domain resource CFR configuration parameters.
  • the value range of G-RNTI is 10000-15000
  • the value range of MRB identifier is 100-200
  • the value range of LCH identifier is 5000-10000.
  • the value range of the multicast configuration parameter can be understood as a shared value range of multiple multicast sessions, that is, the value range does not distinguish between multicast sessions or multicast services, or in other words, the value range of the multicast configuration parameter is applicable to any multicast session or multicast service in the area.
  • the first multicast session, the second multicast session, the third multicast session, etc. in the area can all use the values in this value range.
  • the first device can determine the first multicast configuration information of the first multicast session based on the value range of the multicast configuration parameter and the third message from one or more fifth network devices. For example, when there are multiple different ranges for the value range of the multicast configuration parameter, the first device can select the first multicast configuration information from the intersection of the multiple different ranges. For another example, when there is only one value range for the multicast configuration parameter, the first device can select the first multicast configuration information for the first multicast session within the value range. For another example, when multiple fifth network devices request the multicast configuration information of the first multicast session, the first device can determine the multicast configuration information shared by multiple fifth network devices for the first multicast session.
  • each third message carries the range of values of a multicast configuration parameter pre-configured or determined by the fifth network device.
  • S630 The first device sends first multicast configuration information to the fifth network device.
  • the first device can determine the first multicast configuration information for the first multicast session provided by one or more fifth network devices.
  • the first device can determine the first multicast configuration information that can be used by one or more fifth network devices for the first multicast session, so that for the same multicast session, different network devices supporting the first multicast session in a region can use the same multicast configuration information.
  • the multicast configuration information within the region can be synchronized.
  • the third message includes an identifier of the first multicast session, and the value range of the multicast configuration parameter includes the value range of the G-RNTI.
  • S620 specifically includes: the first device selects a value from the value range of the G-RNTI as the first multicast session.
  • the first multicast configuration information includes the G-RNTI of the first multicast session.
  • the third message includes the identifier of the first multicast session and the number X of multicast radio bearer MRBs required for the first multicast session, and the value range of the multicast configuration parameter includes the value range of the MRB identifier.
  • S620 specifically includes: the first device selects X values from the value range of the MRB identifier as the MRB identifier of the first multicast session, the first multicast configuration information includes the MRB identifier of the first multicast session, and X is a positive integer.
  • the third message includes the identifier of the first multicast session and the number Y of logical channels LCH required by the first MRB of the first multicast session, and the value range of the multicast configuration parameter includes the value range of the LCH identifier.
  • S620 specifically includes: the first device selects Y values from the value range of the LCH identifier as the LCH identifier of the first MRB, the first multicast configuration information includes the LCH identifier of the first MRB, and Y is a positive integer.
  • the third message includes an identifier of the first multicast session, and the value range of the multicast configuration parameter includes the value range of the physical channel configuration parameter.
  • S620 specifically includes: the first device selects at least one value from the value range of the physical channel configuration parameter as the physical channel configuration parameter of the first multicast session, and the first multicast configuration information includes the physical channel configuration parameter of the first multicast session.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the discontinuous reception DRX configuration parameter.
  • S620 specifically includes: the first device selects at least one value from the value range of the DRX configuration parameter as the DRX configuration parameter of the first multicast session, and the first multicast configuration information includes the DRX configuration parameter of the first multicast session.
  • the third message includes an identifier of the first multicast session
  • the value range of the multicast configuration parameter includes the value range of the common frequency domain resource CFR configuration parameter.
  • S620 specifically includes: the first device selects at least one value from the value range of the CFR configuration parameter as the CFR configuration parameter of the first multicast session, and the first multicast configuration information includes the CFR configuration parameter of the first multicast session.
  • the third message includes the identifier of the first multicast session, the number of multicast radio bearer MRBs required for the first multicast session, and the number of logical channels LCH required for each MRB of the first multicast session.
  • the value range of the multicast configuration parameter includes the value range of the MRB identifier and the value range of the LCH identifier.
  • S620 specifically includes: the first device selects a corresponding number of MRB identifiers for the first multicast session from the value range of the MRB identifier, and selects a corresponding number of LCH identifiers for each MRB from the value range of the LCH identifier.
  • the third message indicates that the multicast service TMGI-1 requires 2 MRBs, one of which requires 2 LCHs and the other requires 3 LCHs.
  • the first device determines MRB ID-1 and MRB ID-2, and determines that the LCHs corresponding to MRB ID-1 are LCH ID-1 and LCH ID-2, and the LCHs corresponding to MRB ID-2 are LCH ID-3, LCH ID-4 and LCH ID-5.
  • the number of MRBs and the number of LCHs may be determined by the fifth network device according to the quality of service (QoS) of the first multicast session.
  • QoS quality of service
  • gNBs in a region e.g., RNA region
  • the third message may not include the number of MRBs and the number of logical channels (LCHs) required for the first multicast session.
  • the SMF may determine the number of MRBs and the number of LCHs according to the QoS of the first multicast session. If the first device is the SMF, S620 is executed by the SMF. If the first device is the AMF or the sixth network device, the SMF may send the determined number of MRBs and the number of LCHs required for the first multicast session to the AMF or the sixth network device, and the AMF or the sixth network device executes S620.
  • the first device determines the first multicast configuration information according to the third message and the value range of the multicast configuration parameter, including: the first device determines the G-RNTI of the first multicast session according to the identifier of the first multicast session in the third message, and determines other multicast configuration information in the first multicast configuration information except the G-RNTI according to the value range of the multicast configuration parameter, for example, the MRB identifier, the LCH identifier, the DRX configuration parameter, the CFR configuration parameter, etc.
  • the specific method of the first device determining other multicast configuration information in the first multicast configuration information except the G-RNTI according to the value range of the multicast configuration parameter can refer to the above description.
  • the specific method of the first device determining the G-RNTI of the first multicast session according to the identifier of the first multicast session can refer to the configuration method 1 in method 200. It should be understood that the above method can be regarded as an example of the combination of method 600 and method 200.
  • the value range of the multicast configuration parameter is preconfigured in the first device.
  • OAM can configure the same value range of multicast configuration parameters to multiple network devices in an area, and the first device can determine the corresponding first multicast configuration information for the first multicast session within the value range when determining the first multicast configuration information.
  • the value range of the multicast configuration parameter is sent by the fifth network device to the first device.
  • the method 600 may also include: the fifth network device sends a fourth message to the first device, the fourth message including the value range of the multicast configuration parameter.
  • the fifth network device will send the determined value range to the first device, which can be the sixth network device or the core network device.
  • the fifth network device can send the value range to the core network device.
  • the value ranges determined by different fifth network devices may be different.
  • gNB1 determines the value range of G-RNTI to be 10000-20000
  • gNB2 determines the value range of G-RNTI to be 5000-15000.
  • each fifth network device may send its determined value range to the first device respectively.
  • each fifth network device may indicate the updated value range to the first device.
  • the first device may first determine the intersection of multiple different ranges, and then determine the corresponding first multicast configuration information for the first multicast session from the intersection.
  • the fourth message is a PDU session resource setup request transmission (PDU session resource setup request transfer) message or a PDU session resource setup modification request transmission (PDU session resource setup modify request transfer message).
  • the fifth network device may send the fourth message to the first device when the first multicast session or any multicast session is established.
  • the multicast configuration parameters for example, RNTI value, MRB identifier, LCH identifier
  • the values of certain parameters may have been occupied by unicast or broadcast. If the first device directly specifies the multicast configuration parameters for a multicast service, it will cause a conflict with the unicast or broadcast configuration parameters that have been used. At this time, the fifth network device needs to reconfigure the configuration parameters used by the conflicting unicast or broadcast services, which will affect the user experience and increase the signaling overhead of the reconfiguration.
  • the fifth network device can indicate the value range of the multicast configuration parameters or the value range of the pre-configured multicast configuration parameters in the first device to the first device.
  • the fifth network device can indicate the value range of the multicast configuration parameters or the value range of the pre-configured multicast configuration parameters in the first device to the first device.
  • the method 600 may further include: the fifth network device sends identification information of a second area to the first device, where the second area is an effective area of a value range of the multicast configuration parameter.
  • the cell in the second area provides at least one multicast session, and at least one multicast session includes a first multicast session.
  • the method may also include: the first device determines different multicast configuration information for each multicast session in the at least one multicast session, or in other words, the multicast configuration information of other multicast sessions except the first multicast session in the at least one multicast session is different from the first multicast configuration information.
  • the first device determines the multicast configuration information for the multicast sessions in the area from the value range of the multicast configuration parameter, and the multicast configuration information of different multicast sessions is different. Outside the second area, other multicast sessions are allowed to have the same multicast configuration information as the multicast sessions in the second area.
  • the effective area of the value range of the multicast configuration parameter may be RNA, which includes the fifth network device.
  • the effective area of the value range of the multicast configuration parameter may also be a pre-configured area, for example, an area configured for OAM.
  • the purpose of the fifth network device sending the identification information of the second area to the first device is that the value range of the configuration parameters supported by the terminal device is limited.
  • the first device only needs to ensure that a session in a region has unique multicast configuration information (for example, a unique G-RNTI, MRB ID, LCH ID, etc.), while other sessions outside the area can still use the multicast configuration information in the area.
  • the fifth network device can send the identification information of the second area to the first device, so that different areas (such as two different RNA areas) within the management range of the first device can reuse the same configuration parameters, thereby improving the utilization efficiency of the configuration parameters.
  • the available value range of some configuration parameters is limited (for example, the existing protocol stipulates that the maximum value of the MRB identifier is 512, and when the number of multicast sessions that need to be established by each fifth network device within the management range of the first device exceeds 512), the multicast configuration parameters between multicast sessions will overlap, and the multicast configuration parameters cannot uniquely correspond to a multicast session.
  • a multicast session can correspond to one or more MRBs, which will aggravate the shortage of MRB identifiers.
  • various service forms such as multicast, unicast, and broadcast all need to use wireless bearers, corresponding to the corresponding MRB identifiers. Considering that other service types may have occupied some MRB identifiers, the range of MRB identifiers available for multicast is further reduced. The above solution can effectively solve the above problem.
  • the third message includes an identifier of a second cell
  • the second cell is a cell managed by a fifth network device and providing a first multicast session in an RRC inactive state or an idle state
  • the method 600 may further include: the first device determines tenth information according to the third message from one or more fifth network devices, the tenth information is used to indicate an effective area of the first multicast configuration information.
  • the effective area can be understood as a configured synchronization area.
  • the effective area of the first multicast configuration information is determined according to the second cell included in one or more third messages.
  • the value range of the multicast configuration parameter is pre-configured by OAM.
  • the value range of the multicast configuration parameter configured by multiple network devices in the second area is the same.
  • the first device can determine the second cells of multiple fifth network devices as the effective area of the first multicast configuration information.
  • gNB1 (an example of the fifth network device) indicates to CN (an example of the first device) that the cell 1 (an example of the second cell) it manages provides multicast session #1 in an RRC inactive or idle state
  • gNB2 (another example of the fifth network device) indicates to CN that the cell 3 (another example of the second cell) and cell 5 (another example of the second cell) it manages provide multicast session #1 in an RRC inactive or idle state.
  • CN can determine multicast configuration information #1 for multicast session #1, and determine that the effective area of multicast configuration information #1 is cell 1, cell 3, cell 5, or the effective area of multicast configuration information #1 is the area managed by gNB1 and gNB2.
  • the value range of the multicast configuration parameter is determined by the fifth network device.
  • the value ranges of the multicast configuration parameters configured by multiple network devices in the second area may be different.
  • the first device can determine the intersection of the value ranges of the multicast configuration parameters indicated by multiple fifth network devices. For the network devices corresponding to the value ranges with the intersection, the second cells managed by them can constitute the effective area of the first multicast configuration information. In other words, the first device determines that the multicast configuration information available to multiple fifth network devices is the multicast configuration information corresponding to the multicast session.
  • gNB1 (an example of the fifth network device) indicates to CN (an example of the first device) that cell 1 (an example of the second cell) managed by it provides multicast session #1 in an RRC inactive or idle state
  • gNB2 (another example of the fifth network device) indicates to CN that cell 3 (another example of the second cell) and cell 5 (another example of the second cell) managed by it provide multicast session #1 in an RRC inactive or idle state.
  • gNB1 indicates that the value range of its determined G-RNTI is 5000-10000
  • gNB2 indicates that its determined G-RNT The value range of I is 10000-15000.
  • the first device can determine multicast configuration information #1 for multicast session #1 from the value range of G-RNTI determined by gNB2, and determine that the effective area of multicast configuration information #1 is cell 3, cell 5, or the effective area of multicast configuration information #1 is the area managed by gNB2, that is, cell 1 or the area managed by gNB2 does not belong to the effective area of multicast configuration information #1.
  • the first device can indicate a configuration failure to the fifth network device; optionally, the first device does not add the fifth network device to the effective area of the multicast configuration information, and the identifier of the fifth network device or the identifier of the cell it manages is not included in the effective area of the multicast configuration information.
  • the effective area of the first multicast configuration information may not be determined based on the second cell in the third message.
  • the effective area of the first multicast configuration information may be equal to the second area (i.e., the effective area of the value range of the multicast configuration parameter, such as the RNA area).
  • the effective area of the first multicast configuration information has nothing to do with whether the network device in the second area is providing the first multicast session. That is, the network device in the second area may not be providing the first multicast session in the RRC inactive state or idle state; or it may be providing the first multicast session in the RRC inactive state idle state.
  • the cell providing the first multicast session can use the first multicast configuration information to configure the first multicast session.
  • the effective area of the first multicast configuration information does not need to be dynamically updated, that is, the effective area of the first multicast configuration information will not be updated due to a network device starting or stopping providing the first multicast session in the RRC inactive state idle state.
  • the method may further include: if the cell managed by the fifth network device does not support providing the first multicast session in an inactive state or an idle state, or the cell managed by the fifth network device does not support the multicast session, the fifth network device sends a first message, and the first message does not include an identifier of the multicast session.
  • the fifth network device sends a first message, and the first message does not include an identifier of the multicast session.
  • the effective area of the first multicast configuration information in this application does not limit the terminal device to be able to receive the first multicast configuration information in this area.
  • the first multicast session corresponding to the multicast configuration information In this way, when the current multicast session of the cell in the effective area changes, for example, starts to provide or stops providing, there is no need for synchronization update between network devices.
  • the method 600 further includes: the first device sending tenth information to the fifth network device.
  • the method 600 further includes: the fifth network device sends twelfth information to the first device, where the twelfth information is used to indicate whether the first multicast configuration information is accepted, or in other words, to indicate whether the multicast configuration information of the first multicast session is configured successfully.
  • the fifth network device can further determine whether the first multicast configuration information satisfies the value range of the multicast configuration parameter determined or configured by it, and if so, the twelfth information indicates acceptance of the first multicast configuration information, and if not, the twelfth information indicates rejection of the first multicast configuration information. Further, the first device can update the effective area of the first multicast configuration information according to the twelfth information.
  • the first device updates the effective area to the network devices in the existing effective area, that is, adds the identifier of the new network device or the cell identifier of the network device.
  • the method 600 also includes: the fifth network device sends an eleventh message to the first device, the eleventh message is used to instruct the third cell managed by the fifth network device to stop providing the first multicast session in the radio resource control RRC inactive state or idle state, and the first device removes the third cell from the effective area of the first multicast configuration information, or the first device determines the updated effective area corresponding to the first multicast configuration information, and the updated effective area does not include the third cell.
  • the fifth network device when the fifth network device stops providing the first multicast session in the inactive state or the idle state (for example, no connected terminal device receives the first multicast session), the fifth network device can indicate to the first device that the multicast configuration request stops (an example of the eleventh information), and the first device removes the fifth network device from the effective area of the first multicast configuration information.
  • the fifth network device stops providing the first multicast session in the inactive state or the idle state, when the effective area of the first multicast configuration information is updated, the first device will stop sending the updated effective area to the fifth network device.
  • the fifth network device when the fifth network device stops providing the first multicast session in the inactive state or the idle state, the fifth network device can notify the terminal device of the inactive state multicast configuration update: for example, the updated inactive state multicast configuration indicated by the fifth network device to the terminal device does not include the multicast configuration of the first multicast session. Further, when the inactive state terminal device residing in the cell of the fifth network device still expects to receive the first multicast session, the terminal device can trigger RRC connection recovery.
  • the first device deletes the stored first multicast configuration information.
  • the method 600 further includes: the fifth network device sends the first multicast configuration information and the tenth information to the terminal device.
  • the fifth network device may send the first multicast configuration information and the tenth information to the terminal device through dedicated signaling or public signaling, wherein the dedicated signaling may be an RRC release message, and the public signaling may be MCCH or SIB.
  • the dedicated signaling may be an RRC release message
  • the public signaling may be MCCH or SIB.
  • the meaning of the effective area means that the terminal device receives the first multicast session in the radio resource control RRC inactive state or idle state according to the first multicast configuration information within the effective area of the first multicast configuration information.
  • the terminal device can continue to receive the first multicast session without additionally entering the connected state.
  • the terminal device can trigger the RRC connection recovery process.
  • the terminal device when the terminal device moves within the area, the terminal device can continue to use the multicast configuration information to receive the multicast session, thereby ensuring the continuity of the terminal device receiving the multicast service.
  • the above method 600 may be applied to method 400.
  • the first network device in method 400 may execute the method executed by the fifth network device in method 600, and the steps executed by the fourth network device in method 400 may be executed by the first device in method 600.
  • method 400 includes the following steps:
  • the first network device sends a third message to the first device.
  • the first device determines first multicast configuration information according to a third message and a value range of a multicast configuration parameter.
  • S630 The first device sends first multicast configuration information to the first network device.
  • the first network device sends eighth information to the terminal device.
  • identifiers of R cells corresponding to the first multicast configuration information can be understood as The effective area of the first multicast configuration information.
  • S420 The second network device sends a second message to the terminal device.
  • S430 The second network device sends the first multicast session according to the first multicast configuration.
  • the terminal device receives the first multicast session according to the first multicast configuration information.
  • Fig. 11 is a schematic diagram of a communication method 700 provided in an embodiment of the present application, and the method 700 can be regarded as a specific implementation of the method 600.
  • the method 700 can include the following steps.
  • S701 gNB (an example of the fifth network device) sends message #1 (an example of the fourth message) to CN (an example of the first device).
  • Message #1 includes the value range of the multicast configuration parameter and the identifier of area #1 (an example of the second area).
  • the value range of the multicast configuration parameter includes the value range of the MRB identifier and the value range of the LCH identifier.
  • the value range of the multicast configuration parameter may be pre-configured by OAM.
  • gNB sends message #2 (an example of the third message) to CN.
  • Message #2 is used to request the multicast configuration of multicast session #1.
  • Message #2 includes the identifier of multicast session #1, for example, TMGI-1.
  • message #2 includes the number of MRBs and the number of LCHs.
  • message #2 may also include an identifier of cell #1 (an example of a second cell), and the identifier of cell #1 is used to indicate that cell #1 managed by the gNB starts to provide inactive multicast session #1.
  • This step may refer to S610.
  • S703, CN determines multicast configuration #1 (an example of the first multicast configuration information) and area #2 (an example of the effective area of the first multicast configuration information) according to message #1 and message #2.
  • multicast configuration #1 includes MRB identifiers and LCH identifiers.
  • CN selects a corresponding number of MRB identifiers from the value range of the MRB identifier for multicast session #1, and selects a corresponding number of LCH identifiers from the value range of the LCH identifier for each MRB of multicast session #1.
  • area #2 may include the identifier of cell #1.
  • CN sends multicast configuration #1 to gNB and indicates the identifier of area #2.
  • gNB sends information #5 (an example of the twelfth information) to CN, and information #5 indicates acceptance of multicast configuration #1.
  • the gNB sends the identifier of multicast configuration #1 and area #2 to the UE.
  • the gNB sends the identifier of multicast configuration #1 and area #2 to the UE via an RRC release message.
  • gNB sends information #6 (an example of the eleventh information) to CN, and information #6 instructs cell #1 to stop providing inactive multicast session #1.
  • CN updates area #2 according to information #6, ie, removes cell #1 from the effective area of multicast configuration #1.
  • Fig. 12 is a schematic diagram of a communication method 800 provided in an embodiment of the present application, and the method 800 can be regarded as a specific implementation of the method 600.
  • the method 700 can include the following steps.
  • gNB#1 an example of the fifth network device
  • message #3 an example of the third message
  • gNB#2 an example of the first device and also an example of the sixth network device
  • Message #3 is used to request the multicast configuration of multicast session #1.
  • Message #3 includes the identifier of multicast session #1, for example, TMGI-1.
  • message #3 may also include the identifier of cell #2 (an example of the second cell), and the identifier of cell #2 is used to indicate that cell #2 managed by gNB #1 starts to provide inactive multicast session #1.
  • message #3 includes the number of MRBs and the number of LCHs.
  • This step may refer to S610.
  • gNB#2 determines multicast configuration #2 (an example of the first multicast configuration information) and area #3 (an example of the effective area of the first multicast configuration information) according to message #3 and the value range of the multicast configuration parameters.
  • the value range of the multicast configuration parameter can be pre-configured by OAM to the gNB within the RNA range, and the gNBs within the RNA range include gNB1 and gNB2.
  • multicast configuration #2 includes an MRB identifier and an LCH identifier.
  • gNB #2 selects a corresponding number of MRB identifiers for multicast session #1 from the value range of the MRB identifier, and selects a corresponding number of LCH identifiers for each MRB of multicast session #1 from the value range of the LCH identifier.
  • area #3 may include the identification of cell #2.
  • gNB#2 sends multicast configuration #2 to gNB#1 and indicates the identifier of area #3.
  • gNB#1 sends the identifier of multicast configuration #2 and area #3 to the UE.
  • gNB#1 sends the identifier of multicast configuration #2 and area #3 to the UE via an RRC release message.
  • gNB#1 sends information #7 (an example of the eleventh information) to gNB#2, and information #7 instructs cell #2 to stop providing inactive multicast session #1.
  • gNB #1 executes S805.
  • gNB#2 updates area #3 according to information #7, that is, removes cell #2 from the effective area of multicast configuration #1.
  • Fig. 13 is a schematic diagram of a communication method 900 provided in an embodiment of the present application, and the method 900 can be regarded as a specific implementation of the method 600.
  • the method 900 can include the following steps.
  • gNB#1 (an example of the fifth network device) sends message #4 (an example of the third message) to CN (an example of the first device).
  • Message #4 is used to request the multicast configuration of multicast session #1.
  • Message #4 includes the identifier of multicast session #1, for example, TMGI-1.
  • message #4 includes the number of MRBs and the number of LCHs.
  • message #4 may also include an identifier of cell #2 (an example of a second cell), and the identifier of cell #2 is used to indicate that cell #2 managed by gNB #1 starts to provide inactive multicast session #1.
  • This step may refer to S610.
  • gNB#2 determines multicast configuration #2 (an example of the first multicast configuration information) and area #3 (an example of the effective area of the first multicast configuration information) according to message #4 and the value range of the multicast configuration parameters.
  • S903 may refer to S802.
  • gNB#2 sends multicast configuration #2 to CN and indicates the identifier of area #3.
  • the CN may store multicast configuration #2 and area #3.
  • CN sends multicast configuration #2 to gNB #1 and indicates the identifier of area #3.
  • gNB#1 sends the identifier of multicast configuration #2 and area #3 to the UE.
  • S906 refers to S804.
  • gNB#1 sends information #7 (an example of the eleventh information) to CN, and information #7 instructs cell #2 to stop providing inactive multicast session #1.
  • gNB #1 executes S907.
  • gNB#2 updates area #3 according to information #7, that is, removes cell #2 from the effective area of multicast configuration #1.
  • Method 900 can be applicable to a scenario where there is no communication interface between gNB#1 and gNB#2.
  • the network device mentioned in each embodiment of the present application may refer to a base station, and the steps performed by any network device may be performed by the base station, by the CU of the base station, or by a module of the base station.
  • the methods and operations implemented by the terminal device can also be implemented by components that can be formed by the terminal device (such as chips or circuits); in addition, the methods and operations implemented by the network device can also be implemented by components that can be formed by the network device (such as chips or circuits), without limitation.
  • the embodiments of the present application also provide corresponding devices, which include modules for executing the corresponding methods in the above-mentioned method embodiments.
  • the module can be software, hardware, or a combination of software and hardware. It is understood that the technical features described in the above-mentioned method embodiments are also applicable to the following device embodiments.
  • Fig. 14 is a schematic diagram of a communication device 2800 provided in an embodiment of the present application.
  • the device 2800 includes a transceiver unit 2810, which can be used to implement corresponding communication functions.
  • the transceiver unit 2810 can also be called a communication interface or a communication unit.
  • the device 2800 may further include a processing unit 2820, which may be used for performing data processing.
  • a processing unit 2820 which may be used for performing data processing.
  • the device 2800 further includes a storage unit, which can be used to store instructions and/or data.
  • the processing unit 2820 The instructions and/or data in the storage unit can be read so that the apparatus implements the actions performed by the terminal device or the network device in the aforementioned various method embodiments.
  • the device 2800 may be the terminal device in the aforementioned embodiment, or may be a component (such as a module or chip) of the terminal device.
  • the device 2800 may implement the steps or processes executed by the terminal device in the above method embodiment, wherein the transceiver unit 2810 may be used to perform the transceiver-related operations of the terminal device in the above method embodiment, and the processing unit 2820 may be used to perform the processing-related operations of the terminal device in the above method embodiment.
  • apparatus 2800 is used to implement the functionality of a terminal device in the method embodiment shown in method 200 or 300 .
  • the transceiver unit 2810 is used to receive first information from a first network device, the first information includes at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, the at least one multicast configuration information includes the first multicast configuration information, and the index information corresponding to the at least one multicast configuration information includes the first index information; the transceiver unit 2810 is also used to: receive second information from a second network device, the second information is used to indicate that the first multicast session is associated with the first index information, and the first index information indicates the first multicast configuration information; the processing unit 2820 is used to: receive the first multicast session from the second network device in an inactive state or an idle state of the wireless resource control RRC according to the first multicast configuration information.
  • the device 2800 can also implement other steps, actions or methods related to the terminal device in the above method 200 or 300, which will not be repeated here.
  • apparatus 2800 is used to implement the functionality of a terminal device in the method embodiment shown in method 400 or 500 .
  • the transceiver unit 2810 is used to receive eighth information from the first network device, the eighth information including first multicast configuration information and information of a cell corresponding to the first multicast configuration information, the first multicast configuration corresponding to the first multicast session, and the cell information corresponding to the first multicast configuration information includes the first cell; the transceiver unit 2810 is also used to: receive a second message from the second network device, the second message including first indication information, the first indication information being used to indicate the status of a first multicast session provided by the first cell; the processing unit 2820 is used to: when the first cell is a resident cell of the terminal device, receive the first multicast session according to the first multicast configuration information.
  • the device 2800 can also implement other steps, actions or methods related to the terminal device in the above method 400 or 500, which will not be repeated here.
  • apparatus 2800 is used to implement the functionality of a terminal device in the method embodiments shown in method 600 , 700 , 800 , or 900 .
  • the transceiver unit 2810 is used to receive first multicast configuration information and tenth information from a fifth network device, the first multicast configuration information being used to configure a first multicast session, and the tenth information being used to indicate an effective area of the first multicast configuration information; the processing unit 2820 is used to receive the first multicast session in an inactive state or an idle state of a wireless resource control RRC according to the first multicast configuration information within the effective area.
  • the device 2800 can also implement other steps, actions or methods related to the terminal device in the above method 600, 700, 800 or 900, which will not be repeated here.
  • the device 2800 may be the third network device in the aforementioned embodiment, or may be a component (such as a module or chip) of the third network device.
  • the device 2800 may implement the steps or processes corresponding to those performed by the third network device in the above method embodiment, wherein the transceiver unit 2810 may be used to perform the transceiver-related operations of the third network device in the above method embodiment, and the processing unit 2820 may be used to perform the processing-related operations of the third network device in the above method embodiment.
  • the device 2800 is used to implement the function of the third network device in the method embodiment shown in method 200 or 300.
  • the third network device can be the first network device in method 200 or 300, or the second network device.
  • the transceiver unit 2810 is used to send second information, where the second information is used to indicate that the first multicast session is associated with first index information, and the first index information indicates first multicast configuration information; the transceiver unit 2810 is also used to send the first multicast session according to the first multicast configuration information.
  • the transceiver unit 2810 is also used to send first information to the terminal device, the first information including at least one multicast configuration information and at least one index information corresponding to the multicast configuration information, the at least one multicast configuration information including the first multicast configuration information, and the index information corresponding to the at least one multicast configuration information including the first index information.
  • the device 2800 can also implement other steps, actions or methods related to the third network device in the above method 200 or 300, which will not be repeated here.
  • the device 2800 is used to implement the function of the third network device in the method embodiment shown in method 400 or 500.
  • the third network device can be the first network device in method 400 or 500, or the second network device.
  • the transceiver unit 2810 is used to send a second message, the second message includes first indication information, and the first indication information is used to indicate that the state of the first multicast session provided by the first cell has changed; the transceiver unit 2810 is also used to send the first multicast session according to the first multicast configuration information.
  • the transceiver unit 2810 is also used to send eighth information to the terminal device, the eighth information including first multicast configuration information and cell information corresponding to the first multicast configuration information, the first multicast configuration corresponds to the first multicast session, and the cell information corresponding to the first multicast configuration information includes the first cell.
  • the device 2800 can also implement other steps, actions or methods related to the third network device in the above method 400 or 500, which will not be repeated here.
  • the device 2800 may be the fourth network device in the aforementioned embodiment, or may be a component (such as a module or chip) of the fourth network device.
  • the device 2800 may implement the steps or processes corresponding to those performed by the fourth network device in the above method embodiment, wherein the transceiver unit 2810 may be used to perform the transceiver-related operations of the fourth network device in the above method embodiment, and the processing unit 2820 may be used to perform the processing-related operations of the fourth network device in the above method embodiment.
  • the apparatus 2800 is used to implement the functionality of the fourth network device in the method embodiment shown in method 200 or 300 .
  • the transceiver unit 2810 is used to send sixth information to the third network device, the sixth information including M multicast configuration information and index information corresponding to the M multicast configuration information; or, the sixth information includes M multicast configuration information, M is a positive integer; the transceiver unit 2810 is also used to receive first information from the third network device, the first information including at least one multicast configuration information and index information corresponding to at least one multicast configuration information, and the at least one multicast configuration information includes M multicast configuration information.
  • the device 2800 may be the fifth network device in the aforementioned embodiment, or may be a component (such as a module or chip) of the fifth network device.
  • the device 2800 may implement the steps or processes corresponding to those performed by the fifth network device in the above method embodiment, wherein the transceiver unit 2810 may be used to perform the transceiver-related operations of the fifth network device in the above method embodiment, and the processing unit 2820 may be used to perform the processing-related operations of the fifth network device in the above method embodiment.
  • apparatus 2800 is used to implement the functionality of the fifth network device in the method embodiments shown in method 600 , 700 , 800 , or 900 .
  • the transceiver unit 2810 is used to send a third message to the first device, the third message is used to request multicast configuration information of the first multicast session, and the transceiver unit 2810 is also used to: receive first multicast configuration information from the first device, the first multicast configuration information is determined according to the third message and the value range of the multicast configuration parameter, and the first multicast configuration information is used to configure the terminal device to receive the first multicast session in the inactive state or idle state of the wireless resource control RRC.
  • the device 2800 can also implement other steps, actions or methods related to the fifth network device in the above method 600, 700, 800 or 900, which will not be repeated here.
  • the device 2800 may be the first device in the aforementioned embodiment, or may be a component (such as a module or chip) of the first device.
  • the device 2800 may implement the steps or processes corresponding to those performed by the first device in the above method embodiment, wherein the transceiver unit 2810 may be used to perform the transceiver-related operations of the first device in the above method embodiment, and the processing unit 2820 may be used to perform the processing-related operations of the first device in the above method embodiment.
  • apparatus 2800 is used to implement the functionality of the first device in the method embodiments shown in method 600 , 700 , 800 , or 900 .
  • the transceiver unit 2810 is used to receive a third message from the fifth network device, the third message is used to request multicast configuration information of the first multicast session.
  • the processing unit 2820 is used to determine the first multicast configuration information according to the third message and the value range of the multicast configuration parameter, the first multicast configuration information is used to configure the terminal device to receive the first multicast session in the radio resource control RRC inactive state or idle state; the transceiver unit 2810 is also used to: send the first multicast configuration information to the fifth network device.
  • the device 2800 can also implement other steps, actions or methods related to the first device in the above method 600, 700, 800 or 900, which will not be repeated here.
  • the device 2800 can also implement other steps, actions or methods related to the fourth network device in the above method 200 or 300, which will not be repeated here.
  • the apparatus 2800 is used to implement the functionality of the fourth network device in the method embodiment shown in method 400 or 500.
  • the transceiver unit 2810 is used to send second indication information to a third network device, the second indication information being used to indicate the status of a first multicast session in a non-connected state or an idle state provided by a first cell, and the first cell is a cell managed by a second network device; the transceiver unit 2810 is also used to send a second message, the second message including the first indication information, and the first indication information being used to indicate the status of a first multicast session in a non-connected state or an idle state provided by the first cell.
  • the device 2800 can also implement other steps, actions or methods related to the fourth network device in the above method 400 or 500, which will not be repeated here.
  • the device 2800 here is embodied in the form of a functional unit.
  • the term "unit” here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and/or other suitable components that support the described functions.
  • ASIC application specific integrated circuit
  • processor such as a shared processor, a dedicated processor or a group processor, etc.
  • memory for executing one or more software or firmware programs, a merged logic circuit and/or other suitable components that support the described functions.
  • the device 2800 can be specifically the terminal device in the above-mentioned embodiment, and can be used to execute the various processes and/or steps corresponding to the terminal device in the above-mentioned method embodiments, or the device 2800 can be specifically the third network device in the above-mentioned embodiment, and can be used to execute the various processes and/or steps corresponding to the third network device in the above-mentioned method embodiments, or the device 2800 can be specifically the fourth network device in the above-mentioned embodiment, and can be used to execute the various processes and/or steps corresponding to the fourth network device in the above-mentioned method embodiments. To avoid repetition, it is not repeated here.
  • the device 2800 of each of the above schemes has the function of implementing the corresponding steps performed by the terminal device in the above method, or the device 2800 of each of the above schemes has the function of implementing the corresponding steps performed by the third network device in the above method, or the device 2800 of each of the above schemes has the function of implementing the corresponding steps performed by the fourth network device in the above method, or the device 2800 of each of the above schemes has the function of implementing the corresponding steps performed by the fifth network device in the above method, or the device 2800 of each of the above schemes has the function of implementing the corresponding steps performed by the first device in the above method.
  • the functions can be implemented by hardware, or by hardware executing corresponding software implementations.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor, respectively performing the transceiver operations and related processing operations in each method embodiment.
  • the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor, respectively performing the transceiver operations and related processing operations in each method embodiment.
  • transceiver unit 2810 can also be a transceiver circuit (for example, can include a receiving circuit and a sending circuit), and the processing unit can be a processing circuit.
  • the device in FIG. 10 may be a network element or device in the aforementioned embodiment, or may be a chip or a chip system, such as a system on chip (SoC).
  • the transceiver unit may be an input and output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.
  • the device 2900 includes a processor 2910, the processor 2910 is coupled to a memory 2920, the memory 2920 is used to store computer programs or instructions and/or data, and the processor 2910 is used to execute the computer program or instructions stored in the memory 2920, or read the data stored in the memory 2920, so as to execute the methods in the above method embodiments.
  • processors 2910 there are one or more processors 2910 .
  • memory 2920 is one or more.
  • the memory 2920 is integrated with the processor 2910 or provided separately.
  • the device 2900 further includes an interface circuit 2930.
  • the interface circuit 2930 is used for receiving and/or sending signals.
  • the processor 2910 and the interface circuit 2930 are coupled to each other.
  • the processor 2910 is used to control the interface circuit 2930 to receive and/or send signals.
  • the interface circuit 2930 may be a transceiver or an input/output interface.
  • the processor 2910 is used to implement the function of the above-mentioned processing unit 920, and the interface circuit 2930 is used to implement the function of the above-mentioned transceiver unit 910.
  • the device 2900 is used to implement the operations performed by the terminal device in the above method embodiments.
  • the processor 2910 is used to execute the computer program or instructions stored in the memory 2920 to implement the relevant operations of the terminal device in the above various method embodiments.
  • the method executed by the terminal device in the embodiment shown in FIG. 5 or FIG. 7, and for example, FIG. 8 or FIG. 9 The method executed by the terminal device in the embodiment shown.
  • the apparatus 2900 is used to implement the operations performed by the third network device in each of the above method embodiments.
  • the processor 2910 is used to execute the computer program or instructions stored in the memory 2920 to implement the relevant operations of the third network device in each method embodiment above.
  • the method performed by the third network device in the embodiment shown in Figure 5 or Figure 7 and for example, the method performed by the third network device in the embodiment shown in Figure 8 or Figure 9.
  • the apparatus 2900 is used to implement the operations performed by the fourth network device in each of the above method embodiments.
  • the processor 2910 is used to execute the computer program or instructions stored in the memory 2920 to implement the relevant operations of the fourth network device in each method embodiment above.
  • the method performed by the fourth network device in the embodiment shown in Figure 5 or Figure 7 and for example, the method performed by the fourth network device in the embodiment shown in Figure 8 or Figure 9.
  • the apparatus 2900 is used to implement the operations performed by the fifth network device in each of the above method embodiments.
  • the processor 2910 is used to execute the computer program or instructions stored in the memory 2920 to implement the relevant operations of the fifth network device in each method embodiment above.
  • the apparatus 2900 is used to implement the operations performed by the first device in each of the above method embodiments.
  • the processor 2910 is used to execute the computer program or instructions stored in the memory 2920 to implement the relevant operations of the first device in each method embodiment above.
  • the terminal chip When the above communication device is a chip applied to a terminal, the terminal chip implements the functions of the terminal in the above method embodiment.
  • the terminal chip receives information from other modules in the terminal (such as a radio frequency module or an antenna), and the information is sent by the base station to the terminal; or the terminal chip sends information to other modules in the terminal (such as a radio frequency module or an antenna), and the information is sent by the terminal to the base station.
  • processors mentioned in the embodiments of the present application may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.
  • the memory mentioned in the embodiments of the present application may be a volatile memory and/or a non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory.
  • the volatile memory may be a random access memory (RAM).
  • a RAM may be used as an external cache.
  • RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct rambus RAM (DR RAM).
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous link DRAM
  • DR RAM direct rambus RAM
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.
  • memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.
  • FIG16 is a schematic diagram of a chip system 3000 provided in an embodiment of the present application.
  • the chip system 3000 (or also referred to as a processing system) includes a logic circuit 3010 and an input/output interface 3020.
  • the logic circuit 3010 can be a processing circuit in the chip system 3000.
  • the logic circuit 3010 can be coupled to the storage unit and call the instructions in the storage unit so that the chip system 3000 can implement the methods and functions of each embodiment of the present application.
  • the input/output interface 3020 can be an input/output circuit in the chip system 3000, outputting information processed by the chip system 3000, or inputting data or signaling information to be processed into the chip system 3000 for processing.
  • the chip system 3000 is used to implement the operations performed by the terminal device in the above method embodiments.
  • the logic circuit 3010 is used to implement the processing-related operations performed by the terminal device in the above method embodiments, such as the processing-related operations performed by the terminal device in the embodiments shown in Figures 5, 7, 8, 9, 10, 11, 12 or 13; input
  • the output/output interface 3020 is used to implement the sending and/or receiving related operations performed by the terminal device in the above method embodiments, such as the sending and/or receiving related operations performed by the terminal device in the embodiments shown in Figures 5, 7, 8, 9, 10, 11, 12 or 13.
  • the chip system 3000 is used to implement the operations performed by the third network device in the above method embodiments.
  • the logic circuit 3010 is used to implement the processing-related operations performed by the third network device in the above method embodiments, such as the processing-related operations performed by the third network device in the embodiments shown in Figures 5, 7, 8 or 9;
  • the input/output interface 3020 is used to implement the sending and/or receiving-related operations performed by the third network device in the above method embodiments, such as the sending and/or receiving-related operations performed by the third network device in the embodiments shown in Figures 5, 7, 8 or 9.
  • the chip system 3000 is used to implement the operations performed by the fourth network device in the above method embodiments.
  • the logic circuit 3010 is used to implement the processing-related operations performed by the fourth network device in the above method embodiments, such as the processing-related operations performed by the fourth network device in the embodiments shown in Figures 5, 7, 8 or 9;
  • the input/output interface 3020 is used to implement the sending and/or receiving-related operations performed by the fourth network device in the above method embodiments, such as the sending and/or receiving-related operations performed by the fourth network device in the embodiments shown in Figures 5, 7, 8 or 9.
  • the chip system 3000 is used to implement the operations performed by the fifth network device in the above method embodiments.
  • the logic circuit 3010 is used to implement the processing-related operations performed by the fifth network device in the above method embodiments, such as the processing-related operations performed by the fifth network device in the embodiments shown in Figures 10, 11, 12 or 13;
  • the input/output interface 3020 is used to implement the sending and/or receiving-related operations performed by the fifth network device in the above method embodiments, such as the sending and/or receiving-related operations performed by the fifth network device in the embodiments shown in Figures 10, 11, 12 or 13.
  • the chip system 3000 is used to implement the operations performed by the first device in each of the above method embodiments.
  • the logic circuit 3010 is used to implement the processing-related operations performed by the first device in the above method embodiments, such as the processing-related operations performed by the first device in the embodiments shown in Figures 10, 11, 12 or 13;
  • the input/output interface 3020 is used to implement the sending and/or receiving-related operations performed by the first device in the above method embodiments, such as the sending and/or receiving-related operations performed by the first device in the embodiments shown in Figures 10, 11, 12 or 13.
  • An embodiment of the present application also provides a computer-readable storage medium on which computer instructions are stored for implementing the methods executed by the terminal device, the third network device, the fourth network device, the fifth network device or the first device in the above-mentioned method embodiments.
  • the computer when the computer program is executed by a computer, the computer can implement the method performed by the terminal device, the third network device, the fourth network device, the fifth network device or the first device in each embodiment of the above method.
  • An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by the terminal device, the third network device, the fourth network device, the fifth network device or the first device in the above-mentioned method embodiments.
  • the embodiment of the present application also provides a communication system, which includes the third network device and the fourth network device in the above embodiments.
  • the system includes the third network device and the fourth network device in the embodiment shown in Figure 5 or Figure 7, and for another example, the system includes the third network device and the fourth network device in the embodiment shown in Figure 8 or Figure 9.
  • the embodiment of the present application further provides a communication system, which includes the fifth network device and the first device in the above embodiments.
  • the system includes the fifth network device and the first device in the embodiment shown in Figure 10, Figure 11, Figure 12 or Figure 13.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof.
  • all or part of the embodiments can be implemented in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiments of the present application is generated in whole or in part.
  • the computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer can be a personal computer, a server, or a network device.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium.
  • the command can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated.
  • the available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD), etc.
  • the aforementioned available medium includes, but is not limited to: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

Abstract

一种通信方法和通信装置。该方法可以包括：在终端设备处于连接态时，第一网络设备将组播配置资源池预配置给终端设备，该组播配置资源池可以包括第一组播会话关联的多个组播配置信息，进而第二网络设备可以通过第二信息中的第一索引信息向终端设备指示接收第一组播会话所需的第一组播配置信息。如此，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。

Description

一种通信的方法和装置
本申请要求申请日为2022年9月29日、申请号为202211203248.9、申请名称为“一种通信的方法和装置”的中国发明专利申请的优先权，以及申请日为2022年11月04日、申请号为202211378635.6、申请名称为“一种通信的方法和装置”的中国发明专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种通信的方法和装置。
背景技术
组播广播业务(multicast and broadcast service，MBS)可以以较少的资源为大量具有相同需求的用户同时提供数据，使得网络资源可以得到共享。在第三代合作伙伴计划(3rd generation partnership project，3GPP)版本(release，R)17中，终端设备在连接态接收MBS。对于加入MBS会话且处于RRC连接态的终端设备，网络设备可以先向终端设备发送MBS配置，进一步，终端设备可以根据MBS配置接收MBS。
为了缓解网络拥塞，R18提出支持终端设备在RRC非激活态接收MBS。例如，当终端设备没有单播业务，仅有MBS时，网络可以将终端设备释放到RRC非激活态，终端设备可以在RRC非激活态接收MBS。如此，能够减少网络中处于RRC连接态的终端设备的数目，有利于缓解网络拥塞，也有利于终端设备节能。
然而，对于终端设备如何获取RRC非激活态的MBS配置，对MBS的接收是一个亟待解决的问题。
发明内容
本申请提供一种通信的方法和装置，使得终端设备能够在RRC非激活态接收MBS，有利于缓解网络拥塞，也有利于终端设备节能。
第一方面，提供了一种通信方法，该方法可以由终端设备执行，或者，也可以由终端设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。
该方法可以包括：终端设备接收来自第一网络设备的第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息；终端设备接收来自第二网络设备的第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息；终端设备根据第一组播配置信息在无线资源控制RRC非激活态或空闲态接收来自第二网络设备的第一组播会话。
根据上述方案，在终端设备处于连接态时，第一网络设备将组播配置资源池预配置给终端设备，该组播配置资源池可以包括第一组播会话关联的多个组播配置信息，进而第二网络设备可以通过第二信息向终端设备指示接收第一组播会话所需的第一组播配置信息。如此，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
可选地，第一信息还包括至少一个组播配置信息对应的小区或网络设备的标识信息。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：终端设备获取第一标识，第一标识为终端设备的驻留小区的标识或驻留小区对应的网络设备的标识，第一标识与第一组播配置信息之间具有对应关系；终端设备根据第一标识和第一索引信息确定第一组播配置信息。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：终端设备接收来自于第一网络设备的第三信息，第三信息用于指示至少一个组播配置信息的生效区域。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：终端设备接收来自于第一网络设 备或第二网络设备的第四信息，第四信息用于指示第一组播会话对应的第一G-RNTI；终端设备根据第一G-RNTI解扰第一组播会话。
结合第一方面，在第一方面的某些实现方式中，第四信息为第一G-RNTI的信息；或，第四信息为第一G-RNTI的索引信息，第一G-RNTI的索引信息与第一G-RNTI具有对应关系；或，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
结合第一方面，在第一方面的某些实现方式中，第一索引信息包括以下一项或多项：组播无线承载MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、公共频域资源CFR配置索引、半持续调度(semi-persistent scheduling，SPS)配置索引。
结合第一方面，在第一方面的某些实现方式中，若满足以下任一种条件，则终端设备接收第二信息：终端设备重选至第二网络设备管理的小区；或，终端设备接收到来自第五信息，其中，第五信息用于通知系统消息变更；或，第五信息用于通知组播控制信道消息变更；或，第五信息用于通知第一组播会话激活；第五信息用于指示终端设备在RRC非激活态或空闲态接收组播会话；
其中，系统变更通知消息或通知组播控制信道消息变更用于：
通知第一组播会话的组播配置信息变更为第一组播配置信息，或者，通知第二网络设备管理的小区开始在非激活态或空闲态提供第一组播会话。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：终端设备接收来自第二网络设备的第一消息，第一消息为系统消息或组播控制信道消息，第一消息用于指示停止接收第一组播会话或者第二网络设备管理的小区停止在非激活态提供第一组播会话。
可选地，该方法还包括：终端设备根据所述第一消息确定是否恢复RRC连接。
可选地，所述第一消息指示所述第一组播会话去激活，所述终端设备保持在RRC非激活态或空闲态，停止接收所述第一组播会话。
可选地，所述终端设备接收所述第一消息，所述第一消息中不包括所述第一组播会话的标识。
可选地，终端设备接收所述第一消息，所述第一消息中包括所述第一组播会话的标识，且不包括所述第一索引信息。
具体地，若第一消息中包括第一组播会话的标识，且不包括第一索引信息，终端设备停止接收第一组播会话；或，第一消息中不包括第一组播会话的标识，终端设备向第二网络设备发送RRC恢复请求消息，并进入RRC连接态接收第一组播会话。
可选地，第二信息承载于以下任一种：系统消息、组播控制信道消息、RRC释放消息。
第二方面，提供了一种通信方法，该方法可以由第三网络设备执行，或者，也可以由第三网络设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。其中，该第三网络设备可以是第一方面中的第一网络设备，也可以是第一方面中的第二网络设备。
该方法可以包括：第三网络设备发送第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息；第三网络设备根据第一组播配置信息发送第一组播会话。
根据上述方案，第三网络设备可以通过第二信息向终端设备指示接收第一组播会话所需的第一组播配置信息。如此，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备向终端设备发送第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息；
结合第二方面，在第二方面的某些实现方式中，第一信息还包括至少一个组播配置信息对应的小区或网络设备的标识信息。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备发送第一标识，第一标识为第三网络设备的标识或第二信息对应的小区的标识。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备获取第一信息。
结合第二方面，在第二方面的某些实现方式中，第三网络设备获取第一信息，包括：第三网络设备接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；第三网络设备确定N个组播配置信息和N个组播配置信息对应的索引信息；其中，至少一个 组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。
结合第二方面，在第二方面的某些实现方式中，第三网络设备获取第一信息，包括：第三网络设备确定N个组播配置信息；第三网络设备接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息；第三网络设备根据M个配置信息和N个组播配置信息确定M个组播配置信息和N个组播配置信息对应的索引信息；其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。
可选地，第六信息还包括M个组播配置信息对应的小区的标识信息。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备向第四网络设备发送第一信息。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备向终端设备发送第三信息，第三信息用于指示至少一个组播配置信息的生效区域。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备向终端设备发送第四信息，第四信息用于指示第一G-RNTI，第一G-RNTI用于加扰第一组播会话。
可选地，第四信息为第一G-RNTI的信息；或，第四信息为第一G-RNTI的索引信息，第一G-RNTI的索引信息与第一G-RNTI具有对应关系；或，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
结合第二方面，在第二方面的某些实现方式中，第四信息为第一G-RNTI的信息，该方法还包括：第三网络设备接收来自核心网设备的第一G-RNRI；或，第三网络设备根据第一组播会话的标识确定第一G-RNTI。
结合第二方面，在第二方面的某些实现方式中，第一索引信息包括以下一项或多项：组播无线承载MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、公共频域资源CFR配置索引、半持续调度SPS配置索引。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备发送第五信息，第五信息用于通知系统消息变更或用于通知组播控制信道消息变更，第五信息用于终端设备接收第二信息。
结合第二方面，在第二方面的某些实现方式中，若满足以下任一条件，则第三网络设备向终端设备发送第五信息：第一组播会话的组播配置信息变更为第一组播配置信息；或，第三网络设备管理的小区开始在非激活态或空闲态提供第一组播会话。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备发送第一消息，第一消息为系统消息、组播控制信道消息，第一消息用于指示第一组播会话处于去激活状态或被释放，或者用于指示第二网络设备管理的小区停止在非激活态提供第一组播会话。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：第三网络设备发送第一消息，第一消息为系统消息、组播控制信道消息，第一消息用于指示第一组播会话处于去激活状态或被释放，或者用于指示第二网络设备管理的小区停止在非激活态提供第一组播会话。
可选地，第三网络设备确定第一组播会话处于去激活状态或被释放，第三网络设备发送第一消息，第一消息包括第一组播会话的标识，且第一消息不包括第一索引信息；或，第三网络设备管理的小区停止在RRC非激活态或空闲态提供第一组播会话，第三网络设备发送第一消息，第一消息不包括第一组播会话的标识。
第三方面，提供了一种通信方法，该方法可以由第四网络设备执行，或者，也可以由第四网络设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。
该方法可以包括：第四网络设备向第三网络设备发送第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；或，第六信息包括M个组播配置信息，M为正整数；第四网络设备接收来自第三网络设备的第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括M个组播配置信息。
根据上述方案，第四网络设备可以向第三网络设备发送其确定的M个组播配置信息。如此，使得第三网络设备能够确定第一信息。进一步，第三网络设备可以通过第一信息和索引信息向终端设备指示组播配置，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免 终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
结合第三方面，在第三方面的某些实现方式中，该方法还包括：第四网络设备发送第七信息，第七信息用于指示第一组播会话关联第二索引信息，第二索引信息指示第二组播配置信息，至少一个组播配置信息包括第二组播配置信息，至少一个组播配置信息对应的索引信息包括第二索引信息；第四网络设备根据第二组播配置信息发送第一组播会话。
第四方面，提供了一种通信方法，该方法可以由终端设备执行，或者，也可以由终端设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。
该方法可以包括：终端设备接收来自第一网络设备的第八信息，第八信息包括第一组播配置信息和第一组播配置信息对应的小区的信息，第一组播配置对应第一组播会话，第一组播配置信息对应的小区信息包括第一小区；终端设备接收来自第二网络设备的第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的第一组播会话的状态；在第一小区为终端设备的驻留小区的情况下，终端设备根据第一组播配置信息接收第一组播会话。
基于上述方案，在终端设备处于连接态时，第一网络设备将第一组播配置信息对应的小区的信息预配置给终端设备，第二网络设备可以通过第二消息中的第一指示信息向终端设备指示各个小区的组播会话的状态，在某个小区为终端设备的服务小区，且该小区开始提供非激活态或空闲态的组播会话，终端设备可以使用第一组播配置信息接收该组播会话。如此，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
其中，第一组播会话的状态，包括：第一小区正在或未在提供RRC非激活态或空闲态的第一组播会话，或者，第一小区开始或停止提供RRC非激活态或空闲态的第一组播会话；或，第一组播会话对应的组播配置信息发生变化。
结合第四方面，在第四方面的某些实现方式中，终端设备根据第一组播配置信息接收第一组播会话，包括：在第一指示信息指示第一小区开始在RRC非激活态或空闲态提供第一组播会话的情况下，终端设备根据第一组播配置信息在RRC非激活态或空闲态接收第一组播会话；或，在第一指示信息指示第一小区停止在RRC非激活态或空闲态提供第一组播会话的情况下，终端设备向第一小区对应的网络设备发送RRC恢复请求消息。
可选地，第二消息为寻呼消息或RRC释放消息。
例如，RRC释放消息指示UE进入inactive态收组播，UE使用第一组播配置收组播；或者，RRC释放消息指示EU进入inacitve态收组播，且RRC释放消息中携带更新的组播配置，UE根据该更新的组播配置收组播。
结合第四方面，在第四方面的某些实现方式中，第八信息承载于RRC释放消息或RRC重配置消息。
结合第四方面，在第四方面的某些实现方式中，第一指示信息为比特位图，比特位图中的至少一个比特关联于第一小区。
结合第四方面，在第四方面的某些实现方式中，第一组播配置信息对应的小区信息包括Q个小区，比特位图包括Q个比特，Q个比特和Q个小区一一对应。
结合第四方面，在第四方面的某些实现方式中，第八信息还包括至少一个组播配置信息、至少一个组播配置信息对应的索引信息、至少一个组播配置信息对应的小区信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息，至少一个组播配置信息对应的小区信息包括第一小区。
结合第四方面，在第四方面的某些实现方式中，第二消息还包括第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息。
结合第四方面，在第四方面的某些实现方式中，第一索引信息包括以下一项或多项：MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、CFR配置索引、SPS配置索引。
结合第四方面，在第四方面的某些实现方式中，该方法还包括：终端设备接收来自于第一网络设备或第二网络设备的第四信息，第四信息用于指示第一组播会话对应的第一G-RNTI；终端设备根据第一G-RNTI解扰第一组播会话。
结合第四方面，在第四方面的某些实现方式中，第四信息为第一G-RNTI的信息；或，第四信息为第一G-RNTI的索引信息，第一G-RNTI的索引信息与第一G-RNTI具有对应关系；或，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
第五方面，提供了一种通信方法，该方法可以由第三网络设备执行，或者，也可以由第三网络设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。其中，该第三网络设备可以是第四方面中的第一网络设备，也可以是第四方面中的第二网络设备。
该方法可以包括：第三网络设备发送第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的第一组播会话的状态发生变化；第三网络设备根据第一组播配置信息发送第一组播会话。
基于上述方案，在终端设备处于连接态时，第三网络设备将第一组播配置信息对应的小区的信息预配置给终端设备，第三网络设备还可以通过第二消息中的第一指示信息向终端设备指示各个小区的组播会话的状态，使得：在某个小区为终端设备的服务小区，且该小区开始提供非激活态或空闲态的组播会话，终端设备可以使用第一组播配置信息接收该组播会话。如此，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
其中，第一组播会话的状态，包括：第一小区正在或未在提供RRC非激活态或空闲态的第一组播会话，或者，第一小区开始或停止提供RRC非激活态或空闲态的第一组播会话；或，第一组播会话对应的组播配置信息发生变化。
可选地，第三网络设备为第四方面中的第一网络设备，或者为第四方面中的第二网络设备。
可选地，该方法还包括：第三网络设备向终端设备发送第八信息，第八信息包括第一组播配置信息和第一组播配置信息对应的小区信息，第一组播配置对应第一组播会话，第一组播配置信息对应的小区信息包括第一小区。
结合第五方面，在第五方面的某些实现方式中，第八信息承载于RRC释放消息或RRC重配置消息。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：第三网络设备接收来自第四网络设备的第九信息，第九信息用于指示第一组播配置信息对应的R个小区的标识，第一组播配置信息对应的小区信息包括R个小区，R为正整数。
结合第五方面，在第五方面的某些实现方式中，第一指示信息为比特位图，比特位图中的至少一个比特关联于第一小区。
可选地，第一组播配置信息对应的小区信息包括Q个小区，比特位图包括Q个比特，Q个比特和Q个小区一一对应。
结合第五方面，在第五方面的某些实现方式中，第八信息还包括至少一个组播配置信息、至少一个组播配置信息对应的索引信息、至少一个组播配置信息对应的小区信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息，至少一个组播配置信息对应的小区信息包括第一小区。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：第三网络设备接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；第三网络设备确定N个组播配置信息和N个组播配置信息对应的索引信息；
其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。
结合第五方面，在第五方面的某些实现方式中，第三网络设备获取第一信息，包括：
第三网络设备确定N个组播配置信息；第三网络设备接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息；第三网络设备根据M个配置信息和N个组播配置信息确定M个组播配置信息和N个组播配置信息对应的索引信息；
其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。
结合第五方面，在第五方面的某些实现方式中，第六信息还包括M个组播配置信息对应的小区的标识信息。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：第三网络设备向第四网络设备发 送第八信息。
结合第五方面，在第五方面的某些实现方式中，第二消息还包括第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息。
结合第五方面，在第五方面的某些实现方式中，第一索引信息包括以下一项或多项：
MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、CFR配置索引、SPS配置索引。
结合第五方面，在第五方面的某些实现方式中，该方法还包括：第三网络设备向终端设备发送第四信息，第四信息用于指示第一G-RNTI，第一G-RNTI用于加扰第一组播会话。
结合第五方面，在第五方面的某些实现方式中，第四信息为第一G-RNTI的信息；或，第四信息为第一G-RNTI的索引信息，第一G-RNTI的索引信息与第一G-RNTI具有对应关系；或，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
结合第五方面，在第五方面的某些实现方式中，第四信息为第一G-RNTI的信息，该方法还包括：第三网络设备接收来自核心网设备的第一G-RNRI；或，第三网络设备根据第一组播会话的标识确定第一G-RNTI。
结合第五方面，在第五方面的某些实现方式中，第一小区为第三网络设备管理的小区。
结合第五方面，在第五方面的某些实现方式中，在第三网络设备向终端设备发送第二消息之前，该方法还包括：第三网络设备接收来自第四网络设备的第二指示信息，第二指示信息用于指示第一小区提供的第一组播会话的状态发送变化，第一小区为第四网络设备管理的小区。
第六方面，提供了一种通信方法，该方法可以由第四网络设备执行，或者，也可以由第四网络设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。
该方法可以包括：第四网络设备向第三网络设备发送第二指示信息，第二指示信息用于指示第一小区提供的非连接态或空闲态第一组播会话的状态，第一小区为第二网络设备管理的小区；第四网络设备发送第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的在非连接态或空闲态的第一组播会话的状态。
根据上述方案，第四网络设备可以向第三网络设备发送其管理的小区提供的在非连接态或空闲态的第一组播会话的状态。此外，第四网络设备也能够发送第二消息，通过第一指示信息向终端设备指示各个小区的组播会话的状态，使得：在某个小区为终端设备的服务小区，且该小区开始提供非激活态或空闲态的组播会话，终端设备可以使用第一组播配置信息接收该组播会话。一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
其中，第一组播会话的状态，包括：第一小区正在或未在提供RRC非激活态或空闲态的第一组播会话，或者，第一小区开始或停止提供RRC非激活态或空闲态的第一组播会话；或，第一组播会话对应的组播配置信息发生变化。
结合第六方面，在第六方面的某些实现方式中，该方法还包括：第四网络设备向第三网络设备发送第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；或，第六信息包括M个组播配置信息，M为正整数；第四网络设备接收来自第三网络设备的第八信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括M个组播配置信息。
第七方面，提供了一种通信方法，该方法可以由终端设备执行，或者，也可以由终端设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。
该方法可以包括：终端设备接收来自第五网络设备的第一组播配置信息和第十信息，第一组播配置信息用于配置第一组播会话，第十信息用于指示第一组播配置信息的生效区域；终端设备在生效区域内，根据第一组播配置信息在无线资源控制RRC非激活态或空闲态接收第一组播会话。
基于上述方案，终端设备能够获得接收第一组播会话的第一组播配置信息，还可以获得该第一组播配置信息的生效区域，当终端设备在该区域内移动时，终端设备可以继续使用该组播配置信息接收组播会话，能够保证终端设备接收组播业务的连续性。
另一方面，可以避免终端设备在每次小区重选到新小区时都触发RRC连接恢复，能够节省终端设 备的能耗，也能够节省空口信令开销。
第八方面，提供了一种通信方法，该方法可以由第五网络设备执行，或者，也可以由第五网络设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。
该方法可以包括：第五网络设备向第一设备发送第三消息，第三消息用于请求第一组播会话的组播配置信息；第五网络设备接收来自第一设备的第一组播配置信息，第一组播配置信息根据第三消息和组播配置参数的取值范围确定，第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收第一组播会话。
基于上述方案，第一设备可以为一个或多个第五网络设备提供的第一组播会话确定第一组播配置信息，换言之，第一设备可以为第一组播会话确定一个或多个第五网络设备均可以使用的第一组播配置信息，使得对于同一组播会话，一个区域内支持第一组播会话的不同网络设备可以使用同样的组播配置信息，如此，能够同步区域内的组播配置信息。
另一方面，当终端设备在该区域内移动时，终端设备可以继续使用该组播配置信息接收组播会话，能够保证终端设备接收组播业务的连续性。
结合第八方面，在第八方面的某些实现方式中，该方法还包括：第五网络设备向终端设备发送第一组播配置信息。
结合第八方面，在第八方面的某些实现方式中，该组播配置参数的取值范围包括以下至少一个：G-RNTI的取值范围、组播无线承载MRB标识的取值范围、逻辑信道LCH标识的取值范围、物理信道配置参数的取值范围、非连续接收DRX配置参数的取值范围、公共频域资源CFR配置参数的取值范围。
结合第八方面，在第八方面的某些实现方式中，该第三消息包括以下至少一项：第一组播会话的标识、第一组播会话所需的MRB的数目、第一组播会话的第一MRB所需的逻辑信道LCH的数目。
结合第八方面，在第八方面的某些实现方式中，该第三消息包括第二小区的标识，第二小区为由第五网络设备管理的、提供RRC非激活态或空闲态的第一组播会话的小区。
结合第八方面，在第八方面的某些实现方式中，该方法还包括：第五网络设备接收来自第一设备的第十信息，第十信息指示第一组播配置信息的生效区域。
结合第八方面，在第八方面的某些实现方式中，该方法还包括：第五网络设备向第一设备发送第四消息，第四消息包括组播配置参数的取值范围。
结合第八方面，在第八方面的某些实现方式中，该第四消息还包括第二区域的标识信息，第二区域为组播配置参数的取值范围的生效区域。
结合第八方面，在第八方面的某些实现方式中，该第二区域内的小区提供至少一个组播会话，至少一个组播会话包括第一组播会话，至少一个组播会话中除第一组播会话之外的其他组播会话的组播配置信息和第一组播配置信息不同，至少一个组播会话的组播配置信息互不相同。
结合第八方面，在第八方面的某些实现方式中，该第二区域为第五网络设备所在的基于无线接入网络的通知区域RNA。
结合第八方面，在第八方面的某些实现方式中，该方法还包括：第五网络设备向第一设备发送第十一信息，第十一信息用于指示第五网络设备管理的第三小区停止在无线资源控制RRC非激活态或空闲态提供第一组播会话。
第九方面，提供了一种通信方法，该方法可以由第四网络设备执行，或者，也可以由第四网络设备的组成部件(例如芯片或者电路)执行，本申请对此不作限定。
该方法可以包括：第一设备接收来自第五网络设备的第三消息，第三消息用于请求第一组播会话的组播配置信息；第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收第一组播会话；第一设备向第五网络设备发送第一组播配置信息。
基于上述方案，第一设备可以为一个或多个第五网络设备提供的第一组播会话确定第一组播配置信息，换言之，第一设备可以为第一组播会话确定一个或多个第五网络设备均可以使用的第一组播配置信息，使得对于同一组播会话，一个区域内支持第一组播会话的不同网络设备可以使用同样的组播配置信息，如此，能够同步区域内的组播配置信息。
另一方面，当终端设备在该区域内移动时，终端设备可以继续使用该组播配置信息接收组播会话，能够保证终端设备接收组播业务的连续性。
结合第九方面，在第九方面的某些实现方式中，该第三消息包括第一组播会话的标识，组播配置参数的取值范围包括G-RNTI的取值范围，第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：第一设备从G-RNTI的取值范围中选择一个值作为第一组播会话的G-RNTI，第一组播配置信息包括第一组播会话的G-RNTI。
结合第九方面，在第九方面的某些实现方式中，该第三消息包括第一组播会话的标识和第一组播会话所需的组播无线承载MRB的数目X，组播配置参数的取值范围包括MRB标识的取值范围，第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：第一设备从MRB标识的取值范围中选择X个值作为第一组播会话的MRB标识，第一组播配置信息包括第一组播会话的MRB标识，X为正整数。
结合第九方面，在第九方面的某些实现方式中，该第三消息包括第一组播会话的标识和第一组播会话的第一MRB所需的逻辑信道LCH的数目Y，组播配置参数的取值范围包括LCH标识的取值范围，第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：第一设备从LCH标识的取值范围中选择Y个值作为第一MRB的LCH标识，第一组播配置信息包括第一MRB的LCH标识，Y为正整数。
结合第九方面，在第九方面的某些实现方式中，该第三消息包括第一组播会话的标识，组播配置参数的取值范围包括物理信道配置参数的取值范围，第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：第一设备从物理信道配置参数的取值范围中选择至少一个值作为第一组播会话的物理信道配置参数，第一组播配置信息包括第一组播会话的物理信道配置参数。
结合第九方面，在第九方面的某些实现方式中，该第三消息包括第一组播会话的标识，组播配置参数的取值范围包括非连续接收DRX配置参数的取值范围，第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：第一设备从DRX配置参数的取值范围中选择至少一个值作为第一组播会话的DRX配置参数，第一组播配置信息包括第一组播会话的DRX配置参数。
结合第九方面，在第九方面的某些实现方式中，该第三消息包括第一组播会话的标识，组播配置参数的取值范围包括公共频域资源CFR配置参数的取值范围，第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：第一设备从CFR配置参数的取值范围中选择至少一个值作为第一组播会话的CFR配置参数，第一组播配置信息包括第一组播会话的CFR配置参数。
结合第九方面，在第九方面的某些实现方式中，该第三消息包括第二小区的标识，第二小区为由第五网络设备管理的、提供RRC非激活态或空闲态的第一组播会话的小区，该方法还包括：第一设备根据来自一个或多个第五网络设备的第三消息确定第十信息，第十信息用于指示第一组播配置信息的生效区域。
结合第九方面，在第九方面的某些实现方式中，该方法还包括：第一设备向第五网络设备发送第十信息。
结合第九方面，在第九方面的某些实现方式中，该方法还包括：第一设备接收来自第五网络设备的第四消息，第四消息包括组播配置参数的取值范围。
结合第九方面，在第九方面的某些实现方式中，该第四消息还包括第二区域的标识信息，第二区域为组播配置参数的取值范围的生效区域。
结合第九方面，在第九方面的某些实现方式中，该第二区域内的小区提供至少一个组播会话，至少一个组播会话包括第一组播会话，该方法还包括：第一设备为至少一个组播会话确定互不相同的组播配置信息。或者说，至少一个组播会话中除第一组播会话之外的其他组播会话的组播配置信息和第一组播配置信息不同。
结合第九方面，在第九方面的某些实现方式中，该第二区域为第五网络设备所在的基于无线接入网络的通知区域RNA。
结合第九方面，在第九方面的某些实现方式中，该方法还包括：第一设备接收来自第五网络设备的第十一信息，第十一信息用于指示第五网络设备管理的第三小区停止在无线资源控制RRC非激活态或空闲态提供第一组播会话；第一设备将第三小区从第一组播配置信息的生效区域中移除。
可选地，在上述任一方面的方法中，第一组播配置信息包括一下至少一项：第一组播会话的G-RNTI、MRB配置、CFR配置、DRX配置、物理信道配置。
第十方面，提供了一种通信的装置，该装置可以是终端设备执行，或者，也可以是终端设备的组成部件(例如芯片或者电路)，本申请对此不作限定。
该装置可以包括：收发单元，用于接收来自第一网络设备的第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息；收发单元还用于：接收来自第二网络设备的第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息；处理单元，用于：根据第一组播配置信息在无线资源控制RRC非激活态或空闲态接收来自第二网络设备的第一组播会话。
可选地，第一信息还包括至少一个组播配置信息对应的小区或网络设备的标识信息。
结合第十方面，在第十方面的某些实现方式中，收发单元还用于：获取第一标识，第一标识为终端设备的驻留小区的标识或驻留小区对应的网络设备的标识，第一标识与第一组播配置信息之间具有对应关系；处理单元还用于：根据第一标识和第一索引信息确定第一组播配置信息。
结合第十方面，在第十方面的某些实现方式中，收发单元还用于：接收来自于第一网络设备的第三信息，第三信息用于指示至少一个组播配置信息的生效区域。
结合第十方面，在第十方面的某些实现方式中，收发单元还用于：接收来自于第一网络设备或第二网络设备的第四信息，第四信息用于指示第一组播会话对应的第一G-RNTI；终端设备根据第一G-RNTI解扰第一组播会话。
结合第十方面，在第十方面的某些实现方式中，第四信息为第一G-RNTI的信息；或，第四信息为第一G-RNTI的索引信息，第一G-RNTI的索引信息与第一G-RNTI具有对应关系；或，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
结合第十方面，在第十方面的某些实现方式中，第一索引信息包括以下一项或多项：组播无线承载MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、公共频域资源CFR配置索引、半持续调度(semi-persistent scheduling，SPS)配置索引。
结合第十方面，在第十方面的某些实现方式中，处理单元还用于：在满足以下任一种条件时，接收第二信息：条件包括：终端设备重选至第二网络设备管理的小区；或，终端设备接收到来自第五信息，其中，第五信息用于通知系统消息变更；或，第五信息用于通知组播控制信道消息变更；或，第五信息用于通知第一组播会话激活；第五信息用于指示终端设备在RRC非激活态或空闲态接收组播会话；
其中，系统变更通知消息或通知组播控制信道消息变更用于：
通知第一组播会话的组播配置信息变更为第一组播配置信息，或者，通知第二网络设备管理的小区开始在非激活态或空闲态提供第一组播会话。
结合第十方面，在第十方面的某些实现方式中，收发单元还用于：接收来自第二网络设备的第一消息，第一消息为系统消息或组播控制信道消息，第一消息用于指示停止接收第一组播会话或者第二网络设备管理的小区停止在非激活态提供第一组播会话。
可选地，处理单元还用于：根据所述第一消息确定是否恢复RRC连接。
可选地，所述第一消息指示所述第一组播会话去激活，所述终端设备保持在RRC非激活态或空闲态，停止接收所述第一组播会话。
可选地，所述终端设备接收所述第一消息，所述第一消息中不包括所述第一组播会话的标识。
可选地，终端设备接收所述第一消息，所述第一消息中包括所述第一组播会话的标识，且不包括所述第一索引信息。
具体地，若第一消息中包括第一组播会话的标识，且不包括第一索引信息，终端设备停止接收第一组播会话；或，第一消息中不包括第一组播会话的标识，终端设备向第二网络设备发送RRC恢复请求消息，并进入RRC连接态接收第一组播会话。
可选地，第二信息承载于以下任一种：系统消息、组播控制信道消息、RRC释放消息。
第十一方面，提供了一种通信的装置，该装置可以是第三网络设备，或者，也可以是第三网络设 备的组成部件(例如芯片或者电路)，本申请对此不作限定。其中，该第三网络设备可以是第一方面中的第一网络设备，也可以是第一方面中的第二网络设备。
该装置可以包括：收发单元，用于发送第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息；处理单元，用于根据第一组播配置信息发送第一组播会话。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：向终端设备发送第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息。
结合第十一方面，在第十一方面的某些实现方式中，第一信息还包括至少一个组播配置信息对应的小区或网络设备的标识信息。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：发送第一标识，第一标识为第三网络设备的标识或第二信息对应的小区的标识。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：获取第一信息。
结合第十一方面，在第十一方面的某些实现方式中，收发单元具体用于：接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；处理单元还用于：确定N个组播配置信息和N个组播配置信息对应的索引信息；其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。
结合第十一方面，在第十一方面的某些实现方式中，收发单元具体用于：确定N个组播配置信息；接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息；处理单元还用于：根据M个配置信息和N个组播配置信息确定M个组播配置信息和N个组播配置信息对应的索引信息；其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。
可选地，第六信息还包括M个组播配置信息对应的小区的标识信息。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：向第四网络设备发送第一信息。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：终端设备发送第三信息，第三信息用于指示至少一个组播配置信息的生效区域。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：向终端设备发送第四信息，第四信息用于指示第一G-RNTI，第一G-RNTI用于加扰第一组播会话。
可选地，第四信息为第一G-RNTI的信息；或，第四信息为第一G-RNTI的索引信息，第一G-RNTI的索引信息与第一G-RNTI具有对应关系；或，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
结合第十一方面，在第十一方面的某些实现方式中，第四信息为第一G-RNTI的信息，收发单元还用于：接收来自核心网设备的第一G-RNRI；或，处理单元还用于：根据第一组播会话的标识确定第一G-RNTI。
结合第十一方面，在第十一方面的某些实现方式中，第一索引信息包括以下一项或多项：组播无线承载MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、公共频域资源CFR配置索引、半持续调度SPS配置索引。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：发送第五信息，第五信息用于通知系统消息变更或用于通知组播控制信道消息变更，第五信息用于终端设备接收第二信息。
结合第十一方面，在第十一方面的某些实现方式中，处理单元还用于：在满足以下任一条件时，向终端设备发送第五信息，该条件包括：第一组播会话的组播配置信息变更为第一组播配置信息；或，第三网络设备管理的小区开始在非激活态或空闲态提供第一组播会话。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：发送第一消息，第一消息为系统消息、组播控制信道消息，第一消息用于指示第一组播会话处于去激活状态或被释放，或者用于指示第二网络设备管理的小区停止在非激活态提供第一组播会话。
结合第十一方面，在第十一方面的某些实现方式中，收发单元还用于：发送第一消息，第一消息为系统消息、组播控制信道消息，第一消息用于指示第一组播会话处于去激活状态或被释放，或者用 于指示第二网络设备管理的小区停止在非激活态提供第一组播会话。
可选地，第三网络设备确定第一组播会话处于去激活状态或被释放，第三网络设备发送第一消息，第一消息包括第一组播会话的标识，且第一消息不包括第一索引信息；或，第三网络设备管理的小区停止在RRC非激活态或空闲态提供第一组播会话，第三网络设备发送第一消息，第一消息不包括第一组播会话的标识。
第十二方面，提供了一种通信的装置，该装置可以是第四网络设备，或者，也可以是第四网络设备的组成部件(例如芯片或者电路)，本申请对此不作限定。
该装置可以包括：收发单元，用于向第三网络设备发送第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；或，第六信息包括M个组播配置信息，M为正整数；收发单元还用于：接收来自第三网络设备的第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括M个组播配置信息。
结合第十二方面，在第十二方面的某些实现方式中，收发单元还用于：发送第七信息，第七信息用于指示第一组播会话关联第二索引信息，第二索引信息指示第二组播配置信息，至少一个组播配置信息包括第二组播配置信息，至少一个组播配置信息对应的索引信息包括第二索引信息；该装置还可以包括处理单元，处理单元用于根据第二组播配置信息发送第一组播会话。
第十三方面，提供了一种通信的装置，该装置可以是终端设备执行，或者，也可以是终端设备的组成部件(例如芯片或者电路)，本申请对此不作限定。
该装置可以包括：收发单元，用于接收来自第一网络设备的第八信息，第八信息包括第一组播配置信息和第一组播配置信息对应的小区的信息，第一组播配置对应第一组播会话，第一组播配置信息对应的小区信息包括第一小区；收发单元还用于：接收来自第二网络设备的第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的第一组播会话的状态；收发单元，用于在第一小区为终端设备的驻留小区的情况下，根据第一组播配置信息接收第一组播会话。
其中，第一组播会话的状态，包括：第一小区正在或未在提供RRC非激活态或空闲态的第一组播会话，或者，第一小区开始或停止提供RRC非激活态或空闲态的第一组播会话；或，第一组播会话对应的组播配置信息发生变化。
结合第十三方面，在第十三方面的某些实现方式中，收发单元具体用于：在第一指示信息指示第一小区开始在RRC非激活态或空闲态提供第一组播会话的情况下，根据第一组播配置信息在RRC非激活态或空闲态接收第一组播会话；或，在第一指示信息指示第一小区停止在RRC非激活态或空闲态提供第一组播会话的情况下，向第一小区对应的网络设备发送RRC恢复请求消息。
可选地，第二消息为寻呼消息或RRC释放消息。
例如，RRC释放消息指示UE进入inactive态收组播，UE使用第一组播配置收组播；或者，RRC释放消息指示EU进入inacitve态收组播，且RRC释放消息中携带更新的组播配置，UE根据该更新的组播配置收组播。
结合第十三方面，在第十三方面的某些实现方式中，第八信息承载于RRC释放消息或RRC重配置消息。
结合第十三方面，在第十三方面的某些实现方式中，第一指示信息为比特位图，比特位图中的至少一个比特关联于第一小区。
结合第十三方面，在第十三方面的某些实现方式中，第一组播配置信息对应的小区信息包括Q个小区，比特位图包括Q个比特，Q个比特和Q个小区一一对应。
结合第十三方面，在第十三方面的某些实现方式中，第八信息还包括至少一个组播配置信息、至少一个组播配置信息对应的索引信息、至少一个组播配置信息对应的小区信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息，至少一个组播配置信息对应的小区信息包括第一小区。
结合第十三方面，在第十三方面的某些实现方式中，第二消息还包括第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息。
结合第十三方面，在第十三方面的某些实现方式中，第一索引信息包括以下一项或多项：MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、CFR配置索引、SPS配置 索引。
结合第十三方面，在第十三方面的某些实现方式中，收发单元还用于：接收来自于第一网络设备或第二网络设备的第四信息，第四信息用于指示第一组播会话对应的第一G-RNTI；终端设备根据第一G-RNTI解扰第一组播会话。
结合第十三方面，在第十三方面的某些实现方式中，第四信息为第一G-RNTI的信息；或，第四信息为第一G-RNTI的索引信息，第一G-RNTI的索引信息与第一G-RNTI具有对应关系；或，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
第十四方面，提供了一种通信的装置，该装置可以是第三网络设备，或者，也可以是第三网络设备的组成部件(例如芯片或者电路)，本申请对此不作限定。其中，该第三网络设备可以是第四方面中的第一网络设备，也可以是第四方面中的第二网络设备。
该装置可以包括：收发单元，用于发送第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的第一组播会话的状态发生变化；处理单元，用于根据第一组播配置信息发送第一组播会话。
其中，第一组播会话的状态，包括：第一小区正在或未在提供RRC非激活态或空闲态的第一组播会话，或者，第一小区开始或停止提供RRC非激活态或空闲态的第一组播会话；或，第一组播会话对应的组播配置信息发生变化。
可选地，第三网络设备为第十方面中的第一网络设备，或者为第十方面中的第二网络设备。
可选地，收发单元还用于：向终端设备发送第八信息，第八信息包括第一组播配置信息和第一组播配置信息对应的小区信息，第一组播配置对应第一组播会话，第一组播配置信息对应的小区信息包括第一小区。
结合第十四方面，在第十四方面的某些实现方式中，第八信息承载于RRC释放消息或RRC重配置消息。
结合第十四方面，在第十四方面的某些实现方式中，收发单元还用于：接收来自第四网络设备的第九信息，第九信息用于指示第一组播配置信息对应的R个小区的标识，第一组播配置信息对应的小区信息包括R个小区，R为正整数。
结合第十四方面，在第十四方面的某些实现方式中，第一指示信息为比特位图，比特位图中的至少一个比特关联于第一小区。
可选地，第一组播配置信息对应的小区信息包括Q个小区，比特位图包括Q个比特，Q个比特和Q个小区一一对应。
结合第十四方面，在第十四方面的某些实现方式中，第八信息还包括至少一个组播配置信息、至少一个组播配置信息对应的索引信息、至少一个组播配置信息对应的小区信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息，至少一个组播配置信息对应的小区信息包括第一小区。
结合第十四方面，在第十四方面的某些实现方式中，收发单元还用于：接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；处理单元还用于：确定N个组播配置信息和N个组播配置信息对应的索引信息；
其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。
结合第十四方面，在第十四方面的某些实现方式中，处理单元具体用于：确定N个组播配置信息；收发单元具体用于：接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息；处理单元具体用于：根据M个配置信息和N个组播配置信息确定M个组播配置信息和N个组播配置信息对应的索引信息；
其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。
结合第十四方面，在第十四方面的某些实现方式中，第六信息还包括M个组播配置信息对应的小区的标识信息。
结合第十四方面，在第十四方面的某些实现方式中，收发单元还用于：向第四网络设备发送第八信息。
结合第十四方面，在第十四方面的某些实现方式中，第二消息还包括第二信息，第二信息用于指 示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息。
结合第十四方面，在第十四方面的某些实现方式中，第一索引信息包括以下一项或多项：
MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、CFR配置索引、SPS配置索引。
结合第十四方面，在第十四方面的某些实现方式中，收发单元还用于：向终端设备发送第四信息，第四信息用于指示第一G-RNTI，第一G-RNTI用于加扰第一组播会话。
结合第十四方面，在第十四方面的某些实现方式中，第四信息为第一G-RNTI的信息；或，第四信息为第一G-RNTI的索引信息，第一G-RNTI的索引信息与第一G-RNTI具有对应关系；或，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
结合第十四方面，在第十四方面的某些实现方式中，第四信息为第一G-RNTI的信息，收发单元还用于：第三网络设备接收来自核心网设备的第一G-RNRI；或，处理单元还用于：根据第一组播会话的标识确定第一G-RNTI。
结合第十四方面，在第十四方面的某些实现方式中，第一小区为第三网络设备管理的小区。
结合第十四方面，在第十四方面的某些实现方式中，收发单元还用于：接收来自第四网络设备的第二指示信息，第二指示信息用于指示第一小区提供的第一组播会话的状态发送变化，第一小区为第四网络设备管理的小区。
第十五方面，提供了一种通信的装置，该装置可以是第四网络设备，或者，也可以是第四网络设备的组成部件(例如芯片或者电路)，本申请对此不作限定。
该装置可以包括：收发单元，用于向第三网络设备发送第二指示信息，第二指示信息用于指示第一小区提供的非连接态或空闲态第一组播会话的状态，第一小区为第二网络设备管理的小区；收发单元还用于：发送第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的在非连接态或空闲态的第一组播会话的状态。
其中，第一组播会话的状态，包括：第一小区正在或未在提供RRC非激活态或空闲态的第一组播会话，或者，第一小区开始或停止提供RRC非激活态或空闲态的第一组播会话；或，第一组播会话对应的组播配置信息发生变化。
结合第十五方面，在第十五方面的某些实现方式中，收发单元还用于：向第三网络设备发送第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；或，第六信息包括M个组播配置信息，M为正整数；接收来自第三网络设备的第八信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括M个组播配置信息。
第十六方面，提供了一种通信的装置，该装置可以是终端设备执行，或者，也可以是终端设备的组成部件(例如芯片或者电路)，本申请对此不作限定。
该装置可以包括：收发单元，用于接收来自第五网络设备的第一组播配置信息和第十信息，第一组播配置信息用于配置第一组播会话，第十信息用于指示第一组播配置信息的生效区域；处理单元，用于在该生效区域内，根据第一组播配置信息在无线资源控制RRC非激活态或空闲态接收第一组播会话。
第十七方面，提供了一种通信的装置，该装置可以是第五网络设备，或者，也可以是第五网络设备的组成部件(例如芯片或者电路)，本申请对此不作限定。
该装置可以包括：收发单元，用于向第一设备发送第三消息，第三消息用于请求第一组播会话的组播配置信息；收发单元还用于：接收来自第一设备的第一组播配置信息，第一组播配置信息根据第三消息和组播配置参数的取值范围确定，第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收第一组播会话。
结合第十七方面，在第十七方面的某些实现方式中，收发单元还用于：向终端设备发送第一组播配置信息。
结合第十七方面，在第十七方面的某些实现方式中，该组播配置参数的取值范围包括以下至少一个：G-RNTI的取值范围、组播无线承载MRB标识的取值范围、逻辑信道LCH标识的取值范围、物理信道配置参数的取值范围、非连续接收DRX配置参数的取值范围、公共频域资源CFR配置参数的取值范围。
结合第十七方面，在第十七方面的某些实现方式中，该第三消息包括以下至少一项：第一组播会话的标识、第一组播会话所需的MRB的数目、第一组播会话的第一MRB所需的逻辑信道LCH的数目。
结合第十七方面，在第十七方面的某些实现方式中，该第三消息包括第二小区的标识，第二小区为由第五网络设备管理的、提供RRC非激活态或空闲态的第一组播会话的小区。
结合第十七方面，在第十七方面的某些实现方式中，收发单元还用于：接收来自第一设备的第十信息，第十信息指示第一组播配置信息的生效区域。
结合第十七方面，在第十七方面的某些实现方式中，收发单元还用于：向第一设备发送第四消息，第四消息包括组播配置参数的取值范围。
结合第十七方面，在第十七方面的某些实现方式中，该第四消息还包括第二区域的标识信息，第二区域为组播配置参数的取值范围的生效区域。
结合第十七方面，在第十七方面的某些实现方式中，该第二区域内的小区提供至少一个组播会话，至少一个组播会话包括第一组播会话，至少一个组播会话中除第一组播会话之外的其他组播会话的组播配置信息和第一组播配置信息不同，至少一个组播会话的组播配置信息互不相同。
结合第十七方面，在第十七方面的某些实现方式中，该第二区域为第五网络设备所在的基于无线接入网络的通知区域RNA。
结合第十七方面，在第十七方面的某些实现方式中，收发单元还用于：向第一设备发送第十一信息，第十一信息用于指示第五网络设备管理的第三小区停止在无线资源控制RRC非激活态或空闲态提供第一组播会话。
第十八方面，提供了一种通信的装置，该装置可以是第一设备，或者，也可以是第一设备的组成部件(例如芯片或者电路)，本申请对此不作限定。
该装置可以包括：收发单元，用于接收来自第五网络设备的第三消息，第三消息用于请求第一组播会话的组播配置信息；处理单元，用于根据第三消息和组播配置参数的取值范围确定第一组播配置信息，第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收第一组播会话；该收发单元还用于：向第五网络设备发送第一组播配置信息。
结合第十八方面，在第十八方面的某些实现方式中，该第三消息包括第一组播会话的标识，组播配置参数的取值范围包括G-RNTI的取值范围，该处理单元具体用于：从G-RNTI的取值范围中选择一个值作为第一组播会话的G-RNTI，第一组播配置信息包括第一组播会话的G-RNTI。
结合第十八方面，在第十八方面的某些实现方式中，该第三消息包括第一组播会话的标识和第一组播会话所需的组播无线承载MRB的数目X，组播配置参数的取值范围包括MRB标识的取值范围，该处理单元具体用于：从MRB标识的取值范围中选择X个值作为第一组播会话的MRB标识，第一组播配置信息包括第一组播会话的MRB标识，X为正整数。
结合第十八方面，在第十八方面的某些实现方式中，该第三消息包括第一组播会话的标识和第一组播会话的第一MRB所需的逻辑信道LCH的数目Y，组播配置参数的取值范围包括LCH标识的取值范围，该处理单元具体用于：从LCH标识的取值范围中选择Y个值作为第一MRB的LCH标识，第一组播配置信息包括第一MRB的LCH标识，Y为正整数。
结合第十八方面，在第十八方面的某些实现方式中，该第三消息包括第一组播会话的标识，组播配置参数的取值范围包括物理信道配置参数的取值范围，该处理单元具体用于：从物理信道配置参数的取值范围中选择至少一个值作为第一组播会话的物理信道配置参数，第一组播配置信息包括第一组播会话的物理信道配置参数。
结合第十八方面，在第十八方面的某些实现方式中，该第三消息包括第一组播会话的标识，组播配置参数的取值范围包括非连续接收DRX配置参数的取值范围，该处理单元具体用于：从DRX配置参数的取值范围中选择至少一个值作为第一组播会话的DRX配置参数，第一组播配置信息包括第一组播会话的DRX配置参数。
结合第十八方面，在第十八方面的某些实现方式中，该第三消息包括第一组播会话的标识，组播配置参数的取值范围包括公共频域资源CFR配置参数的取值范围，该处理单元具体用于：从CFR配置参数的取值范围中选择至少一个值作为第一组播会话的CFR配置参数，第一组播配置信息包括第一组 播会话的CFR配置参数。
结合第十八方面，在第十八方面的某些实现方式中，该第三消息包括第二小区的标识，第二小区为由第五网络设备管理的、提供RRC非激活态或空闲态的第一组播会话的小区，该处理单元还用于：根据来自一个或多个第五网络设备的第三消息确定第十信息，第十信息用于指示第一组播配置信息的生效区域。
结合第十八方面，在第十八方面的某些实现方式中，该收发单元还用于：向第五网络设备发送第十信息。
结合第十八方面，在第十八方面的某些实现方式中，该收发单元还用于：接收来自第五网络设备的第四消息，第四消息包括组播配置参数的取值范围。
结合第十八方面，在第十八方面的某些实现方式中，该第四消息还包括第二区域的标识信息，第二区域为组播配置参数的取值范围的生效区域。
结合第十八方面，在第十八方面的某些实现方式中，该第二区域内的小区提供至少一个组播会话，至少一个组播会话包括第一组播会话，该处理单元还用于：为至少一个组播会话确定互不相同的组播配置信息。或者说，至少一个组播会话中除第一组播会话之外的其他组播会话的组播配置信息和第一组播配置信息不同。
结合第十八方面，在第十八方面的某些实现方式中，该第二区域为第五网络设备所在的基于无线接入网络的通知区域RNA。
结合第十八方面，在第十八方面的某些实现方式中，该收发单元还用于：接收来自第五网络设备的第十一信息，第十一信息用于指示第五网络设备管理的第三小区停止在无线资源控制RRC非激活态或空闲态提供第一组播会话；该处理单元还用于：将第三小区从第一组播配置信息的生效区域中移除。
可选地，在上述任一方面的装置中，第一组播配置信息包括一下至少一项：第一组播会话的G-RNTI、MRB配置、CFR配置、DRX配置、物理信道配置。
第十九方面，提供一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面至第九方面任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为终端设备或第一网络设备。
在另一种实现方式中，该装置为用于终端设备或第一网络设备的芯片、芯片系统或电路。
第二十方面，本申请提供一种处理器，用于执行上述第一方面至第九方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第二十一方面，提供一种计算机可读存储介质，该计算机可读介质存储用于设备执行的程序代码，该程序代码包括用于执行上述第一方面至第九方面任一种可能实现方式中的方法。
第二十二方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第九方面任一种可能实现方式中的方法。
第二十三方面，提供一种通信系统，包括第十一方面的第三网络设备和第十二方面的第四网络设备，或者，包括第十四方面的第三网络设备和第十五方面的第四网络设备。
第二十四方面，提供一种通信方法，包括第八方面的第五网络设备执行的方法和第九方面的第一设备执行的方法。
示例性地，该方法包括：第五网络设备向第一设备发送第三消息，第三消息用于请求第一组播会话的组播配置信息；第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收第一组播会话；第一设备向第五网络设备发送第一组播配置信息。
附图说明
图1示出了适用于本申请实施例的无线通信系统的示意图。
图2示出了适用于本申请实施例的几种架构的示意图。
图3示出了适用于本申请实施例的场景的另一示意图。
图4是一种多播广播会话的信息的传输资源的示意图。
图5是本申请实施例提供的一种通信方法200的示意图。
图6是TMGI的一种结构示意图。
图7是本申请实施例提供的一种通信的方法300的示意图。
图8是本申请实施例提供的一种通信方法400的示意图。
图9是本申请实施例提供的一种通信方法500的示意图。
图10是本申请实施例提供的一种通信的方法600的示意图。
图11是本申请实施例提供的一种通信的方法700的示意图。
图12是本申请实施例提供的一种通信的方法800的示意图。
图13是本申请实施例提供的一种通信的方法900的示意图。
图14是本申请实施例提供的一种通信装置2800的示意图。
图15是本申请实施例提供的另一种通信装置2900的示意图。
图16是本申请实施例提供的芯片系统3000的示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信，车到万物(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。作为示例，V2X可包括车辆到车辆(vehicle-to-vehicle，V2V)，车辆到行人(vehicle-to-pedestrian，V2P)，车辆到基础设施(vehicle-to-infrastructure，V2I)。其中，基础设施例如为路侧单元(road side unit，RSU)或者网络设备。
本申请实施例提供的方法可适用但不限于如下领域：MBMS、SC-PTM、组播广播服务、MBSFN、双通道智能单播(Dual-channel intelligent unicast，DC-IU)、Broadcast、Multicast、广播多播(Multicast Broadcast)、Groupcast、V2X、公共安全(public safety)、关键任务(mission critical)、IPv4/IPv6多播透传(transparent IPv4/IPv6multicast delivery)、IPTV、通过无线的软件交付(software delivery over wireless)、组通信(group communications)、物联网(Internet of things，IoT)、电视视频(TV Video)、电视(TV)、线性电视(linear TV)、直播(Live)、广播服务(radio services)、设备到设备(device to device，D2D)、无人驾驶(unmanned driving)、自动驾驶(automated driving，ADS)、辅助驾驶(driver assistance，ADAS)、智能驾驶(intelligent driving)、网联驾驶(connected driving)、智能网联驾驶(intelligent network driving)、汽车共享(car sharing)等。
本申请实施例中的终端设备包括各种具有无线通信功能的设备，其可用于连接人、物、机器等。终端设备可以广泛应用于各种场景，例如：蜂窝通信，D2D，V2X，端到端(peer to peer，P2P)，M2M，MTC，IoT，虚拟现实(virtual reality，VR)，增强现实(augmented reality，AR)，工业控制，自动驾驶，远程医疗，智能电网，智能家具，智能办公，智能穿戴，智能交通，智慧城市无人机，机器人，遥感，被动传感，定位，导航与跟踪，自主交付等场景。终端设备可以是上述任一场景下的终端，如MTC终端、IoT终端等。终端设备可以是第三代合作伙伴项目(3rd generation partnership project，3GPP)标准的用户设备(user equipment，UE)、终端(terminal)、固定设备、移动台(mobile station)设备或者说移动设备、用户单元(subscriber unit)、手持设备、车载设备、可穿戴设备、蜂窝电话(cellular phone)、智能电话(smart phone)、SIP电话、无线数据卡、个人数字助理(personal digital assistant，PDA)、电脑、平板电脑、笔记本电脑、无线调制解调器、手持设备(handset)、膝上型电脑(laptop computer)、具有无线收发功能的计算机、智能书、车辆、卫星、全球定位系统(global positioning system， GPS)设备、目标跟踪设备、飞行器(例如无人机、直升机、多直升机、四直升机、或飞机等)、船只、遥控设备智能家居设备、工业设备，或者内置于上述设备中的装置(例如，上述设备中的通信模块、调制解调器或芯片等)，或者连接到无线调制解调器的其它处理设备。为了描述方便，下文将终端设备以终端或UE为例来描述。
应理解，在某些场景下，UE还可以用于充当基站。例如，UE可以充当调度实体，其在V2X、D2D或P2P等场景中的UE之间提供侧行链路信号。
本申请实施例中，用于实现终端设备的功能的装置，也即终端装置，可以是终端设备，也可以是能够支持终端设备实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在终端设备中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
本申请实施例中的网络设备可以是用于与终端设备通信的设备，该网络设备也可以称为接入网设备或无线接入网设备，如网络设备可以是基站。本申请实施例中的网络设备可以是指将终端设备接入到无线网络的无线接入网(radio access network，RAN)节点(或设备)。基站可以广义的覆盖如下中的各种名称，或与如下名称进行替换，比如：节点B(NodeB)、演进型基站(evolved NodeB，eNB)、下一代基站(next generation NodeB，gNB)、中继站、接入点、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、主站、辅站、多制式无线(motor slide retainer，MSR)节点、家庭基站、网络控制器、接入节点、无线节点、接入点(AP)、传输节点、收发节点、基带单元(BBU)、射频拉远单元(remote radio unit，RRU)、有源天线单元(active antenna unit，AAU)、射频头(remote radio head，RRH)、中心单元(central unit，CU)、分布式单元(distributed unit，DU)、定位节点等。基站可以是宏基站、微基站、中继节点、施主节点或类似物，或其组合。基站还可以指用于设置于前述设备或装置内的通信模块、调制解调器或芯片。基站还可以是移动交换中心以及D2D、V2X、M2M通信中承担基站功能的设备、6G网络中的网络侧设备、未来的通信系统中承担基站功能的设备等。基站可以支持相同或不同接入技术的网络。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。
基站可以是固定的，也可以是移动的。例如，直升机或无人机可以被配置成充当移动基站，一个或多个小区可以根据该移动基站的位置移动。在其他示例中，直升机或无人机可以被配置成用作与另一基站通信的设备。
网络设备和终端设备可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上；还可以部署在空中的飞机、气球和卫星上。本申请实施例中对网络设备和终端设备所处的场景不做限定。
可选的，本申请实施例中的网络设备，也可以是完成基站部分功能的模块或单元，例如，可以是云接入网(cloud radio access network，C-RAN)系统中的CU，也可以是DU。本申请的实施例对网络设备所采用的具体技术和具体设备形态不做限定。网络设备的全部或部分功能也可以通过在硬件上运行的软件功能来实现，或者通过平台(例如云平台)上实例化的虚拟化功能来实现。在本申请中，如果无特殊说明，网络设备指无线接入网设备。
可选地，CU可以进行用户面和控制面解耦，形成CU-控制面(CU-Control Plane，CU-CP)和CU-用户面(CU-User Plane，CU-UP)，CU-CP和CU-UP支持灵活部署。
其中，在本申请实施例中，术语“无线通信”还可以简称为“通信”，术语“通信”还可以描述为“数据传输”、“信息传输”或“传输”。
还应理解，本申请中“终端设备”也称“终端装置”、“终端”等等，“网络设备”也称“网络装置”、“网络侧”等等，“核心网设备”也称“核心网装置”、“核心网”等等。
首先简单介绍适用于本申请的网络架构，如下。
图1示出了适用于本申请一实施例的无线通信系统的示意图。如图1所示，该无线通信系统100可以包括至少一个网络设备，例如图1所示的网络设备110，该无线通信系统还可以包括至少一个终端设备，例如图1所示的终端设备120和终端设备130。网络设备和终端设备均可配置多个天线，网络设备与终端设备可使用多天线技术通信。终端设备120与终端设备130之间可以直接进行通信，也可以通过网络设备110通信。
其中，网络设备和终端设备通信时，网络设备可以管理一个或多个小区，一个小区中可以有一个 或多个终端设备。可选地，网络设备和终端设备组成一个单小区通信系统，不失一般性，将该小区称为小区#1。图1中的网络设备110可以是小区#1中的网络设备，或者，网络设备110可以为小区#1中的终端设备(例如终端设备120)服务。
需要说明的是，小区可以理解为网络设备的无线信号覆盖范围内的区域。
本申请还可以用于双连接(dual connectivity，DC)场景，包括但不限于演进通用无线接入网络(evolved universal terrestrial radio access network，EUTRAN)和NR网络的双连接(EUTRAN-NR dual connectivity，EN-DC)场景、NR网络的双连接(NR-NR dual connectivity，NR-DC或NR-NR-DC)场景。
图2示出了适用于本申请实施例的几种架构的另一示意图。如图2的(a)所示，该场景为5G系统架构图，如图2的(a)所示，5G中的RAN可以称为下一代RAN(next generation RAN，NG-RAN)，NG-RAN包括两种类型，即gNB和基于LTE演进的下一代eNB(next generation eNB，NG-eNB)，这两种类型的接入网设备可以都连接到5G的核心网(5G core，5GC)中，5GC中包括多个网元，包括但不限于接入和移动性管理功能(access and mobility management function,AMF)和用户面功能(user plane function，UPF)。此外，接入网设备之间可以通过Xn接口进行通信，接入网设备与5G核心网之间可以通过NG接口进行通信，相关架构细节详见协议定义。
本申请还可以用于载波聚合(carrier aggregation，CA)场景，在CA场景下，多个小区组可以为终端设备服务，也就是说，可以将多个分量载波(component carrier，CC)聚合在一起，提升终端峰值速率和系统容量的技术，以满足终端越来越高的网络速率要求。CA有两个重要概念：主小区(primary cell，Pcell)下的主分量载波和辅小区(secondary cell，Scell)下的辅分量载波。无线资源控制(radio resource control，RRC)连接建立后，辅小区就可能被配置以提供额外的无线资源进行数据传输，以提升系统容量。
如图2的(b)所示，该场景为CU和DU分别部署的场景，在该场景中，网络设备包括CU和DU，CU用于与核心网通信，DU用于与终端设备通信。
如图2的(c)所示，该场景为CU-CP、CI-UP、DU分别部署的场景，在该场景中，网络设备包括CU-CP、CI-UP、DU，CU-CP用于与核心网的控制面通信，CU-UP用于与核心网的用户面通信，DU用于与终端设备通信。
图3示出了适用于本申请实施例的场景的另一示意图。如图3所示，网络设备可以管理多个小区，其中，小区#1为终端设备的主小区，小区#2、小区#3、小区#4为终端设备的辅小区，小区#1、小区#2、小区#3、小区#4的CC可以通过CA技术共同为终端设备提供服务。
为了便于理解，对相关概念做一简单解释。
1.终端设备的状态
NR中终端设备有三种RRC状态：RRC空闲(idle)态(state)、RRC非激活(inactive)态及RRC连接(connected)态。RRC连接态(简称为连接态)下，终端设备和网络设备之间建立了RRC连接，当没有数据传输时，网络设备可以将终端设备释放到RRC空闲态(简称为空闲态)，或者将终端设备释放到RRC非激活态，挂起(suspend)RRC连接。RRC空闲态下，网络设备和终端设备之间没有建立RRC连接(简称为非激活态)。RRC非激活态下，网络设备仍维护终端设备的上下文信息。引入RRC非激活态的好处是相比于RRC空闲态，RRC非激活下由于网络设备仍保留终端设备上下文，因此可以更快速地恢复RRC连接，当有业务到达时，可以降低时延。
2.寻呼(paging)
由于终端设备具有移动性，当终端设备处于RRC空闲态时，网络为了找到终端设备，需要核心网(core network，CN)在跟踪区标识(tracking area identity，TAI)列表中的所有跟踪区域(tracking area，TA)下的所有小区下发送寻呼消息，CN发起的寻呼(CN-initiated paging)可以简称为CN寻呼。显然，在这种级别的终端跟踪下，由于绝大多数寻呼消息是在终端设备不在的小区中下发的，所以会产生较高的寻呼消息传输开销。为了节省传输开销，针对处于RRC非激活态的终端设备，引入了比TA范围更小的范围，即基于无线接入网络的通知区域(RAN-based Notification Area，RNA)，一个TA范围内可以包括多个RNA，一个RNA可以包括多个小区，RNA由网络设备管理，网络设备可以向RNA范围内的小区发送寻呼消息，网络设备发起的寻呼(RAN-initiated paging)可以简称为RAN寻呼。对 于RAN寻呼，终端设备的最后服务基站(last serving gNB)从UPF接收到下行数据或从AMF接收到下行信令时，会在RNA区域内的小区上寻呼终端设备，并且如果RNA区域内包括邻网络设备的小区，最后服务基站会通过Xn接口向邻网络设备传递RAN寻呼，邻网络设备在其小区内寻呼终端设备。当收到寻呼消息后，处于RRC非激活态或RRC空闲态的终端设备会触发RRC恢复(RRC resume)或RRC连接建立。
3.组播广播业务(multicast and broadcast service，MBS)
MBS可以以较少的资源为大量具有相同需求的用户同时提供数据，使得网络资源可以得到共享。MBS包括组播业务和广播业务，广播业务是指网络设备同时向某个地理区域中的所有终端设备提供相同的特定内容数据的通信服务。组播业务是指网络设备向加入组播会话(multicast session)的一组终端设备提供通信服务。组播业务可以通过组播会话向终端设备下发，接收组播的终端设备要与核心网之间进行鉴权流程后才能接收组播业务，鉴权流程也可以理解终端设备加入组播会话的过程，因此，接收组播业务也可以说接收组播会话或者MBS会话(MBS session)，MBS会话可以通过临时移动组标识(Temporary mobile group identity,TMGI)进行标识。组播业务也可以称为多播业务，本申请中，“组播”和“多播”可以相互替换，组播会话和组播业务可以相互替换，组播业务的标识、组播会话的标识、TMGI三者可以相互替换，不予限制。
4.组播广播控制信道和多播广播业务信道
NR MBS的广播技术中引入了两种逻辑信道，多播广播控制信道(MBS control channel，MCCH)和多播广播业务信道(MBS traffic channel，MTCH)，其中MCCH用于传输控制信息，包含MTCH的配置信息，比如MTCH对应的组无线网络临时标识(group radio network temporary identifier，G-RNTI)以及非连续接收(discontinuous reception，DRX)参数。MCCH以周期的方式进行发送。MTCH逻辑信道用于承载广播业务的用户数据。通过MCCH调度MTCH。MTCH的配置为每(per)g-RNTI级别，也可以说是per MBS service级别。其中，基站通过g-RNTI同时向多个UE调度业务数据，每个g-RNTI可以关联至少一个广播业务。
应理解，在不同通信系统中，上述信道可以对应不同的名称。例如，在第四代(4th generation，4G)通信系统中，多播广播业务控制信道可以为单小区多播广播业务控制信道(single cell MCCH，SC-MCCH)。再例如，在5G通信系统中，多播广播业务控制信道可以为MC-MCCH。在未来技术发展过程中，与该多播广播业务控制信道功能类似的信道还可能有其他称谓，或者，在不同通信环境、通信场景或者通信技术中，相同功能的信道也可能有不同称谓，但是功能类似或相同的信道在不同系统中的不同名称，不对信道内容及功能构成限定。本申请中的多播广播控制信道可以用于传输控制信息，多播广播业务信道可以用于传输用户数据。
如无特殊说明，本申请中以MCCH表示多播广播业务控制信道，以MTCH表示多播广播业务信道。还应理解，本申请其他英文简称与此类似，不再赘述。
5.多播广播控制信道更改通知(MCCH change notification)
如图4所示，MCCH在每个修改周期(Modification period，MP)中重复发送，图中包括重复周期(repetition period，RP)。在一个MP中，MCCH的内容相同，即相同的MCCH会根据调度的重复周期来重复传输若干次。当不同的MP的MCCH发生变化时，网络设备发送包含MCCH更改通知的PDCCH。当UE在PDCCH上检测到MCCH change Notification对应的字段，比如是2比特，即认为检测到了更改通知，UE重新获取MCCH。UE在获取MCCH时，需要检测MCCH-RNTI加扰的PDCCH，以获取MCCH的调度信息。其中，MCCH更改通知中的第一比特指示MCCH修改的原因是会话开始，MCCH更改通知中的第二比特指示MCCH修改的原因是会话修改、会话停止或邻小区列表更新。通常来说，MCCH更改周期大于等于MCCH重复周期。
6.服务质量(quality of service，QoS)和无线承载的映射关系
协议数据单元(protocol data unit，PDU)会话(session)包括用于传输单播的PDU会话和用于传输MBS的PDU会话，传输MBS的PDU会话也可以称为MBS会话。核心网在建立PDU会话时，为了保证提供该PDU session的服务质量，会建立一个或多个QoS流(flow)，每个QoS流有相应的QoS参数(比如5G QoS标识(5G QoS Identifier，5QI)、分配和保留优先级(Allocation and Retention Priority，ARP)等)。NG-RAN根据QoS参数(QoS profiles和QFI)，确定QoS flow和无线承载(包括DRB 和MRB)的映射规则。一个PDU会话可以对应一个或多个QoS flow，一个QoS flow可以对应一个或多个无线承载，由NG-RAN的实现策略决定。在非接入层AS层，下行方向发送侧(NG-RAN)由服务数据适配协议(Service Data Adaptation Protocol，SDAP)层处理QoS flow和无线承载的映射，一个无线承载上的数据包经过分组数据汇聚控制(Packet Data Convergence Control，PDCP)层处理(例如，进行头压缩、完整性保护、加密/解密等)来到无线链路控制(radio link control，RLC)层，根据RB特征或RLC模式，一个PDCP实体可以对应一个、两个或四个RLC实体，RLC实体会对来自PDCP层的RLC服务数据单元(service data unit，SDU)进行分段和重组，组成RLC PDU后放入相应的逻辑信道，一个RLC实体对应一个逻辑信道。由MAC层对来自一个或多个逻辑信道的RLC PDU(也可以称为MAC SDU)复用到一个数据块(TB)中，递交给物理信道进行物理层传输。在MAC报头(MAC header)中，会包括接收RLC PDU的逻辑信道标识。接收侧(UE)会按照相反的流程进行处理，接收到TB后由MAC层负责解复用TB，处理得到一个或多个MAC SDU(RLC PDU)后能够获得该一个或多个MAC SDU对应的逻辑信道标识。根据网络侧的配置，UE可以获知一个无线承载对应的逻辑信道的标识，以保证UE的MAC层将从某个逻辑信道中得到的RLC PDU递交给正确的RLC实体，对应到相应的PDCP实体和无线承载。
在NR R17中，支持NR MBS广播的终端设备可以在RRC连接态、RRC空闲态和RRC非激活态状态下获取广播通信服务。Rel-17中，MBS广播配置采用两步配置的方式，首先，网络设备在系统消息，例如，系统信息块(system information block，SIB)20中指示用于MBS广播的MCCH配置，包括MCCH的重复周期和偏移、MCCH窗口持续时长、MCCH窗口起始时隙、MCCH更改周期等。根据MCCH配置可以接收MCCH，MCCH(或者说通过MCCH信道发送的信息)是周期性传输的，以配置的重复周期，在配置的MCCH传输窗口内传输。MCCH中包括广播会话的配置信息和MTCH调度信息，广播会话的配置信息包括广播会话的标识、MBS无线承载(MRB radio bearer，MRB)配置、G-RNTI等，读取广播会话的配置信息和MTCH调度信息，终端设备可以正确地接收MBS广播会话。
终端设备在对接收MBS广播服务感兴趣时，应执行MCCH信息获取过程。感兴趣接收MBS广播服务的终端设备应在进入提供SIB20的小区时执行MCCH信息获取过程，例如，当正在接收或感兴趣去接收MBS广播服务的终端设备接收到更改通知后，会重新获取SIB 20，以获得新的MCCH。在终端设备获取到新的MCCH信息之前，终端设备会应用先前获取到的MCCH信息。又如，由于MCCH是每(per)小区配置的，所以每个小区的MCCH携带的MBS配置可能不同，当空闲态或非激活态终端设备进行小区重选时，需要读取重选小区的SIB 20，以获得MCCH。应理解，MBS广播支持采用MCCH更改通知来通知UE广播会话的开始，以及正在进行的广播会话的MCCH信息更改，包括MBS会话停止。
在Rel-17，终端设备在RRC连接态接收组播会话。对于加入组播会话的处于RRC连接态的终端设备，网络设备通过专用信令，如RRC重配置消息(RRCReconfiguration message)，向终端设备发送MBS组播配置，例如，包括组播MRB配置、组播公共频域资源(common frequency resource，CFR)配置、物理层配置(也可以称为层1/L1配置)、组播的G-RNTI等。当(暂时)没有用于组播会话的数据要发送到终端设备时，网络设备可以将终端设备切换到RRC空闲或RRC非激活状态。
当一个小区内接收组播会话的用户的数目过多时，可能会出现以下情况：接收组播会话的用户数目超出小区能够容纳的连接态用户数目，这会引起网络拥塞。为了缓解网络拥塞，在Rel-18中支持终端设备在RRC非激活态接收组播。例如，当终端设备没有单播业务，仅有组播业务时，网络可以将终端设备释放到RRC非激活态接收组播。如此，能够减少网络中处于RRC连接态的终端设备的数目，这既有利于缓解网络拥塞，也有利于终端设备节能。
然而，对于终端设备如何获取RRC非激活态的MBS配置，协议中并未定义。
具体来说，与广播会话类似，对于在RRC非激活态接收组播会话的终端设备，在接收组播会话之前，终端设备需要获取组播配置，如此才能根据组播配置接收组播会话。
通过小区广播的系统消息将组播配置通过广播的方式提供给终端设备，比如，采取与上述广播会话类似的方式，在MCCH中向终端设备发送组播配置，MCCH配置可以仍在SIB中指示MCCH。然而，通过广播的方式，未加入组播会话的终端设备也能接收到组播配置，有潜在的安全隐患。此外，终端设备在小区重选时需要重新读取MCCH获得组播配置之后才能继续接收组播业务，重新获取配置 和解读配置有一定时延，不利于组播业务接收的连续性。
网络设备通过专用信令(例如RRC重配消息或RRC释放消息等)向终端设备发送组播配置。终端设备需要恢复RRC连接，终端设备进入RRC连接态之后，网络设备才能通过专用信令将组播配置发送给终端设备。终端设备进入RRC连接态接收组播配置，这会增加终端设备能耗，也会增加空口信令开销。
基于上述分析，本申请提供一通信的方法和装置，在小区重选或组播配置更新等场景下，可以避免终端设备进入RRC连接态或者触发RRC恢复，能够减小终端设备的能耗，降低信令开销。
可以理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
还可以理解，在本申请中，“指示”可以包括直接指示、间接指示、显示指示、隐式指示。当描述某一指示信息用于指示A时，可以理解为该指示信息携带A、直接指示A，或间接指示A。
此外，本申请中的“对应”、“关联”指的是两者之间具有对应关系或映射关系。该对应关系也可以是一对一，也可以是一对多，也可以是多对一。
本申请中，指示信息所指示的信息，称为待指示信息。在具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。
下文将结合附图详细说明本申请实施例提供的方法。本申请提供的实施例可以应用于上述图1、图2或图3所示的网络架构中，不作限定。
图5是本申请实施例提供的一种通信方法200的示意图。方法200可以包括如下步骤。
S210，第一网络设备向终端设备发送第一信息，相应地，终端设备接收第一信息。
第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息。
示例性的，组播配置信息和对应的索引信息如下表1所示。
表1组播配置和索引的一种映射关系示意
应理解，表1以三个配置为例，实际数量不限制。这里表示的是配置与索引的逻辑上的对应关系。
其中，至少一个组播配置信息对应的索引信息可以通过显示或隐式的方式指示。通过显示的方式指示，即第一信息中同时指示组播配置和对应的索引，比如根据上表，指示组播配置1，索引1、组播配置2，索引2、组播配置3、索引3；通过隐式的方式指示，即第一信息中仅指示组播配置的列表，组播配置的索引根据组播配置列表中至少一个组播配置的顺序得出，比如组播配置列表中的第一行的组播配置对应索引1，第二行的组播配置对应索引2。
需说明的是，组播配置对应的索引信息的取值可以是任意值，本发明不限定索引信息的取值范围，也不限定索引信息的取值是连续的。
可选地，作为一种实现方式，第一网络设备在确定每个组播配置关联的索引时，可以不按照顺序排列，而是在一定索引范围内随机分配。例如，第一网络设备需要为10个组播配置确定索引，那么这10个索引可以是不连续的，即不是1～10或0-9等连续的10个数，而是大于10个数的范围内任选10，比如，可以在1～100000中任选10个，如表2所示。这样可以使得组播配置的索引具有随机性。
表2组播配置和索引的一种映射关系示意
应理解，表2以三个配置为例，实际数量不限制。这里表示的是配置与索引的逻辑上的对应关系。
在该实现方式中，终端设备可以将第二信息中的索引和第一信息中的索引进行对比，如果第二信息中指示的索引在第一信息中不存在，可以确该第二信息为无效。基于上述方案，当存在伪基站发送第二信息，并指示一个索引时，终端设备可以识别该索引无效。比如，终端设备通过专用信令获得的第一信息中指示的组播配置和索引的映射关系如表2所示，当UE驻留在小区1时，小区1发送第二信息指示第一组播会话关联索引4997，对应组播配置1；当该区域内存在一个伪基站，指示小区1对第一组播会话的组播配置发生了变化，并发送第二信息指示第一组播会话关联索引1，终端设备可以判断索引1不是第一信息中指示的索引，因此确定小区1的组播配置并未发生变化，仍按照索引4997关联的组播配置接收第一组播会话。通过本方法，可以提高通信安全。
可选地，作为一种实现方式，第二信息中的索引的取值与组播配置列表中的索引具有固定偏移值，第二信息中的索引的取值+固定偏移值＝组播配置列表中的索引。作为示例，固定偏移值为500，所述固定偏移值可以通过第一信息发送给终端设备。可选的，该固定偏移值可以是每组播会话配置的，不同组播会话可以配置不同的固定偏移值。如表3-a，当第一信息中的索引信息通过显示的方式指示时，组播配置#1的索引为index＝503，如果要指示组播配置#1，那么第二信息中的索引的值可以为index＝3。在组播配置列表中，组播配置#2的索引为index＝581。如果要指示组播配置#2，那么第二信息中的索引的值可以为index＝81。
表3组播配置和索引的一种映射关系示意
应理解，表3以三个配置为例，实际数量不限制。这里表示的是配置与索引的逻辑上的对应关系。
如表3，当第一信息中的索引信息通过隐式的方式指示时，组播配置#1的索引为index＝501，对应配置列表的第一行，如果要指示组播配置#1，那么第二信息中的索引的值可以为index＝1。组播配置#2的索引为index＝502，对应配置列表的第二行，如果要指示组播配置#2，那么第二信息中的索引的值可以为index＝2。
基于上述方案，可以提升第二信息的安全性。
其中，组播配置信息又称为MBS组播配置信息或组播配置，指的是用于接收MBS中的组播会话的配置参数。本申请中的组播配置信息，指的是终端设备在RRC非激活态或空闲态下的组播配置，其用于终端设备在RRC非激活态或空闲态接收组播会话。
具体地，组播配置信息可以包括以下一项或多项：组播MRB配置、物理信道配置、非连续接收DRX配置、G-RNTI配置、邻小区配置、公共频域资源(common frequency resource，CFR)配置，组播MRB配置、物理信道配置、非连续接收DRX配置、G-RNTI配置、邻小区配置、CFR配置、半持续调度(semi-persistent scheduling，SPS)配置中的每一项可以称为子配置。其中，物理信道配置包括以下一项或多项：物理下行控制信道(physical downlink control channel、PDCCH)配置、物理下行共享信道(physical downlink shared channel，PDSCH)配置、PDCCH时机(occasion)配置、SSB映射窗口的配置、搜索空间配置、公共控制资源集配置。MRB配置包括以下一项或多项：MRB标识、分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)配置、无线链路控制(Radio Link Control,RLC)承载配置。CFR配置包括：CFR带宽和位置。
索引信息(index)又称为标识信息(identifier，ID)或索引，一个索引信息可以是一个索引，也可以是一个索引集合，一个索引集合包括一个或多个子索引，例如，一个索引信息由MRB配置索引、物理信道配置索引、DRX配置索引、邻小区配置索引、CFR配置索引、SPS配置索引中一项或多项组成，其中，MRB配置索引、物理信道配置索引、DRX配置索引、邻小区配置索引、CFR配置索引、SPS配置索引中的每一项可以称为一个子索引。这种场景下，上述多个索引可以灵活组合，具有更强的灵活性。
一个索引信息是一个索引集合，包括一个或多个子索引的情况。例如，至少一个组播配置包括{组 播配置A，组播配置B，组播配置C}；其中，第一组播配置信息为组播配置A，组播配置A的配置信息可以是一个配置信息list，该list包括{组播配置A_组播MRB配置list，组播配置A_物理信道配置list，组播配置A_DRX配置list，组播配置A_G-RNTI配置list，组播配置A_邻小区配置list，组播配置A_CFR配置list，组播配置A_SPS配置list}或包括其中至少一项的组合。
对应的，第一组播配置信息对应的第一索引信息包括{组播配置A_组播MRB配置索引，组播配置A_物理信道配置索引，组播配置A_DRX配置索引，组播配置A_G-RNTI配置，组播配置A_邻小区配置索引，组播配置A_CFR配置索引，组播配置A_SPS配置索引}。
一个索引信息是一个索引的情况例如，至少一个组播配置包括{组播配置A，组播配置B，组播配置C}；其中，第一组播配置信息为组播配置A，对应第一索引信息；组播配置A的配置信息包括{组播配置A_组播MRB配置，组播配置A_物理信道配置，组播配置A_DRX配置，组播配置A_G-RNTI配置，组播配置A_邻小区配置，组播配置A_CFR配置，组播配置A_SPS配置}。
第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，即第一信息包括组播配置列表。在该组播配置列表中，每个组播配置信息对应一个索引信息。其中，一个或多个组播配置信息包括第一组播配置信息，第一组播配置信息对应第一索引信息。换言之，一个或多个组播配置信息对应的索引信息包括第一索引信息。
可选地，组播配置列表可以是一个列表，列表中的多项分别对应组播配置信息中的一项。该组播配置列表也可以由多个子列表组成，例如，组播配置列表包括MRB配置列表、物理信道配置列表、DRX配置列表、邻小区配置列表、CFR配置列表、SPS配置列表中的一项或多项。这种情况下，每个子列表可以对应一个子索引，即一个索引信息由多个子索引组成，通过该多个子索引，可以对应一个组播配置信息。
此外，组播配置信息可以关联特定的组播会话，每个组播配置信息也可以关联于一个或多个组播会话，即多个组播会话可以共享相同的组播配置信息。类似地，每个组播会话可以关联于一个或多个组播配置，即每个会话可以有多个组播配置，以适用于不同的场景。
可以理解的是，第一信息中的至少一个组播配置是关联于终端设备加入的组播会话的配置，即第一网络设备向终端设备提供的组播配置资源池包括终端设备已经加入的组播会话的组播配置资源池。
可选的，当终端设备加入了新的组播会话时，终端设备向网络设备请求恢复RRC连接态，网络设备根据终端设备当前加入的组播会话，向终端设备发送更新的第一信息。
对于每个组播会话(MBS session)，在一个生效区域内，部分配置可以是区域公共配置，例如MRB配置，公共配置可以是通过OAM预配置的；部分配置是Per网络设备或者Per小区的配置，即可以是不同小区具有不同的配置。对于不同的小区具有不同配置的情况，区域内的网络设备之间需要同步该区域内的小区的组播配置配置信息和索引信息的映射关系。
此外，索引信息和组播配置之间具有对应关系，该关系可以是一对一关系，也可以是一对多关系。当索引信息和组播配置之间的对应关系为一对一时，通过第一索引信息，终端设备可以确定第一配置信息。当索引信息和组播配置之间的对应关系为一对多时，通过第一索引信息和其他信息，终端设备可以确定第一配置信息，作为示例，该其他信息可以是第一标识，第一标识可以是小区标识或网络设备的标识。
可选地，终端设备接入第一组播会话，第一信息中的至少一个组播配置信息包括第一组播会话的一个或多个组播配置信息。
第一信息可以称为组播配置资源池，在收到第一信息后，终端设备可以保存第一信息。
其中，第一信息是终端设备在连接态时、网络设备通过专用信令发送的，该专用信令也可以称为加密信令，该专用信令可以是RRC释放消息或RRC重配置消息。
S220a，第二网络设备向终端设备发送第二信息，相应地，终端设备接收第二信息。
第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息。
第二信息用于指示第一组播会话关联第一索引信息，换言之，第二信息可以包括第一组播会话的标识和第一索引信息，该组播会话的标识也可以称为会话标识(session ID)，该标识可以是TMGI。而通过第一索引信息，终端设备可以获知对应的第一组播配置信息。
可以理解的是，第二信息是第二网络设备在管理的小区上发送给终端设备的，每个小区可以有相 同或不同的第二信息。
其中，第二信息可以承载于小区公共信令，公共信令通过广播的形式发送，即通过非加密的形式发送。该公共信令可以是小区的系统消息，系统消息可以是系统信息(system information block，SI)或系统信息块(system information block，SIB)消息，例如，SIB 20，又如，除了SIB 20之外的其他任一个SIB。该公共信令也可以是MCCH，即通过MCCH发送的消息。可选地，第二信息也可以承载于专用信令，例如，RRC释放消息。
可选地，当第二信息通过MCCH发送时，用于发送第二信息的MCCH可以与目前用于指示广播配置信息的MCCH采用相同的MCCH-RNTI，但是两者关联于不同的逻辑信道和逻辑信道标识(logical channel，LCID或者LCH ID)。或者，用于发送第二信息的MCCH与指示广播配置信息的MCCH采用相同的逻辑信道和逻辑信道标识，但是采用不同的MCCH-RNTI加扰。或者，第二信息与广播配置信息承载在同一条RRC消息且承载在相同的MCCH上，在消息中显示指示该第二信息是用于组播的。
可选的，当第二信息通过RRC释放消息发送时，该RRC释放消息还指示终端设备进入RRC非激活态或空闲态接收第一组播会话。如此，终端设备在进入RRC非激活态或空闲态之前，可以获得驻留的小区对第一组播会话的第一组播配置，而无需通过获取小区公共信令(例如系统消息或MCCH消息)来获得第一组播配置，可以降低终端设备在从RRC连接态转换到RRC非激活态的过程中接收组播业务的中断，提高接收组播业务的连续性。
可选地，第二信息的粒度也可以是per组播会话per MRB的粒度。比如第一组播会话关联M个MRB，每个MRB可以关联一个索引信息(可选的，包括多个子索引信息)，对应相应的MBS配置，不同MRB可以对应不同的索引信息。或者，第二信息的粒度也可以是per组播会话的，一个组播会话对应一个索引信息，即该组播会话关联的一个或多个MRB对应一个索引信息(可选的，包括多个子索引信息)，对应相应的MBS配置。
作为示例，小区提供的组播会话、组播会话的配置、和配置的索引信息的一种可能的映射关系如表4所示。
表4小区、组播会话、组播配置和索引的一种映射关系示意
S230，第二网络设备根据第一组播配置向终端设备发送第一组播会话。
如果方法200中的步骤S220a执行，那么，在S230之后，终端设备根据第一组播配置在RRC非激活态或空闲态接收第一组播会话。
具体地，由于第二信息指示第一组播会话关联第一索引信息，且第一索引信息指示第一配置信息，根据第二信息，终端设备可以确定第一组播会话对应的第一组播配置信息，进而根据第一组播配置接收第一组播会话。
根据上述方案，在终端设备处于连接态时，第一网络设备将组播配置资源池预配置给终端设备，该组播配置资源池可以包括第一组播会话关联的多个组播配置信息，进而第二网络设备可以通过第二信息向终端设备指示接收第一组播会话所需的第一组播配置信息。如此，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
可选地，承载第二信息的公共信令中还可以有信息#A，信息#A可以指示与本小区提供相同组播会话的邻小区列表，并指示邻小区是否与本小区有相同的组播配置，所述组播配置为终端设备在RRC非激活态接收该组播会话的配置。所述信息#A可以针对本小区提供的每组播会话(per MBS session)指示，例如对本小区提供的每个组播会话TMGI，信息#A指示提供该组播会话且组播配置也相同的小区列表；或者，对每个组播会话TMGI，信息A#指示提供该组播会话的小区列表，且还包括一个信息#B，指示上述小区列表中的每个小区是否有相同的组播配置。若邻小区的配置相同，则UE小区重选到该 邻区时，无需重新获取该小区的SIB或MCCH，UE可以提前获知邻小区的配置信息，降低获取配置造成的时延，提高接收组播业务的连续性。
应理解，在方法200中，第二网络设备可以是终端设备的驻留小区对应的网络设备，即第二网络设备可以为终端设备的服务基站，第一网络设备可以理解为终端设备的锚点基站，第一网络设备保存有终端设备和核心网的上下文。
可选地，第一网络设备和第二网络设备也可以为同一个，例如，终端设备在接收第一信息之后执行小区重选，重选后的小区仍然由第一网络设备的管理，此时的第二网络设备与第一网络设备相同。换言之，方法200中描述的第一网络设备执行的步骤也可以由第二网络设备执行，第二网络设备执行的步骤也可以由第一网络设备执行。
可选地，该方法200还包括：第一网络设备获取第一信息。
其中，第一信息可以有一个生效区域，表示在该区域内，预配置的第一信息是有效的，可以理解为第一信息中的至少一个组播配置在该区域内是有效的，或者第一信息中的至少一个组播配置和所述至少一个组播配置信息的索引信息之间的对应关系是有效的。本申请不限定对于生效区域外的小区，不可以与生效区域内的小区提供相同的组播配置。对于生效区域外的小区，对该同一个组播配置可以映射到相同的索引信息，或者不同的索引信息。该生效区域可以为一个地理区域范围，生效区域可以由多个小区组成；生效区域可以是由开放移动联盟(open mobile alliance，OAM)配置的。生效区域内的多个网络设备可以协调确定第一信息。本申请中，以第一网络设备获取第一信息为例进行说明。第一网络设备获取第一信息可以通过以下方式实现。
方式1：第一网络设备接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息。第一网络设备确定N个组播配置信息和N个组播配置信息对应的索引信息。其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。换言之，第一信息包括第六信息。
在这种方式中，第六信息可以包括M个组播配置信息对应的小区或网络设备的标识信息。
具体地，对一个组播会话，生效区域内的每个gNB，或者gNB的小区可以确定至少一个组播配置信息，以及该组播配置信息对应的索引信息，gNB通过Xn接口向邻gNB发送其确定的每个组播会话对应的组播配置信息、索引信息、gNB的标识或小区的标识，从而生效区域内的每个gNB的第一信息都包括接收到的组播配置信息和索引信息，以及自身确定的组播配置信息和索引信息。其中，小区标识可以是NR小区全球标识(NR cell global identifier，NCGI)或物理小区标识(physical cell identifier，PCI)，小区标识也可以是生效区域内分配的小区标识。例如，生效区域内共有32个小区，则该小区标识的长度可以为5比特(bit)，用来指示32个小区。其中，生效区域内的小区标识可以是开放移动联盟(open mobile alliance，OAM)配置的、也可以是生效区域中的一个gNB分配的。
例如，对组播会话1，gNB_1确定2个组播配置，并分别标识为index_1、index_2；gNB_2确定3个组播配置，并分别标识为index_1、index_2、index_3。gNB_1可以将gNB_1的标识、组播会话1、index_1、index_2及index_1、index_2对应的组播配置发送给gNB_2；gNB_2可以将gNB_2的标识、组播会话1、index_1、index_2、index_3和index_1、index_2、index_3发送给gNB_1。如此，在gNB_1和gNB_2中，组播会话_1都包括5个组播配置。在这种情况下，gNB标识和index可以唯一的确定一个组播配置。此处仅为举例，其中索引的粒度并不限定，可以以per组播会话为粒度，或者以per MRB为粒度，或者不同子配置可以有不同的子索引。
方式2：第一网络设备确定N个组播配置信息，第一网络设备接收来自第四网络设备的第六信息，第六信息包括M个组播配置信息。第一网络设备根据M个配置信息和N个组播配置信息确定M个组播配置信息和N个组播配置信息对应的索引信息。其中，至少一个组播配置信息包括M个组播配置信息和N个配置信息，M和N均为正整数。换言之，第一信息包括第六信息。
具体地，在方式2中，第一网络设备可以为生效区域内的网络设备协调配置第一信息，可以理解为生效区域内的中心gNB。生效区域内的gNB将其确定或支持的至少一个组播配置发送给中心gNB，中心gNB确定这些组播配置对应的索引，即中心gNB确定组播配置和索引之间的映射关系，并将映射关系发送给生效区域内的网络设备。
例如，gNB_1向中心gNB指示其确定的组播配置_1、组播配置_2，可选的，gNB_1还指示每个组 播配置关联的组播会话TMGI；gNB2向中心gNB指示其确定的组播配置_1、组播配置_2、组播配置_3，可选的，gNB_2还指示每个组播配置关联的组播会话TMGI。中心gNB确定共有5个组播配置，并分别标识为index_1、index_2、index_3、index_4、index_5，中心gNB将分配好的组播配置及索引发送给生效区域内其他gNB。此处仅为举例，其中索引的粒度并不限定，可以以per组播会话为粒度，或者以per MRB为粒度，或者不同子配置可以有不同的子索引。
可选地，在上述示例中，如果gNB_1确定的组播配置和gNB_2确定的组播配置可能会有一个或多个组播配置是相同的，此时，中心gNB确定组播会话_1的组播配置将小于5个。例如，中心gNB确定gNB_1发送的组播配置_1和gNB_2发送的组播配置2是相同的配置，则中心gNB确定共有4个组播配置，并分别标识为index_1、index_2、index_3、index_4，中心gNB将分配好的组播配置及索引发送给生效区域内其他gNB。
此处，gNB_1和gNB_2之间为具有Xn接口的两个网络设备，上述配置信息通过Xn接口消息发送给邻网络设备。可以理解的是，gNB_1和gNB_2仅为举例，该区域内的接入网络设备可以为1个或多个，此处仅描述任意两个gNB之间的配置交互方式。当区域内有多个接入网络设备时，上述方式可以适用于区域内具有Xn接口的任意两个gNB。
在方式2中，该方法200还包括：第一网络设备向第四网络设备发送第一信息。
方式3：第一网络设备确定N个组播配置信息，第一网络设备向第四网络设备发送N个组播配置信息，第一网络设备接收来自第四网络设备的第一信息，第一信息包括N个组播配置信息和N个组播配置信息对应的索引信息。
方式3与方式2类似，只是在方式3中，第四网络设备为中心gNB，第一网络设备为非中心gNB。
基于上述方案，网络设备协调确定第一信息，使得在一个区域的小区之间对于第一组播配置和第一组播配置的索引信息之间的映射关系具有统一的理解方式，并且允许该区域内的不同小区具有不同的组播配置，也允许一个小区可以有一个或多个组播配置；如此，终端设备在区域内的小区之间移动时，或者当小区对组播会话的组播配置变化时，根据小区对一个组播会话指示的索引信息确定相应的组播配置，终端设备可以保持在RRC非激活态或空闲态根据组播配置接收该组播会话，避免终端设备为了获得小区的组播配置而进入RRC连接态，如此，能够减小终端设备的能耗，也有助于保证终端设备接收组播会话的连续性。
应理解，在上述方式1至方式3中，第四网络设备泛指与第一网络设备协调确定第一信息的网络设备，其可以为生效区域内任一个网络设备。
可选地，该方法200还包括：第四网络设备发送第七信息，第七信息用于指示第一组播会话关联第二索引信息，第二索引信息指示第二组播配置信息，至少一个组播配置信息包括第二组播配置信息，至少一个组播配置信息对应的索引信息包括第二索引信息。第二网络设备根据第二组播配置信息发送第一组播会话。
具体地，若终端设备移动至第四网络设备管理的小区的覆盖范围内，终端设备可以在RRC非激活态或空闲态接收第四网络设备发送的第七信息，并通过第七信息确定第二组播配置，然后根据第二组播配置继续在RRC非激活态或空闲态接收第一组播会话。其中，第七信息可以携带于系统消息或MCCH中。如此，可以避免终端设备进入RRC连接态接收组播配置信息，能够减小终端设备的能耗，也有助于保证终端设备接收组播会话的连续性。
应理解，第四网络设备发送第七信息的情况与第二网络设备发送第二信息的过程是类似的，具体可以参考S220a，在此不赘述。
作为一种实现方式，第一信息还包括至少一个组播配置信息对应的小区或网络设备的标识信息。
在该实现方式中，该方法200还包括：第二网络设备向终端设备发送第一标识，第一标识为第二网络设备的标识或第二信息对应的小区的标识，即第一标识为终端设备的驻留小区的标识或驻留小区对应的网络设备的标识，第一标识与第一组播配置信息之间具有对应关系。终端设备可以根据第一标识和第一索引信息确定第一组播配置信息。
其中，第二网络设备可以将第一标识和第二信息同时发送给终端设备，或者终端设备可以在其他系统消息中获得第一标识。
通过这种方式，可以基于第一标识和第一索引信息唯一确定第一组播会话对应的第一组播配置信 息，提高了小区提供RRC非激活态组播业务配置的灵活性。区域内的不同小区可以具有不同的组播配置，并且，一个小区也可以有一个或多个组播配置。对一个组播会话，小区可以通过第二信息指示的该组播会话对应的索引信息的变更，指示该组播会话对应的配置信息的变更。当终端设备在区域内的小区之间移动时，或者当小区对组播会话的组播配置变化时，终端设备可以保持在RRC非激活态或空闲态根据组播配置接收该组播会话，避免进入RRC连接态导致的能耗开销和信令开销。
作为示例，小区标识和第二信息指示的索引信息和组播配置的一种可能的映射关系如表5所示。
表5小区标识、索引信息和组播配置的一种映射关系示意
可选地，该方法200还包括：第一网络设备向终端设备发送第三信息，相应地，终端设备接收第三信息，第三信息用于指示至少一个组播配置信息的生效区域。
应理解，“生效区域”也可以说可用区域、适用范围、适用区域、有效区域等。至少一个组播配置信息的生效区域，可以理解为至少一个组播配置信息和至少一个组播配置信息对应的索引信息的生效区域，或者，第一信息的生效区域。
其中，第三信息可以是组成生效区域的小区的列表。小区的标识可以为PCI、NCGI等。可选的，该生效区域的范围可以小于或等同于RNA。
作为一种实现方式，第三信息可以和第一信息同时发送，例如在同一条消息中发送。一种实现方式为，第三信息承载在RRC重配置消息或RRC释放消息中。作为又一种实现方式，终端设备通过应用层消息获知该生效区域。
基于上述方案，第一网络设备可以向终端设备指示第一信息的生效区域，使得终端设备在生效区域内移动时，可以继续使用第一信息确定所需的组播配置信息，而无需重复接收第一信息，如此，能够减小终端设备的能耗，也有助于保证终端设备接收组播会话的连续性。
可选地，该方法200还包括：第一网络设备或第二网络设备向终端设备发送第四信息，相应地，终端设备接收第四信息，第四信息用于指示第一组播会话对应的第一G-RNTI，第二网络设备可以通过第一G-RNTI对第一组播会话进行加扰，终端设备可以通过第一G-RNTI对接收的第一组播会话进行解扰。
其中，第一组播会话关联的第一G-RNTI可以有以下配置方式。
配置方式1：第一网络设备接收来自核心网设备的第一G-RNRI；或，第一网络设备根据第一组播会话的标识确定第一G-RNTI。
具体地，核心网可以对每个组播会话分配一个相应的G-RNTI，因此，核心网可以向第一网络设备发送第一组播会话的标识和第一G-RNTI。或者，核心网仅向终端设备发送第一组播会话的标识，第一网络设备根据第一组播会话的标识确定第一G-RNTI，第一网络设备可以向第二网络设备发送组播会话标识与第一G-RNTI的对应关系。
在配置方式1中，由于每个组播会话拥有唯一的会话标识，因此，第一G-RNTI和第一组播会话具有一一对应关系，一个组播会话关联的G-RNTI是生效区域内公共的。此时，第四信息可以是第一G-RNTI的信息。
可选地，在配置方式1中，网络设备可以通过专用信令向终端设备发送第一G-RNTI，该专用信令可以是RRC重配置消息或RRC释放消息。且在配置方式1中，第一信息可以不包括第一G-RNTI。第一组播配置信息可以包括第一G-RNTI，通过第四信息指示。
下面对配置方式1中第一网络设备根据第一播会话的标识确定第一G-RNTI的方法进行说明。
图6是TMGI的一种结构示意图，如图6所示，TGMI包括MBS服务标识(MBS service identifier)、移动国家码(mobile countrycode，MCC)和移动网络号(mobile network code，MNC)。其中，MBS服务标识由6位固定长度的十六进制数(digit)组成，介于000000和FFFFFF之间，MCC由3位固定 长度的十六进制数组成，MBS服务标识由2或3位十六进制数组成。TMGI中一段特定的比特串可以作为G-RNTI参考值(G-RNTI-reference)，例如，G-RNTI参考值为TMGI中从最左边开始的第x位比特位到第y位比特位组成的比特串，G-RNTI参考值可以由TMGI中用于指示MBS服务标识的部分或全部比特位组成的。其中，G-RNTI参考值的起始比特位置和终止比特位置是可配置的，例如，可以通过OAM配置，或通过核心网指示。
作为一个示例，组播会话关联的G-RNTI可以为G-RNTI-reference。作为又一个示例，组播会话关联的G-RNTI还可以关联于提供该组播会话的公共陆地移动网(public land mobile network，PLMN)。例如，提供该组播会话的PLMN可以关联于一个偏移值，记为G-RNTI-base，该偏移值可以是通过OAM配置的。组播会话关联的G-RNTI与该偏移值、G-RNTI参考值之间可以存在对应关系。示例性的，该对应关系可以为：G-RNTI＝G-RNTI-base+/-G-RNTI-reference。
可选地，在配置方式1中，第一网络设备可以将第一信息和第四信息同时发送，例如，第一信息和第四信息均携带于RRC释放消息。
配置方式2：第二网络设备确定第一组播会话的第一G-RNTI。
具体地，作为一种实现方式，gNB或gNB小区(第二网络设备的一例)可以为每个组播会话分配G-RNTI，并确定该G-RNTI的索引index。对一个组播会话，gNB可以向邻gNB(第一网络设备的一例)发送gNB标识或小区标识、TMGI、G-RNTI、G-RNTI索引，此时，在生效区域内，对于一个组播会话，通过gNB ID或小区标识、G-RNTI索引可以唯一标识一个G-RNTI。
作为另一种实现方式，第一网络设备为生效区域内的中心gNB，中心gNB接收生效区域内其他gNB(第二网络设备的一例)自行确定的G-RNTI，并且，中心gNB可以确定一个组播会话的所有G-RNTI和G-RNTI索引的映射关系，进一步，中心gNB可以将该映射关系发送给生效区域内的其他gNB(第二网络设备的一例)，此时，对于一个组播会话，G-RNTI index即可唯一标识一个G-RNTI。
在配置方式2中，第四信息为G-RNTI的索引或者为G-RNTI的索引信息，该G-RNTI的索引信息与G-RNTI具有对应关系。第一网络设备可以先将G-RNTI配置列表预配置给终端设备。第二网络设备可以广播G-RNTI的索引，从而在终端设备需要接收组播会话时，可以根据G-RNTI的索引和预配置的G-RNTI配置列表确定实际使用的第一G-RNTI。
可选地，在配置方式2中，G-RNTI配置列表和第一信息可以同时发送，或者说，第一信息可以包括G-RNTI配置列表。
配置方式3：第二网络设备确定第一组播会话的第二G-RNTI。
具体地，生效区域内存在一个G-RNTI公共值(G-RNTI-common)，该G-RNTI公共值为每个网络设备或小区的初始偏移值，该G-RNTI公共值可以是per组播会话的，即不同组播会话可以有不同的初始偏移值。该G-RNTI公共值可以通过OAM的方式配置给生效区域内的gNB。每个网络设备或小区实际对一个组播会话使用的G-RNTI与G-RNTI公共值具有关联关系，例如，该关联关系为：G-RNTI＝G-RNTI公共值+/-第二G-RNTI，其中，第二G-RNTI可以记为G-RNTI-additional，其为网络设备或网络设备的小区(第二网络设备的一例)自主确定的G-RNTI。第一网络设备可以先将G-RNTI公共值预配置给终端设备。第二网络设备可以广播第二G-RNTI，从而在终端设备需要接收组播会话时，可以根据第二G-RNTI和预配置的G-RNTI公共值确定实际使用的第一G-RNTI。
因此，在配置方式3中，第四信息为第二G-RNTI的信息，第二G-RNTI与第一G-RNTI具有对应关系。
可选地，在配置方式3中，G-RNTI公共值和第一信息可以同时发送，或者说，第一信息可以包括G-RNTI公共值。
可选地，在配置方式2和配置方式3中，第二网络设备可以将第四信息和第二信息一起发送至终端设备，终端设备根据第二信息和第四信息可以确定第一组播配置，该第一组播配置信息包括确定的第一G-RNTI。例如，第四信息和第二信息均携带于SIB中，又如，第四信息和第二信息均携带于MCCH消息中。
基于上述方案，网络设备可以通过第四信息向终端设备指示用于加扰和解扰的第一G-RNTI，由于第四信息是通过专用发送的，或者第四信息为第一G-RNTI的索引或第二G-RNTI，如此，能够避免未加入第一组播会话的终端设备获取第一G-RNTI，有助于保证通信安全。
作为一种可能的实现方式，S210和S220a可以同时执行，例如，第一网络设备要将终端设备释放至空闲态或非激活态，并指示终端设备在空闲态或非激活态接收组播会话。那么，终端设备在连接态时，第一网络设备可以通过RRC释放消息向终端设备发送第一信息和第二信息。终端设备根据RRC释放消息进入空闲态或非激活态，并根据第一信息和第二信息确定第一组播配置，然后根据第一组播配置接收第一组播会话。
可选地，终端设备接收第二信息的触发条件可以为以下任一种：终端设备重选至第二网络设备管理的小区；或，终端设备接收到来自第二网络设备的第五信息，其中，第五信息用于通知系统消息变更；或，第五信息用于通知组播控制信道消息变更；或，第五信息用于通知第一组播会话激活；或，第五信息用于指示终端设备在RRC非激活态或空闲态接收组播会话。
具体地，作为一种场景，当终端设备重选至第二网络设备管理的小区，终端设备会获取系统信息和/或MCCH，从而获取第二信息。
因此，当终端设备发生小区重选时，根据方法200，终端设备能够通过小区广播的消息获得组播会话对应的索引信息，通过该索引信息确定该组播会话对应的组播配置，从而继续保持在RRC非激活态或空闲态接收组播会话，如此，既可以避免终端设备进入RRC连接态增加能耗，也能够避免RRC状态转换过程中的时延，使得终端设备快速开始接收组播会话，避免业务中断。
作为又一个场景，当第一组播会话的组播配置信息变更为第一组播配置信息；或，当第二网络设备管理的小区开始在非激活态或空闲态提供第一组播会话，则第二网络设备会向终端设备发送第五信息，该第五信息用于通知系统信息变更，或者用于通知组播控制信道消息变更。终端设备可以在第五信息的触发下，获取系统信息和/或MCCH，从而获取第二信息。
应理解，开始在非激活态或空闲态提供组播会话，指的是，小区开始提供空闲态或非激活态的组播会话，或者，小区开始在终端设备处于非激活态或空闲态时向终端设备发送组播会话，或者，小区打开在非激活态或空闲态发送组播会话的开关。开始或打开后，支持在非激活态或空闲态接收组播会话的终端设备将会在非激活态或空闲态接收组播会话。如果小区停止在非激活态或空闲态提供组播会话，那么即使终端设备支持在非激活态或空闲态接收组播会话，终端设备也无法在非激活态或空闲态接收组播会话。
因此，当某个组播会话的组播配置信息发生更新时，根据方法200，终端设备能够快速获取更新的组播配置信息，或者当某个小区开始在非激活态或空闲态提供组播会话时，根据方法200，终端设备能够快速获取需要接收的组播会话的组播配置信息，从而快速接收组播会话，如此，能够使得终端设备快速开始接收组播会话，避免业务中断。
作为又一个场景，当第一组播会话激活时，第二网络设备可以向终端设备发送第五信息，第五信息用于通知第一组播会话激活；或，当第二网络设备需要终端设备在RRC非激活态或空闲态接收组播会话时，第二网络设备可以向终端设备发送第五信息，第五信息用于指示终端设备在RRC非激活态或空闲态接收组播会话，或者说，第五信息指示终端设备被允许在RRC非激活态或空闲态接收组播会话。如此，终端设备可以在第五信息的触发下，获取系统信息和/或MCCH，从而获取第二信息。
因此，当第一组播会话激活，或者当终端设备被允许在RRC非激活态或空闲态接收组播会话，根据方法200，终端设备能够快速获取需要接收的组播会话的组播配置信息，从而快速接收组播会话，如此，能够使得终端设备快速开始接收组播会话，避免业务中断。
作为又一个场景，当第五信息用于指示终端设备在RRC非激活态或空闲态接收组播会话时，也可以理解为，第五信息指示让终端设备进入RRC非激活态或空闲态的目的是接收组播会话。示例性的，第五信息承载于RRC释放消息中。终端设备接收到第五信息后，开始获取系统信息和/或MCCH，从而获取第二信息。
可选地，当第一组播会话处于去激活状态或第一组播会话被释放，方法200中的步骤S220a被替换为：S220b，第二网络设备发送第一消息，第一消息包括第一组播会话的标识，且第一消息不包括第一索引信息。其中，第一消息为系统消息、组播控制信道消息或RRC释放消息。
具体地，当小区发送的系统消息、组播控制信道消息或RRC释放消息中包括第一组播会话的标识，但未包括组播配置配置的索引信息时，则指示该组播会话处于去激活状态或已经被释放。终端设备可以停止接收第一组播会话，避免不必要的能耗。
一种可能的实现方式，当第二网络设备确定在其管理的小区上第一组播会话的状态发生变化时，发送系统消息变更通知或MCCH变更通知。驻留在上述小区的终端设备收到系统消息变更通知或MCCH变更通知后，获取第一消息。
在第一组播会话去激活时，终端设备通过获得第二网络设备的小区发送的第一消息，获知第一组播会话去激活。在这种场景下，终端设备停止接收第一组播会话，且终端设备可以保持在RRC非激活态或空闲态，而无需因为在驻留的第二网络设备的小区上无法获得用于RRC非激活态的组播配置而进入RRC连接态，因为终端设备已经确定第一组播会话已经被去激活或释放，因此无需为了接收第一组播会话的目的而进入RRC连接态，可以节约进入RRC连接态的能耗开销和信令开销。
可选地，第二网络设备管理的小区停止在非激活态或空闲态提供第一组播会话，方法200中的步骤S220a被替换为：S220c，第二网络设备发送第一消息，第一消息不包括第一组播会话的标识。其中，第一消息为系统消息、组播控制信道消息或RRC释放消息。
具体地，当小区发送的系统消息、组播控制信道消息或RRC释放消息中不包括某一个组播会话的标识时，指示该小区当前停止在RRC非激活或空闲态提供该组播会话，终端设备可以向驻留的小区对应的网络设备请求恢复RRC连接，用于请求在RRC连接态接收第一组播会话。进一步地，终端设备判断第一组播会话是否处于激活状态来确定是否恢复RRC连接：若第一组播会话仍处于激活态，则终端设备向驻留的小区对应的网络设备请求恢复RRC连接；若第一组播会话处于去激活状态，则终端设备不向网络设备请求恢复RRC连接。例如，如果终端设备在此前收到了该第一组播会话的去激活/释放通知，则在小区重选后，若在第一消息中未包括该第一组播会话的标识，则终端设备也可以不触发RRC连接恢复。一种可能的行为是，终端设备可以等待网络下发用于通知该第一组播会话激活的指示。需要说明的是，该小区可以为指示向非激活态或空闲态的终端设备提供该组播会话的小区，比如该小区为第三信息中指示的组播配置生效区域中的一个小区。当终端设备接收第三信息时，该小区可能在提供RRC非激活态的第一组播会话；但是后来的某一时刻，该小区的状态可能发生变化，停止提供RRC非激活态的第一组播会话，例如当该小区的拥塞缓解，则该小区可以只提供RRC连接态的第一组播会话；或者当该小区上处于RRC非激活态接收第一组播会话的终端设备数目较少时，该小区停止提供RRC非激活态的第一组播会话。
如此，对于该区域内的小区，小区本身为能够提供RRC非激活态或空闲态的组播会话的小区，小区在时刻1提供RRC非激活态的第一组播会话，但在时刻2小区停止提供第一组播会话，此时该小区可以发送系统消息变更通知或MCCH变更通知，终端设备收到变更通知后，获取小区发送的第一消息，以获知该小区停止提供第一组播会话。如此，终端设备可以及时向第二网络设备请求恢复到RRC连接态，以继续接收第一组播会话。
可选地，方法200还包括：第二网络设备管理的小区不支持在非激活态或空闲态提供组播会话，或，第二网络设备管理的小区不支持组播会话，则第二网络设备发送第一消息，第一消息不包括组播会话的标识。
具体地，当小区发送的系统消息、组播控制信道消息或RRC释放消息中一个组播会话的标识都不包括时，指示该小区不支持在非激活态或空闲态提供组播会话，该小区对应的网络设备可以是不支持空闲态或非激活态组播会话的网络设备，但是该网络设备可以支持连接态组播，例如该网络设备为R17的网络设备。或也可以指示该小区不支持组播会话，小区对应的网络设备可以是不支持组播会话的网络设备，例如，R17之前的网络设备。
基于上述方案，本申请不仅能够指示终端设备接收组播会话的组播配置信息，还能够指示组播会话去激活或释放，具有更高的效率，同时可以避免不必要的能耗。
可选地，该方法200还包括：当第一信息发生变化，第二网络设备通过Xn接口通知生效区域内的其他网络设备，区域内的网络设备向加入该组播会话的终端设备发送组通知或组寻呼，在监听到包括第一组播会话的标识的组通知或组寻呼消息后，终端设备触发RRC连接恢复，第二网络设备向终端设备发送专用信令(例如，RRC重配置消息或RRC释放消息)指示更新后的第一信息。
第一信息发生变化包括第一信息指示的至少一个组播配置发生变化，或者理解为组播配置的资源池发生变化，比如新增、修改或删除一个组播配置；还可以包括上述至少一个组播配置的生效区域发生变化，即第三信息变化，比如新增、或删除上述至少一个组播配置适用的小区。
图7是本申请实施例提供的一种通信的方法300的示意图，该方法300可以视为方法200的一种具体实现。该方法300可以包括以下步骤。在该方法300中，假设方法200中的第二信息携带于SIB。
S301，gNB#1(第一网络设备的一例)获取确定信息#1(第一信息的一例)。
其中，gNB#2(第二网络设备的一例)可以向gNB#1发送gNB#2确定的一个或多个组播配置，gNB#1根据自身确定的一个或多个组播配置和来自gNB#2的一个或多个组播配置，为同一个组播会话的不同组播配置确定不同的索引，信息#1包括会话、组播配置和索引三者的对应关系。或者，gNB#2向gNB#1发送gNB#2确定的一个或多个组播配置和组播配置对应的索引，gNB#1将自身确定的一个或多个组播配置和组播配置对应的索引和接收到的一个或多个组播配置和组播配置对应的索引共同作为信息#1。
S302，gNB#1向UE发送信息#1。
信息#1可以通过RRC释放消息或RRC重配置消息发送。
示例性的，信息#1的信令格式如下：
其中，“Multicast-AreaCell”信元包括提供非激活态或空闲态的组播会话的小区标识。“MRB-ConfigList”表示多个MRB配置，“drx-Config-List”表示多个DRX配置，“pdsch-ConfigList”表示多个PDSCH配置，“ssb-MappingWindowList”表示PDCCH时机和SSB的映射窗口配置。应理解，该信令格式仅为示例。
可选地，在S302之前，UE加入了组播会话#1和组播会话#2。因此，信息#1包括组播会话#1和组播会话#2的配置。
在S302之后，gNB#1可以将UE释放至非激活态。
S303，gNB#1广播SIB。
UE在非激活态，可以获取SIB，SIB中包括信息#2(第二信息的一例)。信息#2包括组播会话#1关联索引#1，根据组播会话#1、索引#1和信息#1，UE可以确定组播会话#1对应的组播配置#1，从而UE可以根据组播配置#1接收组播会话#1。
S304，UE发生小区重选，移动到gNB#2管理的小区中。
S305，gNB#2广播SIB。
对于组播会话#1，UE的重选小区的组播配置为组播配置#2。gNB#2可以通过广播的SIB携带组播会话#1关联索引#2的信息#3(第七信息的一例)。UE小区重选后，UE可以获取新小区的SIB，从而获取信息#3。根据组播会话#1、索引#2，UE可以确定组播会话#1对应的组播配置#2，从而UE可以根据组播配置#2继续接收组播会话#1。
S306，gNB#2开始在非激活态提供组播会话#2。
S307，gNB#2发送系统消息变更通知。
UE根据系统变更消息可以获取SIB。
S308，gNB#2广播SIB。
当gNB#2开始在非激活态或空闲态提供组播会话#2。gNB#2可以通过广播的SIB携带组播会话#2关联索引#1的信息#4(第七信息的又一例)。UE根据系统变更消息可以获取SIB，从而获取信息#4。根据组播会话#2、索引#1，UE可以确定组播会话#2对应的组播配置#1，从而UE可以根据组播配置#1接收组播会话#2。
由上可知，在小区重选或者在小区开始提供非激活态组播等场景下，终端设备无需进入连接态即可获取需要接收的组播会话对应的组播配置，能够减小UE的能耗，也能够避免业务中断。
图8是本申请实施例提供的一种通信方法400的示意图。方法400可以包括如下步骤。
S410，第一网络设备向终端设备发送第八信息，相应地，终端设备接收第八信息。
其中，第八信息包括第一组播配置信息和第一组播配置信息对应的小区的信息，该第一组播配置信息对应的小区包括第一小区。
对于同一组播会话，第一区域内的不同小区可以使用同样的组播配置信息发送组播会话。例如，第一区域内的不同小区可以均使用第一组播配置发送第一组播会话，因此，第一网络设备可以在向终端设备发送该组播配置信息的时候，进一步，向终端设备指示该组播配置信息对应的小区的信息。该小区的信息可以是第一区域内的小区列表，或者，该小区信息是第一区域的标识，且该第一区域关联于一个小区列表，终端设备通过应用层消息或通过预设信息可以获知该第一区域关联的一组小区，即小区列表对应的小区。
其中，第一组播配置对应第一组播会话。
可选的，该第一区域可以等同于或者小于RNA。
应理解，组播配置信息的具体描述可以参考方法200，再次不赘述。
可选地，第八信息可以承载于专用信令，例如，RRC释放消息或RRC重配置消息。换言之，第一网络设备可以在终端设备处于RRC连接态时，为终端设备预配置第八信息。
S420，第二网络设备向终端设备发送第二消息，该第二消息包括第一指示信息。
其中，第一指示信息可以为比特位图，比特位图中的每一个比特比特关联于一个小区。例如，第一组播配置信息对应的小区包括Q个，则比特位图包括Q个比特，Q个比特和Q个小区一一对应，Q为正整数。
具体地，每个组播会话对应一个比特位图(bitmap)，该比特位图中每个比特对应一个小区，例如，从第一位开始，比特的顺序与第一区域中的小区列表中的小区是一一对应的。示例性的，第一区域中包括32个小区，该bitmap的长度为32位，一一对应第一区域中的32个小区。
作为一种实现方式，第一指示信息用于指示第一组播配置信息对应的小区提供的第一组播会话的状态。第一组播配置信息对应的小区包括第一小区，也可以说，第一指示信息用于指示第一小区提供的第一组播会话的状态。
其中，第一组播配置信息对应的小区提供的第一组播会话的状态，可以包括：第一组播配置信息对应的小区正在或未在提供RRC非激活态或空闲态的第一组播会话。
例如，对于比特位图#1对应的组播会话#1来说，bit位置1表示该bit对应的小区当前支持非激活态或空闲态提供组播会话#1，或者说，该小区当前正在提供非激活态或空闲态的组播会话#1。bit位置0表示该bit对应的小区当前不支持在非激活态或空闲态提供该组播会话#1，或者说，该小区当前未在提供非激活态或空闲态的组播会话#1。
可选地，第一组播配置信息对应的小区可以组成第一组播配置信息的有效区域。
例如，当第一小区开始或停止在RRC非激活态或空闲态提供第一组播会话时，第二网络设备向终端设备发送第二消息，该第二消息包括第一指示信息。
在该实现方式中，根据第一指示信息，终端设备可以知道当前正在提供非激活态或空闲态的组播会话#1的小区为哪个或哪些，假设正在提供非激活态或空闲态的组播会话#1的小区包括小区#2，若终端设备加入了该组播会话#1，且该小区#2为终端设备的服务小区，则终端设备可以使用第一组播配置信息接收组播会话#1。
作为又一种实现方式，第一指示信息用于指示第一组播配置信息对应的小区提供的第一组播会话的状态发生变化。具体地，可以包括：第一组播配置信息对应的小区开始或停止提供RRC非激活态或空闲态的第一组播会话。
例如，对于比特位图#1对应的组播会话#1来说，bit位置1表示该bit对应的小区当前开始提供非激活态或空闲态组播会话#1。bit位置0表示该bit对应的小区当前停止在非激活态或空闲态提供该组播会话#1，或者说，对于该小区的组播会话，终端设备只能在连接态接收。
在该实现方式中，根据第一指示信息，终端设备可以知道当前开始提供非激活态或空闲态的组播会话#1的小区为哪个或哪些，假设开始提供非激活态或空闲态的组播会话#1的小区包括小区#2，若终端设备加入了该组播会话#1，且该小区#2为终端设备的服务小区，则终端设备可以使用第一组播配置 信息接收组播会话#1。
可选地，第二消息为寻呼消息或RRC释放消息。
可选地，终端设备在执行S420时处于空闲态或非激活态。
S430，第二网络设备根据第一组播配置发送第一组播会话，在第一小区为终端设备的驻留小区的情况下，终端设备根据第一组播配置信息接收第一组播会话。
其中，第一小区可以为正在提供非激活态或空闲态的组播会话#1的小区，也可以是开始提供非激活态或空闲态的组播会话#1的小区。
具体地，终端设备根据第一组播配置信息接收第一组播会话，包括：在第一指示信息指示第一小区开始在非激活态或空闲态提供第一组播会话的情况下，终端设备根据第一组播配置信息在无线资源控制非激活态或空闲态接收第一组播会话。在第一指示信息指示第一小区停止在非激活态或空闲态提供第一组播会话的情况下，终端设备向第一小区对应的网络设备发送RRC恢复请求消息。进一步，第一小区对应的网络设备可以根据RRC恢复请求消息向终端设备发送RRC释放消息或RRC恢复消息。例如，若第一小区此时仍支持在非激活态或空闲态提供第一组播会话，则第一小区对应的网络设备可以根据RRC恢复请求消息向终端设备发送RRC释放消息，终端设备可以根据RRC释放消息继续保持RRC非激活态或空闲态，并根据第一组播配置信息接收第一组播会话。又如，若第一小区此时不支持在非激活态或空闲态提供第一组播会话，则第一小区对应的网络设备可以根据RRC恢复请求消息向终端设备发送RRC恢复消息，进一步，终端设备可以根据RRC恢复消息进入连接态，并在RRC连接态根据第一组播配置信息接收第一组播会话。
其中，第一小区对应的网络设备指的是管理第一小区的网络设备，其可以是第一网络设备，也可以是第二网络设备，也可以是第一区域的其他网络设备。
基于上述方案，在终端设备处于连接态时，第一网络设备将第一组播配置信息对应的小区的信息预配置给终端设备，第二网络设备可以通过第二消息中的第一指示信息向终端设备指示各个小区的组播会话的状态，在某个小区为终端设备的服务小区，且该小区开始提供非激活态或空闲态的组播会话，终端设备可以使用第一组播配置信息接收该组播会话。如此，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
可选地，第一小区为第四网络设备管理的小区。该方法还包括：在第二网络设备向终端设备发送第二消息之前，第二网络设备接收来自第四网络设备的第二指示信息，第二指示信息用于指示第一小区开始或停止在非激活态或空闲态提供第一组播会话。
具体地，当第一区域内任一小区停止或开始提供非激活态或空闲态组播会话，假设该小区为gNB2的小区，gNB2通过Xn接口向相邻基站发送组播配置变更指示信息，其中包括该gNB的小区停止或开始提供inactive态组播会话的小区标识，以及停止或开始提供的组播会话的标识。此时，区域内的gNB都会触发组寻呼，寻呼消息中指示组播会话的标识以及该组播会话对应的第一指示信息。
基于上述方案，第一区域内任一小区停止或开始提供非激活态或空闲态组播会话，第一区域内的网络设备都会触发组寻呼，如此，无论终端设备移动至第一区域的哪个小区，其都能够快速获取区域内的组播会话的开始或停止的情况。此外，在某个小区开始提供非激活态或空闲态组播会话时，终端设备也能够及时接收组播会话，因此，具有较高的通信效率。
可选地，在S410之前，该方法还包括：第一网络设备接收来自第四网络设备的第九信息，第九信息用于指示第一组播配置信息对应的R个小区的标识，第一组播配置信息对应的小区信息包括R个小区，R为正整数。
具体地，第一区域内的网络设备可以协调确定第一区域包括的小区列表。
可选的，第二消息中仅指示组播会话状态发生变化的小区。若组播会话关联的小区未发生改变，则该组播会话及关联的小区不包含在第二消息中。终端设备在第二消息中未收到，则认为小区提供的组播会话未发生改变。
作为一种实现方式，第二网络设备在发送组寻呼时，根据加入了该组播会话的终端设备的标识计算寻呼时机(paging occasion，PO)的位置，在相应的PO上发送组寻呼。
图9是本申请实施例提供的一种通信方法500的示意图。方法500可以视为方法200和方法400 的结合，方法500可以包括如下步骤。
S510，第一网络设备向终端设备发送第八信息，相应地，终端设备接收第八信息。
其中，第八信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，第八信息还包括至少一个组播配置信息对应的小区信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息，至少一个组播配置信息对应的小区信息包括第一组播配置信息对应的小区信息，该第一配置信息对应的小区信息包括第一小区。
对于同一组播会话，第一区域内的不同小区可以使用不同的组播配置信息发送组播会话。对于每一个组播会话，第一网络设备可以向终端设备预配置组播配置信息以及该组播配置信息对应的索引信息、小区信息。例如，TMGI_1的组播配置_1的索引为index1，对应的小区为小区_1、小区_2、小区_3；TMGI_1对应的组播配置_1的索引为index2，对应的小区为小区_1、小区_2、小区_3、小区_4。
S520，第二网络设备向终端设备发送第二消息，该第二消息包括第一指示信息和第二信息，第一指示信息用于指示第一小区提供的第一组播会话的状态，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一配置信息。
例如，当第一区域内的第一小区开始或停止在非激活态或空闲态提供第一组播会话时，或者，当该第一区域内的第一小区的组播配置信息发生变化时，第二网络设备向终端设备发送第二消息，该第二消息包括第一指示信息和第二信息，第一指示信息用于指示第一小区开始或停止在非激活态或空闲态提供第一组播会话，第二信息用于指示第一组播配置。
在方法500中，根据第一指示信息和第一索引信息，终端设备可以确定第一配置信息。
其中，第一指示信息和第一索引信息的具体描述，可以参考方法200和方法400。
S530，第二网络设备根据第一组播配置发送第一组播会话，在第一小区为终端设备的驻留小区的情况下，终端设备根据第一组播配置信息接收第一组播会话。
S530的具体描述可以参考S430。
基于上述方案，在终端设备处于连接态时，第一网络设备将第一组播配置信息对应的小区信息预配置给终端设备，第二网络设备可以通过第二消息中的第一指示信息获取各个小区的组播会话的状态，并通过第二信息向终端设备指示第一组播配置信息。在某个小区为终端设备的服务小区，且该小区开始提供非激活态或空闲态的组播会话，终端设备可以使用第一组播配置信息接收该组播会话。如此，一方面可以避免通过广播的形式接收组播配置信息带来安全隐患，另一方面，可以避免终端设备进入RRC连接态接收组播配置信息带来信令开销和时延。
此外，相比方法400，方法500中，对于同一组播会话，第一区域内的不同小区可以使用不同的组播配置信息，因此，具有更强的灵活性。
可选地，方法400还包括：第一网络设备确定获取第八信息。具体地，可以参考方法200中第一网络设备获取第一信息的方法。
可选地，方法400还包括：第一网络设备或第二网络设备向终端设备发送第四信息，相应地，终端设备接收第四信息，第四信息用于指示第一组播会话对应的第一G-RNTI，第一网络设备可以通过第一G-RNTI对第一组播会话进行加扰，终端设备可以通过第一G-RNTI对接收的第一组播会话进行解扰。
应理解，方法400中未详细描述的内容可以参考方法200和方法300。
本申请还提供一种通信的方法，还方法可以用于解决一个区域内的网络设备之间如何同步组播配置信息的问题，通过该方法，对于同一个组播会话，该区域内的不同小区可以使用同样的组播配置信息发送该组播会话。
图10是本申请实施例提供的一种通信的方法600的示意图，该方法包括以下步骤。
S610，第五网络设备向第一设备发送第三消息。
其中，第三消息用于请求第一组播会话的组播配置信息，或者说，第三消息用于请求该第一组播会话对应的组播配置信息，该第一组播会话对应的组播配置信息可以用于配置第一组播会话。其中，组播配置信息又称为MBS组播配置信息或组播配置，指的是用于接收MBS中的组播会话的配置参数，组播配置信息由组播配置参数组成。又如，组播配置信息可以包括以下一项或多项：组播MRB配置、物理信道配置、DRX配置、G-RNTI配置、邻小区配置、CFR配置，其中每一项都可以理解为一个组播配置参数，关于组播配置信息的解释说明可以参考方法200，在此不赘述。
示例性地，第三消息包括该第一组播会话的标识，第一组播会话的标识可以是TMGI。
其中，第一设备指的是非终端侧的设备。第一设备执行的功能可以是由某个实体设备的功能模块或网元执行，换言之，第一设备可以是指某个实体设备的功能模块或网元。
作为一个示例，第一设备可以是核心网(core network)设备，例如，第一设备指的是核心网设备中的接入和移动性管理功能(access and mobility management function,AMF)网元或会话管理功能(session management function，SMF)网元。
作为另一个示例，第一设备也可以是第六网络设备，例如，第五网络设备可以直接向第六网络设备发送第三消息。或者，第五网络设备也可以经过其他设备的转发向第六网络设备发送第三消息，其中，该其他设备可以是核心网设备，换言之，第五网络设备和第六网络设备之间的可以直接通信，也可以通过核心网间接通信。
可选地，S610的触发条件可以是，第五网络设备管理的小区开始为非激活态或空闲态的终端设备提供第一组播会话，或者，第五网络设备管理的小区中存在终端设备加入第一组播会话。
其中，为非激活态或空闲态的终端设备提供组播会话，也可以说，开始在非激活态或空闲态提供组播会话，或者说小区开始提供空闲态或非激活态的组播会话，或者，小区开始在终端设备处于非激活态或空闲态时向终端设备发送组播会话，或者，小区打开在非激活态或空闲态发送组播会话的开关。开始或打开后，支持在非激活态或空闲态接收组播会话的终端设备将会在非激活态或空闲态接收组播会话。如果小区停止在非激活态或空闲态提供组播会话，那么即使终端设备支持在非激活态或空闲态接收组播会话，终端设备也无法在非激活态或空闲态接收组播会话。
应理解，执行S610的第五网络设备可以是一个，也可以是多个，该多个第五网络设备可以属于同一个区域，对于该区域内的任一个网络设备，若其管理的小区满足上述触发条件，其都可以向第一设备发送第三消息，从而请求第一组播会话的组播配置信息。
S620，第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息。
其中，第一组播配置信息可以用于配置终端设备在RRC非激活态或空闲态接收第一组播会话。
其中，组播配置参数的取值范围可以包括以下至少一个：G-RNTI的取值范围、MRB标识的取值范围、LCH标识的取值范围、物理信道配置参数的取值范围、非连续接收DRX配置参数的取值范围、公共频域资源CFR配置参数的取值范围。例如，G-RNTI的取值范围为10000-15000，MRB的标识的取值范围为100-200，LCH的标识的取值范围为5000-10000。
可选地，组播配置参数的取值范围可以理解为多个组播会话的共享取值范围，即该取值范围不区分组播会话或组播业务，或者说，该组播配置参数的取值范围适用于该区域内的任意一个组播会话或组播业务。例如，该区域内的第一组播会话、第二组播会话、第三组播会话等都可以使用这个取值范围中的取值。
第一设备可以根据组播配置参数的取值范围以及来自一个或多个第五网络设备的第三消息确定第一组播会话的第一组播配置信息。例如，当组播配置参数的取值范围存在多个不同的范围时，第一设备可以从多个不同的范围的交集中选择第一组播配置信息。又如，当组播配置参数的取值范围只有一个时，第一设备可以在该取值范围中为第一组播会话选择第一组播配置信息。又如，当多个第五网络设备请求第一组播会话的组播配置信息，第一设备可以为该第一组播会话确定多个第五网络设备共享的组播配置信息。
应理解，当存在多个第五网络设备，那么就可以理解为存在多个第三消息，或者说，存在多个组播配置信息的取值范围，其中，一个第五网络设发送一个第三消息，每个第三消息携带该第五网络设备预配置或确定的一个组播配置参数的取值范围。
S630，第一设备向第五网络设备发送第一组播配置信息。
基于上述方案，第一设备可以为一个或多个第五网络设备提供的第一组播会话确定第一组播配置信息，换言之，第一设备可以为第一组播会话确定一个或多个第五网络设备均可以使用的第一组播配置信息，使得对于同一组播会话，一个区域内支持第一组播会话的不同网络设备可以使用同样的组播配置信息，如此，能够同步区域内的组播配置信息。
在一种实现方式中，第三消息包括第一组播会话的标识，组播配置参数的取值范围包括G-RNTI的取值范围，此时，S620具体包括：第一设备从G-RNTI的取值范围中选择一个值作为第一组播会话 的G-RNTI，第一组播配置信息包括第一组播会话的G-RNTI。
在又一种实现方式中，第三消息包括第一组播会话的标识和第一组播会话所需的组播无线承载MRB的数目X，组播配置参数的取值范围包括MRB标识的取值范围，此时，S620具体包括：第一设备从MRB标识的取值范围中选择X个值作为第一组播会话的MRB标识，第一组播配置信息包括第一组播会话的MRB标识，X为正整数。
在又一种实现方式中，第三消息包括第一组播会话的标识和第一组播会话的第一MRB所需的逻辑信道LCH的数目Y，组播配置参数的取值范围包括LCH标识的取值范围，此时，S620具体包括：第一设备从LCH标识的取值范围中选择Y个值作为第一MRB的LCH标识，第一组播配置信息包括第一MRB的LCH标识，Y为正整数。
在又一种实现方式中，第三消息包括第一组播会话的标识，组播配置参数的取值范围包括物理信道配置参数的取值范围，此时，S620具体包括：第一设备从物理信道配置参数的取值范围中选择至少一个值作为第一组播会话的物理信道配置参数，第一组播配置信息包括第一组播会话的物理信道配置参数。
在又一种实现方式中，第三消息包括第一组播会话的标识，组播配置参数的取值范围包括非连续接收DRX配置参数的取值范围，此时，S620具体包括：第一设备从DRX配置参数的取值范围中选择至少一个值作为第一组播会话的DRX配置参数，第一组播配置信息包括第一组播会话的DRX配置参数。
在又一种实现方式中，第三消息包括第一组播会话的标识，组播配置参数的取值范围包括公共频域资源CFR配置参数的取值范围，此时，S620具体包括：第一设备从CFR配置参数的取值范围中选择至少一个值作为第一组播会话的CFR配置参数，第一组播配置信息包括第一组播会话的CFR配置参数。
应理解，上述各种实现方式可以相互结合，不予限制。作为示例，第三消息包括第一组播会话的标识、第一组播会话所需的组播无线承载MRB的数目、第一组播会话的每个MRB所需的逻辑信道LCH的数目，组播配置参数的取值范围包括MRB标识的取值范围、LCH标识的取值范围，此时，S620具体包括：第一设备从MRB标识的取值范围中为第一组播会话选择相应数目的MRB标识，从LCH标识的取值范围中为每个MRB选择相应数目的LCH标识。例如，第三消息指示组播业务TMGI-1需要2个MRB，其中一个MRB需要2个LCH，另一个MRB需要3个LCH，第一设备确定MRB ID-1和MRB ID-2，并确定MRB ID-1对应的LCH为LCH ID-1和LCH ID-2，MRB ID-2对应的LCH为LCH ID-3、LCH ID-4和LCH ID-5。
可选地，若第三消息包括该第一组播会话所需的MRB的数目和逻辑信道(logiccal channel，LCH)的数目，那么MRB的数目和LCH的数目可以是第五网络设备根据该第一组播会话的服务质量(quality of service，QoS)确定的。示例性地，对同一个组播业务，一个区域内(例如RNA区域)的gNB可以有相同的QoS和MRB/LCH的映射规则，可以理解，对相同业务，区域内的gNB可以确定出相同的MRB/LCH数目。
可选地，第三消息也可以不包括第一组播会话所需的MRB的数目和逻辑信道(logiccal channel，LCH)的数目。这种情况下，SMF可以根据该第一组播会话的QoS确定MRB的数目和LCH的数目，如果第一设备为SMF，那么由SMF执行S620。如果第一设备为AMF或第六网络设备，那么SMF可以将确定的第一组播会话所需的MRB的数目和LCH的数目发送给AMF或第六网络设备，由AMF或第六网络设备执行S620。
可选地，S620，第一设备根据第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：第一设备根据第三消息中的第一组播会话的标识确定第一组播会话的G-RNTI，并根据组播配置参数的取值范围确定第一组播配置信息中除G-RNTI之外的其他组播配置信息，例如，MRB标识、LCH标识、DRX配置参数、CFR配置参数等。其中，第一根据组播配置参数的取值范围确定第一组播配置信息中除G-RNTI之外的其他组播配置信息的具体方法可以参考上文描述。第一设备根据第一组播会话的标识确定第一组播会话的G-RNTI的具体方式可以参考方法200中的配置方式1。应理解，上述方式可以视为方法600和方法200的结合的一种示例。
作为一种实现方式，组播配置参数的取值范围是第一设备中预配置的。例如，第一设备为第六网 络设备，且组播配置参数的取值范围由OAM配置。这种情况下，OAM可以向一个区域内的多个网络设备配置相同的组播配置参数的取值范围，第一设备在确定第一组播配置信息时，可以在该取值范围内为第一组播会话确定相应的第一组播配置信息。
作为另一种实现方式，组播配置参数的取值范围是第五网络设备向第一设备发送的。在该实现方式中，该方法600还可以包括：第五网络设备向第一设备发送第四消息，第四消息包括组播配置参数的取值范围。
例如，组播配置参数的取值范围由第五网络设备确定，则第五网络设备将确定的取值范围发送给第一设备，该第一设备可以是第六网络设备，也可以是核心网设备。又如，组播配置参数的取值范围由OAM向第五网络设备配置，且第一设备为核心网设备，则第五网络设备可以向核心网设备发送该取值范围。
可选地，在该实现方式中，由于组播配置参数的取值范围由第五网络设备确定，那么不同的第五网络设备确定的取值范围可以是不同的，例如，gNB1确定G-RNTI的取值范围为10000-20000，gNB2确定G-RNTI的取值范围为5000-15000。这种情况下，每个第五网络设备可以分别向第一设备发送其确定的取值范围。当每个第五网络设备确定的组播配置参数的取值范围发生改变时，每个第五网络设备可以向第一设备指示更新的取值范围。此外，第一设备在确定第一组播配置信息时，可以先确定多个不同的范围的交集，在从交集中为第一组播会话确定相应的第一组播配置信息。
示例性地，第四消息为PDU会话资源建立请求传输(PDU session resource setup request transfer)消息或PDU会话资源建立修改请求传输(PDU session resource setup modify request transfer消息)中。第五网络设备可以在第一个组播会话或任一个组播会话建立时，向第一设备发送第四消息。
应理解，由于组播配置参数(例如，RNTI的取值、MRB标识、LCH标识)也用于单播、广播等其他业务类型，当第五网络设备有inactive态组播业务的需求时，某些参数的取值(例如RNTI的取值)可能已经被单播或广播占用，如果由第一设备直接为某个组播业务指定组播配置参数，会导致与已经使用的单播或广播的配置参数发生冲突，此时第五网络设备需要重配置发生冲突的单播或广播业务所使用的配置参数，会影响用户体验，增加重配的信令开销。基于上述方案，第五网络设备可以向第一设备指示组播配置参数的取值范围或者第一设备中预配置组播配置参数的取值范围，如此，可以避免inactive态组播配置与其他业务的配置发生冲突(例如，RNTI的取值冲突，又如，LCH标识冲突)，从而避免上述重配置的发生，避免额外的信令开销，提升用户体验。
可选地，该方法600还可以包括：第五网络设备向第一设备发送第二区域的标识信息，第二区域为组播配置参数的取值范围的生效区域。
其中，第二区域内的小区提供至少一个组播会话，至少一个组播会话包括第一组播会话，该方法还可以包括：第一设备为至少一个组播会话中的每个组播会话确定互不相同的组播配置信息，或者说，至少一个组播会话中除第一组播会话之外的其他组播会话的组播配置信息和第一组播配置信息不同。换言之，在该第二区域内，第一设备从该组播配置参数的取值范围内为该区域内组播会话确定组播配置信息，且不同的组播会话的组播配置信息均不相同。在第二区域外，允许其他组播会话与第二区域内的组播会话的组播配置信息相同。
示例性地，组播配置参数的取值范围的生效区域可以是RNA，该RNA包括第五网络设备。组播配置参数的取值范围的生效区域也可以是预配置的区域，例如，为OAM配置的区域。
应理解，第五网络设备向第一设备发送第二区域的标识信息的目的是，终端设备支持的配置参数的取值范围有限，当组播会话总数较多，可能无法为每个会话确定唯一的组播配置信息。因此，通过指示第二区域，第一设备可以仅需要确保一个区域内一个会话有唯一的组播配置信息(例如，唯一的G-RNTI、MRB ID、LCH ID等)，而该区域外的其他会话，仍可以使用该区域内的组播配置信息。
基于上述方案，第五网络设备可以向第一设备发送第二区域的标识信息，使得允许在第一设备管理范围内的不同区域(例如两个不同的RNA区域)复用相同的配置参数，如此，可以提高配置参数的利用效率。
应理解，当一些配置参数的可用的取值范围有限的情况下(比如，现有协议规定MRB标识的最大取值为512，而当第一设备管理范围内各个第五网络设备需要建立的组播会话的数目超过512时)，组播会话之间的组播配置参数会有重叠，组播配置参数无法唯一对应一个组播会话。此外，继续以MRB 标识为例来说，一方面，根据组播会话的QoS需求不同，一个组播会话可以对应一个或多个MRB，会加剧MRB标识的紧缺。另一方面，组播、单播、广播等多种业务形式都需要使用无线承载，对应相应的MRB标识，考虑到其他业务类型可能已经占用了部分MRB标识，组播可用的MRB标识的范围进一步缩小，上述方案可以有效解决上述问题。
可选地，第三消息包括第二小区的标识，第二小区为由第五网络设备管理的、提供RRC非激活态或空闲态的第一组播会话的小区，该方法600还可以包括：第一设备根据来自一个或多个第五网络设备的第三消息确定第十信息，第十信息用于指示第一组播配置信息的生效区域。其中，生效区域，可以理解为配置的同步区域。
在一种实现方式中，第一组播配置信息的生效区域根据一个或多个第三消息中包括的第二小区确定。
在一个示例中，组播配置参数的取值范围是OAM预配置的，此时，第二区域内的多个网络设备配置的组播配置参数的取值范围相同。在该示例中，第一设备可以将多个第五网络设备的第二小区均确定为第一组播配置信息的生效区域。例如，gNB1(第五网络设备的一例)向CN(第一设备的一例)指示其管理的小区1(第二小区的一例)提供RRC非激活态或空闲态的组播会话#1，gNB2(第五网络设备的又一例)向CN指示其管理的小区3(第二小区的又一例)、小区5(第二小区的又一例)提供RRC非激活态或空闲态的组播会话#1，那么CN可以为组播会话#1确定组播配置信息#1，并确定组播配置信息#1的生效区域为小区1、小区3、小区5，或者组播配置信息#1的生效区域为gNB1和gNB2管理的区域。
在又一个示例中，组播配置参数的取值范围由第五网络设备确定，此时，第二区域内的多个网络设备配置的组播配置参数的取值范围可能不同。在该示例中，第一设备可以确定多个第五网络设备指示的组播配置参数的取值范围的交集，对于存在交集的取值范围对应的网络设备，其管理的第二小区可以组成第一组播配置信息的生效区域，换言之，第一设备确定多个第五网络设备都可用的组播配置信息为该组播会话对应的组播配置信息。例如，gNB1(第五网络设备的一例)向CN(第一设备的一例)指示其管理的小区1(第二小区的一例)提供RRC非激活态或空闲态的组播会话#1，gNB2(第五网络设备的又一例)向CN指示其管理的小区3(第二小区的又一例)、小区5(第二小区的又一例)提供RRC非激活态或空闲态的组播会话#1，此外，gNB1指示其确定的G-RNTI的取值范围为5000-10000，gNB2指示其确定的G-RNTI的取值范围为10000-15000，由于gNB1指示确定的G-RNTI的取值范围和gNB2确定的G-RNTI的取值范围无交集，那么第一设备可以从gNB2确定的G-RNTI的取值范围中为组播会话#1确定组播配置信息#1，并确定组播配置信息#1的生效区域为小区3、小区5，或者组播配置信息#1的生效区域为gNB2管理的区域，即小区1或者说gNB2管理的区域不属于组播配置信息#1的生效区域。
在该示例中，若第二区域内某个第五网络设备确定的组播配置参数的取值范围和其他网络设备确定的组播配置参数的取值范围无法取到交集，第一设备可以向该第五网络设备指示配置失败；可选的，第一设备不将该第五网络设备加入组播配置信息的生效区域，在组播配置信息的生效区域内也不会包括该第五网络设备的标识或其管理的小区的标识。
在另一种实现方式中，第一组播配置信息的生效区域也可以不根据第三消息中的第二小区确定。例如，第一组播配置信息的生效区域可以等于第二区域(即组播配置参数的取值范围的生效区域，比如RNA区域)。这种方式中，第一组播配置信息的生效区域与第二区域内的网络设备是否正在提供第一组播会话无关。即，第二区域内的网络设备可以未在提供RRC inactive态或空闲态的第一组播会话；或者正在提供RRC inactive态空闲态的第一组播会话。如果该区域内的网络设备正在提供RRC inactive态空闲态的第一组播会话，则提供的第一组播会话的小区可以使用第一组播配置信息配置第一组播会话。换言之，这种方式中，第一组播配置信息的生效区域是可以不需要动态更新的，即第一组播配置信息的生效区域不会由于一个网络设备开始或停止提供RRC inactive态空闲态的第一组播会话而更新。
在该实现方式中，该方法还可以包括：若第五网络设备管理的小区不支持在非激活态或空闲态提供第一组播会话，或，第五网络设备管理的小区不支持组播会话，则第五网络设备发送第一消息，第一消息不包括组播会话的标识。具体地，可以参考方法200。
应理解，本申请中的第一组播配置信息的生效区域，并不限定终端设备在该区域一定能收到第一 组播配置信息对应的第一组播会话。如此，该生效区域内的小区当前的组播会话发生变化时，例如，开始提供或停止提供，网络设备之间无需进行同步更新。
可选地，该方法600还包括：第一设备向第五网络设备发送第十信息。
可选地，该方法600还包括：第五网络设备向第一设备发送第十二信息，该第十二信息用于指示是否接受该第一组播配置信息，或者说，用于指示第一组播会话的组播配置信息是否配置成功。
具体地，第五网络设备在接收到第一组播配置信息后，可以进一步确定第一组播配置信息是否满足其确定或配置的组播配置参数的取值范围，如果满足，则第十二信息指示接受该第一组播配置信息，如果不满足，则第十二信息指示拒绝该第一组播配置信息。进一步，第一设备可以根据该第十二信息更新第一组播配置信息的生效区域。
可选地，对某一个组播业务TMGI，有新的网络设备加入生效区域后，第一设备向现有的生效区域中的网络设备更新该生效区域，即加入新的网络设备的标识或者该网络设备的小区标识。
可选地，该方法600还包括：第五网络设备向第一设备发送第十一信息，第十一信息用于指示第五网络设备管理的第三小区停止在无线资源控制RRC非激活态或空闲态提供第一组播会话，第一设备将第三小区从第一组播配置信息的生效区域中移除，或者说，第一设备确定第一组播配置信息对应的更新的生效区域，该更新的生效区域不包括第三小区。
在一种实现方式中，当第五网络设备停止提供inactive态或空闲态的第一组播会话时(例如，没有连接态终端设备接收第一组播会话)，第五网络设备可以向第一设备指示组播配置请求停止(第十一信息的一例)，第一设备将该第五网络设备从第一组播配置信息的生效区域中移除。此外，当第五网络设备停止提供inactive态或空闲态的第一组播会话时，在第一组播配置信息的生效区域发生更新的情况下，第一设备将停止向该第五网络设备发送更新的生效区域。另外，当第五网络设备停止提供inactive态或空闲态的第一组播会话时，第五网络设备可以向终端设备通知inactive态组播配置更新：例如，第五网络设备向终端设备指示的更新的inactive态组播配置中不包含第一组播会话的组播配置，进一步，当驻留在第五网络设备的小区上的inactive态终端设备仍期望接收第一组播会话时，终端设备可以触发RRC连接恢复。
可选地，当第二区域内不再有第五网络设备向第一设备请求提供第一组播会话的组播配置信息时，第一设备删除存储的第一组播配置信息。
应理解，上述方法600可以与其他方法结合使用，例如，下面给出两种实施场景。
在一种实施场景中，该方法600还包括：第五网络设备向终端设备发送第一组播配置信息和第十信息。
示例性地，第五网络设备可以通过专用信令或公共信令向终端设备发送第一组播配置信息和第十信息。其中，该专用信令可以是RRC释放消息，该公共信令可以是MCCH或SIB。
可选地，生效区域的含义是指，终端设备在该第一组播配置信息的生效区域内，根据第一组播配置信息在无线资源控制RRC非激活态或空闲态接收第一组播会话，换言之，在生效区域内，终端设备不需要额外进入连接态就可以继续接收第一组播会话。当终端设备在该生效区域外，或者说，终端设备移出该生效区域，终端设备可以触发RRC连接恢复流程。
基于上述方案，当终端设备在该区域内移动时，终端设备可以继续使用该组播配置信息接收组播会话，能够保证终端设备接收组播业务的连续性。
另一方面，可以避免终端设备在每次小区重选到新小区时都触发RRC连接恢复，能够节省终端设备的能耗，也能够节省空口信令开销。
在另一种实施场景中，上述方法600可以应用于方法400，例如，方法400中第一网络设备可以执行方法600中的第五网络设备执行的方法，方法400中的第四网络设备执行的步骤可以由方法600中的第一设备执行。示例性地，当方法600应用于方法400，方法400包括以下步骤：
S610，第一网络设备向第一设备发送第三消息。
S610，第一设备确定根据第三消息和组播配置参数的取值范围确定第一组播配置信息。
S630，第一设备向第一网络设备发送第一组播配置信息。
S410，第一网络设备向终端设备发送第八信息。
可选地，方法400中，“第一组播配置信息对应的R个小区的标识”，可以理解为方法600中的 第一组播配置信息的生效区域。
S420，第二网络设备向终端设备发送第二消息。
S430，第二网络设备根据第一组播配置发送第一组播会话，在第一小区为终端设备的驻留小区的情况下，终端设备根据第一组播配置信息接收第一组播会话。
应理解，上述步骤的详细描述可以参考方法400和方法600，在此不赘述。
图11是本申请实施例提供的一种通信的方法700的示意图，该方法700可以视为方法600的一种具体实现。该方法700可以包括以下步骤。
S701，gNB(第五网络设备的一例)向CN(第一设备的一例)发送消息#1(第四消息的一例)。
消息#1包括组播配置参数的取值范围以及区域#1(第二区域的一例)的标识。示例性地，组播配置参数的取值范围包括MRB标识的取值范围、LCH标识的取值范围。
可选地，该组播配置参数的取值范围可以是OAM预配置的。
S702，gNB向CN发送消息#2(第三消息的一例)。
消息#2用于请求组播会话#1的组播配置，消息#2包括组播会话#1的标识，例如，为TMGI-1。
可选地，消息#2包括MRB的数目和LCH的数目。
其中，消息#2还可以包括小区#1(第二小区的一例)的标识，该小区#1的标识用于指示gNB管理的小区#1开始提供inactive态组播会话#1。
该步骤可以参考S610。
S703，CN根据消息#1和消息#2确定组播配置#1(第一组播配置信息的一例)和区域#2(第一组播配置信息的生效区域的一例)。
例如，组播配置#1包括MRB标识和LCH标识，CN从MRB标识的取值范围中为组播会话#1选择相应数目的MRB标识，从LCH标识的取值范围中为组播会话#1的每个MRB选择相应数目的LCH标识。
其中，区域#2可以包括小区#1的标识。
S704，CN向gNB发送组播配置#1，并指示区域#2的标识。
S705，gNB向CN发送信息#5(第十二信息的一例)，信息#5指示接受组播配置#1。
S706，gNB向UE发送组播配置#1和区域#2的标识。
例如，gNB通过RRC释放消息向UE发送组播配置#1和区域#2的标识。
S707，gNB向CN发送信息#6(第十一信息的一例)，信息#6指示小区#1停止提供inactive态组播会话#1。
当gNB管理的小区#1停止提供inactive态组播会话#1，gNB执行S707。
S708，CN根据信息#6更新区域#2，即将小区#1从组播配置#1的生效区域移除。
图12是本申请实施例提供的一种通信的方法800的示意图，该方法800可以视为方法600的一种具体实现。该方法700可以包括以下步骤。
S801，gNB#1(第五网络设备的一例)向gNB#2(第一设备的一例，也是第六网络设备的一例)发送消息#3(第三消息的一例)。
消息#3用于请求组播会话#1的组播配置，消息#3包括组播会话#1的标识，例如，为TMGI-1。
其中，消息#3还可以包括小区#2(第二小区的一例)的标识，该小区#2的标识用于指示gNB#1管理的小区#2开始提供inactive态组播会话#1。
可选地，消息#3包括MRB的数目和LCH的数目。
该步骤可以参考S610。
S802，gNB#2根据消息#3和组播配置参数的取值范围确定组播配置#2(第一组播配置信息的一例)和区域#3(第一组播配置信息的生效区域的一例)。
其中，该组播配置参数的取值范围可以是OAM向RNA范围内的gNB预配置的，RNA范围内的gNB包括gNB1和gNB2。
例如，组播配置#2包括MRB标识和LCH标识，gNB#2从MRB标识的取值范围中为组播会话#1选择相应数目的MRB标识，从LCH标识的取值范围中为组播会话#1的每个MRB选择相应数目的LCH标识。
其中，区域#3可以包括小区#2的标识。
S803，gNB#2向gNB#1发送组播配置#2，并指示区域#3的标识。
S804，gNB#1向UE发送组播配置#2和区域#3的标识。
例如，gNB#1通过RRC释放消息向UE发送组播配置#2和区域#3的标识。
S805，gNB#1向gNB#2发送信息#7(第十一信息的一例)，信息#7指示小区#2停止提供inactive态组播会话#1。
当gNB#1管理的小区#2停止提供inactive态组播会话#1，gNB#1执行S805。
S806，gNB#2根据信息#7更新区域#3，即将小区#2从组播配置#1的生效区域移除。
图13是本申请实施例提供的一种通信的方法900的示意图，该方法900可以视为方法600的一种具体实现。该方法900可以包括以下步骤。
S901，gNB#1(第五网络设备的一例)向CN(第一设备的一例)发送消息#4(第三消息的一例)。
消息#4用于请求组播会话#1的组播配置，消息#4包括组播会话#1的标识，例如，为TMGI-1。
可选地，消息#4包括MRB的数目和LCH的数目。
其中，消息#4还可以包括小区#2(第二小区的一例)的标识，该小区#2的标识用于指示gNB#1管理的小区#2开始提供inactive态组播会话#1。
该步骤可以参考S610。
S902，CN向gNB#2发送消息#4。
S903，gNB#2根据消息#4和组播配置参数的取值范围确定组播配置#2(第一组播配置信息的一例)和区域#3(第一组播配置信息的生效区域的一例)。
S903可以参考S802。
S904，gNB#2向CN发送组播配置#2，并指示区域#3的标识。
可选地，CN可以存储组播配置#2和区域#3。
S905，CN向gNB#1发送组播配置#2，并指示区域#3的标识。
S906，gNB#1向UE发送组播配置#2和区域#3的标识。
S906参考S804。
S907，gNB#1向CN发送信息#7(第十一信息的一例)，信息#7指示小区#2停止提供inactive态组播会话#1。
当gNB#1管理的小区#2停止提供inactive态组播会话#1，gNB#1执行S907。
S908，CN向gNB#2发送信息#7。
S909，gNB#2根据信息#7更新区域#3，即将小区#2从组播配置#1的生效区域移除。
方法900可以适用于gNB#1和gNB#2之间没有通信接口的场景。
应理解，本申请各个实施例中提及的网络设备可以是指基站，任一网络设备执行的步骤可以由该基站执行，也可以由该基站的CU执行，或者由该基站的模组执行。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，本申请的各实施例中的方案可以进行合理的组合使用，并且实施例中出现的各个术语的解释或说明可以在各个实施例中互相参考或解释，对此不作限定。
还可以理解，上述各个方法实施例中，由终端设备实现的方法和操作，也可以由可由终端设备的组成部件(例如芯片或者电路)来实现；此外，由网络设备实现的方法和操作，也可以由可由网络设备的组成部件(例如芯片或者电路)来实现，不作限定。
相应于上述各方法实施例给出的方法，本申请实施例还提供了相应的装置，所述装置包括用于执行上述各个方法实施例相应的模块。该模块可以是软件，也可以是硬件，或者是软件和硬件结合。可以理解的是，上述各方法实施例所描述的技术特征同样适用于以下装置实施例。
图14是本申请实施例提供的一种通信装置2800的示意图。该装置2800包括收发单元2810，收发单元2810可以用于实现相应的通信功能。收发单元2810还可以称为通信接口或通信单元。
可选地，该装置2800还可以包括处理单元2820，处理单元2820可以用于进行数据处理。
可选地，该装置2800还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元2820 可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中终端设备或网络设备执行的动作。
一种可能的设计，该装置2800可以是前述实施例中的终端设备，也可以是终端设备的组成部件(如模块或芯片)。该装置2800可实现对应于上文方法实施例中的终端设备执行的步骤或者流程，其中，收发单元2810可用于执行上文方法实施例中终端设备的收发相关的操作，处理单元2820可用于执行上文方法实施例中终端设备的处理相关的操作。
在该设计的一种实现方式中，装置2800用于实现方法200或300中所示的方法实施例中终端设备的功能。
示例性地，收发单元2810用于接收来自第一网络设备的第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息；该收发单元2810还用于：接收来自第二网络设备的第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息；处理单元2820用于：根据第一组播配置信息在无线资源控制RRC非激活态或空闲态接收来自第二网络设备的第一组播会话。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法200或300中的其他与终端设备相关的步骤、动作或者方法，在此不再赘述。
在该设计的另一种实现方式中，装置2800用于实现方法400或500中所示的方法实施例中终端设备的功能。
示例性地，收发单元2810用于接收来自第一网络设备的第八信息，第八信息包括第一组播配置信息和第一组播配置信息对应的小区的信息，第一组播配置对应第一组播会话，第一组播配置信息对应的小区信息包括第一小区；该收发单元2810还用于：接收来自第二网络设备的第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的第一组播会话的状态；处理单元2820用于：在第一小区为终端设备的驻留小区的情况下，根据第一组播配置信息接收第一组播会话。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法400或500中的其他与终端设备相关的步骤、动作或者方法，在此不再赘述。
在该设计的另一种实现方式中，装置2800用于实现方法600、700、800或900中所示的方法实施例中终端设备的功能。
示例性地，收发单元2810，用于接收来自第五网络设备的第一组播配置信息和第十信息，第一组播配置信息用于配置第一组播会话，第十信息用于指示第一组播配置信息的生效区域；处理单元2820，用于在该生效区域内，根据第一组播配置信息在无线资源控制RRC非激活态或空闲态接收第一组播会话。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法600、700、800或900中的其他与终端设备相关的步骤、动作或者方法，在此不再赘述。
又一种可能的设计，该装置2800可以是前述实施例中的第三网络设备，也可以是第三网络设备的组成部件(如模块或芯片)。该装置2800可实现对应于上文方法实施例中的第三网络设备执行的步骤或者流程，其中，收发单元2810可用于执行上文方法实施例中第三网络设备的收发相关的操作，处理单元2820可用于执行上文方法实施例中第三网络设备的处理相关的操作。
在该设计的一种实现方式中，装置2800用于实现方法200或300所示的方法实施例中第三网络设备的功能。其中，该第三网络设备可以是方法200或300中的第一网络设备，也可以是第二网络设备。
示例性地，收发单元2810，用于发送第二信息，第二信息用于指示第一组播会话关联第一索引信息，第一索引信息指示第一组播配置信息；收发单元2810，还用于根据第一组播配置信息发送第一组播会话。
可选地，收发单元2810，还用于向终端设备发送第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括第一组播配置信息，至少一个组播配置信息对应的索引信息包括第一索引信息。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法200或300中的其他与第三网络设备相关的步骤、动作或者方法，在此不再赘述。
在该设计的另一种实现方式中，装置2800用于实现方法400或500所示的方法实施例中第三网络设备的功能。其中，该第三网络设备可以是方法400或500中的第一网络设备，也可以是第二网络设备。
示例性地，收发单元2810，用于发送第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的第一组播会话的状态发生变化；收发单元2810，还用于根据第一组播配置信息发送第一组播会话。
可选地，收发单元2810，还用于向终端设备发送第八信息，第八信息包括第一组播配置信息和第一组播配置信息对应的小区信息，第一组播配置对应第一组播会话，第一组播配置信息对应的小区信息包括第一小区。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法400或500中的其他与第三网络设备相关的步骤、动作或者方法，在此不再赘述。
又一种可能的设计，该装置2800可以是前述实施例中的第四网络设备，也可以是第四网络设备的组成部件(如模块或芯片)。该装置2800可实现对应于上文方法实施例中的第四网络设备执行的步骤或者流程，其中，收发单元2810可用于执行上文方法实施例中第四网络设备的收发相关的操作，处理单元2820可用于执行上文方法实施例中第四网络设备的处理相关的操作。
在该设计的一种实现方式中，装置2800用于实现方法200或300所示的方法实施例中第四网络设备的功能。
示例性地，收发单元2810，用于向第三网络设备发送第六信息，第六信息包括M个组播配置信息和M个组播配置信息对应的索引信息；或，第六信息包括M个组播配置信息，M为正整数；收发单元2810，还用于接收来自第三网络设备的第一信息，第一信息包括至少一个组播配置信息和至少一个组播配置信息对应的索引信息，至少一个组播配置信息包括M个组播配置信息。
又一种可能的设计，该装置2800可以是前述实施例中的第五网络设备，也可以是第五网络设备的组成部件(如模块或芯片)。该装置2800可实现对应于上文方法实施例中的第五网络设备执行的步骤或者流程，其中，收发单元2810可用于执行上文方法实施例中第五网络设备的收发相关的操作，处理单元2820可用于执行上文方法实施例中第五网络设备的处理相关的操作。
在该设计的一种实现方式中，装置2800用于实现方法600、700、800或900中所示的方法实施例中第五网络设备的功能。
示例性地，收发单元2810，用于向第一设备发送第三消息，第三消息用于请求第一组播会话的组播配置信息，收发单元2810还用于：接收来自第一设备的第一组播配置信息，第一组播配置信息根据第三消息和组播配置参数的取值范围确定，第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收第一组播会话。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法600、700、800或900中的其他与第五网络设备相关的步骤、动作或者方法，在此不再赘述。
又一种可能的设计，该装置2800可以是前述实施例中的第一设备，也可以是第一设备组成部件(如模块或芯片)。该装置2800可实现对应于上文方法实施例中的第一设备执行的步骤或者流程，其中，收发单元2810可用于执行上文方法实施例中第一设备的收发相关的操作，处理单元2820可用于执行上文方法实施例中第一设备的处理相关的操作。
在该设计的一种实现方式中，装置2800用于实现方法600、700、800或900中所示的方法实施例中第一设备的功能。
示例性地，收发单元2810，用于接收来自第五网络设备的第三消息，第三消息用于请求第一组播会话的组播配置信息。处理单元2820，用于根据第三消息和组播配置参数的取值范围确定第一组播配置信息，第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收第一组播会话；该收发单元2810还用于：向第五网络设备发送第一组播配置信息。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法600、700、800或900中的其他与第一设备相关的步骤、动作或者方法，在此不再赘述。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法200或300中的其他与第四网络设备相关的步骤、动作或者方法，在此不再赘述。
在该设计的另一种实现方式中，装置2800用于实现方法400或500所示的方法实施例中第四网络设备的功能。
示例性地，收发单元2810，用于向第三网络设备发送第二指示信息，第二指示信息用于指示第一小区提供的非连接态或空闲态第一组播会话的状态，第一小区为第二网络设备管理的小区；收发单元2810，还用于发送第二消息，第二消息包括第一指示信息，第一指示信息用于指示第一小区提供的在非连接态或空闲态的第一组播会话的状态。
应理解，上述内容仅作为示例性理解，该装置2800还能够实现上述方法400或500中的其他与第四网络设备相关的步骤、动作或者方法，在此不再赘述。
还应理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
此外，这里的装置2800以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置2800可以具体为上述实施例中的终端设备，可以用于执行上述各方法实施例中与终端设备对应的各个流程和/或步骤，或者，装置2800可以具体为上述实施例中的第三网络设备，可以用于执行上述各方法实施例中与第三网络设备对应的各个流程和/或步骤，或者，装置2800可以具体为上述实施例中的第四网络设备，可以用于执行上述各方法实施例中与第四网络设备对应的各个流程和/或步骤为避免重复，在此不再赘述。
上述各个方案的装置2800具有实现上述方法中终端设备所执行的相应步骤的功能，或者，上述各个方案的装置2800具有实现上述方法中第三网络设备所执行的相应步骤的功能，或者，上述各个方案的装置2800具有实现上述方法中第四网络设备所执行的相应步骤的功能，或者，上述各个方案的装置2800具有实现上述方法中第五网络设备所执行的相应步骤的功能，或者，上述各个方案的装置2800具有实现上述方法中第一设备所执行的相应步骤的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元2810还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。
需要指出的是，图10中的装置可以是前述实施例中的网元或设备，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
图15是本申请实施例提供的另一种通信装置2900的示意图。该装置2900包括处理器2910，处理器2910与存储器2920耦合，存储器2920用于存储计算机程序或指令和/或数据，处理器2910用于执行存储器2920存储的计算机程序或指令，或读取存储器2920存储的数据，以执行上文各方法实施例中的方法。
可选地，处理器2910为一个或多个。
可选地，存储器2920为一个或多个。
可选地，该存储器2920与该处理器2910集成在一起，或者分离设置。
可选地，如图15所示，该装置2900还包括接口电路2930。接口电路2930用于信号的接收和/或发送。处理器2910和接口电路2930之间相互耦合。例如，处理器2910用于控制接口电路2930进行信号的接收和/或发送。可以理解的是，接口电路2930可以为收发器或输入输出接口。
当装置2900用于实现图5、图7、图8、图9、图10、图11、图12或图13所示的方法时，处理器2910用于实现上述处理单元920的功能，接口电路2930用于实现上述收发单元910的功能。
作为一种方案，该装置2900用于实现上文各个方法实施例中由终端设备执行的操作。
例如，处理器2910用于执行存储器2920存储的计算机程序或指令，以实现上文各个方法实施例中终端设备的相关操作。例如，图5或图7所示实施例中的终端设备执行的方法，又如，图8或图9 所示实施例中的终端设备执行的方法。又如，图10、图11、图12或图13实施例中的终端设备执行的方法。
作为一种方案，该装置2900用于实现上文各个方法实施例中由第三网络设备执行的操作。
例如，处理器2910用于执行存储器2920存储的计算机程序或指令，以实现上文各个方法实施例中第三网络设备的相关操作。例如，图5或图7所示实施例中的第三网络设备执行的方法，又如，图8或图9所示实施例中的第三网络设备执行的方法。
作为又一种方案，该装置2900用于实现上文各个方法实施例中由第四网络设备执行的操作。
例如，处理器2910用于执行存储器2920存储的计算机程序或指令，以实现上文各个方法实施例中第四网络设备的相关操作。例如，图5或图7所示实施例中的第四网络设备执行的方法，又如，图8或图9所示实施例中的第四网络设备执行的方法。
作为又一种方案，该装置2900用于实现上文各个方法实施例中由第五网络设备执行的操作。
例如，处理器2910用于执行存储器2920存储的计算机程序或指令，以实现上文各个方法实施例中第五网络设备的相关操作。例如，图10、图11、图12或图13所示实施例中的第五网络设备执行的方法。
作为又一种方案，该装置2900用于实现上文各个方法实施例中由第一设备执行的操作。
例如，处理器2910用于执行存储器2920存储的计算机程序或指令，以实现上文各个方法实施例中第一设备的相关操作。例如，图10、图11、图12或图13所示实施例中的第一设备执行的方法。
当上述通信装置为应用于终端的芯片时，该终端芯片实现上述方法实施例中终端的功能。该终端芯片从终端中的其它模块(如射频模块或天线)接收信息，该信息是基站发送给终端的；或者，该终端芯片向终端中的其它模块(如射频模块或天线)发送信息，该信息是终端发送给基站的。
应理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，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)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
图16是本申请实施例提供的芯片系统3000的示意图。该芯片系统3000(或者也可以称为处理系统)包括逻辑电路3010以及输入/输出接口(input/output interface)3020。
其中，逻辑电路3010可以为芯片系统3000中的处理电路。逻辑电路3010可以耦合连接存储单元，调用存储单元中的指令，使得芯片系统3000可以实现本申请各实施例的方法和功能。输入/输出接口3020，可以为芯片系统3000中的输入输出电路，将芯片系统3000处理好的信息输出，或将待处理的数据或信令信息输入芯片系统3000进行处理。
作为一种方案，该芯片系统3000用于实现上文各个方法实施例中由终端设备执行的操作。
例如，逻辑电路3010用于实现上文方法实施例中由终端设备执行的处理相关的操作，如，图5、图7、图8、图9、图10、图11、图12或图13所示实施例中的终端设备执行的处理相关的操作；输入 /输出接口3020用于实现上文方法实施例中由终端设备执行的发送和/或接收相关的操作，如，图5、图7、图8、图9、图10、图11、图12或图13所示实施例中的终端设备执行的发送和/或接收相关的操作。
作为另一种方案，该芯片系统3000用于实现上文各个方法实施例中由第三网络设备执行的操作。
例如，逻辑电路3010用于实现上文方法实施例中由第三网络设备执行的处理相关的操作，如，图5、图7、图8或图9所示实施例中的第三网络设备执行的处理相关的操作；输入/输出接口3020用于实现上文方法实施例中由第三网络设备执行的发送和/或接收相关的操作，如，图5、图7、图8或图9所示实施例中的第三网络设备执行的发送和/或接收相关的操作。
作为另一种方案，该芯片系统3000用于实现上文各个方法实施例中由第四网络设备执行的操作。
例如，逻辑电路3010用于实现上文方法实施例中由第四网络设备执行的处理相关的操作，如，图5、图7、图8或图9所示实施例中的第四网络设备执行的处理相关的操作；输入/输出接口3020用于实现上文方法实施例中由第四网络设备执行的发送和/或接收相关的操作，如，图5、图7、图8或图9所示实施例中的第四网络设备执行的发送和/或接收相关的操作。
作为另一种方案，该芯片系统3000用于实现上文各个方法实施例中由第五网络设备执行的操作。
例如，逻辑电路3010用于实现上文方法实施例中由第五网络设备执行的处理相关的操作，如，图10、图11、图12或图13所示实施例中的第五网络设备执行的处理相关的操作；输入/输出接口3020用于实现上文方法实施例中由第五网络设备执行的发送和/或接收相关的操作，如，图10、图11、图12或图13所示实施例中的第五网络设备执行的发送和/或接收相关的操作。
作为另一种方案，该芯片系统3000用于实现上文各个方法实施例中由第一设备执行的操作。
例如，逻辑电路3010用于实现上文方法实施例中由第一设备执行的处理相关的操作，如，图10、图11、图12或图13所示实施例中的第一设备执行的处理相关的操作；输入/输出接口3020用于实现上文方法实施例中由第一设备执行的发送和/或接收相关的操作，如，图10、图11、图12或图13所示实施例中的第一设备执行的发送和/或接收相关的操作。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由终端设备、第三网络设备、第四网络设备、第五网络设备或第一设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法各实施例中由终端设备、第三网络设备、第四网络设备、第五网络设备或第一设备执行的方法。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由终端设备、第三网络设备、第四网络设备、第五网络设备或第一设备执行的方法。
本申请实施例还提供一种通信系统，该通信系统包括上文各实施例中的第三网络设备和第四网络设备。例如，该系统包含图5或图7所示实施例中的第三网络设备和第四网络设备，又如，该系统包含图8或图9所示实施例中的第三网络设备和第四网络设备。
本申请实施例还提供一种通信系统，该通信系统包括上文各实施例中的第五网络设备和第一设备。例如，该系统包含图10、图11、图12或图13所示实施例中的第五网络设备和第一设备。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指 令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (61)

  1. 一种通信方法，其特征在于，包括：
    接收来自第一网络设备的第一信息，所述第一信息包括至少一个组播配置信息和所述至少一个组播配置信息对应的索引信息，所述至少一个组播配置信息包括第一组播配置信息，所述至少一个组播配置信息对应的索引信息包括第一索引信息；
    接收来自第二网络设备的第二信息，所述第二信息用于指示第一组播会话关联第一索引信息，所述第一索引信息指示第一组播配置信息；
    根据所述第一组播配置信息在无线资源控制RRC非激活态或空闲态接收来自所述第二网络设备的所述第一组播会话。
  2. 根据权利要求1所述的方法，其特征在于，所述第一信息还包括所述至少一个组播配置信息对应的小区或网络设备的标识信息。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    获取第一标识，所述第一标识为终端设备的驻留小区的标识或所述驻留小区对应的网络设备的标识，所述第一标识与所述第一组播配置信息之间具有对应关系；
    根据所述第一标识和所述第一索引信息确定所述第一组播配置信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自于所述第一网络设备的第三信息，所述第三信息用于指示所述至少一个组播配置信息的生效区域。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自于所述第一网络设备或所述第二网络设备的第四信息，所述第四信息用于指示所述第一组播会话对应的第一G-RNTI；
    根据所述第一G-RNTI解扰所述第一组播会话。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述第一索引信息包括以下一项或多项：
    组播无线承载MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、公共频域资源CFR配置索引、半持续调度(semi-persistent scheduling，SPS)配置索引。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，若满足以下任一种条件，则接收所述第二信息：
    重选至所述第二网络设备管理的小区；或，
    接收到来自第五信息，其中，
    所述第五信息用于通知系统消息变更；或，
    所述第五信息用于通知组播控制信道消息变更；或，
    所述第五信息用于通知所述第一组播会话激活；
    所述第五信息用于指示终端设备在RRC非激活态或空闲态接收组播会话；
    其中，所述系统变更通知消息或所述通知组播控制信道消息变更用于：
    通知所述第一组播会话的组播配置信息变更为所述第一组播配置信息，或者，通知所述第二网络设备管理的小区开始在非激活态或空闲态提供所述第一组播会话。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述第二网络设备的第一消息，所述第一消息为系统消息或组播控制信道消息，所述第一消息用于指示停止接收所述第一组播会话或者所述第二网络设备管理的小区停止在非激活态提供所述第一组播会话。
  9. 一种通信方法，其特征在于，包括：
    发送第二信息，所述第二信息用于指示第一组播会话关联第一索引信息，所述第一索引信息指示第一组播配置信息；
    根据所述第一组播配置信息发送所述第一组播会话。
  10. 根据权利要求9所述的方法，其特征在于，所述方法还包括：
    向终端设备发送第一信息，所述第一信息包括至少一个组播配置信息和所述至少一个组播配置信息对应的索引信息，所述至少一个组播配置信息包括所述第一组播配置信息，所述至少一个组播配置信息对应的索引信息包括所述第一索引信息。
  11. 根据权利要求10所述的方法，其特征在于，所述第一信息还包括所述至少一个组播配置信息对应的小区或网络设备的标识信息。
  12. 根据权利要求11所述的方法，其特征在于，所述方法还包括：
    发送第一标识，所述第一标识为第三网络设备的标识或所述第二信息对应的小区的标识。
  13. 根据权利要求9至12中任一项所述的方法，其特征在于，所述方法还包括：
    获取所述第一信息。
  14. 根据权利要求13所述的方法，其特征在于，获取所述第一信息，包括：
    接收来自第四网络设备的第六信息，所述第六信息包括M个组播配置信息和所述M个组播配置信息对应的索引信息；
    确定N个组播配置信息和所述N个组播配置信息对应的索引信息；
    其中，所述至少一个组播配置信息包括所述M个组播配置信息和所述N个配置信息，M和N均为正整数。
  15. 根据权利要求13所述的方法，其特征在于，所述第三网络设获取所述第一信息，包括：
    确定N个组播配置信息；
    接收来自第四网络设备的第六信息，所述第六信息包括M个组播配置信息；
    根据所述M个配置信息和所述N个组播配置信息确定所述M个组播配置信息和所述N个组播配置信息对应的索引信息；
    其中，所述至少一个组播配置信息包括所述M个组播配置信息和所述N个配置信息，M和N均为正整数。
  16. 根据权利要求14或15所述的方法，其特征在于，所述第六信息还包括所述M个组播配置信息对应的小区的标识信息。
  17. 根据权利要求14至16中任一项所述的方法，其特征在于，所述方法还包括：
    向第四网络设备发送所述第一信息。
  18. 根据权利要求10至17中任一项所述的方法，其特征在于，所述方法还包括：
    向终端设备发送第三信息，所述第三信息用于指示所述至少一个组播配置信息的生效区域。
  19. 根据权利要求9至18中任一项所述的方法，其特征在于，所述方法还包括：
    向终端设备发送第四信息，所述第四信息用于指示所述第一G-RNTI，所述第一G-RNTI用于加扰所述第一组播会话。
  20. 根据权利要求19所述的方法，其特征在于，所述第四信息为所述第一G-RNTI的信息，所述方法还包括：
    接收来自核心网设备的所述第一G-RNRI；或，
    根据所述第一组播会话的标识确定所述第一G-RNTI。
  21. 根据权利要求9至20中任一项所述的方法，其特征在于，所述第一索引信息包括以下一项或多项：
    组播无线承载MRB配置索引、物理信道配置索引、非连续接收DRX配置索引、邻小区配置索引、公共频域资源CFR配置索引、半持续调度SPS配置索引。
  22. 根据权利要求9至21中任一项所述的方法，其特征在于，所述方法还包括：
    发送第五信息，所述第五信息用于通知系统消息变更或用于通知组播控制信道消息变更，所述第五信息用于终端设备接收所述第二信息。
  23. 根据权利要求22所述的方法，其特征在于，若满足以下任一条件，则向终端设备发送所述第五信息：
    所述第一组播会话的组播配置信息变更为所述第一组播配置信息；或，
    所述第三网络设备管理的小区开始在非激活态或空闲态提供所述第一组播会话。
  24. 根据权利要求9至23中任一项所述的方法，其特征在于，所述方法还包括：
    发送第一消息，所述第一消息为系统消息、组播控制信道消息，所述第一消息用于指示所述第一组播会话处于去激活状态或被释放，或者用于指示所述第二网络设备管理的小区停止在非激活态提供所述第一组播会话。
  25. 一种通信方法，其特征在于，包括：
    向第三网络设备发送第六信息，所述第六信息包括M个组播配置信息和所述M个组播配置信息对应的索引信息；或，所述第六信息包括M个组播配置信息，M为正整数；
    接收来自所述第三网络设备的第一信息，所述第一信息包括至少一个组播配置信息和所述至少一个组播配置信息对应的索引信息，所述至少一个组播配置信息包括所述M个组播配置信息。
  26. 根据权利要求25所述的方法，其特征在于，所述方法还包括：
    发送第七信息，所述第七信息用于指示第一组播会话关联第二索引信息，所述第二索引信息指示第二组播配置信息，所述至少一个组播配置信息包括所述第二组播配置信息，所述至少一个组播配置信息对应的索引信息包括所述第二索引信息；
    根据所述第二组播配置信息发送所述第一组播会话。
  27. 一种通信方法，其特征在于，包括：
    接收来自第五网络设备的第一组播配置信息和第十信息，所述第一组播配置信息用于配置第一组播会话，所述第十信息用于指示所述第一组播配置信息的生效区域；
    在所述生效区域内，根据所述第一组播配置信息在无线资源控制RRC非激活态或空闲态接收所述第一组播会话。
  28. 一种通信方法，其特征在于，包括：
    向第一设备发送第三消息，所述第三消息用于请求第一组播会话的组播配置信息；
    接收来自所述第一设备的第一组播配置信息，所述第一组播配置信息根据所述第三消息和组播配置参数的取值范围确定，所述第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收所述第一组播会话。
  29. 根据权利要求28所述的方法，其特征在于，所述方法还包括：
    向终端设备发送所述第一组播配置信息。
  30. 根据权利要求28或29所述的方法，其特征在于，所述组播配置参数的取值范围包括以下至少一个：
    G-RNTI的取值范围、组播无线承载MRB标识的取值范围、逻辑信道LCH标识的取值范围、物理信道配置参数的取值范围、非连续接收DRX配置参数的取值范围、公共频域资源CFR配置参数的取值范围。
  31. 根据权利要求28至30中任一项所述的方法，其特征在于，所述第三消息包括以下至少一项：
    所述第一组播会话的标识、所述第一组播会话所需的MRB的数目、所述第一组播会话的第一MRB所需的逻辑信道LCH的数目。
  32. 根据权利要求28至31中任一项所述的方法，其特征在于，所述第三消息包括第二小区的标识，所述第二小区为由所述第五网络设备管理的、提供RRC非激活态或空闲态的所述第一组播会话的小区。
  33. 根据权利要求28至32中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述第一设备的第十信息，所述第十信息指示所述第一组播配置信息的生效区域。
  34. 根据权利要求28至33中任一项所述的方法，其特征在于，所述方法还包括：
    向所述第一设备发送第四消息，所述第四消息包括所述组播配置参数的取值范围。
  35. 根据权利要求34所述的方法，其特征在于，所述第四消息还包括第二区域的标识信息，所述第二区域为所述组播配置参数的取值范围的生效区域。
  36. 根据权利要求35所述的方法，其特征在于，所述第二区域内的小区提供至少一个组播会话，所述至少一个组播会话包括所述第一组播会话，所述至少一个组播会话中除所述第一组播会话之外的其他组播会话的组播配置信息和所述第一组播配置信息不同，所述至少一个组播会话中除所述第一组播会话之外的其他组播会话的组播配置信息互不相同。
  37. 根据权利要求34或35所述的方法，其特征在于，所述第二区域为第五网络设备所在的基于无线接入网络的通知区域RNA。
  38. 根据权利要求28至37中任一项所述的方法，其特征在于，所述方法还包括：
    向所述第一设备发送第十一信息，所述第十一信息用于指示第五网络设备管理的第三小区停止在无线资源控制RRC非激活态或空闲态提供所述第一组播会话。
  39. 一种通信方法，其特征在于，包括：
    接收来自第五网络设备的第三消息，所述第三消息用于请求第一组播会话的组播配置信息；
    根据所述第三消息和组播配置参数的取值范围确定第一组播配置信息，所述第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收所述第一组播会话；
    向所述第五网络设备发送所述第一组播配置信息。
  40. 根据权利要求39所述的方法，其特征在于，所述第三消息包括所述第一组播会话的标识，所述组播配置参数的取值范围包括G-RNTI的取值范围，根据所述第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：
    从所述G-RNTI的取值范围中选择一个值作为所述第一组播会话的G-RNTI，所述第一组播配置信息包括所述第一组播会话的G-RNTI。
  41. 根据权利要求39或40所述的方法，其特征在于，所述第三消息包括所述第一组播会话的标识和所述第一组播会话所需的组播无线承载MRB的数目X，所述组播配置参数的取值范围包括MRB标识的取值范围，根据所述第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：
    从所述MRB标识的取值范围中选择X个值作为所述第一组播会话的MRB标识，所述第一组播配置信息包括所述第一组播会话的MRB标识，X为正整数。
  42. 根据权利要求39至41中任一项所述的方法，其特征在于，所述第三消息包括所述第一组播会话的标识和所述第一组播会话的第一MRB所需的逻辑信道LCH的数目Y，所述组播配置参数的取值范围包括LCH标识的取值范围，根据所述第三消息和组播配置参数的取值范围确定第一组播配置信息，包括：
    从所述LCH标识的取值范围中选择Y个值作为所述第一MRB的LCH标识，所述第一组播配置信息包括所述第一MRB的LCH标识，Y为正整数。
  43. 根据权利要求39至42中任一项所述的方法，其特征在于，所述第三消息包括第二小区的标识，所述第二小区为由所述第五网络设备管理的、提供RRC非激活态或空闲态的所述第一组播会话的小区，所述方法还包括：
    根据来自一个或多个所述第五网络设备的所述第三消息确定第十信息，所述第十信息用于指示所述第一组播配置信息的生效区域。
  44. 根据权利要求43所述的方法，其特征在于，所述方法还包括：
    向所述第五网络设备发送所述第十信息。
  45. 根据权利要求39至44中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述第五网络设备的第四消息，所述第四消息包括所述组播配置参数的取值范围。
  46. 根据权利要求45所述的方法，其特征在于，所述第四消息还包括第二区域的标识信息，所述第二区域为所述组播配置参数的取值范围的生效区域。
  47. 根据权利要求46所述的方法，其特征在于，所述第二区域内的小区提供至少一个组播会话，所述至少一个组播会话包括所述第一组播会话，所述方法还包括：
    为所述至少一个组播会话中除所述第一组播会话之外的其他组播会话确定互不相同的组播配置信息，且所述至少一个组播会话中除所述第一组播会话之外的其他组播会话的组播配置信息和所述第一组播配置信息不同。
  48. 根据权利要求46或47所述的方法，其特征在于，所述第二区域为所述第五网络设备所在的基于无线接入网络的通知区域RNA。
  49. 根据权利要求39至48中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述第五网络设备的第十一信息，所述第十一信息用于指示所述第五网络设备管理的第三小区停止在无线资源控制RRC非激活态或空闲态提供所述第一组播会话；
    将所述第三小区从所述第一组播配置信息的生效区域中移除。
  50. 一种通信方法，其特征在于，包括：
    第五网络设备向第一设备发送第三消息，所述第三消息用于请求第一组播会话的组播配置信息；
    所述第一设备根据所述第三消息和组播配置参数的取值范围确定第一组播配置信息，所述第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收所述第一组播会话；
    所述第一设备向所述第五网络设备发送所述第一组播配置信息。
  51. 一种通信装置，其特征在于，包括用于执行如权利要求1至8中任一项所述的方法的单元，或者包括用于执行如权利要求9至24中任一项所述的方法的单元，或者包括用于执行如权利要求25或26所述的方法的单元，或者包括用于执行如权利要求27所述的方法的单元，或者包括用于执行如权利要求28至38中任一项所述的方法的单元，或者包括用于执行如权利要求39至49中任一项所述的方法的单元。
  52. 一种通信装置，其特征在于，包括处理单元和收发单元，其中，
    所述收发单元用于接收来自第一网络设备的第一信息，所述第一信息包括至少一个组播配置信息和所述至少一个组播配置信息对应的索引信息，所述至少一个组播配置信息包括第一组播配置信息，所述至少一个组播配置信息对应的索引信息包括第一索引信息；
    所述收发单元还用于接收来自第二网络设备的第二信息，所述第二信息用于指示第一组播会话关联第一索引信息，所述第一索引信息指示第一组播配置信息；
    所述收发单元还用于根据所述第一组播配置信息在无线资源控制RRC非激活态或空闲态接收来自所述第二网络设备的所述第一组播会话。
  53. 一种通信装置，其特征在于，包括处理单元和收发单元，其中，
    所述收发单元用于发送第二信息，所述第二信息用于指示第一组播会话关联第一索引信息，所述第一索引信息指示第一组播配置信息；
    所述收发单元还用于根据所述第一组播配置信息发送所述第一组播会话。
  54. 一种通信装置，其特征在于，包括处理单元和收发单元，其中，
    所述收发单元用于向第三网络设备发送第六信息，所述第六信息包括M个组播配置信息和所述M个组播配置信息对应的索引信息；或，所述第六信息包括M个组播配置信息，M为正整数；
    所述收发单元还用于接收来自所述第三网络设备的第一信息，所述第一信息包括至少一个组播配置信息和所述至少一个组播配置信息对应的索引信息，所述至少一个组播配置信息包括所述M个组播配置信息。
  55. 一种通信装置，其特征在于，包括处理单元和收发单元，其中，
    所述收发单元用于接收来自第五网络设备的第一组播配置信息和第十信息，所述第一组播配置信息用于配置第一组播会话，所述第十信息用于指示所述第一组播配置信息的生效区域；
    所述收发单元还用于在所述生效区域内，根据所述第一组播配置信息在无线资源控制RRC非激活态或空闲态接收所述第一组播会话。
  56. 一种通信装置，其特征在于，包括处理单元和收发单元，其中，
    所述收发单元用于向第一设备发送第三消息，所述第三消息用于请求第一组播会话的组播配置信息；
    所述收发单元还用于接收来自所述第一设备的第一组播配置信息，所述第一组播配置信息根据所述第三消息和组播配置参数的取值范围确定，所述第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收所述第一组播会话。
  57. 一种通信装置，其特征在于，包括处理单元和收发单元，其中，
    所述收发单元用于接收来自第五网络设备的第三消息，所述第三消息用于请求第一组播会话的组播配置信息；
    所述收发单元还用于根据所述第三消息和组播配置参数的取值范围确定第一组播配置信息，所述第一组播配置信息用于配置终端设备在无线资源控制RRC非激活态或空闲态接收所述第一组播会话；
    所述收发单元还用于向所述第五网络设备发送所述第一组播配置信息。
  58. 一种通信装置，其特征在于，包括：
    处理器，用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至8中任一项所述的方法，或者以使得所述装置执行如权利要求9至24中任一项所述的方法，或者以使得所述装置执行如权利要求25或26所述的方法，或者以使得所述装置执行如权利要求27所述的方法，或者以使得所述装置执行如权利要求28至38中任一项所述的方法，或者以使得所述装置执行如权利要求39至49中任一项所述的方法。
  59. 根据权利要求51所述的装置，其特征在于，所述装置还包括所述存储器和/或通信接口，所述通信接口与所述处理器耦合，
    所述通信接口，用于输入和/或输出信息。
  60. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序，当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至8中任意一项所述的方法，或者以使得所述计算机执行如权利要求9至24中任一项所述的方法，或者以使得所述计算机执行如权利要求25或26所述的方法，或者使得所述计算机执行如权利要求27所述的方法，或者以使得所述计算机执行如权利要求28至38中任一项所述的方法，或者以使得所述计算机执行如权利要求39至49中任一项所述的方法。
  61. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行如权利要求1至8中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求9至24中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求25或26所述的方法的指令，或者所述计算机程序产品包括用于执行如权利要求27所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求28至38中任一项所述的方法的指令，或者，所述计算机程序产品包括用于执行如权利要求39至49中任一项所述的方法的指令。
PCT/CN2023/116145 2022-09-29 2023-08-31 一种通信的方法和装置 WO2024066901A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202211203248.9 2022-09-29
CN202211203248 2022-09-29
CN202211378635.6A CN117835163A (zh) 2022-09-29 2022-11-04 一种通信的方法和装置
CN202211378635.6 2022-11-04

Publications (1)

Publication Number Publication Date
WO2024066901A1 true WO2024066901A1 (zh) 2024-04-04

Family

ID=90476054

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/116145 WO2024066901A1 (zh) 2022-09-29 2023-08-31 一种通信的方法和装置

Country Status (1)

Country Link
WO (1) WO2024066901A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022033505A1 (zh) * 2020-08-13 2022-02-17 展讯通信（上海）有限公司 多播业务的接收及发送方法、装置、存储介质、终端、基站
CN114651453A (zh) * 2020-01-15 2022-06-21 Oppo广东移动通信有限公司 一种业务传输方法及装置、终端设备、网络设备
CN114902758A (zh) * 2019-12-30 2022-08-12 Oppo广东移动通信有限公司 一种资源配置方法及装置、终端设备、网络设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114902758A (zh) * 2019-12-30 2022-08-12 Oppo广东移动通信有限公司 一种资源配置方法及装置、终端设备、网络设备
CN114651453A (zh) * 2020-01-15 2022-06-21 Oppo广东移动通信有限公司 一种业务传输方法及装置、终端设备、网络设备
WO2022033505A1 (zh) * 2020-08-13 2022-02-17 展讯通信（上海）有限公司 多播业务的接收及发送方法、装置、存储介质、终端、基站

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LENOVO, MOTOROLA MOBILITY: "Remaining issues on basic functions for broadcast/multicast in idle/inactive states", 3GPP DRAFT; R1-2202229, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20220221 - 20220303, 14 February 2022 (2022-02-14), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP052110081 *

Similar Documents

Publication Publication Date Title
US20230300938A1 (en) Methods and systems for managing mbs service continuity for a ue
WO2017118199A1 (zh) 一种数据调度方法、基站及系统
KR20160037118A (ko) 무선 통신 시스템에서 방송 자원 혼잡 제어 방법 및 장치
US9820133B2 (en) Method and user equipment for performing D2D service in wireless communication system
US20170325076A1 (en) Base station, user terminal and apparatus
TWI681684B (zh) 使用者裝置及基地台
JP7305693B2 (ja) 情報伝送方法及び装置
CN105307220A (zh) D2d业务的切换实现方法及装置
CN108029051B (zh) 通过支持公共安全服务的终端重选空闲模式小区的方法和装置
WO2021056596A1 (zh) 一种寻呼方法及装置
US20230131538A1 (en) Communication system, communication terminal, and base station
US20230262531A1 (en) Apparatus and method of wireless communication for mbs
CN112866982B (zh) 一种寻呼方法及装置
CN105635988A (zh) Idle态ue迟后进入组呼的方法和实现系统
US11057746B2 (en) Method, device and system for transmitting broadcasting services, and computer storage medium
US20230362959A1 (en) Method and system for managing configuration and control information of mbs services in wireless network
CN114731645A (zh) 在带宽部分上进行通信的方法
WO2024066901A1 (zh) 一种通信的方法和装置
CN105554708A (zh) Idle态ue迟后进入组呼的方法、装置和系统
US20220264697A1 (en) Communication system, communication terminal, and network
WO2024066858A1 (zh) 一种通信的方法和装置
CN117835163A (zh) 一种通信的方法和装置
CN105554903A (zh) 一种idle态ue迟后进入组呼的方法
US20230189299A1 (en) Communication control method
WO2024048772A1 (ja) 通信方法及びユーザ装置