WO2023133843A1 - 一种确定配置信息的方法及装置、终端设备 - Google Patents
一种确定配置信息的方法及装置、终端设备 Download PDFInfo
- Publication number
- WO2023133843A1 WO2023133843A1 PCT/CN2022/072144 CN2022072144W WO2023133843A1 WO 2023133843 A1 WO2023133843 A1 WO 2023133843A1 CN 2022072144 W CN2022072144 W CN 2022072144W WO 2023133843 A1 WO2023133843 A1 WO 2023133843A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- mbs
- terminal device
- configuration information
- rrc
- cell
- Prior art date
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 embodiments of the present application relate to the field of mobile communication technologies, and in particular to a method and device for determining configuration information, and a terminal device.
- NR New Radio
- MMS Multimedia Broadcast Service
- a terminal device can only receive multicast MBS services in a radio resource control (Radio Resource Control, RRC) connection state.
- RRC Radio Resource Control
- the terminal equipment can receive the multicast MBS service in the RRC inactive state, and how the terminal equipment receives the multicast MBS service in the RRC inactive state needs to be perfected.
- Embodiments of the present application provide a method and device for determining configuration information, a terminal device, a chip, a computer-readable storage medium, a computer program product, and a computer program.
- the terminal device When performing cell selection and reselection to a target cell, the terminal device determines target MBS configuration information, and receives a multicast MBS service based on the target MBS configuration information.
- the device for determining configuration information provided in the embodiment of the present application is applied to a terminal device, and the device includes:
- An acquiring unit configured to determine target MBS configuration information when the terminal device performs cell selection and reselection to the target cell
- a communication unit configured to receive multicast MBS services based on the target MBS configuration information.
- the terminal device provided in the embodiment of the present application includes a processor and a memory.
- the memory is used to store a computer program
- the processor is used to call and run the computer program stored in the memory to execute the above-mentioned method for determining configuration information.
- the chip provided in the embodiment of the present application is used to implement the above-mentioned method for determining configuration information.
- the chip includes: a processor, configured to invoke and run a computer program from the memory, so that the device installed with the chip executes the above-mentioned method for determining configuration information.
- the computer-readable storage medium provided by the embodiment of the present application is used for storing a computer program, and the computer program enables a computer to execute the above-mentioned method for determining configuration information.
- the computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the above-mentioned method for determining configuration information.
- the computer program provided by the embodiment of the present application when running on a computer, enables the computer to execute the above-mentioned method for determining configuration information.
- the terminal device can determine the target MBS configuration information and receive the multicast MBS service based on the target MBS configuration information when performing cell selection and reselection to the target cell in the RRC inactive state. In this way, the terminal The device can continue to receive the multicast MBS service in the RRC inactive state.
- FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application
- Fig. 2 is the schematic diagram of the protocol stack corresponding to the PTM mode and the PTP mode of the embodiment of the present application;
- FIG. 3 is a schematic flowchart of a method for determining configuration information provided by an embodiment of the present application
- FIG. 4 is a flow chart of obtaining updated MBS configuration information during the RRC recovery process provided by the embodiment of the present application
- Fig. 5 is a schematic structural composition diagram of a device for determining configuration information provided by an embodiment of the present application
- FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
- FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.
- Fig. 8 is a schematic block diagram of a communication system provided by an embodiment of the present application.
- FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
- a communication system 100 may include a terminal device 110 and a network device 120 .
- the network device 120 may communicate with the terminal device 110 through an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120 .
- the embodiment of the present application is only described by using the communication system 100 as an example, but the embodiment of the present application is not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (Long Term Evolution, LTE) system, LTE Time Division Duplex (Time Division Duplex, TDD), Universal Mobile Communication System (Universal Mobile Telecommunication System, UMTS), Internet of Things (Internet of Things, IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems, etc.
- LTE Long Term Evolution
- LTE Time Division Duplex Time Division Duplex
- TDD Time Division Duplex
- Universal Mobile Telecommunication System Universal Mobile Telecommunication System
- UMTS Universal Mobile Communication System
- Internet of Things Internet of Things
- NB-IoT Narrow Band Internet of Things
- eMTC enhanced Machine-Type Communications
- the network device 120 may be an access network device that communicates with the terminal device 110 .
- the access network device can provide communication coverage for a specific geographic area, and can communicate with terminal devices 110 (such as UEs) located in the coverage area.
- the network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long-term evolution (Long Term Evolution, LTE) system, or a next-generation radio access network (Next Generation Radio Access Network, NG RAN) device, Either a base station (gNB) in the NR system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 can be a relay station, an access point, a vehicle-mounted device, a wearable Devices, hubs, switches, bridges, routers, or network devices in the future evolution of the Public Land Mobile Network (Public Land Mobile Network, PLMN), etc.
- Evolutional Node B, eNB or eNodeB in a long-term evolution (Long Term Evolution, LTE) system
- NG RAN next-generation radio access network
- gNB base station
- CRAN Cloud Radio Access Network
- the network device 120 can be a relay station, an access point,
- the terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wirelessly.
- the terminal equipment 110 may refer to an access terminal, a user equipment (User Equipment, UE), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, user agent, or user device.
- Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, IoT devices, satellite handheld terminals, Wireless Local Loop (WLL) stations, Personal Digital Assistant , PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolution networks, etc.
- SIP Session Initiation Protocol
- WLL Wireless Local Loop
- PDA Personal Digital Assistant
- the terminal device 110 can be used for device-to-device (Device to Device, D2D) communication.
- D2D Device to Device
- the wireless communication system 100 may also include a core network device 130 that communicates with the base station.
- the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, Access and Mobility Management Function (Access and Mobility Management Function , AMF), and for example, authentication server function (Authentication Server Function, AUSF), and for example, user plane function (User Plane Function, UPF), and for example, session management function (Session Management Function, SMF).
- the core network device 130 may also be a packet core evolution (Evolved Packet Core, EPC) device of the LTE network, for example, a data gateway (Session Management Function+Core Packet Gateway, SMF+PGW- C) Equipment.
- EPC packet core evolution
- SMF+PGW-C can realize the functions of SMF and PGW-C at the same time.
- the above-mentioned core network equipment may be called by other names, or a new network entity may be formed by dividing functions of the core network, which is not limited in this embodiment of the present application.
- Various functional units in the communication system 100 may also establish a connection through a next generation network (next generation, NG) interface to implement communication.
- NG next generation network
- the terminal device establishes an air interface connection with the access network device through the NR interface to transmit user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short); access Network equipment such as the next generation wireless access base station (gNB), can establish a user plane data connection with UPF through NG interface 3 (abbreviated as N3); access network equipment can establish control plane signaling with AMF through NG interface 2 (abbreviated as N2) connection; UPF can establish a control plane signaling connection with SMF through NG interface 4 (abbreviated as N4); UPF can exchange user plane data with the data network through NG interface 6 (abbreviated as N6); AMF can communicate with SMF through NG interface 11 (abbreviated as N11) The SMF establishes a control plane signaling connection; the SMF may establish a control plane signaling connection with the PCF through an NG interface 7 (N7 for short).
- gNB next generation wireless access base station
- Figure 1 exemplarily shows a base station, a core network device, and two terminal devices.
- the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminals within the coverage area.
- the device is not limited in the embodiment of this application.
- FIG. 1 is only an illustration of a system applicable to this application, and of course, the method shown in the embodiment of this application may also be applicable to other systems.
- system and “network” are often used interchangeably herein.
- the term “and/or” in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations.
- the character "/" in this article generally indicates that the contextual objects are an "or” relationship.
- the "indication” mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship.
- A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
- the "correspondence” mentioned in the embodiments of the present application may mean that there is a direct correspondence or an indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated. , configuration and configured relationship.
- the "predefined” or “predefined rules” mentioned in the embodiments of this application can be used by pre-saving corresponding codes, tables or other It is implemented by indicating related information, and this application does not limit the specific implementation.
- pre-defined may refer to defined in the protocol.
- the "protocol” may refer to a standard protocol in the communication field, for example, it may include the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit this .
- 5G 3rd Generation Partnership Project
- eMBB Enhanced Mobile Broadband
- URLLC Ultra-Reliable Low-Latency Communications
- mMTC Massive Machine-Type Communications
- eMBB still aims at users obtaining multimedia content, services and data, and its demand is growing rapidly.
- eMBB may be deployed in different scenarios, such as indoors, urban areas, and rural areas, the capabilities and requirements vary greatly, so it cannot be generalized, and detailed analysis must be combined with specific deployment scenarios.
- Typical applications of URLLC include: industrial automation, electric power automation, telemedicine operations (surgery), traffic safety guarantee, etc.
- the typical characteristics of mMTC include: high connection density, small data volume, delay-insensitive services, low cost and long service life of modules, etc.
- Multimedia Broadcast Multicast Service is a technology that transmits data from one data source to multiple terminal devices by sharing network resources. This technology can effectively use network resources while providing multimedia services to achieve Broadcast and multicast of multimedia services at a higher rate (such as 256kbps).
- 3GPP clearly proposed to enhance the ability to support downlink high-speed MBMS services, and determined the design requirements for the physical layer and air interface.
- eMBMS evolved MBMS
- eMBMS evolved MBMS
- MBSFN Single Frequency Network
- MBSFN uses a unified frequency to transmit service data in all cells at the same time, but To ensure the synchronization between cells. This method can greatly improve the overall signal-to-noise ratio distribution of the cell, and the spectrum efficiency will also be greatly improved accordingly.
- eMBMS implements broadcast and multicast of services based on the IP multicast protocol.
- MBMS In LTE or LTE-Advanced (LTE-Advanced, LTE-A), MBMS only has a broadcast bearer mode, but no multicast bearer mode.
- the multicast-type MBS service refers to the MBS service transmitted in a multicast manner.
- the broadcast-type MBS service refers to the MBS service transmitted by broadcasting.
- the network side configures the configuration information (referred to as MBS configuration information) received by the MBS service through RRC dedicated signaling.
- the MBS configuration information includes at least one of the following: identification information of the MBS, Group-radio network temporary identifier (Group-RNTI, G-RNTI), MBS bearer (MBS Radio Bearer, MRB) configuration, physical channel configuration, feedback resource configuration, etc.
- QoS Quality of Service
- the terminal device needs to receive the multicast MBS service in the RRC connection state.
- the network side configures a multicast control channel (Multicast Control Channel, MCCH) through system messages (such as MBS SIB), configures a multicast transport channel (Multicast Transport Channel, MTCH) through MCCH signaling, and the terminal
- MCCH Multicast Control Channel
- system messages such as MBS SIB
- MTCH Multicast Transport Channel
- the device can receive broadcast MBS services in the RRC connected state, RRC idle state, and RRC inactive state.
- the MBS service is sent to all terminal devices in a certain group.
- the terminal device receives the multicast type MBS service in the RRC connection state, and the terminal device can receive the multicast type in the point-to-multipoint (Point-To-Multipoint, PTM) mode or point-to-point (Point-To-Point, PTP) mode MBS business data.
- the MBS service data in the PTM mode scrambles the corresponding scheduling information through the G-RNTI configured on the network side
- the MBS service data in the PTP mode scrambles the corresponding scheduling information through the C-RNTI.
- PTP point-to-Multipoint
- the base station can deliver the MBS service to all terminal devices in a group through the air interface.
- the base station may deliver the MBS service to all terminal devices in a group through PTP and/or PTM.
- a group includes Terminal 1, Terminal 2, and Terminal 3.
- the base station can deliver the MBS service to Terminal 1 through PTP, deliver the MBS service to Terminal 2 through PTP, and deliver the MBS
- the service is delivered to terminal equipment 3; or, the base station can deliver the MBS service to terminal equipment 1 through PTP, and the MBS service can be delivered to terminal equipment 2 and terminal equipment 3 through PTM; or, the base station can deliver the MBS service to terminal equipment 3 through PTM.
- the MBS service is delivered to terminal device 1, terminal device 2 and terminal device 3.
- a shared GTP tunnel (Shared GTP tunnel) is used between the core network and the base station to transmit the MBS service, that is, both the PTM MBS service and the PTP MBS service share the GTP tunnel.
- the base station delivers MBS service data to UE1 and UE2 in a PTM manner, and delivers MBS service data to UE3 in a PTP manner.
- MBS multicast service For the multicast type MBS service (abbreviated as MBS multicast service), a DRX mechanism is introduced to save energy for terminal equipment.
- MBS DRX or multicast DRX (multicast DRX)
- unicast DRX MBS DRX
- MBS DRX multicast DRX
- unicast DRX MBS DRX
- MBS DRX unicast DRX
- Broadcasting DRX is independent of each other.
- the parameters related to MBS DRX can refer to the following Table 1.
- the network side can configure the parameters shown in Table 1 through RRC signaling, so as to control the MBS DRX operation through these parameters.
- MBS DRX is per G -RNTI or per G-CS-RNTI configuration.
- the DRX activation time includes the running time of the following timers: drx-onDurationTimerPTM, drx-InactivityTimerPTM, drx-RetransmissionTimer-DL-PTM.
- 5G defines a new RRC state, that is, the RRC_INACTIVE state. This state is different from the RRC idle (RRC_IDLE) state and the RRC active (RRC_ACTIVE) state. in,
- RRC_IDLE state (referred to as idle (idle) state): Mobility is cell selection and reselection based on terminal equipment, paging is initiated by the core network (Core Network, CN), and the paging area is configured by the CN. There is no UE context and no RRC connection at the base station side.
- RRC_CONNECTED state (referred to as connected (connected) state): there is an RRC connection, and UE context exists on the base station side and the terminal equipment side.
- the network side knows the location of the terminal equipment at the specific cell level. Mobility is mobility controlled by the network side. Unicast data can be transmitted between the terminal equipment and the base station.
- RRC_INACTIVE state (referred to as inactive (inactive) state): Mobility is cell selection and reselection based on terminal equipment, there is a connection between CN-NR, UE AS context exists on a certain base station, and paging is triggered by RAN , the RAN-based paging area is managed by the RAN, and the network side knows the location of the terminal device based on the RAN-based paging area level.
- the network side configures the terminal device with a paging area of the RAN through RRC dedicated signaling, and the paging area of the RAN may be one cell or multiple cells.
- the terminal equipment moves in this area, it does not need to notify the network side, and follows the mobility behavior in the RRC idle state, that is, the principle of cell selection and reselection.
- the terminal device moves out of the paging area of the RAN, it will trigger the terminal device to restore the RRC connection and reacquire the paging area of the RAN.
- the base station that maintains the connection between RAN and CN for the terminal device will trigger all cells in the paging area of the RAN to send a paging message to the terminal device, so that the terminal device in the RRC inactive state
- the RRC connection can be restored to receive data.
- the terminal device enters the RRC connection state from the RRC inactive state, and there are three situations as follows:
- the network side initiates RAN initial paging, prompting the terminal device to enter the RRC connection state.
- the terminal device itself initiates RAN location area update, such as periodic RAN location update or cross-area location update.
- RAN location area update such as periodic RAN location update or cross-area location update.
- the third is that the terminal equipment needs to send uplink data, prompting the terminal equipment to enter the RRC connection state.
- the terminal device sends a preamble to the current serving base station.
- the current serving base station sends a random access response (RAR) to the terminal device.
- RAR random access response
- the terminal device sends an RRC recovery request message to the current serving base station.
- the current serving base station interacts with the base station storing the UE context of the terminal device, and asks for the UE context.
- the current serving base station sends an RRC recovery message to the terminal device.
- the terminal device sends an RRC recovery completion message to the current serving base station.
- the terminal equipment can only receive the multicast MBS service in the RRC connection state. In order to save energy for the terminal equipment, the terminal equipment can receive the multicast MBS service in the RRC inactive state.
- the configuration information received by the MBS service (abbreviated as MBS configuration information) is configured to the terminal device through RRC dedicated signaling, so cell selection and reselection occurs when the terminal device receives the multicast MBS service in the RRC inactive state. How to obtain the MBS configuration information of the target cell is a problem to be solved. To this end, the following technical solutions of the embodiments of the present application are proposed.
- Fig. 3 is a schematic flowchart of a method for determining configuration information provided in an embodiment of the present application. As shown in Fig. 3 , the method for determining configuration information includes the following steps:
- Step 301 When the terminal device performs cell selection and reselection to a target cell, it determines target MBS configuration information, and receives a multicast MBS service based on the target MBS configuration information.
- the network side may configure at least one indication information through the first signaling, and the indication information is used to indicate whether the terminal device can continue to receive the MBS service in the RRC inactive state.
- the indication information may be configured per G-RNTI, that is, each G-RNTI is associated with one indication information.
- the terminal device receives first signaling, the first signaling is used to configure at least one indication information, and the indication information is used to indicate whether the terminal device can continue to Receive multicast MBS services.
- the first signaling is RRC dedicated signaling, for example, the first signaling is an RRC reconfiguration (RRCReconfiguration) message or an RRC release (RRCRelease) message.
- each indication information in the at least one indication information is associated with one G-RNTI.
- the indication information is configured per G-RNTI.
- indication information 1 associated with G-RNTI 1
- the indication information 2 associated G-RNTI 2 is used to indicate that the terminal equipment cannot continue to receive the multicast MBS service in the RRC inactive state, where the G-RNTI of the MBS service is the G-RNTI 2 associated with the indication information 2.
- the at least one indication information includes first indication information, the first indication information is associated with the first G-RNTI, and the first indication information is used to indicate that the terminal device can be in the RRC Continue to receive the multicast MBS service in the inactive state; after the terminal device enters the RRC inactive state, perform at least one of the following behaviors:
- MBS bearer MBS bearer
- keeping the DRX operation associated with the first G-RNTI to continue to execute can also be understood as maintaining the DRX timer associated with the first G-RNTI (here refers to the DRX timer other than the RTT timer and the retransmission timer Other DRX timers) are not affected. If the DRX configuration associated with the first G-RNTI includes a round-trip time RTT timer and/or retransmission timer configuration, the terminal device ignores the RTT timer and/or retransmission timer configuration; or , if the RTT timer and/or retransmission timer associated with the first G-RNTI is running, the terminal device stops the RTT timer and/or retransmission timer.
- the MAC reset refers to: when the MAC entity is requested to be reset by the upper layer entity, the MAC entity executes the items shown in Table 2 below.
- the MAC entity executes the entries shown in Table 3 below.
- partial MAC reset refers to: MAC reset (reset), but some items are not executed.
- MAC reset but the following actions on Downlink Hybrid Automatic Repeat Request (DL HARQ) are not performed:
- the at least one indication information includes second indication information, the second indication information is associated with the second G-RNTI, and the second indication information is used to indicate that the terminal device cannot Continue to receive the multicast MBS service in the RRC inactive state; after the terminal device enters the RRC inactive state, perform at least one of the following behaviors:
- the indication information 1 (associated with G-RNTI 1) is used to indicate that the terminal device can continue to receive the multicast MBS service in the RRC inactive state, where the G-RNTI of the MBS service is the G-RNTI associated with the indication information 1 1.
- the terminal device After the terminal device enters the RRC inactive state, perform at least one of the following actions: keep the MBS bearer (MRB) associated with G-RNTI 1 not suspended; perform partial MAC reset; keep the DRX operation associated with G-RNTI 1 (also That is, the DRX operation corresponding to the MBS service) continues to be executed.
- MBS bearer MBS bearer
- the indication information 2 (associated G-RNTI 2) is used to indicate that the terminal equipment cannot continue to receive the multicast MBS service in the RRC inactive state, where the G-RNTI of the MBS service is the G-RNTI 2 associated with the indication information 2, After the terminal device enters the RRC inactive state, perform at least one of the following actions: suspend the MBS bearer associated with G-RNTI 2; stop performing the DRX operation associated with G-RNTI 2.
- the terminal device after the terminal device enters the RRC idle state from the RRC inactive state, it releases the UE context and autonomously enters the RRC connection state; the terminal device obtains the MBS configuration information in the RRC connection state, and based on The MBS configuration information receives multicast MBS services.
- the terminal device there are many reasons for the terminal device to enter the RRC idle state from the RRC inactive state. For example, the terminal device enters the RRC idle state from the RRC inactive state due to an abnormality. In this case, the terminal device releases the UE AS context, including the MBS service Data context, and autonomously enter the RRC connection state to continue to obtain MBS configuration information and continue to receive MBS services according to the MBS configuration information.
- the terminal device can learn which MBS services can continue to be received in the RRC inactive state through the first signaling.
- the terminal equipment when the terminal equipment is in the RRC inactive state, its mobility behavior follows cell selection and reselection.
- the terminal device determines target MBS configuration information, and receives a multicast MBS service based on the target MBS configuration information. How the terminal device determines the MBS configuration information is described below. It should be noted that the "target MBS configuration information" in the embodiment of the present application may also be understood as updated MBS configuration information.
- Solution 1 Network configuration area granularity (per area) MBS configuration information.
- the terminal device receives second signaling, and the second signaling is used to configure at least one piece of MBS configuration information; when the terminal device performs cell selection and reselects to a target cell, based on The second signaling acquires target MBS configuration information.
- the second signaling is used to configure first MBS configuration information
- the second signaling is also used to configure first area information
- the first area information is used to indicate that the first MBS configuration information is valid the first area of .
- the MBS configuration information includes at least one of the following: MBS identification information, G-RNTI, MRB bearer configuration, frequency domain resource information when receiving MBS multicast services, physical channel configuration, feedback resource configuration, etc. .
- the first area information includes at least one of the following: a cell ID list, an RNA list, and a system broadcast area ID.
- the second signaling is RRC dedicated signaling, and the second signaling may be the same as or different from the first signaling in the foregoing solution.
- the second signaling is an RRC reconfiguration (RRCReconfiguration) message or an RRC release (RRCRelease) message.
- the terminal device receives the configuration information (that is, the first MBS configuration information) about the multicast MBS service reception sent by the network side through the RRC dedicated signaling in the RRC connection state, and at the same time, the RRC dedicated signaling also configures an area information (that is, the first area information), the first area information is used to indicate the first area where the MBS configuration information is valid, and the terminal device does not need to re-acquire the MBS configuration when performing cell selection and reselection in the first area information, the previous MBS configuration information (that is, the MBS configuration information obtained through RRC dedicated signaling) is still valid.
- the configuration information that is, the first MBS configuration information
- the RRC dedicated signaling also configures an area information (that is, the first area information)
- the first area information is used to indicate the first area where the MBS configuration information is valid
- the terminal device does not need to re-acquire the MBS configuration when performing cell selection and reselection in the first area information
- the terminal device when the terminal device performs cell selection reselection to a target cell, if the target cell is located in the first area, the first MBS configuration information is determined as the Target MBS configuration information.
- the terminal device if the target cell is located outside the first area, the terminal device initiates an RRC recovery process, and obtains the target MBS configuration information through the RRC recovery process.
- Solution 2 The network configures the MBS configuration information of the cell granularity (per cell).
- the terminal device receives second signaling, and the second signaling is used to configure at least one piece of MBS configuration information; when the terminal device performs cell selection and reselects to a target cell, based on The second signaling acquires target MBS configuration information.
- each piece of MBS configuration information in the at least one piece of MBS configuration information is associated with a piece of cell identity information, and the MBS configuration information is valid in a cell corresponding to the associated cell identity information.
- the MBS configuration information includes at least one of the following: MBS identification information, G-RNTI, MRB bearer configuration, frequency domain resource information when receiving MBS multicast services, physical channel configuration, feedback resource configuration, etc. .
- the cell identity information includes at least one of the following: a cell identity, a frequency, and a physical cell identity (PCI).
- PCI physical cell identity
- the terminal device when the terminal device performs cell selection and reselection to a target cell, if the cell identity information of the target cell is associated with the first MBS configuration information in the at least one piece of MBS configuration information If the cell identity information matches, the first MBS configuration information is determined as the target MBS configuration information.
- the terminal device if the cell identity information of the target cell does not match the cell identity information associated with any MBS configuration information in the at least one piece of MBS configuration information, the terminal device initiates an RRC recovery process, Obtain the target MBS configuration information through the RRC recovery process.
- the terminal device receives configuration information about multicast MBS service reception through RRC dedicated signaling in the RRC connection state, where the RRC dedicated signaling configures multiple MBS configuration information, and each configuration information is associated with a cell identification information.
- the terminal device performs cell selection and reselects to the target cell, if the cell identity information of the target cell matches the cell identity information associated with one of the MBS configuration information, the terminal device enables the MBS configuration information associated with the cell identity information, and if it does not match , the terminal device initiates an RRC recovery process, and obtains updated MBS configuration information through the RRC recovery process.
- Scheme 3 Update MBS configuration information through a 2-step RRC resume (2step RRC resume) process.
- the terminal device when the terminal device performs cell selection and reselection to the target cell, it initiates an RRC recovery process, and acquires target MBS configuration information through the RRC recovery process.
- the network side configures updated MBS configuration information through an RRC release message
- the terminal device acquires target MBS configuration information through an RRC release message
- the terminal device when performing cell selection and reselection to a target cell, the terminal device initiates an RRC recovery process, and obtains updated MBS configuration information through the RRC recovery process.
- the terminal device obtains the target MBS configuration information through the RRC recovery process or through the RRC release message, including: the terminal device sends an RRC recovery request message to the first base station, and the first base station is the first base station. the base station corresponding to the target cell; the terminal device receives the RRC release message sent by the first base station, the RRC release message carries updated MBS configuration information, and the terminal device determines the updated MBS configuration information as the Describe the target MBS configuration information.
- the first base station sends a UE context request message to the second base station;
- the second base station is the UE that stores the terminal device The base station of the context;
- the first base station receives the request UE context response message sent by the second base station, and the request UE context response message carries the UE context of the terminal device;
- the first base station based on the UE context request message of the terminal device UE context, update MBS configuration information.
- the RRC recovery request message carries a recovery reason, and the value of the recovery reason is a first cause value, and the first cause value is used to indicate that the purpose of the terminal device initiating RRC recovery is to Update MBS configuration information.
- the Request UE Context Request message carries a first cause value, and the first cause value is used to indicate that the purpose of the terminal device initiating RRC recovery is to update MBS configuration information.
- Fig. 4 schematically shows the flow process of obtaining updated MBS configuration information in the RRC recovery process, as shown in Fig. 4, including the following steps:
- the terminal device is in the RRC inactive state, and needs to obtain updated MBS configuration information (that is, configuration information for multicast MBS service reception) to perform cell selection and reselection to a target cell.
- updated MBS configuration information that is, configuration information for multicast MBS service reception
- the terminal device sends the preamble to the first base station.
- the first base station is the base station currently serving the terminal device, that is, the base station corresponding to the target cell.
- the first base station sends the RAR to the terminal device.
- the terminal device sends an RRC recovery request message to the first base station, carrying a recovery reason: MBSconfigupdate.
- MBSconfigupdate is also the first cause value, and is used to indicate that the purpose of initiating RRC recovery by the terminal equipment is to update MBS configuration information.
- the first base station After receiving the RRC recovery request message, the first base station knows from the recovery reason that the purpose of the terminal device initiating RRC recovery is to update the updated MBS configuration information caused by cell selection and reselection, so as to store the terminal device's information according to the I-RNTI.
- the second base station of the UE context sends a UE context request request message, carrying a recovery reason: MBSconfigupdate.
- the second base station sends a UE context request response message to the first base station, carrying the UE context.
- the first base station updates the MBS configuration information according to the configuration information of the multicast MBS service in the UE context, and configures the updated MBS configuration information to the terminal device through an RRC release message.
- the terminal device maintains the RRC inactive state, replaces the previous MBS configuration information with the updated MBS configuration information in the RRC release message, and continues to receive the multicast MBS service using the updated MBS configuration information.
- the terminal device in order to meet the continuity of the service, that is, to make the terminal device reselect to the cell where the MBS service that the terminal device is receiving is as far as possible, so as to ensure the continuity of the MBS service reception, the terminal device performs cell selection and reselection.
- Frequency priority for time selection reference Specifically, for a terminal device entering the RRC inactive state to receive MBS services, the terminal device considers that the frequency corresponding to the current cell has the highest priority during the cell reselection process or is based on the MBS service configured on the network side.
- the frequency priority configuration information for service reception determines the frequency with the highest priority, and then performs cell selection and reselection according to the frequency with the highest priority.
- the RRC release message also carries frequency priority configuration information, and the frequency priority configuration information is used for all
- the terminal device performs cell selection and reselection for the MBS service. Further, if the MBS service ends, the terminal device releases the frequency priority configuration information.
- the RRC release message carries the dedicated frequency priority configuration (namely, frequency priority configuration information) set by the terminal device to ensure the continuity of the MBS service.
- the terminal device uses this configuration to perform cell selection and reselection, thereby ensuring priority reselection to A community with MBS services. If the MBS service ends, the terminal device releases the frequency priority configuration information.
- the RRC release message also carries third indication information, and the third indication information is used to indicate the The terminal device can continue to receive the multicast MBS service and/or the frequency priority of the current cell is the highest in the RRC inactive state, and the third indication information is used for the terminal device to perform cell selection and reselection for the MBS service .
- the RRC release message carries an indication information, which is used to instruct the terminal equipment to return to the RRC inactive state and continue to receive the multicast MBS service. After the terminal equipment receives the RRC release message and enters the RRC inactive state, it will The information can consider that the frequency where the current cell is located has the highest priority, and cell selection and reselection are performed accordingly.
- the RRC release message also carries a first neighbor list with MBS services; if the terminal device judges the cell reselection based on the first neighbor list If the MBS service does not exist in the neighboring cell, the terminal device enters the RRC connection state and receives the MBS service in the RRC connection state; If the above MBS service is provided, the terminal device performs cell reselection and continues to receive the MBS service in the neighboring cell to which the cell is reselected.
- the network side configures a list of neighboring cells with MBS services in the RRC release message (called the first neighboring cell list), if the terminal device judges that there is no neighboring cell for cell reselection according to the list of neighboring cells before cell selection and reselection For the MBS service, the terminal device enters the RRC connection state to receive the MBS service, and then continues to receive the MBS service through handover. If there is an MBS service in the adjacent cell for cell reselection, the terminal device continues to receive the MBS service through cell reselection.
- the terminal device when the terminal device determines that the MBS service ends, it performs at least one of the following actions:
- the terminal device determines that the MBS service ends, which may be implemented in the following manner:
- the terminal device determines the end of the MBS service based on the MAC CE sent by the network side, and the MAC CE is used to notify the end of the MBS service.
- the MAC CE carries the identification information of the MBS service; the terminal device determines the terminated MBS service based on the identification information of the MBS service carried in the MAC CE.
- the terminal device determines the terminated MBS service based on the G-RNTI that schedules the PDCCH corresponding to the MAC CE.
- the MAC CE only includes a MAC CE subheader.
- the network notifies the end of the MBS service through the MAC CE, and the terminal device stops monitoring the MBS service scrambled by the G-RNTI after learning the end of the MBS service, and/or releases the bearer associated with the G-RNTI autonomously configuration and all associated MBS configurations.
- the MAC CE includes identification information of the released (that is, stopped) MBS service, such as TMGI or G-RNTI.
- the MAC The CE can be a MAC CE with only a MAC CE subheader and no MAC CE content, that is, the end of a certain MBS service on the network side can be determined through the subheader of the MAC CE.
- the terminal device determines that the MBS service ends based on the timer configured on the network side.
- the timer is configured for G-RNTI; or, the timer is configured for multiple MBS services.
- the terminal device starts or restarts the timer after receiving the PDCCH for scheduling the MBS service, and determines that the MBS service ends if the timer times out.
- a timer is configured on the network side. If the terminal device receives MBS service scheduling data (that is, the PDCCH scrambled by the G-RNTI), the terminal device restarts the timer. If the timer expires, it means that the MBS service ends.
- MBS service scheduling data that is, the PDCCH scrambled by the G-RNTI
- the timer here can be configured per G-RNTI, or a timer can be configured for all MBS services.
- sequence numbers of the above-mentioned processes do not mean the order of execution, and the order of execution of the processes should be determined by their functions and internal logic, and should not be used in this application.
- the implementation of the examples constitutes no limitation.
- the terms “downlink”, “uplink” and “sidelink” are used to indicate the transmission direction of signals or data, wherein “downlink” is used to indicate that the transmission direction of signals or data is sent from the station The first direction to the user equipment in the cell, “uplink” is used to indicate that the signal or data transmission direction is the second direction sent from the user equipment in the cell to the station, and “side line” is used to indicate that the signal or data transmission direction is A third direction sent from UE1 to UE2.
- “downlink signal” indicates that the transmission direction of the signal is the first direction.
- the term “and/or” is only an association relationship describing associated objects, indicating that there may be three relationships. Specifically, A and/or B may mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or” relationship.
- Fig. 5 is a schematic diagram of the structure and composition of the device for determining configuration information provided by the embodiment of the present application, which is applied to terminal equipment. As shown in Fig. 5, the device for determining configuration information includes:
- An acquiring unit 501 configured to determine target MBS configuration information when the terminal device performs cell selection and reselection to a target cell;
- the communication unit 502 is configured to receive a multicast MBS service based on the target MBS configuration information.
- the communication unit 502 is further configured to receive first signaling, where the first signaling is used to configure at least one indication information, and the indication information is used to indicate whether the terminal device can Continue to receive the multicast MBS service in the RRC inactive state.
- each indication information in the at least one indication information is associated with one G-RNTI.
- the at least one indication information includes first indication information, the first indication information is associated with the first G-RNTI, and the first indication information is used to indicate that the terminal device can be in the RRC Continue to receive multicast MBS services in the inactive state;
- the apparatus further includes: a processing unit 503, configured to perform at least one of the following behaviors after the terminal device enters the RRC inactive state:
- the processing unit 503 is further configured to ignore the RTT if the DRX configuration associated with the first G-RNTI includes a configuration of a round-trip time RTT timer and/or a retransmission timer Timer and/or retransmission timer configuration; if the RTT timer and/or retransmission timer associated with the first G-RNTI is running, stop the RTT timer and/or retransmission timer.
- the at least one indication information includes second indication information, the second indication information is associated with the second G-RNTI, and the second indication information is used to indicate that the terminal device cannot Continue to receive multicast MBS services in RRC inactive state;
- the apparatus further includes: a processing unit 503, configured to perform at least one of the following behaviors after the terminal device enters the RRC inactive state:
- the processing unit 503 is further configured to release the UE context and autonomously enter the RRC connected state after the terminal device enters the RRC idle state from the RRC inactive state;
- the obtaining unit 501 is further configured to obtain MBS configuration information when the terminal device is in an RRC connection state, and the communication unit 502 is further configured to receive multicast MBS services based on the MBS configuration information.
- the first signaling is RRC dedicated signaling.
- the communication unit 502 is further configured to receive second signaling, and the second signaling is used to configure at least one piece of MBS configuration information; the obtaining unit 501 is configured to In a case where the device performs cell selection reselection to the target cell, acquires target MBS configuration information based on the second signaling.
- the second signaling is used to configure the first MBS configuration information, and the second signaling is also used to configure the first area information, and the first area information is used to indicate the first MBS configuration information. A first area where the MBS configuration information is valid.
- the first area information includes at least one of the following: a cell identification list, an RNA list, and a system broadcast area identification.
- the obtaining unit 501 is configured to, when the terminal device performs cell selection and reselection to a target cell, if the target cell is located in the first area, the The first MBS configuration information is determined as the target MBS configuration information.
- the acquiring unit 501 is further configured to initiate an RRC recovery process if the target cell is located outside the first area, and acquire the target MBS configuration information through the RRC recovery process.
- each MBS configuration information in the at least one piece of MBS configuration information is associated with a piece of cell identity information, and the MBS configuration information is valid in a cell corresponding to the associated cell identity information.
- the cell identity information includes at least one of the following: cell identity, frequency, and PCI.
- the acquiring unit 501 is configured to, when the terminal device performs cell selection and reselection to a target cell, if the cell identity information of the target cell and the at least one MBS configuration information If the cell identity information associated with the first MBS configuration information matches, the first MBS configuration information is determined as the target MBS configuration information.
- the obtaining unit 501 is further configured to: if the cell identity information of the target cell does not match the cell identity information associated with any MBS configuration information in the at least one piece of MBS configuration information, then Initiate an RRC recovery process, and obtain the target MBS configuration information through the RRC recovery process.
- the acquiring unit 501 is configured to initiate an RRC recovery process when the terminal device performs cell selection and reselection to a target cell, and acquire target MBS configuration information through the RRC recovery process.
- the communication unit 502 is further configured to send an RRC recovery request message to a first base station, where the first base station is a base station corresponding to the target cell; and receive the RRC message sent by the first base station A release message, where the RRC release message carries updated MBS configuration information, and the acquiring unit 501 determines the updated MBS configuration information as the target MBS configuration information.
- the RRC recovery request message carries a recovery reason, and the value of the recovery reason is a first cause value, and the first cause value is used to indicate that the purpose of the terminal device initiating RRC recovery is to Update MBS configuration information.
- the first base station sends a UE context request message to a second base station;
- the second base station is a base station that stores the UE context of the terminal device;
- the first base station receives the first base station The requesting UE context response message sent by the second base station, where the requesting UE context response message carries the UE context of the terminal device;
- the first base station updates the MBS configuration information based on the UE context of the terminal device.
- the Request UE Context Request message carries a first cause value, and the first cause value is used to indicate that the purpose of the terminal device initiating RRC recovery is to update MBS configuration information.
- the RRC release message further carries frequency priority configuration information, and the frequency priority configuration information is used by the terminal device to perform cell selection and reselection for the MBS service.
- the processing unit 503 is further configured to release the frequency priority configuration information if the MBS service ends.
- the RRC release message also carries third indication information, and the third indication information is used to indicate that the terminal device can continue to receive multicast MBS services and/or The frequency priority of the current cell is the highest, and the third indication information is used for the terminal device to perform cell selection and reselection for the MBS service.
- the RRC release message also carries a first neighbor list with MBS services; the communication unit 502 is further configured to determine the neighbor cell for cell reselection based on the first neighbor list If the MBS service does not exist, then enter the RRC connection state and receive the MBS service in the RRC connection state; if it is judged based on the first neighbor list that the neighbor cell for cell reselection has the MBS service, perform cell reselection and Continue to receive the MBS service in the neighboring cell to which the cell is reselected.
- processing unit 503 is further configured to perform at least one of the following actions when it is determined that the MBS service ends:
- the processing unit 503 is configured to determine the end of the MBS service based on the MAC CE sent by the network side, and the MAC CE is used to notify the end of the MBS service.
- the MAC CE carries identification information of the MBS service; the processing unit 503 is configured to determine the terminated MBS service based on the identification information of the MBS service carried in the MAC CE.
- the processing unit 503 is configured to determine the terminated MBS service based on scheduling the G-RNTI of the PDCCH corresponding to the MAC CE.
- the MAC CE only includes a MAC CE subheader.
- the processing unit 503 is configured to determine the end of the MBS service based on a timer configured on the network side.
- the processing unit 503 is configured to start or restart the timer when the communication unit 501 receives the PDCCH scheduling the MBS service, and determine the MBS service if the timer expires. Finish.
- the timer is configured for G-RNTI; or, the timer is configured for multiple MBS services.
- FIG. 6 is a schematic structural diagram of a communication device 600 provided in an embodiment of the present application.
- the communication device may be a terminal device or a network device.
- the communication device 600 shown in FIG. 6 includes a processor 610, and the processor 610 can invoke and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
- the communication device 600 may further include a memory 620 .
- the processor 610 can invoke and run a computer program from the memory 620, so as to implement the method in the embodiment of the present application.
- the memory 620 may be an independent device independent of the processor 610 , or may be integrated in the processor 610 .
- the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, to send information or data to other devices, or receive other Information or data sent by the device.
- the transceiver 630 may include a transmitter and a receiver.
- the transceiver 630 may further include antennas, and the number of antennas may be one or more.
- the communication device 600 may specifically be the network device of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not repeated here. .
- the communication device 600 may specifically be the mobile terminal/terminal device of the embodiment of the present application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, for the sake of brevity , which will not be repeated here.
- FIG. 7 is a schematic structural diagram of a chip according to an embodiment of the present application.
- the chip 700 shown in FIG. 7 includes a processor 710, and the processor 710 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
- the chip 700 may further include a memory 720 .
- the processor 710 can invoke and run a computer program from the memory 720, so as to implement the method in the embodiment of the present application.
- the memory 720 may be an independent device independent of the processor 710 , or may be integrated in the processor 710 .
- the chip 700 may also include an input interface 730 .
- the processor 710 may control the input interface 730 to communicate with other devices or chips, specifically, may obtain information or data sent by other devices or chips.
- the chip 700 may also include an output interface 740 .
- the processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.
- the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application.
- the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application.
- the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application.
- the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application.
- the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application.
- the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application.
- the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.
- Fig. 8 is a schematic block diagram of a communication system 800 provided by an embodiment of the present application. As shown in FIG. 8 , the communication system 800 includes a terminal device 810 and a network device 820 .
- the terminal device 810 can be used to realize the corresponding functions realized by the terminal device in the above method
- the network device 820 can be used to realize the corresponding functions realized by the network device in the above method.
- the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
- each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
- the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Program logic devices, discrete gate or transistor logic devices, discrete hardware components.
- DSP Digital Signal Processor
- ASIC Application Specific Integrated Circuit
- FPGA Field Programmable Gate Array
- a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
- the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
- the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
- the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
- the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
- the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash.
- the volatile memory can be Random Access Memory (RAM), which acts as external cache memory.
- RAM Static Random Access Memory
- SRAM Static Random Access Memory
- DRAM Dynamic Random Access Memory
- Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
- SDRAM double data rate synchronous dynamic random access memory
- Double Data Rate SDRAM, DDR SDRAM enhanced synchronous dynamic random access memory
- Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
- Synchlink DRAM, SLDRAM Direct Memory Bus Random Access Memory
- Direct Rambus RAM Direct Rambus RAM
- the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.
- the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
- the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application.
- the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application.
- the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application , for the sake of brevity, it is not repeated here.
- the embodiment of the present application also provides a computer program product, including computer program instructions.
- the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the Let me repeat for the sake of brevity, the Let me repeat.
- the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods of the embodiments of the present application, For the sake of brevity, details are not repeated here.
- the embodiment of the present application also provides a computer program.
- the computer program can be applied to the network device in the embodiment of the present application.
- the computer program executes the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program executes the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
- the computer program executes each method in the embodiment of the present application to be implemented by the mobile terminal/terminal device
- the corresponding process will not be repeated here.
- the disclosed systems, devices and methods may be implemented in other ways.
- the device embodiments described above are only illustrative.
- the division of the units is only a logical function division. In actual implementation, there may be other division methods.
- multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
- the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
- the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
- the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
- the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disc, etc., which can store program codes. .
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本申请实施例提供一种确定配置信息的方法及装置、终端设备,该方法包括:终端设备执行小区选择重选到目标小区的情况下,确定目标多媒体广播服务MBS配置信息,并基于所述目标MBS配置信息接收组播的MBS业务。
Description
本申请实施例涉及移动通信技术领域,具体涉及一种确定配置信息的方法及装置、终端设备。
在新无线(New Radio,NR)系统中,很多场景需要支持组播类型和广播类型的业务需求,例如车联网中,工业互联网中等。所以在NR中引入组播类型和广播类型的多媒体广播服务(Multimedia Broadcast Service,MBS)业务是有必要的。
目前,终端设备只能在无线资源控制(Radio Resource Control,RRC)连接状态下接收组播的MBS业务。为了终端设备的节能,终端设备可以在RRC非激活状态下接收组播的MBS业务,终端设备如何在RRC非激活状态下接收组播的MBS业务需要完善。
发明内容
本申请实施例提供一种确定配置信息的方法及装置、终端设备、芯片、计算机可读存储介质、计算机程序产品、计算机程序。
本申请实施例提供的确定配置信息的方法,包括:
终端设备执行小区选择重选到目标小区的情况下,确定目标MBS配置信息,并基于所述目标MBS配置信息接收组播的MBS业务。
本申请实施例提供的确定配置信息的装置,应用于终端设备,所述装置包括:
获取单元,用于在终端设备执行小区选择重选到目标小区的情况下,确定目标MBS配置信息;
通信单元,用于基于所述目标MBS配置信息接收组播的MBS业务。
本申请实施例提供的终端设备,包括处理器和存储器。该存储器用于存储计算机程序,该处理器用于调用并运行该存储器中存储的计算机程序,执行上述的确定配置信息的方法。
本申请实施例提供的芯片,用于实现上述的确定配置信息的方法。
具体地,该芯片包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有该芯片的设备执行上述的确定配置信息的方法。
本申请实施例提供的计算机可读存储介质,用于存储计算机程序,该计算机程序使得计算机执行上述的确定配置信息的方法。
本申请实施例提供的计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行上述的确定配置信息的方法。
本申请实施例提供的计算机程序,当其在计算机上运行时,使得计算机执行上述的确定配置信息的方法。
通过上述技术方案,终端设备可以在RRC非激活状态下执行小区选择重选到目标小区的情况下,确定目标MBS配置信息,并基于所述目标MBS配置信息接收组播的MBS业务,如此,终端设备可以实现在RRC非激活状态下继续接收组播的MBS业务。
此处所说明的附图用来提供对本申请的进一步理解,构成本申请的一部分,本申请的示意性实施例及其说明用于解释本申请,并不构成对本申请的不当限定。在附图中:
图1是本申请实施例的一个应用场景的示意图;
图2是本申请实施例的PTM方式和PTP方式对应的协议栈的示意图;
图3是本申请实施例提供的确定配置信息的方法的流程示意图;
图4是本申请实施例提供的RRC恢复过程中获取更新的MBS配置信息的流程图;
图5是本申请实施例提供的确定配置信息的装置的结构组成示意图;
图6是本申请实施例提供的一种通信设备示意性结构图;
图7是本申请实施例的芯片的示意性结构图;
图8是本申请实施例提供的一种通信系统的示意性框图。
下面将结合本申请实施例中的附图,对本申请实施例中的技术方案进行描述,显然,所描述的实施例是本申请一部分实施例,而不是全部的实施例。基于本申请中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例,都属于本申请保护的范围。
图1是本申请实施例的一个应用场景的示意图。
如图1所示,通信系统100可以包括终端设备110和网络设备120。网络设备120可以通过空口与终端设备110通信。终端设备110和网络设备120之间支持多业务传输。
应理解,本申请实施例仅以通信系统100进行示例性说明,但本申请实施例不限定于此。也就是说,本申请实施例的技术方案可以应用于各种通信系统,例如:长期演进(Long Term Evolution,LTE)系统、LTE时分双工(Time Division Duplex,TDD)、通用移动通信系统(Universal Mobile Telecommunication System,UMTS)、物联网(Internet of Things,IoT)系统、窄带物联网(Narrow Band Internet of Things,NB-IoT)系统、增强的机器类型通信(enhanced Machine-Type Communications,eMTC)系统、5G通信系统(也称为新无线(New Radio,NR)通信系统),或未来的通信系统等。
在图1所示的通信系统100中,网络设备120可以是与终端设备110通信的接入网设备。接入网设备可以为特定的地理区域提供通信覆盖,并且可以与位于该覆盖区域内的终端设备110(例如UE)进行通信。
网络设备120可以是长期演进(Long Term Evolution,LTE)系统中的演进型基站(Evolutional Node B,eNB或eNodeB),或者是下一代无线接入网(Next Generation Radio Access Network,NG RAN)设备,或者是NR系统中的基站(gNB),或者是云无线接入网络(Cloud Radio Access Network,CRAN)中的无线控制器,或者该网络设备120可以为中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器,或者未来演进的公共陆地移动网络(Public Land Mobile Network,PLMN)中的网络设备等。
终端设备110可以是任意终端设备,其包括但不限于与网络设备120或其它终端设备采用有线或者无线连接的终端设备。
例如,所述终端设备110可以指接入终端、用户设备(User Equipment,UE)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,SIP)电话、IoT设备、卫星手持终端、无线本地环路 (Wireless Local Loop,WLL)站、个人数字处理(Personal Digital Assistant,PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进网络中的终端设备等。
终端设备110可以用于设备到设备(Device to Device,D2D)的通信。
无线通信系统100还可以包括与基站进行通信的核心网设备130,该核心网设备130可以是5G核心网(5G Core,5GC)设备,例如,接入与移动性管理功能(Access and Mobility Management Function,AMF),又例如,认证服务器功能(Authentication Server Function,AUSF),又例如,用户面功能(User Plane Function,UPF),又例如,会话管理功能(Session Management Function,SMF)。可选地,核心网络设备130也可以是LTE网络的分组核心演进(Evolved Packet Core,EPC)设备,例如,会话管理功能+核心网络的数据网关(Session Management Function+Core Packet Gateway,SMF+PGW-C)设备。应理解,SMF+PGW-C可以同时实现SMF和PGW-C所能实现的功能。在网络演进过程中,上述核心网设备也有可能叫其它名字,或者通过对核心网的功能进行划分形成新的网络实体,对此本申请实施例不做限制。
通信系统100中的各个功能单元之间还可以通过下一代网络(next generation,NG)接口建立连接实现通信。
例如,终端设备通过NR接口与接入网设备建立空口连接,用于传输用户面数据和控制面信令;终端设备可以通过NG接口1(简称N1)与AMF建立控制面信令连接;接入网设备例如下一代无线接入基站(gNB),可以通过NG接口3(简称N3)与UPF建立用户面数据连接;接入网设备可以通过NG接口2(简称N2)与AMF建立控制面信令连接;UPF可以通过NG接口4(简称N4)与SMF建立控制面信令连接;UPF可以通过NG接口6(简称N6)与数据网络交互用户面数据;AMF可以通过NG接口11(简称N11)与SMF建立控制面信令连接;SMF可以通过NG接口7(简称N7)与PCF建立控制面信令连接。
图1示例性地示出了一个基站、一个核心网设备和两个终端设备,可选地,该无线通信系统100可以包括多个基站设备并且每个基站的覆盖范围内可以包括其它数量的终端设备,本申请实施例对此不做限定。
需要说明的是,图1只是以示例的形式示意本申请所适用的系统,当然,本申请实施例所示的方法还可以适用于其它系统。此外,本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。还应理解,在本申请的实施例中提到的“指示”可以是直接指示,也可以是间接指示,还可以是表示具有关联关系。举例说明,A指示B,可以表示A直接指示B,例如B可以通过A获取;也可以表示A间接指示B,例如A指示C,B可以通过C获取;还可以表示A和B之间具有关联关系。还应理解,在本申请的实施例中提到的“对应”可表示两者之间具有直接对应或间接对应的关系,也可以表示两者之间具有关联关系,也可以是指示与被指示、配置与被配置等关系。还应理解,在本申请的实施例中提到的“预定义”或“预定义规则”可以通过在设备(例如,包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现,本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。还应理解,本申请实施例中,所述"协议"可以指通信领域的标准协议,例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议,本申请对此不做限定。
为便于理解本申请实施例的技术方案,以下对本申请实施例的相关技术进行说明, 以下相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合,其均属于本申请实施例的保护范围。
随着人们对速率、延迟、高速移动性、能效的追求以及未来生活中业务的多样性、复杂性,为此第三代合作伙伴计划(3
rd Generation Partnership Project,3GPP)国际标准组织开始研发5G。5G的主要应用场景为:增强移动超宽带(enhanced Mobile Broadband,eMBB)、低时延高可靠通信(Ultra-Reliable Low-Latency Communications,URLLC)、大规模机器类通信(massive Machine-Type Communications,mMTC)。
一方面,eMBB仍然以用户获得多媒体内容、服务和数据为目标,其需求增长十分迅速。另一方面,由于eMBB可能部署在不同的场景中,例如室内,市区,农村等,其能力和需求的差别也比较大,所以不能一概而论,必须结合具体的部署场景详细分析。URLLC的典型应用包括:工业自动化,电力自动化,远程医疗操作(手术),交通安全保障等。mMTC的典型特点包括:高连接密度,小数据量,时延不敏感业务,模块的低成本和长使用寿命等。
多媒体广播多播服务(Multimedia Broadcast Multicast Service,MBMS)是一种通过共享网络资源从一个数据源向多个终端设备传送数据的技术,该技术在提供多媒体业务的同时能有效地利用网络资源,实现较高速率(如256kbps)的多媒体业务的广播和组播。
由于MBMS频谱效率较低,不足以有效地承载和支撑手机电视类型业务的运营。因此在LTE中,3GPP明确提出增强对下行高速MBMS业务的支持能力,并确定了对物理层和空中接口的设计要求。
3GPP R9将演进的MBMS(evolved MBMS,eMBMS)引入到LTE中。eMBMS提出了单频率网络(Single Frequency Network,SFN)的概念,即多媒体广播多播服务单频率网络(Multimedia Broadcast multicast service Single Frequency Network,MBSFN),MBSFN采用统一频率在所有小区同时发送业务数据,但是要保证小区间的同步。这种方式可以极大的提高小区整体信噪比分布,频谱效率也会相应的大幅提高。eMBMS基于IP多播协议实现业务的广播和多播。
在LTE或增强的LTE(LTE-Advanced,LTE-A)中,MBMS只有广播承载模式,没有多播承载模式。
需要说明的是,虽然上述方案是以MBMS为例进行说明的,但“MBMS”的描述也可以替换为“MBS”。本申请实施例以MBS为例进行说明,“MBS”的描述也可以被替换为“MBMS”。
在NR系统中,很多场景需要支持组播类型和广播类型的业务需求,例如车联网中,工业互联网中等。所以在NR中引入组播类型和广播类型的MBS业务是有必要的。需要说明的是,组播类型的MBS业务是指通过组播方式传输的MBS业务。广播类型的MBS业务是指通过广播方式传输的MBS业务。
对于组播类型的MBS业务来说,网络侧通过RRC专用信令配置MBS业务接收的配置信息(简称为MBS配置信息),可选地,MBS配置信息包括以下至少之一:MBS的标识信息、组-无线网络临时标识(Group-RNTI,G-RNTI)、MBS承载(MBS Radio Bearer,MRB)配置、物理信道配置、反馈资源配置等。针对服务质量(Quality of Service,QoS)要求比较高的MBS业务(例如可靠性要求比较高的MBS业务),终端设备需要在RRC连接状态下接收组播的MBS业务。对于广播类型的MBS业务来说,网络侧通过系统消息(如MBS SIB)配置多播控制信道(Multicast Control Channel,MCCH),通过MCCH信令配置多播传输信道(Multicast Transport Channel,MTCH),终端设备在RRC连接状态,RRC空闲状态,RRC非激活态下都可以接收广播的MBS业务。
对于组播类型的MBS业务来说,MBS业务是发给某个组中的所有终端设备。终端设备在RRC连接状态下接收组播类型的MBS业务,终端设备可以通过点对多点(Point-To-Multipoint,PTM)方式或者点对点(Point-To-Point,PTP)方式接收组播类型的MBS业务数据。其中,参照图2,PTM方式的MBS业务数据通过网络侧配置的G-RNTI来加扰对应的调度信息,PTP方式的MBS业务数据通过C-RNTI来加扰对应的调度信息,可选地,在MBS业务传输过程中,存在PTP用于PTM重传的场景。
对于组播类型的MBS业务来说,基站从共享隧道(tunnel)接收核心网下发的MBS业务后,可以将该MBS业务通过空口下发给一个组中的所有终端设备。这里,基站可以通过PTP方式和/或PTM方式将MBS业务下发给一个组中的所有终端设备。例如:一个组包括终端设备1、终端设备2和终端设备3,基站可以通过PTP方式将MBS业务下发给终端设备1,通过PTP方式将MBS业务下发给终端设备2,通过PTP方式将MBS业务下发给终端设备3;或者,基站可以通过PTP方式将MBS业务下发给终端设备1,通过PTM方式将MBS业务下发给终端设备2和终端设备3;或者,基站可以通过PTM方式将MBS业务下发给终端设备1,终端设备2以及终端设备3。在核心网到基站之间采用一个共享的GTP隧道(Shared GTP tunnel)来传输MBS业务,即无论是PTM方式的MBS业务还是PTP方式的MBS业务都是共享这个GTP隧道的。基站按照PTM方式下发MBS业务数据给UE1和UE2,以及按照PTP方式下发MBS业务数据给UE3。
对于组播类型的MBS业务(简称为MBS组播业务)来说,为了终端设备节能引入了DRX机制。为便于区别,将用于MBS组播业务接收的DRX称为MBS DRX(或者多播DRX(multicast DRX)),将用于传统的单播业务接收的DRX称为单播DRX,MBS DRX和单播DRX是相互独立的。作为示例,MBS DRX相关的参数可以参照以下表1所示,网络侧可以通过RRC信令配置表1所示的参数,从而通过这些参数控制MBS DRX操作,需要说明的是,MBS DRX是per G-RNTI或per G-CS-RNTI配置的。对于终端设备来说,DRX激活时间包括以下定时器运行的时间:drx-onDurationTimerPTM、drx-InactivityTimerPTM、drx-RetransmissionTimer-DL-PTM。
表1
5G为了降低空口信令和快速恢复无线连接,快速恢复数据业务的目的,定义了一个新的RRC状态,即RRC非激活(RRC_INACTIVE)状态。这种状态有别于RRC空闲(RRC_IDLE)状态和RRC激活(RRC_ACTIVE)状态。其中,
1)RRC_IDLE状态(简称为空闲(idle)态):移动性为基于终端设备的小区选择重选,寻呼由核心网(Core Network,CN)发起,寻呼区域由CN配置。基站侧不存在UE上下文,不存在RRC连接。
2)RRC_CONNECTED状态(简称为连接(connected)态):存在RRC连接,基 站侧和终端设备侧存在UE上下文。网络侧知道终端设备的位置是具体小区级别的。移动性是网络侧控制的移动性。终端设备和基站之间可以传输单播数据。
3)RRC_INACTIVE状态(简称为非激活(inactive)态):移动性为基于终端设备的小区选择重选,存在CN-NR之间的连接,UE AS上下文存在某个基站上,寻呼由RAN触发,基于RAN的寻呼区域由RAN管理,网络侧知道终端设备的位置是基于RAN的寻呼区域级别的。
当终端设备处于RRC非激活状态,网络侧(RAN)会通过RRC专用信令给终端设备配置RAN的寻呼区域,该RAN的寻呼区域可以是一个小区或者多个小区。当终端设备在该区域内移动时不用通知网络侧,遵循RRC空闲状态下的移动性行为,即小区选择重选原则。当终端设备移动出RAN的寻呼区域时,会触发终端设备恢复RRC连接并重新获取RAN的寻呼区域。当终端设备有下行数据到达时,为终端设备保持RAN和CN之间连接的基站会触发RAN的寻呼区域内的所有小区发送寻呼消息给终端设备,使得在RRC非激活状态下的终端设备能够恢复RRC连接,进行数据接收。
所以终端设备从RRC非激活状态进入RRC连接状态,有如下三种情况:
一是,终端设备有下行数据到达,网络侧发起RAN初始的寻呼,促使终端设备进入RRC连接状态。
二是,终端设备自身发起RAN位置区域更新,例如周期性RAN位置更新或者跨区域位置更新。
三是,终端设备有上行数据发送需求,促使终端设备进入RRC连接状态。
RRC恢复过程的流程如下:
1、终端设备向当前服务基站发送前导码。
2、当前服务基站向终端设备发送随机接入响应(RAR)。
3、终端设备向当前服务基站发送RRC恢复请求消息。
4、当前服务基站与存储终端设备的UE上下文的基站进行交互,索要UE上下文。
5、当前服务基站向终端设备发送RRC恢复消息。
6、终端设备向当前服务基站发送RRC恢复完成消息。
目前,终端设备只能在RRC连接状态下接收组播的MBS业务。为了终端设备的节能,终端设备可以在RRC非激活状态下接收组播的MBS业务。然而,MBS业务接收的配置信息(简称为MBS配置信息)是通过RRC专用信令配置给终端设备的,所以终端设备在RRC非激活状态下接收组播的MBS业务过程中发生小区选择重选,如何获取目标小区的MBS配置信息是个需要解决的问题。为此,提出了本申请实施例的以下技术方案。
为便于理解本申请实施例的技术方案,以下通过具体实施例详述本申请的技术方案。以上相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合,其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
图3是本申请实施例提供的确定配置信息的方法的流程示意图,如图3所示,所述确定配置信息的方法包括以下步骤:
步骤301:终端设备执行小区选择重选到目标小区的情况下,确定目标MBS配置信息,并基于所述目标MBS配置信息接收组播的MBS业务。
在一些可选实施方式中,网络侧可以通过第一信令配置至少一个指示信息,所述指示信息用于指示终端设备是否能够在RRC非激活状态下继续接收MBS业务,这里,可选地,所述指示信息可以是per G-RNTI配置的,也就是每个G-RNTI关联一个指示信息。对于终端设备来说,所述终端设备接收第一信令,所述第一信令用于配置至少一个指示信息,所述指示信息用于指示所述终端设备是否能够在RRC非激活状态下继续接 收组播的MBS业务。这里,可选地,所述第一信令为RRC专用信令,例如所述第一信令为RRC重配置(RRCReconfiguration)消息或者RRC释放(RRCRelease)消息。
在一些可选实施方式中,所述至少一个指示信息中的每个指示信息与一个G-RNTI关联。换句话说,所述指示信息是per G-RNTI配置的。例如:指示信息1(关联G-RNTI 1)用于指示终端设备能够在RRC非激活状态下继续接收组播的MBS业务,这里的MBS业务的G-RNTI为指示信息1关联的G-RNTI 1。指示信息2(关联G-RNTI 2)用于指示终端设备不能够在RRC非激活状态下继续接收组播的MBS业务,这里的MBS业务的G-RNTI为指示信息2关联的G-RNTI 2。
在一些可选实施方式中,所述至少一个指示信息包括第一指示信息,所述第一指示信息与第一G-RNTI关联,所述第一指示信息用于指示所述终端设备能够在RRC非激活状态下继续接收组播的MBS业务;所述终端设备进入RRC非激活状态后,执行以下至少一种行为:
保持所述第一G-RNTI关联的MBS承载(MRB)不悬挂;
进行部分MAC重置;
保持所述第一G-RNTI关联的DRX操作继续执行。
这里,保持所述第一G-RNTI关联的DRX操作继续执行,也可以理解为,保持所述第一G-RNTI关联的DRX定时器(这里是指除RTT定时器和重传定时器以外的其他DRX定时器)不受影响。若所述第一G-RNTI关联的DRX配置包括往返时间RTT定时器和/或重传定时器的配置,则所述终端设备忽略所述RTT定时器和/或重传定时器的配置;或者,若所述第一G-RNTI关联的RTT定时器和/或重传定时器正在运行,则所述终端设备停止所述RTT定时器和/或重传定时器。
需要说明的是,MAC重置是指:MAC实体被上层实体请求重置的情况下,MAC实体执行以下表2所示的条目。
表2
如果针对PC5-RRC连接,MAC实体被上层请求侧行专用重置,则MAC实体执行以下表3所示的条目。
表3
本申请实施例中,部分MAC重置是指:MAC重置(reset),但部分条目不执行。作为示例:MAC重置,但如下关于下行混合自动重传请求(DL HARQ)的动作不执行:
1>刷新所有DL HARQ进程的软缓冲区(flush the soft buffers for all DL HARQ processes);
1>对于每个DL HARQ进程,考虑下一次接收到的TB传输作为第一次传输(for each DL HARQ process,consider the next received transmission for a TB as the very first transmission)。
在一些可选实施方式中,所述至少一个指示信息包括第二指示信息,所述第二指示信息与第二G-RNTI关联,所述第二指示信息用于指示所述终端设备不能够在RRC非激活状态下继续接收组播的MBS业务;所述终端设备进入RRC非激活状态后,执行以下至少一种行为:
悬挂所述第二G-RNTI关联的MBS承载;
停止执行所述第二G-RNTI关联的DRX操作。
作为示例:指示信息1(关联G-RNTI 1)用于指示终端设备能够在RRC非激活状态下继续接收组播的MBS业务,这里的MBS业务的G-RNTI为指示信息1关联的G-RNTI 1,终端设备进入RRC非激活状态后,执行以下至少一种行为:保持G-RNTI 1关联的MBS承载(MRB)不悬挂;进行部分MAC重置;保持G-RNTI 1关联的DRX操作(也即MBS业务对应的DRX操作)继续执行。指示信息2(关联G-RNTI 2)用于指示终端设备不能够在RRC非激活状态下继续接收组播的MBS业务,这里的MBS业务的G-RNTI为指示信息2关联的G-RNTI 2,终端设备进入RRC非激活状态后,执行以下至少一种行为:悬挂G-RNTI 2关联的MBS承载;停止执行G-RNTI 2关联的DRX操作。
在一些可选实施方式中,所述终端设备从RRC非激活状态进入RRC空闲状态后,释放UE上下文,并自主进入RRC连接状态;所述终端设备在RRC连接状态下获取MBS配置信息,并基于所述MBS配置信息接收组播的MBS业务。这里,终端设备从RRC非激活状态进入RRC空闲状态的原因有多种,例如终端设备由于异常而从RRC非激活状态进入RRC空闲状态,这种情况下,终端设备释放UE AS上下文,包括MBS业务数据的上下文,并自主进入RRC连接状态继续获取MBS配置信息以及根据MBS配置信息继续接收MBS业务。
通过上述方案,终端设备可以通过第一信令获知哪些MBS业务可以在RRC非激活状态下继续接收。
本申请实施例中,终端设备在RRC非激活状态下,其移动性行为遵循小区选择重选。终端设备执行小区选择重选到目标小区的情况下,确定目标MBS配置信息,并基于所述目标MBS配置信息接收组播的MBS业务。以下对终端设备如何确定MBS配置信息进行说明。需要说明的是,本申请实施例中的“目标MBS配置信息”也可以理解为更新的MBS配置信息。
方案一:网络配置区域粒度(per area)的MBS配置信息。
在一些可选实施方式中,所述终端设备接收第二信令,所述第二信令用于配置至少一个MBS配置信息;所述终端设备执行小区选择重选到目标小区的情况下,基于所述第二信令获取目标MBS配置信息。具体地,所述第二信令用于配置第一MBS配置信息,所述第二信令还用于配置第一区域信息,所述第一区域信息用于指示所述第一MBS配置信息有效的第一区域。
这里,可选地,所述MBS配置信息包括以下至少之一:MBS的标识信息、G-RNTI、MRB承载配置、接收MBS组播业务时的频域资源信息、物理信道配置、反馈资源配置等。
这里,可选地,所述第一区域信息包括以下至少之一:小区标识列表、RNA列表、系统广播区域标识。
这里,可选地,所述第二信令为RRC专用信令,所述第二信令和前述方案中的第一信令可以相同,也可以不同。例如所述第二信令为RRC重配置(RRCReconfiguration)消息或者RRC释放(RRCRelease)消息。
作为示例:终端设备在RRC连接状态下通过RRC专用信令接收网络侧发送的关于组播MBS业务接收的配置信息(即第一MBS配置信息),同时所述RRC专用信令还配置一个区域信息(即第一区域信息),所述第一区域信息用于指示所述MBS配置信息有效的第一区域,终端设备在所述第一区域内进行小区选择重选时,不需要重新获取MBS配置信息,之前的MBS配置信息(即通过RRC专用信令获得的MBS配置信息)依然有效。
在一些可选实施方式中,所述终端设备执行小区选择重选到目标小区的情况下,若所述目标小区位于所述第一区域内,则将所述第一MBS配置信息确定为所述目标MBS配置信息。
在一些可选实施方式中,若所述目标小区位于所述第一区域外,则所述终端设备发起RRC恢复过程,通过所述RRC恢复过程获取所述目标MBS配置信息。
方案二:网络配置小区粒度(per cell)的MBS配置信息。
在一些可选实施方式中,所述终端设备接收第二信令,所述第二信令用于配置至少一个MBS配置信息;所述终端设备执行小区选择重选到目标小区的情况下,基于所述第二信令获取目标MBS配置信息。具体地,所述至少一个MBS配置信息中的每个MBS配置信息关联一个小区标识信息,所述MBS配置信息在其关联的小区标识信息对应小区内有效。
这里,可选地,所述MBS配置信息包括以下至少之一:MBS的标识信息、G-RNTI、MRB承载配置、接收MBS组播业务时的频域资源信息、物理信道配置、反馈资源配置等。
这里,可选地,所述小区标识信息包括以下至少之一:小区标识、频率、物理小区标识(PCI)。
在一些可选实施方式中,所述终端设备执行小区选择重选到目标小区的情况下,若 所述目标小区的小区标识信息与所述至少一个MBS配置信息中的第一MBS配置信息关联的小区标识信息匹配,则将所述第一MBS配置信息确定为所述目标MBS配置信息。
在一些可选实施方式中,若所述目标小区的小区标识信息与所述至少一个MBS配置信息中的任意MBS配置信息关联的小区标识信息均不匹配,则所述终端设备发起RRC恢复过程,通过所述RRC恢复过程获取所述目标MBS配置信息。
作为示例:终端设备在RRC连接状态下通过RRC专用信令接收关于组播MBS业务接收的配置信息,这里所述RRC专用信令配置多个MBS配置信息,每个配置信息关联一个小区标识信息。终端设备执行小区选择重选到目标小区时,如果目标小区的小区标识信息和其中一个MBS配置信息关联的小区标识信息匹配,则终端设备启用所述小区标识信息关联的MBS配置信息,如果不匹配,则终端设备发起RRC恢复过程,通过RRC恢复过程获取更新的MBS配置信息。
方案三:通过2步RRC恢复(2step RRC resume)过程更新MBS配置信息。
在一些可选实施方式中,所述终端设备执行小区选择重选到目标小区的情况下,发起RRC恢复过程,通过所述RRC恢复过程获取目标MBS配置信息。
在一些可选实施方式中,网络侧通过RRC释放消息来配置更新的MBS配置信息,终端设备通过RRC释放消息获取目标MBS配置信息。
作为示例:终端设备执行小区选择重选到目标小区时,发起RRC恢复过程,通过RRC恢复过程获取更新的MBS配置信息。
上述方案中的任意方案来说,终端设备通过RRC恢复过程或者说通过RRC释放消息获取目标MBS配置信息,包括:所述终端设备向第一基站发送RRC恢复请求消息,所述第一基站为所述目标小区对应的基站;所述终端设备接收所述第一基站发送的RRC释放消息,所述RRC释放消息携带更新的MBS配置信息,所述终端设备将所述更新的MBS配置信息确定为所述目标MBS配置信息。
这里,可选地,所述终端设备向第一基站发送RRC恢复请求消息后,所述第一基站向第二基站发送索要UE上下文请求消息;所述第二基站为存储所述终端设备的UE上下文的基站;所述第一基站接收所述第二基站发送的索要UE上下文响应消息,所述索要UE上下文响应消息携带所述终端设备的UE上下文;所述第一基站基于所述终端设备的UE上下文,更新MBS配置信息。
上述方案中,可选地,所述RRC恢复请求消息携带恢复原因,所述恢复原因的值为第一原因值,所述第一原因值用于指示所述终端设备发起RRC恢复的目的是为了更新MBS配置信息。
上述方案中,可选地,所述索要UE上下文请求消息携带第一原因值,所述第一原因值用于指示所述终端设备发起RRC恢复的目的是为了更新MBS配置信息。
图4示意出了RRC恢复过程中获取更新的MBS配置信息的流程,如图4所示,包括以下步骤:
1、终端设备处于RRC非激活状态,执行小区选择重选到目标小区,需要获取更新的MBS配置信息(也即组播MBS业务接收的配置信息)。
2、终端设备向第一基站发送前导码。
这里,第一基站为终端设备当前服务的基站,也即目标小区对应的基站。
3、第一基站向终端设备发送RAR。
4、终端设备向第一基站发送RRC恢复请求消息,携带恢复原因为:MBSconfigupdate。
这里,MBSconfigupdate也即第一原因值,用于指示终端设备发起RRC恢复的目的是为了更新MBS配置信息。
5、第一基站接收接收到RRC恢复请求消息后,通过恢复原因知道终端设备发起 RRC恢复的目的是为了更新由于小区选择重选导致的更新MBS配置信息,从而根据I-RNTI向存储终端设备的UE上下文的第二基站发送索要UE上下文请求消息,携带恢复原因为:MBSconfigupdate。
6、第二基站向第一基站发送索要UE上下文响应消息,携带UE上下文。
7、第一基站根据UE上下文中组播MBS业务的配置信息,更新MBS配置信息,并将更新的MBS配置信息通过RRC释放消息配置给终端设备。
8、终端设备保持RRC非激活状态,将RRC释放消息中的更新的MBS配置信息替换之前的MBS配置信息,采用更新的MBS配置信息继续接收组播的MBS业务。
本申请实施例中,为了满足业务的连续性,也就是尽可能使终端设备重选到存在终端设备正在接收的MBS业务的小区上,从而保证MBS业务接收的连续性,终端设备进行小区选择重选时参考的频率优先级,具体地,对于进入RRC非激活状态的终端设备接收MBS业务,终端设备在小区重选过程中认为当前小区对应的频率的优先级最高或者基于网络侧配置的针对MBS业务接收的频率优先级配置信息确定最高优先级的频率,进而根据最高优先级的频率进行小区选择重选。
在一些可选实施方式中,对于上述方案一、方案二、方案三中的任意一种方案来说,所述RRC释放消息还携带频率优先级配置信息,所述频率优先级配置信息用于所述终端设备进行针对所述MBS业务的小区选择重选。进一步,若所述MBS业务结束,则所述终端设备释放所述频率优先级配置信息。
这里,RRC释放消息中携带了终端设备为了保证MBS业务连续性而设置的频率优先级专用配置(即频率优先级配置信息),终端设备使用该配置进行小区选择重选,从而保障优先重选到有MBS业务的小区。如果MBS业务结束,则终端设备释放频率优先级配置信息。
在一些可选实施方式中,对于上述方案一、方案二、方案三中的任意一种方案来说,所述RRC释放消息还携带第三指示信息,所述第三指示信息用于指示所述终端设备在RRC非激活状态下能够继续接收组播的MBS业务和/或当前小区的频率优先级最高,所述第三指示信息用于所述终端设备进行针对所述MBS业务的小区选择重选。
这里,RRC释放消息中携带了一个指示信息,用于指示终端设备回到RRC非激活状态下能够继续接收组播的MBS业务,终端设备接收到RRC释放消息进入RRC非激活状态后,根据该指示信息可以认为当前小区所在的频率优先级最高,并据此进行小区选择重选。
在一些可选实施方式中,对于上述方案三来说,所述RRC释放消息还携带存在MBS业务的第一邻区列表;若所述终端设备基于所述第一邻区列表判断小区重选的邻区不存在所述MBS业务,则所述终端设备进入RRC连接状态并在RRC连接状态下接收MBS业务;若所述终端设备基于所述第一邻区列表判断小区重选的邻区存在所述MBS业务,则所述终端设备进行小区重选并在小区重选到的邻区中继续接收MBS业务。
这里,网络侧在RRC释放消息中配置存在MBS业务的邻区列表(称为第一邻区列表),如果终端设备在小区选择重选前根据该邻区列表判断小区重选的邻区没有存在MBS业务,则终端设备进入RRC连接状态接收MBS业务,然后通过切换的方式继续接收MBS业务。如果小区重选的邻区存在MBS业务,则终端设备通过小区重选的方式继续接收MBS业务。
在一些可选实施方式中,所述终端设备确定MBS业务结束的情况下,执行以下至少一种行为:
停止监听G-RNTI加扰的MBS业务的调度信息;
释放所述G-RNTI关联的承载配置;
释放所述G-RNTI关联的MBS配置信息。
上述方案中,所述终端设备确定MBS业务结束,可以通过以下方式来实现:
方式一)所述终端设备基于网络侧发送的MAC CE确定MBS业务结束,所述所述MAC CE用于通知MBS业务结束。
选项1)所述MAC CE携带MBS业务的标识信息;所述终端设备基于所述MAC CE中携带MBS业务的标识信息,确定结束的MBS业务。
选项2)所述终端设备基于调度所述MAC CE对应的PDCCH的G-RNTI,确定结束的MBS业务。这里,可选地,所述MAC CE仅包括MAC CE子头。
作为示例:如果MBS业务结束,则网络通过MAC CE通知MBS业务结束,终端设备获知MBS业务结束后,停止监听G-RNTI加扰的MBS业务,和/或自主释放所述G-RNTI关联的承载配置以及所有关联的MBS配置。作为一种实现方式,所述MAC CE包含释放(也即停止)的MBS业务的标识信息,例如TMGI或者G-RNTI。作为另一种实现方式,所述MAC CE对应的PDCCH基于哪个G-RNTI调度(或者说加扰)就隐式指示释放(也即停止)该G-RNTI对应的MBS业务,此时所述MAC CE可以是一个只有MAC CE子头没有MAC CE内容的MAC CE,即通过MAC CE的子头确定网络侧结束了某个MBS业务。
方式二)所述终端设备基于网络侧配置的定时器,确定MBS业务结束。这里,可选地,所述定时器为针对G-RNTI配置的;或者,所述定时器为针对多个MBS业务配置的。
具体地,所述终端设备接收到了调度MBS业务的PDCCH,则启动或重启所述定时器,若所述定时器超时,则确定MBS业务结束。
作为示例:网络侧配置一个定时器,如果终端设备接收到了MBS业务调度数据(即G-RNTI加扰的PDCCH),则终端设备重启定时器,如果定时器超时,则表示MBS业务结束。这里的定时器可以per G-RNTI来配置,或者所有MBS业务配置一个定时器。
以上结合附图详细描述了本申请的优选实施方式,但是,本申请并不限于上述实施方式中的具体细节,在本申请的技术构思范围内,可以对本申请的技术方案进行多种简单变型,这些简单变型均属于本申请的保护范围。例如,在上述具体实施方式中所描述的各个具体技术特征,在不矛盾的情况下,可以通过任何合适的方式进行组合,为了避免不必要的重复,本申请对各种可能的组合方式不再另行说明。又例如,本申请的各种不同的实施方式之间也可以进行任意组合,只要其不违背本申请的思想,其同样应当视为本申请所公开的内容。又例如,在不冲突的前提下,本申请描述的各个实施例和/或各个实施例中的技术特征可以和现有技术任意的相互组合,组合之后得到的技术方案也应落入本申请的保护范围。
还应理解,在本申请的各种方法实施例中,上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。此外,在本申请实施例中,术语“下行”、“上行”和“侧行”用于表示信号或数据的传输方向,其中,“下行”用于表示信号或数据的传输方向为从站点发送至小区的用户设备的第一方向,“上行”用于表示信号或数据的传输方向为从小区的用户设备发送至站点的第二方向,“侧行”用于表示信号或数据的传输方向为从用户设备1发送至用户设备2的第三方向。例如,“下行信号”表示该信号的传输方向为第一方向。另外,本申请实施例中,术语“和/或”,仅仅是一种描述关联对象的关联关系,表示可以存在三种关系。具体地,A和/或B可以表示:单独存在A,同时存在A 和B,单独存在B这三种情况。另外,本文中字符“/”,一般表示前后关联对象是一种“或”的关系。
图5是本申请实施例提供的确定配置信息的装置的结构组成示意图,应用于终端设备,如图5所示,所述确定配置信息的装置包括:
获取单元501,用于在终端设备执行小区选择重选到目标小区的情况下,确定目标MBS配置信息;
通信单元502,用于基于所述目标MBS配置信息接收组播的MBS业务。
在一些可选实施方式中,所述通信单元502,还用于接收第一信令,所述第一信令用于配置至少一个指示信息,所述指示信息用于指示所述终端设备是否能够在RRC非激活状态下继续接收组播的MBS业务。
在一些可选实施方式中,所述至少一个指示信息中的每个指示信息与一个G-RNTI关联。
在一些可选实施方式中,所述至少一个指示信息包括第一指示信息,所述第一指示信息与第一G-RNTI关联,所述第一指示信息用于指示所述终端设备能够在RRC非激活状态下继续接收组播的MBS业务;
所述装置还包括:处理单元503,用于在所述终端设备进入RRC非激活状态后,执行以下至少一种行为:
保持所述第一G-RNTI关联的MBS承载不悬挂;
进行部分MAC重置;
保持所述第一G-RNTI关联的DRX操作继续执行。
在一些可选实施方式中,所述处理单元503,还用于若所述第一G-RNTI关联的DRX配置包括往返时间RTT定时器和/或重传定时器的配置,则忽略所述RTT定时器和/或重传定时器的配置;若所述第一G-RNTI关联的RTT定时器和/或重传定时器正在运行,则停止所述RTT定时器和/或重传定时器。
在一些可选实施方式中,所述至少一个指示信息包括第二指示信息,所述第二指示信息与第二G-RNTI关联,所述第二指示信息用于指示所述终端设备不能够在RRC非激活状态下继续接收组播的MBS业务;
所述装置还包括:处理单元503,用于在所述终端设备进入RRC非激活状态后,执行以下至少一种行为:
悬挂所述第二G-RNTI关联的MBS承载;
停止执行所述第二G-RNTI关联的DRX操作。
在一些可选实施方式中,所述处理单元503,还用于在所述终端设备从RRC非激活状态进入RRC空闲状态后,释放UE上下文,并自主进入RRC连接状态;
所述获取单元501,还用于在所述终端设备在RRC连接状态下获取MBS配置信息,所述通信单元502,还用于基于所述MBS配置信息接收组播的MBS业务。
在一些可选实施方式中,所述第一信令为RRC专用信令。
在一些可选实施方式中,所述通信单元502,还用于接收第二信令,所述第二信令用于配置至少一个MBS配置信息;所述获取单元501,用于在所述终端设备执行小区选择重选到目标小区的情况下,基于所述第二信令获取目标MBS配置信息。
在一些可选实施方式中,所述第二信令用于配置第一MBS配置信息,所述第二信令还用于配置第一区域信息,所述第一区域信息用于指示所述第一MBS配置信息有效的第一区域。
在一些可选实施方式中,所述第一区域信息包括以下至少之一:小区标识列表、RNA列表、系统广播区域标识。
在一些可选实施方式中,所述获取单元501,用于在所述终端设备执行小区选择重选到目标小区的情况下,若所述目标小区位于所述第一区域内,则将所述第一MBS配置信息确定为所述目标MBS配置信息。
在一些可选实施方式中,所述获取单元501,还用于若所述目标小区位于所述第一区域外,则发起RRC恢复过程,通过所述RRC恢复过程获取所述目标MBS配置信息。
在一些可选实施方式中,所述至少一个MBS配置信息中的每个MBS配置信息关联一个小区标识信息,所述MBS配置信息在其关联的小区标识信息对应小区内有效。
在一些可选实施方式中,所述小区标识信息包括以下至少之一:小区标识、频率、PCI。
在一些可选实施方式中,所述获取单元501,用于在所述终端设备执行小区选择重选到目标小区的情况下,若所述目标小区的小区标识信息与所述至少一个MBS配置信息中的第一MBS配置信息关联的小区标识信息匹配,则将所述第一MBS配置信息确定为所述目标MBS配置信息。
在一些可选实施方式中,所述获取单元501,还用于若所述目标小区的小区标识信息与所述至少一个MBS配置信息中的任意MBS配置信息关联的小区标识信息均不匹配,则发起RRC恢复过程,通过所述RRC恢复过程获取所述目标MBS配置信息。
在一些可选实施方式中,所述获取单元501,用于在所述终端设备执行小区选择重选到目标小区的情况下,发起RRC恢复过程,通过所述RRC恢复过程获取目标MBS配置信息。
在一些可选实施方式中,所述通信单元502,还用于向第一基站发送RRC恢复请求消息,所述第一基站为所述目标小区对应的基站;接收所述第一基站发送的RRC释放消息,所述RRC释放消息携带更新的MBS配置信息,所述获取单元501将所述更新的MBS配置信息确定为所述目标MBS配置信息。
在一些可选实施方式中,所述RRC恢复请求消息携带恢复原因,所述恢复原因的值为第一原因值,所述第一原因值用于指示所述终端设备发起RRC恢复的目的是为了更新MBS配置信息。
在一些可选实施方式中,所述第一基站向第二基站发送索要UE上下文请求消息;所述第二基站为存储所述终端设备的UE上下文的基站;所述第一基站接收所述第二基站发送的索要UE上下文响应消息,所述索要UE上下文响应消息携带所述终端设备的UE上下文;所述第一基站基于所述终端设备的UE上下文,更新MBS配置信息。
在一些可选实施方式中,所述索要UE上下文请求消息携带第一原因值,所述第一原因值用于指示所述终端设备发起RRC恢复的目的是为了更新MBS配置信息。
在一些可选实施方式中,所述RRC释放消息还携带频率优先级配置信息,所述频率优先级配置信息用于所述终端设备进行针对所述MBS业务的小区选择重选。
在一些可选实施方式中,所述处理单元503,还用于若所述MBS业务结束,则释放所述频率优先级配置信息。
在一些可选实施方式中,所述RRC释放消息还携带第三指示信息,所述第三指示信息用于指示所述终端设备在RRC非激活状态下能够继续接收组播的MBS业务和/或当前小区的频率优先级最高,所述第三指示信息用于所述终端设备进行针对所述MBS业务的小区选择重选。
在一些可选实施方式中,所述RRC释放消息还携带存在MBS业务的第一邻区列表;所述通信单元502,还用于若基于所述第一邻区列表判断小区重选的邻区不存在所述MBS业务,则进入RRC连接状态并在RRC连接状态下接收MBS业务;若基于所述第一邻区列表判断小区重选的邻区存在所述MBS业务,则进行小区重选并在小区重选到 的邻区中继续接收MBS业务。
在一些可选实施方式中,所述处理单元503,还用于在确定MBS业务结束的情况下,执行以下至少一种行为:
停止监听G-RNTI加扰的MBS业务的调度信息;
释放所述G-RNTI关联的承载配置;
释放所述G-RNTI关联的MBS配置信息。
在一些可选实施方式中,所述处理单元503,用于基于网络侧发送的MAC CE确定MBS业务结束,所述所述MAC CE用于通知MBS业务结束。
在一些可选实施方式中,所述MAC CE携带MBS业务的标识信息;所述处理单元503,用于基于所述MAC CE中携带MBS业务的标识信息,确定结束的MBS业务。
在一些可选实施方式中,所述处理单元503,用于基于调度所述MAC CE对应的PDCCH的G-RNTI,确定结束的MBS业务。
在一些可选实施方式中,所述MAC CE仅包括MAC CE子头。
在一些可选实施方式中,所述处理单元503,用于基于网络侧配置的定时器,确定MBS业务结束。
在一些可选实施方式中,所述处理单元503,用于在所述通信单元501接收到了调度MBS业务的PDCCH,则启动或重启所述定时器,若所述定时器超时,则确定MBS业务结束。
在一些可选实施方式中,所述定时器为针对G-RNTI配置的;或者,所述定时器为针对多个MBS业务配置的。
本领域技术人员应当理解,本申请实施例的上述确定配置信息的装置的相关描述可以参照本申请实施例的确定配置信息的方法的相关描述进行理解。
图6是本申请实施例提供的一种通信设备600示意性结构图。该通信设备可以终端设备,也可以是网络设备。图6所示的通信设备600包括处理器610,处理器610可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图6所示,通信设备600还可以包括存储器620。其中,处理器610可以从存储器620中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器620可以是独立于处理器610的一个单独的器件,也可以集成在处理器610中。
可选地,如图6所示,通信设备600还可以包括收发器630,处理器610可以控制该收发器630与其他设备进行通信,具体地,可以向其他设备发送信息或数据,或接收其他设备发送的信息或数据。
其中,收发器630可以包括发射机和接收机。收发器630还可以进一步包括天线,天线的数量可以为一个或多个。
可选地,该通信设备600具体可为本申请实施例的网络设备,并且该通信设备600可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该通信设备600具体可为本申请实施例的移动终端/终端设备,并且该通信设备600可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
图7是本申请实施例的芯片的示意性结构图。图7所示的芯片700包括处理器710,处理器710可以从存储器中调用并运行计算机程序,以实现本申请实施例中的方法。
可选地,如图7所示,芯片700还可以包括存储器720。其中,处理器710可以从存储器720中调用并运行计算机程序,以实现本申请实施例中的方法。
其中,存储器720可以是独立于处理器710的一个单独的器件,也可以集成在处理器710中。
可选地,该芯片700还可以包括输入接口730。其中,处理器710可以控制该输入接口730与其他设备或芯片进行通信,具体地,可以获取其他设备或芯片发送的信息或数据。
可选地,该芯片700还可以包括输出接口740。其中,处理器710可以控制该输出接口740与其他设备或芯片进行通信,具体地,可以向其他设备或芯片输出信息或数据。
可选地,该芯片可应用于本申请实施例中的网络设备,并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该芯片可应用于本申请实施例中的移动终端/终端设备,并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
应理解,本申请实施例提到的芯片还可以称为系统级芯片,系统芯片,芯片系统或片上系统芯片等。
图8是本申请实施例提供的一种通信系统800的示意性框图。如图8所示,该通信系统800包括终端设备810和网络设备820。
其中,该终端设备810可以用于实现上述方法中由终端设备实现的相应的功能,以及该网络设备820可以用于实现上述方法中由网络设备实现的相应的功能为了简洁,在此不再赘述。
应理解,本申请实施例的处理器可能是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor,DSP)、专用集成电路(Application Specific Integrated Circuit,ASIC)、现成可编程门阵列(Field Programmable Gate Array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。
可以理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(Read-Only Memory,ROM)、可编程只读存储器(Programmable ROM,PROM)、可擦除可编程只读存储器(Erasable PROM,EPROM)、电可擦除可编程只读存储器(Electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(Static RAM,SRAM)、动态随机存取存储器(Dynamic RAM,DRAM)、同步动态随机存取存储器(Synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)。应注意,本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解,上述存储器为示例性但不是限制性说明,例如,本申请实施例中的存储器还可以是静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synch link DRAM,SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM,DR RAM)等等。也就是说,本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质,用于存储计算机程序。
可选的,该计算机可读存储介质可应用于本申请实施例中的网络设备,并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备,并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本申请实施例还提供了一种计算机程序产品,包括计算机程序指令。
可选的,该计算机程序产品可应用于本申请实施例中的网络设备,并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机程序产品可应用于本申请实施例中的移动终端/终端设备,并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的,该计算机程序可应用于本申请实施例中的网络设备,当该计算机程序在计算机上运行时,使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程,为了简洁,在此不再赘述。
可选地,该计算机程序可应用于本申请实施例中的移动终端/终端设备,当该计算机程序在计算机上运行时,使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程,为了简洁,在此不再赘述。
本领域普通技术人员可以意识到,结合本文中所公开的实施例描述的各示例的单元及算法步骤,能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、装置和方法,可以通过其它的方式实现。例如,以上所描述的装置实施例仅仅是示意性的,例如,所述单元的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个单元或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另一点,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口,装置或单元的间接耦合或通信连接,可以是电性,机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的,作为单元显示的部件可以是或者也可以不是物理单元,即可以位于一个地方,或者也可以分布到多个 网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外,在本申请各个实施例中的各功能单元可以集成在一个处理单元中,也可以是各个单元单独物理存在,也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读取存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(Read-Only Memory,)ROM、随机存取存储器(Random Access Memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领域的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应所述以权利要求的保护范围为准。
Claims (40)
- 一种确定配置信息的方法,所述方法包括:终端设备执行小区选择重选到目标小区的情况下,确定目标多媒体广播服务MBS配置信息,并基于所述目标MBS配置信息接收组播的MBS业务。
- 根据权利要求1所述的方法,其中,所述方法还包括:所述终端设备接收第一信令,所述第一信令用于配置至少一个指示信息,所述指示信息用于指示所述终端设备是否能够在无线资源控制RRC非激活状态下继续接收组播的MBS业务。
- 根据权利要求2所述的方法,其中,所述至少一个指示信息中的每个指示信息与一个组-无线网络临时标识G-RNTI关联。
- 根据权利要求2或3所述的方法,其中,所述至少一个指示信息包括第一指示信息,所述第一指示信息与第一G-RNTI关联,所述第一指示信息用于指示所述终端设备能够在RRC非激活状态下继续接收组播的MBS业务;所述方法还包括:所述终端设备进入RRC非激活状态后,执行以下至少一种行为:保持所述第一G-RNTI关联的MBS承载不悬挂;进行部分媒体接入控制MAC重置;保持所述第一G-RNTI关联的非连续接收DRX操作继续执行。
- 根据权利要求4所述的方法,其中,若所述第一G-RNTI关联的DRX配置包括往返时间RTT定时器和/或重传定时器的配置,则所述终端设备忽略所述RTT定时器和/或重传定时器的配置;若所述第一G-RNTI关联的RTT定时器和/或重传定时器正在运行,则所述终端设备停止所述RTT定时器和/或重传定时器。
- 根据权利要求2或3所述的方法,其中,所述至少一个指示信息包括第二指示信息,所述第二指示信息与第二G-RNTI关联,所述第二指示信息用于指示所述终端设备不能够在RRC非激活状态下继续接收组播的MBS业务;所述方法还包括:所述终端设备进入RRC非激活状态后,执行以下至少一种行为:悬挂所述第二G-RNTI关联的MBS承载;停止执行所述第二G-RNTI关联的DRX操作。
- 根据权利要求4至6中任一项所述的方法,其中,所述方法还包括:所述终端设备从RRC非激活状态进入RRC空闲状态后,释放UE上下文,并自主进入RRC连接状态;所述终端设备在RRC连接状态下获取MBS配置信息,并基于所述MBS配置信息接收组播的MBS业务。
- 根据权利要求2至7中任一项所述的方法,其中,所述第一信令为RRC专用信令。
- 根据权利要求1至8中任一项所述的方法,其中,所述终端设备执行小区选择重选到目标小区的情况下,确定目标MBS配置信息,包括:所述终端设备接收第二信令,所述第二信令用于配置至少一个MBS配置信息;所述终端设备执行小区选择重选到目标小区的情况下,基于所述第二信令获取目标MBS配置信息。
- 根据权利要求9所述的方法,其中,所述第二信令用于配置第一MBS配置信息,所述第二信令还用于配置第一区域信息,所述第一区域信息用于指示所述第一MBS配置信息有效的第一区域。
- 根据权利要求10所述的方法,其中,所述第一区域信息包括以下至少之一:小区标识列表、无线接入网通知区域RNA列表、系统广播区域标识。
- 根据权利要求10或11所述的方法,其中,所述终端设备执行小区选择重选到目标小区的情况下,基于所述第二信令获取目标MBS配置信息,包括:所述终端设备执行小区选择重选到目标小区的情况下,若所述目标小区位于所述第一区域内,则将所述第一MBS配置信息确定为所述目标MBS配置信息。
- 根据权利要求12所述的方法,其中,所述方法还包括:若所述目标小区位于所述第一区域外,则所述终端设备发起RRC恢复过程,通过所述RRC恢复过程获取所述目标MBS配置信息。
- 根据权利要求9所述的方法,其中,所述至少一个MBS配置信息中的每个MBS配置信息关联一个小区标识信息,所述MBS配置信息在其关联的小区标识信息对应小区内有效。
- 根据权利要求14所述的方法,其中,所述小区标识信息包括以下至少之一:小区标识、频率、物理小区标识PCI。
- 根据权利要求14或15所述的方法,其中,所述终端设备执行小区选择重选到目标小区的情况下,基于所述第二信令获取目标MBS配置信息,包括:所述终端设备执行小区选择重选到目标小区的情况下,若所述目标小区的小区标识信息与所述至少一个MBS配置信息中的第一MBS配置信息关联的小区标识信息匹配,则将所述第一MBS配置信息确定为所述目标MBS配置信息。
- 根据权利要求16所述的方法,其中,所述方法还包括:若所述目标小区的小区标识信息与所述至少一个MBS配置信息中的任意MBS配置信息关联的小区标识信息均不匹配,则所述终端设备发起RRC恢复过程,通过所述RRC恢复过程获取所述目标MBS配置信息。
- 根据权利要求1至8中任一项所述的方法,其中,所述终端设备执行小区选择重选到目标小区的情况下,确定目标MBS配置信息,包括:所述终端设备执行小区选择重选到目标小区的情况下,发起RRC恢复过程,通过所述RRC恢复过程获取目标MBS配置信息。
- 根据权利要求1至18中任一项所述的方法,其中,所述确定目标MBS配置信息,包括:所述终端设备向第一基站发送RRC恢复请求消息,所述第一基站为所述目标小区对应的基站;所述终端设备接收所述第一基站发送的RRC释放消息,所述RRC释放消息携带更新的MBS配置信息,所述终端设备将所述更新的MBS配置信息确定为所述目标MBS配置信息。
- 根据权利要求19所述的方法,其中,所述RRC恢复请求消息携带恢复原因,所述恢复原因的值为第一原因值,所述第一原因值用于指示所述终端设备发起RRC恢复的目的是为了更新MBS配置信息。
- 根据权利要求19或20所述的方法,其中,所述终端设备向第一基站发送RRC恢复请求消息后,所述方法还包括:所述第一基站向第二基站发送索要UE上下文请求消息;所述第二基站为存储所述终端设备的UE上下文的基站;所述第一基站接收所述第二基站发送的索要UE上下文响应消息,所述索要UE上下文响应消息携带所述终端设备的UE上下文;所述第一基站基于所述终端设备的UE上下文,更新MBS配置信息。
- 根据权利要求21所述的方法,其中,所述索要UE上下文请求消息携带第一原因值,所述第一原因值用于指示所述终端设备发起RRC恢复的目的是为了更新MBS配置信息。
- 根据权利要求19至22中任一项所述的方法,其中,所述RRC释放消息还携带频率优先级配置信息,所述频率优先级配置信息用于所述终端设备进行针对所述MBS业务的小区选择重选。
- 根据权利要求23所述的方法,其中,所述方法还包括:若所述MBS业务结束,则所述终端设备释放所述频率优先级配置信息。
- 根据权利要求19至22中任一项所述的方法,其中,所述RRC释放消息还携带第三指示信息,所述第三指示信息用于指示所述终端设备在RRC非激活状态下能够继续接收组播的MBS业务和/或当前小区的频率优先级最高,所述第三指示信息用于所述终端设备进行针对所述MBS业务的小区选择重选。
- 根据权利要求19至22中任一项所述的方法,其中,所述RRC释放消息还携带存在MBS业务的第一邻区列表;所述方法还包括:若所述终端设备基于所述第一邻区列表判断小区重选的邻区不存在所述MBS业务,则所述终端设备进入RRC连接状态并在RRC连接状态下接收MBS业务;若所述终端设备基于所述第一邻区列表判断小区重选的邻区存在所述MBS业务,则所述终端设备进行小区重选并在小区重选到的邻区中继续接收MBS业务。
- 根据权利要求1至26中任一项所述的方法,其中,所述方法还包括:所述终端设备确定MBS业务结束的情况下,执行以下至少一种行为:停止监听G-RNTI加扰的MBS业务的调度信息;释放所述G-RNTI关联的承载配置;释放所述G-RNTI关联的MBS配置信息。
- 根据权利要求27所述的方法,其中,所述终端设备确定MBS业务结束,包括:所述终端设备基于网络侧发送的媒体接入控制MAC控制单元CE确定MBS业务结束,所述所述MAC CE用于通知MBS业务结束。
- 根据权利要求28所述的方法,其中,所述MAC CE携带MBS业务的标识信息;所述终端设备基于网络侧发送的MAC CE确定MBS业务结束,包括:所述终端设备基于所述MAC CE中携带MBS业务的标识信息,确定结束的MBS业务。
- 根据权利要求28所述的方法,其中,所述终端设备基于网络侧发送的MAC CE确定MBS业务结束,包括:所述终端设备基于调度所述MAC CE对应的PDCCH的G-RNTI,确定结束的MBS业务。
- 根据权利要求30所述的方法,其中,所述MAC CE仅包括MAC CE子头。
- 根据权利要求27所述的方法,其中,所述终端设备确定MBS业务结束,包括:所述终端设备基于网络侧配置的定时器,确定MBS业务结束。
- 根据权利要求32所述的方法,其中,所述终端设备基于网络侧配置的定时器,确定MBS业务结束,包括:所述终端设备接收到了调度MBS业务的PDCCH,则启动或重启所述定时器,若所述定时器超时,则确定MBS业务结束。
- 根据权利要求32或33所述的方法,其中,所述定时器为针对G-RNTI配置的;或者,所述定时器为针对多个MBS业务配置的。
- 一种确定配置信息的装置,应用于终端设备,所述装置包括:获取单元,用于在终端设备执行小区选择重选到目标小区的情况下,确定目标MBS配置信息;通信单元,用于基于所述目标MBS配置信息接收组播的MBS业务。
- 一种终端设备,包括:处理器和存储器,该存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,执行如权利要求1至34中任一项所述的方法。
- 一种芯片,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至34中任一项所述的方法。
- 一种计算机可读存储介质,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求1至34中任一项所述的方法。
- 一种计算机程序产品,包括计算机程序指令,该计算机程序指令使得计算机执行如权利要求1至34中任一项所述的方法。
- 一种计算机程序,所述计算机程序使得计算机执行如权利要求1至34中任一项所述的方法。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/072144 WO2023133843A1 (zh) | 2022-01-14 | 2022-01-14 | 一种确定配置信息的方法及装置、终端设备 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2022/072144 WO2023133843A1 (zh) | 2022-01-14 | 2022-01-14 | 一种确定配置信息的方法及装置、终端设备 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2023133843A1 true WO2023133843A1 (zh) | 2023-07-20 |
Family
ID=87279830
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2022/072144 WO2023133843A1 (zh) | 2022-01-14 | 2022-01-14 | 一种确定配置信息的方法及装置、终端设备 |
Country Status (1)
Country | Link |
---|---|
WO (1) | WO2023133843A1 (zh) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103458371A (zh) * | 2012-06-05 | 2013-12-18 | 中兴通讯股份有限公司 | 多媒体广播多播业务的接收方法及装置 |
US20190230564A1 (en) * | 2016-08-11 | 2019-07-25 | Lg Electronics Inc. | Method and apparatus for supporting mbms service continuity |
CN113453159A (zh) * | 2020-03-27 | 2021-09-28 | 维沃移动通信有限公司 | Mbs业务传输方法、mbs业务传输控制方法及相关设备 |
WO2022006746A1 (zh) * | 2020-07-07 | 2022-01-13 | Oppo广东移动通信有限公司 | 接收本地mbs业务的方法及装置、终端设备、网络设备 |
-
2022
- 2022-01-14 WO PCT/CN2022/072144 patent/WO2023133843A1/zh unknown
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103458371A (zh) * | 2012-06-05 | 2013-12-18 | 中兴通讯股份有限公司 | 多媒体广播多播业务的接收方法及装置 |
US20190230564A1 (en) * | 2016-08-11 | 2019-07-25 | Lg Electronics Inc. | Method and apparatus for supporting mbms service continuity |
CN113453159A (zh) * | 2020-03-27 | 2021-09-28 | 维沃移动通信有限公司 | Mbs业务传输方法、mbs业务传输控制方法及相关设备 |
WO2022006746A1 (zh) * | 2020-07-07 | 2022-01-13 | Oppo广东移动通信有限公司 | 接收本地mbs业务的方法及装置、终端设备、网络设备 |
Non-Patent Citations (2)
Title |
---|
SAMSUNG: "NR MBS operation in Idle/Inactive mode", 3GPP TSG-RAN WG2 MEETING #113-BIS-E R2-2102938, 2 April 2021 (2021-04-02), XP052174507 * |
SAMSUNG: "Service Continuity for Multicast", 3GPP TSG RAN WG2 MEETING #115-E R2-2107932, 6 August 2021 (2021-08-06), XP052034533 * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2021142647A1 (zh) | 一种业务传输方法及装置、终端设备、网络设备 | |
CN114424663A (zh) | 一种业务调度方法及装置、终端设备、网络设备 | |
WO2022056806A1 (zh) | 一种mbs业务的管理方法及装置、终端设备、网络设备 | |
CN113661722B (zh) | 一种业务数据传输方法及装置、网络设备、终端设备 | |
US20220210614A1 (en) | Service data transmission method and apparatus, and terminal device | |
WO2021051312A1 (zh) | 一种信息配置方法及装置、终端设备、网络设备 | |
WO2022141255A1 (zh) | 一种mbs业务的配置方法及装置、网络设备、终端设备 | |
WO2022006875A1 (zh) | 建立mbs业务的方法及装置、终端设备、网络设备 | |
WO2022006849A1 (zh) | Mbs业务的tci状态管理方法及装置、终端设备 | |
WO2021056155A1 (zh) | 一种反馈资源配置方法及通信方法、装置、通信设备 | |
WO2023010287A1 (zh) | 一种通知信息变更的方法及装置、终端设备、网络设备 | |
WO2022205454A1 (zh) | 一种指示寻呼的方法及装置、终端设备、网络设备 | |
WO2022141545A1 (zh) | 一种mcch调度传输方法及装置、终端设备 | |
WO2022141088A1 (zh) | 一种mbs业务的传输方法及装置、终端设备 | |
WO2022198415A1 (zh) | 提高mbs业务可靠性的方法及装置、终端设备、网络设备 | |
WO2023133843A1 (zh) | 一种确定配置信息的方法及装置、终端设备 | |
WO2021134761A1 (zh) | 一种小区重选方法及装置、终端设备、网络设备 | |
WO2024011491A1 (zh) | 一种通信方法及装置、终端设备 | |
WO2023050185A1 (zh) | 一种变量的维护方法及装置、终端设备 | |
WO2022226937A1 (zh) | 一种mbs寻呼方法及装置、网络设备、终端设备 | |
WO2022266961A1 (zh) | 一种变量的维护方法及装置、终端设备 | |
WO2023102898A1 (zh) | 重传方式的确定方法及定时器的控制方法、装置 | |
WO2023092531A1 (zh) | 一种广播业务的配置方法及装置、终端设备、网络设备 | |
WO2023004586A1 (zh) | 一种寻呼方法及装置、终端设备、网络设备 | |
WO2023272619A1 (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: 22919493 Country of ref document: EP Kind code of ref document: A1 |