WO2022206898A1 - 寻呼方法、装置、终端及网络侧设备 - Google Patents

寻呼方法、装置、终端及网络侧设备 Download PDF

Info

Publication number
WO2022206898A1
WO2022206898A1 PCT/CN2022/084431 CN2022084431W WO2022206898A1 WO 2022206898 A1 WO2022206898 A1 WO 2022206898A1 CN 2022084431 W CN2022084431 W CN 2022084431W WO 2022206898 A1 WO2022206898 A1 WO 2022206898A1
Authority
WO
WIPO (PCT)
Prior art keywords
paging
terminal
indication information
list
cause
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/084431
Other languages
English (en)
French (fr)
Inventor
鲍炜
刘进华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to EP22779078.9A priority Critical patent/EP4319349A4/en
Publication of WO2022206898A1 publication Critical patent/WO2022206898A1/zh
Priority to US18/373,641 priority patent/US20240031981A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/005—Multiple registrations, e.g. multihoming
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/183—Processing at user equipment or user record carrier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the present application belongs to the field of communication technologies, and specifically relates to a paging method, apparatus, terminal and network side equipment.
  • a dual-SIM device For a multi-SIM device, the following takes a dual-SIM device as an example. If the card 1 is communicating; the card 2 is suddenly paging; at present, some dual-SIM devices will disconnect the communication of the card 1 in order to respond to the card 2 paging. However, without knowing the type of service that triggers the paging of card 2, disconnecting the communication of card 1 and responding to the paging of card 2 may result in more losses than the gain. For example: card 1 is playing a game, and the paging of card 2 is triggered by a short message , interrupting the game of Card 1 in order to receive SMS from Card 2 will cause a bad user experience.
  • 3GPP decided to carry the paging cause in the paging message, so that the user equipment (User Equipment, UE) can decide whether to respond to the paging cause sent by the network (Network, NW) side according to the paging cause. call message.
  • the user equipment User Equipment, UE
  • NW Network
  • UE User Equipment
  • the related art does not consider whether the UE supports or needs the air interface paging cause. For a UE that does not support or does not need the air interface paging cause, if the paging cause is carried on the air interface during paging, it will bring unnecessary signaling overhead.
  • Embodiments of the present application provide a paging method, apparatus, terminal, and network-side equipment, which can solve the signaling overhead caused by carrying paging cause in paging messages without considering whether the UE supports or needs air interface paging cause in related technologies bigger problem.
  • a paging method applied to a terminal, and the method includes:
  • the terminal receives a paging message, and the paging message carries or does not carry paging cause indication information, wherein the paging cause indication information is used to indicate the paging cause corresponding to the paged terminal that needs or supports receiving the paging cause ;
  • the terminal performs the first operation based on the paging message.
  • a paging method applied to a network side device, and the method includes:
  • the network side device sends a paging message to the terminal, and the paging message carries or does not carry paging cause indication information, wherein the paging cause indication information is used to indicate the corresponding paging terminal that needs or supports receiving the paging cause paging reason.
  • a paging apparatus including:
  • a first receiving unit configured to receive a paging message, where the paging message carries or does not carry paging cause indication information, wherein the paging cause indication information is used to indicate a paged person who needs or supports receiving a paging cause The paging reason corresponding to the terminal;
  • a first processing unit configured to perform a first operation based on the paging message.
  • a paging device comprising:
  • the second sending unit is configured to send a paging message to the terminal, where the paging message carries or does not carry paging cause indication information, wherein the paging cause indication information is used to indicate the receiver that needs or supports receiving the paging cause.
  • the paging reason corresponding to the paging terminal.
  • a terminal in a fifth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
  • a terminal including a processor and a communication interface, wherein the communication interface is used to receive a paging message, and the paging message carries or does not carry paging cause indication information, wherein the paging message
  • the paging cause indication information is used to indicate the paging cause corresponding to the paged terminal that needs or supports receiving the paging cause; the processor is configured to perform the first operation based on the paging message.
  • a network side device in a seventh aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the The processor implements the steps of the paging method according to the second aspect when executed.
  • a network-side device including a processor and a communication interface, wherein the communication interface is used to send a paging message to a terminal, and the paging message carries or does not carry paging cause indication information, wherein , the paging cause indication information is used to indicate the paging cause corresponding to the paged terminal that needs or supports receiving the paging cause.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the paging method described in the first aspect are implemented, or The steps of implementing the paging method as described in the second aspect.
  • a chip in a tenth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the search method described in the first aspect. paging method, or implement the paging method described in the second aspect.
  • a computer program/program product is provided, the computer program/program product is stored in a non-volatile storage medium, the program/program product is executed by at least one processor to implement the first The steps of the paging method described in the aspect, or the steps of implementing the paging method described in the second aspect.
  • the terminal receives a paging message, and the paging message carries or does not carry paging cause indication information, and the paging cause indication information is used to indicate that the paging cause needs or supports receiving the paging cause.
  • the paging cause corresponding to the paging terminal is determined. Based on the paging message, the paging cause is determined so as to further determine the subsequent behavior. Considering whether the terminal supports or needs air interface paging cause, signaling overhead can be effectively reduced.
  • FIG. 1 is a schematic structural diagram of a wireless communication system to which an embodiment of the application can be applied;
  • FIG. 2 is one of the schematic flowcharts of the paging method provided by the embodiment of the present application.
  • FIG. 3 is the second schematic flowchart of the paging method provided by the embodiment of the present application.
  • FIG. 4 is one of schematic structural diagrams of a paging apparatus provided by an embodiment of the present application.
  • FIG. 5 is a second schematic structural diagram of a paging apparatus provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of a terminal implementing an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a network side device according to an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the terms so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and that "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the description below, but the techniques can also be applied to applications other than NR system applications, such as 6th generation (6th generation ) Generation, 6G) communication system.
  • 6th generation 6th generation
  • 6G 6th generation
  • FIG. 1 shows a schematic structural diagram of a wireless communication system to which an embodiment of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: smart watches, bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • FIG. 2 is one of the schematic flowcharts of a paging method provided by an embodiment of the present application. As shown in FIG. 2 , the method includes the following steps:
  • Step 200 the terminal receives a paging message, where the paging message carries or does not carry paging reason indication information;
  • the terminal receives a paging Paging message sent by the network side device, where the paging message carries or does not carry paging cause Paging Cause indication information.
  • the paging cause indication information is used to indicate the paging cause corresponding to the paged terminal that needs or supports receiving the paging cause.
  • the paging reason indication information indicates that the paging is triggered by a voice service (eg VoNR).
  • the paging message carries or does not carry paging cause indication information means that the paging message can optionally carry paging cause indication information.
  • the paging message does not carry the paging of the paged terminal.
  • Reason indication if the network side device does not support sending the paging cause of the paged terminal, or the paged terminal does not support or does not need to receive the paging cause, the paging message does not carry the paging of the paged terminal.
  • the paging message carries the paging cause.
  • the paging cause indication information of the terminal if the paging terminal supports or needs to receive the paging cause, and the paging cause of the paging terminal is the paging cause (for example, voice service) defined by the protocol, the paging message carries the paging cause.
  • the paging cause indication information of the terminal if the paging terminal supports or needs to receive the paging cause, and the paging cause of the paging terminal is the paging cause (for example, voice service) defined by the protocol, the paging message carries the paging cause.
  • the paging cause indication information of the terminal if the paging terminal supports or needs to receive the paging cause, and the paging cause of the paging terminal is the paging cause (for example, voice service) defined by the protocol, the paging message carries the paging cause.
  • the paging cause indication information of the terminal if the paging terminal supports or needs
  • the paging message may not carry the paging cause.
  • the paging cause indication information of the paging terminal, but the paging cause indication information that needs to indicate the paging terminal is not carried.
  • the paging cause indication information may be code information, for example, code 000 indicates paging cause A, and code 001 indicates paging cause B.
  • the paging cause indication information may be a paging priority; that is, what the NW sends on the air interface is not the specific service type that triggers paging, but the priority corresponding to the service that triggers paging;
  • the priority corresponding to the service can be specified by the protocol or negotiated between the UE and the NW, or set by the operator;
  • the paging priority can be a number, such as 1, 2...N, N priorities, and the corresponding priorities increase in turn or decreasing.
  • the paging cause indication information may also be other forms of information used to indicate the paging cause.
  • Step 201 The terminal performs a first operation based on the paging message.
  • the terminal determines to be paged based on the paging message, and further determines whether the paging message carries the paging cause indication information of the terminal, and if the paging cause indication information of the terminal can be obtained from the paging message , the paging cause of the terminal is determined according to the paging cause indication information, so that the terminal can further determine the follow-up behavior.
  • the terminal determines to be paged based on the paging message, and further obtains the paging cause indication information of the terminal based on the paging message. If the paging cause indication information of the terminal cannot be obtained, determine the network The side device does not support the sending of paging reasons for the terminal.
  • the terminal determines that it is not paged based on the paging message.
  • the terminal determines the paging cause of the terminal, it further includes:
  • the terminal responds to the paging message or does not respond to the paging message based on the paging reason.
  • UE1 is playing a game.
  • UE2 receives a paging indication, and the corresponding paging cause is VoNR, then the dual-SIM device may choose to respond to UE2's paging indication; if UE2 receives a paging indication message, the corresponding paging cause is a short message, and the dual-SIM device may choose to temporarily ignore the paging instruction of UE2.
  • the terminal is a paged terminal that needs or supports receiving a paging cause.
  • it corresponds to a UE inserted into a dual-card terminal, or a UE that needs to receive the paging reason reported to the network.
  • the terminal receives a paging message, and the paging message can optionally carry paging reason indication information, and the paging reason indication information is used to indicate a paged person who needs or supports receiving a paging reason.
  • the paging cause corresponding to the terminal is determined based on the paging message, so as to further determine the subsequent behavior. Considering whether the terminal supports or needs air interface paging cause, signaling overhead can be effectively reduced.
  • carrying or not carrying the paging cause indication information in the paging message includes: the paging message carries the first list, or the paging message carries the first list and the second list list,
  • each element entry in the described first list includes a first paging ID of a paged terminal
  • each entry in the described second list includes a paging cause indication information of a paged terminal
  • the ordering of the paging cause indication information of the paging terminals in the second list corresponds to the ordering of the first paging IDs of the first M or last M paging terminals in the first list, wherein M is the second The total number of entries contained in the list.
  • an air interface paging message carries a PagingRecordList, and the PagingRecordList has at least one PagingRecord and a maximum of MaxNrofPageRec PagingRecords.
  • Each PagingRecord carries a paging identifier (UE_Identity) of the UE being paged. That is, a paging message can indicate a maximum of MaxNrofPageRec paged UEs, some of which support or need to receive Paging cause; the rest do not support or need not.
  • the first paging ID refers to the legacy legacy UE ID, such as the fifth generation system temporary mobile subscriber identity (Fifth Generation System Temporary Mobile Subscriber Identity, 5G-S-TMSI), the complete inactive wireless network temporary identity (full inactive Radio Network Temporary Identifier, full I-RNTI).
  • 5G-S-TMSI Fifth Generation System Temporary Mobile Subscriber Identity
  • 5G-S-TMSI Fifth Generation System Temporary Mobile Subscriber Identity
  • full I-RNTI full inactive Radio Network Temporary Identifier
  • the first list is used to indicate the first paging identification ID of the paged terminal, the first list contains multiple entries, and each element entry in the first list contains a paged terminal. 's first paging ID.
  • the first list is PagingRecordList.
  • the paging message not only carries the first list, that is, the PagingRecordList, but also optionally carries the second list.
  • the second list includes multiple entries, and each entry in the second list includes paging cause indication information of a paged terminal.
  • the paging cause indication information is optionally carried.
  • the second list contains M elements/entry entries, that is, the length of the second list is M, indicating that the network side device indicates the paging reasons of M terminals, and M is a positive integer greater than or equal to 1.
  • the first list and the second list have the following correspondence: the ordering of the paging reasons of the paging terminals in the second list and the first M or last M paging terminals in the first list.
  • the paging ID ordering is corresponding.
  • the first paging ID included in the i-th entry in the first list corresponds to the paging cause indication information included in the i-th entry in the second list.
  • the paging ID of a UE is successfully matched with the i-th entry in the first list, and the paging reason of the UE is located in the corresponding position in the second list, that is, the i-th entry; or the paging ID of a UE and the i-th entry;
  • the jth entry in the first list is successfully matched, and the paging reason of the UE is located in the corresponding position in the second list, that is, the jth entry from the bottom.
  • the total number of entries included in the first list is La, and La is greater than or equal to the total number of entries M in the second list, that is, the UEs corresponding to the first paging IDs after the first M or before the last M in the first list are not Receive Paging Cause is required or not supported.
  • the terminal receives a paging message
  • the paging message carries a first list, optionally a second list
  • the paging cause indication information is indicated by the second list, based on the paging message
  • the paging cause is determined to further determine the subsequent behavior. Since the second list indicates the paging cause corresponding to the paged terminal that needs or supports receiving the paging cause, signaling overhead can be effectively reduced.
  • the terminal performs the first operation based on the paging message, including:
  • the terminal determines whether the terminal is paged based on the first list
  • the terminal determines the paging reason of the terminal based on the second list
  • the determining whether the terminal is paged includes at least one of the following:
  • the terminal If the first paging ID of the terminal matches the first paging ID contained in the Nth or last Nth entry in the first list, it is determined that the terminal is paged, and N is greater than or equal to 1 A positive integer less than or equal to the total number of entries contained in the first list;
  • the terminal If the first paging ID of the terminal fails to match with the first paging ID included in all entries in the first list, it is determined that the terminal is not paged;
  • the terminal determines the paging reason of the terminal based on the second list, including at least one of the following:
  • the terminal obtains, by the terminal, the paging cause indication information corresponding to the Nth or last Nth entry in the second list, and determining the paging cause of the terminal;
  • the terminal determines that the network side device does not support paging reason sending.
  • the successful matching between the first paging ID of the terminal and the first paging ID contained in the Nth or last Nth entry in the first list refers to the first paging ID of the terminal. be the same as the first paging ID contained in the Nth entry in the first list;
  • the failure to match the first paging ID of the terminal with the first paging ID included in all entries in the first list means that the first paging ID of the terminal and all entries in the first list include The first paging IDs are different.
  • the terminal is paged, that is, the first paging ID of the terminal and the first paging ID contained in the Nth or last Nth entry in the first list are successfully matched, you can further The paging cause of the terminal is determined based on the second list, and the paging cause of the terminal is located in a corresponding position in the second list, that is, the Nth entry or the last Nth entry.
  • the paging cause indication information corresponding to each entry, and then the paging cause of the terminal is determined according to the paging cause indication information.
  • the terminal acquires the paging cause indication information corresponding to the Nth or last Nth entry in the second list, and determines the paging cause of the terminal, including at least one of the following:
  • the paging cause of the terminal is determined according to the paging cause indication information
  • the terminal determines the paging cause of the terminal based on a protocol agreement; determine The paging cause indication information corresponding to the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information.
  • the terminal can obtain the paging cause indication information corresponding to the Nth or last Nth entry from the second list, it means that the network side device has indicated the paging cause of the terminal.
  • the paging cause is determined according to the paging cause indication information corresponding to the entry. For example, if the entry indicates that the UE is paged because of the voice service, the UE determines that it is paged because of the voice service.
  • the terminal determines the paging of the terminal based on the protocol agreement. or, it is determined that the paging cause indication information corresponding to the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information. Doing so can save air interface signaling overhead.
  • the paging cause indication information corresponding to the Nth or last Nth entry is not carried; or, in the terminal whose paging cause corresponds to the previous entry
  • the paging cause indication information corresponding to the terminal may not appear.
  • the Entry field is used to explicitly indicate the paging reason of the terminal; the length is used to indicate the total number of entries included in the second list. For example, the length field is 4, indicating that there are 4 paging terminals (UE_ID1, UE_ID2, UE_ID3, UE_ID4) paging reasons are indicated, and a bit information in the Entry field indicates carrying or not carrying the paging reason defined by the protocol , such as voice service, Entry field: the first entry is 1, the second entry is 0, the third entry is 1, and the fourth entry is 0.
  • the Entry field indicates UE_ID1 and UE_ID3
  • the paging cause of the paging cause is the paging cause defined by the protocol
  • the paging cause of UE_ID2 and UE_ID4 is the paging cause complementary to the paging cause defined by the protocol, such as non-voice service.
  • the paging cause indication information corresponding to the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information, that is, the paging cause of UE_ID2 is the same as UE_ID1.
  • the terminal determines that the network-side device does not support paging reason sending.
  • the paging cause includes the following situations: The network side device does not support paging cause sending. That is, the network side device does not support the sending of the paging cause of the terminal.
  • the reason why the network side device does not support paging includes: the access network does not support it and/or the core network does not support it.
  • a cell can be connected to multiple core networks (assuming that CN1 supports it, but CN2 does not), for example, UE1 is connected to CN1, and UE2 is connected to CN2. If the access network/cell supports the sending of paging reasons for UE1, but the core network CN1 does not. If the sending of the paging cause of the UE1 is supported, the second list does not include the paging cause indication information of the UE1.
  • the paging method further includes:
  • the downlink signaling carries or does not carry first indication information, where the first indication information is used to indicate that the paging message supports carrying a paging cause;
  • the terminal determines that the current cell does not support the sending of paging reasons; or,
  • the terminal determines that the current cell supports sending of paging reasons
  • the downlink signaling includes one of the following:
  • the first indication information is used to indicate that the paging message supports carrying a paging cause, that is, the current cell supports sending the paging cause.
  • the first indication information is carried in the downlink signaling, it means that the current cell supports the sending of paging reasons.
  • the paging message carries or does not carry the first indication information.
  • the system information carries or does not carry the first indication information; for example, in a cell broadcast message, such as SIBx, the first indication information is carried, indicating that the network side device supports the sending of paging reasons for the terminal.
  • a cell broadcast message such as SIBx
  • the first indication information is carried or not carried in the downlink scheduling signaling.
  • the terminal determines the paging reason of the terminal based on the second list, further comprising:
  • the terminal determines that the network-side device does not support the sending of paging reasons.
  • the downlink signaling carries the first indication information, indicating that the current cell supports the sending of paging reasons, but at the same time, the paging message does not carry the second list, that is, the second list contains 0 entries, indicating that there is no terminal.
  • the paging cause is indicated, and in this case, the terminal determines that the network-side device does not support paging cause sending. Further, the terminal determines that the core network does not support paging reason sending.
  • the paging message carries or does not carry paging cause indication information including:
  • the paging message carries at least one of the third list and the fourth list
  • each entry in the third list includes a first paging ID of a paged terminal
  • each entry in the described fourth list includes a first paging ID of a paged terminal and paging cause indication information corresponding to the first paging ID;
  • the first paging ID of a paged terminal does not appear in the third list and the fourth list at the same time.
  • the terminal is a paged terminal that needs or supports receiving paging reasons, but because the network side device does not support sending paging reasons, the paging ID of the terminal will be included in the third list.
  • the paging ID of the terminal will be included in the third list.
  • the terminal is a paged terminal that needs or supports receiving paging reasons
  • the network-side device supports the sending of paging reasons for the terminal
  • the paging ID and paging reason indication information of the terminal will be included in the first page. four in the list.
  • a cell can be connected to multiple core networks. It is assumed that the access network/cell supports paging cause sending, the core network CN1 supports paging cause sending, and CN2 does not support paging cause sending.
  • the access network/cell supports paging cause sending
  • the core network CN1 supports paging cause sending
  • CN2 does not support paging cause sending.
  • UE1 is connected to CN1 and UE2 is connected to CN2
  • the Paging message is sent by the cell, then the first paging ID of UE1 will be included in the fourth list; the first paging ID of UE2 will be included in the third list.
  • the paging cause indication information corresponding to the first paging ID in the fourth list is optionally carried.
  • the terminal determines the paging reason based on the paging message, so as to further determine the subsequent behavior, which can effectively reduce signaling overhead.
  • the terminal performs a first operation based on the paging message, including at least one of the following:
  • the terminal determines that the network side device does not support paging reason sending;
  • the terminal If the first paging ID of the terminal matches the first paging ID contained in the Pth entry in the fourth list successfully, obtain the paging cause indication information contained in the Pth entry in the fourth list , determine the paging reason of the terminal;
  • the terminal determines that it is not paged
  • P is a positive integer greater than or equal to 1.
  • obtaining the paging cause indication information contained in the Pth entry in the fourth list, and determining the paging cause of the terminal includes:
  • the paging cause of the terminal is determined according to the paging cause indication information
  • the paging cause indication information contained in the Pth entry perform one of the following: determine the paging cause of the terminal based on a protocol agreement; determine the paging cause indication information corresponding to the terminal and the previous explicit The paging cause indication information corresponding to the entry carrying or carrying the paging cause indication information is the same.
  • the paging cause indication information included in the Pth entry in the fourth list is carried, then according to the paging cause indication information, determine the paging cause of the terminal, for example, the entry indicates that the UE is due to If the voice service is paged, the UE determines that it is paged for the voice service.
  • the terminal determines the paging of the terminal based on the protocol agreement. or, it is determined that the paging cause indication information corresponding to the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information. Doing so can save air interface signaling overhead.
  • the paging cause indication information corresponding to the p-th or p-th last entry is not carried; or, in the terminal whose paging cause corresponds to the previous entry
  • the paging cause indication information corresponding to the terminal may not appear.
  • the determining the paging cause of the terminal based on the protocol agreement includes:
  • the paging cause of the terminal is a paging triggered by a non-voice service or other paging causes complementary to the paging cause defined by the protocol.
  • the determination of the paging cause of the terminal based on the protocol agreement mentioned in the above-mentioned embodiments can be understood as determining that the paging cause of the terminal is a paging triggered by a non-voice service or a paging cause defined by a protocol. other paging causes complementary to the paging cause.
  • the paging cause indication information is generated based on an encrypted input parameter; wherein the encrypted input parameter includes at least one of the following:
  • the paging cause or paging cause indication information before encryption of the paging terminal
  • the terminal performs the first operation based on the paging message, including:
  • the paging cause indication information is encrypted, and only the paged UE can decrypt the paging cause.
  • the network side device may generate paging cause indication information based on the encrypted input parameter.
  • it can be generated based on at least one of all or part of the terminal identifier UE ID of the terminal being paged, the key shared by the network side device and the terminal being paged, and the paging cause or paging cause indication information before encryption. Paging reason indication information.
  • the terminal after obtaining the paging cause indication information corresponding to the terminal, the terminal needs to decrypt the paging cause indication information, so as to obtain the paging cause of the terminal.
  • the method further includes at least one of the following:
  • the terminal determines that the paging cause indication information or the paging cause is invalid;
  • the terminal When the terminal detects that the paging cause indication information or the paging cause is an unexpected value, the terminal reports the first information to the network side device;
  • the terminal receives the security parameters sent by the network side device for decrypting the subsequent paging reasons.
  • the terminal After the terminal acquires the paging cause indication information, if it detects that the paging cause indication information or the paging cause has an unexpected value, it determines that the paging cause indication information or the paging cause is invalid.
  • the terminal determines that the paging cause indication information or the paging cause is invalid, and reports first information, where the first information is used to indicate at least one of the following: receiving an unexpected paging cause or an unexpected paging cause; Paging cause indication information; the cell identity that received the unexpected paging cause or the unexpected paging cause indication information.
  • the network-side device after receiving the first information reported by the terminal, the network-side device will send the security parameters for decrypting the subsequent paging reasons to the terminal, and the terminal receives the security parameters sent by the network-side device for decrypting the subsequent paging reasons.
  • the second list or the fourth list includes at least one of the following:
  • the length field is used to indicate the total number of entries included in the second list or the fourth list, and the Entry field carries or does not carry the paging cause indication information of the terminal;
  • the paging reason indication information when carried, it indicates that the terminal is paged because of the carried paging reason;
  • the paging cause indication information includes one of the following:
  • the paging cause of the terminal is the paging cause agreed in the protocol
  • the paging cause indication information of the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information.
  • the second list contains: length indication: N; and N entries.
  • each entry there is a bit indicating whether IE pagingCause-r17 is carried; if the indication is carried, it indicates that the paging reason is voice; if the indication is not carried, it indicates that the paging reason is non-voice.
  • N entries must appear, and IE pagingCause-r17 is optional.
  • pagingCause-r17 Because only one pagingCause-r17 value is defined, even if the IE pagingCause-r17 appears, no additional bits are used to indicate what the paging cause is. If two pagingCause values (such as A and B) are defined, then in the case of IE pagingCause-r17, an additional 1 bit is required to indicate whether pagingCause is A or B.
  • the paging cause indication information when the paging cause indication information is not carried, it indicates that the paging cause of the terminal is the paging cause agreed in the protocol.
  • the paging cause indication information representing the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information. That is to say, when the paging cause of the terminal is the same as the paging cause of the terminal corresponding to the previous entry, the paging cause indication information corresponding to the terminal may not appear. Thereby saving signaling overhead.
  • the paging message carries or does not carry paging cause indication information, including at least one of the following:
  • the paging message carries the second paging ID allocated by the network side device to the paging terminal that needs or supports receiving the paging cause;
  • the paging message carries the third paging ID corresponding to the paging terminal that needs or supports receiving the paging reason, wherein the third paging ID is based on the first paging ID of the paging terminal and the protocol agreement obtained by at least one of the derivation methods;
  • the paging message is scheduled by the PDCCH scrambled using the RNTI corresponding to the paging cause, wherein the RNTI corresponding to different paging causes is obtained by the explicit instruction of the network side device or the derivation method agreed in the protocol.
  • the terminal performs a first operation based on the paging message, including at least one of the following:
  • the terminal determines the paging cause according to the second paging ID
  • the terminal determines the paging cause according to the third paging ID
  • the terminal determines the paging reason according to the RNTI.
  • the paging cause can be implicitly carried by the paging ID.
  • the paging message carries the second paging ID allocated by the network side device for the paging terminal that needs or supports receiving the paging cause;
  • the paging message carries a third paging ID corresponding to the paging terminal that needs or supports receiving the paging cause, wherein the third paging ID is based on the first paging ID and the paging terminal of the paged terminal. Obtained by at least one of the derivation methods agreed in the agreement;
  • the NW presets two paging reasons, A and B; at the same time, the NW allocates two paging IDs, ID_A and ID_B, to each UE that needs to receive the paging reasons, corresponding to the paging reasons A and B respectively.
  • the NW When paging is triggered by reason A, the NW carries ID_A in the PagingRecordList to page the UE; when the paging is triggered by reason B, the NW carries ID_B in the PagingRecordList to page the UE.
  • ID_A and ID_B can also be obtained according to at least one of the first paging ID of the paged terminal and a derivation manner agreed in the protocol.
  • the time at which the UE monitors the paging does not change, which can reduce the implementation complexity of the UE.
  • the paging message is scheduled by the PDCCH scrambled by using the RNTI corresponding to the paging cause, wherein the RNTI corresponding to different paging causes is obtained by an explicit instruction of the network side device or a derivation method agreed in a protocol.
  • the NW presets two RNTIs (RNTI_A and RNTI_B), corresponding to preset two paging reasons, A and B, respectively.
  • the NW uses PDCCH scheduling scrambled by RNTI_A, and transmits the paging message on the corresponding PDSCH channel, in which PagingRecordList carries the paging identifier of the paged UE; when paging is triggered by reason B If yes, the NW uses the RNTI_B scrambled PDCCH scheduling, and transmits the paging message on the corresponding PDSCH channel, where the PagingRecordList carries the paging identifier of the paging UE.
  • the method before the terminal receives the paging message, the method further includes:
  • the terminal reports second information to the network-side device, where the second information is used to indicate that the terminal needs or supports receiving the paging cause, or indicates that the terminal does not need or does not support receiving the paging cause.
  • the UE reports to the network whether it needs or supports the reason for receiving paging.
  • a multi-card device enables multi-card, its UE can report the reason why it needs or supports receiving paging.
  • FIG. 3 is a second schematic flowchart of a paging method provided by an embodiment of the present application. As shown in Figure 3, the method includes the following steps:
  • Step 300 The network side device sends a paging message to the terminal, where the paging message carries or does not carry paging reason indication information.
  • the network side device sends a paging Paging message to the terminal, where the paging message carries or does not carry paging cause Paging Cause indication information.
  • the paging cause indication information is used to indicate the paging cause corresponding to the paged terminal that needs or supports receiving the paging cause.
  • the paging reason indication information indicates that the paging is triggered by a voice service (eg VoNR).
  • the paging message carries or does not carry paging cause indication information means that the paging message can optionally carry paging cause indication information.
  • the paging message does not carry the paging of the paged terminal.
  • Reason indication if the network side device does not support sending the paging cause of the paged terminal, or the paged terminal does not support or does not need to receive the paging cause, the paging message does not carry the paging of the paged terminal.
  • the paging message carries the paging cause.
  • the paging cause indication information of the terminal if the paging terminal supports or needs to receive the paging cause, and the paging cause of the paging terminal is the paging cause (for example, voice service) defined by the protocol, the paging message carries the paging cause.
  • the paging cause indication information of the terminal if the paging terminal supports or needs to receive the paging cause, and the paging cause of the paging terminal is the paging cause (for example, voice service) defined by the protocol, the paging message carries the paging cause.
  • the paging cause indication information of the terminal if the paging terminal supports or needs to receive the paging cause, and the paging cause of the paging terminal is the paging cause (for example, voice service) defined by the protocol, the paging message carries the paging cause.
  • the paging cause indication information of the terminal if the paging terminal supports or needs
  • the paging message may not carry the paging cause.
  • the paging cause indication information of the paging terminal, but the paging cause indication information that needs to indicate the paging terminal is not carried.
  • the paging cause indication information may be code information, for example, code 000 indicates paging cause A, and code 001 indicates paging cause B.
  • the paging cause indication information may be a paging priority; that is, what the NW sends on the air interface is not the specific service type that triggers paging, but the priority corresponding to the service that triggers paging;
  • the priority corresponding to the service can be specified by the protocol or negotiated between the UE and the NW, or set by the operator;
  • the paging priority can be a number, such as 1, 2...N, N priorities, and the corresponding priorities increase in turn or decreasing.
  • the paging cause indication information may also be other forms of information.
  • the network side device sends a paging message
  • the paging message can optionally carry paging cause indication information
  • the paging cause indication information is used to indicate the paging cause that needs or supports receiving the paging cause.
  • the paging reason corresponding to the calling terminal can effectively reduce the signaling overhead.
  • the paging message carrying or not carrying the paging cause indication information includes: the paging message carries the first list, or the paging message carries the first list and the second list,
  • each element entry in the described first list includes a first paging ID of a paged terminal
  • each entry in the described second list includes a paging cause indication information of a paged terminal
  • the ordering of the paging cause indication information of the paging terminals in the second list corresponds to the ordering of the first paging IDs of the first M or last M paging terminals in the first list, wherein M is the second The total number of entries contained in the list.
  • the first list is used to indicate the first paging identification ID of the paged terminal, the first list contains multiple entries, and each element entry in the first list contains a paged terminal. 's first paging ID.
  • the paging message not only carries the first list, that is, the PagingRecordList, but also optionally carries the second list.
  • the second list includes multiple entries, and each entry in the second list includes paging cause indication information of a paged terminal.
  • the paging cause indication information is optionally carried.
  • the second list contains M elements/entry entries, that is, the length of the second list is M, indicating that the network side device indicates the paging reasons of M terminals, and M is a positive integer greater than or equal to 1.
  • the first list and the second list have the following correspondence: the ordering of the paging reasons of the paging terminals in the second list and the first M or last M paging terminals in the first list.
  • the paging ID ordering is corresponding.
  • the first paging ID included in the i-th entry in the first list corresponds to the paging cause indication information included in the i-th entry in the second list.
  • the paging ID of a UE is successfully matched with the i-th entry in the first list, and the paging reason of the UE is located in the corresponding position in the second list, that is, the i-th entry; or the paging ID of a UE and the i-th entry;
  • the jth entry in the first list is successfully matched, and the paging reason of the UE is located in the corresponding position in the second list, that is, the jth entry from the bottom.
  • the total number of entries included in the first list is La, and La is greater than or equal to the total number of entries M in the second list, that is, the UEs corresponding to the first paging IDs after the first M or before the last M in the first list are not Receive Paging Cause is required or not supported.
  • the network side device sends a paging message, the paging message carries a first list, and optionally a second list, and the paging cause indication information is indicated by the second list, because the second list It indicates the paging cause corresponding to the paging terminal that needs or supports receiving the paging cause, which can effectively reduce signaling overhead.
  • the paging message carrying or not carrying the paging cause indication information includes: the paging message carries at least one of the third list and the fourth list,
  • each element entry in the described third list includes the first paging ID of a terminal
  • each entry in the described fourth list includes the first paging ID of a terminal and the paging cause indication information corresponding to the first paging ID;
  • the first paging ID of a paged terminal does not appear in the third list and the fourth list at the same time.
  • the terminal is a paged terminal that needs or supports receiving paging reasons, but because the network side device does not support sending paging reasons, the paging ID of the terminal will be included in the third list.
  • the paging ID of the terminal will be included in the third list.
  • the terminal is a paged terminal that needs or supports receiving paging reasons
  • the network-side device supports the sending of paging reasons for the terminal
  • the paging ID and paging reason indication information of the terminal will be included in the first page. four in the list.
  • a cell can be connected to multiple core networks. It is assumed that the access network/cell supports paging cause sending, the core network CN1 supports paging cause sending, and CN2 does not support paging cause sending.
  • the access network/cell supports paging cause sending
  • the core network CN1 supports paging cause sending
  • CN2 does not support paging cause sending.
  • UE1 is connected to CN1 and UE2 is connected to CN2
  • the Paging message is sent by the cell, then the first paging ID of UE1 will be included in the fourth list; the first paging ID of UE2 will be included in the third list.
  • the paging cause indication information corresponding to the first paging ID in the fourth list is optionally carried.
  • the network side device can effectively reduce signaling overhead by carrying at least one of the third list and the fourth list in the paging message.
  • the paging cause indication information is generated based on an encrypted input parameter; wherein the encrypted input parameter includes at least one of the following:
  • the paging cause or paging cause indication information before encryption of the paging terminal is not limited to.
  • the paging cause indication information is encrypted, and only the paged UE can decrypt the paging cause.
  • the network side device may generate paging cause indication information based on the encrypted input parameter.
  • the network side device may be based on all or part of the terminal identification UE ID of the paged terminal, the key shared by the network side device and the paged terminal, and the paging cause or paging cause indication information before encryption.
  • a generated paging reason indication message may be based on all or part of the terminal identification UE ID of the paged terminal, the key shared by the network side device and the paged terminal, and the paging cause or paging cause indication information before encryption.
  • the method also includes at least one of the following:
  • the network side device receives the first information sent by the terminal
  • the network-side device sends the security parameter for decrypting the subsequent paging reason to the terminal.
  • the terminal obtains the paging cause indication information, if it detects that the paging cause indication information or the paging cause is an unexpected value, it determines that the paging cause indication information or the paging cause is invalid, and reports the paging cause indication information or paging cause. first information.
  • the first information is used to indicate at least one of the following: receiving unexpected paging cause or unexpected paging cause indication information; receiving the cell identity of unexpected paging cause or unexpected paging cause indication information.
  • the network-side device after receiving the first information reported by the terminal, the network-side device will send the security parameters for decrypting the subsequent paging reasons to the terminal, and the terminal receives the security parameters sent by the network-side device for decrypting the subsequent paging reasons.
  • the second list or the fourth list includes at least one of the following:
  • the length field is used to indicate the total number of entries included in the second list or the fourth list, and the Entry field carries or does not carry the paging cause indication information of the terminal;
  • the paging cause indication information when carried, it indicates that the terminal is paged because of the carried paging cause;
  • the paging cause indication information includes one of the following:
  • the paging cause of the terminal is the paging cause agreed in the protocol
  • the paging cause indication information of the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information.
  • the second list contains: length indication: N; and N entries.
  • each entry there is a bit indicating whether IE pagingCause-r17 is carried; if carried, it indicates that the paging cause is voice; if it is not carried, it indicates that the paging cause is non-voice.
  • N entries must appear, and IE pagingCause-r17 is optional.
  • pagingCause-r17 Because only one pagingCause-r17 value is defined, even if the IE pagingCause-r17 appears, no additional bits are used to indicate what the paging cause is. If two pagingCause values (such as A and B) are defined, then in the case of IE pagingCause-r17, an additional 1 bit is required to indicate whether pagingCause is A or B.
  • the paging cause indication information when the paging cause indication information is not carried, it indicates that the paging cause of the terminal is the paging cause agreed in the protocol.
  • the paging cause indication information representing the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information. That is to say, when the paging cause of the terminal is the same as the paging cause of the terminal corresponding to the previous entry, the paging cause indication information corresponding to the terminal may not appear. Thereby saving signaling overhead.
  • the method further includes:
  • the network side device sends downlink signaling to the terminal, the downlink signaling carries or does not carry first indication information, and the first indication information is used to indicate that the paging message supports carrying a paging reason;
  • the downlink signaling includes one of the following:
  • the first indication information is used to indicate that the paging message supports carrying a paging cause, that is, the current cell supports sending the paging cause.
  • the first indication information is carried in the downlink signaling, it means that the current cell supports the sending of paging reasons.
  • the paging message sent by the network side device to the terminal carries or does not carry the first indication information.
  • the system information sent by the network side device to the terminal carries or does not carry the first indication information; for example, in a cell broadcast message, for example, the SIBx carries the first indication information, indicating that the network side device supports the first indication information.
  • the terminal's paging reason is sent.
  • the downlink scheduling signaling sent by the network side device to the terminal carries or does not carry the first indication information.
  • the paging message carries or does not carry paging cause indication information, including at least one of the following:
  • the paging message carries the second paging ID allocated by the network side device to the paging terminal that needs or supports receiving the paging cause;
  • the paging message carries the third paging ID corresponding to the paging terminal that needs or supports receiving the paging reason, wherein the third paging ID is the first paging ID of the network side device based on the paging terminal and at least one of the derivation methods agreed in the agreement;
  • the paging message is scheduled by the PDCCH scrambled using the RNTI corresponding to the paging cause, wherein the RNTI corresponding to different paging causes is obtained by the explicit instruction of the network side device or the derivation method agreed in the protocol.
  • the paging cause can be implicitly carried by the paging ID.
  • the paging message carries the second paging ID allocated by the network side device for the paging terminal that needs or supports receiving the paging cause;
  • the paging message carries a third paging ID corresponding to the paging terminal that needs or supports receiving the paging reason, wherein the third paging ID is the first paging ID of the network side device based on the paging terminal It is obtained by at least one of the derivation methods of the call ID and the protocol.
  • the NW presets two paging reasons, A and B; at the same time, the NW allocates two paging IDs, ID_A and ID_B, to each UE that needs to receive the paging reasons, corresponding to the paging reasons A and B respectively.
  • the NW When paging is triggered by reason A, the NW carries ID_A in the PagingRecordList to page the UE; when the paging is triggered by reason B, the NW carries ID_B in the PagingRecordList to page the UE.
  • ID_A and ID_B can also be obtained according to at least one of the first paging ID of the paged terminal and a derivation manner agreed in the protocol.
  • the time at which the UE monitors the paging does not change, which can reduce the implementation complexity of the UE.
  • the paging message is scheduled by the PDCCH scrambled by using the RNTI corresponding to the paging cause, wherein the RNTI corresponding to different paging causes is obtained by an explicit instruction of the network side device or a derivation method agreed in a protocol.
  • the NW presets two RNTIs (RNTI_A and RNTI_B), corresponding to preset two paging reasons, A and B, respectively.
  • the NW uses PDCCH scheduling scrambled by RNTI_A, and transmits the paging message on the corresponding PDSCH channel, in which PagingRecordList carries the paging identifier of the paged UE; when paging is triggered by reason B If yes, the NW uses the RNTI_B scrambled PDCCH scheduling, and transmits the paging message on the corresponding PDSCH channel, where the PagingRecordList carries the paging identifier of the paging UE.
  • the method further includes:
  • the network side device receives the second information reported by the terminal, where the second information is used to indicate that the terminal needs or supports receiving the paging cause, or indicates that the terminal does not need or does not support receiving the paging cause.
  • the UE reports to the network whether it needs or supports the reason for receiving paging.
  • a multi-card device enables multi-card, its UE can report the reason why it needs or supports receiving paging.
  • the paging message After the network side device receives the second information, for a terminal that needs or supports receiving the paging cause, the paging message carries the paging cause indication information of the terminal. For a terminal that does not need or does not support receiving the paging cause, the paging cause indication information of the terminal is not carried in the paging message, thereby effectively reducing signaling overhead.
  • the executing subject may be a paging device, or a control module in the paging device for executing the paging method.
  • the paging device provided by the embodiment of the present application is described by taking the paging device executing the paging method as an example.
  • FIG. 4 is one of schematic structural diagrams of a paging apparatus provided by an embodiment of the present application. As shown in Figure 4, the device includes:
  • the first receiving unit 410 is configured to receive a paging message, where the paging message carries or does not carry paging cause indication information, wherein the paging cause indication information is used to indicate that the paging cause needs or supports receiving the paging cause.
  • the first processing unit 420 is configured to perform a first operation based on the paging message.
  • the paging message can optionally carry paging cause indication information, and the paging cause indication information is used to indicate a paged terminal that needs or supports receiving a paging cause
  • the paging cause is determined so as to further determine the subsequent behavior, which can effectively reduce signaling overhead.
  • the paging message carrying or not carrying the paging cause indication information includes: the paging message carries the first list, or the paging message carries the first list and the second list,
  • each element entry in the described first list includes a first paging ID of a paged terminal
  • each entry in the described second list includes a paging cause indication information of a paged terminal
  • the ordering of the paging cause indication information of the paging terminals in the second list corresponds to the ordering of the first paging IDs of the first M or last M paging terminals in the first list, wherein M is the second The total number of entries contained in the list.
  • the first processing unit is used for:
  • the terminal In the case that the terminal is paged, based on the second list, determine a paging reason for the terminal;
  • the determining whether the terminal is paged includes at least one of the following:
  • the terminal If the first paging ID of the terminal matches the first paging ID contained in the Nth or last Nth entry in the first list, it is determined that the terminal is paged, and N is greater than or equal to 1 A positive integer less than or equal to the total number of entries contained in the first list;
  • the terminal If the first paging ID of the terminal fails to match with the first paging ID included in all entries in the first list, it is determined that the terminal is not paged;
  • determining the paging reason of the terminal based on the second list includes at least one of the following:
  • the network side device determines that the network side device does not support paging reason sending.
  • obtaining the paging cause indication information corresponding to the Nth or last Nth entry in the second list, and determining the paging cause of the terminal including at least one of the following:
  • the paging cause of the terminal is determined according to the paging cause indication information
  • the terminal determines the paging cause of the terminal based on a protocol agreement; determine The paging cause indication information corresponding to the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information.
  • it also includes a second processing unit for:
  • the downlink signaling carries or does not carry first indication information, where the first indication information is used to indicate that the paging message supports carrying a paging cause;
  • the terminal determines that the current cell does not support the sending of paging reasons; or,
  • the terminal determines that the current cell supports sending of paging reasons
  • the downlink signaling includes one of the following:
  • the determining the paging cause of the terminal based on the second list further includes:
  • the terminal determines that the network-side device does not support the sending of paging reasons.
  • the paging message carrying or not carrying paging cause indication information includes: the paging message carries at least one of the third list and the fourth list,
  • each entry in the third list includes a first paging ID of a paged terminal
  • each entry in the described fourth list includes a first paging ID of a paged terminal and paging cause indication information corresponding to the first paging ID;
  • the first paging ID of a paged terminal does not appear in the third list and the fourth list at the same time.
  • the first processing unit is configured to execute at least one of the following:
  • the terminal determines that the network side device does not support paging reason sending;
  • the terminal If the first paging ID of the terminal matches the first paging ID contained in the Pth entry in the fourth list successfully, obtain the paging cause indication information contained in the Pth entry in the fourth list , determine the paging reason of the terminal;
  • the terminal determines that it is not paged
  • P is a positive integer greater than or equal to 1.
  • obtaining the paging cause indication information contained in the Pth entry in the fourth list, and determining the paging cause of the terminal including:
  • the paging cause of the terminal is determined according to the paging cause indication information
  • the paging cause indication information contained in the Pth entry is implicitly carried or not carried, perform one of the following: determine the paging cause of the terminal based on the protocol agreement; determine the paging cause indication information corresponding to the terminal and The paging cause indication information corresponding to the previous entry that explicitly carries or carries the paging cause indication information is the same.
  • the determining the paging cause of the terminal based on the protocol agreement includes:
  • the paging cause of the terminal is a paging triggered by a non-voice service or other paging causes complementary to the paging cause defined by the protocol.
  • the paging cause indication information is generated based on an encrypted input parameter; wherein the encrypted input parameter includes at least one of the following:
  • the first processing unit is used for:
  • a third processing unit configured to execute at least one of the following:
  • the paging cause indication information or the paging cause is an unexpected value, it is determined that the paging cause indication information or the paging cause is invalid;
  • the first information is used to indicate at least one of the following:
  • Unexpected paging cause or unexpected paging cause indication information is received
  • the identity of the cell that received the unexpected paging cause or the unexpected paging cause indication information is based on the identity of the cell that received the unexpected paging cause or the unexpected paging cause indication information.
  • the second list or the fourth list includes at least one of the following:
  • the length field is used to indicate the total number of entries included in the second list or the fourth list, and the Entry field carries or does not carry the paging cause indication information of the terminal;
  • the paging cause indication information when carried, it indicates that the terminal is paged because of the carried paging cause;
  • the paging cause indication information includes one of the following:
  • the paging cause of the terminal is the paging cause agreed in the protocol
  • the paging cause indication information of the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information.
  • the paging message carries or does not carry paging cause indication information, including at least one of the following:
  • the paging message carries the second paging ID allocated by the network side device to the paging terminal that needs or supports receiving the paging cause;
  • the paging message carries the third paging ID corresponding to the paging terminal that needs or supports receiving the paging reason, wherein the third paging ID is based on the first paging ID of the paging terminal and the protocol agreement obtained by at least one of the derivation methods;
  • the paging message is scheduled by the PDCCH scrambled using the RNTI corresponding to the paging cause, wherein the RNTI corresponding to different paging causes is obtained by the explicit instruction of the network side device or the derivation method agreed in the protocol.
  • the first processing unit is configured to execute at least one of the following:
  • the paging reason is determined according to the RNTI.
  • the first sending unit is configured to report second information to the network side device, where the second information is used to indicate that the terminal needs or supports receiving the paging reason, or indicates that the terminal does not need or does not support receiving the paging reason.
  • the paging apparatus in this embodiment of the present application may be an apparatus, an apparatus having an operating system or an electronic device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the apparatus or electronic device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the paging apparatus provided in this embodiment of the present application can implement each process implemented by the method embodiment in FIG. 2 and achieve the same technical effect. To avoid repetition, details are not described here.
  • FIG. 5 is a second schematic structural diagram of a paging apparatus according to an embodiment of the present application. As shown in Figure 5, the device includes:
  • the second sending unit 510 is configured to send a paging message to the terminal, where the paging message carries or does not carry paging reason indication information, wherein the paging reason indication information is used to indicate that the paging reason needs or supports receiving the paging reason.
  • the paging message can optionally carry paging cause indication information, and the paging cause indication information is used to indicate a paged terminal that needs or supports receiving a paging cause
  • the corresponding paging cause can effectively reduce signaling overhead.
  • the paging message carrying or not carrying the paging cause indication information includes: the paging message carries the first list, or the paging message carries the first list and the second list,
  • each element entry in the described first list includes a first paging ID of a paged terminal
  • each entry in the described second list includes a paging cause indication information of a paged terminal
  • the ordering of the paging cause indication information of the paging terminals in the second list corresponds to the ordering of the first paging IDs of the first M or last M paging terminals in the first list, wherein M is the second The total number of entries contained in the list.
  • the paging message carrying or not carrying the paging cause indication information includes: the paging message carries at least one of the third list and the fourth list,
  • each element entry in the described third list includes the first paging ID of a terminal
  • each entry in the described fourth list includes the first paging ID of a terminal and the paging cause indication information corresponding to the first paging ID;
  • the first paging ID of a paged terminal does not appear in the third list and the fourth list at the same time.
  • the paging cause indication information is generated based on an encrypted input parameter; wherein the encrypted input parameter includes at least one of the following:
  • the paging cause or paging cause indication information before encryption of the paging terminal is not limited to.
  • a fourth processing unit configured to execute at least one of the following:
  • the first information is used to indicate at least one of the following:
  • Unexpected paging cause or unexpected paging cause indication information is received
  • the identity of the cell that received the unexpected paging cause or the unexpected paging cause indication information is based on the identity of the cell that received the unexpected paging cause or the unexpected paging cause indication information.
  • the second list or the fourth list includes at least one of the following:
  • the length field is used to indicate the total number of entries included in the second list or the fourth list, and the Entry field carries or does not carry the paging cause indication information of the terminal;
  • the paging cause indication information when carried, it indicates that the terminal is paged because of the carried paging cause;
  • the paging cause indication information includes one of the following:
  • the paging cause of the terminal is the paging cause agreed in the protocol
  • the paging cause indication information of the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information.
  • a third sending unit configured to send downlink signaling to the terminal, where the downlink signaling carries or does not carry first indication information, and the first indication information is used to indicate that the paging message supports carrying a paging reason;
  • the downlink signaling includes one of the following:
  • the paging message carries or does not carry paging cause indication information, including at least one of the following:
  • the paging message carries the second paging ID allocated by the network side device for each paging terminal that needs or supports receiving the paging cause;
  • the paging message carries the third paging ID corresponding to each paging terminal that needs or supports receiving the paging reason, wherein the third paging ID is the first paging ID of the network side device based on the paging terminal. Obtained from at least one of the call ID and the derivation method agreed in the agreement;
  • the paging message is scheduled by the PDCCH scrambled using the RNTI corresponding to the paging cause, wherein the RNTI corresponding to different paging causes is obtained by the explicit instruction of the network side device or the derivation method agreed in the protocol.
  • the second receiving unit is configured to receive second information reported by the terminal, where the second information is used to indicate that the terminal needs or supports receiving the paging cause, or indicates that the terminal does not need or does not support receiving the paging cause.
  • the paging apparatus provided in this embodiment of the present application can implement each process implemented by the method embodiment in FIG. 3 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • an embodiment of the present application further provides a communication device 600, including a processor 601, a memory 602, a program or instruction stored in the memory 602 and executable on the processor 601,
  • a communication device 600 including a processor 601, a memory 602, a program or instruction stored in the memory 602 and executable on the processor 601
  • the communication device 600 is a terminal
  • the program or instruction is executed by the processor 601
  • each process of the foregoing paging method embodiments can be implemented, and the same technical effect can be achieved.
  • the communication device 600 is a network-side device
  • the program or instruction is executed by the processor 601
  • each process of the above-mentioned paging method embodiments can be realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • An embodiment of the present application further provides a terminal, including a processor and a communication interface, where the communication interface is configured to receive a paging message, the paging message carries or not paging cause indication information, wherein the paging cause indicates The information is used to indicate the paging cause corresponding to the paged terminal that needs or supports receiving the paging cause; the processor is configured to perform the first operation based on the paging message.
  • This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this terminal embodiment, and can achieve the same technical effect.
  • FIG. 7 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710, etc. at least part of the components.
  • the terminal 700 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 710 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 704 may include a graphics processor (Graphics Processing Unit, GPU) 7041 and a microphone 7042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 706 may include a display panel 7061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 707 includes a touch panel 7071 and other input devices 7072 .
  • the touch panel 7071 is also called a touch screen.
  • the touch panel 7071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 7072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be repeated here.
  • the radio frequency unit 701 receives the downlink data from the network side device, and then processes it to the processor 710; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 709 may be used to store software programs or instructions as well as various data.
  • the memory 709 may mainly include a storage program or instruction area and a storage data area, wherein the storage program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 709 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 710 may include one or more processing units; optionally, the processor 710 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 710.
  • the radio frequency unit 701 is configured to receive a paging message, the paging message carries or does not carry paging cause indication information, wherein the paging cause indication information is used to indicate that the paging cause needs or supports receiving the paging cause.
  • the processor 710 is configured to perform a first operation based on the paging message.
  • the terminal receives a paging message, and the paging message carries or does not carry paging cause indication information, and the paging cause indication information is used to indicate that the paging cause needs or supports receiving the paging cause.
  • the paging reason corresponding to the terminal is called, and based on the paging message, the paging reason is determined so as to further determine the subsequent behavior, which can effectively reduce signaling overhead.
  • the paging message carrying or not carrying the paging cause indication information includes: the paging message carries the first list, or the paging message carries the first list and the second list,
  • each element entry in the described first list includes a first paging ID of a paged terminal
  • each entry in the described second list includes a paging cause indication information of a paged terminal
  • the ordering of the paging cause indication information of the paging terminals in the second list corresponds to the ordering of the first paging IDs of the first M or last M paging terminals in the first list, wherein M is the second The total number of entries contained in the list.
  • processor 710 is further configured to:
  • the terminal In the case that the terminal is paged, based on the second list, determine a paging reason for the terminal;
  • the determining whether the terminal is paged includes at least one of the following:
  • the terminal If the first paging ID of the terminal matches the first paging ID contained in the Nth or last Nth entry in the first list, it is determined that the terminal is paged, and N is greater than or equal to 1 A positive integer less than or equal to the total number of entries contained in the first list;
  • the terminal If the first paging ID of the terminal fails to match with the first paging ID included in all entries in the first list, it is determined that the terminal is not paged;
  • determining the paging reason of the terminal based on the second list includes at least one of the following:
  • the network side device determines that the network side device does not support paging reason sending.
  • obtaining the paging cause indication information corresponding to the Nth or last Nth entry in the second list, and determining the paging cause of the terminal including at least one of the following:
  • the paging cause of the terminal is determined according to the paging cause indication information
  • the terminal determines the paging cause of the terminal based on a protocol agreement; determine The paging cause indication information corresponding to the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information.
  • processor 710 is further configured to:
  • the downlink signaling carries or does not carry first indication information, where the first indication information is used to indicate that the paging message supports carrying a paging cause;
  • the terminal determines that the current cell does not support the sending of paging reasons; or,
  • the terminal determines that the current cell supports sending of paging reasons
  • the downlink signaling includes one of the following:
  • the determining the paging cause of the terminal based on the second list further includes:
  • the terminal determines that the network-side device does not support the sending of paging reasons.
  • the paging message carrying or not carrying paging cause indication information includes: the paging message carries at least one of the third list and the fourth list,
  • each entry in the third list includes a first paging ID of a paged terminal
  • each entry in the described fourth list includes a first paging ID of a paged terminal and paging cause indication information corresponding to the first paging ID;
  • the first paging ID of a paged terminal does not appear in the third list and the fourth list at the same time.
  • processor 710 is further configured to:
  • the terminal determines that the network side device does not support paging reason sending;
  • the terminal If the first paging ID of the terminal matches the first paging ID contained in the Pth entry in the fourth list successfully, obtain the paging cause indication information contained in the Pth entry in the fourth list , determine the paging reason of the terminal;
  • the terminal determines that it is not paged
  • P is a positive integer greater than or equal to 1.
  • obtaining the paging cause indication information contained in the Pth entry in the fourth list, and determining the paging cause of the terminal including:
  • the paging cause of the terminal is determined according to the paging cause indication information
  • the paging cause indication information contained in the Pth entry is implicitly carried or not carried, perform one of the following: determine the paging cause of the terminal based on the protocol agreement; determine the paging cause indication information corresponding to the terminal and The paging cause indication information corresponding to the previous entry that explicitly carries or carries the paging cause indication information is the same.
  • the determining the paging cause of the terminal based on the protocol agreement includes:
  • the paging cause of the terminal is a paging triggered by a non-voice service or other paging causes complementary to the paging cause defined by the protocol.
  • the paging cause indication information is generated based on an encrypted input parameter; wherein the encrypted input parameter includes at least one of the following:
  • the first processing unit is used for:
  • processor 710 is further configured to execute at least one of the following:
  • the paging cause indication information or the paging cause is an unexpected value, it is determined that the paging cause indication information or the paging cause is invalid;
  • the first information is used to indicate at least one of the following:
  • Unexpected paging cause or unexpected paging cause indication information is received
  • the identity of the cell that received the unexpected paging cause or the unexpected paging cause indication information is based on the identity of the cell that received the unexpected paging cause or the unexpected paging cause indication information.
  • the second list or the fourth list includes at least one of the following:
  • the length field is used to indicate the total number of entries included in the second list or the fourth list, and the Entry field carries or does not carry the paging cause indication information of the terminal;
  • the paging cause indication information when carried, it indicates that the terminal is paged because of the carried paging cause;
  • the paging cause indication information includes one of the following:
  • the paging cause of the terminal is the paging cause agreed in the protocol
  • the paging cause indication information of the terminal is the same as the paging cause indication information corresponding to the previous entry carrying the paging cause indication information.
  • the paging message carries or does not carry paging cause indication information, including at least one of the following:
  • the paging message carries the second paging ID allocated by the network side device to the paging terminal that needs or supports receiving the paging cause;
  • the paging message carries the third paging ID corresponding to the paging terminal that needs or supports receiving the paging reason, wherein the third paging ID is based on the first paging ID of the paging terminal and the protocol agreement obtained by at least one of the derivation methods;
  • the paging message is scheduled by the PDCCH scrambled using the RNTI corresponding to the paging cause, wherein the RNTI corresponding to different paging causes is obtained by the explicit instruction of the network side device or the derivation method agreed in the protocol.
  • processor 710 is further configured to execute at least one of the following:
  • the paging reason is determined according to the RNTI.
  • the radio frequency unit 701 is also used for:
  • the second information is reported to the network side device, where the second information is used to indicate that the terminal needs or supports receiving the paging cause, or indicates that the terminal does not need or does not support receiving the paging cause.
  • An embodiment of the present application further provides a network-side device, including a processor and a communication interface, where the communication interface is used to send a paging message to a terminal, where the paging message carries or does not carry paging cause indication information, wherein the paging message
  • the paging cause indication information is used to indicate the paging cause corresponding to the paged terminal that needs or supports receiving the paging cause.
  • This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation manner of the above-mentioned method embodiment can be applied to this network-side device embodiment, and can achieve the same technical effect.
  • the network side device 800 includes: an antenna 801 , a radio frequency device 802 , and a baseband device 803 .
  • the antenna 801 is connected to the radio frequency device 802 .
  • the radio frequency device 802 receives information through the antenna 801, and sends the received information to the baseband device 803 for processing.
  • the baseband device 803 processes the information to be sent and sends it to the radio frequency device 802
  • the radio frequency device 802 processes the received information and sends it out through the antenna 801 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 803 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 803 .
  • the baseband apparatus 803 includes a processor 804 and a memory 805 .
  • the baseband device 803 may include, for example, at least one baseband board on which multiple chips are arranged. As shown in FIG. 8 , one of the chips is, for example, the processor 804 , which is connected to the memory 805 to call the program in the memory 805 to execute The network-side device shown in the above method embodiments operates.
  • the baseband device 803 may further include a network interface 806 for exchanging information with the radio frequency device 802, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in the embodiment of the present invention further includes: instructions or programs stored in the memory 805 and executable on the processor 804, and the processor 804 invokes the instructions or programs in the memory 805 to execute the modules shown in FIG. 5 .
  • the embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium.
  • a program or an instruction is stored on the readable storage medium.
  • the processor is the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the paging method embodiments described above.
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is configured to run a program or an instruction to implement the paging method embodiments described above.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.

Landscapes

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

Abstract

本申请公开了一种寻呼方法、装置、终端及网络侧设备，属于通信技术领域，本申请实施例的寻呼方法包括：终端接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；终端基于所述寻呼消息，执行第一操作。

Description

寻呼方法、装置、终端及网络侧设备
相关申请的交叉引用
本申请要求于2021年04月01日提交的申请号为2021103579711，发明名称为“寻呼方法、装置、终端及网络侧设备”的中国专利申请的优先权，其通过引用方式全部并入本申请。
技术领域
本申请属于通信技术领域，具体涉及一种寻呼方法、装置、终端及网络侧设备。
背景技术
对于多卡设备(Multi-SIM device)，以下以双卡设备为例，若卡1正在通信；卡2突然来了寻呼；目前，部分双卡设备会断开卡1的通信，以便响应卡2的寻呼。但是，在不知道触发卡2寻呼的业务类型的情况下，断开卡1的通信，响应卡2的寻呼可能导致得不偿失，例如：卡1正在进行游戏，卡2寻呼由一个短信触发，为了接收卡2短信而打断卡1的游戏会造成不好的用户体验。
因此，在Rel-17中，3GPP决定在寻呼消息中携带寻呼原因paging cause，以便用户设备(User Equipment，UE)根据该paging cause，决定是否需要响应网络(Network，NW)侧发送的寻呼消息。但是仅有部分UE需要接收paging cause，还有部分UE是不需要接收paging cause的，例如，不支持Paging cause的UE，多卡设备中仅有一个UE实体工作时。
相关技术未考虑到UE是否支持或需要空口paging cause，对于不支持或不需要空口paging cause的UE，若寻呼时在空口携带其paging cause则会带来无谓的信令开销。
发明内容
本申请实施例提供一种寻呼方法、装置、终端及网络侧设备，能够解决相关技术未考虑到UE是否支持或需要空口paging cause，在寻呼消息中携带paging cause所带来的信令开销较大的问题。
第一方面，提供了一种寻呼方法，应用于终端，该方法包括：
终端接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；
终端基于所述寻呼消息，执行第一操作。
第二方面，提供了一种寻呼方法，应用于网络侧设备，该方法包括：
网络侧设备向终端发送寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。
第三方面，提供了一种寻呼装置，包括：
第一接收单元，用于接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；
第一处理单元，用于基于所述寻呼消息，执行第一操作。
第四方面，提供了一种寻呼装置，包括：
第二发送单元，用于向终端发送寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。
第五方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤。
第六方面，提供了一种终端，包括处理器及通信接口，其中，所述通信接口用于接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息， 其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；所述处理器用于基于所述寻呼消息，执行第一操作。
第七方面，提供了一种网络侧设备，该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的寻呼方法的步骤。
第八方面，提供了一种网络侧设备，包括处理器及通信接口，其中，所述通信接口用于向终端发送寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的寻呼方法的步骤，或者实现如第二方面所述的寻呼方法的步骤。
第十方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的寻呼方法，或实现如第二方面所述的寻呼方法。
第十一方面，提供了一种计算机程序/程序产品，所述计算机程序/程序产品被存储在非易失的存储介质中，所述程序/程序产品被至少一个处理器执行以实现如第一方面所述的寻呼方法的步骤，或实现如第二方面所述的寻呼方法的步骤。
在本申请实施例中，终端通过接收寻呼消息，所述寻呼消息中携带或未携带寻呼原因指示信息，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因，基于该寻呼消息，确定寻呼原因，以便进一步确定后继行为，考虑了终端是否支持或需要空口paging cause，可以有效减少信令开销。
附图说明
图1为本申请实施例可应用的一种无线通信系统的结构示意图；
图2为本申请实施例提供的寻呼方法的流程示意图之一；
图3为本申请实施例提供的寻呼方法的流程示意图之二；
图4为本申请实施例提供的寻呼装置的结构示意图之一；
图5为本申请实施例提供的寻呼装置的结构示意图之二；
图6为本申请实施例提供的通信设备的结构示意图；
图7为实现本申请实施例的一种终端的结构示意图；
图8为本申请实施例提供的网络侧设备的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier  Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的结构示意图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：智能手表、手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过一些实施例及其应用场景对本申请实施例提供的寻呼方法进行详细地说明。
图2为本申请实施例提供的寻呼方法的流程示意图之一，如图2所示，该方法包括以下步骤：
步骤200、终端接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息；
可选的，终端接收网络侧设备发送的寻呼Paging消息，所述寻呼消息携带或未携带寻呼原因Paging Cause指示信息。
其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。例如，所述寻呼原因指示信息指示寻呼是由语音业务(如VoNR)触发的。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息是指所述寻呼消息可选携带寻呼原因指示信息。
可选的，若网络侧设备不支持发送被寻呼终端的寻呼原因，或者，被寻呼终端不支持或不需要接收寻呼原因，则寻呼消息不携带该被寻呼终端的寻呼原因指示信息。
可选的，若被寻呼终端支持或需要接收寻呼原因，且该被寻呼终端的寻呼原因为协议定义的寻呼原因(例如，语音业务)，则寻呼消息携带该被寻呼终端的寻呼原因指示信息。
可选的，若被寻呼终端支持或需要接收寻呼原因，且该被寻呼终端的寻呼原因不是协议定义的寻呼原因(例如，为非语音业务)，则寻呼消息可以不携带该被寻呼终端的寻呼原因指示信息，但是需要指示被寻呼终端的寻呼原因指示信息未被携带。
可选的，所述寻呼原因指示信息可以是编码信息，例如，编码000表示寻呼原因A，编码001表示寻呼原因B。
可选的，所述寻呼原因指示信息可以是寻呼优先级；即NW在空口发送的不是具体的触发寻呼的业务类型，而是触发寻呼的业务对应的优先级；触发寻呼的业务对应的优先级可以由协议规定或者UE和NW协商，或者运营商设定；寻呼优先级可以是一个编号，例如1,2...N，N种优先级，对应的优先级依次递增或递减。
需要说明的是，所述寻呼原因指示信息还可以是其他形式的用于指示寻 呼原因的信息。
步骤201、终端基于所述寻呼消息，执行第一操作。
可选的，终端基于所述寻呼消息，确定被寻呼，并进一步确定寻呼消息是否携带该终端的寻呼原因指示信息，若可以从寻呼消息中获取该终端的寻呼原因指示信息，则根据该寻呼原因指示信息确定该终端的寻呼原因，以便终端进一步确定后继行为。
可选的，终端基于所述寻呼消息，确定被寻呼，并进一步基于该寻呼消息获取该终端的寻呼原因指示信息，若无法获取到该终端的寻呼原因指示信息，则确定网络侧设备不支持该终端的寻呼原因发送。
可选的，终端基于所述寻呼消息，确定未被寻呼。
可选的，终端确定该终端寻呼原因之后，还包括：
终端基于所述寻呼原因，响应所述寻呼消息或不响应所述寻呼消息。
例如，双卡设备，UE1正在进行游戏，此时，UE2收到一个寻呼指示，对应的paging cause为VoNR，则双卡设备可能会选择响应UE2的寻呼指示；若UE2收到一个寻呼消息，对应的paging cause为短信，双卡设备可能会选择暂时忽略UE2的寻呼指示，如等到UE1的游戏结束，才在UE2发起连接建立过程，响应之前的寻呼指示。
可选的，所述终端为需要或支持接收寻呼原因的被寻呼终端。如对应于插入双卡终端的UE，或向网络上报需要接收寻呼原因的UE。
在本申请实施例中，终端通过接收寻呼消息，所述寻呼消息中可选携带寻呼原因指示信息，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因，基于该寻呼消息，确定寻呼原因，以便进一步确定后继行为，考虑了终端是否支持或需要空口paging cause，可以有效减少信令开销。
在一些可选的实施例中，所述寻呼消息中携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第一列表，或者，所述寻呼消息携带第一列表和第二列表，
其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID；
其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
相关技术中一条空口paging消息携带有PagingRecordList，该PagingRecordList中有最少1个，最多MaxNrofPageRec个PagingRecord，每一个PagingRecord中，携带一个被寻呼UE的寻呼标识(UE_Identity)。即一条paging消息可以指示最多MaxNrofPageRec个被寻呼UE，这些UE中有些支持或需要接收Paging cause；剩下的不支持或不需要。
可选的，第一寻呼ID是指遗留legacy UE ID，如第五代系统临时移动订户身份(Fifth Generation System Temporary Mobile Subscriber Identity，5G-S-TMSI)，完整的非激活状态无线网络临时标识(full inactive Radio Network Temporary Identifier，full I-RNTI)。
可以理解的是，所述第一列表用于指示被寻呼终端的第一寻呼标识ID，所述第一列表包含多个entry，第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID。
可选的，所述第一列表为PagingRecordList。
不同于现有寻呼消息，在本申请实施例中，所述寻呼消息中不仅携带第一列表，即PagingRecordList，还可选携带第二列表。
所述第二列表包含多个entry，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息。其中，寻呼原因指示信息是可选携带的。
所述第二列表包含M个元素/条目entry，即所述第二列表的长度为M，表示网络侧设备指示了M个终端的寻呼原因，M为大于等于1的正整数。
可选的，第一列表和第二列表具有如下对应关系：所述第二列表中被寻 呼终端的寻呼原因排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的。
可以理解的是，第一列表中的第i个entry包含的第一寻呼ID与第二列表中的第i个entry包含的寻呼原因指示信息是对应的。
例如：一个UE的寻呼ID和第一列表中第i个entry匹配成功，该UE的寻呼原因位于第二列表中的对应位置，即第i个entry；或一个UE的寻呼ID和第一列表中倒数第j个entry匹配成功，该UE的寻呼原因位于第二列表中的对应位置，即倒数第j个entry。
可选的，第一列表包含的entry总数为La，La大于等于第二列表的entry总数M，即第一列表中的前M个之后或后M个之前的第一寻呼ID对应的UE不需要或不支持接收Paging Cause。
在本申请实施例中，终端通过接收寻呼消息，所述寻呼消息携带第一列表，可选携带第二列表，所述寻呼原因指示信息通过第二列表指示，基于该寻呼消息，确定寻呼原因，以便进一步确定后继行为，由于第二列表中指示的是需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因，可以有效减少信令开销。
可选的，所述终端基于所述寻呼消息，执行第一操作，包括：
终端基于所述第一列表，确定所述终端是否被寻呼；
在所述终端被寻呼的情况下，终端基于所述第二列表，确定所述终端的寻呼原因；
其中，所述确定所述终端是否被寻呼，包括以下至少之一：
若所述终端的第一寻呼ID和所述第一列表中的第N个或倒数第N个entry包含的第一寻呼ID匹配成功，确定所述终端被寻呼，N为大于等于1且小于等于第一列表包含的entry总数的正整数；
若所述终端的第一寻呼ID和所述第一列表中的所有entry包含的第一寻呼ID匹配失败，确定所述终端未被寻呼；
其中，所述终端基于所述第二列表，确定所述终端的寻呼原因，包括以 下至少之一：
所述终端获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因；
在所述第二列表包含的entry总数小于N的情况下，所述终端确定网络侧设备不支持寻呼原因发送。
可选的，所述终端的第一寻呼ID和所述第一列表中的第N个或倒数第N个entry包含的第一寻呼ID匹配成功是指所述终端的第一寻呼ID和所述第一列表中的第N个entry包含的第一寻呼ID相同；
所述终端的第一寻呼ID和所述第一列表中的所有entry包含的第一寻呼ID匹配失败是指所述终端的第一寻呼ID与所述第一列表中的所有entry包含的第一寻呼ID均不相同。
可选的，若终端被寻呼，即所述终端的第一寻呼ID和所述第一列表中的第N个或倒数第N个entry包含的第一寻呼ID匹配成功，则可以进一步基于第二列表确定该终端的寻呼原因，该终端寻呼原因位于第二列表中的对应位置，即第N个entry或倒数第N个entry。
可选的，若所述第二列表包含的entry总数大于等于N，即第二列表中存在第N个或倒数第N个entry，则获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，进而根据该寻呼原因指示信息，确定所述终端的寻呼原因。
进一步地，所述终端获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因，包括以下至少之一：
若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息被携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息未被携带，则执行以下之一：所述终端基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可以理解的是，若终端能够从第二列表中获取到第N个或倒数第N个entry对应的寻呼原因指示信息，表示网络侧设备指示了该终端的寻呼原因。
可选的，若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息被携带，则根据该entry对应的寻呼原因指示信息，确定寻呼原因。例如entry指示UE因为语音业务被寻呼，则UE确定自已因为语音业务被寻呼。
可选的，若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息未被携带，即不出现，则所述终端基于协议约定确定所述终端的寻呼原因；或者，确定所述终端对应的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。这样做可以节省空口信令开销。例如，在该终端的寻呼原因为非语言业务时，第N个或倒数第N个entry对应的寻呼原因指示信息未携带；或者，在该终端的寻呼原因与前一个entry对应的终端的寻呼原因相同时，则该终端对应的寻呼原因指示信息可以不出现。
为了便于理解寻呼原因指示信息未被携带，可以通过第二列表的长度和entry域来进一步说明。其中，Entry域用于显式指示终端的寻呼原因；长度用于指示第二列表包含的entry总数。例如，长度域为4，表示有4个被寻呼终端(UE_ID1,UE_ID2,UE_ID3,UE_ID4)的寻呼原因被指示了，Entry域中的一个bit信息指示携带或未携带协议定义的寻呼原因，如语音业务，Entry域：第一个entry为1，第二个entry为0，第三个entry为1，第四个entry为0，在一种实施方式中，该Entry域表示UE_ID1和UE_ID3的寻呼原因为协议定义的寻呼原因，而UE_ID2和UE_ID4的寻呼原因为与协议定义的寻呼原因互补的寻呼原因，如非语音业务。在另一实施方式中，终端对应的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同，即UE_ID2的寻呼原因与UE_ID1相同。
可选的，在所述第二列表包含的entry总数小于N的情况下，所述终端确定网络侧设备不支持寻呼原因发送。
若第二列表包含的entry总数M小于N，即第二列表中不存在第N个或倒数第N个entry，则表示网络侧设备未指示该终端的寻呼原因，网络侧设备未指示该终端的寻呼原因包括以下情形：网络侧设备不支持寻呼原因发送。也即网络侧设备不支持该终端的寻呼原因发送。
网络侧设备不支持寻呼原因发送包括：接入网不支持和/或核心网不支持。
一个cell可以连到多个核心网(假设CN1支持，CN2不支持)，例如，UE1连到CN1，UE2连到CN2，若接入网/cell支持UE1的寻呼原因发送，但是核心网CN1不支持UE1的寻呼原因发送，则第二列表不包含UE1的寻呼原因指示信息。
在上述实施例的基础上，可选的，所述寻呼方法还包括：
接收下行信令，所述下行信令携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
在所述下行信令未携带第一指示信息的情况下，终端确定当前小区不支持寻呼原因发送；或者，
在所述下行信令携带第一指示信息的情况下，终端确定当前小区支持寻呼原因发送；
其中，所述下行信令包括以下之一：
寻呼消息；
系统信息；
下行调度信令。
可选的，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因，也即当前小区支持寻呼原因发送。
若下行信令中携带了第一指示信息，即表示当前小区支持寻呼原因发送。
一种实施方式中，寻呼消息携带或未携带所述第一指示信息。
一种实施方式中，系统信息携带或未携带所述第一指示信息；例如，在小区广播消息中，如SIBx中携带第一指示信息，指示网络侧设备支持所述终端的寻呼原因发送。
一种实施方式中，在下行调度信令中携带或未携带所述第一指示信息。
在上述实施例的基础上，可选的，所述终端基于所述第二列表，确定所述终端的寻呼原因，还包括：
在所述下行信令携带第一指示信息，且所述寻呼消息未携带第二列表的情况下，终端确定网络侧设备不支持寻呼原因发送。
可以理解的是，下行信令携带了第一指示信息，说明当前小区支持寻呼原因发送，但是同时寻呼消息中却未携带第二列表，即第二列表包含0个entry，表示没有终端的寻呼原因被指示，在这种情形下，终端确定网络侧设备不支持寻呼原因发送。进一步地，终端确定核心网不支持寻呼原因发送。
在另一些可选的实施例中，所述寻呼消息携带或未携带寻呼原因指示信息包括：
所述寻呼消息携带第三列表和第四列表中的至少之一，
其中，所述第三列表中的每个entry包含一个被寻呼终端的第一寻呼ID；
其中，所述第四列表中的每个entry包含一个被寻呼终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表和第四列表中。
可选的，若终端是需要或支持接收寻呼原因的被寻呼终端，但因为网络侧设备不支持寻呼原因发送，该终端的寻呼ID会被包含在第三列表中。
可选的，若终端不需要或不支持接收寻呼原因，则该终端的寻呼ID会被包含在第三列表中。
可选的，若终端是需要或支持接收寻呼原因的被寻呼终端，且网络侧设备支持该终端的寻呼原因发送，该终端的寻呼ID和寻呼原因指示信息会被包含在第四列表中。
例如，一个cell可以连到多个核心网，假设接入网/cell支持寻呼原因发送，核心网CN1支持寻呼原因发送，CN2不支持寻呼原因发送，假设UE1连到CN1，UE2连到CN2，Paging message由cell发送，则UE1的第一寻呼 ID将会被包含在第四列表；UE2的第一寻呼ID则包含在第三列表中。
可选的，第四列表中的第一寻呼ID对应的寻呼原因指示信息是可选携带的。
本申请实施例通过在寻呼消息中携带上述第三列表和第四列表中的至少之一，终端基于该寻呼消息，确定寻呼原因，以便进一步确定后继行为，可以有效减少信令开销。
在上述实施例的基础上，可选的，所述终端基于所述寻呼消息，执行第一操作，包括以下至少之一：
若所述终端的第一寻呼ID和第三列表中的第P个entry包含的第一寻呼ID匹配成功，则终端确定网络侧设备不支持寻呼原因发送；
若所述终端的第一寻呼ID和第四列表中的第P个entry包含的第一寻呼ID匹配成功，则获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因；
若所述终端的第一寻呼ID，与所述第三列表和第四列表中的所有entry包含的第一寻呼ID均匹配失败，则终端确定未被寻呼；
其中，P为大于等于1的正整数。
进一步地，所述获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因，包括：
若所述第四列表中的第P个entry包含的寻呼原因指示信息被携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
若第P个entry包含的寻呼原因指示信息未被携带，则执行以下之一：基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个显式携带或携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可选的，若所述第四列表中的第P个entry包含的寻呼原因指示信息被携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因，例如entry指示UE因为语音业务被寻呼，则UE确定自已因为语音业务被寻呼。
可选的，若所述第四列表中的第P个或倒数第P个entry对应的寻呼原因指示信息未被携带，即不出现，则所述终端基于协议约定确定所述终端的寻呼原因；或者，确定所述终端对应的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。这样做可以节省空口信令开销。例如，在该终端的寻呼原因为非语言业务时，第P个或倒数第P个entry对应的寻呼原因指示信息未携带；或者，在该终端的寻呼原因与前一个entry对应的终端的寻呼原因相同时，则该终端对应的寻呼原因指示信息可以不出现。
对于寻呼原因指示信息未被携带的理解可以参考前述实施例，在此不再赘述。
可选的，所述基于协议约定确定所述终端的寻呼原因，包括：
确定所述终端的寻呼原因为非语音业务触发的寻呼或与协议定义的寻呼原因互补的其他寻呼原因。
需要说明的是，上述实施例中提到的基于协议约定确定所述终端的寻呼原因，均可理解为确定所述终端的寻呼原因为非语音业务触发的寻呼或与协议定义的寻呼原因互补的其他寻呼原因。
可选的，所述寻呼原因指示信息基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
被寻呼终端的全部或部分终端标识UE ID；
网络侧设备和被寻呼终端共享的密钥；
被寻呼终端的加密前的寻呼原因或寻呼原因指示信息；
其中，所述终端基于所述寻呼消息，执行第一操作，包括：
所述终端获取所述终端对应的寻呼原因指示信息；
对所述寻呼原因指示信息进行解密，确定所述终端的寻呼原因。
在一些可选的实施例中，寻呼原因指示信息是加密的，只有被寻呼UE才能解密寻呼原因。
可选的，网络侧设备可以基于加密输入参数生成寻呼原因指示信息。
可选的，可以基于被寻呼终端的全部或部分终端标识UE ID、网络侧设备和被寻呼终端共享的密钥以及加密前的寻呼原因或寻呼原因指示信息中的至少一项生成寻呼原因指示信息。
相应地，终端获取所述终端对应的寻呼原因指示信息之后，需要对该寻呼原因指示信息进行解密，从而获得终端的寻呼原因。
在上述实施例的基础上，可选的，所述执行第一操作之后，所述方法还包括以下至少一项：
在终端检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，终端确定所述寻呼原因指示信息或寻呼原因无效；
在终端检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，终端向网络侧设备上报第一信息；
终端接收网络侧设备发送的用于后继寻呼原因解密的安全参数。
即终端获取到寻呼原因指示信息之后，若检测到所述寻呼原因指示信息或寻呼原因为非预期取值，则确定所述寻呼原因指示信息或寻呼原因无效。
可选的，终端确定所述寻呼原因指示信息或寻呼原因无效，并上报第一信息，其中，所述第一信息用于指示以下至少一项：收到非预期寻呼原因或非预期寻呼原因指示信息；收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
可选的，网络侧设备接收到终端上报的第一信息之后，会向终端发送用于后继寻呼原因解密的安全参数，终端接收网络侧设备发送的用于后继寻呼原因解密的安全参数。
可选的，所述第二列表或第四列表包括以下至少一项：
长度域；
Entry域；
其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被 寻呼；
当寻呼原因指示信息未被携带时，包括以下之一：
终端的寻呼原因为协议约定的寻呼原因；
终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
例如，第二列表中包含：长度指示：N；以及N个entry。
对于每一个entry：有一个bit指示IE pagingCause-r17是否被携带；若指示被携带，表明寻呼原因是voice；若指示未被携带，表明寻呼原因是non-voice。
也就是说，N个entry是一定出现的，IE pagingCause-r17是可选出现的。
因为只定义了一个pagingCause-r17取值，所以，该IE pagingCause-r17即使出现，也不用额外的bit指示paging cause是什么了。若定义了两个pagingCause取值(例如A和B)，那么在IE pagingCause-r17出现的情况下，需要有额外1bit指示pagingCause是A还是B。
在一种实施方式中，当寻呼原因指示信息未被携带时，表示终端的寻呼原因为协议约定的寻呼原因。
在另一种实施方式中，当寻呼原因指示信息未被携带时，表示终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。也就是说，在该终端的寻呼原因与前一个entry对应的终端的寻呼原因相同时，则该终端对应的寻呼原因指示信息可以不出现。从而节省信令开销。
在另一些可选的实施例中，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是基于被寻呼终端的第一寻呼ID和协议约定的推导方式至少之一得到的；
所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
所述终端基于所述寻呼消息，执行第一操作，包括以下至少之一：
终端根据所述第二寻呼ID确定寻呼原因；
终端根据所述第三寻呼ID确定寻呼原因；
终端根据RNTI确定寻呼原因。
可选的，寻呼原因可以通过寻呼ID隐式携带。
可选的，所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
或者，所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是基于被寻呼终端的第一寻呼ID和协议约定的推导方式至少之一得到的；
例如，NW预设两个寻呼原因，A和B；同时，NW为每个需要接收寻呼原因的UE分配两个寻呼ID，ID_A和ID_B，分别对应寻呼原因A和B。
当寻呼是由于原因A触发的，则NW在PagingRecordList中，携带ID_A来寻呼UE；当寻呼是由于原因B触发的，则NW在PagingRecordList中，携带ID_B来寻呼UE。
可选的，ID_A和ID_B也可以根据被寻呼终端的第一寻呼ID和协议约定的推导方式至少之一得到。
其中，不论是使用ID_A还是ID_B寻呼UE，UE监听寻呼的时刻不发生变化，这样可以降低UE的实现复杂度。
可选的，所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
例如，NW预设两个RNTI(RNTI_A和RNTI_B)，分别对应预设两个寻呼原因，A和B。当寻呼是由于原因A触发的，则NW使用RNTI_A加扰的 PDCCH调度，在对应PDSCH信道传输paging message，其中PagingRecordList中，携带被寻呼UE的寻呼标识；当寻呼是由于原因B触发的，则NW使用RNTI_B加扰的PDCCH调度，在对应PDSCH信道传输paging message，其中PagingRecordList中，携带被寻呼UE的寻呼标识。
可选的，所述终端接收寻呼消息之前，还包括：
终端向网络侧设备上报第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
可选的，UE在接入网络后，向网络上报自己是否需要或支持接收寻呼原因。多卡设备在启用多卡时，其UE可以上报自己需要或支持接收寻呼原因。
图3为本申请实施例提供的寻呼方法的流程示意图之二。如图3所示，该方法包括以下步骤：
步骤300、网络侧设备向终端发送寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息。
可选的，网络侧设备向终端发送寻呼Paging消息，所述寻呼消息携带或未携带寻呼原因Paging Cause指示信息。
其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。例如，所述寻呼原因指示信息指示寻呼是由语音业务(如VoNR)触发的。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息是指所述寻呼消息可选携带寻呼原因指示信息。
可选的，若网络侧设备不支持发送被寻呼终端的寻呼原因，或者，被寻呼终端不支持或不需要接收寻呼原因，则寻呼消息不携带该被寻呼终端的寻呼原因指示信息。
可选的，若被寻呼终端支持或需要接收寻呼原因，且该被寻呼终端的寻呼原因为协议定义的寻呼原因(例如，语音业务)，则寻呼消息携带该被寻呼终端的寻呼原因指示信息。
可选的，若被寻呼终端支持或需要接收寻呼原因，且该被寻呼终端的寻呼原因不是协议定义的寻呼原因(例如，为非语音业务)，则寻呼消息可以不携带该被寻呼终端的寻呼原因指示信息，但是需要指示被寻呼终端的寻呼原因指示信息未被携带。
可选的，所述寻呼原因指示信息可以是编码信息，例如，编码000表示寻呼原因A，编码001表示寻呼原因B。
可选的，所述寻呼原因指示信息可以是寻呼优先级；即NW在空口发送的不是具体的触发寻呼的业务类型，而是触发寻呼的业务对应的优先级；触发寻呼的业务对应的优先级可以由协议规定或者UE和NW协商，或者运营商设定；寻呼优先级可以是一个编号，例如1,2...N，N种优先级，对应的优先级依次递增或递减。
需要说明的是，所述寻呼原因指示信息还可以是其他形式的信息。
在本申请实施例中，网络侧设备发送寻呼消息，所述寻呼消息中可选携带寻呼原因指示信息，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因，可以有效减少信令开销。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息中携带第一列表，或者，所述寻呼消息携带第一列表和第二列表，
其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID；
其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
可以理解的是，所述第一列表用于指示被寻呼终端的第一寻呼标识ID，所述第一列表包含多个entry，第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID。
不同于现有寻呼消息，在本申请实施例中，所述寻呼消息中不仅携带第一列表，即PagingRecordList，还可选携带第二列表。
所述第二列表包含多个entry，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息。其中，寻呼原因指示信息是可选携带的。
所述第二列表包含M个元素/条目entry，即所述第二列表的长度为M，表示网络侧设备指示了M个终端的寻呼原因，M为大于等于1的正整数。
可选的，第一列表和第二列表具有如下对应关系：所述第二列表中被寻呼终端的寻呼原因排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的。
可以理解的是，第一列表中的第i个entry包含的第一寻呼ID与第二列表中的第i个entry包含的寻呼原因指示信息是对应的。
例如：一个UE的寻呼ID和第一列表中第i个entry匹配成功，该UE的寻呼原因位于第二列表中的对应位置，即第i个entry；或一个UE的寻呼ID和第一列表中倒数第j个entry匹配成功，该UE的寻呼原因位于第二列表中的对应位置，即倒数第j个entry。
可选的，第一列表包含的entry总数为La，La大于等于第二列表的entry总数M，即第一列表中的前M个之后或后M个之前的第一寻呼ID对应的UE不需要或不支持接收Paging Cause。
在本申请实施例中，网络侧设备发送寻呼消息，所述寻呼消息携带第一列表，可选携带第二列表，所述寻呼原因指示信息通过第二列表指示，由于第二列表中指示的是需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因，可以有效减少信令开销。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息中携带第三列表和第四列表中的至少之一，
其中，所述第三列表中的每个元素entry包含一个终端的第一寻呼ID；
其中，所述第四列表中的每个entry包含一个终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表和第四列表中。
可选的，若终端是需要或支持接收寻呼原因的被寻呼终端，但因为网络侧设备不支持寻呼原因发送，则该终端的寻呼ID会被包含在第三列表中。
可选的，若终端不需要或不支持接收寻呼原因，则该终端的寻呼ID会被包含在第三列表中。
可选的，若终端是需要或支持接收寻呼原因的被寻呼终端，且网络侧设备支持该终端的寻呼原因发送，该终端的寻呼ID和寻呼原因指示信息会被包含在第四列表中。
例如，一个cell可以连到多个核心网，假设接入网/cell支持寻呼原因发送，核心网CN1支持寻呼原因发送，CN2不支持寻呼原因发送，假设UE1连到CN1，UE2连到CN2，Paging message由cell发送，则UE1的第一寻呼ID将会被包含在第四列表；UE2的第一寻呼ID则包含在第三列表中。
可选的，第四列表中的第一寻呼ID对应的寻呼原因指示信息是可选携带的。
在本申请实施例中，网络侧设备通过在寻呼消息中携带上述第三列表和第四列表中的至少之一，可以有效减少信令开销。
可选的，所述寻呼原因指示信息基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
被寻呼终端的全部或部分终端标识UE ID；
网络侧设备和被寻呼终端共享的密钥；
被寻呼终端的加密前的寻呼原因或寻呼原因指示信息。
在一些可选的实施例中，寻呼原因指示信息是加密的，只有被寻呼UE才能解密寻呼原因。
可选的，网络侧设备可以基于加密输入参数生成寻呼原因指示信息。
可选的，网络侧设备可以基于被寻呼终端的全部或部分终端标识UE ID、网络侧设备和被寻呼终端共享的密钥以及加密前的寻呼原因或寻呼原因指示 信息中的至少一项生成寻呼原因指示信息。
可选的，所述方法还包括以下至少一项：
网络侧设备接收终端发送的第一信息；
网络侧设备向终端发送用于后继寻呼原因解密的安全参数。
可选的，终端获取到寻呼原因指示信息之后，若检测到所述寻呼原因指示信息或寻呼原因为非预期取值，则确定所述寻呼原因指示信息或寻呼原因无效，上报第一信息。
其中，所述第一信息用于指示以下至少一项：收到非预期寻呼原因或非预期寻呼原因指示信息；收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
可选的，网络侧设备接收到终端上报的第一信息之后，会向终端发送用于后继寻呼原因解密的安全参数，终端接收网络侧设备发送的用于后继寻呼原因解密的安全参数。
可选的，所述第二列表或第四列表包括以下至少一项：
长度域；
Entry域；
其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被寻呼；
当寻呼原因指示信息未被携带时，包括以下之一：
终端的寻呼原因为协议约定的寻呼原因；
终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
例如，第二列表中包含：长度指示：N；以及N个entry。
对于每一个entry：有一个bit指示IE pagingCause-r17是否被携带；若被携带，表明寻呼原因是voice；若未被携带，表明寻呼原因是non-voice。
也就是说，N个entry是一定出现的，IE pagingCause-r17是可选出现的。
因为只定义了一个pagingCause-r17取值，所以，该IE pagingCause-r17即使出现，也不用额外的bit指示paging cause是什么了。若定义了两个pagingCause取值(例如A和B)，那么在IE pagingCause-r17出现的情况下，需要有额外1bit指示pagingCause是A还是B。
在一种实施方式中，当寻呼原因指示信息未被携带时，表示终端的寻呼原因为协议约定的寻呼原因。
在另一种实施方式中，当寻呼原因指示信息未被携带时，表示终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。也就是说，在该终端的寻呼原因与前一个entry对应的终端的寻呼原因相同时，则该终端对应的寻呼原因指示信息可以不出现。从而节省信令开销。
可选的，所述方法还包括：
网络侧设备向终端发送下行信令，所述下行信令携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
其中，所述下行信令包括以下之一：
寻呼消息；
系统信息；
下行调度信令。
可选的，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因，也即当前小区支持寻呼原因发送。
若下行信令中携带了第一指示信息，即表示当前小区支持寻呼原因发送。
一种实施方式中，网络侧设备向终端发送的寻呼消息携带或未携带所述第一指示信息。
一种实施方式中，网络侧设备向终端发送的系统信息携带或未携带所述第一指示信息；例如，在小区广播消息中，如SIBx中携带第一指示信息，指示网络侧设备支持所述终端的寻呼原因发送。
一种实施方式中，网络侧设备向终端发送的下行调度信令中携带或未携带所述第一指示信息。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是网络侧设备基于被寻呼终端的第一寻呼ID和协议约定的推导方式中至少之一得到的；
所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
可选的，寻呼原因可以通过寻呼ID隐式携带。
可选的，所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
或者，所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是网络侧设备基于被寻呼终端的第一寻呼ID和协议约定的推导方式至少之一得到的。
例如，NW预设两个寻呼原因，A和B；同时，NW为每个需要接收寻呼原因的UE分配两个寻呼ID，ID_A和ID_B，分别对应寻呼原因A和B。
当寻呼是由于原因A触发的，则NW在PagingRecordList中，携带ID_A来寻呼UE；当寻呼是由于原因B触发的，则NW在PagingRecordList中，携带ID_B来寻呼UE。
可选的，ID_A和ID_B也可以根据被寻呼终端的第一寻呼ID和协议约定的推导方式至少之一得到。
其中，不论是使用ID_A还是ID_B寻呼UE，UE监听寻呼的时刻不发生变化，这样可以降低UE的实现复杂度。
可选的，所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
例如，NW预设两个RNTI(RNTI_A和RNTI_B)，分别对应预设两个寻呼原因，A和B。当寻呼是由于原因A触发的，则NW使用RNTI_A加扰的PDCCH调度，在对应PDSCH信道传输paging message，其中PagingRecordList中，携带被寻呼UE的寻呼标识；当寻呼是由于原因B触发的，则NW使用RNTI_B加扰的PDCCH调度，在对应PDSCH信道传输paging message，其中PagingRecordList中，携带被寻呼UE的寻呼标识。
可选的，所述方法还包括：
网络侧设备接收终端上报的第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
可选的，UE在接入网络后，向网络上报自己是否需要或支持接收寻呼原因。多卡设备在启用多卡时，其UE可以上报自己需要或支持接收寻呼原因。
网络侧设备接收到该第二信息后，对于需要或支持接收寻呼原因的终端，在寻呼消息中携带该终端的寻呼原因指示信息。对于不需要或不支持接收寻呼原因的终端，则在寻呼消息中不携带该终端的寻呼原因指示信息，从而可以有效减少信令开销。
需要说明的是，本申请实施例提供的寻呼方法，执行主体可以为寻呼装置，或者，该寻呼装置中的用于执行寻呼方法的控制模块。本申请实施例中以寻呼装置执行寻呼方法为例，说明本申请实施例提供的寻呼装置。
图4为本申请实施例提供的寻呼装置的结构示意图之一。如图4所示，该装置包括：
第一接收单元410，用于接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；
第一处理单元420，用于基于所述寻呼消息，执行第一操作。
在本申请实施例中，通过接收寻呼消息，所述寻呼消息中可选携带寻呼原因指示信息，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因，基于该寻呼消息，确定寻呼原因，以便进一步确定后继行为，可以有效减少信令开销。
可选的，所述寻呼消息中携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第一列表，或者，所述寻呼消息携带第一列表和第二列表，
其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID；
其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
可选的，所述第一处理单元用于：
基于所述第一列表，确定终端是否被寻呼；
在所述终端被寻呼的情况下，基于所述第二列表，确定所述终端的寻呼原因；
其中，所述确定终端是否被寻呼，包括以下至少之一：
若所述终端的第一寻呼ID和所述第一列表中的第N个或倒数第N个entry包含的第一寻呼ID匹配成功，确定所述终端被寻呼，N为大于等于1且小于等于第一列表包含的entry总数的正整数；
若所述终端的第一寻呼ID和所述第一列表中的所有entry包含的第一寻呼ID匹配失败，确定所述终端未被寻呼；
其中，所述基于所述第二列表，确定所述终端的寻呼原因，包括以下至少之一：
获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因；
在所述第二列表包含的entry总数小于N的情况下，确定网络侧设备不支持寻呼原因发送。
可选的，所述获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因，包括以下至少之一：
若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息被携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息未被携带，则执行以下之一：所述终端基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可选的，还包括第二处理单元，用于：
接收下行信令，所述下行信令携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
在所述下行信令未携带第一指示信息的情况下，终端确定当前小区不支持寻呼原因发送；或者，
在所述下行信令携带第一指示信息的情况下，终端确定当前小区支持寻呼原因发送；
其中，所述下行信令包括以下之一：
寻呼消息；
系统信息；
下行调度信令。
可选的，所述基于所述第二列表，确定所述终端的寻呼原因，还包括：
在所述下行信令携带第一指示信息，且所述寻呼消息未携带第二列表的情况下，终端确定网络侧设备不支持寻呼原因发送。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第三列表和第四列表中的至少之一，
其中，所述第三列表中的每个entry包含一个被寻呼终端的第一寻呼ID；
其中，所述第四列表中的每个entry包含一个被寻呼终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表和第四列表中。
可选的，所述第一处理单元用于执行以下至少之一：
若所述终端的第一寻呼ID和第三列表中的第P个entry包含的第一寻呼ID匹配成功，则终端确定网络侧设备不支持寻呼原因发送；
若所述终端的第一寻呼ID和第四列表中的第P个entry包含的第一寻呼ID匹配成功，则获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因；
若所述终端的第一寻呼ID，与所述第三列表和第四列表中的所有entry包含的第一寻呼ID均匹配失败，则终端确定未被寻呼；
其中，P为大于等于1的正整数。
可选的，所述获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因，包括：
若所述第四列表中的第P个entry包含的寻呼原因指示信息被显式携带或携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
若第P个entry包含的寻呼原因指示信息被隐式携带或未携带，则执行以下之一：基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个显式携带或携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可选的，所述基于协议约定确定所述终端的寻呼原因，包括：
确定所述终端的寻呼原因为非语音业务触发的寻呼或与协议定义的寻呼原因互补的其他寻呼原因。
可选的，所述寻呼原因指示信息基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
被寻呼终端的全部或部分终端标识UE ID；
网络侧设备和被寻呼终端共享的密钥；
被寻呼终端的加密前的寻呼原因；
其中，所述第一处理单元，用于：
获取所述终端对应的寻呼原因指示信息；
对所述寻呼原因指示信息进行解密，确定所述终端的寻呼原因。
可选的，还包括第三处理单元，用于执行以下至少一项：
在检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，确定所述寻呼原因指示信息或寻呼原因无效；
在检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，向网络侧设备上报第一信息；
接收网络侧设备发送的用于后继寻呼原因解密的安全参数；
其中，所述第一信息用于指示以下至少一项：
收到非预期寻呼原因或非预期寻呼原因指示信息；
收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
可选的，所述第二列表或第四列表包括以下至少一项：
长度域；
Entry域；
其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被寻呼；
当寻呼原因指示信息未被携带时，包括以下之一：
终端的寻呼原因为协议约定的寻呼原因；
终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是基于被寻呼终端的第一寻呼ID和协议约定的推导方式中至少之一得到的；
所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
可选的，所述第一处理单元用于执行以下至少之一：
根据所述第二寻呼ID确定寻呼原因；
根据所述第三寻呼ID确定寻呼原因；
根据RNTI确定寻呼原因。
可选的，还包括：
第一发送单元，用于向网络侧设备上报第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
本申请实施例中的寻呼装置可以是装置，具有操作系统的装置或电子设备，也可以是终端中的部件、集成电路、或芯片。该装置或电子设备可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例提供的寻呼装置能够实现图2的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图5为本申请实施例提供的寻呼装置的结构示意图之二。如图5所示，该装置包括：
第二发送单元510，用于向终端发送寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。
在本申请实施例中，通过发送寻呼消息，所述寻呼消息中可选携带寻呼原因指示信息，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因，可以有效减少信令开销。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息中携带第一列表，或者，所述寻呼消息携带第一列表和第二列表，
其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID；
其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息中携带第三列表和第四列表中的至少之一，
其中，所述第三列表中的每个元素entry包含一个终端的第一寻呼ID；
其中，所述第四列表中的每个entry包含一个终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表和第四列表中。
可选的，所述寻呼原因指示信息基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
被寻呼终端的全部或部分终端标识UE ID；
网络侧设备和被寻呼终端共享的密钥；
被寻呼终端的加密前的寻呼原因或寻呼原因指示信息。
可选的，还包括：第四处理单元，用于执行以下至少一项：
接收终端发送的第一信息；
向终端发送用于后继寻呼原因解密的安全参数；
其中，所述第一信息用于指示以下至少一项：
收到非预期寻呼原因或非预期寻呼原因指示信息；
收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
可选的，所述第二列表或第四列表包括以下至少一项：
长度域；
Entry域；
其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被寻呼；
当寻呼原因指示信息未被携带时，包括以下之一：
终端的寻呼原因为协议约定的寻呼原因；
终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可选的，还包括：
第三发送单元，用于向终端发送下行信令，所述下行信令中携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
其中，所述下行信令包括以下之一：
寻呼消息；
系统信息；
下行调度信令。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
所述寻呼消息携带网络侧设备为每个需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
所述寻呼消息携带每个需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是网络侧设备基于被寻呼终端的第一寻呼ID和协议约定的推导方式中至少之一得到的；
所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
可选的，还包括：
第二接收单元，用于接收终端上报的第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
本申请实施例提供的寻呼装置能够实现图3的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图6所示，本申请实施例还提供一种通信设备600，包括处理器601，存储器602，存储在存储器602上并可在所述处理器601上运行的程序或指令，例如，该通信设备600为终端时，该程序或指令被处理器601执行时实现上述寻呼方法实施例的各个过程，且能达到相同的技术效果。该通信设备600为网络侧设备时，该程序或指令被处理器601执行时实现上述寻呼方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种终端，包括处理器和通信接口，所述通信接口用于接收寻呼消息，所述寻呼消息携带或未寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；所述处理器用于基于所述寻呼消息，执行第一操作。该终端实施例是与上述终端侧方法实施例对应的，上述方法实施例的各个实施过程和实现方式均可适用于该终端实施例中，且能达到相同的技术效果。具体地，图7 为实现本申请实施例的一种终端的硬件结构示意图。
该终端700包括但不限于：射频单元701、网络模块702、音频输出单元703、输入单元704、传感器705、显示单元706、用户输入单元707、接口单元708、存储器709、以及处理器710等中的至少部分部件。
本领域技术人员可以理解，终端700还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器710逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图7中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元704可以包括图形处理器(Graphics Processing Unit，GPU)7041和麦克风7042，图形处理器7041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元706可包括显示面板7061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板7061。用户输入单元707包括触控面板7071以及其他输入设备7072。触控面板7071，也称为触摸屏。触控面板7071可包括触摸检测装置和触摸控制器两个部分。其他输入设备7072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元701将来自网络侧设备的下行数据接收后，给处理器710处理；另外，将上行的数据发送给网络侧设备。通常，射频单元701包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器709可用于存储软件程序或指令以及各种数据。存储器709可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器709可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only  Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器710可包括一个或多个处理单元；可选的，处理器710可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器710中。
其中，射频单元701，用于接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；
处理器710，用于基于所述寻呼消息，执行第一操作。
在本申请实施例中，终端通过接收寻呼消息，所述寻呼消息中携带或未携带寻呼原因指示信息，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因，基于该寻呼消息，确定寻呼原因，以便进一步确定后继行为，可以有效减少信令开销。
可选的，所述寻呼消息中携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第一列表，或者，所述寻呼消息携带第一列表和第二列表，
其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID；
其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
可选的，处理器710还用于：
基于所述第一列表，确定终端是否被寻呼；
在所述终端被寻呼的情况下，基于所述第二列表，确定所述终端的寻呼原因；
其中，所述确定终端是否被寻呼，包括以下至少之一：
若所述终端的第一寻呼ID和所述第一列表中的第N个或倒数第N个entry包含的第一寻呼ID匹配成功，确定所述终端被寻呼，N为大于等于1且小于等于第一列表包含的entry总数的正整数；
若所述终端的第一寻呼ID和所述第一列表中的所有entry包含的第一寻呼ID匹配失败，确定所述终端未被寻呼；
其中，所述基于所述第二列表，确定所述终端的寻呼原因，包括以下至少之一：
获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因；
在所述第二列表包含的entry总数小于N的情况下，确定网络侧设备不支持寻呼原因发送。
可选的，所述获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因，包括以下至少之一：
若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息被携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息未被携带，则执行以下之一：所述终端基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可选的，处理器710还用于：
接收下行信令，所述下行信令携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
在所述下行信令未携带第一指示信息的情况下，终端确定当前小区不支持寻呼原因发送；或者，
在所述下行信令携带第一指示信息的情况下，终端确定当前小区支持寻呼原因发送；
其中，所述下行信令包括以下之一：
寻呼消息；
系统信息；
下行调度信令。
可选的，所述基于所述第二列表，确定所述终端的寻呼原因，还包括：
在所述下行信令携带第一指示信息，且所述寻呼消息未携带第二列表的情况下，终端确定网络侧设备不支持寻呼原因发送。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第三列表和第四列表中的至少之一，
其中，所述第三列表中的每个entry包含一个被寻呼终端的第一寻呼ID；
其中，所述第四列表中的每个entry包含一个被寻呼终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表和第四列表中。
可选的，处理器710还用于：
若所述终端的第一寻呼ID和第三列表中的第P个entry包含的第一寻呼ID匹配成功，则终端确定网络侧设备不支持寻呼原因发送；
若所述终端的第一寻呼ID和第四列表中的第P个entry包含的第一寻呼ID匹配成功，则获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因；
若所述终端的第一寻呼ID，与所述第三列表和第四列表中的所有entry包含的第一寻呼ID均匹配失败，则终端确定未被寻呼；
其中，P为大于等于1的正整数。
可选的，所述获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因，包括：
若所述第四列表中的第P个entry包含的寻呼原因指示信息被显式携带或携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
若第P个entry包含的寻呼原因指示信息被隐式携带或未携带，则执行以下之一：基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个显式携带或携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可选的，所述基于协议约定确定所述终端的寻呼原因，包括：
确定所述终端的寻呼原因为非语音业务触发的寻呼或与协议定义的寻呼原因互补的其他寻呼原因。
可选的，所述寻呼原因指示信息基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
被寻呼终端的全部或部分终端标识UE ID；
网络侧设备和被寻呼终端共享的密钥；
被寻呼终端的加密前的寻呼原因；
其中，所述第一处理单元，用于：
获取所述终端对应的寻呼原因指示信息；
对所述寻呼原因指示信息进行解密，确定所述终端的寻呼原因。
可选的，处理器710还用于执行以下至少一项：
在检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，确定所述寻呼原因指示信息或寻呼原因无效；
在检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，向网络侧设备上报第一信息；
接收网络侧设备发送的用于后继寻呼原因解密的安全参数；
其中，所述第一信息用于指示以下至少一项：
收到非预期寻呼原因或非预期寻呼原因指示信息；
收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
可选的，所述第二列表或第四列表包括以下至少一项：
长度域；
Entry域；
其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被寻呼；
当寻呼原因指示信息未被携带时，包括以下之一：
终端的寻呼原因为协议约定的寻呼原因；
终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
可选的，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是基于被寻呼终端的第一寻呼ID和协议约定的推导方式中至少之一得到的；
所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
可选的，处理器710还用于执行以下至少之一：
根据所述第二寻呼ID确定寻呼原因；
根据所述第三寻呼ID确定寻呼原因；
根据RNTI确定寻呼原因。
可选的，射频单元701还用于：
向网络侧设备上报第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
本申请实施例还提供一种网络侧设备，包括处理器和通信接口，通信接口用于向终端发送寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。该网络侧设备实施例是与上述网络侧设备方法实施例对应的，上述方法实施例的各个实施过程和实现方式均可适用于该网络侧设备实施例中，且能达到相同的技术效果。
具体地，本申请实施例还提供了一种网络侧设备。如图8所示，该网络侧设备800包括：天线801、射频装置802、基带装置803。天线801与射频装置802连接。在上行方向上，射频装置802通过天线801接收信息，将接收的信息发送给基带装置803进行处理。在下行方向上，基带装置803对要发送的信息进行处理，并发送给射频装置802，射频装置802对收到的信息进行处理后经过天线801发送出去。
上述频带处理装置可以位于基带装置803中，以上实施例中网络侧设备执行的方法可以在基带装置803中实现，该基带装置803包括处理器804和存储器805。
基带装置803例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图8所示，其中一个芯片例如为处理器804，与存储器805连接，以调用存储器805中的程序，执行以上方法实施例中所示的网络侧设备操作。
该基带装置803还可以包括网络接口806，用于与射频装置802交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器805上并可在处理器804上运行的指令或程序，处理器804调用存储器805中的指令或程序执行图5所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述寻呼方法实施例的各个过 程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述寻呼方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以计算机软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服 务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (55)

  1. 一种寻呼方法，包括：
    终端接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；
    终端基于所述寻呼消息，执行第一操作。
  2. 根据权利要求1所述的寻呼方法，其中，所述寻呼消息中携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第一列表，或者，所述寻呼消息携带第一列表和第二列表，
    其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID；
    其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
    所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
  3. 根据权利要求2所述的寻呼方法，其中，所述终端基于所述寻呼消息，执行第一操作，包括：
    终端基于所述第一列表，确定所述终端是否被寻呼；
    在所述终端被寻呼的情况下，终端基于所述第二列表，确定所述终端的寻呼原因；
    其中，所述确定所述终端是否被寻呼，包括以下至少之一：
    若所述终端的第一寻呼ID和所述第一列表中的第N个或倒数第N个entry包含的第一寻呼ID匹配成功，确定所述终端被寻呼，N为大于等于1且小于等于第一列表包含的entry总数的正整数；
    若所述终端的第一寻呼ID和所述第一列表中的所有entry包含的第一 寻呼ID匹配失败，确定所述终端未被寻呼；
    其中，所述终端基于所述第二列表，确定所述终端的寻呼原因，包括以下至少之一：
    所述终端获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因；
    在所述第二列表包含的entry总数小于N的情况下，所述终端确定网络侧设备不支持寻呼原因发送。
  4. 根据权利要求3所述的寻呼方法，其中，所述终端获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因，包括以下至少之一：
    若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息被携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
    若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息未被携带，则执行以下之一：所述终端基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
  5. 根据权利要求3所述的寻呼方法，其中，所述方法还包括：
    接收下行信令，所述下行信令携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
    在所述下行信令未携带第一指示信息的情况下，终端确定当前小区不支持寻呼原因发送；或者，
    在所述下行信令携带第一指示信息的情况下，终端确定当前小区支持寻呼原因发送；
    其中，所述下行信令包括以下之一：
    寻呼消息；
    系统信息；
    下行调度信令。
  6. 根据权利要求5所述的寻呼方法，其中，所述终端基于所述第二列表，确定所述终端的寻呼原因，还包括：
    在所述下行信令携带第一指示信息，且所述寻呼消息未携带第二列表的情况下，终端确定网络侧设备不支持寻呼原因发送。
  7. 根据权利要求1所述的寻呼方法，其中，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第三列表和第四列表中的至少之一，
    其中，所述第三列表中的每个entry包含一个被寻呼终端的第一寻呼ID；
    其中，所述第四列表中的每个entry包含一个被寻呼终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
    其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表和第四列表中。
  8. 根据权利要求7所述的寻呼方法，其中，所述终端基于所述寻呼消息，执行第一操作，包括以下至少之一：
    若所述终端的第一寻呼ID和第三列表中的第P个entry包含的第一寻呼ID匹配成功，则终端确定网络侧设备不支持寻呼原因发送；
    若所述终端的第一寻呼ID和第四列表中的第P个entry包含的第一寻呼ID匹配成功，则获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因；
    若所述终端的第一寻呼ID，与所述第三列表和第四列表中的所有entry包含的第一寻呼ID均匹配失败，则终端确定未被寻呼；
    其中，P为大于等于1的正整数。
  9. 根据权利要求8所述的寻呼方法，其中，所述获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因，包括：
    若所述第四列表中的第P个entry包含的寻呼原因指示信息被携带， 则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
    若第P个entry包含的寻呼原因指示信息未被携带，则执行以下之一：基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个显式携带或携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
  10. 根据权利要求4或9所述的寻呼方法，其中，所述基于协议约定确定所述终端的寻呼原因，包括：
    确定所述终端的寻呼原因为非语音业务触发的寻呼或与协议定义的寻呼原因互补的其他寻呼原因。
  11. 根据权利要求1所述的寻呼方法，其中，所述寻呼原因指示信息基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
    被寻呼终端的全部或部分终端标识UE ID；
    网络侧设备和被寻呼终端共享的密钥；
    被寻呼终端的加密前的寻呼原因或寻呼原因指示信息；
    其中，所述终端基于所述寻呼消息，执行第一操作，包括：
    所述终端获取所述终端对应的寻呼原因指示信息；
    对所述寻呼原因指示信息进行解密，确定所述终端的寻呼原因。
  12. 根据权利要求11所述的寻呼方法，其中，所述执行第一操作之后，所述方法还包括以下至少一项：
    在终端检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，终端确定所述寻呼原因指示信息或寻呼原因无效；
    在终端检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，终端向网络侧设备上报第一信息；
    终端接收网络侧设备发送的用于后继寻呼原因解密的安全参数；
    其中，所述第一信息用于指示以下至少一项：
    收到非预期寻呼原因或非预期寻呼原因指示信息；
    收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
  13. 根据权利要求2或7所述的寻呼方法，其中，所述第二列表或第四列表包括以下至少一项：
    长度域；
    Entry域；
    其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
    其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被寻呼；
    当寻呼原因指示信息未被携带时，包括以下之一：
    终端的寻呼原因为协议约定的寻呼原因；
    终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
  14. 根据权利要求1所述的寻呼方法，其中，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
    所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
    所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是基于被寻呼终端的第一寻呼ID和协议约定的推导方式至少之一得到的；
    所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
  15. 根据权利要求14所述的寻呼方法，其中，所述终端基于所述寻呼消息，执行第一操作，包括以下至少之一：
    终端根据所述第二寻呼ID确定寻呼原因；
    终端根据所述第三寻呼ID确定寻呼原因；
    终端根据RNTI确定寻呼原因。
  16. 根据权利要求1-15中任一项所述的寻呼方法，其中，所述终端接收寻呼消息之前，还包括：
    终端向网络侧设备上报第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
  17. 一种寻呼方法，包括：
    网络侧设备向终端发送寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。
  18. 根据权利要求17所述的寻呼方法，其中，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息中携带第一列表，或者，所述寻呼消息中携带第一列表和第二列表，
    其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID；
    其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
    所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
  19. 根据权利要求17所述的寻呼方法，其中，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息中携带第三列表和第四列表中的至少之一，
    其中，所述第三列表中的每个元素entry包含一个终端的第一寻呼ID；
    其中，所述第四列表中的每个entry包含一个终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
    其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表和第四列表中。
  20. 根据权利要求17所述的寻呼方法，其中，所述寻呼原因指示信息 基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
    被寻呼终端的全部或部分终端标识UE ID；
    网络侧设备和被寻呼终端共享的密钥；
    被寻呼终端的加密前的寻呼原因或寻呼原因指示信息。
  21. 根据权利要求20所述的寻呼方法，其中，所述方法还包括以下至少一项：
    网络侧设备接收终端发送的第一信息；
    网络侧设备向终端发送用于后继寻呼原因解密的安全参数；
    其中，所述第一信息用于指示以下至少一项：
    收到非预期寻呼原因或非预期寻呼原因指示信息；
    收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
  22. 根据权利要求18或19所述的寻呼方法，其中，所述第二列表或第四列表包括以下至少一项：
    长度域；
    Entry域；
    其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
    其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被寻呼；
    当寻呼原因指示信息未被携带时，包括以下之一：
    终端的寻呼原因为协议约定的寻呼原因；
    终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
  23. 根据权利要求17所述的寻呼方法，其中，所述方法还包括：
    网络侧设备向终端发送下行信令，所述下行信令携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
    其中，所述下行信令包括以下之一：
    寻呼消息；
    系统信息；
    下行调度信令。
  24. 根据权利要求17所述的寻呼方法，其中，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
    所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
    所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是网络侧设备基于被寻呼终端的第一寻呼ID和协议约定的推导方式中至少之一得到的；
    所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
  25. 根据权利要求17-24中任一项所述的寻呼方法，其中，所述方法还包括：
    网络侧设备接收终端上报的第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
  26. 一种寻呼装置，包括：
    第一接收单元，用于接收寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因；
    第一处理单元，用于基于所述寻呼消息，执行第一操作。
  27. 根据权利要求26所述的寻呼装置，其中，所述寻呼消息中携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第一列表，或者，所述寻呼消息携带第一列表和第二列表，
    其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一寻呼ID；
    其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
    所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
  28. 根据权利要求27所述的寻呼装置，其中，所述第一处理单元用于：
    基于所述第一列表，确定终端是否被寻呼；
    在所述终端被寻呼的情况下，基于所述第二列表，确定所述终端的寻呼原因；
    其中，所述确定终端是否被寻呼，包括以下至少之一：
    若所述终端的第一寻呼ID和所述第一列表中的第N个或倒数第N个entry包含的第一寻呼ID匹配成功，确定所述终端被寻呼，N为大于等于1且小于等于第一列表包含的entry总数的正整数；
    若所述终端的第一寻呼ID和所述第一列表中的所有entry包含的第一寻呼ID匹配失败，确定所述终端未被寻呼；
    其中，所述基于所述第二列表，确定所述终端的寻呼原因，包括以下至少之一：
    获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因；
    在所述第二列表包含的entry总数小于N的情况下，确定网络侧设备不支持寻呼原因发送。
  29. 根据权利要求28所述的寻呼装置，其中，所述获取所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息，确定所述终端的寻呼原因，包括以下至少之一：
    若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示信息被携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
    若所述第二列表中的第N个或倒数第N个entry对应的寻呼原因指示 信息未被携带，则执行以下之一：所述终端基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
  30. 根据权利要求28所述的寻呼装置，其中，还包括第二处理单元，用于：
    接收下行信令，所述下行信令携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
    在所述下行信令未携带第一指示信息的情况下，终端确定当前小区不支持寻呼原因发送；或者，
    在所述下行信令携带第一指示信息的情况下，终端确定当前小区支持寻呼原因发送；
    其中，所述下行信令包括以下之一：
    寻呼消息；
    系统信息；
    下行调度信令。
  31. 根据权利要求28所述的寻呼装置，其中，所述基于所述第二列表，确定所述终端的寻呼原因，还包括：
    在所述下行信令携带第一指示信息，且所述寻呼消息未携带第二列表的情况下，终端确定网络侧设备不支持寻呼原因发送。
  32. 根据权利要求26所述的寻呼装置，其中，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第三列表和第四列表中的至少之一，
    其中，所述第三列表中的每个entry包含一个被寻呼终端的第一寻呼ID；
    其中，所述第四列表中的每个entry包含一个被寻呼终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
    其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表 和第四列表中。
  33. 根据权利要求32所述的寻呼装置，其中，所述第一处理单元用于执行以下至少之一：
    若所述终端的第一寻呼ID和第三列表中的第P个entry包含的第一寻呼ID匹配成功，则终端确定网络侧设备不支持寻呼原因发送；
    若所述终端的第一寻呼ID和第四列表中的第P个entry包含的第一寻呼ID匹配成功，则获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因；
    若所述终端的第一寻呼ID，与所述第三列表和第四列表中的所有entry包含的第一寻呼ID均匹配失败，则终端确定未被寻呼；
    其中，P为大于等于1的正整数。
  34. 根据权利要求33所述的寻呼装置，其中，所述获取所述第四列表中的第P个entry包含的寻呼原因指示信息，确定所述终端的寻呼原因，包括：
    若所述第四列表中的第P个entry包含的寻呼原因指示信息被显式携带或携带，则根据所述寻呼原因指示信息，确定所述终端的寻呼原因；
    若第P个entry包含的寻呼原因指示信息被隐式携带或未携带，则执行以下之一：基于协议约定确定所述终端的寻呼原因；确定所述终端对应的寻呼原因指示信息和前一个显式携带或携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
  35. 根据权利要求29或34所述的寻呼装置，其中，所述基于协议约定确定所述终端的寻呼原因，包括：
    确定所述终端的寻呼原因为非语音业务触发的寻呼或与协议定义的寻呼原因互补的其他寻呼原因。
  36. 根据权利要求26所述的寻呼装置，其中，所述寻呼原因指示信息基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
    被寻呼终端的全部或部分终端标识UE ID；
    网络侧设备和被寻呼终端共享的密钥；
    被寻呼终端的加密前的寻呼原因；
    其中，所述第一处理单元，用于：
    获取所述终端对应的寻呼原因指示信息；
    对所述寻呼原因指示信息进行解密，确定所述终端的寻呼原因。
  37. 根据权利要求36所述的寻呼装置，其中，还包括第三处理单元，用于执行以下至少一项：
    在检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，确定所述寻呼原因指示信息或寻呼原因无效；
    在检测到所述寻呼原因指示信息或寻呼原因为非预期取值的情况下，向网络侧设备上报第一信息；
    接收网络侧设备发送的用于后继寻呼原因解密的安全参数；
    其中，所述第一信息用于指示以下至少一项：
    收到非预期寻呼原因或非预期寻呼原因指示信息；
    收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
  38. 根据权利要求27或32所述的寻呼装置，其中，所述第二列表或第四列表包括以下至少一项：
    长度域；
    Entry域；
    其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
    其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被寻呼；
    当寻呼原因指示信息未被携带时，包括以下之一：
    终端的寻呼原因为协议约定的寻呼原因；
    终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
  39. 根据权利要求26所述的寻呼装置，其中，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
    所述寻呼消息携带网络侧设备为需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
    所述寻呼消息携带需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是基于被寻呼终端的第一寻呼ID和协议约定的推导方式中至少之一得到的；
    所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
  40. 根据权利要求39所述的寻呼装置，其中，所述第一处理单元用于执行以下至少之一：
    根据所述第二寻呼ID确定寻呼原因；
    根据所述第三寻呼ID确定寻呼原因；
    根据RNTI确定寻呼原因。
  41. 根据权利要求26-40中任一项所述的寻呼装置，其中，还包括：
    第一发送单元，用于向网络侧设备上报第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
  42. 一种寻呼装置，包括：
    第二发送单元，用于向终端发送寻呼消息，所述寻呼消息携带或未携带寻呼原因指示信息，其中，所述寻呼原因指示信息用于指示需要或支持接收寻呼原因的被寻呼终端对应的寻呼原因。
  43. 根据权利要求42所述的寻呼装置，其中，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息携带第一列表，或者，所述寻呼消息携带第一列表和第二列表，
    其中，所述第一列表中的每个元素entry包含一个被寻呼终端的第一 寻呼ID；
    其中，所述第二列表中的每个entry包含一个被寻呼终端的寻呼原因指示信息；
    所述第二列表中被寻呼终端的寻呼原因指示信息排序和第一列表中前M个或后M个被寻呼终端的第一寻呼ID排序是对应的，其中，M为第二列表包含的entry总数。
  44. 根据权利要求42所述的寻呼装置，其中，所述寻呼消息携带或未携带寻呼原因指示信息包括：所述寻呼消息中携带第三列表和第四列表中的至少之一，
    其中，所述第三列表中的每个元素entry包含一个终端的第一寻呼ID；
    其中，所述第四列表中的每个entry包含一个终端的第一寻呼ID和所述第一寻呼ID对应的寻呼原因指示信息；
    其中，一个被寻呼终端的第一寻呼ID不会同时出现在所述第三列表和第四列表中。
  45. 根据权利要求42所述的寻呼装置，其中，所述寻呼原因指示信息基于加密输入参数生成；其中，所述加密输入参数包括以下至少一项：
    被寻呼终端的全部或部分终端标识UE ID；
    网络侧设备和被寻呼终端共享的密钥；
    被寻呼终端的加密前的寻呼原因或寻呼原因指示信息。
  46. 根据权利要求45所述的寻呼装置，其中，还包括：第四处理单元，用于执行以下至少一项：
    接收终端发送的第一信息；
    向终端发送用于后继寻呼原因解密的安全参数；
    其中，所述第一信息用于指示以下至少一项：
    收到非预期寻呼原因或非预期寻呼原因指示信息；
    收到非预期寻呼原因或非预期寻呼原因指示信息的小区标识。
  47. 根据权利要求43或44所述的寻呼装置，其中，所述第二列表或 第四列表包括以下至少一项：
    长度域；
    Entry域；
    其中，所述长度域用于指示所述第二列表或第四列表包含的entry总数，所述Entry域携带或未携带终端的寻呼原因指示信息；
    其中，当寻呼原因指示信息被携带时表明终端因为所携带的寻呼原因被寻呼；
    当寻呼原因指示信息未被携带时，包括以下之一：
    终端的寻呼原因为协议约定的寻呼原因；
    终端的寻呼原因指示信息和前一个携带寻呼原因指示信息的entry对应的寻呼原因指示信息相同。
  48. 根据权利要求42所述的寻呼装置，其中，还包括：
    第三发送单元，用于向终端发送下行信令，所述下行信令中携带或未携带第一指示信息，所述第一指示信息用于指示所述寻呼消息支持携带寻呼原因；
    其中，所述下行信令包括以下之一：
    寻呼消息；
    系统信息；
    下行调度信令。
  49. 根据权利要求42所述的寻呼装置，其中，所述寻呼消息携带或未携带寻呼原因指示信息，包括以下至少之一：
    所述寻呼消息携带网络侧设备为每个需要或支持接收寻呼原因的被寻呼终端分配的第二寻呼ID；
    所述寻呼消息携带每个需要或支持接收寻呼原因的被寻呼终端对应的第三寻呼ID，其中，所述第三寻呼ID是网络侧设备基于被寻呼终端的第一寻呼ID和协议约定的推导方式中至少之一得到的；
    所述寻呼消息由使用寻呼原因对应的RNTI加扰的PDCCH调度，其 中，不同寻呼原因对应的RNTI是网络侧设备显式指示或协议约定的推导方式得到的。
  50. 根据权利要求42-49中任一项所述的寻呼装置，其中，还包括：
    第二接收单元，用于接收终端上报的第二信息，所述第二信息用于指示终端需要或支持接收寻呼原因，或者，指示终端不需要或不支持接收寻呼原因。
  51. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至16任一项所述的寻呼方法的步骤。
  52. 一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求17至25任一项所述的寻呼方法的步骤。
  53. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至16任一项所述的寻呼方法，或者实现如权利要求17至25任一项所述的寻呼方法的步骤。
  54. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至16任一项所述的寻呼方法，或者实现如权利要求17至25任一项所述的寻呼方法的步骤。
  55. 一种计算机程序/程序产品，所述计算机程序/程序产品被存储在非易失的存储介质中，所述程序/程序产品被至少一个处理器执行以实现如权利要求1至16任一项所述的寻呼方法，或者实现如权利要求17至25任一项所述的寻呼方法的步骤。
PCT/CN2022/084431 2021-04-01 2022-03-31 寻呼方法、装置、终端及网络侧设备 Ceased WO2022206898A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22779078.9A EP4319349A4 (en) 2021-04-01 2022-03-31 RADIO POLLING METHOD AND DEVICE, TERMINAL DEVICE AND NETWORK-SIDE DEVICE
US18/373,641 US20240031981A1 (en) 2021-04-01 2023-09-27 Paging Method and Apparatus, Terminal, and Network Side Device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110357971.1 2021-04-01
CN202110357971.1A CN115175312A (zh) 2021-04-01 2021-04-01 寻呼方法、装置、终端及网络侧设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/373,641 Continuation US20240031981A1 (en) 2021-04-01 2023-09-27 Paging Method and Apparatus, Terminal, and Network Side Device

Publications (1)

Publication Number Publication Date
WO2022206898A1 true WO2022206898A1 (zh) 2022-10-06

Family

ID=83458003

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/084431 Ceased WO2022206898A1 (zh) 2021-04-01 2022-03-31 寻呼方法、装置、终端及网络侧设备

Country Status (4)

Country Link
US (1) US20240031981A1 (zh)
EP (1) EP4319349A4 (zh)
CN (1) CN115175312A (zh)
WO (1) WO2022206898A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026007927A1 (zh) * 2024-07-05 2026-01-08 维沃移动通信有限公司 环境物联网配置方法、装置、终端及网络侧设备

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114828203A (zh) * 2021-01-18 2022-07-29 维沃移动通信有限公司 信息处理的方法、装置、设备及可读存储介质
US20240340850A1 (en) * 2021-06-29 2024-10-10 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for implementing paging cause indication

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109392092A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 一种寻呼消息的发送方法及相关设备
EP3479630A1 (en) * 2016-06-30 2019-05-08 Intel IP Corporation Optimized paging mechanism for ip multimedia subsystem (ims)
CN110730445A (zh) * 2019-09-28 2020-01-24 RealMe重庆移动通信有限公司 寻呼处理方法、装置、电子设备以及存储介质
CN111278106A (zh) * 2019-01-18 2020-06-12 维沃软件技术有限公司 寻呼指示方法、寻呼方法、终端和网络侧设备
CN111836219A (zh) * 2019-08-12 2020-10-27 维沃移动通信有限公司 一种消息传输方法和通信设备
CN112166634A (zh) * 2020-08-31 2021-01-01 北京小米移动软件有限公司 寻呼原因发送方法和装置、寻呼原因获取方法和装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632999B (zh) * 2017-03-24 2023-03-31 中兴通讯股份有限公司 信息发送、接收方法及装置、网络侧设备、终端、处理器
CN110536290B (zh) * 2018-05-24 2022-03-29 华为技术有限公司 一种寻呼处理方法及装置
EP4586711A1 (en) * 2019-03-11 2025-07-16 Ofinno, LLC Wireless device paging by a wireless network
WO2020200252A1 (en) * 2019-04-04 2020-10-08 FG Innovation Company Limited Method for monitoring paging and apparatus using the same
WO2020209620A1 (en) * 2019-04-09 2020-10-15 Samsung Electronics Co., Ltd. Method and ue for managing paging procedure in wireless communication network
CN115442891B (zh) * 2019-07-10 2025-07-08 苹果公司 用于多用户身份模块设备的通信协调和冲突缓解
US11452067B2 (en) * 2019-09-25 2022-09-20 Qualcomm Incorporated Secure paging for service prioritization
WO2021066562A1 (en) * 2019-10-04 2021-04-08 Samsung Electronics Co., Ltd. Method and system for providing paging cause to musim user equipment
EP4233411A4 (en) * 2020-10-22 2024-03-20 ZTE Corporation TECHNIQUES FOR MULTI-SUBSCRIBER IDENTIFICATION MODULE FOR WIRELESS SYSTEMS
US12143962B2 (en) * 2021-01-07 2024-11-12 Sharp Kabushiki Kaisha Method of performing a paging reception and user equipment using the same
US12256357B2 (en) * 2021-03-31 2025-03-18 Apple Inc. Multi-SIM UE capability indications and band conflict resolution

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3479630A1 (en) * 2016-06-30 2019-05-08 Intel IP Corporation Optimized paging mechanism for ip multimedia subsystem (ims)
CN109392092A (zh) * 2017-08-11 2019-02-26 华为技术有限公司 一种寻呼消息的发送方法及相关设备
CN111278106A (zh) * 2019-01-18 2020-06-12 维沃软件技术有限公司 寻呼指示方法、寻呼方法、终端和网络侧设备
CN111836219A (zh) * 2019-08-12 2020-10-27 维沃移动通信有限公司 一种消息传输方法和通信设备
CN110730445A (zh) * 2019-09-28 2020-01-24 RealMe重庆移动通信有限公司 寻呼处理方法、装置、电子设备以及存储介质
CN112166634A (zh) * 2020-08-31 2021-01-01 北京小米移动软件有限公司 寻呼原因发送方法和装置、寻呼原因获取方法和装置

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
See also references of EP4319349A4 *
VIVO: "Discussion on Supporting of Paging Cause", 3GPP DRAFT; R2-2100476, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. e-Meeting; 20210125 - 20210205, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051973653 *
VIVO: "Signaling support for paging cause", 3GPP DRAFT; R3-210174, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. E-Meeting; 20210125 - 20210204, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051974907 *
ZTE CORPORATION, SANECHIPS: "Consideration on the Paging Cause", 3GPP DRAFT; R2-2009624, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Online; 20201102 - 20201113, 23 October 2020 (2020-10-23), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051942547 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2026007927A1 (zh) * 2024-07-05 2026-01-08 维沃移动通信有限公司 环境物联网配置方法、装置、终端及网络侧设备

Also Published As

Publication number Publication date
CN115175312A (zh) 2022-10-11
US20240031981A1 (en) 2024-01-25
EP4319349A4 (en) 2024-10-02
EP4319349A1 (en) 2024-02-07

Similar Documents

Publication Publication Date Title
US12127160B2 (en) Communication method and apparatus
US20200213903A1 (en) Data transmission method and device
US20240031981A1 (en) Paging Method and Apparatus, Terminal, and Network Side Device
CN115550956A (zh) 定位测量方法、定位配置方法、装置及通信设备
CN112333795B (zh) 网络接入方法及装置
WO2022017359A1 (zh) 直接通信启动控制方法及相关设备
JP2025016779A (ja) 初期アクセス方法及び装置、端末及びネットワーク側機器
WO2023066129A1 (zh) 信息上报方法、设备及可读存储介质
WO2022083630A1 (zh) 寻呼方法、装置、终端、网络侧设备及可读存储介质
WO2022068813A1 (zh) 拥塞控制方法、装置、终端及网络侧设备
CN114696975B (zh) 速率匹配方法和设备
WO2022148431A1 (zh) 非连续接收drx配置切换的方法、装置及终端
WO2022083629A1 (zh) 寻呼消息的接收方法、寻呼配置方法、终端及网络侧设备
WO2021249438A1 (zh) 模式切换方法、终端及网络侧设备
WO2022036560A1 (zh) 一种数据传输方法及相关设备
CN114501490A (zh) 业务转移方法、终端及网络侧设备
WO2022257934A1 (zh) Pdcch监听方法、终端及网络侧设备
WO2022188836A1 (zh) Cot确定方法、上行传输方法和设备
WO2022017466A1 (zh) 消息发送、消息接收方法、装置及通信设备
WO2022127702A1 (zh) 信息确定方法、装置及通信设备
WO2022028597A1 (zh) 控制辅小区的方法、终端及网络侧设备
WO2022033424A1 (zh) 资源传输方法、装置及通信设备
CN115086882B (zh) 传输方法、装置、设备及可读存储介质
CN116074954B (zh) 接入控制方法、装置及终端
CN115334646B (zh) 资源选择方法、装置及终端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22779078

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022779078

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022779078

Country of ref document: EP

Effective date: 20231023

NENP Non-entry into the national phase

Ref country code: DE