WO2023231030A1 - 业务处理方法、指示发送方法、装置、设备及存储介质 - Google Patents

业务处理方法、指示发送方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2023231030A1
WO2023231030A1 PCT/CN2022/097002 CN2022097002W WO2023231030A1 WO 2023231030 A1 WO2023231030 A1 WO 2023231030A1 CN 2022097002 W CN2022097002 W CN 2022097002W WO 2023231030 A1 WO2023231030 A1 WO 2023231030A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
terminal
inactive
inactive multicast
configuration
Prior art date
Application number
PCT/CN2022/097002
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 北京小米移动软件有限公司
Priority to PCT/CN2022/097002 priority Critical patent/WO2023231030A1/zh
Priority to CN202280001811.6A priority patent/CN117501721A/zh
Publication of WO2023231030A1 publication Critical patent/WO2023231030A1/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

Definitions

  • the present application relates to the field of mobile communications, and in particular to a business processing method, an instruction sending method, a device, a device and a storage medium.
  • the terminal In the mobile communication system, if the terminal enters the inactive state from the connected state, it needs to be ensured that the terminal can still receive the inactive multicast service.
  • the network device needs to send the configuration of the inactive state service to the terminal so that the terminal can receive the inactive multicast service. business. However, if the terminal moves out of the service cell covered by the network device, how to handle the inactive multicast service becomes an urgent problem that needs to be solved.
  • the embodiments of the present application provide a service processing method, an instruction sending method, a device, a device, and a storage medium.
  • the present application provides a solution for a terminal to process inactive multicast services, ensuring transmission reliability.
  • the technical solutions are as follows:
  • a service processing method is provided.
  • the method is executed by a terminal.
  • the method includes:
  • an indication sending method is provided, the method is executed by a network device, and the method includes:
  • a business processing device includes:
  • a processing module configured to release or suspend the configuration and/or radio bearer of the inactive multicast service in response to determining that the serving cell does not support the inactive multicast service.
  • an instruction sending device is provided, and the device includes:
  • a sending module configured to send a configuration instruction to the terminal, where the configuration instruction is used to instruct the terminal to release or suspend the configuration and/or radio bearer of the inactive multicast service.
  • a terminal includes: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions. Execute instructions to implement business processing methods as described above.
  • a network device includes: a processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and Executable instructions are executed to implement the instruction sending method as described above.
  • a computer-readable storage medium stores executable program code.
  • the executable program code is loaded and executed by a processor to implement the business processing method or instructions in the above aspect. Send method.
  • a chip is provided.
  • the chip includes programmable logic circuits and/or program instructions. When the chip is run on a terminal or network device, it is used to implement the business processing method or the instruction sending method as described above. .
  • a computer program product is provided.
  • the computer program product is executed by a processor of a terminal or a network device, it is used to implement the service processing method or the instruction sending method of the above aspect.
  • this application provides a solution for terminals to process inactive multicast services, ensuring transmission reliability.
  • Figure 1 shows a block diagram of a communication system provided by an exemplary embodiment of the present application
  • Figure 2 shows a flow chart of a business processing method provided by an exemplary embodiment of the present application
  • Figure 3 shows a flow chart of yet another business processing method provided by an exemplary embodiment of the present application
  • Figure 4 shows a flow chart of yet another business processing method provided by an exemplary embodiment of the present application
  • Figure 5 shows a block diagram of a service processing device provided by an exemplary embodiment of the present application
  • Figure 6 shows a block diagram of another service processing device provided by an exemplary embodiment of the present application.
  • Figure 7 shows a block diagram of an instruction sending device provided by an exemplary embodiment of the present application.
  • Figure 8 shows a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.
  • first, second, third, etc. may be used in this application to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • word “if” as used herein may be interpreted as "when” or “when” or “in response to determining.”
  • the information including but not limited to user equipment information, user personal information, etc.
  • data including but not limited to data used for analysis, stored data, displayed data, etc.
  • signals involved in this application All are authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.
  • Figure 1 shows a block diagram of a communication system provided by an exemplary embodiment of the present application.
  • the communication system may include: a terminal 10 and a network device 20.
  • the number of terminals 10 is usually multiple, and one or more terminals 10 can be distributed in the cell managed by each network device 20 .
  • the terminal 10 may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to wireless modems with wireless communication functions, as well as various forms of user equipment (User Equipment, UE), mobile stations ( Mobile Station, MS) and so on.
  • UE User Equipment
  • MS Mobile Station
  • the network device 20 is a device deployed in the access network to provide wireless communication functions for the terminal 10 .
  • the above-mentioned devices that provide wireless communication functions for the terminal 10 are collectively referred to as network equipment.
  • a connection can be established between the network device 20 and the terminal 10 through an air interface, so that communication, including signaling and data interaction, can be performed through the connection.
  • the number of network devices 20 may be multiple, and communication between two adjacent network devices 20 may also be carried out in a wired or wireless manner.
  • the terminal 10 can switch between different network devices 20 , that is, establish connections with different network devices 20 .
  • the network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc.
  • the names of devices with network device functions may be different.
  • 5G NR New Radio, New Radio
  • they are called gNodeB or gNB.
  • the name "network device” may change.
  • Figure 2 shows a flow chart of a service processing method provided by an exemplary embodiment of the present application.
  • the exemplary embodiment can be applied to the terminal and network equipment shown in Figure 1.
  • the method includes at least part of the following content:
  • Step 201 In response to determining that the serving cell does not support the inactive multicast service, the terminal releases or suspends the configuration and/or radio bearer of the inactive multicast service.
  • the serving cell refers to the cell currently accessed by the terminal. That is to say, the cell currently providing services to the terminal is the serving cell.
  • the inactive multicast service refers to the multicast service sent by the network device to the terminal when the terminal is in the inactive state.
  • the configuration and/or radio bearer of the inactive multicast service refers to the resource information used to transmit the inactive multicast service.
  • the inactive multicast service is MBMS (Multimedia Broadcast and Multicast Service, multimedia broadcast multicast service) or MBS (Multicast Broadcast Service, multicast broadcast service).
  • MBMS Multimedia Broadcast and Multicast Service, multimedia broadcast multicast service
  • MBS Multicast Broadcast Service, multicast broadcast service
  • MBS can be represented by an MBS service identifier.
  • the MBS service identifier is TMGI (Temporary Mobile Group Identity, temporary mobility group identifier), MBS Session ID (MBS session identifier) or MBS QoSflow ID (MBS service flow identifier).
  • release means that the terminal deletes its stored configuration of the inactive multicast service and/or the radio bearer.
  • Suspension means that the terminal does not use the configuration of the inactive multicast service and/or the radio bearer stored in it, but the configuration of the inactive multicast service and/or the radio bearer are still stored in the terminal.
  • the terminal in response to determining that the serving cell does not support the inactive multicast service, releases the configuration and/or radio bearer of the inactive multicast service.
  • the terminal in response to determining that the serving cell does not support the inactive multicast service, the terminal suspends the configuration and/or radio bearer of the inactive multicast service.
  • the terminal releases or suspends the configuration and/or wireless bearer of the inactive multicast service, including:
  • the terminal determines that the serving cell does not support the inactive multicast service, it means that the serving cell will not transmit the inactive multicast service in this case. For the terminal, the terminal cannot receive the inactive multicast service in the serving cell. multicast service, so the terminal can release or suspend the configuration and/or radio bearer of the inactive multicast service.
  • the radio bearer is MRB (MBS Radio Bearer, MBS Radio Bearer).
  • the inactive multicast service is an INACTIVE multicast service, which can be understood as a multicast service in which the terminal can still receive service data in an inactive state.
  • the terminal will also stop monitoring the PDCCH (Physical Downlink Control Channel) corresponding to the inactive multicast service. That is to say, after determining that the serving cell does not support the inactive multicast service, the terminal stops monitoring the PDCCH corresponding to the inactive multicast service to stop receiving the inactive multicast service.
  • PDCCH Physical Downlink Control Channel
  • this application provides a solution for terminals to process inactive multicast services, ensuring transmission reliability.
  • the embodiment of the present application takes the terminal releasing or suspending the configuration and/or radio bearer of the inactive multicast service as an example for explanation.
  • the network device configures the configuration of the inactive multicast service and/or the radio bearer for the terminal, so that the terminal can configure the inactive multicast service based on the configuration and/or the wireless bearer.
  • the wireless bearer receives the inactive multicast service sent by the serving cell.
  • the above embodiment is explained by taking the terminal to release or suspend the configuration and/or radio bearer of the inactive multicast service as an example.
  • the terminal restores the configuration and/or radio bearer of the inactive multicast service in response to determining that the serving cell supports the inactive multicast service.
  • the terminal after determining that the serving cell supports the inactive multicast service, the terminal automatically restores the configuration and/or radio bearer of the inactive multicast service.
  • the serving cell supports the inactive multicast service, it means that the inactive multicast service can be transmitted between the serving cell and the terminal.
  • the terminal has already configured the inactive multicast service and/or Or the radio bearer is released or suspended, so the network device can configure the terminal to restore the configuration of the inactive multicast service and/or the radio bearer.
  • the terminal can restore the configuration and/or radio bearer of the inactive multicast service, and then the inactive multicast can be transmitted between the terminal and the serving cell. business to ensure the reliability of business transmission.
  • the embodiment shown in Figure 2 illustrates that the terminal releases or suspends the configuration and/or radio bearer of the inactive multicast service. Specifically, the terminal can actively release or suspend the configuration and/or radio bearer of the inactive multicast service.
  • Figure 3 shows a flow chart of yet another business processing method provided by an exemplary embodiment of the present application. Referring to Figure 3, the method includes:
  • Step 301 In response to the fact that the serving cell does not support the inactive multicast service, the terminal directly releases or suspends the configuration and/or radio bearer of the inactive multicast service.
  • the terminal determines that the serving cell does not support the inactive multicast service, it means that the terminal will not receive the inactive multicast service sent by the serving cell, so the terminal directly releases or suspends the configuration of the inactive multicast service. And/or wireless bearer is enough.
  • the terminal in response to determining that the serving cell does not support the inactive multicast service and does not receive the configuration indication, releases or suspends the configuration and/or radio bearer of the inactive multicast service.
  • the terminal can directly release the configuration and/or radio bearer of the inactive multicast service or hang.
  • the inactive multicast service includes a preset type of inactive multicast service.
  • the preset type of inactive multicast service refers to the inactive multicast service that meets the requirements and is received by the terminal in the serving cell.
  • the preset type of inactive multicast service includes at least one of the following:
  • the inactive multicast service that the terminal is interested in refers to the inactive multicast service defined by the terminal itself.
  • the inactive multicast service that the terminal is interested in can also be understood as the inactive multicast service that the terminal needs to receive, and the terminal does not need to receive the inactive multicast service that the terminal does not need to receive.
  • the terminal itself configures the inactive multicast service that the terminal is interested in. It can also be understood that the inactive multicast service that the terminal is interested in is configured by the terminal itself.
  • the terminal is receiving inactive multicast services.
  • the inactive multicast service being received by the terminal refers to the inactive multicast service received by the terminal in a serving cell that supports the inactive multicast service.
  • the terminal switches the serving cell, the serving cell before the terminal switches the serving cell is the first serving cell, and the serving cell after the terminal switches the serving cell is the second serving cell, then the inactive group being received by the terminal
  • the multicast service is actually an inactive multicast service sent by the first serving cell, and the terminal determines that the second serving cell does not support the inactive multicast service.
  • the terminal is configured with correspondingly configured inactive multicast services.
  • the network device configures the inactive multicast service for the terminal, and the terminal can receive the inactive multicast service sent by the serving cell according to the inactive multicast service configured by the network device.
  • the embodiment of the present application takes as an example what type of inactive multicast services the inactive multicast services include.
  • the terminal can determine whether the serving cell supports the inactive multicast service, where the terminal's determination method includes any of the following situations:
  • the terminal will continue to receive the inactive multicast service sent by the serving cell. However, if the terminal cannot receive the inactive multicast service sent by the serving cell, it means that the serving cell fails to send the inactive multicast service to the terminal at this time. Activate the multicast service. At this time, the terminal can determine that the serving cell does not support the inactive multicast service.
  • the network device can configure the active area of the inactive multicast service for the terminal. That is to say, if the terminal is within the active area of the inactive multicast service, the terminal can receive the inactive multicast service sent by the serving cell, and if the terminal When it is not within the scope of the inactive multicast service, it means that the terminal cannot receive the inactive multicast service sent by the serving cell.
  • the terminal has determined that the current serving cell does not belong to the scope of the inactive multicast service. , so the serving cell does not support inactive multicast services, and the serving cell cannot send inactive multicast services to the terminal, and the terminal cannot receive inactive multicast services sent by the serving cell.
  • the network device configures the inactive multicast service for the terminal, and the terminal determines that the inactive multicast service supported by the serving cell is different from the inactive multicast service configured by the network device. This means that the terminal determines that the inactive multicast service supported by the serving cell is different.
  • the inactive multicast service does not belong to the inactive multicast service configured by the network device, and it is determined that the serving cell does not support the inactive multicast service.
  • the inactive multicast services configured by the network device for the terminal include inactive multicast service 1, inactive multicast service 2 and inactive multicast service 3, and the inactive multicast service supported by the serving cell determined by the terminal is inactive multicast service.
  • Activate multicast service 4 indicating that the inactive multicast service supported by the serving cell does not belong to the inactive multicast service configured by the network device, so the terminal determines that the serving cell does not support the inactive multicast service.
  • the terminal can determine that the serving cell does not support the inactive multicast service, so that the terminal can subsequently release or suspend the configuration and/or wireless bearer of the inactive multicast service, which not only improves the terminal's determination of service
  • the cell does not support the accuracy of non-activated multicast services, and saves terminal resources to ensure transmission reliability.
  • the terminal will also stop monitoring the PDCCH (Physical Downlink Control Channel) corresponding to the inactive multicast service. That is to say, after determining that the serving cell does not support the inactive multicast service, the terminal stops monitoring the PDCCH corresponding to the inactive multicast service to stop receiving the inactive multicast service.
  • PDCCH Physical Downlink Control Channel
  • the terminal can determine that the serving cell does not support the inactive multicast service and will stop monitoring the PDCCH corresponding to the inactive multicast service. This not only improves the accuracy of the terminal in determining that the serving cell does not support the inactive multicast service. It also saves terminal resources and ensures the reliability of transmission.
  • the embodiment shown in Figure 2 illustrates the configuration and/or radio bearer of a terminal releasing or suspending an inactive multicast service.
  • the terminal may release or suspend the configuration of the inactive multicast service and/or the radio bearer according to the configuration of the network device.
  • the terminal triggers an RRC (Radio Resource Control) connection
  • the network device returns a configuration instruction to the terminal based on the RRC connection to instruct the terminal to release or suspend the configuration of the inactive multicast service and/or the wireless carry.
  • RRC Radio Resource Control
  • the terminal triggers the RRC connection in response to determining that the serving cell does not support the inactive multicast service.
  • the terminal triggering the RRC connection includes multiple situations: the terminal triggers the RRC connection recovery, or the terminal triggers the RRC connection establishment, or the terminal can also trigger other processes, which are not limited in the embodiments of this application.
  • the inactive multicast service includes a preset type of inactive multicast service.
  • the preset type of inactive multicast service refers to the inactive multicast service that meets the requirements and is received by the terminal in the serving cell.
  • the preset type of inactive multicast service includes at least one of the following:
  • the inactive multicast service that the terminal is interested in refers to the inactive multicast service defined by the terminal itself.
  • the inactive multicast service that the terminal is interested in can also be understood as the inactive multicast service that the terminal needs to receive, and the terminal does not need to receive the inactive multicast service that the terminal does not need to receive.
  • the terminal itself configures the inactive multicast service that the terminal is interested in. It can also be understood that the inactive multicast service that the terminal is interested in is configured by the terminal itself.
  • the terminal is receiving inactive multicast services.
  • the inactive multicast service being received by the terminal refers to the inactive multicast service received by the terminal in a serving cell that supports the inactive multicast service.
  • the terminal switches the serving cell, the serving cell before the terminal switches the serving cell is the first serving cell, and the serving cell after the terminal switches the serving cell is the second serving cell, then the inactive group being received by the terminal
  • the multicast service is actually an inactive multicast service sent by the first serving cell, and the terminal determines that the second serving cell does not support the inactive multicast service.
  • the terminal is configured with correspondingly configured inactive multicast services.
  • the network device configures the inactive multicast service for the terminal, and the terminal can receive the inactive multicast service sent by the serving cell according to the inactive multicast service configured by the network device.
  • the embodiment of the present application takes as an example what type of inactive multicast services the inactive multicast services include.
  • the terminal can determine whether the serving cell supports the inactive multicast service, where the terminal's determination method includes any of the following situations:
  • the terminal will continue to receive the inactive multicast service sent by the serving cell. However, if the terminal cannot receive the inactive multicast service sent by the serving cell, it means that the serving cell fails to send the inactive multicast service to the terminal at this time. Activate the multicast service. At this time, the terminal can determine that the serving cell does not support the inactive multicast service.
  • the network device can configure the active area of the inactive multicast service for the terminal. That is to say, if the terminal is within the active area of the inactive multicast service, the terminal can receive the inactive multicast service sent by the serving cell, and if the terminal When it is not within the scope of the inactive multicast service, it means that the terminal cannot receive the inactive multicast service sent by the serving cell.
  • the terminal has determined that the current serving cell does not belong to the scope of the inactive multicast service. , so the serving cell does not support inactive multicast services, and the serving cell cannot send inactive multicast services to the terminal, and the terminal cannot receive inactive multicast services sent by the serving cell.
  • the network device configures the inactive multicast service for the terminal, and the terminal determines that the inactive multicast service supported by the serving cell is different from the inactive multicast service configured by the network device. This means that the terminal determines that the inactive multicast service supported by the serving cell is different.
  • the inactive multicast service does not belong to the inactive multicast service configured by the network device, and it is determined that the serving cell does not support the inactive multicast service.
  • the inactive multicast services configured by the network device for the terminal include inactive multicast service 1, inactive multicast service 2 and inactive multicast service 3, and the inactive multicast service supported by the serving cell determined by the terminal is inactive multicast service.
  • Activate multicast service 4 indicating that the inactive multicast service supported by the serving cell does not belong to the inactive multicast service configured by the network device, so the terminal determines that the serving cell does not support the inactive multicast service.
  • Figure 4 shows a flow chart of yet another business processing method provided by an exemplary embodiment of the present application. Referring to Figure 4, the method includes:
  • Step 401 The network device sends a configuration instruction to the terminal.
  • Step 402 The terminal receives a configuration instruction sent by the network device.
  • the configuration instruction is used to instruct the terminal to release or suspend the configuration and/or radio bearer of the inactive multicast service.
  • Step 403 In response to receiving the configuration indication, the terminal releases or suspends the configuration and/or radio bearer of the inactive multicast service.
  • the terminal triggers the RRC connection and sends request information to the network device.
  • the network device receives the request information, determines the configuration instruction based on the request information, and sends the configuration instruction to the terminal.
  • the terminal receives the configuration instruction sent by the network device, In response to receiving the configuration indication, release or suspend the configuration and/or radio bearer of the inactive multicast service.
  • the request information is an RRC request, used by the terminal to trigger RRC connection establishment or RRC connection recovery.
  • the RRC request is an RRC connection recovery request, an RRC connection establishment request, or other types of requests, which are not limited in the embodiments of this application.
  • the terminal triggers the RRC connection and sends request information to the network device, and then the network device configures the release in various ways:
  • the terminal sends an RRC request to the network device to trigger RRC connection establishment or RRC connection recovery through the RRC request.
  • the network device receives the RRC request sent by the terminal, sends an RRC request response to the terminal in response to the RRC request, and responds through the RRC request.
  • the included configuration instructions release the configuration and/or radio bearers of the inactive multicast service.
  • the RRC request response is any one of an RRC release message, an RRC recovery message, an RRC setup message, or an RRC reject message, or may also be other RRC messages, which are not limited in the embodiments of this application.
  • the terminal sends an RRC connection recovery request to the network device, triggering the RRC connection recovery.
  • the network device receives the RRC connection recovery request sent by the terminal, responds to the RRC connection recovery request and sends an RRC request response to the terminal, and uses the configuration included in the RRC request response. Indicates the release of the configuration and/or radio bearer of the inactive multicast service.
  • the terminal sends an RRC connection establishment request to the network device, triggering the RRC connection establishment.
  • the network device receives the RRC connection establishment request sent by the terminal, and sends an RRC request response to the terminal in response to the RRC connection establishment request.
  • the RRC request response includes The configuration instruction releases the configuration and/or radio bearer of the inactive multicast service.
  • the RRC request response is an RRC release message as an example.
  • the RRC release message includes identification information used to indicate the deactivation of the multicast service.
  • the RRC release message uses the included identification information to issue configuration instructions, and then indicates The terminal releases the configuration and/or radio bearer of the inactive multicast service.
  • the terminal Upon receiving the RRC release message, the terminal releases the configuration and/or radio bearer of the inactive multicast service.
  • the identification information of the inactive multicast service includes TMGI, MBS Session ID, MBS QoSflow ID or inactive multicast service configuration, or other types of identifiers, which are not limited in the embodiment of this application.
  • the embodiment of the present application takes as an example that the RRC release message contains identification information used to indicate the deactivation of the multicast service. In other embodiments, the RRC release message does not include identification information indicating the inactive multicast service. After receiving the RRC release message, the terminal releases the configuration and/or radio bearer of the inactive multicast service.
  • the RRC request response as an RRC release message as an example.
  • the RRC request response can also be replaced by an RRC recovery message, an RRC establishment message or an RRC reject message, which will not be described again here.
  • the terminal sends an RRC request to the network device for the terminal to trigger RRC connection establishment or RRC connection recovery.
  • the network device receives the RRC request sent by the terminal and configures the terminal to enter the connected state in response to the RRC request. After the terminal enters the connected state, In response to the terminal entering the connected state, the network device sends an RRC message to the terminal to instruct the terminal to release the configuration and/or radio bearer of the inactive multicast service.
  • the RRC message is any one of an RRC release message, an RRC reconfiguration message, or other RRC messages, which are not limited in the embodiments of this application.
  • the network device receives the RRC request sent by the terminal, and responds to the RRC request by sending an RRC recovery message or an RRC establishment message to the terminal to configure the terminal to enter the connected state, or the network device can also send other messages to configure the terminal to enter the connection state. state.
  • the terminal sends an RRC connection recovery request to the network device for the terminal to trigger RRC connection recovery.
  • the network device receives the RRC connection recovery request sent by the terminal, and configures the terminal to enter the connected state in response to the RRC connection recovery request. After the terminal enters the connected state In response to the terminal entering the connected state, the network device sends an RRC message to the terminal to instruct the terminal to release the configuration and/or radio bearer of the inactive multicast service.
  • the terminal sends an RRC connection establishment request to the network device for the terminal to trigger the RRC connection establishment.
  • the network device receives the RRC connection establishment request sent by the terminal, configures the terminal to enter the connected state in response to the RRC connection establishment request, and enters the connected state after the terminal Finally, in response to the terminal entering the connected state, the network device sends an RRC message to the terminal to instruct the terminal to release the configuration and/or radio bearer of the inactive multicast service.
  • the RRC message is an RRC release message as an example.
  • the RRC release message includes identification information used to indicate the inactivation of the multicast service.
  • the RRC release message uses the included identification information to issue configuration instructions, and then instructs the terminal. Release the configuration and/or radio bearer of the inactive multicast service.
  • the terminal Upon receiving the RRC release message, the terminal releases the configuration and/or radio bearer of the inactive multicast service.
  • the identification information of the inactive multicast service includes TMGI, MBS Session ID, MBS QoSflow ID or inactive multicast service configuration, or other types of identifiers, which are not limited in the embodiment of this application.
  • the embodiment of the present application takes as an example that the RRC release message contains identification information used to indicate an inactive multicast service. In other embodiments, the RRC release message does not include identification information indicating the inactive multicast service. After receiving the RRC release message, the terminal releases the configuration and/or radio bearer of the inactive multicast service.
  • the RRC message is an RRC reconfiguration message as an example.
  • the RRC reconfiguration message includes identification information used to indicate the inactive multicast service.
  • the RRC reconfiguration message delivers the configuration instructions through the included identification information.
  • the terminal is further instructed to release the configuration and/or radio bearer of the inactive multicast service.
  • the terminal Upon receiving the RRC reconfiguration message, the terminal releases the configuration and/or radio bearer of the inactive multicast service.
  • the identification information of the inactive multicast service includes TMGI, MBS Session ID, MBS QoSflow ID or inactive multicast service configuration, or other types of identifiers, which are not limited in the embodiment of this application.
  • the embodiment of the present application takes as an example that the RRC reconfiguration message contains identification information used to indicate the inactivation of the multicast service. In other embodiments, the RRC reconfiguration message does not include identification information indicating the inactive multicast service. After receiving the RRC reconfiguration message, the terminal releases the configuration and/or radio bearer of the inactive multicast service. .
  • the terminal triggers the RRC connection and sends request information to the network device, and then the network device configures the suspension in various ways:
  • the terminal sends an RRC request to the network device to trigger RRC connection establishment or RRC connection recovery through the RRC request.
  • the network device receives the RRC request sent by the terminal, sends an RRC request response to the terminal in response to the RRC request, and responds through the RRC request.
  • Included configuration indicates the configuration of suspended inactive multicast services and/or radio bearers.
  • the RRC request response is any one of an RRC release message, an RRC recovery message, an RRC setup message, or an RRC reject message, or may also be other RRC messages, which are not limited in the embodiments of this application.
  • the terminal sends an RRC connection recovery request to the network device, triggering the RRC connection recovery.
  • the network device receives the RRC connection recovery request sent by the terminal, responds to the RRC connection recovery request and sends an RRC request response to the terminal, and uses the configuration included in the RRC request response. Indicates the suspension of configuration and/or radio bearers of inactive multicast services.
  • the terminal sends an RRC connection establishment request to the network device, triggering the RRC connection establishment.
  • the network device receives the RRC connection establishment request sent by the terminal, and sends an RRC request response to the terminal in response to the RRC connection establishment request.
  • the RRC request response includes The configuration indicates the suspension of the configuration and/or radio bearer of the inactive multicast service.
  • the RRC request response is an RRC release message as an example.
  • the RRC release message contains a suspension indication and identification information used to indicate the inactive multicast service, and is used to instruct the terminal to suspend the configuration and configuration of the inactive multicast service. /or wireless bearer, and after receiving the RRC release message, the terminal suspends the configuration of the inactive multicast service and/or the wireless bearer.
  • the identification information of the inactive multicast service includes TMGI, MBS Session ID, MBS QoSflow ID or inactive multicast service configuration, or other types of identifiers, which are not limited in the embodiment of this application.
  • the embodiment of the present application takes as an example that the RRC release message contains identification information used to indicate an inactive multicast service.
  • the RRC release message does not contain the identification information used to indicate the inactive multicast service, but contains a suspension indication used to instruct the terminal to suspend the configuration and/or radio bearer of the inactive multicast service. , after receiving the RRC release message, the terminal suspends the configuration and/or radio bearer of the inactive multicast service.
  • the RRC request response as an RRC release message as an example.
  • the RRC request response may also be replaced by an RRC recovery message, an RRC establishment message or an RRC reject message.
  • the terminal sends an RRC request to the network device for the terminal to trigger RRC connection establishment or RRC connection recovery.
  • the network device receives the RRC request sent by the terminal and configures the terminal to enter the connected state in response to the RRC request. After the terminal enters the connected state, In response to the terminal entering the connected state, the network device sends an RRC message to the terminal to instruct the terminal to suspend the configuration of the inactive multicast service and/or the radio bearer.
  • the RRC message is any one of an RRC release message, an RRC reconfiguration message, or other RRC messages, which are not limited in the embodiments of this application.
  • the network device receives the RRC request sent by the terminal, and responds to the RRC request by sending an RRC recovery message or an RRC establishment message to the terminal to configure the terminal to enter the connected state, or the network device can also send other messages to configure the terminal to enter the connection state. state.
  • the terminal sends an RRC connection recovery request to the network device for the terminal to trigger RRC connection recovery.
  • the network device receives the RRC connection recovery request sent by the terminal, and configures the terminal to enter the connected state in response to the RRC connection recovery request. After the terminal enters the connected state In response to the terminal entering the connected state, the network device sends an RRC message to the terminal to instruct the terminal to suspend the configuration of the inactive multicast service and/or the radio bearer.
  • the terminal sends an RRC connection establishment request to the network device for the terminal to trigger the RRC connection establishment.
  • the network device receives the RRC connection establishment request sent by the terminal, configures the terminal to enter the connected state in response to the RRC connection establishment request, and enters the connected state after the terminal Finally, in response to the terminal entering the connected state, the network device sends an RRC message to the terminal to instruct the terminal to suspend the configuration and/or radio bearer of the inactive multicast service.
  • the RRC message is an RRC release message as an example.
  • the RRC release message contains a suspension indication and identification information used to indicate the inactive multicast service, and is used to instruct the terminal to suspend the configuration and/or the inactive multicast service. or wireless bearer, and after receiving the RRC release message, the terminal suspends the configuration of the inactive multicast service and/or the wireless bearer.
  • the identification information of the inactive multicast service includes TMGI, MBS Session ID, MBS QoSflow ID or inactive multicast service configuration, or other types of identifiers, which are not limited in the embodiment of this application.
  • the embodiment of the present application takes as an example that the RRC release message contains identification information used to indicate an inactive multicast service.
  • the RRC release message does not contain the identification information used to indicate the inactive multicast service, but contains a suspension indication used to instruct the terminal to suspend the configuration and/or radio bearer of the inactive multicast service. , after receiving the RRC release message, the terminal suspends the configuration and/or radio bearer of the inactive multicast service.
  • the RRC message is explained by taking the RRC message as an RRC release message as an example.
  • the RRC message may also be replaced by an RRC reconfiguration message, which will not be described again here.
  • the terminal triggers the RRC connection to release or suspend the configuration and/or wireless bearer of the inactive multicast service by the network device configuration, which provides a solution for the terminal to process the inactive multicast service. , ensuring the reliability of transmission.
  • the terminal will also stop monitoring the PDCCH (Physical Downlink Control Channel) corresponding to the inactive multicast service. That is to say, after determining that the serving cell does not support the inactive multicast service, the terminal stops monitoring the PDCCH corresponding to the inactive multicast service to stop receiving the inactive multicast service.
  • PDCCH Physical Downlink Control Channel
  • the terminal can determine that the serving cell does not support the inactive multicast service and will stop monitoring the PDCCH corresponding to the inactive multicast service. This not only improves the accuracy of the terminal in determining that the serving cell does not support the inactive multicast service. It also saves terminal resources and ensures the reliability of transmission.
  • Figure 5 shows a block diagram of a service processing device provided by an exemplary embodiment of the present application.
  • the device includes:
  • the processing module 501 is configured to release or suspend the configuration and/or radio bearer of the inactive multicast service in response to determining that the serving cell does not support the inactive multicast service.
  • the processing module 501 is also configured to directly release or suspend the configuration and/or radio bearer of the inactive multicast service in response to determining that the serving cell does not support the inactive multicast service. A step of.
  • the processing module 501 is also configured to trigger the establishment of an RRC connection in response to determining that the serving cell does not support the inactive multicast service.
  • the device further includes:
  • the receiving module 502 is configured to receive a configuration instruction sent by the network device, where the configuration instruction is used to instruct the terminal to perform the release or suspension of the configuration and/or wireless bearer of the inactive multicast service;
  • the processing module 501 is also configured to release or suspend the configuration and/or radio bearer of the inactive multicast service in response to receiving the configuration indication.
  • the inactive multicast service includes a preset type of inactive multicast service.
  • the device further includes: a determining module 503, the determining module 303 is used to:
  • the serving cell When it is determined that the serving cell does not belong to the action area of the inactive multicast service, it is determined that the serving cell does not support the inactive multicast service; or,
  • the serving cell When it is determined that the inactive multicast service supported by the serving cell does not belong to the inactive multicast service configured by the network device, it is determined that the serving cell does not support the inactive multicast service.
  • the device further includes:
  • Restoration module 504 configured to restore the configuration and/or radio bearer of the inactive multicast service in response to determining that the serving cell supports the inactive multicast service.
  • Figure 7 shows a block diagram of an instruction sending device provided by an exemplary embodiment of the present application.
  • the device includes:
  • the sending module 701 is configured to send a configuration instruction to the terminal, where the configuration instruction is used to instruct the terminal to release or suspend the configuration and/or radio bearer of the inactive multicast service.
  • the inactive multicast service includes a preset type of inactive multicast service.
  • Figure 8 shows a schematic structural diagram of a communication device provided by an exemplary embodiment of the present application.
  • the communication device includes: a processor 801, a receiver 802, a transmitter 803, a memory 804 and a bus 805.
  • the processor 801 includes one or more processing cores.
  • the processor 801 executes various functional applications and information processing by running software programs and modules.
  • the receiver 802 and the transmitter 803 can be implemented as a communication component, and the communication component can be a communication chip.
  • Memory 804 is connected to processor 801 through bus 805.
  • the memory 804 can be used to store at least one program code, and the processor 801 is used to execute the at least one program code to implement each step in the above method embodiment.
  • Memory 1004 may be implemented by any type of volatile or non-volatile storage device, or combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Static Read-Only Memory (SRAM), Read-Only Memory (ROM), Magnetic Memory, Flash Memory, Programmable Read-Only Memory (PROM).
  • EEPROM electrically erasable programmable read-only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • SRAM Static Read-Only Memory
  • ROM Read-Only Memory
  • Magnetic Memory Flash Memory
  • PROM Programmable Read-Only Memory
  • a computer-readable storage medium is also provided, with executable program code stored in the readable storage medium, and the executable program code is loaded and executed by the processor to implement each of the above methods.
  • the service processing method or instruction sending method performed by the communication device provided by the example.
  • a chip is provided.
  • the chip includes programmable logic circuits and/or program instructions.
  • a computer program product is provided.
  • the computer program product is executed by a processor of a terminal or a network device, it is used to implement the service processing method or the instruction sending method provided by each of the above method embodiments.

Landscapes

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

Abstract

本申请公开了一种业务处理方法、指示发送方法、装置、设备及存储介质，涉及移动通信领域。该方法包括：终端响应于确定服务小区不支持非激活组播业务，释放或挂起所述非激活组播业务的配置和/或无线承载（201），若终端确定服务小区不支持非激活组播业务，则说明网络设备无法传输非激活组播业务，则终端释放或挂起非激活组播业务的配置/或无线承载，本申请提供了一种终端处理非激活组播业务的方案，保证了传输的可靠性。

Description

业务处理方法、指示发送方法、装置、设备及存储介质 技术领域
本申请涉及移动通信领域，特别涉及一种业务处理方法、指示发送方法、装置、设备及存储介质。
背景技术
在移动通信系统中，若终端由连接态进入非激活态，需要保证终端仍可以接收非激活组播业务，则网络设备需要向终端发送非激活态业务的配置，以便于终端接收非激活组播业务。但是，若终端移出该网络设备所覆盖的服务小区时，如何处理非激活组播业务成为亟需解决的问题。
发明内容
本申请实施例提供了一种业务处理方法、指示发送方法、装置、设备及存储介质，本申请提供了一种终端处理非激活组播业务的方案，保证了传输的可靠性。所述技术方案如下：
根据本申请的一个方面，提供了一种业务处理方法，所述方法由终端执行，所述方法包括：
响应于确定服务小区不支持非激活组播业务，释放或挂起所述非激活组播业务的配置和/或无线承载。
根据本申请的一个方面，提供了一种指示发送方法，所述方法由网络设备执行，所述方法包括：
向终端发送配置指示，所述配置指示用于指示所述终端执行释放或挂起非激活组播业务的配置和/或无线承载。
根据本申请的一个方面，提供了一种业务处理装置，所述装置包括：
处理模块，用于响应于确定服务小区不支持非激活组播业务，释放或挂起所述非激活组播业务的配置和/或无线承载。
根据本申请的一个方面，提供了一种指示发送装置，所述装置包括：
发送模块，用于向终端发送配置指示，所述配置指示用于指示所述终端执 行释放或挂起非激活组播业务的配置和/或无线承载。
根据本申请的一个方面，提供了一种终端，终端包括：处理器；与处理器相连的收发器；用于存储处理器的可执行指令的存储器；其中，处理器被配置为加载并执行可执行指令以实现如上述方面的业务处理方法。
根据本申请的一个方面，提供了一种网络设备，网络设备包括：处理器；与处理器相连的收发器；用于存储处理器的可执行指令的存储器；其中，处理器被配置为加载并执行可执行指令以实现如上述方面的指示发送方法。
根据本申请的一个方面，提供了一种计算机可读存储介质，可读存储介质中存储有可执行程序代码，可执行程序代码由处理器加载并执行以实现如上述方面的业务处理方法或指示发送方法。
根据本申请的一个方面，提供了一种芯片，芯片包括可编程逻辑电路和/或程序指令，当芯片在终端或网络设备上运行时，用于实现如上述方面的业务处理方法或指示发送方法。
根据本申请的一个方面，提供了一种计算机程序产品，当计算机程序产品被终端或网络设备的处理器执行时，其用于实现上述方面的业务处理方法或指示发送方法。
本申请实施例提供的业务处理方案中，若终端确定服务小区不支持非激活组播业务，则说明网络设备无法传输非激活组播业务，则终端释放或挂起非激活组播业务的配置和/或无线承载，本申请提供了一种终端处理非激活组播业务的方案，保证了传输的可靠性。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出了本申请一个示例性实施例提供的通信系统的框图；
图2示出了本申请一个示例性实施例提供的业务处理方法的流程图；
图3示出了本申请一个示例性实施例提供的又一种业务处理方法的流程图；
图4示出了本申请一个示例性实施例提供的再一种业务处理方法的流程图；
图5示出了本申请一个示例性实施例提供的一种业务处理装置的框图；
图6示出了本申请一个示例性实施例提供的另一种业务处理装置的框图；
图7示出了本申请一个示例性实施例提供的一种指示发送装置的框图；
图8示出了本申请一个示例性实施例提供的通信设备的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
在本申请使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。在本申请和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也是旨在包括多数形式，除非上下文清楚地表示其它含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本申请可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本申请范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，例如，在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
需要说明的是，本申请所涉及的信息(包括但不限于用户设备信息、用户个人信息等)、数据(包括但不限于用于分析的数据、存储的数据、展示的数据等)以及信号，均为经用户授权或者经过各方充分授权的，且相关数据的收集、使用和处理需要遵守相关国家和地区的相关法律法规和标准。
下面，对本申请的应用场景进行说明：
图1示出了本申请一个示例性实施例提供的通信系统的框图，该通信系统可以包括：终端10和网络设备20。
终端10的数量通常为多个，每一个网络设备20所管理的小区内可以分布一个或多个终端10。终端10可以包括各种具有无线通信功能的手持设备、车载 设备、可穿戴设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(User Equipment，UE)、移动台(Mobile Station，MS)等等。为方便描述，本申请实施例中，上面提到的设备统称为终端。
网络设备20是一种部署在接入网中用以为终端10提供无线通信功能的装置。为方便描述，本申请实施例中，上述为终端10提供无线通信功能的装置统称为网络设备。网络设备20与终端10之间可以通过空口建立连接，从而通过该连接进行通信，包括信令和数据的交互。网络设备20的数量可以有多个，两个邻近的网络设备20之间也可以通过有线或者无线的方式进行通信。终端10可以在不同的网络设备20之间进行切换，也即与不同的网络设备20建立连接。
该网络设备20可以包括各种形式的宏基站，微基站，中继站，接入点等等。在采用不同的无线接入技术的系统中，具备网络设备功能的设备的名称可能会有所不同，例如在5G NR(New Radio，新空口)系统中，称为gNodeB或者gNB。随着通信技术的演进，“网络设备”这一名称可能会变化。
图2示出了本申请一个示例性实施例提供的业务处理方法的流程图，示例性的可以应用于如图1所示的终端和网络设备中，该方法包括以下内容中的至少部分内容：
步骤201：终端响应于确定服务小区不支持非激活组播业务，释放或挂起非激活组播业务的配置和/或无线承载。
其中，服务小区是指终端当前接入的小区。也就是说，当前为终端提供服务的小区为服务小区。非激活组播业务是指终端在处于非激活态时网络设备向终端发送的组播业务。非激活组播业务的配置和/或无线承载是指用于传输非激活组播业务的资源信息。
在一些实施例中，非激活组播业务为MBMS(Multimedia Broadcast and Multicast Service，多媒体广播多播业务)或MBS(Multicast Broadcast Service，多播广播业务)。
可选地，MBS可以采用MBS业务标识表示。例如，该MBS业务标识为TMGI(Temporary Mobile Group Identity，临时移动组标识)、MBS Session ID(MBS会话标识)或者MBS QoSflow ID(MBS业务流标识)。
另外，释放是指终端将自身所存储的非激活组播业务的配置和/或无线承载删除。挂起是指终端不采用自身所存储的非激活组播业务的配置和/或无线承载， 但是非激活组播业务的配置和/或无线承载仍存储在终端中。
在本申请实施例中，终端响应于确定服务小区不支持非激活组播业务，释放非激活组播业务的配置和/或无线承载。或者，终端响应于确定服务小区不支持非激活组播业务，挂起非激活组播业务的配置和/或无线承载。
另外，本申请实施例中终端释放或挂起非激活组播业务的配置和/或无线承载，包括：
(1)释放或挂起非激活组播业务的配置。
(2)释放或挂起非激活组播业务的无线承载。
(3)释放或挂起非激活组播业务的配置和无线承载。
在本申请实施例中，若终端确定服务小区不支持非激活组播业务，说明在此情况下服务小区不会传输非激活组播业务，对于终端来说，终端在服务小区内无法接收非激活组播业务，因此终端可以释放或挂起非激活组播业务的配置和/或无线承载。
在一些实施例中，该无线承载为MRB(MBS Radio Bearer，MBS无线承载)。
在一些实施例中，非激活组播业务为INACTIVE(非激活)组播业务，可以理解为终端在非激活态下仍能够执行业务数据接收的组播业务。
需要说明的是，本申请实施例中终端还会停止监听非激活组播业务对应的PDCCH(Physical Downlink Control Channel，物理下行控制信道)。也就是说，终端确定服务小区不支持非激活组播业务后，停止监听该非激活组播业务对应的PDCCH，以停止接收该非激活组播业务。
本申请实施例提供的方案中，若终端确定服务小区不支持非激活组播业务，则说明网络设备无法传输非激活组播业务，则终端释放或挂起非激活组播业务的配置和/或无线承载，本申请提供了一种终端处理非激活组播业务的方案，保证了传输的可靠性。
需要说明的是，本申请实施例是以终端释放或挂起非激活组播业务的配置和/或无线承载为例进行说明。而在另一实施例中，终端在进入非激活态后，网络设备为终端配置非激活组播业务的配置和/或无线承载，以便于终端基于已配置的非激活组播业务的配置和/或无线承载接收服务小区发送的非激活组播业务。
另外，上述实施例是以终端释放或挂起非激活组播业务的配置和/或无线承载为例进行说明。而在另一实施例中，若服务小区重新支持非激活组播业务，则终端响应于确定服务小区支持非激活组播业务，恢复非激活组播业务的配置 和/或无线承载。
在一些实施例中，终端确定服务小区支持非激活组播业务后，自行恢复非激活组播业务的配置和/或无线承载。
在一些实施例中，若服务小区支持非激活组播业务，则说明服务小区与终端之间可以传输非激活组播业务，而对于终端来说，终端已经将非激活组播业务的配置和/或无线承载释放或挂起，因此网络设备可以为终端配置以恢复非激活组播业务的配置和/或无线承载。
本申请实施例提供的方案中，若服务小区重新支持非激活组播业务，则终端可以恢复非激活组播业务的配置和/或无线承载，进而终端与服务小区之间可以传输非激活组播业务，保证业务传输的可靠性。
图2所示实施例对终端释放或挂起非激活组播业务的配置和/或无线承载进行说明，具体的，终端可以主动释放或挂起非激活组播业务的配置和/或无线承载。
图3示出了本申请一个示例性实施例提供的又一种业务处理方法的流程图，参见图3，该方法包括：
步骤301：终端响应于服务小区不支持非激活组播业务，直接释放或挂起非激活组播业务的配置和/或无线承载。
在本申请实施例中，若终端确定服务小区不支持非激活组播业务，则说明终端不会接收服务小区发送的非激活组播业务，因此终端直接释放或挂起非激活组播业务的配置和/或无线承载即可。
可选地，终端响应于确定服务小区不支持非激活组播业务，且未接收到配置指示，释放或挂起非激活组播业务的配置和/或无线承载。
在本申请实施例中，若终端确定服务小区不支持非激活组播业务，并且终端也没有接收到配置指示，则此时终端可以直接将非激活组播业务的配置和/或无线承载释放或挂起。
在一些实施例中，非激活组播业务包括预设类型的非激活组播业务。
其中，该预设类型的非激活组播业务是指终端在服务小区所接收的符合要求的非激活组播业务。
可选地，该预设类型的非激活组播业务包括以下至少一项：
(1)终端感兴趣的非激活组播业务。
其中，终端感兴趣的非激活组播业务是指终端自身所定义的非激活组播业务。或者，终端感兴趣的非激活组播业务也可以理解为终端需要接收的非激活组播业务，而对于终端不需要接收的非激活组播业务，终端无需接收。
在一些实施例中，终端自身配置感兴趣的非激活组播业务，也可以理解为终端感兴趣的非激活组播业务由终端自行配置。
(2)终端正在接收的非激活组播业务。
其中，终端正在接收的非激活组播业务是指终端在支持非激活组播业务的服务小区接收的非激活组播业务。
在一些实施例中，终端存在切换服务小区的情况，终端切换服务小区前的服务小区为第一服务小区，终端切换服务小区后的服务小区为第二服务小区，则终端正在接收的非激活组播业务实际上是第一服务小区发送的非激活组播业务，而终端确定的为第二服务小区不支持非激活组播业务。
(3)终端配置有对应配置的非激活组播业务。
其中，网络设备为终端配置非激活组播业务，则终端可以根据网络设备配置的非激活组播业务接收服务小区发送的非激活组播业务。
需要说明的是，本申请实施例是以非激活组播业务包括何种类型的非激活组播业务为例进行说明。在另一实施例中，终端可以确定服务小区是否支持非激活组播业务，其中终端的确定方式包括以下任一种情况：
(1)在无法接收所述非激活组播业务的情况下，确定所述服务小区不支持所述非激活组播业务。
在本申请实施例中，终端会持续接收服务小区发送的非激活组播业务，但是，若终端无法接收到服务小区发送的非激活组播业务，则说明此时服务小区未能向终端发送非激活组播业务，此时终端即可确定服务小区不支持非激活组播业务。
(2)在确定所述服务小区不属于所述非激活组播业务的作用区域的情况下，确定所述服务小区不支持所述非激活组播业务。
其中，网络设备可以为终端配置非激活组播业务的作用区域，也就是说若终端在非激活组播业务的作用区域内时，终端可以接收服务小区发送的非激活组播业务，而若终端未位于非激活组播业务的作用区域内时，说明终端无法接收服务小区发送的非激活组播业务，另外，也可以理解为终端确定了当前的服务小区不属于非激活组播业务的作用区域，因此服务小区不支持非激活组播业 务，该服务小区也无法向终端发送非激活组播业务，终端也就无法接收服务小区发送的非激活组播业务。
(3)在确定所述服务小区支持的所述非激活组播业务不属于所述网络设备配置的非激活组播业务的情况下，确定所述服务小区不支持所述非激活组播业务。
在本申请实施例中，网络设备为终端配置非激活组播业务，并且终端确定服务小区支持的非激活组播业务与网络设备配置的非激活组播业务不同，则说明终端确定服务小区支持的所述非激活组播业务不属于所述网络设备配置的非激活组播业务，确定所述服务小区不支持所述非激活组播业务。
例如，网络设备为终端配置的非激活组播业务包括非激活组播业务1、非激活组播业务2和非激活组播业务3，而终端确定的服务小区支持的非激活组播业务为非激活组播业务4，说明服务小区支持的非激活组播业务不属于网络设备配置的非激活组播业务，因此终端确定服务小区不支持非激活组播业务。
本申请实施例提供的方案中，终端可以确定服务小区不支持非激活组播业务，以便于终端执行后续释放或挂起非激活组播业务的配置和/或无线承载，不仅提高了终端确定服务小区不支持非激活组播业务的准确性，而且节省终端资源，保证了传输的可靠性。
需要说明的是，本申请实施例中终端还会停止监听非激活组播业务对应的PDCCH(Physical Downlink Control Channel，物理下行控制信道)。也就是说，终端确定服务小区不支持非激活组播业务后，停止监听该非激活组播业务对应的PDCCH，以停止接收该非激活组播业务。
本申请实施例提供的方案中，终端可以确定服务小区不支持非激活组播业务，会停止监听非激活组播业务对应的PDCCH，不仅提高了终端确定服务小区不支持非激活组播业务的准确性，而且节省终端资源，保证了传输的可靠性。
图2所示实施例对终端释放或挂起非激活组播业务的配置和/或无线承载进行说明。具体的，终端可以根据网络设备的配置来释放或挂起非激活组播业务的配置和/或无线承载。
在一些实施例中，终端触发RRC(Radio Resource Control，无线资源控制)连接，进而网络设备基于RRC连接向终端返回配置指示，以指示终端释放或挂起非激活组播业务的配置和/或无线承载。
在一些实施例中，终端响应于确定服务小区不支持非激活组播业务，触发RRC连接。
其中，终端触发RRC连接包括多种情况：终端触发RRC连接恢复，或者，终端触发RRC连接建立，或者，终端还可以触发其他流程，本申请实施例不作限定。
在一些实施例中，非激活组播业务包括预设类型的非激活组播业务。
其中，该预设类型的非激活组播业务是指终端在服务小区所接收的符合要求的非激活组播业务。
可选地，该预设类型的非激活组播业务包括以下至少一项：
(1)终端感兴趣的非激活组播业务。
其中，终端感兴趣的非激活组播业务是指终端自身所定义的非激活组播业务。或者，终端感兴趣的非激活组播业务也可以理解为终端需要接收的非激活组播业务，而对于终端不需要接收的非激活组播业务，终端无需接收。
在一些实施例中，终端自身配置感兴趣的非激活组播业务，也可以理解为终端感兴趣的非激活组播业务由终端自行配置。
(2)终端正在接收的非激活组播业务。
其中，终端正在接收的非激活组播业务是指终端在支持非激活组播业务的服务小区接收的非激活组播业务。
在一些实施例中，终端存在切换服务小区的情况，终端切换服务小区前的服务小区为第一服务小区，终端切换服务小区后的服务小区为第二服务小区，则终端正在接收的非激活组播业务实际上是第一服务小区发送的非激活组播业务，而终端确定的为第二服务小区不支持非激活组播业务。
(3)终端配置有对应配置的非激活组播业务。
其中，网络设备为终端配置非激活组播业务，则终端可以根据网络设备配置的非激活组播业务接收服务小区发送的非激活组播业务。
需要说明的是，本申请实施例是以非激活组播业务包括何种类型的非激活组播业务为例进行说明。在另一实施例中，终端可以确定服务小区是否支持非激活组播业务，其中终端的确定方式包括以下任一种情况：
(1)在无法接收所述非激活组播业务的情况下，确定所述服务小区不支持所述非激活组播业务。
在本申请实施例中，终端会持续接收服务小区发送的非激活组播业务，但 是，若终端无法接收到服务小区发送的非激活组播业务，则说明此时服务小区未能向终端发送非激活组播业务，此时终端即可确定服务小区不支持非激活组播业务。
(2)在确定所述服务小区不属于所述非激活组播业务的作用区域的情况下，确定所述服务小区不支持所述非激活组播业务。
其中，网络设备可以为终端配置非激活组播业务的作用区域，也就是说若终端在非激活组播业务的作用区域内时，终端可以接收服务小区发送的非激活组播业务，而若终端未位于非激活组播业务的作用区域内时，说明终端无法接收服务小区发送的非激活组播业务，另外，也可以理解为终端确定了当前的服务小区不属于非激活组播业务的作用区域，因此服务小区不支持非激活组播业务，该服务小区也无法向终端发送非激活组播业务，终端也就无法接收服务小区发送的非激活组播业务。
(3)在确定所述服务小区支持的所述非激活组播业务不属于所述网络设备配置的非激活组播业务的情况下，确定所述服务小区不支持所述非激活组播业务。
在本申请实施例中，网络设备为终端配置非激活组播业务，并且终端确定服务小区支持的非激活组播业务与网络设备配置的非激活组播业务不同，则说明终端确定服务小区支持的所述非激活组播业务不属于所述网络设备配置的非激活组播业务，确定所述服务小区不支持所述非激活组播业务。
例如，网络设备为终端配置的非激活组播业务包括非激活组播业务1、非激活组播业务2和非激活组播业务3，而终端确定的服务小区支持的非激活组播业务为非激活组播业务4，说明服务小区支持的非激活组播业务不属于网络设备配置的非激活组播业务，因此终端确定服务小区不支持非激活组播业务。
图4示出了本申请一个示例性实施例提供的再一种业务处理方法的流程图，参见图4，该方法包括：
步骤401：网络设备向终端发送配置指示。
步骤402：终端接收网络设备发送的配置指示，该配置指示用于指示终端执行释放或挂起非激活组播业务的配置和/或无线承载。
步骤403：终端响应于接收到配置指示，释放或挂起非激活组播业务的配置和/或无线承载。
在一些实施例中，终端触发RRC连接，向网络设备发送请求信息，网络设 备接收到该请求信息，基于该请求信息确定配置指示，向终端发送配置指示，终端接收到网络设备发送的配置指示，响应于接收到配置指示，释放或挂起非激活组播业务的配置和/或无线承载。
可选地，该请求信息为RRC请求，用于终端触发RRC连接建立或RRC连接恢复。例如，该RRC请求为RRC连接恢复请求、RRC连接建立请求或者其他类型的请求，本申请实施例不作限定。
可选地，终端触发RRC连接，向网络设备发送请求信息，进而由网络设备配置释放的方式包括多种：
(1)终端向网络设备发送RRC请求，以通过该RRC请求触发RRC连接建立或RRC连接恢复，网络设备接收终端发送的RRC请求，响应于该RRC请求向终端发送RRC请求响应，通过RRC请求响应包括的配置指示释放非激活组播业务的配置和/或无线承载。
在一些实施例中，该RRC请求响应为RRC释放消息、RRC恢复消息、RRC建立消息或者RRC拒绝消息中的任一种，或者还可以为其他RRC消息，本申请实施例不作限定。
例如，该终端向网络设备发送RRC连接恢复请求，触发RRC连接恢复，网络设备接收终端发送的RRC连接恢复请求，响应于该RRC连接恢复请求向终端发送RRC请求响应，通过RRC请求响应包括的配置指示释放非激活组播业务的配置和/或无线承载。
又例如，该终端向网络设备发送RRC连接建立请求，触发RRC连接建立，网络设备接收终端发送的RRC连接建立请求，响应于该RRC连接建立请求向终端发送RRC请求响应，通过RRC请求响应包括的配置指示释放非激活组播业务的配置和/或无线承载。
下面，以RRC请求响应为RRC释放消息为例进行说明，该RRC释放消息中包括用于指示非激活组播业务的标识信息，则RRC释放消息通过包括的标识信息来下发配置指示，进而指示终端释放非激活组播业务的配置和/或无线承载，终端接收到该RRC释放消息，释放非激活组播业务的配置和/或无线承载。
其中，该非激活组播业务的标识信息包括TMGI、MBS Session ID、MBS QoSflow ID或者非激活组播业务配置，或者其他类型的标识，本申请实施例不作限定。
需要说明的是，本申请实施例是以RRC释放消息中包含用于指示非激活组 播业务的标识信息为例进行说明。而在另一些实施例中，RRC释放消息中不包含用于指示非激活组播业务的标识信息，终端接收到该RRC释放消息后，释放非激活组播业务的配置和/或无线承载。
本申请实施例是以RRC请求响应为RRC释放消息为例进行说明。而在另一些实施例中，该RRC请求响应还可以替换为RRC恢复消息、RRC建立消息或者RRC拒绝消息，在此不再赘述。
(2)终端向网络设备发送RRC请求，用于终端触发RRC连接建立或RRC连接恢复，网络设备接收终端发送的RRC请求，响应于该RRC请求配置终端进入连接态，在终端进入连接态后，网络设备响应于终端进入连接态，向终端发送RRC消息指示终端释放非激活组播业务的配置和/或无线承载。
在一些实施例中，该RRC消息为RRC释放消息、RRC重配置消息中的任一种，或者还可以为其他RRC消息，本申请实施例不作限定。
在一些实施例中，网络设备接收终端发送的RRC请求，响应于该RRC请求向终端发送RRC恢复消息或RRC建立消息以配置终端进入连接态，或者网络设备还可以发送其他消息以配置终端进入连接态。
例如，终端向网络设备发送RRC连接恢复请求，用于终端触发RRC连接恢复，网络设备接收终端发送的RRC连接恢复请求，响应于该RRC连接恢复请求配置终端进入连接态，在终端进入连接态后，网络设备响应于终端进入连接态，向终端发送RRC消息指示终端释放非激活组播业务的配置和/或无线承载。
又例如，终端向网络设备发送RRC连接建立请求，用于终端触发RRC连接建立，网络设备接收终端发送的RRC连接建立请求，响应于该RRC连接建立请求配置终端进入连接态，在终端进入连接态后，网络设备响应于终端进入连接态，向终端发送RRC消息指示终端释放非激活组播业务的配置和/或无线承载。
下面，以RRC消息为RRC释放消息为例进行说明，该RRC释放消息中包括用于指示非激活组播业务的标识信息，则RRC释放消息通过包括的标识信息来下发配置指示，进而指示终端释放非激活组播业务的配置和/或无线承载，终端接收到该RRC释放消息，释放非激活组播业务的配置和/或无线承载。
其中，该非激活组播业务的标识信息包括TMGI、MBS Session ID、MBS QoSflow ID或者非激活组播业务配置，或者其他类型的标识，本申请实施例不作限定。
需要说明的是，本申请实施例是以RRC释放消息中包含用于指示非激活组播业务的标识信息为例进行说明。而在另一些实施例中，RRC释放消息中不包含用于指示非激活组播业务的标识信息，终端接收到该RRC释放消息后，释放非激活组播业务的配置和/或无线承载。
另外，以RRC消息为RRC重配置消息为例进行说明，该RRC重配置消息中包括用于指示非激活组播业务的标识信息，则RRC重配置消息通过包括的标识信息来下发配置指示，进而指示终端释放非激活组播业务的配置和/或无线承载，终端接收到该RRC重配置消息，释放非激活组播业务的配置和/或无线承载。
其中，该非激活组播业务的标识信息包括TMGI、MBS Session ID、MBS QoSflow ID或者非激活组播业务配置，或者其他类型的标识，本申请实施例不作限定。
需要说明的是，本申请实施例是以RRC重配置消息中包含用于指示非激活组播业务的标识信息为例进行说明。而在另一些实施例中，RRC重配置消息中不包含用于指示非激活组播业务的标识信息，终端接收到该RRC重配置消息后，释放非激活组播业务的配置和/或无线承载。
可选地，终端触发RRC连接，向网络设备发送请求信息，进而由网络设备配置挂起的方式包括多种：
(1)终端向网络设备发送RRC请求，以通过该RRC请求触发RRC连接建立或RRC连接恢复，网络设备接收终端发送的RRC请求，响应于该RRC请求向终端发送RRC请求响应，通过RRC请求响应包括的配置指示挂起非激活组播业务的配置和/或无线承载。
在一些实施例中，该RRC请求响应为RRC释放消息、RRC恢复消息、RRC建立消息或者RRC拒绝消息中的任一种，或者还可以为其他RRC消息，本申请实施例不作限定。
例如，该终端向网络设备发送RRC连接恢复请求，触发RRC连接恢复，网络设备接收终端发送的RRC连接恢复请求，响应于该RRC连接恢复请求向终端发送RRC请求响应，通过RRC请求响应包括的配置指示挂起非激活组播业务的配置和/或无线承载。
又例如，该终端向网络设备发送RRC连接建立请求，触发RRC连接建立，网络设备接收终端发送的RRC连接建立请求，响应于该RRC连接建立请求向终端发送RRC请求响应，通过RRC请求响应包括的配置指示挂起非激活组播 业务的配置和/或无线承载。
下面，以RRC请求响应为RRC释放消息为例进行说明，RRC释放消息中包含挂起指示和用于指示非激活组播业务的标识信息，用于指示终端挂起非激活组播业务的配置和/或无线承载，而终端接收到该RRC释放消息后，挂起非激活组播业务的配置和/或无线承载。
其中，该非激活组播业务的标识信息包括TMGI、MBS Session ID、MBS QoSflow ID或者非激活组播业务配置，或者其他类型的标识，本申请实施例不作限定。
需要说明的是，本申请实施例是以RRC释放消息中包含用于指示非激活组播业务的标识信息为例进行说明。而在另一些实施例中，RRC释放消息中不包含用于指示非激活组播业务的标识信息，而包含挂起指示，用于指示终端挂起非激活组播业务的配置和/或无线承载，终端接收到该RRC释放消息后，挂起非激活组播业务的配置和/或无线承载。
本申请实施例是以RRC请求响应为RRC释放消息为例进行说明。而在另一些实施例中，该RRC请求响应还可以替换为RRC恢复消息、RRC建立消息或者RRC拒绝消息。
(2)终端向网络设备发送RRC请求，用于终端触发RRC连接建立或RRC连接恢复，网络设备接收终端发送的RRC请求，响应于该RRC请求配置终端进入连接态，在终端进入连接态后，网络设备响应于终端进入连接态，向终端发送RRC消息指示终端挂起非激活组播业务的配置和/或无线承载。
在一些实施例中，该RRC消息为RRC释放消息、RRC重配置消息中的任一种，或者还可以为其他RRC消息，本申请实施例不作限定。
在一些实施例中，网络设备接收终端发送的RRC请求，响应于该RRC请求向终端发送RRC恢复消息或RRC建立消息以配置终端进入连接态，或者网络设备还可以发送其他消息以配置终端进入连接态。
例如，终端向网络设备发送RRC连接恢复请求，用于终端触发RRC连接恢复，网络设备接收终端发送的RRC连接恢复请求，响应于该RRC连接恢复请求配置终端进入连接态，在终端进入连接态后，网络设备响应于终端进入连接态，向终端发送RRC消息指示终端挂起非激活组播业务的配置和/或无线承载。
又例如，终端向网络设备发送RRC连接建立请求，用于终端触发RRC连接建立，网络设备接收终端发送的RRC连接建立请求，响应于该RRC连接建 立请求配置终端进入连接态，在终端进入连接态后，网络设备响应于终端进入连接态，向终端发送RRC消息指示终端挂起非激活组播业务的配置和/或无线承载。
下面，以RRC消息为RRC释放消息为例进行说明，RRC释放消息中包含挂起指示和用于指示非激活组播业务的标识信息，用于指示终端挂起非激活组播业务的配置和/或无线承载，而终端接收到该RRC释放消息后，挂起非激活组播业务的配置和/或无线承载。
其中，该非激活组播业务的标识信息包括TMGI、MBS Session ID、MBS QoSflow ID或者非激活组播业务配置，或者其他类型的标识，本申请实施例不作限定。
需要说明的是，本申请实施例是以RRC释放消息中包含用于指示非激活组播业务的标识信息为例进行说明。而在另一些实施例中，RRC释放消息中不包含用于指示非激活组播业务的标识信息，而包含挂起指示，用于指示终端挂起非激活组播业务的配置和/或无线承载，终端接收到该RRC释放消息后，挂起非激活组播业务的配置和/或无线承载。
本申请实施例是以RRC消息为RRC释放消息为例进行说明。而在另一些实施例中，该RRC消息还可以替换为RRC重配置消息，在此不再赘述。
本申请实施例提供的方案中，终端通过触发RRC连接以实现由网络设备配置释放或挂起非激活组播业务的配置和/或无线承载，提供了一种终端处理非激活组播业务的方案，保证了传输的可靠性。
需要说明的是，本申请实施例中终端还会停止监听非激活组播业务对应的PDCCH(Physical Downlink Control Channel，物理下行控制信道)。也就是说，终端确定服务小区不支持非激活组播业务后，停止监听该非激活组播业务对应的PDCCH，以停止接收该非激活组播业务。
本申请实施例提供的方案中，终端可以确定服务小区不支持非激活组播业务，会停止监听非激活组播业务对应的PDCCH，不仅提高了终端确定服务小区不支持非激活组播业务的准确性，而且节省终端资源，保证了传输的可靠性。
需要说明的是，上述实施例可以拆分为新实施例，或与其他实施例互相组合为新实施例，本申请对实施例之间的组合不做限定。
图5示出了本申请一个示例性实施例提供的一种业务处理装置的框图，参 见图5，该装置包括：
处理模块501，用于响应于确定服务小区不支持非激活组播业务，释放或挂起所述非激活组播业务的配置和/或无线承载。
在一些实施例中，处理模块501，还用于响应于确定所述服务小区不支持所述非激活组播业务，直接执行释放或挂起所述非激活组播业务的配置和/或无线承载的步骤。
在一些实施例中，处理模块501，还用于响应于确定所述服务小区不支持所述非激活组播业务，触发建立RRC连接。
在一些实施例中，参见图6，所述装置还包括：
接收模块502，用于接收所述网络设备发送的配置指示，所述配置指示用于指示所述终端执行所述释放或挂起所述非激活组播业务的配置和/或无线承载；
所述处理模块501，还用于响应于接收到所述配置指示，释放或挂起所述非激活组播业务的配置和/或无线承载。
在一些实施例中，所述非激活组播业务包括预设类型的非激活组播业务。
在一些实施例中，参见图6，所述装置还包括：确定模块503，所述确定模块303用于：
在无法接收所述非激活组播业务的情况下，确定所述服务小区不支持所述非激活组播业务；或，
在确定所述服务小区不属于所述非激活组播业务的作用区域的情况下，确定所述服务小区不支持所述非激活组播业务；或，
在确定所述服务小区支持的所述非激活组播业务不属于所述网络设备配置的非激活组播业务的情况下，确定所述服务小区不支持所述非激活组播业务。
在一些实施例中，参见图6，所述装置还包括：
恢复模块504，用于响应于确定所述服务小区支持所述非激活组播业务，恢复所述非激活组播业务的配置和/或无线承载。
需要说明的是，上述实施例提供的装置，在实现其功能时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置与方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图7示出了本申请一个示例性实施例提供的一种指示发送装置的框图，参见图7，该装置包括：
发送模块701，用于向终端发送配置指示，所述配置指示用于指示所述终端执行释放或挂起非激活组播业务的配置和/或无线承载。
在一些实施例中，所述非激活组播业务包括预设类型的非激活组播业务。
需要说明的是，上述实施例提供的装置，在实现其功能时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的装置与方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
图8示出了本申请一个示例性实施例提供的通信设备的结构示意图，该通信设备包括：处理器801、接收器802、发射器803、存储器804和总线805。
处理器801包括一个或者一个以上处理核心，处理器801通过运行软件程序以及模块，从而执行各种功能应用以及信息处理。
接收器802和发射器803可以实现为一个通信组件，该通信组件可以是一块通信芯片。
存储器804通过总线805与处理器801相连。
存储器804可用于存储至少一个程序代码，处理器801用于执行该至少一个程序代码，以实现上述方法实施例中的各个步骤。
此外，通信设备可以为终端或网络设备。存储器1004可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，易失性或非易失性存储设备包括但不限于：磁盘或光盘，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，静态随时存取存储器(SRAM)，只读存储器(ROM)，磁存储器，快闪存储器，可编程只读存储器(PROM)。
在示例性实施例中，还提供了一种计算机可读存储介质，所述可读存储介质中存储有可执行程序代码，所述可执行程序代码由处理器加载并执行以实现上述各个方法实施例提供的由通信设备执行的业务处理方法或指示发送方法。
在示例性实施例中，提供了一种芯片，所述芯片包括可编程逻辑电路和/或程序指令，当所述芯片在终端或网络设备上运行时，用于实现如各个方法实施例提供的业务处理方法或指示发送方法。
在示例性实施例中，提供了计算机程序产品，当所述计算机程序产品被终端或网络设备的处理器执行时，其用于实现上述各个方法实施例提供的业务处理方法或指示发送方法。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本申请的可选实施例，并不用以限制本申请，凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (14)

  1. 一种业务处理方法，其特征在于，所述方法由终端执行，所述方法包括：
    响应于确定服务小区不支持非激活组播业务，释放或挂起所述非激活组播业务的配置和/或无线承载。
  2. 根据权利要求1所述的方法，其特征在于，所述响应于确定服务小区不支持非激活组播业务，释放或挂起所述非激活组播业务的配置和/或无线承载，包括：
    响应于确定所述服务小区不支持所述非激活组播业务，直接执行释放或挂起所述非激活组播业务的配置和/或无线承载的步骤。
  3. 根据权利要求1所述的方法，其特征在于，所述响应于确定服务小区不支持非激活组播业务，包括：
    响应于确定所述服务小区不支持所述非激活组播业务，触发建立RRC连接。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    接收网络设备发送的配置指示，所述配置指示用于指示所述终端执行释放或挂起所述非激活组播业务的配置和/或无线承载；
    所述释放或挂起所述非激活组播业务的配置和/或无线承载，包括：
    响应于接收到所述配置指示，释放或挂起所述非激活组播业务的配置和/或无线承载。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述非激活组播业务包括预设类型的非激活组播业务。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述方法还包括：
    在无法接收所述非激活组播业务的情况下，确定所述服务小区不支持所述非激活组播业务；或，
    在确定所述服务小区不属于所述非激活组播业务的作用区域的情况下，确 定所述服务小区不支持所述非激活组播业务；或，
    在确定所述服务小区支持的所述非激活组播业务不属于所述网络设备配置的非激活组播业务的情况下，确定所述服务小区不支持所述非激活组播业务。
  7. 根据权利要求1至6任一所述的方法，其特征在于，所述释放或挂起所述非激活组播业务的配置和/或无线承载之后，所述方法还包括：
    响应于确定所述服务小区支持所述非激活组播业务，恢复所述非激活组播业务的配置和/或无线承载。
  8. 一种指示发送方法，其特征在于，所述方法由网络设备执行，所述方法包括：
    向终端发送配置指示，所述配置指示用于指示所述终端执行释放或挂起非激活组播业务的配置和/或无线承载。
  9. 根据权利要求8所述的方法，其特征在于，所述非激活组播业务包括预设类型的非激活组播业务。
  10. 一种业务处理装置，其特征在于，所述装置包括：
    处理模块，用于响应于确定服务小区不支持非激活组播业务，释放或挂起所述非激活组播业务的配置和/或无线承载。
  11. 一种指示发送装置，其特征在于，所述装置包括：
    发送模块，用于向终端发送配置指示，所述配置指示用于指示所述终端执行释放或挂起非激活组播业务的配置和/或无线承载。
  12. 一种终端，其特征在于，所述终端包括：
    处理器；
    与所述处理器相连的收发器；
    其中，所述处理器被配置为加载并执行可执行指令以实现如权利要求1至7任一所述的业务处理方法。
  13. 一种网络设备，其特征在于，所述网络设备包括：
    处理器；
    与所述处理器相连的收发器；
    其中，所述处理器被配置为加载并执行可执行指令以实现如权利要求8至9任一所述的指示发送方法。
  14. 一种计算机可读存储介质，所述可读存储介质中存储有可执行程序代码，所述可执行程序代码由处理器加载并执行以实现如权利要求1至7任一所述的业务处理方法或实现如权利要求8至9任一所述的指示发送方法。
PCT/CN2022/097002 2022-06-02 2022-06-02 业务处理方法、指示发送方法、装置、设备及存储介质 WO2023231030A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/097002 WO2023231030A1 (zh) 2022-06-02 2022-06-02 业务处理方法、指示发送方法、装置、设备及存储介质
CN202280001811.6A CN117501721A (zh) 2022-06-02 2022-06-02 业务处理方法、指示发送方法、装置、设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/097002 WO2023231030A1 (zh) 2022-06-02 2022-06-02 业务处理方法、指示发送方法、装置、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2023231030A1 true WO2023231030A1 (zh) 2023-12-07

Family

ID=89026812

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/097002 WO2023231030A1 (zh) 2022-06-02 2022-06-02 业务处理方法、指示发送方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN117501721A (zh)
WO (1) WO2023231030A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155328A (zh) * 2006-09-26 2008-04-02 华为技术有限公司 通信系统中删除/修改组播广播业务的方法
CN101400028A (zh) * 2007-09-29 2009-04-01 鼎桥通信技术有限公司 一种小区切换方法及装置
WO2020028190A1 (en) * 2018-07-31 2020-02-06 Qualcomm Incorporated Periodic network reselection search while receiving multimedia broadcast multicast services
CN113453159A (zh) * 2020-03-27 2021-09-28 维沃移动通信有限公司 Mbs业务传输方法、mbs业务传输控制方法及相关设备
CN113939042A (zh) * 2020-07-14 2022-01-14 维沃移动通信有限公司 处理方法、发送方法及相关设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101155328A (zh) * 2006-09-26 2008-04-02 华为技术有限公司 通信系统中删除/修改组播广播业务的方法
CN101400028A (zh) * 2007-09-29 2009-04-01 鼎桥通信技术有限公司 一种小区切换方法及装置
WO2020028190A1 (en) * 2018-07-31 2020-02-06 Qualcomm Incorporated Periodic network reselection search while receiving multimedia broadcast multicast services
CN113453159A (zh) * 2020-03-27 2021-09-28 维沃移动通信有限公司 Mbs业务传输方法、mbs业务传输控制方法及相关设备
CN113939042A (zh) * 2020-07-14 2022-01-14 维沃移动通信有限公司 处理方法、发送方法及相关设备

Also Published As

Publication number Publication date
CN117501721A (zh) 2024-02-02

Similar Documents

Publication Publication Date Title
US11805559B2 (en) Session management method and system, and terminal for locating a user plane function (UPF) entity when a session is an inactive state
US20230180349A1 (en) Bearer configuration method and apparatus, context information management method and apparatus, releasing method and apparatus, and device
CN108616950B (zh) 无线接入网络间的移动性管理方法、核心网设备及基站
CN113660616B (zh) 一种组播/广播业务的通信方法和装置
WO2022205381A1 (zh) 广播多播业务传输方法、装置及存储介质
WO2012058979A1 (zh) 一种单站模式下实现集群通话的方法及系统
EP4187941A1 (en) Data transmission method, apparatus and system
US20230188949A1 (en) Communication method, apparatus, and system
US10142804B2 (en) All-group calling method, system, related device and computer storage medium
CN108029154B (zh) 无线承载管理方法、装置及系统
US20230156436A1 (en) Data Transmission Method, Apparatus, and System
WO2023231030A1 (zh) 业务处理方法、指示发送方法、装置、设备及存储介质
JP2020504956A (ja) コンテキスト解放方法、機器及びシステム
CN108924950B (zh) 一种建立承载的方法及装置
WO2023231031A1 (zh) 业务处理方法、指示发送方法、装置、设备及存储介质
CN113141657B (zh) 一种半持续调度方法及装置
AU2022278101A1 (en) Service data transmission method and communication apparatus
CN109548143B (zh) 一种寻呼处理方法及设备
WO2023231033A1 (zh) 指示信息发送方法、组播业务更新方法、装置及介质
WO2024040456A1 (zh) Pdcp实体处理、信息发送方法、装置及存储介质
WO2023231032A1 (zh) 非激活态组播业务区域的确定方法、配置方法、及装置
US20240080931A1 (en) Communication method and apparatus
WO2023245412A1 (zh) 上行定位参考信号的配置方法、装置、设备及存储介质
WO2024011523A1 (zh) 激活或去激活上行定位参考信号的方法、装置
WO2021056244A1 (zh) Rrc连接控制方法、装置、终端及接入网设备

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 202280001811.6

Country of ref document: CN

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

Ref document number: 22944358

Country of ref document: EP

Kind code of ref document: A1