WO2017049442A1 - 一种寻呼设备和方法 - Google Patents

一种寻呼设备和方法 Download PDF

Info

Publication number
WO2017049442A1
WO2017049442A1 PCT/CN2015/090196 CN2015090196W WO2017049442A1 WO 2017049442 A1 WO2017049442 A1 WO 2017049442A1 CN 2015090196 W CN2015090196 W CN 2015090196W WO 2017049442 A1 WO2017049442 A1 WO 2017049442A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
rrc connection
network device
access network
paging message
Prior art date
Application number
PCT/CN2015/090196
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/CN2015/090196 priority Critical patent/WO2017049442A1/zh
Priority to CN201580028250.9A priority patent/CN107409382A/zh
Publication of WO2017049442A1 publication Critical patent/WO2017049442A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation

Definitions

  • the present invention relates to the field of wireless communication technologies, and in particular, to a paging device and method.
  • the user equipment In the Long Term Evolution (LTE) system, the user equipment (UE) has two radio resource control (RRC) states: idle state (IDLE) and connected state (Connected).
  • the UE in the connected state can transmit data with the network, and the UE in the idle state needs to establish a connection with the network to enter the connected state before data transmission can be performed.
  • the serving gateway Serving-GateWay, S-GW
  • MME Mobility Management Entity
  • the UE in the idle state can receive the paging message by using the discontinuous reception (DRX) mode to save power.
  • An evolved base station such as a radio frame configured by an evolved Node B (eNB) for paging, that is, a paging frame (PF), and a subframe used for paging in the PF, that is, a paging occasion (Paging Opportunity, PO).
  • eNB evolved Node B
  • PF paging frame
  • Paging Opportunity Paging Opportunity
  • the evolved base station sends a paging message to page the UE in the idle state, and each cell broadcasts a paging parameter such as a paging cycle in the system message.
  • the UE in the idle state calculates the paging frame of the paging message and the paging occasion in the paging frame according to the received paging parameter, and the UE can search only at its own paging occasion in one DRX cycle. Calling to receive, while entering sleep at other times, this can achieve the purpose of saving electricity.
  • the existing protocol is for a connected UE, and there is no feasible solution to ensure that the network effectively pages the UE.
  • a paging apparatus and method are provided for providing a UE for a connected state, providing a A paging scheme ensures that the network effectively pages the UE.
  • an embodiment of the present invention provides a terminal device, including:
  • a sending module configured to initiate a first radio resource control RRC connection establishment process to the access network device
  • a processing module configured to start a timer during the first RRC connection establishment process
  • a receiving module configured to receive a paging message sent by the access network device, where the paging message includes an identifier of the terminal device;
  • the sending module is further configured to: when the timer is in a timeout state, initiate a second RRC connection establishment process according to the paging message;
  • the processing module is further configured to: when the timer is in a non-timeout state, ignore the paging message to maintain an RRC connection established by the first RRC connection establishment process.
  • the timer is used to identify a scenario in which the RRC connection establishment process initiated by the terminal device and the paging process are concurrent.
  • the processing module is specifically configured to:
  • the timer is started when the sending module sends an RRC connection request message to the access network device.
  • the timer is started when the receiving module receives an RRC connection setup message sent by the access network device.
  • the duration of the timer is pre-defined by a protocol, or is determined by a paging cycle. Or determined by the access network device and notified to the terminal device.
  • an embodiment of the present invention provides an access network device, including:
  • a processing module configured to determine a duration of the timer
  • a sending module configured to notify the terminal device of the duration of the timer, so that the terminal device:
  • the paging message is ignored to maintain the RRC connection established by the first RRC connection establishment procedure.
  • the timer is used to identify a scenario in which the RRC connection establishment process initiated by the terminal device and the paging process are concurrent.
  • the processing module is specifically configured to:
  • the duration of the timer is determined according to a paging cycle.
  • an embodiment of the present invention provides an access network device, including:
  • a receiving module configured to receive a radio resource control RRC connection request message sent by the terminal device, where the RRC connection request message includes an identifier of the terminal device;
  • a processing module configured to determine, according to the identifier of the terminal device, that the receiving module has received the first paging message sent by the core network device for the terminal device, and has not yet been paged according to the first paging message The terminal device discards the first paging message.
  • the processing module is further configured to:
  • the receiving module When the receiving module receives the second paging message sent by the core network device for the terminal device, in the RRC connection establishment process triggered by the RRC connection request message or after the RRC establishment process is completed, Discarding the second paging message.
  • an embodiment of the present invention provides an access network device, including:
  • a receiving module configured to receive a second paging message sent by the core network device for the terminal device
  • a processing module configured to determine, according to the second paging message, whether a radio resource control RRC connection for the terminal device has been established, or whether an RRC connection for the terminal device is in an establishing process;
  • the processing module is further configured to: if it is determined that an RRC connection for the terminal device is established, or an RRC connection for the terminal device is in an establishing process, discarding the second paging message;
  • the access network device further includes a sending module, configured to: when the processing module determines that there is no established RRC connection for the terminal device, and does not have an ongoing RRC connection establishment process for the terminal device, according to The second paging message pages the terminal device.
  • the processing module determines that the RRC connection for the terminal device is established, or the RRC connection for the terminal device is in the process of being established, the receiving module is further configured to: receive the target that is sent by the core network device Receiving, by the terminal device, an RRC connection request message for establishing the RRC connection, where the RRC connection request message includes an identifier of the terminal device, before the second paging message of the terminal device;
  • the processing module is further configured to: if it is determined, according to the identifier of the terminal device, that the receiving module has received the first homing for the terminal device that is sent by the core network device before receiving the RRC connection request message And the sending module has not yet paged the terminal device according to the first paging message, and discards the first paging message.
  • an embodiment of the present invention provides a core network device, including:
  • a receiving module configured to receive a first initial user equipment UE message sent by the access network device, where the first initial UE message is triggered by the terminal device;
  • a processing module configured to: when it is determined that the core network device and the access network device have an S1 connection to the terminal device, release the S1 connection, and re-establish a connection with the access network device S1 connection for the terminal device.
  • the receiving module is further configured to: before receiving the first initial UE message sent by the access network device, receive the second initial sent by the access network device a UE message, where the second initial UE message is triggered by the terminal device;
  • the processing module is further configured to: determine that the S1 connection is already established between the core network device and the access network device;
  • the core network device further includes a sending module
  • the processing module is specifically configured to:
  • an embodiment of the present invention provides a paging method, including:
  • the terminal device initiates a first radio resource control RRC connection establishment process to the access network device;
  • the terminal device starts a timer in the first RRC connection establishment process
  • the terminal device When the timer is in a timeout state, the terminal device initiates a second RRC connection establishment process according to the paging message;
  • the terminal device When the timer is in a non-timeout state, the terminal device ignores the paging message to maintain an RRC connection established by the first RRC connection establishment procedure.
  • the timer is used to identify a scenario in which the RRC connection establishment process initiated by the terminal device and the paging process are concurrent.
  • the starting, by the terminal device, the starting timer in the initiated first RRC connection establishment process includes:
  • the terminal device starts the timer when sending an RRC connection request message to the access network device.
  • the terminal device starts the timer when receiving an RRC connection setup message sent by the access network device.
  • the duration of the timer is pre-defined by a protocol, or is determined by a paging cycle. Or determined by the access network device and notified to the terminal device.
  • an embodiment of the present invention provides a paging method, including:
  • the access network device determines the duration of the timer
  • the access network device notifies the terminal device of the duration of the timer, so that the terminal device:
  • the timer is started in a process of establishing a radio resource control RRC connection initiated by the access network device, and the paging message sent by the access network device is received, and the paging message is received.
  • identity of the terminal device is included:
  • the paging message is ignored to maintain the RRC connection established by the first RRC connection establishment procedure.
  • the timer is used to identify a scenario in which a terminal device initiates an RRC connection setup process and a paging process concurrently.
  • the access network device determines a duration of the timer, including:
  • the access network device determines the duration of the timer according to a paging cycle.
  • an embodiment of the present invention provides a paging method, including:
  • the access network device Determining that the access network device has received the first paging message for the terminal device that is sent by the core network device according to the identifier of the terminal device, and has not yet paged according to the first paging message.
  • the terminal device the access network device discards the first paging message.
  • the method further includes:
  • the access network device When the RRC connection setup procedure triggered by the RRC connection request message or the RRC setup process is completed, the access network device receives the second paging message sent by the core network device for the terminal device. And the access network device discards the second paging message.
  • a ninth aspect, the embodiment of the present invention provides a paging method, including:
  • the access network device determines that an RRC connection for the terminal device has been established, or the RRC connection for the terminal device is in the process of establishing, the access network device discards the second paging message;
  • the access network device determines that there is no established RRC connection for the terminal device, and does not have an ongoing RRC connection setup procedure for the terminal device, the access network device according to the second paging The message pages the terminal device.
  • the access network device determines that the RRC connection for the terminal device has been established, or the RRC connection for the terminal device is in the process of establishing, the access network device receives the target that is sent by the core network device. Before the second paging message of the terminal device, the method further includes: the access network device receiving, by the terminal device, an RRC connection request message for establishing the RRC connection, where the RRC connection request message includes the Identification of the terminal device;
  • the method further includes: if the access network device determines, according to the identifier of the terminal device, that the first homing for the terminal device that is sent by the core network device has been received before receiving the RRC connection request message And calling the message and not paging the terminal device according to the first paging message, the access network device discarding the first paging message.
  • the tenth aspect of the present invention provides a paging method, including:
  • the core network device determines that an S1 connection to the terminal device is already provided between the access network device, the core network device releases the S1 connection;
  • the core network device re-establishes an S1 connection with the access device to the terminal device.
  • the method before the receiving, by the core network device, the first initial UE message sent by the access network device, the method further includes:
  • the core network device determines that the S1 connection is already established between the access network device and the access network device;
  • the core network device releases the S1 connection, including:
  • the core network device sends a user equipment UE context release command message to the access network device, and is configured to trigger the access network device to send an RRC connection release message to the terminal device.
  • the terminal device when the terminal device receives the paging message for paging the terminal device, if the paging message carries the identifier of the terminal device, if it determines that it is in the connected state, it initiates in response to the received paging message. RRC connection establishment process. Therefore, the problem that the terminal device such as the UE determines that it is in the connected state, and the UE considers that the UE is in the idle state, the UE ignores the paging message sent by the network and causes serious loss of words.
  • the timer is ignored before the timer is in the timeout state.
  • the paging message is sent to the terminal device to initiate an RRC connection establishment process after the timer is in the timeout state; or the access network device distinguishes the received RRC connection request from the paging message to determine whether to send the paging message to the terminal device.
  • the previously established S1 connection is released and the new S1 connection is re-established to prevent the terminal device from finally entering the idle state and unable to transmit data with the network.
  • FIG. 1 is a schematic diagram of a signaling flow of an RRC connection established by a UE in response to a paging message;
  • FIG. 2 is a schematic diagram of a process in which a UE ignores a paging delivered by a network
  • FIG. 3 is a schematic structural diagram of a wireless communication system according to an embodiment
  • FIG. 4 is a flowchart of a process in which a terminal device initiates an RRC connection establishment in response to a paging message in the wireless communication system shown in FIG. 3;
  • FIG. 5 is a schematic structural diagram of the wireless communication system shown in FIG. 3 when it is an LTE system;
  • 6A and 6B are schematic diagrams showing a situation in which an RRC connection establishment process and a paging process are concurrent;
  • Option 8 is a flow chart of a possible implementation of Option 1;
  • Figure 11 is a flow chart of an alternative third to avoid concurrency
  • Figure 13 is a flow chart of an alternative fourth to avoid concurrency
  • FIG. 15 is a schematic structural diagram of a terminal device according to an embodiment
  • FIG. 16A and FIG. 16B are respectively schematic structural diagrams of two implementation manners of a terminal device according to an embodiment
  • FIG. 17 is a schematic structural diagram of an access network device according to an embodiment
  • FIG. 18A and FIG. 18B are respectively schematic structural diagrams of two implementation manners of an access network device according to an embodiment
  • FIG. 19 is a schematic structural diagram of an access network device according to an embodiment
  • FIG. 20A and FIG. 20B are respectively schematic structural diagrams of two implementation manners of an access network device according to an embodiment
  • 21 is a schematic structural diagram of an access network device according to an embodiment
  • FIG. 22A and FIG. 22B are respectively schematic structural diagrams of two implementation manners of an access network device according to an embodiment
  • FIG. 23 is a schematic structural diagram of a core network device according to an embodiment
  • FIG. 24A and FIG. 24B are respectively schematic structural diagrams of two implementation manners of a core network device according to an embodiment
  • 25 is a flowchart of a paging method provided by an embodiment
  • 26 is a flowchart of a paging method provided by an embodiment
  • FIG. 27 is a flowchart of a paging method provided by an embodiment
  • 29 is a flow chart of a paging method provided by an embodiment.
  • the UE in the idle state will initiate an RRC connection establishment procedure in response to the paging message, and the UE can perform data transmission with the network after entering the connected state; and if the UE in the connected state receives the homing If the message is called, the paging message will be ignored and the RRC connection establishment process will not be initiated.
  • the above-mentioned UE processing paging messages may cause a loss of call, as detailed below:
  • FIG. 1 A process for processing a paging message sent by a UE to a base station is as shown in FIG. 1:
  • the MME sends a paging message (Paging) to the UE through the base station, and after receiving the paging message, the UE sends an RRC Connection Request message to the base station, requesting to establish an RRC connection, and after receiving the RRC connection request message, the base station receives the RRC connection request message.
  • Paging paging message
  • RRC Connection Request message to the base station
  • the base station receives the RRC connection request message.
  • RRC connection establishment is completed. (RRC Conneciton Setup Complete) message completes the establishment of the RRC connection.
  • the base station After receiving the RRC connection setup complete message, the base station sends an initial UE message to the MME. After receiving the initial UE message, the MME sends an Initial Context Setup Request message to the base station to request to establish the initial UE message. The context of the UE. After receiving the initial context setup request message, the base station may send an RRC Security Mode Command (RRC Security Mode Command) message to the UE, carrying the relevant parameters of the encryption and integrity protection, and the UE obtains the relevant parameters of the encryption and integrity protection, and then replies RRC Security Mode Complete.
  • RRC Security Mode Command RRC Security Mode Command
  • the base station may send an RRC Connection Reconfiguration to the UE, and the UE replies to the RRC Connection Reconfiguration, thereby completing the reconfiguration procedure of the RRC connection.
  • the base station returns an Initial Context Setup Complete message to the MME to complete the establishment of the context of the UE.
  • the UE enters the connected state after receiving the RRC Connection Setup message sent by the base station. If the UE in the connected state receives the paging message, it will ignore the message and will not process it accordingly.
  • the base station sends an RRC Connection Release message to the UE to release the RRC connection and enter the idle state.
  • the UE may not receive the RRC connection release message sent by the base station because the signal quality is poor. This causes the network to consider that the UE enters the idle state, but the UE side is still in the connected state.
  • the UE considers that the UE is in the idle state to trigger the paging.
  • the base station sends the paging message to the UE in the air interface, the UE ignores the paging and does not initiate the connection establishment process according to the provisions of the existing protocol. In the end, the network side cannot page the UE, causing a loss of words.
  • the present invention provides a paging device and method for implementing correct processing of paging messages sent by a base station by a UE to ensure normal communication with a network.
  • FIG. 3 is a schematic structural diagram of a wireless communication system according to an embodiment.
  • the wireless communication system includes: a terminal device 301, an access network device 302, and a core network device 303, wherein the terminal device 301 can be connected to the access network device 302 through a wireless connection, and the access network device 302 can pass A wired or wireless connection is connected to the core network device 303.
  • the base station can send a paging message to the UE in the following situations:
  • the paging message After receiving the paging message of the paging UE sent by the MME, the paging message is sent to the UE in the idle state on the air interface, and the paging message carries the identification information of the UE, for example, the system architecture evolution (System Architecture Evolution) , SAE Temporary Mobile Station Identifier (S-TMSI) or International Mobile Subscriber Identification Number (IMSI);
  • system architecture evolution System Architecture Evolution
  • S-TMSI SAE Temporary Mobile Station Identifier
  • IMSI International Mobile Subscriber Identification Number
  • the paging message carries the identification information of the UE. Therefore, the UE is on the air interface After receiving the paging message, if it is determined that the paging message carries its own identification information, it may be determined that the paging message is a paging message sent to itself for paging the UE in an idle state.
  • the UE if the UE does not receive the RRC connection release message, the UE considers that it is still in the connected state. According to the current processing in the LTE system, the UE discards the paging message.
  • the terminal device 301 when the terminal device 301 receives the paging message for paging the terminal device 301, and the paging message carries the identifier of the terminal device 301, even if it determines that it is in the connected state, The RRC connection setup procedure is initiated in response to the paging message.
  • the communication system of the wireless communication system shown in FIG. 3 includes but is not limited to: Global System of Mobile communication (GSM), Code Division Multiple Access (CDMA) IS-95, and code division multiple access.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • 2000 Time Division-Synchronous Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE-advanced Personal Handy-phone System
  • WiFi Wireless Fidelity
  • 802.11 series of protocols Worldwide Interoperability for Microwave Access (WiMAX)
  • WiMAX Worldwide Interoperability for Microwave Access
  • WiMAX Worldwide Interoperability for Microwave Access
  • future evolutions A wireless communication system.
  • the terminal device determines that it is in the connected state, and the network determines that the terminal device is in the idle state, and causes the terminal device to ignore the paging message for paging the terminal device in the idle state, and can be used.
  • the wireless communication system shown in Figure 3 avoids losing calls.
  • the network here may refer to the access network device 302, and may also refer to the access network device 302 and the core network device 303, or may also include the access network device 302 and the core network device 303 and other network devices.
  • the terminal device 301 may be a wireless terminal, and the wireless terminal may be a device that provides voice and/or data connectivity to the user, a handheld device with wireless connection function, or is connected to the wireless device. Other processing devices for the modem.
  • the wireless terminal can communicate with one or more core networks via a radio access network (eg, RAN, Radio Access Network), which can be a mobile terminal, such as a mobile phone (or "cellular" phone) and with a mobile terminal
  • RAN Radio Access Network
  • the computers for example, can be portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile devices that exchange language and/or data with the wireless access network.
  • a wireless terminal may also be called a Subscriber Unit, a Subscriber Station, a Mobile Station, a Mobile, a Remote Station, an Access Point, and a Remote Terminal.
  • Remote Terminal Access Terminal, User Terminal, User Agent, User Device, or User Equipment.
  • the access network device 302 may include a base station, or a radio resource management device for controlling the base station, or a base station and a radio resource management device for controlling the base station; wherein the base station may be a macro station or a small station, such as a small cell (small).
  • the base station may also be a home base station, such as a Home NodeB (HNB), a Home eNodeB (HeNB), etc., and the base station may also include a relay node ( Relay) and so on.
  • HNB Home NodeB
  • HeNB Home eNodeB
  • Relay relay node
  • the core network device 303 may include a core network device for mobility management, such as a Mobile Switching Center (MSC), or a Mobility Management Entity (MME).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • the LTE system access network device 302 such as TDD LTE, FDD LTE, or LTE-A, may be an evolved Node B (eNodeB), the terminal device 301 may be a UE, and the core network device 303 may be an MME;
  • the SCDMA system or the WCDMA system, the access network device 302 may include: a Node B (NodeB) and/or a Radio Network Controller (RNC), the terminal device 301 may be a UE, and the core network device 303 may be an MSC;
  • the access network device 302 may include a Base Transceiver Station (BTS) and/or a Base Station Controller (BSC), and the terminal 102 may be a mobile station (Mobile Station, MS), the core network device 303 can be an MSC.
  • BTS Base Transceiver Station
  • BSC Base Station Controller
  • the network architecture of the wireless communication system shown in FIG. 3 can be as shown in FIG. 5.
  • the terminal device 301 is a UE
  • the access network device 302 is a base station
  • the core network device 303 is an MME.
  • the interface between the UE and the base station is a Uu interface, which is also called an “air interface”, an “air interface”, and a “wireless interface”.
  • the interface between the MME and the S-GW is the S1-U interface
  • the interface between the MME and the S-GW is the S11 interface.
  • the interface between the MME and the S-GW is the S11 interface. .
  • the process shown in FIG. 4 may cause the terminal device 301 to enter an idle state and fail to establish a connection with the network.
  • the LTE system will be described as an example with reference to FIG. 6A.
  • the dotted line represents the paging access procedure
  • the solid line represents the active access procedure of the terminal device 301.
  • the access network device 302 base station
  • the base station After receiving the paging message sent by the core network device 303 (MME), the access network device 302 (base station) does not immediately page the corresponding terminal device 301 (UE) in the air interface, but waits until the paging occasion of the UE arrives.
  • the paging message is sent to the UE, so the base station may send a paging message to the UE before the RRC Connection Mode Complete message is sent, and the UE responds to the RRC connection setup process.
  • the incoming paging message initiates the RRC connection setup process again, and the base station sends an Initial UE Message to the MME again on the S1-MME interface, and the MME identifies the received Initial UE twice according to the UE identifier S-TMSI carried in the Initial UE Message message.
  • the message is triggered by the same UE. Therefore, the MME considers that there is an error, and then sends a UE context release command to the base station to release the previously established UE context. After receiving the command, the base station determines that the context establishment fails, and returns the initial context establishment to the MME.
  • the "Initial Context Setup Fail" message is sent and the RRC Connection Release message is sent to the UE (corresponding to the RRC Connection Rel in the solid line in Figure 6A).
  • Ease message the MME does not request to establish a new S1 connection because it receives the Initial UE Message again (initial UE Message message in dotted line in FIG. 6A), and therefore corresponds to the second Initial in FIG. 6A sent by the base station.
  • the UE message (the initial UE message in the dotted line in FIG. 6A), the base station waits for a preset duration, but does not receive the response message of the MME before the preset duration expires, and then sends an RRC connection release message to the UE again.
  • the terminal device 301 starts a timer, and if the terminal device 301 receives the paging message before the timer is in the timeout state, the paging is ignored, if the terminal device 301 is in timing. After receiving the paging message after the device is in the timeout state, the RRC connection establishment process is initiated again;
  • the access network device 302 performs corresponding judgment according to the two messages received in the paging message and the RRC connection request message to determine whether to send in the air interface. Paging message
  • the core network device 303 performs corresponding processing on the scenario shown in FIG. 6A: the MME releases the previously established Initial UE Message message and releases the previously established between the core network device 303 and the access network device 302. The S1 connection for the terminal device 301 on the interface and the S1 connection for the terminal device 301 is re-established on the interface between the core network device 303 and the access network device 302.
  • FIG. 7 is a flow chart of an alternative one. As shown in FIG. 7, the process includes the following steps:
  • the terminal device 301 initiates a first RRC connection establishment process to the access network device 302, for example, by sending an RRC connection request message to initiate the first RRC connection establishment process;
  • S702 The terminal device 301 starts a timer in the initiated first RRC connection establishment process, or after the RRC connection establishment is completed.
  • the terminal device 301 receives the paging message sent by the access network device 302, where the paging message carries the identifier of the terminal device 301.
  • the terminal device 301 performs the step S704: Initiate a second RRC connection setup procedure in response to the received paging message; if the timer is in a non-timeout state, the terminal device 301 ignores the paging message.
  • the terminal device 301 ignores the paging message and can maintain the RRC connection established by the first RRC connection procedure.
  • the terminal device 301 may start a timer in the first RRC connection establishment process or after the RRC connection establishment is completed, so that the terminal device 301 is in the timer according to the received paging message. Before the status, the timer is still in the timeout state and then decide whether to process the paging message.
  • the timer started by the terminal device 301 can exclude the foregoing situation shown in FIG. 6A. If the terminal device 301 receives the paging message before the timer is in the timeout state, the terminal device 301 ignores the paging message and does not perform corresponding processing. If the terminal device 301 receives the paging message after the timer is in the timeout state, Then, the terminal device 301 initiates a second RRC connection establishment procedure in response to the paging.
  • the terminal device 301 may start a timer when transmitting an RRC connection request, or the terminal device 301 starts a timer when receiving the RRC connection setup message, or the terminal device 301 starts timing when transmitting the RRC connection setup complete message. Device.
  • the terminal device 301 enters the connected state after receiving the RRC connection setup message, so it may be preferred to start the timer when the terminal device 301 receives the RRC connection setup message.
  • the duration of the timer can be 1 s, 2 s, 2.5 s, 3 s, ..., 10 s, 10.5 s, and the like.
  • the minimum time that the timer can be set is a paging period.
  • the timer is used to identify a scenario in which the terminal device initiates an RRC connection setup process and a paging process, such as the scenario shown in FIG. 6A.
  • the RRC connection setup process initiated by the terminal device and the MME send the search.
  • the call message occurs in a similar time.
  • the access network device 302 starts from the paging occasion of the paging terminal device 301 until the access network device 302 sends the initial UE message to the core network device 303.
  • the network access device 302 sends a paging message of the paging terminal device 301, which will result in the above-mentioned concurrent scene.
  • the setting of the duration of the timer may take into consideration the following factors: if the duration of the timer is too short, the situation shown in FIG. 6A cannot be avoided. If the duration of the timer is too long, the terminal device 301 may miss the receiving occasion of the paging message. However, when the duration of the timer is set, it may be considered that the terminal device 301 can re-enter the connected state and the network for data transmission after initiating the RRC connection establishment process again. such as:
  • the duration of the timer is calculated according to a certain formula.
  • the access network device 302 broadcasts the paging cycle of the terminal device 301 in the system message, and the terminal device 301 can determine the duration of the timer according to the paging cycle, such as a timer.
  • the duration can be set to: 2 times the paging cycle, which is only an example, and does not exclude other ways of determining the duration of the timer according to the paging cycle;
  • the terminal device 301 is determined and notified by the access network device 302. For example, the terminal device 301 starts the timer when the RRC connection setup message is received, and the access network device 302 can carry the information indicating the duration of the timer in the RRC connection setup message sent to the terminal device 301, and the terminal device After receiving the RRC connection setup message, the 301 obtains the information indicating the duration of the timer from the message, and determines the duration of the timer according to the information. For example, the access network device 302 can determine that the duration of the timer is 10s.
  • the access network device 302 can determine the duration of the timer based on the paging cycle.
  • the timer is started when the terminal device 301 receives the RRC connection setup message, and an executable process of the first solution is shown.
  • the terminal device 301 initiates an RRC connection setup procedure by transmitting an RRC connection request message, and the terminal device 301 starts a timer when receiving the RRC connection setup message sent by the access network device 302 in the RRC connection setup process.
  • the terminal device 301 receives the paging message sent by the access network device 302. If the started timer does not time out when the paging message is received, the paging message is ignored; if the paging message is received, the timer is received. If terminated, the RRC connection setup procedure is re-initiated in response to the paging message.
  • the terminal device 301 starts a timer to avoid the situation that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network, and can avoid lost calls.
  • Head In the pre-LTE system only when the terminal device 301 is in the idle state receives the paging message, the connection is established with the network, and the terminal device 301 in the connected state ignores the paging message, which may cause a lost call.
  • the optional solution 1 can solve the problem of lost calls, and can also avoid the situation that the RRC connection establishment process and the paging process are concurrent.
  • the scenario in which the RRC connection establishment process initiated by the terminal device and the paging message sent by the network are concurrently generated is performed, thereby preventing the UE shown in FIG. 6A from entering the idle state.
  • the problem of data transmission with the network is performed, thereby preventing the UE shown in FIG. 6A from entering the idle state.
  • the terminal device 301 starts from transmitting an RRC connection request, to a Signaling Radio Bearer (SRB) 2 or data.
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer
  • the terminal device 301 starts from transmitting an RRC connection request, to a Signaling Radio Bearer (SRB) 2 or data.
  • DRB Data Radio Bearer
  • the received paging message is ignored; optionally, in SRB2 and DRB
  • the received paging message may be processed, for example, an RRC connection establishment procedure is initiated in response to the paging message.
  • FIG. 9 is a flow chart of Option 2. As shown in FIG. 9, the process includes the following steps:
  • the access network device 302 receives an RRC connection request message sent by the terminal device 301, where the RRC connection request message includes an identifier of the terminal device 301.
  • the access network device 302 determines, according to the identifier of the terminal device 301, whether the paging message for the terminal device 301 sent by the core network device 303 has been received before; if the access network device 302 determines that the core network device 303 has been received before. For the paging message of the terminal device 301, step S903 is performed;
  • the access network device 302 determines whether the terminal device 301 has been paged according to the paging message; if the access network device 302 determines that the terminal device 301 has not been paged according to the paging message, the paging message is discarded.
  • the discarding of the paging message may be understood as the access network device 302 abandoning the paging terminal device 301, which will not be described below.
  • the access network device 302 receives the paging message for the terminal device 301 sent by the core network device 303 before receiving the RRC connection request, as an example.
  • the access network device 302 first receives a paging message sent by the core network device 303, where the paging message includes the identifier S-TMSI of the paged terminal device 301.
  • the access network device 302 maintains the S-TMSI after receiving the paging message.
  • the access network device 302 configures the radio frames and subframes used by the paging terminal device 301, i.e., determines the paging occasion, and the access network device 302 prepares to send a paging message at the determined paging occasion to page the terminal device 301.
  • the access network device 302 receives the RRC connection request message sent by the terminal device 301, and the request message also carries the identifier S-TMSI of the terminal device 301, and the access network device 302 is an avoidance map.
  • the method in which the UE shown in FIG. 6A finally enters an idle state and cannot transmit data with the network takes place:
  • the access network device 302 After receiving the RRC connection request message, the access network device 302 determines whether the S-TMSI carried in the message has been maintained by the access network device 302, that is, whether the terminal device has been received by the core network device 303. If the paging message for the terminal device 301 sent by the core network device 303 has been received before, it is further determined whether the paging message has been sent to the terminal device 301, that is, the access network device 302 is from the core network. The device 303 receives the paging message, and the paging message carries the S-TMSI, and the access network device 302 determines the S-TMSI corresponding terminal device 301, and the access network device 302 further determines the seeking for paging the terminal device 301.
  • the access network device 302 discards the paging message waiting to be sent, and does not place the paging at the corresponding paging occasion. The message is sent to the terminal device 301.
  • the access network device 302 receives another one for the terminal device 301 sent by the core network device 303.
  • the paging message (the paging message is not the paging message mentioned in step S902), the access network device 302 discards the paging message.
  • FIG. 11 is a flow chart of Option 3. As shown in FIG. 11, the process includes the following steps:
  • the access network device 302 receives the paging message sent by the core network device 303 for the terminal device 301.
  • the access network device 302 determines whether an RRC connection for the terminal device 301 has been established, or whether the RRC connection for the terminal device 301 is in the establishment process; if the access network device 302 determines that the RRC for the terminal device 301 has been established. The connection, or the RRC connection for the terminal device 301 is in the process of establishing, discarding the paging message (eg, abandoning the paging terminal device 301); if the access network device 302 determines that there is no established RRC connection for the terminal device 301, There is no ongoing RRC connection establishment process for the terminal device 301, then step S1103 is performed;
  • S1103 The access network device 302 pages the terminal device 301.
  • the access network device 302 first receives an RRC connection request message sent by the terminal device 301, where the message includes the identifier S-TMSI of the terminal device 301, and the access network device 302 establishes the message after receiving the message.
  • An instance corresponding to the terminal device 301 is configured to maintain related information (including information related to the terminal device 301 requested by the S-TMSI to enter the connected state and context information after the terminal device 301 enters the connected state).
  • the access network device 302 After receiving the paging message sent by the core network device 303, the access network device 302 determines whether the S-TMSI carried in the paging message is included in the established instance of the access network device 302, that is, whether the established The RRC connection of the terminal device 301, or in the process of whether the RRC connection of the terminal device 301 is being established.
  • the terminal device 301 is requesting to enter the connected state (ie, the RRC connection is being established) or is already in the connected state (ie, the RRC connection for the terminal device 301 has been established), so the access network The device 302 ignores the paging message without paging the terminal device 301; otherwise, the access network device 302 sends a paging message to the terminal device 301 on the air interface.
  • step S1102 if the access network device 302 determines that the RRC connection for the terminal device 301 has been established, or the RRC connection for the terminal device 301 is in the process of establishing, the access network device 302 receives the core in step S1101. Before the paging message sent by the network device 303 for the terminal device 301, the access network device 302 may further include: the RRC connection request message sent by the terminal device 301 for establishing an RRC connection, where the RRC connection request message includes the terminal device 301 Standard knowledge;
  • the access network device 302 determines, according to the identifier of the terminal device 301, another paging message sent by the core network device 303 for the terminal device 301 has been received before receiving the RRC connection request message (the paging message is different from step S1101). The paging message received therein) and the paging device 301 has not been paged according to the paging message, the access network device 302 determines to discard the paging message (e.g., abandon the paging terminal device 301).
  • the access network device 302 receives the RRC connection request message and the paging message according to the situation.
  • the chronological order is processed in two cases, and the access network device 302 determines whether to send a paging message on the air interface according to its own judgment.
  • FIG. 13 is a flow chart of Option 4. As shown in FIG. 13, the process includes the following steps:
  • the core network device 303 receives the initial user equipment UE message sent by the access network device 302 for the terminal device 301.
  • the initial UE message is taken as an example. In fact, any is used between the access network device and the core network device.
  • the message triggering the establishment of a signaling connection for the terminal device on the interface can be applied;
  • the core network device 303 determines whether the S1 connection to the terminal device 301 is already provided on the interface between the core network device 303 and the access network device 302; if it is determined that the S1 connection is already provided, step S1303 is performed;
  • the core network device 303 releases the existing S1 connection, and re-establishes the S1 connection for the terminal device 301 on the interface between the core network device 303 and the access network device 302 in response to the initial UE message.
  • the method further includes:
  • the core network device 303 receives another initial UE message sent by the access network device 302, where the initial UE message is triggered by the terminal device 301.
  • the core network device 303 determines that the S1 connection is already established with the access network device 302;
  • step S1303 the core network device 303 releases the S1 connection, including:
  • the core network device 303 sends a user equipment UE context release command message to the access network device 302 for triggering the access network device 302 to send an RRC connection release message to the terminal device 301.
  • the terminal device 301 finally enters an idle state and cannot perform data transmission with the network.
  • the core network device 303 can perform the step S1302, and if it is determined that the S1 connection exists, the S1 connection is released and the S1 connection to the terminal device 301 is re-established by performing step S1303. The connection enables data transmission between the terminal device 301 and the network.
  • FIG. 14 is a flow chart of an alternative implementation of Option 4.
  • the dotted line represents the paging access procedure
  • the solid line represents the active access procedure of the terminal device 301
  • the dotted line represents the message flow triggered by the core network device 303 reestablishing the S1 connection after the optional scheme 4 is used.
  • the terminal device 301 After receiving the RRC connection setup complete message, the terminal device 301 receives the paging message sent by the access network device 302 before receiving the RRC security mode command message, and the terminal device 301 re-initiates the RRC connection establishment process in response to the paging message.
  • the network access device 302 After receiving the RRC connection setup complete message, the network access device 302 sends an initial UE message to the core network device 303 again on the S1 interface, and the core network device 303 recognizes the identifier of the terminal device 301 (S-TMSI) carried in the initial UE message.
  • S-TMSI the identifier of the terminal device 301
  • the core network device 303 transmits a UE context release command to the access network device 302 after receiving the initial UE message again.
  • the core network device 303 releases the previously established after receiving the initial UE message again.
  • the S1 connection for the terminal device 301 and requesting to establish a new S1 connection for the terminal device 301 ensures that the terminal device 301 re-enters the connected state and the network for data transmission.
  • the core network device 303 identifies the received initial UE twice according to the terminal device 301 identifier (S-TMSI) carried in the message.
  • the message is triggered by the same terminal device 301.
  • the core network device 303 considers that it is erroneous to release the previously established S1 connection for the terminal device 301, that is, sends a UE context release command message to the access network device 302 to trigger the access network.
  • the device 302 sends an RRC connection release message to the terminal device 301.
  • the access network device 302 sends a UE Context Release Complete message to the core network device 303, and the core network device 303 releases the S1.
  • the connection eventually causes the terminal device 301 to enter an idle state and cannot transmit data with the network.
  • the core network device 303 after receiving the initial UE message, not only needs to release the previously established S1 connection for the terminal device 301, but also requests to establish a new S1 connection for the terminal device 301, that is, by sending an initial context.
  • the establishment request triggers the access network device 302 to perform an RRC connection reconfiguration process, sends an RRC Connection Reconfiguration message to the terminal device 301, and receives an RRC Connection Reconfiguration Complete message sent by the terminal device 301.
  • the reconfiguration of the RRC connection of the terminal device 301 is completed, so that the terminal device 301 re-enters the connected state and the network for data transmission.
  • the access network device 302 After receiving the RRC connection reconfiguration complete message sent by the terminal device 301, the access network device 302 sends an Initial Context Setup Complete message to the core network device 303, indicating that the S1 connection has been established.
  • FIG. 15 is a schematic structural diagram of a terminal device according to an embodiment. As shown in Figure 15, the end End devices include:
  • the sending module 1501 is configured to initiate a first RRC connection establishment process to the access network device.
  • the processing module 1502 is configured to start a timer during the first RRC connection establishment process
  • the receiving module 1503 is configured to receive a paging message sent by the access network device, where the paging message includes an identifier of the terminal device.
  • the sending module 1501 is further configured to: when the timer is in a timeout state, initiate a second RRC connection establishment process according to the paging message;
  • the processing module 1502 is further configured to: when the timer is in a non-timeout state, ignore the paging message to maintain the RRC connection established by the first RRC connection establishment process.
  • the timer is used to identify a scenario in which the RRC connection establishment procedure initiated by the terminal device and the paging process are concurrent.
  • processing module 1502 is specifically configured to:
  • the timer is started when the receiving module 1503 receives the RRC connection setup message sent by the access network device.
  • the duration of the timer is pre-defined by the protocol, or determined by the paging cycle, or determined by the access network device and notified to the terminal device.
  • timer duration timer start and termination
  • sending module 1501 refers to the foregoing Option 1
  • sending operation of the terminal device 301 refers to the sending operation of the terminal device 301.
  • processing module 1502 refers to the foregoing Option 1
  • processing of the terminal device 301 refers to the processing of the terminal device 301.
  • receiving module 1503 refers to the receiving operation of the terminal device 301 in the foregoing Option 1.
  • the scenario of the RRC connection establishment process initiated by the terminal device and the paging process sent by the network is identified by setting a timer, thereby avoiding the problem that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network.
  • the transmitter 1601 is configured to initiate a first RRC connection establishment process to the access network device.
  • the processor 1602 is configured to start a timer during the first RRC connection establishment process
  • the receiver 1603 is configured to receive a paging message sent by the access network device, where the paging message includes an identifier of the terminal device.
  • the transmitter 1601 is further configured to: when the timer is in a timeout state, initiate a second RRC connection establishment process according to the paging message;
  • the processor 1602 is further configured to: when the timer is in a non-timeout state, ignore the paging message to maintain the RRC connection established by the first RRC connection establishment process.
  • the terminal device can be implemented by the structure shown in FIG. 16A or FIG. 16B.
  • a transmitter 1601 and a receiver 1603 are respectively connected to a processor 1602.
  • Fig. 16B shows a bus structure.
  • the bus structure may include any number of interconnected buses and bridges.
  • the processor 1602, the memory 1604, the transmitter 1601, and the receiver 1602 are connected to each other through a bus 1605.
  • the memory 1604 is for storing instructions
  • the processor 1602 is for executing instructions stored in the memory 1604 to control the receiver 1603 to receive signals and to control the transmitter 1601 to transmit signals.
  • transmitter 1601 For other optional implementations of the transmitter 1601, reference may be made to the sending module 1501. Other optional implementations of the processor 1602 may refer to the processing module 1502. Other optional implementations of the receiver 1603 may refer to the receiving module 1503.
  • the scenario of the RRC connection establishment process initiated by the terminal device and the paging process initiated by the network is identified by setting a timer, thereby avoiding the problem that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network.
  • FIG. 17 is a schematic structural diagram of an access network device according to an embodiment. As shown in FIG. 17, the access network device includes:
  • the processing module 1701 is configured to determine a duration of the timer
  • the sending module 1702 is configured to notify the terminal device of the duration of the timer, so that the terminal device:
  • the timer is started during the first establishment of the RRC connection initiated by the access network device, and when the paging message sent by the access network device is received, and the paging message includes the identifier of the terminal device:
  • the second RRC connection establishment process is initiated according to the paging message
  • the paging message is ignored to maintain the RRC connection established by the first RRC connection setup procedure.
  • the timer is used to identify a scenario in which the RRC connection establishment procedure initiated by the terminal device and the paging process are concurrent.
  • processing module 1701 is specifically configured to:
  • the duration of the timer is determined according to the paging cycle.
  • the other optional implementation manners of the processing module 1701 may refer to the processing operation of the access network device 302 in the foregoing Option 1
  • other optional implementation manners of the sending module 1702 may refer to the foregoing Option 1
  • the scenario of the RRC connection establishment process initiated by the terminal device and the paging process initiated by the network is identified by setting a timer, thereby avoiding the problem that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network.
  • the processor 1801 is configured to determine a duration of the timer.
  • the sender 1802 is configured to notify the terminal device of the duration of the timer, so that the terminal device:
  • the timer is started during the first establishment of the RRC connection initiated by the access network device, and when the paging message sent by the access network device is received, and the paging message includes the identifier of the terminal device:
  • the second RRC connection establishment process is initiated according to the paging message
  • the paging message is ignored to maintain the RRC connection established by the first RRC connection setup procedure.
  • the timer is used to identify the RRC connection establishment process and the paging process initiated by the terminal device. Concurrent scenes.
  • the processor 1801 is specifically configured to:
  • the duration of the timer is determined according to the paging cycle.
  • processor 1801 For other optional implementation manners of the processor 1801, reference may be made to the processing operation of the access network device in the foregoing Option 1, and other optional implementation manners of the transmitter 1802 may refer to the foregoing Option 1, accessing The sending operation of the network device.
  • the access network device can be implemented by the structure shown in FIG. 18A or FIG. 18B.
  • the transmitter 1802 is connected to the processor 1801.
  • Fig. 18B shows a bus structure.
  • the bus structure may include any number of interconnected buses and bridges.
  • the processor 1801, the memory 1803, and the transmitter 1802 are connected to one another via a bus 1805.
  • the memory 1803 is for storing instructions
  • the processor 1801 is for executing instructions stored in the memory 1803 to control the transmitter 1802 to transmit signals.
  • transmitter 1802 For other optional implementations of the transmitter 1802, reference may be made to the sending module 1702. Other optional implementations of the processor 1801 may refer to the processing module 1701.
  • the scenario of the RRC connection establishment process initiated by the terminal device and the paging process initiated by the network is identified by setting a timer, thereby avoiding the problem that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network.
  • FIG. 19 is a schematic structural diagram of an access network device according to an embodiment. As shown in FIG. 19, the access network device includes:
  • the receiving module 1901 is configured to receive a radio resource control RRC connection request message sent by the terminal device, where the RRC connection request message includes an identifier of the terminal device;
  • the processing module 1902 is configured to determine, according to the identifier of the terminal device, that the receiving module 1901 has received the first paging message for the terminal device sent by the core network device, and has not yet paged the terminal device according to the first paging message, discarding the first homing Call the message.
  • processing module 1902 is further configured to:
  • the receiving module 1901 receives the second paging message sent by the core network device for the terminal device, Then the second paging message is discarded.
  • receiving module 1901 For other optional implementation manners of the receiving module 1901, reference may be made to the receiving operation of the access network device 302 in the foregoing optional solution 2, and other optional implementation manners of the processing module 1502 may be referred to the foregoing optional solution 2.
  • the access network device determines whether to send the paging message in the air interface according to the received RRC connection request message and the paging message. The situation that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network is effectively avoided.
  • the receiver 2001 is configured to receive a radio resource control RRC connection request message sent by the terminal device, where the RRC connection request message includes an identifier of the terminal device.
  • the processor 2002 is configured to determine, according to the identifier of the terminal device, that the receiver 2001 has received the first paging message sent by the core network device for the terminal device, and has not yet paged the terminal device according to the first paging message, discarding the first homing Call the message.
  • the access network device may be implemented by the structure shown in FIG. 20A or FIG. 20B.
  • the receiver 2001 is connected to the processor 2002.
  • Fig. 20B shows a bus structure.
  • the bus structure may include any number of interconnected buses and bridges.
  • the processor 2002, the memory 2003, and the receiver 2001 are connected to each other through a bus 2004.
  • the memory 2003 is for storing instructions
  • the processor 2002 is for executing instructions stored in the memory 2003 to control the receiver 2001 to receive signals.
  • processor 2002 For other optional implementations of the processor 2002, reference may be made to the processing module 1902. Other optional implementations of the receiver 2001 may refer to the receiving module 1901.
  • the access network device determines whether to send the paging message in the air interface according to the received RRC connection request message and the paging message. The situation that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network is effectively avoided.
  • FIG. 21 is a schematic structural diagram of an access network device according to an embodiment. As shown in Figure 21, the Access network equipment includes:
  • the receiving module 2101 is configured to receive a second paging message sent by the core network device for the terminal device.
  • the processing module 2102 is configured to determine, according to the second paging message, whether a radio resource control RRC connection for the terminal device has been established, or whether the RRC connection for the terminal device is in the establishing process;
  • the processing module 2102 is further configured to: if it is determined that the RRC connection for the terminal device has been established, or the RRC connection for the terminal device is in the process of establishing, discarding the second paging message;
  • the access network device further includes a sending module 2103, configured to, according to the second paging message, when the processing module 2102 determines that there is no established RRC connection for the terminal device, and there is no ongoing RRC connection establishment procedure for the terminal device. Call the terminal device.
  • a sending module 2103 configured to, according to the second paging message, when the processing module 2102 determines that there is no established RRC connection for the terminal device, and there is no ongoing RRC connection establishment procedure for the terminal device. Call the terminal device.
  • the receiving module 2101 is further configured to: receive, by the receiving core device, the terminal device Before the second paging message, the receiving, by the terminal device, an RRC connection request message for establishing an RRC connection, where the RRC connection request message includes an identifier of the terminal device;
  • the processing module 2102 is further configured to: if it is determined according to the identifier of the terminal device, the receiving module 2101 has received the first paging message for the terminal device sent by the core network device before the RRC connection request message is received, and the sending module 2103 has not been according to the first The paging message pages the terminal device and discards the first paging message.
  • the other optional implementation manners of the sending module 2103 may refer to the sending operation of the access network device 302 in the foregoing Option 3, and other optional implementation manners of the processing module 2102 may refer to the foregoing Option 3,
  • other optional implementation manners of the receiving module 2101 may refer to the receiving operation of the access network device 302 in the foregoing Option 3.
  • the access network device determines whether to send the paging message in the air interface according to the received RRC connection request message and the paging message. Effectively avoid the UE shown in FIG. 6A eventually entering the idle state and cannot The case where the network performs data transmission.
  • An access network device provided by an embodiment includes: a receiver 2201, configured to receive a second paging message sent by the core network device for the terminal device;
  • the processor 2202 is configured to determine, according to the second paging message, whether a radio resource control RRC connection for the terminal device is established, or whether the RRC connection for the terminal device is in the establishing process;
  • the processor 2202 is further configured to: if it is determined that an RRC connection for the terminal device is established, or the RRC connection for the terminal device is in the process of establishing, discarding the second paging message;
  • the access network device further includes a transmitter 2203, configured to: according to the second paging message, when the processor 2202 determines that there is no established RRC connection for the terminal device, and there is no ongoing RRC connection establishment procedure for the terminal device Terminal Equipment.
  • the access network device can be implemented by the structure shown in FIG. 22A or FIG. 22B.
  • the transmitter 2203 and the receiver 2201 are connected to the processor 2202, respectively.
  • Fig. 22B shows a bus structure.
  • the bus structure may include any number of interconnected buses and bridges.
  • the processor 2202, the memory 2204, the transmitter 2203, and the receiver 2201 are connected to each other through a bus 2205.
  • the memory 2204 is used to store instructions, and the processor 2202 is configured to execute instructions stored in the memory 2204 to control the receiver 2201 to receive signals and control the transmitter 2203 to transmit signals.
  • transmitter 2203 For other optional implementations of the transmitter 2203, reference may be made to the sending module 2103. Other optional implementations of the processor 2202 may refer to the processing module 2102. Other optional implementation manners of the receiver 2201 may refer to the receiving module 2101.
  • the access network device determines whether to send the paging message in the air interface according to the received RRC connection request message and the paging message. The situation that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network is effectively avoided.
  • FIG. 23 is a schematic structural diagram of a core network device according to an embodiment of the present invention. As shown in FIG. 23, the core network device includes:
  • the receiving module 2301 is configured to receive a first initial user equipment UE message sent by the access network device, where The first initial UE message is triggered by the terminal device;
  • the processing module 2302 is configured to: when it is determined that the S1 connection between the core network device and the access network device is provided for the terminal device, release the S1 connection, and re-establish the S1 connection with the access device device for the terminal device.
  • the receiving module 2301 is further configured to: before receiving the first initial UE message sent by the access network device, receive a second initial UE message sent by the access network device, where the second initial UE message is triggered by the terminal device;
  • the processing module 2302 is further configured to: determine that the S1 connection is already established between the core network device and the access network device;
  • the core network device further includes a sending module 2303; the processing module 2302 is specifically configured to:
  • the user equipment UE context release command message is sent to the access network device by the sending module 2303, and is used to trigger the access network device to send an RRC connection release message to the terminal device.
  • the sending module 2303 refers to the foregoing fourth option, the sending operation of the core network device 303.
  • the processing module 2302 refer to the foregoing optional solution 4, the core network.
  • the processing operation of the device 303; the other optional implementation manners of the receiving module 2301 can refer to the receiving operation of the core network device 303 in the foregoing Option 1.
  • the core network device releases the previously established S1 connection for the terminal device after requesting the initial UE message again and requests to establish for the terminal device.
  • the new S1 connection ensures that the terminal device re-enters the connected state and the network for data transmission.
  • the receiver 2401 is configured to receive a first initial user equipment UE message sent by the access network device, where the first initial UE message is triggered by the terminal device;
  • the processor 2402 is configured to: when it is determined that the S1 connection between the core network device and the access network device is provided for the terminal device, release the S1 connection, and re-establish the S1 connection with the access device device for the terminal device.
  • the receiver 2401 is further configured to: before receiving the first initial UE message sent by the access network device, receive a second initial UE message sent by the access network device, where the second initial UE message is sent by the terminal Device triggering;
  • the processor 2402 is further configured to: determine that the S1 connection is already established between the core network device and the access network device;
  • the core network device further includes a transmitter 2403; the processor 2402 is specifically configured to:
  • the user equipment UE context release command message is sent to the access network device by the sender 2403, and is used to trigger the access network device to send an RRC connection release message to the terminal device.
  • the core network device may be implemented by the structure shown in FIG. 24A or FIG. 24B.
  • a receiver 2401 and a transmitter 2403 are connected to a processor 2402, respectively.
  • Fig. 24B shows a bus structure.
  • the bus structure may include any number of interconnected buses and bridges.
  • the processor 2402, the memory 2404, the transmitter 2403, and the receiver 2401 are connected to each other through a bus 2405.
  • the memory 2404 is used to store instructions, and the processor 2402 is configured to execute instructions stored in the memory 2404 to control the receiver 2401 to receive signals and control the transmitter 2403 to transmit signals.
  • transmitter 2403 For other optional implementations of the transmitter 2403, reference may be made to the sending module 2303. Other optional implementations of the processor 2402 may refer to the processing module 2302. Other optional implementation manners of the receiver 2401 may refer to the receiving module 2301.
  • the core network device releases the previously established S1 connection for the terminal device after requesting the initial UE message again and requests to establish for the terminal device.
  • the new S1 connection ensures that the terminal device re-enters the connected state and the network for data transmission.
  • FIG. 25 is a flow chart of a paging method provided by an embodiment. As shown in FIG. 25, the method includes:
  • the terminal device initiates a first radio resource control RRC connection establishment process to the access network device.
  • S2502 The terminal device starts a timer in the first RRC connection establishment process
  • the terminal device receives a paging message sent by the access network device, where the paging message includes an identifier of the terminal device.
  • the timer is used to identify a scenario in which the RRC connection establishment procedure initiated by the terminal device and the paging process are concurrent.
  • starting the timer in the first RRC connection setup process initiated by the terminal device includes:
  • the terminal device starts a timer when transmitting an RRC connection request message to the access network device.
  • the terminal device starts a timer when receiving an RRC connection setup message sent by the access network device.
  • the duration of the timer is pre-defined by the protocol, or determined by the paging cycle, or determined by the access network device and notified to the terminal device.
  • the scenario of the RRC connection establishment process initiated by the terminal device and the paging process initiated by the network is identified by setting a timer, thereby avoiding the problem that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network.
  • FIG. 26 is a flow chart of a paging method provided by an embodiment. As shown in Figure 26, the method includes:
  • the access network device determines a duration of the timer.
  • S2602 The access network device notifies the duration of the terminal device timer, so that the terminal device:
  • the timer is started during the first establishment of the RRC connection initiated by the access network device, and when the paging message sent by the access network device is received, and the paging message includes the identifier of the terminal device:
  • the second RRC connection establishment process is initiated according to the paging message
  • the paging message is ignored to maintain the RRC connection established by the first RRC connection setup procedure.
  • the timer is used to identify a scenario in which the RRC connection establishment procedure initiated by the terminal device and the paging process are concurrent.
  • the access network device determines the duration of the timer, including:
  • the access network device determines the duration of the timer according to the paging cycle.
  • the scenario of the RRC connection establishment process initiated by the terminal device and the paging process initiated by the network is identified by setting a timer, thereby avoiding the problem that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network.
  • Figure 27 is a flow chart of a paging method provided by an embodiment. As shown in FIG. 27, the method includes:
  • the access network device receives a radio resource control RRC connection request message sent by the terminal device, where the RRC connection request message includes an identifier of the terminal device.
  • it also includes:
  • the access network device When the access network device receives the second paging message for the terminal device sent by the core network device, the access network device discards the second homing message during the RRC connection setup process triggered by the RRC connection request message or after the RRC setup process is completed. Call the message.
  • the access network device determines whether to send the paging message in the air interface according to the received RRC connection request message and the paging message. The situation that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network is effectively avoided.
  • FIG. 28 is a flow chart of a paging method provided by an embodiment. As shown in FIG. 28, the method includes:
  • the access network device receives a second paging message sent by the core network device for the terminal device.
  • the access network device determines, according to the second paging message, whether a radio resource control RRC connection for the terminal device is established, or whether the RRC connection for the terminal device is in the establishing process;
  • S2803 If the access network device determines that an RRC connection for the terminal device has been established, or for The RRC connection of the terminal device is in the process of establishing, and the access network device discards the second paging message; if the access network device determines that there is no established RRC connection for the terminal device, there is no ongoing RRC connection establishment for the terminal device. In the process, the access network device pages the terminal device according to the second paging message.
  • the access network device determines that the RRC connection for the terminal device is established, or the RRC connection for the terminal device is in the process of establishing, the access network device receives the second homing for the terminal device sent by the core network device. Before the message is sent, the method further includes: the access network device receives an RRC connection request message that is sent by the terminal device and is used to establish an RRC connection, where the RRC connection request message includes an identifier of the terminal device;
  • the method further includes: if the access network device determines, according to the identifier of the terminal device, that the first paging message for the terminal device sent by the core network device has been received before the RRC connection request message is received, and the information is not found according to the first paging message.
  • the calling terminal device discards the first paging message.
  • the access network device determines whether to send the paging message in the air interface according to the received RRC connection request message and the paging message. The situation that the UE shown in FIG. 6A finally enters an idle state and cannot perform data transmission with the network is effectively avoided.
  • 29 is a flow chart of a paging method provided by an embodiment. As shown in FIG. 29, the method includes:
  • the core network device receives the first initial user equipment UE message sent by the access network device, where the first initial UE message is triggered by the terminal device.
  • the core network device releases the S1 connection when the core network device determines that the S1 connection to the terminal device is already provided between the access network device and the access network device;
  • S2903 The core network device re-establishes an S1 connection with the access device between the access network devices.
  • the method before the receiving, by the core network device, the first initial UE message sent by the access network device, the method further includes:
  • the core network device receives the second initial UE message sent by the access network device, and the second initial UE message Triggered by the terminal device;
  • the core network device determines that an S1 connection is already established between the access network device and the access network device;
  • the core network device releases the S1 connection, including:
  • the core network device sends a user equipment UE context release command message to the access network device, and is used to trigger the access network device to send an RRC connection release message to the terminal device.
  • the core network device releases the previously established S1 connection for the terminal device after requesting the initial UE message again and requests to establish for the terminal device.
  • the new S1 connection ensures that the terminal device re-enters the connected state and the network for data transmission.
  • the terminal device when the terminal device receives the paging message for paging the terminal device, if the paging message carries the identifier of the terminal device, if it determines that it is in the connected state, it initiates in response to the received paging message. RRC connection establishment process. Therefore, the problem that the terminal device such as the UE determines that it is in the connected state, and the UE considers that the UE is in the idle state, the UE ignores the paging message sent by the network and causes serious loss of words.
  • the timer is ignored before the timer is in the timeout state.
  • the paging message is sent to the terminal device to initiate an RRC connection establishment process after the timer is in the timeout state; or the access network device distinguishes the received RRC connection request from the paging message to determine whether to send the paging message to the terminal device.
  • the previously established S1 connection is released and the new S1 connection is re-established to prevent the terminal device from finally entering the idle state and unable to transmit data with the network.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

本发明涉及无线通信技术领域，尤其涉及寻呼设备和方法，针对连接态的终端设备提供寻呼方案，保证网络有效寻呼终端设备。在一种终端设备中，发送模块发起第一次无线资源控制RRC连接建立过程；处理模块在第一次RRC连接建立过程中启动定时器；接收模块接收寻呼消息，消息包括终端设备的标识；发送模块还用于当定时器处于超时状态，根据寻呼消息发起第二次RRC连接建立过程；处理模块还用于当定时器处于未超时状态，忽略寻呼消息以维持第一次RRC连接建立过程建立的RRC连接。通过终端设备启动定时器，在定时器超时前忽略寻呼消息，在定时器超时后响应寻呼消息发起RRC连接建立过程，可避免终端设备进入空闲态而无法进行数据传输。

Description

一种寻呼设备和方法 技术领域
本发明涉及无线通信技术领域，尤其涉及一种寻呼设备和方法。
背景技术
长期演进(Long Term Evolution，LTE)***中，用户设备(User Equipment，UE)在空口有两种无线资源控制(Radio Resource Control，RRC)状态：空闲态(IDLE)和连接态(Connected)。处于连接态的UE能与网络进行数据传输，而处于空闲态的UE需在与网络建立起连接进入连接态后才能进行数据传输。当处于空闲态的UE有下行数据到达时，服务网关(Serving-GateWay，S-GW)能缓存该下行数据并通知移动管理实体(Mobility Management Entity，MME)来触发寻呼消息，UE接收到寻呼消息后会在当前驻留的小区上发起RRC连接建立过程以进入连接态。
处于空闲态的UE可采用非连续接收(Discontinuous Reception，DRX)方式接收寻呼消息以达到省电的目的。演进型基站，比如：演进节点B(evolved NodeB，eNB)配置用来寻呼的无线帧，即寻呼帧(Paging Frame，PF)，以及PF内用来寻呼的子帧，即寻呼时机(Paging Opportunity，PO)。在配置的寻呼帧内的寻呼时机处，演进型基站发送寻呼消息以寻呼该处于空闲态的UE，每个小区在***消息中广播寻呼周期等寻呼参数。处于空闲态的UE根据接收的寻呼参数计算得出自身接收寻呼消息的寻呼帧和寻呼帧内的寻呼时机，在一个DRX周期内UE可以只在自身的寻呼时机处进行寻呼接收，而在其他时间进入睡眠，这样可达到省电的目的。
现有协议针对连接态的UE，并没有可行方案保证网络有效寻呼该UE。
发明内容
有鉴于此，提供一种寻呼设备和方法，用以提针对连接态的UE，提供一 种寻呼方案，可保证网络有效寻呼UE。
第一方面，本发明实施例提供一种终端设备，包括：
发送模块，用于向接入网设备发起第一次无线资源控制RRC连接建立过程；
处理模块，用于在所述第一次RRC连接建立过程中启动定时器；
接收模块，用于接收所述接入网设备发送的寻呼消息，所述寻呼消息包括所述终端设备的标识；
所述发送模块还用于：当所述定时器处于超时状态，根据所述寻呼消息发起第二次RRC连接建立过程；
所述处理模块还用于：当所述定时器处于未超时状态，忽略所述寻呼消息以维持所述第一次RRC连接建立过程建立的RRC连接。
结合第一方面，在第一种可能的实现方式中，
所述定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
结合第一方面或第一方面的第一种可能的实现方式，在第二种可能的实现方式中，所述处理模块具体用于：
在所述发送模块向所述接入网设备发送RRC连接请求消息时启动所述定时器；或
在所述接收模块接收所述接入网设备发送的RRC连接建立消息时启动所述定时器。
结合第一方面，或第一方面的第一种或第二种可能的实现方式，在第三种可能的实现方式中，所述定时器的时长是协议预先规定的，或由寻呼周期确定的，或由所述接入网设备确定并通知所述终端设备的。
第二方面，本发明实施例提供一种接入网设备，包括：
处理模块，用于确定定时器的时长；
发送模块，用于通知终端设备所述定时器的时长，以使所述终端设备：
在向所述接入网设备发起的第一次建立无线资源控制RRC连接的过程中 启动所述定时器，并在收到所述接入网设备发送的寻呼消息，且所述寻呼消息包括所述终端设备的标识时：
当所述定时器处于超时状态，根据所述寻呼消息发起第二次RRC连接建立过程；
当所述定时器处于未超时状态，忽略所述寻呼消息以维持所述第一次RRC连接建立过程建立的RRC连接。
结合第二方面，在第一种可能的实现方式中，
所述定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
结合第二方面，或第二方面的第一种可能的实现方式，在第二种可能的实现方式中，所述处理模块具体用于：
根据寻呼周期确定所述定时器的时长。
第三方面，本发明实施例提供一种接入网设备，包括：
接收模块，用于接收终端设备发送的无线资源控制RRC连接请求消息，所述RRC连接请求消息包括所述终端设备的标识；
处理模块，用于根据所述终端设备的标识确定所述接收模块已收到所述核心网设备发送的针对所述终端设备的第一寻呼消息且尚未根据所述第一寻呼消息寻呼所述终端设备，则丢弃所述第一寻呼消息。
结合第三方面，在第一种可能的实现方式中，所述处理模块还用于：
当在所述RRC连接请求消息触发的RRC连接建立过程中或所述RRC建立过程完成后，所述接收模块收到所述核心网设备发送的针对所述终端设备的第二寻呼消息，则丢弃所述第二寻呼消息。
第四方面，本发明实施例提供一种接入网设备，包括：
接收模块，用于接收核心网设备发送的针对终端设备的第二寻呼消息；
处理模块，用于根据所述第二寻呼消息判断是否已建立了针对所述终端设备的无线资源控制RRC连接，或针对所述终端设备的RRC连接是否处于建立过程中；
所述处理模块还用于：若确定已建立了针对所述终端设备的RRC连接，或针对所述终端设备的RRC连接处于建立过程中，丢弃所述第二寻呼消息；
所述接入网设备还包括发送模块，用于在所述处理模块确定没有已建立的针对所述终端设备的RRC连接，也没有针对所述终端设备的正在进行的RRC连接建立过程时，根据所述第二寻呼消息寻呼所述终端设备。
结合第四方面，在第一种可能的实现方式中，
若所述处理模块确定已建立了针对所述终端设备的RRC连接，或针对所述终端设备的RRC连接处于建立过程中，所述接收模块还用于：在接收所述核心网设备发送的针对终端设备的所述第二寻呼消息之前，接收所述终端设备发送的用于建立所述RRC连接的RRC连接请求消息，所述RRC连接请求消息包括所述终端设备的标识；
所述处理模块还用于：若根据所述终端设备的标识确定所述接收模块在收到所述RRC连接请求消息之前已收到所述核心网设备发送的针对所述终端设备的第一寻呼消息且所述发送模块尚未根据所述第一寻呼消息寻呼所述终端设备，丢弃所述第一寻呼消息。
第五方面，本发明实施例提供一种核心网设备，包括：
接收模块，用于接收接入网设备发送的第一初始用户设备UE消息，所述第一初始UE消息由终端设备触发；
处理模块，用于当确定所述核心网设备与所述接入网设备间已具备针对所述终端设备的S1连接时，释放所述S1连接，并重新建立与所述接入网设备间的针对所述终端设备的S1连接。
结合第五方面，在第一种可能的实现方式中，所述接收模块还用于：在接收接入网设备发送的第一初始UE消息之前，接收所述接入网设备发送的第二初始UE消息，所述第二初始UE消息由所述终端设备触发；
所述处理模块还用于：确定所述核心网设备与所述接入网设备间已具备所述S1连接；
所述核心网设备还包括发送模块；
所述处理模块具体用于：
通过所述发送模块向所述接入网设备发送用户设备UE上下文释放命令消息，用于触发所述接入网设备向所述终端设备发送RRC连接释放消息。
第六方面，本发明实施例提供一种寻呼方法，包括：
终端设备向接入网设备发起第一次无线资源控制RRC连接建立过程；
所述终端设备在所述第一次RRC连接建立过程中启动定时器；
所述终端设备接收所述接入网设备发送的寻呼消息，所述寻呼消息包括所述终端设备的标识；
当所述定时器处于超时状态，所述终端设备根据所述寻呼消息发起第二次RRC连接建立过程；
当所述定时器处于未超时状态，所述终端设备忽略所述寻呼消息以维持所述第一次RRC连接建立过程建立的RRC连接。
结合第六方面，在第一种可能的实现方式中，
所述定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
结合第六方面，或第六方面的第一种可能的实现方式，在第二种可能的实现方式中，所述终端设备在发起的第一次RRC连接建立过程中启动定时器包括：
所述终端设备在向所述接入网设备发送RRC连接请求消息时启动所述定时器；或
所述终端设备在接收所述接入网设备发送的RRC连接建立消息时启动所述定时器。
结合第六方面，或第六方面的第一种或第二种可能的实现方式，在第三种可能的实现方式中，所述定时器的时长是协议预先规定的，或由寻呼周期确定的，或由所述接入网设备确定并通知所述终端设备的。
第七方面，本发明实施例提供一种寻呼方法，包括：
接入网设备确定定时器的时长；
所述接入网设备通知终端设备所述定时器的时长，以使所述终端设备：
在向所述接入网设备发起的第一次建立无线资源控制RRC连接的过程中启动所述定时器，并在收到所述接入网设备发送的寻呼消息，且所述寻呼消息包括所述终端设备的标识时：
当所述定时器处于超时状态，根据所述寻呼消息发起第二次RRC连接建立过程；
当所述定时器处于未超时状态，忽略所述寻呼消息以维持所述第一次RRC连接建立过程建立的RRC连接。
结合第七方面，在第一种可能的实现方式中，所述定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
结合第七方面，或第七方面的第一种可能的实现方式，在第二种可能的实现方式中，所述接入网设备确定定时器的时长，包括：
所述接入网设备根据寻呼周期确定所述定时器的时长。
第八方面，本发明实施例提供一种寻呼方法，包括：
接入网设备接收终端设备发送的无线资源控制RRC连接请求消息，所述RRC连接请求消息包括所述终端设备的标识；
当所述接入网设备根据所述终端设备的标识确定已收到所述核心网设备发送的针对所述终端设备的第一寻呼消息且尚未根据所述第一寻呼消息寻呼所述终端设备，则所述接入网设备丢弃所述第一寻呼消息。
结合第八方面，在第一种可能的实现方式中，还包括：
当在所述RRC连接请求消息触发的RRC连接建立过程中或所述RRC建立过程完成后，所述接入网设备收到所述核心网设备发送的针对所述终端设备的第二寻呼消息，则所述接入网设备丢弃所述第二寻呼消息。
第九方面，本发明实施例提供一种寻呼方法，包括：
接入网设备接收核心网设备发送的针对终端设备的第二寻呼消息；
所述接入网设备根据所述第二寻呼消息判断是否已建立了针对所述终端设备的无线资源控制RRC连接，或针对所述终端设备的RRC连接是否处于 建立过程中；
若所述接入网设备确定已建立了针对所述终端设备的RRC连接，或针对所述终端设备的RRC连接处于建立过程中，所述接入网设备丢弃所述第二寻呼消息；
若所述接入网设备确定没有已建立的针对所述终端设备的RRC连接，也没有针对所述终端设备的正在进行的RRC连接建立过程，所述接入网设备根据所述第二寻呼消息寻呼所述终端设备。
结合第九方面，在第一种可能的实现方式中，
若所述接入网设备确定已建立了针对所述终端设备的RRC连接，或针对所述终端设备的RRC连接处于建立过程中，在所述接入网设备接收所述核心网设备发送的针对终端设备的所述第二寻呼消息之前，还包括：所述接入网设备接收所述终端设备发送的用于建立所述RRC连接的RRC连接请求消息，所述RRC连接请求消息包括所述终端设备的标识；
所述方法还包括：若所述接入网设备根据所述终端设备的标识确定在收到所述RRC连接请求消息之前已收到所述核心网设备发送的针对所述终端设备的第一寻呼消息且尚未根据所述第一寻呼消息寻呼所述终端设备，所述接入网设备丢弃所述第一寻呼消息。
第十方面，本发明实施例提供一种寻呼方法，包括：
核心网设备接收接入网设备发送的第一初始用户设备UE消息，所述第一初始UE消息由终端设备触发；
当所述核心网设备确定与所述接入网设备间已具备针对所述终端设备的S1连接时，所述核心网设备释放所述S1连接；
所述核心网设备重新建立与所述接入网设备间的针对所述终端设备的S1连接。
结合第十方面，在第一种可能的实现方式中，在所述核心网设备接收接入网设备发送的第一初始UE消息之前，还包括：
所述核心网设备接收所述接入网设备发送的第二初始UE消息，所述第二 初始UE消息由所述终端设备触发；
所述核心网设备确定与所述接入网设备间已具备所述S1连接；
所述核心网设备释放所述S1连接，包括：
所述核心网设备向所述接入网设备发送用户设备UE上下文释放命令消息，用于触发所述接入网设备向所述终端设备发送RRC连接释放消息。
综上，终端设备在收到用于寻呼该终端设备的寻呼消息时，若寻呼消息中携带该终端设备的标识，若确定自身处于连接态，则响应于接收的该寻呼消息发起RRC连接建立过程。从而解决了上述诸如UE的终端设备确定自身处于连接态，而网络认为UE处于空闲态的情况下，UE忽略网络下发的寻呼消息而造成的严重丢话的问题。
进一步地，为了避免UE响应于寻呼消息发起RRC连接建立过程可能造成的UE最终进入空闲态而无法与网络进行数据传输的情形，通过在终端设备启动定时器，在定时器处于超时状态前忽略寻呼消息，在定时器处于超时状态后响应寻呼消息发起RRC连接建立过程；或者通过接入网设备区分接收的RRC连接请求和寻呼消息的先后关系，确定是否向终端设备发送寻呼消息；再或者通过核心网设备在出现并发情形后，释放先前建立的S1连接，重新建立新的S1连接，避免终端设备最终进入空闲态而无法与网络进行数据传输。
附图说明
图1为目前UE响应寻呼消息而建立RRC连接的信令流程的示意图；
图2为目前UE忽略网络下发的寻呼的过程示意图；
图3为一个实施例提供的无线通信***的结构示意图；
图4为图3所示的无线通信***中终端设备响应寻呼消息发起RRC连接建立过程的流程图；
图5为图3所示的无线通信***为LTE***时的结构示意图；
图6A和图6B为RRC连接建立过程和寻呼过程并发情形的示意图；
图7为避免并发情形的可选方案一的流程图；
图8为可选方案一的一种可能实现方式的流程图；
图9为避免并发情形的可选方案二的流程图；
图10为可选方案二的一种可能实现方式的流程图
图11为避免并发情形的可选方案三的流程图；
图12为可选方案三的一种可能实现方式的流程图
图13为避免并发情形的可选方案四的流程图；
图14为可选方案四的一种可能实现方式的流程图；
图15为一个实施例提供的终端设备的结构示意图；
图16A和图16B分别为一个实施例提供的终端设备的两种实现方式下的结构示意图；
图17为一个实施例提供的接入网设备的结构示意图；
图18A和图18B分别为一个实施例提供的接入网设备的两种实现方式下的结构示意图；
图19为一个实施例提供的接入网设备的结构示意图；
图20A和图20B分别为一个实施例提供的接入网设备的两种实现方式下的结构示意图；
图21为一个实施例提供的接入网设备的结构示意图；
图22A和图22B分别为一个实施例提供的接入网设备的两种实现方式下的结构示意图；
图23为一个实施例提供的核心网设备的结构示意图；
图24A和图24B分别为一个实施例提供的核心网设备的两种实现方式下的结构示意图；
图25为一个实施例提供的寻呼方法的流程图；
图26为一个实施例提供的寻呼方法的流程图；
图27为一个实施例提供的寻呼方法的流程图；
图28为一个实施例提供的寻呼方法的流程图；
图29为一个实施例提供的寻呼方法的流程图。
具体实施方式
正常情况下，处于空闲态的UE接收到寻呼消息后将发起RRC连接建立过程以响应寻呼消息，UE进入连接态后即可与网络进行数据传输；而处于连接态的UE如果收到寻呼消息，则会忽略该寻呼消息，不会发起RRC连接建立过程。但是，上述UE处理寻呼消息可能引发丢话，详述如下：
一种UE针对基站发送的寻呼消息的处理过程如图1所示：
MME通过基站向UE发送寻呼消息(Paging)，UE收到该寻呼消息后，向基站发送RRC连接请求(RRC Connection Request)消息，请求建立RRC连接，基站收到该RRC连接请求消息后，向UE发送RRC连接建立(RRC Connection Setup)消息，通知UE建立的RRC连接的相关参数，UE按照RRC连接建立消息中的建立RRC连接的相关参数进行配置，配置完成后向基站发送RRC连接建立完成(RRC Conneciton Setup Complete)消息，完成RRC连接的建立。
基站收到该RRC连接建立完成消息后，向MME发送初始UE消息(Initial UE Message)，MME收到该初始UE消息后，向基站发送初始上下文建立请求(Initial Context Setup Request)消息，请求建立该UE的上下文。基站收到该初始上下文建立请求消息后，可向UE发送RRC安全模式命令(RRC Security Mode Command)消息，携带加密和完整性保护的相关参数，UE获取加密和完整性保护的相关参数后，回复RRC安全模式完成(RRC Security Mode Complete)。
接下来，基站可向UE发送RRC连接重配置(RRC Connection Reconfiguration)，UE回复RRC连接重配置完成(RRC Connection Reconfiguration)，从而完成RRC连接的重配置过程。RRC连接重配置完成后，基站向MME回复初始上下文建立完成(Initial Context Setup Complete)消息，完成该UE的上下文的建立。
此时，UE在收到基站发送的RRC Connection Setup消息后进入连接态， 处于连接态的UE如果收到寻呼消息，则会忽略该消息而不会进行相应的处理。
另一种UE针对基站发送的寻呼消息的处理过程如图2所示：
处于连接态的UE如果长时间没有数据传输，基站侧的不活动定时器(Inactivity Timer)超时，则基站给UE发送RRC连接释放(RRC Connection Release)消息以使UE释放RRC连接而进入空闲态。但可能由于信号质量差，UE一直接收不到基站发送的RRC连接释放消息，这就导致网络认为UE进入空闲态，但UE侧仍处于连接态。当UE有下行数据到达时，认为UE处于空闲态的网络触发寻呼，基站在空口给UE发送寻呼消息后，按现有协议的规定，UE会忽略该寻呼而不会发起连接建立过程，最终导致网络侧寻呼不到该UE，造成丢话。
本发明提供一种寻呼设备和方法，用以实现UE正确处理基站发送的寻呼消息，以确保与网络正常通信。
下面，结合附图进行详细说明。
图3为一个实施例提供的无线通信***的结构示意图。如图3所示，该无线通信***包括：终端设备301、接入网设备302和核心网设备303，其中终端设备301可通过无线连接与接入网设备302连接，接入网设备302可通过有线或无线连接与核心网设备303连接。
目前，以LTE***为例，基站可在以下多种情况下，向UE发送寻呼消息：
1、收到MME发送的寻呼UE的寻呼消息后，在空口上向处于空闲态的UE发送寻呼消息，寻呼消息中携带该UE的标识信息，比如：***框架演进(System Architecture Evolution，SAE临时移动站标识(SAE Temporary Mobile Station Identifier，S-TMSI)或国际移动用户识别码(International Mobile Subscriber Identification Number，IMSI)；
2、通知处于空闲态或连接态的UE***信息改变。
在情况1下，寻呼消息中会携带该UE的标识信息。因此，UE在空口上 收到寻呼消息后，若确定寻呼消息中携带自身的标识信息，则可确定该寻呼消息是发给自身的用于寻呼处于空闲态UE的寻呼消息。
但是，如前所述，若UE在之前没有收到RRC连接释放消息，则UE会认为自身仍处于连接态，按照目前LTE***中的处理，UE会丢弃该寻呼消息。
图3所示的无线通信***中，终端设备301在收到该用于寻呼终端设备301的寻呼消息，且该寻呼消息携带终端设备301的标识时，即使自身确定处于连接态，也会响应该寻呼消息发起RRC连接建立过程。
图3所示的无线通信***的通信制式包括但不限于：全球移动通信***(Global System of Mobile communication，GSM)、码分多址(Code Division Multiple Access，CDMA)IS-95、码分多址(Code Division Multiple Access，CDMA)2000、时分同步码分多址(Time Division-Synchronous Code Division Multiple Access，TD-SCDMA)、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)、时分双工-长期演进(Time Division Duplexing-Long Term Evolution，TDD LTE)、频分双工-长期演进(Frequency Division Duplexing-Long Term Evolution，FDD LTE)、长期演进-增强(Long Term Evolution-Advanced，LTE-advanced)、个人手持电话***(Personal Handy-phone System，PHS)、802.11系列协议规定的无线保真(Wireless Fidelity，WiFi)、全球微波互联接入(Worldwide Interoperability for Microwave Access，WiMAX)，以及未来演进的各种无线通信***。
只要存在终端设备和网络状态不一致，终端设备确定自身处于连接态，而网络确定终端设备处于空闲态，而导致终端设备忽略用于寻呼处于空闲态的终端设备的寻呼消息，均可以可使用图3所示的无线通信***以避免丢话。
其中，这里网络可指接入网设备302，也可指接入网设备302和核心网设备303，或者也可包括接入网设备302和核心网设备303以及其他设备在内的网络设备。
其中，终端设备301可以是无线终端，无线终端可以是指向用户提供语音和/或数据连通性的设备，具有无线连接功能的手持式设备、或连接到无线 调制解调器的其他处理设备。无线终端可以经无线接入网(例如，RAN，Radio Access Network)与一个或多个核心网进行通信，无线终端可以是移动终端，如移动电话(或称为“蜂窝”电话)和具有移动终端的计算机，例如，可以是便携式、袖珍式、手持式、计算机内置的或者车载的移动装置，它们与无线接入网交换语言和/或数据。例如，个人通信业务(PCS，Personal Communication Service)电话、无绳电话、会话发起协议(SIP)话机、无线本地环路(WLL，Wireless Local Loop)站、个人数字助理(PDA，Personal Digital Assistant)等设备。无线终端也可以称为订户单元(Subscriber Unit)、订户站(Subscriber Station)，移动站(Mobile Station)、移动台(Mobile)、远程站(Remote Station)、接入点(Access Point)、远程终端(Remote Terminal)、接入终端(Access Terminal)、用户终端(User Terminal)、用户代理(User Agent)、用户设备(User Device)、或用户装备(User Equipment)。
接入网设备302可包括基站，或用于控制基站的无线资源管理设备，或包括基站和用于控制基站的无线资源管理设备；其中基站可为宏站或小站，比如：小小区(small cell)、微小区(pico cell)等，基站也可为家庭基站，比如：家庭节点B(Home NodeB，HNB)、家庭演进节点B(Home eNodeB，HeNB)等，基站也可包括中继节点(relay)等。
核心网设备303可包括用于进行移动性管理的核心网设备，比如：移动交换中心(Mobile Switching Center，MSC)，或者移动管理实体(Mobility Management Entity，MME)等。
比如：对于TDD LTE、FDD LTE或LTE-A等LTE***接入网设备302可为演进节点B(evolved NodeB，eNodeB)，终端设备301可为UE，核心网设备303可为MME；对于TD-SCDMA***或WCDMA***，接入网设备302可包括：节点B(NodeB)和/或无线网络控制器(Radio Network Controller，RNC),终端设备301可为UE，核心网设备303可为MSC；对于GSM***，接入网设备302可包括基站收发台(Base Transceiver Station，BTS)和/或基站控制器(Base Station Controller，BSC)，终端102可为移动台(Mobile Station， MS)，核心网设备303可为MSC。
比如：对于LTE***，图3所示的无线通信***的网络架构可如图5所示。其中，终端设备301为UE，接入网设备302为基站，核心网设备303为MME，UE和基站之间的接口为Uu口，也称为“空口”、“空中接口”、“无线接口”等，基站和MME之间的接口为S1-MME口，基站和服务网关(Serving-GateWay，S-GW)之间的接口为S1-U口，MME和S-GW之间的接口为S11口。
采用图4所示的流程，可能导致终端设备301进入空闲态，无法与网络建立连接的问题。下面参考图6A，以LTE***为例加以说明。
图6A中，虚线代表寻呼接入流程，实线代表终端设备301主动接入流程。接入网设备302(基站)收到核心网设备303(MME)发送的寻呼消息后不会立即在空口寻呼对应的终端设备301(UE)，而是等到该UE的寻呼时机到来时将寻呼消息发送给UE，所以基站可能在UE主动发起的RRC连接建立过程中，如收到RRC Connection Setup Complete消息之后、发送RRC Security Mode Command消息之前发送寻呼消息给UE，UE为响应收到的寻呼消息再次发起RRC连接建立过程，基站在S1-MME口再次给MME发送Initial UE Message消息，MME根据Initial UE Message消息中携带的UE标识S-TMSI识别出两次接收到的Initial UE message消息是同一个UE触发的，因此MME认为有误，进而向基站发送UE上下文释放命令，要求释放先前建立的UE上下文，基站收到该命令后，确定上下文建立失败，向MME返回初始上下文建立失败(Initial Context Setup Fail)消息，并给UE发送RRC连接释放消息(对应图6A中实线的RRC Connection Release消息)，而MME并没有因为再次收到Initial UE Message消息(图6A中虚线的Initial UE Message消息)而请求建立新的S1连接，因此，对应于基站发送的图6A中的第二条Initial UE Message消息(图6A中虚线的Initial UE Message消息)，基站等待预设的时长，但在该预设的时长结束前没有接收到MME的响应消息，则再次向UE发送RRC连接释放消息。
从图6A中可以看出，如果基站在UE发起的RRC连接建立过程中，或RRC连接建立完成后向UE发送寻呼消息，可能导致图6A所示的UE最终进入空闲态而无法与网络进行数据传输，因此，进一步地，可通过包括可选方案一～可选方案四在内的多种方案，避免连接态的UE响应寻呼消息时产生并发的情况。
为避免上述情况的发生，可选方案一中，终端设备301处启动一个定时器，若终端设备301在定时器处于超时状态前收到寻呼消息则忽略该寻呼，若终端设备301在定时器处于超时状态后收到寻呼消息则再次发起RRC连接建立过程；
可选方案二和可选方案三中，接入网设备302根据先后接收到的两条消息——寻呼消息和RRC连接请求消息中携带的相关信息来进行相应的判断从而决定是否在空口发送寻呼消息；
可选方案四中，核心网设备303针对发生的图6A所示的情况进行对应的处理：MME再次收到Initial UE Message消息后释放先前建立的在核心网设备303与接入网设备302之间的接口上的针对终端设备301的S1连接并在核心网设备303与接入网设备302之间的接口上重新建立针对终端设备301的S1连接。
下面对该四种可选方案进行详细描述。
【可选方案一】
图7为可选方案一的流程图。如图7所示，该流程包括如下步骤：
S701：终端设备301向接入网设备302发起第一次RRC连接建立过程，比如通过发送RRC连接请求消息发起该第一次RRC连接建立过程；
S702：终端设备301在发起的第一次RRC连接建立过程中，或RRC连接建立完成后启动定时器；
S703：终端设备301接收接入网设备302发送的寻呼消息，该寻呼消息中携带终端设备301的标识；
如果在收到寻呼消息时定时器处于超时状态，则终端设备301执行步骤 S704：响应于接收的寻呼消息发起第二次RRC连接建立过程；如果定时器处于未超时状态，则终端设备301忽略寻呼消息。
终端设备301忽略该寻呼消息，可以维持上述第一次RRC连接过程建立的RRC连接。
可选方案一中，终端设备301可以在第一次RRC连接建立过程中，或在RRC连接建立完成后，启动一个定时器，从而终端设备301根据接收到的寻呼消息是在定时器处于超时状态前还是定时器处于超时状态后来决定是否处理该寻呼消息。
其中，终端设备301启动的该定时器可排除前述的图6A所示的情况。如果终端设备301在定时器处于超时状态前收到寻呼消息，终端设备301会忽略该寻呼消息而不会进行相应处理，如果终端设备301在定时器处于超时状态后收到寻呼消息，则终端设备301会发起第二次RRC连接建立过程以响应寻呼。
可选地，终端设备301可在发送RRC连接请求时启动定时器，或者终端设备301在收到RRC连接建立消息时启动定时器，再或者，终端设备301在发送RRC连接建立完成消息时启动定时器。
比如：按照目前LTE***相关协议的规定，终端设备301在收到RRC连接建立消息后进入连接态，因此可优先考虑在终端设备301收到RRC连接建立消息时启动定时器。
该定时器的时长可为1s、2s、2.5s、3s、……、10s、10.5s等等。可选地，该定时器的时长可设置的最小值为寻呼周期。
该定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景，比如：图6A所示的并发的场景，在该场景下，终端设备主动发起的RRC连接建立过程与MME发送寻呼消息在相近的时间内发生。如图6B所示，接入网设备302在寻呼终端设备301的寻呼时机开始到接入网设备302向核心网设备303发送初始UE消息结束这段时间内，若核心网设备303向接入网设备302发送寻呼终端设备301的寻呼消息，将导致上述并发的场景。
该定时器的时长的设置可考虑如下因素：若定时器的时长过短则无法避免上述图6A所示情形的发生，若定时器的时长过长则终端设备301可能错过寻呼消息的接收时机而再次丢话，因此在设置定时器的时长时，可考虑使终端设备301再次发起RRC连接建立过程后能重新进入连接态与网络进行数据传输。比如：
1、在协议中规定定时器的时长，如10s；
2、根据一定的公式计算定时器的时长，比如：接入网设备302在***消息中广播终端设备301的寻呼周期，终端设备301可根据寻呼周期决定定时器的时长，如定时器的时长可设置为：2倍的寻呼周期，该2倍仅为示例，不排除其他根据寻呼周期确定定时器的时长的方式；
3、由接入网设备302确定并通知终端设备301。比如：终端设备301在收到RRC连接建立消息时启动定时器，则接入网设备302可在向终端设备301发送的RRC连接建立消息中，携带用于指示定时器的时长的信息，终端设备301收到RRC连接建立消息后，从该消息中获取该用于指示定时器的时长的信息，并根据该信息确定定时器的时长，比如：接入网设备302可确定该定时器的时长为10s。
可选地，接入网设备302可根据寻呼周期确定定时器的时长。
图8中以终端设备301收到RRC连接建立消息时启动定时器为例，示出了可选方案一的一种可实现的流程。
图8中，终端设备301通过发送RRC连接请求消息发起RRC连接建立过程，终端设备301在RRC连接建立过程中，在收到接入网设备302发送的RRC连接建立消息时，启动定时器。终端设备301接收接入网设备302发送的寻呼消息，若在收到该寻呼消息时，启动的定时器未超时，则忽略该寻呼消息；若收到该寻呼消息时，定时器已终止，则响应该寻呼消息重新发起RRC连接建立过程。
通过采用可选方案一，终端设备301启动一个定时器，以避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形，并可避免丢话。目 前LTE***中，只有当终端设备301处于空闲态时收到寻呼消息才会与网络建立连接，而处于连接态的终端设备301会忽略寻呼消息，这可能造成丢话。与目前LTE***的处理方式相比，可选方案一既能够解决丢话的问题，也能够避免RRC连接建立过程与寻呼过程并发的情况。
可选方案一中，通过在终端设备301侧设置定时器，识别终端设备发起的RRC连接建立过程与网络发送的寻呼消息并发的场景，从而避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的问题。
此外，另一种通过终端设备301侧的处理避免图6A所示的情形的可选方案包括：终端设备301从发送RRC连接请求开始，到信令无线承载(Signalling Radio Bearer，SRB)2或数据无线承载(Data Radio Bearer，DRB)建立完成这段时间内，若收到用于寻呼空闲态终端设备的寻呼消息，则忽略收到的该寻呼消息；可选地，在SRB2和DRB建立完成后，若收到用于寻呼空闲态UE的寻呼消息，可以处理收到的该寻呼消息，比如响应于该寻呼消息发起RRC连接建立过程。
【可选方案二】
图9为可选方案二的流程图。如图9所示，该流程包括如下步骤：
S901：接入网设备302接收终端设备301发送的RRC连接请求消息，RRC连接请求消息包括终端设备301的标识；
S902：接入网设备302基于终端设备301的标识判断之前是否已收到核心网设备303发送的针对终端设备301的寻呼消息；若接入网设备302确定之前已收到核心网设备303发送的针对终端设备301的寻呼消息，则执行步骤S903；
S903：接入网设备302判断是否已根据寻呼消息寻呼终端设备301；若接入网设备302确定尚未根据寻呼消息寻呼终端设备301，则丢弃该寻呼消息。
本发明各个实施例中，丢弃寻呼消息可以理解为接入网设备302放弃寻呼终端设备301，以下不再赘述。
下面，参考图10，以接入网设备302在收到RRC连接请求之前已收到核心网设备303发送的针对终端设备301的寻呼消息为例，加以说明。
如图10所示，接入网设备302首先接收到核心网设备303发送的寻呼消息，该寻呼消息中包含被寻呼的终端设备301的标识S-TMSI。
接入网设备302收到该寻呼消息后会维护该S-TMSI。接入网设备302配置寻呼终端设备301所使用的无线帧和子帧，即确定寻呼时机，接入网设备302准备在确定的寻呼时机处发送寻呼消息以寻呼终端设备301。
但是，在寻呼时机来临前，接入网设备302收到终端设备301发送的RRC连接请求消息，该请求消息中同样带有终端设备301的标识S-TMSI，接入网设备302为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形发生采取的方法是：
接入网设备302在收到RRC连接请求消息后，判断该消息中携带的S-TMSI是不是已被接入网设备302维护，即判断之前是否已收到了核心网设备303发送的针对终端设备301的寻呼消息；若确定之前已经收到核心网设备303发送的针对终端设备301的寻呼消息，则进一步判断是否已向终端设备301发送寻呼消息，即接入网设备302从核心网设备303处收到寻呼消息该寻呼消息中携带S-TMSI，接入网设备302确定该S-TMSI对应终端设备301，接入网设备302进而判断用于寻呼该终端设备301的寻呼消息是不是正在等待通过空口被发送给终端设备301，若该寻呼消息等待被发送，则接入网设备302丢弃该等待发送的寻呼消息，在对应的寻呼时机不会将寻呼消息发送给终端设备301。
此外，可选地，若在步骤S901中的RRC连接请求消息触发的RRC连接建立过程中或RRC建立过程完成后，接入网设备302收到核心网设备303发送的针对终端设备301的另一个寻呼消息(该寻呼消息不是步骤S902中提到的寻呼消息)，则接入网设备302丢弃该寻呼消息。
【可选方案三】
图11为可选方案三的流程图。如图11所示，该流程包括如下步骤：
S1101：接入网设备302接收核心网设备303发送的针对终端设备301的寻呼消息；
S1102：接入网设备302判断是否已建立了针对终端设备301的RRC连接，或针对终端设备301的RRC连接是否处于建立过程中；若接入网设备302确定已建立了针对终端设备301的RRC连接，或针对终端设备301的RRC连接处于建立过程中，则丢弃该寻呼消息(例如放弃寻呼终端设备301)；若接入网设备302确定没有已建立的针对终端设备301的RRC连接，也没有针对终端设备301的正在进行的RRC连接建立过程，则执行步骤S1103；
S1103：接入网设备302寻呼终端设备301。
图12为可选方案三的一种可能的实现方式的流程图。如图12所示，接入网设备302首先接收到终端设备301发送的RRC连接请求消息，该消息中包含终端设备301的标识S-TMSI，接入网设备302在收到该消息后建立该终端设备301对应的一个实例以维护相关信息(包括S-TMSI等终端设备301请求进入连接态的相关信息及终端设备301进入连接态后的上下文信息)。
接入网设备302在收到核心网设备303发送的寻呼消息后判断该寻呼消息中携带的S-TMSI是否包含在接入网设备302已建立的实例中，即判断是否已建立了针对终端设备301的RRC连接，或者针对终端设备301的RRC连接是否正在建立的过程中。
若实例中包含该S-TMSI说明终端设备301正请求进入连接态(即RRC连接正在建立的过程中)或已经处于连接态(即已经建立了针对终端设备301的RRC连接)，因此接入网设备302会忽略该寻呼消息而不寻呼该终端设备301；反之，接入网设备302在空口发送寻呼消息给终端设备301。
可选地，步骤S1102中，若接入网设备302确定已建立了针对终端设备301的RRC连接，或针对终端设备301的RRC连接处于建立过程中，则在步骤S1101接入网设备302接收核心网设备303发送的针对终端设备301的寻呼消息之前，还可包括：接入网设备302接收终端设备301发送的用于建立RRC连接的RRC连接请求消息，RRC连接请求消息包括终端设备301的标 识；
若接入网设备302根据终端设备301的标识确定在收到该RRC连接请求消息之前已收到核心网设备303发送的针对终端设备301的另一个寻呼消息(该寻呼消息不同于步骤S1101中接收的寻呼消息)且尚未根据该寻呼消息寻呼终端设备301，则接入网设备302确定丢弃该寻呼消息(例如放弃寻呼终端设备301)。
可选方案二和可选方案三中，为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形，接入网设备302根据接收到RRC连接请求消息和寻呼消息的时间先后顺序分两种情况进行处理，接入网设备302根据自身判断来决定是否在空口发送寻呼消息。
目前LTE***中，只有当UE处于空闲态时收到寻呼消息才会发起RRC连接建立过程从而与网络进行数据传输，而处于连接态的UE会忽略寻呼消息，这可能会造成丢话。可选方案二和可选方案三中，为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形给出接入网设备302的解决方法，可有效避免图6A所示的情形。
【可选方案四】
图13为可选方案四的流程图。如图13所示，该流程包括如下步骤：
S1301：核心网设备303接收接入网设备302发送的针对终端设备301的初始用户设备UE消息，这里以初始UE消息为例，实际上，任何用于在接入网设备与核心网设备之间的接口上触发建立针对终端设备的信令连接的消息均可适用；
S1302：核心网设备303判断在核心网设备303与接入网设备302之间的接口上是否已具备针对终端设备301的S1连接；若确定已具备S1连接，则执行步骤S1303；
S1303：核心网设备303释放已具备的S1连接，并响应初始UE消息，在核心网设备303与接入网设备302之间的接口上重新建立针对终端设备301的S1连接。
在步骤S1301核心网设备303接收接入网设备302发送的UE初始消息之前，还包括：
核心网设备303接收接入网设备302发送的另一条初始UE消息，该初始UE消息由终端设备301触发；
核心网设备303确定与接入网设备302间已具备S1连接；
步骤S1303中，核心网设备303释放S1连接，包括：
核心网设备303向接入网设备302发送用户设备UE上下文释放命令消息，用于触发接入网设备302向终端设备301发送RRC连接释放消息。
图6A所示的流程中，终端设备301最终进入空闲态而无法与网络进行数据传输。而可选方案四中，核心网设备303可经过步骤S1302中的判断，在确定已存在S1连接的情况下，通过执行步骤S1303，释放已经连的S1连接，并重新建立针对终端设备301的S1连接，从而实现了终端设备301与网络的数据传输。
图14为可选方案四的一种可选实现方式的流程图。图14中，虚线代表寻呼接入流程，实线代表终端设备301主动接入流程，点划线代表采用可选方案四后，核心网设备303重建S1连接而触发的消息流程。如图14所示。终端设备301在发送RRC连接建立完成消息之后、收到RRC安全模式命令消息之前收到接入网设备302发送的寻呼消息，终端设备301为响应该寻呼消息重新发起RRC连接建立过程，接入网设备302收到RRC连接建立完成消息之后在S1接口再次给核心网设备303发送初始UE消息，核心网设备303根据初始UE消息中携带的终端设备301的标识(S-TMSI)识别出前后两次接收到的初始UE消息是同一个终端设备301触发的。
为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的图6A的情形，核心网设备303在再次收到初始UE消息后，通过向接入网设备302发送UE上下文释放命令，释放先前建立的在核心网设备303与接入网设备302之间的接口上的针对终端设备301的S1连接，以触发接入网设备302在空口给终端设备301发送RRC连接释放消息，并且核心网设备303请求建 立新的初始上下文以触发终端设备301在空口完成安全功能激活及RRC连接重配置流程，从而保证接入网设备302侧重新建立起针对终端设备301的S1连接。这一系列流程完成后，终端设备301便重新进入连接态从而能与网络进行数据传输。
可选方案四中，为解决图6A所示的终端设备301进入空闲态而无法与网络进行数据传输的问题，可选方案四中，核心网设备303在再次收到初始UE消息后释放先前建立的针对终端设备301的S1连接并请求针对终端设备301建立新的S1连接，保证终端设备301重新进入连接态与网络进行数据传输。
目前LTE***中，在图6A所示的情形下，核心网设备303在再次收到初始UE消息后根据该消息中携带的终端设备301标识(S-TMSI)识别出两次接收到的初始UE消息是同一个终端设备301触发的，核心网设备303认为有误便要求释放先前建立的针对终端设备301的S1连接，即向接入网设备302发送UE上下文释放命令消息，以触发接入网设备302给终端设备301发送RRC连接释放消息，终端设备301释放了RRC连接后，接入网设备302向核心网设备303发送UE上下文释放完成(UE Context Release Complete)消息，核心网设备303释放S1连接最终导致终端设备301进入空闲态而无法与网络进行数据传输。而可选方案四中，核心网设备303再次收到初始UE消息后不仅要求释放先前建立的针对终端设备301的S1连接，并且请求建立新的针对终端设备301的S1连接，即通过发送初始上下文建立请求触发接入网设备302进行RRC连接重配置过程，向终端设备301发送RRC连接重配置(RRC Connection Reconfiguration)消息，并接收终端设备301发送的RRC连接重配置完成(RRC Connection Reconfiguration Complete)消息，完成终端设备301的RRC连接的重配置，使得终端设备301重新进入连接态与网络进行数据传输。接入网设备302在收到终端设备301发送的RRC连接重配置完成消息后，向核心网设备303发送初始上下文建立完成(Initial Context Setup Complete)消息，指示S1连接已建立完成。
图15为一个实施例提供的终端设备的结构示意图。如图15所示，该终 端设备包括：
发送模块1501，用于向接入网设备发起第一次RRC连接建立过程；
处理模块1502，用于在第一次RRC连接建立过程中启动定时器；
接收模块1503，用于接收接入网设备发送的寻呼消息，寻呼消息包括终端设备的标识；
发送模块1501还用于：当定时器处于超时状态，根据寻呼消息发起第二次RRC连接建立过程；
处理模块1502还用于：当定时器处于未超时状态，忽略寻呼消息以维持第一次RRC连接建立过程建立的RRC连接。
可选地，定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
可选地，处理模块1502具体用于：
在发送模块1501向接入网设备发送RRC连接请求消息时启动定时器；或
在接收模块1503接收接入网设备发送的RRC连接建立消息时启动定时器。
可选地，定时器的时长是协议预先规定的，或由寻呼周期确定的，或由接入网设备确定并通知终端设备的。
定时器的时长、定时器启动和终止的可选实现方式，可参考前述的可选方案一。发送模块1501的其他可选实现方式可参考前述的可选方案一中，终端设备301的发送操作；处理模块1502的其他可选实现方式可参考前述的可选方案一中，终端设备301的处理操作；接收模块1503的其他可选实现方式可参考前述的可选方案一中，终端设备301的接收操作。
其中，通过设置定时器，识别终端设备发起的RRC连接建立过程与网络发送的寻呼过程并发的场景，从而避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的问题。
一个实施例提供的终端设备可包括：
发送器1601，用于向接入网设备发起第一次RRC连接建立过程；
处理器1602，用于在第一次RRC连接建立过程中启动定时器；
接收器1603，用于接收接入网设备发送的寻呼消息，寻呼消息包括终端设备的标识；
发送器1601还用于：当定时器处于超时状态，根据寻呼消息发起第二次RRC连接建立过程；
处理器1602还用于：当定时器处于未超时状态，忽略寻呼消息以维持第一次RRC连接建立过程建立的RRC连接。
可选地，该终端设备可由图16A或图16B所示的结构实现。
图16A中，发送器1601和接收器1603分别与处理器1602相连。
图16B示出了一种总线结构。其中，在图16B中，总线结构可以包括任意数量的互联的总线和桥。处理器1602、存储器1604、发送器1601和接收器1602通过总线1605相互连接。存储器1604用于存储指令，处理器1602用于执行存储器1604中存储的指令，以控制接收器1603接收信号，并控制发送器1601发送信号。
其中，发送器1601的其他可选实现方式可参考发送模块1501，处理器1602的其他可选实现方式可参考处理模块1502，接收器1603的其他可选实现方式可参考接收模块1503。
其中，通过设置定时器，识别终端设备发起的RRC连接建立过程与网络发起的寻呼过程并发的场景，从而避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的问题。
图17为一个实施例提供的接入网设备的结构示意图。如图17所示，该接入网设备包括：
处理模块1701，用于确定定时器的时长；
发送模块1702，用于通知终端设备定时器的时长，以使终端设备：
在向接入网设备发起的第一次建立无线资源控制RRC连接的过程中启动定时器，并在收到接入网设备发送的寻呼消息，且寻呼消息包括终端设备的标识时：
当定时器处于超时状态，根据寻呼消息发起第二次RRC连接建立过程；
当定时器处于未超时状态，忽略寻呼消息以维持第一次RRC连接建立过程建立的RRC连接。
可选地，定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
可选地，处理模块1701具体用于：
根据寻呼周期确定定时器的时长。
其中，处理模块1701的其他可选实现方式可参考前述的可选方案一中，接入网设备302的处理操作；发送模块1702的其他可选实现方式可参考前述的可选方案一中，接入网设备302的发送操作。
其中，通过设置定时器，识别终端设备发起的RRC连接建立过程与网络发起的寻呼过程并发的场景，从而避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的问题。
一个实施例提供的接入网设备包括：
处理器1801，用于确定定时器的时长；
发送器1802，用于通知终端设备定时器的时长，以使终端设备：
在向接入网设备发起的第一次建立无线资源控制RRC连接的过程中启动定时器，并在收到接入网设备发送的寻呼消息，且寻呼消息包括终端设备的标识时：
当定时器处于超时状态，根据寻呼消息发起第二次RRC连接建立过程；
当定时器处于未超时状态，忽略寻呼消息以维持第一次RRC连接建立过程建立的RRC连接。
可选地，定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程 并发的场景。
可选地，处理器1801具体用于：
根据寻呼周期确定定时器的时长。
其中，处理器1801的其他可选实现方式可参考前述的可选方案一中，接入网设备的处理操作；发送器1802的其他可选实现方式可参考前述的可选方案一中，接入网设备的发送操作。
可选地，该接入网设备可由图18A或图18B所示的结构实现。
图18A中，发送器1802与处理器1801相连。
图18B示出了一种总线结构。其中，在图18B中，总线结构可以包括任意数量的互联的总线和桥。处理器1801、存储器1803、发送器1802通过总线1805相互连接。存储器1803用于存储指令，处理器1801用于执行存储器1803中存储的指令，以控制发送器1802发送信号。
其中，发送器1802的其他可选实现方式可参考发送模块1702，处理器1801的其他可选实现方式可参考处理模块1701。
其中，通过设置定时器，识别终端设备发起的RRC连接建立过程与网络发起的寻呼过程并发的场景，从而避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的问题。
图19为一个实施例提供的接入网设备的结构示意图。如图19所示，该接入网设备包括：
接收模块1901，用于接收终端设备发送的无线资源控制RRC连接请求消息，RRC连接请求消息包括终端设备的标识；
处理模块1902，用于根据终端设备的标识确定接收模块1901已收到核心网设备发送的针对终端设备的第一寻呼消息且尚未根据第一寻呼消息寻呼终端设备，则丢弃第一寻呼消息。
可选地，处理模块1902还用于：
当在RRC连接请求消息触发的RRC连接建立过程中或RRC建立过程完成后，接收模块1901收到核心网设备发送的针对终端设备的第二寻呼消息， 则丢弃第二寻呼消息。
其中，接收模块1901的其他可选实现方式可参考前述的可选方案二中，接入网设备302的接收操作；处理模块1502的其他可选实现方式可参考前述的可选方案二中，接入网设备302的处理操作。
其中，为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形，接入网设备根据接收到RRC连接请求消息和寻呼消息，判断是否在空口发送寻呼消息，可有效避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形。
一个实施例提供的接入网设备包括：
接收器2001，用于接收终端设备发送的无线资源控制RRC连接请求消息，RRC连接请求消息包括终端设备的标识；
处理器2002，用于根据终端设备的标识确定接收器2001已收到核心网设备发送的针对终端设备的第一寻呼消息且尚未根据第一寻呼消息寻呼终端设备，则丢弃第一寻呼消息。
可选地，该接入网设备可由图20A或图20B所示的结构实现。
图20A中，接收器2001与处理器2002相连。
图20B示出了一种总线结构。其中，在图20B中，总线结构可以包括任意数量的互联的总线和桥。处理器2002、存储器2003和接收器2001通过总线2004相互连接。存储器2003用于存储指令，处理器2002用于执行存储器2003中存储的指令，以控制接收器2001接收信号。
其中，处理器2002的其他可选实现方式可参考处理模块1902，接收器2001的其他可选实现方式可参考接收模块1901。
其中，为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形，接入网设备根据接收到RRC连接请求消息和寻呼消息，判断是否在空口发送寻呼消息，可有效避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形。
图21为一个实施例提供的接入网设备的结构示意图。如图21所示，该 接入网设备包括：
接收模块2101，用于接收核心网设备发送的针对终端设备的第二寻呼消息；
处理模块2102，用于根据第二寻呼消息判断是否已建立了针对终端设备的无线资源控制RRC连接，或针对终端设备的RRC连接是否处于建立过程中；
处理模块2102还用于：若确定已建立了针对终端设备的RRC连接，或针对终端设备的RRC连接处于建立过程中，丢弃第二寻呼消息；
接入网设备还包括发送模块2103，用于在处理模块2102确定没有已建立的针对终端设备的RRC连接，也没有针对终端设备的正在进行的RRC连接建立过程时，根据第二寻呼消息寻呼终端设备。
可选地，若处理模块2102确定已建立了针对终端设备的RRC连接，或针对终端设备的RRC连接处于建立过程中，接收模块2101还用于：在接收核心网设备发送的针对终端设备的第二寻呼消息之前，接收终端设备发送的用于建立RRC连接的RRC连接请求消息，RRC连接请求消息包括终端设备的标识；
处理模块2102还用于：若根据终端设备的标识确定接收模块2101在收到RRC连接请求消息之前已收到核心网设备发送的针对终端设备的第一寻呼消息且发送模块2103尚未根据第一寻呼消息寻呼终端设备，丢弃第一寻呼消息。
其中，发送模块2103的其他可选实现方式可参考前述的可选方案三中，接入网设备302的发送操作；处理模块2102的其他可选实现方式可参考前述的可选方案三中，接入网设备302的处理操作；接收模块2101的其他可选实现方式可参考前述的可选方案三中，接入网设备302的接收操作。
其中，为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形，接入网设备根据接收到RRC连接请求消息和寻呼消息，判断是否在空口发送寻呼消息，可有效避免图6A所示的UE最终进入空闲态而无法与 网络进行数据传输的情形。
一个实施例提供的接入网设备包括：接收器2201，用于接收核心网设备发送的针对终端设备的第二寻呼消息；
处理器2202，用于根据第二寻呼消息判断是否已建立了针对终端设备的无线资源控制RRC连接，或针对终端设备的RRC连接是否处于建立过程中；
处理器2202还用于：若确定已建立了针对终端设备的RRC连接，或针对终端设备的RRC连接处于建立过程中，丢弃第二寻呼消息；
接入网设备还包括发送器2203，用于在处理器2202确定没有已建立的针对终端设备的RRC连接，也没有针对终端设备的正在进行RRC连接建立过程时，根据第二寻呼消息寻呼终端设备。
可选地，该接入网设备可由图22A或图22B所示的结构实现。
图22A中，发送器2203和接收器2201分别与处理器2202相连。
图22B示出了一种总线结构。其中，在图22B中，总线结构可以包括任意数量的互联的总线和桥。处理器2202、存储器2204、发送器2203和接收器2201通过总线2205相互连接。存储器2204用于存储指令，处理器2202用于执行存储器2204中存储的指令，以控制接收器2201接收信号，并控制发送器2203发送信号。
其中，发送器2203的其他可选实现方式可参考发送模块2103，处理器2202的其他可选实现方式可参考处理模块2102，接收器2201的其他可选实现方式可参考接收模块2101。
其中，为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形，接入网设备根据接收到RRC连接请求消息和寻呼消息，判断是否在空口发送寻呼消息，可有效避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形。
图23为本发明实施例提供的一种核心网设备的结构示意图。如图23所示，该核心网设备包括：
接收模块2301，用于接收接入网设备发送的第一初始用户设备UE消息， 第一初始UE消息由终端设备触发；
处理模块2302，用于当确定核心网设备与接入网设备间已具备针对终端设备的S1连接时，释放S1连接，并重新建立与接入网设备间的针对终端设备的S1连接。
可选地，接收模块2301还用于：在接收接入网设备发送的第一初始UE消息之前，接收接入网设备发送的第二初始UE消息，第二初始UE消息由终端设备触发；
处理模块2302还用于：确定核心网设备与接入网设备间已具备S1连接；
核心网设备还包括发送模块2303；处理模块2302具体用于：
通过发送模块2303向接入网设备发送用户设备UE上下文释放命令消息，用于触发接入网设备向终端设备发送RRC连接释放消息。
其中，发送模块2303的其他可选实现方式可参考前述的可选方案四中，核心网设备303的发送操作；处理模块2302的其他可选实现方式可参考前述的可选方案四中，核心网设备303的处理操作；接收模块2301的其他可选实现方式可参考前述的可选方案一中，核心网设备303的接收操作。
为解决图6A所示的终端设备301进入空闲态而无法与网络进行数据传输的问题，核心网设备在再次收到初始UE消息后释放先前建立的针对终端设备的S1连接并请求针对终端设备建立新的S1连接，保证终端设备重新进入连接态与网络进行数据传输。
一个实施例提供的核心网设备包括：
接收器2401，用于接收接入网设备发送的第一初始用户设备UE消息，第一初始UE消息由终端设备触发；
处理器2402，用于当确定核心网设备与接入网设备间已具备针对终端设备的S1连接时，释放S1连接，并重新建立与接入网设备间的针对终端设备的S1连接。
可选地，接收器2401还用于：在接收接入网设备发送的第一初始UE消息之前，接收接入网设备发送的第二初始UE消息，第二初始UE消息由终端 设备触发；
处理器2402还用于：确定核心网设备与接入网设备间已具备S1连接；
核心网设备还包括发送器2403；处理器2402具体用于：
通过发送器2403向接入网设备发送用户设备UE上下文释放命令消息，用于触发接入网设备向终端设备发送RRC连接释放消息。
可选地，该核心网设备可由图24A或图24B所示的结构实现。
图24A中，接收器2401和发送器2403分别与处理器2402相连。
图24B示出了一种总线结构。其中，在图24B中，总线结构可以包括任意数量的互联的总线和桥。处理器2402、存储器2404、发送器2403和接收器2401通过总线2405相互连接。存储器2404用于存储指令，处理器2402用于执行存储器2404中存储的指令，以控制接收器2401接收信号，并控制发送器2403发送信号。
其中，发送器2403的其他可选实现方式可参考发送模块2303，处理器2402的其他可选实现方式可参考处理模块2302，接收器2401的其他可选实现方式可参考接收模块2301。
为解决图6A所示的终端设备301进入空闲态而无法与网络进行数据传输的问题，核心网设备在再次收到初始UE消息后释放先前建立的针对终端设备的S1连接并请求针对终端设备建立新的S1连接，保证终端设备重新进入连接态与网络进行数据传输。
图25为一个实施例提供的寻呼方法的流程图。如图25所示，该方法包括：
S2501：终端设备向接入网设备发起第一次无线资源控制RRC连接建立过程；
S2502：终端设备在第一次RRC连接建立过程中启动定时器；
S2503：终端设备接收接入网设备发送的寻呼消息，寻呼消息包括终端设备的标识；
S2504：当定时器处于超时状态，终端设备根据寻呼消息发起第二次RRC 连接建立过程；当定时器处于未超时状态，终端设备忽略寻呼消息以维持第一次RRC连接建立过程建立的RRC连接。
可选地，定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
可选地，终端设备在发起的第一次RRC连接建立过程中启动定时器包括：
终端设备在向接入网设备发送RRC连接请求消息时启动定时器；或
终端设备在接收接入网设备发送的RRC连接建立消息时启动定时器。
可选地，定时器的时长是协议预先规定的，或由寻呼周期确定的，或由接入网设备确定并通知终端设备的。
该方法的其他可选实现方式可参考可选方案一。
其中，通过设置定时器，识别终端设备发起的RRC连接建立过程与网络发起的寻呼过程并发的场景，从而避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的问题。
图26为一个实施例提供的寻呼方法的流程图。如图26所示，该方法包括：
S2601:接入网设备确定定时器的时长；
S2602:接入网设备通知终端设备定时器的时长，以使终端设备：
在向接入网设备发起的第一次建立无线资源控制RRC连接的过程中启动定时器，并在收到接入网设备发送的寻呼消息，且寻呼消息包括终端设备的标识时：
当定时器处于超时状态，根据寻呼消息发起第二次RRC连接建立过程；
当定时器处于未超时状态，忽略寻呼消息以维持第一次RRC连接建立过程建立的RRC连接。
可选地，定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
可选地，接入网设备确定定时器的时长，包括：
接入网设备根据寻呼周期确定定时器的时长。
该方法的其他可选实现方式可参考可选方案一。
其中，通过设置定时器，识别终端设备发起的RRC连接建立过程与网络发起的寻呼过程并发的场景，从而避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的问题。
图27为一个实施例提供的寻呼方法的流程图。如图27所示，该方法包括：
S2701:接入网设备接收终端设备发送的无线资源控制RRC连接请求消息，RRC连接请求消息包括终端设备的标识；
S2702:当接入网设备根据终端设备的标识确定已收到核心网设备发送的针对终端设备的第一寻呼消息且尚未根据第一寻呼消息寻呼终端设备，则接入网设备丢弃第一寻呼消息。
可选地，还包括：
当在RRC连接请求消息触发的RRC连接建立过程中或RRC建立过程完成后，接入网设备收到核心网设备发送的针对终端设备的第二寻呼消息，则接入网设备丢弃第二寻呼消息。
该方法的其他可选实现方式可参考可选方案二。
其中，为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形，接入网设备根据接收到RRC连接请求消息和寻呼消息，判断是否在空口发送寻呼消息，可有效避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形。
图28为一个实施例提供的寻呼方法的流程图。如图28所示，该方法包括：
S2801：接入网设备接收核心网设备发送的针对终端设备的第二寻呼消息；
S2802：接入网设备根据第二寻呼消息判断是否已建立了针对终端设备的无线资源控制RRC连接，或针对终端设备的RRC连接是否处于建立过程中；
S2803：若接入网设备确定已建立了针对终端设备的RRC连接，或针对 终端设备的RRC连接处于建立过程中，接入网设备丢弃第二寻呼消息；若接入网设备确定没有已建立的针对终端设备的RRC连接，也没有针对终端设备的正在进行的RRC连接建立过程，接入网设备根据第二寻呼消息寻呼终端设备。
可选地，若接入网设备确定已建立了针对终端设备的RRC连接，或针对终端设备的RRC连接处于建立过程中，在接入网设备接收核心网设备发送的针对终端设备的第二寻呼消息之前，还包括：接入网设备接收终端设备发送的用于建立RRC连接的RRC连接请求消息，RRC连接请求消息包括终端设备的标识；
该方法还包括：若接入网设备根据终端设备的标识确定在收到RRC连接请求消息之前已收到核心网设备发送的针对终端设备的第一寻呼消息且尚未根据第一寻呼消息寻呼终端设备，接入网设备丢弃第一寻呼消息。
该方法的其他可选实现方式可参考可选方案三。
其中，为避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形，接入网设备根据接收到RRC连接请求消息和寻呼消息，判断是否在空口发送寻呼消息，可有效避免图6A所示的UE最终进入空闲态而无法与网络进行数据传输的情形。
图29为一个实施例提供的寻呼方法的流程图。如图29所示，该方法包括：
S2901：核心网设备接收接入网设备发送的第一初始用户设备UE消息，第一初始UE消息由终端设备触发；
S2902：当核心网设备确定与接入网设备间已具备针对终端设备的S1连接时，核心网设备释放S1连接；
S2903：核心网设备重新建立与接入网设备间的针对终端设备的S1连接。
可选地，在核心网设备接收接入网设备发送的第一初始UE消息之前，还包括：
核心网设备接收接入网设备发送的第二初始UE消息，第二初始UE消息 由终端设备触发；
核心网设备确定与接入网设备间已具备S1连接；
核心网设备释放S1连接，包括：
核心网设备向接入网设备发送用户设备UE上下文释放命令消息，用于触发接入网设备向终端设备发送RRC连接释放消息。
该方法的其他可选实现方式可参考可选方案四。
为解决图6A所示的终端设备301进入空闲态而无法与网络进行数据传输的问题，核心网设备在再次收到初始UE消息后释放先前建立的针对终端设备的S1连接并请求针对终端设备建立新的S1连接，保证终端设备重新进入连接态与网络进行数据传输。
综上，终端设备在收到用于寻呼该终端设备的寻呼消息时，若寻呼消息中携带该终端设备的标识，若确定自身处于连接态，则响应于接收的该寻呼消息发起RRC连接建立过程。从而解决了上述诸如UE的终端设备确定自身处于连接态，而网络认为UE处于空闲态的情况下，UE忽略网络下发的寻呼消息而造成的严重丢话的问题。
进一步地，为了避免UE响应于寻呼消息发起RRC连接建立过程可能造成的UE最终进入空闲态而无法与网络进行数据传输的情形，通过在终端设备启动定时器，在定时器处于超时状态前忽略寻呼消息，在定时器处于超时状态后响应寻呼消息发起RRC连接建立过程；或者通过接入网设备区分接收的RRC连接请求和寻呼消息的先后关系，确定是否向终端设备发送寻呼消息；再或者通过核心网设备在出现并发情形后，释放先前建立的S1连接，重新建立新的S1连接，避免终端设备最终进入空闲态而无法与网络进行数据传输。
本领域内的技术人员应明白，本发明的实施例可提供为方法、***、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例做出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然，本领域的技术人员可以对本发明实施例进行各种改动和变型而不脱离本发明实施例的精神和范围。这样，倘若本发明实施例的这些修改和变型属于本发明权利要求及其等同技术的范围之内，则本发明也意图包含这些改动和变型在内。

Claims (22)

  1. 一种终端设备，其特征在于，包括：
    发送模块，用于向接入网设备发起第一次无线资源控制RRC连接建立过程；
    处理模块，用于在所述第一次RRC连接建立过程中启动定时器；
    接收模块，用于接收所述接入网设备发送的寻呼消息，所述寻呼消息包括所述终端设备的标识；
    所述发送模块还用于：当所述定时器处于超时状态，根据所述寻呼消息发起第二次RRC连接建立过程；
    所述处理模块还用于：当所述定时器处于未超时状态，忽略所述寻呼消息以维持所述第一次RRC连接建立过程建立的RRC连接。
  2. 如权利要求1所述的终端设备，其特征在于，
    所述定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
  3. 如权利要求1或2所述的终端设备，其特征在于，所述处理模块具体用于：
    在所述发送模块向所述接入网设备发送RRC连接请求消息时启动所述定时器；或
    在所述接收模块接收所述接入网设备发送的RRC连接建立消息时启动所述定时器。
  4. 如权利要求1～3任一项所述的终端设备，其特征在于，所述定时器的时长是协议预先规定的，或由寻呼周期确定的，或由所述接入网设备确定并通知所述终端设备的。
  5. 一种接入网设备，其特征在于，包括：
    处理模块，用于确定定时器的时长；
    发送模块，用于通知终端设备所述定时器的时长，以使所述终端设备：
    在向所述接入网设备发起的第一次建立无线资源控制RRC连接的过程中启动所述定时器，并在收到所述接入网设备发送的寻呼消息，且所述寻呼消息包括所述终端设备的标识时：
    当所述定时器处于超时状态，根据所述寻呼消息发起第二次RRC连接建立过程；
    当所述定时器处于未超时状态，忽略所述寻呼消息以维持所述第一次RRC连接建立过程建立的RRC连接。
  6. 如权利要求5所述的接入网设备，其特征在于，
    所述定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
  7. 如权利要求5或6所述的接入网设备，其特征在于，所述处理模块具体用于：
    根据寻呼周期确定所述定时器的时长。
  8. 一种接入网设备，其特征在于，包括：
    接收模块，用于接收终端设备发送的无线资源控制RRC连接请求消息，所述RRC连接请求消息包括所述终端设备的标识；
    处理模块，用于根据所述终端设备的标识确定所述接收模块已收到所述核心网设备发送的针对所述终端设备的第一寻呼消息且尚未根据所述第一寻呼消息寻呼所述终端设备，则丢弃所述第一寻呼消息。
  9. 如权利要求8所述的接入网设备，其特征在于，所述处理模块还用于：
    当在所述RRC连接请求消息触发的RRC连接建立过程中或所述RRC建立过程完成后，所述接收模块收到所述核心网设备发送的针对所述终端设备的第二寻呼消息，则丢弃所述第二寻呼消息。
  10. 一种接入网设备，其特征在于，包括：
    接收模块，用于接收核心网设备发送的针对终端设备的第二寻呼消息；
    处理模块，用于根据所述第二寻呼消息判断是否已建立了针对所述终端设备的无线资源控制RRC连接，或针对所述终端设备的RRC连接是否处于 建立过程中；
    所述处理模块还用于：若确定已建立了针对所述终端设备的RRC连接，或针对所述终端设备的RRC连接处于建立过程中，丢弃所述第二寻呼消息；
    所述接入网设备还包括发送模块，用于在所述处理模块确定没有已建立的针对所述终端设备的RRC连接，也没有针对所述终端设备的正在进行过的RRC连接建立过程时，根据所述第二寻呼消息寻呼所述终端设备。
  11. 如权利要求10所述的接入网设备，其特征在于，
    若所述处理模块确定已建立了针对所述终端设备的RRC连接，或针对所述终端设备的RRC连接处于建立过程中，所述接收模块还用于：在接收所述核心网设备发送的针对终端设备的所述第二寻呼消息之前，接收所述终端设备发送的用于建立所述RRC连接的RRC连接请求消息，所述RRC连接请求消息包括所述终端设备的标识；
    所述处理模块还用于：若根据所述终端设备的标识确定所述接收模块在收到所述RRC连接请求消息之前已收到所述核心网设备发送的针对所述终端设备的第一寻呼消息且所述发送模块尚未根据所述第一寻呼消息寻呼所述终端设备，丢弃所述第一寻呼消息。
  12. 一种寻呼方法，其特征在于，包括：
    终端设备向接入网设备发起第一次无线资源控制RRC连接建立过程；
    所述终端设备在所述第一次RRC连接建立过程中启动定时器；
    所述终端设备接收所述接入网设备发送的寻呼消息，所述寻呼消息包括所述终端设备的标识；
    当所述定时器处于超时状态，所述终端设备根据所述寻呼消息发起第二次RRC连接建立过程；
    当所述定时器处于未超时状态，所述终端设备忽略所述寻呼消息以维持所述第一次RRC连接建立过程建立的RRC连接。
  13. 如权利要求12所述的方法，其特征在于，
    所述定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发 的场景。
  14. 如权利要求12或13所述的方法，其特征在于，所述终端设备在发起的第一次RRC连接建立过程中启动定时器包括：
    所述终端设备在向所述接入网设备发送RRC连接请求消息时启动所述定时器；或
    所述终端设备在接收所述接入网设备发送的RRC连接建立消息时启动所述定时器。
  15. 如权利要求12～14任一项所述的方法，其特征在于，所述定时器的时长是协议预先规定的，或由寻呼周期确定的，或由所述接入网设备确定并通知所述终端设备的。
  16. 一种寻呼方法，其特征在于，包括：
    接入网设备确定定时器的时长；
    所述接入网设备通知终端设备所述定时器的时长，以使所述终端设备：
    在向所述接入网设备发起的第一次建立无线资源控制RRC连接的过程中启动所述定时器，并在收到所述接入网设备发送的寻呼消息，且所述寻呼消息包括所述终端设备的标识时：
    当所述定时器处于超时状态，根据所述寻呼消息发起第二次RRC连接建立过程；
    当所述定时器处于未超时状态，忽略所述寻呼消息以维持所述第一次RRC连接建立过程建立的RRC连接。
  17. 如权利要求16所述的方法，其特征在于，
    所述定时器用于识别终端设备发起的RRC连接建立过程与寻呼过程并发的场景。
  18. 如权利要求16或17所述的方法，其特征在于，所述接入网设备确定定时器的时长，包括：
    所述接入网设备根据寻呼周期确定所述定时器的时长。
  19. 一种寻呼方法，其特征在于，包括：
    接入网设备接收终端设备发送的无线资源控制RRC连接请求消息，所述RRC连接请求消息包括所述终端设备的标识；
    当所述接入网设备根据所述终端设备的标识确定已收到所述核心网设备发送的针对所述终端设备的第一寻呼消息且尚未根据所述第一寻呼消息寻呼所述终端设备，则所述接入网设备丢弃所述第一寻呼消息。
  20. 如权利要求19所述的方法，其特征在于，还包括：
    当在所述RRC连接请求消息触发的RRC连接建立过程中或所述RRC建立过程完成后，所述接入网设备收到所述核心网设备发送的针对所述终端设备的第二寻呼消息，则所述接入网设备丢弃所述第二寻呼消息。
  21. 一种寻呼方法，其特征在于，包括：
    接入网设备接收核心网设备发送的针对终端设备的第二寻呼消息；
    所述接入网设备根据所述第二寻呼消息判断是否已建立了针对所述终端设备的无线资源控制RRC连接，或针对所述终端设备的RRC连接是否处于建立过程中；
    若所述接入网设备确定已建立了针对所述终端设备的RRC连接，或针对所述终端设备的RRC连接处于建立过程中，所述接入网设备丢弃所述第二寻呼消息；
    若所述接入网设备确定没有已建立的针对所述终端设备的RRC连接，也没有针对所述终端设备的正在进行的RRC连接建立过程，所述接入网设备根据所述第二寻呼消息寻呼所述终端设备。
  22. 如权利要求21所述的方法，其特征在于，
    若所述接入网设备确定已建立了针对所述终端设备的RRC连接，或针对所述终端设备的RRC连接处于建立过程中，在所述接入网设备接收所述核心网设备发送的针对终端设备的所述第二寻呼消息之前，还包括：所述接入网设备接收所述终端设备发送的用于建立所述RRC连接的RRC连接请求消息，所述RRC连接请求消息包括所述终端设备的标识；
    所述方法还包括：若所述接入网设备根据所述终端设备的标识确定在收 到所述RRC连接请求消息之前已收到所述核心网设备发送的针对所述终端设备的第一寻呼消息且尚未根据所述第一寻呼消息寻呼所述终端设备，所述接入网设备丢弃所述第一寻呼消息。
PCT/CN2015/090196 2015-09-21 2015-09-21 一种寻呼设备和方法 WO2017049442A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2015/090196 WO2017049442A1 (zh) 2015-09-21 2015-09-21 一种寻呼设备和方法
CN201580028250.9A CN107409382A (zh) 2015-09-21 2015-09-21 一种寻呼设备和方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/090196 WO2017049442A1 (zh) 2015-09-21 2015-09-21 一种寻呼设备和方法

Publications (1)

Publication Number Publication Date
WO2017049442A1 true WO2017049442A1 (zh) 2017-03-30

Family

ID=58385545

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/090196 WO2017049442A1 (zh) 2015-09-21 2015-09-21 一种寻呼设备和方法

Country Status (2)

Country Link
CN (1) CN107409382A (zh)
WO (1) WO2017049442A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110547006A (zh) * 2017-04-28 2019-12-06 Oppo广东移动通信有限公司 无线通信的方法、网络设备和终端设备
CN111372310A (zh) * 2020-03-16 2020-07-03 展讯通信（上海）有限公司 一种寻呼管理方法及相关产品
CN114845393A (zh) * 2020-09-16 2022-08-02 北京小米移动软件有限公司 发送、接收寻呼消息的方法、装置、设备及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020186526A1 (zh) * 2019-03-21 2020-09-24 华为技术有限公司 一种寻呼终端设备的方法及装置
CN112672355A (zh) * 2019-09-29 2021-04-16 RealMe重庆移动通信有限公司 一种安全模式的建立方法、ue及计算机存储介质
CN111246569B (zh) * 2020-01-20 2023-04-07 展讯通信（上海）有限公司 寻呼处理方法、装置、设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101043734A (zh) * 2006-03-26 2007-09-26 华为技术有限公司 长期演进网络中用户设备的寻呼方法及其***
CN101820616A (zh) * 2009-02-26 2010-09-01 中兴通讯股份有限公司 用户设备及其寻呼处理方法、无线网络控制器
CN102932873A (zh) * 2006-08-04 2013-02-13 捷讯研究有限公司 在通信限制期间响应寻呼的***和方法

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159919A (zh) * 2005-03-28 2008-04-09 华为技术有限公司 一种简化消息发送处理的方法
CN100344181C (zh) * 2005-03-28 2007-10-17 华为技术有限公司 一种简化消息发送处理的方法
CN101222658B (zh) * 2007-01-10 2011-05-11 中兴通讯股份有限公司 寻呼广播消息的发送方法及***方法和合并方法
CN101784113B (zh) * 2009-01-19 2014-07-09 华为技术有限公司 寻呼***、寻呼方法和设备
CN101808415A (zh) * 2009-02-16 2010-08-18 大唐移动通信设备有限公司 处理通信业务过程冲突的方法及相关装置
CN102378120B (zh) * 2010-08-24 2015-10-21 中兴通讯股份有限公司 一种寻呼方法及***

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101043734A (zh) * 2006-03-26 2007-09-26 华为技术有限公司 长期演进网络中用户设备的寻呼方法及其***
CN102932873A (zh) * 2006-08-04 2013-02-13 捷讯研究有限公司 在通信限制期间响应寻呼的***和方法
CN101820616A (zh) * 2009-02-26 2010-09-01 中兴通讯股份有限公司 用户设备及其寻呼处理方法、无线网络控制器

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110547006A (zh) * 2017-04-28 2019-12-06 Oppo广东移动通信有限公司 无线通信的方法、网络设备和终端设备
CN111372310A (zh) * 2020-03-16 2020-07-03 展讯通信（上海）有限公司 一种寻呼管理方法及相关产品
CN111372310B (zh) * 2020-03-16 2022-12-27 展讯通信（上海）有限公司 一种寻呼管理方法及相关产品
CN114845393A (zh) * 2020-09-16 2022-08-02 北京小米移动软件有限公司 发送、接收寻呼消息的方法、装置、设备及存储介质
CN114845393B (zh) * 2020-09-16 2024-02-13 北京小米移动软件有限公司 发送、接收寻呼消息的方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN107409382A (zh) 2017-11-28

Similar Documents

Publication Publication Date Title
JP7213359B2 (ja) 無線通信方法、端末装置及びネットワーク装置
US20220386184A1 (en) Mobility management method, terminal, and base station
WO2017049442A1 (zh) 一种寻呼设备和方法
JP7123152B2 (ja) Ｒｒｃインアクティブ状態における測定の一時停止／再開
US12041549B2 (en) Terminal energy-saving method, base station, terminal, terminal energy-saving system and computer-readable storage medium
KR102200982B1 (ko) Ue의 상태 전환 방법 및 장치
KR102240644B1 (ko) 데이터 전송/수신 장치 및 방법, 및 통신 시스템
US11357071B2 (en) Handling of parameters provided in release / suspend
KR102484223B1 (ko) Pdu 세션 활성화 방법, 페이징 방법 및 그의 장치
JP2019501595A (ja) 狭帯域のインターネット・オブ・シングスのためのユーザープレーンの最適化
CN109076494B (zh) 在寻呼上下文中的无线电网络节点、核心网络节点和其中执行的方法
WO2022148398A1 (zh) Ue能力信息处理方法、装置、设备及存储介质
EP3806575A1 (en) Tracking area update in rrc_inactive
WO2019024812A1 (zh) 一种邻区测量方法及装置
CN112868264B (zh) 状态转移的方法和设备
WO2018126365A1 (zh) 信息传输的方法、终端设备和网络设备
WO2018027901A1 (zh) 通信方法、终端设备和接入网设备
TWI763685B (zh) 數據傳輸的方法、接入網設備、終端設備和網絡實體
WO2021062610A1 (zh) 用于寻呼的方法和装置
WO2021012188A1 (zh) 通信处理方法及相关设备
KR20230008758A (ko) 멀티캐스트 하향 서비스의 알림 방법, 단말 디바이스 및 네트워크 디바이스
JP2023526479A (ja) 端末装置、基地局装置及び通信のための方法
CN113647128B (zh) 无线通信方法、终端设备和网络设备
WO2020019329A1 (zh) 一种寻呼消息处理方法及装置
WO2024022193A1 (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: 15904330

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: 15904330

Country of ref document: EP

Kind code of ref document: A1