WO2023066081A1 - 非激活态多播业务发送、接收方法及装置 - Google Patents

非激活态多播业务发送、接收方法及装置 Download PDF

Info

Publication number
WO2023066081A1
WO2023066081A1 PCT/CN2022/124552 CN2022124552W WO2023066081A1 WO 2023066081 A1 WO2023066081 A1 WO 2023066081A1 CN 2022124552 W CN2022124552 W CN 2022124552W WO 2023066081 A1 WO2023066081 A1 WO 2023066081A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
indication information
receiving
sending
inactive
Prior art date
Application number
PCT/CN2022/124552
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 WO2023066081A1 publication Critical patent/WO2023066081A1/zh

Links

Images

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the invention relates to the field of communication technology, in particular to a method and device for sending and receiving non-active multicast services.
  • the Multimedia Broadcast Multicast Service (MBMS) function will be introduced in the New Radio (NR) system.
  • the terminal equipment User Equipment, UE
  • the terminal equipment For terminal devices in the connected state, it is necessary to perform the measurement task configured by the network, and report the measurement report when the measurement reporting conditions are met; the network will also configure the terminal device to perform physical layer (that is, layer 1, Layer1, referred to as L1) measurement and reporting channel Status information, etc. Therefore, a terminal device in a connected state needs to maintain a large signaling overhead, which is not only detrimental to the power consumption of the terminal device, but also significantly increases the load on the network.
  • the first problem to be solved is how the terminal device can determine whether it can receive the multicast service in the inactive state.
  • the technical problem solved by the invention is how to realize the judgment of the inactive state transmission multicast service.
  • a method for sending an inactive multicast service includes: sending first indication information and/or second indication information, and the first The indication information indicates that the multicast service is received in the inactive state, and the second indication information indicates the conditions to be met for receiving the multicast service in the inactive state; and the data of the multicast service is sent.
  • the first indication information has a corresponding relationship with the identifier of at least one multicast service
  • the second indication information has a corresponding relationship with the identifier of at least one multicast service
  • the sending the first indication information includes: sending the first indication information in RRC release signaling.
  • the sending the second indication information includes: carrying the second indication information in RRC signaling and sending it.
  • the sending of the first indication information and/or the second indication information includes: for a terminal device that receives the multicast service and is in a connected state, if there is no multicast service within a preset time period and unicast service, then send the first indication information or the second indication information.
  • the sending the first indication information includes: carrying the first indication information in paging and sending it.
  • the sending the first indication information includes: for a terminal device in an inactive state, if there is data of the multicast service to be transmitted, sending the first indication information in paging,
  • the paging also includes the identifier of the multicast service.
  • the second indication information includes one or more of the following conditions: being in a serving cell that can receive the multicast service; being in a serving cell when receiving the first indication information or the second indication information; receiving The signal quality threshold of the multicast service; in the serving cell, and the uplink advance timer has not expired, and one or more configured configuration authorizations are valid; in the serving cell, and the uplink advance timer has not expired, the The serving cell configures uplink resources for transmitting HARQ feedback.
  • a method for receiving a multicast service in an inactive state includes: receiving first indication information and/or second indication information, the first indication information indicating The multicast service is received in the inactive state, and the second indication information indicates the conditions to be met for receiving the multicast service in the inactive state; the data of the multicast service is received in the inactive state.
  • the conditions to be met for receiving the multicast service in the inactive state are preset by the protocol.
  • the receiving the first indication information includes: receiving RRC release signaling in an active state, where the RRC release signaling includes the first indication information.
  • the receiving the second indication information includes: receiving RRC signaling in an active state, where the RRC signaling includes the second indication information.
  • the method includes: entering an inactive state; saving the reception configuration of the multicast service obtained in the active state.
  • the receiving the first indication information includes: receiving paging in an inactive state, where the paging includes the first indication information.
  • the receiving data of the multicast service in the inactive state includes: if the first indication information is received, after receiving paging or update information indicating the data transmission of the multicast service, receiving The data of the multicast service; if the second indication information is received, it is judged whether the condition indicated by the second indication information is satisfied, and when the condition is met and the data indicating the multicast service is received After the paging or update information is transmitted, receive the data of the multicast service; if only the first indication information is received, and the conditions to be met for receiving the multicast service in the inactive state are preset by the protocol, judge Whether the condition is met, after the condition is met and the paging or update information indicating the data transmission of the multicast service is received, the data of the multicast service is received.
  • an inactive state multicast service sending device configured to send first indication information and/or second indication information, the first indication information The one instruction information indicates receiving multicast service in an inactive state, and the second instruction information indicates conditions to be met for receiving multicast service in an inactive state; the data sending module is used to send data of multicast service.
  • an inactive state multicast service receiving device configured to receive first indication information and/or second indication information, the first indication information The one indication information indicates receiving the multicast service in the inactive state, and the second indication information indicates the conditions to be met for receiving the multicast service in the inactive state; the data receiving module is configured to receive the data of the multicast service in the inactive state.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is run by a processor, the steps of the method for sending a multicast service in an inactive state are executed, or the inactive state The steps of the method for receiving multicast services, or the steps of the method for transmitting multicast services in an inactive state.
  • a network device including a memory and a processor, the memory stores a computer program that can run on the processor, and the processor executes the inactivation when running the computer program. The steps of the method for sending multicast services in the active state, or the steps of the method for transmitting multicast services in the inactive state.
  • a terminal device including a memory and a processor, the memory stores a computer program that can run on the processor, and the processor executes the inactive Steps in the method for receiving a multicast service in an active state, or steps in a method for transmitting a multicast service in an inactive state.
  • a method for transmitting a multicast service in an inactive state includes: receiving a preamble sent by a terminal device in an inactive state; Information about the first beam; and sending multicast service data on the first beam.
  • the method before sending the data of the multicast service on the first beam, the method further includes: determining the multicast service that the terminal device is interested in.
  • the determining the multicast service that the terminal device is interested in includes: determining the multicast service that the terminal device is interested in according to the preamble.
  • each multicast service is configured with a dedicated preamble.
  • the determining the multicast service that the terminal device is interested in includes: receiving message 3, where the message 3 includes an identifier of the multicast service that the terminal device is interested in.
  • the terminal device before receiving the preamble sent by the terminal device using the current first beam, it further includes: indicating to the terminal device information about the beam used by the multicast service to be transmitted, for the terminal The device sends the preamble when it finds that the beam it is in is different from the beam used to transmit the multicast service.
  • a method for transmitting multicast services in an inactive state includes: when in an inactive state, sending a preamble according to the first beam currently in which the preamble is located.
  • the receiving occasion can be used to determine the information of the first beam; receive the data of the multicast service on the first beam.
  • the method further includes: sending the service identifier of the multicast service.
  • the sending the service identifier includes: sending a message 3, where the message 3 includes the service identifier.
  • each multicast service is configured with a dedicated preamble.
  • the sending the preamble according to the current first beam includes: sending a message 1 according to the first beam, where the message 1 includes the preamble.
  • an inactive state multicast service transmission device configured to include: a preamble receiving module, configured to receive a preamble sent by a terminal device in an inactive state; beam information determination A module, configured to determine the information of the first beam according to the receiving timing of the preamble; a sending module, configured to send multicast service data on the first beam.
  • an inactive state multicast service transmission device includes: a preamble sending module, configured to send a preamble according to the current first beam when it is in an inactive state
  • the preamble, the receiving timing of the preamble can be used to determine the information of the first beam
  • the receiving module is configured to receive the data of the multicast service on the first beam.
  • the network device can send the first indication information to the terminal equipment, and the terminal equipment can receive multicast service data in an inactive state according to the indication of the first indication information; or, the network equipment can send the second indication information to The terminal device, the terminal device judges whether it can receive multicast service data in an inactive state according to the condition indicated by the second indication information.
  • the terminal equipment can clearly receive the data of the multicast service in the inactive state, and realize the transmission of the multicast service in the inactive state, thereby reducing the signaling overhead of the terminal equipment and reduce network load.
  • the network device can notify the terminal device in the connected state to release the RRC connection through the RRC release signaling, and at the same time notify the terminal device to continue to receive multicast service data after entering the inactive state, which is realized by multiplexing signaling
  • the flexibility of indication does not require additional signaling to indicate, which can further reduce signaling overhead.
  • the first indication information is carried in paging and sent, and the paging also includes the multicast The ID of the broadcast service.
  • the network device when the network device indicates that the multicast service data will be transmitted through paging, it can also indicate to the terminal device that it can receive the multicast service data in an inactive state, so as to realize the flexibility of the indication.
  • Fig. 1 is a flow chart of a method for sending an inactive multicast service in an embodiment of the present invention
  • Fig. 2 is an interactive flowchart of an inactive state multicast service transmission in an embodiment of the present invention
  • FIG. 3 is an interactive flowchart of another inactive state multicast service transmission in an embodiment of the present invention.
  • FIG. 4 is a flow chart of a method for transmitting an inactive multicast service in an embodiment of the present invention
  • FIG. 5 is an interaction flowchart of another method for transmitting an inactive multicast service in an embodiment of the present invention.
  • FIG. 6 is an interactive flowchart of another method for transmitting an inactive multicast service in an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of an inactive-state multicast service sending device in an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of an inactive multicast service receiving device in an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a hardware structure of a communication device in an embodiment of the present invention.
  • the communication systems to which the embodiments of the present application are applicable include, but are not limited to, long term evolution (long term evolution, LTE) systems, fifth generation (5th-generation, 5G) systems, NR systems, and future evolution systems or multiple communication fusion systems.
  • the 5G system may be a non-standalone (NSA) 5G system or a standalone (standalone, SA) 5G system.
  • NSA non-standalone
  • SA standalone 5G system.
  • the technical solution of the present application is also applicable to different network architectures, including but not limited to relay network architecture, dual-link architecture, Vehicle-to-Everything (vehicle-to-everything communication) architecture and other architectures.
  • This application mainly relates to communication between terminal equipment and network equipment. in:
  • the network device in the embodiment of the present application may also be called an access network device, for example, it may be a base station (base station, BS) (also called a base station device), and the network device is a type of network device deployed on a wireless access network (Radio Access Network, RAN) is a device used to provide wireless communication functions.
  • base station base station
  • RAN Radio Access Network
  • equipment that provides base station functions in the second-generation (2nd-generation, 2G) network includes base transceiver stations (base transceiver stations, BTS), and equipment that provides base station functions in the third-generation (3rd-generation, 3G) network includes Node B (NodeB), the equipment that provides base station functions in the fourth-generation (4th-generation, 4G) network includes evolved Node B (evolved NodeB, eNB), in wireless local area networks (wireless local area networks, WLAN),
  • the device that provides base station functions is the access point (access point, AP), the device that provides base station functions in NR, the next generation base station node (next generation node base station, gNB), and the node B (ng-eNB) that continues to evolve,
  • gNB and terminal devices use NR technology for communication
  • ng-eNB and terminal devices use Evolved Universal Terrestrial Radio Access (E-UTRA) technology for communication.
  • E-UTRA Evolved Universal Terrestrial Radio Access
  • the terminal equipment (terminal equipment) in the embodiment of the present application may refer to various forms of access terminals, subscriber units, subscriber stations, mobile stations, mobile stations (mobile station, MS), remote stations, remote terminals, mobile equipment, user Terminal, wireless communication device, user agent or user device.
  • the terminal equipment can also be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital processing (Personal Digital Assistant, PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in the future 5G network or future evolution of the public land mobile network (Public Land Mobile Network, PLMN)
  • PLMN Public Land Mobile Network
  • a terminal device may also be called a user equipment (User Equipment, UE), a terminal, and the like.
  • the network device will notify the terminal device that the multicast service is about to start transmission. After the terminal device in the idle state or inactive state receives the paging notification, if the If you are interested in multicast services, you need to switch to the connected state to receive multicast services. If the terminal device can receive the multicast service in the inactive state, the terminal device in the inactive state first needs to determine whether it can receive the multicast service in the current state.
  • the technical solution of the present invention provides a method.
  • the terminal equipment can clearly receive the data of the multicast service in the inactive state, and realize the transmission of the multicast service in the inactive state, thereby reducing the Signaling overhead for end devices and reduced network load.
  • Another problem to be solved when transmitting multicast services in an inactive state is that once a terminal device in an inactive state is allowed to receive multicast services, the network device may not know which beams (Beams) need to send multicast services.
  • Beams beams
  • the network device can learn which beams need to transmit multicast services through the information reported by the terminal device at layer 1 or layer 3.
  • FIG. 1 is a method for sending an inactive multicast service according to an embodiment of the present invention.
  • the method for sending an inactive multicast service can be used on the network device side, that is, the network device can execute each step of the sending method.
  • the method for sending an inactive multicast service may include the following steps:
  • Step 101 Sending first indication information and/or second indication information, the first indication information indicates receiving the multicast service in the inactive state, and the second indication information indicates the requirements to be met for receiving the multicast service in the inactive state condition;
  • Step 102 Send the data of the multicast service.
  • the first indication information can directly indicate whether the terminal device can receive the multicast service in the inactive state; the second indication information indirectly indicates whether the terminal device can receive the multicast service in the inactive state through conditions.
  • the network device may send the first indication information to the terminal device, and the terminal device can receive multicast service data in an inactive state according to the indication of the first indication information.
  • the network device may also send the second indication information to the terminal device, and the terminal device judges whether it can receive multicast service data in an inactive state according to the condition indicated by the second indication information.
  • the terminal device receives the first indication information and/or the second indication information; if the terminal device determines that it can receive the data of the multicast service in the inactive state, the terminal device receives the data of the multicast service in the inactive state.
  • the second indication information may include some or all parameters related to the conditions for the terminal device to receive the multicast service in the inactive state.
  • the method for sending and receiving the inactive multicast service can be implemented in the form of a software program, and the software program runs in a processor integrated in a chip or a chip module.
  • the method may also be implemented by combining software with hardware, which is not limited in this application.
  • the network device carries the first indication information in RRC release signaling and sends it to the terminal device.
  • FIG. 2 shows an interaction diagram between a terminal device and a network device.
  • the network device sends RRC release signaling to the terminal device.
  • the RRC release signaling includes the first indication information and/or the second indication information.
  • the terminal device releases the connection and enters the inactive state, and determines that it can receive the multicast service in the inactive state through the first indication information and/or the second indication information in the RRC release signaling.
  • the terminal device is in the connected state and is receiving the multicast service, and the network device finds that there is no data transmission of the multicast service, and there is no other multicast service or unicast service within the preset time period, then The network device may send the above RRC release signaling.
  • step 202 the network device sends a page to the terminal device.
  • the network device when the data of the multicast service needs to be transmitted, the network device notifies the terminal device of the data transmission of the multicast service through paging.
  • step 203 the network device sends data of the multicast service to the terminal device.
  • the terminal device receives the data of the multicast service in an inactive state by using previously saved configuration parameters of the multicast service, such as search space configuration and other parameters.
  • the second indication information when the network device sends the second indication information, the second indication information may be carried in RRC signaling and sent out.
  • the RRC signaling may be the RRC release signaling, or any other practicable RRC signaling, which is not limited in this embodiment of the present invention.
  • the network device carries the first indication information in paging and sends it to the terminal device.
  • FIG. 3 shows an interaction diagram between a terminal device and a network device.
  • step 301 the network device sends RRC release signaling to the terminal device.
  • the terminal device is in a connected state and is receiving multicast services.
  • the RRC release signaling is sent, To turn the terminal equipment in the connected state into the inactive state to reduce the network load.
  • step 302 the network device sends a page to the terminal device.
  • the paging includes the first indication information.
  • the network device when the data of the multicast service needs to be transmitted, the network device notifies the terminal device of the data transmission of the multicast service through paging, and at the same time indicates in the paging that the terminal device can receive the data of the multicast service in an inactive state.
  • step 303 the network device sends data of the multicast service to the terminal device.
  • the terminal device receives the data of the multicast service in an inactive state by using previously saved configuration parameters of the multicast service, such as search space configuration and other parameters.
  • the first indication information corresponds to an identifier of at least one multicast service
  • the second indication information corresponds to an identifier of at least one multicast service
  • each type of multicast service can be independently indicated whether it can be received in an inactive state.
  • an association may be established between the first indication information and the multicast service identifier, and the first indication information may correspond to one multicast service identifier, or may correspond to multiple multicast service identifiers.
  • the second indication information may correspond to a multicast service identifier, or may correspond to multiple multicast service identifiers.
  • the paging includes identifiers of multiple multicast services.
  • the first indication information may include multiple bit values, and each bit value corresponds to an identifier of a multicast service.
  • the identifier of the multicast service may be in the form of a list, and the first indication information may also be in the form of a list. The contents of the corresponding positions in the two lists have a corresponding relationship, so that the terminal device can know which multicast service is based on the corresponding relationship. Services can be received in the inactive state.
  • the second indication information includes one or more of the following: in a serving cell that can receive the multicast service; when receiving the first indication information or the second indication information in the serving cell; under one or more beams of the serving cell, and the signal quality of at least one beam reaches the preset threshold; in the serving cell, and the uplink advance timer has not timed out, configured one or more configurations
  • the authorization is valid (Configured Grant, CG); in the serving cell, and the uplink advance timer has not timed out, the serving cell is configured to transmit Hybrid Automatic Repeat reQuest (Hybrid Automatic Repeat reQuest, HARQ) feedback uplink resources.
  • the second indication information may directly indicate the specific condition content, and may also include some or all parameters related to the condition, for example, if the serving cell is under one or more beams, and the signal quality of at least one beam reaches Preset threshold, the second indication information may indicate one or more beam identifiers, and indicate a preset threshold value (that is, the signal quality threshold for receiving multicast services); if the uplink advance timer does not expire, the configured one or more The first configuration authorization is valid, and the second indication information can indicate the duration of the uplink advance timer and one or more configured configuration authorizations; if the uplink advance timer has not expired, configure the uplink resources used to transmit the HARQ feedback, the first The second indication information may indicate the duration of the uplink advance timer and the configured uplink resource. After obtaining some or all parameters related to the condition, the terminal device can determine the specific content of the condition, and then can judge whether the condition is satisfied.
  • the condition that the signal quality of at least one beam reaches a preset threshold can ensure that the terminal device can reliably receive data of the multicast service in an inactive state.
  • the condition that the uplink advance timer does not expire can ensure that the terminal device is in the precondition of being able to perform uplink feedback, and the condition that one or more configuration grants configured are valid can ensure that the terminal device has uplink resources available for uplink feedback.
  • the condition that the serving cell configures uplink resources for transmitting HARQ feedback can ensure that the terminal device has available uplink resources for uplink feedback, and the uplink resources may be physical uplink control channel (Physical Uplink Control Channel, PUCCH) resources.
  • PUCCH Physical Uplink Control Channel
  • the terminal device after the terminal device enters the inactive state, it judges whether the multicast service can be received in the inactive state according to the criterion configured by the network device (that is, the second indication information).
  • the serving cell restarts to transmit multicast service data
  • the terminal device judges that the multicast service can be received in the inactive state, it will remain in the inactive state, and use the saved search space corresponding to the downlink control signaling for detecting the multicast service and other parameters to receive multicast service data.
  • the terminal device judges that the criteria are not met, for example, the terminal device finds that the signal quality of multiple beams configured in the serving cell is lower than the preset threshold, or the CG configured in the serving cell is no longer valid, etc., the terminal device does not receive multiple beams in the inactive state. broadcast data. If the terminal device is still interested in the multicast service at this time, the terminal device needs to initiate the radio resource control (Radio Resource Control, RRC) connection establishment or recovery process, after entering the connection state, wait for the reconfiguration of the serving cell, and then receive the multicast broadcast business data.
  • RRC Radio Resource Control
  • an NR cell supports multicast services (Multicast), and the NR cell can transmit to terminal devices in different states in the cell, such as terminal devices in RRC connection state and inactive state (can be extended to idle state) Multicast service.
  • the NR cell needs to transmit three kinds of multicast services, which are called session 1, session 2 and session 3 respectively.
  • session 1, session 2 and session 3 the NR cell believes that Session 1 can be received by connected terminal devices and inactive terminal devices, while the other two sessions (session 2 and session 3) need to be received by connected terminal devices.
  • the network device is configured to receive the multicast service (that is, the first indication information) in an inactive state through RRC release signaling (RRC Release), and configures according to the session. For example, for the terminal equipment UE1 in the connected state that is receiving Session 1, if the serving cell finds that there is no data transmission of the Session 1 for a period of time, and the UE1 has no other multicast and unicast services, the network equipment can pass The RRC release signaling releases the RRC connection of the UE1, notifies the UE1 to enter the inactive state, and at the same time indicates in the signaling that Session 1 can receive in the inactive state.
  • RRC release signaling releases the RRC connection of the UE11, notifies the UE1 to enter the inactive state, and at the same time indicates in the signaling that Session 1 can receive in the inactive state.
  • UE1 After UE1 enters the inactive state, it saves the relevant configuration of receiving Session 1 obtained in the active state, such as parameters such as the search space corresponding to the downlink control signaling for detecting multicast services. After a period of time, the network device obtains the new Session 1 data from the core network. The network device instructs the terminal device interested in Session 1 to receive the multicast data through the paging indication or the update information of the multicast service (it may be a group activation notification indication or an MCCH change notification). After UE1 receives the instruction, it receives Session 1 in the inactive state by using the saved parameters for detecting the search space of the multicast service.
  • the relevant configuration of receiving Session 1 obtained in the active state such as parameters such as the search space corresponding to the downlink control signaling for detecting multicast services.
  • the network device After a period of time, the network device obtains the new Session 1 data from the core network. The network device instructs the terminal device interested in Session
  • the network device uses RRC signaling to configure a criterion (that is, second indication information) for receiving multicast services in an inactive state, and the terminal device judges whether to receive multicast services in an inactive state according to the criterion.
  • a criterion that is, second indication information
  • the serving cell can release the session through RRC. Signaling, releasing the RRC connection of the UE, notifying UE2 to enter the inactive state, and indicating in the signaling the criterion that Session 1 can be received in the inactive state. Possible criteria are one or more of the following:
  • UE2 continues to be in the serving cell (i.e. the serving cell where the criterion is sent), or
  • UE2 is under one or more beams configured in the serving cell, and UE2 measures that any (at least one) of the multiple beams needs to exceed the preset threshold (that is, the signal quality threshold). If the serving cell is configured according to SSB Beams, SSB1 and SSB2 are configured, and a preset threshold is configured, as long as UE2 measures that at least one of SSB1 or SSB2 exceeds the preset threshold, it is considered to meet the criteria, or
  • UE2 is in the serving cell, the uplink advance timer (Timing Advance Timer) has not timed out, and one or more configuration authorizations configured are valid, UE2 can upload necessary information through configuration authorization, such as for receiving multicast data HARQ ACK/NACK, channel state information of the beam measured by UE2, etc., or
  • UE2 is under the serving cell, the uplink advance timer has not expired, and the serving cell has configured PUCCH resources for transmitting HARQ feedback for UE2.
  • UE2 After UE2 enters the inactive state, it judges whether it can receive Session 1 in the inactive state according to the criteria configured by the network device.
  • the serving cell restarts to transmit the data of Session 1
  • UE2 judges that Session 1 can be received in the inactive state, it will remain in the inactive state and use the saved parameters such as the search space corresponding to the downlink control signaling for detecting multicast services to receive Session 1 scheduling information and data.
  • UE2 judges that the criteria are not met for example, UE2 finds that the signal quality of multiple beams configured by the serving cell is lower than the preset threshold, or the configuration authorization configured by the serving cell is no longer valid, etc., then UE2 will not receive Session 1 in the inactive state The data. If UE2 is still interested in Session1 at this time, UE2 needs to initiate the RRC connection establishment or recovery process, after entering the connection state, wait for the reconfiguration of the serving cell, and then receive the data of Session 1.
  • the terminal equipment that was originally in the connected state to receive the multicast data may be transferred to the inactive state.
  • the serving cell After a period of time, if there is multicast data transmission, the serving cell notifies the terminal device that Session 1 has data transmission through paging, and at the same time, the serving cell indicates during paging that it can receive data from Session 1 in an inactive state.
  • the serving cell notifies the terminal device to receive the multicast service in the inactive state through the first indication information, and the conditions (ie criteria) that the terminal device needs to meet to receive the multicast service in the inactive state are preset by the protocol , if the terminal device in the inactive state continues to be interested in the multicast service, it needs to judge whether the condition is met, after the condition is met and the paging or update information indicating the data transmission of the multicast service is received , receiving data of the multicast service.
  • the conditions to be met for receiving multicast services in the inactive state include one or more of the following:
  • the UE continues to be in the serving cell (that is, the serving cell that sends the first indication information), or
  • the UE is under one or more beams configured in the serving cell, and the UE measures that any (at least one) of the multiple beams exceeds the preset threshold. If the serving cell configures beams according to SSB, SSB1 and SSB2 are configured, And a preset threshold is configured, as long as UE2 measures that either SSB1 or SSB2 exceeds the preset threshold, it is considered to meet the criteria, or 3.
  • the uplink advance timer (Timing Advance Timer) has not timed out, and all One or more configuration authorizations configured are valid, and UE2 can upload necessary information through configuration authorization, such as HARQ ACK/NACK for receiving multicast data, channel state information of beams measured by UE, etc., or
  • the UE is under the serving cell, and the uplink advance timer has not expired, and the serving cell configures PUCCH resources for transmitting HARQ feedback for the UE.
  • the embodiment of the invention also discloses a non-activated state multicast service transmission method.
  • the terminal equipment in this embodiment is in an inactive state.
  • the inactive state multicast service transmission method may include the following steps:
  • the terminal device first learns the service identifier of the multicast service that can be received in the inactive state and the preamble information corresponding to each multicast service through the system message or MCCH of the serving cell, and expects to receive the multicast service in the inactive state.
  • the network device can know the position of the beam it is in, and the network device can send multicast data in the corresponding beam, avoiding sending multicast data on all beams , which can effectively save wireless transmission resources.
  • Step 401 The terminal device sends a preamble (Preamble) at a random access opportunity (RACH Occasion) corresponding to the first beam.
  • Preamble a preamble
  • RACH Occasion a random access opportunity
  • the terminal device is on the first beam, that is, the terminal device uses the first beam to send and receive data. Accordingly, the network device receives the preamble.
  • Step 402 The network device determines the information of the first beam according to the receiving timing of the preamble. Specifically, the network device may determine the identifier of the first beam.
  • Step 403 The network device sends data of the multicast service on the first beam. That is, after the network device knows through the preamble that the terminal device is sending and receiving data on the first beam, it can send the data of the multicast service to the terminal device through the first beam, so as to realize reliable transmission of the multicast service. Correspondingly, the terminal device receives the data of the multicast service.
  • the embodiment of the present invention enables the network device to know which beams need to send multicast services, that is, the network device can know the distribution of terminal devices in the inactive state in the cell, and the beams where the terminal device receives multicast services data, so that the data of the multicast service can be correctly transmitted to the terminal equipment in the inactive state.
  • the preamble may be sent and received via message 1 (Msg1).
  • the interaction process between the terminal device and the network device is as follows.
  • the terminal device sends a Msg1 to the network device, and the Msg1 includes a preamble.
  • the preamble may be a common preamble, that is, the form and content of the preamble specified in the communication standard protocol.
  • step 502 the network device determines the information of the first beam according to the receiving timing of the preamble.
  • Msg2 may be a response message of Msg1, and specifically may be a random access response.
  • step 504 the terminal device sends Msg3 to the network device, and Msg3 includes the service identifier of the multicast service it is interested in.
  • Msg4 may be a response message of Msg3, specifically an acknowledgment message (ACK) or a conflict resolution message.
  • ACK acknowledgment message
  • the network device can know the identifier of the first beam used by the terminal device to receive multicast data, and the service identifier of the multicast service that the terminal device is interested in. Then, the network device may send data of the multicast service pointed to by the service identifier to the terminal device on the first beam.
  • the interaction process between the terminal device and the network device is as follows.
  • Step 601 the terminal device sends a Msg1 to the network device, and the Msg1 includes a preamble dedicated to the multicast service.
  • the network device can assign a specific preamble to a terminal device requesting multicast service transmission in an MBMS point-to-multipoint control channel (MBMS Control Channel, MCCH), such as assigning a dedicated preamble for the request of Session 1.
  • MBMS Control Channel MCCH
  • Step 602 The network device determines the information of the first beam according to the receiving timing of the preamble. Further, the network device may also determine the service identifier of the multicast service corresponding to the preamble.
  • Step 603 the network device sends Msg2 to the terminal device.
  • Msg2 may be a response message of Msg1, and specifically may be a random access response.
  • Step 604 The network device sends data of the multicast service on the first beam.
  • the embodiment of the present invention sets a preamble dedicated to the multicast service, and the terminal device and the network device only need to interact with Msg1 and Msg2 to enable the network device to obtain the required information, thereby improving the interaction between the terminal device and the network device. s efficiency.
  • the terminal device may send the preamble multiple times to feed back the beam information to the network device until the data of the multicast service is received.
  • the wireless signal presents the characteristics of good directionality and large path loss at high frequency.
  • a cell with a large coverage needs multiple beams (Beam) to achieve complete coverage.
  • Beam can only cover a limited range.
  • a cell with a small coverage area may contain only one beam.
  • Beam Sweeping For a cell composed of multiple beams, due to hardware limitations, not all beams can transmit at the same time, and time-sharing transmission is required, which is called beam sweeping (Beam Sweeping).
  • Beam Sweeping beam sweeping
  • its synchronization signal (including primary synchronization signal and secondary synchronization signal) is transmitted according to a certain cycle, such as 5ms/10ms/20ms/40ms/80ms.
  • a cell will transmit one or more Synchronization Signal Blocks (SSB) (that is, different beams), such as 4 SSBs or 8 SSBs. In a cycle, these SSBs are distributed within 5ms.
  • One SSB includes PSS/SSS and PBCH.
  • PSS and SSS are used to enable the terminal equipment to identify the cell identity, and to enable the terminal equipment to obtain symbol-level synchronization.
  • the terminal device needs to synthesize the measured strongest N beams of the cell to obtain the signal quality of the cell.
  • the serving cell usually includes 8 SSBs from SSB0 to SSB7.
  • the serving cell determines that at least the data of Session 1 needs to be transmitted in SSB2, SSB3, and SSB5 according to the current distribution of terminal devices in the connected state that need to receive Session1.
  • the serving cell does not know the distribution of terminal devices in the inactive state that need to receive Session 1 in the cell, that is, it does not know in which beams the terminal devices in the inactive state will receive multicast data.
  • the serving cell indicates in MCCH the beam information that Session 1 will transmit (ie SSB2, SSB3, and SSB5), for other beams that need to be served
  • the terminal equipment in the inactive state needs to send feedback information to the serving cell, indicating which beam it needs to receive Session 1.
  • terminal devices in the inactive state can receive Session 1 at SSB2, SSB3 or SSB5, these terminal devices do not need to indicate any information to the base station.
  • terminal devices that cannot receive Session 1 at SSB2, 3, and 5 they need to indicate to the serving cell which beam (or beams) they need to receive Session 1, and can indicate which beam (or beams) they need to receive Session 1 through the random access process. Which beams) receive Session 1.
  • One of the ways is that the terminal device sends a preamble through Msg1, and indicates the identifier of Session 1 to the serving cell through Msg3.
  • the network device judges at which SSB the terminal device needs to receive Session 1 from the timing when the terminal device sends the preamble.
  • the serving cell can allocate a specific preamble (preamble dedicated to the multicast service) in the MCCH to the terminal device requesting the multicast service, such as allocating a dedicated preamble for the request of Session 1.
  • a specific preamble preamble dedicated to the multicast service
  • the serving cell can determine at which SSB the terminal device needs to receive Session 1 from the timing when the UE sends the preamble.
  • the terminal device If the terminal device fails to receive Session 1 from the corresponding beam after multiple requests, the terminal device initiates an RRC connection/recovery request to the network device, and requests the serving cell to send Session 1 to itself after entering the connected state.
  • the threshold for the number of request failures can be set by the serving cell. When the number of times is lower than or equal to the threshold, the terminal device indicates to the network device the multicast service it is interested in and the beam information it is in in the above manner.
  • the device 70 for sending an inactive multicast service may include:
  • An indication information sending module 701 configured to send first indication information and/or second indication information, the first indication information indicates receiving a multicast service in an inactive state, and the second indication information indicates receiving a multicast service in an inactive state Conditions that broadcasting services need to meet;
  • the data sending module 702 is configured to send the data of the multicast service.
  • the above-mentioned inactive state multicast service sending device may correspond to a chip with an inactive state multicast service sending function in the network equipment, such as a SOC (System-On-a-Chip, system on a chip), a baseband chip, etc. ; or corresponding to a chip module including a non-active multicast service sending function in the network device; or corresponding to a chip module with a data processing function chip, or corresponding to the network device.
  • SOC System-On-a-Chip, system on a chip
  • baseband chip etc.
  • a chip module including a non-active multicast service sending function in the network device or corresponding to a chip module with a data processing function chip, or corresponding to the network device.
  • the inactive multicast service receiving device 80 may include:
  • An indication information receiving module 801 configured to receive first indication information and/or second indication information, the first indication information indicates receiving a multicast service in an inactive state, and the second indication information indicates receiving a multicast service in an inactive state Conditions that broadcasting services need to meet;
  • the data receiving module 802 is configured to receive multicast service data in an inactive state.
  • the above-mentioned device for receiving inactive multicast services may correspond to a chip with an inactive multicast service receiving function in the terminal equipment, such as a SOC (System-On-a-Chip, system on chip), a baseband chip, etc. ; or corresponding to a terminal device including a chip module with an inactive state multicast service receiving function; or corresponding to a chip module with a data processing function chip, or corresponding to a terminal device.
  • SOC System-On-a-Chip, system on chip
  • a baseband chip etc.
  • a terminal device including a chip module with an inactive state multicast service receiving function or corresponding to a chip module with a data processing function chip, or corresponding to a terminal device.
  • each module/unit contained in the product may be a software module/unit, or a hardware module/unit, or may be partly a software module/unit and partly a hardware module/unit.
  • each module/unit contained therein may be realized by hardware such as a circuit, or at least some modules/units may be realized by a software program, and the software program Running on the integrated processor inside the chip, the remaining (if any) modules/units can be realized by means of hardware such as circuits; They are all realized by means of hardware such as circuits, and different modules/units can be located in the same component (such as chips, circuit modules, etc.) or different components of the chip module, or at least some modules/units can be realized by means of software programs, The software program runs on the processor integrated in the chip module, and the remaining (if any) modules/units can be realized by hardware such as circuits; /Units can be realized by means of hardware such as circuits
  • the embodiment of the present invention also discloses a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and the computer program can execute the steps of the methods shown in FIG. 1 to FIG. 6 when running.
  • the storage medium may include ROM, RAM, magnetic or optical disks, and the like.
  • the storage medium may also include a non-volatile memory (non-volatile) or a non-transitory (non-transitory) memory, and the like.
  • the embodiment of the present application also provides a schematic diagram of a hardware structure of a communication device.
  • the device includes a processor 901 , a memory 902 and a transceiver 903 .
  • the processor 901 can be a general-purpose central processing unit (central processing unit, CPU), a microprocessor, a specific application integrated circuit (application-specific integrated circuit, ASIC), or one or more for controlling the execution of the application program program integrated circuit.
  • the processor 601 may also include multiple CPUs, and the processor 901 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, or processing cores for processing data such as computer program instructions.
  • Memory 902 can be ROM or other types of static storage devices that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, and can also be an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), read-only disc (compactdisc read-only memory, CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), disk storage
  • the medium or other magnetic storage devices, or any other medium that can be used to carry or store desired program codes in the form of instructions or data structures and can be accessed by a computer, is not limited in this embodiment of the present application.
  • the memory 902 may exist independently (in this case, the memory 902 may be located outside the device or within the device), or may be integrated with the processor 901 . Wherein, the memory 902 may contain computer program codes.
  • the processor 901 is configured to execute the computer program code stored in the memory 902, so as to implement the method provided in the embodiment of the present application.
  • the processor 901, the memory 902 and the transceiver 903 are connected through a bus.
  • the transceiver 903 is used to communicate with other devices or a communication network.
  • the transceiver 903 may include a transmitter and a receiver.
  • the device in the transceiver 903 for implementing the receiving function may be regarded as a receiver, and the receiver is configured to perform the receiving step in the embodiment of the present application.
  • the device in the transceiver 903 for implementing the sending function may be regarded as a transmitter, and the transmitter is used to perform the sending step in the embodiment of the present application.
  • the processor 901 is used to control and manage the actions of the terminal device.
  • the processor 901 is used to support the terminal device to execute the diagram Step 501 and step 504 in 5, or step 601 in FIG. 6 , and/or actions performed by the terminal device in other processes described in the embodiments of this application.
  • the processor 901 may communicate with other network entities through the transceiver 903, for example, communicate with the aforementioned network devices.
  • the memory 902 is used to store program codes and data of the terminal device. When the processor runs the computer program, it can control the transceiver 903 to receive RRC release signaling, paging, multicast service data, Msg2, Msg4 and so on.
  • the processor 901 is used to control and manage the actions of the network device, for example, the processor 901 is used to support the network device to execute the diagram.
  • the processor 901 may communicate with other network entities through the transceiver 903, for example, communicate with the above-mentioned terminal equipment.
  • the memory 902 is used to store program codes and data of network devices. When the processor runs the computer program, it may control the transceiver 903 to send one or more of RRC signaling, MAC signaling and DCI.
  • the embodiment of this application defines the one-way communication link from the access network to the terminal equipment as the downlink, the data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called the downlink direction;
  • the one-way communication link of the network is the uplink, the data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is called the uplink direction.
  • the embodiment of this application defines the one-way communication link from the access network to the terminal as the downlink, the data transmitted on the downlink is downlink data, and the transmission direction of the downlink data is called the downlink direction;
  • the one-way communication link is an uplink, the data transmitted on the uplink is uplink data, and the transmission direction of the uplink data is called the uplink direction.
  • Multiple appearing in the embodiments of the present application means two or more.
  • connection in the embodiment of the present application refers to various connection methods such as direct connection or indirect connection to realize communication between devices, which is not limited in the embodiment of the present application.
  • the processor may be a central processing unit (CPU for short), and the processor may also be other general-purpose processors, digital signal processors (digital signal processor, DSP for short) , application specific integrated circuit (ASIC for short), off-the-shelf programmable gate array (field programmable gate array, FPGA for short) 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, or the like.
  • the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (read-only memory, referred to as ROM), programmable read-only memory (programmable ROM, referred to as PROM), erasable programmable read-only memory (erasable PROM, referred to as EPROM) , Electrically Erasable Programmable Read-Only Memory (electrically EPROM, referred to as EEPROM) or flash memory.
  • the volatile memory can be random access memory (RAM), which acts as external cache memory.
  • RAM random access memory
  • static random access memory static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous Dynamic random access memory
  • SDRAM synchronous Dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM Synchronously connect dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the above-mentioned embodiments may be implemented in whole or in part by software, hardware, firmware or other arbitrary combinations.
  • the above-described embodiments may be implemented in whole or in part in the form of computer program products.
  • the computer program product comprises one or more computer instructions or computer programs.
  • the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Wired or wireless transmission to another website site, computer, server or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center that includes one or more sets of available media.
  • the available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed methods, devices and systems can be implemented in other ways.
  • the device embodiments described above are only illustrative; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of 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 may be distributed to multiple network units. Part 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 invention may be integrated into one processing unit, each unit may be physically included separately, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software functional units.
  • the above-mentioned integrated units implemented in the form of software functional units may be stored in a computer-readable storage medium.
  • the above-mentioned software functional units are stored in a storage medium, and include several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to execute some steps of the methods described in various embodiments of the present invention.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), magnetic disk or optical disc, etc., which can store program codes. medium.

Landscapes

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

Abstract

一种非激活态多播业务发送、接收方法及装置，非激活态多播业务发送方法包括：发送第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；发送多播业务的数据。本发明技术方案能够实现对非激活态传输多播业务的判定。

Description

非激活态多播业务发送、接收方法及装置
本申请要求2021年10月19日提交中国专利局、申请号为202111217425.4、发明名称为“非激活态多播业务发送、接收方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域，尤其涉及一种非激活态多播业务发送、接收方法及装置。
背景技术
在新无线(New Radio,NR)系统中将引入多媒体广播组播服务(Multimedia Broadcast Multicast Service,MBMS)功能。在当前的协议版本中，对于多播业务(Multicast)，由于其服务质量要求较高，终端设备(User Equipment,UE)需要在连接态接收多播业务。对于连接态的终端设备，需要执行网络配置的测量任务，在满足测量上报条件时上报测量报告；网络也会配置终端设备执行物理层(也即层1，Layer1,简称L1)的测量以及上报信道状态信息等，因此处于连接态的终端设备需要维持较大的信令开销，不仅对终端设备的功耗不利，对于网络的负载也会显著增加。
为了减小终端设备的信令开销以及降低网络的负载，可以考虑在非激活态支持多播业务的传输。
但是，如果需要在非激活态接收多播业务，首先需要解决的问题是，终端设备如何判断自己能否在非激活态接收多播业务。
发明内容
本发明解决的技术问题是如何实现对非激活态传输多播业务的 判定。
为解决上述技术问题，第一方面，提供了一种非激活态多播业务发送方法，非激活态多播业务发送方法包括：发送第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；发送多播业务的数据。
可选的，所述第一指示信息与至少一种多播业务的标识具有对应关系，所述第二指示信息与至少一种多播业务的标识具有对应关系。
可选的，所述发送第一指示信息包括：将所述第一指示信息承载在RRC释放信令中发送出去。
可选的，所述发送第二指示信息包括：将所述第二指示信息承载在RRC信令中发送出去。
可选的，所述发送第一指示信息和/或第二指示信息包括：对于接收所述多播业务且处于连接态的终端设备，如果在时长为预设时长的时间段内没有多播业务和单播业务，则发送所述第一指示信息或所述第二指示信息。
可选的，所述发送第一指示信息包括：将所述第一指示信息承载在寻呼中发送出去。
可选的，所述发送第一指示信息包括：对于处于非激活态的终端设备，如果存在所述多播业务的数据需要传输，则将所述第一指示信息承载在寻呼中发送出去，所述寻呼中还包括所述多播业务的标识。
可选的，所述第二指示信息包括以下一项或多项条件：处于可接收所述多播业务的服务小区；处于接收所述第一指示信息或第二指示信息时的服务小区；接收所述多播业务的信号质量门限；处于所述服务小区，且上行提前定时器没有超时，配置的一个或多个配置授权有效；处于所述服务小区，且上行提前定时器没有超时，所述服务小区配置用于传输HARQ反馈的上行资源。
第二方面，提供了一种非激活态多播业务接收方法，非激活态多播业务接收方法包括：接收第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；在非激活态接收多播业务的数据。
可选的，在接收到第一指示信息的情况下，在非激活态接收多播业务需要满足的条件由协议预先设定。
可选的，所述接收第一指示信息包括：在激活态接收RRC释放信令，所述RRC释放信令包括所述第一指示信息。
可选的，所述接收第二指示信息包括：在激活态接收RRC信令，所述RRC信令包括所述第二指示信息。
可选的，所述接收第一指示信息和/或第二指示信息之后包括：进入非激活态；保存在所述激活态时所获得的所述多播业务的接收配置。
可选的，所述接收第一指示信息包括：在非激活态接收寻呼，所述寻呼包括所述第一指示信息。
可选的，所述在非激活态接收多播业务的数据包括：如果接收到所述第一指示信息，则在接收到指示所述多播业务的数据传输的寻呼或更新信息后，接收所述多播业务的数据；如果接收到所述第二指示信息，则判断所述第二指示信息所指示的条件是否满足，并在满足所述条件且接收到指示所述多播业务的数据传输的寻呼或更新信息后，接收所述多播业务的数据；如果仅收到所述第一指示信息，并且在非激活态接收多播业务需要满足的条件由协议预先设定时，判断所述条件是否满足，在满足所述条件且接收到指示所述多播业务的数据传输的寻呼或更新信息后，接收所述多播业务的数据。
第三方面，提供了一种非激活态多播业务发送装置，非激活态多 播业务发送装置包括：指示信息发送模块，用于发送第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；数据发送模块，用于发送多播业务的数据。
第四方面，提供了一种非激活态多播业务接收装置，非激活态多播业务接收装置包括：指示信息接收模块，用于接收第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；数据接收模块，用于在非激活态接收多播业务的数据。
第五方面，提供了一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器运行时执行所述非激活态多播业务发送方法的步骤，或者所述非激活态多播业务接收方法的步骤，或者所述非激活态多播业务传输方法的步骤。
第六方面，提供了一种网络设备，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行所述非激活态多播业务发送方法的步骤，或者所述非激活态多播业务传输方法的步骤。
第七方面，提供了一种终端设备，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，所述处理器运行所述计算机程序时执行所述非激活态多播业务接收方法的步骤，或者所述非激活态多播业务传输方法的步骤。
第八方面，提供了一种非激活态多播业务传输方法，非激活态多播业务传输方法包括：接收处于非激活态的终端设备发送的前导码；根据所述前导码的接收时机确定所述第一波束的信息；在所述第一波束上发送多播业务的数据。
可选的，所述在所述第一波束上发送多播业务的数据之前还包括：确定所述终端设备感兴趣的多播业务。
可选的，所述确定所述终端设备感兴趣的多播业务包括：根据所述前导码确定所述终端设备感兴趣的多播业务。
可选的，每一多播业务配置有专用的前导码。
可选的，所述确定所述终端设备感兴趣的多播业务包括：接收消息3，所述消息3包括所述终端设备感兴趣的多播业务的标识。
可选的，所述接收所述终端设备利用当前所处的第一波束发送的前导码之前还包括：向所述终端设备指示将要传输的多播业务使用的波束的信息，以供所述终端设备在发现自己所处的波束与传输所述多播业务使用的波束不同时发送所述前导码。
第九方面，提供了一种非激活态多播业务传输方法，非激活态多播业务传输方法包括：处于非激活态时，根据当前所处的第一波束发送前导码，所述前导码的接收时机能够用于确定所述第一波束的信息；在所述第一波束上接收多播业务的数据。
可选的，所述根据当前所处的第一波束发送前导码之后还包括：发送所述多播业务的业务标识。
可选的，所述发送业务标识包括：发送消息3，所述消息3包括所述业务标识。
可选的，每一多播业务配置有专用的前导码。
可选的，所述根据当前所处的第一波束发送前导码包括：根据所述第一波束发送消息1，所述消息1包括所述前导码。
第十方面，提供了一种非激活态多播业务传输装置，非激活态多播业务传输装置包括：前导码接收模块，用于接收处于非激活态的终端设备发送的前导码；波束信息确定模块，用于根据所述前导码的接收时机确定所述第一波束的信息；发送模块，用于在所述第一波束上发送多播业务的数据。
第十一方面，提供了一种非激活态多播业务传输装置，非激活态 多播业务传输装置包括：前导码发送模块，用于处于非激活态时，根据当前所处的第一波束发送前导码，所述前导码的接收时机能够用于确定所述第一波束的信息；接收模块，用于在所述第一波束上接收多播业务的数据。
与现有技术相比，本发明实施例的技术方案具有以下有益效果：
本发明技术方案中，网络设备可以发送第一指示信息至终端设备，终端设备根据第一指示信息的指示，能够在非激活态接收多播业务的数据；或者，网络设备发送第二指示信息至终端设备，终端设备根据第二指示信息指示的条件，判断自身是否能够在非激活态接收多播业务的数据。本发明技术方案通过设置第一指示信息和第二指示信息，能够使得终端设备明确在非激活态接收多播业务的数据，实现非激活态多播业务的传输，从而降低终端设备的信令开销以及降低网络负载。
进一步地，对于接收所述多播业务且处于连接态的终端设备，如果在时长为预设时长的时间段内没有多播业务和单播业务，则发送所述第一指示信息和/或所述第二指示信息。本发明技术方案中，网络设备可以通过RRC释放信令通知处于连接态的终端设备释放RRC连接的同时，通知终端设备在进入非激活态后继续接收多播业务的数据，通过复用信令实现指示的灵活性，无需额外的信令来指示，能够进一步降低信令开销。
进一步地，对于处于非激活态的终端设备，如果存在所述多播业务的数据需要传输，则将所述第一指示信息承载在寻呼中发送出去，所述寻呼中还包括所述多播业务的标识。本发明技术方案中，网络设备可以在通过寻呼指示将要传输多播业务的数据时，一并向终端设备指示能够在非激活态接收多播业务的数据，实现指示的灵活性。
附图说明
图1是本发明实施例中一种非激活态多播业务发送方法的流程 图；
图2是本发明实施例中一种非激活态多播业务传输的交互流程图
图3是本发明实施例中另一种非激活态多播业务传输的交互流程图；
图4是本发明实施例中一种非激活态多播业务传输方法的流程图；
图5是本发明实施例中又一种非激活态多播业务传输方法的交互流程图；
图6是本发明实施例中又一种非激活态多播业务传输方法的交互流程图；
图7是本发明实施例中一种非激活态多播业务发送装置的结构示意图；
图8是本发明实施例中一种非激活态多播业务接收装置的结构示意图；
图9本发明实施例中一种通信装置的硬件结构示意图。
具体实施方式
本申请实施例适用的通信系统包括但不限于长期演进(long term evolution，LTE)系统、第五代(5th-generation，5G)系统、NR系统，以及未来演进系统或者多种通信融合系统。其中，5G系统可以为非独立组网(non-standalone，NSA)的5G系统或独立组网(standalone，SA)的5G系统。本申请技术方案也适用于不同的网络架构，包括但不限于中继网络架构、双链接架构、Vehicle-to-Everything(车辆到任何物体的通信)架构等架构。
本申请主要涉及终端设备和网络设备之间的通信。其中：
本申请实施例中的网络设备也可以称为接入网设备，例如，可以为基站(base station，BS)(也可称为基站设备)，网络设备是一种部署在无线接入网(Radio Access Network，RAN)用以提供无线通信功能的装置。例如在第二代(2nd-generation，2G)网络中提供基站功能的设备包括基地无线收发站(base transceiver station,BTS)，第三代(3rd-generation，3G)网络中提供基站功能的设备包括节点B(NodeB)，在第四代(4th-generation，4G)网络中提供基站功能的设备包括演进的节点B(evolved NodeB，eNB)，在无线局域网络(wireless local area networks，WLAN)中，提供基站功能的设备为接入点(access point，AP)，NR中的提供基站功能的设备下一代基站节点(next generation node base station，gNB),以及继续演进的节点B(ng-eNB),其中gNB和终端设备之间采用NR技术进行通信，ng-eNB和终端设备之间采用演进的通用地面无线电接入(Evolved Universal Terrestrial Radio Access,E-UTRA)技术进行通信，gNB和ng-eNB均可连接到5G核心网。本申请实施例中的网络设备还包含在未来新的通信系统中提供基站功能的设备等。
本申请实施例中的终端设备(terminal equipment)可以指各种形式的接入终端、用户单元、用户站、移动站、移动台(mobile station，MS)、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。终端设备还可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(Public Land Mobile Network，PLMN)中的终端设备等，本申请实施例对此并不限定。终端设备也可以称为用户设备(User Equipment，UE)、终端等。
如背景技术中所述，在当前的协议版本中，网络设备会通知终端设备多播业务即将开始传输，处于空闲态或非激活态的终端设备收到 寻呼(Paging)通知之后，如果对该多播业务感兴趣，需要转入连接态接收多播业务。如果终端设备能够在非激活态接收多播业务，处于非激活态的终端设备首先需要确定自己是否可以在当前状态接收多播业务。
本发明技术方案提供了一种方法，通过设置第一指示信息和第二指示信息，能够使得终端设备明确在非激活态接收多播业务的数据，实现非激活态多播业务的传输，从而降低终端设备的信令开销以及降低网络负载。
在非激活态传输多播业务需要解决的另一个问题是，一旦允许处于非激活态的终端设备接收多播业务，网络设备可能不清楚需要在哪些波束(Beam)发送多播业务。在当前协议版本中，处于连接态的终端设备接收多播业务时，网络设备能够通过终端设备在层1或层3等的上报信息获知需要在哪些波束传输多播业务。但是对于非激活态的终端设备，网络设备很难及时跟踪服务该终端设备的波束，因此需要确定传输多播业务的波束，以便非激活态的终端设备能够接收到多播业务。
为使本发明的上述目的、特征和优点能够更为明显易懂，下面结合附图对本发明的具体实施例做详细的说明。
图1是本发明实施例一种非激活态多播业务发送方法。
所述非激活态多播业务发送方法可以用于网络设备侧，也即可以由网络设备执行所述发送方法的各个步骤。
具体地，非激活态多播业务发送方法可以包括以下步骤：
步骤101：发送第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；
步骤102：发送多播业务的数据。
需要指出的是，本实施例中各个步骤的序号并不代表对各个步骤的执行顺序的限定。
本实施例中，第一指示信息能够直接指示终端设备是否能够在非激活态接收多播业务；第二指示信息则是通过条件间接指示终端设备是否能够在非激活态接收多播业务。网络设备可以发送第一指示信息至终端设备，终端设备根据第一指示信息的指示，能够在非激活态接收多播业务的数据。网络设备也可以发送第二指示信息至终端设备，终端设备根据第二指示信息指示的条件，判断自身是否能够在非激活态接收多播业务的数据。
相应地，终端设备接收第一指示信息和/或第二指示信息；如果终端设备确定能够在非激活态接收多播业务的数据，则终端设备在非激活态接收多播业务的数据。
进一步地，第二指示信息可以包含终端设备在非激活态接收多播业务的条件相关的部分或全部参数。
可以理解的是，在具体实施中，所述非激活态多播业务发送方法、接收方法可以采用软件程序的方式实现，该软件程序运行于芯片或芯片模组内部集成的处理器中。该方法也可以采用软件结合硬件的方式实现，本申请不作限制。
在一个非限制性的实施例中，网络设备将所述第一指示信息承载在RRC释放信令中发送至终端设备。
具体请参照图2，图2示出了终端设备和网络设备的一种交互图。
在步骤201中，网络设备发送RRC释放信令至终端设备。RRC释放信令中包括第一指示信息和/或第二指示信息。终端设备在接收到RRC释放信令之后，释放连接进入非激活态，并且通过RRC释放信令中的第一指示信息和/或第二指示信息确定能够在非激活态接收多播业务。
具体地，终端设备处于连接态，且正在接收多播业务，网络设备 发现在时长为预设时长的时间段内没有该多播业务的数据传输，也没有其他多播业务和单播业务，则网络设备可以发送上述RRC释放信令。
在步骤202中，网络设备发送寻呼至终端设备。
具体地，网络设备在有多播业务的数据需要传输时，通过寻呼通知终端设备有多播业务的数据传输。
在步骤203中，网络设备发送多播业务的数据至终端设备。
具体地，终端设备利用之前保存的多播业务的配置参数，例如搜索空间配置等参数，在非激活态接收该多播业务的数据。
在一个非限制性的实施例中，当网络设备发送第二指示信息时，可以将第二指示信息承载在RRC信令中发送出去。该RRC信令可以是RRC释放信令，也可以是其他任意可实施的RRC信令，本发明实施例对此不作限制。
在一个非限制性的实施例中，网络设备将所述第一指示信息承载在寻呼中发送至终端设备。
具体请参照图3，图3示出了终端设备和网络设备的一种交互图。
在步骤301中，网络设备发送RRC释放信令至终端设备。
具体地，终端设备处于连接态，且正在接收多播业务。服务小区在没有多播业务的数据传输时，例如在时长为预设时长的时间段内没有该多播业务的数据传输，也没有其他多播业务和单播业务，则发送RRC释放信令，以将处于连接态的终端设备转入非激活态，以降低网络负载。
在步骤302中，网络设备发送寻呼至终端设备。寻呼中包括第一指示信息。
具体地，网络设备在有多播业务的数据需要传输时，通过寻呼通 知终端设备有多播业务的数据传输，同时在寻呼中指示终端设备可以在非激活态接收多播业务的数据。
在步骤303中，网络设备发送多播业务的数据至终端设备。
具体地，终端设备利用之前保存的多播业务的配置参数，例如搜索空间配置等参数，在非激活态接收该多播业务的数据。
在一个非限制性的实施例中，第一指示信息与至少一种多播业务的标识具有对应关系，所述第二指示信息与至少一种多播业务的标识具有对应关系。
具体实施中，由于存在多种类型的多播业务，因此可以针对每种类型的多播业务独立地指示是否可以在非激活态接收。具体可以是将第一指示信息与多播业务的标识之间建立关联，第一指示信息可以对应一个多播业务的标识，也可以对应多个多播业务的标识。类似地，第二指示信息可以对应一个多播业务的标识，也可以对应多个多播业务的标识。
具体地，寻呼中包括多个多播业务的标识。那么在寻呼中承载第一指示信息时，第一指示信息可以包括多个比特值，每一比特值对应一个多播业务的标识。在一个具体的例子中，多播业务的标识可以是列表的形式，第一指示信息也可以是列表的形式，两个列表相应位置的内容具有对应关系，以便终端设备依据对应关系获知哪个多播业务可以在非激活态接收。
在一个非限制性的实施例中，所述第二指示信息包括以下一项或多项：处于可接收所述多播业务的服务小区；处于接收所述第一指示信息或第二指示信息时的服务小区；处于所述服务小区的一个或多个波束下，且至少一波束的信号质量达到预设门限；处于所述服务小区，且上行提前定时器没有超时，配置的一个或多个配置授权有效(Configured Grant,CG)；处于所述服务小区，且上行提前定时器没有超时，所述服务小区配置用于传输混合自动重传请求(Hybrid  Automatic Repeat reQuest，HARQ)反馈的上行资源。
具体实施中，第二指示信息可以直接指示具体的条件内容，也可以包括条件相关的部分或全部参数，比如对于处于所述服务小区的一个或多个波束下，且至少一个波束的信号质量达到预设门限，第二指示信息可以指示一个或多个波束标识，以及指示预设门限值(也即接收多播业务的信号质量门限)；对于上行提前定时器没有超时，配置的一个或多个配置授权有效，第二指示信息可以指示上行提前定时器的时长以及配置的一个或多个配置授权；对于上行提前定时器没有超时，配置用于传输混合自动重传请求反馈的上行资源，第二指示信息可以指示上行提前定时器的时长以及配置的上行资源。终端设备获得条件相关的部分或全部参数，就能够确定条件的具体内容，进而可以判断是否满足条件。
其中，至少一波束的信号质量达到预设门限这一条件能够保证终端设备在非激活态可靠地接收多播业务的数据。上行提前定时器没有超时这一条件能够保证终端设备处于能够进行上行反馈的前提条件，配置的一个或多个配置授权有效这一条件能够保证终端设备具有上行反馈可用的上行资源。类似地，服务小区配置用于传输HARQ反馈的上行资源这一条件能够保证终端设备具有上行反馈可用的上行资源，该上行资源可以是物理上行控制信道(Physical Uplink Control Channel,PUCCH)资源。
具体实施中，终端设备进入非激活态之后，依据网络设备所配置的准则(也即第二指示信息)判断是否可以在非激活态接收多播业务。在服务小区重新开始传输多播业务的数据时，如果终端设备判断可以在非激活态接收多播业务，则维持在非激活态，利用保存的检测多播业务的下行控制信令对应的搜索空间等参数接收多播业务的数据。如果终端设备判断不满足准则，比如终端设备发现服务小区所配置的多个波束的信号质量均低于预设门限、或者服务小区所配置的CG不再有效等，终端设备不在非激活态接收多播数据。如果终端设备此时仍 然对多播业务感兴趣，终端设备需要发起无线资源控制(Radio Resource Control,RRC)连接建立或恢复流程，在进入连接态之后，等待服务小区的重配置，之后再接收多播业务的数据。
在一个具体应用场景中，一个NR小区支持多播业务(Multicast)，该NR小区可以向小区内不同状态的终端设备，如RRC连接态、非激活态(可以扩展到空闲态)的终端设备传输多播业务。在一段时间内，NR小区需要传输3种多播业务，分别称为会话(session)1、session 2和session 3。依据不同会话的服务质量参数，NR小区认为Session 1可以由连接态的终端设备和非激活态的终端设备接收，而其他两个会话(session 2和session 3)需要由连接态的终端设备接收。
在一种实现方式中，网络设备通过RRC释放信令(RRC Release)配置在非激活态接收多播业务(也即第一指示信息)，并按照会话进行配置。例如，对于正在接收Session 1的处于连接态的终端设备UE1，如果服务小区发现一段时间内没有该Session1的数据的传输，并且该UE1没有其他多播和单波(unicast)业务，网络设备可以通过RRC释放信令，释放该UE1的RRC连接，通知UE1进入非激活态，同时在该信令中指示Session 1可以在非激活态接收。
UE1在进入非激活态之后，保存在激活态所获得的接收Session 1的相关配置，如检测多播业务的下行控制信令对应的搜索空间等参数。过了一段时间，网络设备从核心网获得新的Session 1的数据。网络设备通过寻呼指示、或者是多播业务的更新信息(可以是组激活通知指示、或者是MCCH改变通知)指示对Session 1感兴趣的终端设备接收多播数据。UE1收到指示之后，利用所保存的检测该多播业务的搜索空间的参数，在非激活态接收Session 1。
在另一种实现方式中，网络设备利用RRC信令配置在非激活态接收多播业务的准则(也即第二指示信息)，终端设备按照准则判断是否在非激活态接收多播业务。
例如，对于正在接收Session 1的处于连接态的UE2，如果服务 小区发现一段时间内没有该Session1的数据的传输，并且该UE2没有其他多播和单波(unicast)业务，服务小区可以通过RRC释放信令，释放该UE的RRC连接，通知UE2进入非激活态，同时在该信令中指示可以在非激活态接收Session 1的准则。可能的准则有以下一项或多项：
1.UE2继续在该服务小区中(即发送准则的服务小区)，或者
2.UE2在该服务小区所配置的一个或多个波束下，UE2测得多个波束中任一个(至少一个)波束需要超过预设门限(也即信号质量门限)，如服务小区依据SSB配置波束，配置了SSB1和SSB2，并且配置了一个预设门限，只要UE2测得SSB1或SSB2至少一个超过预设门限就认为满足准则，或者
3.UE2在该服务小区下，上行提前定时器(Timing Advance Timer)没有超时，且所配置的一个或多个配置授权有效，UE2可以通过配置授权上传必要的信息，如针对接收多播数据的HARQ ACK/NACK、UE2测得的波束的信道状态信息等，或者
4.UE2在该服务小区下，上行提前定时器没有超时，且服务小区为UE2配置了用于传输HARQ反馈的PUCCH资源。
UE2进入非激活态之后，依据网络设备所配置的准则判断是否可以在非激活态接收Session 1。在服务小区重新开始传输Session 1的数据时，如果UE2判断可以在非激活态接收Session 1，则维持在非激活态，利用保存的检测多播业务的下行控制信令对应的搜索空间等参数接收Session 1的调度信息和数据。如果UE2判断不满足准则，比如UE2发现服务小区所配置的多个波束的信号质量均低于预设门限、或者服务小区所配置的配置授权不再有效等，则UE2不在非激活态接收Session 1的数据。如果UE2此时仍然对Session1感兴趣，UE2需要发起RRC连接建立或恢复流程，在进入连接态之后，等待服务小区的重配置，之后再接收Session 1的数据。
在又一种实现方式中，服务小区在没有多播数据传输时，可以将原先处于连接态接收多播数据的终端设备转入非激活态。过一段时间，如果有多播数据传输，服务小区通过寻呼通知终端设备Session 1有数据传输，同时服务小区在寻呼中指示可以在非激活态接收Session 1的数据。
对于转入非激活态的终端设备，此时利用之前保存的接收Session 1的配置，如搜索空间配置等参数，接收Session 1的数据。
在又一种实现方式中，服务小区通过第一指示信息通知终端设备在非激活态接收多播业务，终端设备在非激活态接收多播业务需要满足的条件(即准则)由协议预先设定，处于非激活态的终端设备如果继续对多播业务感兴趣，则需要判断所述条件是否满足，在满足所述条件且接收到指示所述多播业务的数据传输的寻呼或更新信息后，接收所述多播业务的数据。在非激活态接收多播业务需要满足的条件即包含以下一项或多项：
1.UE继续在该服务小区中(即发送第一指示信息的服务小区)，或者
2.UE在该服务小区所配置的一个或多个波束下，UE测得多个波束中任一个(至少一个)波束超过预设门限，如服务小区依据SSB配置波束，配置了SSB1和SSB2，并且配置了一个预设门限，只要UE2测得SSB1或SSB2任一个超过预设门限就认为满足准则，或者3.UE在该服务小区下，上行提前定时器(Timing Advance Timer)没有超时，且所配置的一个或多个配置授权有效，UE2可以通过配置授权上传必要的信息，如针对接收多播数据的HARQ ACK/NACK、UE测得的波束的信道状态信息等，或者
4.UE在该服务小区下，上行提前定时器没有超时，且服务小区为UE配置了用于传输HARQ反馈的PUCCH资源。
本发明实施例还公开了一种非激活态多播业务传输方法。本实施 例中的终端设备处于非激活态。
具体地，请参照图4，非激活态多播业务传输方法可以包括以下步骤：
终端设备首先通过服务小区的系统消息或者MCCH获知可以在非激活态接收的多播业务的业务标识，以及每个多播业务对应的前导码信息，期待在非激活态接收多播业务的UE，依据自己感兴趣多播业务对应的前导码，通过随机接入流程使得网络设备获知自己所处的波束位置，网络设备可以在相应的波束发送多播数据，避免在所有的波束上发送多播数据，可以有效节省无线传输资源。
步骤401：终端设备在第一波束对应的随机接入时机(RACH Occasion)发送前导码(Preamble)。其中，终端设备处于第一波束上，也即终端设备利用第一波束收发数据。相应地，网络设备接收前导码。
步骤402：网络设备根据前导码的接收时机确定第一波束的信息。具体地，网络设备可以确定第一波束的标识。
步骤403：网络设备在第一波束上发送多播业务的数据。也即，当网络设备通过前导码获知终端设备在第一波束上收发数据后，可以通过第一波束将多播业务的数据发给终端设备，以实现多播业务的可靠传输。相应地，终端设备接收多播业务的数据。
本发明实施例能够使得网络设备获知需要在哪些波束发送多播业务，也就是说，网络设备能够获知处于非激活态的终端设备在小区的分布，以及该终端设备在哪些波束接收多播业务的数据，从而使得多播业务的数据能够被正确地传输至处于非激活态的终端设备。
在一个具体实施例中，前导码可以是通过消息1(Msg1)发送和接收的。
在一个非限制性的实施例中，请参照图5，终端设备和网络设备的交互流程如下所述。
在步骤501中，终端设备发送Msg1至网络设备，Msg1中包括前导码。其中，该前导码可以是普通前导码，也即通信标准协议中规定的前导码的形式和内容。
在步骤502中，网络设备根据前导码的接收时机确定第一波束的信息。
在步骤503中，网络设备发送Msg2至终端设备。Msg2可以是Msg1的响应消息，具体可以是随机接入响应。
在步骤504中，终端设备发送Msg3至网络设备，Msg3中包括自己感兴趣的多播业务的业务标识。
在步骤505中，网络设备发送Msg4至终端设备。Msg4可以是Msg3的响应消息，具体可以是确认消息(ACK)或者冲突解决消息。
至此，网络设备可以获知终端设备接收多播数据使用的第一波束的标识，以及终端设备感兴趣的多播业务的业务标识。那么，网络设备可以在第一波束上发送业务标识指向的多播业务的数据至终端设备。
在另一个非限制性的实施例中，请参照图6，终端设备和网络设备的交互流程如下所述。
步骤601：终端设备发送Msg1至网络设备，Msg1中包括多播业务专用的前导码。具体地，网络设备可以在MBMS点到多点控制信道(MBMS Control Channel,MCCH)中为请求多播业务发送的终端设备分配特定的前导码，如分配专用的前导码用于Session 1的请求。
步骤602：网络设备根据前导码的接收时机确定第一波束的信息。进一步地，网络设备还可以确定前导码对应的多播业务的业务标识。
步骤603：网络设备发送Msg2至终端设备。Msg2可以是Msg1的响应消息，具体可以是随机接入响应。
步骤604：网络设备在第一波束上发送多播业务的数据。
相对于前述实施例，本发明实施例通过设置多播业务专用的前导码，终端设备和网络设备仅需通过交互Msg1和Msg2就能使网络设备获得所需的信息，提升终端设备和网络设备交互的效率。
需要说明的是，终端设备可以发送多次前导码，以向网络设备反馈波束信息，直至接收到多播业务的数据。
在具体实施中，因为NR会在高频部署，无线信号在高频呈现出方向性好、路损大的特点，一个覆盖范围较大的小区需要多个波束(Beam)才能实现完整的覆盖，一个波束只能覆盖有限的范围。覆盖范围较小的小区可以只包含一个波束。对于由多个波束构成的小区，由于硬件的限制，不是所有的波束均可以在同一时间进行传输，需要分时传输，称之为扫波束(Beam Sweeping)。对于NR中的一个小区，其同步信号(包括主同步信号和辅同步信号)的传输按照一定的周期，如5ms/10ms/20ms/40ms/80ms进行传输。一个小区会传输一个或多个同步信号块(Synchronization Signal Block,SSB)(即不同的波束)，如4个SSB或8个SSB。在一个周期内，这些SSB分布在5ms内。一个SSB包括PSS/SSS和PBCH。PSS和SSS用于使终端设备识别小区标识，以及使终端设备获得符号级别的同步。终端设备评估一个小区的信号质量时需要将所测得的该小区最强的N个波束综合获得小区的信号质量。N值可以由网络配置，N>＝1。
在一个具体的应用场景中，服务小区通常包含SSB0到SSB7共8个SSB。服务小区依据当前需要接收Session1的处于连接态终端设备的分布确定至少需要在SSB2、SSB3和SSB5中传输Session 1的数据。但服务小区并不清楚当前处于非激活态的需要接收Session 1的终端设备在小区内的分布，即不知道处于非激活态的终端设备会在哪些波束接收多播数据。
为了明确需要在SSB2、SSB3和SSB5之外的哪些其他波束发送Session 1的数据，服务小区在MCCH中指示Session 1将要传输的波束信息(也即SSB2、SSB3和SSB5)，对于需要由其他波束服务的处 于非激活态的终端设备，需要向服务小区发送反馈信息，指示自己需要在哪个波束接收Session 1。
具体而言，处于非激活态的终端设备如果可以在SSB2、SSB3或SSB5接收Session 1，这些终端设备不需要向基站指示任何信息。对于不能在SSB2、3、5接收Session 1的终端设备，需要向服务小区指示自己需要在哪个波束(或哪几个波束)接收Session 1，可以通过随机接入流程指示自己需要在哪个波束(或哪几个波束)接收Session 1。
其中一种方式是终端设备通过Msg1发送前导码，并通过Msg3向服务小区指示Session 1的标识。网络设备从终端设备发送前导码的时机判断终端设备需要在哪个SSB接收Session 1。
另一种方式是服务小区可以在MCCH中为请求多播业务的终端设备分配特定的前导码(多播业务专用的前导码)，如分配专用的前导码用于Session 1的请求。服务小区一旦收到该前导码，可以从UE发送前导码的时机判断终端设备需要在哪个SSB接收Session 1。
如果终端设备多次请求还是不能从相应的波束接收Session 1，则终端设备向网络设备发起RRC连接/恢复请求，进入连接态之后请求服务小区向自己发送Session 1。请求失败的次数门限可以由服务小区设置，在低于等于这个门限次数时，终端设备通过上述方式向网络设备指示感兴趣的多播业务和自己所处的波束信息。
请参照图7，本发明实施例还公开了一种非激活态多播业务发送装置。非激活态多播业务发送装置70可以包括：
指示信息发送模块701，用于发送第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；
数据发送模块702，用于发送多播业务的数据。
在具体实施中，上述非激活态多播业务发送装置可以对应于网络设备中具有非激活态多播业务发送功能的芯片，例如SOC (System-On-a-Chip，片上系统)、基带芯片等；或者对应于网络设备中包括具有非激活态多播业务发送功能的芯片模组；或者对应于具有数据处理功能芯片的芯片模组，或者对应于网络设备。
请参照图8，本发明实施例还公开了一种非激活态多播业务接收装置。非激活态多播业务接收装置80可以包括：
指示信息接收模块801，用于接收第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；
数据接收模块802，用于在非激活态接收多播业务的数据。
在具体实施中，上述非激活态多播业务接收装置可以对应于终端设备中具有非激活态多播业务接收功能的芯片，例如SOC(System-On-a-Chip，片上系统)、基带芯片等；或者对应于终端设备中包括具有非激活态多播业务接收功能的芯片模组；或者对应于具有数据处理功能芯片的芯片模组，或者对应于终端设备。
关于所述非激活态多播业务发送装置70或非激活态多播业务接收装置80的工作原理、工作方式的更多内容，可以参照图1至图6中的相关描述，这里不再赘述。
关于上述实施例中描述的各个装置、产品包含的各个模块/单元，其可以是软件模块/单元，也可以是硬件模块/单元，或者也可以部分是软件模块/单元，部分是硬件模块/单元。例如，对于应用于或集成于芯片的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于芯片模组的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于芯片模组的同一组件(例如芯片、电路模块等)或者不同组件中，或者，至少部分 模块/单元可以采用软件程序的方式实现，该软件程序运行于芯片模组内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现；对于应用于或集成于终端的各个装置、产品，其包含的各个模块/单元可以都采用电路等硬件的方式实现，不同的模块/单元可以位于终端内同一组件(例如，芯片、电路模块等)或者不同组件中，或者，至少部分模块/单元可以采用软件程序的方式实现，该软件程序运行于终端内部集成的处理器，剩余的(如果有)部分模块/单元可以采用电路等硬件方式实现。
本发明实施例还公开了一种存储介质，所述存储介质为计算机可读存储介质，其上存储有计算机程序，所述计算机程序运行时可以执行图1至图6中所示方法的步骤。所述存储介质可以包括ROM、RAM、磁盘或光盘等。所述存储介质还可以包括非挥发性存储器(non-volatile)或者非瞬态(non-transitory)存储器等。
请参照图9，本申请实施例还提供了一种通信装置的硬件结构示意图。该装置包括处理器901、存储器902和收发器903。
处理器901可以是一个通用中央处理器(central processing unit，CPU)、微处理器、特定应用集成电路(application-specific integrated circuit，ASIC)，或者一个或多个用于控制本申请方案程序执行的集成电路。处理器601也可以包括多个CPU，并且处理器901可以是一个单核(single-CPU)处理器，也可以是多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路或用于处理数据(例如计算机程序指令)的处理核。
存储器902可以是ROM或可存储静态信息和指令的其他类型的静态存储设备、RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compactdisc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或 者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，本申请实施例对此不作任何限制。存储器902可以是独立存在(此时，存储器902可以位于该装置外，也可以位于该装置内)，也可以和处理器901集成在一起。其中，存储器902中可以包含计算机程序代码。处理器901用于执行存储器902中存储的计算机程序代码，从而实现本申请实施例提供的方法。
处理器901、存储器902和收发器903通过总线相连接。收发器903用于与其他设备或通信网络通信。可选的，收发器903可以包括发射机和接收机。收发器903中用于实现接收功能的器件可以视为接收机，接收机用于执行本申请实施例中的接收的步骤。收发器903中用于实现发送功能的器件可以视为发射机，发射机用于执行本申请实施例中的发送的步骤。
当图9所示的结构示意图用于示意上述实施例中所涉及的终端设备的结构时，处理器901用于对终端设备的动作进行控制管理，例如，处理器901用于支持终端设备执行图5中的步骤501和步骤504，或者图6中的步骤601，和/或本申请实施例中所描述的其他过程中的终端设备执行的动作。处理器901可以通过收发器903与其他网络实体通信，例如，与上述网络设备通信。存储器902用于存储终端设备的程序代码和数据。所述处理器运行所述计算机程序时可以控制所述收发器903接收RRC释放信令、寻呼、多播业务的数据、Msg2、Msg4等。
当图9所示的结构示意图用于示意上述实施例中所涉及的网络设备的结构时，处理器901用于对网络设备的动作进行控制管理，例如，处理器901用于支持网络设备执行图1中的步骤101和步骤102，或者图2中的步骤201、步骤202和步骤203，图3中的步骤301、步骤302和步骤303，图4中的步骤402和步骤403，图5中的步骤502、步骤503和步骤505，图6中的步骤602、步骤603和步骤604。 和/或本申请实施例中所描述的其他过程中的网络设备执行的动作。处理器901可以通过收发器903与其他网络实体通信，例如，与上述终端设备通信。存储器902用于存储网络设备的程序代码和数据。所述处理器运行所述计算机程序时可以控制所述收发器903发送RRC信令、MAC信令和DCI中的一个或多个。
本申请实施例定义接入网到终端设备的单向通信链路为下行链路，在下行链路上传输的数据为下行数据，下行数据的传输方向称为下行方向；而终端设备到接入网的单向通信链路为上行链路，在上行链路上传输的数据为上行数据，上行数据的传输方向称为上行方向。
本申请实施例定义接入网到终端的单向通信链路为下行链路，在下行链路上传输的数据为下行数据，下行数据的传输方向称为下行方向；而终端到接入网的单向通信链路为上行链路，在上行链路上传输的数据为上行数据，上行数据的传输方向称为上行方向。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/“，表示前后关联对象是一种“或”的关系。
本申请实施例中出现的“多个”是指两个或两个以上。
本申请实施例中出现的第一、第二等描述，仅作示意与区分描述对象之用，没有次序之分，也不表示本申请实施例中对设备个数的特别限定，不能构成对本申请实施例的任何限制。
本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式，以实现设备间的通信，本申请实施例对此不做任何限定。
应理解，本申请实施例中，所述处理器可以为中央处理单元(central processing unit，简称CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，简称DSP)、专用集成电路(application specific integrated circuit，简称ASIC)、现成可编 程门阵列(field programmable gate array，简称FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，简称ROM)、可编程只读存储器(programmable ROM，简称PROM)、可擦除可编程只读存储器(erasable PROM，简称EPROM)、电可擦除可编程只读存储器(electrically EPROM，简称EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，简称RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，简称RAM)可用，例如静态随机存取存储器(static RAM，简称SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，简称SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，简称DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，简称ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，简称SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，简称DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线或无线方式向另一个网站站点、计算机、服务器或 数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
在本申请所提供的几个实施例中，应该理解到，所揭露的方法、装置和系统，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的；例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式；例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本发明各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理包括，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用硬件加软件功能单元的形式实现。
上述以软件功能单元的形式实现的集成的单元，可以存储在一个计算机可读取存储介质中。上述软件功能单元存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本发明各个实施例所述方法的部分步骤。 而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，简称ROM)、随机存取存储器(Random Access Memory，简称RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
虽然本发明披露如上，但本发明并非限定于此。任何本领域技术人员，在不脱离本发明的精神和范围内，均可作各种更动与修改，因此本发明的保护范围应当以权利要求所限定的范围为准。

Claims (24)

  1. 一种非激活态多播业务发送方法，其特征在于，包括：
    发送第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；
    发送多播业务的数据。
  2. 根据权利要求1所述的非激活态多播业务发送方法，其特征在于，所述第一指示信息与至少一种多播业务的标识具有对应关系，所述第二指示信息与至少一种多播业务的标识具有对应关系。
  3. 根据权利要求1所述的非激活态多播业务发送方法，其特征在于，所述发送第一指示信息包括：
    将所述第一指示信息承载在RRC释放信令中发送出去。
  4. 根据权利要求1所述的非激活态多播业务发送方法，其特征在于，所述发送第二指示信息包括：
    将所述第二指示信息承载在RRC信令中发送出去。
  5. 根据权利要求3或4所述的非激活态多播业务发送方法，其特征在于，所述发送第一指示信息和/或第二指示信息包括：
    对于接收所述多播业务且处于连接态的终端设备，如果在时长为预设时长的时间段内没有多播业务和单播业务，则发送所述第一指示信息或所述第二指示信息。
  6. 根据权利要求1所述的非激活态多播业务发送方法，其特征在于，所述发送第一指示信息包括：
    将所述第一指示信息承载在寻呼中发送出去。
  7. 根据权利要求6所述的非激活态多播业务发送方法，其特征在于，所述发送第一指示信息包括：
    对于处于非激活态的终端设备，如果存在所述多播业务的数据需要传输，则将所述第一指示信息承载在寻呼中发送出去，所述寻呼中还包括所述多播业务的标识。
  8. 根据权利要求1所述的非激活态多播业务发送方法，其特征在于，所述第二指示信息包括以下一项或多项条件：
    处于可接收所述多播业务的服务小区；
    处于接收所述第一指示信息或第二指示信息时的服务小区；
    接收所述多播业务的信号质量门限；
    处于所述服务小区，且上行提前定时器没有超时，配置的一个或多个配置授权有效；
    处于所述服务小区，且上行提前定时器没有超时，所述服务小区配置用于传输HARQ反馈的上行资源。
  9. 根据权利要求1所述的非激活态多播业务发送方法，其特征在于，所述第二指示信息包括与所述条件相关的部分参数或全部参数。
  10. 根据权利要求1所述的非激活态多播业务发送方法，其特征在于，发送多播业务的数据包括：
    接收终端设备通过MSG1或MSG3指示的波束信息，并在所述波束信息指示的波束发送所述多播业务的数据。
  11. 一种非激活态多播业务接收方法，其特征在于，包括：
    接收第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；
    在非激活态接收多播业务的数据。
  12. 根据权利要求11所述的非激活态多播业务接收方法，其特征在于， 在接收到第一指示信息的情况下，在非激活态接收多播业务需要满足的条件由协议预先设定。
  13. 根据权利要求11所述的非激活态多播业务接收方法，其特征在于，所述第一指示信息是按照多播业务标识来设置是否在非激活态接收多播业务的。
  14. 根据权利要求11所述的非激活态多播业务接收方法，其特征在于，所述接收第一指示信息包括：
    接收RRC释放信令，所述RRC释放信令包括所述第一指示信息。
  15. 根据权利要求11所述的非激活态多播业务接收方法，其特征在于，所述接收第二指示信息包括：
    在激活态接收RRC信令，所述RRC信令包括所述第二指示信息。
  16. 根据权利要求13或14所述的非激活态多播业务接收方法，其特征在于，所述接收第一指示信息和/或第二指示信息之后包括：
    进入非激活态；
    保存在所述激活态时所获得的接收所述多播业务的参数配置。
  17. 根据权利要求11所述的非激活态多播业务接收方法，其特征在于，所述接收第一指示信息包括：
    在非激活态接收寻呼，所述寻呼包括所述第一指示信息。
  18. 根据权利要求11所述的非激活态多播业务接收方法，其特征在于，所述在非激活态接收多播业务的数据包括：
    如果接收到所述第一指示信息，则在接收到指示所述多播业务的数据传输的寻呼或更新信息后，接收所述多播业务的数据；
    如果接收到所述第二指示信息，则判断所述第二指示信息所指示的条件是否满足，并在满足所述条件且接收到指示所述多播业务的数据传输的寻呼或更新信息后，接收所述多播业务的数据；
    如果仅收到所述第一指示信息，并且在非激活态接收多播业务需要满足的条件由协议预先设定时，判断所述条件是否满足，在满足所述条件且接收到指示所述多播业务的数据传输的寻呼或更新信息后，接收所述多播业务的数据。
  19. 根据权利要求11所述的非激活态多播业务接收方法，其特征在于，所述第二指示信息包括以下一项或多项条件：
    处于可接收所述多播业务的服务小区；
    处于接收所述第一指示信息或第二指示信息时的服务小区；
    接收所述多播业务的信号质量门限；
    处于所述服务小区，且上行提前定时器没有超时，配置的一个或多个配置授权有效；
    处于所述服务小区，且上行提前定时器没有超时，所述服务小区配置用于传输HARQ反馈的上行资源。
  20. 一种非激活态多播业务发送装置，其特征在于，包括：
    指示信息发送模块，用于发送第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；
    数据发送模块，用于发送多播业务的数据。
  21. 一种非激活态多播业务接收装置，其特征在于，包括：
    指示信息接收模块，用于接收第一指示信息和/或第二指示信息，所述第一指示信息指示在非激活态接收多播业务，所述第二指示信息指示在非激活态接收多播业务需要满足的条件；
    数据接收模块，用于在非激活态接收多播业务的数据。
  22. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，所述计算机程序被处理器运行时执行权利要求1至10中任一项所 述非激活态多播业务发送方法的步骤，或者权利要求11至19任一项所述非激活态多播业务接收方法的步骤。
  23. 一种网络设备，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，其特征在于，所述处理器运行所述计算机程序时执行权利要求1至10中任一项所述非激活态多播业务发送方法的步骤。
  24. 一种终端设备，包括存储器和处理器，所述存储器上存储有可在所述处理器上运行的计算机程序，其特征在于，所述处理器运行所述计算机程序时执行权利要求11至19任一项所述非激活态多播业务接收方法的步骤。
PCT/CN2022/124552 2021-10-19 2022-10-11 非激活态多播业务发送、接收方法及装置 WO2023066081A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111217425.4A CN115996485A (zh) 2021-10-19 2021-10-19 非激活态多播业务发送、接收方法及装置
CN202111217425.4 2021-10-19

Publications (1)

Publication Number Publication Date
WO2023066081A1 true WO2023066081A1 (zh) 2023-04-27

Family

ID=85994105

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/124552 WO2023066081A1 (zh) 2021-10-19 2022-10-11 非激活态多播业务发送、接收方法及装置

Country Status (2)

Country Link
CN (1) CN115996485A (zh)
WO (1) WO2023066081A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210127448A1 (en) * 2019-10-24 2021-04-29 Qualcomm Incorporated Maintaining a multicast/broadcast radio bearer in an idle state or an inactive state
WO2021120018A1 (zh) * 2019-12-17 2021-06-24 华为技术有限公司 一种通信方法及装置
CN113163456A (zh) * 2020-01-07 2021-07-23 大唐移动通信设备有限公司 一种通信方法及装置
US20210321226A1 (en) * 2020-04-08 2021-10-14 Qualcomm Incorporated Feedback for multicast transmissions while in an inactive or idle mode

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210127448A1 (en) * 2019-10-24 2021-04-29 Qualcomm Incorporated Maintaining a multicast/broadcast radio bearer in an idle state or an inactive state
WO2021120018A1 (zh) * 2019-12-17 2021-06-24 华为技术有限公司 一种通信方法及装置
CN113163456A (zh) * 2020-01-07 2021-07-23 大唐移动通信设备有限公司 一种通信方法及装置
US20210321226A1 (en) * 2020-04-08 2021-10-14 Qualcomm Incorporated Feedback for multicast transmissions while in an inactive or idle mode

Also Published As

Publication number Publication date
CN115996485A (zh) 2023-04-21

Similar Documents

Publication Publication Date Title
US20230300938A1 (en) Methods and systems for managing mbs service continuity for a ue
US20210323490A1 (en) System and method of reducing interruptions for vehicle to vehicle communication
CN110602654B (zh) 使用mbms中继装置管理多媒体广播多播服务
WO2021259129A1 (zh) 一种通信方法及通信装置
EP4106358A1 (en) Wireless communication method and communication apparatus
WO2018145558A1 (zh) 数据传输方法及装置
TWI771369B (zh) 系統訊息的獲取方法及裝置
US20230254933A1 (en) State switching method and apparatus, method and apparatus for indicating connected-state mtch, storage medium, terminal and base station
WO2019233472A1 (zh) 由用户设备执行的方法以及用户设备
US20230247401A1 (en) Communication method and apparatus
KR20220052750A (ko) 무선 통신 시스템에서 mbs 통신을 위한 방법 및 장치
WO2018019060A1 (zh) 一种下行数据传输方法及装置
US20230362959A1 (en) Method and system for managing configuration and control information of mbs services in wireless network
WO2022006875A1 (zh) 建立mbs业务的方法及装置、终端设备、网络设备
WO2020007086A1 (en) Method and terminal device for harq transmission
WO2020223878A1 (zh) 随机接入的方法、终端设备和网络设备
US20220353883A1 (en) Service conflict solution method, apparatus and device, and storage medium
CN114846824A (zh) 对设备的计数
WO2023066081A1 (zh) 非激活态多播业务发送、接收方法及装置
WO2021155547A1 (zh) 数据接收方法、装置、设备及存储介质
WO2017045177A1 (zh) 移动性管理的方法、用户设备和基站
WO2023133843A1 (zh) 一种确定配置信息的方法及装置、终端设备
WO2023165588A1 (zh) 多播业务接收方法及装置、存储介质、终端设备、网络设备
WO2022165843A1 (zh) 侧行传输方法和终端
WO2024066858A1 (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: 22882691

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022882691

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022882691

Country of ref document: EP

Effective date: 20240521