WO2024153083A1 - 一种邻小区信息指示方法、装置、终端及网络侧设备 - Google Patents

一种邻小区信息指示方法、装置、终端及网络侧设备 Download PDF

Info

Publication number
WO2024153083A1
WO2024153083A1 PCT/CN2024/072596 CN2024072596W WO2024153083A1 WO 2024153083 A1 WO2024153083 A1 WO 2024153083A1 CN 2024072596 W CN2024072596 W CN 2024072596W WO 2024153083 A1 WO2024153083 A1 WO 2024153083A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
cell
multicast service
information
connected state
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2024/072596
Other languages
English (en)
French (fr)
Inventor
刘佳敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Publication of WO2024153083A1 publication Critical patent/WO2024153083A1/zh
Priority to US19/271,806 priority Critical patent/US20250344110A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0007—Control or signalling for completing the hand-off for multicast or broadcast services, e.g. MBMS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast

Definitions

  • the present application belongs to the field of communication technology, and specifically relates to a method, device, terminal and network-side equipment for indicating neighboring cell information.
  • the existing technical solution only supports terminals in the connected state to receive multicast services.
  • the network side equipment needs to keep a large number of interested terminals in the connected state, resulting in a lot of additional control and management overhead, which is not conducive to the overall efficiency of the network.
  • the embodiment of the present application provides a method for indicating neighboring cell information, which can release a terminal to a non-connected state to receive multicast services.
  • a method for indicating neighboring cell information including:
  • the terminal obtains target information about whether a neighboring cell supports receiving a multicast service in a non-connected state from the first signaling of the serving cell.
  • a method for indicating neighboring cell information including:
  • the network side device sends a first signaling carrying target information, where the target information is information about whether a neighboring cell of a cell controlled by the network side device supports a terminal receiving a multicast service in a non-connected state.
  • a neighboring cell information indication device which is applied to a terminal, and the device includes:
  • the information receiving module is used to obtain target information about whether the neighboring cell supports receiving the multicast service in a non-connected state from the first signaling of the serving cell.
  • a neighboring cell information indication device which is applied to a network side device, and the device includes:
  • the information sending module is used to send a first signaling carrying target information, where the target information is information about whether a neighboring cell of a cell controlled by the network side device supports a terminal to receive a multicast service in a non-connected state.
  • a terminal comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the neighboring cell information indication method as described in the first aspect are implemented.
  • a network side device including a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the neighboring cell information indication method as described in the second aspect are implemented.
  • a neighboring cell information indication system comprising: a network side device and a terminal, the terminal is used to execute the steps of the neighboring cell information indication method as described in the first aspect above, and the network side device is used to Execute the steps of the neighboring cell information indication method as described in the second aspect above.
  • a readable storage medium on which a program or instruction is stored.
  • the program or instruction is executed by a processor, the steps of the neighboring cell information indication method as described in the first aspect are implemented, or the steps of the neighboring cell information indication method as described in the second aspect are implemented.
  • a chip comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the neighboring cell information indication method as described in the first aspect, or to implement the neighboring cell information indication method as described in the second aspect.
  • a computer program/program product is provided, wherein the computer program/program product is stored in a storage medium, and the computer program/program product is executed by at least one processor to implement the steps of the neighboring cell information indication method as described in the first aspect or the second aspect.
  • the first signaling is used to implement the neighboring cell information indication for receiving multicast services in a non-connected state, so that the terminal can obtain relevant information about the neighboring cells in a timely manner when receiving multicast services in a non-connected state, and then can receive the multicast services continuously in a timely manner when reselecting the target cell, thereby improving the overall network efficiency while ensuring the reception effect and network overhead.
  • FIG1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG2 is a flow chart of a method for indicating neighboring cell information in an embodiment of the present application
  • FIG3 is a flow chart of another method for indicating neighboring cell information in an embodiment of the present application.
  • FIG4 is a structural block diagram of a device for indicating neighboring cell information in an embodiment of the present application.
  • FIG5 is a structural block diagram of another neighboring cell information indication device in an embodiment of the present application.
  • FIG6 is a structural block diagram of a communication device in an embodiment of the present application.
  • FIG7 is a schematic diagram of the hardware structure of a terminal in an embodiment of the present application.
  • FIG8 is a block diagram of a terminal in an embodiment of the present application.
  • FIG. 9 is a structural block diagram of a network-side device in an embodiment of the present application.
  • first, second, etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first” and “second” are generally of the same type, and the number of objects is not limited.
  • the first object can be one or at least two.
  • “and/or” in the specification and claims represents at least one of the connected objects, and the character “/" generally represents that the objects associated with each other are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency Division Multiple Access
  • NR new radio
  • FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application.
  • the wireless communication system includes a terminal device 11 and a network side device 12 .
  • the terminal device 11 can be a mobile phone, a tablet personal computer, a laptop computer or a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), an augmented reality (AR)/virtual reality (VR) device, a robot, a wearable device (Wearable Device), a vehicle user equipment (VUE), a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home equipment with wireless communication function, such as a refrigerator, a television, a washing machine or furniture, etc.), a game console, a personal computer (personal computer, PC), a teller machine or a self-service machine and other terminal side devices, and the wearable device includes: a smart watch, a smart bracelet, a smart headset, a smart
  • the network side device 12 may include an access network device or a core network device, wherein the access network device 12 may also be referred to as a radio access network device, a radio access network (RAN), a radio access network function or a radio access network unit.
  • the access network device may include a base station, a wireless local area network (WLAN) access point, a wireless fidelity (WiFi) node, etc.
  • WLAN wireless local area network
  • WiFi wireless fidelity
  • the base station may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home B node, a home evolved B node, a transmitting and receiving point (TRP) or other appropriate terms in the field, as long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary, it should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.
  • the core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), etc.
  • MME mobility management entity
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • UPF User Plane Function
  • Policy Control Function Policy Control Function
  • LTE Long Term Evolution
  • MBSFN Multimedia Broadcast Multicast Service
  • Sc-PtM Single Cell Point to Multipoint
  • MBSFN Multimedia Broadcast Multicast Service
  • control information control channel parameters and service channel parameters, as well as scheduling information, etc.
  • data information of MBMS services are sent in broadcast mode, so that both idle terminals and connected terminals can receive MBMS services.
  • Sc-PtM is a multicast transmission method standardized after the MBMS service.
  • the biggest difference from the MBSFN method is that it is only scheduled and sent in a single cell, and the service scheduling is performed by the group-Radio Network Temporary Identity (g-RNTI).
  • g-RNTI group-Radio Network Temporary Identity
  • the broadcast control channel parameters, service identification, periodic information and other scheduling information are notified by the Physical Downlink Control Channel (PDCCH) encrypted by g-RNTI.
  • the data part is sent in multicast mode, which is equivalent to the interested terminal listening to g-RNTI to obtain data scheduling and then receiving it.
  • the network When receiving the New Radio broadcast (NR broadcast) service in the R17 version, the network carries the indication information of whether the neighboring cell supports the broadcast service in the System Information Block (SIB) and the Multicast/Broadcast Services Control Channel (MCCH).
  • SIB System Information Block
  • MCCH Multicast/Broadcast Services Control Channel
  • R17 NR multicast service only supports reception by terminals in the Radio Resource Control CONNECTED (RRC CONNECTED) state, there is no non-connected mobility problem.
  • the terminals in the connected state are switched when moving, and the interaction between the source cell and the target cell ensures that the target cell supports multicast service reception in an appropriate manner for the terminal, and sends the configuration of the target cell to the UE through dedicated signaling.
  • the existing technical solutions only support terminals in the connected state to receive multicast services.
  • the network-side equipment needs to keep a large number of interested terminals in the connected state, which has a lot of additional control and management overhead, which is not conducive to the overall efficiency of the network. Therefore, considering releasing the terminal to a non-connected state to receive multicast services will be a compromise solution to ensure both the reception effect and network overhead, thereby improving the overall efficiency of the network.
  • R17 NR multicast services only support reception by terminals in the connected state. Therefore, when the terminal moves, the service continuity of the terminal switching to the target cell is ensured through inter-interface messages and dedicated signaling.
  • the neighbor cell indication information of R17 NR broadcast services cannot be directly reused for multicast services because the reception of multicast services is slower than that of broadcast services.
  • the multicast service is more complicated.
  • the target cell may only support connected terminals to receive the multicast service, or may support non-connected terminals to receive the multicast service, or may not support the multicast service.
  • the present application provides a neighbor cell information indication method, which can realize the neighbor cell information indication of the terminal receiving multicast services in a non-connected state, so that the terminal can obtain relevant information about the neighboring cell in a timely manner when receiving the multicast service in a non-connected state, and then can receive the multicast service continuously in a timely manner when reselecting the target cell, which not only ensures the experience of the terminal receiving the multicast service, but also reduces the overall network overhead.
  • FIG. 2 is a flowchart of a method for indicating neighboring cell information provided by an embodiment of the present application, the method may include the following steps:
  • Step S201 The terminal obtains target information about whether a neighboring cell supports receiving a multicast service in a non-connected state from a first signaling of a serving cell.
  • the non-connected state may include at least one of an idle state and a deactivated state
  • the first signaling may be public signaling such as SIB signaling and MCCH signaling.
  • the terminal can obtain the target information from the first signaling of the serving cell, and can promptly obtain the support status of the relevant neighboring cells for the non-connected reception of multicast services, so that the terminal can reselect to the appropriate target cell according to the target information (such as selecting a target cell that supports non-connected reception of multicast services), and can also promptly select the appropriate method when reselecting the target cell (such as for a target cell that only supports connected reception of multicast services, the terminal can promptly switch to a connected state to receive multicast services), thereby ensuring the continuity of multicast service reception, and improving the terminal experience and system efficiency on the basis of ensuring the reception effect.
  • the target information such as selecting a target cell that supports non-connected reception of multicast services
  • the terminal can also promptly select the appropriate method when reselecting the target cell (such as for a target cell that only supports connected reception of multicast services, the terminal can promptly switch to a connected state to receive multicast services), thereby ensuring the continuity of multicast service reception, and improving the
  • the first signaling is used to implement the neighboring cell information indication for receiving multicast services in a non-connected state, so that the terminal can obtain relevant information about the neighboring cells in a timely manner when receiving multicast services in a non-connected state, and then can receive the multicast services continuously in a timely manner when reselecting the target cell, thereby improving the overall network efficiency while ensuring the reception effect and network overhead.
  • This embodiment describes an example of transmitting the first signaling carrying target information.
  • Case 1 The network side device sends a first signaling carrying target information, and the terminal obtains target information about whether the neighboring cell supports receiving the multicast service in a non-connected state from the first signaling of the serving cell.
  • the network side device sends information about whether the neighboring cells of the cell controlled by the network side device support the terminal to receive multicast services in a non-connected state through a first instruction based on the support of the neighboring cells of each cell controlled by it for non-connected reception of multicast services.
  • each cell controlled by the above-mentioned network side device can be a cell that supports non-connected reception of multicast services, or a cell that does not support non-connected reception of multicast services. It can be understood that when the cell controlled by the network side device does not support non-connected reception of multicast services, if the cell has at least one neighboring cell that supports non-connected reception of multicast services, the first signaling can also indicate whether the neighboring cell of the cell supports receiving the target information of the multicast service in a non-connected state, so that the terminal of the cell can reselect to a suitable target cell according to the target information, and/or can timely select a suitable method when reselecting to the target cell, thereby solving the mobility problem of the terminal receiving multicast services in a non-connected state.
  • the target information carried by the first signaling includes: first information and/or second information, the first information is used to indicate neighboring cells that support receiving multicast services in a non-connected state, and the second information is used to indicate each neighboring cell. Supports multicast service information received in a non-connected state.
  • a cell can be divided into three categories according to whether and how it supports multicast services:
  • MRB Multicast/Broadcast Services Radio Bearer
  • Category 2 Supports terminals to receive multicast services in a non-connected state, and MRB configuration is scheduled in PTM/G-RNTI multicast mode;
  • the third category does not support multicast scheduling, but can provide multicast service transmission to terminals in unicast mode (such as unicast/data radio bearer (DRB)/cell wireless network temporary identifier (Cell-Radio Network Temporary Identifier, C-RNTI), etc.).
  • unicast/data radio bearer DRB
  • C-RNTI Cell-Radio Network Temporary Identifier
  • the network side device can use the cell as the granularity to indicate the neighboring cells' support for non-connected reception of multicast services through the first information. For example, if all multicast services in the cell are sent in the first category (i.e., in a connected transmission mode), the cell belongs to the above-mentioned first category of cells; as long as there is at least one multicast service in the cell that is sent in the second category (i.e., in a non-connected transmission mode), the cell can belong to the above-mentioned second category of cells; if all multicast services in the cell are sent in the third category (i.e., in a unicast transmission mode), the cell belongs to the above-mentioned third category of cells. At this time, the network side device can use the first information to indicate the neighboring cells of any cell it controls that belong to the above-mentioned second category of cells.
  • the above neighbor cell information indication method is for all multicast services in the cell, and the granularity is relatively coarse. Therefore, the network side device can also use a specific multicast service as the granularity, and indicate the support of each neighbor cell for the non-connected reception of the specific multicast service through the second information. For example, if the specific multicast service is sent in the cell using the above first type of method, then this cell belongs to the first type of cell for this multicast service. If the multicast service is sent in the cell using the above second type of method, then this cell belongs to the second type of cell for this multicast service. If the multicast service is sent in the cell using the third type of method, then this cell belongs to the third type of cell for this multicast service.
  • the network side device can use the second information to indicate the neighbor cell that belongs to the second type of cell relative to any related multicast service (such as a multicast service that the terminal has joined in the cell it controls).
  • this neighbor cell information indication method is for a single multicast service, and the granularity is finer.
  • the multicast service that the terminal has joined refers to: the terminal has joined successfully (that is, the network side device has authorized the terminal to receive) and has been maintaining a joined state.
  • SIB signaling will carry information about MCCH scheduling (such as scheduling period, etc.), that is, the terminal usually reads the SIB signaling first, and then finds the relevant MCCH signaling based on the SIB signaling, compared with MCCH signaling, SIB signaling is usually used to carry coarse-grained information. Therefore, SIB signaling can be used to carry the above-mentioned first information with cell as the granularity, and since MCCH can be used to carry fine-grained information, MCCH signaling can be flexibly used to carry the above-mentioned first information with cell as the granularity and/or the second information with specific multicast services as the granularity.
  • the first information carried by the above-mentioned first signaling may be: a first cell ID list or a first cell index list, wherein:
  • the first cell ID list includes the ID of each neighboring cell carried in the first signaling for indicating support for receiving at least one multicast service in a non-connected state, and the ID of the neighboring cell may be a New Radio Cell Global Identifier Identity Document (NCGI ID).
  • NCGI ID New Radio Cell Global Identifier Identity Document
  • the second information carried by the MCCH signaling may be: a second cell ID list or a second cell index list corresponding to each multicast service (such as service description information such as a temporary mobile group identity (TMGI) of the multicast service), wherein:
  • TMGI temporary mobile group identity
  • the second cell ID list corresponding to each multicast service includes the IDs of each neighboring cell that supports receiving the multicast service in a non-connected state, and the ID of the neighboring cell may be an NCGI ID;
  • the second cell index list corresponding to each multicast service is the position or sorting information of each neighboring cell supporting the reception of the multicast service in the non-connected state in the cell ID list carried by the first signaling or other signaling.
  • the first signaling or other signaling has indicated the neighboring cell ID list supporting the reception of a multicast service in the non-connected state (such as the first cell ID list mentioned above)
  • the second cell index list may include three index values of 0, 1, and 2, indicating that in the first cell ID list, the neighboring cells corresponding to the first three IDs are the neighboring cells supporting the reception of the multicast service in the non-connected state. Bits may also be used to identify the neighboring cells supporting the reception of the multicast service in the non-connected state.
  • the second cell index list may include the bit "11100000", the first three 1s representing that the cell IDs ranked in the first three places in the corresponding neighboring cell ID list correspond to the neighboring cells supporting the reception of the multicast service in the non-connected state, and the last five 0s representing that the cell IDs ranked in the last five places in the neighboring cell ID list are not the neighboring cells that do not support the reception of the multicast service in the non-connected state.
  • Case 2 When the neighboring cell's support for non-connected reception of multicast services changes, the network-side device updates the target information and sends a first signaling carrying the updated target information.
  • the terminal receives the changed first signaling of the serving cell, which is generated when the information about whether the neighboring cell supports non-connected reception of multicast services changes; the terminal receives the changed first signaling from the serving cell.
  • target information about whether a neighboring cell supports receiving a multicast service in a non-connected state is retrieved.
  • the network side device can update the corresponding target information through the SIB update or MCCH update process, so that the interested terminal can read the updated corresponding target information in time after being notified of the SIB update or MCCH update.
  • the network side device is able to update the target information in a timely manner, and through the target information carried in the SIB signaling (i.e., the neighboring cell information that supports the reception of multicast services in a non-connected state), and/or through the target information carried in the MCCH signaling (i.e., the neighboring cell information that supports the reception of multicast services in a non-connected state, and/or the specific information on whether each multicast service supports non-connected reception in each neighboring cell), the terminal can obtain the relevant neighboring cell information in a timely manner, so as to reselect a suitable target cell during the cell reselection process, and/or when reselecting the target cell, it can timely select a suitable method to ensure the reception continuity of the multicast service, thereby improving the terminal reception experience and system efficiency on the basis of ensuring the terminal reception effect.
  • the target information carried in the SIB signaling i.e., the neighboring cell information that supports the reception of multicast services in a non-connected state
  • This implementation describes an example of how a terminal determines a target cell before accessing the target cell and receiving a multicast service to which the terminal has joined from the target cell.
  • Case 1 When the triggering conditions of the cell selection and/or reselection mechanism are met, the terminal determines the target cell according to the above target information.
  • mobility management is an essential mechanism for cellular mobile communication systems, which can assist in achieving load balancing, improving user experience and overall system performance.
  • mobility management is divided into two categories: mobility management in a non-connected state and mobility management in a connected state.
  • Mobility management in a connected state is mainly implemented through cell switching, which is fully controlled by network-side equipment and assisted in measurement by the terminal; mobility management in a non-connected state is implemented through cell selection/reselection, and network-side equipment assists in configuration.
  • the terminal can take the completion of Public Land Mobile Network (PLMN) selection and/or the access technology stored (or indicated) as a prerequisite for cell selection, and can use the R criterion as a trigger for cell reselection.
  • PLMN Public Land Mobile Network
  • the terminal determines at least one candidate target cell from each neighboring cell indicated by the target information; and the terminal determines the target cell according to at least one candidate target cell according to at least one of the following:
  • the terminal determines, as the target cell, a candidate target cell among the at least one candidate target cell that supports receiving, in a non-connected state, a multicast service that the terminal has joined, wherein, in the case where the number of multicast services that the terminal has joined is multiple, the candidate target cell supports receiving, in a non-connected state, the multicast service that the terminal has joined, means that the candidate target cell supports receiving, in a non-connected state, all multicast services that the terminal has joined;
  • the terminal determines any candidate target cell among the at least one candidate target cell as the target cell when none of the at least one candidate target cell supports receiving the multicast service to which the terminal has joined in a non-connected state;
  • Item A-3 When the at least one candidate target cell partially supports receiving the multicast service to which the terminal has joined in a non-connected state, the terminal determines, as the target cell, a candidate target cell among the at least one candidate target cell that supports the largest number of multicast services to which the terminal has joined or supports the highest priority of the multicast service;
  • the candidate target cell does not support receiving the multicast service that the terminal has joined in the non-connected state, which means: The candidate target cell does not support receiving all multicast services that the terminal has joined in a non-connected state; the candidate target cell partially supports receiving the multicast services that the terminal has joined in a non-connected state, which means that the candidate target cell supports receiving a part of the multicast services that the terminal has joined in a non-connected state.
  • the terminal can give priority to selecting a candidate target cell that supports non-connected reception of all multicast services to which it has joined (the terminal can join one or more multicast services) as the target cell; if there are multiple candidate target cells that support non-connected reception of all multicast services to which the terminal has joined, the terminal can select one of them (such as selecting the candidate target cell with the best link quality) as the target cell based on its own implementation.
  • the terminal can directly use the candidate target cell as the target cell; when there are multiple candidate target cells, the terminal can arbitrarily select a candidate target cell, or select a candidate target cell according to its own implementation (such as based on link quality), and use the selected candidate target cell as the target cell.
  • the terminal can give priority to selecting a candidate target cell that supports non-connected reception of as many multicast services as possible that the terminal has joined, or the terminal can give priority to selecting a candidate target cell that supports non-connected reception of high-priority multicast services that the terminal has joined, and use the selected candidate target cell as the target cell.
  • Case 2 The terminal determines the target cell when the triggering conditions of the cell selection and/or reselection mechanism are met.
  • the terminal can directly determine the target cell according to the cell selection criteria, cell reselection criteria and other rules, and when accessing the target cell subsequently, select an appropriate way to receive the multicast service according to the target information.
  • the source cell may release the terminal back to the non-connected state.
  • the terminal does not know the neighboring cell's support for non-connected reception of multicast services from the SIB signaling and/or MCCH signaling of the source cell (i.e., the target information is not obtained from the source cell)
  • it can select the target cell according to the cell reselection criteria, and obtain the information and configuration of the target cell supporting the reception of multicast services (such as supporting non-connected reception of multicast services that the terminal has joined) by reading the SIB and MCCH signaling related to the multicast service of the target cell, so that the terminal can directly stay in the non-connected state to receive the multicast service when the multicast service is activated next time.
  • the terminal can also try to select the target cell that supports the non-connected reception of the multicast service that the terminal has joined based on situation 1, so as to obtain the configuration directly in the target cell through the SIB/MCCH method, and continue to receive the multicast service in the non-connected state.
  • the terminal may determine a suitable target cell according to the target information to ensure the continuity of multicast service reception.
  • the terminal may also determine a suitable target cell according to the cell selection and/or reselection mechanism adopted by the terminal to reduce configuration changes to the terminal.
  • This implementation manner describes an example of a manner in which a terminal accesses a target cell after determining the target cell, and the terminal receives a multicast service from the target cell.
  • Case 1 When the terminal receives a multicast service that the terminal has joined from the serving cell in a non-connected state, and the target cell supports receiving the multicast service that the terminal has joined in a non-connected state, the terminal maintains a non-connected state to access the target cell, and the terminal receives the multicast service that the terminal has joined from the target cell in a non-connected state. The terminal has joined the multicast service.
  • the terminal can obtain the multicast service configuration it has joined through the SIB and/or MCCH of the target cell, and continue to receive the multicast service in a non-connected state.
  • Case 2 When the terminal receives the multicast service that the terminal has joined from the serving cell in a non-connected state, and the target cell does not support receiving the multicast service that the terminal has joined in a non-connected state, the terminal switches from the non-connected state to the connected state and accesses the target cell, and the terminal receives the multicast service that the terminal has joined from the target cell in a connected state.
  • the terminal is converted from a non-connected state to a connected state before or after accessing the target cell.
  • the terminal can initiate the state transition of RRC before or after accessing the target cell, and enter the connected state from the non-connected state. If the terminal enters the connected state before reselecting or accessing the target cell, it is equivalent to the terminal entering the connected state in the source cell. At this time, the interaction between the source cell and the target cell and the dedicated signaling process can ensure the continuity of the terminal receiving multicast services from the source cell to the target cell. This method is better for the service continuity of the terminal; if the terminal enters the connected state after reselecting or accessing the target cell, it is equivalent to the terminal entering the connected state in the target cell.
  • Case 3 When the terminal receives the multicast service to which the terminal has joined from the serving cell in a connected state, and the target cell does not support receiving the multicast service to which the terminal has joined in a non-connected state, the terminal remains in a connected state and receives the multicast service to which the terminal has joined from the target cell.
  • the terminal needs to perform related operations according to the mobility of the connected state (such as the interaction between the source cell and the target cell and the dedicated signaling process to ensure the continuity of the terminal receiving the multicast service from the source cell to the target cell).
  • Case 4 When the terminal receives the multicast service to which the terminal has joined from the serving cell in a connected state, and the target cell supports receiving the multicast service to which the terminal has joined in a non-connected state, the terminal switches from the connected state to the non-connected state after or before switching from the serving cell to the target cell through a connected state conversion process, and receives the multicast service to which the terminal has joined from the target cell in the non-connected state.
  • the terminal in the connected state can directly go through the connected state conversion process, with the source cell and the target cell interacting, and through the dedicated signaling given by the target cell, the terminal can first switch to the target cell to receive multicast services in a connected state. After the switch, the target cell can release the terminal and allow it to continue to receive multicast services in a non-connected state.
  • Case 5 When the number of multicast services that the terminal has joined is multiple, it is determined whether the terminal is in a connected state or a non-connected state after accessing the target cell based on the respective priorities of the multiple multicast services that the terminal has joined, the preference information of the terminal, and at least one of the indication information of the network side device, and the multiple multicast services that the terminal has joined are received from the target cell in the connected state or the non-connected state.
  • the terminal when the terminal has a tendency (such as a strong tendency to save power) or the network has an indication (such as an indication issued when the network is overloaded), the terminal can also select some multicast services with higher priority among multiple multicast services that have been joined to receive, and abandon the reception of other low-priority multicast services.
  • a tendency such as a strong tendency to save power
  • the network has an indication (such as an indication issued when the network is overloaded)
  • the terminal when the terminal has a tendency (such as a strong tendency to save power) or the network has an indication (such as an indication issued when the network is overloaded)
  • the terminal can also select some multicast services with higher priority among multiple multicast services that have been joined to receive, and abandon the reception of other low-priority multicast services.
  • the terminal may select a target cell that supports receiving a high-priority multicast service in a non-connected state, and obtain configuration through the SIB and/or MCCH of the target cell, so as to continue to receive the high-priority multicast service in a non-connected state, while discarding other low-priority multicast services that need to be received in a connected state.
  • the network side device may send indication information to indicate the respective priorities of multiple multicast services that the terminal has joined.
  • the network side device configures the service cell of the terminal to support receiving all multicast services that the terminal has joined in a non-connected state, or configures the service cell of the terminal to support receiving all multicast services that the terminal has joined in a connected state.
  • the network side device may adjust the support of the terminal's service cell for multicast services according to actual conditions. For example, when the network load is light, the network side device may configure the terminal's service cell to support receiving all multicast services that the terminal has joined in a connected state, and when the network load is too heavy, the network side device may configure the terminal's service cell to support receiving all or part of the multicast services that the terminal has joined in a non-connected state. In addition, the network side device may also adjust the terminal's service cell's support for multicast services according to information such as the number of terminals that can receive multicast services in a non-connected state and access the controlled cell, so that the terminal receives the multicast services in an appropriate manner.
  • the terminal selects a suitable mode (ie switches to a suitable state) to receive the multicast service according to the target information, combined with its own inclination or network indication, which can improve the terminal's receiving experience while ensuring the receiving effect.
  • This embodiment describes the configuration information of the multicast service.
  • Case 1 The terminal reads the target configuration information of the multicast service that the terminal has joined in the target cell from the SIB signaling and/or MCCH signaling of the target cell, and receives the multicast service that the terminal has joined from the target cell according to the target configuration information.
  • the premise that the terminal can successfully obtain the new configuration through SIB and/or MCCH after moving to or accessing the target cell and continue to receive services in a non-connected state is that all multicast services that the terminal has joined support non-connected state reception in the target cell. As long as there is a multicast service that does not support this transmission mode, the terminal must migrate the RRC state and enter the connected state to complete the reception under the control of the network side device.
  • the network side device can configure the connected state reception mode for the multicast service that does not support non-connected state reception so that the terminal can receive it, and for the multicast service that supports the connected state, the terminal can continue to read the SIB and/or MCCH to obtain the configuration and receive it.
  • the terminal receives, in a non-connected state, from a target cell a multicast service that the terminal has joined, according to the target configuration information, including at least one of the following:
  • the terminal When the original configuration information is the same as the target configuration information, the terminal retains the entity and parameters corresponding to the original configuration information, and receives the multicast service that the terminal has joined from the target cell in a non-connected state, wherein the original configuration information is the configuration information of the multicast service that the terminal has joined in the serving cell;
  • the terminal When the original configuration information and the target configuration information are different, the terminal performs reconfiguration according to the target configuration information, and receives the multicast service that the terminal has joined from the target cell in a non-connected state.
  • the terminal that is interested in or has received the multicast service in the source cell stores the configuration information of the active cell (i.e., the original configuration information), when obtaining the new multicast service configuration (i.e., the target configuration information) again from the SIB and/or MCCH of the target cell, the terminal can compare the specific content of the configuration. If the configuration is the same, the existing entity operation and parameters can be directly maintained.
  • the parameter needs to be reconfigured and the new configuration parameter is applied immediately; if the parameter reconfiguration affects the operation of the entire entity, such as involving the reconfiguration of the sequence number (SN) length of the Radio Link Control (RLC) or Packet Data Convergence Protocol (PDCP) entity, the entire entity needs to be re-established (such as re-establishment) process.
  • SN sequence number
  • RLC Radio Link Control
  • PDCP Packet Data Convergence Protocol
  • the terminal reconfigures according to the target configuration information, including at least one of the following:
  • Item B-1 the terminal retains the value of the SN state variable or the COUNT state variable of the L2 entity
  • Item B-2 The terminal re-establishes the RLC entity in the L2 entity;
  • Item B-3 The terminal retains the value of the COUNT state variable of the PDCP in the L2 entity.
  • the COUNT value of the PDCP entity needs to be synchronized or continuous, so the PDCP should try to keep the COUNT value in a unified order before and after the reselection.
  • the COUNT value is maintained, that is, when the target configuration information is an AM MRB configuration, the terminal retains the value of the COUNT state variable of the PDCP in the L2 entity;
  • the reception can be started with the initial state of the state variable, or the SN state variable of the first data packet received is used as the initial value of the receiving state variable, or the initial value of the state variable is calculated.
  • the mapping relationship between the Quality of Service (QoS) flow of the source cell and the target cell to the DRB is preferably kept unified, so as to ensure that the COUNT value of the PDCP entity before and after the reselection can be as continuous as possible, thereby ensuring the continuous reception of the terminal's services and the synchronization of the COUNT value in the target cell.
  • QoS Quality of Service
  • Case 2 The network side device recovers or sends MRB configuration information, where the MRB configuration information is used for the terminal to receive the multicast service that the terminal has joined from the target cell in a connected state after accessing the target cell.
  • the target cell can support (or only support) the MRB configuration of the terminal in the connected state for the multicast service of interest to the terminal, and schedule it through the PTM/G-RNTI multicast mode.
  • the network side device will restore or configure the MRB and related multicast scheduling configuration information to complete Scheduling and transmission of continued connection status.
  • Case 3 The network side device sends DRB configuration information, and the DRB configuration information is used by the terminal to receive the multicast service that the terminal has joined from the target cell in a connected state after accessing the target cell.
  • the target cell may support (or only support) the DRB configuration of the connected terminal for the multicast service of interest to the terminal, and schedule it in a point-to-point (PTP) or C-RNTI unicast manner.
  • PTP point-to-point
  • the context configuration information of the terminal includes not only the MRB and multicast scheduling configuration of the multicast service, but also the DRB configuration of the accompanying multicast service of the multicast service.
  • the recovery or switching command of the source cell or the target cell only needs to include the DRB configuration; if the terminal is in an idle state, during the interaction between the source cell and the target cell, or after the terminal accesses the target cell, the target cell will configure the DRB for the terminal for service reception.
  • a terminal when a terminal needs to reselect from a source cell to a target cell, if the target cell supports non-connected reception of multicast services of interest to the terminal, after the terminal accesses the target cell, it can obtain the multicast service configuration through SIB and/or MCCH, and retain or reset the terminal's configuration application and L2 entity and related parameters accordingly, so that the terminal can perform continuous reception.
  • This implementation manner describes the situation where the neighboring cells include cells controlled by adjacent network-side devices (eg, across base stations).
  • Case 1 The network side device obtains the multicast service configuration information of the neighboring cell from the interface message of the adjacent network side device, and configures the multicast service configuration information of the controlled cell to be the same as the multicast service configuration information of the neighboring cell.
  • the first signaling of the network side device also carries multicast service configuration information of the cell controlled by the network side device.
  • the multicast service configuration information of a cell is used for the terminal to receive the multicast service that the terminal has joined in the cell.
  • the cell controlled by the network side device needs to inform the terminal through SIB and/or MCCH that the neighboring cell supports non-connected reception of multicast services. If there are cross-network side devices (such as the next generation Node B (gNB) nodes), this information needs to be transmitted through the interface message between gNB nodes, and when this information of the neighboring cell changes, it is necessary to promptly notify the surrounding cells so that other cells can update their neighboring cell information in their SIB and/or MCCH in a timely manner.
  • gNB next generation Node B
  • the multicast service configuration information includes at least one of the following: a mapping relationship between a multicast service QoS flow and an MRB; and configuration information of an L2 entity.
  • the configuration information of adjacent cells is preferably consistent.
  • Case 2 The network side device receives multicast service update information of a cell controlled by an adjacent network side device, wherein the multicast service update information indicates whether the adjacent cell supports multicast service.
  • the network side device updates the target information according to the multicast service update information.
  • the interface between base stations needs to be used to exchange information about neighboring cells that support non-connected multicast service reception (such as a service list).
  • information about the multicast service of the local cell i.e., a cell controlled by a base station
  • the neighboring base station needs to be notified in a timely manner through an interface message.
  • the neighboring base station will update its own neighboring cell information based on the latest information received, thereby ensuring that the terminal of the neighboring base station can read the correct target information.
  • each adjacent network side device exchanges the neighboring cell's support status for non-connected multicast service reception and configuration information for non-connected multicast service reception through an interface, thereby ensuring the continuity of the terminal receiving multicast services across cells.
  • an embodiment of the present application provides another method for indicating neighboring cell information, the method comprising at least the following steps:
  • Step S301 a network side device sends a first signaling carrying target information, where the target information is information about whether a neighboring cell of a cell controlled by the network side device supports a terminal receiving a multicast service in a non-connected state.
  • the network side device sends the first signaling carrying the target information, including:
  • the network side device sends a first signaling carrying target information.
  • the method further includes:
  • the network side device receives multicast service update information of a cell controlled by an adjacent network side device, wherein the multicast service update information indicates that information on whether the adjacent cell supports the multicast service has changed;
  • the network side device updates the target information according to the multicast service update information
  • the network side device sends a first signaling carrying updated target information.
  • the method further includes at least one of the following:
  • the network side device recovers or sends MRB configuration information, where the MRB configuration information is used for the terminal to receive the multicast service that the terminal has joined from the target cell in a connected state after accessing the target cell;
  • the network side device sends DRB configuration information, where the DRB configuration information is used by the terminal to receive the multicast service that the terminal has joined from the target cell in a connected state after the terminal accesses the target cell.
  • the first signaling further carries multicast service configuration information of a cell controlled by the network side device, and the multicast service configuration information of a cell is used for the terminal to receive the multicast service that the terminal has joined in the cell; the method further includes:
  • the network side device obtains the multicast service configuration information of the neighboring cell from the interface message of the adjacent network side device;
  • the network side device configures the multicast service configuration information of the controlled cell to be the same as the multicast service configuration information of the neighboring cell.
  • the multicast service configuration information includes at least one of the following:
  • the method further includes:
  • the network side device configures the mapping relationship between the multicast service QoS flow of the controlled cell and the DRB to be the same as the mapping relationship between the multicast service QoS flow of the neighboring cell of the cell and the DRB.
  • the method further includes:
  • the network side device configures the serving cell of the terminal to support receiving all multicast services that the terminal has joined in a non-connected state
  • the network side device configures the serving cell of the terminal to support receiving all multicast services to which the terminal has joined in a connected state.
  • the method further includes:
  • the network side device sends indication information, where the indication information is used to indicate respective priorities of multiple multicast services that the terminal has joined.
  • the neighboring cell information indication method provided in the embodiment of the present application may be executed by a neighboring cell information indication device.
  • the neighboring cell information indication method performed by the neighboring cell information indication device is taken as an example to illustrate the neighboring cell information indication device provided in the embodiment of the present application.
  • an embodiment of the present application provides a neighboring cell information indication device, which can be applied to a terminal.
  • the neighboring cell information indication device 100 includes:
  • the information receiving module 101 is configured to obtain target information about whether a neighboring cell supports receiving a multicast service in a non-connected state from a first signaling of a serving cell.
  • the target information includes: first information and/or second information
  • the first information is used to indicate a neighboring cell that supports receiving a multicast service in a non-connected state
  • the second information is used to indicate that each neighboring cell supports multicast service information received in a non-connected state.
  • the first signaling of the serving cell includes at least one of the following:
  • SIB signaling of the serving cell the SIB signaling carrying the first information
  • the MCCH signaling of the serving cell the MCCH signaling carrying the first information and/or the second information.
  • the device further comprises:
  • a first determination module configured to determine a target cell when a triggering condition of a cell selection and/or reselection mechanism is met
  • the first processing module is used to access the target cell and receive from the target cell the multicast service to which the terminal has joined.
  • the device further comprises:
  • a second determination module is used to determine a target cell according to the target information when a triggering condition of a cell selection and/or reselection mechanism is met;
  • the second processing module is used to access the target cell and receive the multicast service that the terminal has joined from the target cell.
  • the second determining module includes:
  • a first determination submodule is used to determine at least one candidate target cell from each neighboring cell indicated by the target information when a triggering condition of a cell selection and/or reselection mechanism is met;
  • the second determination submodule is configured to determine the target cell according to at least one of the following:
  • determining, as the target cell, a candidate target cell among the at least one candidate target cell that supports receiving, in a non-connected state, a multicast service that the terminal has joined wherein, in the case where the number of multicast services that the terminal has joined is multiple, the candidate target cell supports receiving, in a non-connected state, the multicast service that the terminal has joined, means that the candidate target cell supports receiving, in a non-connected state, all multicast services that the terminal has joined;
  • the at least one candidate target cell In a case where the at least one candidate target cell partially supports receiving the multicast service to which the terminal has joined in a non-connected state, determining, among the at least one candidate target cell, a candidate target cell that supports the largest number of multicast services to which the terminal has joined or supports the highest priority of the multicast service as the target cell;
  • the candidate target cell does not support receiving the multicast service that the terminal has joined in the non-connected state, which means that the candidate target cell does not support receiving all multicast services that the terminal has joined in the non-connected state; the candidate target cell partially supports receiving the multicast service that the terminal has joined in the non-connected state, which means that the candidate target cell supports receiving a part of the multicast service that the terminal has joined in the non-connected state.
  • the first processing module or the second processing module includes at least one of the following:
  • a first receiving module configured to, when the terminal receives a multicast service that the terminal has joined from the serving cell in a non-connected state, and the target cell supports receiving the multicast service that the terminal has joined in a non-connected state, maintain non-connected access to the target cell, and the terminal receives the multicast service that the terminal has joined from the target cell in a non-connected state;
  • the second receiving module is used for converting from a non-connected state to a connected state and accessing the target cell when the terminal receives the multicast service that the terminal has joined from the serving cell in a non-connected state and the target cell does not support receiving the multicast service that the terminal has joined in a non-connected state, and the terminal receives the multicast service that the terminal has joined from the target cell in a connected state, wherein the terminal converts from the non-connected state to the connected state before or after accessing the target cell.
  • the first processing module or the second processing module includes at least one of the following:
  • a third receiving module is configured to, when the terminal receives the multicast service that the terminal has joined from the serving cell in a connected state and the target cell does not support receiving the multicast service that the terminal has joined in a non-connected state, remain in a connected state and receive the multicast service that the terminal has joined from the target cell;
  • the fourth receiving module is used to convert from the connected state to the non-connected state after or before switching from the serving cell to the target cell through a connected state conversion process, and receive the multicast service to which the terminal has joined from the target cell in the non-connected state, when the terminal receives the multicast service to which the terminal has joined from the serving cell in a connected state, and the target cell supports receiving the multicast service to which the terminal has joined in a non-connected state.
  • the first processing module or the second processing module includes:
  • a state determination module configured to determine whether the terminal is in a connected state or a non-connected state after accessing the target cell according to respective priorities of a plurality of multicast services to which the terminal has joined, preference information of the terminal, and at least one of indication information of a network-side device;
  • the fifth receiving module is used to receive the information that the terminal has joined from the target cell in a connected state or a non-connected state. Multiple multicast services.
  • the first processing module or the second processing module includes:
  • a first reading module is used to read the target configuration information of the multicast service that the terminal has joined in the target cell from the SIB signaling and/or MCCH signaling of the target cell;
  • the sixth receiving module is used to receive the multicast service that the terminal has joined from the target cell according to the target configuration information.
  • the sixth receiving module includes at least one of the following:
  • a first receiving submodule is configured to retain entities and parameters corresponding to the original configuration information when the original configuration information is the same as the target configuration information, and receive the multicast service that the terminal has joined from the target cell in a non-connected state, wherein the original configuration information is configuration information of the multicast service that the terminal has joined in the serving cell;
  • the second receiving submodule is used to, when the original configuration information and the target configuration information are different, perform reconfiguration according to the target configuration information, and receive the multicast service that the terminal has joined from the target cell in a non-connected state.
  • the second receiving submodule includes at least one of the following:
  • a first reconfiguration module configured to retain a value of an SN state variable or a COUNT state variable of the L2 entity
  • a second reconfiguration module configured to reestablish the RLC entity in the L2 entity
  • the third reconfiguration module is used to retain the value of the COUNT state variable of the PDCP in the L2 entity.
  • the first reconfiguration module includes:
  • the reconfiguration submodule is used to retain the value of the COUNT state variable of the PDCP in the L2 entity when the target configuration information is the AM MRB configuration.
  • the first information is: a first cell ID list or a first cell index list;
  • the first cell ID list includes the IDs of each neighboring cell carried in the first signaling and used to indicate the IDs of each neighboring cell supporting reception of at least one multicast service in a non-connected state;
  • the first cell index list is a cell ID list carried in other signaling, and supports location or ranking information of each neighboring cell that receives at least one multicast service in a non-connected state.
  • the second information is: a second cell ID list or a second cell index list corresponding to each multicast service;
  • the second cell ID list corresponding to each multicast service includes the IDs of each neighboring cell that supports receiving the multicast service in a non-connected state
  • the second cell index list corresponding to each multicast service is a cell ID list carried in the first signaling or other signaling, and supports location or ranking information of each neighboring cell that receives the multicast service in a non-connected state.
  • the device further comprises:
  • a signaling receiving module configured to receive a first signaling after a service cell is changed, wherein the first signaling after a service cell is changed is generated when information on whether a neighboring cell supports receiving a multicast service in a non-connected state is changed;
  • the information re-acquisition module is used to re-acquire target information about whether the neighboring cell supports receiving the multicast service in a non-connected state from the changed first signaling of the serving cell.
  • the neighboring cell information indication device provided in the embodiment of the present application can implement the neighboring cell information indication described in the first aspect.
  • the various processes implemented by the embodiment of the method are shown in the figure, and the same technical effect is achieved. To avoid repetition, they are not described here.
  • the information sending module 201 is used to send a first signaling carrying target information, where the target information is information about whether a neighboring cell of a cell controlled by the network side device supports a terminal to receive a multicast service in a non-connected state.
  • the information sending module 201 includes:
  • the first sending submodule is used to send a first signaling carrying target information when at least one neighboring cell of the cell controlled by the network side device supports receiving a multicast service in a non-connected state.
  • the device further comprises:
  • a first processing module is configured to receive multicast service update information of a cell controlled by an adjacent network-side device, wherein the multicast service update information indicates whether information of whether the adjacent cell supports the multicast service has changed;
  • a second processing module configured to update the target information according to the multicast service update information
  • the third processing module is used to send a first signaling carrying updated target information.
  • the device further comprises at least one of the following:
  • a fourth processing module configured to restore or send MRB configuration information, wherein the MRB configuration information is used for the terminal to receive the multicast service that the terminal has joined from the target cell in a connected state after accessing the target cell;
  • the fifth processing module is used to send DRB configuration information, where the DRB configuration information is used by the terminal to receive the multicast service that the terminal has joined from the target cell in a connected state after the terminal accesses the target cell.
  • the first signaling further carries multicast service configuration information of a cell controlled by the network side device, and the multicast service configuration information of a cell is used for the terminal to receive the multicast service that the terminal has joined in the cell;
  • the apparatus further includes:
  • a sixth processing module configured to obtain multicast service configuration information of a neighboring cell from an interface message of an adjacent network side device
  • the seventh processing module is used to configure the multicast service configuration information of the controlled cell to be the same as the multicast service configuration information of the neighboring cell.
  • the multicast service configuration information includes at least one of the following:
  • the device further comprises:
  • the relationship configuration module is used to configure the mapping relationship between the multicast service QoS flow of the controlled cell and the DRB to be the same as the mapping relationship between the multicast service QoS flow of the neighboring cell of the cell and the DRB.
  • the device further comprises:
  • the eighth processing module is used to configure the service cell of the terminal to support receiving all multicast services that the terminal has joined in a non-connected state; or to configure the service cell of the terminal to support receiving all multicast services that the terminal has joined in a connected state.
  • the device further comprises:
  • the ninth processing module is used to send indication information, where the indication information is used to indicate the respective priorities of multiple multicast services that the terminal has joined.
  • the neighbor cell information indication device provided in the embodiment of the present application can implement each process implemented by the neighbor cell information indication method embodiment described in the second aspect and achieve the same technical effect. To avoid repetition, it will not be described here.
  • an embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, wherein the memory 902 stores a program or instruction that can be run on the processor 901, for example, when the communication device 900 is a terminal, the program or instruction is executed by the processor 901 to implement the various steps of the embodiment of the neighboring cell information indication method described in the first aspect above, and can achieve the same technical effect, and when the communication device 900 is a network side device, the program or instruction is executed by the processor 901 to implement the various steps of the embodiment of the neighboring cell information indication method described in the second aspect above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • FIG. 7 it is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 1000 is used to execute the various steps of the embodiment of the neighboring cell information indication method described in the first aspect above, and can achieve the same technical effect.
  • the terminal 1000 includes but is not limited to: at least some of the components of the radio frequency unit 1001, the network module 1002, the audio output unit 1003, the input unit 1004, the sensor 1005, the display unit 1006, the user input unit 1007, the interface unit 1008, the memory 1009 and the processor 1010.
  • the terminal 1000 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1010 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system.
  • a power source such as a battery
  • the terminal structure shown in FIG7 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently, which will not be described in detail here.
  • the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode.
  • the display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc.
  • the user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072.
  • the touch panel 10071 is also called a touch screen.
  • the touch panel 10071 may include two parts: a touch detection device and a touch controller.
  • Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control key, a switch key, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.
  • the RF unit 1001 can transmit the data to the processor 1010 for processing; in addition, the RF unit 1001 can send uplink data to the network side device.
  • the RF unit 1001 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
  • the memory 1009 can be used to store software programs or instructions and various data.
  • the memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc.
  • the memory 1009 may include a volatile memory or a non-volatile memory, or the memory 1009 may include both volatile and non-volatile memories.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (ELPROM), or an electrically erasable programmable read-only memory (ELPROM).
  • ROM read-only memory
  • PROM programmable read-only memory
  • EPROM erasable programmable read-only memory
  • EPROM electrically erasable programmable read-only memory
  • ELPROM electrically erasable programmable read-only memory
  • ELPROM electrically erasable programmable read-only memory
  • ELPROM electrically erasable programmable read-only memory
  • Volatile memory can be random access memory (Random Access Memory, RAM), static random access memory (Static RAM, SRAM), 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, DDRSDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DRRAM).
  • RAM Random Access Memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM Double Data Rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • Synch link DRAM, SLDRAM synchronous link dynamic random access memory
  • Direct Rambus RAM Direct Rambus RAM
  • the processor 1010 may include one or at least two processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.
  • the terminal 1100 includes: an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114 and a memory 115.
  • the antenna 111 is connected to the radio frequency device 112.
  • the radio frequency device 112 receives information through the antenna 111 and sends the received information to the baseband device 113 for processing.
  • the baseband device 113 processes the information to be sent and sends it to the radio frequency device 112, and the radio frequency device 112 processes the received information and sends it out through the antenna 111.
  • the neighbor cell information indication method executed by the terminal in the above embodiment may be implemented in the baseband device 113, which includes a baseband processor.
  • the baseband device 113 may include, for example, at least one baseband board, on which at least two chips are arranged, as shown in Figure 8, one of which is, for example, a baseband processor, which is connected to the memory 115 through a bus interface to call the program in the memory 115 and execute the network device operation shown in the embodiment of the neighboring cell information indication method of the first aspect above.
  • the terminal may also include a network interface 116, which may be, for example, a common public radio interface (CPRI).
  • a network interface 116 which may be, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the terminal 1100 of the embodiment of the present application also includes: instructions or programs stored in the memory 115 and executable on the processor 114.
  • the processor 114 calls the instructions or programs in the memory 115 to execute the neighboring cell information indication method shown in the first aspect and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the embodiment of the present application also provides a network side device.
  • the network side device 1200 includes: a processor 1201, a network interface 1202 and a memory 1203.
  • the network interface 1202 is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network side device 1200 of the embodiment of the present application also includes: instructions or programs stored in the memory 1203 and executable on the processor 1201.
  • the processor 1201 calls the instructions or programs in the memory 1203 to execute the neighboring cell information indication method shown in the second aspect and achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored.
  • a program or instruction is stored.
  • the program or instruction is executed by a processor, each process of the above-mentioned neighboring cell information indication method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.
  • the processor is the processor in the terminal device described in the above embodiment.
  • the medium includes computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disk or optical disk, etc.
  • An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned neighboring cell information indication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
  • An embodiment of the present application further provides a computer program/program product, which is stored in a storage medium, and is executed by at least one processor to implement the various processes of the above-mentioned neighboring cell information indication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.
  • An embodiment of the present application also provides a neighbor cell information indication system, including: a network side device and a terminal, the terminal is used to execute the steps of the neighbor cell information indication method as described in the first aspect above, and the network side device is used to execute the steps of the neighbor cell information indication method as described in the second aspect above.
  • the technical solution of the present application can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM/RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.
  • a storage medium such as ROM/RAM, a magnetic disk, or an optical disk
  • a terminal which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.

Landscapes

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

Abstract

本申请公开了一种邻小区信息指示方法、装置、终端及网络侧设备，本申请实施例的邻小区信息指示方法包括：终端从服务小区的第一信令中获得关于邻小区是否支持在非连接态接收多播业务的目标信息。

Description

一种邻小区信息指示方法、装置、终端及网络侧设备
相关申请的交叉引用
本申请主张在2023年01月18日在中国提交的中国专利申请号202310077046.2的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种邻小区信息指示方法、装置、终端及网络侧设备。
背景技术
现有技术方案仅支持连接(Connected)状态终端接收多播(multicast)业务。当大量终端对multicast业务感兴趣时，网络侧设备需要将大量感兴趣的终端保留在Connected状态，造成很多控制和管理的额外开销，不利于网络整体效率。
发明内容
本申请实施例提供一种邻小区信息指示方法，能够将终端释放到非连接态进行multicast业务接收。
第一方面，提供了一种邻小区信息指示方法，包括：
终端从服务小区的第一信令中获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
第二方面，提供了一种邻小区信息指示方法，包括：
网络侧设备发送携带目标信息的第一信令，所述目标信息是关于所述网络侧设备控制的小区的邻小区是否支持终端在非连接态接收多播业务的信息。
第三方面，提供了一种邻小区信息指示装置，应用于终端，所述装置包括：
信息接收模块，用于从服务小区的第一信令中获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
第四方面，提供了一种邻小区信息指示装置，应用于网络侧设备，所述装置包括：
信息发送模块，用于发送携带目标信息的第一信令，所述目标信息是关于所述网络侧设备控制的小区的邻小区是否支持终端在非连接态接收多播业务的信息。
第五方面，提供了一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的邻小区信息指示方法的步骤。
第六方面，提供了一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的邻小区信息指示方法的步骤。
第七方面，提供了一种邻小区信息指示系统，包括：网络侧设备和终端，所述终端用于执行如上述第一方面所述的邻小区信息指示方法的步骤，所述网络侧设备用于 执行如上述第二方面所述的邻小区信息指示方法的步骤。
第八方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的邻小区信息指示方法的步骤，或者实现如第二方面所述的邻小区信息指示方法的步骤。
第九方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的邻小区信息指示方法，或实现如第二方面所述的邻小区信息指示方法。
第十方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现如第一方面或者第二方面所述的邻小区信息指示方法的步骤。
在本申请实施例中，通过第一信令实现非连接态接收多播业务的邻小区信息指示，使得终端可以在非连接态进行多播业务接收时能够及时获得关于邻小区的相关信息，继而可以在重选到目标小区时及时进行多播业务的连续性接收，从而在确保接收效果和网络开销的同时，提升网络整体效率。
附图说明
为了更清楚地说明本申请实施例，下面将对实施例中所需要使用的附图做简单的介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是本申请实施例中的一种邻小区信息指示方法的流程图；
图3是本申请实施例中的另一种邻小区信息指示方法的流程图；
图4是本申请实施例中的一种邻小区信息指示装置的结构框图；
图5是本申请实施例中的另一种邻小区信息指示装置的结构框图；
图6是本申请实施例中的一种通信设备的结构框图；
图7是本申请实施例中的一种终端的硬件结构示意图；
图8是本申请实施例中的一种终端的结构框图；
图9是本申请实施例中的一种网络侧设备的结构框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是至少两个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端设备11和网络侧设备12。其中，终端设备11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、增强现实(augmented reality，AR)/虚拟现实(virtual reality，VR)设备、机器人、可穿戴式设备(Wearable Device)、车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)、智能家居(具有无线通信功能的家居设备，如冰箱、电视、洗衣机或者家具等)、游戏机、个人计算机(personal computer，PC)、柜员机或者自助机等终端侧设备，可穿戴式设备包括：智能手表、智能手环、智能耳机、智能眼镜、智能首饰(智能手镯、智能手链、智能戒指、智能项链、智能脚镯、智能脚链等)、智能腕带、智能服装等。需要说明的是，在本申请实施例并不限定终端设备11的具体类型。网络侧设备12可以包括接入网设备或核心网设备，其中，接入网设备12也可以称为无线接入网设备、无线接入网(Radio Access Network,RAN)、无线接入网功能或无线接入网单元。接入网设备可以包括基站、无线局域网(Wireless Local Area Network，WLAN)接入点、无线保真(Wireless Fidelity，WiFi)节点等，基站可被称为节点B、演进节点B(eNB)、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、家用B节点、家用演进型B节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例进行介绍，并不限定基站的具体类型。核心网设备可以包含但不限于如下至少一项：核心网节点、核心网功能、移动管理实体(Mobility Management Entity，MME)、接入移动管理功能(Access and Mobility Management Function，AMF)、会话管理功能(Session Management Function，SMF)、用户平面功能(User Plane Function，UPF)、策略控制功能(Policy Control Function，PCF)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)、边缘应用服务发现功能(Edge Application Server Discovery Function，EASDF)、统一数据管理(Unified Data Management，UDM)， 统一数据仓储(Unified Data Repository，UDR)、归属用户服务器(Home Subscriber Server，HSS)、集中式网络配置(Centralized network configuration，CNC)、网络存储功能(Network Repository Function，NRF)，网络开放功能(Network Exposure Function，NEF)、本地NEF(Local NEF，或L-NEF)、绑定支持功能(Binding Support Function，BSF)、应用功能(Application Function，AF)等。需要说明的是，在本申请实施例中仅以NR系统中的核心网设备为例进行介绍，并不限定核心网设备的具体类型。
在长期演进(Long Term Evolution，LTE)的广播和多播传输中，支持多播(或组播)单频网络(Multicast Broadcast Single Frequency Network，MBSFN)方式多媒体广播多播业务(Multimedia Broadcast Multicast Service，MBMS)业务发送和单小区点对点(Single cell-Point to Multipoint，Sc-PtM)方式多播业务发送。MBSFN的方式中，处于同一个MBSFN区域的小区会同步的发送相同的广播业务，便于终端进行接收。MBMS业务的控制信息(控制信道参数和业务信道参数，以及调度信息等)和数据信息都是广播方式发送，使得空闲(idle)态终端和连接态终端都可以接收MBMS业务。
Sc-PtM是在MBMS业务之后又标准化的一种多播发送方式，跟MBSFN方式最大的不同是只在单小区调度发送，由集群组无线网络临时标识((group-Radio Network Tempory Identity，g-RNTI)来进行业务调度。在广播消息里广播控制信道参数和业务的标识、以及周期信息等调度信息由g-RNTI加扰的物理下行控制信道(Physical Downlink Control Channel，PDCCH)来进行通知，数据部分是组播方式发送，相当于感兴趣的终端监听g-RNTI获得数据调度进而进行接收。
在R17版本的新空口广播(New Radio broadcast，NR broadcast)业务接收时，网络在系统信息块(System Information Block，SIB)和多播/广播业务控制信道(Multicast/Broadcast Services Control Channel，MCCH)里携带邻小区是否支持广播业务的指示信息，非连接态终端在发生小区重选，重选到目标小区时，根据目标小区是否支持自己感兴趣的业务，决定是通过读取MCCH还是通过发起建立单播来继续接收广播业务。
R17 NR多播业务由于只支持无线资源控制连接(Radio Resource Control CONNECTED，RRC CONNECTED)状态的终端接收，因此不存在非连接态移动性问题，连接状态的终端在移动时发生切换，由源小区和目标小区的交互为终端确保目标小区以合适的方式支持多播业务接收，并通过专用信令将目标小区的配置发送给UE。
目前现有技术方案仅支持连接状态终端接收multicast业务。当大量UE对multicast业务感兴趣时，网络侧设备需要将大量感兴趣终端保留在连接状态，有很多控制和管理的额外开销，不利于网络整体效率。因此考虑将终端释放到非连接态进行multicast业务接收，将是一种同时确保接收效果和网络开销的折中方案，提升网络整体效率。但将终端释放到非连接态进行multicast接收之后，又需要考虑当UE发生移动时，如何连续进行多播业务接收的问题。
相关技术中，R17 NR多播业务由于仅支持连接状态终端接收，因此是在终端移动时通过接口间消息和专用信令来确保终端切换到目标小区的业务连续性，而R17 NR广播业务的邻小区指示信息，也无法直接重用到多播业务，因为多播业务的接收比广 播业务更复杂，例如目标小区可以仅支持连接态终端接收multicast业务，也可以支持非连接态终端接收multicast业务，还可能是不支持multicast业务。
针对相关技术中存在的问题，本申请提供了一种邻小区信息指示方法，能够实现非连接态接收多播业务终端的邻小区信息指示，使得终端可以在非连接状态进行multicast业务接收时，及时获得关于邻小区的相关信息，继而可以在重选到目标小区时及时进行多播业务的连续性接收，既保障了终端接收多播业务的体验，也降低了整体网络开销。
第一方面，参见图2所示，为本申请实施例所提供的一种邻小区信息指示方法的流程图，该方法可以包括以下步骤：
步骤S201：终端从服务小区的第一信令中获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
其中，非连接态可以包含空闲态和去激活态中的至少一者，第一信令可以是SIB信令、MCCH信令等公共信令。
在具体实施时，终端通过从服务小区的第一信令中获得目标信息，能够及时获得相关邻小区对多播业务非连接态接收的支持情况，使得终端可以根据该目标信息重选至合适的目标小区(如选择支持多播业务非连接态接收的目标小区)，也可以在重选到目标小区时及时选择合适的方式(如对于仅支持多播业务连接态接收的目标小区，终端能够及时转换至连接态接收多播业务)，从而确保多播业务接收连续性，能够在保障接收效果的基础上提升终端的体验和系统效率。
由上述步骤可知，通过第一信令实现非连接态接收多播业务的邻小区信息指示，使得终端可以在非连接态进行多播业务接收时能够及时获得关于邻小区的相关信息，继而可以在重选到目标小区时及时进行多播业务的连续性接收，从而在确保接收效果和网络开销的同时，提升网络整体效率。
实施方式一
本实施方式描述的是传输携带目标信息的第一信令的示例。
情况1：网络侧设备发送携带目标信息的第一信令，终端从服务小区的第一信令中获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
在该实施例中，网络侧设备根据其所控制的各个小区的邻小区对多播业务非连接态接收的支持情况，通过第一指令发送关于该网络侧设备控制的小区的邻小区是否支持终端在非连接态接收多播业务的信息。
其中，上述网络侧设备所控制的各个小区可以是支持多播业务非连接态接收的小区，也可以是不支持多播业务非连接态接收的小区。可以理解的是，网络侧设备在控制的小区不支持多播业务非连接态接收的情况下，如果该小区存在支持多播业务非连接态接收的至少一个邻小区，也可以通过第一信令指示该小区的邻小区是否支持在非连接态接收多播业务的目标信息，便于该小区的终端可以根据该目标信息重选至合适的目标小区，和/或重选到目标小区时能够及时选择合适的方式，从而解决终端非连接态接收多播业务的移动性问题。
可选地，第一信令携带的目标信息包括：第一信息和/或第二信息，所述第一信息用于指示支持在非连接态接收多播业务的邻小区，所述第二信息用于指示各个邻小区 支持在非连接态接收的多播业务信息。
需要说明的是，对于一个小区，可以按照是否支持以及如何支持multicast业务，将其分成三类：
第一类：仅支持终端在连接态接收multicast业务，多播/广播业务无线承载(Multicast/Broadcast Services Radio Bearer，MRB)配置以点到多点(Point To Multipoint，PTM)/G-RNTI多播方式调度；
第二类：支持终端在非连接态接收multicast业务，MRB配置以PTM/G-RNTI多播方式调度；
第三类：不支持多播方式调度，可以以单播(如单播(unicast)/数据无线承载(Data Radio Bearer，DRB)/小区无线网络临时标识(Cell-RadioNetworkTemporaryIdentifier，C-RNTI)等)方式为终端提供多播业务传输。
根据以上分类方式，网络侧设备可以以小区为颗粒度，通过第一信息指示邻小区对多播业务非连接态接收的支持情况。例如，小区里所有多播业务都是以第一类方式(即以连接态传输方式)发送，则小区属于上述第一类小区；小区里只要有至少一个多播业务属于第二类方式(即以非连接态传输方式)发送，则小区可以属于上述第二类小区，小区里所有多播业务都是按照第三类方式(即以单播传输方式)发送，则小区属于上述第三类小区，此时网络侧设备可以使用第一信息指示其所控制的任一小区的邻小区中，属于上述第二类小区的邻小区。
上述邻小区信息指示方式针对小区里全部multicast业务，颗粒度较粗，故网络侧设备也可以以一个特定的多播业务为粒度，通过第二信息指示各个邻小区对该特定的多播业务的非连接态接收的支持情况，例如该特定的多播业务在小区里采用上述第一类方式发送，那么这个小区对于这个多播业务来说属于第一类小区，该多播业务在小区里采用上述第二类方式发送，那么这个小区对于这个多播业务来说属于第二类小区，该多播业务在小区里采用第三类方式发送，那么这个小区对于这个多播业务来说属于第三类小区，此时网络侧设备可以使用第二信息指示相对于任一相关多播业务(如其所控制小区中终端已经加入的一个多播业务)来说，属于第二类小区的邻小区，可以看出这种邻小区信息指示方式针对单个多播业务，颗粒度更细。其中，终端已经加入的多播业务是指：终端加入成功(即网络侧设备授权了终端进行接收)且一直维持在加入状态的多播业务。
一般来说，当小区内的所有多播业务或者终端感兴趣(想要接收)的多播业务都采用上述第一类方式或者上述第三类方式发送，即该小区内的终端需要在连接态进行多播业务接收，此时小区重选前后相关终端的移动性完全在源小区和目标小区的控制之下，关于业务连续性的保证可以通过接口信令和专用信令进行确保，无需额外机制。
只有当小区内有至少一个多播业务采用第二类方式发送时，即该小区内存在终端可以在非连接态进行多播业务接收时，那么这部分终端的移动性，是遵循非连接态终端的移动性准则，由终端自行进行小区选择和重选，不受网络控制，因此这部分终端的移动性引起的多播业务连续性，是本案重点解决的场景。
当多播业务支持被非连接态终端接收时，该多播业务相关的配置以及配置更新可以通过公共信令的方式发送，例如以SIB和MCCH组合的方式进行发送。此时，可以 在SIB信令和/或MCCH信令中携带邻小区是否支持在非连接态接收多播业务的目标信息，由已经加入多播业务(或对多播业务感兴趣且已经加入该多播业务)的终端，在非连接态从该SIB信令和/或MCCH信令中读取上述目标信息并执行相应操作(如小区重选、转换多播业务接收状态等)，以确保终端多播业务的连续性。
作为一种可能的实施方式，考虑到SIB信令会携带关于MCCH调度的(如调度周期等)信息，即终端通常会先读取SIB信令，再根据SIB信令找到相关的MCCH信令，故相较于MCCH信令，SIB信令通常会用于携带粗粒度信息，因此可以使用SIB信令携带上述以小区为颗粒度的第一信息，而MCCH由于可以用来携带细粒度信息，故可以灵活使用MCCH信令携带上述以小区为颗粒度的第一信息和/或以特定的多播业务为粒度的第二信息。
可选地，上述第一信令(即SIB信令和/或MCCH信令)所携带的第一信息可以为：第一小区ID列表或第一小区index列表，其中：
所述第一小区ID列表包括所述第一信令中携带的用于指示支持在非连接态接收至少一个多播业务的各个邻小区的ID，该邻小区的ID可以是新空口小区全球标识符编号(New Radio Cell Global Identifier Identity Document，NCGI ID)；
所述第一小区index列表为其它信令(如除SIB信令和/或MCCH信令之外的其它公共信令)携带的小区ID列表中，支持在非连接态接收至少一个多播业务的各个邻小区的位置或排序信息。例如，第一小区index列表中可以包含0、1、2共三个索引值，表示在该第一小区index列表所关联的其它信令携带的小区ID列表中，前三个ID对应的小区为支持在非连接态接收至少一个多播业务的邻小区。
可选地，上述MCCH信令所携带的第二信息可以为：每个多播业务(如多播业务的临时移动组标识(Temporary Mobile Group Identity，TMGI)等业务描述信息)分别对应的第二小区ID列表或第二小区index列表，其中：
每个多播业务对应的第二小区ID列表包括支持在非连接态接收该多播业务的各个邻小区的ID，该邻小区的ID可以是NCGI ID；
每个多播业务对应的第二小区index列表为所述第一信令或其它信令携带的小区ID列表中，支持在非连接态接收该多播业务的各个邻小区的位置或排序信息，例如，第一信令或其它信令已经指示了支持在非连接态接收某一多播业务的邻小区ID列表(如上述第一小区ID列表)，则该第二小区index列表可以包含0、1、2共三个索引值，表示在该第一小区ID列表中，前三个ID对应的邻小区为支持在非连接态接收该多播业务的邻小区，也可以使用比特位标识支持在非连接态接收该多播业务的邻小区，如该第二小区index列表可以包含比特“11100000”，前三位的1代表对应的邻小区ID列表中排在前三位的小区ID对应支持该多播业务在非连接态接收的邻小区，后五位的0代表该邻小区ID列表中排在后五位的小区ID是不支持该多播业务在非连接态接收的邻小区。
情况2：在邻小区对多播业务非连接态接收的支持情况出现变更时，网络侧设备更新上述目标信息，并发送携带更新后的目标信息的第一信令。终端接收服务小区的变更后的第一信令，所述服务小区的变更后的第一信令是在邻小区是否支持在非连接态接收多播业务的信息发生变更的情况下生成的；终端从所述服务小区的变更后的第 一信令中，重新获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
在该实施例中，如果邻小区的支持情况发生变更，网络侧设备可以通过SIB更新或者MCCH更新的过程，进行相应目标信息的更新操作，使得感兴趣的终端在被通知SIB更新或者MCCH更新之后，能够及时读取更新后的相应目标信息。
在实施方式一中，网络侧设备能够及时更新目标信息，且能够通过SIB信令中携带的目标信息(即支持在非连接态接收多播业务的邻小区信息)，和/或通过MCCH信令中携带的目标信息(即支持在非连接态接收多播业务的邻小区信息，和/或每个多播业务在各个邻小区是否支持非连接态接收的具体信息)，使得终端可以及时获得相关邻小区信息，从而在小区重选过程时重选到合适的目标小区，和/或重选到目标小区时可以及时选择合适的方式确保多播业务的接收连续性，从而在保障终端接收效果的基础上，提升了终端的接收体验和系统效率。
实施方式二
本实施方式描述的是终端在接入目标小区，并从目标小区接收所述终端已经加入的多播业务之前，如何确定目标小区的示例。
情况1：终端在满足小区选择和/或重选机制的触发条件的情况下，根据上述目标信息，确定目标小区。
可以理解的是，移动性管理是蜂窝移动通信系统必备的机制，能够辅助实现负载均衡、提高用户体验以及系统整体性能。NR中，移动性管理分为两类：非连接态下的移动性管理和连接态下的移动性管理。连接态下的移动性管理主要通过小区切换实现，由网络侧设备完全控制，终端辅助测量；非连接态下的移动性管理通过小区选择/重选来实现，网络侧设备辅助配置。在具体实施时，终端可以将完成公共陆地移动网(Public Land Mobile Network，PLMN)选择，和/或依照存储(或指示)的接入技术作为小区选择的前提条件，且可以将R准则作为小区重选的触发条件。
可选地，终端在满足小区选择和/或重选机制的触发条件的情况下，从所述目标信息指示的各个邻小区中确定出至少一个候选目标小区；所述终端根据所述至少一个候选目标小区，按照以下至少一项确定目标小区：
A-1项：所述终端将所述至少一个候选目标小区中，支持在非连接态接收所述终端已经加入的多播业务的一个候选目标小区，确定为目标小区，其中，在所述终端已经加入的多播业务的数量是多个的情况下，候选目标小区支持在非连接态接收所述终端已经加入的多播业务是指：候选目标小区支持在非连接态接收所述终端已经加入的所有多播业务；
A-2项：所述终端在所述至少一个候选目标小区均不支持在非连接态接收所述终端已经加入的多播业务的情况下，将所述至少一个候选目标小区中的任一候选目标小区确定为目标小区；
A-3项：所述终端在所述至少一个候选目标小区部分支持在非连接态接收所述终端已经加入的多播业务的情况下，将所述至少一个候选目标小区中，支持所述终端已经加入的多播业务数量最多或支持的多播业务优先级最高的一个候选目标小区，确定为目标小区；
其中，候选目标小区不支持在非连接态接收所述终端已经加入的多播业务是指： 候选目标小区不支持在非连接态接收所述终端已经加入的所有多播业务；候选目标小区部分支持在非连接态接收所述终端已经加入的多播业务是指：候选目标小区支持在非连接态接收所述终端已经加入的一部分多播业务。
针对A-1项，终端可以优先选择支持自己已经加入的所有多播业务(终端可以加入1个或多个多播业务)非连接态接收的候选目标小区作为目标小区；如果支持非连接态接收终端已经加入的所有多播业务的候选目标小区有多个，则终端可以基于自己的实现选择其中之一(如从中选择链路质量最好的候选目标小区)作为目标小区。
针对A-2项，如果没有一个候选目标小区支持终端已经加入的至少一个多播业务非连接态接收，在候选目标小区只有一个时，终端可以将该候选目标小区直接作为目标小区；在候选目标小区有多个时，终端可以任意选择一个候选目标小区，或根据自己的实现(如根据链路质量)选择一个候选目标小区，并将选择出的候选目标小区作为目标小区。
针对A-3项，如果有多个候选目标小区，且该多个候选目标小区最多只支持终端已经加入的部分多播业务非连接态接收，则终端可以优先选择支持终端已经加入的尽量多的多播业务非连接态接收的候选目标小区，或终端可以优先选择支持终端已经加入的高优先级的多播业务非连接态接收的候选目标小区，并将选择出的候选目标小区作为目标小区。
情况2：终端在满足小区选择和/或重选机制的触发条件的情况下，确定目标小区。
在该实施例中，终端可以根据小区选择准测、小区重选准则等规则直接确定目标小区，在后续接入目标小区时，再根据目标信息选择合适的方式接收多播业务。
例如，终端当前的多播业务如果处于暂时没有数据或者去激活状态(多播业务具有生命周期)，源小区可能将终端释放回非连接态。此时终端如果没有从源小区的SIB信令和/或MCCH信令中获知邻小区对多播业务非连接态接收的支持情况(即没有从源小区获得目标信息)，可以按照小区重选准则选择到目标小区后，通过读取该目标小区的多播业务相关的SIB和MCCH信令，获得目标小区支持接收多播业务的信息和配置(如支持非连接态接收终端已经加入的多播业务的信息和配置)，以便终端在下次多播业务激活时，直接留在非连接态接收多播业务。可以理解的是，若该终端从源小区获得了目标信息，也可以基于情况1，尽量选择支持终端已经加入的多播业务非连接态接收的目标小区，以在该目标小区直接通过SIB/MCCH方式获得配置，并在非连接态继续接收多播业务。
在实施方式二中，终端可以根据目标信息确定合适的目标小区，以保证多播业务接收的连续性，终端也可以根据自身所采用的小区选择和/或重选机制确定合适的目标小区，以减少对终端的配置更改。
实施方式三
本实施方式描述的是终端在确定目标小区后接入，终端从目标小区接收多播业务的方式的示例。
情况1：在终端在非连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区支持在非连接态接收所述终端已经加入的多播业务的情况下，所述终端保持非连接态接入所述目标小区，所述终端在非连接态从所述目标小区中接收所述 终端已经加入的多播业务。
在该实施例中，终端在完成该目标小区的接入后，可以通过目标小区的SIB和/或MCCH，获得自己已经加入的多播业务配置，并继续保持非连接态接收多播业务。
情况2：在终端在非连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区不支持在非连接态接收所述终端已经加入的多播业务的情况下，所述终端由非连接态转换至连接态，并接入所述目标小区，所述终端在连接态从所述目标小区中接收所述终端已经加入的多播业务。
其中，所述终端是在接入所述目标小区之前或之后由非连接态转换至连接态的。
在该实施例中，终端可以在接入该目标小区之前或者之后，发起RRC的状态转换，从非连接态进入连接态。如果在重选或接入该目标小区之前终端进入连接态，相当于终端在源小区就进入连接态，此时可以由源小区和目标小区的交互以及专用信令过程来确保终端从源小区到目标小区接收多播业务的连续性，这种方式对终端的业务连续性较好；如果终端在重选或接入目标小区之后再进入连接态，相当于终端在目标小区才进入连接态，终端在完成状态转换之后，可以由目标小区的专用信令配置来确保终端能重新在目标小区接收多播业务，但在状态转换的信令交互过程中，终端可能因为距离源小区过远而接收不到源小区的多播业务发送，而同时目标小区的新配置还没有获得，也无法直接从目标小区接收多播业务，因此中间可能存在业务中断，影响业务接收体验。
情况3：在终端在连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区不支持在非连接态接收所述终端已经加入的多播业务的情况下，所述终端保持在连接态，从所述目标小区中接收所述终端已经加入的多播业务。
可以理解的是，在终端当前正在接收或者感兴趣的多播业务，并没有支持非连接态接收的情况下，那么即使源小区和目标小区是支持其它多播业务非连接态接收，终端也需按照连接态的移动性来进行相关操作(如由源小区和目标小区的交互以及专用信令过程来确保终端从源小区到目标小区接收多播业务的连续性)。
情况4：在所述终端在连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区支持在非连接态接收所述终端已经加入的多播业务的情况下，所述终端通过连接态的转换过程由所述服务小区切换至所述目标小区之后或者之前，由连接态转换至非连接态，并在非连接态从所述目标小区中接收所述终端已经加入的多播业务。
在该实施例中，如果终端在源小区仅能在连接态接收多播业务，例如通过连接态MRB或者DRB的方式，则处于连接态的终端可以直接通过连接态的转换过程，由源小区和目标小区交互，并通过目标小区给的专用信令，让终端先切换至目标小区在连接态接收多播业务，切换之后目标小区可以再对终端进行释放，令其在非连接态继续接收多播业务。
情况5：终端已经加入的多播业务的数量是多个的情况下，根据终端已经加入的多个多播业务各自的优先级、终端的倾向信息以及网络侧设备的指示信息中的至少一者，确定接入目标小区后处于连接态或非连接态，并在连接态或非连接态从所述目标小区接收所述终端已经加入的多个多播业务。
在该实施例中，在终端有倾向(如强烈省电倾向)，或者网络有指示(如网络负荷过重时发出的指示)等情况，终端也可以在多个已经加入的多播业务中选择其中更高优先级的部分多播业务进行接收，而舍弃其它低优先级多播业务接收。
例如，终端可以选择支持非连接态接收高优先级多播业务的目标小区，通过该目标小区的SIB和/或MCCH获得配置，从而以非连接态继续接收该高优先级多播业务，而舍弃其它低优先级需要进入连接态接收的多播业务。其中，网络侧设备可以发送指示信息，以指示终端已经加入的多个多播业务各自的优先级。
情况6：网络侧设备将终端的服务小区配置为支持在非连接态接收所述终端已经加入的所有多播业务，或将终端的服务小区配置为支持在连接态接收所述终端已经加入的所有多播业务。
在具体实施时，网络侧设备可以根据实际情况调整终端的服务小区对多播业务的支持情况。例如，网络侧设备在网络负荷较轻时，可以将终端的服务小区配置为支持在连接态接收所述终端已经加入的所有多播业务，而网络侧设备可以在网络负荷过重时，将终端的服务小区配置为支持在非连接态接收所述终端已经加入的所有或者部分多播业务，此外，网络侧设备也可以根据所控制小区接入的能够在非连接态接收多播业务的终端数量等信息，调整终端的服务小区对多播业务的支持情况，以使终端通过合适的方式接收多播业务。
在实施方式三中，终端根据目标信息，结合自身倾向或网络指示，选择合适的方式(即切换至合适的状态)接收多播业务，能够在保障接收效果的基础上提升终端的接收体验。
实施方式四
本实施方式描述的是多播业务的配置信息的情况。
情况1：终端从目标小区的SIB信令和/或MCCH信令中，读取终端已经加入的多播业务在目标小区的目标配置信息，根据所述目标配置信息，从所述目标小区中接收所述终端已经加入的多播业务。
可以理解的是，如果终端已经加入或者正在非连接态接收的多播业务不止一个，那么终端能在移动到或者接入目标小区后顺利通过SIB和/或MCCH来获取新配置，并继续在非连接态接收业务的前提，是终端所有已经加入的多播业务在目标小区都支持非连接态接收，只要有一个多播业务不支持该传输方式，则终端都必须进行RRC状态的迁移，进入连接态由网络侧设备控制完成接收。此时网络侧设备可以对不支持非连接态接收的多播业务配置连接态接收方式以使终端进行接收，而对支持连接态的多播业务，可以使终端继续读取SIB和/或MCCH以获得配置并接收。
可选地，终端根据目标配置信息，在非连接态从目标小区中接收所述终端已经加入的多播业务，包括以下至少一项：
终端在原配置信息与所述目标配置信息相同的情况下，保留所述原配置信息对应的实体和参数，在非连接态从所述目标小区中接收所述终端已经加入的多播业务，所述原配置信息为所述终端已经加入的多播业务在所述服务小区的配置信息；
终端在所述原配置信息和所述目标配置信息不相同的情况下，根据所述目标配置信息进行重配置，在非连接态从所述目标小区中接收所述终端已经加入的多播业务。
在该实施例中，感兴趣或者在源小区已经接收过多播业务的终端，如果存储有源小区的配置信息(即原配置信息)，则从目标小区的SIB和/或MCCH中再次获得新的多播业务配置(即目标配置信息)时，终端可以比较配置的具体内容。如果配置相同，可以直接保持现有实体运行和参数。如果有参数配置不一致(即配置信息和目标配置信息不相同)，则需要对该参数进行重配置，并立即应用新配置参数；如果该参数重配置会影响整个实体的运行，例如涉及无线链路层控制协议(Radio Link Control，RLC)或者分组数据汇聚层协议(Packet Data Convergence Protocol，PDCP)实体的序列号(Sequence Number，SN)长度重配置，则需要对整个实体执行重建立(如re-establishment)过程。
作为一种可能的实施方式，终端根据所述目标配置信息进行重配置，包括以下至少一项：
B-1项：所述终端保留L2实体的SN状态变量或者COUNT状态变量的值；
B-2项：所述终端将L2实体中的RLC实体进行重建立；
B-3项：所述终端保留L2实体中的PDCP的COUNT状态变量的值。
针对B-1项，在L2(即数据链路)实体(如RLC实体或者PDCP实体)发生参数重配置或者实体重建立时，需要保留SN状态变量或者计数(COUNT)状态变量的值，确保源小区的数据和目标小区的数据可以按序进行接收处理，并能确定在目标小区的接收初始变量的COUNT值，不至于引发超帧号(Hyper Frame Number，HFN)失步等错误情况。
针对B-2项，由于RLC实体的SN状态变量重置并不会造成失步影响，因此可以考虑在重选前后，将RLC实体进行重置(reset)或重建立(re-estalishment)，目标小区以状态变量的初始值开始接收，或者以接收到第一个数据包的SN状态变量作为接收状态变量初值。
针对B-3项，PDCP实体的COUNT值由于需要保持同步或者连续，因此PDCP应尽量在重选前后保持COUNT值的统一排序。可选地，针对确认模式(Acknowledged Mode，AM)MRB，保持COUNT值，即在所述目标配置信息为AM MRB配置的情况下，所述终端保留L2实体中的PDCP的COUNT状态变量的值；针对非确认模式(Unacknowledged Mode，UM)MRB，可以以状态变量的初始状态开始接收，或者以接收到第一个数据包的SN状态变量作为接收状态变量初值，或者计算状态变量初始值。可以理解的是，源小区和目标小区的服务质量(Quality of Service，QoS)流到DRB的映射关系最好保持统一，这样能尽量确保重选前后的PDCP实体的COUNT值可以尽量连续，从而确保终端的业务连续性接收，以及在目标小区能够获得COUNT值同步。
情况2：网络侧设备恢复或发送MRB配置信息，所述MRB配置信息用于终端在接入目标小区后，在连接态从所述目标小区中接收所述终端已经加入的多播业务。
在该实施例中，如果网络侧设备控制的小区(即目标小区)不支持终端感兴趣的多播业务在非连接态接收，则目标小区可以对该终端感兴趣的多播业务支持(或仅支持)连接态终端的MRB配置，通过PTM/G-RNTI多播方式调度，则在终端恢复或者进入连接态后，网络侧设备会恢复或配置MRB和相关多播调度配置信息，以完成后 续连接状态的调度和传输。
情况3：网络侧设备发送DRB配置信息，所述DRB配置信息用于所述终端在接入目标小区后，在连接态从所述目标小区中接收所述终端已经加入的多播业务。
在该实施例中，如果网络侧设备控制的小区(即目标小区)不支持终端感兴趣的多播业务在非连接态接收，则目标小区可以对该终端感兴趣的多播业务支持(或仅支持)连接态终端的DRB配置，通过点对点(Point To Point，PTP)或C-RNTI单播方式调度。
在具体实施时，如果这个终端处于去激活态，在该终端的上下文配置信息中不仅有该多播业务的MRB和多播调度配置，还可以有该多播业务的伴随多播业务的DRB配置，此时源小区或目标小区的恢复或者切换命令里仅包含DRB配置即可；如果该终端处于空闲态，在源小区和目标小区的交互过程中，或者终端接入目标小区之后，会由目标小区配置DRB给该终端用于业务接收。
在实施方式四中，当一个终端由源小区需要重选到目标小区时，如果目标小区支持非连接态接收终端感兴趣的多播业务，则终端接入目标小区之后，可以通过SIB和/或MCCH获得多播业务配置，并对终端的配置应用和L2实体及相关参数进行相应保留或重置，以使终端能够进行连续性接收。
实施方式五
本实施方式描述的是邻小区包含相邻的网络侧设备所控制小区(如跨基站)的情况。
情况1：网络侧设备从相邻的网络侧设备的接口消息中，获取邻小区的多播业务配置信息，并将控制的小区的多播业务配置信息，配置为与所述邻小区的多播业务配置信息相同的信息
其中，该网络侧设备的第一信令还携带网络侧设备控制的小区的多播业务配置信息，一个小区的多播业务配置信息用于终端在该小区中接收所述终端已经加入的多播业务。
可以理解的是，由于网络侧设备控制的小区需要通过SIB和/或MCCH告知终端在邻小区支持多播业务非连接态接收的情况。若存在跨网络侧设备(如下一代基站(the next Generation Node B，gNB)节点)的情况下，需要通过gNB节点间的接口消息传递这些信息，并且在邻小区的这些信息发生变化时，需要及时通知周围的小区，以便于其它小区及时的更新自己的SIB和/或MCCH中的邻小区信息。
可选地，所述多播业务配置信息包括以下至少一项：多播业务QoS流到MRB之间的映射关系；L2实体的配置信息。
可以理解的是，为使非连接态终端进行跨小区的连续接收，故终端除了能知晓并顺利获取目标小区的SIB和/或MCCH的业务配置信息之外，还有一个比较重要的点，在于为了确保一个多播业务的MRB能顺利连续接收，相邻小区的配置信息最好一致。
例如，多播业务的QoS流到MRB之间的映射关系、L2例如RLC，PDCP的配置等在相邻小区最好一致，这样能尽可能地维持重选前后COUNT值的连续性以及HFN同步，对终端业务连续性体验更好，因此相邻网络侧设备之间可以交互关于多播业务在非连接态接收的相关配置，尽量确保配置一致，如网络侧设备可以将控制的小区的 多播业务QoS流到DRB的之间的映射关系，配置为与该小区的邻小区的多播业务QoS流到DRB的之间的映射关系相同的映射关系。
情况2：网络侧设备接收相邻的网络侧设备控制的小区的多播业务更新信息，所述多播业务更新信息表征邻小区是否支持多播业务的信息发生变更。网络侧设备根据所述多播业务更新信息，更新所述目标信息。
例如，在跨基站的场景下，需要通过基站之间的接口交互邻小区的支持非连接态接收多播业务的信息(如业务列表)。当本小区(即基站控制的某一小区)的多播业务的信息发生变更时，需要及时通过接口消息通知邻基站，邻基站会根据接收到的最新信息更新自己的邻小区信息，从而确保邻基站的终端能够读取到正确的目标信息。
在实施方式五中，各相邻网络侧设备通过接口交互邻小区对非连接态接收多播业务的支持情况、以及非连接态接收多播业务的配置信息，从而确保终端跨小区接收多播业务的连续性。
第二方面，如图3所示，本申请实施例提供了另一种邻小区信息指示方法，该方法至少包括以下步骤：
步骤S301：网络侧设备发送携带目标信息的第一信令，所述目标信息是关于所述网络侧设备控制的小区的邻小区是否支持终端在非连接态接收多播业务的信息。
作为一种可能的实施方式，所述网络侧设备发送携带目标信息的第一信令，包括：
在所述网络侧设备控制的小区的至少一个邻小区支持在非连接态接收多播业务的情况下，所述网络侧设备发送携带目标信息的第一信令。
作为一种可能的实施方式，所述方法还包括：
所述网络侧设备接收相邻的网络侧设备控制的小区的多播业务更新信息，所述多播业务更新信息表征邻小区是否支持多播业务的信息发生变更；
所述网络侧设备根据所述多播业务更新信息，更新所述目标信息；
所述网络侧设备发送携带更新后的目标信息的第一信令。
作为一种可能的实施方式，所述方法还包括以下至少一项：
所述网络侧设备恢复或发送MRB配置信息，所述MRB配置信息用于终端在接入目标小区后，在连接态从所述目标小区中接收所述终端已经加入的多播业务；
所述网络侧设备发送DRB配置信息，所述DRB配置信息用于所述终端在接入目标小区后，在连接态从所述目标小区中接收所述终端已经加入的多播业务。
作为一种可能的实施方式，所述第一信令还携带所述网络侧设备控制的小区的多播业务配置信息，一个小区的多播业务配置信息用于终端在该小区中接收所述终端已经加入的多播业务；所述方法还包括：
所述网络侧设备从相邻的网络侧设备的接口消息中，获取邻小区的多播业务配置信息；
所述网络侧设备将控制的小区的多播业务配置信息，配置为与所述邻小区的多播业务配置信息相同的信息。
作为一种可能的实施方式，所述多播业务配置信息包括以下至少一项：
多播业务QoS流到MRB之间的映射关系；
L2实体的配置信息。
作为一种可能的实施方式，所述方法还包括：
所述网络侧设备将控制的小区的多播业务QoS流到DRB的之间的映射关系，配置为与该小区的邻小区的多播业务QoS流到DRB的之间的映射关系相同的映射关系。
作为一种可能的实施方式，所述方法还包括：
所述网络侧设备将终端的服务小区配置为支持在非连接态接收所述终端已经加入的所有多播业务；或
所述网络侧设备将终端的服务小区配置为支持在连接态接收所述终端已经加入的所有多播业务。
作为一种可能的实施方式，所述方法还包括：
所述网络侧设备发送指示信息，所述指示信息用于指示终端已经加入的多个多播业务各自的优先级。
本申请实施例提供的邻小区信息指示方法，执行主体可以为邻小区信息指示装置。本申请实施例中以邻小区信息指示装置执行邻小区信息指示方法为例，说明本申请实施例提供的邻小区信息指示装置。
第三方面，本申请实施例提供了一种邻小区信息指示装置，该装置可以应用于终端，如图4所示，该邻小区信息指示装置100包括：
信息接收模块101，用于从服务小区的第一信令中获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
可选地，所述目标信息包括：第一信息和/或第二信息；
所述第一信息用于指示支持在非连接态接收多播业务的邻小区；
所述第二信息用于指示各个邻小区支持在非连接态接收的多播业务信息。
可选地，所述服务小区的第一信令包括以下至少一项：
所述服务小区的SIB信令，所述SIB信令携带所述第一信息；
所述服务小区的MCCH信令，所述MCCH信令携带所述第一信息和/或所述第二信息。
可选地，所述装置还包括：
第一确定模块，用于在满足小区选择和/或重选机制的触发条件的情况下，确定目标小区；
第一处理模块，用于接入所述目标小区，并从所述目标小区接收所述终端已经加入的多播业务。
可选地，所述装置还包括：
第二确定模块，用于在满足小区选择和/或重选机制的触发条件的情况下，根据所述目标信息，确定目标小区；
第二处理模块，用于接入所述目标小区，并从所述目标小区接收所述终端已经加入的多播业务。
可选地，所述第二确定模块包括：
第一确定子模块，用于在满足小区选择和/或重选机制的触发条件的情况下，从所述目标信息指示的各个邻小区中确定出至少一个候选目标小区；
第二确定子模块，用于按照以下至少一项确定目标小区：
将所述至少一个候选目标小区中，支持在非连接态接收所述终端已经加入的多播业务的一个候选目标小区，确定为目标小区，其中，在所述终端已经加入的多播业务的数量是多个的情况下，候选目标小区支持在非连接态接收所述终端已经加入的多播业务是指：候选目标小区支持在非连接态接收所述终端已经加入的所有多播业务；
在所述至少一个候选目标小区均不支持在非连接态接收所述终端已经加入的多播业务的情况下，将所述至少一个候选目标小区中的任一候选目标小区确定为目标小区；
在所述至少一个候选目标小区部分支持在非连接态接收所述终端已经加入的多播业务的情况下，将所述至少一个候选目标小区中，支持所述终端已经加入的多播业务数量最多或支持的多播业务优先级最高的一个候选目标小区，确定为目标小区；
其中，候选目标小区不支持在非连接态接收所述终端已经加入的多播业务是指：候选目标小区不支持在非连接态接收所述终端已经加入的所有多播业务；候选目标小区部分支持在非连接态接收所述终端已经加入的多播业务是指：候选目标小区支持在非连接态接收所述终端已经加入的一部分多播业务。
可选地，所述第一处理模块或第二处理模块，包括以下至少一项：
第一接收模块，用于在所述终端在非连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区支持在非连接态接收所述终端已经加入的多播业务的情况下，保持非连接态接入所述目标小区，所述终端在非连接态从所述目标小区中接收所述终端已经加入的多播业务；
第二接收模块，用于在所述终端在非连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区不支持在非连接态接收所述终端已经加入的多播业务的情况下，由非连接态转换至连接态，并接入所述目标小区，所述终端在连接态从所述目标小区中接收所述终端已经加入的多播业务，其中，所述终端是在接入所述目标小区之前或之后由非连接态转换至连接态的。
可选地，所述第一处理模块或第二处理模块，包括以下至少一项：
第三接收模块，用于在所述终端在连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区不支持在非连接态接收所述终端已经加入的多播业务的情况下，保持在连接态，从所述目标小区中接收所述终端已经加入的多播业务；
第四接收模块，用于在所述终端在连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区支持在非连接态接收所述终端已经加入的多播业务的情况下，通过连接态的转换过程由所述服务小区切换至所述目标小区之后或者之前，由连接态转换至非连接态，并在非连接态从所述目标小区中接收所述终端已经加入的多播业务。
可选地，在所述终端已经加入的多播业务的数量是多个的情况下，所述第一处理模块或第二处理模块包括：
状态确定模块，用于根据所述终端已经加入的多个多播业务各自的优先级、所述终端的倾向信息以及网络侧设备的指示信息中的至少一者，确定接入所述目标小区后处于连接态或非连接态；
第五接收模块，用于在连接态或非连接态从所述目标小区接收所述终端已经加入 的多个多播业务。
可选地，所述第一处理模块或第二处理模块包括：
第一读取模块，用于从所述目标小区的SIB信令和/或MCCH信令中，读取所述终端已经加入的多播业务在所述目标小区的目标配置信息；
第六接收模块，用于根据所述目标配置信息，从所述目标小区中接收所述终端已经加入的多播业务。
可选地，所述第六接收模块，包括以下至少一项：
第一接收子模块，用于在原配置信息与所述目标配置信息相同的情况下，保留所述原配置信息对应的实体和参数，在非连接态从所述目标小区中接收所述终端已经加入的多播业务，所述原配置信息为所述终端已经加入的多播业务在所述服务小区的配置信息；
第二接收子模块，用于在所述原配置信息和所述目标配置信息不相同的情况下，根据所述目标配置信息进行重配置，在非连接态从所述目标小区中接收所述终端已经加入的多播业务。
可选地，所述第二接收子模块。包括以下至少一项：
第一重配置模块，用于保留L2实体的SN状态变量或者COUNT状态变量的值；
第二重配置模块，用于将L2实体中的RLC实体进行重建立；
第三重配置模块，用于保留L2实体中的PDCP的COUNT状态变量的值。
可选地，所述第一重配置模块包括：
重配置子模块，用于在所述目标配置信息为AM MRB配置的情况下，保留L2实体中的PDCP的COUNT状态变量的值。
可选地，所述第一信息为：第一小区ID列表或第一小区index列表；
所述第一小区ID列表包括所述第一信令中携带的用于指示支持在非连接态接收至少一个多播业务的各个邻小区的ID；
所述第一小区index列表为其它信令携带的小区ID列表中，支持在非连接态接收至少一个多播业务的各个邻小区的位置或排序信息。
可选地，所述第二信息为：每个多播业务分别对应的第二小区ID列表或第二小区index列表；
每个多播业务对应的第二小区ID列表包括支持在非连接态接收该多播业务的各个邻小区的ID；
每个多播业务对应的第二小区index列表为所述第一信令或其它信令携带的小区ID列表中，支持在非连接态接收该多播业务的各个邻小区的位置或排序信息。
可选地，所述装置还包括：
信令接收模块，用于接收服务小区的变更后的第一信令，所述服务小区的变更后的第一信令是在邻小区是否支持在非连接态接收多播业务的信息发生变更的情况下生成的；
信息重获取模块，用于从所述服务小区的变更后的第一信令中，重新获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
本申请实施例提供的邻小区信息指示装置能够实现第一方面所述的邻小区信息指 示方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
第四方面，本申请实施例提供了另一种邻小区信息指示装置，该装置可以应用于网络侧设备，如图5所示，该邻小区信息指示装置200包括：
信息发送模块201，用于发送携带目标信息的第一信令，所述目标信息是关于所述网络侧设备控制的小区的邻小区是否支持终端在非连接态接收多播业务的信息。
可选地，所述信息发送模块201包括：
第一发送子模块，用于在所述网络侧设备控制的小区的至少一个邻小区支持在非连接态接收多播业务的情况下，发送携带目标信息的第一信令。
可选地，所述装置还包括：
第一处理模块，用于接收相邻的网络侧设备控制的小区的多播业务更新信息，所述多播业务更新信息表征邻小区是否支持多播业务的信息发生变更；
第二处理模块，用于根据所述多播业务更新信息，更新所述目标信息；
第三处理模块，用于发送携带更新后的目标信息的第一信令。
可选地，所述装置还包括以下至少一项：
第四处理模块，用于恢复或发送MRB配置信息，所述MRB配置信息用于终端在接入目标小区后，在连接态从所述目标小区中接收所述终端已经加入的多播业务；
第五处理模块，用于发送DRB配置信息，所述DRB配置信息用于所述终端在接入目标小区后，在连接态从所述目标小区中接收所述终端已经加入的多播业务。
可选地，所述第一信令还携带所述网络侧设备控制的小区的多播业务配置信息，一个小区的多播业务配置信息用于终端在该小区中接收所述终端已经加入的多播业务；所述装置还包括：
第六处理模块，用于从相邻的网络侧设备的接口消息中，获取邻小区的多播业务配置信息；
第七处理模块，用于将控制的小区的多播业务配置信息，配置为与所述邻小区的多播业务配置信息相同的信息。
可选地，所述多播业务配置信息包括以下至少一项：
多播业务QoS流到MRB之间的映射关系；
L2实体的配置信息。
可选地，所述装置还包括：
关系配置模块，用于将控制的小区的多播业务QoS流到DRB的之间的映射关系，配置为与该小区的邻小区的多播业务QoS流到DRB的之间的映射关系相同的映射关系。
可选地，所述装置还包括：
第八处理模块，用于将终端的服务小区配置为支持在非连接态接收所述终端已经加入的所有多播业务；或用于将终端的服务小区配置为支持在连接态接收所述终端已经加入的所有多播业务。
可选地，所述装置还包括：
第九处理模块，用于发送指示信息，所述指示信息用于指示终端已经加入的多个多播业务各自的优先级。
本申请实施例提供的邻小区信息指示装置能够实现第二方面所述的邻小区信息指示方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图6所示，本申请实施例还提供一种通信设备900，包括处理器901和存储器902，存储器902上存储有可在所述处理器901上运行的程序或指令，例如，该通信设备900为终端时，该程序或指令被处理器901执行时实现上述第一方面所述的邻小区信息指示方法实施例的各个步骤，且能达到相同的技术效果，该通信设备900为网络侧设备时，该程序或指令被处理器901执行时实现上述第二方面所述的邻小区信息指示方法实施例的各个步骤，且能达到相同的技术效果。为避免重复，这里不再赘述。
如图7所示，为实现本申请实施例的一种终端的硬件结构示意图。
该终端1000用于执行上述第一方面所述的邻小区信息指示方法实施例的各个步骤，且能达到相同的技术效果。该终端1000包括但不限于：射频单元1001、网络模块1002、音频输出单元1003、输入单元1004、传感器1005、显示单元1006、用户输入单元1007、接口单元1008、存储器1009以及处理器1010等中的至少部分部件。
本领域技术人员可以理解，终端1000还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1010逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1004可以包括图形处理单元(Graphics Processing Unit，GPU)10041和麦克风10042，图形处理器10041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1006可包括显示面板10061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板10061。用户输入单元1007包括触控面板10071以及其他输入设备10072中的至少一种。触控面板10071，也称为触摸屏。触控面板10071可包括触摸检测装置和触摸控制器两个部分。其他输入设备10072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1001接收来自网络侧设备的下行数据后，可以传输给处理器1010进行处理；另外，射频单元1001可以向网络侧设备发送上行数据。通常，射频单元1001包括但不限于天线、放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1009可用于存储软件程序或指令以及各种数据。存储器1009可主要包括存储程序或指令的第一存储区和存储数据的第二存储区，其中，第一存储区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1009可以包括易失性存储器或非易失性存储器，或者，存储器1009可以包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器 (Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDRSDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synch link DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DRRAM)。本申请实施例中的存储器1009包括但不限于这些和任意其它适合类型的存储器。
处理器1010可包括一个或至少两个处理单元；可选的，处理器1010集成应用处理器和调制解调处理器，其中，应用处理器主要处理涉及操作系统、用户界面和应用程序等的操作，调制解调处理器主要处理无线通信信号，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1010中。
本申请实施例还提供一种终端，如图8所示，该终端1100包括：天线111、射频装置112、基带装置113、处理器114和存储器115。天线111与射频装置112连接。在上行方向上，射频装置112通过天线111接收信息，将接收的信息发送给基带装置113进行处理。在下行方向上，基带装置113对要发送的信息进行处理，并发送给射频装置112，射频装置112对收到的信息进行处理后经过天线111发送出去。
以上实施例中终端执行的邻小区信息指示方法可以在基带装置113中实现，该基带装置113包括基带处理器。
基带装置113例如可以包括至少一个基带板，该基带板上设置有至少两个芯片，如图8所示，其中一个芯片例如为基带处理器，通过总线接口与存储器115连接，以调用存储器115中的程序，执行以上第一方面的邻小区信息指示方法实施例中所示的网络设备操作。
该终端还可以包括网络接口116，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本申请实施例的终端1100还包括：存储在存储器115上并可在处理器114上运行的指令或程序，处理器114调用存储器115中的指令或程序执行第一方面所示的邻小区信息指示方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供了一种网络侧设备。如图9所示，该网络侧设备1200包括：处理器1201、网络接口1202和存储器1203。其中，网络接口1202例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本申请实施例的网络侧设备1200还包括：存储在存储器1203上并可在处理器1201上运行的指令或程序，处理器1201调用存储器1203中的指令或程序执行第二方面所示的邻小区信息指示方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述邻小区信息指示方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端设备中的处理器。所述可读存储介 质，包括计算机可读存储介质，如计算机只读存储器ROM、随机存取存储器RAM、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述邻小区信息指示方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在存储介质中，所述计算机程序/程序产品被至少一个处理器执行以实现上述邻小区信息指示方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供了一种邻小区信息指示系统，包括：网络侧设备和终端，所述终端用于执行如上述第一方面所述的邻小区信息指示方法的步骤，所述网络侧设备用于执行如上述第二方面所述的邻小区信息指示方法的步骤。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (29)

  1. 一种邻小区信息指示方法，包括：
    终端从服务小区的第一信令中获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
  2. 根据权利要求1所述的方法，其中，所述目标信息包括：第一信息和/或第二信息；
    所述第一信息用于指示支持在非连接态接收多播业务的邻小区；
    所述第二信息用于指示各个邻小区支持在非连接态接收的多播业务信息。
  3. 根据权利要求2所述的方法，其中，所述服务小区的第一信令包括以下至少一项：
    所述服务小区的系统信息块SIB信令，所述SIB信令携带所述第一信息；
    所述服务小区的多播/广播业务控制信道MCCH信令，所述MCCH信令携带所述第一信息和/或所述第二信息。
  4. 根据权利要求1-3任一所述的方法，其中，所述方法还包括：
    所述终端在满足小区选择和/或重选机制的触发条件的情况下，确定目标小区；
    所述终端接入所述目标小区，并从所述目标小区接收所述终端已经加入的多播业务。
  5. 根据权利要求1-3任一所述的方法，其中，所述方法还包括：
    所述终端在满足小区选择和/或重选机制的触发条件的情况下，根据所述目标信息，确定目标小区；
    所述终端接入所述目标小区，并从所述目标小区接收所述终端已经加入的多播业务。
  6. 根据权利要求5所述的方法，其中，所述终端在满足小区选择和/或重选机制的触发条件的情况下，根据所述目标信息，确定目标小区，包括：
    所述终端在满足小区选择和/或重选机制的触发条件的情况下，从所述目标信息指示的各个邻小区中确定出至少一个候选目标小区；
    所述终端根据所述至少一个候选目标小区，按照以下至少一项确定目标小区：
    所述终端将所述至少一个候选目标小区中，支持在非连接态接收所述终端已经加入的多播业务的一个候选目标小区，确定为目标小区，其中，在所述终端已经加入的多播业务的数量是多个的情况下，候选目标小区支持在非连接态接收所述终端已经加入的多播业务是指：候选目标小区支持在非连接态接收所述终端已经加入的所有多播业务；
    所述终端在所述至少一个候选目标小区均不支持在非连接态接收所述终端已经加入的多播业务的情况下，将所述至少一个候选目标小区中的任一候选目标小区确定为目标小区；
    所述终端在所述至少一个候选目标小区部分支持在非连接态接收所述终端已经加入的多播业务的情况下，将所述至少一个候选目标小区中，支持所述终端已经加入的多播业务数量最多或支持的多播业务优先级最高的一个候选目标小区，确定为目标小区；
    其中，候选目标小区不支持在非连接态接收所述终端已经加入的多播业务是指：候选目标小区不支持在非连接态接收所述终端已经加入的所有多播业务；候选目标小区部分支持在非连接态接收所述终端已经加入的多播业务是指：候选目标小区支持在非连接态接收所述终端已经加入的一部分多播业务。
  7. 根据权利要求4或5所述的方法，其中，所述终端从所述目标小区接收所述终端已经加入的多播业务，包括以下至少一项：
    在所述终端在非连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区支持在非连接态接收所述终端已经加入的多播业务的情况下，所述终端保持非连接态接入所述目标小区，所述终端在非连接态从所述目标小区中接收所述终端已经加入的多播业务；
    在所述终端在非连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区不支持在非连接态接收所述终端已经加入的多播业务的情况下，所述终端由非连接态转换至连接态，并接入所述目标小区，所述终端在连接态从所述目标小区中接收所述终端已经加入的多播业务，其中，所述终端是在接入所述目标小区之前或之后由非连接态转换至连接态的。
  8. 根据权利要求4或5所述的方法，其中，所述终端从所述目标小区接收所述终端已经加入的多播业务，包括以下至少一项：
    在所述终端在连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区不支持在非连接态接收所述终端已经加入的多播业务的情况下，所述终端保持在连接态，从所述目标小区中接收所述终端已经加入的多播业务；
    在所述终端在连接态从所述服务小区接收所述终端已经加入的多播业务，且所述目标小区支持在非连接态接收所述终端已经加入的多播业务的情况下，所述终端通过连接态的转换过程由所述服务小区切换至所述目标小区之后或者之前，由连接态转换至非连接态，并在非连接态从所述目标小区中接收所述终端已经加入的多播业务。
  9. 根据权利要求4或5所述的方法，其中，在所述终端已经加入的多播业务的数量是多个的情况下，所述终端从所述目标小区接收所述终端已经加入的多播业务，包括：
    所述终端根据所述终端已经加入的多个多播业务各自的优先级、所述终端的倾向信息以及网络侧设备的指示信息中的至少一者，确定接入所述目标小区后处于连接态或非连接态；
    所述终端在连接态或非连接态从所述目标小区接收所述终端已经加入的多个多播业务。
  10. 根据权利要求4或5所述的方法，其中，所述终端从所述目标小区中接收所述终端已经加入的多播业务，包括：
    所述终端从所述目标小区的SIB信令和/或MCCH信令中，读取所述终端已经加入的多播业务在所述目标小区的目标配置信息；
    所述终端根据所述目标配置信息，从所述目标小区中接收所述终端已经加入的多播业务。
  11. 根据权利要求10所述的方法，其中，所述终端根据所述目标配置信息，在非 连接态从所述目标小区中接收所述终端已经加入的多播业务，包括以下至少一项：
    所述终端在原配置信息与所述目标配置信息相同的情况下，保留所述原配置信息对应的实体和参数，在非连接态从所述目标小区中接收所述终端已经加入的多播业务，所述原配置信息为所述终端已经加入的多播业务在所述服务小区的配置信息；
    所述终端在所述原配置信息和所述目标配置信息不相同的情况下，根据所述目标配置信息进行重配置，在非连接态从所述目标小区中接收所述终端已经加入的多播业务。
  12. 根据权利要求11所述的方法，其中，所述终端根据所述目标配置信息进行重配置，包括以下至少一项：
    所述终端保留数据链路L2实体的序列号SN状态变量或者计数COUNT状态变量的值；
    所述终端将L2实体中的无线链路层控制协议RLC实体进行重建立；
    所述终端保留L2实体中的分组数据汇聚层协议PDCP的COUNT状态变量的值。
  13. 根据权利要求12所述的方法，其中，所述终端保留L2实体中的PDCP的COUNT状态变量的值，包括：
    在所述目标配置信息为确认模式多播/广播业务无线承载AM MRB配置的情况下，所述终端保留L2实体中的PDCP的COUNT状态变量的值。
  14. 根据权利要求2或3所述的方法，其中，所述第一信息为：第一小区ID列表或第一小区索引index列表；
    所述第一小区编号ID列表包括所述第一信令中携带的用于指示支持在非连接态接收至少一个多播业务的各个邻小区的ID；
    所述第一小区index列表为其它信令携带的小区ID列表中，支持在非连接态接收至少一个多播业务的各个邻小区的位置或排序信息。
  15. 根据权利要求2或3所述的方法，其中，所述第二信息为：每个多播业务分别对应的第二小区ID列表或第二小区index列表；
    每个多播业务对应的第二小区ID列表包括支持在非连接态接收该多播业务的各个邻小区的ID；
    每个多播业务对应的第二小区index列表为所述第一信令或其它信令携带的小区ID列表中，支持在非连接态接收该多播业务的各个邻小区的位置或排序信息。
  16. 根据权利要求1-15任一所述的方法，其中，所述方法还包括：
    所述终端接收服务小区的变更后的第一信令，所述服务小区的变更后的第一信令是在邻小区是否支持在非连接态接收多播业务的信息发生变更的情况下生成的；
    所述终端从所述服务小区的变更后的第一信令中，重新获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
  17. 一种邻小区信息指示方法，所述方法包括：
    网络侧设备发送携带目标信息的第一信令，所述目标信息是关于所述网络侧设备控制的小区的邻小区是否支持终端在非连接态接收多播业务的信息。
  18. 根据权利要求17所述的方法，其中，所述网络侧设备发送携带目标信息的第一信令，包括：
    在所述网络侧设备控制的小区的至少一个邻小区支持在非连接态接收多播业务的情况下，所述网络侧设备发送携带目标信息的第一信令。
  19. 根据权利要求17或18所述的方法，其中，所述方法还包括：
    所述网络侧设备接收相邻的网络侧设备控制的小区的多播业务更新信息，所述多播业务更新信息表征邻小区是否支持多播业务的信息发生变更；
    所述网络侧设备根据所述多播业务更新信息，更新所述目标信息；
    所述网络侧设备发送携带更新后的目标信息的第一信令。
  20. 根据权利要求17-19任一所述的方法，其中，所述方法还包括以下至少一项：
    所述网络侧设备恢复或发送多播/广播业务无线承载MRB配置信息，所述MRB配置信息用于终端在接入目标小区后，在连接态从所述目标小区中接收所述终端已经加入的多播业务；
    所述网络侧设备发送数据无线承载DRB配置信息，所述DRB配置信息用于所述终端在接入目标小区后，在连接态从所述目标小区中接收所述终端已经加入的多播业务。
  21. 根据权利要求17-20任一所述的方法，其中，所述第一信令还携带所述网络侧设备控制的小区的多播业务配置信息，一个小区的多播业务配置信息用于终端在该小区中接收所述终端已经加入的多播业务；所述方法还包括：
    所述网络侧设备从相邻的网络侧设备的接口消息中，获取邻小区的多播业务配置信息；
    所述网络侧设备将控制的小区的多播业务配置信息，配置为与所述邻小区的多播业务配置信息相同的信息。
  22. 根据权利要求21所述的方法，其中，所述多播业务配置信息包括以下至少一项：
    多播业务服务质量QoS流到MRB之间的映射关系；
    L2实体的配置信息。
  23. 根据权利要求22所述的方法，其中，所述方法还包括：
    所述网络侧设备将控制的小区的多播业务QoS流到DRB的之间的映射关系，配置为与该小区的邻小区的多播业务QoS流到DRB的之间的映射关系相同的映射关系。
  24. 根据权利要求17-23任一所述的方法，其中，所述方法还包括：
    所述网络侧设备将终端的服务小区配置为支持在非连接态接收所述终端已经加入的所有多播业务；或
    所述网络侧设备将终端的服务小区配置为支持在连接态接收所述终端已经加入的所有多播业务。
  25. 根据权利要求17-24任一所述的方法，其中，所述方法还包括：
    所述网络侧设备发送指示信息，所述指示信息用于指示终端已经加入的多个多播业务各自的优先级。
  26. 一种邻小区信息指示装置，应用于终端，所述装置包括：
    信息接收模块，用于从服务小区的第一信令中获得关于邻小区是否支持在非连接态接收多播业务的目标信息。
  27. 一种邻小区信息指示装置，应用于网络侧设备，所述装置包括：
    信息发送模块，用于发送携带目标信息的第一信令，所述目标信息是关于所述网络侧设备控制的小区的邻小区是否支持终端在非连接态接收多播业务的信息。
  28. 一种终端，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至16任一项所述的邻小区信息指示方法的步骤。
  29. 一种网络侧设备，包括处理器和存储器，所述存储器存储可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求17或25所述的邻小区信息指示方法的步骤。
PCT/CN2024/072596 2023-01-18 2024-01-16 一种邻小区信息指示方法、装置、终端及网络侧设备 Ceased WO2024153083A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US19/271,806 US20250344110A1 (en) 2023-01-18 2025-07-17 Neighbor cell information indication method and apparatus, terminal, and network-side device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310077046.2A CN118368673A (zh) 2023-01-18 2023-01-18 一种邻小区信息指示方法、装置、终端及网络侧设备
CN202310077046.2 2023-01-18

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US19/271,806 Continuation US20250344110A1 (en) 2023-01-18 2025-07-17 Neighbor cell information indication method and apparatus, terminal, and network-side device

Publications (1)

Publication Number Publication Date
WO2024153083A1 true WO2024153083A1 (zh) 2024-07-25

Family

ID=91880901

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/072596 Ceased WO2024153083A1 (zh) 2023-01-18 2024-01-16 一种邻小区信息指示方法、装置、终端及网络侧设备

Country Status (3)

Country Link
US (1) US20250344110A1 (zh)
CN (1) CN118368673A (zh)
WO (1) WO2024153083A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102685684A (zh) * 2011-03-18 2012-09-19 中兴通讯股份有限公司 一种实现mbms业务连续性的方法、系统和用户设备
CN113453159A (zh) * 2020-03-27 2021-09-28 维沃移动通信有限公司 Mbs业务传输方法、mbs业务传输控制方法及相关设备
CN113853824A (zh) * 2019-10-26 2021-12-28 华为技术有限公司 一种通信方法及装置
CN114095875A (zh) * 2020-08-24 2022-02-25 大唐移动通信设备有限公司 多媒体广播多播业务mbms业务的传输区域处理方法
CN114765816A (zh) * 2021-01-14 2022-07-19 大唐移动通信设备有限公司 小区重选方法、装置、网络设备、终端设备、介质及产品
CN115348619A (zh) * 2021-05-10 2022-11-15 中国移动通信有限公司研究院 组播业务的处理方法、装置、相关设备及存储介质

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102685684A (zh) * 2011-03-18 2012-09-19 中兴通讯股份有限公司 一种实现mbms业务连续性的方法、系统和用户设备
CN113853824A (zh) * 2019-10-26 2021-12-28 华为技术有限公司 一种通信方法及装置
CN113453159A (zh) * 2020-03-27 2021-09-28 维沃移动通信有限公司 Mbs业务传输方法、mbs业务传输控制方法及相关设备
WO2021190483A1 (zh) * 2020-03-27 2021-09-30 维沃移动通信有限公司 多播广播业务传输方法、多播广播业务传输控制方法及相关设备
CN114095875A (zh) * 2020-08-24 2022-02-25 大唐移动通信设备有限公司 多媒体广播多播业务mbms业务的传输区域处理方法
CN114765816A (zh) * 2021-01-14 2022-07-19 大唐移动通信设备有限公司 小区重选方法、装置、网络设备、终端设备、介质及产品
CN115348619A (zh) * 2021-05-10 2022-11-15 中国移动通信有限公司研究院 组播业务的处理方法、装置、相关设备及存储介质

Also Published As

Publication number Publication date
US20250344110A1 (en) 2025-11-06
CN118368673A (zh) 2024-07-19

Similar Documents

Publication Publication Date Title
CN113498132B (zh) 移动性管理方法、源基站、目标基站及终端设备
CN112399558A (zh) 寻呼的方法和装置
WO2013113200A1 (zh) 小区列表的处理方法及装置、移动终端
CN102017772B (zh) 一种重定向的方法、装置和系统
CN115623451A (zh) 条件切换方法和设备
CN107371200A (zh) 一种小区重选的方法及装置
WO2024153083A1 (zh) 一种邻小区信息指示方法、装置、终端及网络侧设备
CN113939042A (zh) 处理方法、发送方法及相关设备
WO2024131715A1 (zh) 条件切换方法、装置、终端设备及网络侧设备
CN120128943A (zh) 无线通信方法、装置及设备
WO2024104149A1 (zh) 信息传输方法、装置、终端、网络侧设备及存储介质
WO2022214094A1 (zh) 一种网络切换方法和装置
WO2024208347A1 (zh) 多播业务处理方法、装置、终端及网络侧设备
EP4557782A1 (en) Connection resumption method and apparatus, and terminal and network-side device
CN115696218A (zh) 多播广播业务的接收方法、发送方法、装置及设备
WO2024027403A1 (zh) 通信方法和通信装置
WO2024160240A1 (zh) 多播业务传输方法、装置、终端及网络侧设备
WO2025140202A1 (zh) 通信方法和装置
WO2024160200A1 (zh) 多播业务传输方法、装置、终端及网络侧设备
WO2024067383A1 (zh) 连接建立方法、终端及网络侧设备
WO2025021046A1 (zh) 网络接入方法、装置、ue及网络侧设备
WO2024093777A1 (zh) 终端聚合建立方法、配置方法、装置及通信设备
WO2024012304A1 (zh) 多播业务接收方法、装置、终端及网络侧设备
WO2025055801A1 (zh) 注册方法、网络信息记录方法、装置、终端及网络侧设备
WO2025148973A1 (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: 24744258

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 24744258

Country of ref document: EP

Kind code of ref document: A1