WO2024031458A1 - 资源配置方法、装置、存储介质以及终端 - Google Patents

资源配置方法、装置、存储介质以及终端 Download PDF

Info

Publication number
WO2024031458A1
WO2024031458A1 PCT/CN2022/111539 CN2022111539W WO2024031458A1 WO 2024031458 A1 WO2024031458 A1 WO 2024031458A1 CN 2022111539 W CN2022111539 W CN 2022111539W WO 2024031458 A1 WO2024031458 A1 WO 2024031458A1
Authority
WO
WIPO (PCT)
Prior art keywords
multicast service
configuration information
inactive
service configuration
terminal device
Prior art date
Application number
PCT/CN2022/111539
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/111539 priority Critical patent/WO2024031458A1/zh
Priority to CN202280002626.9A priority patent/CN117882471A/zh
Publication of WO2024031458A1 publication Critical patent/WO2024031458A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L27/00—Modulated-carrier systems
    • 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 disclosure relates to the field of communication technology, and in particular, to a resource configuration method, device, storage medium and terminal.
  • MBS Multicast and Broadcast Service
  • MBS Multicast and Broadcast Service
  • the present disclosure provides a resource configuration method, device, storage medium and terminal.
  • a resource configuration method includes:
  • a resource configuration method includes:
  • the terminal device is used to release or retain the inactive multicast service configuration information and use the multicast service configuration information.
  • a resource configuration device where the device includes:
  • the configuration module is configured to release or retain inactive multicast service configuration information, and use the multicast service configuration information configured on the network side device.
  • a resource configuration device where the device includes:
  • a sending module configured to configure multicast service configuration information and send the multicast service configuration information to a terminal device.
  • the terminal device is used to release or retain inactive multicast service configuration information and use the multicast service configuration information.
  • Business configuration information configured to configure multicast service configuration information and send the multicast service configuration information to a terminal device.
  • a terminal device including:
  • a first memory for storing instructions executable by the first processor
  • the first processor is configured to execute the executable instructions to implement the resource configuration method provided by the first aspect of this disclosure.
  • a network side device including:
  • a second memory for storing instructions executable by the second processor
  • the second processor is configured to execute the executable instructions to implement the resource configuration method provided by the second aspect of the present disclosure.
  • a computer-readable storage medium on which computer program instructions are stored.
  • the program instructions are executed by a processor, the resource configuration provided by the first or second aspect of the present disclosure is implemented. Method steps.
  • the technical solution provided by the embodiments of the present disclosure can include the following beneficial effects: by releasing or retaining the inactive state multicast configuration information and utilizing the multicast service configuration configured by the network side device, the present application can perform multicast in the inactive state Business data reception.
  • Figure 1 is a schematic diagram of the transition between RRC connected state, inactive state and idle state.
  • Figure 2 shows an application scenario applicable to a resource configuration method according to some embodiments.
  • Figure 3 is a flow chart of a resource configuration method according to some embodiments.
  • Figure 4 is a flow chart of a resource configuration method according to other embodiments.
  • Figure 5 is a flow chart of a resource configuration method according to some embodiments.
  • Figure 6 is a flow chart of a resource configuration method according to some further embodiments.
  • Figure 7 is a flow chart of a resource configuration method according to some embodiments.
  • Figure 8 is a communication sequence diagram illustrating a resource configuration method according to some embodiments.
  • Figure 9 is a flow chart of a resource configuration method according to some further embodiments.
  • Figure 10 is a flow chart of a resource configuration method according to some embodiments.
  • Figure 11 is a communication sequence diagram when the designated signaling is RRC recovery signaling in a resource configuration method according to some embodiments.
  • Figure 12 is a communication sequence diagram when the designated signaling is RRC reconfiguration signaling in a resource configuration method according to some embodiments.
  • Figure 13 shows a resource configuration method according to some embodiments, in which the designated signaling is RRC release signaling including suspension configuration.
  • Figure 14 is a flow chart of a resource configuration method according to some embodiments.
  • Figure 15 is a block diagram of a resource configuration device according to some embodiments.
  • Figure 16 is a block diagram of a resource configuration device according to some embodiments.
  • Figure 17 is a block diagram of a terminal device according to some embodiments.
  • Figure 18 is a block diagram of a network side device according to some embodiments.
  • Terminal equipment includes equipment that provides voice and/or data connectivity to users. Specifically, it includes equipment that provides voice to users, or equipment that provides data connectivity to users, or equipment that provides voice and data connectivity to users. equipment. This may include, for example, a handheld device with wireless connectivity, or a processing device connected to a wireless modem. As a way, the terminal device may include user equipment (UE), wireless terminal equipment, mobile terminal equipment, or user equipment (user device), etc.
  • UE user equipment
  • wireless terminal equipment wireless terminal equipment
  • mobile terminal equipment or user equipment (user device), etc.
  • Network side equipment is also called wireless access network equipment.
  • the network side equipment is a device that connects terminal equipment to the wireless network. It can include access network equipment, core network equipment, and services. Supplier's equipment (such as servers), etc.
  • network side equipment includes but is not limited to: transmission point (transmission reception point, TRP), base station (such as gNB), wireless network controller (radionetwork controller, RNC), Node B (Node B, NB), base station controller (base station controller, BSC), BTS (base transceiver station), HeNB (home evolved NodeB), or HNB (home NodeB), baseband unit (baseband uit, BBU), etc.
  • the terminal device can perform the RRC (radio resource control, radio resource control) establishment process with the network-side device.
  • RRC radio resource control, radio resource control
  • the RRC state of the terminal device is the RRC connected (RRC_CONNECTED) state.
  • the RRC state of the terminal device can be converted among the following states: RRC idle state (RRC_IDLE), RRC connected state (RRC_CONNECTED) and RRC inactive state (RRC_INACTIVE).
  • RRC idle state RRC_IDLE
  • RRC connected state RRC_CONNECTED
  • RRC inactive state RRC_INACTIVE
  • the transition of each RRC state can be shown in Figure 1, from As shown in Figure 1, the connected state, inactive state and idle state of RRC can be converted to each other.
  • the terminal device may transition from an inactive state to a connected state, or may transition from an inactive state to an idle state, etc.
  • RRC connected state can also be referred to as connected state.
  • the terminal device has established an RRC connection with the network and can transmit data.
  • the RRC idle state can also be referred to as the idle state.
  • idle state and “RRC idle state” are the same concept, and the two terms are interchangeable.
  • the RRC idle state means that the RRC connection between the terminal device and the network-side device is not established, and the connection between the network-side device corresponding to the terminal device and the core network device is not established.
  • the terminal device is in idle state, if there is data that needs to be transmitted, the connection between the terminal device and the network-side device, and the connection between the network-side device and the core network device need to be established first before data can be transmitted.
  • the RRC inactive state can also be referred to as the inactive state.
  • deactivated state means that the RRC connection between the terminal device and the network-side device has been disconnected, but the connection between the network-side device corresponding to the terminal device and the core network device has not been disconnected.
  • the terminal device is in the deactivated state, if there is data that needs to be transmitted, the RRC connection between the terminal device and the network side device needs to be restored before data transmission can be carried out.
  • the application environment may include a terminal device 01 and a network-side device 02, where the terminal device 01 and the network-side device 02 can communicate via wired Or connect wirelessly.
  • the terminal device 01 may be a user equipment (user equipment, UE) or a mobile station (mobile station, MS) or a mobile terminal (mobile terminal, MT), etc.
  • the terminal device 01 can be a mobile phone, a tablet, or a computer with wireless transceiver functions, or it can be a virtual reality (VR) terminal, an augmented reality (AR) terminal, or an industrial control center Wireless terminals, wireless terminals in driverless driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in smart cities, smart homes, vehicle-mounted terminals, etc.
  • VR virtual reality
  • AR augmented reality
  • the network side device 02 may include access network equipment, core network equipment, or service provider equipment (such as a server), etc., without limitation.
  • the network side device 02 is mainly used to implement the resource scheduling, wireless resource management, wireless access control and other functions of the terminal device 01.
  • the network side device 02 can be any node among a small base station, a wireless access point, a transceiver point (TRP), a transmission point (TP), and some other access node.
  • the first sending mode is multicast (multicast) sending mode.
  • the terminal device In the multicast sending mode, the terminal device enters the connected state (RRC_CONNECTED) to receive the sending configuration information of the MBS service. In this way, the MBS service can be received, and the network side device can also send the MBS service reception configuration information to the terminal device through UE-specific signaling.
  • the second transmission mode is the broadcast transmission mode.
  • the terminal device In the broadcast transmission mode, the terminal device can receive the transmission configuration information of the MBS service in the idle state (IDLE), the inactive state (INACTIVE) or the connected state (CONNECTED), and receive the MBS service.
  • the network side device can send the MBS service receiving configuration information to the terminal device through system information, such as SIB (System Information Block, System Information Block) and MBS control channel information, such as MCCH (MBS Control Channel, MBS Control Channel).
  • SIB System Information Block, System Information Block
  • MBS control channel information such as MCCH (MBS Control Channel, M
  • the existing technology cannot support the reception of inactive multicast services.
  • the reception of multicast service data cannot be performed.
  • the terminal device enters the connected state there are no relevant regulations on how to handle the inactive state multicast service configuration.
  • FIG 3 is a flow chart of a resource configuration method according to some embodiments. As shown in Figure 3, this resource configuration method can be used in the terminal device in Figure 2, including the following steps.
  • step S110 the terminal device releases the inactive multicast service configuration information and uses the multicast service configuration information configured by the network side device.
  • the terminal device can support inactive multicast service reception, that is, when the terminal device is in an inactive state, it can continue to receive multicast service data. It can be seen that the terminal device can obtain the inactive multicast service configuration when it is inactive, and use the inactive multicast service configuration to perform the inactive multicast service.
  • this application can release the inactive multicast service configuration information when configuring resources.
  • the inactive multicast service configuration information can be the configuration information obtained when the terminal device is in the inactive state.
  • the terminal device can also use the multicast service configuration information configured by the network side device.
  • the multicast service configuration information configured by the network side device can include at least one of the following: Use Configuration information for receiving multicast services in the inactive state, and configuration information for receiving multicast services in the connected state.
  • the multicast service configuration information configured by the network side device may include configuration information for inactive state multicast service reception, may also include configuration information for connected state multicast service reception, or may include configuration information for inactive state multicast service reception. Configuration information for receiving multicast services in active state and configuration information for receiving multicast services in connected state.
  • this application can use the configuration information for inactive multicast service reception, that is, using the configuration information for inactive multicast service reception transmitted by the network side device.
  • the information replaces the inactive multicast service configuration information in the terminal device.
  • this application can also use the configuration information received by the connected multicast service, that is, the configuration information received by the connected multicast service transmitted by the network side device is used to replace the configuration information in the terminal device. Inactive multicast service configuration information.
  • this application can also use the configuration information received by the inactive multicast service and the configuration information received by the connected multicast service, that is, by using the inactive multicast service transmitted by the network side device.
  • the configuration information for multicast service reception in the multicast state and the configuration information for multicast service reception in the connection state replace the inactive multicast service configuration information in the terminal device.
  • the operation of the terminal device to release the inactive multicast service configuration information can be called a full configuration operation.
  • the terminal device can release the inactive multicast service configuration and use the network side device. Configured multicast service configuration information.
  • the embodiment of this application stipulates that the terminal device can process the inactive multicast service configuration by releasing the inactive multicast service configuration information and using the multicast service configuration information configured by the network side device, so that the configuration information can be guaranteed real-time.
  • FIG 4 is a flow chart of a resource configuration method according to other embodiments. As shown in Figure 4, this resource configuration method can be used in the terminal device in Figure 2, including the following steps.
  • step S210 the terminal device retains the inactive multicast service configuration information and uses the multicast service configuration information configured by the network side device.
  • this application can retain the inactive multicast service configuration information when configuring resources.
  • the inactive multicast service configuration information can be the configuration information obtained when the terminal device is in the inactive state.
  • the terminal device after the terminal device retains the inactive multicast service configuration information, it can also use the multicast service configuration information configured by the network side device.
  • the multicast service configuration information configured by the network side device can include at least one of the following: Use Configuration information for receiving multicast services in the inactive state, and configuration information for receiving multicast services in the connected state.
  • the multicast service configuration information configured by the network side device may include configuration information for inactive state multicast service reception, may also include configuration information for connected state multicast service reception, or may include configuration information for inactive state multicast service reception. Configuration information for receiving multicast services in active state and configuration information for receiving multicast services in connected state.
  • this application when the terminal configures resources, this application can retain the configured inactive multicast service configuration information and use the configuration information for connected multicast service reception.
  • the configuration information may be sent by the network side device to the terminal device.
  • this application can retain the configured inactive multicast service configuration information and use the configuration information received by the inactive multicast service.
  • the above is used for the inactive multicast service.
  • the received configuration information may be sent by the network side device to the terminal device.
  • this application when the terminal configures resources, this application can retain the configured inactive multicast service configuration information, and use the configuration information for inactive multicast service reception and the configuration for connected multicast service reception.
  • Information, the configuration information for receiving inactive multicast services and the configuration information for receiving connected multicast services may be sent by the network side device to the terminal device.
  • the operation of the terminal device to retain the inactive multicast service configuration information can be called an incremental configuration operation.
  • the terminal device can retain the inactive multicast service configuration and use the network Multicast service configuration information configured on the side device.
  • the embodiments of this application stipulate that the terminal device can handle the inactive multicast service configuration by retaining the inactive multicast service configuration information and using the multicast service configuration information configured by the network side device, which can reduce the inactive multicast service configuration.
  • the transmission of necessary signaling can thereby reduce the burden of network transmission.
  • FIG 5 is a flow chart of a resource configuration method according to some embodiments. As shown in Figure 5, this resource configuration method can be used in the terminal device in Figure 2, including the following steps.
  • step S310 the terminal device releases or retains the inactive multicast service configuration information, and uses the multicast service configuration information configured by the network side device.
  • the terminal device can release the inactive multicast service configuration information, or can retain the inactive multicast service configuration information, and use the multicast service configuration information configured by the network side device. Whether the terminal device releases the inactive multicast service configuration information or retains the inactive multicast service configuration information is not explicitly restricted here and can be selected according to the actual situation. For example, the terminal device can determine whether to release or retain the inactive multicast service configuration information according to the protocol provisions. For another example, the terminal device may also determine whether to release or retain the inactive multicast service configuration information according to instructions from the network side device.
  • the embodiments of this application stipulate that the terminal device may process the inactive multicast service configuration by releasing the inactive multicast service configuration information, or it may retain the inactive multicast service configuration information and use the network side device
  • the configured multicast service configuration information can improve the flexibility of processing inactive multicast service configuration.
  • Figure 6 is a flow chart of a resource configuration method according to some further embodiments. As shown in Figure 6, this resource configuration method can be used in the terminal device in Figure 2, including the following steps.
  • step S410 the terminal device determines to release or retain the inactive multicast service configuration information according to the protocol provisions, and uses the multicast service configuration information configured by the network side device.
  • the terminal device may determine to release or retain the inactive multicast service configuration information according to the protocol provisions, and use the multicast service configuration information configured by the network side device.
  • the embodiment of the present application can release the inactive multicast service configuration information and use the multicast service configuration information configured by the network side device.
  • the embodiment of the present application can retain the inactive multicast service configuration information and use the multicast service configuration information configured by the network side device.
  • the protocol provisions may be preset. Each time the terminal device performs resource configuration, it can determine whether to release the inactive multicast service configuration information or retain the inactive multicast service based on the protocol provisions. Configuration information.
  • the embodiments of this application stipulate that the terminal device can determine the processing method for the inactive multicast service configuration based on the protocol regulations. If the protocol regulations are different, the corresponding processing methods for the inactive multicast service configuration will also be different, so that it can Further improve the flexibility in processing inactive multicast service configuration.
  • FIG 7 is a flow chart of a resource configuration method according to some embodiments. As shown in Figure 7, this resource configuration method can be used in the terminal device in Figure 2, including the following steps.
  • step S510 the terminal device receives the configuration instruction information sent by the network side device.
  • the terminal device may determine to release or retain the inactive multicast service configuration information based on the configuration indication information transmitted by the network side device. Specifically, the terminal device may receive the configuration indication information sent by the network side device, and determine whether to release or retain the inactive multicast service configuration information based on the configuration indication information.
  • the configuration indication information may be information determined by the network side device based on the network conditions of the terminal device, or based on the configuration information received by the inactive state multicast service and the configuration information received by the connected state multicast service.
  • step S520 the terminal device determines to release or retain the inactive multicast service configuration information according to the configuration instruction information, and uses the multicast service configuration information configured by the network side device.
  • the corresponding processing methods for inactive multicast service configuration may also be different.
  • the terminal device when the terminal device receives the configuration indication information sent by the network side device as a full configuration (fullConfig) message, it can release the inactive multicast service configuration information and use the multicast service configuration information configured by the network side device.
  • fullConfig full configuration
  • the terminal device when the terminal device receives the configuration instruction information sent by the network side device as an incremental configuration message, it can retain the inactive multicast service configuration information and use the multicast service configuration information configured by the network side device.
  • the embodiments of this application stipulate that the terminal device can determine the processing method for the inactive multicast service configuration through the configuration instruction information transmitted by the network side device. If the configuration instruction information transmitted by the network side device is different, the corresponding inactive group The processing methods of multicast service configuration are also different, so that inactive multicast service configuration can be processed more flexibly.
  • Figure 8 is a communication sequence diagram illustrating a resource configuration method according to some embodiments.
  • the terminal device can receive the multicast service configuration information and configuration instruction information sent by the network side device. On this basis, the terminal device can determine whether to release or retain the inactive multicast service configuration information according to the configuration information, and use the multicast service configuration information transmitted by the network side device.
  • the embodiment of the present application can be based on the network side device.
  • the configuration instruction information sent by the server determines whether to release or retain the inactive multicast service configuration information, which can improve the accuracy of resource configuration.
  • FIG 9 is a flow chart of a resource configuration method according to some further embodiments. As shown in Figure 9, this resource configuration method can be used in the terminal device in Figure 2, including the following steps.
  • step S610 when the status of the terminal device changes, the terminal device releases or retains the inactive multicast service configuration information and uses the multicast service configuration information configured by the network side device.
  • the embodiment of the present application can release or retain the inactive multicast service configuration information and use the multicast service configuration information configured by the network side device.
  • the status of the terminal device includes three states, which are inactive, connected and idle.
  • the change in the status of the terminal device may be that the terminal device enters the connected state (connected) from the inactive state.
  • the embodiment of the present application can release or retain the inactive state multicast service configuration information, and use the group configuration information configured by the network side device. broadcast service configuration information.
  • the change in the status of the terminal device may also be that the terminal device enters an inactive state (inactive).
  • the terminal device when the terminal device is in an inactive state, it may send a connection request to the network side device.
  • the state of the terminal device Upon receiving the RRC release signaling containing the pending configuration sent by the network side device, the state of the terminal device can enter the inactive state (inactive), that is, the state of the terminal device changes from the inactive state (inactive) to the inactive state. (inactive).
  • the embodiment of the present application can release or retain the inactive state multicast service configuration information and use the network side device configuration multicast service configuration information.
  • the status of the terminal device when the status of the terminal device changes, it may also be a change in other statuses.
  • the state change may be from a connected state to an inactive state.
  • the specific changes in the status of the terminal device will not be described in detail here, and the selection can be made according to the actual situation.
  • the embodiment of the present application may determine to release or retain the inactive multicast service configuration information according to the protocol provisions. As an example, when the status of the terminal device changes, if the protocol stipulates that the inactive multicast service configuration information is released, this application releases the inactive multicast service configuration information.
  • the embodiment of the present application may also determine to release or retain the inactive multicast service configuration information based on the configuration instruction information sent by the network side device. As an example, when the status of the terminal device changes, if the configuration indication information received from the network side is full configuration, this application can release the inactive multicast service configuration information.
  • the embodiments of this application stipulate that the terminal equipment can process the inactive multicast service configuration according to the status change of the terminal equipment, that is, when the status of the terminal equipment changes, this application can release or retain the inactive multicast service Configuration information, and use the multicast service configuration information configured on the network side device, which can improve the flexibility and accuracy of resource configuration.
  • FIG 10 is a flow chart of a resource configuration method according to some embodiments. As shown in Figure 10, this resource configuration method can be used in the terminal device in Figure 2, including the following steps.
  • step S710 when receiving designated signaling from the network side device, the terminal device releases or retains the inactive multicast service configuration information and uses the multicast service configuration information configured by the network side device.
  • the inactive multicast service configuration information when it is determined that the terminal device receives the specified signaling transmitted by the network side device, the inactive multicast service configuration information can be released or retained, and the inactive multicast service configuration information can be used. Multicast service configuration information.
  • the designated signaling may include at least one of RRC recovery signaling (RRCResume), RRC reconfiguration signaling (RRCReconfiguration), and RRC release signaling (RRCRelease with Suspend configuration).
  • RRC recovery signaling RRCResume
  • RRC reconfiguration signaling RRCReconfiguration
  • RRC release signaling RRCRelease with Suspend configuration
  • the terminal device when the configured inactive multicast service configuration information is carried in the suspension configuration, if the terminal device receives the RRC recovery signaling (RRCResume) transmitted by the network side device, it can retain the inactive state.
  • multicast service configuration information that is, the inactive multicast service carried in the pending configuration cannot be released.
  • FIG 11 is a communication sequence diagram when the designated signaling is RRC recovery signaling (RRCResume) in a resource configuration method according to some embodiments.
  • the terminal device can receive the RRC recovery signaling (RRCResume) sent by the network side device. On this basis, the terminal device can release or retain the inactive multicast service configuration information, and use the multicast service configuration information configured by the network side device contained in the RRC recovery signaling (RRCResume).
  • FIG 12 is a communication sequence diagram when the designated signaling is RRC reconfiguration signaling (RRCReconfiguration) in a resource configuration method according to some embodiments.
  • the terminal device can receive RRC reconfiguration signaling (RRCReconfiguration) sent by the network side device. On this basis, the terminal device can release or retain the inactive multicast service configuration information, and use the multicast service configuration information configured by the network side device contained in the RRC reconfiguration signaling (RRCReconfiguration).
  • RRCReconfiguration RRC reconfiguration signaling
  • Figure 13 is a communication sequence diagram when the specified signaling is RRC release signaling (RRCRelease with Suspend configuration) including suspension configuration in a resource configuration method according to some embodiments.
  • the terminal device can receive RRC release signaling containing suspend configuration (RRCRelease with Suspend configuration) sent by the network side device. On this basis, the terminal device can release or retain the inactive multicast service configuration information and use the multicast service configuration contained in the RRC release signaling (RRCRelease with Suspend configuration) of the network side device configuration. information.
  • the designated signaling can include the multicast service configuration information configured by the network side device.
  • the terminal device can release or retain the inactive multicast service configuration information and can use the designated signaling.
  • the embodiment of the present application can determine to release or retain the inactive multicast service configuration information according to the protocol provisions, and use the network side device configuration multicast service configuration information.
  • the terminal device receives specified signaling from the network side device, if the protocol stipulates that the inactive multicast service configuration information be released, this application can release the inactive multicast service configuration information.
  • the embodiment of the present application may also determine to release or retain the inactive multicast service configuration information based on the configuration instruction information sent by the network side device. And use the multicast service configuration information configured on the network side device. As an example, when the terminal device receives specified signaling from the network side device, if the configuration indication information received from the network side is full configuration, this application can release the inactive multicast service configuration information.
  • the embodiments of this application stipulate that the terminal device can process the inactive multicast service configuration according to the designated signaling received from the network side device. That is, when the terminal device receives the designated signaling from the network side device, this application You can release or retain inactive multicast service configuration information and use the multicast service configuration information configured on the network side device, which can improve the flexibility and accuracy of resource configuration.
  • Figure 14 is a flow chart of a resource configuration method according to some embodiments. As shown in Figure 14, this resource configuration method can be used in the network side device in Figure 2, including the following steps.
  • step S810 the network side device configures the multicast service configuration information and sends the multicast service configuration information to the terminal device.
  • the terminal device is used to release or retain the inactive multicast service configuration information and use the multicast service configuration information. .
  • the network side device can configure multicast service configuration information and send the multicast service configuration information to the terminal device.
  • the terminal device can be used to release or retain the inactive multicast service configuration information, and use the multicast service configuration information transmitted by the network side device.
  • the multicast service configuration information configured by the network side device includes at least one of configuration information for receiving multicast services in an inactive state and configuration information for receiving multicast services in a connected state.
  • the network side device may obtain the configuration indication information and send the configuration indication information to the terminal device to instruct the terminal device to determine whether to release or retain the inactive multicast service configuration information according to the configuration indication information. It can be seen that the configuration indication information is used to instruct the terminal device to release or retain the inactive multicast service configuration information.
  • the network side device can also send designated signaling to the terminal device so that the terminal device releases or retains the inactive multicast service configuration information and uses the multicast service configuration information configured by the network side device, that is, the terminal device uses Release or retain inactive multicast service configuration information when receiving specified signaling.
  • the designated signaling may include at least one of RRC recovery signaling, RRC reconfiguration signaling, and RRC release signaling including suspended configuration.
  • Figure 15 is a block diagram of a resource configuration device 900 according to some embodiments.
  • the resource configuration device 900 is applied to a terminal device, and the resource configuration device 900 may include a configuration module 910 .
  • the configuration module 910 is configured to release or retain inactive multicast service configuration information, and use the multicast service configuration information configured by the network side device.
  • the multicast service configuration information configured by the network side device includes at least one of configuration information for inactive multicast service reception and configuration information for connected multicast service reception.
  • the configuration module 910 may be configured to determine whether to release or retain the inactive multicast service configuration information according to protocol regulations.
  • configuration module 910 may include:
  • a receiving submodule configured to receive configuration indication information sent by the network side device
  • the determining submodule is configured to determine whether to release or retain the inactive multicast service configuration information according to the configuration indication information.
  • the configuration module 910 may also be configured to release or retain the inactive multicast service configuration information when the status of the terminal device changes, and use the multicast service configuration information configured by the network side device.
  • the change in the state of the terminal device includes the terminal device entering the connected state from the inactive state, or the terminal device entering the inactive state from the inactive state.
  • the configuration module 910 may also be configured to release or retain the inactive multicast service configuration information when receiving specified signaling from the network side device, and use the multicast service configured by the network side device. Configuration information.
  • the designated signaling includes at least one of RRC recovery signaling, RRC reconfiguration signaling, and RRC release signaling including pending configuration.
  • Figure 16 is a block diagram of a resource configuration device 1000 according to some embodiments.
  • the resource configuration device 1000 is applied to network side equipment, and the resource configuration device 1000 may include a sending module 1010 .
  • the sending module 1010 is configured to configure multicast service configuration information and send the multicast service configuration information to the terminal device.
  • the terminal device is used to release or retain the inactive multicast service configuration information and use the multicast service configuration information. Describes the multicast service configuration information.
  • the multicast service configuration information includes at least one of configuration information for receiving multicast services in an inactive state and configuration information for receiving multicast services in a connected state.
  • the resource configuration device 1000 may also include:
  • the configuration instruction sending module is configured to send configuration instruction information to the terminal device to instruct the terminal device to determine to release or retain the inactive multicast service configuration information according to the configuration instruction information.
  • the resource configuration device 1000 may also include:
  • a designated signaling sending module configured to send designated signaling to the terminal device, and the terminal device is configured to release or retain the inactive multicast service configuration information when receiving the designated signaling, and use The multicast service configuration information.
  • the designated signaling includes at least one of RRC recovery signaling, RRC reconfiguration signaling, and RRC release signaling including pending configuration.
  • the present disclosure also provides a computer-readable storage medium on which computer program instructions are stored. When the program instructions are executed by a processor, the steps of the resource configuration method provided by the present disclosure are implemented.
  • Figure 17 is a block diagram of a terminal device according to some embodiments.
  • the terminal device 1100 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, a smart car, etc.
  • the terminal device 1100 may include one or more of the following components: a first processing component 1102, a first memory 1104, a first power supply component 1106, a multimedia component 1108, an audio component 1110, a first input/output interface 1112, a sensor component 1114, and communications component 1116.
  • the first processing component 1102 generally controls the overall operations of the terminal device 1100, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the first processing component 1102 may include one or more first processors 1120 to execute instructions to complete all or part of the steps of the above resource configuration method.
  • first processing component 1102 may include one or more modules that facilitate interaction between first processing component 1102 and other components.
  • first processing component 1102 may include a multimedia module to facilitate interaction between multimedia component 1108 and first processing component 1102.
  • the first memory 1104 is configured to store various types of data to support operations at the terminal device 1100 . Examples of such data include instructions for any application or method operating on the terminal device 1100, contact data, phonebook data, messages, pictures, videos, etc.
  • the first memory 1104 may be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Except programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read-only memory
  • EPROM erasable Except programmable read-only memory
  • PROM programmable read-only memory
  • ROM read-only memory
  • magnetic memory flash memory
  • flash memory magnetic disk or optical disk.
  • the first power supply component 1106 provides power to various components of the terminal device 1100 .
  • the first power component 1106 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the end device 1100 .
  • Multimedia component 1108 includes a screen providing an output interface between the terminal device 1100 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide action.
  • multimedia component 1108 includes a front-facing camera and/or a rear-facing camera.
  • the front camera and/or the rear camera may receive external multimedia data.
  • Each front-facing camera and rear-facing camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.
  • Audio component 1110 is configured to output and/or input audio signals.
  • the audio component 1110 includes a microphone (MIC) configured to receive external audio signals when the terminal device 1100 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal may be further stored in first memory 1104 or sent via communication component 1116 .
  • audio component 1110 also includes a speaker for outputting audio signals.
  • the first input/output interface 1112 provides an interface between the first processing component 1102 and a peripheral interface module.
  • the peripheral interface module may be a keyboard, a click wheel, a button, etc. These buttons may include, but are not limited to: Home button, Volume buttons, Start button, and Lock button.
  • Sensor component 1114 includes one or more sensors for providing various aspects of status assessment for terminal device 1100 .
  • the sensor component 1114 can detect the open/closed state of the terminal device 1100 and the relative positioning of components, such as the display and keypad of the terminal device 1100.
  • the sensor component 1114 can also detect the terminal device 1100 or a terminal device 1100. Changes in the position of components, presence or absence of user contact with the terminal device 1100 , orientation or acceleration/deceleration of the terminal device 1100 and temperature changes of the terminal device 1100 .
  • Sensor assembly 1114 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact.
  • Sensor assembly 1114 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor component 1114 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • the communication component 1116 is configured to facilitate wired or wireless communication between the terminal device 1100 and other devices.
  • the terminal device 1100 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 1116 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communications component 1116 also includes a near field communications (NFC) module to facilitate short-range communications.
  • NFC near field communications
  • the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • the terminal device 1100 may be configured by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Programming gate array (FPGA), controller, microcontroller, microprocessor or other electronic components are implemented for executing the above resource configuration method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable Programming gate array
  • controller microcontroller, microprocessor or other electronic components are implemented for executing the above resource configuration method.
  • a non-transitory computer-readable storage medium including instructions such as a first memory 1104 including instructions, which can be executed by the first processor 1120 of the terminal device 1100 to complete the above resources is also provided.
  • Configuration method the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
  • a computer program product comprising a computer program executable by a programmable device, the computer program having a function for performing the above when executed by the programmable device.
  • the code part of the resource configuration method.
  • Figure 18 is a block diagram of a network side device according to an exemplary embodiment.
  • the network side device 1200 may be provided as a server.
  • the network side device 1200 includes a second processing component 1222 , which further includes one or more processors, and a memory resource represented by a second memory 1232 for storing instructions executable by the second processing component 1222 , such as applications.
  • the application program stored in the second memory 1232 may include one or more modules each corresponding to a set of instructions.
  • the second processing component 1222 is configured to execute instructions to perform the resource configuration method.
  • the network side device 1200 may also include a second power component 1226 configured to perform power management of the network side device 1200, a wired or wireless network interface 1250 configured to connect the network side device 1200 to the network, and a second input/ Output interface 1258.
  • the network side device 1200 may operate based on an operating system stored in the memory 1232, such as Windows Server TM , Mac OS X TM , Unix TM , Linux TM , FreeBSD TM or the like.

Landscapes

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

Abstract

一种资源配置方法、装置、存储介质以及终端，所述方法包括：释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。本申请通过释放或保留非激活态组播业务配置信息，能够灵活有效的对资源进行配置。

Description

资源配置方法、装置、存储介质以及终端 技术领域
本公开涉及通信技术领域，尤其涉及一种资源配置方法、装置、存储介质以及终端。
背景技术
随着通信技术的发展及需求的丰富，以及第五代通信技术的标准制定日趋完善。新无线(New Radio，NR)中定义了3种状态，包括空闲(idle)态、非激活(inactive)态、连接(connected)态。MBS(Multicast and Broadcast Service，多播广播业务)业务包括组播业务(多播业务)，组播业务是将相同的内容传输给多个接收方。如何对非激活态组播业务进行配置，目前没有相关的解决方案。
发明内容
为克服相关技术中存在的问题，本公开提供一种资源配置方法、装置、存储介质以及终端。
根据本公开实施例的第一方面，提供一种资源配置方法，所述方法包括：
释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
根据本公开实施例的第二方面，提供一种资源配置方法，所述方法包括：
配置组播业务配置信息，并将所述组播业务配置信息发送给终端设备，所述终端设备用于释放或保留非激活态组播业务配置信息，并使用所述组播业务配置信息。
根据本公开实施例的第三方面，提供一种资源配置装置，所述装置包括：
配置模块，配置为释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
根据本公开实施例的第四方面，提供一种资源配置装置，所述装置包括：
发送模块，配置为配置组播业务配置信息，并将所述组播业务配置信息发送给终端设备，所述终端设备用于释放或保留非激活态组播业务配置信息，并使用所述组播业务配置信息。
根据本公开实施例的第五方面，提供一种终端设备，包括：
第一处理器；
用于存储第一处理器可执行指令的第一存储器；
其中，所述第一处理器被配置为执行所述可执行指令，以实现本公开第一方面所提供的资源配置方法。
根据本公开实施例的第六方面，提供一种网络侧设备，包括：
第二处理器；
用于存储第二处理器可执行指令的第二存储器；
其中，所述第二处理器被配置为执行所述可执行指令，以实现本公开第二方面所提供的资源配置方法。
根据本公开实施例的第七方面，提供一种计算机可读存储介质，其上存储有计算机程序指令，该程序指令被处理器执行时实现本公开第一方面或第二方面所提供的资源配置方法的步骤。
本公开的实施例提供的技术方案可以包括以下有益效果：通过释放或保留非激活态组播配置信息，并利用网络侧设备配置的组播业务配置，本申请可以在非激活态下执行组播业务数据接收。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限 制本公开。
附图说明
本公开上述的和/或附加的方面和优点从下面结合附图对实施例的描述中将变得明显和容易理解，其中：
图1是RRC连接态、非激活态以及空闲态的转换示意图。
图2是根据一些实施例示出的一种资源配置方法所适用的应用场景。
图3是根据一些实施例示出的一种资源配置方法的流程图。
图4是根据另一些实施例示出的一种资源配置方法的流程图。
图5是根据又一些实施例示出的一种资源配置方法的流程图。
图6是根据再一些实施例示出的一种资源配置方法的流程图。
图7是根据又一些实施例示出的一种资源配置方法的流程图。
图8是根据又一些实施例示出的一种资源配置方法的通信时序图。
图9是根据再一些实施例示出的一种资源配置方法的流程图。
图10是根据又一些实施例示出的一种资源配置方法的流程图。
图11是根据又一些实施例示出的一种资源配置方法中指定信令为RRC恢复信令时的通信时序图。
图12是根据又一些实施例示出的一种资源配置方法中指定信令为RRC重配置信令时的通信时序图。
图13是根据又一些实施例示出的一种资源配置方法中指定信令为包含挂起配置的RRC释放信令。
图14是根据一些实施例示出的一种资源配置方法的流程图。
图15是根据一些实施例示出的一种资源配置装置的框图。
图16是根据一些实施例示出的一种资源配置装置的框图。
图17是根据一些实施例示出的一种终端设备的框图。
图18是根据一些实施例示出的一种网络侧设备的框图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本公开相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本公开的一些方面相一致的装置和方法的例子。
为便于理解本申请实施例，以下对本申请实施例的部分用语进行解释说明，以便于本领域技术人员理解。
1)终端设备
终端设备，包括向用户提供语音和/或数据连通性的设备，具体的，包括向用户提供语音的设备，或包括向用户提供数据连通性的设备，或包括向用户提供语音和数据连通性的设备。例如可以包括具有无线连接功能的手持式设备、或连接到无线调制解调器的处理设备。作为一种方式，终端设备可以包括用户设备(user equipment，UE)、无线终端设备、移动终端设备、或用户装备(user device)等。
2)网络侧设备
网络侧设备又称为无线接入网设备，该网络侧设备是一种将终端设备接入到无线网络的设备，其既可以包括接入网设备，也可以包括核心网设备，还可以包括服务供应商的设备(如服务器)等。例如，网络侧设备包括但不限于：传输点(transmission reception point，TRP)、 基站(如，gNB)、无线网络控制器(radionetwork controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、BTS(base transceiver station)、HeNB(home evolved NodeB)，或HNB(home NodeB)、基带单元(baseband uit，BBU)等。
终端设备在接入网络侧设备的过程中或者接入网络侧设备后，可以和网络侧设备进行RRC(radio resource control，无线资源控制)建立过程。终端设备和网络侧设备建立了RRC连接后，该终端设备的RRC状态为RRC连接(RRC_CONNECTED)态。
随后，终端设备的RRC状态可以在以下状态中进行转换：RRC空闲态(RRC_IDLE)、RRC连接态(RRC_CONNECTED)和RRC非激活态(RRC_INACTIVE)，RRC各状态的转换可以如图1所示，从图1知道，RRC的连接态、非激活态以及空闲态之间可以相互转换。例如，终端设备可以从非激活态转换至连接态，或者也可以从非激活转换为空闲态等。
3)RRC连接态
RRC连接态(connected)也可以简称为连接态，在本文中，“连接态”和“RRC连接态”，是同一概念，两种称呼可以互换。终端设备与网络建立了RRC连接，可以进行数据传输。
4)RRC空闲态
RRC空闲(idle)态也可以简称为空闲态。在本文中，“空闲态”和“RRC空闲态”，是同一概念，两种称呼可以互换。RRC空闲态是指终端设备与网络侧设备之间的RRC连接未建立，且终端设备对应的网络侧设备与核心网设备之间的连接未建立。当终端设备处于空闲态时，若有数据需要传输，需要先建立终端设备与网络侧设备之间的连接，以及网络侧设备与核心网设备之间的连接，才能进行数据传输。
5)RRC非激活态
RRC非激活((inactive)态也可以简称为非激活态。在本文中，“去活动态”、“去激活态”、“非激活态”、“RRC非激活态”或“RRC去激活态”等，是同一概念，这几种称呼可以互换)。RRC非激活态是指终端设备与网络侧设备之间的RRC连接已断开，但是终端设备对应的网络侧设备与核心网设备之间的连接未断开。当终端设备处于去激活状态时，若有数据需要传输，需要先恢复终端设备与网络侧设备之间的RRC连接，才能进行数据传输。
下面对本实施例提供的一种网络切换方法的应用环境进行说明，如图2所示，该应用环境可以包括终端设备01和网络侧设备02，其中，终端设备01与网络侧设备02可以通过有线或者无线的方式进行连接。
其中，终端设备01可以是用户设备(user equipment，UE)或者移动台(mobile station，MS)或者移动终端(mobile terminal，MT)等。具体的，终端设备01可以是手机(mobile phone)、平板电脑或带无线收发功能的电脑，还可以是虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制中的无线终端、无人驾驶中的无线终端、远程医疗中的无线终端、智能电网中的无线终端、智慧城市(smart city)中的无线终端、智能家居、车载终端等。
网络侧设备02可以包括接入网设备，也可以包括核心网设备，还可以包括服务供应商的设备(如服务器)等，不予限制。网络侧设备02主要用于实现终端设备01的资源调度、无线资源管理、无线接入控制等功能。具体的，网络侧设备02可以为小型基站、无线接入点、收发点(transmission receive point，TRP)、传输点(transmission point，TP)以及某种其它接入节点中的任一节点。
目前MBS业务的发送模式包括两种，第一种发送模式为组播(多播)发送模式，在组播发送模式下，终端设备进入连接态(RRC_CONNECTED)，以接收MBS业务的发送配置信息，如此才能接收MBS业务，网络侧设备也可以通过UE专属信令将MBS业务的接收配置信息发送给终端设备。第二种发送模式为广播发送模式，在广播发送模式下，终 端设备可以在空闲态(IDLE)、非激活态(INACTIVE)或连接态(CONNECTED)接收MBS业务的发送配置信息，并接收MBS业务，网络侧设备可以通过系统信息，如SIB(System Information Block，系统信息块)和MBS控制信道信息，如MCCH(MBS Control Channel，MBS控制信道)，将MBS业务的接收配置信息发送给终端设备。
可见，现有技术无法支持非激活组播业务的接收，当终端设备处于非激活态时，无法执行组播业务数据的接收。另外，当终端设备进入连接态时，对非激活态组播业务配置的处理方式也没有相关的规定。
图3是根据一些实施例示出的一种资源配置方法的流程图。如图3所示，该资源配置方法可以用于图2中的终端设备中，包括以下步骤。
在步骤S110中，终端设备释放非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
本申请实施例中，终端设备可以支持非激活态组播业务接收，即当终端设备处于非激活态时，其也能够继续执行组播业务数据接收。可见，终端设备在处于非激活时可以获取到非激活态组播业务配置，并利用该非激活组播业务配置进行非激活态组播业务。
作为一种可选地方式，本申请在进行资源配置时可以释放非激活态组播业务配置信息，所述非激活态组播业务配置信息可以是终端设备处于非激活态时获取的配置信息。
可选地，终端设备释放非激活态组播业务配置信息后，其也可以使用网络侧设备配置的组播业务配置信息，网络侧设备配置的组播业务配置信息可以包括以下至少一项：用于非激活态组播业务接收的配置信息，以及用于连接态组播业务接收的配置信息。换句话说，网络侧设备配置的组播业务配置信息可以包括用于非激活态组播业务接收的配置信息，也可以包括用于连接态组播业务接收的配置信息，或者可以包括用于非激活态组播业务接收的配置信息和连接态组播业务接收的配置信息。
作为一种可选地方式，释放非激活态组播业务配置信息后，本申请可以使用非激活态组播业务接收的配置信息，即利用网络侧设备传输的非激活态组播业务接收的配置信息替换终端设备中非激活态组播业务配置信息。
可选地，释放非激活态组播业务配置信息后，本申请也可以使用连接态组播业务接收的配置信息，即利用网络侧设备传输的连接态组播业务接收的配置信息替换终端设备中非激活态组播业务配置信息。
可选地，释放非激活态组播业务配置信息后，本申请也可以使用非激活态组播业务接收的配置信息和连接态组播业务接收的配置信息，即利用网络侧设备传输的非激活态组播业务接收的配置信息和连接态组播业务接收的配置信息替换终端设备中非激活态组播业务配置信息。具体如何使用网络侧设备配置的组播业务配置信息，这里不进行明确限制，可根据实际情况进行选择。例如，终端设备在处于非激活态时，若接收到网络侧设备传输的非激活态组播业务接收的配置信息，则可以利用网络侧设备传输的所述非激活态组播业务接收的配置信息替换终端设备中非激活态组播业务配置信息。
本申请实施例中，终端设备释放非激活态组播业务配置信息的操作可以称作是全配置操作，在执行全配置操作时，终端设备可以释放非激活组播业务配置，并使用网络侧设备配置的组播业务配置信息。
本申请实施例规定了，终端设备对非激活态组播业务配置的处理方式可以是释放非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息，如此可以保证配置信息的实时性。
图4是根据另一些实施例示出的一种资源配置方法的流程图。如图4所示，该资源配置方法可以用于图2中的终端设备中，包括以下步骤。
在步骤S210中，终端设备保留非激活态组播业务配置信息，并使用网络侧设备配置 的组播业务配置信息。
作为一种可选地方式，本申请在进行资源配置时可以保留非激活态组播业务配置信息，所述非激活态组播业务配置信息可以是终端设备处于非激活态时获取的配置信息。
可选地，终端设备保留非激活态组播业务配置信息后，其也可以使用网络侧设备配置的组播业务配置信息，网络侧设备配置的组播业务配置信息可以包括以下至少一项：用于非激活态组播业务接收的配置信息，以及用于连接态组播业务接收的配置信息。换句话说，网络侧设备配置的组播业务配置信息可以包括用于非激活态组播业务接收的配置信息，也可以包括用于连接态组播业务接收的配置信息，或者可以包括用于非激活态组播业务接收的配置信息和连接态组播业务接收的配置信息。
作为一个示例，终端在进行资源配置时，本申请可以保留已配置的非激活态组播业务配置信息，并使用连接态组播业务接收的配置信息，所述用于连接态组播业务接收的配置信息可以是网络侧设备发送给终端设备的。
作为一个示例，终端在进行资源配置时，本申请可以保留已配置的非激活态组播业务配置信息，并使用非激活态组播业务接收的配置信息，所述用于非激活态组播业务接收的配置信息可以是网络侧设备发送给终端设备的。
作为一个示例，终端在进行资源配置时，本申请可以保留已配置的非激活态组播业务配置信息，并使用用于非激活态组播业务接收的配置信息和连接态组播业务接收的配置信息，所述用于非激活态组播业务接收的配置信息和连接态组播业务接收的配置信息可以是网络侧设备发送给终端设备的。
本申请实施例中，终端设备保留非激活态组播业务配置信息的操作可以称作是增量配置操作，在执行增量配置操作时，终端设备可以保留非激活组播业务配置，并使用网络侧设备配置的组播业务配置信息。
本申请实施例规定了，终端设备对非激活态组播业务配置的处理方式可以是保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息，如此可以减小不必要信令的传输，进而可以降低网络传输的负担。
图5是根据又一些实施例示出的一种资源配置方法的流程图。如图5所示，该资源配置方法可以用于图2中的终端设备中，包括以下步骤。
在步骤S310中，终端设备释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
本申请实施例中，终端设备可以释放非激活态组播业务配置信息，也可以保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。终端设备具体是释放非激活态组播业务配置信息还是保留非激活态组播业务配置信息，这里不进行明确限制，可根据实际情况进行选择。例如，终端设备可以根据协议规定确定释放还是保留非激活态组播业务配置信息。又如，终端设备也可以根据网络侧设备的指示来确定释放还是保留非激活态组播业务配置信息。
本申请实施例规定了，终端设备对非激活态组播业务配置的处理方式可以是释放非激活态组播业务配置信息，或者可以是保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息，如此可以提高对非激活态组播业务配置的处理的灵活性。
图6是根据再一些实施例示出的一种资源配置方法的流程图。如图6所示，该资源配置方法可以用于图2中的终端设备中，包括以下步骤。
在步骤S410中，终端设备根据协议规定确定释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
作为一种可选地方式，终端设备可以根据协议规定确定释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。作为一个具体的实施方式，当协 议规定释放非激活态组播业务配置信息，本申请实施例则可以释放非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
作为另一个具体的实施方式，当协议规定保留非激活态组播业务配置信息，本申请实施例则可以保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
本申请实施例中，协议规定可以是预先设置的，每次终端设备在执行资源配置时，均可以基于该协议规定来确定是释放非激活态组播业务配置信息还是保留非激活态组播业务配置信息。
本申请实施例规定了，终端设备可以基于协议规定来确定对非激活态组播业务配置的处理方式，协议规定不同，则对应对非激活态组播业务配置的处理方式也不相同，如此可以进一步提高对非激活态组播业务配置的处理的灵活性。
图7是根据又一些实施例示出的一种资源配置方法的流程图。如图7所示，该资源配置方法可以用于图2中的终端设备中，包括以下步骤。
在步骤S510中，终端设备接收网络侧设备发送的配置指示信息。
作为一种可选地方式，终端设备可以基于网络侧设备传输的配置指示信息来确定释放或保留非激活态组播业务配置信息。具体的，终端设备可以接收网络侧设备发送的配置指示信息，并基于该配置指示信息来确定释放或保留非激活态组播业务配置信息。其中，配置指示信息可以是网络侧设备基于终端设备的网络情况，或者是基于非激活态组播业务接收的配置信息以及连接态组播业务接收的配置信息等的情况确定的信息。
在步骤S520中，终端设备根据配置指示信息确定释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
本申请实施例中，终端设备接收的配置指示信息不同，则对应的对非激活态组播业务配置的处理方式也可能不相同。
作为一个示例，终端设备接收到网络侧设备发送的配置指示信息为全配置(fullConfig)消息时，其可以释放非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
作为另一个示例，终端设备接收到网络侧设备发送的配置指示信息为增量配置消息时，其可以保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
本申请实施例规定了，终端设备可以通过网络侧设备传输的配置指示信息来确定对非激活态组播业务配置的处理方式，网络侧设备传输的配置指示信息不同，则对应对非激活态组播业务配置的处理方式也不相同，如此可以更加的灵活的对非激活态组播业务配置进行处理。
图8是根据又一些实施例示出的一种资源配置方法的通信时序图。如图8所示，终端设备可以接收网络侧设备发送的组播业务配置信息和配置指示信息。在此基础上，终端设备可以根据配置信息确定释放还或保留非激活态组播业务配置信息，并使用网络侧设备传输的组播业务配置信息。
需要说明的是，若终端设备既存在协议规定，又接收到网络侧设备发送的配置指示信息，并且协议规定的处理方式与网络侧设备发送的处理方式不相同，本申请实施例则可以根据网络侧发送的配置指示信息确定释放或保留非激活态组播业务配置信息，如此可以提高资源配置的准确性。
图9是根据再一些实施例示出的一种资源配置方法的流程图。如图9所示，该资源配置方法可以用于图2中的终端设备中，包括以下步骤。
在步骤S610中，当终端设备的状态发生改变时，终端设备释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
作为一种可选地方式，本申请实施例在确定终端设备的状态发生改变的情况下，可以 释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
通过上述介绍知道，终端设备的状态包括三种状态，这三种状态分别是非激活态(inactive)、连接态(connected)和空闲态(idle)。终端设备的状态发生改变可以是终端设备从非激活态(inactive)进入连接态(connected)。
作为一个具体的实施方式，当终端设备从非激活态(inactive)进入连接态(connected)时，本申请实施例可以释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
可选地，终端设备的状态发生改变也可以是终端设备从非激活态(inactive)进入非激活态(inactive)。具体的，终端设备在处于非激活态(inactive)时，其可以向网络侧设备发送连接请求。在接收到网络侧设备发送的包含挂起配置的RRC释放信令的情况下，终端设备的状态可以进入非激活态(inactive)，即终端设备的状态从非激活态(inactive)进入非激活态(inactive)。
作为另一个具体的实施方式，当终端设备从非激活态(inactive)进入非激活态(inactive)时，本申请实施例可以释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
本申请实施例中，终端设备的状态发生改变，也可以是其他状态的改变。例如，状态发生改变可以是从连接态(connected)进入非激活态(inactive)。终端设备的状态发生改变具体包括哪些这里就不再进行赘述，可根据实际情况进行选择。
作为一种可选地方式，终端设备的状态发生改变时，本申请实施例可以根据协议规定确定释放或保留所述非激活态组播业务配置信息。作为一个示例，终端设备的状态发生改变时，若协议规定释放非激活态组播业务配置信息，本申请则释放非激活态组播业务配置信息。
作为另一种可选地方式，终端设备的状态发生改变时，本申请实施例也可以根据网络侧设备发送的配置指示信息确定释放或保留非激活态组播业务配置信息。作为一个示例，终端设备的状态发生改变时，若接收到网络侧发送的配置指示信息是全配置，本申请则可以释放非激活态组播业务配置信息。
本申请实施例规定了，终端设备可以根据终端设备的状态变化来对非激活态组播业务配置进行处理，即当终端设备的状态发生改变时，本申请可以释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息，如此可以提高资源配置的灵活性和准确性。
图10是根据又一些实施例示出的一种资源配置方法的流程图。如图10所示，该资源配置方法可以用于图2中的终端设备中，包括以下步骤。
在步骤S710中，当从网络侧设备接收到指定信令时，终端设备释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
作为一种可选地方式，本申请实施例在确定终端设备接收到网络侧设备传输的指定信令的情况下，可以释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
本申请实施例中，指定信令可以包括RRC恢复信令(RRCResume)、RRC重配置信令(RRCReconfiguration)和包含挂起配置的RRC释放信令(RRCRelease with Suspend configuration)中的至少一个。
作为一个具体的实施方式，当已配置的非激活态组播业务配置信息携带于挂起配置中时，若终端设备接收到网络侧设备传输的RRC恢复信令(RRCResume)，则可以保留非激活态组播业务配置信息，即携带在挂起配置中的非激活态组播业务不能被释放。
图11是根据又一些实施例示出的一种资源配置方法中指定信令为RRC恢复信令 (RRCResume)时的通信时序图。如图11所示，终端设备可以接收网络侧设备发送的RRC恢复信令(RRCResume)。在此基础上，终端设备可以释放或保留非激活态组播业务配置信息，并使用RRC恢复信令(RRCResume)中包含的网络侧设备配置的组播业务配置信息。
图12是根据又一些实施例示出的一种资源配置方法中指定信令为RRC重配置信令(RRCReconfiguration)时的通信时序图。如图12所示，终端设备可以接收网络侧设备发送的RRC重配置信令(RRCReconfiguration)。在此基础上，终端设备可以释放或保留非激活态组播业务配置信息，并使用RRC重配置信令(RRCReconfiguration)中包含的网络侧设备配置的组播业务配置信息。
图13是根据又一些实施例示出的一种资源配置方法中指定信令为包含挂起配置的RRC释放信令(RRCRelease with Suspend configuration)时的通信时序图。如图13所示，终端设备可以接收网络侧设备发送的包含挂起配置的RRC释放信令(RRCRelease with Suspend configuration)。在此基础上，终端设备可以根据释放或保留非激活态组播业务配置信息，并使用包含挂起配置的RRC释放信令(RRCRelease with Suspend configuration)中包含的网络侧设备配置的组播业务配置信息。
通过上述介绍知道，指定信令中可以包括网络侧设备配置的组播业务配置信息，终端设备在接收到指定信令时，可以释放或保留非激活态组播业务配置信息，同时可以使用指定信令中包含的网络侧设备配置的组播业务配置信息。
作为一种可选地方式，终端设备从网络侧设备接收到指定信令时，本申请实施例可以根据协议规定确定释放或保留所述非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。作为一个示例，终端设备从网络侧设备接收到指定信令时，若协议规定释放非激活态组播业务配置信息，本申请则可以释放非激活态组播业务配置信息。
作为另一种可选地方式，终端设备从网络侧设备接收到指定信令时，本申请实施例也可以根据网络侧设备发送的配置指示信息确定释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。作为一个示例，终端设备从网络侧设备接收到指定信令时，若接收到网络侧发送的配置指示信息是全配置，本申请则可以释放非激活态组播业务配置信息。
本申请实施例规定了，终端设备可以根据其从网络侧设备接收到的指定信令对非激活态组播业务配置进行处理，即当终端设备从网络侧设备接收到指定信令时，本申请可以释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息，如此可以提高资源配置的灵活性和准确性。
图14是根据一些实施例示出的一种资源配置方法的流程图。如图14所示，该资源配置方法可以用于图2中的网络侧设备中，包括以下步骤。
在步骤S810中，网络侧设备配置组播业务配置信息，并将组播业务配置信息发送给终端设备，终端设备用于释放或保留非激活态组播业务配置信息，并使用组播业务配置信息。
本申请实施例中，网络侧设备可以配置组播业务配置信息，并将组播业务配置信息发送给终端设备。其中，终端设备可用于释放或保留非激活态组播业务配置信息，并使用网络侧设备传输的组播业务配置信息。
另外，网络侧设备配置的组播业务配置信息包括用于非激活态组播业务接收的配置信息和用于连接态组播业务接收的配置信息中的至少一个。
可选地，网络侧设备可以获取配置指示信息，并将该配置指示信息发送至终端设备，以指示终端设备根据该配置指示信息确定释放或保留非激活态组播业务配置信息。可见，配置指示信息用于指示终端设备释放或保留非激活态组播业务配置信息。
可选地，网络侧设备也可以向终端设备发送指定信令，以使终端设备释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息，即终端设备用于在接收到指定信令时释放或保留非激活态组播业务配置信息。其中，指定信令可以包括RRC恢复信令、RRC重配置信令和包含挂起配置的RRC释放信令中的至少一个。
图15是根据一些实施例示出的一种资源配置装置900的框图。参照图15，该资源配置装置900应用于终端设备，该资源配置装置900可以包括配置模块910。
该配置模块910被配置为释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
在一些实施方式中，所述网络侧设备配置的组播业务配置信息包括用于非激活态组播业务接收的配置信息和用于连接态组播业务接收的配置信息中的至少一个。
在一些实施方式中，配置模块910可以被配置为根据协议规定确定释放或保留所述非激活态组播业务配置信息。
在一些实施方式中，配置模块910，可以包括：
接收子模块，被配置为接收所述网络侧设备发送的配置指示信息；
确定子模块，被配置为根据所述配置指示信息确定释放或保留非激活态组播业务配置信息。
在一些实施方式中，配置模块910还可以被配置为当所述终端设备的状态发生改变时，释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
在一些实施方式中，所述终端设备的状态发生改变包括所述终端设备从非激活态进入连接态，或者所述终端设备从非激活态进入非激活态。
在一些实施方式中，配置模块910还可以被配置为当从所述网络侧设备接收到指定信令时，释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
在一些实施方式中，指定信令包括RRC恢复信令、RRC重配置信令和包含挂起配置的RRC释放信令中的至少一个。
图16是根据一些实施例示出的一种资源配置装置1000的框图。参照图16，该资源配置装置1000应用于网络侧设备，该资源配置装置1000可以包括发送模块1010。
该发送模块1010，被配置为配置组播业务配置信息，并将所述组播业务配置信息发送给终端设备，所述终端设备用于释放或保留非激活态组播业务配置信息，并使用所述组播业务配置信息。
在一些实施方式中，所述组播业务配置信息包括用于非激活态组播业务接收的配置信息和用于连接态组播业务接收的配置信息中的至少一个。
在一些实施方式中，资源配置装置1000还可以包括：
配置指示发送模块，被配置为向所述终端设备发送配置指示信息，以指示所述终端设备根据所述配置指示信息确定释放或保留非激活态组播业务配置信息。
在一些实施方式中，资源配置装置1000还可以包括：
指定信令发送模块，被配置为向所述终端设备发送指定信令，所述终端设备用于在接收到所述指定信令时释放或保留所述非激活态组播业务配置信息，并使用所述组播业务配置信息。
在一些实施方式中，所述指定信令包括RRC恢复信令、RRC重配置信令和包含挂起配置的RRC释放信令中的至少一个。
关于上述实施例中的装置，其中各个模块执行操作的具体方式已经在有关该方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开还提供一种计算机可读存储介质，其上存储有计算机程序指令，该程序指令被 处理器执行时实现本公开提供的资源配置方法的步骤。
图17是根据一些实施例示出的一种终端设备的框图。例如，终端设备1100可以是移动电话，计算机，数字广播终端，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理，智能汽车等。
参照图17，终端设备1100可以包括以下一个或多个组件：第一处理组件1102，第一存储器1104，第一电源组件1106，多媒体组件1108，音频组件1110，第一输入/输出接口1112，传感器组件1114，以及通信组件1116。
第一处理组件1102通常控制终端设备1100的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。第一处理组件1102可以包括一个或多个第一处理器1120来执行指令，以完成上述的资源配置方法的全部或部分步骤。此外，第一处理组件1102可以包括一个或多个模块，便于第一处理组件1102和其他组件之间的交互。例如，第一处理组件1102可以包括多媒体模块，以方便多媒体组件1108和第一处理组件1102之间的交互。
第一存储器1104被配置为存储各种类型的数据以支持在终端设备1100的操作。这些数据的示例包括用于在终端设备1100上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。第一存储器1104可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
第一电源组件1106为终端设备1100的各种组件提供电力。第一电源组件1106可以包括电源管理系统，一个或多个电源，及其他与为终端设备1100生成、管理和分配电力相关联的组件。
多媒体组件1108包括在所述终端设备1100和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件1108包括一个前置摄像头和/或后置摄像头。当终端设备1100处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件1110被配置为输出和/或输入音频信号。例如，音频组件1110包括一个麦克风(MIC)，当终端设备1100处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在第一存储器1104或经由通信组件1116发送。在一些实施例中，音频组件1110还包括一个扬声器，用于输出音频信号。
第一输入/输出接口1112为第一处理组件1102和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件1114包括一个或多个传感器，用于为终端设备1100提供各个方面的状态评估。例如，传感器组件1114可以检测到终端设备1100的打开/关闭状态，组件的相对定位，例如所述组件为终端设备1100的显示器和小键盘，传感器组件1114还可以检测终端设备1100或终端设备1100一个组件的位置改变，用户与终端设备1100接触的存在或不存在，终端设备1100方位或加速/减速和终端设备1100的温度变化。传感器组件1114可以 包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件1114还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件1114还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件1116被配置为便于终端设备1100和其他设备之间有线或无线方式的通信。终端设备1100可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件1116经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件1116还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，终端设备1100可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述资源配置方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的第一存储器1104，上述指令可由终端设备1100的第一处理器1120执行以完成上述资源配置方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
在另一示例性实施例中，还提供一种计算机程序产品，该计算机程序产品包含能够由可编程的装置执行的计算机程序，该计算机程序具有当由该可编程的装置执行时用于执行上述的资源配置方法的代码部分。
图18是根据一示例性实施例示出的一种网络侧设备的框图。例如，网络侧设备1200可以被提供为一服务器。参照图18，网络侧设备1200包括第二处理组件1222，其进一步包括一个或多个处理器，以及由第二存储器1232所代表的存储器资源，用于存储可由第二处理组件1222的执行的指令，例如应用程序。第二存储器1232中存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，第二处理组件1222被配置为执行指令，以执行资源配置方法。
网络侧设备1200还可以包括一个第二电源组件1226被配置为执行网络侧设备1200的电源管理，一个有线或无线网络接口1250被配置为将网络侧设备1200连接到网络，和一个第二输入/输出接口1258。网络侧设备1200可以操作基于存储在存储器1232的操作系统，例如Windows Server TM，Mac OS X TM，Unix TM，Linux TM，FreeBSD TM或类似。
本领域技术人员在考虑说明书及实践本公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由下面的权利要求指出。
应当理解的是，本公开并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本公开的范围仅由所附的权利要求来限制。

Claims (18)

  1. 一种资源配置方法，其特征在于，包括：
    释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
  2. 根据权利要求1所述的资源配置方法，其特征在于，所述网络侧设备配置的组播业务配置信息包括用于非激活态组播业务接收的配置信息和用于连接态组播业务接收的配置信息中的至少一个。
  3. 根据权利要求1所述的资源配置方法，其特征在于，所述释放或保留非激活态组播业务配置信息，包括：
    根据协议规定确定释放或保留所述非激活态组播业务配置信息。
  4. 根据权利要求1所述的资源配置方法，其特征在于，所述释放或保留非激活态组播业务配置信息，还包括：
    接收所述网络侧设备发送的配置指示信息；
    根据所述配置指示信息确定释放或保留非激活态组播业务配置信息。
  5. 根据权利要求1所述的资源配置方法，其特征在于，所述方法应用于终端设备，所述释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息，包括：
    当所述终端设备的状态发生改变时，释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
  6. 根据权利要求5所述的资源配置方法，其特征在于，所述终端设备的状态发生改变包括所述终端设备从非激活态进入连接态，或者所述终端设备从非激活态进入非激活态。
  7. 根据权利要求1所述的资源配置方法，其特征在于，所述释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息，包括：
    当从所述网络侧设备接收到指定信令时，释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
  8. 根据权利要求7所述的资源配置方法，其特征在于，所述指定信令包括RRC恢复信令、RRC重配置信令和包含挂起配置的RRC释放信令中的至少一个。
  9. 一种资源配置方法，其特征在于，包括：
    配置组播业务配置信息，并将所述组播业务配置信息发送给终端设备，所述终端设备用于释放或保留非激活态组播业务配置信息，并使用所述组播业务配置信息。
  10. 根据权利要求9所述的资源配置方法，其特征在于，所述组播业务配置信息包括用于非激活态组播业务接收的配置信息和用于连接态组播业务接收的配置信息中的至少一个。
  11. 根据权利要求9所述的资源配置方法，其特征在于，所述方法还包括：
    向所述终端设备发送配置指示信息，以指示所述终端设备根据所述配置指示信息确定释放或保留非激活态组播业务配置信息。
  12. 根据权利要求9所述的资源配置方法，其特征在于，所述方法还包括：
    向所述终端设备发送指定信令，所述终端设备用于在接收到所述指定信令时释放或保留所述非激活态组播业务配置信息，并使用所述组播业务配置信息。
  13. 根据权利要求12所述的资源配置方法，其特征在于，所述指定信令包括RRC恢复信令、RRC重配置信令和包含挂起配置的RRC释放信令中的至少一个。
  14. 一种资源配置装置，其特征在于，包括：
    配置模块，配置为释放或保留非激活态组播业务配置信息，并使用网络侧设备配置的组播业务配置信息。
  15. 一种资源配置装置，其特征在于，包括：
    发送模块，配置为配置组播业务配置信息，并将所述组播业务配置信息发送给终端设备，所述终端设备用于释放或保留非激活态组播业务配置信息，并使用所述组播业务配置信息。
  16. 一种终端设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为执行所述可执行指令，以实现如权利要求1至8中任一项所述的资源配置方法。
  17. 一种网络侧设备，其特征在于，包括：
    处理器；
    用于存储处理器可执行指令的存储器；
    其中，所述处理器被配置为执行所述可执行指令，以实现如权利要求9至13中任一所述的资源配置方法。
  18. 一种计算机可读存储介质，其上存储有计算机程序指令，其特征在于，该程序指令被处理装置执行时实现权利要求1至13中任一项所述的资源配置方法的步骤。
PCT/CN2022/111539 2022-08-10 2022-08-10 资源配置方法、装置、存储介质以及终端 WO2024031458A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/111539 WO2024031458A1 (zh) 2022-08-10 2022-08-10 资源配置方法、装置、存储介质以及终端
CN202280002626.9A CN117882471A (zh) 2022-08-10 2022-08-10 资源配置方法、装置、存储介质以及终端

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/111539 WO2024031458A1 (zh) 2022-08-10 2022-08-10 资源配置方法、装置、存储介质以及终端

Publications (1)

Publication Number Publication Date
WO2024031458A1 true WO2024031458A1 (zh) 2024-02-15

Family

ID=89850283

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/111539 WO2024031458A1 (zh) 2022-08-10 2022-08-10 资源配置方法、装置、存储介质以及终端

Country Status (2)

Country Link
CN (1) CN117882471A (zh)
WO (1) WO2024031458A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021077434A1 (zh) * 2019-10-26 2021-04-29 华为技术有限公司 一种通信方法及装置
CN113498022A (zh) * 2020-03-19 2021-10-12 华为技术有限公司 配置信息更新方法及装置
WO2021212413A1 (zh) * 2020-04-23 2021-10-28 华为技术有限公司 一种密钥的传输方法及装置
CN114501340A (zh) * 2020-10-23 2022-05-13 中国移动通信有限公司研究院 Mbs接收方法、发送方法、装置、终端及基站
CN114731642A (zh) * 2019-12-17 2022-07-08 华为技术有限公司 一种通信方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021077434A1 (zh) * 2019-10-26 2021-04-29 华为技术有限公司 一种通信方法及装置
CN114731642A (zh) * 2019-12-17 2022-07-08 华为技术有限公司 一种通信方法及装置
CN113498022A (zh) * 2020-03-19 2021-10-12 华为技术有限公司 配置信息更新方法及装置
WO2021212413A1 (zh) * 2020-04-23 2021-10-28 华为技术有限公司 一种密钥的传输方法及装置
CN114501340A (zh) * 2020-10-23 2022-05-13 中国移动通信有限公司研究院 Mbs接收方法、发送方法、装置、终端及基站

Also Published As

Publication number Publication date
CN117882471A (zh) 2024-04-12

Similar Documents

Publication Publication Date Title
CN107637123B (zh) 信息传递方法、装置及计算机可读存储介质
WO2020019351A1 (zh) 传输配置指示的配置方法及装置
US10098166B2 (en) Method and device for wireless connection establishment
EP3163803B1 (en) Method and device for establishing connection
US11323977B2 (en) Method, apparatus, user equipment and base station for implementing location area update
US10694572B2 (en) Methods and devices for controlling states of user equipment
JP6383109B2 (ja) ネットワーク接続方法、ネットワーク接続機器、端末、通信機器、ネットワーク接続システム、プログラム及び記録媒体
EP3125615B1 (en) Method, apparatus and system for a smart device to access a router
US11792659B2 (en) Method and device for using network slice
US20220295590A1 (en) Inactivity timer control method and device
EP4175338A1 (en) Communication processing method, communication processing apparatus and storage medium
WO2020097783A1 (zh) 资源配置方法及装置
WO2018209657A1 (zh) 降低用户设备温度的方法、装置、基站和用户设备
WO2019119421A1 (zh) 小区接入方法、装置及存储介质
US20160308869A1 (en) Method and Device for Controlling Access
EP3280217B1 (en) Method and device for establishing service connection
WO2024031458A1 (zh) 资源配置方法、装置、存储介质以及终端
WO2022067766A1 (zh) 定位参考信号配置方法、配置装置及存储介质
WO2022120611A1 (zh) 一种参数配置方法、参数配置装置及存储介质
WO2022036610A1 (zh) 一种通信方法、通信装置及存储介质
US20240089801A1 (en) Application function session processing method, apparatus and storage medium
WO2024011528A1 (zh) 端口切换、端口切换指示方法和装置
WO2024045197A1 (zh) 寻呼提前指示pei方法、装置、存储介质以及终端设备
WO2024060249A1 (zh) Scg配置方法、装置、存储介质、用户设备以及网络侧设备
WO2023226056A1 (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: 22954433

Country of ref document: EP

Kind code of ref document: A1