WO2018082598A1 - 一种寻呼方法、基站及终端 - Google Patents

一种寻呼方法、基站及终端 Download PDF

Info

Publication number
WO2018082598A1
WO2018082598A1 PCT/CN2017/109060 CN2017109060W WO2018082598A1 WO 2018082598 A1 WO2018082598 A1 WO 2018082598A1 CN 2017109060 W CN2017109060 W CN 2017109060W WO 2018082598 A1 WO2018082598 A1 WO 2018082598A1
Authority
WO
WIPO (PCT)
Prior art keywords
paging
terminal
paging message
type
preset parameter
Prior art date
Application number
PCT/CN2017/109060
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 JP2019522558A priority Critical patent/JP6949113B2/ja
Priority to KR1020197015901A priority patent/KR102207119B1/ko
Priority to US16/345,538 priority patent/US11184873B2/en
Priority to EP17867354.7A priority patent/EP3537789B1/en
Publication of WO2018082598A1 publication Critical patent/WO2018082598A1/zh
Priority to US17/508,755 priority patent/US11963132B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/005—Transmission of information for alerting of incoming communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0247—Traffic management, e.g. flow control or congestion control based on conditions of the access network or the infrastructure network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/022—Selective call receivers
    • H04W88/023—Selective call receivers with message or information receiving capability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections

Definitions

  • the present disclosure relates to the field of wireless communications technologies, and in particular, to a paging method, a base station, and a terminal.
  • a plurality of terminal states such as a radio resource control idle state (RRC_IDLE), a radio resource control connection state (RRC_CONNECTED), a light connection, and the like, are defined in a Long Term Evolution (LTE) system.
  • RRC_IDLE radio resource control idle state
  • RRC_CONNECTED radio resource control connection state
  • LTE Long Term Evolution
  • the UE is assigned a unique identifier within a certain tracking area
  • the eNB does not save the UE context (UE context information);
  • D2D communication sidelink communication
  • the UE has an E-UTRAN-RRC connection
  • - E-UTRAN knows the cell to which the UE belongs and allocates the intra-cell UE identity C-RNTI;
  • C-RNTI C-RNTI
  • D2D communication sidelink communication
  • the UE listens to the control signaling channel for the shared data channel to see if there is a transmission on the shared data channel assigned to the UE.
  • the UE reports channel quality information and feedback information to the eNB;
  • the non-connected reception (DRX) period is controlled by the NB, and is configured according to the energy saving of the UE and the activity level of the resource utilization.
  • the state transitions supported in the LTE system include the RRC_IDLE to RRC_CONNECTED state, and the terminal needs to perform an access or re-establishment process. From the RRC_CONNECTED state, the RRC_IDLE state can be entered through the release process.
  • an Inactive state which is also called an inactive state or an inactive connection state.
  • the terminal UE
  • the terminal maintains the core network connection, but does not perform the normal operation of the air interface connection state (such as handover, uplink timing update, radio link monitoring, etc.), and does not allocate the terminal identifier directly used for air interface transmission (such as C). -RNTI), therefore it is not possible to directly perform air interface scheduling transmission.
  • the Inactive state the terminal needs to listen to the paging message to receive the call from the network side.
  • the Inactive state has the following characteristics:
  • - Mobility is performed by the terminal, and is performed by cell reselection in the radio access network (RAN) tracking area preconfigured on the network side, instead of the handover process;
  • RAN radio access network
  • the terminal is assigned a unique user identity within the RAN tracking area preconfigured on the network side.
  • the network side allocates a valid RAN identifier in a certain area for the terminal.
  • the identifier is used to identify the terminal in the Inactive state.
  • the identifier can be used to identify the terminal when the terminal or the terminal initiates the uplink access.
  • the identifier may be referred to as an Inactive UE ID, and may also be referred to as a resume UE ID.
  • the identifier is different from the globally unique IMSI or the connected terminal identifier C-RNTI, and the identifier length is between the two (for example, the length of the Inactive UE ID is 40 bits, and the length of the C-RNTI is 16 bits), and only the multiple cells or Effective in a certain area of multiple base stations (eNBs), such as If the area is exceeded, the terminal needs to update the Inactive UE ID.
  • the identifier length is between the two (for example, the length of the Inactive UE ID is 40 bits, and the length of the C-RNTI is 16 bits), and only the multiple cells or Effective in a certain area of multiple base stations (eNBs), such as If the area is exceeded, the terminal needs to update the Inactive UE ID.
  • the terminal When the terminal is in the Inactive state, there is no connection with the base station, but the paging can be received, and the service can be initiated. Entering the state can save the power of the terminal.
  • the paging When the terminal is in the Inactive state, the paging is monitored according to the paging cycle of the Inactive state, and when the terminal is in the RRC_IDLE state, the paging is monitored according to the paging cycle of the RRC_IDLE state.
  • the paging cycle of the terminal in the Inactive state is configured by the base station, and the paging cycle of the terminal in the RRC_IDLE state is configured by the core network. The relationship between the two is not certain.
  • the network side (including the base station and the core network) releases the context of the Inactive terminal for its own reasons, but does not notify the terminal, or the notification message of the air interface is lost, the status of the terminal and the network side are inconsistent.
  • the side understands that the terminal is in the IDLE state (the access layer AS and the non-access NAS layer are both IDLE), and the AS of the terminal considers itself to be in the inactive state, and the NAS of the terminal considers that it is the CONNECTED state. Because the paging period of the Inactive state and the IDLE state are different, if the network side initiates the paging of the core network, the terminal cannot receive the paging.
  • the understanding of the state of the terminal may be inconsistent between the network and the terminal, which may cause a problem in paging of the terminal in the Inactive state.
  • the technical problem to be solved by the embodiments of the present disclosure is to provide a paging method, a base station, and a terminal, which are used to avoid paging problems caused by inconsistent understanding between the network and the terminal to the terminal state when the terminal is in an inactive state.
  • the paging method provided by the embodiment of the present disclosure includes:
  • the terminal in the inactive state receives a paging message that is sent by the base station and can determine a paging type, where the paging type includes an access network initiated by the access network or a core network initiated by the core network;
  • the terminal When the paging type corresponding to the paging message is a core network paging, the terminal updates the status of the non-access NAS layer and the radio resource control RRC layer of the terminal to an idle state, and responds to the paging message. .
  • the embodiment of the present disclosure further provides another paging method, including:
  • the base station When the base station needs to initiate paging to the terminal, determining, by the base station, a paging type of the paging, where the paging type includes an access network initiated by the access network or a core network initiated by the core network;
  • the base station transmits a paging message capable of determining the paging type to the terminal.
  • the embodiment of the present disclosure further provides a terminal, including:
  • a receiving unit configured to receive, when the terminal is in an inactive state, a paging message that is sent by the base station to determine a paging type, where the paging type includes an access network initiated access network paging or a core network initiated core Web page
  • a determining unit configured to determine a paging type corresponding to the paging message
  • a first response unit configured to: when the paging type is a core network paging, the terminal updates a status of a non-access NAS layer and a radio resource control RRC layer of the terminal to an idle state, and responds to the searching Call the message.
  • the embodiment of the present disclosure further provides a base station, including:
  • a determining unit configured to determine a paging type of the paging when the paging of the terminal needs to be initiated, where the paging type includes an access network initiated by the access network or a core network initiated by the core network;
  • a sending unit configured to send, to the terminal, a paging message that can determine a paging type.
  • the embodiment of the present disclosure further provides a terminal, including a processor, a transceiver, and a memory;
  • the processor is configured to read a program in the memory and perform the following process:
  • the terminal When the terminal is in an inactive state, receiving a paging message that is sent by the base station and determining a paging type, where the paging type includes an access network initiated by the access network or a core network initiated by the core network;
  • the terminal updates the status of the non-access NAS layer and the radio resource control RRC layer of the terminal to an idle state, and responds to the paging message;
  • the transceiver is configured to receive and transmit data
  • the memory is used to store data used by the processor to perform operations.
  • the embodiment of the present disclosure further provides a base station, including a processor, a transceiver, and a memory;
  • the processor is configured to read a program in the memory and perform the following process:
  • the paging type includes an access network initiated by the access network or a core network initiated by the core network;
  • the transceiver is configured to receive and transmit data
  • the memory is used to store data used by the processor to perform operations.
  • the paging method, the base station, and the terminal provided by the embodiments of the present disclosure are in the paging non- In the process of the terminal in the active state, the terminal paging failure problem caused when the network and the terminal understand the state of the terminal are inconsistent, so that the terminal can correctly receive the paging and improve the paging success rate.
  • FIG. 1 is a schematic diagram of an application scenario of a method for wireless system area management according to some embodiments of the present disclosure
  • FIG. 2 is a schematic diagram of another application scenario of a method for wireless system area management according to some embodiments of the present disclosure
  • FIG. 3 is a schematic flowchart of a paging method according to some embodiments of the present disclosure
  • FIG. 4 is a schematic flowchart diagram of another paging method according to some embodiments of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a terminal according to some embodiments of the present disclosure.
  • FIG. 6 is another schematic structural diagram of a terminal according to some embodiments of the present disclosure.
  • FIG. 7 is a schematic structural diagram of a base station according to some embodiments of the present disclosure.
  • FIG. 8 is another schematic structural diagram of a base station according to some embodiments of the present disclosure.
  • system and “network” are used interchangeably herein.
  • B corresponding to A means that B is associated with A, and B can be determined from A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the terminal may be a mobile phone (or cell phone), or other device capable of transmitting or receiving wireless signals, including user equipment (UE), personal digital assistant (PDA), wireless modem, wireless communication device, Handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, CPE (Customer Premise Equipment) or mobile smart hotspots, smart home appliances, or other non-passengers capable of converting mobile signals into WiFi signals
  • UE user equipment
  • PDA personal digital assistant
  • WLL wireless local loop
  • CPE Customer Premise Equipment
  • smart hotspots smart home appliances
  • smart home appliances or other non-passengers capable of converting mobile signals into WiFi signals
  • the operation can spontaneously communicate with a device communicating with a mobile communication network.
  • the base station is not limited in form, and may be a Macro Base Station, a Pico Base Station, a Node B (referred to as a 3G mobile base station), or an enhanced base station (eNB).
  • the home enhanced base station (Femto eNB or Home eNode B or Home eNB or HeNB), the relay station, the access point, the RRU (Remote Radio Unit), the RRH (Remote Radio Head), and the like.
  • the base station may be replaced with other functional nodes, such as a central unit (CU, Central Unit) and a distributed unit (DU, distributed unit).
  • the embodiments of the present disclosure may be applied to the foregoing scenario.
  • the RAN side architecture in a possible networking scenario of the LTE networking and the 5G is briefly described below.
  • Figure 1 is a typical LTE architecture.
  • the base stations can communicate through the X2 interface, and the base station and the core network can communicate through the S1 interface.
  • the network side node is divided into a central unit (CU, Central Unit) and a distributed unit (DU, distributed unit), and the user side node is a terminal (UE).
  • CU central unit
  • DU distributed unit
  • UE terminal
  • FIG. 2 is an architecture that may be adopted by the future mobile communication 5G.
  • the network side node includes a central unit and a distributed unit, and one central unit controls a plurality of distributed units deployed in a certain area.
  • the cloth unit can also be called a Transmission Reception Point (TRP).
  • TRP Transmission Reception Point
  • the TRP and the terminal perform air interface transmission.
  • One or more transmission points can simultaneously serve the terminal for data transmission.
  • the terminal air interface unique identifier assigned to the terminal by the network side is used for data scheduling and transmission.
  • the identifier may be C-RNTI or TRP-RNTI.
  • the embodiments of the present disclosure may be applied to the foregoing two RAN architectures, and may also be applied to other scenarios than the foregoing scenarios.
  • the network side wireless signaling and data transceiving nodes are collectively referred to herein as base stations, including the eNB in FIG. 1 and the CU/DU in FIG. 2 (the specific sending and receiving point is TRP).
  • the unique identifier of the terminal used for the terminal connection state transmission is referred to as a terminal air interface transmission unique identifier, and the identifier is a C-RNTI C-Radio Network Temporary Identity in the legacy LTE.
  • a terminal in the inactive state is uniquely identified in the area as an Inactive UE ID.
  • some embodiments of the present disclosure provide a paging method, which is applied to a terminal side, and includes:
  • Step 31 The terminal in the inactive state receives a paging message that is sent by the base station and can determine a paging type, where the paging type includes an access network initiated by the access network or a core network initiated by the core network.
  • the core network paging is usually a paging initiated by the core network for an active state (such as RRC_CONNECTED), and the access network paging is usually a paging initiated by the base station for the terminal in an inactive state.
  • the core network paging also needs to be forwarded to the terminal through the base station.
  • the paging message sent by the base station in the embodiment of the present disclosure can be used to determine the paging type corresponding to the paging message.
  • the base station can explicitly or implicitly indicate the paging type by using a paging message.
  • Step 32 The terminal determines a paging type corresponding to the paging message.
  • Step 33 When the paging type corresponding to the paging message is a core network paging, the terminal updates the status of the non-access NAS layer and the radio resource control RRC layer of the terminal to an idle state, and responds to the Paging message.
  • the terminal in the Inactive state receives the paging of the core network
  • the NAS layer and the RRC layer are both updated to the idle state, so that the terminal behavior defined in the idle state can be performed.
  • the paging message responds, avoiding the paging problem caused by the inconsistency between the network and the terminal to the terminal state.
  • the terminal may directly respond to the paging message, initiate a connection. Connect to the recovery, establishment or reconstruction process. For example, the terminal directly responds to the paging message at the RRC layer, and initiates a connection recovery, establishment, or re-establishment process.
  • the subsequent paging response process may refer to related technologies, and details are not described herein again.
  • the base station may indicate the paging type in an explicit manner or an implicit manner.
  • the indication manners that can be adopted by some embodiments of the present disclosure are exemplified below.
  • some embodiments of the present disclosure may also adopt any manner other than the following manners that can indicate the paging type of the terminal.
  • the base station carries the indication information of the paging type in the paging message.
  • the terminal may determine, according to the indication information, a paging type corresponding to the paging message.
  • the value of the specific 1 bit indicator bit is indicated. If the value is 0, it represents the access network paging, and the value 1 represents the core network paging.
  • the terminal can determine the paging type by reading the value of the indicator bit.
  • the base station carries a preset parameter that is expressed according to a predetermined expression manner, and different expression manners of the preset parameter correspond to different paging types.
  • the terminal determines the paging type corresponding to the expression manner of the preset parameter in the paging message, and obtains the paging type of the paging message.
  • the access network paging and the core network paging respectively use different paging identifiers of the terminal
  • the access network paging uses an inactive UE ID or a resume ID
  • the core network paging can use a temporary UE identification number (S-TMSI, S-Temporary Mobile Station Identity) or International Mobile Subscrider Identification Number (IMSI).
  • S-TMSI temporary UE identification number
  • IMSI International Mobile Subscrider Identification Number
  • the terminal can determine the paging type according to the expression manner of the terminal paging identifier in the paging message.
  • the base station carries or does not carry the first preset parameter in the paging message, wherein whether the paging message carries the first preset parameter is determined according to the paging type.
  • the terminal may determine the paging type of the paging message according to whether the first preset parameter is carried in the paging message.
  • the core network page carries a core domain parameter, such as a CN-Domain parameter, to identify whether the page is a packet (PS) domain or a circuit (CS) domain page, and the access network page does not carry the parameter.
  • a core domain parameter such as a CN-Domain parameter
  • the terminal After receiving the paging message, the terminal determines whether the paging type is the core according to whether the core domain parameter is included in the paging message. Web paging or access network paging.
  • the terminal when the paging message is a core network paging, the terminal needs to update the status of the own NAS layer and the RRC layer to an idle state, and then respond to the paging message in an idle state, and perform corresponding Paging response behavior.
  • the terminal can update the state of the NAS layer and the RRC layer as follows:
  • Manner 1 The RRC layer of the terminal updates the RRC layer state to the idle state, and notifies the NAS layer to release the connection of the terminal, and the NAS layer of the terminal updates the NAS layer state to the idle state according to the notification; the terminal The RRC layer forwards the paging content of the paging message to the NAS layer, and the NAS layer receives the paging content and responds.
  • the RRC layer is used as the master, and the NAS layer is notified of the status update, and the paging content of the paging message is delivered to the NAS layer to perform the response process of the paging message in the idle state.
  • Manner 2 The RRC layer of the terminal submits the paging content of the paging message to the NAS layer, and updates the RRC layer status to an idle state; the NAS layer of the terminal receives the paging content. Thereafter, the NAS layer status is updated to an idle state, and the paging content is responded to.
  • the NAS layer after receiving the paging content submitted by the RRC layer, the NAS layer updates its own state to an idle state, and further can perform a response process of the paging message in an idle state.
  • the update of the above state can be realized by updating the state of the corresponding state machine in the layer.
  • the terminal can perform the behavior in the corresponding state, for example, responding to the paging message.
  • specific behavior reference may be made to the related definitions of related technologies, and details are not described herein.
  • the foregoing update manner is only a partial implementation manner that may be adopted by some embodiments of the present disclosure, and the terminal may also perform status update in other manners than the foregoing manner, and is not illustrated herein.
  • a paging method provided by some embodiments of the present disclosure when applied to a base station side, includes:
  • Step 41 The base station determines a paging type of the paging when the paging of the terminal needs to be initiated, and the paging type includes an access network paging initiated by the access network or a core network paging initiated by the core network.
  • the base station can determine whether the paging is a core network paging or an access network paging according to the originator of the paging.
  • Step 42 The base station sends a paging message to the terminal that can determine the paging type.
  • the paging type may be indicated to the terminal by using a paging message by referring to the above explicit or implicit indication manner.
  • the paging message when explicitly indicated, the paging message carries indication information of the paging type.
  • the base station may send a paging message carrying the indication information of the paging type to the terminal.
  • the paging message may carry preset parameters that are expressed according to a predetermined expression manner, and different expression manners of the preset parameters correspond to different paging types.
  • the base station determines, according to the paging type, a manner of expressing a preset parameter, where different expression manners of the preset parameter correspond to different paging types; The base station sends a paging message to the terminal, where the paging message carries the preset parameter expressed according to the determined expression manner.
  • the paging message may carry or not carry the first preset parameter, wherein whether the paging message carries the first preset parameter is determined according to the paging type.
  • the base station determines, according to the paging type, whether the paging message carries the first preset parameter; and then, the base station sends the first pre-carrier to the terminal. Set the paging message of the parameter.
  • the base station indicates the paging type in the sent paging message
  • the terminal in the inactive state receives both the own NAS layer and the RRC layer after receiving the paging message.
  • Update to the idle state and then respond to the paging message, so that the network side and the terminal side can complete the paging behavior of the terminal based on the same terminal state, and avoid the paging caused by the inconsistent understanding between the network and the terminal to the terminal state. problem.
  • some embodiments of the present disclosure provide a terminal, including:
  • the receiving unit 51 is configured to receive, when the terminal is in an inactive state, a paging message that is sent by the base station and can determine a paging type, where the paging type includes an access network initiated by the access network or initiated by the core network.
  • Core network paging
  • a determining unit 52 configured to determine a paging type corresponding to the paging message
  • the first response unit 53 is configured to: when the paging type is a core network paging, the terminal updates the status of the non-access NAS layer and the radio resource control RRC layer of the local terminal to an idle state, and responds to the Paging message.
  • the first response unit 53 may include:
  • a first processing unit at the RRC layer configured to update an RRC layer status of the terminal to an idle state, And notifying the NAS layer of the terminal to release the connection of the terminal, and submitting the paging content of the paging message to the NAS layer;
  • a second processing unit located at the NAS layer, configured to update the NAS layer status to an idle state according to the notification of the first response unit, and receive the paging content submitted by the first processing unit and respond.
  • the first response unit 53 may include:
  • a third processing unit located at the RRC layer, configured to deliver the paging content of the paging message to the NAS layer, and update the RRC layer status to an idle state;
  • the fourth processing unit located at the NAS layer, is configured to update the NAS layer status to an idle state after receiving the paging content submitted by the third processing unit, and respond to the paging content.
  • the foregoing terminal may further include: a second response unit, configured to: when the paging type is an access network paging, the terminal directly initiates a connection recovery, establishment, or reconstruction process by responding to the paging message.
  • a second response unit configured to: when the paging type is an access network paging, the terminal directly initiates a connection recovery, establishment, or reconstruction process by responding to the paging message.
  • the second response unit may include:
  • a fifth processing unit located at the RRC layer, configured to initiate a connection recovery, establishment, or reestablishment process in response to the paging message at the RRC layer.
  • the paging message carries indication information of the paging type.
  • the determining unit 52 is specifically configured to determine, according to the indication information, a paging type corresponding to the paging message.
  • the paging message carries a preset parameter that is expressed according to a predetermined expression manner, and different expression manners of the preset parameter correspond to different paging types.
  • the determining unit 52 is specifically configured to determine a paging type corresponding to the expression manner of the preset parameter in the paging message, and obtain a paging type of the paging message.
  • the paging message carries or does not carry the first preset parameter, wherein whether the paging message carries the first preset parameter is determined according to the paging type.
  • the determining unit 52 is specifically configured to determine, according to whether the first preset parameter is carried in the paging message, a paging type of the paging message.
  • some embodiments of the present disclosure provide another structure of the terminal, including:
  • the first transceiver 601 receives and transmits data under the control of the first processor 604. Specifically, it can receive a paging message that is sent by the base station and can determine a paging type, where the paging type includes an access network initiated connection. Incoming network paging or core network paging initiated by the core network.
  • the first processor 604 is configured to read the program in the first memory 605 and perform the following process:
  • the terminal Determining, according to the paging message received by the first transceiver 601, a paging type corresponding to the paging message; and, when the paging type corresponding to the paging message is a core network paging, the terminal
  • the status of the non-access NAS layer and the radio resource control RRC layer of the terminal is updated to an idle state, and is responsive to the paging message.
  • the bus architecture (represented by the first bus 600) can include any number of interconnected buses and bridges, the first bus 600 will include one or more processors and firsts represented by the first processor 604
  • the various circuits of the memory represented by memory 605 are linked together.
  • the first bus 600 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art and, therefore, will not be further described herein.
  • the first bus interface 603 provides an interface between the first bus 600 and the first transceiver 601.
  • the first transceiver 601 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the first processor 604 is transmitted over the wireless medium by the first transceiver 601 and the first antenna 602. Further, the first antenna 602 also receives the data and transmits the data to the first processing via the first transceiver 601. 604.
  • the first processor 604 is responsible for managing the first bus 600 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the first memory 605 can be used for data used by the first storage processor 604 when performing operations.
  • the first processor 604 can be a CPU, an ASIC, an FPGA, or a CPLD.
  • the first processor 604 is further configured to: when it is determined that the paging type corresponding to the paging message is a core network paging, control an RRC layer of the terminal, and update an RRC layer status to In the idle state, and notifying the NAS layer to release the connection of the terminal, the NAS layer of the terminal updates the NAS layer status to an idle state; and the RRC layer controlling the terminal submits the paging content of the paging message to the NAS layer. And controlling the NAS layer to receive the paging content and responding.
  • the first processor 604 is further configured to: when it is determined that the paging type corresponding to the paging message is a core network paging, control an RRC layer of the terminal, and send the paging message
  • the paging content is delivered to the NAS layer, and the RRC layer status is updated to an idle state; and the NAS layer controlling the terminal, after receiving the paging content, updating the NAS layer status to an idle state, and then responding to the Paging content.
  • the first processor 604 is further configured to: when determining that the paging type corresponding to the paging message is an access network paging, directly initiate the connection recovery, establishment, or reconstruction process by responding to the paging message. Specifically, the connection recovery, establishment, or reconstruction process may be initiated by responding to the paging message directly at the RRC layer.
  • the paging message carries the indication information of the paging type
  • the first processor 604 may determine, according to the indication information, a paging type corresponding to the paging message.
  • the paging message carries a preset parameter that is expressed according to a predetermined expression manner, and different expression manners of the preset parameter correspond to different paging types, and the first processor 604 The paging type corresponding to the expression manner of the preset parameter in the paging message may be determined, and the paging type of the paging message is obtained.
  • the paging message carries or does not carry a first preset parameter, where whether the paging message carries the first preset parameter is determined according to the paging type, and the first processing The 604 may determine, according to whether the first preset parameter is carried in the paging message, a paging type of the paging message.
  • a base station including:
  • the determining unit 71 is configured to determine a paging type of the paging when the paging of the terminal needs to be initiated, where the paging type includes an access network initiated access network paging or a core network initiated core network paging. ;
  • the sending unit 72 is configured to send, to the terminal, a paging message that can determine a paging type.
  • the paging message carries the indication information of the paging type, or the paging message carries a preset parameter that is expressed according to a predetermined expression manner, and different expression manners of the preset parameter Corresponding to different paging types, or the paging message carries or does not carry the first preset parameter, wherein whether the paging message carries the first preset parameter is determined according to the paging type.
  • some embodiments of the present disclosure provide another structure of a base station, including:
  • the second transceiver 801 receives and transmits data under the control of the second processor 804. Specifically, the paging message capable of determining the paging type may be sent to the terminal.
  • the second processor 804 is configured to read the program in the second memory 805 and perform the following process:
  • the second transceiver 801 transmits to the terminal a paging message capable of determining a paging type.
  • the bus architecture (represented by the second bus 800) can include any number of interconnected buses and bridges, and the second bus 800 will include one or more processors and seconds represented by the second processor 804.
  • the various circuits of the memory represented by memory 805 are linked together.
  • the second bus 800 can also The linking of various other circuits, such as peripherals, voltage regulators, and power management circuits, is well known in the art and, therefore, will not be further described herein.
  • the second bus interface 803 provides an interface between the second bus 800 and the second transceiver 801.
  • the second transceiver 801 can be an element or a plurality of elements, such as a plurality of receivers and transmitters, providing means for communicating with various other devices on a transmission medium.
  • the data processed by the second processor 804 is transmitted over the wireless medium by the second transceiver 801 and the second antenna 802. Further, the second antenna 802 also receives the data and transmits the data to the second processing via the second transceiver 801. 804.
  • the second processor 804 is responsible for managing the second bus 800 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions.
  • the second memory 805 can be used for data used by the second storage processor 804 when performing operations.
  • the second processor 804 can be a CPU, an ASIC, an FPGA, or a CPLD.
  • the paging method, the base station, and the terminal provided by the embodiments of the present disclosure can solve the problem of terminal paging failure caused by the inconsistency between the network and the terminal to the terminal state in the process of paging the inactive terminal.
  • the terminal can correctly receive the paging, which improves the paging success rate.
  • 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

本公开提供了一种寻呼方法、基站及终端。所述寻呼方法包括：处于非激活态的终端，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；所述终端确定所述寻呼消息对应的寻呼类型；在所述寻呼消息对应的寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息。

Description

一种寻呼方法、基站及终端
相关申请的交叉引用
本申请主张在2016年11月3日在中国提交的中国专利申请号No.201610955201.6的优先权，其全部内容通过引用包含于此。
技术领域
本公开涉及无线通信技术领域，具体涉及一种寻呼方法、基站及终端。
背景技术
长期演进(LTE)***中定义了多个终端状态，如无线资源控制空闲态(RRC_IDLE)、无线资源控制连接态(RRC_CONNECTED)、轻连接(light connection)等。随着无线通信***的发展，终端类型和业务类型多样化，终端省电、节约网络资源和满足各种业务类型的需求并存。下面介绍各种状态下终端可执行的行为。
1、RRC_IDLE下可以执行的UE行为：
-PLMN选择；
-NAS配置DRX；
-***信息广播；
-寻呼；
-Cell重选方式的移动性；
-UE被分配一个在一定跟踪区域内唯一的标识；
-eNB不保存UE context(UE上下文信息)；
-可以进行sidelink通信的发送接收(D2D通信)；
-Sidelink发现的通知和监听(D2D发现)。
2、RRC_CONNECTED下可以执行的UE行为：
-UE有E-UTRAN-RRC的连接；
-E-UTRAN侧有UE的上下文信息；
-E-UTRAN知道UE所属的小区并分配小区内UE标识C-RNTI；
-Network和UE间可以利用C-RNTI收发数据；
-Network控制的移动性；
-邻小区测量；
-可以进行sidelink通信的发送接收(D2D通信)；
-Sidelink发现的通知和监听(D2D发现)；
-PDCP/RLC/MAC层：
-UE与网络间进行收发数据；
-UE监听关于共享数据信道的控制信令信道以便查看是否有分配给该UE的共享数据信道上的传输。
-UE上报信道质量信息和反馈信息给eNB；
-非连接接收(DRX)周期由而NB控制，根据UE节能以及资源利用率的活跃程度来配置。
LTE***中支持的状态跃迁，包括从RRC_IDLE到RRC_CONNECTED状态，终端需要进行接入或者重建过程；从RRC_CONNECTED状态，则可以通过释放过程进入到RRC_IDLE状态。
为了同时保证终端省电和快速数据传输，目前引入了一种终端状态：Inactive状态，该Inactive状态又被称为非激活态或不活跃连接态。这种状态下终端(UE)保持核心网连接，但不进行空口连接态的常规操作(如切换、上行定时更新、无线链路监控等)，不分配直接用于空口传输的终端标识(如C-RNTI)，因此不能直接进行空口调度传输。在Inactive状态下，终端需要监听寻呼消息，以接收来自网络侧的呼叫。Inactive状态则有着以下特点：
-核心网看该终端处于连接状态；
-移动性是终端执行的，在网络侧预配置的无线接入网(RAN)跟踪区域内，通过小区重选来执行，而不是切换过程进行；
-终端被分配了在网络侧预配置的RAN跟踪区域内的唯一用户标识。
Inactive状态下，网络侧为终端分配一定区域内有效的RAN标识，该标识用于在Inactive状态下识别终端，可以在网络侧查找终端或终端主动发起上行接入时用该标识作为身份识别进入连接态，该标识可以称为Inactive UE ID，也可以称为resume UE ID。该标识不同于全球唯一的IMSI或连接态终端标识C-RNTI，该标识长度介于两者之间(例如Inactive UE ID长度为40bit，C-RNTI长度为16bit)，只在包含多个小区或多个基站(eNB)的一定区域内有效，如 果超过该区域，终端需要更新Inactive UE ID。
当终端在Inactive状态时，与基站之间没有连接，但是可以接收寻呼，可以发起业务，进入该状态可以起到节省终端电量的作用。终端在Inactive状态时，根据Inactive状态的寻呼周期来监听寻呼，而终端在RRC_IDLE态时，根据RRC_IDLE态的寻呼周期来监听寻呼。终端在Inactive状态时的寻呼周期为基站配置的，而终端在RRC_IDLE态时的寻呼周期，是核心网配置的。二者之间的关系没有确定。
如果网络侧(包括基站和核心网)因为自身原因释放了Inactive终端的上下文，但是却没通知给终端，或者在空口对终端的通知消息丢失，则会导致终端和网络侧的状态理解不一致，网络侧理解终端为IDLE态(接入层AS和非接入NAS层都是IDLE)，而终端的AS认为自己是Inactive态，终端的NAS认为自己是CONNECTED态。因为Inactive状态和IDLE态的寻呼周期不同，此时如果网络侧发起核心网寻呼，会导致终端无法收到该寻呼。
可以看出，在终端处于非激活态(Inactive)时，由于网络与终端对终端状态的理解可能不一致，因此可能导致Inactive状态下的终端的寻呼出现问题。
发明内容
本公开实施例要解决的技术问题是提供一种寻呼方法、基站及终端，用于在终端处于非激活态时，避免因为网络与终端对终端状态理解不一致所导致的寻呼问题。
为解决上述技术问题，本公开实施例提供的寻呼方法，包括：
处于非激活态的终端，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
所述终端确定所述寻呼消息对应的寻呼类型；
在所述寻呼消息对应的寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息。
本公开实施例还提供了另一种寻呼方法，包括：
基站在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
基站向所述终端发送能够确定寻呼类型的寻呼消息。
本公开实施例还提供了一种终端，包括：
接收单元，用于在本终端处于非激活态时，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
确定单元，用于确定所述寻呼消息对应的寻呼类型；
第一响应单元，用于在所述寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息。
本公开实施例还提供了一种基站，包括：
确定单元，用于在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
发送单元，用于向所述终端发送能够确定寻呼类型的寻呼消息。
本公开实施例还提供了一种终端，包括处理器、收发机和存储器；
其中，所述处理器用于读取所述存储器中的程序，执行下列过程：
在本终端处于非激活态时，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
确定所述寻呼消息对应的寻呼类型；
在所述寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息；
所述收发机用于接收和发送数据；
所述存储器用于保存所述处理器执行操作时所使用的数据。
本公开实施例还提供了一种基站，包括处理器、收发机和存储器；
其中，所述处理器用于读取所述存储器中的程序，执行下列过程：
在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
向所述终端发送能够确定寻呼类型的寻呼消息；
所述收发机用于接收和发送数据；
所述存储器用于保存所述处理器执行操作时所使用的数据。
与相关技术相比，本公开实施例提供的寻呼方法、基站及终端，在寻呼非 激活态的终端的过程中，可以解决当网络与终端对终端状态理解不一致时所导致的终端寻呼失败问题，使终端可以正确接收到寻呼，提高了寻呼成功率。
附图说明
图1为本公开的一些实施例无线***区域管理的方法的一种应用场景的示意图；
图2为本公开的一些实施例无线***区域管理的方法的另一应用场景的示意图；
图3为本公开的一些实施例提供的一种寻呼方法的流程示意图；
图4为本公开的一些实施例提供的另一种寻呼方法的流程示意图；
图5为本公开的一些实施例提供的终端的一种结构示意图；
图6为本公开的一些实施例提供的终端的另一结构示意图；
图7为本公开的一些实施例提供的基站的结构示意图；
图8为本公开的一些实施例提供的基站的另一结构示意图。
具体实施方式
为使本公开要解决的技术问题、技术方案和优点更加清楚，下面将结合附图及具体实施例进行详细描述。在下面的描述中，提供诸如具体的配置和组件的特定细节仅仅是为了帮助全面理解本公开的实施例。因此，本领域技术人员应该清楚，可以对这里描述的实施例进行各种改变和修改而不脱离本公开的范围和精神。另外，为了清楚和简洁，省略了对已知功能和构造的描述。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本公开的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。
在本公开的各种实施例中，应理解，下述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本公开实施例的实施过程构成任何限定。
另外，本文中术语“***”和“网络”在本文中常可互换使用。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
在本申请所提供的实施例中，应理解，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本公开的一些实施例中，终端可以是移动电话(或手机)，或者其他能够发送或接收无线信号的设备，包括用户设备(UE)、个人数字助理(PDA)、无线调制解调器、无线通信装置、手持装置、膝上型计算机、无绳电话、无线本地回路(WLL)站、能够将移动信号转换为WiFi信号的CPE(Customer Premise Equipment，客户终端)或移动智能热点、智能家电、或其他不通过人的操作就能自发与移动通信网络通信的设备等。
本公开的一些实施例中，所述基站的形式不限，可以是宏基站(Macro Base Station)、微基站(Pico Base Station)、Node B(3G移动基站的称呼)、增强型基站(eNB)、家庭增强型基站(Femto eNB或Home eNode B或Home eNB或HeNB)、中继站、接入点、RRU(Remote Radio Unit，远端射频模块)、RRH(Remote Radio Head，射频拉远头)等。另外，随着5G技术的发展，基站可能替换为其他功能节点，如中央单元(CU，Central Unit)和分布式单元(DU，Distributed Unit)。本公开实施例可以应用于上述场景，下面将简单介绍其中的LTE组网和5G的一种可能组网场景中的RAN侧架构。
LTE组网场景：基站+终端
图1是典型的LTE架构。基站(eNB)下有多个小区(cell)，连接态的终端(UE)与小区进行空口数据收发，连接态的UE被分配小区内唯一的UE标识(C-RNTI)。基站之间可以通过X2接口通信，基站与核心网之间可以通过S1接口通信。
5G组网场景：网络侧节点分为中央单元(CU，Central Unit)和分布式单元(DU，Distributed Unit)，用户侧节点为终端(UE)。
图2是未来移动通信5G可能采用的一种架构，网络侧节点包括中央单元和分布式单元，一个中央单元控制一定区域内部署的多个分布式单元，这些分 布式单元也可以被称为传输点(TRP，Transmission Reception Point)。TRP与终端进行空口传输。一个或多个传输点可以同时为终端服务，进行数据传输，这里也需要通过网络侧为终端分配的终端空口唯一标识来进行数据调度和传输，这个标识可以是C-RNTI或TRP-RNTI。
本公开实施例可以应用于上述两种RAN架构，也可以应用于除上述场景外的其他场景。为统一描述，本文中将网络侧无线信令和数据收发节点都统称为基站，包括图1中的eNB以及图2中的CU/DU(具体收发点为TRP)。另外，本文中将用于终端连接态传输的终端唯一标识称为终端空口传输唯一标识，该标识在传统LTE中即为小区无线网络临时标识(C-RNTI C-Radio Network Temporary Identity)。Inactive态的终端在区域内唯一标识称为Inactive UE ID。
请参照图3，本公开的一些实施例提供了一种寻呼方法，应用于终端侧，包括：
步骤31，处于非激活态的终端，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼。
这里，核心网寻呼通常是核心网针对激活态(如RRC_CONNECTED)的终端发起的寻呼，接入网寻呼通常是基站针对非激活态的终端发起的寻呼。当然，核心网寻呼也需要通过基站转发给终端。本公开实施例中基站发送的寻呼消息能够用于确定该寻呼消息对应的寻呼类型，具体的，基站可以通过寻呼消息，显式或隐式指示寻呼类型。
步骤32，所述终端确定所述寻呼消息对应的寻呼类型。
步骤33，在所述寻呼消息对应的寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息。
通过以上步骤，本公开的一些实施例中，当Inactive态的终端接收到核心网寻呼时，将自身NAS层和RRC层都更新为空闲态，从而可以按照空闲态下定义的终端行为，对寻呼消息进行响应，避免了因为网络与终端对终端状态理解不一致所导致的寻呼问题。
本公开的一些实施例中，如果在上述步骤32中，确定所述寻呼消息对应的寻呼类型为接入网寻呼时，则所述终端可以直接响应所述寻呼消息，发起连 接恢复、建立或重建过程。例如，所述终端直接在RRC层响应所述寻呼消息，发起连接恢复、建立或重建过程，后续寻呼响应过程可以参考相关技术，此处不再赘述。
本公开的一些实施例中，基站可以通过显式方式或隐式方式，指示寻呼类型。下面对本公开的一些实施例可以采用的指示方式进行举例说明，当然，本公开的一些实施例还可以采用以下方式以外的其他任何能够指示终端寻呼类型的方式。
1)显式指示
基站在所述寻呼消息携带所述寻呼类型的指示信息，此时，在步骤32中，所述终端根据所述指示信息，可以确定所述寻呼消息对应的寻呼类型。
例如，通过特定的1bit的指示位的值进行指示，如值为0时代表接入网寻呼，值为1时代表核心网寻呼。终端通过读取该指示位的值，即可确定寻呼类型。
2)隐式指示
2.1)基站在所述寻呼消息中携带有按照预先确定的表达方式表示的预设参数，且所述预设参数的不同表达方式对应于不同的寻呼类型。此时，在步骤32中，所述终端确定所述寻呼消息中的预设参数的表达方式所对应的寻呼类型，可以得到所述寻呼消息的寻呼类型。
例如，接入网寻呼和核心网寻呼分别使用终端不同的寻呼标识，接入网寻呼使用inactive UE ID或者resume ID，而核心网寻呼可以使用临时UE识别号(S-TMSI，S-Temporary Mobile Station Identity)或者国际移动用户识别码(IMSI，International Mobile Subscrider Identification Number)。终端根据寻呼消息中的终端寻呼标识的表达方式，可以确定寻呼类型。
2.2)基站在所述寻呼消息中携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的。此时，在步骤32中，终端根据所述寻呼消息中是否携带所述第一预设参数，可以确定所述寻呼消息的寻呼类型。
例如，核心网寻呼携带核心网域参数，如CN-Domain参数，标识该寻呼是分组(PS)域还是电路(CS)域寻呼，而接入网寻呼不携带该参数。终端接收到寻呼消息后，根据寻呼消息中是否有该核心网域参数，确定寻呼类型为核心 网寻呼或接入网寻呼。
在上述步骤33中，当所述寻呼消息为核心网寻呼时，终端需要将自身NAS层和RRC层的状态更新为空闲态，进而在空闲态下响应所述寻呼消息，执行对应的寻呼响应行为。例如，终端可以按照以下方式更新NAS层和RRC层的状态：
方式1：所述终端的RRC层，将RRC层状态更新为空闲态，并通知NAS层释放所述终端的连接，终端的NAS层根据所述通知将NAS层状态更新为空闲态；所述终端的RRC层将所述寻呼消息的寻呼内容递交给NAS层，所述NAS层接收所述寻呼内容并进行响应。
在上述方式1中，由RRC层作为主导，通知NAS层进行状态更新，并将寻呼消息的寻呼内容递交给NAS层，以在空闲态下进行寻呼消息的响应过程。
方式2：所述终端的RRC层，将所述寻呼消息的寻呼内容递交给NAS层，以及，将RRC层状态更新为空闲态；所述终端的NAS层，接收到所述寻呼内容后，将NAS层状态更新为空闲态，以及，响应所述寻呼内容。
在上述方式2中，NAS层收到RRC层递交的寻呼内容后，将自身状态更新为空闲态，进而可以在空闲态下进行寻呼消息的响应过程。
以上状态的更新，可以通过更新层中对应的状态机的状态来实现。在状态机的不同状态下，终端可以执行对应状态下的行为，例如，对寻呼消息进行响应，具体行为可以参考相关技术的标准的相关定义，本文不再赘述。
需要指出的是，以上更新方式仅为本公开的一些实施例可以采用的部分实现方式，终端也可以按照以上方式之外的其他方式进行状态更新，此处不再一一举例说明。
请参照图4，本公开的一些实施例提供的寻呼方法，在应用于基站侧时，包括：
步骤41，基站在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼。
这里，基站可以根据寻呼的发起者，来确定寻呼为核心网寻呼或接入网寻呼。
步骤42，基站向所述终端发送能够确定寻呼类型的寻呼消息。
这里，可以参照上文的显式或隐式的指示方式，通过寻呼消息向终端指示寻呼类型。
例如，在显式指示时，所述寻呼消息携带有所述寻呼类型的指示信息。此时，在上述步骤42中，所述基站可以向所述终端发送携带有所述寻呼类型的指示信息的寻呼消息。
例如，在隐式指示时，所述寻呼消息中可以携带有按照预先确定的表达方式表示的预设参数，且所述预设参数的不同表达方式对应于不同的寻呼类型。此时，在上述步骤42中，所述基站根据所述寻呼类型，确定预设参数的表达方式，其中，所述预设参数的不同表达方式对应于不同的寻呼类型；然后，所述基站向所述终端发送寻呼消息，所述寻呼消息携带有按照所确定的表达方式表示的所述预设参数。
又例如，在隐式指示时，所述寻呼消息中可以携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的。此时，在上述步骤42中，所述基站根据所述寻呼类型，确定所述寻呼消息是否携带第一预设参数；然后，所述基站向所述终端发送携带或未携带第一预设参数的寻呼消息。
从上文可以看出，本公开的一些实施例中，基站在发送的寻呼消息中指示寻呼类型，处于非激活态的终端在收到寻呼消息后，将自身NAS层和RRC层都更新为空闲态，再对寻呼消息进行响应，从而可以保证网络侧与终端侧能够基于相同的终端状态完成终端的寻呼行为，避免了因网络与终端对终端状态理解不一致所导致的寻呼问题。
下面将进一步提供实现上述方法的基站和终端。
请参照图5，本公开的一些实施例提供了一种终端，包括：
接收单元51，用于在本终端处于非激活态时，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
确定单元52，用于确定所述寻呼消息对应的寻呼类型；
第一响应单元53，用于在所述寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息。
作为一种实现方式，所述第一响应单元53可以包括：
位于RRC层的第一处理单元，用于将所述终端的RRC层状态更新为空闲态， 并通知所述终端的NAS层释放所述终端的连接，以及，将所述寻呼消息的寻呼内容递交给NAS层；
位于NAS层的第二处理单元，用于根据所述第一响应单元的通知将NAS层状态更新为空闲态，以及，接收到第一处理单元递交的寻呼内容并进行响应。
作为另一种实现方式，所述第一响应单元53可以包括：
位于RRC层的第三处理单元，用于将所述寻呼消息的寻呼内容递交给NAS层，以及，将RRC层状态更新为空闲态；
位于NAS层的第四处理单元，用于接收到所述第三处理单元递交的所述寻呼内容后，将NAS层状态更新为空闲态，以及，响应所述寻呼内容。
这里，上述终端还可以包括：第二响应单元，用于在所述寻呼类型为接入网寻呼时，所述终端直接响应所述寻呼消息，发起连接恢复、建立或重建过程。
具体的，所述第二响应单元可以包括：
位于RRC层的第五处理单元，用于在RRC层响应所述寻呼消息，发起连接恢复、建立或重建过程。
作为一种实现方式，所述寻呼消息携带有所述寻呼类型的指示信息。此时，所述确定单元52，具体用于根据所述指示信息，确定所述寻呼消息对应的寻呼类型。
作为另一种实现方式，所述寻呼消息中携带有按照预先确定的表达方式表示的预设参数，且所述预设参数的不同表达方式对应于不同的寻呼类型。此时，所述确定单元52，具体用于确定所述寻呼消息中的预设参数的表达方式所对应的寻呼类型，得到所述寻呼消息的寻呼类型。
作为又一种实现方式，所述寻呼消息中携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的。此时，所述确定单元52，具体用于根据所述寻呼消息中是否携带所述第一预设参数，确定所述寻呼消息的寻呼类型。
请参照图6，本公开的一些实施例提供了终端的另一种结构，包括：
第一收发机601，在第一处理器604的控制下接收和发送数据，具体的，可以接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼。
第一处理器604，用于读取第一存储器605中的程序，执行下列过程：
根据第一收发机601接收到的寻呼消息，确定所述寻呼消息对应的寻呼类型；以及，在所述寻呼消息对应的寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息。
在图6中，总线架构(用第一总线600来代表)可以包括任意数量的互联的总线和桥，第一总线600将包括由第一处理器604代表的一个或多个处理器和第一存储器605代表的存储器的各种电路链接在一起。第一总线600还可以将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。第一总线接口603在第一总线600和第一收发机601之间提供接口。第一收发机601可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经第一处理器604处理的数据通过第一收发机601和第一天线602在无线介质上进行传输，进一步，第一天线602还接收数据并将数据经由第一收发机601传送给第一处理器604。
第一处理器604负责管理第一总线600和通常的处理，还可以提供各种功能，包括定时，***接口，电压调节、电源管理以及其他控制功能。而第一存储器605可以被用于第一存储处理器604在执行操作时所使用的数据。具体的，第一处理器604可以是CPU、ASIC、FPGA或CPLD。
作为一种实现方式，第一处理器604还可以用于在判断出在所述寻呼消息对应的寻呼类型为核心网寻呼时，控制所述终端的RRC层，将RRC层状态更新为空闲态，并通知NAS层释放所述终端的连接，终端的NAS层将NAS层状态更新为空闲态；以及，控制所述终端的RRC层将所述寻呼消息的寻呼内容递交给NAS层，以及，控制所述NAS层接收所述寻呼内容并进行响应。
作为一种实现方式，第一处理器604还可以用于在判断出在所述寻呼消息对应的寻呼类型为核心网寻呼时，控制所述终端的RRC层，将所述寻呼消息的寻呼内容递交给NAS层，并将RRC层状态更新为空闲态；以及控制所述终端的NAS层，接收到所述寻呼内容后，将NAS层状态更新为空闲态，然后响应所述寻呼内容。
第一处理器604还可以用于在判断出在所述寻呼消息对应的寻呼类型为接入网寻呼时，可以直接响应所述寻呼消息，发起连接恢复、建立或重建过程。 具体的，可以直接在RRC层响应所述寻呼消息，发起连接恢复、建立或重建过程。
作为一种实现方式，所述寻呼消息携带有所述寻呼类型的指示信息，第一处理器604可以根据所述指示信息，确定所述寻呼消息对应的寻呼类型。作为另一种实现方式，所述寻呼消息中携带有按照预先确定的表达方式表示的预设参数，且所述预设参数的不同表达方式对应于不同的寻呼类型，第一处理器604可以确定所述寻呼消息中的预设参数的表达方式所对应的寻呼类型，得到所述寻呼消息的寻呼类型。作为又一种实现方式，所述寻呼消息中携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的，第一处理器604可以根据所述寻呼消息中是否携带所述第一预设参数，确定所述寻呼消息的寻呼类型。
请参照图7，本公开的一些实施例提供了一种基站，包括：
确定单元71，用于在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
发送单元72，用于向所述终端发送能够确定寻呼类型的寻呼消息。
这里，所述寻呼消息携带有所述寻呼类型的指示信息，或者，所述寻呼消息中携带有按照预先确定的表达方式表示的预设参数，且所述预设参数的不同表达方式对应于不同的寻呼类型，或者，所述寻呼消息中携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的。
请参照图8，本公开的一些实施例提供了基站的另一种结构，包括：
第二收发机801，在第二处理器804的控制下接收和发送数据，具体的，可以向终端发送能够确定寻呼类型的寻呼消息。
第二处理器804，用于读取第二存储器805中的程序，执行下列过程：
在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；以及，控制所述第二收发机801向所述终端发送能够确定寻呼类型的寻呼消息。
在图8中，总线架构(用第二总线800来代表)可以包括任意数量的互联的总线和桥，第二总线800将包括由第二处理器804代表的一个或多个处理器和第二存储器805代表的存储器的各种电路链接在一起。第二总线800还可以 将诸如***设备、稳压器和功率管理电路等之类的各种其他电路链接在一起，这些都是本领域所公知的，因此，本文不再对其进行进一步描述。第二总线接口803在第二总线800和第二收发机801之间提供接口。第二收发机801可以是一个元件，也可以是多个元件，比如多个接收器和发送器，提供用于在传输介质上与各种其他装置通信的单元。经第二处理器804处理的数据通过第二收发机801和第二天线802在无线介质上进行传输，进一步，第二天线802还接收数据并将数据经由第二收发机801传送给第二处理器804。
第二处理器804负责管理第二总线800和通常的处理，还可以提供各种功能，包括定时，***接口，电压调节、电源管理以及其他控制功能。而第二存储器805可以被用于第二存储处理器804在执行操作时所使用的数据。具体的额，第二处理器804可以是CPU、ASIC、FPGA或CPLD。
综上，本公开实施例提供的寻呼方法、基站及终端，在寻呼非激活态的终端的过程中，可以解决当网络与终端对终端状态理解不一致时所导致的终端寻呼失败问题，使终端可以正确接收到寻呼，提高了寻呼成功率。
本公开是参照根据本公开的一些实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述是本公开的优选实施方式，应当指出，对于本技术领域的普通技术人员来说，在不脱离本公开所述原理的前提下，还可以做出若干改进和润饰，这些改进和润饰也应视为本公开的保护范围。

Claims (20)

  1. 一种寻呼方法，包括：
    处于非激活态的终端，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
    所述终端确定所述寻呼消息对应的寻呼类型；
    在所述寻呼消息对应的寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息。
  2. 如权利要求1所述的方法，其中，
    所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息的步骤，包括：
    所述终端的RRC层，将RRC层状态更新为空闲态，并通知NAS层释放所述终端的连接，终端的NAS层将NAS层状态更新为空闲态；
    所述终端的RRC层将所述寻呼消息的寻呼内容递交给NAS层，所述NAS层接收所述寻呼内容并进行响应。
  3. 如权利要求1所述的方法，其中，
    所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息的步骤，包括：
    所述终端的RRC层，将所述寻呼消息的寻呼内容递交给NAS层，以及，将RRC层状态更新为空闲态；
    所述终端的NAS层，接收到所述寻呼内容后，将NAS层状态更新为空闲态，以及，响应所述寻呼内容。
  4. 如权利要求1所述的方法，还包括：
    在所述寻呼消息对应的寻呼类型为接入网寻呼时，所述终端直接响应所述寻呼消息，发起连接恢复、建立或重建过程。
  5. 如权利要求1所述的方法，其中，
    所述寻呼消息携带有所述寻呼类型的指示信息；
    所述终端确定所述寻呼消息对应的寻呼类型的步骤，包括：
    所述终端根据所述指示信息，确定所述寻呼消息对应的寻呼类型。
  6. 如权利要求1所述的方法，其中，
    所述寻呼消息中携带有按照预先确定的表达方式表示的预设参数，且所述 预设参数的不同表达方式对应于不同的寻呼类型；
    所述终端确定所述寻呼消息对应的寻呼类型的步骤，包括：
    所述终端确定所述寻呼消息中的预设参数的表达方式所对应的寻呼类型，得到所述寻呼消息的寻呼类型。
  7. 如权利要求1所述的方法，其中，
    所述寻呼消息中携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的；
    所述终端确定所述寻呼消息对应的寻呼类型的步骤，包括：
    所述终端根据所述寻呼消息中是否携带所述第一预设参数，确定所述寻呼消息的寻呼类型。
  8. 一种寻呼方法，包括：
    基站在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
    基站向所述终端发送能够确定寻呼类型的寻呼消息。
  9. 如权利要求8所述的方法，其中，
    所述寻呼消息携带有所述寻呼类型的指示信息；
    或者，所述寻呼消息中携带有按照预先确定的表达方式表示的预设参数，且所述预设参数的不同表达方式对应于不同的寻呼类型；
    或者，所述寻呼消息中携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的。
  10. 一种终端，包括：
    接收单元，用于在本终端处于非激活态时，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
    确定单元，用于确定所述寻呼消息对应的寻呼类型；
    第一响应单元，用于在所述寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息。
  11. 如权利要求10所述的终端，其中，所述第一响应单元包括：
    位于RRC层的第一处理单元，用于将所述终端的RRC层状态更新为空闲态， 并通知所述终端的NAS层释放所述终端的连接，以及，将所述寻呼消息的寻呼内容递交给NAS层；
    位于NAS层的第二处理单元，用于根据所述第一响应单元的通知将NAS层状态更新为空闲态，以及，接收到第一处理单元递交的寻呼内容并进行响应。
  12. 如权利要求10所述的终端，其中，所述第一响应单元包括：
    位于RRC层的第三处理单元，用于将所述寻呼消息的寻呼内容递交给NAS层，以及，将RRC层状态更新为空闲态；
    位于NAS层的第四处理单元，用于接收到所述第三处理单元递交的所述寻呼内容后，将NAS层状态更新为空闲态，以及，响应所述寻呼内容。
  13. 如权利要求10所述的终端，还包括：
    第二响应单元，用于在所述寻呼类型为接入网寻呼时，所述终端直接响应所述寻呼消息，发起连接恢复、建立或重建过程。
  14. 如权利要求10所述的终端，其中，
    所述寻呼消息携带有所述寻呼类型的指示信息；
    所述确定单元，具体用于根据所述指示信息，确定所述寻呼消息对应的寻呼类型。
  15. 如权利要求10所述的终端，其中，
    所述寻呼消息中携带有按照预先确定的表达方式表示的预设参数，且所述预设参数的不同表达方式对应于不同的寻呼类型；
    所述确定单元，具体用于确定所述寻呼消息中的预设参数的表达方式所对应的寻呼类型，得到所述寻呼消息的寻呼类型。
  16. 如权利要求10所述的终端，其中，
    所述寻呼消息中携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的；
    所述确定单元，具体用于根据所述寻呼消息中是否携带所述第一预设参数，确定所述寻呼消息的寻呼类型。
  17. 一种基站，包括：
    确定单元，用于在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
    发送单元，用于向所述终端发送能够确定寻呼类型的寻呼消息。
  18. 如权利要求17所述的基站，其中，
    所述寻呼消息携带有所述寻呼类型的指示信息；
    或者，所述寻呼消息中携带有按照预先确定的表达方式表示的预设参数，且所述预设参数的不同表达方式对应于不同的寻呼类型；
    或者，所述寻呼消息中携带或未携带第一预设参数，其中，所述寻呼消息是否携带第一预设参数是根据所述寻呼类型确定的。
  19. 一种终端，包括处理器、收发机和存储器；
    其中，所述处理器用于读取所述存储器中的程序，执行下列过程：
    在本终端处于非激活态时，接收基站发送的能够确定寻呼类型的寻呼消息，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
    确定所述寻呼消息对应的寻呼类型；
    在所述寻呼类型为核心网寻呼时，所述终端将本终端的非接入NAS层和无线资源控制RRC层的状态更新为空闲态，并响应所述寻呼消息；
    所述收发机用于接收和发送数据；
    所述存储器用于保存所述处理器执行操作时所使用的数据。
  20. 一种基站，包括处理器、收发机和存储器；
    其中，所述处理器用于读取所述存储器中的程序，执行下列过程：
    在需要发起对终端的寻呼时，确定该寻呼的寻呼类型，所述寻呼类型包括接入网发起的接入网寻呼或核心网发起的核心网寻呼；
    向所述终端发送能够确定寻呼类型的寻呼消息；
    所述收发机用于接收和发送数据；
    所述存储器用于保存所述处理器执行操作时所使用的数据。
PCT/CN2017/109060 2016-11-03 2017-11-02 一种寻呼方法、基站及终端 WO2018082598A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
JP2019522558A JP6949113B2 (ja) 2016-11-03 2017-11-02 ページング方法、基地局および端末
KR1020197015901A KR102207119B1 (ko) 2016-11-03 2017-11-02 페이징 방법, 기지국 및 단말기
US16/345,538 US11184873B2 (en) 2016-11-03 2017-11-02 Paging method, base station and user equipment
EP17867354.7A EP3537789B1 (en) 2016-11-03 2017-11-02 Paging method, base station and terminal
US17/508,755 US11963132B2 (en) 2016-11-03 2021-10-22 Paging method, base station and user equipment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610955201.6 2016-11-03
CN201610955201.6A CN108024221B (zh) 2016-11-03 2016-11-03 一种寻呼方法、基站及终端

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US16/345,538 A-371-Of-International US11184873B2 (en) 2016-11-03 2017-11-02 Paging method, base station and user equipment
US17/508,755 Continuation US11963132B2 (en) 2016-11-03 2021-10-22 Paging method, base station and user equipment

Publications (1)

Publication Number Publication Date
WO2018082598A1 true WO2018082598A1 (zh) 2018-05-11

Family

ID=62076731

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/109060 WO2018082598A1 (zh) 2016-11-03 2017-11-02 一种寻呼方法、基站及终端

Country Status (6)

Country Link
US (2) US11184873B2 (zh)
EP (1) EP3537789B1 (zh)
JP (1) JP6949113B2 (zh)
KR (1) KR102207119B1 (zh)
CN (1) CN108024221B (zh)
WO (1) WO2018082598A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112689295A (zh) * 2019-10-18 2021-04-20 ***通信集团辽宁有限公司 寻呼消息的业务识别方法、装置、计算设备及存储介质
CN115226206A (zh) * 2021-04-21 2022-10-21 维沃移动通信有限公司 信息处理方法、装置、终端及存储介质

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3691348A1 (en) * 2016-04-01 2020-08-05 KYOCERA Corporation Base station and radio terminal
CN108024221B (zh) * 2016-11-03 2019-12-20 电信科学技术研究院 一种寻呼方法、基站及终端
US11240781B2 (en) * 2017-03-31 2022-02-01 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Communication method, terminal apparatus, and access network apparatus
EP3614754B1 (en) * 2017-06-09 2022-09-21 Huawei Technologies Co., Ltd. Paging message sending method and paging message receiving method
CN110519712B (zh) * 2018-05-21 2020-11-17 ***通信有限公司研究院 信息处理方法及装置、网元及存储介质
CN110971373B (zh) * 2018-09-29 2022-04-12 大唐移动通信设备有限公司 一种节能区域的配置方法、基站、终端及核心网
CN111356230B (zh) * 2018-12-21 2022-03-29 华为技术有限公司 一种通信方法及装置
WO2021026739A1 (zh) * 2019-08-12 2021-02-18 华为技术有限公司 一种无线网络临时标识rnti更新方法及设备
CN115604822B (zh) * 2019-09-29 2024-03-05 中兴通讯股份有限公司 一种数据传输和信息确定方法、装置和存储介质
EP4236594A3 (en) * 2019-11-01 2023-09-27 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Wireless communication method, terminal device and computer-readable storage medium
CN113950122A (zh) * 2020-07-17 2022-01-18 华为技术有限公司 接入回传一体化iab网络的通信方法及装置
CN114845393B (zh) * 2020-09-16 2024-02-13 北京小米移动软件有限公司 发送、接收寻呼消息的方法、装置、设备及存储介质
CN114390677A (zh) * 2020-10-22 2022-04-22 维沃移动通信有限公司 寻呼方法、装置、终端、网络侧设备及可读存储介质
US11979853B2 (en) * 2020-10-23 2024-05-07 Samsung Electronics Co., Ltd. Method and apparatus for transmitting and receiving a signal in the wireless communication system
CN114946204B (zh) * 2020-12-15 2024-06-18 北京小米移动软件有限公司 一种寻呼消息监听方法、寻呼消息监听装置及存储介质
WO2022236622A1 (zh) * 2021-05-10 2022-11-17 北京小米移动软件有限公司 一种寻呼方法及其装置
CN113676836B (zh) * 2021-08-05 2022-11-04 重庆智铸华信科技有限公司 一种无线通信方法、装置、电子设备及存储介质
CN116170899B (zh) * 2023-03-01 2023-10-17 上海移芯通信科技股份有限公司 一种防止连接态寻呼响应丢失的方法和***

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104115536A (zh) * 2012-02-16 2014-10-22 苹果公司 用于对失去同步进行识别的方法

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH02167136A (ja) * 1988-12-20 1990-06-27 Hitachi Ltd Ｍｒイメージング装置
JPH0775116B2 (ja) * 1988-12-20 1995-08-09 三菱電機株式会社 半導体記憶装置
JP2730937B2 (ja) * 1988-12-21 1998-03-25 マツダ株式会社 車両用多重伝送装置
CN100579123C (zh) * 2006-01-18 2010-01-06 华为技术有限公司 一种在通讯***中保障信息安全的处理方法
CN101047977A (zh) * 2006-03-27 2007-10-03 华为技术有限公司 无线通信***及方法以及在该***中使用的寻呼方法
KR20140066356A (ko) 2012-11-23 2014-06-02 삼성전자주식회사 무선통신시스템에서 무선자원 제어 상태 불일치를 해결하기 위한 방법 및 장치
KR101296578B1 (ko) 2013-03-07 2013-08-14 주식회사 에스엠이씨 Lte 네트워크를 위한 페이징 노드 장치 및 페이징 방법
KR20180135023A (ko) * 2016-04-20 2018-12-19 콘비다 와이어리스, 엘엘씨 이동성 시그널링 로드 감소
EP3446524B1 (en) * 2016-04-22 2019-12-11 Telefonaktiebolaget LM Ericsson (publ) Method performed by a radio network node in the context of paging
CN108024221B (zh) * 2016-11-03 2019-12-20 电信科学技术研究院 一种寻呼方法、基站及终端

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104115536A (zh) * 2012-02-16 2014-10-22 苹果公司 用于对失去同步进行识别的方法

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Report from E-mail Discussion on RRC Procedures", TSG-RAN WORKING GROUP 2 (RADIO LAYER 2 AND RADIO LAYER 3), 20 September 1999 (1999-09-20), pages 6, XP050113547 *
NTT DOCOMO, INC: "UE State Transition Diagram for NR", 3GPP TSG-RAN WG2#95BIS, R2-167136, 10 October 2016 (2016-10-10), Kaohsiung, Taiwan, XP051151530 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112689295A (zh) * 2019-10-18 2021-04-20 ***通信集团辽宁有限公司 寻呼消息的业务识别方法、装置、计算设备及存储介质
CN112689295B (zh) * 2019-10-18 2023-09-05 ***通信集团辽宁有限公司 寻呼消息的业务识别方法、装置、计算设备及存储介质
CN115226206A (zh) * 2021-04-21 2022-10-21 维沃移动通信有限公司 信息处理方法、装置、终端及存储介质

Also Published As

Publication number Publication date
EP3537789B1 (en) 2020-12-30
CN108024221B (zh) 2019-12-20
EP3537789A4 (en) 2019-10-30
CN108024221A (zh) 2018-05-11
JP6949113B2 (ja) 2021-10-13
EP3537789A1 (en) 2019-09-11
JP2019537357A (ja) 2019-12-19
KR20190073540A (ko) 2019-06-26
US20220046584A1 (en) 2022-02-10
US11963132B2 (en) 2024-04-16
US11184873B2 (en) 2021-11-23
US20190313364A1 (en) 2019-10-10
KR102207119B1 (ko) 2021-01-22

Similar Documents

Publication Publication Date Title
WO2018082598A1 (zh) 一种寻呼方法、基站及终端
WO2017193766A1 (zh) 一种下行数据传输的方法及设备
US9113370B2 (en) Method and apparatus for handling a stationary user terminal in a network
WO2018019001A1 (zh) 一种终端状态转换方法及装置
WO2017166963A1 (zh) 一种寻呼方法、设备及***
WO2018014661A1 (zh) 一种数据或者信令发送、传输方法及装置
US10057937B2 (en) Communications via multiple access points
WO2017133295A1 (zh) 数据传输方法、装置和***
CN114449043B (zh) 通信方法及通信装置
US20230050355A1 (en) Wus for paging for rrc inactive states
US20240172120A1 (en) Communication method and related apparatus
EP3493612B1 (en) Method for managing wireless system area, terminal and base station
WO2021103026A1 (zh) 在带宽部分上进行通信的方法
WO2022213885A1 (zh) 一种通信方法及装置
WO2021030987A1 (zh) 一种冲突解决方法及装置
WO2023165420A1 (zh) 通信方法及通信装置
WO2024012224A1 (zh) 一种通信的方法和装置
WO2024051391A1 (zh) 一种通信的方法和通信装置
WO2023241504A1 (zh) 一种通信方法及设备
WO2023116740A1 (zh) 通信方法和通信装置
WO2023283778A1 (zh) 终端设备的控制方法、设备及存储介质
US20240214935A1 (en) Communication method and communication apparatus

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019522558

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197015901

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2017867354

Country of ref document: EP

Effective date: 20190603