A method and apparatus for determining configuration information, and a terminal device

Abstract

The embodiment of the application provides a method and device for determining configuration information and a terminal device, the method comprising: in the case that the terminal device performs cell selection and reselection to a target cell, determining target multimedia broadcast service (MBS) configuration information, and receiving multicast MBS service based on the target MBS configuration information.

Description

[0001] This application is a divisional application of Chinese patent application No. 202280088001.9, entitled "A method and apparatus for determining configuration information and a terminal device", which entered the Chinese national phase of PCT international patent application PCT / CN2022 / 072144, filed on January 14, 2022. Technical Field

[0002] This application relates to the field of mobile communication technology, specifically to a method and apparatus for determining configuration information, and a terminal device. Background Technology

[0003] In New Radio (NR) systems, many scenarios require support for both multicast and broadcast services, such as in connected vehicles and the Industrial Internet. Therefore, it is necessary to introduce Multimedia Broadcast Service (MBS) services with both multicast and broadcast capabilities into NR.

[0004] Currently, terminal devices can only receive multicast MBS services when connected via Radio Resource Control (RRC). To improve energy efficiency, terminal devices can receive multicast MBS services when RRC is inactive. The method for terminal devices to receive multicast MBS services when RRC is inactive needs further development. Summary of the Invention

[0005] This application provides a method and apparatus for determining configuration information, a terminal device, a chip, a computer-readable storage medium, a computer program product, and a computer program.

[0006] The method for determining configuration information provided in this application embodiment includes:

[0007] When the terminal device performs cell selection reselection to the target cell, it determines the target MBS configuration information and receives multicast MBS services based on the target MBS configuration information.

[0008] The apparatus for determining configuration information provided in this application embodiment is applied to a terminal device, and the apparatus includes:

[0009] The acquisition unit is used to determine the target MBS configuration information when the terminal device performs cell selection reselection to the target cell;

[0010] The communication unit is used to receive multicast MBS services based on the target MBS configuration information.

[0011] The terminal device provided in this application includes a processor and a memory. The memory is used to store computer programs, and the processor is used to call and run the computer programs stored in the memory to perform the method described above for determining configuration information.

[0012] The chip provided in this application embodiment is used to implement the above-described method for determining configuration information.

[0013] Specifically, the chip includes a processor for retrieving and running a computer program from memory, causing a device equipped with the chip to perform the aforementioned method for determining configuration information.

[0014] The computer-readable storage medium provided in this application embodiment is used to store a computer program that causes a computer to execute the above-described method for determining configuration information.

[0015] The computer program product provided in this application includes computer program instructions that cause a computer to execute the method for determining configuration information described above.

[0016] The computer program provided in this application embodiment, when run on a computer, causes the computer to perform the above-described method for determining configuration information.

[0017] Through the above technical solution, the terminal device can determine the target MBS configuration information when performing cell selection reselection to the target cell in the RRC inactive state, and receive multicast MBS services based on the target MBS configuration information. In this way, the terminal device can continue to receive multicast MBS services in the RRC inactive state. Attached Figure Description

[0018] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0019] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application;

[0020] Figure 2 This is a schematic diagram of the protocol stack corresponding to the PTM and PTP methods in the embodiments of this application;

[0021] Figure 3 This is a flowchart illustrating the method for determining configuration information provided in an embodiment of this application;

[0022] Figure 4 This is a flowchart illustrating the process of obtaining updated MBS configuration information during RRC recovery, as provided in an embodiment of this application.

[0023] Figure 5 This is a schematic diagram of the structural composition of the device for determining configuration information provided in the embodiments of this application;

[0024] Figure 6 This is a schematic structural diagram of a communication device provided in an embodiment of this application;

[0025] Figure 7 This is a schematic structural diagram of the chip according to an embodiment of this application;

[0026] Figure 8 This is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0027] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0028] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0029] like Figure 1 As shown, the communication system 100 may include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 via an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120.

[0030] It should be understood that the embodiments of this application are only illustrated by way of example with communication system 100, but the embodiments of this application are not limited thereto. That is to say, the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Long Term Evolution (LTE) system, LTE Time Division Duplex (TDD), Universal Mobile Telecommunication System (UMTS), 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.

[0031] exist Figure 1In the communication system 100 shown, network device 120 may be an access network device that communicates with terminal device 110. The access network device can provide communication coverage for a specific geographical area and can communicate with terminal device 110 (e.g., UE) located within that coverage area.

[0032] Network device 120 may be an evolved Node B (eNB or eNodeB) in a Long Term Evolution (LTE) system, a Next Generation Radio Access Network (NG RAN) device, a base station (gNB) in an NR system, a radio controller in a Cloud Radio Access Network (CRAN), or a relay station, access point, vehicle-mounted device, wearable device, hub, switch, bridge, router, or network device in a future evolved Public Land Mobile Network (PLMN), etc.

[0033] Terminal device 110 can be any terminal device, including but not limited to terminal devices that are connected to network device 120 or other terminal devices via wired or wireless connections.

[0034] For example, the terminal device 110 may refer to an access terminal, user equipment (UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The access terminal may be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, IoT device, satellite handheld terminal, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, terminal device in a 5G network, or terminal device in a future evolved network, etc.

[0035] Terminal device 110 can be used for device-to-device (D2D) communication.

[0036] The wireless communication system 100 may further include a core network device 130 that communicates with the base station. This core network device 130 may be a 5G core network (5G Core, 5GC) device, such as an Access and Mobility Management Function (AMF), an Authentication Server Function (AUSF), a User Plane Function (UPF), or a Session Management Function (SMF). Optionally, the core network device 130 may also be an Evolved Packet Core (EPC) device for an LTE network, such as a Session Management Function + Core Packet Gateway (SMF+PGW-C) device. It should be understood that SMF+PGW-C can simultaneously implement the functions of both SMF and PGW-C. During network evolution, the aforementioned core network device may also be called by other names, or new network entities may be formed by dividing the core network functions; this embodiment does not limit this.

[0037] The various functional units in the communication system 100 can also establish connections and communicate with each other through the next generation (NG) interface.

[0038] For example, terminal devices establish air interface connections with access network devices through the NR interface for transmitting user plane data and control plane signaling; terminal devices can establish control plane signaling connections with the AMF through NG interface 1 (N1); access network devices, such as next-generation radio access base stations (gNB), can establish user plane data connections with the UPF through NG interface 3 (N3); access network devices can establish control plane signaling connections with the AMF through NG interface 2 (N2); the UPF can establish control plane signaling connections with the SMF through NG interface 4 (N4); the UPF can interact with the data network for user plane data through NG interface 6 (N6); the AMF can establish control plane signaling connections with the SMF through NG interface 11 (N11); and the SMF can establish control plane signaling connections with the PCF through NG interface 7 (N7).

[0039] Figure 1An exemplary embodiment shows a base station, a core network device, and two terminal devices. Optionally, the wireless communication system 100 may include multiple base station devices, and each base station may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this.

[0040] It should be noted that, Figure 1 This application merely illustrates the system to which this application applies; of course, the methods shown in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0041] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0042] With people's pursuit of speed, latency, high-speed mobility, and energy efficiency, and the increasing diversity and complexity of business in future life, the third-generation partnership program (3GPP) is therefore being developed. rdThe Generation Partnership Project (3GPP) international standards organization has begun developing 5G. The main application scenarios for 5G are: enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC).

[0043] On the one hand, eMBB still aims to provide users with multimedia content, services, and data, and its demand is growing rapidly. On the other hand, because eMBB may be deployed in different scenarios, such as indoors, urban areas, and rural areas, its capabilities and needs vary considerably. Therefore, generalizations cannot be made; a detailed analysis based on the specific deployment scenario is necessary. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety assurance. Typical characteristics of mMTC include high connection density, small data volume, latency-insensitive services, low module cost, and long service life.

[0044] Multimedia Broadcast Multicast Service (MBMS) is a technology that transmits data from one data source to multiple terminal devices by sharing network resources. This technology can effectively utilize network resources while providing multimedia services, enabling the broadcasting and multicast of multimedia services at higher speeds (such as 256kbps).

[0045] Because MBMS has low spectral efficiency, it is insufficient to effectively carry and support the operation of mobile TV services. Therefore, in LTE, 3GPP explicitly proposed enhancing support for downlink high-speed MBMS services and defined the design requirements for the physical layer and air interface.

[0046] 3GPP Release 9 introduced evolved MBMS (eMBMS) into LTE. eMBMS introduced the concept of a Single Frequency Network (SFN), specifically a Multimedia Broadcast Multicast Service Single Frequency Network (MBSFN). MBSFN uses a unified frequency to transmit service data simultaneously in all cells, while ensuring synchronization between cells. This approach can significantly improve the overall signal-to-noise ratio distribution of cells, and spectrum efficiency will also be greatly improved accordingly. eMBMS implements service broadcasting and multicasting based on the IP multicast protocol.

[0047] In LTE or enhanced LTE (LTE-Advanced, LTE-A), MBMS only has a broadcast bearer mode and no multicast bearer mode.

[0048] It should be noted that although the above solution is illustrated using MBMS as an example, the description of "MBMS" can also be replaced with "MBS". This application's embodiments are illustrated using MBS as an example, and the description of "MBS" can also be replaced with "MBMS".

[0049] In NR systems, many scenarios require support for both multicast and broadcast services, such as in connected vehicles and the Industrial Internet. Therefore, introducing multicast and broadcast MBS services into NR is necessary. It's important to note that multicast MBS services refer to MBS services transmitted via multicast, while broadcast MBS services refer to MBS services transmitted via broadcast.

[0050] For multicast MBS services, the network side configures the MBS service reception configuration information (hereinafter referred to as MBS configuration information) through RRC dedicated signaling. Optionally, the MBS configuration information includes at least one of the following: MBS identification information, Group-RNTI (G-RNTI), MBS Radio Bearer (MRB) configuration, physical channel configuration, feedback resource configuration, etc. For MBS services with high Quality of Service (QoS) requirements (such as MBS services with high reliability requirements), the terminal device needs to receive multicast MBS services in RRC connected state. For broadcast MBS services, the network side configures the Multicast Control Channel (MCCH) through system messages (such as MBS SIB) and the Multicast Transport Channel (MTCH) through MCCH signaling. The terminal device can receive broadcast MBS services in RRC connected state, RRC idle state, and RRC inactive state.

[0051] For multicast MBS services, the MBS service is sent to all terminal devices in a group. Terminal devices receive multicast MBS services in RRC connection state, and can receive multicast MBS service data via Point-to-Multipoint (PTM) or Point-to-Point (PTP) methods. (Refer to...) Figure 2 In PTM mode, MBS service data is scrambled with the corresponding scheduling information using G-RNTI configured on the network side. In PTP mode, MBS service data is scrambled with the corresponding scheduling information using C-RNTI. Optionally, during MBS service transmission, there may be scenarios where PTP is used for PTM retransmission.

[0052] For multicast MBS services, after receiving the MBS service from the core network via the shared tunnel, the base station can distribute the MBS service over the air interface to all terminal devices in a group. Here, the base station can distribute the MBS service to all terminal devices in a group using PTP and / or PTM methods. For example, if a group includes terminal device 1, terminal device 2, and terminal device 3, the base station can distribute the MBS service to terminal device 1 via PTP, terminal device 2 via PTP, and terminal device 3 via PTM; or, the base station can distribute the MBS service to terminal device 1 via PTP and to terminal devices 2 and 3 via PTM; or, the base station can distribute the MBS service to terminal devices 1, 2, and 3 via PTM. A shared GTP tunnel is used to transmit MBS services between the core network and the base station. This means that both PTM and PTP-based MBS services share this GTP tunnel. The base station sends MBS service data to UE1 and UE2 in PTM mode, and to UE3 in PTP mode.

[0053] For multicast MBS services (MBS multicast service for short), a DRX mechanism is introduced to save energy for terminal devices. For clarity, the DRX used for MBS multicast service reception is called MBSDRX (or multicast DRX), and the DRX used for traditional unicast service reception is called unicast DRX. MBSDRX and unicast DRX are independent of each other. As an example, the parameters related to MBSDRX can be found in Table 1 below. The network side can configure the parameters shown in Table 1 through RRC signaling, thereby controlling MBSDRX operation. It should be noted that MBSDRX is configured per G-RNTI or per G-CS-RNTI. For terminal devices, the DRX activation time includes the following timer execution times: drx-onDurationTimerPTM, drx-InactivityTimerPTM, and drx-RetransmissionTimer-DL-PTM.

[0054]

[0055] Table 1

[0056] To reduce air interface signaling and facilitate rapid restoration of wireless connections and data services, 5G defines a new RRC state: the RRC Inactive (RRC_INACTIVE) state. This state differs from the RRC Idle (RRC_IDLE) and RRC Active (RRC_ACTIVE) states.

[0057] 1) RRC_IDLE state (abbreviated as idle state): Mobility is based on cell selection and reselection of the terminal device, paging is initiated by the core network (CN), and the paging area is configured by the CN. There is no UE context on the base station side, and there is no RRC connection.

[0058] 2) RRC_CONNECTED state (simply called connected state): An RRC connection exists, and UE context exists on both the base station side and the terminal device side. The network side knows the location of the terminal device at the cell level. Mobility is network-controlled. Unicast data can be transmitted between the terminal device and the base station.

[0059] 3) RRC_INACTIVE state (abbreviated as inactive state): Mobility is based on cell selection reselection of terminal device, there is a connection between CN-NR, the UE AS context exists on a certain base station, paging is triggered by RAN, the paging area based on RAN is managed by RAN, and the network side knows the location of terminal device at the paging area level based on RAN.

[0060] When a terminal device is in RRC inactive, the network side (RAN) configures a paging area for the terminal device via dedicated RRC signaling. This paging area can be one or more cells. When the terminal device moves within this area, it does not need to notify the network side and follows the mobility behavior of the RRC idle state, i.e., the cell selection and reselection principle. When the terminal device moves out of the RAN paging area, it triggers the terminal device to restore the RRC connection and reacquire the RAN paging area. When downlink data arrives for the terminal device, the base station, in order to maintain the connection between the RAN and CN, triggers all cells within the RAN paging area to send paging messages to the terminal device, enabling the terminal device in RRC inactive to restore the RRC connection and receive data.

[0061] Therefore, there are three scenarios when a terminal device transitions from an inactive RRC state to a connected RRC state:

[0062] First, when downlink data arrives at the terminal device, the network side initiates an initial RAN paging, prompting the terminal device to enter the RRC connection state.

[0063] Second, the terminal device itself initiates RAN location area updates, such as periodic RAN location updates or cross-regional location updates.

[0064] Third, the terminal device has an uplink data transmission requirement, which prompts the terminal device to enter the RRC connection state.

[0065] The RRC recovery process is as follows:

[0066] 1. The terminal device sends a preamble to the current serving base station.

[0067] 2. The current serving base station sends a Random Access Response (RAR) to the terminal device.

[0068] 3. The terminal device sends an RRC recovery request message to the current serving base station.

[0069] 4. The current serving base station interacts with the base station storing the UE context of the terminal device to request the UE context.

[0070] 5. The current serving base station sends an RRC recovery message to the terminal device.

[0071] 6. The terminal device sends an RRC recovery complete message to the current serving base station.

[0072] Currently, terminal devices can only receive multicast MBS services while in RRC connected state. To conserve energy, terminal devices can receive multicast MBS services while in RRC inactive state. However, the configuration information for MBS service reception (hereinafter referred to as MBS configuration information) is configured to the terminal device via RRC dedicated signaling. Therefore, cell reselection occurs during the process of receiving multicast MBS services while in RRC inactive state. How to obtain the MBS configuration information of the target cell is a problem that needs to be solved. To address this, the following technical solution, as proposed in this application embodiment, is presented.

[0073] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0074] Figure 3 This is a flowchart illustrating the method for determining configuration information provided in an embodiment of this application, such as... Figure 3 As shown, the method for determining configuration information includes the following steps:

[0075] Step 301: When the terminal device performs cell selection reselection to the target cell, it determines the target MBS configuration information and receives multicast MBS services based on the target MBS configuration information.

[0076] In some optional implementations, the network side can configure at least one indication message via a first signaling message. This indication message is used to indicate whether the terminal device can continue to receive MBS services in the RRC inactive state. Optionally, the indication message can be configured per G-RNTI, meaning each G-RNTI is associated with one indication message. For the terminal device, receiving the first signaling message, which is used to configure at least one indication message, indicates whether the terminal device can continue to receive multicast MBS services in the RRC inactive state. Optionally, the first signaling message is RRC-specific signaling, such as an RRC Reconfiguration message or an RRC Release message.

[0077] In some alternative implementations, each of the at least one indication message is associated with a G-RNTI. In other words, the indication message is configured per G-RNTI. For example, indication message 1 (associated with G-RNTI 1) indicates that the terminal device can continue to receive multicast MBS services in the RRC inactive state, where the G-RNTI for the MBS service is G-RNTI 1 associated with indication message 1. Indication message 2 (associated with G-RNTI 2) indicates that the terminal device cannot continue to receive multicast MBS services in the RRC inactive state, where the G-RNTI for the MBS service is G-RNTI 2 associated with indication message 2.

[0078] In some optional implementations, the at least one indication information includes first indication information associated with a first G-RNTI. The first indication information is used to indicate that the terminal device can continue to receive multicast MBS services in the RRC inactive state. After entering the RRC inactive state, the terminal device performs at least one of the following actions:

[0079] Keep the MBS bearer (MRB) associated with the first G-RNTI from hanging;

[0080] Perform a partial MAC reset;

[0081] Continue executing the DRX operation associated with the first G-RNTI.

[0082] Here, keeping the DRX operation associated with the first G-RNTI running can also be understood as keeping the DRX timers associated with the first G-RNTI (here referring to DRX timers other than the RTT timer and retransmission timer) unaffected. If the DRX configuration associated with the first G-RNTI includes the configuration of the round-trip time (RTT) timer and / or retransmission timer, the terminal device ignores the configuration of the RTT timer and / or retransmission timer; or, if the RTT timer and / or retransmission timer associated with the first G-RNTI are running, the terminal device stops the RTT timer and / or retransmission timer.

[0083] It should be noted that MAC reset refers to the MAC entity executing the entries shown in Table 2 below when the MAC entity is requested to be reset by the upper-level entity.

[0084]

[0085]

[0086] Table 2

[0087] If, for a PC5-RRC connection, the MAC entity is requested by the upper layer to undergo a dedicated reset, the MAC entity performs the following...

[0088] The entries shown in Table 3.

[0089]

[0090] Table 3

[0091] In this embodiment, "partial MAC reset" means that the MAC is reset, but some entries are not executed. For example, the MAC is reset, but the following actions regarding Downlink Hybrid Automatic Repeat Request (DL HARQ) are not executed:

[0092] 1> Flush the soft buffers for all DL HARQ processes;

[0093] 1> For each DL HARQ process, consider the next received transmission for a TB as the very first transmission.

[0094] In some optional implementations, the at least one indication information includes second indication information, which is associated with a second G-RNTI. The second indication information is used to indicate that the terminal device cannot continue to receive multicast MBS services in the RRC inactive state. After the terminal device enters the RRC inactive state, it performs at least one of the following actions:

[0095] The MBS bearing associated with the second G-RNTI is suspended;

[0096] Stop executing the DRX operation associated with the second G-RNTI.

[0097] As an example: Instruction Message 1 (associated with G-RNTI 1) instructs the terminal device to continue receiving multicast MBS services in the RRC inactive state. Here, the G-RNTI for the MBS service is G-RNTI 1 associated with Instruction Message 1. After entering the RRC inactive state, the terminal device performs at least one of the following actions: keeps the MBS bearer (MRB) associated with G-RNTI 1 from suspending; performs a partial MAC reset; and continues to execute the DRX operation associated with G-RNTI 1 (i.e., the DRX operation corresponding to the MBS service). Instruction Message 2 (associated with G-RNTI 2) instructs the terminal device not to continue receiving multicast MBS services in the RRC inactive state. Here, the G-RNTI for the MBS service is G-RNTI 2 associated with Instruction Message 2. After entering the RRC inactive state, the terminal device performs at least one of the following actions: suspends the MBS bearer associated with G-RNTI 2; and stops executing the DRX operation associated with G-RNTI 2.

[0098] In some optional implementations, after the terminal device enters the RRC idle state from the RRC inactive state, it releases the UE context and autonomously enters the RRC connected state. In the RRC connected state, the terminal device acquires MBS configuration information and receives multicast MBS services based on the MBS configuration information. There are various reasons why the terminal device may enter the RRC idle state from the RRC inactive state. For example, the terminal device may enter the RRC idle state due to an anomaly. In this case, the terminal device releases the UE AS context, including the context of the MBS service data, and autonomously enters the RRC connected state to continue acquiring MBS configuration information and receiving MBS services based on the MBS configuration information.

[0099] Through the above scheme, the terminal device can learn which MBS services can continue to be received in the RRC inactive state through the first signaling.

[0100] In this embodiment, when the terminal device is in the RRC inactive state, its mobility behavior follows cell selection and reselection. When the terminal device performs cell selection and reselection to the target cell, it determines the target MBS configuration information and receives multicast MBS services based on the target MBS configuration information. The following explains how the terminal device determines the MBS configuration information. It should be noted that the "target MBS configuration information" in this embodiment can also be understood as updated MBS configuration information.

[0101] Option 1: Configure MBS information at the per-area level.

[0102] In some optional implementations, the terminal device receives a second signaling message, which is used to configure at least one MBS configuration information; when the terminal device performs cell selection reselection to a target cell, it obtains the target MBS configuration information based on the second signaling message. Specifically, the second signaling message is used to configure first MBS configuration information, and the second signaling message is also used to configure first area information, which is used to indicate a first area where the first MBS configuration information is valid.

[0103] Optionally, 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.

[0104] Optionally, the first area information includes at least one of the following: a cell identifier list, an RNA list, and a system broadcast area identifier.

[0105] Optionally, the second signaling is RRC-specific signaling. The second signaling can be the same as or different from the first signaling in the aforementioned scheme. For example, the second signaling can be an RRC Reconfiguration message or an RRC Release message.

[0106] As an example: When the terminal device is in RRC connection state, it receives configuration information (i.e., first MBS configuration information) about multicast MBS service reception sent by the network side through RRC dedicated signaling. At the same time, the RRC dedicated signaling also configures a region information (i.e., first region information). The first region information is used to indicate the first region where the MBS configuration information is valid. When the terminal device performs cell selection reselection in the first region, it does not need to reacquire the MBS configuration information, and the previous MBS configuration information (i.e., the MBS configuration information obtained through RRC dedicated signaling) remains valid.

[0107] In some optional implementations, when the terminal device performs cell selection reselection to the 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.

[0108] In some optional implementations, if the target cell is located outside the first area, the terminal device initiates an RRC recovery process to obtain the target MBS configuration information through the RRC recovery process.

[0109] Option 2: Configure MBS configuration information at the cell level (per cell) in the network.

[0110] In some optional implementations, the terminal device receives a second signaling message, which is used to configure at least one MBS configuration information; when the terminal device performs cell selection reselection to a target cell, it obtains the target MBS configuration information based on the second signaling message. Specifically, each MBS configuration information in the at least one MBS configuration information is associated with a cell identifier, and the MBS configuration information is valid within the cell corresponding to its associated cell identifier.

[0111] Optionally, 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.

[0112] Optionally, the cell identification information includes at least one of the following: cell identifier, frequency, and physical cell identifier (PCI).

[0113] In some optional implementations, when the terminal device performs cell selection reselection to the target cell, if the cell identifier information of the target cell matches the cell identifier information associated with the first MBS configuration information in the at least one MBS configuration information, then the first MBS configuration information is determined as the target MBS configuration information.

[0114] In some optional implementations, if the cell identifier information of the target cell does not match the cell identifier information associated with any of the at least one MBS configuration information, the terminal device initiates an RRC recovery process to obtain the target MBS configuration information through the RRC recovery process.

[0115] As an example: When a terminal device is in RRC connection state, it receives configuration information about multicast MBS service reception via RRC dedicated signaling. This RRC dedicated signaling configures multiple MBS configuration information entries, each associated with a cell identifier. When the terminal device performs cell selection reselection to a target cell, if the target cell's cell identifier matches the cell identifier associated with one of the MBS configuration entries, the terminal device activates the MBS configuration information associated with that cell identifier. If they do not match, the terminal device initiates an RRC recovery process to obtain updated MBS configuration information.

[0116] Option 3: Update MBS configuration information through a 2-step RRC resume process.

[0117] In some optional implementations, when the terminal device performs cell selection reselection to the target cell, it initiates an RRC recovery process to obtain the target MBS configuration information through the RRC recovery process.

[0118] In some alternative implementations, the network side configures updated MBS configuration information through RRC release messages, and the terminal device obtains the target MBS configuration information through RRC release messages.

[0119] As an example: When a terminal device performs cell selection reselection to the target cell, it initiates an RRC recovery process to obtain updated MBS configuration information through the RRC recovery process.

[0120] In any of the above schemes, the terminal device obtains the target MBS configuration information through the RRC recovery process or through the RRC release message, including: the terminal device sending an RRC recovery request message to a first base station, the first base station being the base station corresponding to the target cell; the terminal device receiving an RRC release message sent by the first base station, the RRC release message carrying updated MBS configuration information, and the terminal device determining the updated MBS configuration information as the target MBS configuration information.

[0121] Optionally, after the terminal device sends an RRC recovery request message to the first base station, the first base station sends a UE context request message to the 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 a UE context request response message sent by the second base station, the UE context request response message carrying 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.

[0122] Optionally, in the above scheme, the RRC recovery request message carries a recovery reason, the value of which is a first reason value, which indicates that the purpose of the terminal device initiating the RRC recovery is to update the MBS configuration information.

[0123] Optionally, in the above scheme, the UE context request message carries a first reason value, which is used to indicate that the purpose of the terminal device initiating RRC recovery is to update the MBS configuration information.

[0124] Figure 4 This illustrates the process of obtaining updated MBS configuration information during RRC recovery, such as... Figure 4 As shown, it includes the following steps:

[0125] 1. When the terminal device is in an RRC inactive state and performs cell selection reselection to the target cell, it needs to obtain updated MBS configuration information (i.e., configuration information for multicast MBS service reception).

[0126] 2. The terminal device sends a preamble to the first base station.

[0127] Here, the first base station is the base station currently served by the terminal device, that is, the base station corresponding to the target cell.

[0128] 3. The first base station sends a RAR to the terminal device.

[0129] 4. The terminal device sends an RRC recovery request message to the first base station, carrying the recovery reason as: MBSconfigupdate.

[0130] Here, MBSconfigupdate, also known as the first cause value, is used to indicate that the purpose of the terminal device initiating RRC recovery is to update the MBS configuration information.

[0131] 5. After receiving the RRC recovery request message, the first base station knows from the recovery reason that the purpose of the terminal device initiating the RRC recovery is to update the MBS configuration information caused by cell selection reselection. Therefore, according to the I-RNTI, the first base station sends a request message to the second base station storing the UE context of the terminal device, carrying the recovery reason: MBSconfigupdate.

[0132] 6. The second base station sends a request for UE context response message to the first base station, carrying the UE context.

[0133] 7. 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 the RRC release message.

[0134] 8. The terminal device keeps 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 multicast MBS services using the updated MBS configuration information.

[0135] In this embodiment of the application, in order to meet the requirement of service continuity, that is, to enable the terminal device to reselect to a cell where the terminal device is receiving MBS service as much as possible, thereby ensuring the continuity of MBS service reception, the frequency priority referenced by the terminal device when performing cell selection and reselection is as follows: Specifically, for a terminal device in the RRC inactive state to receive MBS service, the terminal device considers the frequency corresponding to the current cell to have the highest priority during the cell reselection process, or determines the frequency with the highest priority based on the frequency priority configuration information for MBS service reception configured on the network side, and then performs cell selection and reselection based on the frequency with the highest priority.

[0136] In some optional implementations, for any of the above-mentioned schemes 1, 2, and 3, the RRC release message also carries frequency priority configuration information, which is used by the terminal device to perform cell selection reselection for the MBS service. Furthermore, if the MBS service ends, the terminal device releases the frequency priority configuration information.

[0137] Here, the RRC release message carries a dedicated frequency priority configuration (i.e., frequency priority configuration information) set by the terminal device to ensure the continuity of MBS services. The terminal device uses this configuration for cell selection and reselection, thereby ensuring priority reselection to a cell with MBS services. If the MBS service ends, the terminal device releases the frequency priority configuration information.

[0138] In some optional implementations, for any of the above schemes 1, 2, and 3, the RRC release message also carries third indication information. The third indication information is used to indicate that the terminal device can continue to receive multicast MBS services and / or the current cell has the highest frequency priority in the RRC inactive state. The third indication information is used by the terminal device to perform cell selection reselection for the MBS service.

[0139] Here, the RRC release message carries an indication message to instruct the terminal device to return to the RRC inactive state so that it can continue to receive multicast MBS services. After the terminal device receives the RRC release message and enters the RRC inactive state, it can assume that the frequency of the current cell has the highest priority based on the indication message, and perform cell selection reselection accordingly.

[0140] In some optional implementations, for Scheme 3 above, the RRC release message also carries a first neighboring cell list containing MBS service; if the terminal device determines based on the first neighboring cell list that the neighboring cell for cell reselection does not contain MBS service, then the terminal device enters the RRC connection state and receives MBS service in the RRC connection state; if the terminal device determines based on the first neighboring cell list that the neighboring cell for cell reselection contains MBS service, then the terminal device performs cell reselection and continues to receive MBS service in the neighboring cell of the cell reselected.

[0141] Here, the network side configures a list of neighboring cells with MBS service (referred to as the first neighboring cell list) in the RRC release message. If the terminal device determines, based on this neighboring cell list, that no neighboring cell in the cell to be reselected does not have MBS service before cell reselection, the terminal device enters the RRC connected state to receive MBS service, and then continues to receive MBS service through handover. If a neighboring cell in the cell reselection does have MBS service, the terminal device continues to receive MBS service through cell reselection.

[0142] In some alternative implementations, when the terminal device determines that the MBS service has ended, it performs at least one of the following actions:

[0143] Stop monitoring the scheduling information of MBS services scrambled with G-RNTI;

[0144] Release the bearer configuration associated with the G-RNTI;

[0145] Release the MBS configuration information associated with the G-RNTI.

[0146] In the above scheme, the terminal device can determine the end of the MBS service in the following ways:

[0147] Method 1) The terminal device determines the end of MBS service based on the MAC CE sent by the network side, and the MAC CE is used to notify the end of MBS service.

[0148] Option 1) 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.

[0149] Option 2) The terminal device determines the terminated MBS service based on the G-RNTI of the PDCCH corresponding to the MAC CE. Here, optionally, the MAC CE only includes the MAC CE subheader.

[0150] As an example: If the MBS service ends, the network notifies the terminal device of the end of the MBS service via the MAC CE. Upon learning that the MBS service has ended, the terminal device stops listening to MBS services scrambled by G-RNTI and / or voluntarily releases the bearer configuration associated with the G-RNTI and all associated MBS configurations. In one implementation, the MAC CE contains identification information of the released (i.e., stopped) MBS service, such as TMGI or G-RNTI. In another implementation, the PDCCH corresponding to the MAC CE implicitly indicates the release (i.e., stop) of the MBS service corresponding to the G-RNTI based on which G-RNTI is used for scheduling (or scrambling). In this case, the MAC CE can be a MAC CE with only a MAC CE header and no MAC CE content; that is, the network side determines the end of a certain MBS service through the MAC CE header.

[0151] Method 2) The terminal device determines the end of the MBS service based on a timer configured on the network side. Here, optionally, the timer is configured for G-RNTI; or, the timer is configured for multiple MBS services.

[0152] Specifically, when the terminal device receives the PDCCH for scheduling MBS services, it starts or restarts the timer. If the timer times out, it determines that the MBS service has ended.

[0153] As an example: Configure a timer on the network side. If the terminal device receives MBS service scheduling data (i.e., PDCCH scrambled with G-RNTI), the terminal device restarts the timer. If the timer expires, it indicates that the MBS service has ended. This timer can be configured per G-RNTI, or a timer can be configured for all MBS services.

[0154] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0155] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0156] Figure 5 This is a schematic diagram of the structure of the device for determining configuration information provided in the embodiments of this application, which is applied to a terminal device, such as... Figure 5 As shown, the device for determining configuration information includes:

[0157] The acquisition unit 501 is used to determine the target MBS configuration information when the terminal device performs cell selection reselection to the target cell;

[0158] The communication unit 502 is used to receive multicast MBS services based on the target MBS configuration information.

[0159] In some optional embodiments, the communication unit 502 is further configured to receive a first signaling, the first signaling being configured to configure at least one indication information, the indication information being configured to indicate whether the terminal device can continue to receive multicast MBS services in the RRC inactive state.

[0160] In some alternative implementations, each of the at least one indication information is associated with a G-RNTI.

[0161] In some alternative implementations, the at least one indication information includes first indication information associated with a first G-RNTI, the first indication information being used to indicate that the terminal device can continue to receive multicast MBS services in the RRC inactive state;

[0162] The device further includes a processing unit 503, configured to perform at least one of the following actions after the terminal device enters the RRC inactive state:

[0163] Keep the MBS bearing associated with the first G-RNTI from suspending;

[0164] Perform a partial MAC reset;

[0165] Continue executing the DRX operation associated with the first G-RNTI.

[0166] In some alternative implementations, the processing unit 503 is further configured to ignore the configuration of the RTT timer and / or retransmission timer if the DRX configuration associated with the first G-RNTI includes the configuration of the round-trip time (RTT) timer and / or retransmission timer; and to stop the RTT timer and / or retransmission timer if the RTT timer and / or retransmission timer associated with the first G-RNTI is running.

[0167] In some optional implementations, the at least one indication information includes second indication information, which is associated with a second G-RNTI. The second indication information is used to indicate that the terminal device cannot continue to receive multicast MBS services in the RRC inactive state.

[0168] The device further includes a processing unit 503, configured to perform at least one of the following actions after the terminal device enters the RRC inactive state:

[0169] The MBS bearing associated with the second G-RNTI is suspended;

[0170] Stop executing the DRX operation associated with the second G-RNTI.

[0171] In some optional embodiments, the processing unit 503 is further configured to release the UE context and autonomously enter the RRC connection state after the terminal device enters the RRC idle state from the RRC inactive state.

[0172] The acquisition unit 501 is further configured to acquire MBS configuration information when the terminal device is in RRC connection state, and the communication unit 502 is further configured to receive multicast MBS services based on the MBS configuration information.

[0173] In some alternative implementations, the first signaling is RRC-specific signaling.

[0174] In some optional embodiments, the communication unit 502 is further configured to receive a second signaling, the second signaling being used to configure at least one MBS configuration information; the acquisition unit 501 is configured to acquire target MBS configuration information based on the second signaling when the terminal device performs cell selection reselection to the target cell.

[0175] In some alternative implementations, the second signaling is used to configure first MBS configuration information, and the second signaling is also used to configure first area information, the first area information being used to indicate the first area where the first MBS configuration information is valid.

[0176] In some alternative implementations, the first area information includes at least one of the following: a cell identifier list, an RNA list, and a system broadcast area identifier.

[0177] In some optional embodiments, the acquisition unit 501 is configured to, when the terminal device performs cell selection reselection to the target cell, if the target cell is located in the first area, determine the first MBS configuration information as the target MBS configuration information.

[0178] In some optional embodiments, the acquisition unit 501 is further configured to initiate an RRC recovery process if the target cell is located outside the first area, and obtain the target MBS configuration information through the RRC recovery process.

[0179] In some alternative implementations, each MBS configuration information in the at least one MBS configuration information is associated with a cell identifier information, and the MBS configuration information is valid within the cell corresponding to its associated cell identifier information.

[0180] In some alternative implementations, the cell identification information includes at least one of the following: cell identifier, frequency, and PCI.

[0181] In some optional embodiments, the acquisition unit 501 is configured to, when the terminal device performs cell selection reselection to the target cell, determine the first MBS configuration information as the target MBS configuration information if the cell identifier information of the target cell matches the cell identifier information associated with the first MBS configuration information in the at least one MBS configuration information.

[0182] In some optional embodiments, the acquisition unit 501 is further configured to initiate an RRC recovery process if the cell identifier information of the target cell does not match the cell identifier information associated with any of the at least one MBS configuration information, and to acquire the target MBS configuration information through the RRC recovery process.

[0183] In some optional embodiments, the acquisition unit 501 is used to initiate an RRC recovery process when the terminal device performs cell selection reselection to the target cell, and to acquire the target MBS configuration information through the RRC recovery process.

[0184] In some optional embodiments, the communication unit 502 is further configured to send an RRC recovery request message to a first base station, the first base station being the base station corresponding to the target cell; receive an RRC release message sent by the first base station, the RRC release message carrying updated MBS configuration information, and the acquisition unit 501 determines the updated MBS configuration information as the target MBS configuration information.

[0185] In some optional implementations, the RRC recovery request message carries a recovery reason, the value of which is a first reason value, which indicates that the purpose of the terminal device initiating the RRC recovery is to update the MBS configuration information.

[0186] In some optional implementations, the first base station sends a request message for UE context to the 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 a request message for UE context response sent by the second base station, the request message for UE context response carrying 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.

[0187] In some alternative implementations, the UE Context Request message carries a first cause value, which indicates that the purpose of the terminal device initiating RRC recovery is to update MBS configuration information.

[0188] In some optional implementations, the RRC release message also carries frequency priority configuration information, which is used by the terminal device to perform cell selection reselection for the MBS service.

[0189] In some optional embodiments, the processing unit 503 is further configured to release the frequency priority configuration information if the MBS service ends.

[0190] In some optional implementations, the RRC release message also carries third indication information, which is used to indicate that the terminal device can continue to receive multicast MBS services and / or the current cell has the highest frequency priority in the RRC inactive state. The third indication information is used by the terminal device to perform cell selection reselection for the MBS service.

[0191] In some optional implementations, the RRC release message also carries a first neighboring cell list containing MBS service; the communication unit 502 is further configured to, if it is determined based on the first neighboring cell list that the neighboring cell for cell reselection does not contain MBS service, enter the RRC connection state and receive MBS service in the RRC connection state; if it is determined based on the first neighboring cell list that the neighboring cell for cell reselection contains MBS service, perform cell reselection and continue to receive MBS service in the neighboring cell for cell reselection.

[0192] In some alternative implementations, the processing unit 503 is further configured to perform at least one of the following actions upon determining that the MBS service has ended:

[0193] Stop monitoring the scheduling information of MBS services scrambled with G-RNTI;

[0194] Release the bearer configuration associated with the G-RNTI;

[0195] Release the MBS configuration information associated with the G-RNTI.

[0196] In some optional embodiments, the processing unit 503 is used to determine the termination of MBS service based on the MAC CE sent by the network side, wherein the MAC CE is used to notify the termination of MBS service.

[0197] In some optional implementations, the MAC CE carries identification information of the MBS service; the processing unit 503 is used to determine the terminated MBS service based on the identification information of the MBS service carried in the MAC CE.

[0198] In some alternative implementations, the processing unit 503 is used to determine the terminated MBS service based on the G-RNTI of the PDCCH corresponding to the MAC CE.

[0199] In some alternative implementations, the MAC CE includes only the MAC CE subheader.

[0200] In some alternative implementations, the processing unit 503 is used to determine the end of MBS service based on a timer configured on the network side.

[0201] In some optional embodiments, the processing unit 503 is configured to start or restart the timer when the communication unit 502 receives the PDCCH for scheduling MBS services, and determine that the MBS service has ended if the timer times out.

[0202] In some alternative implementations, the timer is configured for G-RNTI; or, the timer is configured for multiple MBS services.

[0203] Those skilled in the art should understand that the description of the apparatus for determining configuration information in the embodiments of this application can be understood with reference to the description of the method for determining configuration information in the embodiments of this application.

[0204] Figure 6 This is a schematic structural diagram of a communication device 600 provided in an embodiment of this application. This communication device can be a terminal device or a network device. Figure 6 The communication device 600 shown includes a processor 610, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0205] Optionally, such as Figure 6 As shown, the communication device 600 may further include a memory 620. The processor 610 can retrieve and run computer programs from the memory 620 to implement the methods described in this embodiment.

[0206] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.

[0207] Optionally, such as Figure 6 As shown, the communication device 600 may also include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0208] 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.

[0209] Optionally, the communication device 600 may specifically be a network device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0210] Optionally, the communication device 600 may specifically be a mobile terminal / terminal device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0211] Figure 7 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 7 The chip 700 shown includes a processor 710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0212] Optionally, such as Figure 7 As shown, chip 700 may further include memory 720. Processor 710 can retrieve and run computer programs from memory 720 to implement the methods described in this embodiment.

[0213] The memory 720 can be a separate device independent of the processor 710, or it can be integrated into the processor 710.

[0214] Optionally, the chip 700 may also include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0215] Optionally, 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, to output information or data to other devices or chips.

[0216] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0217] Optionally, the chip can be applied to the mobile terminal / terminal device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0218] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0219] Figure 8 This is a schematic block diagram of a communication system 800 provided in an embodiment of this application. Figure 8 As shown, the communication system 800 includes a terminal device 810 and a network device 820.

[0220] The terminal device 810 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 820 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, these will not be elaborated here.

[0221] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0222] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0223] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0224] This application also provides a computer-readable storage medium for storing computer programs.

[0225] Optionally, the computer-readable storage medium can be applied to the network device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0226] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0227] This application also provides a computer program product, including computer program instructions.

[0228] Optionally, the computer program product can be applied to the network device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0229] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0230] This application also provides a computer program.

[0231] Optionally, the computer program can be applied to the network device in the embodiments of this application. When the computer program is run on the computer, it causes the computer to execute the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0232] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0233] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0234] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0235] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0236] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0237] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0238] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0239] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for determining configuration information, the method comprising: When the terminal device performs cell selection reselection to the target cell, it determines the target multimedia broadcast service (MBS) configuration information associated with the target cell, and receives multicast MBS services based on the target MBS configuration information. The terminal device receives a first signaling message, which is used to configure at least one indication message. The indication message is used to indicate whether the terminal device can continue to receive multicast MBS services in the Radio Resource Control (RRC) inactive state. The first signaling is an RRC release message.

2. The method according to claim 1, wherein, Each of the at least one indication information is associated with a Group-Radio Network Temporary Identifier (G-RNTI).

3. The method according to claim 1 or 2, wherein, The at least one indication information includes first indication information, which is associated with a first G-RNTI. The first indication information is used to indicate that the terminal device can continue to receive multicast MBS services in the RRC inactive state. The method further includes: after the terminal device enters the RRC inactive state, performing at least one of the following actions: Keep the MBS bearing associated with the first G-RNTI from suspending; Perform a partial media access control MAC reset; The discontinuous reception DRX operation associated with the first G-RNTI continues to be executed.

4. The method according to claim 1 or 2, wherein, The at least one indication information includes second indication information, which is associated with a second G-RNTI. The second indication information is used to indicate that the terminal device cannot continue to receive multicast MBS services in the RRC inactive state. The method further includes: after the terminal device enters the RRC inactive state, performing at least one of the following actions: The MBS bearing associated with the second G-RNTI is suspended; Stop executing the DRX operation associated with the second G-RNTI.

5. The method according to claim 1, wherein, The first signaling is RRC-specific signaling.

6. A terminal device, the device comprising: The acquisition unit is used to determine the target MBS configuration information associated with the target cell when the terminal device performs cell selection reselection to the target cell; The communication unit is used to receive multicast MBS services based on the target MBS configuration information; The communication unit is further configured to receive a first signaling message, the first signaling message being configured to configure at least one indication message, the indication message being configured to indicate whether the terminal device can continue to receive multicast MBS services in the Radio Resource Control (RRC) inactive state; wherein, the first signaling message is an RRC release message.

7. A terminal device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 5.

8. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 5.

9. A computer-readable storage medium for storing a computer program that causes a computer to perform the method as described in any one of claims 1 to 5.

Images