WO2024051517A1 - 一种通信方法及相关装置 - Google Patents

一种通信方法及相关装置 Download PDF

Info

Publication number
WO2024051517A1
WO2024051517A1 PCT/CN2023/115371 CN2023115371W WO2024051517A1 WO 2024051517 A1 WO2024051517 A1 WO 2024051517A1 CN 2023115371 W CN2023115371 W CN 2023115371W WO 2024051517 A1 WO2024051517 A1 WO 2024051517A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
network device
terminal device
sdt
data
Prior art date
Application number
PCT/CN2023/115371
Other languages
English (en)
French (fr)
Inventor
沙桐
李秉肇
张海森
常俊仁
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024051517A1 publication Critical patent/WO2024051517A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states

Definitions

  • the present application relates to the field of communication technology, and in particular, to a communication method and related devices.
  • the terminal equipment When the terminal equipment (user equipment, UE) is in the radio resource control (RRC) inactive state, for small and infrequent data transmission, it can remain in the RRC inactive state for small data transmission (small data transmission, SDT) without switching to the RRC connection state for transmission, thereby reducing the power consumption and signaling overhead caused by RRC state transition due to small data transmission requirements, and achieving the purpose of reducing UE power consumption.
  • RRC radio resource control
  • the SDT and SDT scheduled by the network equipment corresponding to the serving cell will be The data transmission of broadcast multicast services may exceed the receiving capabilities of terminal devices, causing packet loss or bit errors, affecting service quality.
  • Embodiments of the present application provide a communication method and related devices.
  • the network device corresponding to the serving cell can learn the multicast broadcast service that the terminal device is interested in receiving or is receiving. Information for reasonable scheduling and data transmission, so that terminal devices can receive data from SDT and multicast broadcast services.
  • embodiments of the present application provide a communication method, which method includes:
  • the terminal device performs small data transmission SDT with the first network device, and the terminal device is interested in receiving or is receiving the first broadcast service from the first network device, and the SDT is in the Radio Resource Control RRC inactive state.
  • the first network device is the network device corresponding to the cell where the terminal device resides;
  • the terminal device sends first information to the first network device, the first information includes information about the first broadcast service, and the first information is used by the first network device to provide the terminal device with The first broadcast service.
  • the first broadcast service may be one or more broadcast services.
  • the information of the first broadcast service is the information of one or more of the above broadcast services.
  • the first multicast session (MBS Session) can be one or more multicast sessions, and a multicast session can also be understood as a multicast service/multicast business.
  • a communication method is provided.
  • a terminal device in an RRC inactive state performs SDT with a first network device, and the terminal device is interested in receiving or is receiving the first broadcast service from the first network device.
  • the terminal sends first information to the first network device.
  • the first information includes information about the first broadcast service.
  • the first information may be multicast broadcast service (MBS) interest indication information (MBS Interest Indication, MII). ), used to indicate information about the MBS broadcast service that the terminal device is interested in receiving or is receiving, such as the frequency of the MBS broadcast service, the identification information of the MBS broadcast service, and the priority information of MBS broadcast compared with unicast and MBS multicast reception. wait.
  • MBS multicast broadcast service
  • MII multicast broadcast service
  • the broadcast service that the terminal device is interested in receiving in this application may also refer to the broadcast service that the terminal device has not received but is to be received.
  • the terminal device in a scenario where the terminal device is in the RRC inactive state and performs SDT with the first network device, and the terminal device receives the first broadcast service from the first network device, it can report the third broadcast service to the first network device.
  • data from SDT and broadcast services can also be received to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • the broadcast service may refer to MBS (multicast broadcast service, MBS) broadcast service (broadcast service)
  • MBS multicast service multicast service
  • SDT includes data and/or signaling of downlink/uplink SDT.
  • the method further includes:
  • the terminal device receives data of the SDT and the first broadcast service from the first network device on different time slots.
  • the SDT can be understood as downlink SDT data (DownLink SDT data).
  • the receiving data of the SDT and the first broadcast service on different time slots may be understood/replaced as receiving a physical downlink shared channel (physical downlink shared channel) for transmitting the SDT data on different time slots.
  • PDSCH physical downlink shared channel
  • group PDSCH group PDSCH used to transmit data of the first broadcast service.
  • the first network device schedules the SDT and the first broadcast service through inter-slot time division multiplexing (inter-slot TDM).
  • Broadcast service such as sending SDT data to the terminal device in time slot 1, and sending data of the first broadcast service to the terminal device in time slot 2, so that the terminal device can receive data from the first network device in different time slots.
  • the first network device (That is, the network equipment corresponding to the serving cell, which can also be called the receiving gNB of SDT, can learn the information of the first broadcast service received by the terminal equipment, thereby scheduling the data of SDT and the first broadcast service on different time slots, so that the terminal equipment can It does not have the ability to receive unicast data and broadcast data on the same time slot, and can also receive data from the SDT and the first broadcast service sent by the first network device on different time slots.
  • the first network device That is, the network equipment corresponding to the serving cell, which can also be called the receiving gNB of SDT, can learn the information of the first broadcast service received by the terminal equipment, thereby scheduling the data of SDT and the first broadcast service on different time slots, so that the terminal equipment can It does not have the ability to receive unicast data and broadcast data on the same time slot, and can also receive data from the SDT and the first broadcast service sent by the first network device on different time slots.
  • the terminal device sends the first information to the first network device, which can indicate that the terminal device supports receiving the MBS broadcast service, and the terminal device must select one that supports PDSCH for transmitting unicast data and PDSCH/GC-PDSCH for transmitting MBS broadcast data.
  • Inter-slot time division multiplexing (inter-slot TDM) reception, therefore the first network device sends SDT and the data of the first broadcast service according to inter-slot time division multiplexing, which can ensure that the terminal device can receive the first broadcast service data during the SDT process.
  • broadcast services to avoid bit errors and/or packet loss, thereby ensuring the service quality of SDT and MBS broadcast services.
  • the first network device When the terminal device does not support receiving unicast data and MBS broadcast data in the same time slot, in the SDT scenario without context relocation, the first network device does not have UE capability information. If the first network device does not know that the terminal device is receiving First broadcast service, when the first network device sends SDT data (SDT can be understood as a unicast transmission method) and data of the first broadcast service in the same time slot, it will cause the terminal device to be unable to receive SDT and broadcast data, or the terminal device can only receive one of SDT or broadcast data, causing data errors and/or packet loss, affecting service reception quality. Therefore, through the solution of this application, the above problems can be avoided.
  • SDT data SDT can be understood as a unicast transmission method
  • the method before the terminal device sends the first information to the first network device, the method further includes:
  • the terminal device receives the second information sent by the first network device and/or the third information sent by the second network device, and the second network device is the network device that sends the RRC release message to the terminal device;
  • the terminal device sends first information to the first network device, including:
  • the terminal device sends the first information to the first network device according to the second information and/or the third information.
  • the terminal device before the terminal device sends the first information to the first network device, the terminal device also receives the third message sent by the first network device. the second information and/or the third information sent by the second network device, and based on the second information and/or the third information, it is determined to send the first information to the first network device, where the first information includes the first broadcast service Information, the first information may specifically be MII, which is used to indicate the information of the MBS broadcast service that the terminal device is interested in receiving or is receiving, such as the frequency of the MBS broadcast service, the identification information of the MBS broadcast service, MBS broadcast and unicast and MBS multicast reception priority information, etc.
  • MII MII
  • the terminal device in the scenario where the terminal device is in the RRC inactive state and performs SDT with the first network device, and the terminal device receives the first broadcast service from the first network device, it can perform the SDT according to the first broadcast service sent by the first network device.
  • Determine the reporting of the first information it can also be understood that the first network device controls whether to allow the terminal device to report the first information by sending the second information and/or the second network device by sending the third information.
  • the second information and the third information may be the same information or different information.
  • the information of the first broadcast service includes temporary mobility group identity TMGI information; before the terminal device sends the first information to the first network device, the method further includes:
  • the terminal device receives the fourth information sent by the first network device and/or the fifth information sent by the second network device;
  • the terminal device sends first information to the first network device, including:
  • the terminal device sends the first information to the first network device according to the fourth information and/or the fifth information, where the first information includes TMGI information of the first broadcast service.
  • a possible specific implementation manner of sending the first information is provided. Specifically, before the terminal device sends the first information to the first network device, the terminal device also receives the third message sent by the first network device. The fourth information and/or the fifth information sent by the second network device, and based on the fourth information and/or the fifth information, it is determined to send the first information to the first network device, where the first information includes the first broadcast service Temporary mobile group identity (TMGI) information.
  • TMGI Temporary mobile group identity
  • the fifth information sent by the second network device is used to determine that the first information sent includes the TMGI information of the first broadcast service, Or it is determined based on the fourth information sent by the first network device and the fifth information sent by the second network device that the first information sent contains the TMGI information of the first broadcast service.
  • the fourth information and the fifth information may be the same information or different information.
  • the third information and/or the fifth information are carried in an RRC release message; the method further includes:
  • the terminal device enters the RRC inactive state according to the RRC release message.
  • the third information and/or the fifth information can be carried in the RRC release message, for example,
  • the third information and/or the fifth information can be an indication bit (such as 1 bit) in the RRC release message.
  • the third information and the fifth information can be different information, indicated by two independent bits, or they can The same information is indicated by the same bit.
  • the RRC release message contains the third information, or the bit position corresponding to the third information is 1, indicating that the terminal device is allowed to report the first information.
  • the second network device supports receiving the first information reported from the terminal device in the RRC inactive state, or the first information reported from the terminal device during the SDT process; for example, in the RRC release message If the third information is not included, or the bit position corresponding to the third information is 0, it indicates that the terminal device is not allowed to report/the second network device does not support receiving the first information (specifically, it may be MII), or it indicates that it is not allowed/no Support the terminal equipment receiving the RRC inactive state to report the first information, or indicate that the receiving terminal equipment is not allowed/not supported to report the first information during the SDT process.
  • the setting and meaning of the fifth information refer to the above-mentioned third information.
  • the RRC release message contains the fifth information or the bit position corresponding to the fifth information is 1, it indicates that the first information reported by the terminal device is allowed.
  • the first information that contains the TMGI information of the broadcast service/the second network device supports receiving the report reported by the terminal device contains the TMGI information of the broadcast service, or the first information reported by the terminal device indicating that it is allowed/supported to receive RRC inactive state contains The TMGI information of the broadcast service, or the first information reported by the receiving terminal device during the SDT process indicating that the receiving terminal device is allowed/supported, contains the TMGI information of the broadcast service.
  • the fifth information and the third information are the same information, or when the fifth information and the third information are the same indication bit/bit, for example, when the RRC release message contains the information, or The bit/indicator position is 1, indicating that the terminal device is allowed to report/the second network device supports receiving the first information (specifically, it can be MII), and the first information can include the TMGI information of the broadcast service; the RRC When the release message does not contain this information, or the bit/indicator position is 0, it indicates that the terminal device is not allowed to report the first information.
  • the third information/fifth information please refer to the above description of the third information/fifth information and will not be repeated here.
  • the second network device can control the reporting of the first information by the terminal device through the third information and/or the fifth information, and has better backward compatibility.
  • the RRC release message may not contain all the first information. If the third information and/or the fifth information are provided, the terminal device will not report the first information; for the upgraded terminal device that can support RRC inactive state, the first information will be reported/the terminal device will report the third information during the SDT process.
  • a network device with information may include the third information and/or the fifth information in the RRC release message.
  • the second information, and/or the third information, and/or the fourth information, and/or the fifth information include system information.
  • the second information, and/or the third information, and/or the fourth information, and/or the fifth information may include system information (System Information, SI); or the second information, and/or the third information, and/or the fourth information , and/or the fifth information may be transmitted in the form of a System Information Block (SIB).
  • SI System Information
  • SIB System Information Block
  • the second information and/or the third information includes first system information, which is used to indicate a mapping relationship between multicast broadcast services and frequencies, or to Indicates the configuration parameters of the multicast broadcast service control channel MCCH.
  • the second information and/or the third information may include the first system information; or, the second The information and/or the third information may be transmitted in the form of a first system information block.
  • the first system information is used to indicate the mapping relationship between the multicast broadcast service and frequency, for example, it may correspond to the system information block SIB21; or, the first system information is used to indicate the multicast broadcast service control channel (MBS control channel, MCCH ) configuration parameters, for example, may correspond to system information block SIB20.
  • the fourth information and/or the fifth information includes second system information
  • the second system information is used to indicate the mapping relationship between multicast broadcast services and frequencies, or is used to Indicates the configuration parameters of the multicast broadcast service control channel MCCH.
  • the fourth information and/or the fifth information may include second system information; or, the fourth The information and/or the fifth information may be transmitted in the form of a second system information block.
  • the second system information is used to indicate the mapping relationship between the multicast broadcast service and frequency, for example, it may correspond to the system information block SIB21; or the second system information is used to indicate the multicast broadcast service control channel (MBS control channel, MCCH ) configuration parameters, for example, may correspond to system information block SIB20.
  • MMS control channel, MCCH multicast broadcast service control channel
  • embodiments of the present application provide a communication method, which method includes:
  • the first network device receives the first information sent by the terminal device.
  • the first information includes information about the first broadcast service that the terminal device is interested in receiving or is receiving.
  • the first network device is camped for the terminal device.
  • the network equipment corresponding to the community;
  • the first network device performs small data transmission SDT with the terminal device, and the first network device provides the first broadcast service to the terminal device, and the SDT is in a radio resource control (RRC) inactive state. transmission of data and/or signaling.
  • RRC radio resource control
  • a communication method receives the first information sent by the terminal device.
  • the first information includes the information of the first broadcast service that the terminal device is interested in receiving or is receiving.
  • the information may specifically be multicast broadcast service (MBS) interest indication information (MBS Interest Indication, MII), which is used to indicate information about the MBS broadcast service that the terminal device is interested in receiving or is receiving, such as MBS broadcast service information. frequency, identification information of MBS broadcast service, priority information of MBS broadcast compared with unicast and MBS multicast reception, etc., the first network device uses this first information when performing SDT with the terminal device in the RRC inactive state.
  • a first broadcast service is provided to the terminal device.
  • the broadcast service that the terminal device is interested in receiving in this application may also refer to the broadcast service that the terminal device has not received but is to be received.
  • the first network device performs SDT with the terminal device in the RRC inactive state, and the first network device provides the first broadcast service for the terminal device in the RRC inactive state
  • the first network device It can be known from the first information reported by the terminal device that the terminal device is still receiving the first broadcast service while performing SDT, so that the first network device can appropriately schedule the SDT and the first broadcast service so that the terminal device can
  • data from SDT and broadcast services can also be received to avoid bit errors and/or packet loss caused by scheduling exceeding the receiving capabilities of the terminal device.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • the method further includes:
  • the first network device sends the SDT and the data of the first broadcast service to the terminal device on different time slots.
  • the SDT can be understood as downlink SDT data (DL SDT data).
  • the sending of the SDT and the data of the first broadcast service on different time slots can be understood/replaced as sending the PDSCH of the SDT and the PDSCH/GC- of the first broadcast service on different time slots.
  • PDSCH or understood as transmitting the PDSCH of the SDT and the PDSCH/GC-PDSCH of the first broadcast service in an inter-slot time division multiplexing (inter-slot TDM) manner.
  • the first network device schedules the SDT and the first broadcast service through inter-slot time division multiplexing (inter-slot TDM).
  • Broadcast service such as sending SDT data to the terminal device in time slot 1, and sending data of the first broadcast service to the terminal device in time slot 2, so that the terminal device can receive data from the first network device in different time slots.
  • the first network device that is, the network equipment corresponding to the serving cell, which can also be called the receiving gNB of SDT, can learn the information of the first broadcast service received by the terminal equipment, so that the terminal can schedule the data of SDT and the first broadcast service on different time slots. Even if the device does not have the ability to receive unicast data and broadcast data on the same time slot, it can still receive data from the SDT and the first broadcast service sent by the first network device on different time slots.
  • the terminal device sends the first information to the first network device, which can indicate that the terminal device supports receiving the MBS broadcast service, and the terminal device must select one that supports PDSCH for transmitting unicast data and PDSCH/GC-PDSCH for transmitting MBS broadcast data.
  • Inter-slot time division multiplexing (inter-slot TDM) reception, therefore the first network device sends SDT and the data of the first broadcast service according to inter-slot time division multiplexing, which can ensure that the terminal device can receive the first broadcast service data during the SDT process.
  • broadcast services to avoid bit errors and/or packet loss, thereby ensuring the service quality of SDT and MBS broadcast services.
  • the first network device When the terminal device does not support receiving unicast data and MBS broadcast data in the same time slot, in the SDT scenario without context relocation, the first network device does not have UE capability information. If the first network device does not know that the terminal device is receiving First broadcast service, when the first network device schedules/sends SDT data (SDT can be understood as a unicast transmission method) and the data of the first broadcast service in the same time slot, it will cause the terminal device to be unable to receive SDT and broadcast data, or the terminal device can only receive one of SDT or broadcast data, causing data errors and/or packet loss, affecting service reception quality. Therefore, through the solution of this application, the above problems can be avoided.
  • SDT can be understood as a unicast transmission method
  • the method further includes:
  • the first network device sends the first information to a second network device that connects the terminal device and the core Network equipment of network equipment;
  • the first network device receives sixth information from the second network device, the sixth information is used to indicate the first broadcast service, and the sixth information is determined by the first information.
  • the first network device sends the first information to the second network device and receives the information from the second network device.
  • the sixth information of the network device wherein the second network device is a network device connecting the terminal device and the core network device, the sixth information is determined by the second network device based on the first information, and the sixth information is used to indicate the first broadcast service.
  • the first information may be an RRC message.
  • the first network device After the first network device receives the first information sent by the terminal device, since the first network device does not have complete context information of the terminal device, for example, the first network device only Having the RLC context of the terminal device, but not having the PDCP and RRC related information (such as PDCP context) of the terminal device, and therefore unable to interpret the first information, the first network device transmits the first information (specifically, it may be a bearer of the first
  • the information RLC packet such as RLC SDU or PDCP PDU
  • the second network device has complete context information of the terminal device.
  • the second network device has the PDCP and RRC related information of the terminal device ( For example, PDCP context), so the second network device can interpret the first information forwarded by the first network device based on the complete context information of the terminal device (for example, receiving an RLC data packet carrying the first information forwarded by the first network device, passing through the PDCP layer Obtain the PDCP SDU after processing, interpret the PDCP SDU at the RRC layer to obtain the content of the first information), obtain the sixth information, and send it to the first network device, the sixth information is obtained based on the first information, so The sixth information and the first information may be the same information.
  • the sixth information is the first information sent by the second network device to the first network device through an interface between network devices (for example, the Xn interface);
  • the sixth information and the first information may also be different information.
  • the sixth information includes part or all of the first information and is determined/generated by the second network device through an interface between network devices (for example, Xn interface) is sent to the first network device.
  • the first information includes TMGI information of the first broadcast service, where the TMGI information may include associated public land mobile network (PLMN) information, such as PLMN-index or PLMN -Identity (PLMN identity can also be referred to as PLMN ID).
  • PLMN information is PLMN-index
  • the second network device translates or converts the PLMN-index in the first information into PLMN-identity and sends it to the first network device through the sixth information, that is, The sixth information sent by the second network device is generated by replacing the PLMN-index in the first information with PLMN-identity.
  • the PLMNs of the first network device and the second network device are different at the same time, or that the order of the PLMNs in the PLMN list (for example, plmn-IdentityInfoList) indicated in SIB1 is different between the cell of the first network device and the cell of the second network device.
  • this causes a problem of misalignment in the understanding of PLMN-index by the first network device and the second network device (for example, the same plmn-index corresponds to different PLMNs in the first network device and the second network device).
  • the method further includes:
  • the first network device sends a first request message to the second network device, where the first request message is used to request acquisition of context information of the terminal device for SDT;
  • the first network device receives partial context information of the terminal device sent by the second network device, and the partial context information includes seventh information, and the seventh information is used to indicate the third information received by the terminal device. 2. Broadcasting services.
  • the first network device sends a first request message to the second network device and receives the second network device.
  • the device sends part of the context information of the terminal device in response to the first request message, where the first request message is used to request to obtain the context information of the terminal device for SDT, and the second network device sends the terminal device in response to the first request message.
  • Part of the context information includes seventh information, the seventh information is used to indicate the second broadcast service received by the terminal device.
  • the first network device in the scenario where the first network device performs SDT with the terminal device in the RRC inactive state, and the first network device provides the second broadcast service for the terminal device in the RRC inactive state, the first network device By sending the first request message to the second network device and receiving the seventh information in the partial context information of the terminal device provided by the second network device, it can be learned that the terminal device may also be interested in receiving or is in the process of performing SDT. Receive the second broadcast service, so that the first network device can properly schedule the SDT and the second broadcast service, so that the terminal device can also receive the SDT and the second broadcast service in a small data transmission scenario without UE context relocation. data to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • the method further includes:
  • the first network device When receiving the sixth information, the first network device ignores the seventh information.
  • the first network device performs corresponding broadcast service scheduling according to the sixth information or the seventh information. Specifically, the first network device performs broadcast service scheduling after receiving the sixth information. In this case, ignoring the seventh information, it can be understood that when the first network device receives the sixth information, regardless of whether the first network device receives the seventh information, the first network device will respond to the SDT based on the sixth information. and the corresponding first broadcast service for scheduling.
  • the broadcast service indicated in the sixth information When the first network device receives the broadcast service indicated in the seventh information and When the broadcast service indicated in the sixth information is different, the broadcast service indicated in the sixth information shall prevail.
  • the seventh information indicates that the terminal device receives broadcast service 1, broadcast service 2, and broadcast service 3.
  • the sixth information indicates that the terminal device receives broadcast service 2 and broadcast service 4, then the first network device considers that the broadcast services that the terminal device is interested in receiving or is receiving are broadcast service 2 and broadcast service 4, and the terminal device is not receiving broadcast service 1 and broadcast service 3.
  • the first network device will schedule the SDT and the corresponding second broadcast service according to the seventh information, so that the terminal device can In small data transmission scenarios without UE context relocation, data from SDT and the second broadcast service can also be received to avoid bit errors and/or packet loss caused by scheduling exceeding the receiving capabilities of the terminal device.
  • the method further includes:
  • the first network device receives eighth information from the second network device.
  • the eighth information is used to indicate whether the terminal device supports M unicast data and N broadcast data at the same time. Frequency division multiplexing FDM reception within the slot, the M and the N are integers greater than or equal to 1; and/or,
  • the first network device receives ninth information from the second network device.
  • the ninth information is used to indicate whether the terminal device supports P unicast data and Q broadcast data at the same time.
  • the P and the Q are integers greater than or equal to 1.
  • the eighth information is also used to indicate that the terminal device supports or does not support M unicast data and N broadcast data in the same time slot on the first frequency band (band) or the carrier of the first frequency band.
  • Frequency division multiplexing FDM reception within, the M and N are integers greater than or equal to 1; the eighth information includes the identifier of the first frequency band;
  • the ninth information is also used to indicate that the terminal device supports or does not support P unicast data and Q broadcast data in the same time slot on the second frequency band or the carrier of the second frequency band.
  • the P and the Q are integers greater than or equal to 1; the ninth information includes the identifier of the second frequency band; the first frequency band and the second frequency band may be the same frequency band , can also be different frequency bands.
  • the unicast data can be understood as/replaced as PDSCH used to transmit unicast data, or the cell's wireless network temporary identifier (Cell Radio Network Temporary Identifier, cell RNTI) scrambled PDSCH;
  • the broadcast data can be understood as/replaced as PDSCH/GC-PDSCH used to transmit MBS broadcast data, or PDSCH scrambled by Group Radio Network Temporary Identifier (G-RNTI).
  • G-RNTI Group Radio Network Temporary Identifier
  • the time division multiplexing/frequency division multiplexing of unicast data and broadcast data in the same time slot can be understood as the time division multiplexing/frequency division multiplexing of unicast PDSCH and MBS broadcast GC-PDSCH in the same time slot (intra-slot). Time division multiplexing/frequency division multiplexing.
  • the first network device receives the eighth information and/or the ninth information from the second network device.
  • Nine information the first network device can perform SDT according to The eighth information and/or the ninth information is to learn that the terminal device supports or does not support frequency division multiplexing TDM reception or time division multiplexing TDM of one or more unicast data and one or more broadcast data in the same time slot.
  • the terminal device can also receive data of SDT and broadcast services in a small data transmission scenario without UE context relocation, and avoid scheduling beyond the terminal device. bit errors and/or packet loss caused by poor reception capabilities.
  • embodiments of the present application provide a communication method, which method includes:
  • the second network device sends small data transmission SDT and sixth information to the first network device.
  • the sixth information is used to indicate the first broadcast service.
  • the first broadcast service is a broadcast service that the terminal device is interested in receiving or is receiving.
  • the second network device is a network device that connects the terminal device and the core network device
  • the first network device is a network device corresponding to the community where the terminal device resides
  • the SDT is the network device where the terminal device resides.
  • the radio resource controls the transmission of RRC inactive data and/or signaling, and the SDT is sent to the terminal device through the first network device.
  • the second network device sends SDT and sixth information to the first network device, where the sixth information is used to indicate The first broadcast service that the terminal device is interested in receiving or is receiving, the SDT and the first broadcast service indicated by the sixth information are sent by the first network device to the terminal device.
  • the broadcast service that the terminal device is interested in receiving in this application may also refer to the broadcast service that the terminal device has not received but is to be received.
  • the second network device By sending the sixth information to the first network device, the first network device can learn that the terminal device is still receiving the first broadcast service during SDT, so that the first network device can perform appropriate processing on SDT and the first broadcast service.
  • Scheduling enables terminal devices to receive SDT and broadcast service data in small data transmission scenarios without UE context relocation, avoiding bit errors and/or packet loss caused by scheduling exceeding the terminal device's receiving capabilities.
  • the first network device is the end device that resides in the RRC inactive state.
  • the network equipment corresponding to the serving cell can also be the receiving gNB that performs SDT with the terminal equipment.
  • the method further includes:
  • the second network device receives the first information sent by the first network device, where the first information includes information about the first broadcast service;
  • the second network device determines the sixth information based on the first information.
  • the first network device sends the first information to the second network device, and the first information includes the information of the first broadcast service.
  • the second network device determines sixth information according to the first information, and the sixth information is used to indicate the first broadcast service.
  • the first information may be an RRC message.
  • the first network device After the first network device receives the first information sent by the terminal device, since the first network device does not have complete context information of the terminal device, for example, the first network device only Having the RLC context of the terminal device, but not having the PDCP and RRC related information (such as PDCP context) of the terminal device, and therefore unable to interpret the first information, the first network device transmits the first information (specifically, it may be a bearer of the first
  • the information RLC packet such as RLC SDU or PDCP PDU
  • the second network device has complete context information of the terminal device.
  • the second network device has the PDCP and RRC related information of the terminal device ( For example, PDCP context), so the second network device can interpret the first information forwarded by the first network device based on the complete context information of the terminal device (for example, receiving an RLC data packet carrying the first information forwarded by the first network device, passing through the PDCP layer Obtain the PDCP SDU after processing, interpret the PDCP SDU at the RRC layer to obtain the content of the first information), obtain the sixth information, and send it to the first network device, the sixth information is obtained based on the first information, so The sixth information and the first information may be the same information.
  • the sixth information is the first information sent by the second network device to the first network device through an interface between network devices (for example, the Xn interface);
  • the sixth information and the first information may also be different information.
  • the sixth information includes part or all of the first information and is determined/generated by the second network device through an interface between network devices (for example, Xn interface) is sent to the first network device.
  • the first information includes TMGI information of the first broadcast service, where the TMGI information may include associated public land mobile network (PLMN) information, such as PLMN-index or PLMN -Identity (PLMN identity can also be referred to as PLMN ID).
  • PLMN information is PLMN-index
  • the second network device translates or converts the PLMN-index in the first information into PLMN-identity and then sends it to the first network device through the sixth information, that is, The sixth information sent by the second network device is generated by replacing the PLMN-index in the first information with PLMN-identity.
  • the PLMNs of the first network device and the second network device are different at the same time, or that the order of the PLMNs in the PLMN list (for example, plmn-IdentityInfoList) indicated in SIB1 is different between the cell of the first network device and the cell of the second network device.
  • this causes a problem of misalignment of the understanding of PLMN-index by the first network device and the second network device (that is, the same plmn-index corresponds to different PLMNs in the first network device and the second network device).
  • the method further includes:
  • the second network device receives a first request message sent by the first network device, where the first request message is used to request acquisition of context information of the terminal device for SDT;
  • the second network device sends partial context information of the terminal device to the first network device, where the partial context information includes seventh information, and the seventh information is used to Indicates the second broadcast service received by the terminal device.
  • the second network device receives the first request message sent by the first network device, and responds to the The first request message sends part of the context information of the terminal device to the first network device, where the first request message is used to request to obtain the context information of the terminal device for SDT, and the second network device responds to the first request message to send the terminal device
  • Part of the context information includes seventh information, the seventh information is used to indicate the second broadcast service received by the terminal device.
  • the second network device may learn that the terminal device is in During the process of SDT, you may also be interested in receiving or receiving the second broadcast service, so that the first network device can properly schedule SDT and the second broadcast service, so that the terminal device can perform small data transmission scenarios without UE context relocation. Under this condition, data from SDT and the second broadcast service can also be received to avoid bit errors and/or packet loss caused by scheduling exceeding the receiving capabilities of the terminal device.
  • the method before the second network device sends the sixth information and/or the seventh information to the first network device, the method further includes:
  • the second network device determines, based on the capability information of the terminal device, that the terminal device does not support receiving unicast data and broadcast data in the same time slot.
  • the second network device can determine whether the terminal device supports or does not support the communication at the same time according to the capability information of the terminal device. Receive unicast data and broadcast data in the same time slot. When the second network device determines that the terminal device does not support receiving unicast data and broadcast data in the same time slot, the second network device determines to send the sixth information and/or to the first network device.
  • the first network device can appropriately schedule SDT and broadcast services, for example, send SDT data and broadcast data to the terminal device through inter-slot time division multiplexing (inter-slot TDM), so that Terminal devices can receive data from SDT and broadcast services to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • inter-slot TDM inter-slot time division multiplexing
  • embodiments of the present application provide a communication method, which method includes:
  • the terminal device receives the small data transmission SDT sent by the first network device and the data of the first multicast session.
  • the SDT is the transmission of data and/or signaling in the RRC inactive state of the radio resource control.
  • the first network The device is a network device corresponding to the cell where the terminal device resides, the first multicast session is a multicast session joined by the terminal device, and the tenth information used to indicate the first multicast session is provided by the second
  • the network device sends it to the first network device, and the second network device is a network device that connects the terminal device and the core network device.
  • a communication method is provided.
  • a terminal device in an RRC inactive state performs SDT with a first network device, and the terminal device is interested in receiving or is receiving information about the first multicast session from the first network device.
  • data wherein the first multicast session is a multicast session joined by the terminal device, the first network device sends the data of the first multicast session to the terminal device according to the tenth information, and the tenth information is sent by the second network device to the A network device.
  • the multicast session that the terminal device is interested in receiving may also refer to the multicast session that the terminal device has not received but is to be received.
  • the second network device passes The tenth information used to indicate the first multicast session is sent to the first network device, so that the first network device knows that the terminal device has also joined the first multicast session during the SDT process, so that when the first network device can
  • the first network device can appropriately schedule the SDT and the data of the first multicast session, for example, send the SDT data and the first multicast through inter-slot time division multiplexing.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • the tenth information is carried in part of the context information of the terminal device sent by the second network device to the first network device.
  • the tenth information is carried in part of the context information of the terminal device sent by the second network device to the first network device.
  • the second network device passes Part of the context information of the terminal device is sent to the first network device.
  • the part of the context information of the terminal device includes the tenth information used to indicate the first multicast session, so that the first network device knows that the terminal device also joins the SDT process.
  • the first multicast session is obtained, so that the first network device can appropriately schedule the SDT and the data of the first multicast session, for example, sending the SDT data and the data of the first multicast session through time division multiplexing between time slots, Or send the SDT data and the data of the first multicast session through frequency division multiplexing between time slots, etc., so that the terminal device can also receive the SDT and the first multicast session in a small data transmission scenario without UE context relocation. Multicast session data to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • embodiments of the present application provide a communication method, which method includes:
  • the first network device receives the tenth information from the second network device, the tenth information is used to indicate the first multicast session that the terminal device joins, for example, the tenth information is the TMGI information of the multicast session;
  • the The first network device is a network device corresponding to the cell where the terminal resides, and the second network device is a network device connecting the terminal device and the core network device;
  • the first network device sends a small data transmission SDT and the data of the first multicast session to the terminal device, where the SDT is the transmission of data and/or signaling in an RRC inactive state.
  • a communication method is provided.
  • the first network device receives the tenth information sent by the second network device.
  • the tenth information is used to indicate the information of the first multicast session that the terminal device joins.
  • the tenth information Specifically, the information may be TMGI information of the first multicast session.
  • the first network device is performing SDT with the terminal device in the RRC inactive state, and the first network device provides the terminal device with the TMGI information of the first multicast session based on the tenth information. data.
  • the first network device A network device can learn from the tenth information sent by the second network device that the terminal device also joined the first multicast session during the SDT process and received The data of the first multicast session, so that the first network device can appropriately schedule the SDT and the data of the first multicast session, for example, send the SDT data and the data of the first multicast session through inter-slot time division multiplexing.
  • the first network device is a network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be a receiving gNB that performs SDT with the terminal device.
  • the first network device receives the tenth information from the second network device, including:
  • the first network device sends a second request message to the second network device, where the second request message is used to request acquisition of context information of the terminal device for SDT;
  • the first network device receives partial context information of the terminal device sent by the second network device, and the partial context information includes the tenth information.
  • the first network device sends a second request message to the second network device, and receives the second network device's response to the third request message.
  • Part of the context information of the terminal device sent by the second request message wherein the second request message is used to request to obtain the context information of the terminal device for SDT, and the part of the context information of the terminal device sent by the second network device in response to the second request message includes
  • the tenth information is used to indicate the information of the first multicast session that the terminal device joins.
  • the first network device performs SDT with the terminal device in the RRC inactive state, and the first network device provides the first multicast session for the terminal device in the RRC inactive state
  • the first network device The device can learn that the terminal device has also joined the first group during the SDT process by sending a second request message to the second network device and receiving the tenth information in the partial context information of the terminal device provided by the second network device.
  • the first network device can appropriately schedule the data of the SDT and the first multicast session, for example, send the SDT data and the data of the first multicast session through time division multiplexing between time slots, or through time slots
  • the SDT data and the data of the first multicast session are sent through frequency division multiplexing, etc., so that the terminal device can also receive the SDT and the data of the first multicast session in a small data transmission scenario without UE context relocation. data to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • the method further includes:
  • the first network device sends the SDT and the data of the first multicast session to the terminal device on different time slots.
  • the SDT can be understood as downlink SDT data (DL SDT data).
  • the sending of the SDT and the data of the first multicast session on different time slots can be understood as/replaced by sending the PDSCH of the SDT and the PDSCH of the first multicast session on different time slots/ GC-PDSCH, or understood as sending the PDSCH of the SDT and the PDSCH/GC-PDSCH of the first multicast session in an inter-slot time division multiplexing (inter-slot TDM) manner.
  • inter-slot TDM inter-slot time division multiplexing
  • the first network device schedules SDT through inter-slot time division multiplexing (inter-slot TDM). and the data of the first multicast session, for example, sending the SDT data to the terminal device on time slot 1, and sending the data of the first multicast session to the terminal device on time slot 2, so that the terminal device can receive it on different time slots.
  • inter-slot TDM inter-slot time division multiplexing
  • the first network device i.e., the serving cell
  • the corresponding network device which may also be called the receiving gNB of SDT, can learn the information of the first multicast session received by the terminal device, so that the terminal device can schedule the data of the SDT and the first multicast session on different time slots. Even if you do not have the ability to receive unicast data and multicast data on the same time slot, you can still receive the SDT sent by the first network device and the data of the first multicast session on different time slots to avoid scheduling exceeding Bit errors and/or packet loss caused by the receiving capabilities of the terminal device.
  • the method further includes:
  • the first network device receives eleventh information from the second network device, the eleventh information is used to indicate whether the terminal device supports M unicast data and N multicast data in Frequency division multiplexing FDM reception in the same time slot, the M and N are integers greater than or equal to 1; and/or,
  • the first network device receives twelfth information from the second network device, the twelfth information is used to indicate whether the terminal device supports P unicast data and Q multicast data in For time division multiplexing TDM reception in the same time slot, the P and Q are integers greater than or equal to 1.
  • the eleventh information is also used to indicate that the terminal device supports or does not support M unicast data and N multicast data in the same time slot on the first frequency band or the carrier of the first frequency band.
  • Frequency division multiplexing FDM reception the M and N are integers greater than or equal to 1; the eleventh information includes the identification of the first frequency band;
  • the twelfth information is also used to indicate that the terminal device supports or does not support P unicast data and Q multicast data in the same time slot on the second frequency band or the carrier of the second frequency band.
  • the P and the Q are integers greater than or equal to 1;
  • the twelfth information includes an identifier of the second frequency band; the first frequency band and the second frequency band may be the same frequency band or different frequency bands.
  • the unicast data can be understood as/replaced as PDSCH used to transmit unicast data, or the cell's wireless network temporary identifier (Cell Radio Network Temporary Identifier, cell RNTI) scrambled PDSCH;
  • the multicast data can be understood as/replaced as PDSCH/GC-PDSCH used to transmit MBS multicast data, or PDSCH scrambled by Group Radio Network Temporary Identifier (G-RNTI).
  • G-RNTI Group Radio Network Temporary Identifier
  • the time division multiplexing/frequency division multiplexing of unicast data and multicast data in the same time slot (intra-slot) can be understood as the unicast PDSCH and MBS multicast GC-PDSCH in the same time slot (intra-slot). ) time division multiplexing/frequency division multiplexing.
  • the first network device receives the eleventh information and/or the twelfth information from the second network device. /or twelfth message.
  • the first network device in the scenario where the first network device performs SDT with the terminal device in the RRC inactive state, and the first network device provides a multicast session for the terminal device in the RRC inactive state, the first network device can According to the eleventh information and/or the twelfth information, it is learned that the terminal device supports or does not support frequency division multiplexing TDM reception of one or more unicast data and one or more multicast data in the same time slot or Time division multiplexing TDM reception, so that the first network device can properly schedule the data of SDT and multicast sessions, so that the terminal device can also receive SDT and multicast sessions in a small data transmission scenario without UE context relocation. data to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • embodiments of the present application provide a communication method, which method includes:
  • the second network device sends the small data transmission SDT and the tenth information to the first network device.
  • the tenth information is used to indicate the first multicast session joined by the terminal device.
  • the first network device is the terminal resident.
  • Network equipment corresponding to the cell, the second network equipment is a network equipment connecting the terminal equipment and the core network equipment;
  • the SDT and the data of the first multicast session are sent by the first network device to the terminal device.
  • the SDT is the data and/or signaling of the terminal device in the Radio Resource Control RRC inactive state. transmission.
  • the second network device sends SDT and tenth information to the first network device, where the tenth information is used to indicate The first multicast session that the terminal device joins, the SDT and the data of the first multicast session indicated by the tenth information are sent by the first network device to the terminal device.
  • the second network The device can send the tenth information to the first network device, so that the first network device knows that the terminal device is still receiving data of the first multicast session during SDT, so that the first network device can compare SDT and the first The data of the multicast session is properly scheduled so that the terminal device can receive the SDT and the data of the first multicast session even in a small data transmission scenario without UE context relocation, thus avoiding problems caused by scheduling exceeding the capabilities of the terminal device. Bit errors and/or packet loss.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • the second network device sends tenth information to the first network device, including:
  • the second network device receives a second request message sent by the first network device, where the second request message is used to request acquisition of context information of the terminal device for SDT;
  • the second network device sends partial context information of the terminal device to the first network device, where the partial context information includes the tenth information.
  • the second network device receives the second request message sent by the first network device, and responds to the second request message to The first network device sends partial context information of the terminal device, where the second request message is used to request to obtain the context information of the terminal device for SDT, and the partial context information of the terminal device sent by the second network device in response to the second request message includes
  • the tenth information is used to indicate the information of the first multicast session that the terminal device joins.
  • the second network The device may enable the first network device to learn about the terminal device by receiving the second request message sent by the first network device and sending the tenth information in the partial context information of the terminal device to the first network device in response to the second request message.
  • the first multicast session is also added, so that the first network device can properly schedule the data of SDT and the first multicast session, so that the terminal device can transmit small data in a scenario without UE context relocation. Under this condition, the data of SDT and the first multicast session can also be received to avoid bit errors and/or packet loss caused by scheduling exceeding the receiving capabilities of the terminal device.
  • the SDT and the data of the first multicast session are sent by the first network device on different time slots. sent to the terminal device.
  • the SDT can be understood as downlink SDT data (DL SDT data).
  • the sending of the SDT and the data of the first multicast session on different time slots can be understood as/replaced by sending the PDSCH of the SDT and the PDSCH of the first multicast session on different time slots/ GC-PDSCH, or understood as sending the PDSCH of the SDT and the PDSCH/GC-PDSCH of the first multicast session in an inter-slot time division multiplexing (inter-slot TDM) manner.
  • inter-slot TDM inter-slot time division multiplexing
  • the first network device schedules SDT through inter-slot time division multiplexing (inter-slot TDM). and the data of the first multicast session, for example, sending the SDT data to the terminal device on time slot 1, and sending the data of the first multicast session to the terminal device on time slot 2, so that the terminal device can receive it on different time slots.
  • inter-slot TDM inter-slot time division multiplexing
  • the first network device i.e., the serving cell
  • the corresponding network device which may also be called the receiving gNB of SDT, can learn the information of the first multicast session received by the terminal device, so that the terminal device can schedule the data of the SDT and the first multicast session on different time slots. Even if you do not have the ability to receive unicast data and multicast data on the same time slot, you can still receive the SDT sent by the first network device and the data of the first multicast session on different time slots to avoid scheduling exceeding Bit errors and/or packet loss caused by the receiving capabilities of the terminal device.
  • the method before the second network device sends the tenth information to the first network device, the method further includes:
  • the second network device determines, based on the capability information of the terminal device, that the terminal device does not support receiving unicast data and multicast data in the same time slot.
  • the second network device can determine whether the terminal device supports or does not support the communication at the same time according to the capability information of the terminal device. Receive unicast data and multicast data in the same time slot.
  • the second network device determines that the terminal device does not support receiving unicast data and multicast data in the same time slot, determines to send the tenth information so that the first network device can properly schedule SDT and multicast sessions, for example, sending SDT data and multicast session data to the terminal device through inter-slot time division multiplexing (inter-slot TDM), Enables terminal devices to receive data from SDT and multicast sessions, and avoids bit errors and/or packet loss caused by scheduling exceeding the receiving capabilities of terminal devices.
  • inter-slot TDM inter-slot time division multiplexing
  • embodiments of the present application provide a communication method, which method includes:
  • the terminal device performs small data transmission SDT with the first network device, and the terminal device joins the second multicast session from the first network device.
  • the SDT is data in the Radio Resource Control RRC inactive state and /or signaling transmission
  • the first network device is a network device corresponding to the cell where the terminal device resides;
  • the terminal device sends thirteenth information to the first network device, the thirteenth information is used to indicate the second multicast session, and the thirteenth information is used for the first network device to send The terminal device sends the second multicast session.
  • a communication method is provided.
  • a terminal device in an RRC inactive state performs SDT with a first network device, and the terminal device joins a second multicast session from the first network device.
  • the terminal device communicates to The first network device sends thirteenth information, where the thirteenth information includes information of the second multicast session.
  • the thirteenth information may be TMGI information of the second multicast session.
  • the terminal device in the scenario where the terminal device is in the RRC inactive state and performs SDT with the first network device, and the terminal device receives the second multicast session from the first network device, it can report to the first network device
  • the thirteenth information allows the first network device to know that the terminal device is still receiving data of the second multicast session during SDT, so that the first network device can appropriately schedule SDT and the second multicast session, for example
  • the SDT data and the data of the second multicast session are sent by time division multiplexing between time slots, or the SDT data and the data of the second multicast session are sent by frequency division multiplexing between time slots, etc., so that the terminal equipment
  • data from SDT and the second multicast session can also be received to avoid bit errors and/or packet loss caused by scheduling exceeding the receiving capabilities of the terminal device.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT
  • the thirteenth information is carried in a media access control element MAC CE or a radio resource control RRC message.
  • the thirteenth information can be carried in a media access control control element (media access control control element, MAC CE) or radio resource control RRC. in the message.
  • MAC CE media access control control element
  • RRC radio resource control
  • the first network device can properly schedule the data of the SDT and the second multicast session, so that the terminal device can also receive the SDT and the second multicast session in a small data transmission scenario without UE context relocation.
  • data avoid Data errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • the method further includes:
  • the terminal device receives data of the SDT and the second multicast session from the first network device on different time slots.
  • the SDT can be understood as downlink SDT data (DownLink SDT data).
  • the receiving data of the SDT and the second multicast session on different time slots can be understood/replaced as receiving a physical downlink shared channel (physical downlink shared channel) for transmitting the SDT data on different time slots.
  • PDSCH physical downlink shared channel
  • GC-PDSCH group common physical downlink shared channel
  • a possible specific implementation method of scheduling SDT and the second multicast session is provided.
  • the first network device schedules the SDT and the second multicast session through inter-slot time division multiplexing (inter-slot TDM).
  • Two multicast sessions such as sending SDT data to the terminal device on time slot 1, and sending data of the second multicast session to the terminal device on time slot 2, so that the terminal device can receive data from the first multicast session on different time slots.
  • SDT of the network device and the data of the second multicast session are examples of the network device.
  • the terminal device receives data from the second multicast session of the first network device
  • the first network device i.e., the service The network equipment corresponding to the cell, which can also be called the receiving gNB of SDT
  • the terminal equipment can learn the information of the second multicast session received by the terminal equipment, thereby scheduling the data of SDT and the second multicast session on different time slots, so that the terminal equipment can It does not have the ability to receive unicast data and multicast data on the same time slot. It can also receive data from the SDT and the second multicast session sent by the first network device on different time slots to avoid scheduling beyond the terminal. Data errors and/or packet loss caused by the device's receiving capabilities.
  • embodiments of the present application provide a communication method, which method includes:
  • the first network device receives the thirteenth information sent by the terminal device, the thirteenth information is used to indicate a second multicast session, the second multicast session is a multicast session joined by the terminal device, and the third One network device is a network device corresponding to the cell where the terminal device resides;
  • the first network device performs small data transmission (SDT) with the terminal device, and the first network device sends data of the second multicast session to the terminal device.
  • SDT small data transmission
  • RRC radio resource control
  • a communication method is provided.
  • the first network device receives the thirteenth information sent by the terminal device.
  • the thirteenth information is used to indicate the information of the second multicast session that the terminal device joins.
  • the tenth information may specifically be the TMGI information of the second multicast session.
  • the first network device is performing SDT with the terminal device in the RRC inactive state, and the first network device provides the second multicast to the terminal device based on the thirteenth information. session.
  • the first network device in the scenario where the first network device performs SDT with the terminal device in the RRC inactive state, and the first network device provides the second multicast session for the terminal device in the RRC inactive state, the first network device The device can learn from the thirteenth information reported by the terminal device that the terminal device is still receiving the data of the second multicast session during SDT, so that the first network device can process the data of the SDT and the second multicast session. Appropriate scheduling, such as sending SDT data and the data of the second multicast session through time division multiplexing between slots, or sending SDT data and the data of the second multicast session through frequency division multiplexing between slots, etc.
  • the terminal device can also receive the data of SDT and the second multicast session in a small data transmission scenario without UE context relocation, avoiding bit errors and/or packet loss caused by scheduling exceeding the receiving capability of the terminal device.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • the first network device performs small data transmission SDT with the terminal device, and the first network device sends the data of the second multicast session to the terminal device, including :
  • the first network device sends the SDT and the data of the second multicast session to the terminal device on different time slots.
  • the SDT can be understood as downlink SDT data (DL SDT data).
  • the sending of the data of the SDT and the second multicast session on different time slots can be understood as/replaced by sending the PDSCH of the SDT and the PDSCH of the second multicast session on different time slots/ GC-PDSCH, or understood as sending the PDSCH of the SDT and the PDSCH/GC-PDSCH of the second multicast session in an inter-slot time division multiplexing (inter-slot TDM) manner.
  • inter-slot TDM inter-slot time division multiplexing
  • the first network device schedules the SDT and the second multicast session through inter-slot time division multiplexing (inter-slot TDM).
  • Inter-slot TDM inter-slot time division multiplexing
  • Two multicast sessions such as sending SDT data to the terminal device on time slot 1, and sending data of the second multicast session to the terminal device on time slot 2, so that the terminal device can receive data from the first multicast session on different time slots.
  • SDT of the network device and the data of the second multicast session are examples of the network device.
  • the first network device i.e., the serving cell
  • the corresponding network device which may also be called the receiving gNB of SDT, can learn the information of the second multicast session received by the terminal device, so that the terminal device can schedule the data of the SDT and the second multicast session on different time slots. Even if there is no ability to receive unicast data and multicast data on the same time slot, the data from the SDT sent by the first network device and the second multicast session can be received on different time slots.
  • the terminal device sends the thirteenth information to the first network device, which can indicate that the terminal device supports receiving the MBS multicast service.
  • the terminal device must support PDSCH for transmitting unicast data and PDSCH/GC for transmitting MBS multicast data.
  • - PDSCH inter-slot time division multiplexing (inter-slot TDM) reception so the first network device sends SDT and second multicast session data according to inter-slot time division multiplexing, which can ensure that the terminal device can The data of the second multicast session is received to avoid bit errors and/or packet loss, thereby ensuring the service quality of SDT and MBS multicast services.
  • the first network device When the terminal device does not support receiving unicast data and MBS multicast data in the same time slot, in the SDT scenario without context relocation, the first network device does not have UE capability information. If the first network device does not know that the terminal device is When receiving the second multicast session, when the first network device schedules/sends SDT data (SDT can be understood as a unicast transmission method) and the data of the second multicast session in the same time slot, it will cause the terminal device to be unable to SDT and multicast data are received, or the terminal device can only receive one of SDT or multicast data, causing data errors and/or packet loss, affecting service reception quality. Therefore, through the solution of this application, the above problems can be avoided.
  • SDT can be understood as a unicast transmission method
  • the thirteenth information is carried in a media access control element MAC CE or a radio resource control RRC message.
  • the thirteenth information can be carried in the media access control element MAC CE or the radio resource control RRC message.
  • the first network device receives the terminal The MAC CE or RRC message sent by the device.
  • the MAC CE or RRC message includes the thirteenth information used to indicate the second multicast session, so that the first network device knows that the terminal device has also joined the second group during the SDT process.
  • the first network device can properly schedule the data of the SDT and the second multicast session, so that the terminal device can also receive the SDT and the second multicast in a small data transmission scenario without UE context relocation. session data to avoid data errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • embodiments of the present application provide a communication method, which method includes:
  • the second network device sends a small data transmission SDT to the first network device; wherein the SDT and the data of the second multicast session are sent by the first network device to the terminal device, and the SDT is the wireless transmission of the terminal device.
  • the resource controls the transmission of RRC inactive data and/or signaling.
  • the first network device is a network device corresponding to the cell where the terminal device resides.
  • the second network device is a network device that connects the terminal device and the core.
  • a network device of a network device, the second multicast session is a multicast session that the thirteenth information indicates that the terminal device joins, and the thirteenth information comes from the terminal device.
  • the second network device sends SDT to the first network device, where the SDT and the second multicast indicated by the thirteenth information
  • the session is sent by the first network device to the terminal device, and the thirteenth information is used to indicate the second multicast session that the terminal device joins.
  • the second network device can send the thirteenth information to the first network device, so that the first network device knows that the terminal device is still receiving data of the second multicast session during SDT, so that the first network device can compare SDT and the third multicast session.
  • the data of the second multicast session is properly scheduled, for example, SDT data and the data of the second multicast session are sent by time division multiplexing between time slots, or SDT data and the second multicast session are sent by frequency division multiplexing between time slots.
  • the data of the multicast session, etc. enable the terminal device to receive SDT and the data of the second multicast session in a small data transmission scenario without UE context relocation, avoiding the problem caused by scheduling exceeding the receiving capability of the terminal device. Data errors and/or packet loss.
  • an embodiment of the present application provides a communication device, which includes a module or unit for executing the method described in any one of the first to ninth aspects.
  • the device includes:
  • a transceiver unit configured to perform small data transmission SDT with a first network device, and is interested in receiving or currently receiving a first broadcast service from the first network device, where the SDT is in the Radio Resource Control (RRC) inactive state.
  • RRC Radio Resource Control
  • the first network device is the network device corresponding to the cell where the communication device resides;
  • the transceiver unit is further configured to send first information to the first network device, where the first information includes information about the first broadcast service, and the first information is used by the first network device to send information to the first network device.
  • the communication device provides the first broadcast service.
  • the transceiver unit is further configured to receive the SDT and the first broadcast service from the first network device on different time slots.
  • the transceiver unit is also configured to receive the second information sent by the first network device and/or the second network device.
  • the third information sent by a network device, the second network device is a network device that sends an RRC release message to the communication device;
  • a processing unit configured to send the first information to the first network device through the transceiver unit according to the second information and/or the third information.
  • the transceiver unit is further configured to receive the fourth information sent by the first network device and/or the fifth information sent by the second network device;
  • the processing unit is further configured to send the first information to the first network device through the transceiver unit according to the fourth information and/or the fifth information, where the first information includes the TMGI information of First Broadcasting Service
  • the third information and/or the fifth information are carried in an RRC release message
  • the processing unit is also configured to enter the RRC inactive state according to the RRC release message.
  • the second information, and/or the third information, and/or the fourth information, and/or the fifth information include system information.
  • the second information and/or the third information includes first system information, which is used to indicate a mapping relationship between multicast broadcast services and frequencies, or to Indicates the configuration parameters of the multicast broadcast service control channel MCCH.
  • the fourth information and/or the fifth information includes second system information
  • the second system information is used to indicate the mapping relationship between multicast broadcast services and frequencies, or is used to Indicates the configuration parameters of the multicast broadcast service control channel MCCH.
  • the device includes:
  • a transceiver unit configured to receive first information sent by a terminal device, where the first information includes information about a first broadcast service that the terminal device is interested in receiving or is receiving, and the communication device is resident for the terminal device.
  • Network equipment corresponding to the community;
  • the transceiver unit is also configured to perform small data transmission SDT with the terminal device, and provide the first broadcast service to the terminal device, where the SDT is data and/or data in the Radio Resource Control (RRC) inactive state. or signaling transmission.
  • RRC Radio Resource Control
  • the transceiver unit is further configured to send the SDT and the first broadcast service to the terminal device on different time slots.
  • the transceiver unit is further configured to send the first information to a second network device, where the second network device is a network device connecting the terminal device and the core network device;
  • the transceiver unit is further configured to receive sixth information from the second network device, where the sixth information is used to indicate the first broadcast service, and the sixth information is determined by the first information.
  • the transceiver unit is further configured to send a first request message to the second network device, where the first request message is used to request acquisition of context information of the terminal device for SDT;
  • the transceiver unit is also configured to receive partial context information of the terminal device sent by the second network device, where the partial context information includes seventh information, and the seventh information is used to instruct the terminal device to receive of the Second Broadcasting Service.
  • the processing unit is configured to ignore the seventh information when receiving the sixth information.
  • the transceiver unit is further configured to receive eighth information from the second network device, where the eighth information is used to indicate whether the terminal device supports or does not support M single Frequency division multiplexing FDM reception of broadcast data and N broadcast data in the same time slot, where the M and N are integers greater than or equal to 1; and/or,
  • the transceiver unit is also configured to receive ninth information from the second network device, where the ninth information is used to indicate that the terminal device supports or does not support P unicast data and Q broadcast data at the same time.
  • the P and the Q are integers greater than or equal to 1.
  • the device includes:
  • a transceiver unit configured to send small data transmission SDT and sixth information to the first network device.
  • the sixth information is used to indicate a first broadcast service.
  • the first broadcast service is a broadcast that the terminal device is interested in receiving or is receiving.
  • the communication device is a network device that connects the terminal device and the core network device
  • the first network device is a network device corresponding to the cell where the terminal device resides
  • the SDT is a wireless communication device for the terminal device.
  • the resource controls the transmission of RRC inactive data and/or signaling, and the SDT is sent to the terminal device through the first network device.
  • the transceiver unit is further configured to receive first information sent by the first network device, where the first information includes information about the first broadcast service;
  • a processing unit configured to determine the sixth information based on the first information.
  • the transceiver unit is further configured to receive a first request message sent by the first network device, where the first request message is used to request to obtain context information of the terminal device for SDT. ;
  • the transceiver unit is further configured to send partial context information of the terminal device to the first network device in response to the first request message, where the partial context information includes seventh information, and the seventh information Used to indicate the second broadcast service received by the terminal device.
  • the processing unit is further configured to determine, based on the capability information of the terminal device, that the terminal device does not support receiving unicast data and broadcast data in the same time slot.
  • the device includes:
  • a transceiver unit configured to receive a small data transmission SDT sent by the first network device and the data of the first multicast session, where the SDT is the transmission of data and/or signaling in the RRC inactive state, the
  • the first network device is a network device corresponding to the cell where the communication device resides
  • the first multicast session is a multicast session joined by the communication device, and is used to indicate the tenth information of the first multicast session. It is sent to the first network device by a second network device, and the second network device is a network device that connects the communication device and the core network device.
  • the tenth information is carried in part of the context information of the communication device sent by the second network device to the first network device.
  • the device includes:
  • a transceiver unit configured to receive the tenth information from the second network device, where the tenth information is used to indicate the first multicast session that the terminal device joins, and the communication device is the network corresponding to the cell where the terminal resides.
  • Equipment, the second network equipment is a network equipment connecting the terminal equipment and the core network equipment;
  • the transceiver unit is also configured to send small data transmission SDT and data of the first multicast session to the terminal device, where the SDT is data and/or signaling in the Radio Resource Control (RRC) inactive state. transmission.
  • RRC Radio Resource Control
  • the transceiver unit is further configured to send a second request message to the second network device, where the second request message is used to request acquisition of context information of the terminal device for SDT;
  • the transceiver unit is also configured to receive partial context information of the terminal device sent by the second network device, where the partial context information includes the tenth information.
  • the transceiver unit is further configured to send the SDT and the data of the first multicast session to the terminal device on different time slots.
  • the transceiver unit is further configured to receive eleventh information from the second network device, where the eleventh information is used to indicate that the terminal device supports or does not support M Frequency division multiplexing FDM reception of unicast data and N multicast data within a time slot, where the M and N are integers greater than or equal to 1; and/or,
  • the transceiver unit is also configured to receive twelfth information from the second network device, where the twelfth information is used to indicate that the terminal device supports or does not support P unicast data and Q multicast data.
  • the data is received in time division multiplexing TDM within the time slot, and the P and the Q are integers greater than or equal to 1.
  • the device includes:
  • a transceiver unit configured to send small data transmission SDT and tenth information to the first network device.
  • the tenth information is used to indicate the first multicast session joined by the terminal device.
  • the first network device is camped for the terminal.
  • the network equipment corresponding to the cell, the communication device is the network equipment connecting the terminal equipment and the core network equipment;
  • the SDT and the data of the first multicast session are sent by the first network device to the terminal device.
  • the SDT is the data and/or signaling of the terminal device in the Radio Resource Control RRC inactive state. transmission.
  • the transceiver unit is further configured to receive a second request message sent by the first network device.
  • the second request message is used to request to obtain context information of the terminal device for SDT. ;
  • the transceiver unit is further configured to send partial context information of the terminal device to the first network device, where the partial context information includes the tenth information.
  • the SDT and the data of the first multicast session are sent by the first network device to the terminal device on different time slots.
  • the processing unit is configured to determine, based on the capability information of the terminal device, that the terminal device does not support receiving unicast data and multicast data in the same time slot.
  • the device includes:
  • a transceiver unit configured to perform small data transmission SDT with the first network device, and join the second multicast session from the first network device, where the SDT is data in the Radio Resource Control RRC inactive state and/ Or the transmission of signaling, the first network device is the network device corresponding to the cell where the communication device resides;
  • the transceiver unit is further configured to send thirteenth information to the first network device, where the thirteenth information is used to indicate the second multicast session, and the thirteenth information is used for the first
  • the network device sends the second multicast session to the communication device.
  • the thirteenth information is carried in a media access control element MAC CE or a radio resource control RRC message.
  • the transceiver unit is further configured to receive data from the SDT and the second multicast session of the first network device on different time slots.
  • the device includes:
  • a transceiver unit configured to receive the thirteenth information sent by the terminal device, where the thirteenth information is used to indicate a second multicast session, where the second multicast session is a multicast session joined by the terminal device, and the
  • the communication device is a network device corresponding to the cell where the terminal device resides;
  • the transceiver unit is also configured to perform small data transmission SDT with the terminal device, and send data of the second multicast session to the terminal device, where the SDT is in the Radio Resource Control (RRC) inactive state. Transmission of data and/or signaling.
  • RRC Radio Resource Control
  • the transceiver unit is further configured to send the SDT and the data of the second multicast session to the terminal device on different time slots.
  • the thirteenth information is carried in a media access control element MAC CE or a radio resource control RRC message.
  • the device includes:
  • the transceiver unit is also configured to send small data transmission SDT to the first network device; wherein the SDT and the data of the second multicast session are sent to the terminal device by the first network device, and the SDT is the terminal device.
  • the first network device is a network device corresponding to the cell where the terminal resides, and the communication device is used to connect the terminal device to the core network.
  • a network device of the device, the second multicast session is a multicast session that the thirteenth information indicates that the terminal device joins, and the thirteenth information comes from the terminal device.
  • an embodiment of the present application provides a communication device, which includes a processor.
  • the processor is coupled to a memory and may be used to execute instructions in the memory to implement any one of the above-mentioned first to ninth aspects and the method of any possible implementation.
  • the communication device further includes a memory.
  • the communication device further includes a communication interface, and the processor is coupled with the communication interface.
  • embodiments of the present application provide a communication device, including: a logic circuit and a communication interface.
  • the communication interface is used to receive information or send information;
  • the logic circuit is used to receive information or send information through the communication interface, so that the communication device performs any one of the first to ninth aspects and any of the above.
  • embodiments of the present application provide a computer-readable storage medium, the computer-readable storage medium being used to store a computer program (also called a code, or an instruction); when the computer program is stored on a computer When running, the method of any one of the above-mentioned first to ninth aspects and any possible implementation is implemented.
  • a computer program also called a code, or an instruction
  • inventions of the present application provide a computer program product.
  • the computer program product includes: a computer program (which can also be called a code, or an instruction); when the computer program is run, it causes the computer to execute the above Any one from the first aspect to the ninth aspect and any possible implementation method.
  • embodiments of the present application provide a chip.
  • the chip includes a processor.
  • the processor is configured to execute instructions.
  • the chip performs the above-mentioned first to ninth aspects.
  • the chip also includes a communication interface, which is used to receive signals or send signals.
  • embodiments of the present application provide a communication system, which includes at least one communication device as described in the tenth aspect, or a communication device as described in the eleventh aspect, or a communication device as described in the twelfth aspect.
  • embodiments of the present application provide a communication system, including a terminal device, a first network device, and a second network device; wherein the terminal device is used to perform the above first aspect and any possible implementation.
  • the terminal device is used to perform the above first aspect and any possible implementation.
  • the first network device is configured to perform the method of the above-mentioned second aspect and any possible implementation manner
  • the second network device is configured to perform the method of the above-mentioned third aspect and any possible implementation manner.
  • the terminal device is configured to perform the method of the above-mentioned fourth aspect and any possible implementation manner
  • the first network device is configured to perform the method of the above-mentioned fifth aspect and any possible implementation manner
  • the second network device is configured to perform the method of the above-mentioned sixth aspect and any possible implementation manner
  • the terminal device is configured to perform the method of the above-mentioned seventh aspect and any possible implementation manner
  • the The first network device is configured to perform the method of the eighth aspect and any possible implementation manner
  • the second network device is configured to perform the method of the ninth aspect and any possible implementation manner.
  • the process of sending information and/or receiving information in the above method can be understood as The process by which a processor outputs information, and/or the process by which a processor receives input information.
  • the processor may output the information to the transceiver (or communication interface, or transmitting module) for transmission by the transceiver. After the information is output by the processor, it may also need to undergo other processing before it reaches the transceiver.
  • the transceiver or communication interface, or sending module
  • the transceiver receives the information and inputs it into the processor.
  • the information may need to undergo other processing before being input to the processor.
  • the sending information mentioned in the foregoing method can be understood as processor output information.
  • receiving information can be understood as the processor receiving input information.
  • the above processor may be a processor specially used to execute these methods, or may be A processor, such as a general-purpose processor, that performs these methods by executing computer instructions in memory.
  • the above-mentioned memory can be a non-transitory memory, such as a read-only memory (Read Only Memory, ROM), which can be integrated on the same chip with the processor, or can be separately provided on different chips.
  • ROM Read Only Memory
  • the above-mentioned at least one memory is located outside the device.
  • the above-mentioned at least one memory is located within the device.
  • part of the at least one memory is located within the device, and another part of the memory is located outside the device.
  • processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.
  • the terminal device in a scenario where the terminal device is in the RRC inactive state and performs SDT with the first network device, and the terminal device receives a broadcast service or multicast session from the first network device, it can send a request to the first network device by sending a message to the first network device.
  • the broadcast services that the terminal device is interested in receiving or is receiving, or the multicast sessions that it has joined so that the first network device knows that the terminal device is still receiving broadcast services or multicast sessions during the SDT process, so that the first network device SDT, broadcast services and/or multicast sessions can be properly scheduled so that terminal devices can receive SDT and multicast broadcast service data in small data transmission scenarios without UE context relocation to avoid scheduling beyond the terminal Data errors and/or packet loss caused by the device's receiving capabilities.
  • Figure 1 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • Figure 2 is a schematic diagram of terminal equipment state switching provided by an embodiment of the present application.
  • Figure 3 is a schematic diagram of the RRC connection recovery process of a terminal device provided by an embodiment of the present application.
  • Figure 4 is a schematic flow chart of a communication method provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another communication method provided by an embodiment of the present application.
  • Figure 6 is a schematic flow chart of another communication method provided by an embodiment of the present application.
  • Figure 7 is a schematic flow chart of another communication method provided by an embodiment of the present application.
  • Figure 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 10 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • an embodiment means that a particular feature, structure or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application.
  • the appearances of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments.
  • Those skilled in the art can understand explicitly and implicitly that in the various embodiments of the present application, if there is no special explanation or logical conflict, the terminology and/or description between the various embodiments are consistent, and can By referencing each other, technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
  • At least one (item) refers to one or more
  • plural refers to two or more
  • at least two (items) refers to two or three and three or more
  • "and/or” is used to describe the relationship between associated objects, indicating that there can be three relationships.
  • a and/or B can mean: only A exists, only B exists, and A exists at the same time. and B, where A and B can be singular or plural.
  • the character “/” generally indicates that the related objects are in an "or” relationship.
  • At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • At least one of a, b or c can mean: a, b, c, "a and b", “a and c", “b and c", or "a and b and c” ”, where a, b, c can be single or multiple.
  • the method provided by this application can be applied to various communication systems, for example, it can be an Internet of things (IoT) system, a narrowband Internet of things (NB-IoT) system, a long term evolution (long term evolution) , LTE) system, it can also be the fifth generation (5th-generation, 5G) communication system, and new communication systems (such as 6G) that will appear in future communication development.
  • IoT Internet of things
  • NB-IoT narrowband Internet of things
  • LTE long term evolution
  • 5G fifth generation
  • new communication systems such as 6G
  • the technical solution provided by this application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), and device-to-device (D2D) networks.
  • M2M machine to machine
  • IoT Internet of things
  • the IoT network may include, for example, the Internet of Vehicles.
  • the communication methods in the Internet of Vehicles system are collectively called vehicle-to-everything (V2X, X can represent anything).
  • the V2X can include: vehicle-to-vehicle (V2V) communication, Vehicle to infrastructure (V2I) communication, vehicle to pedestrian (V2P) communication, or vehicle to network (V2N) communication, etc.
  • V2V vehicle-to-vehicle
  • V2I Vehicle to infrastructure
  • V2P vehicle to pedestrian
  • V2N vehicle to network
  • Figure 1 is a schematic diagram of a communication system provided by an embodiment of the present application.
  • the communication system may include at least one access network device and at least one terminal device.
  • the access network equipment may be the next generation node B (next generation node B, gNB), the next generation evolved base station (next generation evolved nodeB, ng-eNB), or the access network equipment in future 6G communications, etc. .
  • the access network device can be any device with wireless transceiver functions, including but not limited to the base stations shown above.
  • the base station may also be a base station in a future communication system such as a sixth generation communication system.
  • the access network device can be an access node, a wireless relay node, a wireless backhaul node, etc. in a wireless fidelity (WiFi) system.
  • the access network device may be a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario.
  • cloud radio access network cloud radio access network
  • the access network device may be a wearable device or a vehicle-mounted device.
  • the access network device may also be a small station, a transmission reception point (TRP) (or may also be called a transmission point), etc.
  • TRP transmission reception point
  • the access network equipment may also be a base station in a public land mobile network (public land mobile network, PLMN) that will evolve in the future. etc.
  • base stations can be composed of centralized units (CU) and distributed units (DU). That is, the functions of the base station in the access network are split, some functions of the base station are deployed in a CU, and the remaining functions are deployed in a DU. And multiple DUs share one CU, which can save costs and facilitate network expansion.
  • CU can also be divided into CU-control plane (CP) and CU-user plane (user plan, UP).
  • CP CU-control plane
  • UP user plan
  • the base stations may also be open radio access network (ORAN) architectures, etc. This application does not limit the specific type of base stations.
  • the following uses the access network device as a base station as an example to introduce the method involved in this application.
  • the terminal equipment may also be called user equipment (user equipment, UE), terminal, etc.
  • Terminal equipment is a device with wireless transceiver functions that can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on water, such as on ships; it can also be deployed in the air, such as on On board an airplane, balloon or satellite, etc.
  • the terminal device can be a mobile phone (mobile phone), tablet computer (Pad), computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, industrial control (industrial control) ), wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, and wireless terminals in transportation safety , wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the terminal equipment may also be a terminal equipment in a future 6G network or a terminal equipment in a future evolved PLMN, etc.
  • the terminal equipment shown in this application may not only include vehicles in the Internet of Vehicles (such as complete vehicles), but may also include vehicle-mounted equipment or vehicle-mounted terminals in the Internet of Vehicles, etc. This application will not apply to the terminal equipment when it is applied to the Internet of Vehicles.
  • the specific form is not limited.
  • the terminal device as a UE as an example to introduce the method involved in this application.
  • the communication system can also include at least one core network device.
  • the introduction of the core network device is as follows:
  • the core network equipment includes user access control, mobility management, session management, user security authentication, accounting and other services. It consists of multiple functional units, which can be divided into functional entities of the control plane and data plane. Among them, the access and mobility management function (AMF) is responsible for user access management, security authentication, and mobility management.
  • the location management function (LMF) is responsible for managing and controlling the location service requests of the target terminal and processing location-related information.
  • the user plane function (UPF) is responsible for managing user plane data transmission, traffic statistics and other functions.
  • base station 1 can send downlink signals such as configuration information or downlink control information (DCI) to UE1 to UE6, and UE1 to UE6 can send SRS or physical uplink shared channel (physical uplink shared channel) to base station 1. PUSCH) and wait for the uplink signal.
  • DCI downlink control information
  • Base station 1 can also send downlink signals to UE7 to UE8 through base station 2, and UE7 to UE8 can send uplink signals to base station 1 through base station 2.
  • Base station 2 can send configuration information or downlink signals such as DCI to UE7 to UE8, and UE7 to UE8 can send uplink signals such as SRS or PUSCH to base station 2. It can be understood that for the communication method between UEs, reference can be made to the above description, which will not be described in detail here.
  • FIG. 1 exemplarily shows one core network device, two base stations and eight UEs, as well as communication links between each communication device.
  • the communication system may include multiple base stations, and the coverage of each base station may include other numbers of UEs, such as more or less UEs, etc., which is not limited in this application.
  • Each of the above communication devices can be configured with multiple antennas.
  • the multiple antennas may include at least one transmitting antenna for transmitting signals and at least one receiving antenna for receiving signals.
  • the embodiments of the present application do not limit the specific structure of each communication device.
  • the communication system may also include other network entities such as a network controller and a mobility management entity, and the embodiments of the present application are not limited thereto.
  • This application provides a communication method, which is applied in the field of communication technology.
  • the UE communicates with SDT, broadcast services, and multicast sessions in an inactive state.
  • SDT Session Initiation Protocol
  • broadcast services Session Initiation Protocol
  • multicast sessions in an inactive state.
  • Figure 2 is a schematic diagram of terminal device state switching provided by an embodiment of the present application.
  • RRC radio resource control
  • NR 5G new radio
  • UE has three RRC states: RRC_INACTIVE (radio resource control-inactive state), RRC_CONNECTED (radio resource control - connected state) and RRC_IDLE (radio resource control - idle state).
  • RRC connected state an RRC connection is established between the UE and the base station.
  • RRC idle state there is no RRC connection established between the base station and the UE; or the base station releases the UE to In the RRC inactive state, the RRC connection is suspended.
  • the base station In the RRC inactive state, the base station still maintains UE context information.
  • the advantage of NR introducing the RRC inactive state is that compared to the RRC idle state, in the RRC inactive state, the base station still retains the UE context, so the RRC connection can be restored more quickly, and when traffic arrives, the delay can be reduced.
  • RRC_INACTIVE radio resource control - inactive state
  • RRC_CONNECTED radio resource control - connected state
  • RRC_IDLE radio resource control - idle state
  • RRC_INACTIVE radio resource control - inactive state
  • RRC_CONNECTED radio resource control - connected state
  • the base station will allocate an identity I- to the UE.
  • RNTI Inactive Radio Network Temporary Identifier
  • This base station is also called the UE's last serving gNB (last serving gNB), and is sometimes also recorded as the anchor gNB (anchor gNB).
  • the UE When the UE requests to resume a previously suspended RRC connection or update the radio notification area (RNA), the UE sends a RRCResumeRequest message to the current serving base station.
  • the RRCResumeRequest message structure includes a recovery reason value, which is used to indicate The RRCResumeRequest message requests the recovery reason.
  • the RRCResumeRequest message structure also includes the I_RNTI identifier. The current serving base station goes to the last serving gNB to retrieve the UE context according to the I_RNTI identifier.
  • Figure 3 is a schematic diagram of the RRC connection recovery process of a terminal device provided by an embodiment of the present application. Each step in Figure 3 is explained below:
  • the UE sends an RRC connection recovery request RRCResumeRequst to the current serving base station (gNB).
  • the RRCResumeRequst contains the I-RNTI allocated to the UE by the last serving base station (last serving gNB).
  • gNB When gNB receives RRCResumeRequst, and based on the gNB identity contained in I-RNTI, it can find the last serving gNB and request it to provide the context of the UE.
  • gNB sends a context acquisition request Retrieve UE context request message to the corresponding last serving gNB.
  • S303 The last serving gNB provides the context of the UE to gNB.
  • the last serving gNB sends a context retrieval response Retrieve UE context response message to gNB, and the context retrieval response message includes the context of the UE.
  • S304/S305: gNB and UE complete the restoration of RRC connection, and can send user data after obtaining the authorization grant.
  • S307/S308 gNB performs path conversion.
  • gNB triggers resource release of the UE at the last serving gNB.
  • gNB can send an RRCSetup message to the UE to re-establish the RRC connection; or gNB can directly send an RRCReject message to the UE to reject the UE's establishment request.
  • CN paging Since the UE is mobile, when the UE is in the RRC idle state, in order to find the UE, the network needs all the tracking areas (tracking area, TA) of the core network (CN) in the tracking area identity (TAI) list. ) sends paging messages (CN-initiated paging, hereinafter referred to as CN paging). It can be seen that under this level of terminal tracking, since most paging messages are delivered in cells where the UE is not present, high paging message transmission overhead will be generated.
  • TA tracking area
  • TAI tracking area identity
  • RNA RAN-based Notification Area
  • a TA range can include multiple RNAs, and one RNA can include Multiple cells
  • RNA is managed by gNB, and gNB can send paging messages (RAN-initiated paging, hereinafter referred to as RAN paging) to cells within the range of RNA.
  • RAN paging paging messages
  • the last serving gNB For RAN paging, when the last serving gNB receives downlink data from UPF or downlink signaling from AMF, it will page the UE on the cell in the RNA area, and if the RNA area includes cells of neighboring gNB(s), The last serving gNB will deliver RAN paging to the neighboring gNB(s) through the Xn interface, and the neighboring gNB(s) will page the UE in its cell.
  • Typical small and infrequent data transmissions include but are not limited to: instant messaging services, push notifications from various applications, periodic positioning information from wearable devices, regular data transmission from industrial sensors, etc.
  • the transmission of SDT can include:
  • RACH random access channel
  • UE sends SDT UL data and RRCResumeRequest to gNB through the CG resources configured by gNB in the RRCRelease message.
  • SDT transmission includes two network architectures:
  • the gNB Since the UE will move in the inactive state, if the gNB the UE accesses is not the last serving gNB, the UL SDT data/signaling is cached in the current serving base station (receiving gNB), and then the receiving gNB triggers XnAP to retrieve the UE context (XnAP Retrieve UE Context) process.
  • the receiving gNB indicates to the last serving gNB that there is SDT, and the last serving gNB decides whether to relocate the UE context.
  • the last serving gNB decides to relocate the complete UE context, it will send the complete UE context to the receiving gNB. This is called SDT with UE context relocation.
  • the uplink SDT data is sent from the receiving gNB to the UPF.
  • the receiving gNB can send an RRCRelease message to the UE to release the UE back to the RRC inactive state or RRC idle state; if downlink non-SDT data or signaling arrives during the SDT process, or uplink non-SDT data arrives, the receiving gNB can Send an RRCResume message to the UE to return the UE to the RRC connected state.
  • the last serving gNB decides not to relocate the complete UE context, it sends a partial UE context (partial UE context) to the receiving gNB, which contains the SDT radio link control (RLC) context required to process SDT. information, this is called SDT without UE context relocation.
  • Last serving gNB maintains the packet data convergence protocol (PDCP) entity, and receiving gNB will establish the SDT-related RLC context and establish the UL/DL GTP-U tunnel required for SDT to transfer SDT data and/or signaling Forwarded to the last serving gNB, and then sent to the core network CN by the last serving gNB.
  • PDCP packet data convergence protocol
  • the receiving gNB After the SDT process is completed (the receiving gNB detects that there are no more data packets to transmit), the receiving gNB sends a retrieval context confirmation RETRIEVE UE CONTEXT CONFIRM message to notify the last serving gNB.
  • the last serving gNB controls whether to terminate the SDT process. If it decides to terminate, then Sending the retrieval context failure RETRIEVE UE CONTEXT FAILURE containing the encapsulated RRCRelease message to the receiving gNB, the receiving gNB will release the partial UE context (partial UE context) and send the RRCRelease message to the UE.
  • the last serving gNB will release the UE to the RRC inactive state, otherwise it will release it to the RRC idle state. It can be understood that the receiving gNB does not have a completed UE context at this time. After the gNB releases the UE to the inactive state, it can page the UE again to enter the RRC connected state for transmission.
  • Broadcast communication refers to a communication service model in which network equipment provides the same specific content data to all terminal devices in a certain geographical area at the same time.
  • terminal equipment that supports NR MBS broadcast can obtain broadcast communication services in the RRC connected state, RRC idle state, and RRC inactive state.
  • SIB21 contains the mapping relationship between frequencies and broadcast services provided in an area
  • the UE can determine which frequency provides which broadcast services in the area based on SIB21 to give priority to the one that can provide the UE wants.
  • the UE can camp on the cell with the frequency of the broadcast service to be received), and the UE can report MBS Interest Indication (MII) to the gNB in the RRC connection state to indicate that the UE is interested in receiving the frequency information of the broadcast (broadcast service).
  • MII MBS Interest Indication
  • frequency point ARFCN broadcast session identifier
  • TMGI broadcast session identifier
  • priority of broadcast compared with unicast, etc.
  • gNB learns the broadcast services that the UE is receiving or is interested in receiving through MII, and then performs appropriate scheduling according to the UE's capabilities to ensure that the broadcast and unicast scheduled at the same time do not exceed the UE's capabilities.
  • the UE if the UE supports broadcast (the UE reporting MII can indicate that the UE supports broadcast), the UE must support unicast physical downlink shared channel (PDSCH) and broadcast PDSCH through different time slots. TDM reception (can be understood as unicast data blocks and broadcast data blocks are received on different time slots). In addition, in the UE capability information, the UE will also report whether it supports TDM reception of unicast PDSCH and broadcast PDSCH in the same time slot, and FDM reception between unicast and broadcast in the same time slot. If the UE does not support receiving broadcast and unicast simultaneously in one time slot, the base station needs to schedule unicast and broadcast data in different time slots.
  • PDSCH physical downlink shared channel
  • broadcast PDSCH can be understood as unicast data blocks and broadcast data blocks are received on different time slots.
  • TDM reception can be understood as unicast data blocks and broadcast data blocks are received on different time slots.
  • the UE will also report whether it supports TDM reception of unicast PDSCH and broadcast
  • Multicast (or multicast) communication refers to the same service and the same specific content data being provided to a group of dedicated UEs at the same time (that is, not all UEs in the multicast service area are authorized to receive data).
  • Multicast communication services are delivered to the UE through a multicast session.
  • the UE can only receive multicast session data in the RRC connected state. If the UE joining the multicast session is in the RRC connected state, when the multicast session is activated, the gNB sends an RRCReconfiguration message with the MBS configuration related to the multicast session to the UE.
  • the gNB can move the UE to the RRC idle state or inactive state.
  • the gNB that supports MBS uses the group notification mechanism to notify the UE in the RRC idle or inactive state that there is multicast session data to be delivered.
  • CN controls the activation/deactivation of multicast. After CN paging, CN can also notify gNB of multicast activation and trigger RAN paging, or trigger RAN paging after multicast session data reaches gNB).
  • the UE receives After being notified to the group, the RRC connection is re-established with gNB.
  • the group notification is sent to the UE through a paging message.
  • the paging message used for the group notification contains the MBS session ID (TMGI) and is used to page all the RRC idle and RRC parties associated with an MBS multicast session. Inactive UE.
  • the UE determines that the paging message contains the TMGI of the multicast session that the UE has joined, and then the UE triggers RRC connection establishment or RRC connection recovery.
  • TMGI MBS session ID
  • a communication method is provided that enables terminal equipment to transmit small data without UE context relocation.
  • the network equipment corresponding to the serving cell can learn the multicast broadcast service information that the terminal equipment is interested in receiving or is receiving for reasonable scheduling. and data transmission, so that terminal devices can receive data from SDT and multicast broadcast services.
  • Figure 4 is a schematic flow chart of a communication method provided by an embodiment of the present application. This communication method is applied in the field of communication technology.
  • the communication method includes but is not limited to the following steps:
  • the terminal device performs small data transmission SDT with the first network device, and the terminal device is interested in receiving or is receiving the first broadcast service from the first network device.
  • the terminal device is in the RRC inactive state
  • the terminal device in the RRC inactive state performs SDT with the first network device
  • the terminal device is interested in receiving or is receiving the first broadcast service from the first network device.
  • the broadcast service that the terminal device is interested in receiving in this application may also refer to the broadcast service that the terminal device has not received but is to be received.
  • the terminal device in the embodiment of the present application is a device equipped with a processor that can be used to execute computer execution instructions. It can be a handheld terminal (such as a mobile phone, a tablet computer, etc.) or a vehicle-mounted terminal (such as an autonomous driving system). (wireless terminal, etc.), etc., specifically, it can also be the terminal device in the above-mentioned Figure 1 (including but not limited to any device among UE1 to UE8), used to execute the communication method in the embodiment of the present application to implement the terminal device In the small data transmission scenario without UE context relocation, data of SDT and multicast broadcast services can be received.
  • the first network device in the embodiment of the present application is a device equipped with a processor that can be used to execute computer execution instructions. It can be an access network device, such as a base station, a transmission point TRP, etc., or it can be a server. Specifically, It is the access network equipment in the above-mentioned Figure 1 (including but not limited to any equipment such as base station 1 and base station 2), used to perform the communication method in the embodiment of the present application to realize terminal equipment relocation without UE context. In small data transmission scenarios, data from SDT and multicast broadcast services can be received.
  • the terminal device sends the first information to the first network device, and accordingly, the first network device receives the first information sent by the terminal device.
  • the first information may be sent by the terminal device to the first network device during the SDT process, for example, it may be carried in random access message 3 (msg3) and sent through SRB1 or SRB2.
  • the random access message 3 may also include the RRC recovery request message RRCResumeRequest.
  • the first information may also be information sent by the terminal device on uplink resources dynamically scheduled by the first network device during the SDT process or on configured grant resources.
  • the first information includes information about the first broadcast service.
  • the first information may be multicast broadcast service (MBS) interest indication information (MBS Interest Indication, MII), which is used to indicate that the terminal device is interested in Information about the MBS broadcast service that is received or being received, such as the frequency of the MBS broadcast service, the identification information of the MBS broadcast service, the priority information of MBS broadcast compared with unicast and MBS multicast reception, etc.
  • MBS multicast broadcast service
  • MII MBS Interest Indication
  • the first information is used by the first network device to also provide the first broadcast service to the terminal device during SDT with the terminal device.
  • the terminal device in a scenario where the terminal device is in the RRC inactive state and performs SDT with the first network device, and the terminal device receives the first broadcast service from the first network device, it can report the third broadcast service to the first network device.
  • the SDT data and the data of the first broadcast service are sent in the way of frequency division multiplexing between time slots, etc., so that the terminal equipment can operate in a small time without UE context relocation.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • the broadcast service may refer to the MBS broadcast service (broadcast service)
  • the multicast service may refer to the MBS multicast service (multicast service).
  • SDT includes data and/or signaling of downlink/uplink SDT.
  • the first network device sends SDT and the first broadcast service on different time slots, and accordingly, the terminal device sends Receive SDT and the first broadcast service from the first network device on different time slots.
  • SDT can be understood as downlink SDT data (DownLink SDT data).
  • Receiving the data of SDT and the first broadcast service on different time slots can be understood/replaced as receiving the physical downlink shared channel (PDSCH) used to transmit SDT data and the physical downlink shared channel (PDSCH) used to transmit the first broadcast service on different time slots.
  • PDSCH or group common PDSCH group common physical downlink shared channel, GC-PDSCH that broadcasts service data.
  • the first network device learns that the terminal device is also interested in receiving or is receiving the first broadcast service during SDT with the first network device.
  • the first network device schedules SDT and the first Broadcast service, such as sending SDT data and the data of the first broadcast service through inter-slot time division multiplexing (inter-slot TDM), or sending SDT data through inter-slot frequency division multiplexing (inter-slot FDM) and data from the First Broadcasting Service, among others.
  • the SDT data may be sent to the terminal device in time slot 1
  • the data of the first broadcast service may be sent to the terminal device in time slot 2, so that the terminal device can receive data from the first network device in different time slots.
  • SDT and first broadcast service data avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal equipment.
  • the first network device (That is, the network equipment corresponding to the serving cell, which can also be called the receiving gNB of SDT, can learn the information of the first broadcast service received by the terminal equipment, thereby scheduling the data of SDT and the first broadcast service on different time slots, so that the terminal equipment can It does not have the ability to receive unicast data and broadcast data on the same time slot, and can also receive data from the SDT and the first broadcast service sent by the first network device on different time slots.
  • the first network device That is, the network equipment corresponding to the serving cell, which can also be called the receiving gNB of SDT, can learn the information of the first broadcast service received by the terminal equipment, thereby scheduling the data of SDT and the first broadcast service on different time slots, so that the terminal equipment can It does not have the ability to receive unicast data and broadcast data on the same time slot, and can also receive data from the SDT and the first broadcast service sent by the first network device on different time slots.
  • the terminal device when the terminal device sends the first information to the first network device, it can indicate that the terminal device supports receiving the MBS broadcast service, and the terminal device must support the PDSCH for transmitting unicast data and the PDSCH for transmitting MBS broadcast data.
  • /GC-PDSCH inter-slot time division multiplexing (inter-slot TDM) reception so the first network device sends SDT and first broadcast service data according to inter-slot time division multiplexing, which can ensure that the terminal device can perform the SDT process
  • the first broadcast service is received in the network to avoid bit errors and/or packet loss, thereby ensuring the service quality of SDT and MBS broadcast services.
  • the first network device When the terminal device does not support receiving unicast data and MBS broadcast data in the same time slot, in the SDT scenario without context relocation, the first network device does not have UE capability information. If the first network device does not know that the terminal device is receiving First broadcast service, when the first network device schedules/sends SDT data (SDT can be understood as a unicast transmission method) and the data of the first broadcast service in the same time slot, it will cause the terminal device to be unable to receive SDT and broadcast data, or the terminal device can only receive one of SDT or broadcast data, causing data errors and/or packet loss, affecting service reception quality.
  • SDT can be understood as a unicast transmission method
  • the terminal device sends the first information to the first network device when it is determined that certain conditions are met.
  • the terminal device Before the terminal device sends the first information to the first network device, the terminal device also receives the second information sent by the first network device and/or the third information sent by the second network device, and based on the second information and/or the third information Third information, determine to send the first information to the first network device.
  • the first information at this time includes information about the first broadcast service.
  • the first information may be MII, which is used to indicate information about the MBS broadcast service that the terminal device is interested in receiving or is receiving, such as the frequency of the MBS broadcast service, the frequency of the MBS broadcast service, and the frequency of the MBS broadcast service. Service identification information, priority information of MBS broadcast compared with unicast and MBS multicast reception, etc.
  • the terminal device in the scenario where the terminal device is in the RRC inactive state and performs SDT with the first network device, and the terminal device receives the first broadcast service from the first network device, it can perform the SDT according to the first broadcast service sent by the first network device.
  • Determine the reporting of the first information it can also be understood that the first network device controls whether to allow the terminal device to report the first information by sending the second information and/or the second network device sends the third information.
  • the second information and the third information may be the same information or different information.
  • the terminal device Before the terminal device sends the first information to the first network device, the terminal device also receives the fourth information sent by the first network device and/or the fifth information sent by the second network device, and based on the fourth information and/or the fifth information Five information, determining to send the first information to the first network device.
  • the first information at this time includes temporary mobile group identity (TMGI) information of the first broadcast service.
  • TMGI temporary mobile group identity
  • the terminal device in the scenario where the terminal device is in the RRC inactive state and performs SDT with the first network device, and the terminal device receives the first broadcast service from the first network device, it can perform the SDT according to the first broadcast service sent by the first network device.
  • Four pieces of information are used to determine that the first information sent contains the TMGI information of the first broadcast service, or the fifth information sent by the second network device is used to determine that the first information sent includes the TMGI information of the first broadcast service, or It is determined according to the fourth information sent by the first network device and the fifth information sent by the second network device that the first information sent contains the TMGI information of the first broadcast service.
  • the fourth information and the fifth information may be the same information, It can also be different information.
  • the third information and/or the fifth information may be carried in the RRC release message.
  • the third information and/or the fifth information can be an indication bit (such as 1 bit) in the RRC release message, and the third information and the fifth information can be different information, indicated by two independent bits. , or the same information can be indicated by the same bit.
  • the RRC release message contains the third information, or the bit position corresponding to the third information is 1, indicating that the terminal device is allowed to report the first information (specifically It may be MII) or indicates that the terminal device is allowed to report the first information in the RRC inactive state, or indicates that the terminal device is allowed to report the first information during the SDT process.
  • allowing reporting can also be understood as the second network device supports receiving the first information reported from the terminal device in the RRC inactive state, or the first information reported from the terminal device during the SDT process.
  • the RRC release message does not contain the third information, or the bit position corresponding to the third information is 0, indicating that the terminal device is not allowed to report/th
  • the second network device does not support receiving the first information (specifically, it may be MII), or indicates that the terminal device is not allowed/supported to receive the RRC inactive state to report the first information, or indicates that it is not allowed/unsupported to receive the terminal device during the SDT process. Report the first information.
  • the setting and meaning of the fifth information refer to the above-mentioned third information.
  • the RRC release message contains the fifth information or the bit position corresponding to the fifth information is 1, it indicates that the first information reported by the terminal device is allowed.
  • the TMGI information containing the broadcast service/the second network device supports receiving the first information reported by the terminal device contains the TMGI information of the broadcast service, or the first information reported by the terminal device indicating that it is allowed/supported to receive RRC inactive state contains the broadcast service TMGI information, or indicates that the first information reported by the receiving terminal device during the SDT process is allowed/supported to include the TMGI information of the broadcast service.
  • the fifth information and the third information are the same information, or when the fifth information and the third information are the same indication bit/bit
  • the RRC release message contains the information, or the bit/ The indication position is 1, indicating that the terminal device is allowed to report/the second network device supports receiving the first information (specifically, it may be MII), and the first information may include TMGI information of the broadcast service.
  • the fifth information and the third information are the same information, or when the fifth information and the third information are the same indication bit/bit, when the RRC release message does not contain the information or the bit /When the indication position is 0, it indicates that the terminal device is not allowed to report the first information (specifically, it may be MII) including the TMGI information of the broadcast service.
  • the first information specifically, it may be MII
  • the third information/fifth information please refer to the above description of the third information/fifth information and will not be repeated here.
  • the second network device can control the reporting of the first information by the terminal device through the third information and/or the fifth information, and has better backward compatibility.
  • the RRC release message may not include the first information.
  • the terminal device will not report the first information; for upgraded network devices that can support RRC inactive terminal devices reporting the first information/terminal devices reporting the first information during the SDT process, The third information and/or the fifth information may be included in the RRC release message.
  • the second information, and/or the third information, and/or the fourth information, and/or the fifth information may include system information (System Information, SI); alternatively, the second information, and/or the third information, and/or the fourth information, and/or the fifth information may be transmitted in the form of a System Information Block (SIB).
  • SI System Information Block
  • the second information and/or the third information may include the first system information; or the second information and/or the third information may be transmitted in the form of a first system information block.
  • the first system information is used to indicate the mapping relationship between the multicast broadcast service and frequency, for example, it may correspond to the system information block SIB21; or, the first system information is used to indicate the multicast broadcast service control channel (MBS control channel, MCCH ) configuration parameters, for example, may correspond to system information block SIB20.
  • MMS control channel MCS control channel
  • the fourth information and/or the fifth information may include second system information; or the fourth information and/or the fifth information may be transmitted in the form of a second system information block.
  • the second system information is used to indicate the mapping relationship between the multicast broadcast service and the frequency, for example, it may correspond to the system information block SIB21; or the second system information is used to indicate the multicast broadcast service control channel (MBS control channel, MCCH ) configuration parameters, for example, may correspond to system information block SIB20.
  • MMS control channel MCS control channel
  • the control sends the first message.
  • the terminal device determines that the conditions described in at least one of the following ways are met:
  • the first serving cell associated with the second network device provides the system information block SIB21, and the terminal device determines that the first information can be sent to the first network device.
  • the first serving cell associated with the second network device provides the system information block SIB21, and the serving cell (associated with the first network device) where the terminal device currently resides provides the system information block SIB20. Then the terminal device determines that it can send the first network device to the first network device.
  • a piece of information, and the first information may include TMGI information of the broadcast service.
  • the first serving cell associated with the second network device providing SIB21 can be understood as the first serving cell being a cell that can provide SIB21, and the first serving cell may be the serving cell where the terminal device once camped.
  • the terminal device stores a list of cells that broadcast SIB21, and the terminal device determines whether the first serving cell is in the above-mentioned cell list based on the above-mentioned cell list. If the first serving cell is in the above-mentioned list, then the first serving cell is in the above-mentioned list.
  • the serving cell can provide SIB21.
  • the fact that the serving cell provides SIB20 can be understood to mean that the SIB1 broadcast by the serving cell contains the scheduling information of SIB20, or it can be understood that the serving cell can provide SIB20.
  • This application does not limit whether the serving cell is broadcasting SIB20.
  • the serving cell may or may not be broadcasting SIB20.
  • the first serving cell associated with the second network device provides SIB21, and the serving cell (associated with the first network device) where the terminal device currently resides provides SIB21, then the terminal device determines that the first information can be sent to the first network device.
  • the first serving cell associated with the second network device provides SIB21, and the serving cell (associated with the first network device) where the terminal device currently resides provides SIB21, and the serving cell where the terminal device currently resides provides SIB20, then the terminal device determines that it can
  • the first network device sends first information, and the first information may include TMGI information of the broadcast service.
  • SIB21 provided by the first serving cell associated with the second network device are as described in manner 1, which will not be described again here.
  • the terminal device After receiving the RRC release message from the second network device containing the third information, and the serving cell (associated with the first network device) where the terminal device currently resides provides SIB21, the terminal device determines that it can send the third information to the first network device. a message.
  • the RRC release message received from the second network device contains the third information, and the serving cell (associated with the first network device) where the terminal device currently resides provides SIB21, and the RRC release message from the second network device is received. contains the fifth information, the terminal device determines that the first information can be sent to the first network device, and the first information can include the TMGI information of the broadcast service, and the third information and the fifth information are different information.
  • the third information and the fifth information are the same information.
  • the RRC release message received from the second network device contains the third information (or fifth information), and the serving cell where the terminal device currently resides (associated with the first network device) provides SIB21, then the terminal device determines that the first information can be sent to the first network device.
  • the third information and the fifth information are the same information.
  • the RRC release message received from the second network device contains the third information (or fifth information), and the serving cell where the terminal device currently resides (associated with the first network device) provides SIB21, and the serving cell where the terminal device currently resides provides SIB20, then the terminal device determines that it can send the first information to the first network device, and the first information can include the TMGI information of the broadcast service.
  • the third information and the fifth information are the same information.
  • the RRC release message received from the second network device contains the third information (or fifth information), and the first serving cell associated with the second network device provides SIB21 (The implementation can be as described in the above-mentioned mode 1 (not repeated here), and the serving cell (associated with the first network device) where the terminal device currently resides provides SIB21, then the terminal device determines that it can send the first network device to the first network device. a message.
  • the third information and the fifth information are the same information.
  • the RRC release message received from the second network device contains the third information (or fifth information), and the first serving cell associated with the second network device provides SIB21 ( The implementation can be as described in the above-mentioned mode 1 (no details will be described here), and the serving cell (associated with the first network device) where the terminal device currently resides provides SIB21, and the serving cell where the terminal device currently resides provides SIB20, then The terminal device determines that the first information can be sent to the first network device, and the first information can include TMGI information of the broadcast service.
  • the terminal device determines that the first information can be sent to the first network device.
  • the serving cell (associated with the first network device) where the terminal device currently resides provides SIB21, and the terminal device receives the RRC release message from the second network device that contains the third information (or fifth information), then the terminal device determines that it can
  • the first information is sent to the first network device, and the first information may include TMGI information of the broadcast service, and the third information and the fifth information are the same information.
  • the above-mentioned second network device is a device equipped with a processor that can be used to execute computer execution instructions. It can be an access network device, such as a base station, a transmission point TRP, etc., or it can be a server. Specifically, it can be The access network equipment in Figure 1 above (including but not limited to any equipment such as base station 1 and base station 2) is used to perform the communication method in the embodiment of the present application to realize terminal equipment without UE context relocation. In small data transmission scenarios, data from SDT and multicast broadcast services can be received.
  • the second network device is a network device that connects the terminal device and the core network device. It can be understood that the connection between the terminal device and the core network device may be a non-access stratum (NAS) connection.
  • NAS non-access stratum
  • FIG. 5 is a schematic flowchart of another communication method provided by an embodiment of the present application. It can be understood that steps S503 to S508 in the embodiment of the present application can be regarded as reasonable modifications or supplements of the embodiment in Figure 4; or, it can be understood that the communication method in the embodiment of the present application can also be regarded as Embodiments that can be executed independently are not limited by this application.
  • the communication method provided by the embodiment of this application is applied in the field of communication technology.
  • the communication method includes but is not limited to the following steps:
  • the terminal device performs small data transmission SDT with the first network device, and the terminal device is interested in receiving or is receiving the first broadcast service from the first network device.
  • the terminal device sends the first information to the first network device, and accordingly, the first network device receives the first information sent by the terminal device.
  • step S402 It is consistent with the above step S402 and will not be described again here.
  • the terminal device in the embodiment of the present application is a device equipped with a processor that can be used to execute computer execution instructions. It can be a handheld terminal (such as a mobile phone, a tablet computer, etc.) or a vehicle-mounted terminal (such as an autonomous driving system). (wireless terminal, etc.), etc., specifically, it can also be the terminal device in the above-mentioned Figure 1 (including but not limited to any device among UE1 to UE8), used to execute the communication method in the embodiment of the present application to implement the terminal device In the small data transmission scenario without UE context relocation, data of SDT and multicast broadcast services can be received.
  • the first network device and the second network device in the embodiment of the present application are devices equipped with a processor that can be used to execute computer execution instructions. They can be access network devices, such as base stations, transmission points TRP, etc., or they can It is a server, specifically it can be the access network equipment in Figure 1 (including but not limited to any equipment such as base station 1 and base station 2), used to execute the communication method in the embodiment of the present application to implement the terminal equipment in In a small data transmission scenario without UE context relocation, data from SDT and multicast broadcast services can be received.
  • S503 The first network device sends the first request message to the second network device.
  • the second network device receives the first request message sent by the first network device.
  • the first network device sends a first request message to the second network device, where the first request message is used to request to obtain context information of the terminal device for SDT.
  • the second network device sends UE context information to the first network device.
  • the first network device receives the UE context information sent by the second network device.
  • the second network device sends partial context information of the terminal device to the first network device in response to the first request message.
  • the first network device receives the partial context information of the terminal device sent by the second network device in response to the first request message. information.
  • the part of the context information includes seventh information, the seventh information is used to indicate the second broadcast service received by the terminal device.
  • the second network device determines that the terminal device does not support receiving data of SDT and MBS broadcast services in the same time slot, then the second network device includes the seventh information in the partial context information of the terminal device; the second network device determines If the terminal device supports receiving data of SDT and MBS broadcast services in the same time slot, the second network device does not include the seventh information in the partial context information of the terminal device.
  • the first network device performs SDT with the terminal device in the RRC inactive state, and the first network device provides the second broadcast service for the terminal device in the RRC inactive state
  • the first network device By sending a first request message to the second network device and receiving the seventh information in the partial context information of the terminal device provided by the second network device, it can be learned that the terminal device is During the process of performing SDT, you may also be interested in receiving or receiving a second broadcast service, so that the first network device can appropriately schedule SDT and the second broadcast service, for example, sending SDT data and data via inter-slot time division multiplexing.
  • the data of the first broadcast service, or the SDT data and the data of the first broadcast service are sent through frequency division multiplexing between time slots, etc., so that the terminal device can also transmit data in small data transmission scenarios without UE context relocation.
  • Receive data from SDT and the second broadcast service to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • the first network device sends the first information to the second network device, and accordingly, the second network device receives the first information sent by the first network device.
  • step S502 the first network device receives the first information sent by the terminal device.
  • the first network device sends the first information to the second network device.
  • the second network device is a network device that connects the terminal device and the core network device. It can be understood that the connection between the terminal device and the core network device may be a non-access stratum (NAS) connection. Or it can be understood that the second network device is a network device that has an NGAP (NG Application Protocol) association relationship between the terminal device and the core network device.
  • NAS non-access stratum
  • NGAP NG Application Protocol
  • the first information may be an RRC message.
  • the first network device receives the first information sent by the terminal device, since the first network device does not have complete context information of the terminal device, for example, the first network device only Having the RLC context of the terminal device, but not having the PDCP and RRC related information (such as PDCP context) of the terminal device, and therefore unable to interpret the first information, the first network device transmits the first information (specifically, it may be a bearer of the first RLC packets of information, such as RLC SDU or PDCP PDU) are forwarded to the second network device.
  • the second network device has complete context information of the terminal device.
  • the second network device has PDCP and RRC related information (such as PDCP context) of the terminal device. Therefore, the second network device can interpret based on the complete context information of the terminal device.
  • Sixth information is obtained from the first information forwarded by the first network device and sent to the first network device.
  • the sixth information is used to indicate the first broadcast service.
  • the sixth information is obtained based on the first information.
  • the sixth information and the first information may be the same information.
  • the sixth information is sent by the second network device to the first network device through an interface between network devices (for example, the Xn interface).
  • the first information; the sixth information and the first information can also be different information.
  • the sixth information contains part or all of the first information, which is determined/generated by the second network device through the interface between network devices (for example, Xn interface) is sent to the first network device.
  • the first information includes TMGI information of the first broadcast service, where the TMGI information may include associated public land mobile network (PLMN) information, such as PLMN-index or PLMN -Identity (PLMN identity can also be referred to as PLMN ID).
  • PLMN information is PLMN-index
  • the second network device translates or converts the PLMN-index in the first information into PLMN-identity and then sends it to the first network device through the sixth information, that is, The sixth information sent by the second network device is generated by replacing the PLMN-index in the first information with PLMN-identity.
  • the PLMNs of the first network device and the second network device are different at the same time, or that the order of the PLMNs in the PLMN list (for example, plmn-IdentityInfoList) indicated in SIB1 is different between the cell of the first network device and the cell of the second network device.
  • this causes a problem of misalignment of the understanding of PLMN-index by the first network device and the second network device (that is, the same plmn-index corresponds to different PLMNs in the first network device and the second network device).
  • the second network device sends the sixth information to the first network device, and accordingly, the first network device receives the sixth information sent by the second network device.
  • the second network device can decode the first information sent by the first network device to obtain sixth information, and the sixth information is used to indicate the first broadcast service.
  • the second network device sends the sixth information to the first network device, and accordingly, the first network device receives the sixth information sent by the second network device.
  • the first network device can learn that the terminal device is still receiving the first broadcast service during the SDT process, so that the first network device can respond to the SDT and the first broadcast service. Scheduling enables terminal devices to receive SDT and broadcast service data in small data transmission scenarios without UE context relocation.
  • the second network device determines that the terminal device does not support receiving data of SDT and MBS broadcast services in the same time slot, then the second network device sends the sixth information to the first network device; the second network device determines that the terminal device If data of SDT and MBS broadcast services are supported in the same time slot, the second network device does not send the sixth information.
  • the first network device when receiving the sixth information, ignores the seventh information.
  • the first network device when the first network device receives the sixth information, regardless of whether the first network device receives the seventh information, the first network device will perform SDT and the corresponding first broadcast service based on the sixth information. Scheduling.
  • the broadcast service indicated in the sixth information shall prevail.
  • the seventh information indicates that the terminal device receives broadcast service 1, broadcast service 2, and broadcast service 3.
  • the sixth information indicates that the terminal device receives broadcast service 2 and broadcast service 4, then the first network device believes that the broadcast services that the terminal device is interested in receiving or is receiving are broadcast service 2 and broadcast service 4, and the terminal device is not receiving broadcasts.
  • the first network device when the first network device does not receive the sixth information and receives the seventh information, the first network device will schedule the SDT and the corresponding second broadcast service according to the seventh information. , so that the terminal device can also receive the data of SDT and the second broadcast service in a small data transmission scenario without UE context relocation, avoiding bit errors and/or packet loss caused by scheduling exceeding the receiving capability of the terminal device.
  • the second network device sends the eighth information and/or the ninth information to the first network device.
  • the first network device receives the eighth information and/or the ninth information sent by the second network device.
  • the eighth information is used to indicate whether the terminal device supports frequency division multiplexing (FDM) reception of one or more unicast data and one or more broadcast data in the same time slot.
  • FDM frequency division multiplexing
  • the information is used to indicate whether the terminal device supports frequency division multiplexing FDM reception of M unicast data and N broadcast data in the same time slot.
  • M and N are integers greater than or equal to 1.
  • the ninth information is used to indicate whether the terminal device supports or does not support time division multiplexing (TDM) reception of one or more unicast data and one or more broadcast data in the same time slot.
  • TDM time division multiplexing
  • the ninth information is used to indicate Indicates whether the terminal device supports or does not support time division multiplexing TDM reception of P unicast data and Q broadcast data in the same time slot.
  • P and Q are integers greater than or equal to 1.
  • the eighth information is also used to indicate whether the terminal device supports or does not support frequency division multiplexing FDM of M unicast data and N broadcast data in the same time slot on the first frequency band or the carrier of the first frequency band.
  • M and N are integers greater than or equal to 1; the eighth information includes the identification of the first frequency band;
  • the ninth information is also used to indicate whether the terminal device supports or does not support time division multiplexing TDM reception of P unicast data and Q broadcast data in the same time slot on the second frequency band or the carrier of the second frequency band.
  • P and Q are integers greater than or equal to 1; the ninth information includes the identifier of the second frequency band; the first frequency band and the second frequency band may be the same frequency band or different frequency bands.
  • the second network device sends the eighth information and/or the ninth information to the first network device, so that the first network device can learn the terminal device's ability to receive SDT data and broadcast data in parallel, thereby scheduling data in a more flexible manner. For example, when the terminal device supports receiving one unicast PDSCH and one broadcast GC-PDSCH in the same time slot in a frequency division multiplexing manner, the first network device can receive a unicast PDSCH and a broadcast GC-PDSCH in the same time slot in a frequency division multiplexing manner. Send 1 unicast PDSCH and 1 broadcast GC-PDSCH.
  • the terminal device when the terminal device supports receiving one unicast PDSCH and one broadcast GC-PDSCH in the same time slot in a time division multiplexing manner, the first network device can send one in the same time slot in a time division multiplexing manner.
  • the first network device provides SDT and the first broadcast service to the terminal device.
  • the terminal device receives the SDT and the first broadcast service from the first network device.
  • the first network device schedules SDT and the first broadcast service, for example, sends the SDT data and the data of the first broadcast service in an inter-slot time division multiplexing manner, or sends the SDT data and the first broadcast service in an inter-slot frequency division multiplexing manner.
  • Data of a broadcast service, etc. so that the terminal device can receive SDT and data of the first broadcast service from the first network device on different time slots.
  • the network device corresponding to the serving cell can learn the multicast broadcast service information that the terminal device is interested in receiving or is receiving for reasonable scheduling. and data transmission, so that terminal devices can receive data from SDT and multicast broadcast services.
  • FIG. 6 is a schematic flowchart of another communication method provided by an embodiment of the present application. It can be understood that the embodiments of the present application can be regarded as reasonable modifications or supplements of the embodiments in Figure 4 and Figure 5; or, it can be understood that the communication method in the embodiments of the present application can also be regarded as being able to be executed independently. embodiment, this application does not limit this.
  • the communication method provided by the embodiment of this application is applied in the field of communication technology.
  • the communication method includes but is not limited to the following steps:
  • the terminal device performs small data transmission SDT with the first network device, and the terminal device joins the first multicast session from the first network device.
  • the terminal device is in the RRC inactive state
  • the terminal device in the RRC inactive state performs SDT with the first network device
  • the terminal device joins the first multicast session from the first network device.
  • a multicast service is provided and capable of receiving a first multicast session from a first network device.
  • the terminal device is receiving the first multicast session from the first network device.
  • the terminal device in the embodiment of the present application is a device equipped with a processor that can be used to execute computer execution instructions. It can be a handheld terminal (such as a mobile phone, a tablet computer, etc.) or a vehicle-mounted terminal (such as an autonomous driving system). (wireless terminal, etc.), etc., specifically, it can also be the terminal device in the above-mentioned Figure 1 (including but not limited to any device among UE1 to UE8), used to execute the communication method in the embodiment of the present application to implement the terminal device In the small data transmission scenario without UE context relocation, data of SDT and multicast broadcast services can be received.
  • the first network device and the second network device in the embodiment of the present application are devices equipped with a processor that can be used to execute computer execution instructions. They can be access network devices, such as base stations, transmission points TRP, etc., or they can It is a server, specifically it can be the access network equipment in Figure 1 (including but not limited to any equipment such as base station 1 and base station 2), used to execute the communication method in the embodiment of the present application to implement the terminal equipment in In a small data transmission scenario without UE context relocation, data from SDT and multicast broadcast services can be received.
  • the first network device sends a second request message to the second network device.
  • the second network device receives the second request message sent by the first network device.
  • the first network device sends a second request message to the second network device, where the second request message is used to request to obtain context information of the terminal device for SDT.
  • the first network device may be providing the first multicast session to the terminal device, or may not be providing the first multicast session to the terminal device, and this embodiment of the present application does not limit this.
  • the second network device sends UE context information to the first network device.
  • the first network device receives the UE context information sent by the second network device.
  • the second network device sends partial context information (UE context information) of the terminal device to the first network device in response to the second request message.
  • the first network device receives the information sent by the second network device in response to the second request message.
  • Part of the context information of the terminal device UE context information
  • the UE context information includes tenth information
  • the tenth information is used to indicate the information of the first multicast session joined by the terminal device
  • the first network device can send the data of the first multicast session to the terminal device according to the tenth information.
  • the second network device determines that the first multicast session is activated.
  • the first multicast session indicated by the tenth information is an activated multicast session.
  • the second network device determines that the first network device is a network device that supports providing RRC inactive multicast.
  • the second network device learns through an interface between network devices (for example, the Xn interface) that the first network device supports providing multicast services for RRC inactive terminal devices.
  • the first network device in the scenario where the first network device performs SDT with the terminal device in the RRC inactive state, and the first network device provides the first multicast session for the terminal device in the RRC inactive state, the first network device The device can learn that the terminal device has also joined the first group during the SDT process by sending a second request message to the second network device and receiving the tenth information in the partial context information of the terminal device provided by the second network device. broadcast session, so that the first network device can appropriately schedule the data of the SDT and the first multicast session, for example, send the SDT data and the data of the first multicast session through time division multiplexing between time slots, or send the data of the first multicast session through time slots.
  • the SDT data and the data of the first multicast session are sent through frequency division multiplexing, etc., so that the terminal device can also receive the SDT and the data of the first multicast session in a small data transmission scenario without UE context relocation. data to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • multicast service may refer to MBS multicast service (multicast service), and SDT includes data and/or signaling of downlink/uplink SDT.
  • MBS multicast service multicast service
  • SDT includes data and/or signaling of downlink/uplink SDT.
  • the second network device sends the eleventh information and/or the twelfth information to the first network device.
  • the first network device receives the eleventh information and/or the twelfth information sent by the second network device.
  • the eleventh information is used to indicate whether the terminal device supports frequency division multiplexing FDM reception of one or more unicast data and one or more multicast data in the same time slot.
  • the eleventh information Used to indicate whether the terminal device supports frequency division multiplexing FDM reception of M unicast data and N multicast data in the same time slot.
  • M and N are integers greater than or equal to 1.
  • the twelfth information is used to indicate that the terminal device supports or does not support time division multiplexing TDM reception of one or more unicast data and one or more multicast data in the same time slot.
  • the twelfth information is used to indicate The terminal equipment supports or does not support time division multiplexing TDM reception of P unicast data and Q multicast data in the same time slot.
  • P and Q are integers greater than or equal to 1.
  • the eleventh information is also used to indicate whether the terminal device supports or does not support M unicast data on the first frequency band or the carrier of the first frequency band.
  • the twelfth information is also used to indicate whether the terminal device supports or does not support time division multiplexing of P unicast data and Q multicast data in the same time slot on the second frequency band or the carrier of the second frequency band.
  • P and Q are integers greater than or equal to 1; the twelfth information includes the identifier of the second frequency band; the first frequency band and the second frequency band may be the same frequency band or different frequency bands.
  • the second network device sends the eleventh information and/or the twelfth information to the first network device, so that the first network device can learn the terminal device's ability to receive SDT data and multicast data in parallel, thereby scheduling data in a more flexible manner.
  • the first network device may use frequency division multiplexing in the same time slot.
  • the method sends one unicast PDSCH and one multicast GC-PDSCH.
  • the terminal device when the terminal device supports receiving 1 unicast PDSCH and 1 multicast GC-PDSCH in the same time slot in a time division multiplexing manner, the first network device can send 1 in the same time slot in a time division multiplexing manner.
  • unicast PDSCH and 1 multicast GC-PDSCH when the terminal device supports receiving 1 unicast PDSCH and 1 multicast GC-PDSCH in the same time slot in a time division multiplexing manner, the first network device can send 1 in the same time slot in a time division multiplexing manner.
  • unicast PDSCH and 1 multicast GC-PDSCH when the terminal device supports receiving 1 unicast PDSCH and 1 multicast GC-PDSCH in the same time slot in a time division multiplexing manner.
  • unicast data can be understood as/replaced as PDSCH used to transmit unicast data, or PDSCH scrambled by the cell's wireless network temporary identifier (Cell Radio Network Temporary Identifier, cell RNTI); Multicast data can be understood/replaced as PDSCH/GC-PDSCH used to transmit MBS multicast data, or PDSCH scrambled by Group Radio Network Temporary Identifier (G-RNTI).
  • G-RNTI Group Radio Network Temporary Identifier
  • the time division multiplexing/frequency division multiplexing of unicast data and multicast data in the same time slot (intra-slot) can be understood as the unicast PDSCH and MBS multicast GC-PDSCH in the same time slot (intra-slot). ) time division multiplexing/frequency division multiplexing.
  • the first network device in the scenario where the first network device performs SDT with the terminal device in the RRC inactive state, and the first network device provides a multicast session for the terminal device in the RRC inactive state, the first network device can According to the eleventh information and/or the twelfth information, it is learned that the terminal device supports or does not support frequency division multiplexing TDM reception of one or more unicast data and one or more multicast data in the same time slot or Time division multiplexing TDM reception, so that the first network device can properly schedule the data of SDT and multicast sessions, so that the terminal device can also receive SDT and multicast sessions in a small data transmission scenario without UE context relocation. data to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • the first network device provides SDT and the data and/or signaling of the first multicast session to the terminal device.
  • the terminal device receives the SDT and the first multicast session from the first network device.
  • One possible implementation method is that the first network device schedules the data and/or signaling of the SDT and the first multicast session through inter-slot time division multiplexing (inter-slot TDM), such as sending the data and/or signaling to the terminal device on time slot 1.
  • Inter-slot TDM inter-slot time division multiplexing
  • Send SDT data, and send data and/or signaling of the first multicast session to the terminal device on time slot 2 so that the terminal device can receive SDT and the first multicast from the first network device on different time slots. session data and/or signaling.
  • the terminal device may be receiving the first multicast session from the first network device, or may not have started receiving the first multicast session from the first network device.
  • This embodiment of the present application is There is no restriction on this.
  • SDT in the embodiment of this application can be understood as downlink SDT data (DL SDT data).
  • Sending the data of SDT and the first multicast session on different time slots can be understood as/replaced as sending the PDSCH of SDT and sending the PDSCH/GC-PDSCH of the first multicast session on different time slots, or it can be understood as using time slots.
  • the PDSCH of SDT and the PDSCH/GC-PDSCH of the first multicast session are sent in an inter-slot TDM manner.
  • the first network device i.e., the serving cell
  • the corresponding network device which may also be called the receiving gNB of SDT, can learn the information of the first multicast session received by the terminal device, so that it can schedule the data and/or information of the SDT and the first multicast session on different time slots. order, so that even if the terminal device does not have the ability to receive unicast data and multicast data on the same time slot, it can still receive the SDT sent by the first network device and the first multicast session on different time slots. data and/or signaling to avoid bit errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • FIG. 7 is a schematic flowchart of another communication method provided by an embodiment of the present application. It can be understood that the embodiments of the present application can be regarded as reasonable modifications or supplements of the embodiments in FIG. 4, FIG. 5, and FIG. 6; or, it can be understood that the communication method in the embodiment of the present application can also be regarded as Embodiments that can be executed independently are not limited by this application.
  • the communication method provided by the embodiment of this application is applied in the field of communication technology.
  • the communication method includes but is not limited to the following steps:
  • S701 The terminal device performs small data transmission SDT with the first network device, and the terminal device joins the third SDT from the first network device. Two multicast sessions.
  • the terminal device is in the RRC inactive state
  • the terminal device in the RRC inactive state performs SDT with the first network device
  • the terminal device joins the second multicast session from the first network device.
  • the terminal device in the embodiment of the present application is a device equipped with a processor that can be used to execute computer execution instructions. It can be a handheld terminal (such as a mobile phone, a tablet computer, etc.) or a vehicle-mounted terminal (such as an autonomous driving system). (wireless terminal, etc.), etc., specifically, it can also be the terminal device in the above-mentioned Figure 1 (including but not limited to any device among UE1 to UE8), used to execute the communication method in the embodiment of the present application to implement the terminal device In the small data transmission scenario without UE context relocation, data of SDT and multicast broadcast services can be received.
  • the first network device and the second network device in the embodiment of the present application are devices equipped with a processor that can be used to execute computer execution instructions. They can be access network devices, such as base stations, transmission points TRP, etc., or they can It is a server, specifically it can be the access network equipment in Figure 1 (including but not limited to any equipment such as base station 1 and base station 2), used to execute the communication method in the embodiment of the present application to implement the terminal equipment in In a small data transmission scenario without UE context relocation, data from SDT and multicast broadcast services can be received.
  • the terminal device sends the thirteenth information to the first network device, and accordingly, the first network device receives the thirteenth information sent by the terminal device.
  • the thirteenth information includes information of the second multicast session.
  • the thirteenth information may be TMGI information of the second multicast session.
  • the thirteenth information is used by the first network device to provide data and/or signaling of the second multicast session to the terminal device while performing SDT with the terminal device.
  • the terminal device in the scenario where the terminal device is in the RRC inactive state and performs SDT with the first network device, and the terminal device receives the second multicast session from the first network device, it can report to the first network device
  • the thirteenth information allows the first network device to know that the terminal device is still receiving data and/or signaling of the second multicast session during SDT, so that the first network device can perform SDT and the second multicast session.
  • Appropriate scheduling such as sending SDT data and the data of the second multicast session through time division multiplexing between slots, or sending SDT data and the data of the second multicast session through frequency division multiplexing between slots, etc.
  • the terminal device can receive the data and/or signaling of SDT and the second multicast session in a small data transmission scenario without UE context relocation, thereby avoiding bit errors caused by scheduling exceeding the receiving capability of the terminal device. and/or packet loss.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • the first network device is the network device corresponding to the serving cell where the terminal device is camped in the RRC inactive state, and may also be the receiving gNB that performs SDT with the terminal device.
  • multicast service may refer to MBS multicast service (multicast service), and SDT includes data and/or signaling of downlink/uplink SDT.
  • MBS multicast service multicast service
  • SDT includes data and/or signaling of downlink/uplink SDT.
  • the thirteenth information may be carried in a media access control control element (MAC CE) or a radio resource control RRC message.
  • MAC CE media access control control element
  • RRC message radio resource control
  • the first network device can interpret the thirteenth information to obtain the information of the multicast session (TMGI of the multicast session) joined by the terminal device.
  • TMGI information of the multicast session
  • the first network device when the thirteenth information is carried in the RRC message, the first network device also needs to forward the thirteenth information to the second network device, and the second network device interprets the thirteenth information to obtain the multicast that the terminal device joins.
  • the second network device then sends the decoded information of the multicast session (TMGI of the multicast session) that the terminal device joins to the first network device.
  • TMGI decoded information of the multicast session
  • the terminal device in the scenario where the terminal device performs SDT with the first network device in the RRC inactive state, and the terminal device receives data from the second multicast session of the first network device, the terminal device sends a message to the first network device.
  • the device sends a MAC CE or RRC message.
  • the MAC CE or RRC message includes the thirteenth information used to indicate the second multicast session, so that the first network device knows that the terminal device has also joined the second multicast during the SDT process. session, so that the first network device can properly schedule the data of the SDT and the second multicast session, so that the terminal device can also receive the SDT and the second multicast session in a small data transmission scenario without UE context relocation. data to avoid data errors and/or packet loss caused by scheduling beyond the receiving capabilities of the terminal device.
  • the first network device provides data and/or signaling of SDT and the second multicast session to the terminal device.
  • the terminal device receives the SDT and the second multicast session sent by the first network device.
  • the first network device learns that the terminal device has also joined the second multicast session during the SDT with the first network device.
  • the first network device uses inter-slot time division multiplexing (inter-slot TDM) schedules the data and/or signaling of SDT and the second multicast session, such as sending the data of SDT to the terminal device on time slot 1 and sending the data of the second multicast session to the terminal device on time slot 2.
  • inter-slot TDM inter-slot time division multiplexing
  • the data and/or signaling enables the terminal device to receive data and/or signaling from the SDT of the first network device and the second multicast session on different time slots.
  • SDT in the embodiment of this application can be understood as downlink SDT data (DL SDT data).
  • Sending the data of SDT and the second multicast session on different time slots can be understood as/replaced as sending the PDSCH of SDT and sending the PDSCH/GC-PDSCH of the second multicast session on different time slots, or it can be understood as using time slots.
  • the PDSCH of SDT and the PDSCH/GC-PDSCH of the second multicast session are sent in an inter-slot TDM manner.
  • the first The network device (that is, the network device corresponding to the serving cell, which can also be called the receiving gNB of SDT) can learn the information of the second multicast session received by the terminal device, thereby scheduling the data of the SDT and the second multicast session on different time slots. , so that even if the terminal device does not have the ability to receive unicast data and multicast data and/or signaling on the same time slot, it can still receive the SDT and the second SDT sent by the first network device on different time slots. Multicast session data and/or signaling to avoid data errors and/or packet loss caused by scheduling beyond the receiving capabilities of terminal devices.
  • the terminal device sends the thirteenth information to the first network device, which can indicate that the terminal device supports receiving the MBS multicast service.
  • the terminal device must support PDSCH for transmitting unicast data and PDSCH/GC for transmitting MBS multicast data.
  • - PDSCH inter-slot time division multiplexing (inter-slot TDM) reception so the first network device sends SDT and second multicast session data according to inter-slot time division multiplexing, which can ensure that the terminal device can The data of the second multicast session is received to avoid bit errors and/or packet loss, thereby ensuring the service quality of SDT and MBS multicast services.
  • the first network device When the terminal device does not support receiving unicast data and MBS multicast data in the same time slot, in the SDT scenario without context relocation, the first network device does not have UE capability information. If the first network device does not know that the terminal device is When receiving the second multicast session, when the first network device schedules/sends SDT data (SDT can be understood as a unicast transmission method) and the data of the second multicast session in the same time slot, it will cause the terminal device to be unable to SDT and multicast data are received, or the terminal device can only receive one of SDT or multicast data, causing data errors and/or packet loss, affecting service reception quality.
  • SDT can be understood as a unicast transmission method
  • FIG. 8 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 80 may include a transceiver unit 801 and a processing unit 802 .
  • the transceiver unit 801 and the processing unit 802 may be software, hardware, or a combination of software and hardware.
  • the transceiver unit 801 can implement a sending function and/or a receiving function, and the transceiver unit 801 can also be described as a communication unit.
  • the transceiver unit 801 may also be a unit that integrates an acquisition unit and a sending unit, where the acquisition unit is used to implement the receiving function and the sending unit is used to implement the sending function.
  • the transceiver unit 801 can be used to receive information sent by other devices, and can also be used to send information to other devices.
  • the communication device 80 may correspond to the terminal equipment in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be a terminal equipment, or may be It is a chip in the terminal device.
  • the communication device 80 may include units for performing the operations performed by the terminal device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 is for Implement the operations performed by the terminal device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7. Among them, the descriptions of each unit are as follows:
  • the transceiver unit 801 is configured to perform small data transmission SDT with the first network device, and is interested in receiving or receiving the first broadcast service from the first network device.
  • the SDT is in the Radio Resource Control RRC inactive state.
  • the first network device is the network device corresponding to the cell where the communication device resides;
  • the transceiver unit 801 is also configured to send first information to the first network device, where the first information includes information about the first broadcast service, and the first information is used by the first network device to The communication device provides the first broadcast service.
  • the transceiver unit 801 is further configured to receive the SDT and the first broadcast service from the first network device on different time slots.
  • the transceiver unit 801 is also configured to receive the second information sent by the first network device and/or the third information sent by the second network device, and the second network device is A network device that sends an RRC release message to the communication device;
  • the processing unit 802 is configured to send the first information to the first network device through the transceiver unit 801 according to the second information and/or the third information.
  • the transceiver unit 801 is further configured to receive the fourth information sent by the first network device and/or the fifth information sent by the second network device;
  • the processing unit 802 is further configured to send a message to the first through the transceiver unit 801 according to the fourth information and/or the fifth information.
  • the network device sends the first information, where the first information includes TMGI information of the first broadcast service.
  • the third information and/or the fifth information are carried in an RRC release message
  • the processing unit 802 is also configured to enter the RRC inactive state according to the RRC release message.
  • the second information, and/or the third information, and/or the fourth information, and/or the fifth information include system information.
  • the second information and/or the third information includes first system information, which is used to indicate a mapping relationship between multicast broadcast services and frequencies, or to Indicates the configuration parameters of the multicast broadcast service control channel MCCH.
  • the fourth information and/or the fifth information includes second system information
  • the second system information is used to indicate the mapping relationship between multicast broadcast services and frequencies, or is used to Indicates the configuration parameters of the multicast broadcast service control channel MCCH.
  • the communication device 80 may correspond to the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be the first network device.
  • the network device may also be a chip in the first network device.
  • the communication device 80 may include units for performing the operations performed by the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 In order to implement the operations performed by the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7 respectively.
  • the descriptions of each unit are as follows:
  • Transceiver unit 801 configured to receive first information sent by a terminal device.
  • the first information includes information about a first broadcast service that the terminal device is interested in receiving or is receiving.
  • the communication device resides for the terminal device.
  • the network equipment corresponding to the community;
  • the transceiver unit 801 is also configured to perform small data transmission SDT with the terminal device, and provide the first broadcast service to the terminal device.
  • the SDT is data in the radio resource control RRC inactive state and /or transmission of signaling.
  • the transceiver unit 801 is also configured to send the SDT and the first broadcast service to the terminal device on different time slots.
  • the transceiver unit 801 is further configured to send the first information to a second network device, where the second network device is a network device connecting the terminal device and the core network device;
  • the transceiver unit 801 is also configured to receive sixth information from the second network device.
  • the sixth information is used to indicate the first broadcast service.
  • the sixth information is determined by the first information. .
  • the transceiver unit 801 is further configured to send a first request message to the second network device, where the first request message is used to request to obtain context information of the terminal device for SDT. ;
  • the transceiver unit 801 is also configured to receive partial context information of the terminal device sent by the second network device, where the partial context information includes seventh information, and the seventh information is used to indicate to the terminal device Received second broadcast service.
  • the processing unit 802 is configured to ignore the seventh information when the sixth information is received.
  • the transceiver unit 801 is further configured to receive eighth information from the second network device, where the eighth information is used to indicate whether the terminal device supports or does not support M Frequency division multiplexing FDM reception of unicast data and N broadcast data in the same time slot, where the M and N are integers greater than or equal to 1; and/or,
  • the transceiver unit 801 is also configured to receive ninth information from the second network device, where the ninth information is used to indicate whether the terminal device supports P unicast data and Q broadcast data.
  • the P and Q are integers greater than or equal to 1.
  • the communication device 80 may correspond to the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be the second network device.
  • the network device may also be a chip in the second network device.
  • the communication device 80 may include units for performing operations performed by the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 In order to implement the operations performed by the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, respectively.
  • the descriptions of each unit are as follows:
  • Transceiver unit 801 configured to send small data transmission SDT and sixth information to the first network device.
  • the sixth information is used to indicate the first broadcast service.
  • the first broadcast service is what the terminal device is interested in receiving or is receiving.
  • Broadcast service the communication device is a network device that connects the terminal device and the core network device, the first network device is a network device corresponding to the cell where the terminal device resides, and the SDT is the network device where the terminal device resides.
  • the radio resource controls the transmission of RRC inactive data and/or signaling, and the SDT is sent to the terminal device through the first network device.
  • the transceiver unit 801 is further configured to receive the first information sent by the first network device, where the first information includes the information of the first broadcast service;
  • the processing unit 802 is configured to determine the sixth information according to the first information.
  • the transceiver unit 801 is also configured to receive the first request message sent by the first network device, The first request message is used to request to obtain context information of the terminal device for SDT;
  • the transceiver unit 801 is further configured to send partial context information of the terminal device to the first network device in response to the first request message, where the partial context information includes seventh information, and the seventh information The information is used to indicate the second broadcast service received by the terminal device.
  • the processing unit 802 is further configured to determine, based on the capability information of the terminal device, that the terminal device does not support receiving unicast data and broadcast data in the same time slot.
  • the communication device 80 may correspond to the terminal equipment in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be a terminal equipment, or It can be a chip in the terminal device.
  • the communication device 80 may include units for performing the operations performed by the terminal device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 is for Implement the operations performed by the terminal device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7. Among them, the descriptions of each unit are as follows:
  • the transceiver unit 801 is configured to receive the small data transmission SDT sent by the first network device and the data of the first multicast session.
  • the SDT is the transmission of data and/or signaling in the RRC inactive state of Radio Resource Control, so
  • the first network device is a network device corresponding to the cell where the communication device resides, and the first multicast session is a multicast session joined by the communication device, and is used to indicate the tenth session of the first multicast session.
  • the information is sent to the first network device by a second network device, and the second network device is a network device that connects the communication device and the core network device.
  • the tenth information is carried in part of the context information of the communication device sent by the second network device to the first network device.
  • the communication device 80 may correspond to the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be the first network device.
  • the network device may also be a chip in the first network device.
  • the communication device 80 may include units for performing the operations performed by the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 In order to implement the operations performed by the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, respectively.
  • the descriptions of each unit are as follows:
  • the transceiver unit 801 is configured to receive the tenth information from the second network device.
  • the tenth information is used to indicate the first multicast session that the terminal device joins.
  • the communication device is corresponding to the cell where the terminal resides.
  • Network equipment, the second network equipment is a network equipment connecting the terminal equipment and the core network equipment;
  • the transceiver unit 801 is also configured to send small data transmission SDT and data of the first multicast session to the terminal device.
  • the SDT is data and/or signaling in the radio resource control (RRC) inactive state. transmission.
  • RRC radio resource control
  • the transceiver unit 801 is also configured to send a second request message to the second network device.
  • the second request message is used to request to obtain the context information of the terminal device for SDT. ;
  • the transceiver unit 801 is also configured to receive partial context information of the terminal device sent by the second network device, where the partial context information includes the tenth information.
  • the transceiver unit 801 is further configured to send the SDT and the data of the first multicast session to the terminal device on different time slots.
  • the transceiver unit 801 is also configured to receive eleventh information from the second network device, where the eleventh information is used to indicate whether the terminal device supports or does not support Frequency division multiplexing FDM reception of M unicast data and N multicast data within a time slot, where the M and N are integers greater than or equal to 1; and/or,
  • the transceiver unit 801 is also configured to receive twelfth information from the second network device, where the twelfth information is used to indicate whether the terminal device supports P unicast data and Q groups.
  • the broadcast data is received by time division multiplexing TDM within the time slot, and the P and Q are integers greater than or equal to 1.
  • the communication device 80 may correspond to the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be the second network device.
  • the network device may also be a chip in the second network device.
  • the communication device 80 may include units for performing operations performed by the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 In order to implement the operations performed by the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, respectively.
  • the descriptions of each unit are as follows:
  • the transceiver unit 801 is configured to send small data transmission SDT and tenth information to the first network device.
  • the tenth information is used to indicate the first multicast session joined by the terminal device.
  • the first network device is the terminal station.
  • the network equipment corresponding to the remaining cells, the communication device is the network equipment connecting the terminal equipment and the core network equipment;
  • the SDT and the data of the first multicast session are sent to the terminal device by the first network device, and the SDT is the The end device controls the transmission of RRC inactive data and/or signaling in radio resources.
  • the transceiver unit 801 is also configured to receive a second request message sent by the first network device, where the second request message is used to request to obtain context information of the terminal device. SDT;
  • the transceiver unit 801 is further configured to send partial context information of the terminal device to the first network device, where the partial context information includes the tenth information.
  • the SDT and the data of the first multicast session are sent by the first network device to the terminal device on different time slots.
  • the processing unit 802 is configured to determine, based on the capability information of the terminal device, that the terminal device does not support receiving unicast data and multicast data in the same time slot.
  • the communication device 80 may correspond to the terminal equipment in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be a terminal equipment, or It can be a chip in the terminal device.
  • the communication device 80 may include units for performing operations performed by the terminal device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 is for Implement the operations performed by the terminal device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7. Among them, the descriptions of each unit are as follows:
  • the transceiver unit 801 is configured to perform small data transmission SDT with the first network device, and join the second multicast session from the first network device.
  • the SDT is data in the Radio Resource Control RRC inactive state and /or signaling transmission
  • the first network device is the network device corresponding to the cell where the communication device resides;
  • the transceiver unit 801 is further configured to send thirteenth information to the first network device, where the thirteenth information is used to indicate the second multicast session, and the thirteenth information is used for the third multicast session.
  • a network device sends the second multicast session to the communication device.
  • the thirteenth information is carried in a media access control element MAC CE or a radio resource control RRC message.
  • the transceiver unit 801 is further configured to receive data from the SDT and the second multicast session of the first network device on different time slots.
  • the communication device 80 may correspond to the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be the first network device.
  • the network device may also be a chip in the first network device.
  • the communication device 80 may include units for performing the operations performed by the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 In order to implement the operations performed by the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7 respectively.
  • the descriptions of each unit are as follows:
  • the transceiver unit 801 is configured to receive the thirteenth information sent by the terminal device, where the thirteenth information is used to indicate a second multicast session, where the second multicast session is a multicast session joined by the terminal device, so
  • the communication device is a network device corresponding to the cell where the terminal device resides;
  • the transceiver unit 801 is also configured to perform small data transmission SDT with the terminal device, and send data of the second multicast session to the terminal device.
  • the SDT is in the Radio Resource Control RRC inactive state. transmission of data and/or signaling.
  • the transceiver unit 801 is further configured to send the SDT and the data of the second multicast session to the terminal device on different time slots.
  • the thirteenth information is carried in a media access control element MAC CE or a radio resource control RRC message.
  • the communication device 80 may correspond to the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 80 may be the second network device.
  • the network device may also be a chip in the second network device.
  • the communication device 80 may include units for performing operations performed by the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, and each unit in the communication device 80 In order to implement the operations performed by the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7, respectively.
  • the descriptions of each unit are as follows:
  • the transceiver unit 801 is also configured to send a small data transmission SDT to the first network device; wherein the SDT and the data of the second multicast session are sent by the first network device to the terminal device, and the SDT is the terminal device.
  • the device controls the transmission of data and/or signaling in the RRC inactive state in the radio resource.
  • the first network device is a network device corresponding to the cell where the terminal resides.
  • the communication device is a device that connects the terminal device and the core.
  • a network device of a network device, the second multicast session is a multicast session that the thirteenth information indicates that the terminal device joins, and the thirteenth information comes from the terminal device.
  • each unit in the device shown in Figure 8 can be separately or entirely combined into one or several additional units, or one (some) of the units can be further divided into more functional units. It is composed of multiple small units, which can achieve the same operation without affecting the realization of the technical effects of the embodiments of the present application.
  • the above units are divided based on logical functions.
  • a unit The functions of multiple units can also be implemented by multiple units, or the functions of multiple units can be implemented by one unit.
  • the electronic device may also include other units. In practical applications, these functions may also be implemented with the assistance of other units, and may be implemented by multiple units in cooperation.
  • each unit may also refer to the corresponding descriptions of the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the network device corresponding to the serving cell can learn the multicast broadcast service information that the terminal device is interested in receiving or is receiving.
  • the terminal device can receive the data of SDT and multicast broadcast services.
  • FIG. 9 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 90 shown in FIG. 9 is only an example.
  • the communication device in the embodiment of the present application may also include other components, or components with similar functions to the components in FIG. 9 , or is not intended to include the components in FIG. 9 All parts.
  • the communication device 90 includes a communication interface 901 and at least one processor 902 .
  • the communication device 90 may correspond to any network element or device among the terminal device, the first network device, and the second network device.
  • the communication interface 901 is used to send and receive signals, and at least one processor 902 executes program instructions, so that the communication device 90 implements the corresponding process of the method executed by the corresponding device in the above method embodiment.
  • the communication device 90 may correspond to the terminal equipment in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be a terminal equipment, or may be It is a chip in the terminal device.
  • the communication device 90 may include components for performing operations performed by the terminal device in the above method embodiment, and each component in the communication device 90 is respectively intended to implement the operations performed by the terminal device in the above method embodiment. The details can be as follows:
  • the terminal device performs small data transmission SDT with the first network device, and the terminal device is interested in receiving or is receiving the first broadcast service from the first network device, and the SDT is in the Radio Resource Control RRC inactive state.
  • the first network device is the network device corresponding to the cell where the terminal device resides;
  • the terminal device sends first information to the first network device, the first information includes information about the first broadcast service, and the first information is used by the first network device to provide the terminal device with The first broadcast service.
  • the communication device 90 may correspond to the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be the first network device.
  • the network device may also be a chip in the first network device.
  • the communication device 90 may include components for performing the operations performed by the first network device in the above method embodiment, and each component in the communication device 90 is respectively used to implement the operations performed by the first network device in the above method embodiment. The operation performed.
  • the details can be as follows:
  • the first network device receives the first information sent by the terminal device.
  • the first information includes information about the first broadcast service that the terminal device is interested in receiving or is receiving.
  • the first network device is camped for the terminal device.
  • the network equipment corresponding to the community;
  • the first network device performs small data transmission SDT with the terminal device, and the first network device provides the first broadcast service to the terminal device, and the SDT is in a radio resource control (RRC) inactive state. transmission of data and/or signaling.
  • RRC radio resource control
  • the communication device 90 may correspond to the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be the second network device.
  • the network device may also be a chip in the second network device.
  • the communication device 90 may include components for performing the operations performed by the second network device in the above method embodiment, and each component in the communication device 90 is respectively used to implement the operations performed by the second network device in the above method embodiment. The operation performed.
  • the details can be as follows:
  • the second network device sends small data transmission SDT and sixth information to the first network device.
  • the sixth information is used to indicate the first broadcast service.
  • the first broadcast service is a broadcast service that the terminal device is interested in receiving or is receiving.
  • the second network device is a network device that connects the terminal device and the core network device
  • the first network device is a network device corresponding to the community where the terminal device resides
  • the SDT is the network device where the terminal device resides.
  • the radio resource controls the transmission of RRC inactive data and/or signaling, and the SDT is sent to the terminal device through the first network device.
  • the communication device 90 may correspond to the terminal equipment in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be a terminal equipment, or It can be a chip in the terminal device.
  • the communication device 90 may include components for performing operations performed by the terminal device in the above method embodiment, and each component in the communication device 90 is respectively intended to implement the operations performed by the terminal device in the above method embodiment. The details can be as follows:
  • the terminal device receives the small data transmission SDT sent by the first network device and the data of the first multicast session.
  • the SDT is the transmission of data and/or signaling in the RRC inactive state of the radio resource control.
  • the first network The device is a network device corresponding to the cell where the terminal device resides, the first multicast session is a multicast session joined by the terminal device, and the tenth information used to indicate the first multicast session is provided by the second
  • the network device sends it to the first network device, and the second network device is a network device that connects the terminal device and the core network device.
  • the communication device 90 may correspond to the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be the first network device.
  • the network device may also be a chip in the first network device.
  • the communication device 90 may include components for performing the operations performed by the first network device in the above method embodiment, and each component in the communication device 90 is respectively used to implement the operations performed by the first network device in the above method embodiment. The operation performed.
  • the details can be as follows:
  • the first network device receives the tenth information from the second network device, the tenth information is used to indicate the first multicast session that the terminal device joins, and the first network device is corresponding to the cell where the terminal resides.
  • Network equipment, the second network equipment is a network equipment connecting the terminal equipment and the core network equipment;
  • the first network device sends a small data transmission SDT and the data of the first multicast session to the terminal device, where the SDT is the transmission of data and/or signaling in an RRC inactive state.
  • the communication device 90 may correspond to the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be the second network device.
  • the network device may also be a chip in the second network device.
  • the communication device 90 may include components for performing the operations performed by the second network device in the above method embodiment, and each component in the communication device 90 is respectively used to implement the operations performed by the second network device in the above method embodiment. The operation performed.
  • the details can be as follows:
  • the second network device sends the small data transmission SDT and the tenth information to the first network device.
  • the tenth information is used to indicate the first multicast session joined by the terminal device.
  • the first network device is the terminal resident.
  • Network equipment corresponding to the cell, the second network equipment is a network equipment connecting the terminal equipment and the core network equipment;
  • the SDT and the data of the first multicast session are sent by the first network device to the terminal device.
  • the SDT is the data and/or signaling of the terminal device in the Radio Resource Control RRC inactive state. transmission.
  • the communication device 90 may correspond to the terminal equipment in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be a terminal equipment, or It can be a chip in the terminal device.
  • the communication device 90 may include components for performing operations performed by the terminal device in the above method embodiment, and each component in the communication device 90 is respectively intended to implement the operations performed by the terminal device in the above method embodiment. The details can be as follows:
  • the terminal device performs small data transmission SDT with the first network device, and the terminal device joins the second multicast session from the first network device.
  • the SDT is data in the Radio Resource Control RRC inactive state and /or signaling transmission
  • the first network device is a network device corresponding to the cell where the terminal device resides;
  • the terminal device sends thirteenth information to the first network device, the thirteenth information is used to indicate the second multicast session, and the thirteenth information is used for the first network device to send The terminal device sends the second multicast session.
  • the communication device 90 may correspond to the first network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be the first network device.
  • the network device may also be a chip in the first network device.
  • the communication device 90 may include components for performing the operations performed by the first network device in the above method embodiment, and each component in the communication device 90 is respectively used to implement the operations performed by the first network device in the above method embodiment. The operation performed.
  • the details can be as follows:
  • the first network device receives the thirteenth information sent by the terminal device, the thirteenth information is used to indicate a second multicast session, the second multicast session is a multicast session joined by the terminal device, and the third One network device is a network device corresponding to the cell where the terminal device resides;
  • the first network device performs small data transmission (SDT) with the terminal device, and the first network device sends data of the second multicast session to the terminal device.
  • SDT small data transmission
  • RRC radio resource control
  • the communication device 90 may correspond to the second network device in the method embodiments shown in FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the communication device 90 may be the second network device.
  • the network device may also be a chip in the second network device.
  • the communication device 90 may include components for performing the operations performed by the second network device in the above method embodiment, and each component in the communication device 90 is respectively used to implement the operations performed by the second network device in the above method embodiment. The operation performed.
  • the details can be as follows:
  • the second network device sends a small data transmission SDT to the first network device; wherein the SDT and the data of the second multicast session are sent by the first network device to the terminal device, and the SDT is the wireless transmission of the terminal device.
  • the resource controls the transmission of RRC inactive data and/or signaling.
  • the first network device is a network device corresponding to the cell where the terminal resides, and the second network device is a network device that connects the terminal device and the core network.
  • the network device of the device, the second multicast session is a multicast session that the thirteenth information indicates that the terminal device joins, and the thirteenth information comes from the terminal device.
  • the network device corresponding to the serving cell can learn the multicast broadcast service information that the terminal device is interested in receiving or is receiving.
  • the terminal device can receive the data of SDT and multicast broadcast services.
  • the communication device may be a chip or a chip system
  • the communication device may be a chip or a chip system
  • the chip 100 includes a processor 1001 and an interface 1002.
  • the number of processors 1001 may be one or more, and the number of interfaces 1002 may be multiple. It should be noted that the corresponding functions of the processor 1001 and the interface 1002 can be realized through hardware design, software design, or a combination of software and hardware, which are not limited here.
  • the chip 100 may also include a memory 1003, which is used to store necessary program instructions and data.
  • the processor 1001 can be used to call the communication method provided by one or more embodiments of the application from the memory 1003 to use one or more devices or network elements among the terminal device, the first network device, and the second network device. Implement a program and execute the instructions contained in the program.
  • the interface 1002 may be used to output execution results of the processor 1001. In this application, the interface 1002 may be specifically used to output various messages or information from the processor 1001.
  • the processor in the embodiment of this application can be a central processing unit (Central Processing Unit, CPU).
  • the processor can also be other general-purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the memory in the embodiment of the present application is used to provide storage space, and data such as operating systems and computer programs can be stored in the storage space.
  • Memory includes but is not limited to random access memory (RAM), read-only memory (ROM), erasable programmable read only memory (EPROM), or portable Read-only memory (compact disc read-only memory, CD-ROM).
  • the embodiment of the present application also provides a computer-readable storage medium.
  • the computer-readable storage medium stores a computer program.
  • the embodiment of the present application also provides a computer program product.
  • the above-mentioned computer program product includes a computer program.
  • the above-mentioned computer program is run on a processor, the above-mentioned Figures 4, 5 and 5 can be realized. 6.
  • Embodiments of the present application also provide a system, which includes at least one communication device 80 or communication device 90 or chip 100 as described above, for executing the corresponding steps in any of the embodiments of FIG. 4, FIG. 5, FIG. 6, and FIG. 7. The steps the device performs.
  • Embodiments of the present application also provide a system, which includes a terminal device, a first network device, and a second network device.
  • the terminal device is used to perform any of the above embodiments of FIG. 4, FIG. 5, FIG. 6, and FIG. 7.
  • the steps performed by the terminal device, the first network device is used to perform the steps performed by the first network device in any of the embodiments of Figure 4, Figure 5, Figure 6, and Figure 7, and the second network device is used to perform the steps described in Figure 4 , steps performed by the second network device in any embodiment of FIG. 5, FIG. 6, and FIG. 7.
  • An embodiment of the present application also provides a processing device, including a processor and an interface; the processor is configured to execute the method in any of the above method embodiments.
  • the above processing device may be a chip.
  • the processing device may be a field programmable gate array (FPGA), a general processor, a digital signal processor (DSP), or an application specific integrated circuit (ASIC).
  • FPGA field programmable gate array
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • SoC system on chip
  • It can be a central processor unit (CPU), a network processor (NP), a digital signal processing circuit (digital signal processor, DSP), or a microcontroller (micro controller unit, MCU).
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories.
  • the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM static State random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous link dynamic random access memory direct rambus RAM, DR RAM
  • direct rambus RAM direct rambus RAM
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the usable media may be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., high-density digital video discs (DVD)), or semiconductor media (e.g., solid state disks, SSD)) etc.
  • magnetic media e.g., floppy disks, hard disks, tapes
  • optical media e.g., high-density digital video discs (DVD)
  • DVD digital video discs
  • semiconductor media e.g., solid state disks, SSD
  • the units in each of the above device embodiments correspond completely to the electronic equipment in the method embodiments, and the corresponding modules or units perform corresponding steps.
  • the communication unit transmits the steps of receiving or sending in the method embodiments, except for sending.
  • other steps besides receiving may be performed by the processing unit (processor).
  • the processing unit processor
  • the electronic device can perform some or all of the steps in the embodiments of the present application. These steps or operations are only examples. The embodiments of the present application can also perform other operations or variations of various operations. In addition, various steps may be performed in a different order than those presented in the embodiments of the present application, and it may not be necessary to perform all operations in the embodiments of the present application.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the computer software product is stored in a storage medium and includes a number of instructions to A computer device (which may be a personal computer, a server, or a network device, etc.) is caused to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory ROM, random access memory RAM, magnetic disk or optical disk and other various media that can store program codes.

Landscapes

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

Abstract

本申请公开了一种通信方法及相关装置。该方法包括：终端设备与第一网络设备进行小数据传输SDT，终端设备感兴趣接收或正在接收来自于第一网络设备的第一广播服务，SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，第一网络设备为终端设备驻留的小区对应的网络设备；终端设备向第一网络设备发送第一信息，第一信息包括第一广播服务的信息，第一信息用于第一网络设备向终端设备提供第一广播服务。本方法可以实现终端设备在无UE上下文重定位的小数据传输场景下，服务小区对应的网络设备可以获知终端设备感兴趣接收或正在接收的组播广播服务信息以进行合理的调度和数据传输，使得终端设备可以接收到SDT和组播广播服务的数据。

Description

一种通信方法及相关装置
本申请要求于2022年9月9日提交中国专利局、申请号为202211103843.5、申请名称为“一种通信方法及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种通信方法及相关装置。
背景技术
终端设备(user equipment，UE)在无线资源控制(radio resource control，RRC)非活动态下，对于数据量较小且不频繁的数据传输，可以保持在RRC非活动态进行小数据传输(small data transmission，SDT)，而无需转换到RRC连接态再进行传输，从而减少由于小数据传输需求而进行RRC状态转换导致的功耗和信令开销，实现降低UE功耗的目的。
但是，终端设备在无UE上下文重定位的小数据传输(SDT without UE context relocation)场景下，如果终端设备还感兴趣接收或正在接收组播广播服务，则服务小区对应的网络设备调度的SDT和广播组播服务的数据传输可能超出终端设备的接收能力，造成丢包或误码，影响服务质量。
发明内容
本申请实施例提供了一种通信方法及相关装置，终端设备在无UE上下文重定位的小数据传输场景下，服务小区对应的网络设备可以获知终端设备感兴趣接收或正在接收的组播广播服务信息以进行合理的调度和数据传输，使得终端设备可以接收到SDT和组播广播服务的数据。
第一方面，本申请实施例提供了一种通信方法，该方法包括：
终端设备与第一网络设备进行小数据传输SDT，并且所述终端设备感兴趣接收或正在接收来自于所述第一网络设备的第一广播服务，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
所述终端设备向所述第一网络设备发送第一信息，所述第一信息包括所述第一广播服务的信息，所述第一信息用于所述第一网络设备向所述终端设备提供所述第一广播服务。
本申请中，第一广播服务可以为一个或多个广播服务。第一广播服务的信息为上述一个或多个广播服务的信息。第一组播会话(MBS Session)可以为一个或多个组播会话，组播会话也可以理解为组播服务/组播业务。
本申请实施例中，提供了一种通信方法，处于RRC非活动态的终端设备与第一网络设备进行SDT，并且终端设备感兴趣接收或正在接收来自第一网络设备的第一广播服务，终端设备向第一网络设备发送第一信息，该第一信息包括第一广播服务的信息，该第一信息具体可以是组播广播业务(multicast broadcast service，MBS)兴趣指示信息(MBS Interest Indication，MII)，用于指示终端设备感兴趣接收或正在接收的MBS广播服务的信息，例如MBS广播服务的频率、MBS广播服务的标识信息、MBS广播与单播和MBS组播接收相比的优先级信息等。本申请中的终端设备感兴趣接收的广播服务还可以指终端设备未接收但是待接收的广播服务。通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第一广播服务的场景下，可以通过向第一网络设备上报第一信息，使第一网络设备知道终端设备在进行SDT的过程中还在接收第一广播服务，从而第一网络设备可以对SDT和第一广播服务进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
本申请中，广播服务可以指MBS(multicast broadcast service,MBS)广播服务(broadcast service)，组播服务可以指MBS组播服务(multicast service)。SDT包括下行/上行SDT的数据和/或信令。
在一种可能的实施方式中，所述方法还包括：
所述终端设备在不同时隙上接收来自于所述第一网络设备的所述SDT和所述第一广播服务的数据。所述SDT可以理解为下行SDT数据(DownLink SDT data)。所述在不同时隙上接收所述SDT和所述第一广播服务的数据可以理解为/替换为在不同时隙上接收用于传输所述SDT数据的物理下行共享信道(physical downlink shared channel,PDSCH)和用于传输所述第一广播服务的数据的PDSCH或组公共PDSCH(group  common physical downlink shared channel,GC-PDSCH)。
在本申请实施方式中，提供了一种调度SDT和第一广播服务的可能的具体实施方式，具体为，第一网络设备通过时隙间时分复用(inter-slot TDM)调度SDT和第一广播服务，比如在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第一广播服务的数据，使终端设备可以在不同时隙上接收来自于第一网络设备的SDT和第一广播服务。通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备感兴趣接收或正在接收来自于第一网络设备的第一广播服务，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第一广播服务的信息，从而在不同时隙上调度SDT和第一广播服务的数据，使终端设备即使不具备在同一个时隙上接收单播数据和广播数据的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第一广播服务的数据。
终端设备向第一网络设备发送第一信息，可以表示终端设备支持接收MBS广播服务，则终端设备必选支持用于传输单播数据的PDSCH和用于传输MBS广播数据的PDSCH/GC-PDSCH的时隙间时分复用(inter-slot TDM)接收，因此第一网络设备按照时隙间时分复用发送SDT和第一广播服务的数据，可以保证终端设备能够在SDT的过程中接收到第一广播服务，避免造成误码和/或丢包，从而保证SDT和MBS广播服务的业务质量。当终端设备不支持在同一时隙内接收单播数据和MBS广播数据时，在无上下文重定位的SDT场景下，第一网络设备没有UE能力信息，如果第一网络设备不知道终端设备正在接收第一广播服务，当第一网络设备在同一时隙内发送SDT数据(SDT可以理解为一种单播传输方式)和第一广播服务的数据时，则会导致终端设备无法接收到SDT和广播数据，或者终端设备只能接收到SDT或广播数据二者其中之一，造成数据误码和/或丢包，影响业务接收质量。因此，通过本申请方案，可以避免上述问题。
在一种可能的实施方式中，所述终端设备向所述第一网络设备发送第一信息之前，所述方法还包括：
所述终端设备接收所述第一网络设备发送的第二信息和/或第二网络设备发送的第三信息，所述第二网络设备为向所述终端设备发送RRC释放消息的网络设备；
所述终端设备向所述第一网络设备发送第一信息，包括：
所述终端设备根据所述第二信息和/或所述第三信息，向所述第一网络设备发送所述第一信息。
在本申请实施方式中，提供了一种发送第一信息的可能的具体实施方式，具体为，终端设备在向第一网络设备发送第一信息之前，终端设备还接收第一网络设备发送的第二信息和/或第二网络设备发送的第三信息，并根据该第二信息和/或第三信息，确定向第一网络设备发送第一信息，此时的第一信息包括第一广播服务的信息，该第一信息具体可以是MII，用于指示终端设备感兴趣接收或正在接收的MBS广播服务的信息，例如MBS广播服务的频率、MBS广播服务的标识信息、MBS广播与单播和MBS组播接收相比的优先级信息等。通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第一广播服务的场景下，可以根据第一网络设备发送的第二信息来确定第一信息的上报，或者根据第二网络设备发送的第三信息来确定第一信息的上报，或者根据第一网络设备发送的第二信息和第二网络设备发送的第三信息确定第一信息的上报；也可以理解为，第一网络设备通过发送的第二信息和/或第二网络设备通过发送的第三信息来控制是否允许终端设备上报所述第一信息。第二信息和第三信息可以是相同的信息，也可以是不同的信息。
在一种可能的实施方式中，所述第一广播服务的信息包括临时移动组标识TMGI信息；所述终端设备向所述第一网络设备发送第一信息之前，所述方法还包括：
所述终端设备接收所述第一网络设备发送的第四信息和/或所述第二网络设备发送的第五信息；
所述终端设备向所述第一网络设备发送第一信息，包括：
所述终端设备根据所述第四信息和/或所述第五信息，向所述第一网络设备发送所述第一信息，所述第一信息包括所述第一广播服务的TMGI信息。
在本申请实施方式中，提供了一种发送第一信息的可能的具体实施方式，具体为，终端设备在向第一网络设备发送第一信息之前，终端设备还接收第一网络设备发送的第四信息和/或第二网络设备发送的第五信息，并根据该第四信息和/或第五信息，确定向第一网络设备发送第一信息，此时的第一信息包括第一广播服务的临时移动组标识(temporary mobile group identity，TMGI)信息。通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第一广播服务的场景下，可以根据第一网络设备发送的第四信息来确定在发送的第一信息中包含第一广播服务的TMGI信息，或者根据第二网络设备发送的第五信息来确定在发送的第一信息中包含第一广播服务的TMGI信息， 或者根据第一网络设备发送的第四信息和第二网络设备发送的第五信息来确定在发送的第一信息中包含第一广播服务的TMGI信息。第四信息和第五信息可以是相同的信息，也可以是不同的信息。
在一种可能的实施方式中，所述第三信息和/或所述第五信息承载于RRC释放消息中；所述方法还包括：
所述终端设备根据所述RRC释放消息进入RRC非活动态。
在本申请实施方式中，提供了一种传输第三信息和/或第五信息的可能的具体实施方式，具体为，第三信息和/或第五信息可以承载于RRC释放消息中，比如，第三信息和/或第五信息可以为RRC释放消息中的一个指示位(比如1比特位)，第三信息和第五信息可以为不同的信息，通过两个独立的比特位指示，也可以为相同的信息，通过同一个比特位指示。示例性的，第三信息和第五信息为两个相互独立的信息时，RRC释放消息中包含第三信息，或第三信息对应的比特位置为1，指示允许终端设备上报所述第一信息(具体可以是MII)，或指示允许终端设备在RRC非活动态上报所述第一信息，或指示允许终端设备在SDT过程中上报所述第一信息，其中，所述允许上报也可以理解为所述第二网络设备支持接收来自于RRC非活动态的终端设备上报的所述第一信息，或来自于终端设备在SDT过程中上报的所述第一信息；示例性的，RRC释放消息中不包含第三信息，或第三信息对应的比特位置为0，则指示不允许终端设备上报/第二网络设备不支持接收所述第一信息(具体可以是MII)，或指示不允许/不支持接收RRC非活动态的终端设备上报所述第一信息，或指示不允许/不支持接收终端设备在SDT过程中上报所述第一信息。类似的，第五信息的设置和含义参考上述第三信息，示例性的，RRC释放消息中包含第五信息或第五信息对应的比特位置为1时，指示允许终端设备上报的第一信息中包含广播服务的TMGI信息/第二网络设备支持接收终端设备上报的第一信息中包含广播服务的TMGI信息，或指示允许/支持接收RRC非活动态的终端设备上报的所述第一信息中包含广播服务的TMGI信息，或指示允许/支持接收终端设备在SDT过程中上报的所述第一信息中包含广播服务的TMGI信息。
当所述第五信息和所述第三信息为同一个信息时，或者第五信息和第三信息为同一个指示位/比特位时，示例性的，当RRC释放消息中包含该信息、或该比特位/指示位置为1，指示允许终端设备上报/第二网络设备支持接收所述第一信息(具体可以为MII)，且所述第一信息中可以包含广播服务的TMGI信息；该RRC释放消息中不包含该信息、或该比特位/指示位置为0时，指示不允许终端设备上报所述第一信息。其他含义示例参考上文对第三信息/第五信息的描述，此处不赘述。
通过本申请实施例，第二网络设备可以通过第三信息和/或第五信息，控制终端设备对第一信息的上报，并且具有更好的后向兼容性。比如，对于老版本的网络设备，不期望RRC非活动态的终端设备上报第一信息，或不期望在SDT过程中收到终端设备上报的第一信息，则可以在RRC释放消息中不包含所述第三信息和/或所述第五信息，则终端设备不会上报所述第一信息；对于升级后的可以支持RRC非活动态终端设备上报第一信息/终端设备在SDT过程中上报第一信息的网络设备，可以在RRC释放消息中包含所述第三信息和/或第五信息。
在一种可能的实施方式中，所述第二信息，和/或所述第三信息，和/或所述第四信息，和/或所述第五信息包括系统信息。
在本申请实施方式中，提供了一种传输第二信息，和/或第三信息，和/或第四信息，和/或第五信息的可能的具体实施方式，具体为，第二信息，和/或第三信息，和/或第四信息，和/或第五信息可以包括系统信息(System Information,SI)；或者，第二信息，和/或第三信息，和/或第四信息，和/或第五信息可以以系统信息块(System Information Bloack,SIB)的形式传输。
在一种可能的实施方式中，所述第二信息和/或所述第三信息包括第一系统信息，所述第一系统信息用于指示组播广播服务和频率的映射关系，或者用于指示组播广播服务控制信道MCCH的配置参数。
在本申请实施方式中，提供了一种第二信息和/或第三信息的可能的具体实施方式，具体为，第二信息和/或第三信息可以包括第一系统信息；或者，第二信息和/或第三信息可以以第一系统信息块的形式传输。其中，第一系统信息用于指示组播广播服务和频率的映射关系，比如，可以对应于系统信息块SIB21；或者，第一系统信息用于指示组播广播服务控制信道(MBS control channel，MCCH)的配置参数，比如，可以对应于系统信息块SIB20。
在一种可能的实施方式中，所述第四信息和/或所述第五信息包括第二系统信息，所述第二系统信息用于指示组播广播服务和频率的映射关系，或者用于指示组播广播服务控制信道MCCH的配置参数。
在本申请实施方式中，提供了一种第四信息和/或第五信息的可能的具体实施方式，具体为，第四信息和/或第五信息可以包括第二系统信息；或者，第四信息和/或第五信息可以以第二系统信息块的形式传输。 其中，第二系统信息用于指示组播广播服务和频率的映射关系，比如，可以对应于系统信息块SIB21；或者，第二系统信息用于指示组播广播服务控制信道(MBS control channel，MCCH)的配置参数，比如，可以对应于系统信息块SIB20。
第二方面，本申请实施例提供了一种通信方法，该方法包括：
第一网络设备接收终端设备发送的第一信息，所述第一信息包括所述终端设备感兴趣接收或正在接收的第一广播服务的信息，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
所述第一网络设备与所述终端设备进行小数据传输SDT，并且所述第一网络设备向所述终端设备提供所述第一广播服务，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
本申请实施例中，提供了一种通信方法，第一网络设备接收终端设备发送的第一信息，该第一信息包括了终端设备感兴趣接收或正在接收的第一广播服务的信息，该第一信息具体可以是组播广播业务(multicast broadcast service，MBS)兴趣指示信息(MBS Interest Indication，MII)，用于指示终端设备感兴趣接收或正在接收的MBS广播服务的信息，例如MBS广播服务的频率、MBS广播服务的标识信息、MBS广播与单播和MBS组播接收相比的优先级信息等，第一网络设备在与处于RRC非活动态的终端设备进行SDT时，基于该第一信息向终端设备提供第一广播服务。本申请中的终端设备感兴趣接收的广播服务还可以指终端设备未接收但是待接收的广播服务。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第一广播服务的场景下，第一网络设备可以通过终端设备上报的第一信息，得知终端设备在进行SDT的过程中还在接收第一广播服务，从而第一网络设备可以对SDT和第一广播服务进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
在一种可能的实施方式中，所述方法还包括：
所述第一网络设备在不同时隙上向所述终端设备发送所述SDT和所述第一广播服务的数据。所述SDT可以理解为下行SDT数据(DL SDT data)。所述在不同时隙上发送所述SDT和所述第一广播服务的数据可以理解为/替换为在不同时隙上发送所述SDT的PDSCH和发送所述第一广播服务的PDSCH/GC-PDSCH，或者理解为以时隙间时分复用(inter-slot TDM)的方式发送所述SDT的PDSCH和所述第一广播服务的PDSCH/GC-PDSCH。
在本申请实施方式中，提供了一种调度SDT和第一广播服务的可能的具体实施方式，具体为，第一网络设备通过时隙间时分复用(inter-slot TDM)调度SDT和第一广播服务，比如在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第一广播服务的数据，使终端设备可以在不同时隙上接收来自于第一网络设备的SDT和第一广播服务。通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备感兴趣接收或正在接收来自于第一网络设备的第一广播服务，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第一广播服务的信息，从而可以通过在不同时隙上调度SDT和第一广播服务的数据，使终端设备即使不具备在同一个时隙上接收单播数据和广播数据的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第一广播服务的数据。
终端设备向第一网络设备发送第一信息，可以表示终端设备支持接收MBS广播服务，则终端设备必选支持用于传输单播数据的PDSCH和用于传输MBS广播数据的PDSCH/GC-PDSCH的时隙间时分复用(inter-slot TDM)接收，因此第一网络设备按照时隙间时分复用发送SDT和第一广播服务的数据，可以保证终端设备能够在SDT的过程中接收到第一广播服务，避免造成误码和/或丢包，从而保证SDT和MBS广播服务的业务质量。当终端设备不支持在同一时隙内接收单播数据和MBS广播数据时，在无上下文重定位的SDT场景下，第一网络设备没有UE能力信息，如果第一网络设备不知道终端设备正在接收第一广播服务，当第一网络设备在同一时隙内调度/发送SDT数据(SDT可以理解为一种单播传输方式)和第一广播服务的数据时，则会导致终端设备无法接收到SDT和广播数据，或者终端设备只能接收到SDT或广播数据二者其中之一，造成数据误码和/或丢包，影响业务接收质量。因此，通过本申请方案，可以避免上述问题。
在一种可能的实施方式中，所述方法还包括：
所述第一网络设备向第二网络设备发送所述第一信息，所述第二网络设备为连接所述终端设备与核心 网设备的网络设备；
所述第一网络设备接收来自于所述第二网络设备的第六信息，所述第六信息用于指示所述第一广播服务，所述第六信息由所述第一信息确定。
在本申请实施方式中，提供了一种用于指示第一广播服务的信息的可能的具体实施方式，具体为，第一网络设备向第二网络设备发送第一信息，并接收来自于第二网络设备的第六信息，其中，第二网络设备为连接终端设备和核心网设备的网络设备，第六信息由第二网络设备根据第一信息确定，第六信息用于指示第一广播服务。可以理解的是，第一信息可以为RRC消息，当第一网络设备接收到终端设备发送的第一信息后，由于第一网络设备不具备终端设备的完整的上下文信息，例如第一网络设备只具备所述终端设备的RLC上下文，但不具备所述终端设备的PDCP和RRC相关信息(例如PDCP上下文)，因此无法解读第一信息，第一网络设备将第一信息(具体可以为承载第一信息的RLC数据包，例如RLC SDU或PDCP PDU)转发给第二网络设备，第二网络设备具备终端设备的完整的上下文信息，例如第二网络设备具备所述终端设备的PDCP和RRC相关信息(例如PDCP上下文)，因此第二网络设备可以基于终端设备的完整的上下文信息解读第一网络设备转发的第一信息(例如接收第一网络设备转发的承载第一信息的RLC数据包，经过PDCP层处理后获得PDCP SDU，在RRC层解读PDCP SDU以获知第一信息的内容)，得到第六信息，并发送给第一网络设备，所述第六信息是基于所述第一信息得到的，所述第六信息和所述第一信息可以是同一信息，例如所述第六信息是第二网络设备通过网络设备间的接口(例如Xn接口)发送给第一网络设备的第一信息；所述第六信息和所述第一信息也可以是不同信息，例如所述第六信息包含第一信息的部分或全部内容，由第二网络设备确定/生成的，通过网络设备间的接口(例如Xn接口)发送给第一网络设备。
在一种可能的实施方式中，第一信息中包含第一广播服务的TMGI信息，其中，TMGI信息可以包含关联的公共陆地移动网络(public land mobile network，PLMN)信息，例如PLMN-index或者PLMN-Identity(PLMN identity也可以简称为PLMN ID)其中之一。当PLMN信息为PLMN-index时，第二网络设备解读/解码第一信息后，将第一信息中的PLMN-index翻译或者转换成PLMN-identity后通过第六信息发送给第一网络设备，即第二网络设备发送的第六信息是将第一信息中的PLMN-index替换为PLMN-identity生成的。如此，可以避免第一网络设备和第二网络设备的PLMN不同时，或者第一网络设备的小区和第二网络设备的小区在SIB1中指示的PLMN列表(例如plmn-IdentityInfoList)中的PLMN顺序不同时，造成第一网络设备和第二网络设备对PLMN-index理解不对齐问题(例如相同plmn-index在第一网络设备和第二网络设备对应不同的PLMN)。
在一种可能的实施方式中，所述方法还包括：
所述第一网络设备向所述第二网络设备发送第一请求消息，所述第一请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述第一网络设备接收所述第二网络设备发送的所述终端设备的部分上下文信息，所述部分上下文信息中包括第七信息，所述第七信息用于指示所述终端设备接收的第二广播服务。
在本申请实施方式中，提供了一种用于指示第二广播服务的信息的可能的具体实施方式，具体为，第一网络设备向第二网络设备发送第一请求消息，并接收第二网络设备响应于该第一请求消息发送的终端设备的部分上下文信息，其中，第一请求消息用于请求获取终端设备的上下文信息进行SDT，第二网络设备响应于该第一请求消息发送的终端设备的部分上下文信息包括第七信息，该第七信息用于指示终端设备接收的第二广播服务。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第二广播服务的场景下，第一网络设备可以通过向第二网络设备发送第一请求消息，并接收第二网络设备提供的终端设备的部分上下文信息中的第七信息，得知终端设备在进行SDT的过程中还可能感兴趣接收或正在接收第二广播服务，从而第一网络设备可以对SDT和第二广播服务进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
在一种可能的实施方式中，所述方法还包括：
所述第一网络设备在接收到所述第六信息的情况下，忽略所述第七信息。
在本申请实施方式中，提供了一种第一网络设备根据第六信息或第七信息进行相应的广播服务调度的可能的具体实施方式，具体为，第一网络设备在接收到第六信息的情况下，忽略第七信息，可以理解为，第一网络设备在接收到第六信息的情况下，无论第一网络设备是否接收到第七信息，第一网络设备都将根据第六信息对SDT和相应的第一广播服务进行调度。当第一网络设备接收到第七信息中指示的广播服务与 第六信息中指示的广播服务不同时，以第六信息中指示的广播服务为准，示例性的，第七信息中指示终端设备接收广播服务1、广播服务2、广播服务3，第六信息中指示终端设备接收广播服务2和广播服务4，则第一网络设备认为终端设备感兴趣接收或正在接收的广播服务为广播服务2和广播服务4，终端设备未在接收广播服务1和广播服务3。可选的，第一网络设备在未接收到第六信息且接收到第七信息的情况下，第一网络设备将根据第七信息对SDT和相应的第二广播服务进行调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
在一种可能的实施方式中，所述方法还包括：
所述第一网络设备接收来自于所述第二网络设备的第八信息，所述第八信息用于指示所述终端设备支持或不支持M个单播数据和N个广播数据在同一个时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；和/或，
所述第一网络设备接收来自于所述第二网络设备的第九信息，所述第九信息用于指示所述终端设备支持或不支持P个单播数据和Q个广播数据在同一个时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数。
可选的，所述第八信息还用于指示所述终端设备在第一频段(band)或第一频段的载波上支持或不支持M个单播数据和N个广播数据在同一个时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；所述第八信息包括所述第一频段的标识；
可选的，所述第九信息还用于指示所述终端设备在第二频段或第二频段的载波上支持或不支持P个单播数据和Q个广播数据在同一个时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数；所述第九信息包括所述第二频段的标识；所述第一频段和所述第二频段可以为相同的频段，也可以为不同的频段。在本申请实施方式中，所述单播数据可以理解为/替换为用于传输单播(unicast)数据的PDSCH，或者小区的无线网络临时标识(Cell Radio Network Temporary Identifier，cell RNTI)加扰的PDSCH；所述广播数据可以理解为/替换为用于传输MBS广播数据的PDSCH/GC-PDSCH，或者组无线网络临时标识(Group Radio Network Temporary Identifier,G-RNTI)加扰的PDSCH。单播数据和广播数据在同一时隙内(intra-slot)的时分复用/频分复用可以理解为单播的PDSCH和MBS广播的GC-PDSCH在同一时隙内(intra-slot)的时分复用/频分复用。
在本申请实施方式中，提供了一种接收第八信息和/或第九信息的可能的具体实施方式，具体为，第一网络设备接收来自于第二网络设备的第八信息和/或第九信息。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供广播服务的场景下，第一网络设备可以根据第八信息和/或第九信息，得知终端设备支持或不支持在同一个时隙内一个或多个单播数据和一个或多个广播数据的频分复用TDM接收或时分复用TDM接收，从而第一网络设备可以对SDT和广播服务进行相应的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
第三方面，本申请实施例提供了一种通信方法，该方法包括：
第二网络设备向第一网络设备发送小数据传输SDT和第六信息，所述第六信息用于指示第一广播服务，所述第一广播服务为终端设备感兴趣接收或正在接收的广播服务，所述第二网络设备为连接所述终端设备与核心网设备的网络设备，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述SDT通过所述第一网络设备发送至所述终端设备。
本申请实施例中，提供了一种发送SDT和第六信息的可能的具体实施方式，具体为，第二网络设备向第一网络设备发送SDT和第六信息，其中，第六信息用于指示终端设备感兴趣接收或正在接收的第一广播服务，SDT和第六信息所指示的第一广播服务由第一网络设备发送至终端设备。本申请中的终端设备感兴趣接收的广播服务还可以指终端设备未接收但是待接收的广播服务。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第一广播服务的场景下，第二网络设备可以通过向第一网络设备发送第六信息，使第一网络设备得知终端设备在进行SDT的过程中还在接收第一广播服务，从而第一网络设备可以对SDT和第一广播服务进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留 的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
在一种可能的实施方式中，所述方法还包括：
所述第二网络设备接收所述第一网络设备发送的第一信息，所述第一信息包括所述第一广播服务的信息；
所述第二网络设备根据所述第一信息，确定所述第六信息。
在本申请实施方式中，提供了一种确定第六信息的可能的具体实施方式，具体为，第一网络设备向第二网络设备发送第一信息，该第一信息包括第一广播服务的信息，第二网络设备根据第一信息确定第六信息，第六信息用于指示第一广播服务。可以理解的是，第一信息可以为RRC消息，当第一网络设备接收到终端设备发送的第一信息后，由于第一网络设备不具备终端设备的完整的上下文信息，例如第一网络设备只具备所述终端设备的RLC上下文，但不具备所述终端设备的PDCP和RRC相关信息(例如PDCP上下文)，因此无法解读第一信息，第一网络设备将第一信息(具体可以为承载第一信息的RLC数据包，例如RLC SDU或PDCP PDU)转发给第二网络设备，第二网络设备具备终端设备的完整的上下文信息，例如第二网络设备具备所述终端设备的PDCP和RRC相关信息(例如PDCP上下文)，因此第二网络设备可以基于终端设备的完整的上下文信息解读第一网络设备转发的第一信息(例如接收第一网络设备转发的承载第一信息的RLC数据包，经过PDCP层处理后获得PDCP SDU，在RRC层解读PDCP SDU以获知第一信息的内容)，得到第六信息，并发送给第一网络设备，所述第六信息是基于所述第一信息得到的，所述第六信息和所述第一信息可以是同一信息，例如所述第六信息是第二网络设备通过网络设备间的接口(例如Xn接口)发送给第一网络设备的第一信息；所述第六信息和所述第一信息也可以是不同信息，例如所述第六信息包含第一信息的部分或全部内容，由第二网络设备确定/生成的，通过网络设备间的接口(例如Xn接口)发送给第一网络设备。
在一种可能的实施方式中，第一信息中包含第一广播服务的TMGI信息，其中，TMGI信息可以包含关联的公共陆地移动网络(public land mobile network，PLMN)信息，例如PLMN-index或者PLMN-Identity(PLMN identity也可以简称为PLMN ID)其中之一。当PLMN信息为PLMN-index时，第二网络设备解读/解码第一信息后，将第一信息中的PLMN-index翻译或者转换成PLMN-identity后通过第六信息发送给第一网络设备，即第二网络设备发送的第六信息是将第一信息中的PLMN-index替换为PLMN-identity生成的。如此，可以避免第一网络设备和第二网络设备的PLMN不同时，或者第一网络设备的小区和第二网络设备的小区在SIB1中指示的PLMN列表(例如plmn-IdentityInfoList)中的PLMN顺序不同时，造成第一网络设备和第二网络设备对PLMN-index理解不对齐问题(即相同plmn-index在第一网络设备和第二网络设备对应不同的PLMN)。
在一种可能的实施方式中，所述方法还包括：
所述第二网络设备接收所述第一网络设备发送的第一请求消息，所述第一请求消息用于请求获取所述终端设备的上下文信息进行SDT；
响应于所述第一请求消息，所述第二网络设备向所述第一网络设备发送所述终端设备的部分上下文信息，所述部分上下文信息中包括第七信息，所述第七信息用于指示所述终端设备接收的第二广播服务。
在本申请实施方式中，提供了一种用于指示第二广播服务的信息的可能的具体实施方式，具体为，第二网络设备接收第一网络设备发送的第一请求消息，并响应于该第一请求消息向第一网络设备发送终端设备的部分上下文信息，其中，第一请求消息用于请求获取终端设备的上下文信息进行SDT，第二网络设备响应于该第一请求消息发送的终端设备的部分上下文信息包括第七信息，该第七信息用于指示终端设备接收的第二广播服务。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第二广播服务的场景下，第二网络设备可以通过接收第一网络设备发送的第一请求消息，并响应于该第一请求消息向第一网络设备发送终端设备的部分上下文信息中的第七信息，使第一网络设备得知终端设备在进行SDT的过程中还可能感兴趣接收或正在接收第二广播服务，从而第一网络设备可以对SDT和第二广播服务进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
在一种可能的实施方式中，所述第二网络设备向第一网络设备发送第六信息和/或第七信息之前，所述方法还包括：
所述第二网络设备根据所述终端设备的能力信息，确定所述终端设备不支持在同一个时隙内接收单播数据和广播数据。
在本申请实施方式中，提供了一种确定终端设备的能力信息的可能的具体实施方式，具体为，第二网络设备根据终端设备的能力信息，可以确定终端设备支持或不支持在同一个时隙内接收单播数据和广播数据，当第二网络设备确定终端设备不支持在同一时隙内接收单播数据和广播数据，则第二网络设备确定向第一网络设备发送第六信息和/或第七信息，使第一网络设备可以对SDT和广播服务进行恰当的调度，例如通过时隙间时分复用(inter-slot TDM)的方式发送SDT数据和广播数据至所述终端设备，使终端设备可以接收到SDT和广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
第四方面，本申请实施例提供了一种通信方法，该方法包括：
终端设备接收第一网络设备发送的小数据传输SDT和第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述第一组播会话为所述终端设备加入的组播会话，用于指示所述第一组播会话的第十信息由第二网络设备发送至所述第一网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备。
本申请实施例中，提供了一种通信方法，处于RRC非活动态的终端设备与第一网络设备进行SDT，并且终端设备感兴趣接收或正在接收来自第一网络设备的第一组播会话的数据，其中，该第一组播会话为终端设备加入的组播会话，第一网络设备根据第十信息向终端设备发送第一组播会话的数据，第十信息由第二网络设备发送至第一网络设备。本申请中的终端设备感兴趣接收的组播会话还可以指终端设备未接收但是待接收的组播会话。通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第一组播会话的数据的场景下，第二网络设备通过将用于指示第一组播会话的第十信息发送给第一网络设备，使第一网络设备知道终端设备在进行SDT的过程中还加入了第一组播会话，从而当第一网络设备能够向所述终端设备提供第一组播会话时，第一网络设备可以对SDT和第一组播会话的数据进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第一组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第一组播会话的数据，等等，使终端设备在无UE上下文重定位的SDT场景下，也可以接收到SDT和第一组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
在一种可能的实施方式中，所述第十信息承载于所述第二网络设备向所述第一网络设备发送的所述终端设备的部分上下文信息中。
在本申请实施方式中，提供了一种第十信息的可能的具体实施方式，具体为，第十信息承载于第二网络设备向第一网络设备发送的终端设备的部分上下文信息中。通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第一组播会话的数据的场景下，第二网络设备通过将终端设备的部分上下文信息发送给第一网络设备，该终端设备的部分上下文信息包括用于指示第一组播会话的第十信息，使第一网络设备知道终端设备在进行SDT的过程中还加入了第一组播会话，从而第一网络设备可以对SDT和第一组播会话的数据进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第一组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第一组播会话的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第一组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
第五方面，本申请实施例提供了一种通信方法，该方法包括：
第一网络设备接收来自于第二网络设备的第十信息，所述第十信息用于指示终端设备加入的第一组播会话，例如所述第十信息为组播会话的TMGI信息；所述第一网络设备为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
所述第一网络设备向所述终端设备发送小数据传输SDT和所述第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
本申请实施例中，提供了一种通信方法，第一网络设备接收第二网络设备发送的第十信息，该第十信息用于指示终端设备加入的第一组播会话的信息，该第十信息具体可以是第一组播会话的TMGI信息，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备基于该第十信息向终端设备提供第一组播会话的数据。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第一组播会话的数据的场景下，第一网络设备可以通过第二网络设备发送的第十信息，得知终端设备在进行SDT的过程中还加入了第一组播会话并在接收 第一组播会话的数据，从而第一网络设备可以对SDT和第一组播会话的数据进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第一组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第一组播会话的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以到接收SDT和组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
在一种可能的实施方式中，所述第一网络设备接收来自于第二网络设备的第十信息，包括：
所述第一网络设备向所述第二网络设备发送第二请求消息，所述第二请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述第一网络设备接收所述第二网络设备发送的所述终端设备的部分上下文信息，所述部分上下文信息中包括所述第十信息。
在本申请实施方式中，提供了一种接收第十信息的可能的具体实施方式，具体为，第一网络设备向第二网络设备发送第二请求消息，并接收第二网络设备响应于该第二请求消息发送的终端设备的部分上下文信息，其中，第二请求消息用于请求获取终端设备的上下文信息进行SDT，第二网络设备响应于该第二请求消息发送的终端设备的部分上下文信息包括第十信息，该第十信息用于指示终端设备加入的第一组播会话的信息。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第一组播会话的场景下，第一网络设备可以通过向第二网络设备发送第二请求消息，并接收第二网络设备提供的终端设备的部分上下文信息中的第十信息，得知终端设备在进行SDT的过程中还加入了第一组播会话，从而第一网络设备可以对SDT和第一组播会话的数据进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第一组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第一组播会话的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第一组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
在一种可能的实施方式中，所述方法还包括：
所述第一网络设备在不同时隙上向所述终端设备发送所述SDT和所述第一组播会话的数据。所述SDT可以理解为下行SDT数据(DL SDT data)。所述在不同时隙上发送所述SDT和所述第一组播会话的数据可以理解为/替换为在不同时隙上发送所述SDT的PDSCH和发送所述第一组播会话的PDSCH/GC-PDSCH，或者理解为以时隙间时分复用(inter-slot TDM)的方式发送所述SDT的PDSCH和所述第一组播会话的PDSCH/GC-PDSCH。
在本申请实施方式中，提供了一种调度SDT和第一组播会话的数据的可能的具体实施方式，具体为，第一网络设备通过时隙间时分复用(inter-slot TDM)调度SDT和第一组播会话的数据，比如在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第一组播会话的数据，使终端设备可以在不同时隙上接收来自于第一网络设备的SDT和第一组播会话的数据。通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备加入了来自于第一网络设备的第一组播会话，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第一组播会话的信息，从而可以通过在不同时隙上调度SDT和第一组播会话的数据，使终端设备即使不具备在同一个时隙上接收单播数据和组播数据的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第一组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
在一种可能的实施方式中，所述方法还包括：
所述第一网络设备接收来自于所述第二网络设备的第十一信息，所述第十一信息用于指示所述终端设备支持或不支持M个单播数据和N个组播数据在同一时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；和/或，
所述第一网络设备接收来自于所述第二网络设备的第十二信息，所述第十二信息用于指示所述终端设备支持或不支持P个单播数据和Q个组播数据在同一时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数。
可选的，所述第十一信息还用于指示所述终端设备在第一频段或第一频段的载波上支持或不支持M个单播数据和N个组播数据在同一个时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；所述第十一信息包括所述第一频段的标识；
可选的，所述第十二信息还用于指示所述终端设备在第二频段或第二频段的载波上支持或不支持P个单播数据和Q个组播数据在同一个时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数； 所述第十二信息包括所述第二频段的标识；所述第一频段和所述第二频段可以为相同的频段，也可以为不同的频段。
在本申请实施方式中，所述单播数据可以理解为/替换为用于传输单播(unicast)数据的PDSCH，或者小区的无线网络临时标识(Cell Radio Network Temporary Identifier，cell RNTI)加扰的PDSCH；所述组播数据可以理解为/替换为用于传输MBS组播数据的PDSCH/GC-PDSCH，或者组无线网络临时标识(Group Radio Network Temporary Identifier,G-RNTI)加扰的PDSCH。单播数据和组播数据在同一时隙内(intra-slot)的时分复用/频分复用可以理解为单播的PDSCH和MBS组播的GC-PDSCH在同一时隙内(intra-slot)的时分复用/频分复用。
在本申请实施方式中，提供了一种接收第十一信息和/或第十二信息的可能的具体实施方式，具体为，第一网络设备接收来自于第二网络设备的第十一信息和/或第十二信息。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供组播会话的场景下，第一网络设备可以根据第十一信息和/或第十二信息，得知终端设备支持或不支持在同一个时隙内一个或多个单播数据和一个或多个组播数据的频分复用TDM接收或时分复用TDM接收，从而第一网络设备可以对SDT和组播会话的数据进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
第六方面，本申请实施例提供了一种通信方法，该方法包括：
第二网络设备向第一网络设备发送小数据传输SDT和第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
所述SDT和所述第一组播会话的数据由所述第一网络设备发送至所述终端设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输。
本申请实施例中，提供了一种发送SDT和第十信息的可能的具体实施方式，具体为，第二网络设备向第一网络设备发送SDT和第十信息，其中，第十信息用于指示终端设备加入的第一组播会话，SDT和第十信息所指示的第一组播会话的数据由第一网络设备发送至终端设备。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第一组播会话的场景下，第二网络设备可以通过向第一网络设备发送第十信息，使第一网络设备得知终端设备在进行SDT的过程中还在接收第一组播会话的数据，从而第一网络设备可以对SDT和第一组播会话的数据进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第一组播会话的数据，避免调度超出终端设备的能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
在一种可能的实施方式中，所述第二网络设备向第一网络设备发送第十信息，包括：
所述第二网络设备接收所述第一网络设备发送的第二请求消息，所述第二请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述第二网络设备向所述第一网络设备发送所述终端设备的部分上下文信息，所述部分上下文信息中包括所述第十信息。
在本申请实施方式中，提供了一种发送第十信息的可能的具体实施方式，具体为，第二网络设备接收第一网络设备发送的第二请求消息，并响应于该第二请求消息向第一网络设备发送终端设备的部分上下文信息，其中，第二请求消息用于请求获取终端设备的上下文信息进行SDT，第二网络设备响应于该第二请求消息发送的终端设备的部分上下文信息包括第十信息，该第十信息用于指示终端设备加入的第一组播会话的信息。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第一组播会话的场景下，第二网络设备可以通过接收第一网络设备发送的第二请求消息，并响应于该第二请求消息向第一网络设备发送终端设备的部分上下文信息中的第十信息，使第一网络设备得知终端设备在进行SDT的过程中还加入了第一组播会话，从而第一网络设备可以对SDT和第一组播会话的数据进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收SDT和第一组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
在一种可能的实施方式中，所述SDT和所述第一组播会话的数据由所述第一网络设备在不同时隙上发 送至所述终端设备。所述SDT可以理解为下行SDT数据(DL SDT data)。所述在不同时隙上发送所述SDT和所述第一组播会话的数据可以理解为/替换为在不同时隙上发送所述SDT的PDSCH和发送所述第一组播会话的PDSCH/GC-PDSCH，或者理解为以时隙间时分复用(inter-slot TDM)的方式发送所述SDT的PDSCH和所述第一组播会话的PDSCH/GC-PDSCH。
在本申请实施方式中，提供了一种调度SDT和第一组播会话的数据的可能的具体实施方式，具体为，第一网络设备通过时隙间时分复用(inter-slot TDM)调度SDT和第一组播会话的数据，比如在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第一组播会话的数据，使终端设备可以在不同时隙上接收来自于第一网络设备的SDT和第一组播会话的数据。通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备加入了来自于第一网络设备的第一组播会话，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第一组播会话的信息，从而可以通过在不同时隙上调度SDT和第一组播会话的数据，使终端设备即使不具备在同一个时隙上接收单播数据和组播数据的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第一组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
在一种可能的实施方式中，所述第二网络设备向第一网络设备发送第十信息之前，所述方法还包括：
所述第二网络设备根据所述终端设备的能力信息，确定所述终端设备不支持在同一个时隙内接收单播数据和组播数据。
在本申请实施方式中，提供了一种确定终端设备的能力信息的可能的具体实施方式，具体为，第二网络设备根据终端设备的能力信息，可以确定终端设备支持或不支持在同一个时隙内接收单播数据和组播数据，当第二网络设备确定终端设备不支持在同一个时隙内接收单播数据和组播数据，则第二网络设备确定向第一网络设备发送第十信息，使第一网络设备可以对SDT和组播会话进行恰当的调度，例如通过时隙间时分复用(inter-slot TDM)的方式发送SDT数据和组播会话的数据至所述终端设备，使终端设备可以接收到SDT和组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
第七方面，本申请实施例提供了一种通信方法，该方法包括：
终端设备与第一网络设备进行小数据传输SDT，并且所述终端设备加入了来自于所述第一网络设备的第二组播会话，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
所述终端设备向所述第一网络设备发送第十三信息，所述第十三信息用于指示所述第二组播会话，所述第十三信息用于所述第一网络设备向所述终端设备发送所述第二组播会话。
本申请实施例中，提供了一种通信方法，处于RRC非活动态的终端设备与第一网络设备进行SDT，并且终端设备加入了来自于第一网络设备的第二组播会话，终端设备向第一网络设备发送第十三信息，该第十三信息包括第二组播会话的信息，该第十三信息具体可以是第二组播会话的TMGI信息。通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第二组播会话的场景下，可以通过向第一网络设备上报第十三信息，使第一网络设备知道终端设备在进行SDT的过程中还在接收第二组播会话的数据，从而第一网络设备可以对SDT和第二组播会话进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第二组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第二组播会话的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
在一种可能的实施方式中，所述第十三信息承载于媒体接入控制控制元素MAC CE，或无线资源控制RRC消息中。
在本申请实施方式中，提供了一种第十三信息的可能的具体实施方式，具体为，第十三信息可以承载于媒体接入控制控制元素(mediaaccesscontrolcontrolelement，MAC CE)，或无线资源控制RRC消息中。通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第二组播会话的数据的场景下，终端设备向第一网络设备发送MAC CE或RRC消息，该MAC CE或RRC消息包括用于指示第二组播会话的第十三信息，使第一网络设备知道终端设备在进行SDT的过程中还加入了第二组播会话，从而第一网络设备可以对SDT和第二组播会话的数据进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二组播会话的数据，避免 调度超出终端设备的接收能力而导致的数据误码和/或丢包。
在一种可能的实施方式中，所述方法还包括：
所述终端设备在不同时隙上接收来自于所述第一网络设备的所述SDT和所述第二组播会话的数据。所述SDT可以理解为下行SDT数据(DownLink SDT data)。所述在不同时隙上接收所述SDT和所述第二组播会话的数据可以理解为/替换为在不同时隙上接收用于传输所述SDT数据的物理下行共享信道(physical downlink shared channel,PDSCH)和用于传输所述第二组播会话的数据的PDSCH或组公共PDSCH(group common physical downlink shared channel,GC-PDSCH)。
在本申请实施方式中，提供了一种调度SDT和第二组播会话的可能的具体实施方式，具体为，第一网络设备通过时隙间时分复用(inter-slot TDM)调度SDT和第二组播会话，比如在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第二组播会话的数据，使终端设备可以在不同时隙上接收来自于第一网络设备的SDT和第二组播会话的数据。通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备接收来自于第一网络设备的第二组播会话的数据，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第二组播会话的信息，从而在不同时隙上调度SDT和第二组播会话的数据，使终端设备即使不具备在同一个时隙上接收单播数据和组播数据的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第二组播会话的数据，避免调度超出终端设备的接收能力而导致的数据误码和/或丢包。
第八方面，本申请实施例提供了一种通信方法，该方法包括：
第一网络设备接收终端设备发送的第十三信息，所述第十三信息用于指示第二组播会话，所述第二组播会话为所述终端设备加入的组播会话，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
所述第一网络设备与所述终端设备进行小数据传输SDT，并且所述第一网络设备向所述终端设备发送所述第二组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
本申请实施例中，提供了一种通信方法，第一网络设备接收终端设备发送的第十三信息，该第十三信息用于指示终端设备加入的第二组播会话的信息，该第十三信息具体可以是第二组播会话的TMGI信息，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备基于该第十三信息向终端设备提供第二组播会话。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第二组播会话的场景下，第一网络设备可以通过终端设备上报的第十三信息，得知终端设备在进行SDT的过程中还在接收第二组播会话的数据，从而第一网络设备可以对SDT和第二组播会话的数据进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第二组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第二组播会话的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
在一种可能的实施方式中，所述第一网络设备与所述终端设备进行小数据传输SDT，并且所述第一网络设备向所述终端设备发送所述第二组播会话的数据，包括：
所述第一网络设备在不同时隙上向所述终端设备发送所述SDT和所述第二组播会话的数据。所述SDT可以理解为下行SDT数据(DL SDT data)。所述在不同时隙上发送所述SDT和所述第二组播会话的数据可以理解为/替换为在不同时隙上发送所述SDT的PDSCH和发送所述第二组播会话的PDSCH/GC-PDSCH，或者理解为以时隙间时分复用(inter-slot TDM)的方式发送所述SDT的PDSCH和所述第二组播会话的PDSCH/GC-PDSCH。
在本申请实施方式中，提供了一种调度SDT和第二组播会话的可能的具体实施方式，具体为，第一网络设备通过时隙间时分复用(inter-slot TDM)调度SDT和第二组播会话，比如在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第二组播会话的数据，使终端设备可以在不同时隙上接收来自于第一网络设备的SDT和第二组播会话的数据。通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备加入了来自于第一网络设备的第二组播会话，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第二组播会话的信息，从而可以通过在不同时隙上调度SDT和第二组播会话的数据，使终端设备即使不具备在同一个时隙上接收单播数据和组播数据的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第二组播会话的数据。
终端设备向第一网络设备发送第十三信息，可以表示终端设备支持接收MBS组播服务，则终端设备必选支持用于传输单播数据的PDSCH和用于传输MBS组播数据的PDSCH/GC-PDSCH的时隙间时分复用(inter-slot TDM)接收，因此第一网络设备按照时隙间时分复用发送SDT和第二组播会话的数据，可以保证终端设备能够在SDT的过程中接收到第二组播会话的数据，避免造成误码和/或丢包，从而保证SDT和MBS组播服务的业务质量。当终端设备不支持在同一时隙内接收单播数据和MBS组播数据时，在无上下文重定位的SDT场景下，第一网络设备没有UE能力信息，如果第一网络设备不知道终端设备正在接收第二组播会话，当第一网络设备在同一时隙内调度/发送SDT数据(SDT可以理解为一种单播传输方式)和第二组播会话的数据时，则会导致终端设备无法接收到SDT和组播数据，或者终端设备只能接收到SDT或组播数据二者其中之一，造成数据误码和/或丢包，影响业务接收质量。因此，通过本申请方案，可以避免上述问题。
在一种可能的实施方式中，所述第十三信息承载于媒体接入控制控制元素MAC CE，或无线资源控制RRC消息中。
在本申请实施方式中，提供了一种第十三信息的可能的具体实施方式，具体为，第十三信息可以承载于媒体接入控制控制元素MAC CE，或无线资源控制RRC消息中。通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第二组播会话的数据的场景下，第一网络设备接收终端设备发送的MAC CE或RRC消息，该MAC CE或RRC消息包括用于指示第二组播会话的第十三信息，使第一网络设备知道终端设备在进行SDT的过程中还加入了第二组播会话，从而第一网络设备可以对SDT和第二组播会话的数据进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二组播会话的数据，避免调度超出终端设备的接收能力而导致的数据误码和/或丢包。
第九方面，本申请实施例提供了一种通信方法，该方法包括：
第二网络设备向第一网络设备发送小数据传输SDT；其中，所述SDT和第二组播会话的数据由所述第一网络设备发送至终端设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备，所述第二组播会话为第十三信息指示所述终端设备加入的组播会话，所述第十三信息来自于所述终端设备。
本申请实施例中，提供了一种发送SDT的可能的具体实施方式，具体为，第二网络设备向第一网络设备发送SDT，其中，该SDT和第十三信息所指示的第二组播会话由第一网络设备发送至终端设备，该第十三信息用于指示终端设备加入的第二组播会话。通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第二组播会话的场景下，第二网络设备可以通过向第一网络设备发送第十三信息，使第一网络设备得知终端设备在进行SDT的过程中还在接收第二组播会话的数据，从而第一网络设备可以对SDT和第二组播会话的数据进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第二组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第二组播会话的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二组播会话的数据，避免调度超出终端设备的接收能力而导致的数据误码和/或丢包。
第十方面，本申请实施例提供了一种通信装置，该装置包括用于执行如第一方面至第九方面任一方面中任一项所述方法的模块或单元。
在一种可能的设计中，该装置包括：
收发单元，用于与第一网络设备进行小数据传输SDT，并且感兴趣接收或正在接收来自于所述第一网络设备的第一广播服务，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述通信装置驻留的小区对应的网络设备；
所述收发单元，还用于向所述第一网络设备发送第一信息，所述第一信息包括所述第一广播服务的信息，所述第一信息用于所述第一网络设备向所述通信装置提供所述第一广播服务。
在一种可能的实施方式中，所述收发单元，还用于在不同时隙上接收来自于所述第一网络设备的所述SDT和所述第一广播服务。
在一种可能的实施方式中，所述收发单元，还用于接收所述第一网络设备发送的第二信息和/或第二网 络设备发送的第三信息，所述第二网络设备为向所述通信装置发送RRC释放消息的网络设备；
处理单元，用于根据所述第二信息和/或所述第三信息，通过所述收发单元向所述第一网络设备发送所述第一信息。
在一种可能的实施方式中，所述收发单元，还用于接收所述第一网络设备发送的第四信息和/或所述第二网络设备发送的第五信息；
所述处理单元，还用于根据所述第四信息和/或所述第五信息，通过所述收发单元向所述第一网络设备发送所述第一信息，所述第一信息包括所述第一广播服务的TMGI信息
在一种可能的实施方式中，所述第三信息和/或所述第五信息承载于RRC释放消息中；
所述处理单元，还用于根据所述RRC释放消息进入RRC非活动态。
在一种可能的实施方式中，所述第二信息，和/或所述第三信息，和/或所述第四信息，和/或所述第五信息包括系统信息。
在一种可能的实施方式中，所述第二信息和/或所述第三信息包括第一系统信息，所述第一系统信息用于指示组播广播服务和频率的映射关系，或者用于指示组播广播服务控制信道MCCH的配置参数。
在一种可能的实施方式中，所述第四信息和/或所述第五信息包括第二系统信息，所述第二系统信息用于指示组播广播服务和频率的映射关系，或者用于指示组播广播服务控制信道MCCH的配置参数。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第一方面以及相应的实施方式的技术效果的介绍。
在另一种可能的设计中，该装置包括：
收发单元，用于接收终端设备发送的第一信息，所述第一信息包括所述终端设备感兴趣接收或正在接收的第一广播服务的信息，所述通信装置为所述终端设备驻留的小区对应的网络设备；
所述收发单元，还用于与所述终端设备进行小数据传输SDT，并且向所述终端设备提供所述第一广播服务，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在一种可能的实施方式中，所述收发单元，还用于在不同时隙上向所述终端设备发送所述SDT和所述第一广播服务。
在一种可能的实施方式中，所述收发单元，还用于向第二网络设备发送所述第一信息，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
所述收发单元，还用于接收来自于所述第二网络设备的第六信息，所述第六信息用于指示所述第一广播服务，所述第六信息由所述第一信息确定。
在一种可能的实施方式中，所述收发单元，还用于向所述第二网络设备发送第一请求消息，所述第一请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述收发单元，还用于接收所述第二网络设备发送的所述终端设备的部分上下文信息，所述部分上下文信息中包括第七信息，所述第七信息用于指示所述终端设备接收的第二广播服务。
在一种可能的实施方式中，处理单元，用于在接收到所述第六信息的情况下，忽略所述第七信息。
在一种可能的实施方式中，所述收发单元，还用于接收来自于所述第二网络设备的第八信息，所述第八信息用于指示所述终端设备支持或不支持M个单播数据和N个广播数据在同一个时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；和/或，
所述收发单元，还用于接收来自于所述第二网络设备的第九信息，所述第九信息用于指示所述终端设备支持或不支持P个单播数据和Q个广播数据在同一个时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第二方面以及相应的实施方式的技术效果的介绍。
在另一种可能的设计中，该装置包括：
收发单元，用于向第一网络设备发送小数据传输SDT和第六信息，所述第六信息用于指示第一广播服务，所述第一广播服务为终端设备感兴趣接收或正在接收的广播服务，所述通信装置为连接所述终端设备与核心网设备的网络设备，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述SDT通过所述第一网络设备发送至所述终端设备。
在一种可能的实施方式中，所述收发单元，还用于接收所述第一网络设备发送的第一信息，所述第一信息包括所述第一广播服务的信息；
处理单元，用于根据所述第一信息，确定所述第六信息。
在一种可能的实施方式中，所述收发单元，还用于接收所述第一网络设备发送的第一请求消息，所述第一请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述收发单元，还用于响应于所述第一请求消息，向所述第一网络设备发送所述终端设备的部分上下文信息，所述部分上下文信息中包括第七信息，所述第七信息用于指示所述终端设备接收的第二广播服务。
在一种可能的实施方式中，所述处理单元，还用于根据所述终端设备的能力信息，确定所述终端设备不支持在同一个时隙内接收单播数据和广播数据。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第三方面以及相应的实施方式的技术效果的介绍。
在另一种可能的设计中，该装置包括：
收发单元，用于接收第一网络设备发送的小数据传输SDT和第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输，所述第一网络设备为所述通信装置驻留的小区对应的网络设备，所述第一组播会话为所述通信装置加入的组播会话，用于指示所述第一组播会话的第十信息由第二网络设备发送至所述第一网络设备，所述第二网络设备为连接所述通信装置与核心网设备的网络设备。
在一种可能的实施方式中，所述第十信息承载于所述第二网络设备向所述第一网络设备发送的所述通信装置的部分上下文信息中。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第四方面以及相应的实施方式的技术效果的介绍。
在另一种可能的设计中，该装置包括：
收发单元，用于接收来自于第二网络设备的第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述通信装置为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
所述收发单元，还用于向所述终端设备发送小数据传输SDT和所述第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在一种可能的实施方式中，所述收发单元，还用于向所述第二网络设备发送第二请求消息，所述第二请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述收发单元，还用于接收所述第二网络设备发送的所述终端设备的部分上下文信息，所述部分上下文信息中包括所述第十信息。
在一种可能的实施方式中，所述收发单元，还用于在不同时隙上向所述终端设备发送所述SDT和所述第一组播会话的数据。
在一种可能的实施方式中，所述收发单元，还用于接收来自于所述第二网络设备的第十一信息，所述第十一信息用于指示所述终端设备支持或不支持M个单播数据和N个组播数据在时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；和/或，
所述收发单元，还用于接收来自于所述第二网络设备的第十二信息，所述第十二信息用于指示所述终端设备支持或不支持P个单播数据和Q个组播数据在时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第五方面以及相应的实施方式的技术效果的介绍。
在另一种可能的设计中，该装置包括：
收发单元，用于向第一网络设备发送小数据传输SDT和第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述通信装置为连接所述终端设备与核心网设备的网络设备；
所述SDT和所述第一组播会话的数据由所述第一网络设备发送至所述终端设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输。
在一种可能的实施方式中，所述收发单元，还用于接收所述第一网络设备发送的第二请求消息，所述第二请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述收发单元，还用于向所述第一网络设备发送所述终端设备的部分上下文信息，所述部分上下文信息中包括所述第十信息。
在一种可能的实施方式中，所述SDT和所述第一组播会话的数据由所述第一网络设备在不同时隙上发送至所述终端设备。
在一种可能的实施方式中，处理单元，用于根据所述终端设备的能力信息，确定所述终端设备不支持在同一个时隙内接收单播数据和组播数据。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第六方面以及相应的实施方式的技术效果的介绍。
在另一种可能的设计中，该装置包括：
收发单元，用于与第一网络设备进行小数据传输SDT，并且加入了来自于所述第一网络设备的第二组播会话，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述通信装置驻留的小区对应的网络设备；
所述收发单元，还用于向所述第一网络设备发送第十三信息，所述第十三信息用于指示所述第二组播会话，所述第十三信息用于所述第一网络设备向所述通信装置发送所述第二组播会话。
在一种可能的实施方式中，所述第十三信息承载于媒体接入控制控制元素MAC CE，或无线资源控制RRC消息中。
在一种可能的实施方式中，所述收发单元，还用于在不同时隙上接收来自于所述第一网络设备的所述SDT和所述第二组播会话的数据。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第七方面以及相应的实施方式的技术效果的介绍。
在另一种可能的设计中，该装置包括：
收发单元，用于接收终端设备发送的第十三信息，所述第十三信息用于指示第二组播会话，所述第二组播会话为所述终端设备加入的组播会话，所述通信装置为所述终端设备驻留的小区对应的网络设备；
所述收发单元，还用于与所述终端设备进行小数据传输SDT，并且向所述终端设备发送所述第二组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在一种可能的实施方式中，所述收发单元，还用于在不同时隙上向所述终端设备发送所述SDT和所述第二组播会话的数据。
在一种可能的实施方式中，所述第十三信息承载于媒体接入控制控制元素MAC CE，或无线资源控制RRC消息中。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第八方面以及相应的实施方式的技术效果的介绍。
在另一种可能的设计中，该装置包括：
收发单元，还用于向第一网络设备发送小数据传输SDT；其中，所述SDT和第二组播会话的数据由所述第一网络设备发送至终端设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述通信装置为连接所述终端设备与核心网设备的网络设备，所述第二组播会话为第十三信息指示所述终端设备加入的组播会话，所述第十三信息来自于所述终端设备。
关于第十方面以及任一项可能的实施方式所带来的技术效果，可参考对应于第九方面以及相应的实施方式的技术效果的介绍。
第十一方面，本申请实施例提供了一种通信装置，该通信装置包括处理器。该处理器与存储器耦合，可用于执行存储器中的指令，以实现上述第一方面至第九方面任一方面以及任一项可能的实施方式的方法。可选地，该通信装置还包括存储器。可选地，该通信装置还包括通信接口，处理器与通信接口耦合。
第十二方面，本申请实施例提供了一种通信装置，包括：逻辑电路和通信接口。所述通信接口，用于接收信息或者发送信息；所述逻辑电路，用于通过所述通信接口接收信息或者发送信息，使得所述通信装置执行上述第一方面至第九方面任一方面以及任一项可能的实施方式的方法。
第十三方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质用于存储计算机程序(也可以称为代码，或指令)；当所述计算机程序在计算机上运行时，使得上述第一方面至第九方面任一方面以及任一项可能的实施方式的方法被实现。
第十四方面，本申请实施例提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序(也可以称为代码，或指令)；当所述计算机程序被运行时，使得计算机执行上述第一方面至第九方面任一方 面以及任一项可能的实施方式的方法。
第十五方面，本申请实施例提供一种芯片，该芯片包括处理器，所述处理器用于执行指令，当该处理器执行所述指令时，使得该芯片执行上述第一方面至第九方面任一方面以及任一项可能的实施方式的方法。可选的，该芯片还包括通信接口，所述通信接口用于接收信号或发送信号。
第十六方面，本申请实施例提供一种通信系统，所述通信系统包括至少一个如第十方面所述的通信装置，或第十一方面所述的通信装置，或第十二方面所述的通信装置，或第十五方面所述的芯片。
第十七方面，本申请实施例提供了一种通信系统，包括终端设备、第一网络设备、第二网络设备；其中，所述终端设备用于执行上述第一方面以及任一项可能的实施方式的方法，所述第一网络设备用于执行上述第二方面以及任一项可能的实施方式的方法，所述第二网络设备用于执行上述第三方面以及任一项可能的实施方式的方法；或者，所述终端设备用于执行上述第四方面以及任一项可能的实施方式的方法，所述第一网络设备用于执行上述第五方面以及任一项可能的实施方式的方法，所述第二网络设备用于执行上述第六方面以及任一项可能的实施方式的方法；或者，所述终端设备用于执行上述第七方面以及任一项可能的实施方式的方法，所述第一网络设备用于执行上述第八方面以及任一项可能的实施方式的方法，所述第二网络设备用于执行上述第九方面以及任一项可能的实施方式的方法。
此外，在执行上述第一方面至第九方面任一方面以及任一项可能的实施方式所述的方法的过程中，上述方法中有关发送信息和/或接收信息等的过程，可以理解为由处理器输出信息的过程，和/或，处理器接收输入的信息的过程。在输出信息时，处理器可以将信息输出给收发器(或者通信接口、或发送模块)，以便由收发器进行发射。信息在由处理器输出之后，还可能需要进行其他的处理，然后才到达收发器。类似的，处理器接收输入的信息时，收发器(或者通信接口、或发送模块)接收信息，并将其输入处理器。更进一步的，在收发器收到该信息之后，该信息可能需要进行其他的处理，然后才输入处理器。
基于上述原理，举例来说，前述方法中提及的发送信息可以理解为处理器输出信息。又例如，接收信息可以理解为处理器接收输入的信息。
可选的，对于处理器所涉及的发射、发送和接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则均可以更加一般性的理解为处理器输出和接收、输入等操作。
可选的，在执行上述第一方面至第九方面任一方面以及任一项可能的实施方式所述的方法的过程中，上述处理器可以是专门用于执行这些方法的处理器，也可以是通过执行存储器中的计算机指令来执行这些方法的处理器，例如通用处理器。上述存储器可以为非瞬时性(non-transitory)存储器，例如只读存储器(Read Only Memory，ROM)，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
在一种可能的实施方式中，上述至少一个存储器位于装置之外。
在又一种可能的实施方式中，上述至少一个存储器位于装置之内。
在又一种可能的实施方式之中，上述至少一个存储器的部分存储器位于装置之内，另一部分存储器位于装置之外。
本申请中，处理器和存储器还可能集成于一个器件中，即处理器和存储器还可以被集成在一起。
本申请实施例中，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的广播服务或组播会话的场景下，可以通过向第一网络设备上报终端设备感兴趣接收或正在接收的广播服务，或已加入的组播会话，使第一网络设备知道终端设备在进行SDT的过程中还在接收广播服务或组播会话，从而第一网络设备可以对SDT、广播服务和/或组播会话进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和组播广播服务的数据，避免调度超出终端设备的接收能力而导致的数据误码和/或丢包。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对本申请实施例中所需要使用的附图作简单地介绍，显而易见地，下面所描述的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本申请实施例提供的一种通信系统的示意图；
图2为本申请实施例提供的一种终端设备状态切换示意图；
图3为本申请实施例提供的一种终端设备的RRC连接恢复流程示意图；
图4为本申请实施例提供的一种通信方法的流程示意图；
图5为本申请实施例提供的另一种通信方法的流程示意图；
图6为本申请实施例提供的又一种通信方法的流程示意图；
图7为本申请实施例提供的又一种通信方法的流程示意图；
图8为本申请实施例提供的一种通信装置的结构示意图；
图9为本申请实施例提供的一种通信装置的结构示意图；
图10为本申请实施例提供的一种芯片的结构示意图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合本申请实施例中的附图对本申请实施例进行描述。
本申请的说明书、权利要求书及附图中的术语“第一”和“第二”等是用于区别不同对象，而不是用于描述特定顺序。此外，术语“包括”和“具有”以及它们的任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、系统、产品或设备等，没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元等，或可选地还包括对于这些过程、方法、产品或设备等固有的其它步骤或单元。
在本文中提及的“实施例”意味着，结合实施例描述的特定特征、结构或特性可以包含在本申请的至少一个实施例中。在说明书中的各个位置出现该短语并不一定均是指相同的实施例，也不是与其它实施例互斥的独立的或备选的实施例。本领域技术人员可以显式地和隐式地理解的是，在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，各个实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
应当理解，在本申请中，“至少一个(项)”是指一个或者多个，“多个”是指两个或两个以上，“至少两个(项)”是指两个或三个及三个以上，“和/或”，用于描述关联对象的关联关系，表示可以存在三种关系，例如，“A和/或B”可以表示：只存在A，只存在B以及同时存在A和B三种情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b或c中的至少一项(个)，可以表示：a，b，c，“a和b”，“a和c”，“b和c”，或“a和b和c”，其中a，b，c可以是单个，也可以是多个。
本申请提供的方法可以应用于各类通信系统，例如，可以是物联网(internet of things，IoT)系统、窄带物联网(narrow band internet of things，NB-IoT)系统、长期演进(long term evolution，LTE)系统，也可以是第五代(5th-generation，5G)通信系统，以及未来通信发展中出现的新的通信系统(如6G)等。
本申请提供的技术方案还可以应用于机器类通信(machine type communication，MTC)、机器间通信长期演进技术(long term evolution-machine，LTE-M)、设备到设备(device-todevice，D2D)网络、机器到机器(machine to machine，M2M)网络、物联网(internet of things，IoT)网络或者其他网络。其中，IoT网络例如可以包括车联网。其中，车联网系统中的通信方式统称为车与任何事物(vehicle-to-everything，V2X，X可以代表任何事物)，例如，该V2X可以包括：车辆到车辆(vehicle to vehicle，V2V)通信，车辆与基础设施(vehicle to infrastructure，V2I)通信、车辆与行人之间的通信(vehicle to pedestrian，V2P)或车辆与网络(vehicle to network，V2N)通信等。示例性的，下文示出的图1中，终端设备与终端设备之间便可以通过D2D技术、M2M技术或V2X技术通信等。
请参阅图1，图1是本申请实施例提供的一种通信系统的示意图。
如图1所示，该通信系统可以包括至少一个接入网设备以及至少一个终端设备。
对于接入网设备和终端设备的介绍分别如下所示：
示例性的，接入网设备可以是下一代节点B(next generation node B，gNB)、下一代演进型基站(next generation evolved nodeB，ng-eNB)、或者未来6G通信中的接入网设备等。接入网设备可以是任意一种具有无线收发功能的设备，包括但不限于以上所示的基站。该基站还可以是未来通信系统如第六代通信系统中的基站。可选的，该接入网设备可以为无线局域网(wireless fidelity，WiFi)系统中的接入节点、无线中继节点、无线回传节点等。可选的，该接入网设备可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器。可选的，该接入网设备可以是可穿戴设备或车载设备等。可选的，该接入网设备还可以是小站，传输接收节点(transmission reception point，TRP)(或也可以称为传输点)等。可理解，该接入网设备还可以是未来演进的公共陆地移动网络(public land mobile network，PLMN)中的基站 等等。
在一些部署中，基站(如gNB)可以由集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)构成。即对接入网中的基站的功能进行拆分，将基站的部分功能部署在一个CU，将剩余功能部署在DU。且多个DU共用一个CU，可以节省成本，以及易于网络扩展。在基站的另一些部署中，CU还可以划分为CU-控制面(control plane，CP)和CU-用户面(user plan，UP)等。在基站的又一些部署中，基站还可以是开放的无线接入网(open radio access network，ORAN)架构等等，本申请对于基站的具体类型不作限定。
为便于描述，下文中将以接入网设备为基站为例，介绍本申请所涉及的方法。
示例性的，该终端设备也可称为用户设备(user equipment，UE)、终端等。终端设备是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上，如轮船上等；还可以部署在空中，例如部署在飞机、气球或卫星上等。终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等等。可理解，该终端设备还可以是未来6G网络中的终端设备或者未来演进的PLMN中的终端设备等。
可理解，本申请示出的终端设备不仅可以包括车联网中的车(如整车)、而且还可以包括车联网中的车载设备或车载终端等，本申请对于该终端设备应用于车联网时的具体形态不作限定。
为便于描述，下文中将以终端设备为UE为例，介绍本申请所涉及的方法。
如图1所示，该通信系统还可以包括至少一个核心网设备，对于核心网设备的介绍如下所示：
示例性的，该核心网设备包括用户接入控制，移动性管理，会话管理，用户安全认证，计费等业务。它由多个功能单元组成，可以分为控制面和数据面的功能实体。其中，接入与移动管理单元(access and mobility management function，AMF)，负责用户接入管理，安全认证，还有移动性管理。位置管理单元(location management function，LMF)负责对目标终端的定位服务请求进行管理和控制，处理定位相关信息。用户面单元(user plane function，UPF)负责管理用户面数据的传输，流量统计等功能。
在图1所示的通信系统中，包括一个核心网设备、两个基站和八个UE，如图1中的核心网设备、基站1和基站2，以及UE1至UE8。该通信系统中，基站1可以向UE1至UE6发送配置信息或下行控制信息(downlink control information，DCI)等下行信号，UE1至UE6可以向基站1发送SRS或物理上行共享信道(physical uplink shared channel，PUSCH)等上行信号。基站1还可以通过基站2向UE7至UE8发送下行信号，UE7至UE8可以通过基站2向基站1发送上行信号。基站2可以向UE7至UE8发送配置信息或DCI等下行信号，UE7至UE8可以向基站2发送SRS或PUSCH等上行信号。可理解，对于UE之间的通信方式，可以参考上文的描述，这里不再详述。
应理解，图1示例性地示出了一个核心网设备、两个基站和八个UE，以及各通信设备之间的通信链路。可选地，该通信系统可以包括多个基站，并且每个基站的覆盖范围内可以包括其它数量的UE，例如更多或更少的UE等，本申请对此不做限定。
上述各个通信设备，如图1中的核心网设备、基站1和基站2、UE1至UE8，可以配置多个天线。该多个天线可以包括至少一个用于发送信号的发射天线和至少一个用于接收信号的接收天线等，本申请实施例对于各个通信设备的具体结构不作限定。可选地，该通信系统还可以包括网络控制器、移动管理实体等其他网络实体，本申请实施例不限于此。
可理解，图1所示的通信系统示意图仅为示例，对于其他形式的通信系统示意图可以参考相关标准或协议等，这里不再一一详述。
下文示出的各个实施例可以适用于图1所示的通信系统，也可以适用于其他形式的通信系统，对此，下文不再赘述。
本申请提供了一种通信方法，应用于通信技术领域，如UE在非活动态下进行SDT和广播服务、组播会话的通信。为了更清楚地描述本申请的方案，下面先介绍一些与SDT和广播服务、组播会话的通信相关的知识。
请参阅图2，图2为本申请实施例提供的一种终端设备状态切换示意图。
如图2所示，为无线资源控制(radio resource control，RRC)状态以及状态之间的转换过程。5G新空口(new radio，NR)中，UE有三种RRC状态：RRC_INACTIVE(无线资源控制-非活动态)、 RRC_CONNECTED(无线资源控制-连接态)和RRC_IDLE(无线资源控制-空闲态)。RRC连接态下UE和基站之间建立了RRC连接，当没有数据传输时，基站可以将UE释放到RRC空闲态，RRC空闲态下基站和UE之间没有建立RRC连接；或者基站将UE释放到RRC非活动态，挂起(suspend)RRC连接，RRC非活动态基站仍维护UE上下文信息。NR引入RRC非活动态的好处是，相比于RRC空闲态，RRC非活动态下由于基站仍保留UE上下文，因此可以更快速地恢复RRC连接，当有业务到达时，可以降低时延。
RRC_INACTIVE(无线资源控制-非活动态)与RRC_CONNECTED(无线资源控制-连接态)和RRC_IDLE(无线资源控制-空闲态)的转换关系如图2所示。
RRC_INACTIVE(无线资源控制-非活动态)只能从RRC_CONNECTED(无线资源控制-连接态)通过RRC release(释放)消息转变，在UE从RRC_CONNECTED状态释放到RRC_INACTIVE时，基站会分配该UE一个标识I-RNTI(非活动态无线网络临时标识)，并且以此标识存储UE的上下文，此基站也叫做UE的上一个服务gNB(last serving gNB)，有时也被记为锚点gNB(anchor gNB)。
当UE请求恢复之前挂起的RRC连接或者进行无线通知区(radio notification area，RNA)更新时，UE发送RRCResumeRequest消息给当前服务基站，RRCResumeRequest消息结构中包括恢复原因值，该恢复原因值用于指示该RRCResumeRequest消息请求恢复的恢复原因，该RRCResumeRequest消息结构中还包括I_RNTI标识，当前服务基站根据I_RNTI标识去last serving gNB取回UE的上下文。
具体流程可参阅图3，图3为本申请实施例提供的一种终端设备的RRC连接恢复流程示意图。下面对图3的各个步骤进行说明：
S301：UE发送RRC连接恢复请求RRCResumeRequst给当前服务基站(gNB)，该RRCResumeRequst包含了由上一个服务基站(last serving gNB)为该UE分配的I-RNTI。
S302：gNB接收RRCResumeRequst，并根据I-RNTI中包含的gNB identity时，可以找到last serving gNB并请求其提供UE的上下文。
具体的，gNB向对应的last serving gNB发送上下文获取请求Retrieve UE context request消息。
S303：last serving gNB向gNB提供UE的上下文。
具体的，last serving gNB向gNB发送上下文获取响应Retrieve UE context response消息，该上下文获取响应消息包括UE的上下文。
S304/S305：gNB和UE完成RRC连接的恢复，在获得授权grant的情况下，可以发送用户数据。
S306：如果要求last serving gNB中缓存的下行(downlink，DL)用户数据无损，gNB需要提供转发地址。
S307/S308：gNB进行路径转换。
S309：gNB触发last serving gNB处UE的资源释放。
需要指出的是，在无法取回UE上下文时，gNB可以发送RRCSetup消息给UE，重新建立RRC连接；或者gNB可以直接发送RRCReject消息给UE，用于拒绝UE的建立请求。
由于UE具有移动性，当UE处于RRC空闲态时，网络为了找到UE，需要核心网(core network，CN)在跟踪区标识(tracking area identity，TAI)列表中的所有跟踪区域(tracking area，TA)下的所有小区下发寻呼消息(CN-initiated paging，后简称为CN寻呼)。可以看出，在这种级别的终端跟踪下，由于绝大多数寻呼消息是在UE不在的小区中下发的，所以会产生较高的寻呼消息传输开销。为了节省传输开销，针对处于RRC非活动态的UE，引入了比TA范围更小的“(RAN-based Notification Area，RNA)”的概念(一个TA范围内可以包括多个RNA，一个RNA可以包括多个小区)，RNA由gNB管理，gNB可以向RNA范围内的小区发送寻呼消息(RAN-initiated paging，后简称为RAN寻呼)。对于RAN寻呼，last serving gNB从UPF接收到下行数据或从AMF接收到下行信令时，会在RNA区域内的小区上寻呼UE，并且如果RNA区域内包括邻gNB(s)的小区，last serving gNB会通过Xn接口向邻gNB(s)传递RAN寻呼，邻gNB(s)在其小区内寻呼UE。
终端设备在RRC非活动态下，对于数据量较小且不频繁的数据传输，可以直接进行小数据传输(small data transmission，SDT)，而无需转换到RRC连接态再进行传输，从而减少由于小数据传输需求而频繁进行RRC状态转换导致的功耗和信令开销，实现降低UE功耗的目的。典型的少量且不频繁的数据传输包括但不限于：即时通讯服务、各种应用程序的推送通知，可穿戴设备的周期性定位信息，工业传感器的定期数据传输等。
其中，SDT的传输可以包括：
(1)通过随机接入信道(random access channel，RACH)的小数据传输：UE在msg3(对应四步RACH) 或msgA(对应两步RACH)中向gNB发送SDT上行数据(uplinkdata，UL data)和RRCResumeRequest；
(2)通过配置授权(configured grant，CG)资源的小数据传输：UE通过gNB在RRCRelease消息中配置的CG资源，向gNB发送SDT UL data和RRCResumeRequest。
其中，SDT的传输包括两种网络架构：
架构一：有UE上下文重定位的SDT(SDT with UE context relocation)；
架构二：没有UE上下文重定位的SDT(SDT without UE context relocation)。
由于UE在非活动态会进行移动，如果UE接入的gNB不是last serving gNB，则UL SDT数据/信令在当前服务基站(receiving gNB)缓存，然后receiving gNB触发XnAP检索UE上下文(XnAP Retrieve UE Context)流程。receiving gNB向last serving gNB指示有SDT，last serving gNB决定是否重新定位UE上下文。
架构一：如果last serving gNB决定重新定位完整的UE上下文，则将完整的UE上下文发送给receiving gNB，这称为有UE上下文重定位的SDT。这种情况下，上行SDT数据从receiving gNB发送给UPF。SDT传输结束后，receiving gNB可以向UE发送RRCRelease消息释放UE回到RRC非活动态或RRC空闲态；如果SDT过程中有下行非SDT数据或信令到达，或上行非SDT数据到达，receiving gNB可以向UE发送RRCResume消息让UE回到RRC连接态。
架构二：如果last serving gNB决定不重新定位完整的UE上下文，则向receiving gNB发送部分UE上下文(partial UE context)，其中包含处理SDT所需的SDT无线链路控制(radio link control，RLC)上下文信息，这称为无UE上下文重定位的SDT。Last serving gNB保持数据汇聚协议(packet data convergence protocol，PDCP)实体，而receiving gNB会建立SDT相关的RLC上下文，并建立SDT所需的UL/DL GTP-U tunnel，将SDT数据和/或信令转发给last serving gNB，然后由last serving gNB发送给核心网CN。SDT过程完成后(receiving gNB检测到没有更多的数据包要传输)，receiving gNB发送检索上下文确认RETRIEVE UE CONTEXT CONFIRM消息通知last serving gNB，last serving gNB控制决定是否终止SDT过程，若决定终止，则向receiving gNB发送包含了封装的RRCRelease消息的检索上下文失败RETRIEVE UE CONTEXT FAILURE给receiving gNB，receiving gNB会释放部分UE上下文(partial UE context)，并向UE发送RRCRelease消息。如果SDT过程中有下行非SDT数据或信令到达，或上行非SDT数据到达，则last serving gNB会将UE释放到RRC非活动态，否则释放到RRC空闲态。可以理解的是，此时receiving gNB没有完成的UE上下文，gNB将UE释放到非活动态后可以再次寻呼UE，以进入RRC连接态进行传输。
广播通信：是指网络设备同时向某个地理区域中的所有终端设备提供相同的特定内容数据的通信服务模式。在NR R17中，支持NR MBS广播的终端设备可以在RRC连接态、RRC空闲态、和RRC非活动态的状态下获取广播通信服务。
如果gNB在某小区上广播了SIB21(SIB21包含频率和一个区域内提供的广播业务之间的映射关系，UE可以根据SIB21确定哪个频率在该区域内提供哪些广播业务，以优先选择能够提供UE想要接收的广播业务的频率的小区进行驻留)，UE在该小区上可以在RRC连接态向gNB上报MBS兴趣指示信息(MBS Interest Indication，MII)，指示UE感兴趣接收广播的频率信息(广播的频点ARFCN)、广播会话的标识(TMGI)、广播与单播相比的优先级等。gNB通过MII获知UE正在接收或感兴趣接收的广播服务，进而根据UE能力进行合适的调度，保证同时调度的广播和单播不超过UE的能力。
示例性的，如果UE支持广播(UE上报MII可以表示该UE支持广播)，则UE必选支持单播物理下行共享信道(physical downlink shared channel，PDSCH)和广播PDSCH之间通过在不同时隙的TDM接收(可以理解为单播数据块和广播数据块在不同的时隙上接收)。此外，在UE能力信息中，UE还会上报是否支持同一时隙内单播PDSCH和广播PDSCH的TDM接收、以及同一时隙内单播和广播之间FDM接收。如果UE不支持在一个时隙内同时接收广播和单播，基站需要在不同时隙时分地调度单播和广播数据。
组播(或多播)通信：是指相同的服务和相同的特定内容数据同时提供给一组专用的UE(即并非多播服务区域中的所有UE都被授权接收数据)。通过组播会话(multicast session)向UE下发组播通信业务。在Rel-17中，UE只能在RRC连接态接收组播会话的数据。如果加入组播会话的UE处于RRC连接态，当组播会话激活时，gNB向UE发送带有组播会话相关MBS配置的RRCReconfiguration消息。当(暂时)没有用于组播会话的数据要发送到UE时，gNB可以将UE移动到RRC空闲态或非活动态。支持MBS的gNB在组播会话被CN激活时或gNB有组播会话数据要传输时，使用组通知(group notification)机制通知处于RRC空闲态或非活动态的UE有组播会话数据要下发(CN控制组播的激活/去激活，CN寻呼后，CN也可以通知gNB组播激活，触发RAN寻呼，或者组播会话数据到达gNB后触发RAN寻呼)。UE收 到组通知后，重新与gNB建立RRC连接。组通知是通过寻呼消息下发给UE的，用于组通知的寻呼消息包含MBS会话ID(即TMGI)，用于寻呼加入关联某个MBS组播会话的所有处于RRC空闲态和RRC非活动态的UE。UE收到寻呼消息后，确定寻呼消息中包含UE已经加入的组播会话的TMGI，则UE触发RRC连接建立或RRC连接恢复。
终端设备在无UE上下文重定位的小数据传输(SDT without UE context relocation)场景下，如果终端设备还感兴趣接收或正在接收组播广播服务，则服务小区对应的网络设备调度的SDT和广播组播服务的数据传输可能超出终端设备的接收能力，造成丢包或误码，影响服务质量。针对上述通信过程中存在的服务小区对应的网络设备调度的SDT和广播组播服务的数据传输可能超出终端设备的接收能力，从而造成丢包或误码的技术问题，本申请实施例中，提供了一种通信方法，可以实现终端设备在无UE上下文重定位的小数据传输场景下，服务小区对应的网络设备可以获知终端设备感兴趣接收或正在接收的组播广播服务信息以进行合理的调度和数据传输，使得终端设备可以接收到SDT和组播广播服务的数据。
请参阅图4，图4为本申请实施例提供的一种通信方法的流程示意图。该通信方法应用于通信技术领域，该通信方法包括但不限于如下步骤：
S401：终端设备与第一网络设备进行小数据传输SDT，并且终端设备感兴趣接收或正在接收来自于第一网络设备的第一广播服务。
其中，终端设备处于RRC非活动态，处于RRC非活动态的终端设备与第一网络设备进行SDT，并且终端设备感兴趣接收或正在接收来自第一网络设备的第一广播服务。本申请中的终端设备感兴趣接收的广播服务还可以指终端设备未接收但是待接收的广播服务。
可理解，本申请实施例中的终端设备为搭载了可用于执行计算机执行指令的处理器的设备，可以是手持终端(比如手机、平板电脑等)，也可以是车载终端(比如无人驾驶中的无线终端等)等，具体也可以是上述图1中的终端设备(包括但不限于如UE1至UE8中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。
可理解，本申请实施例中的第一网络设备为搭载了可用于执行计算机执行指令的处理器的设备，可以是接入网设备，比如基站、传输点TRP等，也可以是服务器，具体可以是上述图1中的接入网设备(包括但不限于如基站1和基站2中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。
S402：终端设备向第一网络设备发送第一信息，相应的，第一网络设备接收终端设备发送的第一信息。
示例性的，该第一信息可以是终端设备在SDT过程中，向第一网络设备发送的，例如承载在随机接入消息3(msg3)中，通过SRB1或SRB2发送的，该随机接入消息3中还可以包括RRC恢复请求消息RRCResumeRequest。
示例性的，该第一信息也可以是终端设备在SDT过程中，通过第一网络设备动态调度的上行资源上或在配置授权(configured grant)的资源上发送的信息。
其中，该第一信息包括第一广播服务的信息，该第一信息具体可以是组播广播业务(multicast broadcast service，MBS)兴趣指示信息(MBS Interest Indication，MII)，用于指示终端设备感兴趣接收或正在接收的MBS广播服务的信息，例如MBS广播服务的频率、MBS广播服务的标识信息、MBS广播与单播和MBS组播接收相比的优先级信息等。该第一信息用于第一网络设备在与终端设备进行SDT的过程中，还向终端设备提供第一广播服务。
通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第一广播服务的场景下，可以通过向第一网络设备上报第一信息，使第一网络设备知道终端设备在进行SDT的过程中还在接收第一广播服务，从而第一网络设备可以对SDT和第一广播服务进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第一广播服务的数据，或者通过时隙间频分复用的方式发送SDT数据和第一广播服务的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
本申请实施例中，广播服务可以指MBS广播服务(broadcast service)，组播服务可以指MBS组播服务(multicast service)。SDT包括下行/上行SDT的数据和/或信令。
在一种可能的实施例中，第一网络设备在不同时隙上发送SDT和第一广播服务，相应的，终端设备在 不同时隙上接收来自于第一网络设备的SDT和第一广播服务。
其中，SDT可以理解为下行SDT数据(DownLink SDT data)。在不同时隙上接收SDT和第一广播服务的数据可以理解为/替换为在不同时隙上接收用于传输SDT数据的物理下行共享信道(physical downlink shared channel,PDSCH)和用于传输第一广播服务的数据的PDSCH或组公共PDSCH(group common physical downlink shared channel,GC-PDSCH)。
第一网络设备在接收到第一信息后，得知终端设备在与第一网络设备进行SDT的过程中，还感兴趣接收或正在接收第一广播服务，第一网络设备通过调度SDT和第一广播服务，例如通过时隙间时分复用(inter-slot TDM)的方式发送SDT数据和第一广播服务的数据，或者通过时隙间频分复用(inter-slot FDM)的方式发送SDT数据和第一广播服务的数据，等等。比如，可以是在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第一广播服务的数据，使终端设备可以在不同时隙上接收来自于第一网络设备的SDT和第一广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备感兴趣接收或正在接收来自于第一网络设备的第一广播服务，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第一广播服务的信息，从而在不同时隙上调度SDT和第一广播服务的数据，使终端设备即使不具备在同一个时隙上接收单播数据和广播数据的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第一广播服务的数据。
可以理解的是，终端设备向第一网络设备发送第一信息，可以表示终端设备支持接收MBS广播服务，则终端设备必选支持用于传输单播数据的PDSCH和用于传输MBS广播数据的PDSCH/GC-PDSCH的时隙间时分复用(inter-slot TDM)接收，因此第一网络设备按照时隙间时分复用发送SDT和第一广播服务的数据，可以保证终端设备能够在SDT的过程中接收到第一广播服务，避免造成误码和/或丢包，从而保证SDT和MBS广播服务的业务质量。当终端设备不支持在同一时隙内接收单播数据和MBS广播数据时，在无上下文重定位的SDT场景下，第一网络设备没有UE能力信息，如果第一网络设备不知道终端设备正在接收第一广播服务，当第一网络设备在同一时隙内调度/发送SDT数据(SDT可以理解为一种单播传输方式)和第一广播服务的数据时，则会导致终端设备无法接收到SDT和广播数据，或者终端设备只能接收到SDT或广播数据二者其中之一，造成数据误码和/或丢包，影响业务接收质量。因此，通过本申请方案，可以避免上述服务小区对应的网络设备调度的SDT和广播组播服务的数据传输可能超出终端设备的接收能力，从而造成丢包或误码的问题。
在一种可能的实施例中，终端设备在确定满足一定条件的情况下，向第一网络设备发送第一信息。
示例性一：
终端设备在向第一网络设备发送第一信息之前，终端设备还接收第一网络设备发送的第二信息和/或第二网络设备发送的第三信息，并根据该第二信息和/或第三信息，确定向第一网络设备发送第一信息。
此时的第一信息包括第一广播服务的信息，该第一信息具体可以是MII，用于指示终端设备感兴趣接收或正在接收的MBS广播服务的信息，例如MBS广播服务的频率、MBS广播服务的标识信息、MBS广播与单播和MBS组播接收相比的优先级信息等。
通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第一广播服务的场景下，可以根据第一网络设备发送的第二信息来确定第一信息的上报，或者根据第二网络设备发送的第三信息来确定第一信息的上报，或者根据第一网络设备发送的第二信息和第二网络设备发送的第三信息确定第一信息的上报；也可以理解为，第一网络设备通过发送的第二信息和/或第二网络设备通过发送的第三信息来控制是否允许终端设备上报第一信息。第二信息和第三信息可以是相同的信息，也可以是不同的信息。
示例性二：
终端设备在向第一网络设备发送第一信息之前，终端设备还接收第一网络设备发送的第四信息和/或第二网络设备发送的第五信息，并根据该第四信息和/或第五信息，确定向第一网络设备发送第一信息。
此时的第一信息包括第一广播服务的临时移动组标识(temporary mobile group identity，TMGI)信息。
通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第一广播服务的场景下，可以根据第一网络设备发送的第四信息来确定在发送的第一信息中包含第一广播服务的TMGI信息，或者根据第二网络设备发送的第五信息来确定在发送的第一信息中包含第一广播服务的TMGI信息，或者根据第一网络设备发送的第四信息和第二网络设备发送的第五信息来确定在发送的第一信息中包含第一广播服务的TMGI信息。第四信息和第五信息可以是相同的信息， 也可以是不同的信息。
在一种可能的实施例中，在上述示例性一、示例性二中，第三信息和/或第五信息可以承载于RRC释放消息中。
例如，第三信息和/或第五信息可以为RRC释放消息中的一个指示位(比如1个比特位)，第三信息和第五信息可以为不同的信息，通过两个独立的比特位指示，也可以为相同的信息，通过同一个比特位指示。
示例性的，第三信息和第五信息为两个相互独立的信息时，RRC释放消息中包含第三信息，或第三信息对应的比特位置为1，指示允许终端设备上报第一信息(具体可以是MII)或指示允许终端设备在RRC非活动态上报第一信息，或指示允许终端设备在SDT过程中上报第一信息。其中，允许上报也可以理解为第二网络设备支持接收来自于RRC非活动态的终端设备上报的第一信息，或来自于终端设备在SDT过程中上报的第一信息。
示例性的，第三信息和第五信息为两个相互独立的信息时，RRC释放消息中不包含第三信息，或第三信息对应的比特位置为0，则指示不允许终端设备上报/第二网络设备不支持接收第一信息(具体可以是MII)，或指示不允许/不支持接收RRC非活动态的终端设备上报第一信息，或指示不允许/不支持接收终端设备在SDT过程中上报第一信息。
类似的，第五信息的设置和含义参考上述第三信息，示例性的，RRC释放消息中包含第五信息或第五信息对应的比特位置为1时，指示允许终端设备上报的第一信息中包含广播服务的TMGI信息/第二网络设备支持接收终端设备上报的第一信息中包含广播服务的TMGI信息，或指示允许/支持接收RRC非活动态的终端设备上报的第一信息中包含广播服务的TMGI信息，或指示允许/支持接收终端设备在SDT过程中上报的第一信息中包含广播服务的TMGI信息。
示例性的，当第五信息和第三信息为同一个信息时，或者第五信息和第三信息为同一个指示位/比特位时，当RRC释放消息中包含该信息、或该比特位/指示位置为1，指示允许终端设备上报/第二网络设备支持接收第一信息(具体可以为MII)，且第一信息中可以包含广播服务的TMGI信息。
示例性的，当第五信息和第三信息为同一个信息时，或者第五信息和第三信息为同一个指示位/比特位时，当RRC释放消息中不包含该信息、或该比特位/指示位置为0时，指示不允许终端设备上报包含了广播服务的TMGI信息的第一信息(具体可以为MII)。其他含义示例参考上文对第三信息/第五信息的描述，此处不赘述。
通过本申请实施例，第二网络设备可以通过第三信息和/或第五信息，控制终端设备对第一信息的上报，并且具有更好的后向兼容性。比如，对于老版本的网络设备，不期望RRC非活动态的终端设备上报第一信息，或不期望在SDT过程中收到终端设备上报的第一信息，则可以在RRC释放消息中不包含第三信息和/或第五信息，则终端设备不会上报第一信息；对于升级后的可以支持RRC非活动态终端设备上报第一信息/终端设备在SDT过程中上报第一信息的网络设备，可以在RRC释放消息中包含第三信息和/或第五信息。
在一种可能的实施例中，在上述示例性一、示例性二中，第二信息，和/或第三信息，和/或第四信息，和/或第五信息可以包括系统信息(System Information,SI)；或者，第二信息，和/或第三信息，和/或第四信息，和/或第五信息可以以系统信息块(System Information Bloack,SIB)的形式传输。
示例性A：
第二信息和/或第三信息可以包括第一系统信息；或者，第二信息和/或第三信息可以以第一系统信息块的形式传输。
其中，第一系统信息用于指示组播广播服务和频率的映射关系，比如，可以对应于系统信息块SIB21；或者，第一系统信息用于指示组播广播服务控制信道(MBS control channel，MCCH)的配置参数，比如，可以对应于系统信息块SIB20。
示例性B：
第四信息和/或第五信息可以包括第二系统信息；或者，第四信息和/或第五信息可以以第二系统信息块的形式传输。
其中，第二系统信息用于指示组播广播服务和频率的映射关系，比如，可以对应于系统信息块SIB21；或者，第二系统信息用于指示组播广播服务控制信道(MBS control channel，MCCH)的配置参数，比如，可以对应于系统信息块SIB20。
可以理解的是，通过上述实施例示出的第二信息，和/或第三信息，和/或第四信息，和/或第五信息，可以得到多种可能的组合方式，提供给终端设备用于控制发送第一信息。
可以理解的是，终端设备向第一网络设备发送第一信息之前，终端设备确定满足以下方式中的至少一个方式中所描述的条件：
方式一：
第二网络设备关联的第一服务小区提供系统信息块SIB21，则终端设备确定可以向第一网络设备发送第一信息。
第二网络设备关联的第一服务小区提供系统信息块SIB21，终端设备当前驻留的服务小区(关联于第一网络设备)提供系统信息块SIB20，则终端设备确定可以向第一网络设备发送第一信息，且该第一信息中可以包含广播服务的TMGI信息。
本申请实施例中，第二网络设备关联的第一服务小区提供SIB21可以理解为第一服务小区是能够提供SIB21的小区，第一服务小区可以是终端设备曾经驻留过的服务小区。一种可能的实施方式为，终端设备存储广播了SIB21的小区列表，终端设备根据上述小区列表，确定第一服务小区是否在上述小区列表中，若第一服务小区在上述列表中，则第一服务小区能够提供SIB21。
在本申请实施例中，服务小区提供SIB20可以理解为服务小区广播的SIB1中包含SIB20的调度信息，或者理解为服务小区能够提供SIB20。本申请不限定服务小区是否正在广播SIB20，服务小区可以正在广播SIB20也可以未在广播SIB20。
方式二：
第二网络设备关联的第一服务小区提供SIB21，并且终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，则终端设备确定可以向第一网络设备发送第一信息。
第二网络设备关联的第一服务小区提供SIB21，并且终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，终端设备当前驻留的服务小区提供SIB20，则终端设备确定可以向第一网络设备发送第一信息，且该第一信息中可以包含广播服务的TMGI信息。
其中，第二网络设备关联的第一服务小区提供SIB21的理解和可能的实施方式如方式一所述，此处不再赘述。
方式三：
接收到来自于第二网络设备的RRC释放消息中包含第三信息，并且终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，则终端设备确定可以向第一网络设备发送第一信息。
接收到来自于第二网络设备的RRC释放消息中包含第三信息，并且终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，接收到来自于第二网络设备的RRC释放消息中包含第五信息，则终端设备确定可以向第一网络设备发送第一信息，且该第一信息中可以包含广播服务的TMGI信息，第三信息和第五信息为不同的信息。
方式四：
第三信息和第五信息为同一个信息，接收到来自于第二网络设备的RRC释放消息中包含第三信息(或第五信息)，并且终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，则终端设备确定可以向第一网络设备发送第一信息。
第三信息和第五信息为同一个信息，接收到来自于第二网络设备的RRC释放消息中包含第三信息(或第五信息)，并且终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，终端设备当前驻留的服务小区提供SIB20，则终端设备确定可以向第一网络设备发送第一信息，且该第一信息中可以包含广播服务的TMGI信息。
方式五：
第三信息和第五信息为同一个信息，接收到来自于第二网络设备的RRC释放消息中包含第三信息(或第五信息)，并且第二网络设备关联的第一服务小区提供SIB21(可以如上述方式一所述的实施方式，此处不再赘述)，并且终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，则终端设备确定可以向第一网络设备发送第一信息。
第三信息和第五信息为同一个信息，接收到来自于第二网络设备的RRC释放消息中包含第三信息(或第五信息)，并且第二网络设备关联的第一服务小区提供SIB21(可以如上述方式一所述的实施方式，此处不再赘述)，并且终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，终端设备当前驻留的服务小区提供SIB20，则终端设备确定可以向第一网络设备发送第一信息，且该第一信息中可以包含广播服务的TMGI信息。
方式六：
终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，则终端设备确定可以向第一网络设备发送第一信息。
终端设备当前驻留的服务小区(关联于第一网络设备)提供SIB21，终端设备接收到来自于第二网络设备的RRC释放消息中包含第三信息(或第五信息)，则终端设备确定可以向第一网络设备发送第一信息，且该第一信息中可以包括广播服务的TMGI信息，该第三信息和第五信息为同一个信息。
应理解，上述六种方式仅作为示例性的方式对第二信息，和/或第三信息，和/或第四信息，和/或第五信息得到的可能的组合方式进行说明，不应以此对本申请实施例构成限定。还可以是其他经过合理变形的组合方式用于提供给终端设备控制第一信息的上报或第一信息中的TMGI的上报，本申请实施例对此不作限制。
应理解，上述提及的第二网络设备，为搭载了可用于执行计算机执行指令的处理器的设备，可以是接入网设备，比如基站、传输点TRP等，也可以是服务器，具体可以是上述图1中的接入网设备(包括但不限于如基站1和基站2中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。其中，第二网络设备为连接终端设备和核心网设备的网络设备，可以理解的是，此处终端设备和核心网设备之间的连接可以是非接入层(non access stratum，NAS)的连接。
请参阅图5，图5为本申请实施例提供的另一种通信方法的流程示意图。可以理解的是，本申请实施例中的步骤S503至S508可以视为上述图4中的实施例的合理变形或补充；或者，可以理解的是，本申请实施例中的通信方法也可以视为能单独执行的实施例，本申请对此不作限制。本申请实施例提供的通信方法应用于通信技术领域，该通信方法包括但不限于如下步骤：
S501：终端设备与第一网络设备进行小数据传输SDT，并且终端设备感兴趣接收或正在接收来自于第一网络设备的第一广播服务。
与上述步骤S401一致，此处不再赘述。
S502：终端设备向第一网络设备发送第一信息，相应的，第一网络设备接收终端设备发送的第一信息。
与上述步骤S402一致，此处不再赘述。
可理解，本申请实施例中的终端设备为搭载了可用于执行计算机执行指令的处理器的设备，可以是手持终端(比如手机、平板电脑等)，也可以是车载终端(比如无人驾驶中的无线终端等)等，具体也可以是上述图1中的终端设备(包括但不限于如UE1至UE8中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。
可理解，本申请实施例中的第一网络设备、第二网络设备为搭载了可用于执行计算机执行指令的处理器的设备，可以是接入网设备，比如基站、传输点TRP等，也可以是服务器，具体可以是上述图1中的接入网设备(包括但不限于如基站1和基站2中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。
S503：第一网络设备向第二网络设备发送第一请求消息，相应的，第二网络设备接收第一网络设备发送的第一请求消息。
第一网络设备向第二网络设备发送第一请求消息，其中，第一请求消息用于请求获取终端设备的上下文信息进行SDT。
S504：第二网络设备向第一网络设备发送UE上下文信息，相应的，第一网络设备接收第二网络设备发送的UE上下文信息。
第二网络设备响应于该第一请求消息向第一网络设备发送终端设备的部分上下文信息，相应的，第一网络设备接收第二网络设备响应于该第一请求消息发送的终端设备的部分上下文信息。
可选的，该部分上下文信息包括第七信息，该第七信息用于指示终端设备接收的第二广播服务。
可选的，第二网络设备确定终端设备不支持在同一个时隙内接收SDT和MBS广播服务的数据，则第二网络设备在终端设备部分上下文信息中包括第七信息；第二网络设备确定终端设备支持在同一个时隙内接收SDT和MBS广播服务的数据，则第二网络设备在终端设备部分上下文信息中不包括第七信息。
通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第二广播服务的场景下，第一网络设备可以通过向第二网络设备发送第一请求消息，并接收第二网络设备提供的终端设备的部分上下文信息中的第七信息，得知终端设备在 进行SDT的过程中还可能感兴趣接收或正在接收第二广播服务，从而第一网络设备可以对SDT和第二广播服务进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第一广播服务的数据，或者通过时隙间频分复用的方式发送SDT数据和第一广播服务的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
S505：第一网络设备向第二网络设备发送第一信息，相应的，第二网络设备接收第一网络设备发送的第一信息。
由上述步骤S502可知，第一网络设备接收终端设备发送的第一信息。
在本实施例步骤中，第一网络设备向第二网络设备发送第一信息。
其中，第二网络设备为连接终端设备和核心网设备的网络设备，可以理解的是，此处终端设备和核心网设备之间的连接可以是非接入层(non access stratum，NAS)的连接，或者理解为第二网络设备是具备终端设备与核心网设备之间的NGAP(NG Application Protocol)关联关系的网络设备。
可以理解的是，第一信息可以为RRC消息，当第一网络设备接收到终端设备发送的第一信息后，由于第一网络设备不具备终端设备的完整的上下文信息，例如第一网络设备只具备所述终端设备的RLC上下文，但不具备所述终端设备的PDCP和RRC相关信息(例如PDCP上下文)，因此无法解读第一信息，第一网络设备将第一信息(具体可以为承载第一信息的RLC数据包，例如RLC SDU或PDCP PDU)转发给第二网络设备。第二网络设备具备终端设备的完整的上下文信息，例如第二网络设备具备所述终端设备的PDCP和RRC相关信息(例如PDCP上下文)，因此第二网络设备可以基于终端设备的完整的上下文信息解读第一网络设备转发的第一信息，得到第六信息，并发送给第一网络设备，该第六信息用于指示第一广播服务。该第六信息是基于第一信息得到的，第六信息和第一信息可以是同一信息，例如第六信息是第二网络设备通过网络设备间的接口(例如Xn接口)发送给第一网络设备的第一信息；第六信息和第一信息也可以是不同信息，例如第六信息包含第一信息的部分或全部内容，由第二网络设备确定/生成的，通过网络设备间的接口(例如Xn接口)发送给第一网络设备。
在一种可能的实施例中，第一信息中包含第一广播服务的TMGI信息，其中，TMGI信息可以包含关联的公共陆地移动网络(public land mobile network，PLMN)信息，例如PLMN-index或者PLMN-Identity(PLMN identity也可以简称为PLMN ID)其中之一。当PLMN信息为PLMN-index时，第二网络设备解读/解码第一信息后，将第一信息中的PLMN-index翻译或者转换成PLMN-identity后通过第六信息发送给第一网络设备，即第二网络设备发送的第六信息是将第一信息中的PLMN-index替换为PLMN-identity生成的。如此，可以避免第一网络设备和第二网络设备的PLMN不同时，或者第一网络设备的小区和第二网络设备的小区在SIB1中指示的PLMN列表(例如plmn-IdentityInfoList)中的PLMN顺序不同时，造成第一网络设备和第二网络设备对PLMN-index理解不对齐问题(即相同plmn-index在第一网络设备和第二网络设备对应不同的PLMN)。
S506：第二网络设备向第一网络设备发送第六信息，相应的，第一网络设备接收第二网络设备发送的第六信息。
由上述步骤S505可知，第二网络设备可以对第一网络设备发送的第一信息解码得到第六信息，该第六信息用于指示第一广播服务。
在本步骤中，第二网络设备向第一网络设备发送第六信息，相应的，第一网络设备接收第二网络设备发送的第六信息。第一网络设备可以通过接收第二网络设备发送的第六信息，得知终端设备在进行SDT的过程中还在接收第一广播服务，从而第一网络设备可以对SDT和第一广播服务进行相应的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和广播服务的数据。
可选的，第二网络设备确定终端设备不支持在同一个时隙内接收SDT和MBS广播服务的数据，则第二网络设备向第一网络设备发送第六信息；第二网络设备确定终端设备支持在同一个时隙内接收SDT和MBS广播服务的数据，则第二网络设备不发送第六信息。
应理解，本申请实施例对上述步骤S503和S504、步骤S505和S506的执行顺序不做具体限制，其执行顺序以方案的实际实现顺序为准。
在一种可能的实施例中，第一网络设备在接收到第六信息的情况下，忽略第七信息。
可以理解为，第一网络设备在接收到第六信息的情况下，无论第一网络设备是否接收到第七信息，第一网络设备都将根据第六信息对SDT和相应的第一广播服务进行调度。当第一网络设备接收到第七信息中 指示的广播服务与第六信息中指示的广播服务不同时，以第六信息中指示的广播服务为准，示例性的，第七信息中指示终端设备接收广播服务1、广播服务2、广播服务3，第六信息中指示终端设备接收广播服务2和广播服务4，则第一网络设备认为终端设备感兴趣接收或正在接收的广播服务为广播服务2和广播服务4，终端设备未在接收广播服务1和广播服务3。
在一种可能的实施例中，第一网络设备在未接收到第六信息且接收到第七信息的情况下，第一网络设备将根据第七信息对SDT和相应的第二广播服务进行调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二广播服务的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
S507：第二网络设备向第一网络设备发送第八信息和/或第九信息，相应的，第一网络设备接收第二网络设备发送的第八信息和/或第九信息。
其中，第八信息用于指示终端设备支持或不支持一个或多个单播数据和一个或多个广播数据在同一个时隙内的频分复用(frequencydivisionmultiplexing，FDM)接收，换言之，第八信息用于指示终端设备支持或不支持M个单播数据和N个广播数据在同一个时隙内的频分复用FDM接收，M和N为大于或等于1的整数。
第九信息用于指示终端设备支持或不支持一个或多个单播数据和一个或多个广播数据在同一个时隙内的时分复用(timedivisionmultiplexing，TDM)接收，换言之，第九信息用于指示终端设备支持或不支持P个单播数据和Q个广播数据在同一个时隙内的时分复用TDM接收，P和Q为大于或等于1的整数。
可选的，第八信息还用于指示终端设备在第一频段或第一频段的载波上支持或不支持M个单播数据和N个广播数据在同一个时隙内的频分复用FDM接收，M和N为大于或等于1的整数；第八信息包括第一频段的标识；
可选的，第九信息还用于指示终端设备在第二频段或第二频段的载波上支持或不支持P个单播数据和Q个广播数据在同一个时隙内的时分复用TDM接收，P和Q为大于或等于1的整数；第九信息包括第二频段的标识；第一频段和第二频段可以为相同的频段，也可以为不同的频段。
第二网络设备向第一网络设备发送第八信息和/或第九信息，可以使第一网络设备获知终端设备并行接收SDT数据和广播数据的能力，从而以更灵活的方式调度数据。例如，当终端设备支持在同一时隙内以频分复用方式接收1个单播的PDSCH和1个广播的GC-PDSCH时，第一网络设备可以在同一时隙内以频分复用方式发送1个单播的PDSCH和1个广播的GC-PDSCH。又例如，当终端设备支持在同一时隙内以时分复用方式接收1个单播PDSCH和1个广播GC-PDSCH时，第一网络设备可以在同一时隙内以时分复用方式发送1个单播PDSCH和1个广播GC-PDSCH。
应理解，本申请实施例对本步骤S507、上述步骤S503和S504、上述步骤S505和S506的执行顺序不做具体限制，其执行顺序以方案的实际实现顺序为准。
S508：第一网络设备向终端设备提供SDT和第一广播服务，相应的，终端设备接收来自于第一网络设备的SDT和第一广播服务。
第一网络设备通过调度SDT和第一广播服务，例如通过时隙间时分复用的方式发送SDT数据和第一广播服务的数据，或者通过时隙间频分复用的方式发送SDT数据和第一广播服务的数据，等等，使终端设备可以在不同时隙上接收到来自于第一网络设备的SDT和第一广播服务的数据。
通过本申请实施例，可以实现终端设备在无UE上下文重定位的小数据传输场景下，服务小区对应的网络设备可以获知终端设备感兴趣接收或正在接收的组播广播服务信息以进行合理的调度和数据传输，使得终端设备可以接收到SDT和组播广播服务的数据。
请参阅图6，图6为本申请实施例提供的另一种通信方法的流程示意图。可以理解的是，本申请实施例可以视为上述图4、图5中的实施例的合理变形或补充；或者，可以理解的是，本申请实施例中的通信方法也可以视为能单独执行的实施例，本申请对此不作限制。本申请实施例提供的通信方法应用于通信技术领域，该通信方法包括但不限于如下步骤：
S601：终端设备与第一网络设备进行小数据传输SDT，并且终端设备加入了来自于第一网络设备的第一组播会话。
其中，终端设备处于RRC非活动态，处于RRC非活动态的终端设备与第一网络设备进行SDT，并且终端设备加入了来自第一网络设备的第一组播会话。
可以理解的是，终端设备加入了来自第一网络设备的第一组播会话，可以理解为该终端设备加入了第 一组播服务，并且能够接收来自于第一网络设备的第一组播会话。可选的，该终端设备正在接收来自于第一网络设备的第一组播会话。
可理解，本申请实施例中的终端设备为搭载了可用于执行计算机执行指令的处理器的设备，可以是手持终端(比如手机、平板电脑等)，也可以是车载终端(比如无人驾驶中的无线终端等)等，具体也可以是上述图1中的终端设备(包括但不限于如UE1至UE8中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。
可理解，本申请实施例中的第一网络设备、第二网络设备为搭载了可用于执行计算机执行指令的处理器的设备，可以是接入网设备，比如基站、传输点TRP等，也可以是服务器，具体可以是上述图1中的接入网设备(包括但不限于如基站1和基站2中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。
S602：第一网络设备向第二网络设备发送第二请求消息，相应的，第二网络设备接收第一网络设备发送的第二请求消息。
第一网络设备向第二网络设备发送第二请求消息，其中，第二请求消息用于请求获取终端设备的上下文信息进行SDT。
可以理解的是，在S602步骤前，第一网络设备可能正在向终端设备提供第一组播会话，也可能未向终端设备提供第一组播会话，本申请实施例对此不做限制。
S603：第二网络设备向第一网络设备发送UE上下文信息，相应的，第一网络设备接收第二网络设备发送的UE上下文信息。
第二网络设备响应于该第二请求消息向第一网络设备发送终端设备的部分上下文信息(UE上下文信息)，相应的，第一网络设备接收第二网络设备响应于该第二请求消息发送的终端设备的部分上下文信息(UE上下文信息)。
其中，该UE上下文信息包括第十信息，该第十信息用于指示终端设备加入的第一组播会话的信息，第一网络设备可以根据第十信息向终端设备发送第一组播会话的数据。
可选的，第二网络设备在发送第一信息之前，确定该第一组播会话是激活(activated)的。上述第十信息指示的第一组播会话是激活的组播会话。
可选的，第二网络设备在发送第一信息之前，确定第一网络设备是支持提供RRC非活动态组播的网络设备。一种可能的实现方式为，第二网络设备通过网络设备之间的接口(例如Xn接口)获知第一网络设备支持为RRC非活动态的终端设备提供组播服务。
通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供第一组播会话的场景下，第一网络设备可以通过向第二网络设备发送第二请求消息，并接收第二网络设备提供的终端设备的部分上下文信息中的第十信息，得知终端设备在进行SDT的过程中还加入了第一组播会话，从而第一网络设备可以对SDT和第一组播会话的数据进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第一组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第一组播会话的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第一组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
本申请中，组播服务可以指MBS组播服务(multicast service)，SDT包括下行/上行SDT的数据和/或信令。
S604：第二网络设备向第一网络设备发送第十一信息和/或第十二信息，相应的，第一网络设备接收第二网络设备发送的第十一信息和/或第十二信息。
其中，第十一信息用于指示终端设备支持或不支持一个或多个单播数据和一个或多个组播数据在同一个时隙内的频分复用FDM接收，换言之，第十一信息用于指示终端设备支持或不支持M个单播数据和N个组播数据在同一个时隙内的频分复用FDM接收，M和N为大于或等于1的整数。
第十二信息用于指示终端设备支持或不支持一个或多个单播数据和一个或多个组播数据在同一个时隙内的时分复用TDM接收，换言之，第十二信息用于指示终端设备支持或不支持P个单播数据和Q个组播数据在同一个时隙内的时分复用TDM接收，P和Q为大于或等于1的整数。
可选的，第十一信息还用于指示终端设备在第一频段或第一频段的载波上支持或不支持M个单播数据 和N个组播数据在同一个时隙内的频分复用FDM接收，M和N为大于或等于1的整数；第十一信息包括第一频段的标识；
可选的，第十二信息还用于指示终端设备在第二频段或第二频段的载波上支持或不支持P个单播数据和Q个组播数据在同一个时隙内的时分复用TDM接收，P和Q为大于或等于1的整数；第十二信息包括第二频段的标识；第一频段和第二频段可以为相同的频段，也可以为不同的频段。
第二网络设备向第一网络设备发送第十一信息和/或第十二信息，可以使第一网络设备获知终端设备并行接收SDT数据和组播数据的能力，从而以更灵活的方式调度数据。例如，当终端设备支持在同一时隙内以频分复用方式接收1个单播的PDSCH和1个组播的GC-PDSCH时，第一网络设备可以在同一时隙内以频分复用方式发送1个单播的PDSCH和1个组播的GC-PDSCH。又例如，当终端设备支持在同一时隙内以时分复用方式接收1个单播PDSCH和1个组播GC-PDSCH时，第一网络设备可以在同一时隙内以时分复用方式发送1个单播PDSCH和1个组播GC-PDSCH。
在本申请实施方式中，单播数据可以理解为/替换为用于传输单播(unicast)数据的PDSCH，或者小区的无线网络临时标识(Cell Radio Network Temporary Identifier，cell RNTI)加扰的PDSCH；组播数据可以理解为/替换为用于传输MBS组播数据的PDSCH/GC-PDSCH，或者组无线网络临时标识(Group Radio Network Temporary Identifier,G-RNTI)加扰的PDSCH。单播数据和组播数据在同一时隙内(intra-slot)的时分复用/频分复用可以理解为单播的PDSCH和MBS组播的GC-PDSCH在同一时隙内(intra-slot)的时分复用/频分复用。
通过本申请实施例，第一网络设备在与处于RRC非活动态的终端设备进行SDT，并且第一网络设备为处于RRC非活动态的终端设备提供组播会话的场景下，第一网络设备可以根据第十一信息和/或第十二信息，得知终端设备支持或不支持在同一个时隙内一个或多个单播数据和一个或多个组播数据的频分复用TDM接收或时分复用TDM接收，从而第一网络设备可以对SDT和组播会话的数据进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和组播会话的数据，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
应理解，本申请实施例对本步骤S604、上述步骤S602和S603的执行顺序不做具体限制，其执行顺序以方案的实际实现顺序为准。
S605：第一网络设备向终端设备提供SDT和第一组播会话的数据和/或信令，相应的，终端设备接收来自于第一网络设备的SDT和第一组播会话。
一种可能的实现方式为，第一网络设备通过时隙间时分复用(inter-slot TDM)调度SDT和第一组播会话的数据和/或信令，比如在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第一组播会话的数据和/或信令，使终端设备可以在不同时隙上接收来自于第一网络设备的SDT和第一组播会话的数据和/或信令。
可以理解的是，终端设备在步骤S605之前，可能正在接收来自于第一网络设备的第一组播会话，或者尚未开始接收来自于第一网络设备的第一组播会话，本申请实施例对此不做限制。
本申请实施例中的SDT可以理解为下行SDT数据(DL SDT data)。在不同时隙上发送SDT和第一组播会话的数据可以理解为/替换为在不同时隙上发送SDT的PDSCH和发送第一组播会话的PDSCH/GC-PDSCH，或者理解为以时隙间时分复用(inter-slot TDM)的方式发送SDT的PDSCH和第一组播会话的PDSCH/GC-PDSCH。
通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备加入了来自于第一网络设备的第一组播会话，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第一组播会话的信息，从而可以通过在不同时隙上调度SDT和第一组播会话的数据和/或信令，使终端设备即使不具备在同一个时隙上接收单播数据和组播数据的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第一组播会话的数据和/或信令，避免调度超出终端设备的接收能力而导致的误码和/或丢包。
请参阅图7，图7为本申请实施例提供的另一种通信方法的流程示意图。可以理解的是，本申请实施例可以视为上述图4、图5、图6中的实施例的合理变形或补充；或者，可以理解的是，本申请实施例中的通信方法也可以视为能单独执行的实施例，本申请对此不作限制。本申请实施例提供的通信方法应用于通信技术领域，该通信方法包括但不限于如下步骤：
S701：终端设备与第一网络设备进行小数据传输SDT，并且终端设备加入了来自于第一网络设备的第 二组播会话。
其中，终端设备处于RRC非活动态，处于RRC非活动态的终端设备与第一网络设备进行SDT，并且终端设备加入了来自第一网络设备的第二组播会话。
可理解，本申请实施例中的终端设备为搭载了可用于执行计算机执行指令的处理器的设备，可以是手持终端(比如手机、平板电脑等)，也可以是车载终端(比如无人驾驶中的无线终端等)等，具体也可以是上述图1中的终端设备(包括但不限于如UE1至UE8中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。
可理解，本申请实施例中的第一网络设备、第二网络设备为搭载了可用于执行计算机执行指令的处理器的设备，可以是接入网设备，比如基站、传输点TRP等，也可以是服务器，具体可以是上述图1中的接入网设备(包括但不限于如基站1和基站2中的任一设备)，用于执行本申请实施例中的通信方法，以实现终端设备在无UE上下文重定位的小数据传输场景下，可以接收到SDT和组播广播服务的数据。
S702：终端设备向第一网络设备发送第十三信息，相应的，第一网络设备接收终端设备发送的第十三信息。
其中，该第十三信息包括第二组播会话的信息，该第十三信息具体可以是第二组播会话的TMGI信息。该第十三信息用于第一网络设备在与终端设备进行SDT的同时，还向终端设备提供第二组播会话的数据和/或信令。
通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第二组播会话的场景下，可以通过向第一网络设备上报第十三信息，使第一网络设备知道终端设备在进行SDT的过程中还在接收第二组播会话的数据和/或信令，从而第一网络设备可以对SDT和第二组播会话进行恰当的调度，例如通过时隙间时分复用的方式发送SDT数据和第二组播会话的数据，或者通过时隙间频分复用的方式发送SDT数据和第二组播会话的数据，等等，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二组播会话的数据和/或信令，避免调度超出终端设备的接收能力而导致的误码和/或丢包。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。第一网络设备为终端设备在RRC非活动态驻留的服务小区对应的网络设备，也可以为与终端设备进行SDT的receiving gNB。
本申请中，组播服务可以指MBS组播服务(multicast service)，SDT包括下行/上行SDT的数据和/或信令。
在一种可能的实施例中，第十三信息可以承载于媒体接入控制控制元素(mediaaccesscontrolcontrolelement，MAC CE)，或无线资源控制RRC消息中。
可选的，当第十三信息承载于MAC CE中，第一网络设备可以解读第十三信息，得到终端设备加入的组播会话的信息(组播会话的TMGI)。
可选的，当第十三信息承载于RRC消息中，第一网络设备还需将第十三信息转发至第二网络设备，由第二网络设备解读第十三信息得到终端设备加入的组播会话的信息(组播会话的TMGI)，第二网络设备再将解读得到的终端设备加入的组播会话的信息(组播会话的TMGI)发送给第一网络设备。可以理解的是，该过程和上述图5所示的广播通信的方法类似，具体可以参阅上述步骤S505和S506，此处不再赘述。
通过本申请实施例，终端设备在处于RRC非活动态与第一网络设备进行SDT，并且终端设备接收来自于第一网络设备的第二组播会话的数据的场景下，终端设备向第一网络设备发送MAC CE或RRC消息，该MAC CE或RRC消息包括用于指示第二组播会话的第十三信息，使第一网络设备知道终端设备在进行SDT的过程中还加入了第二组播会话，从而第一网络设备可以对SDT和第二组播会话的数据进行恰当的调度，使终端设备在无UE上下文重定位的小数据传输场景下，也可以接收到SDT和第二组播会话的数据，避免调度超出终端设备的接收能力而导致的数据误码和/或丢包。
S703：第一网络设备向终端设备提供SDT和第二组播会话的数据和/或信令，相应的，终端设备接收第一网络设备发送的SDT和第二组播会话。
第一网络设备在接收到第十三信息后，得知终端设备在与第一网络设备进行SDT的过程中，还加入了第二组播会话，第一网络设备通过时隙间时分复用(inter-slot TDM)调度SDT和第二组播会话的数据和/或信令，比如在时隙1上向终端设备发送SDT的数据，在时隙2上向终端设备发送第二组播会话的数据和/或信令，使终端设备可以在不同时隙上接收到来自于第一网络设备的SDT和第二组播会话的数据和/或信令。
本申请实施例中的SDT可以理解为下行SDT数据(DL SDT data)。在不同时隙上发送SDT和第二组播会话的数据可以理解为/替换为在不同时隙上发送SDT的PDSCH和发送第二组播会话的PDSCH/GC-PDSCH，或者理解为以时隙间时分复用(inter-slot TDM)的方式发送SDT的PDSCH和第二组播会话的PDSCH/GC-PDSCH。
通过本申请实施例，在无UE上下文重定位的SDT(SDT without UE context relocation)场景下，如果终端设备接收来自于第一网络设备的第二组播会话的数据和/或信令，第一网络设备(即服务小区对应的网络设备，也可以称为SDT的receiving gNB)可以获知终端设备接收的第二组播会话的信息，从而在不同时隙上调度SDT和第二组播会话的数据，使终端设备即使不具备在同一个时隙上接收单播数据和组播数据和/或信令的能力，也可以在不同时隙上接收到来自于第一网络设备发送的SDT和第二组播会话的数据和/或信令，避免调度超出终端设备的接收能力而导致的数据误码和/或丢包。
终端设备向第一网络设备发送第十三信息，可以表示终端设备支持接收MBS组播服务，则终端设备必选支持用于传输单播数据的PDSCH和用于传输MBS组播数据的PDSCH/GC-PDSCH的时隙间时分复用(inter-slot TDM)接收，因此第一网络设备按照时隙间时分复用发送SDT和第二组播会话的数据，可以保证终端设备能够在SDT的过程中接收到第二组播会话的数据，避免造成误码和/或丢包，从而保证SDT和MBS组播服务的业务质量。当终端设备不支持在同一时隙内接收单播数据和MBS组播数据时，在无上下文重定位的SDT场景下，第一网络设备没有UE能力信息，如果第一网络设备不知道终端设备正在接收第二组播会话，当第一网络设备在同一时隙内调度/发送SDT数据(SDT可以理解为一种单播传输方式)和第二组播会话的数据时，则会导致终端设备无法接收到SDT和组播数据，或者终端设备只能接收到SDT或组播数据二者其中之一，造成数据误码和/或丢包，影响业务接收质量。因此，通过本申请方案，可以避免上述服务小区对应的网络设备调度的SDT和广播组播服务的数据传输可能超出终端设备的接收能力，从而造成丢包或误码的问题。
上述详细阐述了本申请实施例的方法，下面提供用于实现本申请实施例中任一种方法的装置，例如，提供一种装置包括用以实现以上任一种方法中设备所执行的各步骤的单元(或手段)。
请参阅图8，图8为本申请实施例提供的一种通信装置的结构示意图。
如图8所示，该通信装置80可以包括收发单元801以及处理单元802。收发单元801以及处理单元802可以是软件，也可以是硬件，或者是软件和硬件结合。
其中，收发单元801可以实现发送功能和/或接收功能，收发单元801也可以描述为通信单元。收发单元801还可以是集成了获取单元和发送单元的单元，其中，获取单元用于实现接收功能，发送单元用于实现发送功能。可选的，收发单元801可以用于接收其他装置发送的信息，还可以用于向其他装置发送信息。
在一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的终端设备，如该通信装置80可以是终端设备，也可以是终端设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由终端设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由终端设备所执行的操作。其中，各个单元的描述如下：
收发单元801，用于与第一网络设备进行小数据传输SDT，并且感兴趣接收或正在接收来自于所述第一网络设备的第一广播服务，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述通信装置驻留的小区对应的网络设备；
所述收发单元801，还用于向所述第一网络设备发送第一信息，所述第一信息包括所述第一广播服务的信息，所述第一信息用于所述第一网络设备向所述通信装置提供所述第一广播服务。
在一种可能的实施方式中，所述收发单元801，还用于在不同时隙上接收来自于所述第一网络设备的所述SDT和所述第一广播服务。
在一种可能的实施方式中，所述收发单元801，还用于接收所述第一网络设备发送的第二信息和/或第二网络设备发送的第三信息，所述第二网络设备为向所述通信装置发送RRC释放消息的网络设备；
处理单元802，用于根据所述第二信息和/或所述第三信息，通过所述收发单元801向所述第一网络设备发送所述第一信息。
在一种可能的实施方式中，所述收发单元801，还用于接收所述第一网络设备发送的第四信息和/或所述第二网络设备发送的第五信息；
所述处理单元802，还用于根据所述第四信息和/或所述第五信息，通过所述收发单元801向所述第一 网络设备发送所述第一信息，所述第一信息包括所述第一广播服务的TMGI信息。
在一种可能的实施方式中，所述第三信息和/或所述第五信息承载于RRC释放消息中；
所述处理单元802，还用于根据所述RRC释放消息进入RRC非活动态。
在一种可能的实施方式中，所述第二信息，和/或所述第三信息，和/或所述第四信息，和/或所述第五信息包括系统信息。
在一种可能的实施方式中，所述第二信息和/或所述第三信息包括第一系统信息，所述第一系统信息用于指示组播广播服务和频率的映射关系，或者用于指示组播广播服务控制信道MCCH的配置参数。
在一种可能的实施方式中，所述第四信息和/或所述第五信息包括第二系统信息，所述第二系统信息用于指示组播广播服务和频率的映射关系，或者用于指示组播广播服务控制信道MCCH的配置参数。
在另一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的第一网络设备，如该通信装置80可以是第一网络设备，也可以是第一网络设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由第一网络设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由第一网络设备所执行的操作。其中，各个单元的描述如下：
收发单元801，用于接收终端设备发送的第一信息，所述第一信息包括所述终端设备感兴趣接收或正在接收的第一广播服务的信息，所述通信装置为所述终端设备驻留的小区对应的网络设备；
所述收发单元801，还用于与所述终端设备进行小数据传输SDT，并且向所述终端设备提供所述第一广播服务，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在一种可能的实施方式中，所述收发单元801，还用于在不同时隙上向所述终端设备发送所述SDT和所述第一广播服务。
在一种可能的实施方式中，所述收发单元801，还用于向第二网络设备发送所述第一信息，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
所述收发单元801，还用于接收来自于所述第二网络设备的第六信息，所述第六信息用于指示所述第一广播服务，所述第六信息由所述第一信息确定。
在一种可能的实施方式中，所述收发单元801，还用于向所述第二网络设备发送第一请求消息，所述第一请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述收发单元801，还用于接收所述第二网络设备发送的所述终端设备的部分上下文信息，所述部分上下文信息中包括第七信息，所述第七信息用于指示所述终端设备接收的第二广播服务。
在一种可能的实施方式中，处理单元802，用于在接收到所述第六信息的情况下，忽略所述第七信息。
在一种可能的实施方式中，所述收发单元801，还用于接收来自于所述第二网络设备的第八信息，所述第八信息用于指示所述终端设备支持或不支持M个单播数据和N个广播数据在同一个时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；和/或，
所述收发单元801，还用于接收来自于所述第二网络设备的第九信息，所述第九信息用于指示所述终端设备支持或不支持P个单播数据和Q个广播数据在同一个时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数。
在另一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的第二网络设备，如该通信装置80可以是第二网络设备，也可以是第二网络设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由第二网络设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由第二网络设备所执行的操作。其中，各个单元的描述如下：
收发单元801，用于向第一网络设备发送小数据传输SDT和第六信息，所述第六信息用于指示第一广播服务，所述第一广播服务为终端设备感兴趣接收或正在接收的广播服务，所述通信装置为连接所述终端设备与核心网设备的网络设备，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述SDT通过所述第一网络设备发送至所述终端设备。
在一种可能的实施方式中，所述收发单元801，还用于接收所述第一网络设备发送的第一信息，所述第一信息包括所述第一广播服务的信息；
处理单元802，用于根据所述第一信息，确定所述第六信息。
在一种可能的实施方式中，所述收发单元801，还用于接收所述第一网络设备发送的第一请求消息， 所述第一请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述收发单元801，还用于响应于所述第一请求消息，向所述第一网络设备发送所述终端设备的部分上下文信息，所述部分上下文信息中包括第七信息，所述第七信息用于指示所述终端设备接收的第二广播服务。
在一种可能的实施方式中，所述处理单元802，还用于根据所述终端设备的能力信息，确定所述终端设备不支持在同一个时隙内接收单播数据和广播数据。
在另一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的终端设备，如该通信装置80可以是终端设备，也可以是终端设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由终端设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由终端设备所执行的操作。其中，各个单元的描述如下：
收发单元801，用于接收第一网络设备发送的小数据传输SDT和第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输，所述第一网络设备为所述通信装置驻留的小区对应的网络设备，所述第一组播会话为所述通信装置加入的组播会话，用于指示所述第一组播会话的第十信息由第二网络设备发送至所述第一网络设备，所述第二网络设备为连接所述通信装置与核心网设备的网络设备。
在一种可能的实施方式中，所述第十信息承载于所述第二网络设备向所述第一网络设备发送的所述通信装置的部分上下文信息中。
在另一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的第一网络设备，如该通信装置80可以是第一网络设备，也可以是第一网络设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由第一网络设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由第一网络设备所执行的操作。其中，各个单元的描述如下：
收发单元801，用于接收来自于第二网络设备的第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述通信装置为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
所述收发单元801，还用于向所述终端设备发送小数据传输SDT和所述第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在一种可能的实施方式中，所述收发单元801，还用于向所述第二网络设备发送第二请求消息，所述第二请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述收发单元801，还用于接收所述第二网络设备发送的所述终端设备的部分上下文信息，所述部分上下文信息中包括所述第十信息。
在一种可能的实施方式中，所述收发单元801，还用于在不同时隙上向所述终端设备发送所述SDT和所述第一组播会话的数据。
在一种可能的实施方式中，所述收发单元801，还用于接收来自于所述第二网络设备的第十一信息，所述第十一信息用于指示所述终端设备支持或不支持M个单播数据和N个组播数据在时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；和/或，
所述收发单元801，还用于接收来自于所述第二网络设备的第十二信息，所述第十二信息用于指示所述终端设备支持或不支持P个单播数据和Q个组播数据在时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数。
在另一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的第二网络设备，如该通信装置80可以是第二网络设备，也可以是第二网络设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由第二网络设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由第二网络设备所执行的操作。其中，各个单元的描述如下：
收发单元801，用于向第一网络设备发送小数据传输SDT和第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述通信装置为连接所述终端设备与核心网设备的网络设备；
所述SDT和所述第一组播会话的数据由所述第一网络设备发送至所述终端设备，所述SDT为所述终 端设备在无线资源控制RRC非活动态的数据和/或信令的传输。
在一种可能的实施方式中，所述收发单元801，还用于接收所述第一网络设备发送的第二请求消息，所述第二请求消息用于请求获取所述终端设备的上下文信息进行SDT；
所述收发单元801，还用于向所述第一网络设备发送所述终端设备的部分上下文信息，所述部分上下文信息中包括所述第十信息。
在一种可能的实施方式中，所述SDT和所述第一组播会话的数据由所述第一网络设备在不同时隙上发送至所述终端设备。
在一种可能的实施方式中，处理单元802，用于根据所述终端设备的能力信息，确定所述终端设备不支持在同一个时隙内接收单播数据和组播数据。
在另一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的终端设备，如该通信装置80可以是终端设备，也可以是终端设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由终端设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由终端设备所执行的操作。其中，各个单元的描述如下：
收发单元801，用于与第一网络设备进行小数据传输SDT，并且加入了来自于所述第一网络设备的第二组播会话，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述通信装置驻留的小区对应的网络设备；
所述收发单元801，还用于向所述第一网络设备发送第十三信息，所述第十三信息用于指示所述第二组播会话，所述第十三信息用于所述第一网络设备向所述通信装置发送所述第二组播会话。
在一种可能的实施方式中，所述第十三信息承载于媒体接入控制控制元素MAC CE，或无线资源控制RRC消息中。
在一种可能的实施方式中，所述收发单元801，还用于在不同时隙上接收来自于所述第一网络设备的所述SDT和所述第二组播会话的数据。
在另一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的第一网络设备，如该通信装置80可以是第一网络设备，也可以是第一网络设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由第一网络设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由第一网络设备所执行的操作。其中，各个单元的描述如下：
收发单元801，用于接收终端设备发送的第十三信息，所述第十三信息用于指示第二组播会话，所述第二组播会话为所述终端设备加入的组播会话，所述通信装置为所述终端设备驻留的小区对应的网络设备；
所述收发单元801，还用于与所述终端设备进行小数据传输SDT，并且向所述终端设备发送所述第二组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在一种可能的实施方式中，所述收发单元801，还用于在不同时隙上向所述终端设备发送所述SDT和所述第二组播会话的数据。
在一种可能的实施方式中，所述第十三信息承载于媒体接入控制控制元素MAC CE，或无线资源控制RRC消息中。
在另一种可能的设计中，该通信装置80可对应于上述图4、图5、图6、图7所示的方法实施例中的第二网络设备，如该通信装置80可以是第二网络设备，也可以是第二网络设备中的芯片。该通信装置80可以包括用于执行上述图4、图5、图6、图7所示的方法实施例中由第二网络设备所执行的操作的单元，并且，该通信装置80中的各单元分别为了实现上述图4、图5、图6、图7所示的方法实施例中由第二网络设备所执行的操作。其中，各个单元的描述如下：
收发单元801，还用于向第一网络设备发送小数据传输SDT；其中，所述SDT和第二组播会话的数据由所述第一网络设备发送至终端设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述通信装置为连接所述终端设备与核心网设备的网络设备，所述第二组播会话为第十三信息指示所述终端设备加入的组播会话，所述第十三信息来自于所述终端设备。
根据本申请实施例，图8所示的装置中的各个单元可以分别或全部合并为一个或若干个另外的单元来构成，或者其中的某个(些)单元还可以再拆分为功能上更小的多个单元来构成，这可以实现同样的操作，而不影响本申请的实施例的技术效果的实现。上述单元是基于逻辑功能划分的，在实际应用中，一个单元 的功能也可以由多个单元来实现，或者多个单元的功能由一个单元实现。在本申请的其它实施例中，基于电子设备也可以包括其它单元，在实际应用中，这些功能也可以由其它单元协助实现，并且可以由多个单元协作实现。
需要说明的是，各个单元的实现还可以对应参照上述图4、图5、图6、图7所示的方法实施例的相应描述。
在图8所描述的通信装置80中，可以实现终端设备在无UE上下文重定位的小数据传输场景下，服务小区对应的网络设备可以获知终端设备感兴趣接收或正在接收的组播广播服务信息以进行合理的调度和数据传输，使得终端设备可以接收到SDT和组播广播服务的数据。
请参阅图9，图9为本申请实施例提供的一种通信装置的结构示意图。
应理解，图9示出的通信装置90仅是示例，本申请实施例的通信装置还可包括其他部件，或者包括与图9中的各个部件的功能相似的部件，或者并非要包括图9中所有部件。
通信装置90包括通信接口901和至少一个处理器902。
该通信装置90可以对应终端设备、第一网络设备、第二网络设备中的任一网元或设备。通信接口901用于收发信号，至少一个处理器902执行程序指令，使得通信装置90实现上述方法实施例中由对应设备所执行的方法的相应流程。
在一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的终端设备，如该通信装置90可以是终端设备，也可以是终端设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由终端设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由终端设备所执行的操作。具体可以如下所示：
终端设备与第一网络设备进行小数据传输SDT，并且所述终端设备感兴趣接收或正在接收来自于所述第一网络设备的第一广播服务，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
所述终端设备向所述第一网络设备发送第一信息，所述第一信息包括所述第一广播服务的信息，所述第一信息用于所述第一网络设备向所述终端设备提供所述第一广播服务。
在另一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的第一网络设备，如该通信装置90可以是第一网络设备，也可以是第一网络设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由第一网络设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由第一网络设备所执行的操作。具体可以如下所示：
第一网络设备接收终端设备发送的第一信息，所述第一信息包括所述终端设备感兴趣接收或正在接收的第一广播服务的信息，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
所述第一网络设备与所述终端设备进行小数据传输SDT，并且所述第一网络设备向所述终端设备提供所述第一广播服务，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在另一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的第二网络设备，如该通信装置90可以是第二网络设备，也可以是第二网络设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由第二网络设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由第二网络设备所执行的操作。具体可以如下所示：
第二网络设备向第一网络设备发送小数据传输SDT和第六信息，所述第六信息用于指示第一广播服务，所述第一广播服务为终端设备感兴趣接收或正在接收的广播服务，所述第二网络设备为连接所述终端设备与核心网设备的网络设备，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述SDT通过所述第一网络设备发送至所述终端设备。
在另一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的终端设备，如该通信装置90可以是终端设备，也可以是终端设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由终端设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由终端设备所执行的操作。具体可以如下所示：
终端设备接收第一网络设备发送的小数据传输SDT和第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述第一组播会话为所述终端设备加入的组播会话，用于指示所述第一组播会话的第十信息由第二 网络设备发送至所述第一网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备。
在另一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的第一网络设备，如该通信装置90可以是第一网络设备，也可以是第一网络设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由第一网络设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由第一网络设备所执行的操作。具体可以如下所示：
第一网络设备接收来自于第二网络设备的第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
所述第一网络设备向所述终端设备发送小数据传输SDT和所述第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在另一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的第二网络设备，如该通信装置90可以是第二网络设备，也可以是第二网络设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由第二网络设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由第二网络设备所执行的操作。具体可以如下所示：
第二网络设备向第一网络设备发送小数据传输SDT和第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
所述SDT和所述第一组播会话的数据由所述第一网络设备发送至所述终端设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输。
在另一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的终端设备，如该通信装置90可以是终端设备，也可以是终端设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由终端设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由终端设备所执行的操作。具体可以如下所示：
终端设备与第一网络设备进行小数据传输SDT，并且所述终端设备加入了来自于所述第一网络设备的第二组播会话，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
所述终端设备向所述第一网络设备发送第十三信息，所述第十三信息用于指示所述第二组播会话，所述第十三信息用于所述第一网络设备向所述终端设备发送所述第二组播会话。
在另一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的第一网络设备，如该通信装置90可以是第一网络设备，也可以是第一网络设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由第一网络设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由第一网络设备所执行的操作。具体可以如下所示：
第一网络设备接收终端设备发送的第十三信息，所述第十三信息用于指示第二组播会话，所述第二组播会话为所述终端设备加入的组播会话，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
所述第一网络设备与所述终端设备进行小数据传输SDT，并且所述第一网络设备向所述终端设备发送所述第二组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
在另一种可能的设计中，该通信装置90可对应于上述图4、图5、图6、图7所示的方法实施例中的第二网络设备，如该通信装置90可以是第二网络设备，也可以是第二网络设备中的芯片。该通信装置90可以包括用于执行上述方法实施例中由第二网络设备所执行的操作的部件，并且，该通信装置90中的各部件分别为了实现上述方法实施例中由第二网络设备所执行的操作。具体可以如下所示：
第二网络设备向第一网络设备发送小数据传输SDT；其中，所述SDT和第二组播会话的数据由所述第一网络设备发送至终端设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备，所述第二组播会话为第十三信息指示所述终端设备加入的组播会话，所述第十三信息来自于所述终端设备。
在图9所描述的通信装置90中，可以实现终端设备在无UE上下文重定位的小数据传输场景下，服务小区对应的网络设备可以获知终端设备感兴趣接收或正在接收的组播广播服务信息以进行合理的调度和数据传输，使得终端设备可以接收到SDT和组播广播服务的数据。
对于通信装置可以是芯片或芯片系统的情况，可参阅图10所示的芯片的结构示意图。
如图10所示，芯片100包括处理器1001和接口1002。其中，处理器1001的数量可以是一个或多个，接口1002的数量可以是多个。需要说明的是，处理器1001、接口1002各自对应的功能既可以通过硬件设计实现，也可以通过软件设计来实现，还可以通过软硬件结合的方式来实现，这里不作限制。
可选的，芯片100还可以包括存储器1003，存储器1003用于存储必要的程序指令和数据。
本申请中，处理器1001可用于从存储器1003中调用本申请的一个或多个实施例提供的通信方法在终端设备、第一网络设备、第二网络设备中一个或多个设备或网元的实现程序，并执行该程序包含的指令。接口1002可用于输出处理器1001的执行结果。本申请中，接口1002可具体用于输出处理器1001的各个消息或信息。
关于本申请的一个或多个实施例提供的通信方法可参考前述图4、图5、图6、图7所示各个实施例，这里不再赘述。
本申请实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
本申请实施例中的存储器用于提供存储空间，存储空间中可以存储操作系统和计算机程序等数据。存储器包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)、或便携式只读存储器(compact disc read-only memory，CD-ROM)。
根据本申请实施例提供的方法，本申请实施例还提供一种计算机可读存储介质，上述计算机可读存储介质中存储有计算机程序，当上述计算机程序在一个或多个处理器上运行时，可以实现上述图4、图5、图6、图7所示的方法。
根据本申请实施例提供的方法，本申请实施例还提供一种计算机程序产品，上述计算机程序产品包括计算机程序，当上述计算机程序在处理器上运行时，可以实现上述图4、图5、图6、图7所示的方法。
本申请实施例还提供了一种系统，该系统包括至少一个如上述通信装置80或通信装置90或芯片100，用于执行上述图4、图5、图6、图7任一实施例中相应设备执行的步骤。
本申请实施例还提供了一种系统，该系统包括终端设备、第一网络设备、第二网络设备，该终端设备用于执行上述图4、图5、图6、图7任一实施例中终端设备执行的步骤，该第一网络设备用于执行上述图4、图5、图6、图7任一实施例中第一网络设备执行的步骤，该第二网络设备用于执行上述图4、图5、图6、图7任一实施例中第二网络设备执行的步骤。
本申请实施例还提供了一种处理装置，包括处理器和接口；所述处理器用于执行上述任一方法实施例中的方法。
应理解，上述处理装置可以是一个芯片。例如，该处理装置可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静 态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disc，SSD))等。
上述各个装置实施例中的单元和方法实施例中的电子设备完全对应，由相应的模块或单元执行相应的步骤，例如通信单元(收发器)执行方法实施例中接收或发送的步骤，除发送、接收外的其它步骤可以由处理单元(处理器)执行。具体单元的功能可以参考相应的方法实施例。其中，处理器可以为一个或多个。
可以理解的，本申请实施例中，电子设备可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。

Claims (31)

  1. 一种通信方法，其特征在于，包括：
    终端设备与第一网络设备进行小数据传输SDT，并且所述终端设备感兴趣接收或正在接收来自于所述第一网络设备的第一广播服务，所述SDT为在无线资源控制RRC非活动态的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
    所述终端设备向所述第一网络设备发送第一信息，所述第一信息包括所述第一广播服务的信息，所述第一信息用于所述第一网络设备向所述终端设备提供所述第一广播服务。
  2. 根据权利要求1所述的方法，其特征在于，所述终端设备向所述第一网络设备发送第一信息之前，所述方法还包括：
    所述终端设备接收所述第一网络设备发送的第二信息和/或第二网络设备发送的第三信息，所述第二网络设备为向所述终端设备发送RRC释放消息的网络设备；
    所述终端设备向所述第一网络设备发送第一信息，包括：
    所述终端设备根据所述第二信息和/或所述第三信息，向所述第一网络设备发送所述第一信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一广播服务的信息包括临时移动组标识TMGI信息；所述终端设备向所述第一网络设备发送第一信息之前，所述方法还包括：
    所述终端设备接收所述第一网络设备发送的第四信息和/或所述第二网络设备发送的第五信息；
    所述终端设备向所述第一网络设备发送第一信息，包括：
    所述终端设备根据所述第四信息和/或所述第五信息，向所述第一网络设备发送所述第一信息，所述第一信息包括所述第一广播服务的TMGI信息。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第三信息和/或所述第五信息承载于RRC释放消息中；所述方法还包括：
    所述终端设备根据所述RRC释放消息进入RRC非活动态。
  5. 根据权利要求2或3所述的方法，其特征在于，所述第二信息，和/或所述第三信息，和/或所述第四信息，和/或所述第五信息包括系统信息。
  6. 根据权利要求5所述的方法，其特征在于，所述第二信息和/或所述第三信息包括第一系统信息，所述第一系统信息用于指示组播广播服务和频率的映射关系，或者用于指示组播广播服务控制信道MCCH的配置参数。
  7. 根据权利要求5所述的方法，其特征在于，所述第四信息和/或所述第五信息包括第二系统信息，所述第二系统信息用于指示组播广播服务和频率的映射关系，或者用于指示组播广播服务控制信道MCCH的配置参数。
  8. 一种通信方法，其特征在于，包括：
    第一网络设备接收终端设备发送的第一信息，所述第一信息包括所述终端设备感兴趣接收或正在接收的第一广播服务的信息，所述第一网络设备为所述终端设备驻留的小区对应的网络设备；
    所述第一网络设备与所述终端设备进行小数据传输SDT，并且所述第一网络设备向所述终端设备提供所述第一广播服务，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向第二网络设备发送所述第一信息，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
    所述第一网络设备接收来自于所述第二网络设备的第六信息，所述第六信息用于指示所述第一广播服务，所述第六信息由所述第一信息确定。
  10. 根据权利要求8或9所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备向所述第二网络设备发送第一请求消息，所述第一请求消息用于请求获取所述终端设备的上下文信息进行SDT；
    所述第一网络设备接收所述第二网络设备发送的所述终端设备的部分上下文信息，所述部分上下文信息中包括第七信息，所述第七信息用于指示所述终端设备接收的第二广播服务。
  11. 根据权利要求10所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备在接收到所述第六信息的情况下，忽略所述第七信息。
  12. 根据权利要求8至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自于所述第二网络设备的第八信息，所述第八信息用于指示所述终端设备支持或不支持M个单播数据和N个广播数据在同一个时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；和/或，
    所述第一网络设备接收来自于所述第二网络设备的第九信息，所述第九信息用于指示所述终端设备支持或不支持P个单播数据和Q个广播数据在同一个时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数。
  13. 一种通信方法，其特征在于，包括：
    第二网络设备向第一网络设备发送小数据传输SDT和第六信息，所述第六信息用于指示第一广播服务，所述第一广播服务为终端设备感兴趣接收或正在接收的广播服务，所述第二网络设备为连接所述终端设备与核心网设备的网络设备，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输，所述SDT通过所述第一网络设备发送至所述终端设备。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收所述第一网络设备发送的第一信息，所述第一信息包括所述第一广播服务的信息；
    所述第二网络设备根据所述第一信息，确定所述第六信息。
  15. 根据权利要求13或14所述的方法，其特征在于，所述方法还包括：
    所述第二网络设备接收所述第一网络设备发送的第一请求消息，所述第一请求消息用于请求获取所述终端设备的上下文信息进行SDT；
    响应于所述第一请求消息，所述第二网络设备向所述第一网络设备发送所述终端设备的部分上下文信息，所述部分上下文信息中包括第七信息，所述第七信息用于指示所述终端设备接收的第二广播服务。
  16. 根据权利要求13至15中任一项所述的方法，其特征在于，所述第二网络设备向第一网络设备发送第六信息之前，所述方法还包括：
    所述第二网络设备根据所述终端设备的能力信息，确定所述终端设备不支持在同一个时隙内接收单播数据和广播数据。
  17. 一种通信方法，其特征在于，包括：
    终端设备接收第一网络设备发送的小数据传输SDT和第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输，所述第一网络设备为所述终端设备驻留的小区对应的网络设备，所述第一组播会话为所述终端设备加入的组播会话，用于指示所述第一组播会话的第十信息由第二网络设备发送至所述第一网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备。
  18. 根据权利要求17所述的方法，其特征在于，所述第十信息承载于所述第二网络设备向所述第一网络设备发送的所述终端设备的部分上下文信息中。
  19. 一种通信方法，其特征在于，包括：
    第一网络设备接收来自于第二网络设备的第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
    所述第一网络设备向所述终端设备发送小数据传输SDT和所述第一组播会话的数据，所述SDT为在无线资源控制RRC非活动态下的数据和/或信令的传输。
  20. 根据权利要求19所述的方法，其特征在于，所述第一网络设备接收来自于第二网络设备的第十信息，包括：
    所述第一网络设备向所述第二网络设备发送第二请求消息，所述第二请求消息用于请求获取所述终端设备的上下文信息进行SDT；
    所述第一网络设备接收所述第二网络设备发送的所述终端设备的部分上下文信息，所述部分上下文信息中包括所述第十信息。
  21. 根据权利要求19或20所述的方法，其特征在于，所述方法还包括：
    所述第一网络设备接收来自于所述第二网络设备的第十一信息，所述第十一信息用于指示所述终端设备支持或不支持M个单播数据和N个组播数据在时隙内的频分复用FDM接收，所述M和所述N为大于或等于1的整数；和/或，
    所述第一网络设备接收来自于所述第二网络设备的第十二信息，所述第十二信息用于指示所述终端设备支持或不支持P个单播数据和Q个组播数据在时隙内的时分复用TDM接收，所述P和所述Q为大于或等于1的整数。
  22. 一种通信方法，其特征在于，包括：
    第二网络设备向第一网络设备发送小数据传输SDT和第十信息，所述第十信息用于指示终端设备加入的第一组播会话，所述第一网络设备为所述终端驻留的小区对应的网络设备，所述第二网络设备为连接所述终端设备与核心网设备的网络设备；
    所述SDT和所述第一组播会话的数据由所述第一网络设备发送至所述终端设备，所述SDT为所述终端设备在无线资源控制RRC非活动态的数据和/或信令的传输。
  23. 根据权利要求22所述的方法，其特征在于，所述第二网络设备向第一网络设备发送第十信息，包括：
    所述第二网络设备接收所述第一网络设备发送的第二请求消息，所述第二请求消息用于请求获取所述终端设备的上下文信息进行SDT；
    所述第二网络设备向所述第一网络设备发送所述终端设备的部分上下文信息，所述部分上下文信息中包括所述第十信息。
  24. 根据权利要求22或23所述的方法，其特征在于，所述第二网络设备向第一网络设备发送第十信息之前，所述方法还包括：
    所述第二网络设备根据所述终端设备的能力信息，确定所述终端设备不支持在同一个时隙内接收单播数据和组播数据。
  25. 一种通信装置，其特征在于，包括用于执行如权利要求1至7或权利要求8至12或权利要求13至16或权利要求17至18或权利要求19至21或权利要求22至24中任一项所述方法的模块或单元。
  26. 一种通信装置，其特征在于，包括：处理器；
    当所述处理器调用存储器中的计算机程序或指令时，使如权利要求1至7中任一项所述的方法被执行，或权利要求8至12中任一项所述的方法被执行，或权利要求13至16中任一项所述的方法被执行，或权利要求17至18中任一项所述的方法被执行，或权利要求19至21中任一项所述的方法被执行，或权利要求22至24中任一项所述的方法被执行。
  27. 一种通信装置，其特征在于，包括逻辑电路和接口，所述逻辑电路和所述接口耦合；
    所述接口用于输入待处理的数据，所述逻辑电路按照如权利要求1至7或权利要求8至12或权利要求13至16或权利要求17至18或权利要求19至21或权利要求22至24中任一项所述的方法对所述待处理的数据进行处理，获得处理后的数据，所述接口用于输出所述处理后的数据。
  28. 一种计算机可读存储介质，其特征在于，包括：
    所述计算机可读存储介质用于存储指令或计算机程序；当所述指令或所述计算机程序被执行时，使如权利要求1至7中任一项所述的方法被实现，或权利要求8至12中任一项所述的方法被实现，或权利要求13至16中任一项所述的方法被实现，或权利要求17至18中任一项所述的方法被实现，或权利要求19至21中任一项所述的方法被实现，或权利要求22至24中任一项所述的方法被实现。
  29. 一种计算机程序产品，其特征在于，包括：指令或计算机程序；
    所述指令或所述计算机程序被执行时，使如权利要求1至7中任一项所述的方法被执行，或权利要求8至12中任一项所述的方法被执行，或权利要求13至16中任一项所述的方法被执行，或权利要求17至18中任一项所述的方法被执行，或权利要求19至21中任一项所述的方法被执行，或权利要求22至24中任一项所述的方法被执行。
  30. 一种通信系统，其特征在于，包括如权利要求25所述的通信装置，或权利要求26所述的通信装置，或权利要求27所述的通信装置。
  31. 一种通信系统，其特征在于，包括：终端设备、第一网络设备、第二网络设备；
    所述终端设备用于执行如权利要求1至7中任一项所述的方法，所述第一网络设备用于执行如权利要求8至12中任一项所述的方法，所述第二网络设备用于执行如权利要求13至16中任一项所述的方法；或者，
    所述终端设备用于执行如权利要求17至18中任一项所述的方法，所述第一网络设备用于执行如权利要求19至21中任一项所述的方法，所述第二网络设备用于执行如权利要求22至24中任一项所述的方法。
PCT/CN2023/115371 2022-09-09 2023-08-29 一种通信方法及相关装置 WO2024051517A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211103843.5 2022-09-09
CN202211103843.5A CN117714993A (zh) 2022-09-09 2022-09-09 一种通信方法及相关装置

Publications (1)

Publication Number Publication Date
WO2024051517A1 true WO2024051517A1 (zh) 2024-03-14

Family

ID=90144880

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/115371 WO2024051517A1 (zh) 2022-09-09 2023-08-29 一种通信方法及相关装置

Country Status (2)

Country Link
CN (1) CN117714993A (zh)
WO (1) WO2024051517A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112534901A (zh) * 2018-08-13 2021-03-19 高通股份有限公司 Rrc不活动模式下的下行链路数据传输
WO2022109877A1 (en) * 2020-11-25 2022-06-02 Lenovo (Beijing) Limited Method and apparatus for small data transmission
CN114698152A (zh) * 2020-12-29 2022-07-01 鸿颖创新有限公司 小数据传输方法及相关设备
WO2022151292A1 (en) * 2021-01-14 2022-07-21 Nokia Shanghai Bell Co., Ltd. Transmission in small data transmission mode

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112534901A (zh) * 2018-08-13 2021-03-19 高通股份有限公司 Rrc不活动模式下的下行链路数据传输
WO2022109877A1 (en) * 2020-11-25 2022-06-02 Lenovo (Beijing) Limited Method and apparatus for small data transmission
CN114698152A (zh) * 2020-12-29 2022-07-01 鸿颖创新有限公司 小数据传输方法及相关设备
WO2022151292A1 (en) * 2021-01-14 2022-07-21 Nokia Shanghai Bell Co., Ltd. Transmission in small data transmission mode

Also Published As

Publication number Publication date
CN117714993A (zh) 2024-03-15

Similar Documents

Publication Publication Date Title
WO2021077434A1 (zh) 一种通信方法及装置
WO2017118199A1 (zh) 一种数据调度方法、基站及系统
WO2021259129A1 (zh) 一种通信方法及通信装置
WO2021142647A1 (zh) 一种业务传输方法及装置、终端设备、网络设备
WO2021062797A1 (zh) 配置方法和装置
CN114424663A (zh) 一种业务调度方法及装置、终端设备、网络设备
EP4030846A1 (en) Method and device for multicasting network slice
CN115707036A (zh) 传输数据的方法和装置
CN113661722B (zh) 一种业务数据传输方法及装置、网络设备、终端设备
WO2021051312A1 (zh) 一种信息配置方法及装置、终端设备、网络设备
TW202224455A (zh) 用於mbs的無線通信的裝置和方法
WO2022073246A1 (zh) 一种通信方法及装置
WO2022057173A1 (zh) 一种通信方法及装置
WO2021051321A1 (zh) 一种业务数据传输方法及装置、终端设备
WO2024051517A1 (zh) 一种通信方法及相关装置
WO2022127777A1 (zh) 一种通信方法及通信装置
WO2021078170A1 (zh) 一种通信方法及装置
CN115529662A (zh) 一种通信方法及装置
CN116391408A (zh) 动态切换多播和广播服务（mbs）数据包传送模式的方法和装置
WO2024066858A1 (zh) 一种通信的方法和装置
WO2021189458A1 (zh) 一种数据转发方法及装置、通信设备
WO2022237552A1 (zh) 一种无线通信方法、装置及系统
WO2024067270A1 (zh) 一种切换方法及通信装置
WO2023226659A1 (zh) 一种信息传输方法、装置和通信系统
WO2022267883A1 (zh) 一种通信方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23862213

Country of ref document: EP

Kind code of ref document: A1