Paging monitoring method and apparatus, paging processing method and apparatus, and related device

By obtaining configuration information to determine the target paging timing (PO), the problem of unnecessary network wake-ups caused by the uniform distribution of paging frames (PF) is solved, thus achieving network energy-saving gains.

WO2026032177A1PCT designated stage Publication Date: 2026-02-12VIVO MOBILE COMM CO LTD
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2025/112317
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2024-08-09
Filing Date
2025-08-04
Publication Date
2026-02-12

AI Technical Summary

Technical Problem

In existing technologies, the paging frame (PF) is evenly distributed within each DRX cycle, causing the network to need to wake up periodically to send paging messages, which is not conducive to network energy saving.

Method used

By obtaining the first configuration information, the paging frame PF and the target paging timing PO that the first type of terminal supports for aggregate paging are determined, and paging listening is performed on the PO.

Benefits of technology

It enables paging processing for PF aggregation, improving network energy efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2025112317_12022026_PF_FP_ABST
    Figure CN2025112317_12022026_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to the technical field of communications, and discloses a paging monitoring method and apparatus, a paging processing method and apparatus, and a related device. The paging monitoring method in embodiments of the present application comprises: a terminal acquires first configuration information, wherein the first configuration information comprises binding information of a first paging frame (PF), the first PF is a PF used for paging a first-type terminal, and the first-type terminal supports aggregated paging; the terminal determines a first target paging occasion (PO) on the basis of the first configuration information; and the terminal performs paging monitoring on the first target PO.
Need to check novelty before this filing date? Find Prior Art

Description

Paging monitoring method, paging processing method, device and related equipment

[0001] Cross-reference to Related Applications

[0002] This application claims priority to Chinese Patent Application No. 202411094439.5, filed on August 9, 2024, the contents of which are incorporated herein by reference in its entirety. TECHNICAL FIELD

[0003] The present application belongs to the field of communication technology, and specifically relates to a paging monitoring method, a paging processing method, a device and related equipment. BACKGROUND

[0004] Currently, to receive a paging message, a terminal first needs to calculate a possible paging occasion (PO) and a paging frame (PF). The calculation method in the related art supports uniformly distributing all PFs in each discontinuous reception (DRX) cycle.

[0005] However, PFs are uniformly distributed in each DRX cycle, and the network needs to wake up regularly to send paging, which is not conducive to network energy saving. Therefore, a PF aggregation scheme is proposed to achieve greater network energy saving gain. However, how to perform paging processing for PF aggregation has become a technical problem to be solved. SUMMARY

[0006] Embodiments of the present application provide a paging monitoring method, a paging processing method, a device and related equipment, which can achieve the purpose of paging processing for PF aggregation.

[0007] In a first aspect, a paging monitoring method is provided, comprising:

[0008] A terminal obtains first configuration information; wherein the first configuration information includes binding information of a first paging frame (PF), the first PF is a PF for paging a first type of terminal, and the first type of terminal supports aggregated paging;

[0009] The terminal determines a first target paging occasion (PO) according to the first configuration information;

[0010] The terminal performs paging monitoring at the first target PO.

[0011] In a second aspect, a paging processing method is provided, comprising:

[0012] The network-side device sends first configuration information to a terminal; wherein the first configuration information comprises binding information of a first PF, the first PF being a PF used for paging a first type of terminal, and the first type of terminal supporting aggregated paging.

[0013] In a third aspect, a paging processing method is provided, comprising:

[0014] A centralized unit (CU) of a network-side device receives capability information sent by a terminal, and sends the capability information to a distributed unit (DU); wherein the capability information is used to indicate whether the terminal supports aggregated paging;

[0015] The DU of the network-side device receives the capability information, and performs paging according to the capability information.

[0016] In a fourth aspect, a paging monitoring apparatus is provided, comprising:

[0017] A first processing module is configured to acquire first configuration information; wherein the first configuration information comprises binding information of a first paging frame (PF), and the first PF is a PF used for paging a first type of terminal, and the first type of terminal supports aggregated paging;

[0018] A second processing module is configured to determine a first target paging occasion (PO) according to the first configuration information.

[0019] A third processing module is configured to perform paging monitoring at the first target PO.

[0020] In a fifth aspect, a paging processing apparatus is provided, comprising:

[0021] A first sending module is configured to send first configuration information to a terminal; wherein the first configuration information comprises binding information of a first PF, the first PF being a PF used for paging a first type of terminal, and the first type of terminal supporting aggregated paging.

[0022] In a sixth aspect, a paging processing apparatus is provided, comprising:

[0023] A capability information transceiving module is configured to receive capability information sent by a terminal, and send the capability information to a distributed unit (DU); wherein the capability information is used to indicate whether the terminal supports aggregated paging;

[0024] A ninth processing module is configured to receive the capability information, and perform paging according to the capability information.

[0025] In a seventh aspect, a paging processing apparatus is provided, which is configured to perform the steps of the method according to the first aspect, or implement the steps of the method according to the second aspect, or implement the steps of the method according to the third aspect.

[0026] In an eighth aspect, a terminal is provided, comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement steps of the method according to the first aspect.

[0027] In a ninth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to:

[0028] obtain first configuration information, wherein the first configuration information comprises binding information of a first paging frame (PF), the first PF being a PF used for paging a first type of terminal, the first type of terminal supporting aggregated paging;

[0029] determine a first target paging occasion (PO) according to the first configuration information;

[0030] perform paging monitoring at the first target PO.

[0031] In a tenth aspect, a network-side device is provided, comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions, when executed by the processor, implement steps of the method according to the second aspect or implement steps of the method according to the third aspect.

[0032] In an eleventh aspect, a network-side device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to send first configuration information to a terminal, wherein the first configuration information comprises binding information of a first PF, the first PF being a PF used for paging a first type of terminal, the first type of terminal supporting aggregated paging.

[0033] In a twelfth aspect, a network-side device is provided, comprising a processor and a communication interface, wherein the communication interface is configured to receive capability information sent by a terminal and send the capability information to a distribution unit (DU), wherein the capability information is used to indicate whether the terminal supports aggregated paging.

[0034] the processor is configured to receive the capability information and perform paging according to the capability information.

[0035] In a thirteenth aspect, a readable storage medium is provided, the readable storage medium storing programs or instructions, the programs or instructions, when executed by a processor, implement steps of the method according to the first aspect, or implement steps of the method according to the second aspect, or implement steps of the method according to the third aspect.

[0036] In a fourteenth aspect, a wireless communication system is provided, comprising: a terminal configured to perform the steps of the method according to the first aspect, and a network-side device configured to perform the steps of the method according to the second aspect or the third aspect.

[0037] In a fifteenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the method according to the first aspect, or to implement the method according to the second aspect, or to implement the method according to the third aspect.

[0038] In a sixteenth aspect, a computer program / program product is provided, which is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the method according to the first aspect, or to implement the steps of the method according to the second aspect, or to implement the steps of the method according to the third aspect.

[0039] In the embodiments of the present application, the terminal first acquires the first configuration information to obtain the binding information of the first PF, and then determines the object of the paging monitoring, i.e., the first target PO, by using the first configuration information. Finally, the terminal can perform the paging monitoring on the first target PO, and realizes the paging monitoring when the PF is bound. BRIEF DESCRIPTION OF DRAWINGS

[0040] FIG. 1 is a block diagram of a wireless communication system;

[0041] FIG. 2 is a schematic diagram of a paging indication field of a conventional PEI;

[0042] FIG. 3 is a flowchart of a method according to an embodiment of the present application;

[0043] FIG. 4 is a schematic diagram of a location of a first PF according to an embodiment of the present application;

[0044] FIG. 5 is a schematic diagram of a location of a first PF according to an embodiment of the present application;

[0045] FIG. 6 is a schematic diagram of a location of a first PF according to an embodiment of the present application;

[0046] FIG. 7 is a schematic diagram of a location of a first PF according to an embodiment of the present application;

[0047] FIG. 8 is a schematic diagram of a location of a first PF according to an embodiment of the present application;

[0048] FIG. 9 is a schematic diagram of a location of a PO of a first PF according to an embodiment of the present application;

[0049] FIG. 10 is a schematic diagram of a location of a PO of a first PF according to an embodiment of the present application;

[0050] FIG. 11 is a third position diagram of the PO of the first PF in the embodiment of the present application;

[0051] FIG. 12 is a fourth position diagram of the PO of the first PF in the embodiment of the present application;

[0052] FIG. 13 is a fifth position diagram of the PO of the first PF in the embodiment of the present application;

[0053] FIG. 14 is a second method flow diagram of the embodiment of the present application;

[0054] FIG. 15 is a third method flow diagram of the embodiment of the present application;

[0055] FIG. 16 is a first module structure diagram of the apparatus of the embodiment of the present application;

[0056] FIG. 17 is a second module structure diagram of the apparatus of the embodiment of the present application;

[0057] FIG. 18 is a third module structure diagram of the apparatus of the embodiment of the present application;

[0058] FIG. 19 is a structure diagram of the communication device of the embodiment of the present application;

[0059] FIG. 20 is a structure diagram of the terminal of the embodiment of the present application;

[0060] FIG. 21 is a structure diagram of the network side device of the embodiment of the present application. DETAILED DESCRIPTION

[0061] The technical solutions in the embodiments of the present application will be clearly described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all the other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0062] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, the scope of protection for "A or B" covers at least three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. In addition, the terms "A and / or B," "at least one of A and B," and "at least one of A or B" also cover at least the above three scenarios. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0063] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc., in the instruction sent. An indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0064] It is worth noting that the technology described in the embodiments of the present application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in other wireless communication systems, such as 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) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th Generation (6G) communication systems. th

[0065] ​FIG. 1 shows a block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a terminal-side device such as a mobile phone, a Tablet Personal Computer, a Laptop Computer, a notebook computer, a Personal Digital Assistant (PDA), a palmtop computer, a netbook, an Ultra-mobile Personal Computer (UMPC), a Mobile Internet Device (MID), an Augmented Reality (AR) device, a Virtual Reality (VR) device, a robot, a wearable device, a flight vehicle, a Vehicle User Equipment (VUE), a shipboard device, a Pedestrian User Equipment (PUE), a smart home (a home device with a wireless communication function such as a refrigerator, a television, a washing machine, or furniture), a game console, a Personal Computer (PC), a kiosk, or a self-service machine. The wearable device includes a smart watch, a smart bracelet, a smart earphone, smart glasses, smart jewelry (a smart bracelet, a smart necklace, a smart ring, a smart necklace, a smart anklet, a smart necklace, etc.), a smart wristband, smart clothes, etc. The vehicle-mounted device can also be referred to as a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip, or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. The access network device can also be referred to as a Radio Access Network (RAN) device, a radio access network function, or a radio access network unit. The access network device can include a base station, a Wireless Local Area Network (WLAN) Access Point (AP), or a Wireless Fidelity (WiFi) node, etc.The base station can be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a relay station (RBS), a serving base station (SBS), a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home Node B (HNB), a home evolved Node B, a transmit / receive point (TRP), or some other suitable terminology in the art, and is not limited to a particular technical terminology, provided that the same technical effect is achieved. It should be noted that in the embodiments of the present application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0066] The core network device can also be referred to as a core network node, a core network function, or a core network network element, etc., which includes but is not limited to at least one of the following: a mobility management entity (MME), an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a policy control function (PCF), a policy and charging rules function (PCRF), an edge application server discovery function (EASDF), a unified data management (UDM), a unified data repository (UDR), a home subscriber server (HSS), a centralized network configuration (CNC), a network repository function (NRF), a network exposure function (NEF), a local NEF (L-NEF), a binding support function (BSF), an application function (AF), a location management function (LMF), a gateway mobile location center (GMLC), a network data analytics function (NWDAF), etc. It should be noted that only the core network device in the NR system is taken as an example for introduction in the embodiments of the present application, and the specific type of the core network device is not limited. If the name of the core network device mentioned in the embodiments of the present application changes in the subsequent protocol version (for example, 6G), it is also within the protection scope of the present application.

[0067] Optionally, the core network device can be implemented by one or more function modules in one device, or can be implemented by multiple devices together, and the embodiments of the present application do not make a specific limitation in this regard. It can be understood that the above function modules can be network elements in a hardware device, can be software function modules running on a special hardware, or can be virtualized function modules instantiated on a platform (for example, a cloud platform).

[0068] For the convenience of understanding, some contents related to the embodiments of the present application are described as follows:

[0069] I. Paging

[0070] When the terminal is in an idle or inactive state, the network cannot know the specific cell where the terminal is located, and can only grasp the approximate range where the terminal is located. Therefore, when there is a service arrival or other reasons for the terminal to enter a connected state, a paging mechanism needs to be used to notify the terminal and trigger the terminal to enter the connected state through a random access channel (RACH).

[0071] The principle of the paging mechanism is to use a physical downlink shared channel (PDSCH) carrying a paging message delivered by a physical downlink control channel (PDCCH) indication. A user equipment (UE) monitors the PDCCH on a specific time-frequency resource (such as a PF, PO), receives the paging message sent to itself. Therefore, to receive the paging message, the UE first needs to calculate the possible paging PO (Paging Occasion) and PF (Paging Frame), and then starts monitoring the PDCCH of the corresponding subframe. If a paging radio network temporary identity (P-RNTI) is found, the UE obtains the paging message from the corresponding PDSCH according to the resource block (RB) allocation and modulation and coding format indicated by the PDCCH. The UE determines whether the paging message is sent to itself according to the UE identity (ID) carried in the paging message.

[0072] The PF and PO can be calculated by the UE according to the configuration information of the network, and the calculation formula of the PF and PO is as follows: PF: (SFN+PF_offset)mod T=(T div N)*(UE_ID mod N); PO: i_s=floor(UE_ID / N)mod Ns;

[0073] T: DRX cycle of the UE.

[0074] N: total number of PFs in a DRX cycle T (network configurable as oneT, halfT, quarterT, oneEighthT and oneSixteenthT).

[0075] PF_offset: offset to determine the PF position.

[0076] UE_ID: 5G-S-TMSI mod 1024, or UE_ID = 0 (when UE has no 5G-S-TMSI mod 1024).

[0077] Ns: number of POs in a PF (network configurable as 1, 2, 4).

[0078] The effect of the calculation formula of PF is to uniformly distribute UEs with different UE_IDs in N PFs, and N PFs are also uniformly distributed in T. The effect of the PO formula is to uniformly distribute POs of different UEs in POs of different PFs.

[0079] II. Paging Early Indication (PEI) mechanism

[0080] The PEI mechanism associates the PEI occasion with the PO of the UE by grouping the UEs, so as to achieve the purpose of controlling the PO through the PEI. When the UE receives the PEI of the subgroup to which the UE belongs, it means that there is paging to receive, and the UE will listen to the paging in the associated PO. Otherwise, the UE can continue to sleep, thereby achieving energy saving.

[0081] Specifically, the terminal will listen to a PEI occasion (PEI-O) in each DRX cycle, and a PEI-O includes a group of PDCCH monitoring occasions. The time domain starting position of the PEI-O is determined by a reference point and an offset. The reference point refers to the starting position of the reference frame, which is determined by the starting frame of the first PF in the PF associated with the PEI-O (pei-FrameOffset in the System Information Block (SIB) 1). The offset is the symbol level offset from the reference point to the first PDCCH monitoring occasion of the PEI-O (firstPDCCH-MonitoringOccasionOfPEI-O in the SIB 1).

[0082] The downlink control information (DCI) that the UE specifically monitors in the PEI-O is DCI 2_7, which is used to issue PEI to a group of UEs, wherein, as shown in FIG. 2, the paging indication field contains bits, wherein configured by the RRC layer parameter po-NumPerPEI, indicating the number of POs corresponding to one PEI-O, configured by the RRC layer parameter subgroupsNumPerPO, indicating the number of subgroups corresponding to one PO; the UE needs to determine the (i PO ·K+i SG )th bit in the paging indication field, wherein corresponds to a paging occasion index. When the value of the bit corresponding to the paging indication field is 1, the UE needs to monitor the associated PO, otherwise it does not need to monitor the corresponding PO. K is the number of subgroup bits.

[0083] Grouping method in PEI

[0084] There are two currently supported grouping methods, CN assigned subgrouping and UE_ID based subgrouping. UEs in RRC_IDLE or RRC_INACTIVE state that support CN assigned subgrouping can be assigned a subgroup ID (between 0 and 7) by the AMF through NAS signaling, and UEs belonging to the assigned subgroup ID monitor their associated PEI. If the UE is not configured with a CN assigned subgroup ID, or if it is configured with a CN assigned subgroup ID but the UE is in a cell that only supports UE_ID based subgrouping, the subgroup ID of the UE is determined by the following formula: SubgroupID=(floor(UE_ID / (N*Ns))mod subgroupsNumForUEID)+ (subgroupsNumPerPO-subgroupsNumForUEID);

[0085] wherein, N: the total number of PFs in the DRX cycle T (network configurable as oneT, halfT, quarterT, oneEighthT and oneSixteenthT).

[0086] PF_offset: offset to determine the PF location.

[0087] UE_ID: 5G-S-TMSI mod X, X is 32768 if eDRX is applied; otherwise X is 8192.

[0088] Ns: number of POs in one PF (network configurable to 1, 2, 4).

[0089] subgroupsNumForUEID: number of subgroups based on UE ID grouping in one PO, broadcast in system message.

[0090] III. Common signal adaptation

[0091] Common signal adaptation is discussed in R19 network energy saving project, which includes paging adaptation, mainly to achieve greater network energy saving gain by aggregating PFs. Currently, two ways of PF aggregation are discussed. Way one includes binding all PFs together, and way two includes configuring a PF by the network (the mechanism in the related art only supports configuring at least two PFs), but supports configuring more POs in one PF. For way one, the specific binding method is still under discussion.

[0092] The paging monitoring method, paging processing method, device and related equipment provided by the embodiments of the present application will be described in detail in combination with the accompanying drawings and some embodiments and application scenarios.

[0093] As shown in FIG. 3, a paging monitoring method according to an embodiment of the present application includes:

[0094] Step 301: A terminal acquires first configuration information; wherein the first configuration information includes binding information of a first paging frame PF, the first PF is a PF for paging a first type of terminal, and the first type of terminal supports aggregated paging.

[0095] Step 302: The terminal determines a first target paging occasion PO according to the first configuration information.

[0096] Step 303: The terminal performs paging monitoring at the first target PO.

[0097] Here, the first configuration information can be configured and sent by the network side device, or can be predefined. According to steps 301-303, the terminal first acquires the first configuration information to learn the binding information of the first PF; then, the first configuration information is used to determine the object of the paging listening, that is, the first target PO; finally, the terminal can perform paging listening on the first target PO, and realize paging listening when the PF is bound.

[0098] It should be noted that in this embodiment, the terminal is a first type terminal, and can also be understood as a terminal supporting aggregated paging. Wherein, the terminal supports aggregated paging, that is, the terminal will listen to paging on the aggregated PF, and the aggregated PF is the bound PF, or the bound PF can also be represented as the PFs that are continuous in time domain, which can be one or more groups of first PFs after individual binding of all first PFs, or one or more groups of PFs after binding of the first PFs and the second PFs.

[0099] Optionally, in this embodiment, the binding mode of the first PF can include two kinds, one is that the first PF is bound with the second PF, for example, as shown in FIG. 4, all first PFs are grouped and bound with multiple second PFs respectively; one is that the first PF is not bound with the second PF, for example, all first PFs are individually bound. Wherein, the second PF is used for paging terminals that do not support aggregated paging. The binding information of the first PF can reflect the binding mode of the first PF.

[0100] In this embodiment, the first PF can also be referred to as a network energy saving (NES) PF, and the second PF can also be referred to as a legacy PF.

[0101] Optionally, in this embodiment, the first configuration information includes at least one of the following:

[0102] A first parameter, the first parameter is used to indicate the number of bound first PFs;

[0103] A second parameter, the second parameter is used to indicate the number of POs in each first PF;

[0104] A paging listening factor, the paging listening factor is used to indicate the listening behavior of the terminal;

[0105] A first offset, the first offset is used to indicate the offset between the first PF and the second PF;

[0106] A third parameter, the third parameter is used to indicate the number of second PFs bound by the first PF;

[0107] a second offset, used to indicate an offset of the first PF per discontinuous reception (DRX) cycle;

[0108] a fourth parameter, used to indicate a total number of POs in all the first PFs;

[0109] a first position, used to indicate a position of a starting PF in the bound PFs;

[0110] a fifth parameter, used to indicate a first physical downlink control channel (PDCCH) monitoring occasion per PO in the bound PFs;

[0111] a first indication information, used to indicate whether the terminal can simultaneously monitor the first PF and the second PF;

[0112] wherein the second PF is a PF used for paging a second type of terminal, and the second type of terminal does not support aggregated paging.

[0113] In an implementation, if the first PF is bound to the second PF, the first parameter can be a total number of all the first PFs, such as a number of all the first PFs in a cell. Alternatively, the first parameter can also be a number of the first PFs bound to one second PF; if the first PF is not bound to the second PF, the first parameter can be a total number of all the first PFs, such as a number of all the first PFs in a cell.

[0114] In an implementation, the terminal can determine a monitoring behavior of the terminal based on the paging monitoring factor, and the monitoring behavior of the terminal includes that the terminal needs to determine one PF for monitoring in all the first PFs, or needs to determine one PF for monitoring in the first PF and the second PF. For example, the paging monitoring factor can have a value of 0 or 1, when the value is 0, it indicates that the UE only needs to determine one PF for monitoring in all the NES PFs; when the value is 1, it indicates that the UE can determine one PF for monitoring in the legacy PF and the NES PF.

[0115] Alternatively, the paging monitoring factor can also be understood as being used to indicate a type of PF monitored by the terminal. Correspondingly, the paging monitoring factor can have a value of 0 or 1, when the value is 0, it indicates that the type of PF monitored by the UE is the first PF; when the value is 1, it indicates that the type of PF monitored by the UE needs to be determined in the first PF and the second PF.

[0116] Alternatively, the terminal can also simultaneously monitor the first PF and the second PF, whether to allow simultaneous monitoring of the first PF and the second PF can be based on a network side indication or based on a protocol agreement. In an implementation, the first offset can indicate an offset between the first PF and the second PF bound to the first PF.

[0117] In an implementation, the first position can indicate a position of a first one of the PFs in the binding. For example, if three PFs, SFN1, SFN2 and SFN3, are bound, the network indication can explicitly indicate that the first position is SFN1. Alternatively, the terminal can determine the first paging position in the binding by itself through calculation.

[0118] In an implementation, the first indication information can indicate whether the terminal can simultaneously listen to the legacy PF / PO and the NES PF / PO, or listen to any one of the legacy PF / PO and the NES PF / PO. Specifically, if the first PF and the second PF are bound, the first indication information can be configured to indicate that the terminal simultaneously listens to the first PF and the second PF, or the first indication information can be configured to indicate that the terminal listens to the first PF or the second PF. If the first PF is not bound with the second PF, the first indication information can be configured to indicate that the terminal listens to the first PF or the second PF, or the first indication information can be configured to indicate that the terminal simultaneously listens to the first PF and the second PF.

[0119] Optionally, in this embodiment, before the terminal determines the first target paging occasion PO according to the first configuration information, the method further includes:

[0120] The terminal acquires the position and configuration of the second PF.

[0121] The configuration of the second PF is configured by the network side device or predefined. The terminal acquiring the configuration of the second PF can include, but is not limited to, the number of the second PF (such as the number of all second PFs in a cell).

[0122] The terminal acquiring the position of the second PF can be the position of the second PF that the UE needs to listen to, which is calculated by the legacy PF calculation formula "(SFN+PF_offset)mod T=(T div N)*(UE_ID mod N)". For example, if two legacy PFs are configured in the current network, UE1 calculates that the legacy PF to be listened to is SFN0, and UE2 calculates that the legacy PF to be listened to is SFN16.

[0123] Correspondingly, the terminal determines the first target paging occasion PO according to the first configuration information, including:

[0124] The terminal determines the target PF based on at least one of the first target PF strategy, the first configuration information, the identity of the terminal, the position of the second PF and the configuration of the second PF.

[0125] The terminal determines the first target PO in the target PF based on at least one of the first target PO policy, the first configuration information, an identifier of the terminal, and a configuration of the second PF.

[0126] That is, the terminal first determines the target PF (or the location of the target PF), and then determines the first target PO (or the location of the first target PO) in the target PF.

[0127] In the embodiments of the present application, when considering binding all first PFs, one way can bind the NES PF and the legacy PF together, which can maximize the energy consumption generated by the sending of the paging message. Secondly, the NES PF bound with the legacy PF can be grouped according to the legacy PF, and compared with binding all NES PFs in one group, the advantage is that the RACH is dispersed to a certain extent.

[0128] In the embodiments of the present application, the first type of terminal (NES UE) can determine a PF to listen to paging in all NES PFs (all NES UEs are mapped to all NES PFs), or can determine a PF to listen to paging in all NES PFs and legacy PFs (NES UEs can be mapped to NES PFs and legacy PFs together), and the advantage of the latter is that, when there are fewer legacy UEs, a part of NES UEs can be allocated to the legacy PF to listen, which can reduce the load of the NES PF to a certain extent. In this embodiment, the meaning of mapping can be represented as: each UE can calculate the PF that needs to be listened to according to its own UE identifier in all candidate PFs.

[0129] Optionally, the first target PF policy is one of first preset PF policies, and the first preset PF policies include a first PF policy, a second PF policy, a third PF policy, and a fourth PF policy.

[0130] The first PF policy is used in the case of binding the first PF and the second PF.

[0131] The second PF policy is used in the case of binding and overlapping the first PF and the second PF.

[0132] The third PF policy is used in the case of binding and existing interval between the first PF and the second PF.

[0133] The fourth PF policy is used in the case of binding the first PF.

[0134] Therefore, if the first PF is bound with the second PF (all the first PFs are bound with the second PFs), the first target PF strategy used by the terminal is the first PF strategy; if the first PF is bound with the second PF and overlaps (all the first PFs are bound with the second PFs), the first target PF strategy used by the terminal is the second PF strategy; if the first PF is bound with the second PF and there is an interval (all the first PFs are bound with the second PFs, as shown in FIG. 7), the first target PF strategy used by the terminal is the third PF strategy; if the first PF is bound (the first PF is not bound with the second PF, all the first PFs are bound alone), the first target PF strategy used by the terminal is the fourth PF strategy.

[0135] In an implementation, the first PF strategy is: determining the NES PF by NES PF = legacy PF + [(UE_ID mod(N_new / N’+factor))-(factor-1)], the NES PF representing the first PF position (such as SFN) that the UE needs to listen to. Wherein, the legacy PF represents the position of the legacy PF calculated by the terminal according to the traditional formula (legacy PF calculation formula);

[0136] N_new is the first parameter, which can be the number of all NES PFs of the cell;

[0137] N’ represents the number of bound legacy PFs, so N_new / N’ represents that the NES PFs are divided into N groups;

[0138] The factor represents a paging listening factor, which can be configured as 0 when the network only wants the UE to perform mapping in all NES PFs (only the NES PF is the candidate PF); the factor can be configured as 1 when the network wants the UE to perform mapping in the NES PF and the legacy PF (both the NES PF and the legacy PF are candidate PFs).

[0139] Specifically, when the network configures the paging monitoring factor, the mapping manner of the UE (i.e., whether the NES UE only maps to all NES PFs or can map to NES PFs and legacy PFs) can be determined based on the network configuration. When the first parameter in the first configuration information is 6, and the number of the second PFs indicated in the second PF configuration is 2, N' = 2, and the calculated legacy PF positions include SFN = {0, 16}. When the network only wants the UE to map in all NES PFs, the factor can be configured as 0, and then according to the first PF strategy, as shown in FIG. 5, the SFN of all the PFs (NES PFs) that can be mapped is {1, 2, 3, 17, 18, 19}. When the network wants the UE to map in NES PFs and legacy PFs, the factor can be configured as 1, and then according to the first PF strategy, as shown in FIG. 6, the SFN of all the PFs (NES PFs + legacy PFs) that can be mapped is {0, 1, 2, 3, 16, 17, 18, 19}. In this way, for a certain terminal such as UE1, the legacy PF is SFN0, and when the factor is configured as 0, the target PF (NES PF) position can be determined based on the UE identifier in SFN1, SFN2, and SFN3.

[0140] In an implementation, the NES PF does not overlap with the legacy PF, and by default, the NES UE only maps in all NES PFs, the factor = 0, and the formula in the first PF strategy is NES PF = legacy PF + [(UE_ID mod(N_new / N')) + 1].

[0141] In an implementation, the second PF strategy is NES PF = legacy PF + [UE_ID mod(N_new / N')], and the NES PF is determined. When the first parameter indicated in the first configuration information is 6, and N' is equal to the number of PFs indicated in the legacy configuration, i.e., 2, the legacy PF positions include SFN = {0, 16}, and then according to the second PF strategy, the SFN of all the PFs that can be mapped is {0, 1, 2, 16, 17, 18}. For a certain terminal such as UE1, the legacy PF is SFN0, and the target PF position can be determined based on the UE identifier in SFN1, SFN2, and SFN3.

[0142] In an implementation, the third PF strategy is: determining the NES PF by NES PF=legacy PF+Offset+[UE_ID mod(N_new / N)'] or NES PF=legacy PF-Offset+[UE_ID mod(N_new / N')]. Wherein, the Offset is the first offset. Of course, the first offset is also applicable in the formula of the first PF strategy, + / -Offset after the legacy PF.

[0143] In an implementation, if the first PF is only bound with part of the second PF, in the first PF strategy, the second PF strategy, and the third PF strategy, the value of N' will no longer be equal to the number of PFs indicated in the legacy configuration, such as N'=N1, N1 is the number of bound second PFs, such as indicated by the third parameter in the first configuration information. For example, the formula in the first PF strategy becomes NES PF=legacy PF+[(UE_ID mod(N_new / N1+factor))-(factor-1)]. Of course, in the formula of the legacy PF calculation, N should be replaced by N1, that is, (legacy PF+PF_offset)mod T=(T div N1)*(UE_ID mod N1). For example, as shown in FIG. 8, the current network is configured with 4 legacy PFs, SFN0, SFN8, SFN16, and SFN32, and the network is configured with N1=2, indicating that the network only wants to bind the NES PF with two of the legacy PFs (SFN0 and SFN8). Optionally, if the network only wants to bind with one legacy PF, N1 can be configured as 1.

[0144] In an implementation, the fourth PF strategy is used for the case where the first PF is bound by itself, and the NES PF position is determined by (NES PF+offset)mod T=UE_ID mod N_new.

[0145] Specifically, in the process of determining the target PF, the terminal determines the information required by the first target PF strategy based on at least one of the first configuration information, the identifier of the terminal, the position of the second PF, and the configuration of the second PF, and brings the information into the formula of the first target PF strategy to determine the target PF.

[0146] Optionally, in this embodiment, the first target PO strategy is one of the first preset PO strategies, and the first preset PO strategies include a first PO strategy, a second PO strategy, and a third PO strategy.

[0147] In the first PO strategy, the type of the PF to be listened to is the first PF.

[0148] the type of the PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the second PF;

[0149] the type of the PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the first PF.

[0150] Therefore, if the type of the PF to be monitored is the first PF, that is, the UE only performs mapping in all NES PFs, the first target PO strategy is the first PO strategy; if the type of the PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the second PF, that is, the UE can perform mapping in legacy PFs and NES PFs, if the UE calculates that the PF to be monitored is a legacy PF, the first target PO strategy is the second PO strategy; if the type of the PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the first PF, that is, the UE can perform mapping in legacy PFs and NES PFs, if the UE calculates that the PF to be monitored is a NES PF, the first target PO strategy is the third PO strategy.

[0151] In an embodiment, the first PO strategy is: determining i_s’ by i_s’ = floor(UE_ID / N_new) mod N2, wherein i_s’ represents the serial number of the first target PO, and N2 represents a second parameter, that is, the number of POs in each first PF.

[0152] In an embodiment, the second PO strategy is: determining i_s’ by i_s’ = floor(UE_ID / (N_new+N)) mod Ns.

[0153] In an embodiment, the second PO strategy is: determining i_s’ by i_s’ = floor(UE_ID / (N_new+N)) mod N2. Wherein N represents the number of legacy PFs.

[0154] In this way, in the case of binding of the first PF and the second PF, the serial number of the first target PO is determined, and the position of the first target PO can be determined, which will not be described herein.

[0155] Optionally, in this embodiment, the terminal acquires the position of the second PF, comprising:

[0156] In the case that the first PF is bound with the second PF, the terminal determines the location of the first target PO based on the number of the second PFs bound by the first PF and the sequence number of the first target PO.

[0157] That is, the legacy PF is determined by (legacy PF+PF_offset)mod T=(T div N1)*(UE_ID mod N1). N1 is the number of the second PFs bound.

[0158] In addition, when all the NES PFs are bound together, as shown in FIG. 9, in a first mode, each of the NES PFs is bound together (for example, the NES PFs can be consecutive SFNs, such as SFN1, SFN2, SFN3, and the like), and in a second mode, the POs in all the NES PFs are bound together. Compared with the first mode, the second mode can achieve greater NES energy saving gain.

[0159] Optionally, in this embodiment, the terminal determines the first target PO according to the first configuration information, including:

[0160] The terminal determines the sequence number of the first target PO based on the first configuration information and the identity of the terminal.

[0161] In the case that the first PF is bound with the second PF, the terminal determines the location of the first target PO based on the location of the PO of the second PF and the sequence number of the first target PO.

[0162] In the case that the first PF is not bound with the second PF, the terminal determines the location of the first target PO based on the location of the first PF and the sequence number of the first target PO.

[0163] In this way, for the case that the first PF is bound with the second PF (actually, the PO of the first PF is bound with the PO of the second PF) or the case that the first PF is bound alone (actually, the PO of the first PF is bound), the sequence number of the first target PO can be determined based on the first configuration information and the identity of the terminal, and then the location of the first target PO can be determined in the applicable manner for the two cases.

[0164] Optionally, the sequence number of the first target PO can be determined based on the first configuration information and the identity of the terminal by calculating nes_i_s=UE_ID mod Nt, where nes_i_s represents the sequence number of the first target PO. Nt is a fourth parameter, that is, the total number of the POs in all the first PFs. Optionally, Nt can also be represented as the second parameter*the first parameter. nes_i_s takes a value of [0, Nt-1].

[0165] In the case of the first PF and the second PF binding, the ending PO position in each legacy PF position is the starting position of the bound NES PO. In this way, the UE can determine the NES PO starting position according to the legacy PO position. For example, if each legacy PF currently supports configuring 4 POs, then SFN1 includes 4 POs, i_s (PO position number) = {0, 1, 2, 3}, and SFN6 includes 4 POs, i_s (PO position number) = {0, 1, 2, 3}, and the UE determines the NES PO starting position according to the legacy PO position. Then, based on the UE knowing the sequence number of the first target PO, the position of the first target PO can be determined.

[0166] Specifically, based on the sequence number nes_i_s of the first target PO, the sequence number n of the legacy PF that needs to be actually monitored can be obtained through the formula [Nt / N]*(n-1)<nes_i_s<[(Nt / N]*n. Wherein, N is the number of legacy PFs. As shown in FIG. 10, if the UE needs to perform mapping in the NES PO, N=2, Nt=12, nes_i_s is calculated as 2 (the third PO), then n=1, and the UE needs to actually monitor the PO with the sequence number i_s=Ns+nes_i_s in the first legacy PF. Wherein, Ns=4, nes_i_s=2, so i_s=6, that is, the position of the seventh PO in SFN0 is the position of the first target PO. Optionally, when the UE needs to perform mapping in the legacy PO and the NES PO together, then the UE needs to actually monitor the PO with the sequence number i_s=nes_i_s=2 in the first legacy PF, that is, the third PO in SFN0; that is, the NES PO will continue to arrange along the legacy PO number. Optionally, if the network configures the first PO monitoring occasion, then the first PDCCH monitoring occasion of each PO is determined by the first PO monitoring occasion, and if not, the PDCCH MO is arranged in sequence.

[0167] In the case that the first PF is not bound with the second PF, the terminal can determine the location of the first target PO in combination with the location of the first PF, i.e., the location of the PO in the first PF in the bound first PF, after determining nes_i_s. For example, as shown in FIG. 11, in the case that 6 first PFs are bound, i.e., 12 POs in total, the location of the first target PO can be determined by the location of the PO in the first PF and nes_i_s. The location of the PO in the first PF in the bound first PF can be determined by at least one of the following: a start PF location indicated by the network; a second offset indicated by the network; and a first PF location in the candidate PF (all PFs) determined by the UE through calculation.

[0168] In the case that the first PF is not bound with the second PF, the first PDCCH monitoring occasion of each PO can be determined by the first PO monitoring occasion if the network configures the first PO monitoring occasion, or arranged in the order of the PDCCH monitoring occasion (MO) if the network does not configure the first PO monitoring occasion.

[0169] Optionally, in this embodiment, the method further comprises:

[0170] The terminal acquires second configuration information, wherein the second configuration information comprises information of a first paging early indication (PEI); and the first PEI is associated with one or more first PFs.

[0171] Optionally, the first PEI is associated with a group of bound first PFs, or the first PEI is associated with multiple groups of bound first PFs.

[0172] That is, one first PEI can be associated with a group of bound first PFs, so that if there are A groups of bound first PFs, there are A first PEIs; or one first PEI can be associated with multiple groups of bound first PFs, as shown in FIG. 12 or FIG. 13, so that if there are A groups of bound first PFs, the number of first PEIs is less than A.

[0173] In FIG. 12, NES PEI is the first PEI.

[0174] The second configuration information can be configured by the network side device or predefined.

[0175] Optionally, the second configuration information comprises at least one of the following:

[0176] A sixth parameter, the sixth parameter is used to indicate the number of POs associated with the first PEI;

[0177] A first load, the first load is used to indicate the load of the downlink control information (DCI) of the first PEI.

[0178] a third offset, used to indicate an offset between a first PF associated with the first PEI and a reference frame;

[0179] a fourth offset, used to indicate an offset between the reference frame of the first PEI and a first PDCCH monitoring occasion.

[0180] The third offset can indicate how many frames the offset between the first PF associated with the first PEI and the reference frame is. The fourth offset can indicate how many symbols the offset between the reference frame of the first PEI and the first PDCCH monitoring occasion is.

[0181] Optionally, the method further comprises:

[0182] The terminal determines an identity of a second target PO in the first PEI according to at least one of a second target PO policy, an identity of the terminal, the first configuration information and the second configuration information;

[0183] The terminal determines a position of a first first PF associated with the first PEI according to at least one of a second target PF policy, the identity of the second target PO, the first configuration information and the second configuration information;

[0184] The terminal determines the second target PO according to the identity of the second target PO and the position of the first first PF associated with the first PEI.

[0185] In this way, after the second target PO is determined, it can be determined whether it is necessary to wake up to monitor paging at the associated NES PF / PO position, and whether to monitor the first target PO. Wherein, NES_i po indicates the identity of the second target PO, and NES_firstPF indicates the position of the first first PF associated with the first PEI.

[0186] Optionally, the second target PF policy is one of a second preset PF policy, and the second preset PF policy includes a fifth PF policy, a sixth PF policy, a seventh PF policy, an eighth PF policy, a ninth PF policy, a tenth PF policy, an eleventh PF policy, a twelfth PF policy, a thirteenth PF policy, a fourteenth PF policy and a fifteenth PF policy.

[0187] The fifth PF policy is used in a case where all the first PFs are not bound to the second PF, and the type of the PF to be monitored is the first PF.

[0188] The sixth PF policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located before the first PF;

[0189] The seventh PF policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located after the first PF;

[0190] The eighth PF policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located before the first PF;

[0191] The ninth PF policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located after the first PF;

[0192] The tenth PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened is the first PF, and the first PEI is associated with a group of bound first PFs;

[0193] The eleventh PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened is the first PF, and the first PEI is associated with multiple groups of bound first PFs;

[0194] The twelfth PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with a group of bound first PFs;

[0195] The thirteenth PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with multiple groups of bound first PFs;

[0196] The fourteenth PF strategy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a group of bound first PFs.

[0197] The fifteenth PF strategy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a plurality of groups of bound first PFs.

[0198] Therefore, the terminal can apply one of the second preset PF strategies as the second target PF strategy for different cases.

[0199] In an embodiment, the fifth PF strategy is: determining NES_firstPF by NES_firstPF = (SFN for NES PF) - floor(NES_i PO / N2). SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, i.e., the number of POs in each first PF.

[0200] When all the first PFs are individually bound, or the network only configures one NES PF (increasing the number of POs in each NES PF), if the PF actually monitored by the UE only needs to be mapped in the NES PF, the fifth PF strategy is used to determine NES_firstPF.

[0201] In an embodiment, the sixth PF strategy is: determining NES_firstPF by NES_firstPF = (SFN for NES PF) - floor((NES_i PO -Ns) / N2). SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, i.e., the number of POs in each first PF.

[0202] When all first PFs are individually bound, or the network only configures one NES PF (increasing the number of POs in each NES PF), if the PF that the UE actually monitors needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF that needs to be monitored is the legacy PF (because at this time the legacy PF is not bound with the NES PF, so only the position of the associated first PF can be determined according to the NES PF), if the legacy PF appears in front of the NES PF: according to the sixth PF strategy, the NES_firstPF is determined.

[0203] In an embodiment, the seventh PF strategy is: the NES_firstPF is determined by NES_firstPF=(SFN for NES PF)-floor(NES_i PO / N2). Wherein SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, that is, the number of POs in each first PF.

[0204] When all first PFs are individually bound, or the network only configures one NES PF (increasing the number of POs in each NES PF), if the PF that the UE actually monitors needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF that needs to be monitored is the legacy PF (because at this time the legacy PF is not bound with the NES PF, so only the position of the associated first PF can be determined according to the NES PF), if the legacy PF appears in front of the NES PF: according to the sixth PF strategy, the NES_firstPF is determined.

[0205] In an embodiment, the eighth PF strategy is: the NES_firstPF is determined by NES_firstPF=(SFN for NES PF)-floor((NES_i PO -Ns) / N2). Wherein SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, that is, the number of POs in each first PF.

[0206] When all first PFs are individually bound, or the network only configures one NES PF (increasing the number of POs in each NES PF), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is the NES PF, if the legacy PF appears in front of the NES PF, the NES_firstPF is determined according to the eighth PF strategy.

[0207] In an implementation, the ninth PF strategy is: the NES_firstPF is determined by NES_firstPF = (SFN for NES PF) - floor(NES_i PO / N2). Wherein, the SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, that is, the number of POs in each first PF.

[0208] When all first PFs are individually bound, or the network only configures one NES PF (increasing the number of POs in each NES PF), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is the NES PF, if the legacy PF appears in front of the NES PF, the NES_firstPF is determined according to the eighth PF strategy.

[0209] In an implementation, the tenth PF strategy is: the NES_firstPF is determined by NES_firstPF = (SFN for NES PF) - floor(NES_i PO / N2). Wherein, the SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, that is, the number of POs in each first PF.

[0210] When all first PFs and second PFs are bound (equivalent to dividing the NES PF into multiple groups according to the number of legacy PFs), if the PF actually monitored by the UE only needs to be mapped in the NES PF, if a first PF is associated with a group of bound first PFs, the NES_firstPF is determined according to the tenth PF strategy.

[0211] In an implementation, the eleventh PF strategy is: the NES_firstPF is determined by NES_firstPF = [(SFN for NES PF) - floor(NES_i PO / N2)] - floor(NES_i PON2), to determine NES firstPF. Wherein, SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, i.e., the number of POs in each first PF.

[0212] When all the first PFs and the second PFs are bound (equivalent to binding the NES PFs into multiple groups according to the number of legacy PFs), if the PF actually monitored by the UE only needs to be mapped in the NES PF, if one first PEI is associated with multiple groups of bound first PFs, the eleventh PF strategy is used to determine NES firstPF.

[0213] In an implementation, the twelfth PF strategy is: NES firstPF is determined by NES firstPF = (SFN for NES PF) - floor((NES_i PO -Ns) / N2). Wherein, SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, i.e., the number of POs in each first PF.

[0214] When all the first PFs and the second PFs are bound (equivalent to binding the NES PFs into multiple groups according to the number of legacy PFs), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is a legacy PF, if one first PEI is associated with one group of bound first PFs, the twelfth PF strategy is used to determine NES firstPF. Optionally, the associated first PF can also be a legacy PF (if the associated first PF is a legacy PF, the frame offset of the sharing mechanism can be reused to determine the position of the PEI reference frame, and optionally, the frame offset of the NES can also be used) legacy firstPF = (SFN for NES PF) - floor((NES_i PO -Ns) / N2) - 1.

[0215] In an implementation, the thirteenth PF strategy is: NES firstPF is determined by NES firstPF = [(SFN for NES PF) - floor(NES_i PO / N2)] - floor(NES_i PON2), to determine NES firstPF. Wherein, SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents the second parameter, i.e., the number of POs in each first PF.

[0216] When all the first PFs and the second PFs are bound (equivalent to binding the NES PFs into multiple groups according to the number of legacy PFs), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is a legacy PF, if a first PEI is associated with a plurality of groups of bound first PFs, the thirteenth PF strategy is used to determine NES firstPF.

[0217] In an implementation manner, the fourteenth PF strategy is: NES firstPF is determined through NES firstPF = (SFN for NES PF) - floor((NES_i PO N2), to determine NES firstPF. Wherein, SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents the second parameter, i.e., the number of POs in each first PF.

[0218] When all the first PFs and the second PFs are bound (equivalent to binding the NES PFs into multiple groups according to the number of legacy PFs), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is a NES PF, if a first PEI is associated with a group of bound first PFs, the fourteenth PF strategy is used to determine NES firstPF. Optionally, the associated first PF can also be a legacy PF (if the associated first PF is a legacy PF, the frame offset of the sharing mechanism can be reused to determine the position of the PEI reference frame, and optionally, the frame offset of the NES can also be used) legacy firstPF = (SFN for NES PF) - floor((NES_i PO Ns) / N2) - 1.

[0219] In an implementation manner, the fifteenth PF strategy is: NES firstPF is determined through NES firstPF = [(SFN for NES PF) - floor(NES_i PO N2)] - floor(NES_i POSFN for NES PF = SFN for target PF = SFN for legacy PF + (N2)*(T / N), and NES firstPF is determined. SFN for NES PF is the target PF determined above, and can also be understood as the NES PF actually monitored by the UE. N2 represents a second parameter, i.e., the number of POs in each first PF.

[0220] When all first PFs and second PFs are bound (equivalent to grouping the NES PFs according to the number of legacy PFs), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is the NES PF, if a first PF is associated with multiple groups of bound first PFs, according to the fifteenth PF strategy, NES firstPF is determined.

[0221] Optionally, the second target PO strategy is one of second preset PO strategies, and the second preset PO strategies include a fourth PO strategy, a fifth PO strategy, a sixth PO strategy, a seventh PO strategy, an eighth PO strategy, a ninth PO strategy, a tenth PO strategy, an eleventh PO strategy, a twelfth PO strategy, a thirteenth PO strategy, and a fourteenth PO strategy.

[0222] The fourth PO strategy is used in a case where all the first PFs are not bound to the second PF, and the type of the PF to be monitored is the first PF.

[0223] The fifth PO strategy is used in a case where all the first PFs are not bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located before the first PF.

[0224] The sixth PO strategy is used in a case where all the first PFs are not bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located after the first PF.

[0225] The seventh PO strategy is used in a case where all the first PFs are not bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located before the first PF.

[0226] The eighth PO policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened to needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located after the first PF;

[0227] The ninth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened to is the first PF, and the first PEI is associated with a group of bound first PFs;

[0228] The tenth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened to is the first PF, and the first PEI is associated with a plurality of groups of bound first PFs;

[0229] The eleventh PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened to needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with a group of bound first PFs;

[0230] The twelfth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened to needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with a plurality of groups of bound first PFs;

[0231] The thirteenth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened to needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a group of bound first PFs;

[0232] The fourteenth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened to needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a plurality of groups of bound first PFs.

[0233] Therefore, the terminal can apply one of the second preset PO policies as a second target PO policy for different cases.

[0234] In an implementation form, the fourth PO policy is: determining NES_i PO = ((UE_ID mod N_new)*N2+i_s_nes) mod NES_N PO PEI , by NES_i POHere, i_s_nes represents the identifier of the first target PO, which can also be understood as the NES PO sequence number monitored by the UE. NES_N PO PEI The number of POs associated with the first PEI.

[0235] When all first PFs are individually bound, or when the network is configured with only one NES PF (increasing the number of POs in each NES PF), if the PF that the UE is actually listening to only needs to be mapped in the NES PF, then NES_i is determined according to the fourth PO strategy. PO .

[0236] In one implementation, the fifth PO strategy is: via NES_i PO =((UE_ID mod(N_new+N))*Ns+i_s)mod NES_N PO PEI Determine NES_i PO Where i_s is the legacy PO number being monitored by the UE.

[0237] When all first PFs are individually bound, or when the network is configured with only one NES PF (increasing the number of POs in each NES PF), if the PF the UE is actually listening to needs to be mapped between the NES PF and the legacy PF, and if the UE calculates that the PF to be listened to is the legacy PF (because at this time the legacy PF is not bound to the NES PF, so the position of the first associated PF can only be determined based on the NES PF), if the legacy PF appears before the NES PF: according to the fifth PO strategy, determine NES_i. PO .

[0238] In one implementation, the sixth PO strategy is: via NES_i PO =((UE_ID mod(N_new+N))*N2+i_s)mod NES_N PO PEI Determine NES_i PO .

[0239] When all first PFs are individually bound, or the network only configures one NES PF (increasing the number of POs in each NES PF), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is the legacy PF (because the legacy PF is not bound with the NES PF at this time, so the position of the first PF associated with the NES PF can only be determined according to the NES PF), if the legacy PF appears behind the NES PF, the NES_i is determined according to the sixth PO strategy. PO .

[0240] In an embodiment, the seventh PO strategy is: NES_i PO = N PO PEI + ((UE_ID mod (N_new+N))*N2+i_s_nes) mod NES_N PO PEI , the NES_i is determined according to the seventh PO strategy. PO .

[0241] When all first PFs are individually bound, or the network only configures one NES PF (increasing the number of POs in each NES PF), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is the NES PF, if the legacy PF appears in front of the NES PF, the NES_i is determined according to the seventh PO strategy. PO .

[0242] In an embodiment, the eighth PO strategy is: NES_i PO = ((UE_ID mod (N_new+N))*N2+i_s_nes) mod NES_N PO PEI , the NES_i is determined according to the eighth PO strategy. PO .

[0243] When all first PFs are individually bound, or the network only configures one NES PF (increasing the number of POs in each NES PF), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is the NES PF, if the legacy PF appears behind the NES PF, the NES_i is determined according to the eighth PO strategy. PO .

[0244] In an embodiment, the ninth PO strategy is: NES_i PO= ((UE_ID mod N_new) * N2 + i_s_nes) mod NES_N PO PEI , determine NES_i PO .

[0245] When all the first PFs and the second PFs are bound (equivalent to grouping the NES PFs according to the number of the legacy PFs), if the PFs actually listened to by the UE only need to be mapped in the NES PFs, if one first PEI is associated with one group of bound first PFs, according to the ninth PO strategy, NES_i PO .

[0246] In an embodiment, the tenth PO strategy is: NES_i PO = ((UE_ID mod N_new) * N2 + i_s_nes) mod NES_N PO PEI , determine NES_i PO .

[0247] When all the first PFs and the second PFs are bound (equivalent to grouping the NES PFs according to the number of the legacy PFs), if the PFs actually listened to by the UE only need to be mapped in the NES PFs, if one first PEI is associated with one group of bound first PFs, according to the ninth PO strategy, NES_i PO .

[0248] In an embodiment, the eleventh PO strategy is: NES_i PO = ((UE_ID mod (N_new + N)) * Ns + i_s) mod NES_N PO PEI , determine NES_i PO .

[0249] When all the first PFs and the second PFs are bound (equivalent to grouping the NES PFs according to the number of the legacy PFs), if the PFs actually listened to by the UE need to be mapped in the NES PFs and the legacy PFs, if the UE calculates that the PFs needed to be listened to are the legacy PFs, if one first PEI is associated with one group of bound first PFs, according to the eleventh PO strategy, NES_i PO .

[0250] In an embodiment, the twelfth PO strategy is: NES_i PO= ((UE_ID mod (N_new + N)) * N2 + i_s_nes + (Ns + N2 * N_new) * (a - 1)) mod NES_N PO PEI , determine NES_i PO . Wherein, a is the sequence number of the legacy PF calculated by the UE, if the legacy PF of the UE = {SFN1, SFN6}, the UE calculates the PF to be monitored as SFN1, then a = 1, if the UE calculates the PF to be monitored as SFN2, then a = 2.

[0251] When all the first PFs and the second PFs are bound (equivalent to binding the NES PFs into groups according to the number of the legacy PFs), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates the PF to be monitored as the legacy PF, if a first PEI is associated with a group of bound first PFs, according to the twelfth PO strategy, determine NES_i PO .

[0252] In an embodiment, the thirteenth PO strategy is: determine NES_i PO = Ns + ((UE_ID mod (N_new + N)) * N2 + i_s_nes) mod NES_N PO PEI , determine NES_i PO .

[0253] When all the first PFs and the second PFs are bound (equivalent to binding the NES PFs into groups according to the number of the legacy PFs), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates the PF to be monitored as the NES PF, if a first PEI is associated with a group of bound first PFs, according to the thirteenth PO strategy, determine NES_i PO .

[0254] In an embodiment, the fourteenth PO strategy is: determine NES_i PO = ((UE_ID mod (N_new + N)) * N2 + i_s_nes + (Ns + N2 * N_new) * (a - 1)) mod NES_N PO PEI , determine NES_i PO, wherein a is a serial number of the legacy PF calculated by the UE, if the legacy PF of the UE = {SFN1, SFN6}, the UE calculates that the PF to be monitored is SFN1, a = 1, and if the UE calculates that the PF to be monitored is SFN2, a = 2.

[0255] When all the first PFs and the second PFs are bound (equivalent to binding the NES PFs into multiple groups according to the number of the legacy PFs), if the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is the NES PF, if a first PEI is associated with multiple groups of bound first PFs, according to the fourteenth PO strategy, NES_i PO .

[0256] Optionally, the method further comprises:

[0257] The terminal determines the identity of the second target PO in the first PEI based on at least one of the third target PO strategy, the identity of the terminal, the first configuration information, and the second configuration information;

[0258] The terminal acquires the position of the first PF associated with the first PEI;

[0259] The terminal determines the second target PO based on the identity of the second target PO and the position of the first PF associated with the first PEI.

[0260] In this way, after the second target PO is determined, it can be judged whether it is necessary to wake up to monitor the paging in the associated NES PF / PO position, and whether to monitor the first target PO. NES_i po represents the identity of the second target PO, and NES_firstPF represents the position of the first PF associated with the first PEI. The first PEI is extended on the basis of the traditional PEI to realize the association of the first PF. In this way, the position of the first PF associated with the first PEI can be determined according to the position of the first PF associated with the traditional PEI, for example, NES_firstPF = (SFN for PF) - floor(i PO / Ns) * T / N.

[0261] Optionally, the third target PO strategy is one of third preset PO strategies,

[0262] The third preset PO strategies include a fifteenth PO strategy, a sixteenth PO strategy, and a seventeenth PO strategy.

[0263] The fifteenth PO policy is used in the case that the type of the PF to be monitored is the first PF;

[0264] The sixteenth PO policy is used in the case that the type of the PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the second PF;

[0265] The seventeenth PO policy is used in the case that the type of the PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the first PF.

[0266] Therefore, the terminal can apply one of the third preset PF policies as the third target PF policy for different cases.

[0267] In an implementation, the fifteenth PO policy is: NES_i PO = N PO PEI + (UE_ID mod N_new) * N2 + i_s_nes) mod NES_N PO PEI is determined according to the fifteenth PO policy. PO Wherein, N PO PEI is the number of POs associated with the legacy PEI.

[0268] When the PF actually monitored by the UE needs to be mapped in the NES PF, NES_i PO is determined according to the fifteenth PO policy.

[0269] In an implementation, the sixteenth PO policy is: NES_i PO = ((UE_ID mod (N_new + N)) * Ns + i_s) mod (NES_N PO PEI + N PO PEI is determined according to the sixteenth PO policy. PO

[0270] When the PF actually monitored by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF to be monitored is the legacy PF, NES_i PO is determined according to the sixteenth PO policy.

[0271] In an implementation, the seventeenth PO policy is: NES_i PO = N PO PEI ​+ ((UE_ID mod (N_new + N) ) * N2 + i_s_nes) mod (NES_N PO PEI +N PO PEI ), determine NES_i PO .

[0272] When the PF actually listened to by the UE needs to be mapped in the NES PF and the legacy PF, if the UE calculates that the PF needed to be listened to is the NES PF, according to the seventeenth PO strategy, NES_i PO .

[0273] Optionally, the method further comprises:

[0274] The terminal sends capability information to the network side device, and the capability information is used to indicate whether the terminal supports aggregated paging.

[0275] In this way, the centralized unit CU of the network side device receives the capability information sent by the terminal, and sends the capability information to the distributed unit DU. After receiving the capability information, the DU can perform paging according to the capability information, so as to realize different processing of different UEs, such as paging the UE supporting aggregated paging in the paging position of the NES, and paging the UE (also referred to as legacy UE) not supporting aggregated paging in the legacy paging position.

[0276] In an implementation manner, the DU receives a first message of the CU, wherein the first message contains the capability information of the terminal, such as the capability information used to indicate that the terminal supports aggregated paging. Optionally, the capability information can also include the capability of supporting the aggregated paging group. Specifically, the first message can be a paging message sent by the CU to the DU.

[0277] In an implementation manner, after receiving the capability information, the DU can perform paging on the first type of terminal according to the capability information and the first configuration information.

[0278] As shown in FIG. 14, the embodiment of the present application further provides a paging processing method, comprising:

[0279] In step 1401, the network side device sends first configuration information to the terminal; wherein the first configuration information includes binding information of a first PF, and the first PF is a PF used for paging a first type of terminal, and the first type of terminal supports aggregated paging.

[0280] In this way, after receiving the first configuration information, the terminal can determine a first target PO using the first configuration information, and perform paging listening on the first target PO, so as to realize paging listening when the PF is bound.

[0281] Optionally, the method further comprises:

[0282] The network-side device determines a first target PO according to the first configuration information.

[0283] The network-side device performs paging on the first target PO.

[0284] That is, the network-side device can also determine a first target PO using the first configuration information and perform paging on the first target PO.

[0285] It should be noted that the manner in which the terminal determines the first target PO in the above embodiments is applicable to the network-side device determining the first target PO, achieving the same technical effects, which will not be described here.

[0286] Optionally, the first configuration information comprises at least one of:

[0287] a first parameter, the first parameter being used to indicate a number of the first PFs in a bundle;

[0288] a second parameter, the second parameter being used to indicate a number of POs in each of the first PFs;

[0289] a paging monitoring factor, the paging monitoring factor being used to indicate a monitoring behavior of the terminal;

[0290] a first offset, the first offset being used to indicate an offset between the first PF and a second PF;

[0291] a third parameter, the third parameter being used to indicate a number of the second PFs in a bundle of the first PF;

[0292] a second offset, the second offset being used to indicate an offset of the first PF in each of discontinuous reception (DRX) cycles;

[0293] a fourth parameter, the fourth parameter being used to indicate a total number of POs in all the first PFs;

[0294] a first position, the first position being used to indicate a position of a starting PF in a bundle of PFs;

[0295] a fifth parameter, the fifth parameter being used to indicate a first physical downlink control channel (PDCCH) monitoring occasion of each PO in a bundle of PFs;

[0296] first indication information, the first indication information being used to indicate whether the terminal can simultaneously monitor a first PF and a second PF;

[0297] The second PF is a PF used for paging a second type of terminal, and the second type of terminal does not support aggregated paging.

[0298] Optionally, the method further comprises:

[0299] The network-side device sends second configuration information to the terminal, wherein the second configuration information comprises information of a first paging early indication (PEI), and the first PEI is associated with one or more first PFs.

[0300] In this way, the terminal can determine the position of the second target PO in the first PEI after obtaining the first configuration information and the second configuration information, as described in the method of the terminal-side embodiment.

[0301] Of course, the way in which the terminal determines the position of the second target PO in the first PEI is applicable to the network-side device determining the second target PO, and achieves the same technical effect, which will not be described here again.

[0302] Optionally, the network-side device determining the second target PO can be used to generate the first PEI, establish the association between the first PEI and the PF or the PO, and indicate whether the terminal listens to the PF or the PO.

[0303] Optionally, the method further comprises:

[0304] The centralized unit (CU) of the network-side device receives the capability information sent by the terminal and sends the capability information to a distributed unit (DU), wherein the capability information is used to indicate whether the terminal supports aggregated paging.

[0305] Optionally, the network-side device performs paging on the first target PO, comprising:

[0306] The DU of the network-side device performs paging on the first target PO according to the capability information after receiving the capability information and the capability information indicating that the terminal supports aggregated paging.

[0307] In an implementation, the DU receives the first message of the CU, wherein the first message comprises the capability information of the terminal, such as the capability information used to indicate that the terminal supports aggregated paging. Optionally, the capability information can also comprise the capability of supporting the aggregated paging group. Specifically, the first message can be a paging message sent by the CU to the DU.

[0308] In an implementation, after receiving the capability information, the DU can perform paging on the first type of terminal according to the capability information and the first configuration information.

[0309] As shown in FIG. 15, the embodiment of the present application further provides a paging processing method, comprising:

[0310] In step 1501, a centralized unit CU of a network-side device receives capability information sent by a terminal, and sends the capability information to a distributed unit DU; wherein the capability information is used to indicate whether the terminal supports aggregated paging.

[0311] The DU of the network-side device receives the capability information, and performs paging according to the capability information.

[0312] In this way, the centralized unit CU of the network-side device receives the capability information sent by the terminal, and sends the capability information to the distributed unit DU. After the DU receives the capability information, the DU can perform paging according to the capability information, so as to realize different processing of different terminals, such as paging a terminal supporting aggregated paging in a paging location of NES, and paging a terminal not supporting aggregated paging (also referred to as a legacy UE) in a legacy paging location.

[0313] In an implementation form, the DU receives a first message of the CU, wherein the first message contains the capability information of the terminal, such as the capability information used to indicate that the terminal supports aggregated paging. Optionally, the capability information can also include the capability of supporting an aggregated paging group. Specifically, the first message can be a paging message sent by the CU to the DU.

[0314] In an implementation form, after the DU receives the capability information, the DU can perform paging on a first type of terminal according to the capability information and first configuration information.

[0315] The execution subject of the paging monitoring method provided in the embodiments of the present application can be a paging monitoring apparatus. In the embodiments of the present application, the paging monitoring apparatus is taken as an example to illustrate the paging monitoring method provided in the embodiments of the present application.

[0316] The execution subject of the paging processing method provided in the embodiments of the present application can be a paging processing apparatus. In the embodiments of the present application, the paging processing apparatus is taken as an example to illustrate the paging processing method provided in the embodiments of the present application.

[0317] The embodiments of the present application provide a paging monitoring apparatus or a paging processing apparatus. As an example, the paging monitoring apparatus or the paging processing apparatus can be a communication device or a component in a communication device, such as a chip. The communication device can be a terminal, a network-side device, a server, or the like. For example, the terminal can include, but is not limited to, the types of the terminal 11 listed above, the network-side device can include, but is not limited to, the types of the network-side device 12 listed above, and the embodiments of the present application are not limited in this regard.

[0318] The paging monitoring device or the paging processing device comprises a receiving module, a sending module and a processing module. The receiving module, the sending module and the processing module can be implemented by software or by hardware. When implemented by hardware, the processing module can be implemented by a processor, which can include a general-purpose processor, a special-purpose processor, etc., such as a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), an artificial intelligent (AI) processor, a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a network processor (NP), a field programmable gate array (FPGA) or other programmable logic devices, a gate circuit, a transistor, a discrete hardware component, etc. The receiving module and the sending module can be implemented by a communication interface, which can include one or more of a transceiver, a pin, a circuit, a bus, a radio frequency unit, etc.

[0319] Specifically, referring to FIG. 16, when the paging monitoring device is a terminal or a component in the terminal, the paging monitoring device 1600 comprises:

[0320] A first processing module 1610 is configured to acquire first configuration information, wherein the first configuration information comprises binding information of a first paging frame (PF), and the first PF is a PF used for paging a first type of terminal, and the first type of terminal supports aggregated paging.

[0321] A second processing module 1620 is configured to determine a first target paging occasion (PO) according to the first configuration information.

[0322] A third processing module 1630 is configured to perform paging monitoring at the first target PO.

[0323] Optionally, the first configuration information comprises at least one of the following:

[0324] A first parameter, wherein the first parameter is used to indicate a number of the first PFs that are bound;

[0325] A second parameter, wherein the second parameter is used to indicate a number of POs in each of the first PFs;

[0326] A paging monitoring factor, wherein the paging monitoring factor is used to indicate a monitoring behavior of the terminal;

[0327] a first offset, used to indicate an offset between the first PF and a second PF;

[0328] a third parameter, used to indicate a number of the second PFs bound by the first PF;

[0329] a second offset, used to indicate an offset of the first PF per discontinuous reception (DRX) cycle;

[0330] a fourth parameter, used to indicate a total number of POs in all the first PFs;

[0331] a first position, used to indicate a position of a starting PF in a bound PF;

[0332] a fifth parameter, used to indicate a first physical downlink control channel (PDCCH) monitoring occasion of each PO in a bound PF;

[0333] first indication information, used to indicate whether the terminal can simultaneously monitor a first PF and a second PF;

[0334] wherein the second PF is a PF used for paging a second type of terminal, and the second type of terminal does not support aggregated paging.

[0335] Optionally, the apparatus further includes:

[0336] a fourth processing module, configured to acquire a position and configuration of a second PF;

[0337] The second processing module 1620 is further configured to:

[0338] determine a target PF based on at least one of a first target PF policy, the first configuration information, an identifier of the terminal, a position of the second PF, and a configuration of the second PF;

[0339] determine the first target PO in the target PF based on at least one of a first target PO policy, the first configuration information, the identifier of the terminal, and the configuration of the second PF.

[0340] Optionally, the second processing module 1620 is further configured to:

[0341] determine a serial number of the first target PO based on the first configuration information and the identifier of the terminal;

[0342] determine a position of the first target PO based on a position of a PO of the second PF and the serial number of the first target PO, in a case where the first PF is bound with a second PF;

[0343] In a case that the first PF is not bound with a second PF, a location of the first target PO is determined based on a location of the first PF and a sequence number of the first target PO.

[0344] Optionally, the apparatus further comprises:

[0345] a fifth processing module, configured to acquire second configuration information; wherein the second configuration information comprises information of a first paging early indication (PEI); and the first PEI is associated with one or more first PFs.

[0346] Optionally, the second configuration information comprises at least one of the following:

[0347] a sixth parameter, used to indicate a number of POs associated with the first PEI;

[0348] a first load, used to indicate a load of a downlink control information (DCI) of the first PEI;

[0349] a third offset, used to indicate an offset between a first PF associated with the first PEI and a reference frame;

[0350] a fourth offset, used to indicate an offset between a reference frame of the first PEI and a first PDCCH monitoring occasion.

[0351] Optionally, the apparatus further comprises:

[0352] a sixth processing module, configured to determine an identity of a second target PO in the first PEI according to at least one of a second target PO policy, an identity of the terminal, the first configuration information and the second configuration information;

[0353] a seventh processing module, configured to determine a location of a first first PF associated with the first PEI according to at least one of a second target PF policy, the identity of the second target PO, the first configuration information and the second configuration information;

[0354] an eighth processing module, configured to determine the second target PO according to the identity of the second target PO and the location of the first first PF associated with the first PEI.

[0355] Optionally, the apparatus further comprises:

[0356] a ninth processing module, configured to determine an identity of a second target PO in the first PEI according to at least one of a third target PO policy, an identity of the terminal, the first configuration information and the second configuration information;

[0357] The tenth processing module is configured to acquire a location of a first PF associated with the first PEI.

[0358] The eleventh processing module is configured to determine the second target PO based on the identification of the second target PO and the location of the first PF associated with the first PEI.

[0359] It should be noted that the apparatus is an apparatus to which the paging monitoring method is applied, and the implementation manners of the method embodiments are applicable to the apparatus, and the same technical effects can also be achieved.

[0360] The apparatus provided by the embodiments of the present application can implement each process implemented by the method embodiments of FIG. 3 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0361] As shown in FIG. 17, when the paging processing apparatus is a network side device or a component in the network side device, the paging processing apparatus 1700 includes:

[0362] The first sending module 1710 is configured to send first configuration information to a terminal, wherein the first configuration information includes binding information of a first PF, and the first PF is a PF used for paging a first type of terminal, and the first type of terminal supports aggregated paging.

[0363] Optionally, the apparatus further includes:

[0364] The second sending module is configured to send second configuration information to a terminal, wherein the second configuration information includes information of a first paging early indication PEI; and the first PEI is associated with one or more first PFs.

[0365] It should be noted that the apparatus is an apparatus to which the paging processing method is applied, and the implementation manners of the method embodiments are applicable to the apparatus, and the same technical effects can also be achieved.

[0366] The apparatus provided by the embodiments of the present application can implement each process implemented by the method embodiments of FIG. 14 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0367] As shown in FIG. 18, when the paging processing apparatus is a network side device or a component in the network side device, the paging processing apparatus 1800 includes:

[0368] The capability information transceiving module 1810 is configured to receive capability information sent by a terminal and send the capability information to a distribution unit DU, wherein the capability information is used to indicate whether the terminal supports aggregated paging;

[0369] The twelfth processing module 1820 is configured to receive the capability information and perform paging according to the capability information.

[0370] It should be noted that the device is a device applying the paging processing method, and the implementation manners of the method embodiments are applicable to the device, and the same technical effects can also be achieved.

[0371] The device provided by the embodiments of the present application can implement each process implemented by the method embodiments of FIG. 15, and achieve the same technical effects. To avoid repetition, details are not described herein.

[0372] As shown in FIG. 19, the embodiments of the present application further provide a communication device 1900, which includes a processor 1901 and a memory 1902, and the memory 1902 stores programs or instructions executable on the processor 1901. For example, when the communication device 1900 is a terminal, the programs or instructions are executed by the processor 1901 to implement each step of the paging monitoring method embodiments described above, and the same technical effects can be achieved. When the communication device 1900 is a network side device, the programs or instructions are executed by the processor 1901 to implement each step of the paging processing method embodiments described above, and the same technical effects can be achieved. To avoid repetition, details are not described herein.

[0373] The embodiments of the present application further provide a terminal, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run programs or instructions to implement the steps in the method embodiments shown in FIG. 3. The terminal embodiments correspond to the terminal side method embodiments described above, and each implementation process and implementation manner of the method embodiments can be applicable to the terminal embodiments, and the same technical effects can be achieved. The terminal can be the paging monitoring device shown in FIG. 16. Specifically, FIG. 20 is a schematic diagram of a hardware structure of a terminal for implementing the embodiments of the present application.

[0374] The terminal 2000 includes, but is not limited to, at least part of components such as a radio frequency unit 2001, a network module 2002, an audio output unit 2003, an input unit 2004, a sensor 2005, a display unit 2006, a user input unit 2007, an interface unit 2008, a memory 2009, and a processor 2010.

[0375] Those skilled in the art can understand that the terminal 2000 can further include a power supply (such as a battery) for supplying power to each component, and the power supply can be logically connected to the processor 2010 through a power management system, so as to realize functions such as power management, discharge management, and power consumption management through the power management system. The terminal structure shown in FIG. 20 does not constitute a limitation on the terminal, and the terminal can include more or fewer components than those shown, or combine certain components, or different component arrangements, which are not described herein.

[0376] It should be understood that in the embodiments of the present application, the input unit 2004 can include a graphics processor 20041 and a microphone 20042, and the graphics processor 20041 processes image data of a still picture or a video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 2006 can include a display panel 20061, which can be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 2007 includes at least one of a touch panel 20071 and other input devices 20072. The touch panel 20071 is also called a touch screen. The touch panel 20071 can include two parts of a touch detection device and a touch controller. The other input devices 20072 can include, but are not limited to, a physical keyboard, function keys (such as volume control keys, on-off keys, etc.), a trackball, a mouse, a joystick, and the like, which will not be described here.

[0377] In the embodiments of the present application, after the radio frequency unit 2001 receives the downlink data from the network side device, it can be transmitted to the processor 2010 for processing. In addition, the radio frequency unit 2001 can send uplink data to the network side device. Generally, the radio frequency unit 2001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0378] The memory 2009 can be used to store software programs or instructions and various data. The memory 2009 can mainly include a first storage area storing programs or instructions and a second storage area storing data, wherein the first storage area can store an operating system, application programs or instructions required by at least one function (such as a sound playing function, an image playing function, etc.), and the like. In addition, the memory 2009 can include a volatile memory or a non-volatile memory. The non-volatile memory can be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically EPROM (EEPROM), or a flash memory. The volatile memory can be a Random Access Memory (RAM), a Static RAM (SRAM), a Dynamic RAM (DRAM), a Synchronous DRAM (SDRAM), a Double Data Rate SDRAM (DDR SDRAM), an Enhanced SDRAM (ESDRAM), a Synch link DRAM (SLDRAM), and a Direct Rambus RAM (DRRAM). The memory 2009 in the embodiments of the present application includes but is not limited to these and any other suitable types of memory.

[0379] The processor 2010 can include one or more processing units; optionally, the processor 2010 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 can be understood that the above-mentioned modem processor can also not be integrated into the processor 2010.

[0380] The processor 2010 is configured to obtain first configuration information; wherein the first configuration information includes binding information of a first paging frame PF, and the first PF is a PF used for paging a first type of terminal, and the first type of terminal supports aggregated paging.

[0381] The processor 2010 is configured to determine a first target paging occasion PO according to the first configuration information.

[0382] The processor 2010 is configured to perform paging monitoring at the first target PO.

[0383] Optionally, the first configuration information comprises at least one of:

[0384] a first parameter, the first parameter being used for indicating a number of the first PFs in a bundle;

[0385] a second parameter, the second parameter being used for indicating a number of POs in each of the first PFs;

[0386] a paging monitoring factor, the paging monitoring factor being used for indicating a monitoring behavior of the terminal;

[0387] a first offset, the first offset being used for indicating an offset between the first PF and a second PF;

[0388] a third parameter, the third parameter being used for indicating a number of the second PFs in the first PF bundle;

[0389] a second offset, the second offset being used for indicating an offset of the first PF in each discontinuous reception (DRX) cycle;

[0390] a fourth parameter, the fourth parameter being used for indicating a total number of POs in all the first PFs;

[0391] a first position, the first position being used for indicating a position of a starting PF in a PF bundle;

[0392] a fifth parameter, the fifth parameter being used for indicating a first physical downlink control channel (PDCCH) monitoring occasion of each PO in a PF bundle;

[0393] a first indication information, the first indication information being used for indicating whether the terminal can simultaneously monitor a first PF and a second PF;

[0394] wherein the second PF is a PF used for paging a second type of terminal, and the second type of terminal does not support aggregated paging.

[0395] Optionally, before the terminal determines the first target paging occasion PO according to the first configuration information, the method further comprises:

[0396] the terminal acquires a position and configuration of the second PF;

[0397] the terminal determines the first target paging occasion PO according to the first configuration information, comprising:

[0398] the terminal determines a target PF based on at least one of a first target PF strategy, the first configuration information, an identity of the terminal, the position of the second PF, and the configuration of the second PF;

[0399] The terminal determines the first target PO in the target PF based on at least one of the first target PF policy, the first configuration information, an identifier of the terminal, and a configuration of the second PF.

[0400] Optionally, the first target PF policy is one of first preset PF policies, and the first preset PF policies include a first PF policy, a second PF policy, a third PF policy, and a fourth PF policy.

[0401] The first PF policy is used in a case where the first PF is bound with the second PF.

[0402] The second PF policy is used in a case where the first PF is bound with the second PF and the first PF and the second PF overlap.

[0403] The third PF policy is used in a case where the first PF is bound with the second PF and there is an interval between the first PF and the second PF.

[0404] The fourth PF policy is used in a case where the first PF is bound.

[0405] Optionally, the first target PO policy is one of first preset PO policies, and the first preset PO policies include a first PO policy, a second PO policy, and a third PO policy.

[0406] The first PO policy is used in a case where a type of a PF to be monitored is the first PF.

[0407] The second PO policy is used in a case where a type of a PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the second PF.

[0408] The third PO policy is used in a case where a type of a PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the first PF.

[0409] Optionally, the terminal acquires a position of the second PF, including:

[0410] In a case where the first PF is bound with part of the second PF, the terminal determines the position of the second PF bound with the first PF based on a number of the second PF bound with the first PF.

[0411] Optionally, the terminal determines a first target paging occasion (PO) according to the first configuration information, including:

[0412] The terminal determines a sequence number of the first target PO based on the first configuration information and an identifier of the terminal.

[0413] In a case that the first PF is bound with a second PF, the terminal determines a position of the first target PO based on a position of a PO of the second PF and a sequence number of the first target PO.

[0414] In a case that the first PF is not bound with a second PF, the terminal determines the position of the first target PO based on a position of the first PF and the sequence number of the first target PO.

[0415] Optionally, the method further comprises:

[0416] The terminal acquires second configuration information, wherein the second configuration information comprises information of a first paging early indication (PEI); and the first PEI is associated with one or more first PFs.

[0417] Optionally, the second configuration information comprises at least one of the following:

[0418] A sixth parameter, used to indicate a number of POs associated with the first PEI;

[0419] A first load, used to indicate a load of a downlink control information (DCI) of the first PEI;

[0420] A third offset, used to indicate an offset between a first PF associated with the first PEI and a reference frame;

[0421] A fourth offset, used to indicate an offset between a reference frame of the first PEI and a first PDCCH monitoring occasion.

[0422] Optionally, the method further comprises:

[0423] The terminal determines an identity of a second target PO in the first PEI according to at least one of a second target PO policy, an identity of the terminal, the first configuration information and the second configuration information;

[0424] The terminal determines a position of a first first PF associated with the first PEI according to at least one of a second target PF policy, the identity of the second target PO, the first configuration information and the second configuration information;

[0425] The terminal determines the second target PO according to the identity of the second target PO and the position of the first first PF associated with the first PEI.

[0426] Optionally, the second target PF policy is one of second preset PF policies, and the second preset PF policies include a fifth PF policy, a sixth PF policy, a seventh PF policy, an eighth PF policy, a ninth PF policy, a tenth PF policy, an eleventh PF policy, a twelfth PF policy, a thirteenth PF policy, a fourteenth PF policy and a fifteenth PF policy.

[0427] The fifth PF policy is used in a case that all the first PFs are not bound to the second PF, and a type of a PF being listened to is the first PF.

[0428] The sixth PF policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF being listened to needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located before the first PF.

[0429] The seventh PF policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF being listened to needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located after the first PF.

[0430] The eighth PF policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF being listened to needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located before the first PF.

[0431] The ninth PF policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF being listened to needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located after the first PF.

[0432] The tenth PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF being listened to is the first PF, and the first PEI is associated with a group of bound first PFs.

[0433] The eleventh PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF being listened to is the first PF, and the first PEI is associated with a plurality of groups of bound first PFs.

[0434] The twelfth PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with a group of the first PFs bound;

[0435] The thirteenth PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with multiple groups of the first PFs bound;

[0436] The fourteenth PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a group of the first PFs bound;

[0437] The fifteenth PF policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with multiple groups of the first PFs bound.

[0438] Optionally, the second target PO policy is one of second preset PO policies, and the second preset PO policies include a fourth PO policy, a fifth PO policy, a sixth PO policy, a seventh PO policy, an eighth PO policy, a ninth PO policy, a tenth PO policy, an eleventh PO policy, a twelfth PO policy, a thirteenth PO policy, and a fourteenth PO policy.

[0439] The fourth PO policy is used in a case that all the first PFs are not bound to the second PF, and the type of the PF to be monitored is the first PF;

[0440] The fifth PO policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located before the first PF;

[0441] The sixth PO policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located after the first PF;

[0442] The seventh PO policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located before the first PF;

[0443] The eighth PO policy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located after the first PF;

[0444] The ninth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened is the first PF, and the first PEI is associated with a group of bound first PFs;

[0445] The tenth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened is the first PF, and the first PEI is associated with multiple groups of bound first PFs;

[0446] The eleventh PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with a group of bound first PFs;

[0447] The twelfth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with multiple groups of bound first PFs;

[0448] The thirteenth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a group of bound first PFs;

[0449] The fourteenth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with multiple groups of bound first PFs.

[0450] Optionally, the method further comprises:

[0451] The terminal determines the identity of the second target PO in the first PEI based on at least one of the third target PO policy, the identity of the terminal, the first configuration information, and the second configuration information.

[0452] The terminal acquires the location of the first PF associated with the first PEI.

[0453] The terminal determines the second target PO based on the identity of the second target PO and the location of the first PF associated with the first PEI.

[0454] Optionally, the third target PO policy is one of third preset PO policies,

[0455] The third preset PO policies include a fifteenth PO policy, a sixteenth PO policy, and a seventeenth PO policy.

[0456] The fifteenth PO policy is used in a case where the type of the PF for listening is the first PF.

[0457] The sixteenth PO policy is used in a case where the type of the PF for listening needs to be determined from the first PF and the second PF, and the target PF is the second PF.

[0458] The seventeenth PO policy is used in a case where the type of the PF for listening needs to be determined from the first PF and the second PF, and the target PF is the first PF.

[0459] Optionally, the first PEI is associated with a group of bound first PFs, or the first PEI is associated with multiple groups of bound first PFs.

[0460] Optionally, the method further includes:

[0461] The terminal sends capability information to the network side device, and the capability information is used to indicate whether the terminal supports aggregated paging.

[0462] The terminal first acquires the first configuration information to learn the binding information of the first PF, then determines the object of paging listening, i.e., the first target PO, using the first configuration information, and finally performs paging listening on the first target PO to realize paging listening when the PF is bound.

[0463] It can be understood that the implementation processes of the implementation manners mentioned in the embodiment can refer to the related descriptions of the terminal side method embodiments and achieve the same or corresponding technical effects. To avoid repetition, they will not be described here.

[0464] The embodiment of the present application further provides a network side device, comprising a processor and a communication interface, the communication interface is coupled with the processor, and the processor is used to run programs or instructions to realize the steps of the method embodiment shown in FIG. 14 or 15. The network side device embodiment corresponds to the network side device method embodiment described above, and each implementation process and implementation manner of the method embodiment described above can be applied to the network side device embodiment and can achieve the same technical effects.

[0465] Specifically, the embodiment of the present application further provides a network side device, which can be the paging processing apparatus shown in FIG. 17 or 18. As shown in FIG. 21, the network side device 2100 comprises an antenna 211, a radio frequency device 212, a baseband device 213, a processor 214 and a memory 215. The antenna 211 is connected with the radio frequency device 212. In the uplink direction, the radio frequency device 212 receives information through the antenna 211 and sends the received information to the baseband device 213 for processing. In the downlink direction, the baseband device 213 processes the information to be sent and sends it to the radio frequency device 212, and the radio frequency device 212 processes the received information and sends it out through the antenna 211.

[0466] The method performed by the network side device in the above embodiment can be implemented in the baseband device 213, which comprises a baseband processor.

[0467] The baseband device 213 may, for example, comprise at least one baseband board, and a plurality of chips are arranged on the baseband board, as shown in FIG. 21. One of the chips is, for example, a baseband processor, which is connected with the memory 215 through a bus interface to call the programs in the memory 215 and perform the network device operations shown in the above method embodiment.

[0468] The network side device may, for example, further comprise a network interface 216, which is, for example, a Common Public Radio Interface (CPRI).

[0469] Specifically, the network side device 2100 of the embodiment of the present application further comprises instructions or programs stored in the memory 215 and executable on the processor 214, the processor 214 calls the instructions or programs in the memory 215 to perform the method performed by each module shown in FIG. 17 or 18 and achieve the same technical effects. To avoid repetition, details are not described herein.

[0470] The embodiment of the present application further provides a readable storage medium, which stores programs or instructions, the programs or instructions are executed by a processor to realize each process of the paging monitoring method embodiment described above, or each process of the paging processing method embodiment described above, and can achieve the same technical effects. To avoid repetition, details are not described herein.

[0471] The processor is the processor in the terminal in the above embodiments. The readable storage medium includes a computer readable storage medium, such as a computer readable only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc. In some examples, the readable storage medium can be a non-transitory readable storage medium.

[0472] The embodiment of the present application further provides a chip, which comprises a processor and a communication interface, the communication interface is coupled with the processor, the processor is used for running programs or instructions to realize the processes of the above-mentioned paging monitoring method embodiments or the processes of the above-mentioned paging processing method embodiments, and the same technical effects can be achieved. To avoid repetition, details are not described here.

[0473] It should be understood that the chip mentioned in the embodiment of the present application can also be referred to as a system chip, a system chip, a chip system or a system on chip, etc.

[0474] The embodiment of the present application further provides a computer program / program product stored in a storage medium, which is executed by at least one processor to realize the processes of the above-mentioned paging monitoring method embodiments or the processes of the above-mentioned paging processing method embodiments, and the same technical effects can be achieved. To avoid repetition, details are not described here.

[0475] The embodiment of the present application further provides a wireless communication system, which comprises a terminal and a network side device, the terminal can be used to execute the steps of the paging monitoring method as described above, and the network side device can be used to execute the steps of the paging processing method as described above.

[0476] It should be noted that in this document, the terms "comprising", "including" or any other variant thereof are intended to cover non-exclusive inclusion, so that processes, methods, articles or devices including a series of elements not only include those elements, but also include other elements not explicitly listed or inherent to such processes, methods, articles or devices. Without more limitations, the element defined by the statement "including a" does not exclude the presence of additional identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to the order of performing the functions shown or discussed, but can also include performing the functions in a substantially simultaneous manner or in a reverse order, for example, the described method can be performed in an order different from the described order, and various steps can be added, omitted or combined. In addition, the features described with reference to some examples can be combined in other examples.

[0477] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned example methods can be realized by means of a computer software product and a general hardware platform as necessary, and of course can also be realized by hardware. The computer software product is stored in a storage medium (such as a ROM, a RAM, a magnetic disc, an optical disc, etc.), and includes a plurality of instructions for enabling a terminal or a network side device to execute the method described in each embodiment of the present application.

[0478] The embodiments of the present application are described above in combination with the drawings, but the present application is not limited to the specific embodiments described above, and the specific embodiments described above are merely illustrative rather than limiting. Those skilled in the art can make many forms of embodiments under the inspiration of the present application without departing from the scope of the present application and the scope protected by the claims, and these embodiments all belong to the protection of the present application.

Claims

1. A paging monitoring method, comprising: obtaining, by a terminal, first configuration information, wherein the first configuration information comprises binding information of first paging frames (PFs), the first PFs being PFs for paging first-type terminals, and the first-type terminals supporting aggregated paging; determining, by the terminal, a first target paging occasion (PO) according to the first configuration information; performing, by the terminal, paging monitoring at the first target PO.

2. The method of claim 1, wherein, The first configuration information comprises at least one of the following: a first parameter, used to indicate a number of the first PFs in a binding; a second parameter, used to indicate a number of POs in each of the first PFs; a paging monitoring factor, used to indicate a monitoring behavior of the terminal; a first offset, used to indicate an offset between the first PFs and second PFs; a third parameter, used to indicate a number of the second PFs in the binding of the first PFs; a second offset, used to indicate an offset of the first PFs in each of discontinuous reception (DRX) cycles; a fourth parameter, used to indicate a total number of POs in all the first PFs; a first position, used to indicate a position of a starting PF in the binding of PFs; a fifth parameter, used to indicate a first physical downlink control channel (PDCCH) monitoring occasion of each PO in the binding of PFs; first indication information, used to indicate whether the terminal can simultaneously monitor the first PFs and the second PFs; wherein the second PFs are PFs for paging second-type terminals, and the second-type terminals do not support aggregated paging.

3. The method of claim 1 or 2, wherein, Before the determining, by the terminal, the first target PO according to the first configuration information, the method further comprises: obtaining, by the terminal, a position and configuration of the second PFs; The determining, by the terminal, the first target PO according to the first configuration information comprises: determining, by the terminal, a target PF based on at least one of a first target PF strategy, the first configuration information, an identity of the terminal, the position of the second PFs, and the configuration of the second PFs; determining, by the terminal, the first target PO in the target PF based on at least one of a first target PO strategy, the first configuration information, the identity of the terminal, and the configuration of the second PFs.

4. The method of claim 3, wherein, The first target PF strategy is one of first preset PF strategies, and the first preset PF strategies comprise a first PF strategy, a second PF strategy, a third PF strategy, and a fourth PF strategy; wherein the first PF strategy is used in a case where the first PFs are bound with the second PFs; the second PF strategy is used in a case where the first PFs are bound with the second PFs and overlap; the third PF strategy is used in a case where the first PFs are bound with the second PFs and there is an interval; the fourth PF strategy is used in a case where the first PFs are bound.

5. The method of claim 3, wherein, The first target PO strategy is one of first preset PO strategies, and the first preset PO strategies comprise a first PO strategy, a second PO strategy, and a third PO strategy. The first PO policy is used for the type of PF for listening in the case of the first PF; The type of PF for listening needs to be determined in the first PF and the second PF in the case of the second PF as the target PF; The type of PF for listening needs to be determined in the first PF and the second PF in the case of the first PF as the target PF.

6. The method according to any one of claims 3 to 5, wherein, The terminal acquires the position of the second PF, comprising: In the case of the first PF binding part of the second PF, the terminal determines the position of the second PF bound by the first PF based on the number of the second PF bound by the first PF.

7. The method of claim 1 or 2, wherein, The terminal determines the first target paging occasion PO according to the first configuration information, comprising: The terminal determines the serial number of the first target PO based on the first configuration information and the identifier of the terminal; In the case of the first PF binding with the second PF, the terminal determines the position of the first target PO based on the position of the PO of the second PF and the serial number of the first target PO; In the case of the first PF not binding with the second PF, the terminal determines the position of the first target PO based on the position of the first PF and the serial number of the first target PO.

8. The method of claim 1 or 2, further comprising: The terminal acquires second configuration information; wherein the second configuration information includes information of a first paging early indication PEI; the first PEI is associated with one or more first PFs.

9. The method of claim 8, wherein, The second configuration information includes at least one of the following: A sixth parameter, the sixth parameter is used to indicate the number of POs associated with the first PEI; A first load, the first load is used to indicate the load of the first PEI downlink control information DCI; A third offset, the third offset is used to indicate the offset between the first PF associated with the first PEI and the reference frame; A fourth offset, the fourth offset is used to indicate the offset between the reference frame of the first PEI and the first PDCCH listening occasion.

10. The method of claim 8 or 9, further comprising: The terminal determines the identifier of the second target PO in the first PEI according to at least one of the second target PO policy, the identifier of the terminal, the first configuration information and the second configuration information; The terminal determines the position of the first first PF associated with the first PEI according to at least one of the second target PO policy, the identifier of the second target PO, the first configuration information and the second configuration information; The terminal determines the second target PO according to the identifier of the second target PO and the position of the first first PF associated with the first PEI.

11. The method of claim 10, wherein, The second target PF policy is one of second preset PF policies, and the second preset PF policies include a fifth PF policy, a sixth PF policy, a seventh PF policy, an eighth PF policy, a ninth PF policy, a tenth PF policy, an eleventh PF policy, a twelfth PF policy, a thirteenth PF policy, a fourteenth PF policy and a fifteenth PF policy; The fifth PF policy is used in a case that all the first PFs are not bound with the second PF, and the type of the PF listened to is the first PF; The sixth PF policy is used in a case that all the first PFs are not bound with the second PF, the type of the PF listened to needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound with the first PF is located before the first PF; The seventh PF policy is used in a case that all the first PFs are not bound with the second PF, the type of the PF listened to needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound with the first PF is located after the first PF; The eighth PF policy is used in a case that all the first PFs are not bound with the second PF, the type of the PF listened to needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound with the first PF is located before the first PF; The ninth PF policy is used in a case that all the first PFs are not bound with the second PF, the type of the PF listened to needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound with the first PF is located after the first PF; The tenth PF policy is used in a case that all the first PFs are bound with the second PF, the type of the PF listened to is the first PF, and the first PEI is associated with a group of bound first PFs; The eleventh PF policy is used in a case that all the first PFs are bound with the second PF, the type of the PF listened to is the first PF, and the first PEI is associated with multiple groups of bound first PFs; The twelfth PF policy is used in a case that all the first PFs are bound with the second PF, the type of the PF listened to needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with a group of bound first PFs; The thirteenth PF policy is used in a case that all the first PFs are bound with the second PF, the type of the PF listened to needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with multiple groups of bound first PFs; The fourteenth PF strategy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a group of the first PFs bound; The fifteenth PF strategy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a plurality of groups of the first PFs bound.

12. The method of claim 10 or 11, wherein, The second target PO strategy is one of second preset PO strategies, and the second preset PO strategies include a fourth PO strategy, a fifth PO strategy, a sixth PO strategy, a seventh PO strategy, an eighth PO strategy, a ninth PO strategy, a tenth PO strategy, an eleventh PO strategy, a twelfth PO strategy, a thirteenth PO strategy and a fourteenth PO strategy; The fourth PO strategy is used in a case that all the first PFs are not bound to the second PF, and the type of the PF to be listened is the first PF; The fifth PO strategy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located before the first PF; The sixth PO strategy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the second PF, and the second PF bound to the first PF is located after the first PF; The seventh PO strategy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located before the first PF; The eighth PO strategy is used in a case that all the first PFs are not bound to the second PF, the type of the PF to be listened needs to be determined in the first PF and the second PF, the target PF is the first PF, and the second PF bound to the first PF is located after the first PF; The ninth PO strategy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened is the first PF, and the first PEI is associated with a group of the first PFs bound; The tenth PO strategy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be listened is the first PF, and the first PEI is associated with a plurality of groups of the first PFs bound; The eleventh PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with a group of the first PFs bound; The twelfth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the second PF, and the first PEI is associated with a plurality of groups of the first PFs bound; The thirteenth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a group of the first PFs bound; The fourteenth PO policy is used in a case that all the first PFs are bound to the second PF, the type of the PF to be monitored needs to be determined in the first PF and the second PF, the target PF is the first PF, and the first PEI is associated with a plurality of groups of the first PFs bound.

13. The method of claim 8 or 9, further comprising: determining, by the terminal, an identity of a second target PO in the first PEI based on at least one of a third target PO policy, an identity of the terminal, the first configuration information, and the second configuration information; obtaining, by the terminal, a location of a first PF associated with the first PEI; determining, by the terminal, the second target PO based on the identity of the second target PO and the location of the first PF associated with the first PEI.

14. The method of claim 13, wherein, The third target PO policy is one of third preset PO policies, The third preset PO policies include a fifteenth PO policy, a sixteenth PO policy, and a seventeenth PO policy. The fifteenth PO policy is used in a case that the type of the PF to be monitored is the first PF. The sixteenth PO policy is used in a case that the type of the PF to be monitored needs to be determined in the first PF and a second PF, and the target PF is the second PF. The seventeenth PO policy is used in a case that the type of the PF to be monitored needs to be determined in the first PF and the second PF, and the target PF is the first PF.

15. The method according to any one of claims 8 to 14, wherein, The first PEI is associated with a group of the first PFs bound, or the first PEI is associated with a plurality of groups of the first PFs bound.

16. The method of any one of claims 1-15, further comprising: sending, by the terminal, capability information to a network side device, the capability information being used to indicate whether the terminal supports aggregated paging.

17. A paging processing method, comprising: sending, by a network side device, first configuration information to a terminal; wherein the first configuration information comprises binding information of a first PF, the first PF being a PF used for paging a first type of terminal, and the first type of terminal supporting aggregated paging.

18. The method of claim 1, further comprising: The network-side device determines a first target PO according to the first configuration information. The network-side device performs paging on the first target PO.

19. The method of claim 17 or 18, wherein, The first configuration information comprises at least one of: a first parameter, used for indicating a number of the first PFs in a bundle; a second parameter, used for indicating a number of POs in each of the first PFs; a paging monitoring factor, used for indicating a monitoring behavior of the terminal; a first offset, used for indicating an offset between the first PF and a second PF; a third parameter, used for indicating a number of the second PFs in a bundle of the first PF; a second offset, used for indicating an offset of the first PF in each discontinuous reception (DRX) cycle; a fourth parameter, used for indicating a total number of POs in all the first PFs; a first position, used for indicating a position of a starting PF in a bundle of PFs; a fifth parameter, used for indicating a first physical downlink control channel (PDCCH) monitoring occasion of each PO in a bundle of PFs; first indication information, used for indicating whether the terminal can monitor a first PF and a second PF simultaneously; and The second PF is a PF used for paging a second type of terminal, and the second type of terminal does not support aggregated paging.

20. The method of any one of claims 17 to 19, further comprising: The network-side device sends second configuration information to the terminal; wherein the second configuration information comprises information of a first paging early indication (PEI); and the first PEI is associated with one or more of the first PFs.

21. The method of any one of claims 17 to 20, further comprising: A centralized unit (CU) of the network-side device receives capability information sent by the terminal, and sends the capability information to a distributed unit (DU); wherein the capability information is used to indicate whether the terminal supports aggregated paging.

22. The method of claim 21, wherein, The network-side device performs paging on the first target PO, comprising: The DU of the network-side device performs paging on the first target PO according to the capability information after receiving the capability information and the capability information indicating that the terminal supports aggregated paging.

23. A paging processing method, comprising: A centralized unit (CU) of a network-side device receives capability information sent by a terminal, and sends the capability information to a distributed unit (DU); wherein the capability information is used to indicate whether the terminal supports aggregated paging; The DU of the network-side device receives the capability information, and performs paging according to the capability information.

24. A paging monitoring apparatus, comprising: A first processing module, configured to acquire first configuration information; wherein the first configuration information comprises bundle information of first paging frames (PFs), and a first PF is a PF used for paging a first type of terminal, and the first type of terminal supports aggregated paging; A second processing module, configured to determine a first target paging occasion (PO) according to the first configuration information; A third processing module, configured to perform paging monitoring on the first target PO.

25. The apparatus of claim 24, wherein, The first configuration information comprises at least one of: a first parameter, used for indicating a number of the first PFs in a bundle; a second parameter, used for indicating a number of POs in each of the first PFs; a paging monitoring factor, used for indicating a monitoring behavior of the terminal; a first offset, used for indicating an offset between the first PF and a second PF; a third parameter, used for indicating a number of the second PFs in a bundle of the first PF; a second offset, used for indicating an offset of the first PF in each discontinuous reception (DRX) cycle; a fourth parameter, used for indicating a total number of POs in all the first PFs; a first position, used for indicating a position of a starting PF in a PF bundle; a fifth parameter, used for indicating a first physical downlink control channel (PDCCH) monitoring occasion of each PO in a PF bundle; first indication information, used for indicating whether the terminal can simultaneously monitor a first PF and a second PF; wherein the second PF is a PF used for paging a second type of terminal, and the second type of terminal does not support aggregated paging.

26. The apparatus of claim 24 or 25, further comprising: a fourth processing module, configured to acquire a position and configuration of a second PF; the second processing module is further configured to: determine a target PF based on at least one of a first target PF policy, the first configuration information, an identity of the terminal, the position of the second PF, and a configuration of the second PF; determine the first target PO in the target PF based on at least one of a first target PO policy, the first configuration information, the identity of the terminal, and the configuration of the second PF.

27. The apparatus of claim 24 or 25, wherein, the second processing module is further configured to: determine a serial number of the first target PO based on the first configuration information and the identity of the terminal; in a case where the first PF is bundled with a second PF, determine a position of the first target PO based on a position of a PO of the second PF and the serial number of the first target PO; in a case where the first PF is not bundled with a second PF, determine the position of the first target PO based on a position of the first PF and the serial number of the first target PO.

28. The apparatus of claim 24 or 25, further comprising: a fifth processing module, configured to acquire second configuration information; wherein the second configuration information comprises information of a first paging early indication (PEI); and the first PEI is associated with one or more of the first PFs.

29. The apparatus of claim 28, wherein, the second configuration information comprises at least one of: a sixth parameter, used for indicating a number of POs associated with the first PEI; a first load, used for indicating a load of downlink control information (DCI) of the first PEI; a third offset, used for indicating an offset between a first PF associated with the first PEI and a reference frame; a fourth offset, used for indicating an offset between a reference frame of the first PEI and a first PDCCH monitoring occasion.

30. The apparatus of claim 28 or 29, further comprising: a sixth processing module configured to determine an identity of a second target PO in the first PEI based on at least one of the second target PO policy, the identity of the terminal, the first configuration information, and the second configuration information; a seventh processing module configured to determine a location of a first one of the first PFs associated with the first PEI based on at least one of the second target PO policy, the identity of the second target PO, the first configuration information, and the second configuration information; an eighth processing module configured to determine the second target PO based on the identity of the second target PO and the location of the first one of the first PFs associated with the first PEI.

31. The apparatus of claim 28 or 29, further comprising: a ninth processing module configured to determine an identity of a second target PO in the first PEI based on at least one of the third target PO policy, the identity of the terminal, the first configuration information, and the second configuration information; a tenth processing module configured to determine a location of a first one of the PFs associated with the first PEI; an eleventh processing module configured to determine the second target PO based on the identity of the second target PO and the location of the first one of the PFs associated with the first PEI.

32. An apparatus for paging processing, comprising: a first sending module configured to send first configuration information to a terminal; wherein the first configuration information comprises binding information of first PFs, the first PFs being PFs for paging first-type terminals, the first-type terminals supporting aggregated paging.

33. The apparatus of claim 32, further comprising: a second sending module configured to send second configuration information to the terminal; wherein the second configuration information comprises information of a first paging early indication PEI, the first PEI being associated with one or more of the first PFs.

34. An apparatus for paging processing, comprising: a capability information receiving and sending module configured to receive capability information sent by a terminal and send the capability information to a distribution unit DU; wherein the capability information is used to indicate whether the terminal supports aggregated paging; a twelfth processing module configured to receive the capability information and perform paging based on the capability information.

35. A terminal comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the paging monitoring method according to any one of claims 1 to 16.

36. A network-side device comprising a processor and a memory, the memory storing programs or instructions executable on the processor, the programs or instructions being executed by the processor to implement the steps of the paging processing method according to any one of claims 17 to 22, or the steps of the paging processing method according to claim 23.

37. A readable storage medium, on which a program or instructions are stored, the program or instructions being executed by a processor to implement the steps of the paging monitoring method according to any one of claims 1 to 16, or the steps of the paging processing method according to any one of claims 17 to 22, or the steps of the paging processing method according to claim 23.

Citation Information

Patent Citations

  • Paging message monitoring method and device, terminal and readable storage medium

    CN114071496A

  • Method for transmitting and receiving paging message in wireless communication system by using unlicensed band, and device therefor

    US20210352616A1

  • Method and apparatus for reducing transmission delay of paging message

    WO2016180105A1

  • Paging transmission method, communication device and storage medium

    WO2024145766A1