WO2022222012A1 - 寻呼处理方法及其装置 - Google Patents

寻呼处理方法及其装置 Download PDF

Info

Publication number
WO2022222012A1
WO2022222012A1 PCT/CN2021/088233 CN2021088233W WO2022222012A1 WO 2022222012 A1 WO2022222012 A1 WO 2022222012A1 CN 2021088233 W CN2021088233 W CN 2021088233W WO 2022222012 A1 WO2022222012 A1 WO 2022222012A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
mac
access network
request message
paging
Prior art date
Application number
PCT/CN2021/088233
Other languages
English (en)
French (fr)
Inventor
洪伟
Original Assignee
北京小米移动软件有限公司
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 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to PCT/CN2021/088233 priority Critical patent/WO2022222012A1/zh
Priority to CN202180001177.1A priority patent/CN115516942A/zh
Publication of WO2022222012A1 publication Critical patent/WO2022222012A1/zh

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

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a paging processing method and device thereof.
  • a terminal device with multiple USIM can pass multiple RAT (Radio Access Technology, radio access technology) related to 3GPP (the 3rd Generation Partnership Project, the third generation partnership project) Multiple USIMs connected to the network register concurrently.
  • RAT Radio Access Technology, radio access technology
  • 3GPP the 3rd Generation Partnership Project, the third generation partnership project
  • Multiple USIMs connected to the network register concurrently.
  • the terminal device with multiple USIMs may need to be associated with a USIM that is different from the one of the USIMs perform certain activities (eg, listen for pages, respond to pages, perform mobility updates, etc.) in another system that is referred to as a non-currently connected system.
  • a terminal device with multiple USIMs When a terminal device with multiple USIMs receives a page from a non-currently connected system for notifying an MT (Mobile Terminated, terminal to receive) service to be received, if there is a running service in the currently connected system, it has multiple USIMs.
  • a terminal device with multiple USIMs may send a busy indication to the network side, wherein a terminal device with multiple USIMs carries a busy indication in a specific non-access stratum (Non-Access Stratum, NAS) message.
  • Non-Access Stratum Non-Access Stratum
  • the busy indication may not be carried in the NAS message. Therefore, in a communication scenario where the terminal device is in an RRC-inactive state , how to timely notify the access network equipment that the terminal equipment is in a busy state is very important for saving paging resources.
  • RRC Radio Resource Control
  • Embodiments of the present application provide a paging processing method and apparatus, which can be applied to a scenario of communication between a terminal device and an access network device in a cellular mobile communication technology, so that a terminal device in an RRC inactive state can recover a request through RRC
  • the message sends a busy indication to the access network device, so that the access network device learns that the terminal device is in a busy state through the RRC recovery request message, thereby reducing the waste of paging resources.
  • an embodiment of the present application provides a paging processing method, the method is executed by a terminal device, and the method includes: receiving a paging request for a non-currently connected system forwarded by an access network device; responding to the The current connection system of the terminal device is in a busy state, and sends a radio resource control RRC recovery request message to the access network device, wherein the RRC recovery request message includes a busy indication; wherein, the terminal device has a first communication card and a A second communication card, the terminal device uses the first communication card to communicate with the currently connected system, and the terminal device uses the second communication card to communicate with the non-currently connected system.
  • a paging request for a non-currently connected system is received, and when it is determined that the currently connected system of the terminal device is in a busy state, an RRC recovery request message carrying a busy indication is sent to the access network device. Therefore, the terminal equipment in the RRC inactive state can send a busy indication to the access network equipment through the RRC recovery request message, so that the access network equipment can quickly know that the terminal equipment is in a busy state through the RRC recovery request message, thereby reducing the waste of paging resources. .
  • the RRC recovery request message further includes a message verification code MAC
  • the input parameters required for generating the MAC include specified message content, integrity key, count value, bearer identifier, and transmission direction information
  • the specified message content includes the busy indication
  • the method further includes: performing a message verification code calculation on the specified message content according to the integrity key, the count value, the bearer identifier and the transmission direction information, The MAC is generated.
  • the RRC recovery request message includes a message verification code MAC
  • the input parameters required for generating the MAC include recovery reason information element, specified message content, integrity key, count value, bearer identifier, and transmission direction information.
  • the method further includes: performing an analysis on the designated message according to the integrity key, the recovery cause information element, the count value, the bearer identifier and the transmission direction information.
  • the content performs message verification code calculation to generate the MAC.
  • the recovery cause information element of the RRC recovery request message includes the busy indication.
  • an embodiment of the present application provides another paging processing method.
  • the method is executed by an access network device, and the method includes: forwarding a paging request for a non-currently connected system to a terminal device;
  • the radio resource control RRC recovery request message sent by the terminal device determines that the current connection system of the terminal device is in a busy state, wherein the RRC recovery request message includes a busy indication.
  • a paging request for a non-currently connected system is forwarded to a terminal device, and when an RRC recovery request message carrying a busy indication sent by the terminal device is received, the current state of the terminal device is determined.
  • the connection system is busy. Therefore, the access network device can quickly know that the terminal device in the RRC inactive state is in the busy state through the busy indication in the RRC recovery request message, thereby reducing the waste of paging resources.
  • the determining that the current connection system of the terminal device is in a busy state includes: extracting a first message verification code MAC from the RRC recovery request message; acquiring input parameters required for generating the MAC generating a second MAC according to the input parameters required for generating the MAC; in the case that the first MAC and the second MAC are consistent, determine that the current connection system of the terminal device is in a busy state.
  • the input parameters required for generating the MAC include a specified message content, an integrity key, a count value, a bearer identifier, and transmission direction information
  • the specified message content includes the busy indication
  • the input parameters required for generating the MAC include a recovery cause information element, a specified message content, an integrity key, a count value, a bearer identifier, and transmission direction information.
  • the recovery cause information element of the RRC recovery request message includes the busy indication.
  • an embodiment of the present application provides a paging processing apparatus, and the paging processing apparatus has part or all of the functions of the terminal device in the method described in the first aspect above.
  • the functions of the paging processing apparatus may have this function.
  • the functions in some or all of the embodiments in the application may also have the functions of independently implementing any one of the embodiments in the application.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • an embodiment of the present application provides another paging processing apparatus, the paging processing apparatus has some or all of the functions of the access network equipment in the method example described in the second aspect above, such as the paging processing apparatus.
  • the functions may have the functions of some or all of the embodiments in the present application, and may also have the functions of independently implementing any one of the embodiments of the present application.
  • the functions can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • an embodiment of the present application provides a paging processing apparatus, the apparatus includes a processor, and when the processor calls a computer program in a memory, the method described in the first aspect is executed.
  • an embodiment of the present application provides a paging processing apparatus, the apparatus includes a processor, and when the processor invokes a computer program in a memory, the method described in the second aspect above is executed.
  • an embodiment of the present application provides a paging processing apparatus, the apparatus includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the apparatus executes The method described in the first aspect above.
  • an embodiment of the present application provides a paging processing device, the device includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory, so that the device executes The method described in the second aspect above.
  • an embodiment of the present application provides a paging processing device, the device includes a processor and an interface circuit, the interface circuit is configured to receive a code instruction and transmit it to the processor, and the processor is configured to run the code instruction to The apparatus is caused to perform the method described in the first aspect above.
  • an embodiment of the present application provides a paging processing device, the device includes a processor and an interface circuit, the interface circuit is configured to receive a code instruction and transmit it to the processor, and the processor is configured to run the code instruction to The apparatus is caused to perform the method of the second aspect above.
  • an embodiment of the present application provides a communication system, where the system includes the paging processing apparatus described in the third aspect and the paging processing apparatus described in the fourth aspect, or the system includes the paging processing apparatus described in the fifth aspect
  • the paging processing device and the paging processing device described in the sixth aspect or the system includes the paging processing device described in the seventh aspect and the paging processing device described in the eighth aspect, or the system includes the paging processing device described in the sixth aspect.
  • an embodiment of the present invention provides a computer-readable storage medium for storing an instruction used by the above-mentioned access network device.
  • the terminal device is made to execute the above-mentioned first aspect. method described.
  • an embodiment of the present invention provides a readable storage medium for storing an instruction used by the above-mentioned terminal device, and when the instruction is executed, the access network device is caused to execute the above-mentioned second aspect.
  • the present application further provides a computer program product comprising a computer program, which, when run on a computer, causes the computer to execute the method described in the first aspect.
  • the present application further provides a computer program product comprising a computer program, which, when run on a computer, causes the computer to execute the method described in the second aspect above.
  • the present application provides a chip system
  • the chip system includes at least one processor and an interface, configured to support an access network device to implement the functions involved in the first aspect, for example, determining or processing the functions involved in the above method. at least one of the data and information.
  • the chip system further includes a memory for storing necessary computer programs and data of the access network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present application provides a chip system
  • the chip system includes at least one processor and an interface for supporting a terminal device to implement the functions involved in the second aspect, for example, determining or processing data involved in the above method and at least one of information.
  • the chip system further includes a memory for storing necessary computer programs and data of the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the present application provides a computer program that, when executed on a computer, causes the computer to execute the method described in the first aspect.
  • the present application provides a computer program that, when executed on a computer, causes the computer to execute the method described in the second aspect above.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a paging processing method provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of another paging processing method provided by an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of another paging processing method provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another paging processing method provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a paging processing method provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of another paging processing method provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a paging processing apparatus provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another paging processing apparatus provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a chip provided by an embodiment of the present application.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present application.
  • the communication system may include, but is not limited to, an access network device and a terminal device.
  • the number and shape of the devices shown in FIG. 1 are only for examples and do not constitute a limitation to the embodiments of the present application. In practical applications, two or two devices may be included. More than one access network device and two or more terminal devices.
  • the communication system shown in FIG. 1 includes one access network device 101 and one terminal device 102 as an example.
  • LTE long term evolution
  • 5G fifth generation
  • NR 5G new radio
  • the access network device 101 in the embodiment of the present application is an entity on the network side for transmitting or receiving signals.
  • the access network device 101 may be an evolved base station (evolved NodeB, eNB), a transmission point (transmission reception point, TRP), a next generation base station (next generation NodeB, gNB) in an NR system, and other future mobile communication systems.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device.
  • the access network device provided in this embodiment of the present application may be composed of a centralized unit (central unit, CU) and a distributed unit (distributed unit, DU).
  • the structure of the DU can separate the protocol layers of the access network equipment, such as the base station, and the functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the CU centrally controls the DU .
  • the terminal device 102 in this embodiment of the present application is an entity on the user side that is used to receive or transmit signals, such as a mobile phone.
  • a terminal device may also be referred to as a terminal device (terminal), a user equipment (UE), a mobile station (mobile station, MS), a mobile terminal device (mobile terminal, MT), and the like.
  • the terminal device can be a car with a communication function, a smart car, a mobile phone (mobile phone), a wearable device, a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (virtual reality, VR) terminal device, augmented reality (augmented reality (AR) terminal equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self-driving, wireless terminal equipment in remote medical surgery, smart grid ( Wireless terminal equipment in smart grid), wireless terminal equipment in transportation safety, wireless terminal equipment in smart city, wireless terminal equipment in smart home, etc.
  • the embodiments of the present application do not limit the specific technology and specific device form adopted by the terminal device.
  • a terminal device with multiple USIMs only responds to a paging from a non-currently connected system according to the existing procedure, but the above-mentioned way of responding to a paging will interrupt the running service in the currently connected system.
  • a terminal device with multiple USIMs does not respond to paging from a non-currently connected system.
  • the non-currently connected system will maintain the The paging of the terminal equipment of each USIM, thus, will cause the resources of the non-currently connected system to be wasted.
  • a terminal device having multiple USIMs may send a busy indication to the network side, wherein the terminal device having multiple USIMs carries a busy indication in a specific non-access stratum (Non-Access Stratum, NAS) message.
  • NAS Non-Access Stratum
  • the busy indication may not be carried in the NAS message. Therefore, the above-mentioned specific NAS message carries the busy indication mode, not applicable to terminal equipment in RRC inactive state.
  • a paging request for a non-currently connected system is received, and an RRC recovery request message carrying a busy indication is sent to the access network device when it is determined that the currently connected system of the terminal device is in a busy state. Therefore, the terminal equipment in the RRC inactive state can send a busy indication to the access network equipment through the RRC recovery request message, so that the access network equipment can quickly know that the terminal equipment is in a busy state through the RRC recovery request message, thereby reducing the waste of paging resources. .
  • the access network device when the access network device receives the busy indication, the access network device can stop paging the terminal device, so as to reduce resource occupation and save paging resources.
  • FIG. 2 is a schematic flowchart of a paging processing method provided by an embodiment of the present application.
  • the method is applied to the terminal equipment in the communication system shown in FIG. 1 .
  • the method is executed by the terminal device in the communication system shown in FIG. 1, and as shown in FIG. 2, the method may include but not limited to the following steps:
  • Step S201 Receive a paging request for a non-currently connected system forwarded by an access network device.
  • the above-mentioned paging request is sent by the core network device to the access network device.
  • Step S202 In response to the current connection system of the terminal device being in a busy state, send a radio resource control RRC recovery request message to the access network device, wherein the RRC recovery request message includes a busy indication.
  • the terminal device has a first communication card and a second communication card, the terminal device uses the first communication card to communicate with the currently connected system, and the terminal device uses the second communication card to communicate with the non-currently connected system.
  • the recovery cause information element (Information Element, IE) of the RRC recovery request message may include a busy indication. That is, the busy indication can be used as the cause value of the recovery cause information element.
  • the access network device receives the RRC recovery request message sent by the terminal device, and obtains the recovery cause information element of the RRC recovery request message, and determines that the recovery cause information element is a busy indication, it can determine that the terminal device In a busy state, then the access network device can stop sending paging requests for the non-currently connected system to the terminal device, saving paging resources, and can not interrupt the ongoing service of the terminal device's currently connected system.
  • the cause value of the restoration cause information element may also include other cause values included in the current protocol, for example, a cause value for indicating a higher priority access, or a cause value for indicating an emergency situation.
  • the currently connected system refers to the system corresponding to the network currently accessed by the terminal device, and the system and the terminal device are in the connection mode;
  • the non-currently connected system refers to the system corresponding to the network currently accessed by the terminal device , and the system and the terminal device are in idle mode, wherein, in order to distinguish different communication cards in the terminal device, the communication card in the terminal device that communicates with the currently connected system may be called the first communication card in the present disclosure, and the terminal device is referred to as the first communication card.
  • the communication card in the device that communicates with the non-currently connected system is called the second communication card.
  • the terminal device has two communication cards, and the two communication cards are a mobile communication card and a telecommunication communication card respectively.
  • the currently connected system may be a system corresponding to the mobile network
  • the non-currently connected system may be a system corresponding to the telecommunication network.
  • the terminal device has two communication cards, both of which are mobile communication cards, for exemplary illustration.
  • the currently connected system may be the system 1 corresponding to the mobile network
  • the non-currently connected system may be the system 2 corresponding to the mobile network, that is, both the system 1 and the system 2 are systems corresponding to the mobile network.
  • the terminal device may use the second communication card to receive a paging request for the non-currently connected system forwarded by the access network device, where the paging request is used to page the terminal device.
  • the core network device of the non-currently connected system may send a paging request to the terminal device through the access network device, and correspondingly, the terminal device may use the second communication card to receive the message for the non-currently connected system forwarded by the access network device. paging request.
  • the access network device may stop paging the terminal device to reduce resource occupation.
  • a paging request for a non-currently connected system is received, and an RRC recovery request message carrying a busy indication is sent to the access network device when it is determined that the currently connected system of the terminal device is in a busy state. Therefore, the terminal equipment in the RRC inactive state can send a busy indication to the access network equipment through the RRC recovery request message, so that the access network equipment can quickly know that the terminal equipment is in a busy state through the RRC recovery request message, thereby reducing the waste of paging resources. .
  • FIG. 3 is a schematic flowchart of another paging processing method provided by an embodiment of the present application.
  • the method is applied to the terminal equipment in the communication system shown in FIG. 1 .
  • the paging processing method can be executed alone, or can be executed in combination with any of the embodiments of the present disclosure or possible implementation manners of the embodiments, and can also be executed in conjunction with any technical solution in the related art .
  • the method may include but is not limited to the following steps:
  • Step S301 Receive a paging request for a non-currently connected system forwarded by an access network device.
  • the paging request is sent by the core network device to the access network device.
  • Step S302 In response to the current connection system of the terminal device being in a busy state, send a radio resource control RRC recovery request message to the access network device, wherein the RRC recovery request message includes a busy indication and a message verification code MAC.
  • the terminal device has a first communication card and a second communication card, wherein the terminal device uses the first communication card to communicate with the currently connected system, and the terminal device uses the second communication card to communicate with the non-currently connected system.
  • the above RRC recovery request message may also include a message authentication code (Message Authentication Code, MAC).
  • MAC Message Authentication Code
  • the access network device can perform integrity verification on the key information in the RRC recovery request message based on the message verification code, and in the case of determining that the integrity verification of the key information in the RRC recovery request message is successful, determine the terminal device The currently connected system is in a busy state, and then the access network device can stop sending paging requests to the terminal device for the non-currently connected system, saving paging resources, and can not interrupt the ongoing service of the terminal device's currently connected system.
  • MAC message Authentication Code
  • the above input parameters required for generating the MAC include specified message content, integrity key, count value, bearer identifier and transmission direction information, and the specified message content includes busy instruct.
  • the input parameters required by the MAC include an AS integrity key named KEY (K RRcint ), a 32-bit COUNT (count value), a 5-bit bearer identifier (BEARER) for the bearer identity, a 1-bit transmission direction information (DIRECTION), where DIRECTION is 0 for uplink and 1 for downlink, and specifies the message content (MESSAGE).
  • the specified message content is the cell information VarResumeMAC-Input or VarShortMAC-Input of the access network device.
  • VarResumeMAC-Input and VarShortMAC-Input both include the following information: the identification information of the source cell, the identification information of the target cell, the wireless network temporary identifier (Cell-RadioNetworkTemporaryIdentifier, C-RNTI) of the terminal device in the source cell and busy indication.
  • C-RNTI Cell-RadioNetworkTemporaryIdentifier
  • the recovery reason information element (Information Element, IE) of the RRC recovery request message may include a busy indication. That is, the busy indication can be used as the cause value of the recovery cause information element.
  • the access network device when the access network device receives the RRC recovery request message sent by the terminal device, and obtains the recovery cause information element of the RRC recovery request message, and determines that the recovery cause information element is a busy indication, it can determine that the terminal device In a busy state, then the access network device can stop sending paging requests for the non-currently connected system to the terminal device, saving paging resources, and can not interrupt the ongoing service of the terminal device's currently connected system.
  • the cause value of the restoration cause information element may also be other cause values included in the current protocol, for example, a cause value for indicating a higher priority access, or a cause value for indicating an emergency.
  • a paging request for a non-currently connected system is received, and an RRC recovery request message carrying a busy indication and a MAC is sent to the access network device when it is determined that the currently connected system of the terminal device is in a busy state. Therefore, the terminal device in the RRC inactive state can send the busy indication and the MAC to the access network device through the RRC recovery request message, so that the access network device can perform integrity verification on the key information of the received message based on the MAC. , and in the case of successful integrity verification, it is determined that the terminal device is in a busy state to reduce waste of paging resources.
  • FIG. 4 is a schematic flowchart of another paging processing method provided by an embodiment of the present application.
  • the method is applied to the terminal equipment in the communication system shown in FIG. 1 .
  • the paging processing method can be executed alone, or can be executed in combination with any of the embodiments of the present disclosure or possible implementation manners of the embodiments, and can also be executed in conjunction with any technical solution in the related art .
  • the method may include but is not limited to the following steps:
  • Step S401 Receive a paging request for a non-currently connected system forwarded by an access network device.
  • Step S402 In response to the current connection system of the terminal device being in a busy state, obtain the input parameters required for generating the MAC, wherein the input parameters include the specified message content, the integrity key, the count value, the bearer identifier and the transmission direction information, and the specified message Content includes busy indication.
  • the above-mentioned integrity key may be obtained from the access stratum AS context stored in the terminal device. It should be noted that the above AS context is shared between the terminal device and the access network device.
  • Step S403 Calculate the message verification code for the content of the specified message according to the integrity key, the count value, the bearer identifier and the transmission direction information, and generate a MAC.
  • the integrity algorithm agreed between the terminal device and the access network device can be obtained, and based on the integrity algorithm, message verification is performed on the specified message content according to the integrity key, count value, bearer identifier and transmission direction information code calculation to generate MAC.
  • the terminal device and the access network device in order to enable the terminal device and the access network device to generate the MAC in the same manner, it may be specified in the communication protocol on which the two communicate with each other.
  • the bearer In the case of generating the MAC, the bearer will identify its corresponding All bits are set to 1; all bits corresponding to the count value are set to 1; all bits of the transmission direction information are set to 1.
  • the above-mentioned integrity algorithm may also be obtained from the access stratum AS context stored in the terminal device. That is, in some embodiments, the above-mentioned access stratum AS context may include an integrity algorithm and an integrity key.
  • Step S404 Send an RRC recovery request message to the access network device, where the RRC recovery request message includes a busy indication and a MAC.
  • the recovery cause information element (Information Element, IE) of the RRC recovery request message may include a busy indication. That is, the busy indication can be used as the cause value of the recovery cause information element. That is, the busy indication can be used as the cause value of the recovery cause information element.
  • the access network device when the access network device receives the RRC recovery request message sent by the terminal device, and obtains the recovery cause information element of the RRC recovery request message, and determines that the recovery cause information element is a busy indication, it can determine that the terminal device In a busy state, then the access network device can stop sending paging requests for the non-currently connected system to the terminal device, saving paging resources, and can not interrupt the ongoing service of the terminal device's currently connected system.
  • the cause value of the restoration cause information element may also be other cause values included in the current protocol, for example, a cause value for indicating a higher priority access, or a cause value for indicating an emergency.
  • a paging request for a non-currently connected system is received, and when it is determined that the currently connected system of the terminal device is in a busy state, the input parameters required to generate the MAC are obtained, and the input parameters required for generating the MAC are obtained based on the integrity key and the count value.
  • FIG. 5 is a schematic flowchart of another paging processing method provided by an embodiment of the present application.
  • the method is applied to the terminal equipment in the communication system shown in FIG. 1 .
  • the paging processing method can be executed alone, or can be executed in combination with any of the embodiments of the present disclosure or possible implementation manners of the embodiments, and can also be executed in conjunction with any technical solution in the related art .
  • the method may include but is not limited to the following steps:
  • Step S501 Receive a paging request for a non-currently connected system forwarded by an access network device.
  • the paging request is sent by the core network device to the access network device.
  • Step S502 In response to the current connection system of the terminal device being in a busy state, obtain the input parameters required to generate the MAC, wherein the input parameters include the recovery reason information element, the specified message content, the integrity key, the count value, the bearer identifier and the transmission direction information.
  • Step S503 Calculate the message verification code for the content of the specified message according to the integrity key, the restoration reason information element, the count value, the bearer identifier and the transmission direction information, and generate a MAC.
  • the recovery reason information element in order to prevent the content of the specified message from being tampered with and reduce the impact on the current protocol, can be used as one of the additional input parameters for calculating the MAC.
  • the input parameters required by the MAC include the recovery reason information element, an AS integrity key named KEY (K RRcint ), a 32-bit COUNT (count value), and a 5-bit bearer identification for bearer identity (BEARER), a 1-bit transmission direction information (DIRECTION), where DIRECTION is 0 for uplink and 1 for downlink, and specifies the message content (MESSAGE).
  • the specified message content is the cell information VarResumeMAC-Input or VarShortMAC-Input of the access network device.
  • VarResumeMAC-Input and VarShortMAC-Input both include the following information: the identification information of the source cell, the identification information of the target cell, the wireless network temporary identifier (Cell-RadioNetworkTemporaryIdentifier, C-RNTI) of the terminal device in the source cell .
  • C-RNTI Cell-RadioNetworkTemporaryIdentifier
  • the above-mentioned integrity key may be obtained from the access stratum AS context stored in the terminal device. It should be noted that the above AS context is shared between the terminal device and the access network device.
  • the integrity algorithm agreed between the terminal device and the access network device can be obtained, and based on the integrity algorithm, the specified data can be assigned according to the integrity key, the recovery reason information element, the count value, the bearer identifier and the transmission direction information.
  • the message content is calculated by the message verification code to generate the MAC.
  • the terminal device and the access network device in order to enable the terminal device and the access network device to generate the MAC in the same manner, it may be specified in the communication protocol on which the two communicate with each other.
  • the bearer In the case of generating the MAC, the bearer will identify its corresponding All bits are set to 1; all bits corresponding to the count value are set to 1; all bits of the transmission direction information are set to 1.
  • the above-mentioned integrity algorithm may also be obtained from the access stratum AS context stored in the terminal device. That is, in some embodiments, the above-mentioned access stratum AS context may include an integrity algorithm and an integrity key.
  • Step S504 Send the RRC recovery request message to the access network device, including the busy indication and the message verification code MAC.
  • the terminal device has a first communication card and a second communication card, wherein the terminal device uses the first communication card to communicate with the currently connected system, and the terminal device uses the second communication card to communicate with the non-currently connected system.
  • the recovery cause information element (Information Element, IE) of the RRC recovery request message may include a busy indication. That is, the busy indication can be used as the cause value of the recovery cause information element. That is, the busy indication can be used as the cause value of the recovery cause information element. That is, the busy indication can be used as the cause value of the recovery cause information element.
  • the access network device when the access network device receives the RRC recovery request message sent by the terminal device, and obtains the recovery cause information element of the RRC recovery request message, and determines that the recovery cause information element is a busy indication, it can determine that the terminal device In a busy state, then the access network device can stop sending paging requests for the non-currently connected system to the terminal device, saving paging resources, and can not interrupt the ongoing service of the terminal device's currently connected system.
  • the cause value of the restoration cause information element may also be other cause values included in the current protocol, for example, a cause value for indicating a higher priority access, or a cause value for indicating an emergency.
  • a paging request for a non-currently connected system is received, and when it is determined that the currently connected system of the terminal device is in a busy state, the input parameters required to generate the MAC are obtained, and the input parameters required for generating the MAC are obtained according to the integrity key and the recovery reason.
  • the information element, count value, bearer identification and transmission direction information perform message verification code calculation on the content of the specified message, generate a MAC, and send an RRC recovery request message carrying a busy indication and a MAC to the access network device.
  • the terminal device in the RRC inactive state can send the busy indication and the MAC to the access network device through the RRC recovery request message, so that the access network device can perform integrity verification on the key information of the received message based on the MAC. , and in the case of successful integrity verification, it is determined that the terminal device is in a busy state to reduce waste of paging resources.
  • FIG. 6 is a schematic flowchart of a paging processing method provided by an embodiment of the present application.
  • the method is applied to the access network equipment in the communication system shown in FIG. 1 .
  • the method may be performed by an access network device in the communication system shown in FIG. 1 .
  • the method may include but is not limited to the following steps:
  • Step S601 Forward the paging request for the non-currently connected system to the terminal device.
  • the above-mentioned paging request is sent by the core network device to the access network device.
  • the terminal device has a first communication card and a second communication card, wherein the terminal device uses the first communication card to communicate with the currently connected system, and the terminal device uses the second communication card to communicate with the non-currently connected system.
  • Step S602 In response to receiving the radio resource control RRC recovery request message sent by the terminal device, determine that the current connection system of the terminal device is in a busy state, wherein the RRC recovery request message includes a busy indication.
  • the recovery cause information element (Information Element, IE) of the RRC recovery request message may include a busy indication. That is, the busy indication can be used as the cause value of the recovery cause information element.
  • the access network device receives the RRC recovery request message sent by the terminal device, and obtains the recovery cause information element of the RRC recovery request message, and determines that the recovery cause information element is a busy indication, it can determine that the terminal device In a busy state, then the access network device can stop sending paging requests for the non-currently connected system to the terminal device, saving paging resources, and can not interrupt the ongoing service of the terminal device's currently connected system.
  • the reason value of the restoration reason information element may also be other reason values included in the current protocol, for example, a reason value for indicating a higher priority access, or a reason value for indicating an emergency situation, for example, for Reason value to indicate higher priority access, or to indicate urgency.
  • the paging request for the non-currently connected system is forwarded to the terminal device, and in the case of receiving the RRC recovery request message carrying the busy indication sent by the terminal device, it is determined that the currently connected system of the terminal device is busy state. Therefore, the access network device can quickly know that the terminal device in the RRC inactive state is in a busy state through the busy indication in the RRC recovery request message, thereby reducing waste of paging resources.
  • FIG. 7 is a schematic flowchart of another paging processing method provided by an embodiment of the present application.
  • the method is applied to the access network equipment in the communication system shown in FIG. 1 . That is, the method can be executed by the access network device in the communication system shown in FIG. 1 .
  • a possible implementation manner of determining that the current connection system of the terminal device is in a busy state is as follows:
  • Step S701 Extract the first message verification code MAC from the RRC recovery request message.
  • Step S702 Obtain input parameters required for generating the MAC.
  • Step S703 Generate a second MAC according to the input parameters required for generating the MAC.
  • Step S704 In the case that the first MAC and the second MAC are consistent, it is determined that the current connection system of the terminal device is in a busy state.
  • the input parameters required for generating the MAC include specified message content, integrity key, count value, bearer identifier, and transmission direction information
  • the specified message content includes a busy indication.
  • the specific implementation manner of generating the second MAC according to the input parameters required for generating the MAC may be: performing message verification code calculation on the content of the specified message according to the integrity key, count value, bearer identifier and transmission direction information to generate the second MAC.
  • the input parameters required by the MAC include an AS integrity key named KEY (K RRcint ), a 32-bit COUNT (count value), a 5-bit bearer identifier (BEARER) for the bearer identity, a 1-bit transmission direction information (DIRECTION), where DIRECTION is 0 for uplink and 1 for downlink, and specifies the message content (MESSAGE).
  • the specified message content is the cell information VarResumeMAC-Input or VarShortMAC-Input of the access network device.
  • VarResumeMAC-Input and VarShortMAC-Input both include the following information: the identification information of the source cell, the identification information of the target cell, the wireless network temporary identifier (Cell-RadioNetworkTemporaryIdentifier, C-RNTI) of the terminal device in the source cell and busy indication.
  • C-RNTI Cell-RadioNetworkTemporaryIdentifier
  • the above-mentioned integrity key may be obtained from the access stratum AS context stored in the access network device. It should be noted that the above AS context is shared between the terminal device and the access network device.
  • the integrity algorithm agreed between the terminal device and the access network device can be obtained, and based on the integrity algorithm, message verification is performed on the specified message content according to the integrity key, count value, bearer identifier and transmission direction information code calculation to generate the first MAC.
  • the above-mentioned integrity algorithm may also be obtained from the access stratum AS context stored in the access network device. That is, in some embodiments, the above-mentioned access stratum AS context may include an integrity algorithm and an integrity key.
  • the terminal device and the access network device in order to enable the terminal device and the access network device to generate the MAC in the same manner, it may be specified in the communication protocol on which the two communicate with each other.
  • the bearer In the case of generating the MAC, the bearer will identify its corresponding All bits are set to 1; all bits corresponding to the count value are set to 1; all bits of the transmission direction information are set to 1.
  • the above-mentioned input parameters required for generating the MAC include a recovery cause information element, a specified message content, an integrity key, a count value, a bearer identifier, and transmission direction information.
  • the specific implementation manner of generating the second MAC according to the input parameters required for generating the MAC may be: performing a message verification code on the specified message content according to the recovery reason information element, the integrity key, the count value, the bearer identifier and the transmission direction information. Calculate to generate a second MAC.
  • the above-mentioned integrity key may be obtained from the access stratum AS context stored in the access network device. It should be noted that the above AS context is shared between the terminal device and the access network device.
  • the integrity algorithm agreed between the terminal device and the access network device can be obtained, and based on the integrity algorithm, the specified data can be assigned according to the recovery reason information element, the integrity key, the count value, the bearer identifier and the transmission direction information.
  • the message content is calculated by the message verification code to generate the second MAC.
  • the above-mentioned integrity algorithm may also be obtained from the access stratum AS context stored in the access network device. That is, in some embodiments, the above-mentioned access stratum AS context may include an integrity algorithm and an integrity key.
  • the terminal device and the access network device in order to enable the terminal device and the access network device to generate the MAC in the same manner, it may be specified in the communication protocol on which the two communicate with each other.
  • the bearer In the case of generating the MAC, the bearer will identify its corresponding All bits are set to 1; all bits corresponding to the count value are set to 1; all bits of the transmission direction information are set to 1.
  • the recovery cause information element of the RRC recovery request message includes a busy indication.
  • the implementation manner of generating the second MAC according to the input parameters required for generating the MAC may be: according to the recovery reason information element, the integrity key, the count value, the bearer identifier and the transmission direction information, the message verification code calculation is performed on the specified message content. , to generate the second MAC.
  • the access network device after the access network device receives the radio resource control RRC recovery request message sent by the terminal device, it can extract the first MAC and the recovery reason information element from the RRC recovery request message.
  • the second MAC when it is determined that the recovery cause information element is a busy indication, the second MAC can be generated according to the busy indication and the input parameters required for generating the MAC, wherein the input parameters can include an integrity key, a count value, a bearer Identify, specify message content and transfer direction information.
  • the second MAC can be generated by performing message verification code calculation on the content of the specified message according to the recovery reason information element, the integrity key, the count value, the bearer identifier and the transmission direction information.
  • the access network device may determine that the current connection system of the terminal device is in a busy state.
  • the access network device will not be able to identify the RRC recovery request message in the The recovery reason IE is busy indication. Therefore, the second MAC generated based on the input parameters required for generating the MAC and the recovery reason IE does not match the first MAC, and at this time, the integrity verification fails.
  • the methods provided by the embodiments of the present application are respectively introduced from the perspectives of access network equipment and terminal equipment.
  • the access network device and the terminal device may include hardware structures and software modules, and the above functions are implemented in the form of hardware structures, software modules, or hardware structures plus software modules.
  • a certain function among the above functions may be implemented in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 8 is a schematic structural diagram of a paging processing apparatus 80 provided by an embodiment of the present application.
  • the paging processing apparatus 80 shown in FIG. 8 may include a transceiving unit 801 and a processing unit 802 .
  • the transceiver unit 801 may include a sending unit and/or a receiving unit, the sending unit is used to implement the sending function, the receiving unit is used to implement the receiving function, and the transceiver unit 801 may implement the sending function and/or the receiving function.
  • the paging processing apparatus 80 may be an access network device, or a device in the access network device, or a device that can be matched and used with the access network device.
  • the paging processing apparatus 80 may be a terminal device, may also be a device in the terminal device, or may be a device that can be matched and used with the terminal device.
  • the paging processing device 80 is a terminal device: the transceiver unit 801 is configured to receive a paging request for a non-currently connected system forwarded by the access network device; in response to the current connection system of the terminal device being in a busy state, send a message to the access network device.
  • Radio resource control RRC recovery request message wherein the RRC recovery request message includes a busy indication;
  • the terminal device has a first communication card and a second communication card, wherein the terminal device uses the first communication card to communicate with the currently connected system, and the terminal device A second communication card is used to communicate with a non-currently connected system.
  • the RRC recovery request message further includes a message verification code MAC
  • the input parameters required to generate the MAC include the specified message content, the integrity key, the count value, the bearer identifier, and the transmission direction information, and the specified message content Include busy indication.
  • the processing unit 802 is configured to perform message verification code calculation on the content of the specified message according to the integrity key, the count value, the bearer identifier and the transmission direction information to generate the MAC.
  • the RRC recovery request message includes a message verification code MAC
  • the input parameters required to generate the MAC include recovery reason information element, specified message content, integrity key, count value, bearer identifier, and transmission direction information .
  • the processing unit 802 is configured to perform message verification code calculation on the content of the specified message according to the integrity key, the recovery reason information element, the count value, the bearer identifier and the transmission direction information to generate the MAC.
  • the recovery cause information element of the RRC recovery request message includes a busy indication.
  • the paging processing device 80 is an access network device: a transceiver unit 801, configured to forward a paging request for a non-currently connected system to a terminal device.
  • the processing unit 802 is configured to, in response to receiving a radio resource control RRC recovery request message sent by the terminal device, determine that the current connection system of the terminal device is in a busy state, wherein the RRC recovery request message includes a busy indication.
  • the processing unit 802 is specifically configured to: extract the first message verification code MAC from the RRC recovery request message; obtain input parameters required for generating the MAC;
  • the second MAC is generated according to the input parameters required for generating the MAC; when the first MAC and the second MAC are consistent, it is determined that the current connection system of the terminal device is in a busy state.
  • the input parameters required for generating the MAC include a specified message content, an integrity key, a count value, a bearer identifier, and transmission direction information
  • the specified message content includes a busy indication
  • the input parameters required for generating the MAC include a recovery cause information element, a specified message content, an integrity key, a count value, a bearer identifier, and transmission direction information.
  • the recovery cause information element of the RRC recovery request message includes a busy indication.
  • FIG. 9 is a schematic structural diagram of another paging processing apparatus 90 provided by an embodiment of the present application.
  • the paging processing apparatus 90 may be an access network device, a terminal device, a chip, a chip system, or a processor that supports the access network device to implement the above method, or a terminal device that supports the above method.
  • a chip, a system on a chip, or a processor, etc. The apparatus can be used to implement the methods described in the foregoing method embodiments, and for details, reference may be made to the descriptions in the foregoing method embodiments.
  • the paging processing apparatus 90 may include one or more processors 901 .
  • the processor 901 may be a general-purpose processor or a special-purpose processor, or the like.
  • it may be a baseband processor or a central processing unit.
  • the baseband processor can be used to process the communication protocol and communication data
  • the central processing unit can be used to control the paging processing device (eg, base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute A computer program that processes data from a computer program.
  • the paging processing apparatus 90 may further include one or more memories 902 on which a computer program 903 may be stored, and the processor 901 executes the computer program 903, so that the paging processing apparatus 90 executes the above method embodiments. method described.
  • the computer program 903 may be embodied in the processor 901, in which case the processor 901 may be implemented by hardware.
  • data may also be stored in the memory 902 .
  • the paging processing device 90 and the memory 902 can be provided separately or integrated together.
  • the paging processing apparatus 90 may further include a transceiver 905 and an antenna 906 .
  • the transceiver 905 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is used to implement a transceiver function.
  • the transceiver 905 may include a receiver and a transmitter, the receiver may be called a receiver or a receiving circuit, etc., for implementing a receiving function; the transmitter may be called a transmitter or a transmitting circuit, etc., for implementing a transmitting function.
  • the paging processing apparatus 90 may further include one or more interface circuits 907 .
  • the interface circuit 907 is used to receive code instructions and transmit them to the processor 901 .
  • the processor 901 executes the code instructions to cause the paging processing apparatus 90 to execute the methods described in the above method embodiments.
  • the paging processing apparatus 90 is a terminal device: the transceiver 905 is used to perform steps S201 and S202 in FIG. 2 ; steps S301 and S302 in FIG. 3 ; steps S401 and S404 in FIG. 4 ; Step S501, Step S504.
  • the processor 901 is configured to execute steps S402 and S403 in FIG. 4 ; and steps S502 and S503 in FIG. 5 .
  • the above-mentioned paging processing apparatus 90 is an access network device, and the above-mentioned transceiver 905 is configured to perform step S601 in FIG. 6 .
  • the processor 901 is configured to execute step S602 in FIG. 6 ; step S701 to step S704 in FIG. 7 .
  • the processor 901 may include a transceiver for implementing receiving and transmitting functions.
  • the transceiver may be a transceiver circuit, or an interface, or an interface circuit.
  • Transceiver circuits, interfaces or interface circuits used to implement receiving and transmitting functions may be separate or integrated.
  • the above-mentioned transceiver circuit, interface or interface circuit can be used for reading and writing code/data, or the above-mentioned transceiver circuit, interface or interface circuit can be used for signal transmission or transmission.
  • the paging processing apparatus 90 may include a circuit, and the circuit may implement the function of sending or receiving or communicating in the foregoing method embodiments.
  • the processors and transceivers described in this application can be implemented in integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application specific integrated circuits (ASICs), printed circuit boards ( printed circuit board, PCB), electronic equipment, etc.
  • the processor and transceiver can also be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), nMetal-oxide-semiconductor (NMOS), P-type Metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
  • CMOS complementary metal oxide semiconductor
  • NMOS nMetal-oxide-semiconductor
  • PMOS P-type Metal oxide semiconductor
  • BJT bipolar junction transistor
  • BiCMOS bipolar CMOS
  • SiGe silicon germanium
  • GaAs gallium arsenide
  • the paging processing apparatus described in the above embodiments may be access network equipment or terminal equipment, but the scope of the paging processing apparatus described in this application is not limited to this, and the structure of the paging processing apparatus may not be affected by the structure shown in FIG. 9 . limit.
  • the paging processing means may be a stand-alone device or may be part of a larger device.
  • the paging processing means may be:
  • the IC set can also include a storage component for storing data and computer programs;
  • ASIC such as modem (Modem);
  • the paging processing apparatus may be a chip or a chip system
  • the chip shown in FIG. 10 includes a processor 1001 and an interface 1002 .
  • the number of processors 1001 may be one or more, and the number of interfaces 1002 may be multiple.
  • the processor 1001 is configured to run code instructions to execute the methods as shown in FIG. 2 to FIG. 5 .
  • the processor 1001 is configured to run code instructions to execute the methods as shown in FIG. 6 to FIG. 7 .
  • the chip further includes a memory 1003 for storing necessary computer programs and data.
  • An embodiment of the present application further provides a communication system, where the system includes the paging processing apparatus as the terminal device and the paging processing apparatus as the access network device in the foregoing embodiment in FIG. 8 , or the system includes the foregoing embodiment in FIG. 9 The paging processing device as the terminal equipment and the paging processing device as the access network equipment.
  • the present application further provides a readable storage medium on which instructions are stored, and when the instructions are executed by a computer, implement the functions of any of the foregoing method embodiments.
  • the present application further provides a computer program product, which implements the functions of any of the above method embodiments when the computer program product is executed by a computer.
  • a computer program product includes one or more computer programs.
  • the computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer program can be stored on or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer program can be transferred from a website site, computer, server, or data center over a wire (e.g.
  • coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless means to transmit to another website site, computer, server or data center.
  • a computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes an integration of one or more available media.
  • Useful media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, high-density digital video disc (DVD)), or semiconductor media (eg, solid state disk (SSD)) )Wait.
  • At least one in this application may also be described as one or more, and the multiple may be two, three, four or more, which is not limited in this application.
  • the technical feature is distinguished by “first”, “second”, “third”, “A”, “B”, “C” and “D”, etc.
  • the technical features described in the “first”, “second”, “third”, “A”, “B”, “C” and “D” described technical features in no order or order of magnitude.
  • the corresponding relationships shown in each table in this application may be configured or predefined.
  • the values of the information in each table are only examples, and can be configured with other values, which are not limited in this application.
  • the corresponding relationships shown in some rows may not be configured.
  • appropriate deformation adjustments can be made based on the above table, for example, splitting, merging, and so on.
  • the names of the parameters shown in the headings in the above tables may also adopt other names that can be understood by the communication device, and the values or representations of the parameters may also be other values or representations that the communication device can understand.
  • other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables. Wait.
  • Predefined in this application may be understood as defining, predefining, storing, pre-storing, pre-negotiating, pre-configuring, curing, or pre-firing.

Landscapes

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

Abstract

本申请实施例公开了一种寻呼处理方法及其装置，可以应用于蜂窝移动通信技术中，该方法包括：接收针对非当前连接系统的寻呼请求，在确定终端设备的当前连接系统处于繁忙状态的情况下，向接入网设备发送携带有繁忙指示的RRC恢复请求消息。由此，使得处于RRC非活动状态的终端设备可通过RRC恢复请求消息向接入网设备发送繁忙指示，使得接入网设备通过RRC恢复请求消息快速获知终端设备处于繁忙状态，减少寻呼资源浪费。

Description

寻呼处理方法及其装置 技术领域
本申请涉及通信技术领域，尤其涉及一种寻呼处理方法及其装置。
背景技术
具有多个USIM(Universal Subscriber Identity Module，全球用户识别卡)的终端设备可以通过多个与3GPP(the 3rd Generation Partnership Project，第三代合作伙伴项目)RAT(Radio Access Technology，无线接入技术)相关联的多个USIM并发进行注册。当具有多个USIM的终端设备与其中一个USIM关联的系统进行通信时(上述系统称为当前连接系统)，该具有多个USIM的终端设备可能需要在与所述其中一个USIM不同的USIM相关联的另一个系统中执行某些活动(例如，侦听寻呼、响应寻呼、执行移动性更新等)，上述另一个系统称为非当前连接系统。
当具有多个USIM的终端设备从非当前连接系统接收到用于通知待接收的MT(Mobile Terminated，终端待接收)服务的寻呼时，若当前连接系统中存在正在运行的服务，则具有多个USIM的终端设备可以向网络侧发送繁忙指示，其中，具有多个USIM的终端设备在特定的非接入层(Non-Access Stratum，NAS)消息中携带繁忙指示。
然而，针对处于无线资源控制(Radio Resource Control，RRC)非活动(RRC-Inactive)状态的终端设备，忙碌指示可能不会承载在NAS消息中，因此，在终端设备处于RRC非活动的通信场景中，如何将终端设备处于繁忙的状态及时通知接入网设备，对于节省寻呼资源是十分重要的。
发明内容
本申请实施例提供一种寻呼处理方法及其装置，可以应用于蜂窝移动通信技术中终端设备与接入网设备之间通信的场景，使得处于RRC非活动状态的终端设备可通过RRC恢复请求消息向接入网设备发送繁忙指示，使得接入网设备通过RRC恢复请求消息获知终端设备处于繁忙状态，减少寻呼资源浪费。
第一方面，本申请实施例提供一种寻呼处理方法，所述方法由终端设备执行，所述方法包括：接收接入网设备转发的针对非当前连接系统的寻呼请求；响应于所述终端设备的当前连接系统为繁忙状态，向所述接入网设备发送无线资源控制RRC恢复请求消息，其中，所述RRC恢复请求消息包括繁忙指示；其中，所述终端设备具有第一通信卡和第二通信卡，所述终端设备使用所述第一通信卡与所述当前连接系统通信，所述终端设备使用所述第二通信卡与所述非当前连接系统通信。
在该技术方案中，接收针对非当前连接系统的寻呼请求，在确定终端设备的当前连接系统处于繁忙状态的情况下，向接入网设备发送携带有繁忙指示的RRC恢复请求消息。由此，使得处于RRC非活动状态的终端设备可通过RRC恢复请求消息向接入网设备发送繁忙指示，使得接入网设备通过RRC恢复请求消息快速获知终端设备处于繁忙状态，减少寻呼资源浪费。
在一种可能的实现方式中，所述RRC恢复请求消息还包括消息验证码MAC，所述生成 MAC所需的输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，所述指定消息内容包括所述繁忙指示。
在一种可能的实现方式中，所述方法还包括：根据所述完整性密钥、所述计数值、所述承载标识和所述传输方向信息对所述指定消息内容进行消息验证码计算，生成所述MAC。
可选的，所述RRC恢复请求消息包括消息验证码MAC，所述生成MAC所需的输入参数包括恢复原因信息元、指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息。
在一种可能的实现方式中，所述方法还包括：根据所述完整性密钥、所述恢复原因信息元、所述计数值、所述承载标识和所述传输方向信息对所述指定消息内容进行消息验证码计算，生成所述MAC。
在一种可选的实现方式中，所述RRC恢复请求消息的恢复原因信息元包括所述繁忙指示。
第二方面，本申请实施例提供另一种寻呼处理方法，所述方法由接入网设备执行，所述方法包括：向终端设备转发针对非当前连接系统的寻呼请求；响应于接收到所述终端设备发送的无线资源控制RRC恢复请求消息，确定所述终端设备的当前连接系统处于繁忙状态，其中，所述RRC恢复请求消息包括繁忙指示。
在该技术方案中，向终端设备转发针对非当前连接系统的寻呼请求，并在接收到所述终端设备发送的携带有繁忙指示的RRC恢复请求消息的情况下，确定所述终端设备的当前连接系统处于繁忙状态。由此，使得接入网设备通过RRC恢复请求消息中的繁忙指示即可快速获知处于RRC非活动状态的终端设备处于繁忙状态，减少寻呼资源浪费。
在一种可能的实现方式中，所述确定所述终端设备的当前连接系统处于繁忙状态，包括：从所述RRC恢复请求消息中提取第一消息验证码MAC；获取生成MAC所需的输入参数；根据所述生成MAC所需的输入参数生成第二MAC；在所述第一MAC和所述第二MAC一致的情况下，确定所述终端设备的当前连接系统处于繁忙状态。
在一种可能的实现方式中，所述生成MAC所需的输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，所述指定消息内容包括所述繁忙指示。
在一种可能的实现方式中，所述生成MAC所需的输入参数包括恢复原因信息元、指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息。
在一种可选的实现方式中，所述RRC恢复请求消息的恢复原因信息元包括所述繁忙指示。
第三方面，本申请实施例提供一种寻呼处理装置，该寻呼处理装置具有实现上述第一方面所述的方法中终端设备的部分或全部功能，比如寻呼处理装置的功能可具备本申请中的部分或全部实施例中的功能，也可以具备单独实施本申请中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
第四方面，本申请实施例提供另一种寻呼处理装置，该寻呼处理装置具有实现上述第二方面所述的方法示例中接入网设备的部分或全部功能，比如寻呼处理装置的功能可具备本申请中的部分或全部实施例中的功能，也可以具备单独实施本申请中的任一个实施例的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元或模块。
第五方面，本申请实施例提供一种寻呼处理装置，该装置包括处理器，当该处理器调 用存储器中的计算机程序时，执行上述第一方面所述的方法。
第六方面，本申请实施例提供一种寻呼处理装置，该装置包括处理器，当该处理器调用存储器中的计算机程序时，执行上述第二方面所述的方法。
第七方面，本申请实施例提供一种寻呼处理装置，该装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该装置执行上述第一方面所述的方法。
第八方面，本申请实施例提供一种寻呼处理装置，该装置包括处理器和存储器，该存储器中存储有计算机程序；所述处理器执行该存储器所存储的计算机程序，以使该装置执行上述第二方面所述的方法。
第九方面，本申请实施例提供一种寻呼处理装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第一方面所述的方法。
第十方面，本申请实施例提供一种寻呼处理装置，该装置包括处理器和接口电路，该接口电路用于接收代码指令并传输至该处理器，该处理器用于运行所述代码指令以使该装置执行上述第二方面所述的方法。
第十一方面，本申请实施例提供一种通信系统，该系统包括第三方面所述的寻呼处理装置以及第四方面所述的寻呼处理装置，或者，该系统包括第五方面所述的寻呼处理装置以及第六方面所述的寻呼处理装置，或者，该系统包括第七方面所述的寻呼处理装置以及第八方面所述的寻呼处理装置，或者，该系统包括第九方面所述的寻呼处理装置以及第十方面所述的寻呼处理装置。
第十二方面，本发明实施例提供一种计算机可读存储介质，用于储存为上述接入网设备所用的指令，当所述指令被执行时，使所述终端设备执行上述第一方面所述的方法。
第十三方面，本发明实施例提供一种可读存储介质，用于储存为上述终端设备所用的指令，当所述指令被执行时，使所述接入网设备执行上述第二方面所述的方法。
第十四方面，本申请还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十五方面，本申请还提供一种包括计算机程序的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
第十六方面，本申请提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持接入网设备实现第一方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存接入网设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十七方面，本申请提供一种芯片系统，该芯片系统包括至少一个处理器和接口，用于支持终端设备实现第二方面所涉及的功能，例如，确定或处理上述方法中所涉及的数据和信息中的至少一种。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存终端设备必要的计算机程序和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十八方面，本申请提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第一方面所述的方法。
第十九方面，本申请提供一种计算机程序，当其在计算机上运行时，使得计算机执行上述第二方面所述的方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请实施例提供的一种通信系统的架构示意图；
图2是本申请实施例提供的一种寻呼处理方法的流程示意图；
图3是本申请实施例提供的另一种寻呼处理方法的流程示意图；
图4是本申请实施例提供的另一种寻呼处理方法的流程示意图；
图5是本申请实施例提供的另一种寻呼处理方法的流程示意图；
图6是本申请实施例提供的一种寻呼处理方法的流程示意图；
图7是本申请实施例提供的另一种寻呼处理方法的流程示意图；
图8是本申请实施例提供的一种寻呼处理装置的结构示意图；
图9是本申请实施例提供的另一种寻呼处理装置的结构示意图；
图10是本申请实施例提供的一种芯片的结构示意图。
具体实施方式
为了更好的理解本申请实施例公开的一种寻呼处理方法，下面首先对本申请实施例适用的通信系统进行描述。
请参见图1，图1为本申请实施例提供的一种通信系统的架构示意图。该通信系统可包括但不限于一个接入网设备和一个终端设备，图1所示的设备数量和形态仅用于举例并不构成对本申请实施例的限定，实际应用中可以包括两个或两个以上的接入网设备，两个或两个以上的终端设备。图1所示的通信系统以包括一个接入网设备101、一个终端设备102为例。
需要说明的是，本申请实施例的技术方案可以应用于各种通信系统。例如：长期演进(long term evolution，LTE)系统、第五代(5th generation，5G)移动通信系统、5G新空口(new radio，NR)系统，或者其他未来的新型移动通信系统等。
本申请实施例中的接入网设备101是网络侧的一种用于发射或接收信号的实体。例如，接入网设备101可以为演进型基站(evolved NodeB，eNB)、传输点(transmission reception point，TRP)、NR系统中的下一代基站(next generation NodeB，gNB)、其他未来移动通信系统中的基站或无线保真(wireless fidelity，WiFi)系统中的接入节点等。本申请的实施例对接入网设备所采用的具体技术和具体设备形态不做限定。本申请实施例提供的接入网设备可以是由集中单元(central unit，CU)与分布式单元(distributed unit，DU)组成的，其中，CU也可以称为控制单元(control unit)，采用CU-DU的结构可以将 接入网设备，例如基站的协议层拆分开，部分协议层的功能放在CU集中控制，剩下部分或全部协议层的功能分布在DU中，由CU集中控制DU。
本申请实施例中的终端设备102是用户侧的一种用于接收或发射信号的实体，如手机。终端设备也可以称为终端设备(terminal)、用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端设备(mobile terminal，MT)等。终端设备可以是具备通信功能的汽车、智能汽车、手机(mobile phone)、穿戴式设备、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端设备、无人驾驶(self-driving)中的无线终端设备、远程手术(remote medical surgery)中的无线终端设备、智能电网(smart grid)中的无线终端设备、运输安全(transportation safety)中的无线终端设备、智慧城市(smart city)中的无线终端设备、智慧家庭(smart home)中的无线终端设备等等。本申请的实施例对终端设备所采用的具体技术和具体设备形态不做限定。
上述通信系统中，当具有多个USIM的终端设备从非当前连接系统接收到用于通知待接收的MT(Mobile Terminated，终端待接收)服务的寻呼时，如果该具有多个USIM的终端设备确定MT服务的重要性低于正在运行的服务，宁愿在当前连接系统中继续保持正在运行的服务，则可能存在以下两种情况：
第一种，具有多个USIM的终端设备仅按照现有流程来响应来自非当前连接系统的寻呼，但是上述响应寻呼的方式，将中断当前连接系统中正在运行的服务。
第二种，具有多个USIM的终端设备不响应来自非当前连接系统的寻呼，这种方式下，将使非当前连接系统通过将寻呼范围扩大到更大的区域来保持对该具有多个USIM的终端设备的寻呼，由此，将导致非当前连接系统的资源被浪费。
目前，当具有多个USIM的终端设备从非当前连接系统接收到用于通知待接收的MT(Mobile Terminated，终端待接收)服务的寻呼时，若当前连接系统中存在正在运行的服务，则具有多个USIM的终端设备可以向网络侧发送繁忙指示，其中，具有多个USIM的终端设备在特定的非接入层(Non-Access Stratum，NAS)消息中携带繁忙指示。然而，针对处于无线资源控制(Radio Resource Control，RRC)非活动(RRC-Inactive)状态的终端设备，忙碌指示可能不会承载在NAS消息中，因此，上述在特定的NAS消息中携带繁忙指示的方式，不适用于处于RRC非活动状态的终端设备。
本申请实施例中，接收针对非当前连接系统的寻呼请求，在确定终端设备的当前连接系统处于繁忙状态的情况下，向接入网设备发送携带有繁忙指示的RRC恢复请求消息。由此，使得处于RRC非活动状态的终端设备可通过RRC恢复请求消息向接入网设备发送繁忙指示，使得接入网设备通过RRC恢复请求消息快速获知终端设备处于繁忙状态，减少寻呼资源浪费。
可以理解的是，在接入网设备接收到繁忙指示的情况下，接入网设备可以停止对终端设备进行寻呼，以降低资源的占用，节省了寻呼资源。
可以理解的是，本申请实施例描述的通信系统是为了更加清楚的说明本申请实施例的 技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着系统架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
下面结合附图对本申请所提供的寻呼处理方法及其装置进行详细地介绍。
请参见图2，图2是本申请实施例提供的一种寻呼处理方法的流程示意图。该方法应用于图1所示通信系统中的终端设备。该方法由图1所示的通信系统中的终端设备执行，如图2所示，该方法可以包括但不限于如下步骤：
步骤S201：接收接入网设备转发的针对非当前连接系统的寻呼请求。
在本公开实施例中，上述寻呼请求是核心网设备发送给接入网设备的。
步骤S202：响应于终端设备的当前连接系统为繁忙状态，向接入网设备发送无线资源控制RRC恢复请求消息，其中，RRC恢复请求消息包括繁忙指示。
其中，终端设备具有第一通信卡和第二通信卡，终端设备使用第一通信卡与当前连接系统通信，终端设备使用第二通信卡与非当前连接系统通信。
在一些实施例中，为了减少对当前协议的影响，以及减少终端设备实现的影响，RRC恢复请求消息的恢复原因信息元(Information Element，IE)可以包括繁忙指示。也就是说，可将繁忙指示作为恢复原因信息元的原因值。对应地，接入网设备在接收到终端设备发送的RRC恢复请求消息，并获取该RRC恢复请求消息的恢复原因信息元，在确定恢复原因信息元为繁忙指示的情况下，可确定该终端设备处于繁忙状态，继而接入网设备可停止向终端设备发送针对非当前连接系统的寻呼请求，节省了寻呼资源，并且可以不中断终端设备的当前连接系统正在进行的服务。
其中，恢复原因信息元的原因值还可以包括当前协议中所包括的其他原因值，例如，用于指示更高优先级访问的原因值，或用于指示紧急情况的原因值。
本公开实施例中，当前连接系统是指终端设备当前接入的网络所对应的系统，且该系统与终端设备处于连接模式；非当前连接系统是指终端设备当前接入的网络所对应的系统，且该系统与终端设备处于空闲模式，其中，为了便于区分终端设备中的不同的通信卡，本公开中可以将终端设备中与当前连接系统通信的通信卡称为第一通信卡，将终端设备中与非当前连接系统通信的通信卡称为第二通信卡。
以终端设备具有两个通信卡，两个通信卡分别为移动通信卡和电信通信卡进行示例性说明。假设终端设备通过移动通信卡与其他终端设备进行通信，则当前连接系统可以为移动网络所对应的系统，非当前连接系统可以为电信网络所对应的系统。
再以终端设备具有两个通信卡，两个通信卡均为移动通信卡进行示例性说明。当前连接系统可以为移动网络所对应的系统1，非当前连接系统可以为移动网络所对应的系统2，即系统1和系统2均为移动网络所对应的系统。
本公开实施例中，终端设备可以使用第二通信卡接收接入网设备转发的针对该非当前连接系统的寻呼请求，其中，寻呼请求，用于寻呼该终端设备。
可选地，非当前连接系统的核心网设备可以通过接入网设备向终端设备发送寻呼请求，相应的，终端设备可以使用第二通信卡接收接入网设备转发的针对非当前连接系统的寻呼 请求。
可以理解的是，在接入网设备基于RRC恢复请求消息确定终端设备处于繁忙状态的情况下，接入网设备可以停止对终端设备进行寻呼，以降低资源的占用。
本公开实施例中，接收针对非当前连接系统的寻呼请求，在确定终端设备的当前连接系统处于繁忙状态的情况下，向接入网设备发送携带有繁忙指示的RRC恢复请求消息。由此，使得处于RRC非活动状态的终端设备可通过RRC恢复请求消息向接入网设备发送繁忙指示，使得接入网设备通过RRC恢复请求消息快速获知终端设备处于繁忙状态，减少寻呼资源浪费。
请参见图3，图3是本申请实施例提供的另一种寻呼处理方法的流程示意图。该方法应用于图1所示通信系统中的终端设备。该寻呼处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。如图3所示，该方法可以包括但不限于如下步骤：
步骤S301：接收接入网设备转发的针对非当前连接系统的寻呼请求。
在本公开实施例中，寻呼请求是核心网设备发送给接入网设备的。
步骤S302：响应于终端设备的当前连接系统为繁忙状态，向接入网设备发送无线资源控制RRC恢复请求消息，其中，RRC恢复请求消息包括繁忙指示和消息验证码MAC。
其中，终端设备具有第一通信卡和第二通信卡，其中，终端设备使用第一通信卡与当前连接系统通信，终端设备使用第二通信卡与非当前连接系统通信。
在本公开的一种可能实现方式，为了避免RRC恢复请求消息被篡改，保证RRC恢复请求消息中关键信息的完整性，上述RRC恢复请求消息还可以包括消息验证码(Message Authentication Code，MAC)。由此，从而使得接入网设备可基于消息验证码对RRC恢复请求消息中的关键信息进行完整性验证，并在确定RRC恢复请求消息中的关键信息完整性验证成功的情况下，确定终端设备的当前连接系统处于繁忙状态，继而接入网设备可停止向终端设备发送针对非当前连接系统的寻呼请求，节省了寻呼资源，并且可以不中断终端设备的当前连接系统正在进行的服务。
在本公开的一种可能的实现方式，为了进行完整性保护，上述生成MAC所需的输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，指定消息内容包括繁忙指示。
例如，MAC所需的输入参数包括一个名为KEY(K RRcint)的AS完整性密钥，一个32位的COUNT(计数值)，一个用于承载身份的5位的承载标识(BEARER)，一个1位的传输方向信息(DIRECTION)，其中，对于上行链路，DIRECTION为0，对于下行链路，DIRECTION为1，以及指定消息内容(MESSAGE)。其中，指定消息内容为接入网设备的小区信息VarResumeMAC-Input或者VarShortMAC-Input。
其中，上述VarResumeMAC-Input和VarShortMAC-Input这两者均包括以下信息：源小区的标识信息、目标小区的标识信息、终端设备在源小区的无线网络临时标识符(Cell-RadioNetworkTemporaryIdentifier，C-RNTI)和繁忙指示。
在一些实施例中，为了减少对当前协议的影响，以及减少对终端设备或者接入网设备 实现的影响，RRC恢复请求消息的恢复原因信息元(Information Element，IE)可以包括繁忙指示。也就是说，可将繁忙指示作为恢复原因信息元的原因值。对应地，接入网设备在接收到终端设备发送的RRC恢复请求消息，并获取该RRC恢复请求消息的恢复原因信息元，在确定恢复原因信息元为繁忙指示的情况下，可确定该终端设备处于繁忙状态，继而接入网设备可停止向终端设备发送针对非当前连接系统的寻呼请求，节省了寻呼资源，并且可以不中断终端设备的当前连接系统正在进行的服务。
其中，恢复原因信息元的原因值还可以为当前协议中所包括的其他原因值，例如，用于指示更高优先级访问的原因值，或用于指示紧急情况的原因值。
本申请实施例中，接收针对非当前连接系统的寻呼请求，在确定终端设备的当前连接系统处于繁忙状态的情况下，向接入网设备发送携带有繁忙指示以及MAC的RRC恢复请求消息。由此，使得处于RRC非活动状态的终端设备可通过RRC恢复请求消息向接入网设备发送繁忙指示以及MAC，从而使得接入网设备可基于MAC对接收到的消息的关键信息进行完整性验证，并在完整性验证成功的情况下，确定终端设备处于繁忙状态，减少寻呼资源浪费。
请参见图4，图4是本申请实施例提供的另一种寻呼处理方法的流程示意图。该方法应用于图1所示通信系统中的终端设备。该寻呼处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。如图4所示，该方法可以包括但不限于如下步骤：
步骤S401：接收接入网设备转发的针对非当前连接系统的寻呼请求。
步骤S402：响应于终端设备的当前连接系统为繁忙状态，获取生成MAC所需的输入参数，其中，输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，指定消息内容包括繁忙指示。
在一些实施例中，上述完整性密钥可以是从终端设备中存储的接入层AS上下文中得到的。其中，需要说明的是，终端设备和接入网设备之间共享上述AS上下文。
步骤S403：根据完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成MAC。
在一些实施例中，可获取终端设备与接入网设备所约定的完整性算法，并基于完整性算法，根据完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成MAC。
作为一种示例性的实施方式，为了使得终端设备和接入网设备生成MAC的方式相同，可在两者通信所基于的通信协议中规定，在生成MAC的情况下，将承载标识其对应的所有位均设置为1；将计数值其对应的所有位均设置为1；将传输方向信息其位均设置为1。
在一些实施例中，上述完整性算法也可以是从终端设备中存储的接入层AS上下文中得到的。也就是说，在一些实施例中，上述接入层AS上下文可以包括完整性算法以及完整性密钥。
步骤S404：向接入网设备发送RRC恢复请求消息，其中，RRC恢复请求消息包括繁忙指示和MAC。
在一些实施例中，为了减少对当前协议的影响，以及减少终端设备实现的影响，RRC恢复请求消息的恢复原因信息元(Information Element，IE)可以包括繁忙指示。也就是说，可将繁忙指示作为恢复原因信息元的原因值。也就是说，可将繁忙指示作为恢复原因信息元的原因值。对应地，接入网设备在接收到终端设备发送的RRC恢复请求消息，并获取该RRC恢复请求消息的恢复原因信息元，在确定恢复原因信息元为繁忙指示的情况下，可确定该终端设备处于繁忙状态，继而接入网设备可停止向终端设备发送针对非当前连接系统的寻呼请求，节省了寻呼资源，并且可以不中断终端设备的当前连接系统正在进行的服务。
其中，恢复原因信息元的原因值还可以为当前协议中所包括的其他原因值，例如，用于指示更高优先级访问的原因值，或用于指示紧急情况的原因值。
在本实施例中，接收针对非当前连接系统的寻呼请求，在确定终端设备的当前连接系统处于繁忙状态的情况下，获取生成MAC所需的输入参数，并基于完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成MAC，以及向接入网设备发送携带有繁忙指示以及MAC的RRC恢复请求消息。由此，使得处于RRC非活动状态的终端设备可通过RRC恢复请求消息向接入网设备发送繁忙指示以及MAC，从而使得接入网设备可基于MAC对接收到的消息的关键信息进行完整性验证，并在完整性验证成功的情况下，确定终端设备处于繁忙状态，减少寻呼资源浪费。
请参见图5，图5是本申请实施例提供的另一种寻呼处理方法的流程示意图。该方法应用于图1所示通信系统中的终端设备。该寻呼处理方法可以单独被执行，也可以结合本公开中的任一个实施例或是实施例中的可能的实现方式一起被执行，还可以结合相关技术中的任一种技术方案一起被执行。如图5所示，该方法可以包括但不限于如下步骤：
步骤S501：接收接入网设备转发的针对非当前连接系统的寻呼请求。
在本公开实施例中，寻呼请求是核心网设备发送给接入网设备的。
步骤S502：响应于终端设备的当前连接系统为繁忙状态，获取生成MAC所需的输入参数，其中，输入参数包括恢复原因信息元、指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息。
步骤S503：根据完整性密钥、恢复原因信息元、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成MAC。
在本实施例中，为了避免指定消息内容被篡改，减少对当前协议的影响，可将恢复原因信息元作为计算MAC的附加输入参数之一。
例如，MAC所需的输入参数包括恢复原因信息元、一个名为KEY(K RRcint)的AS完整性密钥，一个32位的COUNT(计数值)，一个用于承载身份的5位的承载标识(BEARER)，一个1位的传输方向信息(DIRECTION)，其中，对于上行链路，DIRECTION为0，对于下行链路，DIRECTION为1，以及指定消息内容(MESSAGE)。其中，指定消息内容为接入网设备的小区信息VarResumeMAC-Input或者VarShortMAC-Input。
其中，上述VarResumeMAC-Input和VarShortMAC-Input这两者均包括以下信息：源小区的标识信息、目标小区的标识信息、终端设备在源小区的无线网络临时标识符 (Cell-RadioNetworkTemporaryIdentifier，C-RNTI)。
在一些实施例中，上述完整性密钥可以是从终端设备中存储的接入层AS上下文中得到的。其中，需要说明的是，终端设备和接入网设备之间共享上述AS上下文。
在一些实施例中，可获取终端设备与接入网设备所约定的完整性算法，并基于完整性算法，根据完整性密钥、恢复原因信息元、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成MAC。
作为一种示例性的实施方式，为了使得终端设备和接入网设备生成MAC的方式相同，可在两者通信所基于的通信协议中规定，在生成MAC的情况下，将承载标识其对应的所有位均设置为1；将计数值其对应的所有位均设置为1；将传输方向信息其位均设置为1。
在一些实施例中，上述完整性算法也可以是从终端设备中存储的接入层AS上下文中得到的。也就是说，在一些实施例中，上述接入层AS上下文可以包括完整性算法以及完整性密钥。
步骤S504：向接入网设备发送RRC恢复请求消息包括繁忙指示和消息验证码MAC。
其中，终端设备具有第一通信卡和第二通信卡，其中，终端设备使用第一通信卡与当前连接系统通信，终端设备使用第二通信卡与非当前连接系统通信。
在一些实施例中，为了减少对当前协议的影响，以及减少对终端设备或者接入网设备实现的影响，RRC恢复请求消息的恢复原因信息元(Information Element，IE)可以包括繁忙指示。也就是说，可将繁忙指示作为恢复原因信息元的原因值。也就是说，可将繁忙指示作为恢复原因信息元的原因值。也就是说，可将繁忙指示作为恢复原因信息元的原因值。对应地，接入网设备在接收到终端设备发送的RRC恢复请求消息，并获取该RRC恢复请求消息的恢复原因信息元，在确定恢复原因信息元为繁忙指示的情况下，可确定该终端设备处于繁忙状态，继而接入网设备可停止向终端设备发送针对非当前连接系统的寻呼请求，节省了寻呼资源，并且可以不中断终端设备的当前连接系统正在进行的服务。
其中，恢复原因信息元的原因值还可以为当前协议中所包括的其他原因值，例如，用于指示更高优先级访问的原因值，或用于指示紧急情况的原因值。
在本实施例中，接收针对非当前连接系统的寻呼请求，在确定终端设备的当前连接系统处于繁忙状态的情况下，获取生成MAC所需的输入参数，并根据完整性密钥、恢复原因信息元、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成MAC，以及向接入网设备发送携带有繁忙指示以及MAC的RRC恢复请求消息。由此，使得处于RRC非活动状态的终端设备可通过RRC恢复请求消息向接入网设备发送繁忙指示以及MAC，从而使得接入网设备可基于MAC对接收到的消息的关键信息进行完整性验证，并在完整性验证成功的情况下，确定终端设备处于繁忙状态，减少寻呼资源浪费。
请参见图6，图6是本申请实施例提供的一种寻呼处理方法的流程示意图。该方法应用于图1所示通信系统中的接入网设备。该方法可以由图1所示通信系统中的接入网设备执行。如图6所示，该方法可以包括但不限于如下步骤：
步骤S601：向终端设备转发针对非当前连接系统的寻呼请求。
在本公开实施例中，上述寻呼请求是核心网设备发送给接入网设备的。
其中，终端设备具有第一通信卡和第二通信卡，其中，终端设备使用第一通信卡与当前连接系统通信，终端设备使用第二通信卡与非当前连接系统通信。
步骤S602：响应于接收到终端设备发送的无线资源控制RRC恢复请求消息，确定终端设备的当前连接系统处于繁忙状态，其中，RRC恢复请求消息包括繁忙指示。
在一些实施例中，为了减少对当前协议的影响，RRC恢复请求消息的恢复原因信息元(Information Element，IE)可以包括繁忙指示。也就是说，可将繁忙指示作为恢复原因信息元的原因值。对应地，接入网设备在接收到终端设备发送的RRC恢复请求消息，并获取该RRC恢复请求消息的恢复原因信息元，在确定恢复原因信息元为繁忙指示的情况下，可确定该终端设备处于繁忙状态，继而接入网设备可停止向终端设备发送针对非当前连接系统的寻呼请求，节省了寻呼资源，并且可以不中断终端设备的当前连接系统正在进行的服务。
其中，恢复原因信息元的原因值还可以为当前协议中所包括的其他原因值，例如，用于指示更高优先级访问的原因值，或用于指示紧急情况的原因值，例如，用于指示更高优先级访问的原因值，或用于指示紧急情况的原因值。
在本实施例中，向终端设备转发针对非当前连接系统的寻呼请求，并在接收到终端设备发送的携带有繁忙指示的RRC恢复请求消息的情况下，确定终端设备的当前连接系统处于繁忙状态。由此，使得接入网设备通过RRC恢复请求消息中的繁忙指示即可快速获知处于RRC非活动状态下的终端设备处于繁忙状态，减少寻呼资源浪费。
请参见图7，图7是本申请实施例提供的另一种寻呼处理方法的流程示意图。该方法应用于图1所示通信系统中的接入网设备。也就是说，该方法可以由图1所示通信系统中的接入网设备执行。为了使得接入网设备可以准确确定出终端设备的状态，如图7所示，上述确定终端设备的当前连接系统处于繁忙状态的一种可能实现方式为：
步骤S701：从RRC恢复请求消息中提取第一消息验证码MAC。
步骤S702：获取生成MAC所需的输入参数。
步骤S703：根据生成MAC所需的输入参数生成第二MAC。
步骤S704：在第一MAC和第二MAC一致的情况下，确定终端设备的当前连接系统处于繁忙状态。
在一种可能的实现方式中，上述生成MAC所需的输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，指定消息内容包括繁忙指示。根据生成MAC所需的输入参数生成第二MAC的具体实现方式可以为：根据完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成第二MAC。
例如，MAC所需的输入参数包括一个名为KEY(K RRcint)的AS完整性密钥，一个32位的COUNT(计数值)，一个用于承载身份的5位的承载标识(BEARER)，一个1位的传输方向信息(DIRECTION)，其中，对于上行链路，DIRECTION为0，对于下行链路，DIRECTION为1，以及指定消息内容(MESSAGE)。其中，指定消息内容为接入网设备的小区信息VarResumeMAC-Input或者VarShortMAC-Input。
其中，上述VarResumeMAC-Input和VarShortMAC-Input这两者均包括以下信息：源小 区的标识信息、目标小区的标识信息、终端设备在源小区的无线网络临时标识符(Cell-RadioNetworkTemporaryIdentifier，C-RNTI)以及繁忙指示。
在一些实施例中，上述完整性密钥可以是从接入网设备中存储的接入层AS上下文中得到的。其中，需要说明的是，终端设备和接入网设备之间共享上述AS上下文。
在一些实施例中，可获取终端设备与接入网设备所约定的完整性算法，并基于完整性算法，根据完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成第一MAC。
在一些实施例中，上述完整性算法也可以是从接入网设备中存储的接入层AS上下文中得到的。也就是说，在一些实施例中，上述接入层AS上下文可以包括完整性算法以及完整性密钥。
作为一种示例性的实施方式，为了使得终端设备和接入网设备生成MAC的方式相同，可在两者通信所基于的通信协议中规定，在生成MAC的情况下，将承载标识其对应的所有位均设置为1；将计数值其对应的所有位均设置为1；将传输方向信息其位均设置为1。
在另一种可能的实现方式中，上述生成MAC所需的输入参数包括恢复原因信息元、指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息。对应地，根据生成MAC所需的输入参数生成第二MAC的具体实现方式可以为：根据恢复原因信息元、完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成第二MAC。
在一些实施例中，上述完整性密钥可以是从接入网设备中存储的接入层AS上下文中得到的。其中，需要说明的是，终端设备和接入网设备之间共享上述AS上下文。
在一些实施例中，可获取终端设备与接入网设备所约定的完整性算法，并基于完整性算法，根据恢复原因信息元、完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成第二MAC。
在一些实施例中，上述完整性算法也可以是从接入网设备中存储的接入层AS上下文中得到的。也就是说，在一些实施例中，上述接入层AS上下文可以包括完整性算法以及完整性密钥。
作为一种示例性的实施方式，为了使得终端设备和接入网设备生成MAC的方式相同，可在两者通信所基于的通信协议中规定，在生成MAC的情况下，将承载标识其对应的所有位均设置为1；将计数值其对应的所有位均设置为1；将传输方向信息其位均设置为1。
在一些实施例中，为了减少对当前协议的影响，以及减少对接入网设备的影响，RRC恢复请求消息的恢复原因信息元包括繁忙指示。对应地，根据生成MAC所需的输入参数生成第二MAC的实现方式可以为：根据恢复原因信息元、完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成第二MAC。
作为一种示例性的实施方式中，在接入网设备接收到终端设备发送的无线资源控制RRC恢复请求消息后，可从RRC恢复请求消息中提取第一MAC和恢复原因信息元。对应地，在确定恢复原因信息元为繁忙指示的情况下，可根据繁忙指示和生成MAC所需的输入参数，生成第二MAC，其中，输入参数可以可以包括完整性密钥、计数值、承载标识、指定消息内容和传输方向信息。具体而言，可根据恢复原因信息元、完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成第二MAC。在获取第二MAC 后，可将第一MAC和第二MAC进行比较，如果两者一致，则确定所接收到的RRC恢复请求消息的关键信息通过完整性验证，即，上述RRC恢复请求消息是完整的，并没有被篡改。此时，接入网设备可确定终端设备的当前连接系统处于繁忙状态。
其中，可以理解的是，在RRC恢复请求消息被破坏的情况下，例如，RC恢复请求消息被攻击者删除或者篡改的情况下，对应地，接入网设备将无法识别出RRC恢复请求消息中恢复原因IE为繁忙指示。因此，基于生成MAC所需的输入参数和恢复原因IE所生成的第二MAC和第一MAC不匹配，此时，即完整性验证失败。
上述本申请提供的实施例中，分别从接入网设备、终端设备的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，接入网设备和终端设备可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来执行。
请参见图8，图8是本申请实施例提供的一种寻呼处理装置80的结构示意图。图8所示的寻呼处理装置80可包括收发单元801和处理单元802。收发单元801可包括发送单元和/或接收单元，发送单元用于实现发送功能，接收单元用于实现接收功能，收发单元801可以实现发送功能和/或接收功能。
寻呼处理装置80可以是接入网设备，也可以是接入网设备中的装置，还可以是能够与接入网设备匹配使用的装置。或者，寻呼处理装置80可以是终端设备，也可以是终端设备中的装置，还可以是能够与终端设备匹配使用的装置。
寻呼处理装置80为终端设备：收发单元801，用于接收接入网设备转发的针对非当前连接系统的寻呼请求；响应于终端设备的当前连接系统为繁忙状态，向接入网设备发送无线资源控制RRC恢复请求消息，其中，RRC恢复请求消息包括繁忙指示；其中，终端设备具有第一通信卡和第二通信卡，其中，终端设备使用第一通信卡与当前连接系统通信，终端设备使用第二通信卡与非当前连接系统通信。
在一种可能的实现方式中，RRC恢复请求消息还包括消息验证码MAC，生成MAC所需的输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，指定消息内容包括繁忙指示。
在一种可选的实现方式中，处理单元802，用于根据完整性密钥、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成MAC。
在一种可能的实现方式中，RRC恢复请求消息包括消息验证码MAC，生成MAC所需的输入参数包括恢复原因信息元、指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息。
在一种可能的实现方式中，处理单元802，用于根据完整性密钥、恢复原因信息元、计数值、承载标识和传输方向信息对指定消息内容进行消息验证码计算，生成MAC。
在一种可能的实现方式中，RRC恢复请求消息的恢复原因信息元包括繁忙指示。
寻呼处理装置80为接入网设备：收发单元801，用于向终端设备转发针对非当前连接 系统的寻呼请求。
处理单元802，用于响应于接收到终端设备发送的无线资源控制RRC恢复请求消息，确定终端设备的当前连接系统处于繁忙状态，其中，RRC恢复请求消息包括繁忙指示。
在一种可能的实现方式中，处理单元802，具体用于：从RRC恢复请求消息中提取第一消息验证码MAC；获取生成MAC所需的输入参数；
根据生成MAC所需的输入参数生成第二MAC；在第一MAC和第二MAC一致的情况下，确定终端设备的当前连接系统处于繁忙状态。
在另一种可选的实现方式中，生成MAC所需的输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，指定消息内容包括繁忙指示。
在一种可能的实现方式中，生成MAC所需的输入参数包括恢复原因信息元、指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息。
在一种可能的实现方式中，RRC恢复请求消息的恢复原因信息元包括繁忙指示。
请参见图9，图9是本申请实施例提供的另一种寻呼处理装置90的结构示意图。寻呼处理装置90可以是接入网设备，也可以是终端设备，也可以是支持接入网设备实现上述方法的芯片、芯片系统、或处理器等，还可以是支持终端设备实现上述方法的芯片、芯片系统、或处理器等。该装置可用于实现上述方法实施例中描述的方法，具体可以参见上述方法实施例中的说明。
寻呼处理装置90可以包括一个或多个处理器901。处理器901可以是通用处理器或者专用处理器等。例如可以是基带处理器或中央处理器。基带处理器可以用于对通信协议以及通信数据进行处理，中央处理器可以用于对寻呼处理装置(如，基站、基带芯片，终端设备、终端设备芯片，DU或CU等)进行控制，执行计算机程序，处理计算机程序的数据。
可选的，寻呼处理装置90中还可以包括一个或多个存储器902，其上可以存有计算机程序903，处理器901执行计算机程序903，以使得寻呼处理装置90执行上述方法实施例中描述的方法。计算机程序903可能固化在处理器901中，该种情况下，处理器901可能由硬件实现。
可选的，存储器902中还可以存储有数据。寻呼处理装置90和存储器902可以单独设置，也可以集成在一起。
可选的，寻呼处理装置90还可以包括收发器905、天线906。收发器905可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器905可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
可选的，寻呼处理装置90中还可以包括一个或多个接口电路907。接口电路907用于接收代码指令并传输至处理器901。处理器901运行代码指令以使寻呼处理装置90执行上述方法实施例中描述的方法。
寻呼处理装置90为终端设备：收发器905用于执行图2中的步骤S201、步骤S202；图3中的步骤步骤S301、步骤S302；图4中的步骤S401、步骤S404；图5中的步骤S501、步骤S504。处理器901用于执行图4中的步骤S402和步骤S403；图5中的步骤S502和步骤S503。
在一些实施例中，上述寻呼处理装置90为接入网设备，上述收发器905用于执行图6中的步骤S601。处理器901用于执行图6中的步骤S602,；图7中的步骤S701至步骤S704。
在一种实现方式中，处理器901中可以包括用于实现接收和发送功能的收发器。例如该收发器可以是收发电路，或者是接口，或者是接口电路。用于实现接收和发送功能的收发电路、接口或接口电路可以是分开的，也可以集成在一起。上述收发电路、接口或接口电路可以用于代码/数据的读写，或者，上述收发电路、接口或接口电路可以用于信号的传输或传递。
在一种实现方式中，寻呼处理装置90可以包括电路，电路可以实现前述方法实施例中发送或接收或者通信的功能。本申请中描述的处理器和收发器可实现在集成电路(integrated circuit，IC)、模拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。该处理器和收发器也可以用各种IC工艺技术来制造，例如互补金属氧化物半导体(complementary metal oxide semiconductor，CMOS)、N型金属氧化物半导体(nMetal-oxide-semiconductor，NMOS)、P型金属氧化物半导体(positive channel metal oxide semiconductor，PMOS)、双极结型晶体管(bipolar junction transistor，BJT)、双极CMOS(BiCMOS)、硅锗(SiGe)、砷化镓(GaAs)等。
以上实施例描述中的寻呼处理装置可以是接入网设备或者终端设备，但本申请中描述的寻呼处理装置的范围并不限于此，而且寻呼处理装置的结构可以不受图9的限制。寻呼处理装置可以是独立的设备或者可以是较大设备的一部分。例如寻呼处理装置可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；
(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，计算机程序的存储部件；
(3)ASIC，例如调制解调器(Modem)；
(4)可嵌入在其他设备内的模块；
(5)接收机、终端设备、智能终端设备、蜂窝电话、无线设备、手持机、移动单元、车载设备、接入网设备、云设备、人工智能设备等等；
(6)其他等等。
对于寻呼处理装置可以是芯片或芯片系统的情况，可参见图10所示的芯片的结构示意图。图10所示的芯片包括处理器1001和接口1002。其中，处理器1001的数量可以是一个或多个，接口1002的数量可以是多个。
对于芯片用于实现本申请实施例中接入网设备的功能的情况：
接口1002，用于代码指令并传输至处理器；
处理器1001，用于运行代码指令以执行如图2至图5的方法。
对于芯片用于实现本申请实施例中终端设备的功能的情况：
接口1002，用于代码指令并传输至处理器；
处理器1001，用于运行代码指令以执行如图6至图7的方法。
可选的，芯片还包括存储器1003，存储器1003用于存储必要的计算机程序和数据。
本领域技术人员还可以了解到本申请实施例列出的各种说明性逻辑块(illustrative  logical block)和步骤(step)可以通过电子硬件、电脑软件，或两者的结合进行实现。这样的功能是通过硬件还是软件来实现取决于特定的应用和整个系统的设计要求。本领域技术人员可以对于每种特定的应用，可以使用各种方法实现的功能，但这种实现不应被理解为超出本申请实施例保护的范围。
本申请实施例还提供一种通信系统，该系统包括前述图8实施例中作为终端设备的寻呼处理装置和作为接入网设备的寻呼处理装置，或者，该系统包括前述图9实施例中作为终端设备的寻呼处理装置和作为接入网设备的寻呼处理装置。
本申请还提供一种可读存储介质，其上存储有指令，该指令被计算机执行时实现上述任一方法实施例的功能。
本申请还提供一种计算机程序产品，该计算机程序产品被计算机执行时实现上述任一方法实施例的功能。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。计算机程序产品包括一个或多个计算机程序。在计算机上加载和执行计算机程序时，全部或部分地产生按照本申请实施例的流程或功能。计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。计算机程序可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，计算机程序可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，高密度数字视频光盘(digital video disc，DVD))、或者半导体介质(例如，固态硬盘(solid state disk，SSD))等。
本领域普通技术人员可以理解：本申请中涉及的第一、第二等各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围，也表示先后顺序。
本申请中的至少一个还可以描述为一个或多个，多个可以是两个、三个、四个或者更多个，本申请不做限制。在本申请实施例中，对于一种技术特征，通过“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”等区分该种技术特征中的技术特征，该“第一”、“第二”、“第三”、“A”、“B”、“C”和“D”描述的技术特征间无先后顺序或者大小顺序。
本申请中各表所示的对应关系可以被配置，也可以是预定义的。各表中的信息的取值仅仅是举例，可以配置为其他值，本申请并不限定。在配置信息与各参数的对应关系时，并不一定要求必须配置各表中示意出的所有对应关系。例如，本申请中的表格中，某些行示出的对应关系也可以不配置。又例如，可以基于上述表格做适当的变形调整，例如，拆分，合并等等。上述各表中标题示出参数的名称也可以采用通信装置可理解的其他名称，其参数的取值或表示方式也可以通信装置可理解的其他取值或表示方式。上述各表在实现时，也可以采用其他的数据结构，例如可以采用数组、队列、容器、栈、线性表、指针、链表、树、图、结构体、类、堆、散列表或哈希表等。
本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (19)

  1. 一种寻呼处理方法，其特征在于，所述方法由终端设备执行，所述方法包括：
    接收接入网设备转发的针对非当前连接系统的寻呼请求；
    响应于所述终端设备的当前连接系统为繁忙状态，向所述接入网设备发送无线资源控制RRC恢复请求消息，其中，所述RRC恢复请求消息包括繁忙指示；
    其中，所述终端设备具有第一通信卡和第二通信卡，所述终端设备使用所述第一通信卡与所述当前连接系统通信，所述终端设备使用所述第二通信卡与所述非当前连接系统通信。
  2. 根据权利要求1所述的方法，其特征在于，所述RRC恢复请求消息还包括消息验证码MAC，所述生成MAC所需的输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，所述指定消息内容包括所述繁忙指示。
  3. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    根据所述完整性密钥、所述计数值、所述承载标识和所述传输方向信息对所述指定消息内容进行消息验证码计算，生成所述MAC。
  4. 根据权利要求1所述的方法，其特征在于，所述RRC恢复请求消息包括消息验证码MAC，所述生成MAC所需的输入参数包括恢复原因信息元、指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息。
  5. 根据权利要求4所述的方法，其特征在于，所述方法还包括：
    根据所述完整性密钥、所述恢复原因信息元、所述计数值、所述承载标识和所述传输方向信息对所述指定消息内容进行消息验证码计算，生成所述MAC。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述RRC恢复请求消息的恢复原因信息元包括所述繁忙指示。
  7. 一种寻呼处理方法，其特征在于，所述方法由接入网设备执行，所述方法包括：
    向终端设备转发针对非当前连接系统的寻呼请求；
    响应于接收到所述终端设备发送的无线资源控制RRC恢复请求消息，确定所述终端设备的当前连接系统处于繁忙状态，其中，所述RRC恢复请求消息包括繁忙指示。
  8. 根据权利要求7所述的方法，其特征在于，所述确定所述终端设备的当前连接系统处于繁忙状态，包括：
    从所述RRC恢复请求消息中提取第一消息验证码MAC；
    获取生成MAC所需的输入参数；
    根据所述生成MAC所需的输入参数生成第二MAC；
    在所述第一MAC和所述第二MAC一致的情况下，确定所述终端设备的当前连接系统处于繁忙状态。
  9. 根据权利要求8所述的方法，其特征在于，所述生成MAC所需的输入参数包括指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息，所述指定消息内容包括所述繁忙指示。
  10. 根据权利要求8所述的方法，其特征在于，所述生成MAC所需的输入参数包括恢复原因信息元、指定消息内容、完整性密钥、计数值、承载标识以及传输方向信息。
  11. 根据权利要求7-10任一项所述的方法，其特征在于，所述RRC恢复请求消息的恢复原因信息元包括所述繁忙指示。
  12. 一种寻呼处理装置，其特征在于，所述装置由终端设备执行，所述装置包括：
    收发单元，用于接收接入网设备转发的针对非当前连接系统的寻呼请求；响应于所述终端设备的当前连接系统为繁忙状态，向所述接入网设备发送无线资源控制RRC恢复请求消息，其中，所述RRC恢复请求消息包括繁忙指示；
    其中，所述终端设备具有第一通信卡和第二通信卡，所述终端设备使用所述第一通信卡与所述当前连接系统通信，所述终端设备使用所述第二通信卡与所述非当前连接系统通信。
  13. 一种寻呼处理装置，其特征在于，所述装置由接入网设备执行，所述装置包括：
    收发单元，用于向终端设备转发针对非当前连接系统的寻呼请求；
    处理单元，用于响应于接收到所述终端设备发送的无线资源控制RRC恢复请求消息，确定所述终端设备的当前连接系统处于繁忙状态，其中，所述RRC恢复请求消息包括繁忙指示。
  14. 一种寻呼处理装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求1至6中任一项所述的方法。
  15. 一种寻呼处理装置，其特征在于，所述装置包括处理器和存储器，所述存储器中存储有计算机程序，所述处理器执行所述存储器中存储的计算机程序，以使所述装置执行如权利要求7至11中任一项所述的方法。
  16. 一种寻呼处理装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求1至6中任一项所述的方法。
  17. 一种寻呼处理装置，其特征在于，包括：处理器和接口电路；
    所述接口电路，用于接收代码指令并传输至所述处理器；
    所述处理器，用于运行所述代码指令以执行如权利要求7至11中任一项所述的方法。
  18. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，实现如权利要求1至6中任一项所述的方法。
  19. 一种计算机可读存储介质，用于存储有指令，当所述指令被执行时，实现如权利要求7至11中任一项所述的方法。
PCT/CN2021/088233 2021-04-19 2021-04-19 寻呼处理方法及其装置 WO2022222012A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/088233 WO2022222012A1 (zh) 2021-04-19 2021-04-19 寻呼处理方法及其装置
CN202180001177.1A CN115516942A (zh) 2021-04-19 2021-04-19 寻呼处理方法及其装置

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/088233 WO2022222012A1 (zh) 2021-04-19 2021-04-19 寻呼处理方法及其装置

Publications (1)

Publication Number Publication Date
WO2022222012A1 true WO2022222012A1 (zh) 2022-10-27

Family

ID=83723674

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/088233 WO2022222012A1 (zh) 2021-04-19 2021-04-19 寻呼处理方法及其装置

Country Status (2)

Country Link
CN (1) CN115516942A (zh)
WO (1) WO2022222012A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112514472A (zh) * 2020-11-06 2021-03-16 北京小米移动软件有限公司 信息发送方法及装置、存储介质
WO2021159389A1 (en) * 2020-02-13 2021-08-19 Lenovo (Beijing) Limited Method and apparatus for paging control

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021159389A1 (en) * 2020-02-13 2021-08-19 Lenovo (Beijing) Limited Method and apparatus for paging control
CN112514472A (zh) * 2020-11-06 2021-03-16 北京小米移动软件有限公司 信息发送方法及装置、存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SONY: "KI#2: Update Solution #3 Busy Indication", 3GPP DRAFT; S2-2000838, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Incheon, South Korea; 20200113 - 20200117, 7 January 2020 (2020-01-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051842892 *

Also Published As

Publication number Publication date
CN115516942A (zh) 2022-12-23

Similar Documents

Publication Publication Date Title
CN113396611B (zh) 接入失败处理方法、装置、终端设备和存储介质
US11259362B2 (en) Method for repeatedly transmitting data and device
EP3764707A1 (en) Communication method, and communication device
US20220256501A1 (en) Communication method and apparatus
CN114342483A (zh) 接入控制方法及装置
WO2024065127A1 (zh) 控制中继设备信息发送的方法及其装置
WO2022222012A1 (zh) 寻呼处理方法及其装置
CN114175840A (zh) 随机接入方法和装置
CN113632551B (zh) 一种实现寻呼原因指示的方法及其装置
WO2022236623A1 (zh) 一种寻呼方法及其装置
WO2024060143A1 (zh) 一种上报方法/装置/设备及存储介质
WO2022266861A1 (zh) 寻呼处理方法、通信装置和存储介质
WO2024011435A1 (zh) 一种失败处理方法及其装置
WO2024011546A1 (zh) 数据传输配置方法和装置
WO2023206572A1 (zh) 小区状态配置方法及其装置
WO2024031373A1 (zh) 一种确定触发连续lbt失败的方法及装置
WO2024036519A1 (zh) 一种侧行链路pdcp复用的激活方法及装置
WO2024045039A1 (zh) 一种能力交互方法/装置/设备及存储介质
WO2023010531A1 (zh) 无线资源控制rrc连接恢复的安全增强方法和通信装置
WO2024060233A1 (zh) 信息上报方法和装置
WO2023130321A1 (zh) 一种数据压缩方法和装置
WO2024060234A1 (zh) 信息上报方法和装置
WO2023206033A1 (zh) 混合自动重传请求harq反馈的处理方法及其装置
WO2023010429A1 (zh) 一种带宽部分的同步方法及其装置
WO2023245453A1 (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: 21937263

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21937263

Country of ref document: EP

Kind code of ref document: A1