WO2018001086A1 - 承载寻呼消息载波的确定、寻呼消息的发送方法及装置 - Google Patents

承载寻呼消息载波的确定、寻呼消息的发送方法及装置 Download PDF

Info

Publication number
WO2018001086A1
WO2018001086A1 PCT/CN2017/088102 CN2017088102W WO2018001086A1 WO 2018001086 A1 WO2018001086 A1 WO 2018001086A1 CN 2017088102 W CN2017088102 W CN 2017088102W WO 2018001086 A1 WO2018001086 A1 WO 2018001086A1
Authority
WO
WIPO (PCT)
Prior art keywords
paging
terminal
paging message
message
feature
Prior art date
Application number
PCT/CN2017/088102
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 US16/314,279 priority Critical patent/US10917871B2/en
Publication of WO2018001086A1 publication Critical patent/WO2018001086A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a method for determining a carrier carrying a paging message, and a method for transmitting a paging message.
  • Machine to Machine (M2M) communication is an important subject of the fifth generation of mobile communication technology (5G), and an important application field for wireless communication in the future.
  • M2M Machine to Machine
  • 5G mobile communication technology
  • NB-IoT NarowBand-Internet of Things
  • Low-cost (User Equipment, UE for short) provides low-throughput wireless communication services.
  • the NB-IoT system introduces a multi-carrier cell: one cell contains multiple 200khz carriers, of which only one The carrier carries a Narrowband Physical Broadcast Channel (NPBCH)/Narrowband Primary Synchronization Signal (NPSS)/Narrowband Secondary Synchronization Signal (NSSS), which is called the main (Anchor). Carrier, the remaining carriers are called Non-Anchor carriers.
  • NNBCH Narrowband Physical Broadcast Channel
  • NPSS Narrowband Primary Synchronization Signal
  • NSSS Narrowband Secondary Synchronization Signal
  • anchor carrier may also be referred to as an anchor carrier
  • a non-anchor carrier may also be referred to as a non-anchor carrier.
  • the current standard stipulates that the UE in the idle (IDLE) mode can only reside on the Anchor carrier.
  • the eNodeB can pass the fourth Radio Resource Control (RRC) message or the subsequent RRC message according to the load of each carrier in the cell. Assign traffic to the Non-Anchor carrier. This has a problem, the paging message can only be sent and received through the Anchor carrier.
  • RRC Radio Resource Control
  • the paging volume is large, and concentrating paging of all users in the multi-carrier cell on the Anchor carrier may result in limited paging capacity of the cell.
  • the embodiment of the invention provides a method for determining a paging message carrier and a method for transmitting a paging message, so as to at least solve the problem that the paging capacity of the multi-carrier cell is limited in the related art.
  • a method for determining a carrier that carries a paging message including: acquiring a terminal from a paging message sent by a Mobile Management Entity (MME) or locally stored information of a base station.
  • MME Mobile Management Entity
  • the paging feature wherein the paging feature is whether the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message; determining the carrier carrying the paging message corresponding to the terminal according to the paging characteristic.
  • determining, according to the paging characteristic, the carrier that carries the paging message corresponding to the terminal includes: determining, when the paging feature is that the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message.
  • the carrier of the paging message corresponding to the terminal is a primary Anchor carrier or a non-primary Non-Anchor carrier; and if the paging characteristic is that the terminal does not have the capability of supporting the Non-Anchor carrier to carry the paging message, determining that the bearer corresponds to the terminal
  • the carrier of the paging message is the primary Anchor carrier.
  • determining that the carrier carrying the paging message corresponding to the terminal is a primary Anchor carrier or a non-primary Non-Anchor carrier includes: according to a preset carrier and a terminal identifier of a cell where the terminal is located, capable of carrying a paging message The correspondence determines that the carrier carrying the paging message corresponding to the terminal is a primary Anchor carrier or a non-primary Non-Anchor carrier.
  • the method before obtaining the paging feature of the terminal from the paging message sent by the mobility management entity MME, the method further includes: using the S1 port signaling, indicating whether the cell where the terminal is located supports the Non-Anchor carrier bearer search The indication information of the call message is sent to the MME.
  • the method before obtaining the paging feature of the terminal from the information stored locally by the base station, the method further includes: acquiring the paging feature of the terminal from the radio resource control RRC signaling reported by the terminal; and saving the paging feature of the terminal In the message.
  • the RRC signaling includes at least one of the following: an RRC connection request message, an RRC connection recovery request message, an RRC re-establishment request message, an RRC connection setup complete message, an RRC connection recovery complete message, and an RRC connection re-establishment completion. Message.
  • the paging feature of the terminal is indicated by at least one of: a cell, a bit in a cell, a paging type, and a terminal category.
  • a method for transmitting a paging message including: sending a paging message to a base station, where the paging message carries a paging feature of the terminal, and the paging feature is whether the terminal has a support non- The ability of the primary Non-Anchor carrier to carry the paging message; the paging feature is used by the base station to determine the carrier carrying the paging message corresponding to the terminal.
  • the method before sending the paging message to the base station, the method further includes: determining whether the paging feature of the terminal is carried in the paging message sent to the base station.
  • determining whether the paging feature of the terminal is carried in the paging message sent to the base station includes: determining, according to the indication information and the paging feature of the terminal, whether the paging message carries the paging feature of the terminal;
  • the indication information is indication information that is used by the base station to indicate whether the cell where the terminal is located supports the Non-Anchor carrier-bearing paging message, and the indication information indicates that the cell where the terminal is located supports the Non-Anchor carrier-bearing paging message and the paging of the terminal.
  • the feature is that the terminal has the capability of supporting the Non-Anchor carrier to carry the paging message, and determines the paging characteristic of the carrying terminal in the paging message; the indication information indicates that the cell where the terminal is located supports the Non-Anchor carrier-bearing paging message and the terminal.
  • the paging feature is that if the terminal does not have the capability of supporting the Non-Anchor carrier to carry the paging message, the paging feature of the paging message with or without the terminal is determined.
  • the paging feature of the terminal in the paging message includes: carrying the paging feature of the terminal by using a specific indication field in the paging message; wherein, when the value of the specific indication field is the first value, The terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message. When the value of the specific indication field is the second value, the terminal does not have the capability of supporting the non-primary Non-Anchor carrier to carry the paging message;
  • the paging feature of the paging message that does not carry the terminal includes: the specific indication domain is not included in the paging message.
  • the method before the sending of the paging message to the base station, the method further includes: when the terminal is initially attached or the tracking area is updated, the non-access stratum (NAS) message sent by the terminal is connected or received.
  • the access stratum (AS) signaling acquires the paging feature of the terminal, or acquires the paging feature of the terminal from the subscription information of the terminal.
  • the NAS message includes at least one of the following: an attach request message, a tracking area update TAU request message.
  • the AS signaling includes at least one of the following: the terminal capability information of the air interface, and the terminal capability information indication of the S1 interface.
  • a determining apparatus for carrying a paging message carrier comprising: a first acquiring module, configured to acquire a terminal from a paging message sent by a mobility management entity MME or locally stored information of a base station a paging feature, wherein the paging feature is whether the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message; and the determining module is configured to determine, according to the paging characteristic, a carrier that carries the paging message corresponding to the terminal.
  • the determining module is further configured to: when the paging characteristic is that the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message, determine that the carrier carrying the paging message corresponding to the terminal is the primary Anchor.
  • the determining module is further configured to determine, according to the preset correspondence between the carrier capable of carrying the paging message and the terminal identifier of the cell where the terminal is located, the carrier that carries the paging message corresponding to the terminal is the primary Anchor carrier or the non- Primary Non-Anchor carrier.
  • the device further includes: a sending module, configured to send, by using the S1 port signaling, indication information indicating whether the cell where the terminal is located supports the Non-Anchor carrier-bearing paging message, to the MME.
  • a sending module configured to send, by using the S1 port signaling, indication information indicating whether the cell where the terminal is located supports the Non-Anchor carrier-bearing paging message, to the MME.
  • the device further includes: a second acquiring module, configured to acquire a paging feature of the terminal from the radio resource control RRC signaling reported by the terminal; and save the module, and set the terminal to be The paging feature of the terminal is stored in the message.
  • the RRC signaling includes at least one of the following: an RRC connection request message, an RRC connection recovery request message, an RRC re-establishment request message, an RRC connection setup complete message, an RRC connection recovery complete message, and an RRC connection re-establishment completion. Message.
  • the paging feature of the terminal is indicated by at least one of: a cell, a bit in a cell, a paging type, and a terminal category.
  • a device for transmitting a paging message including: a sending module, configured to send a paging message to a base station, where the paging message carries a paging feature of the terminal, and the paging feature is Whether the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message; the paging feature is used by the base station to determine the carrier carrying the paging message corresponding to the terminal.
  • the apparatus further includes: a determining module, configured to determine whether to carry a paging feature of the terminal in sending the paging message to the base station.
  • the determining module is further configured to: determine, according to the indication information and the paging characteristic of the terminal, whether the paging message sent by the base station carries the paging feature of the terminal; wherein the indication information is obtained from the base station for indicating Whether the cell in which the terminal is located supports the indication information of the non-Anchor carrier-bearing paging message, and the indication information indicates that the cell in which the terminal is located supports the Non-Anchor carrier-bearing paging message and the paging feature of the terminal is that the terminal has the non-Anchor carrier-carrying paging.
  • the paging message In the case of the capability of the message, it is confirmed that the paging message carries the paging characteristic of the terminal; the indication information indicates that the cell in which the terminal is located supports the Non-Anchor carrier-bearing paging message and the paging characteristic of the terminal is that the terminal does not have the support for the Non-Anchor carrier. In the case of carrying the capability of paging messages, the paging characteristics of the paging message with or without the terminal are determined.
  • the paging feature of the terminal in the paging message includes: carrying the paging feature of the terminal by using a specific indication field in the paging message; wherein, when the value of the specific indication field is the first value, The terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message. When the value of the specific indication field is the second value, the terminal does not have the capability of supporting the non-primary Non-Anchor carrier to carry the paging message; the paging message
  • the paging feature of the terminal that does not carry the terminal includes: the specific indication domain is not included in the paging message.
  • the device further includes: an acquiring module, configured to acquire a paging feature of the terminal by using a non-access stratum NAS message or an access layer AS signaling sent by the terminal, when the terminal initially attaches or the tracking area is updated, Or obtain the paging feature of the terminal from the subscription information of the terminal.
  • an acquiring module configured to acquire a paging feature of the terminal by using a non-access stratum NAS message or an access layer AS signaling sent by the terminal, when the terminal initially attaches or the tracking area is updated, Or obtain the paging feature of the terminal from the subscription information of the terminal.
  • the NAS message includes at least one of the following: an attach request message, and a Tracking Area Update (TAU) request message.
  • an attach request message includes at least one of the following: an attach request message, and a Tracking Area Update (TAU) request message.
  • TAU Tracking Area Update
  • the AS signaling includes at least one of the following: the terminal capability information of the air interface, and the terminal capability information indication of the S1 interface.
  • a base station comprising: determining means for carrying a paging message carrier.
  • a mobility management entity MME including: a sending apparatus for the paging message.
  • a system comprising the above base station, the MME and the terminal; wherein the terminal is configured to pass the non-access stratum NAS message or the access layer AS letter when the initial attach or tracking area is updated.
  • the paging feature of the terminal is reported to the MME or the paging feature of the terminal is reported to the base station by using RRC signaling during the RRC establishment process; wherein the paging feature is whether the terminal supports the non-primary Non-Anchor carrier The ability to carry paging messages.
  • the terminal is further configured to determine, according to the paging feature of the terminal itself, the carrier and the terminal identifier of the cell in which the terminal is located, the carrier that receives the paging message sent by the base station.
  • a storage medium comprising a stored program, wherein the program is executed to perform the method of any of the above.
  • a processor for running a program wherein the program is executed to perform the method of any of the above.
  • the paging feature of the terminal is obtained by the paging message sent by the MME or the information stored locally by the eNB, so that the paging feature of the terminal can be obtained, and the bearer corresponding to the terminal can be determined according to the paging characteristic. Calling the carrier of the message, which in turn can not The paging message of the same terminal is shared by the determined carrier, thereby solving the problem that the paging capacity of the multi-carrier cell is limited in the related art, and improving the paging capacity of the multi-carrier cell.
  • FIG. 1 is a schematic diagram of a network architecture according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a method for determining a carrier carrying a paging message according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for transmitting a paging message according to an embodiment of the present invention
  • FIG. 4 is a schematic flowchart of a process for initial attaching of a UE according to a preferred embodiment of the present invention
  • FIG. 5 is a schematic diagram of a UE capability query procedure triggered by a UE initial attach procedure according to a preferred embodiment of the present invention
  • FIG. 6 is a schematic diagram of a TAU flow of an idle mode according to a preferred embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a TAU flow of an idle mode according to a preferred embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a TAU flow of a connection mode according to a preferred embodiment of the present invention.
  • FIG. 9 is a schematic diagram of a UE capability query procedure triggered by a connection mode TAU process according to a preferred embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a capability of a base station to report whether it supports a non-primary Non-Anchor carrier-bearing paging message according to a preferred embodiment of the present invention
  • FIG. 11 is a schematic flowchart of a method for a base station to acquire a paging feature of a terminal according to a preferred embodiment of the present invention
  • FIG. 12 is a schematic flowchart of an RRC connection establishment process for a UE that supports a user plane optimization process based on a user plane optimization-based service flow according to a preferred embodiment of the present invention
  • FIG. 13 is a schematic flowchart of a “Non-Anchor Carrier Bearer Paging Message” paging feature acquisition process when a paging message is sent to a UE in a user-suspended state according to a preferred embodiment of the present invention
  • FIG. 14 is a structural block diagram of a determining apparatus for carrying a paging message carrier according to an embodiment of the present invention.
  • 15 is a structural block diagram of a device for transmitting a paging message according to an embodiment of the present invention.
  • Figure 16 is a block diagram showing the structure of a system in accordance with a preferred embodiment of the present invention.
  • a paging capacity improvement method is: a non-primary Non-Anchor carrier can also carry a paging message, and paging messages of different terminals in a multi-carrier cell pass the primary Anchor carrier and the non-primary Non-Anchor carrier. Load sharing.
  • a UE supporting this feature and a UE not supporting the feature may exist under the eNodeB supporting the feature.
  • the eNodeB When sending a paging message to the UE, the eNodeB first needs to determine whether the UE supports the feature, and then determines which carrier in the multi-carrier cell is sent by the paging of the UE.
  • the embodiment of the present application provides a method for determining a carrier carrying a paging message.
  • the method of the embodiment of the present application can be run on the network architecture shown in FIG. 1.
  • the network architecture includes: a terminal, a base station, and a mobility management entity MME, where the terminal can The base station and the MME can interact with each other, and the base station and the MME can also interact.
  • FIG. 2 is a flowchart of a method for determining a bearer paging message carrier according to an embodiment of the present invention, as shown in FIG. The process includes the following steps:
  • Step S202 Acquire a paging feature of the terminal from a paging message sent by the mobility management entity MME or information stored locally by the base station, where the paging feature is whether the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message;
  • Step S204 determining, according to the paging characteristic, a carrier that carries a paging message corresponding to the terminal.
  • the paging feature of the terminal is obtained by the paging message sent by the MME or the information stored locally by the base station, so that the paging feature of the terminal can be obtained, and the bearer corresponding to the terminal can be determined according to the paging characteristic.
  • the carrier of the message can further share the paging message of different terminals in the cell by using the determined carrier, thereby solving the problem that the paging capacity of the multi-carrier cell is limited in the related art, and improving the paging capacity of the multi-carrier cell. .
  • obtaining the paging feature of the terminal from the paging message sent by the mobility management entity MME may be performed by: the paging message carrying the paging feature of the terminal, and after obtaining the paging message, parsing
  • the information in the paging message is used to obtain the paging characteristics of the terminal, but is not limited thereto.
  • the carrier that determines the paging message corresponding to the terminal is the primary Anchor.
  • the paging characteristic of the terminal determines which carrier is used to carry the paging message, so that the Non-Anchor carrier can share the work of carrying the paging message of the partial Anchor carrier, and does not concentrate all the users' paging in the Anchor. On the carrier, the problem of limited paging capacity of the cell is avoided.
  • determining that the carrier carrying the paging message corresponding to the terminal is a primary Anchor carrier or a non-primary Non-Anchor carrier includes: according to a preset terminal Corresponding relationship between the carrier and the terminal identifier of the cell in which the paging message is located determines that the carrier carrying the paging message corresponding to the terminal is a primary Anchor carrier or a non-primary Non-Anchor carrier.
  • the terminal identifier is divided by the number of carriers capable of carrying the paging message, and the quotient obtained by the division is used as the number of the carrier corresponding to the terminal identifier.
  • the determined carrier that carries the paging message corresponding to the terminal is the carrier corresponding to the corresponding carrier number
  • the carrier is the primary Anchor carrier
  • the determined bearer of the paging message corresponding to the terminal is the primary Anchor carrier.
  • the carrier is a non-primary Non-Anchor carrier
  • the determined carrier carrying the paging message corresponding to the terminal is a non-primary Non-Anchor carrier.
  • the method may further include The indication information indicating whether the cell where the terminal is located supports the Non-Anchor carrier-bearing paging message is sent to the MME by using the S1 interface signaling.
  • the indication information is used to indicate that the cell where the terminal is located does not support the Non-Anchor carrier-bearing paging.
  • the paging message sent by the MME to the base station does not carry the paging feature of the terminal, or the paging feature of the carrying terminal, and the indication information is used to indicate that the cell where the terminal is located supports the Non-Anchor carrier bearer search.
  • the paging message sent by the MME to the base station carries the paging characteristics of the terminal, but is not limited thereto.
  • S1 port signaling may be an S1 setup request message or a base station configuration update message, but is not limited thereto.
  • the method may further include: acquiring the radio resource control RRC signaling reported by the terminal.
  • the paging feature of the terminal; the paging characteristics of the terminal are saved in the information.
  • RRC signaling may include at least one of the following, but is not limited thereto: an RRC connection request message, an RRC connection recovery request message, an RRC re-establishment request message, an RRC connection setup complete message, and an RRC connection recovery complete message.
  • the RRC connection re-establishment completion message may include at least one of the following, but is not limited thereto: an RRC connection request message, an RRC connection recovery request message, an RRC re-establishment request message, an RRC connection setup complete message, and an RRC connection recovery complete message.
  • the paging feature of the foregoing terminal may be indicated by at least one of: one cell, one bit in a cell, a paging type, and a terminal category.
  • the paging feature of the foregoing terminal may be characterized by a single cell, or by a value of a certain bit of a cell; may be explicitly characterized or implicitly characterized. For example, if the value of a certain indication field is 1, the UE supports the "Non-Anchor carrier-carrying paging message" feature, and the value of a certain indication field is 0, indicating that the UE does not support the "Non-Anchor carrier-bearing paging message” feature; or The signaling includes an indication field and the value of “TRUE” indicates that the UE supports the “Non-Anchor carrier-bearing paging message” feature.
  • the UE does not support the “Non-Anchor carrier”.
  • Carrying a paging message” characteristic; or implicitly indicating whether the UE supports "Non-Anchor carrier-bearing paging message” by different classes of UEs; or indicating whether the UE supports "Non-Anchor carrier-bearing seeking" by "paging type” Call message" (for example: paging type one is a regular paging, only supports paging information on Anchor carrier; paging type 2 is paging of multi-carrier cell, supporting paging on Anchor carrier and on-Anchor carrier Information) and so on.
  • the executor of the foregoing steps may be the base station shown in FIG. 1 above, and specifically may be a base station supporting a Non-Anchor carrier-bearing paging message, but is not limited thereto.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be through hardware, but in many cases the former is a better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • FIG. 3 A flowchart of a method for sending a paging message, as shown in FIG. 3, the process includes the following steps:
  • Step S302 determining whether the paging feature of the terminal is carried in the paging message sent to the base station;
  • Step S304 sending a paging message to the base station, where the paging message carries the paging feature of the terminal, and the paging feature is whether the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message; the paging feature is used for the base station.
  • a carrier that carries a paging message corresponding to the terminal is determined.
  • the paging message sent by the base station carries the paging feature of the terminal, so that the base station can obtain the paging feature of the terminal when the paging message is obtained, and the bearer can be determined according to the paging feature.
  • the carrier of the paging message can further share the paging messages of different terminals in the cell by using the determined carrier, thereby solving the problem that the paging capacity of the multi-carrier cell is limited in the related art, and improving the searching of the multi-carrier cell. Call capacity.
  • the foregoing step S302 may include: determining, according to the indication information and the paging characteristic of the terminal, whether the paging feature of the terminal is carried in the paging message sent to the base station; wherein the indication information is used by the base station to indicate whether the cell where the terminal is located supports Non.
  • the Non-Anchor carrier-bearing paging message and the paging feature of the terminal are: when the terminal has the capability of supporting the Non-Anchor carrier to carry the paging message, determining the paging characteristic of the carrying terminal in the paging message; The cell supports the Non-Anchor carrier-bearing paging message and the paging feature of the terminal. If the terminal does not have the capability of supporting the Non-Anchor carrier to carry the paging message, the paging feature of the paging message carrying or not carrying the terminal is determined.
  • the paging feature of the terminal in the paging message includes: carrying the paging feature of the terminal by using a specific indication field in the paging message; wherein, when the value of the specific indication field is the first value, the terminal The capability of supporting a non-primary Non-Anchor carrier to carry a paging message, when the value of the specific indication field is a second value, the terminal does not have the capability of supporting the non-primary Non-Anchor carrier to carry the paging message;
  • the paging feature of the mobile terminal includes: the specific indication domain is not included in the paging message.
  • the indication information indicates that the cell where the terminal is located does not support the Non-Anchor carrier-bearing paging message, it is determined that the paging feature of the non-bearing terminal in the paging message sent to the base station is determined.
  • step S304 may be performed independently of the step S302, that is, the foregoing step S304 may be performed separately, or may be performed together with the step S302, and is not limited thereto.
  • the method may further include: acquiring the terminal by using the non-access stratum NAS message or the access stratum AS signaling sent by the terminal when the terminal initially attaches or the tracking area is updated.
  • the paging feature or obtain the paging characteristics of the terminal from the subscription information of the terminal.
  • the method may further include: storing the obtained paging feature of the terminal.
  • the foregoing NAS message may include at least one of the following: an attach request message, a tracking area update TAU request message, but is not limited thereto.
  • the foregoing AS signaling may include at least one of the following: the terminal capability information of the air interface, and the terminal capability information of the S1 port indicates, but is not limited to.
  • the paging feature of the foregoing terminal may be indicated by at least one of: one cell, one bit in a cell, a paging type, and a terminal category.
  • the paging feature of the foregoing terminal may be characterized by a single cell, or by a value of a certain bit of a cell; may be explicitly characterized or implicitly characterized. For example, if the value of a certain indication field is 1, the UE supports the "Non-Anchor carrier-carrying paging message" feature, and the value of a certain indication field is 0, indicating that the UE does not support the "Non-Anchor carrier-bearing paging message” feature; or The signaling includes an indication field and the value of “TRUE” indicates that the UE supports the “Non-Anchor carrier-bearing paging message” feature.
  • the UE does not support the “Non-Anchor carrier”.
  • Carrying a paging message” characteristic; or implicitly indicating whether the UE supports "Non-Anchor carrier-bearing paging message” by different classes of UEs; or indicating whether the UE supports "Non-Anchor carrier-bearing seeking" by "paging type” Call message" (for example: paging type one is a regular paging, only supports paging information on Anchor carrier; paging type 2 is paging of multi-carrier cell, supporting paging on Anchor carrier and on-Anchor carrier Information) and so on.
  • the executor of the foregoing step may be the mobility management entity MME. Specifically, it may be the MME in the network architecture shown in FIG. 1 above, but is not limited thereto.
  • the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
  • the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
  • the technical problem to be solved by the preferred embodiment of the present invention is to propose a method for how the eNodeB in the NB-IoT system acquires the "Non-Anchor Carrier Bearer Paging Message" paging feature of the UE.
  • the method can solve the problem that the eNodeB cannot obtain the paging feature of the “Non-Anchor carrier-carrying paging message” of the UE when sending the paging message.
  • the method for obtaining the paging feature of the "Non-Anchor carrier-carrying paging message" of the UE by the eNodeB includes:
  • the UE When the UE is in the initial attachment or the TRAUKING AREA UPDATE (TAU), the UE passes the Non-Access-Stratiction (NAS) message or the access layer (Access-Stratum, referred to as The AS) signaling reports the paging feature of the "Non-Anchor carrier-bearing paging message" of the UE to the Mobility Management Entity (MME); when the MME initiates paging, the UE "" The non-Anchor carrier bearer paging message carries the paging feature to the eNodeB.
  • NAS Non-Access-Stratiction
  • the AS Access-Stratum
  • the eNodeB obtains the "Non-Anchor Carrier Bearer Paging Message" paging feature of the UE by parsing the information in the paging message, and performs the paging function according to the acquired capability. Selection of paging carriers in a multi-carrier cell.
  • the NAS message may be an attach request or a TAU request message; the AS signaling may be the “UE capability information” of the air interface and the “UE capability information indication” of the S1 interface.
  • the eNodeB transmits an indication of whether the cell supports the Non-Anchor carrier transmission paging to the MME through the S1 port signaling, so that the MME determines whether the UE carrying the UE “Non-Anchor” in the paging message sent to the eNodeB.
  • Carrier bearer paging message" feature support indication.
  • the UE reports the "Non-Anchor Carrier Bearer Paging Message" paging feature of the UE to the eNodeB through RRC signaling; the eNodeB saves the "Non-Anchor carrier bearer paging" of the UE when the RRC connection is released.
  • the message "paging characteristic" when the UE is paged again, the eNodeB performs the selection of the paging carrier in the multi-carrier cell according to the paging feature of the UE "Non-Anchor Carrier Bearer Paging Message" saved by itself.
  • the RRC signaling may be: an RRC connection request, an RRC connection recovery request, an RRC re-establishment request, an RRC connection setup completion, an RRC connection recovery completion, and an RRC connection re-establishment completion.
  • the paging feature of the "Non-Anchor carrier-carrying paging message" of the UE may be characterized by a single cell or by the value of a certain bit of a cell; Can be implicitly characterized. For example, if the value of a certain indication field is 1, the UE supports the "Non-Anchor carrier-carrying paging message" feature, and the value of a certain indication field is 0, indicating that the UE does not support the "Non-Anchor carrier-bearing paging message” feature; or The signaling includes an indication field and the value of “TRUE” indicates that the UE supports the “Non-Anchor carrier-bearing paging message” feature.
  • the UE does not support the “Non-Anchor carrier”.
  • Carrying a paging message” characteristic; or implicitly indicating whether the UE supports "Non-Anchor carrier-bearing paging message” by different classes of UEs; or indicating whether the UE supports "Non-Anchor carrier-bearing seeking" by "paging type” Call message" (for example: paging type one is a regular paging, only supports paging information on Anchor carrier; paging type 2 is paging of multi-carrier cell, supporting paging on Anchor carrier and on-Anchor carrier Information) and so on.
  • FIG. 4 is a schematic flowchart of a process for initial attaching of a UE according to a preferred embodiment of the present invention.
  • the preferred embodiment of the present invention shown in FIG. 4 provides that the UE passes its own "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication.
  • the NAS message is reported to the MME.
  • the process includes:
  • the UE carries the NAS PDU of the Attach Request in the RRC Connection Setup Complete message.
  • the eNodeB After receiving the RRC connection setup complete message, the eNodeB delivers the NAS PDU carrying the attach request to the MME through the initial UE message.
  • the NAS PDU carrying the attach request carries the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE.
  • the MME After receiving the NAS PDU carrying the attach request, the MME parses the UE "Non-Anchor Carrier Bearer Paging Message" paging feature indication and saves it for use in subsequent paging.
  • FIG. 5 is a schematic diagram of a UE capability query procedure triggered by a UE initial attach procedure according to a preferred embodiment of the present invention.
  • the preferred embodiment of the present invention shown in FIG. 5 provides a UE with its own “Non-Anchor carrier bearer paging message.
  • the paging feature indicates an example reported to the MME by using AS signaling.
  • the process includes:
  • the initial attach procedure of the UE triggers the eNodeB to initiate a UE capability query procedure (the eNodeB sends a UE capability query message to the UE)
  • the UE reports its own capability to the eNodeB through the “UE Capability Information”, where the UE capability includes the “Non-Anchor Carrier Bearer Paging Message” paging feature indication of the UE.
  • the eNodeB reports the received UE capability to the MME through the “UE Capability Information Indication”, where the UE capability includes the “Non-Anchor Carrier Bearer Paging Message” paging feature indication of the UE.
  • the MME After receiving the “UE Capability Information Indication”, the MME parses the UE “Non-Anchor Carrier Bearer Paging Message” paging feature indication and saves it for use in subsequent paging.
  • FIG. 6 is a schematic diagram of a TAU flow in an idle mode according to a preferred embodiment of the present invention.
  • the preferred embodiment of the present invention shown in FIG. 6 provides a paging feature indication of a “Non-Anchor Carrier Bearer Paging Message” of the UE.
  • Another example of reporting the NAS message to the MME, the process includes:
  • the UE carries the Tracking Area Update (TAU) NAS PDU in the RRC Connection Setup Complete message.
  • the NAS PDU carrying the TAU carries the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE.
  • the eNodeB receives the RRC connection setup complete message, and delivers the NAS PDU carrying the TAU to the MME through the initial UE message.
  • the NAS PDU carrying the TAU carries the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE.
  • the MME After receiving the NAS PDU carrying the TAU, the MME parses the UE "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication and saves it for use in subsequent paging.
  • FIG. 7 is a schematic diagram of a TAU flow in an idle mode according to a preferred embodiment of the present invention.
  • the preferred embodiment of the present invention shown in FIG. 7 provides a paging feature indication that the UE sets its own “Non-Anchor Carrier Bearer Paging Message”.
  • a further example of reporting the AS signaling to the MME, the process includes:
  • the UE's TAU procedure triggers the eNodeB to initiate a UE capability query procedure (the eNodeB sends a "UE Capability Query" message to the UE).
  • the UE reports its own capability to the eNodeB through the “UE Capability Information”, where the UE capability includes the “Non-Anchor Carrier Bearer Paging Message” paging feature indication of the UE.
  • the eNodeB reports the received UE capability to the MME through the “UE Capability Information Indication”, where the UE capability includes the “Non-Anchor Carrier Bearer Paging Message” paging feature indication of the UE.
  • the MME After receiving the “UE Capability Information Indication”, the MME parses the UE “Non-Anchor Carrier Bearer Paging Message” paging feature indication and saves it for use in subsequent paging.
  • FIG. 8 is a schematic diagram of a TAU flow of a connection mode according to a preferred embodiment of the present invention.
  • the preferred embodiment of the present invention as shown in FIG. 8 provides a paging feature indication of a “Non-Anchor carrier bearer paging message” of the UE.
  • the process includes:
  • the UE After the RRC connection establishment is completed, the UE carries the tracking area update (TAU) NAS PDU through the uplink information transmission (ULInformationTransfer) message.
  • the NAS PDU carrying the TAU carries the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE.
  • the eNodeB receives the uplink information transmission message, and transmits the NAS PDU carrying the TAU to the MME through the uplink NAS transmission message (UPLINK NAS TRANSPORT).
  • the NAS PDU carrying the TAU carries the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE.
  • the MME After receiving the NAS PDU carrying the TAU, the MME parses the UE "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication and saves it for use in subsequent paging.
  • FIG. 9 is a schematic diagram of a UE capability query procedure triggered by a TAU process in a connection mode according to a preferred embodiment of the present invention.
  • the preferred embodiment of the present invention shown in FIG. 9 provides that the UE transmits its own “Non-Anchor carrier bearer paging.
  • the message "Paging Feature" indicates another example of reporting to the MME through AS signaling.
  • the process includes:
  • the TAU procedure of the connected mode UE triggers the eNodeB to initiate a UE capability query procedure (the eNodeB sends a "UE Capability Query" message to the UE).
  • the UE reports its own capability to the eNodeB through the “UE Capability Information”, where the UE capability includes the “Non-Anchor Carrier Bearer Paging Message” paging feature indication of the UE.
  • the eNodeB reports the received UE capability to the MME through the “UE Capability Information Indication”, where the UE capability includes the “Non-Anchor Carrier Bearer Paging Message” paging feature indication of the UE.
  • the MME After receiving the “UE Capability Information Indication”, the MME parses the UE “Non-Anchor Carrier Bearer Paging Message” paging feature indication and saves it for use in subsequent paging.
  • FIG. 10 is a schematic diagram of a base station reporting its ability to support a non-primary Non-Anchor carrier-carrying paging message to a MME according to a preferred embodiment of the present invention.
  • a preferred embodiment of the present invention provides an eNodeB to report whether it is reported.
  • An example of supporting a Non-Anchor carrier to send a page, the process includes:
  • the eNodeB transmits an indication of whether the non-Anchor carrier transmits a paging message to the MME through the S1 interface signaling, so that the MME determines whether the paging message sent to the eNodeB carries the UE "Non-Anchor carrier-bearing paging message" feature support. Instructions. If the eNodeB supports the Non-Anchor carrier to send a page, the MME carries the UE "Non-Anchor Carrier Bearer Paging Message" feature support indication in the paging message sent to the eNodeB; otherwise, the MME sends the paging message to the eNodeB. It is not necessary to carry the UE "Non-Anchor Carrier Bearer Paging Message" feature support indication.
  • the S1 interface signaling that the eNodeB reports whether it supports the non-Anchor carrier to send the paging to the MME may be an "S1 setup request" or an "eNodeB configuration update" message; it may be reported in units of cells or eNodeBs. It can be characterized by a single cell, or by the value of a bit of a cell; it can be characterized either explicitly or implicitly. For example, if an indicator field has a value of 1, the eNodeB supports the Non-Anchor carrier to send a page. If the value of a certain indication field is 0, the eNodeB does not support the Non-Anchor carrier to send a page; or the signaling includes an indication.
  • the value of the field and the value of "TRUE" indicates that the eNodeB supports the Non-Anchor carrier to send a page. If the signal does not include an indication field, the eNodeB does not support the Non-Anchor carrier transmission page.
  • FIG. 11 is a schematic flowchart of a method for a base station to acquire a paging feature of a terminal according to a preferred embodiment of the present invention.
  • a preferred embodiment of the present invention provides that an eNodeB obtains a UE from a paging message sent by an MME.
  • - Anchor carrier bearer paging message example of paging feature, the process includes:
  • the paging message sent by the MME to the eNodeB carries the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE.
  • the eNodeB determines, according to the paging feature of the UE "Non-Anchor Carrier Bearer Paging Message" carried in the received paging message, whether the UE supports the "Non-Anchor Carrier Bearer Paging Message" feature: if not supported, the Anchor carrier Sending a paging message to the UE; otherwise, determining a carrier carrying the paging information of the UE according to information such as a carrier and a UE identifier that the cell can carry paging information, and sending a paging message to the UE on the carrier.
  • FIG. 12 is a schematic flowchart of an RRC connection establishment process for a UE that supports a user plane optimization-based service according to a user plane optimization-based service flow according to a preferred embodiment of the present invention.
  • a preferred embodiment of the present invention provides An example of the UE reporting the "Non-Anchor carrier-carrying paging message" paging feature of the UE to the eNodeB by using the RRC signaling, the process includes:
  • the UE carries the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE in the RRC setup complete message.
  • the UE context is stored, and the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE is stored.
  • the service flow based on the user plane optimization refers to a service flow introduced by the NB-IoT system for small data service signaling optimization: the terminal and the network use the data radio bearer (DRB, Data Radio Bearer) to transmit data, after the data transmission is completed.
  • DRB Data Radio Bearer
  • the two parties maintain information such as the bearer information context and the access layer (AS, Access Stratum) security context to suspend the RRC connection.
  • AS Access Stratum
  • FIG. 13 is a flowchart of a “Non-Anchor Carrier Bearer Paging Message” paging feature acquisition process when a paging message is sent to a UE in a user-suspend state according to a preferred embodiment of the present invention.
  • Schematic diagram of the process, as shown in FIG. 13, a preferred embodiment of the present invention provides an example of the eNodeB acquiring a paging feature of a UE "Non-Anchor Carrier Bearer Paging Message” from the UE context storage information, where the process includes:
  • the paging feature of the UE "Non-Anchor Carrier Bearer Paging Message" is first obtained in the information stored by the eNodeB.
  • the eNodeB determines whether the UE supports the "Non-Anchor Carrier Bearer Paging Message" feature according to the "Non-Anchor Carrier Bearer Paging Message" paging characteristic indication of the UE: if not supported, the paging message is sent to the UE on the Anchor carrier; Otherwise, the carrier carrying the paging information of the UE is determined according to information such as the carrier and the UE identifier that the cell can carry the paging information, and the paging message is sent to the UE on the carrier.
  • a determining device for carrying a paging message carrier is also provided in this embodiment.
  • the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 14 is a structural block diagram of a determining apparatus for carrying a paging message carrier according to an embodiment of the present invention. As shown in FIG. 14, the apparatus includes:
  • the first obtaining module 1402 is configured to obtain a paging feature of the terminal from a paging message sent by the mobility management entity MME or information stored locally by the base station, where the paging feature is whether the terminal has a non-primary Non-Anchor carrier bearer. The ability to call a message;
  • the determining module 1404 is connected to the first obtaining module 1402, and is configured to determine a carrier that carries a paging message corresponding to the terminal according to the paging characteristic.
  • the first obtaining module 1402 obtains the paging feature of the terminal from the paging message sent by the MME or the information stored locally by the base station, so that the paging feature of the terminal can be obtained, and the determining module 1404 can Obtaining the paging feature of the terminal to determine the carrier carrying the paging message corresponding to the terminal, and further searching for different terminals in the cell
  • the call message is shared by the determined carrier, thereby solving the problem that the paging capacity of the multi-carrier cell is limited in the related art, and improving the paging capacity of the multi-carrier cell.
  • the determining module 1404 may be further configured to obtain the paging feature of the terminal by parsing the information in the paging message after the paging message is obtained.
  • the determining module 1404 may further be configured to determine, according to the paging feature that the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message, determine the bearer message corresponding to the terminal.
  • the carrier is a primary carrier carrier or a non-primary Non-Anchor carrier; and in the case that the paging feature is that the terminal does not have the capability of supporting the Non-Anchor carrier to carry the paging message, determining that the carrier carrying the paging message corresponding to the terminal is Primary Anchor carrier.
  • the above-mentioned determining module 1404 enables the Non-Anchor carrier to share the work of carrying the paging message of the partial Anchor carrier, and does not concentrate all the users' paging on the Anchor carrier, thereby avoiding the problem that the paging capacity of the cell is limited. .
  • the determining module 1404 may be further configured to determine, according to a preset correspondence between a carrier capable of carrying a paging message and a terminal identifier of a cell where the terminal is located, a carrier that carries a paging message corresponding to the terminal.
  • the primary Anchor carrier or the non-primary Non-Anchor carrier may be further configured to determine, according to a preset correspondence between a carrier capable of carrying a paging message and a terminal identifier of a cell where the terminal is located, a carrier that carries a paging message corresponding to the terminal.
  • the apparatus may further include: a sending module, connected to the first acquiring module 1402, configured to indicate, by using the S1 port signaling, whether the cell where the terminal is located supports the Non-Anchor carrier bearer paging.
  • the indication information of the message is sent to the MME. Sending the indication information to the MME by using the sending module, so that the MME determines whether the paging feature of the terminal is to be carried in the paging message sent to the base station, for example, the indication information is used to indicate that the cell where the terminal is located does not support the Non-Anchor carrier.
  • the paging message sent by the MME to the base station does not carry the paging feature of the terminal; if the indication information is used to indicate that the cell where the terminal is located supports the Non-Anchor carrier-bearing paging message, the MME sends The paging message to the base station carries the paging characteristics of the terminal, but is not limited thereto.
  • S1 port signaling may be an S1 setup request message or a base station configuration update message, but is not limited thereto.
  • the apparatus may further include: a second acquiring module, configured to be connected to the first acquiring module 1402, configured to acquire a paging feature of the terminal from the radio resource control RRC signaling reported by the terminal; And connecting to the second acquiring module, configured to save the paging feature of the terminal in the information.
  • RRC signaling may include at least one of the following: an RRC connection request message, an RRC connection recovery request message, an RRC re-establishment request message, an RRC connection setup complete message, an RRC connection recovery complete message, and an RRC connection re-establishment completion. Message.
  • the paging feature of the foregoing terminal may be indicated by at least one of: one cell, one bit in a cell, a paging type, and a terminal category.
  • the paging feature of the foregoing terminal may be characterized by a single cell, or by a value of a certain bit of a cell; may be explicitly characterized or implicitly characterized. For example, if the value of a certain indication field is 1, the UE supports the "Non-Anchor carrier-carrying paging message" feature, and the value of a certain indication field is 0, indicating that the UE does not support the "Non-Anchor carrier-bearing paging message” feature; or The signaling includes an indication field and the value of “TRUE” indicates that the UE supports the “Non-Anchor carrier-bearing paging message” feature.
  • the UE does not support the “Non-Anchor carrier”.
  • Carrying a paging message” characteristic; or implicitly indicating whether the UE supports "Non-Anchor carrier-bearing paging message” by different classes of UEs; or indicating whether the UE supports "Non-Anchor carrier-bearing seeking" by "paging type” Call message" (for example: paging type one is a regular paging, only supports paging information on Anchor carrier; paging type 2 is paging of multi-carrier cell, supporting paging on Anchor carrier and on-Anchor carrier Information) and so on.
  • the foregoing apparatus may be located in a base station, and specifically may be located in a base station supporting a Non-Anchor carrier to carry a paging message, but is not limited thereto.
  • the above device may be applied to the NB-IoT system, but is not limited thereto.
  • a base station is further provided, including the bearer searching in the third embodiment.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • a device for transmitting a paging message is also provided in this embodiment.
  • the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
  • the term "module” may implement a combination of software and/or hardware of a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG. 15 is a structural block diagram of a device for sending a paging message according to an embodiment of the present invention. As shown in FIG. 15, the device includes:
  • the determining module 1502 is configured to determine whether the paging feature of the terminal is carried in sending the paging message to the base station
  • the sending module 1504 is connected to the determining module 1502, and is configured to send a paging message to the base station, where the paging message carries the paging feature of the terminal, and the paging feature is whether the terminal has the non-primary Non-Anchor carrier-bearing paging.
  • the ability of the message; the paging feature is used by the base station to determine the carrier carrying the paging message corresponding to the terminal.
  • the paging message sent by the sending module 1504 to the base station carries the paging feature of the terminal, so that the base station can obtain the paging feature of the terminal when the paging message is obtained, and the bearer can be determined according to the paging feature.
  • the carrier of the paging message corresponding to the terminal can further share the paging message of different terminals in the cell by using the determined carrier, thereby solving the problem that the paging capacity of the multi-carrier cell in the related art is limited, and improving the multi-carrier The paging capacity of the cell.
  • the determining module 1502 may also And determining, according to the indication information and the paging characteristic of the terminal, whether the paging feature of the terminal is carried in the paging message sent to the base station; wherein the indication information is used by the base station to indicate whether the cell where the terminal is located supports the Non-Anchor carrier bearer.
  • the indication information of the paging message is determined when the indication information indicates that the cell where the terminal is located supports the Non-Anchor carrier-bearing paging message and the paging characteristic of the terminal is that the terminal has the capability of supporting the Non-Anchor carrier-bearing paging message.
  • the message carries the paging feature of the terminal; if the indication information indicates that the cell in which the terminal is located supports the Non-Anchor carrier-bearing paging message and the paging feature of the terminal is that the terminal does not have the capability of supporting the Non-Anchor carrier to carry the paging message, Determining the paging characteristics of the paging message with or without the terminal.
  • the paging feature of the terminal in the paging message includes: carrying the paging feature of the terminal by using a specific indication field in the paging message sent to the base station; wherein the value of the specific indication field is the first value.
  • the value of the terminal has the capability of supporting the non-primary Non-Anchor carrier to carry the paging message.
  • the terminal does not have the capability of supporting the non-primary Non-Anchor carrier to carry the paging message;
  • the paging feature of the non-bearing terminal in the call message includes: the specific indication field is not included in the paging message.
  • sending module 1504 may exist separately or may be combined with the above determining module 1502, but is not limited thereto.
  • the apparatus may further include: an obtaining module, and the sending module 1504 is configured to send a non-access stratum NAS message or an access stratum AS through the terminal when the terminal initially attaches or the tracking area is updated.
  • the signaling acquires the paging feature of the terminal, or is set to obtain the paging feature of the terminal from the subscription information of the terminal.
  • the foregoing apparatus may further include: a storage module, connected to the acquiring module, configured to store a paging feature of the acquired terminal.
  • the foregoing NAS message may include at least one of the following: an attach request message, a tracking area update TAU request message, but is not limited thereto.
  • the foregoing AS signaling may include at least one of the following: the terminal capability information of the air interface, and the terminal capability information of the S1 port indicates, but is not limited to.
  • the paging feature of the foregoing terminal may be indicated by at least one of: one cell, one bit in a cell, a paging type, and a terminal category.
  • the paging feature of the foregoing terminal may be characterized by a single cell, or by a value of a certain bit of a cell; may be explicitly characterized or implicitly characterized. For example, if the value of a certain indication field is 1, the UE supports the "Non-Anchor carrier-carrying paging message" feature, and the value of a certain indication field is 0, indicating that the UE does not support the "Non-Anchor carrier-bearing paging message” feature; or The signaling includes an indication field and the value of “TRUE” indicates that the UE supports the “Non-Anchor carrier-bearing paging message” feature.
  • the UE does not support the “Non-Anchor carrier”.
  • Carrying a paging message” characteristic; or implicitly indicating whether the UE supports "Non-Anchor carrier-bearing paging message” by different classes of UEs; or indicating whether the UE supports "Non-Anchor carrier-bearing seeking" by "paging type” Call message" (for example: paging type one is a regular paging, only supports paging information on Anchor carrier; paging type 2 is paging of multi-carrier cell, supporting paging on Anchor carrier and on-Anchor carrier Information) and so on.
  • the foregoing apparatus may be located in the mobility management entity MME, and specifically may be the MME in the network architecture shown in FIG. 1 above, but is not limited thereto.
  • the above device may be applied to the NB-IoT system, but is not limited thereto.
  • the embodiment of the present invention further provides an MME, which includes the sending apparatus of the paging message in this embodiment.
  • each of the above modules may be implemented by software or hardware.
  • the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the above modules are in any combination.
  • the forms are located in different processors.
  • a preferred embodiment of the present invention further provides a system, including the base station in Embodiment 3, the MME and the terminal in Embodiment 4.
  • the access layer NAS message or the access layer AS signaling reports the paging feature of the terminal to the MME or reports the paging feature of the terminal to the base station through RRC signaling during the RRC establishment process; wherein, the paging feature Whether the terminal has the ability to support non-primary Non-Anchor carriers to carry paging messages.
  • the terminal is further configured to determine, according to the paging feature of the terminal itself, the carrier and the terminal identifier of the cell where the terminal is located, the carrier that receives the paging message sent by the base station.
  • FIG. 16 is a schematic structural diagram of a system according to a preferred embodiment of the present invention, as shown in FIG.
  • the system in the preferred embodiment includes three network element devices: a UE (corresponding to the above terminal), an eNodeB (corresponding to the base station in the third embodiment), and an MME (corresponding to the MME in the fourth embodiment). among them:
  • the UE contains two modules:
  • the UE "Non-Anchor Carrier Bearer Paging Message” capability reporting module when the UE is in the initial attach or the TAU, the UE reports the paging feature of the "Non-Anchor carrier bearer paging message" of the UE to the UE through the NAS message. MME; in the RRC establishment process, the UE reports the "Non-Anchor Carrier Bearer Paging Message" paging feature of the UE to the eNodeB through RRC signaling;
  • the paging receiving module the UE determines the carrier for receiving the paging according to the information of the “Non-Anchor Carrier Bearer Paging Message” paging feature, the carrier that can carry the paging information, and the UE identifier, and the paging occasion is The paging information is monitored and received on the carrier.
  • the eNodeB consists of two modules:
  • the paging receiving module (corresponding to the first obtaining module 1402 in the embodiment 3) receives the paging message originating from the MME, and parses the "Non-Anchor Carrier Bearer Paging Message" paging characteristic of the UE that may be carried.
  • the UE paging capability receiving module (corresponding to the second acquiring module in the third embodiment) is configured to receive a “Non-Anchor Carrier Bearer Paging Message” paging feature of the UE reported by the UE through the RRC signaling.
  • the UE paging capability storage module (corresponding to the saving module in Embodiment 3) stores a "Non-Anchor Carrier Bearer Paging Message" paging characteristic of the UE reported by the UE through RRC signaling.
  • a paging sending module (corresponding to the determining module 1404 in Embodiment 3): the UE "Non-Anchor Carrier Bearer Paging Message" paging feature carried by the eNodeB according to the paging message sent by the MME or the UE paging capability storage module of the eNodeB
  • the paging feature of the UE "Non-Anchor carrier-carrying paging message" stored in the UE is combined with the carrier and the UE identifier that the cell can carry the paging information to determine the carrier that the UE receives the paging, and sends the paging message on the corresponding carrier.
  • the MME consists of three modules:
  • the UE paging capability receiving module (corresponding to the acquiring module in Embodiment 4) is configured to receive a UE "Non-Anchor Carrier Bearer Paging Message" paging characteristic reported by the UE when it is initially attached or TAU.
  • the UE paging capability storage module (corresponding to the storage module in Embodiment 4) stores a paging feature of the UE "Non-Anchor Carrier Bearer Paging Message" reported by the UE when initially attached or TAU.
  • a paging sending module (corresponding to the sending module 1504 in Embodiment 4): when the MME sends the paging message, optionally carrying the UE "Non-Anchor carrier" stored by the UE paging capability storage module of the MME in the paging information Carrying a paging message "Paging feature; when the UE is in a suspended state, the MME may not carry the paging feature of the UE "Non-Anchor Carrier Bearer Paging Message" in the paging information.
  • Embodiments of the present invention also provide a storage medium.
  • the above storage medium may be set to store program code for executing the steps of the method in Embodiment 1 or 2.
  • the foregoing storage medium may include, but is not limited to: a USB flash drive, only A medium that can store program code, such as a read-only memory (ROM), a random access memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.
  • ROM read-only memory
  • RAM random access memory
  • removable hard disk such as a hard disk, a magnetic disk, or an optical disk.
  • the processor performs the steps of the method in Embodiment 1 or 2 according to the stored program code in the storage medium.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the paging feature of the terminal is obtained by obtaining the paging feature of the terminal from the paging message sent by the MME or the information stored locally by the base station, so that the paging feature of the terminal can be obtained, and then the paging feature can be obtained according to the paging feature.
  • the carrier that carries the paging message corresponding to the terminal is determined, and the paging message of the different terminals in the cell is shared by the determined carrier, thereby solving the problem that the paging capacity of the multi-carrier cell in the related art is limited, and the problem is improved. Paging capacity of a multi-carrier cell.

Landscapes

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

Abstract

本发明提供了一种承载寻呼消息载波的确定、寻呼消息的发送方法及装置，其中，该承载寻呼消息载波的确定方法包括：从移动管理实体MME发送的寻呼消息或基站本地存储的信息中获取终端的寻呼特性，其中，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；依据寻呼特性确定承载与终端对应的寻呼消息的载波。通过本发明，解决了相关技术中多载波小区寻呼容量受限的问题。

Description

承载寻呼消息载波的确定、寻呼消息的发送方法及装置 技术领域
本发明涉及无线通信领域，具体而言，涉及一种承载寻呼消息载波的确定、寻呼消息的发送方法及装置。
背景技术
机器间(Machine to Machine，简称M2M)通信是第五代移动通信技术(5G)目前研究的一个重要课题，也是未来无线通信的一个重要应用领域。在M2M课题里，针对低成本低吞吐量类型终端的特性，提出了窄带物联网(NarowBand-Internet of Things，简称NB-IoT)的研究子课题：也就是在200khz的频谱带宽内为NB-IoT低成本终端(User Equipment，简称UE)提供低吞吐量的无线通讯服务。
考虑到200khz频谱带宽的单载波小区容量很小，大量NB-IoT终端接入难免会容量受限，因此NB-IoT系统引入了多载波小区：一个小区包含多个200khz的载波，其中，只有一个载波承载窄带物理广播信道(Narrowband Physical Broadcast Channel，简称NPBCH)/窄带主同步信道(Narrowband Primary Synchronization Signal，简称NPSS)/窄带辅同步信道(Narrowband Secondary Synchronization Signal，简称NSSS)，称之为主(Anchor)载波，其余载波称之为非主(Non-Anchor)载波。需要说明的是，上述主(Anchor)载波也可以称为锚点载波，非主(Non-Anchor)载波也可以称为非锚点载波。目前标准规定：空闲(IDLE)模式的UE只能驻留于Anchor载波，eNodeB可以根据小区内各载波的负荷情况通过第四条无线资源控制(Radio Resource Control，简称RRC)消息或者后续的RRC消息将业务指派到Non-Anchor载波。这就存在一个问题，寻呼消息只能通过Anchor载波收发。考虑到NB-IoT系统主要承载海量终端的小数据业务，寻呼量较大，将多载波小区内所有用户的寻呼都集中在Anchor载波会导致小区寻呼容量受限。
针对相关技术中的多载波小区寻呼容量受限的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种承载寻呼消息载波的确定、寻呼消息的发送方法及装置，以至少解决相关技术中多载波小区寻呼容量受限的问题。
根据本发明的一个实施例，提供了一种承载寻呼消息载波的确定方法，包括：从移动管理实体(Mobile Management Entity，简称为MME)发送的寻呼消息或基站本地存储的信息中获取终端的寻呼特性，其中，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；依据寻呼特性确定承载与终端对应的寻呼消息的载波。
在本发明实施例中，依据寻呼特性确定承载与终端对应的寻呼消息的载波包括：在寻呼特性为终端具有支持非主Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波；在寻呼特性为终端不具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与终端对应的寻呼消息的载波为主Anchor载波。
在本发明实施例中，确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波包括：根据预先设置的终端所在小区的能够承载寻呼消息的载波和终端标识的对应关系确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波。
在本发明实施例中，从移动管理实体MME发送的寻呼消息中获取终端的寻呼特性之前，方法还包括：通过S1口信令将用于指示终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息发送给MME。
在本发明实施例中，从基站本地存储的信息中获取终端的寻呼特性之前，方法还包括：从终端上报的无线资源控制RRC信令获取终端的寻呼特性；将终端的寻呼特性保存在信息中。
在本发明实施例中，RRC信令包括以下至少之一：RRC连接请求消息，RRC连接恢复请求消息，RRC重建立请求消息，RRC连接建立完成消息，RRC连接恢复完成消息，RRC连接重建立完成消息。
在本发明实施例中，终端的寻呼特性通过以下至少之一来指示：一个信元，一个信元中的一个比特，寻呼类型，终端类别。
根据本发明的一个实施例，提供了一种寻呼消息的发送方法，包括：向基站发送寻呼消息，其中，寻呼消息中携带终端的寻呼特性，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；寻呼特性用于基站确定承载与终端对应的寻呼消息的载波。
在本发明实施例中，在向基站发送寻呼消息之前，方法还包括：确定在向基站发送寻呼消息中是否携带终端的寻呼特性。
在本发明实施例中，确定在向基站发送的寻呼消息中是否携带终端的寻呼特性包括：根据指示信息和终端的寻呼特性确定寻呼消息中是否携带终端的寻呼特性；其中，所述指示信息为从基站获取的用于指示终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息，在指示信息指示终端所在小区支持Non-Anchor载波承载寻呼消息和终端的寻呼特性为终端具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定寻呼消息中携带终端的寻呼特性；在指示信息指示终端所在小区支持Non-Anchor载波承载寻呼消息和终端的寻呼特性为终端不具备支持Non-Anchor载波承载寻呼消息的能力的情况下，确定寻呼消息中携带或者不携带终端的寻呼特性。
在本发明实施例中，寻呼消息中携带终端的寻呼特性包括：通过寻呼消息中的特定指示域来携带终端的寻呼特性；其中，在特定指示域的取值为第一值时，终端具有支持非主Non-Anchor载波承载寻呼消息的能力，在特定指示域的取值为第二值时，终端不具有支持非主Non-Anchor载波承载寻呼消息的能力；向基站发送寻呼消息中不携带终端的寻呼特性包括：在寻呼消息中不包含特定指示域。
在本发明实施例中，从向基站发送寻呼消息之前，方法还包括：在终端初始附着或跟踪区更新时，通过终端发送的非接入层(Non-access stratum，简称NAS)消息或接入层(Access stratum，简称AS)信令获取终端的寻呼特性，或者从所述终端的签约信息中获取所述终端的所述寻呼特性。
在本发明实施例中，NAS消息包括以下至少之一：附着请求消息、跟踪区更新TAU请求消息。
在本发明实施例中，AS信令包括以下至少之一：空口的终端能力信息，S1口的终端能力信息指示。
根据本发明的一个实施例，提供了一种承载寻呼消息载波的确定装置，包括：第一获取模块，设置为从移动管理实体MME发送的寻呼消息或基站本地存储的信息中获取终端的寻呼特性，其中，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；确定模块，设置为依据寻呼特性确定承载与终端对应的寻呼消息的载波。
在本发明实施例中，确定模块还设置为在寻呼特性为终端具有支持非主Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波；以及在寻呼特性为终端不具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与终端对应的寻呼消息的载波为主Anchor载波。
在本发明实施例中，确定模块还设置为根据预先设置的终端所在小区的能够承载寻呼消息的载波和终端标识的对应关系确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波。
在本发明实施例中，装置还包括：发送模块，设置为通过S1口信令将用于指示终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息发送给MME。
在本发明实施例中，装置还包括：第二获取模块，设置为从终端上报的无线资源控制RRC信令获取终端的寻呼特性；保存模块，设置为将终 端的寻呼特性保存在信息中。
在本发明实施例中，RRC信令包括以下至少之一：RRC连接请求消息，RRC连接恢复请求消息，RRC重建立请求消息，RRC连接建立完成消息，RRC连接恢复完成消息，RRC连接重建立完成消息。
在本发明实施例中，终端的寻呼特性通过以下至少之一来指示：一个信元，一个信元中的一个比特，寻呼类型，终端类别。
根据本发明的一个实施例，提供了一种寻呼消息的发送装置，包括：发送模块，设置为向基站发送寻呼消息，其中，寻呼消息中携带终端的寻呼特性，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；寻呼特性用于基站确定承载与终端对应的寻呼消息的载波。
在本发明实施例中，装置还包括：确定模块，设置为确定在向基站发送寻呼消息中是否携带终端的寻呼特性。
在本发明实施例中，确定模块还设置为根据指示信息和终端的寻呼特性确定向基站发送的寻呼消息中是否携带终端的寻呼特性；其中，指示信息为从基站获取的用于指示终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息，在指示信息指示终端所在小区支持Non-Anchor载波承载寻呼消息和终端的寻呼特性为终端具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确寻呼消息中携带终端的寻呼特性；在指示信息指示终端所在小区支持Non-Anchor载波承载寻呼消息和终端的寻呼特性为终端不具备支持Non-Anchor载波承载寻呼消息的能力的情况下，确定寻呼消息中携带或者不携带终端的寻呼特性。
在本发明实施例中，寻呼消息中携带终端的寻呼特性包括：通过寻呼消息中的特定指示域来携带终端的寻呼特性；其中，在特定指示域的取值为第一值时，终端具有支持非主Non-Anchor载波承载寻呼消息的能力，在特定指示域的取值为第二值时，终端不具有支持非主Non-Anchor载波承载寻呼消息的能力；寻呼消息中不携带终端的寻呼特性包括：在寻呼消息中不包含特定指示域。
在本发明实施例中，装置还包括：获取模块，设置为在终端初始附着或跟踪区更新时，通过终端发送的非接入层NAS消息或接入层AS信令获取终端的寻呼特性，或者从终端的签约信息中获取终端的寻呼特性。
在本发明实施例中，NAS消息包括以下至少之一：附着请求消息、跟踪区更新(Tracking Area Update，简称TAU)请求消息。
在本发明实施例中，AS信令包括以下至少之一：空口的终端能力信息，S1口的终端能力信息指示。
根据本发明的一个实施例，提供了一种基站，包括：承载寻呼消息载波的确定装置。
根据本发明的一个实施例，提供了一种移动管理实体MME，包括：上述寻呼消息的发送装置。
根据本发明的一个实施例，提供了一种系统，包括上述基站，上述MME和终端；其中，终端设置为在初始附着或跟踪区更新时，通过非接入层NAS消息或接入层AS信令将终端的寻呼特性上报给MME或者在无线资源控制RRC建立过程中，通过RRC信令将终端的寻呼特性上报给基站；其中，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力。
在本发明实施例中，终端还设置为根据终端自身的寻呼特性、终端所在小区能够承载寻呼消息的载波和终端标识确定接收基站发送的寻呼消息的载波。
根据本发明的又一个实施例，还提供了一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行上述任一项所述的方法。
根据本发明的又一个实施例，还提供了一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行上述任一项所述的方法。
通过本发明，通过从MME发送的寻呼消息或者基站本地保存的信息中获取终端的寻呼特性，使得能够获取该终端的寻呼特性，进而可以根据该寻呼特性确定承载与终端对应的寻呼消息的载波，进而可以将小区内不 同终端的寻呼消息通过确定的载波进行分担，进而解决了相关技术中的多载波小区寻呼容量受限的问题，提高了多载波小区的寻呼容量。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的网络架构示意图；
图2是根据本发明实施例的承载寻呼消息载波的确定方法的流程图；
图3是根据本发明实施例的寻呼消息的发送方法的流程图；
图4是根据本发明优选实施例提供的UE初始附着流程的流程示意图；
图5是根据本发明优选实施例提供的UE初始附着流程触发的UE能力查询流程的示意图；
图6是根据本发明优选实施例提供的空闲模式的TAU流程的示意图；
图7是根据本发明优选实施例提供的空闲模式的TAU流程的示意图；
图8是根据本发明优选实施例提供的连接模式的TAU流程的示意图；
图9是根据本发明优选实施例提供的连接模式的TAU流程触发的UE能力查询流程的示意图；
图10是根据本发明优选实施例提供的基站上报其是否支持非主Non-Anchor载波承载寻呼消息的能力给MME的示意图；
图11是根据本发明优选实施例提供的基站获取终端的寻呼特性的方法的流程示意图；
图12是根据本发明优选实施例提供的支持基于用户面优化的业务流程的UE发起基于用户面优化流程的业务的RRC连接建立过程的流程示意图；
图13是根据本发明优选实施例提供的给处于用户面挂起状态的UE发送寻呼消息时的“Non-Anchor载波承载寻呼消息”寻呼特性获取流程的流程示意图；
图14是根据本发明实施例的承载寻呼消息载波的确定装置的结构框图；
图15是根据本发明实施例的寻呼消息的发送装置的结构框图；
图16是根据本发明优选实施例提供的系统的结构示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
实施例1
在本申请实施例中，一个寻呼容量改进的办法是：非主Non-Anchor载波也可以承载寻呼消息，多载波小区内不同终端的寻呼消息通过主Anchor载波和非主Non-Anchor载波负荷分担。但是在引入“Non-Anchor载波承载寻呼消息”特性后：支持该特性的eNodeB下可能存在支持该特性的UE和不支持该特性的UE。eNodeB在给UE发送寻呼消息时首先需要确定UE是否支持该特性，才能确定该UE的寻呼在多载波小区内的哪个载波下发。但是由于寻呼消息是呼叫连接过程中的第一条空口消息，eNodeB在发送寻呼消息时无法获取UE的“Non-Anchor载波承载寻呼消息”寻呼特性。因而，本申请实施例提供了一种承载寻呼消息载波的确定方法。
本申请实施例的方法可以运行于图1所示的网络架构上，如图1所示，该网络架构包括：终端，基站和移动管理实体MME，其中，该终端可以 与基站和MME进行交互，基站和MME之间也可以进行交互。
在本实施例中提供了一种运行于上述网络架构的承载寻呼消息载波的确定方法，图2是根据本发明实施例的承载寻呼消息载波的确定方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，从移动管理实体MME发送的寻呼消息或基站本地存储的信息中获取终端的寻呼特性，其中，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；
步骤S204，依据寻呼特性确定承载与终端对应的寻呼消息的载波。
通过上述步骤，通过从MME发送的寻呼消息或者基站本地保存的信息中获取终端的寻呼特性，使得能够获取该终端的寻呼特性，进而可以根据该寻呼特性确定承载与终端对应的寻呼消息的载波，进而可以将小区内不同终端的寻呼消息通过确定的载波进行分担，进而解决了相关技术中的多载波小区寻呼容量受限的问题，提高了多载波小区的寻呼容量。
需要说明的是，从移动管理实体MME发送的寻呼消息中获取终端的寻呼特性可以表现为，该寻呼消息中携带该终端的寻呼特性，在获取到该寻呼消息后，通过解析寻呼消息中的信息来获取终端的寻呼特性，但并不限于此。
需要说明的是，上述步骤S204可以表现为：在寻呼特性为终端具有支持非主Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波；在寻呼特性为终端不具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与终端对应的寻呼消息的载波为主Anchor载波。即通过终端的寻呼特性确定是采用哪种载波承载寻呼消息，进而使得Non-Anchor载波可以分担部分Anchor载波的承载寻呼消息的工作，不会将所有的用户的寻呼后集中在Anchor载波上，避免了小区寻呼容量受限的问题。
需要说明的是，由于一个小区内的Non-Anchor载波的数量可能有多个，因而到底在哪个Non-Anchor载波或者哪几个Non-Anchor载波上承载 该终端的寻呼消息还需要进一步确认，因而在本发明的一个实施例中，确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波包括：根据预先设置的终端所在小区的能够承载寻呼消息的载波和终端标识的对应关系确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波。
上述对应关系可以通过以下方式表现，但并不限于此：终端标识与能够承载寻呼消息的载波的数目做除法运算，将该除法运算得到的商值作为该终端标识对应的载波的编号，在此情况下，确定的承载与终端对应的寻呼消息的载波为对应的载波编号对应的载波，该载波为主Anchor载波，则确定的承载与终端对应的寻呼消息的载波就为主Anchor载波，该载波为非主Non-Anchor载波，则确定的承载与终端对应的寻呼消息的载波就为非主Non-Anchor载波。
需要说明的是，在获知终端的寻呼特性之前，还应当获知终端所在小区是否支持Non-Anchor载波承载寻呼消息，即在终端所在小区支持Non-Anchor载波承载寻呼消息的情况下，获取终端的寻呼特性会更有意义，因而在通过MME发送的寻呼消息中获取终端的寻呼特性的情况下，在本发明的一个实施例中，在上述步骤S202之前，上述方法还可以包括：通过S1口信令将用于指示终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息发送给MME。通过将该指示信息发送给MME，以便MME决策在发送给基站的寻呼消息中是否要携带终端的寻呼特性，比如在该指示信息用于指示终端所在小区不支持Non-Anchor载波承载寻呼消息的情况下，MME发送给基站的寻呼消息中不携带终端的寻呼特性，或者携带终端的寻呼特性，都可以；在该指示信息用于指示终端所在小区支持Non-Anchor载波承载寻呼消息的情况下，MME发送给基站的寻呼消息中携带终端的寻呼特性，但并不限于此。
需要说明的是，上述S1口信令可以是S1建立请求消息或者基站配置更新消息，但并不限于此。
在本发明的一个实施例中，在通过基站本地存储的信息中获取终端的寻呼特性的情况下，在上述步骤S202之前，上述方法还可以包括：从终端上报的无线资源控制RRC信令获取终端的寻呼特性；将终端的寻呼特性保存在信息中。通过将终端的寻呼特性保存在基站的信息中，以备后续使用。
需要说明的是，上述RRC信令可以包括以下至少之一，但并不限于此：RRC连接请求消息，RRC连接恢复请求消息，RRC重建立请求消息，RRC连接建立完成消息，RRC连接恢复完成消息，RRC连接重建立完成消息。
需要说明的是，上述终端的寻呼特性可以通过以下至少之一指示：一个信元，一个信元中的一个比特，寻呼类型，终端类别。
具体地，上述终端的寻呼特性可以通过一个单独的信元来表征，也可以通过一个信元的某个比特的取值来表征；可以通过显式表征，也可以隐式表征。比如：某个指示域取值为1表示UE支持“Non-Anchor载波承载寻呼消息”特性，某个指示域取值为0表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者信令中包含了某个指示域且取值为“TRUE”表示UE支持“Non-Anchor载波承载寻呼消息”特性，信令中未包含某个指示域则表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者通过不同类别的UE来隐含指示UE是否支持“Non-Anchor载波承载寻呼消息”；或者通过“寻呼类型”来指示UE是否支持“Non-Anchor载波承载寻呼消息”(比如：寻呼类型一为常规的寻呼，只支持在Anchor载波承载寻呼信息；寻呼类型二为多载波小区的寻呼，支持在Anchor载波和on-Anchor载波承载寻呼信息)等。
需要说明的是，上述步骤的执行主体可以是上述图1所示的基站，具体地，可以是支持Non-Anchor载波承载寻呼消息的基站，但并不限于此。
需要说明的是，上述方法可以应用于NB-IoT系统中，但并不限于此。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根 据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
实施例2
本申请实施例的方法也可以运行于图1所示的网络架构上，因而在本实施例中还提供了一种运行于上述网络架构的寻呼消息的发送方法，图3是根据本发明实施例的寻呼消息的发送方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，确定在向基站发送寻呼消息中是否携带终端的寻呼特性；
步骤S304，向基站发送寻呼消息，其中，寻呼消息中携带终端的寻呼特性，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；寻呼特性用于基站确定承载与终端对应的寻呼消息的载波。
通过上述步骤，在向基站发送的寻呼消息中携带终端的寻呼特性，使得基站在获取到寻呼消息时能够获取到终端的寻呼特性，进而可以根据该寻呼特性确定承载与终端对应的寻呼消息的载波，进而可以将小区内不同终端的寻呼消息通过确定的载波进行分担，进而解决了相关技术中的多载波小区寻呼容量受限的问题，提高了多载波小区的寻呼容量。
需要说明的是，向基站发送的寻呼消息中是否携带终端的寻呼特性还需要进行判断，在不需要携带终端的寻呼特性的情况下可以不携带，因而在本发明的一个实施例中，上述步骤S302可以包括：根据指示信息和终端的寻呼特性确定向基站发送寻呼消息中是否携带终端的寻呼特性；其中，指示信息为从基站获取的用于指示终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息，在指示信息指示终端所在小区支持 Non-Anchor载波承载寻呼消息和终端的寻呼特性为终端具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定寻呼消息中携带终端的寻呼特性；在指示信息指示终端所在小区支持Non-Anchor载波承载寻呼消息和终端的寻呼特性为终端不具备支持Non-Anchor载波承载寻呼消息的能力的情况下，确定寻呼消息中携带或者不携带终端的寻呼特性。
需要说明的是，寻呼消息中携带终端的寻呼特性包括：通过寻呼消息中的特定指示域来携带终端的寻呼特性；其中，在特定指示域的取值为第一值时，终端具有支持非主Non-Anchor载波承载寻呼消息的能力，在特定指示域的取值为第二值时，终端不具有支持非主Non-Anchor载波承载寻呼消息的能力；寻呼消息中不携带终端的寻呼特性包括：在寻呼消息中不包含特定指示域。
需要说明的是，在指示信息指示终端所在小区不支持Non-Anchor载波承载寻呼消息的情况下，确定向基站发送寻呼消息中不携带终端的寻呼特性。
需要说明的是，上述步骤S304可以不依赖于步骤S302，即上述步骤S304可以单独执行，也可以结合步骤S302一起执行，并不限于此。
在本发明的一个实施例中，在上述步骤S304之前，上述方法还可以包括：在终端初始附着或跟踪区更新时，通过终端发送的非接入层NAS消息或接入层AS信令获取终端的寻呼特性，或者从终端的签约信息中获取终端的寻呼特性。
需要说明的是，通过终端发送的非接入层NAS消息或接入层AS信令获取终端的寻呼特性之后，上述方法还可以包括：存储获取到的终端的寻呼特性。
需要说明的是，上述NAS消息可以包括以下至少之一：附着请求消息、跟踪区更新TAU请求消息，但并不限于此。上述AS信令可以包括以下至少之一：空口的终端能力信息，S1口的终端能力信息指示，但并不限于此。
需要说明的是，上述终端的寻呼特性可以通过以下至少之一指示：一个信元，一个信元中的一个比特，寻呼类型，终端类别。
具体地，上述终端的寻呼特性可以通过一个单独的信元来表征，也可以通过一个信元的某个比特的取值来表征；可以通过显式表征，也可以隐式表征。比如：某个指示域取值为1表示UE支持“Non-Anchor载波承载寻呼消息”特性，某个指示域取值为0表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者信令中包含了某个指示域且取值为“TRUE”表示UE支持“Non-Anchor载波承载寻呼消息”特性，信令中未包含某个指示域则表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者通过不同类别的UE来隐含指示UE是否支持“Non-Anchor载波承载寻呼消息”；或者通过“寻呼类型”来指示UE是否支持“Non-Anchor载波承载寻呼消息”(比如：寻呼类型一为常规的寻呼，只支持在Anchor载波承载寻呼信息；寻呼类型二为多载波小区的寻呼，支持在Anchor载波和on-Anchor载波承载寻呼信息)等。
需要说明的是，上述步骤的执行主体可以是移动管理实体MME，具体的，可以是上述图1所示的网络架构中的MME，但并不限于此。
需要说明的是，上述方法可以应用于NB-IoT系统中，但并不限于此。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
为了更好地理解本发明实施例1和2，以下结合优选的实施例对本发明做进一步解释。
本发明优选实施例要解决的技术问题是针对NB-IoT系统中eNodeB如何获取UE的“Non-Anchor载波承载寻呼消息”寻呼特性提出一种方法。该方法可以解决eNodeB在发送寻呼消息时无法获取UE的”Non-Anchor载波承载寻呼消息”寻呼特性的问题。
本发明优选实施例提出的一种eNodeB获取UE的”Non-Anchor载波承载寻呼消息”寻呼特性的方法包括：
当UE在初始附着(Initial Attach)或者跟踪区更新(TRACKING AREA UPDATE，简称TAU)时，UE通过非接入层(Non-Access-Stratum，简称NAS)消息或接入层(Access-Stratum，简称AS)信令将UE的“Non-Anchor载波承载寻呼消息”寻呼特性上报给移动性管理实体(Mobility Management Entity，简称MME)；MME在发起寻呼时，通过寻呼消息将UE的“Non-Anchor载波承载寻呼消息”寻呼特性携带给eNodeB；eNodeB通过解析寻呼消息中的信息来来获取UE的“Non-Anchor载波承载寻呼消息”寻呼特性，并依据获取的能力进行多载波小区中寻呼载波的选择。其中：NAS消息可以是附着请求或TAU请求消息；AS信令可以是空口的“UE能力信息”和S1口的“UE能力信息指示”。
在本发明优选实施例中，eNodeB通过S1口信令将小区是否支持Non-Anchor载波发送寻呼的指示传递给MME，以便MME决策在发送给eNodeB的寻呼消息中是否携带UE“Non-Anchor载波承载寻呼消息”特性支持指示。
在本发明优选实施例中，UE通过RRC信令将UE的“Non-Anchor载波承载寻呼消息”寻呼特性上报给eNodeB；eNodeB在RRC连接释放时保存UE的“Non-Anchor载波承载寻呼消息”寻呼特性；当再次寻呼UE时，eNodeB根据自己保存的UE“Non-Anchor载波承载寻呼消息”寻呼特性来进行多载波小区中寻呼载波的选择。其中的RRC信令可以是：RRC连接请求、RRC连接恢复请求、RRC重建立请求、RRC连接建立完成、RRC连接恢复完成、RRC连接重建立完成。
其中，UE的“Non-Anchor载波承载寻呼消息”寻呼特性可以通过一个单独的信元来表征，也可以通过一个信元的某个比特的取值来表征；可以通过显式表征，也可以隐式表征。比如：某个指示域取值为1表示UE支持“Non-Anchor载波承载寻呼消息”特性，某个指示域取值为0表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者信令中包含了某个指示域且取值为“TRUE”表示UE支持“Non-Anchor载波承载寻呼消息”特性，信令中未包含某个指示域则表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者通过不同类别的UE来隐含指示UE是否支持“Non-Anchor载波承载寻呼消息”；或者通过“寻呼类型”来指示UE是否支持“Non-Anchor载波承载寻呼消息”(比如：寻呼类型一为常规的寻呼，只支持在Anchor载波承载寻呼信息；寻呼类型二为多载波小区的寻呼，支持在Anchor载波和on-Anchor载波承载寻呼信息)等。
图4是根据本发明优选实施例提供的UE初始附着流程的流程示意图，图4所示的本发明优选实施例提供了UE将自己的“Non-Anchor载波承载寻呼消息”寻呼特性指示通过NAS消息上报给MME，如图4所示，该流程包括：
UE在RRC连接建立完成消息中携带附着请求(Attach Request)的NAS PDU。
eNodeB收到RRC连接建立完成消息后，将其中携带附着请求的NAS PDU通过初始UE消息传递给MME。其中携带附着请求的NAS PDU中携带UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
MME收到携带附着请求的NAS PDU后，解析其中的UE“Non-Anchor载波承载寻呼消息”寻呼特性指示并保存下来供后续寻呼时使用。
图5是根据本发明优选实施例提供的UE初始附着流程触发的UE能力查询流程的示意图，如图5所示的本发明优选实施例提供了UE将自己的“Non-Anchor载波承载寻呼消息”寻呼特性指示通过AS信令上报给MME的示例，如图5所示，该流程包括：
UE初始附着流程触发eNodeB发起UE能力查询流程(eNodeB给UE发送“UE能力查询”消息)
UE将自己的能力通过“UE能力信息”上报给eNodeB，其中的UE能力包含UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
eNodeB将收到的UE能力通过“UE能力信息指示”上报给MME，其中的UE能力包含UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
MME收到“UE能力信息指示”后，解析其中的UE“Non-Anchor载波承载寻呼消息”寻呼特性指示并保存下来供后续寻呼时使用。
图6是根据本发明优选实施例提供的空闲模式的TAU流程的示意图，如图6所示的本发明优选实施例提供了UE将自己的“Non-Anchor载波承载寻呼消息”寻呼特性指示通过NAS消息上报给MME的又一示例，该流程包括：
UE在RRC连接建立完成消息中携带跟踪区更新(TAU)的NAS PDU。其中携带TAU的NAS PDU中携带UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
eNodeB收到RRC连接建立完成消息，将其中携带TAU的NAS PDU通过初始UE消息传递给MME。其中携带TAU的NAS PDU中携带UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
MME收到携带TAU的NAS PDU后，解析其中的UE“Non-Anchor载波承载寻呼消息”寻呼特性指示并保存下来供后续寻呼时使用。
图7是根据本发明优选实施例提供的空闲模式的TAU流程的示意图，如图7所示的本发明优选实施例提供了UE将自己的“Non-Anchor载波承载寻呼消息”寻呼特性指示通过AS信令上报给MME的又一示例，该流程包括：
UE的TAU流程触发eNodeB发起UE能力查询流程(eNodeB给UE发送“UE能力查询”消息)。
UE将自己的能力通过“UE能力信息”上报给eNodeB，其中的UE能力包含UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
eNodeB将收到的UE能力通过“UE能力信息指示”上报给MME，其中的UE能力包含UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
MME收到“UE能力信息指示”后，解析其中的UE“Non-Anchor载波承载寻呼消息”寻呼特性指示并保存下来供后续寻呼时使用。
图8是根据本发明优选实施例提供的连接模式的TAU流程的示意图，如图8所示的本发明优选实施例提供了UE将自己的“Non-Anchor载波承载寻呼消息”寻呼特性指示通过NAS消息上报给MME的再一示例，该流程包括：
UE在RRC连接建立完成后，通过上行链路信息传输(ULInformationTransfer)消息中携带跟踪区更新(TAU)的NAS PDU。其中携带TAU的NAS PDU中携带UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
eNodeB收到上行链路信息传输消息，将其中携带TAU的NAS PDU通过上行链路NAS传输消息(UPLINK NAS TRANSPORT)传递给MME。其中携带TAU的NAS PDU中携带UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
MME收到携带TAU的NAS PDU后，解析其中的UE“Non-Anchor载波承载寻呼消息”寻呼特性指示并保存下来供后续寻呼时使用。
图9是根据本发明优选实施例提供的连接模式的TAU流程触发的UE能力查询流程的示意图，如图9所示的本发明优选实施例提供了UE将自己的“Non-Anchor载波承载寻呼消息”寻呼特性指示通过AS信令上报给MME的再一示例，该流程包括：
连接模式的UE的TAU流程触发eNodeB发起UE能力查询流程(eNodeB给UE发送“UE能力查询”消息)。
UE将自己的能力通过“UE能力信息”上报给eNodeB，其中的UE能力包含UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
eNodeB将收到的UE能力通过“UE能力信息指示”上报给MME，其中的UE能力包含UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
MME收到“UE能力信息指示”后，解析其中的UE“Non-Anchor载波承载寻呼消息”寻呼特性指示并保存下来供后续寻呼时使用。
图10是根据本发明优选实施例提供的基站上报其是否支持非主Non-Anchor载波承载寻呼消息的能力给MME的示意图，如图10所示，本发明优选实施例提供了eNodeB上报其是否支持Non-Anchor载波发送寻呼的示例，该流程包括：
eNodeB通过S1口信令将其是否支持Non-Anchor载波发送寻呼的指示传递给MME，以便MME决策在发送给eNodeB的寻呼消息中是否携带UE“Non-Anchor载波承载寻呼消息”特性支持指示。如果eNodeB支持Non-Anchor载波发送寻呼，则MME在发送给eNodeB的寻呼消息中携带UE“Non-Anchor载波承载寻呼消息”特性支持指示；否则，MME在发送给eNodeB的寻呼消息中不需要携带UE“Non-Anchor载波承载寻呼消息”特性支持指示。
eNodeB上报其是否支持Non-Anchor载波发送寻呼的指示传递给MME的S1口信令可以是“S1建立请求”或“eNodeB配置更新”消息；可以是以小区为单位或者以eNodeB为单位来上报；可以同过一个单独的信元来表征，也可以通过一个信元的某个比特的取值来表征；可以通过显式表征，也可以隐式表征。比如：某个指示域取值为1表示eNodeB支持Non-Anchor载波发送寻呼，某个指示域取值为0表示eNodeB不支持Non-Anchor载波发送寻呼；或者信令中包含了某个指示域且取值为“TRUE”表示eNodeB支持Non-Anchor载波发送寻呼，信令中未包含某个指示域则表示eNodeB不支持Non-Anchor载波发送寻呼。
图11是根据本发明优选实施例提供的基站获取终端的寻呼特性的方法的流程示意图，如图11所示，本发明优选实施例提供了eNodeB从MME发送的寻呼消息中获取UE“Non-Anchor载波承载寻呼消息”寻呼特性的示例，该流程包括：
MME发送给eNodeB的寻呼消息中携带UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
eNodeB根据收到的寻呼消息中携带的UE“Non-Anchor载波承载寻呼消息”寻呼特性指示判决UE是否支持“Non-Anchor载波承载寻呼消息”特性：如果不支持，则在Anchor载波给UE发送寻呼消息；否则，根据小区可承载寻呼信息的载波和UE标识等信息来决策承载该UE寻呼信息的载波，并在该载波上给UE发送寻呼消息。
图12是根据本发明优选实施例提供的支持基于用户面优化的业务流程的UE发起基于用户面优化流程的业务的RRC连接建立过程的流程示意图，如图12所示，本发明优选实施例提供了UE通过RRC信令将UE的“Non-Anchor载波承载寻呼消息”寻呼特性上报给eNodeB的示例，该流程包括：
UE在RRC建立完成消息中携带UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
当eNodeB决定挂起RRC连接时，存储UE上下文，同时存储UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示。
其中，基于用户面优化的业务流程是指NB-IoT系统针对小数据业务信令优化引入的一种业务流程：终端和网络使用数据无线承载(DRB，Data Radio Bearer)传输数据，数据传输完毕后，双方保存承载信息上下文、接入层(AS，Access Stratum)安全上下文等信息来挂起RRC连接；后续再次发送数据时，双方通过恢复RRC连接来快速恢复DRB承载的使用。
图13是根据本发明优选实施例提供的给处于用户面挂起状态的UE发送寻呼消息时的“Non-Anchor载波承载寻呼消息”寻呼特性获取流程 的流程示意图，如图13所示，本发明优选实施例提供了eNodeB从UE上下文存储信息中获取UE“Non-Anchor载波承载寻呼消息”寻呼特性的示例，该流程包括：
当eNodeB给处于用户面挂起状态的UE发送寻呼消息时，首先在eNodeB存储的信息中获取UE“Non-Anchor载波承载寻呼消息”寻呼特性。然后eNodeB根据UE的“Non-Anchor载波承载寻呼消息”寻呼特性指示判决UE是否支持“Non-Anchor载波承载寻呼消息”特性：如果不支持，则在Anchor载波给UE发送寻呼消息；否则，根据小区可承载寻呼信息的载波和UE标识等信息来决策承载该UE寻呼信息的载波，并在该载波上给UE发送寻呼消息。
实施例3
在本实施例中还提供了一种承载寻呼消息载波的确定装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图14是根据本发明实施例的承载寻呼消息载波的确定装置的结构框图，如图14所示，该装置包括：
第一获取模块1402，设置为从移动管理实体MME发送的寻呼消息或基站本地存储的信息中获取终端的寻呼特性，其中，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；
确定模块1404，与上述第一获取模块1402连接，设置为依据寻呼特性确定承载与终端对应的寻呼消息的载波。
通过上述装置，通过上述第一获取模块1402从从MME发送的寻呼消息或者基站本地保存的信息中获取终端的寻呼特性，使得能够获取该终端的寻呼特性，进而上述确定模块1404可以根据获取的终端的寻呼特性确定承载与终端对应的寻呼消息的载波，进而可以将小区内不同终端的寻 呼消息通过确定的载波进行分担，进而解决了相关技术中的多载波小区寻呼容量受限的问题，提高了多载波小区的寻呼容量。
需要说明的是，上述确定模块1404还可以设置为在获取到该寻呼消息后，通过解析寻呼消息中的信息来获取终端的寻呼特性。
在本发明的一个实施例中，上述确定模块1404还可以设置为在寻呼特性为终端具有支持非主Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波；以及在寻呼特性为终端不具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与终端对应的寻呼消息的载波为主Anchor载波。即通过上述确定模块1404使得Non-Anchor载波可以分担部分Anchor载波的承载寻呼消息的工作，不会将所有的用户的寻呼后集中在Anchor载波上，避免了小区寻呼容量受限的问题。
需要说明的是，由于一个小区内的Non-Anchor载波的数量可能有多个，因而到底在哪个Non-Anchor载波或者哪几个Non-Anchor载波上承载该终端的寻呼消息还需要进一步确认，因而在本发明的一个实施例中，上述确定模块1404还可以设置为根据预先设置的终端所在小区的能够承载寻呼消息的载波和终端标识的对应关系确定承载与终端对应的寻呼消息的载波为主Anchor载波或非主Non-Anchor载波。
在本发明的一个实施例中，上述装置还可以包括：发送模块，与上述第一获取模块1402连接，设置为通过S1口信令将用于指示终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息发送给MME。通过上述发送模块将该指示信息发送给MME，以便MME决策在发送给基站的寻呼消息中是否要携带终端的寻呼特性，比如在该指示信息用于指示终端所在小区不支持Non-Anchor载波承载寻呼消息的情况下，MME发送给基站的寻呼消息中不携带终端的寻呼特性；在该指示信息用于指示终端所在小区支持Non-Anchor载波承载寻呼消息的情况下，MME发送给基站的寻呼消息中携带终端的寻呼特性，但并不限于此。
需要说明的是，上述S1口信令可以是S1建立请求消息或者基站配置更新消息，但并不限于此。
在本发明的一个实施例中，上述装置还可以包括：第二获取模块，与上述第一获取模块1402连接，设置为从终端上报的无线资源控制RRC信令获取终端的寻呼特性；保存模块，与上述第二获取模块连接，设置为将终端的寻呼特性保存在信息中。
需要说明的是，上述RRC信令可以包括以下至少之一：RRC连接请求消息，RRC连接恢复请求消息，RRC重建立请求消息，RRC连接建立完成消息，RRC连接恢复完成消息，RRC连接重建立完成消息。
需要说明的是，上述终端的寻呼特性可以通过以下至少之一指示：一个信元，一个信元中的一个比特，寻呼类型，终端类别。
具体地，上述终端的寻呼特性可以通过一个单独的信元来表征，也可以通过一个信元的某个比特的取值来表征；可以通过显式表征，也可以隐式表征。比如：某个指示域取值为1表示UE支持“Non-Anchor载波承载寻呼消息”特性，某个指示域取值为0表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者信令中包含了某个指示域且取值为“TRUE”表示UE支持“Non-Anchor载波承载寻呼消息”特性，信令中未包含某个指示域则表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者通过不同类别的UE来隐含指示UE是否支持“Non-Anchor载波承载寻呼消息”；或者通过“寻呼类型”来指示UE是否支持“Non-Anchor载波承载寻呼消息”(比如：寻呼类型一为常规的寻呼，只支持在Anchor载波承载寻呼信息；寻呼类型二为多载波小区的寻呼，支持在Anchor载波和on-Anchor载波承载寻呼信息)等。
需要说明的是，上述装置可以位于基站中，具体地，可以位于支持Non-Anchor载波承载寻呼消息的基站，但并不限于此。
需要说明的是，上述装置可以应用于NB-IoT系统中，但并不限于此。
在本发明实施例中，还提供了一种基站，包括本实施例3中的承载寻 呼消息载波的确定装置。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例4
在本实施例中还提供了一种寻呼消息的发送装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图15是根据本发明实施例的寻呼消息的发送装置的结构框图，如图15所示，该装置包括：
确定模块1502，设置为确定在向基站发送寻呼消息中是否携带终端的寻呼特性
发送模块1504，与上述确定模块1502连接，设置为向基站发送寻呼消息，其中，寻呼消息中携带终端的寻呼特性，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；寻呼特性用于基站确定承载与终端对应的寻呼消息的载波。
通过上述装置，在发送模块1504向基站发送的寻呼消息中携带终端的寻呼特性，使得基站在获取到寻呼消息时能够获取到终端的寻呼特性，进而可以根据该寻呼特性确定承载与终端对应的寻呼消息的载波，进而可以将小区内不同终端的寻呼消息通过确定的载波进行分担，进而解决了相关技术中的多载波小区寻呼容量受限的问题，提高了多载波小区的寻呼容量。
需要说明的是，上述发送模块1504向基站发送的寻呼消息中是否携带终端的寻呼特性还需要进行判断，在不需要携带终端的寻呼特性的情况下可以不携带，因而在本发明的一个实施例中，上述确定模块1502还可 以设置为根据指示信息和终端的寻呼特性确定向基站发送寻呼消息中是否携带终端的寻呼特性；其中，指示信息为从基站获取的用于指示终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息，在指示信息指示终端所在小区支持Non-Anchor载波承载寻呼消息和终端的寻呼特性为终端具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定寻呼消息中携带终端的寻呼特性；在指示信息指示终端所在小区支持Non-Anchor载波承载寻呼消息和终端的寻呼特性为终端不具备支持Non-Anchor载波承载寻呼消息的能力的情况下，确定寻呼消息中携带或者不携带终端的寻呼特性。
需要说明的是，寻呼消息中携带终端的寻呼特性包括：通过向基站发送的寻呼消息中的特定指示域来携带终端的寻呼特性；其中，在特定指示域的取值为第一值时，终端具有支持非主Non-Anchor载波承载寻呼消息的能力，在特定指示域的取值为第二值时，终端不具有支持非主Non-Anchor载波承载寻呼消息的能力；寻呼消息中不携带终端的寻呼特性包括：在寻呼消息中不包含特定指示域。
需要说明的是，上述发送模块1504可以单独存在，也可以与上述确定模块1502结合存在，但并不限于此。
在本发明的一个实施例中，上述装置还可以包括：获取模块，与上述发送模块1504设置为在终端初始附着或跟踪区更新时，通过终端发送的非接入层NAS消息或接入层AS信令获取终端的寻呼特性，或者设置为从终端的签约信息中获取终端的寻呼特性。
需要说明的是，上述装置还可以包括：存储模块，与上述获取模块连接，设置为存储获取的终端的寻呼特性。
需要说明的是，上述NAS消息可以包括以下至少之一：附着请求消息、跟踪区更新TAU请求消息，但并不限于此。上述AS信令可以包括以下至少之一：空口的终端能力信息，S1口的终端能力信息指示，但并不限于此。
需要说明的是，上述终端的寻呼特性可以通过以下至少之一指示：一个信元，一个信元中的一个比特，寻呼类型，终端类别。
具体地，上述终端的寻呼特性可以通过一个单独的信元来表征，也可以通过一个信元的某个比特的取值来表征；可以通过显式表征，也可以隐式表征。比如：某个指示域取值为1表示UE支持“Non-Anchor载波承载寻呼消息”特性，某个指示域取值为0表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者信令中包含了某个指示域且取值为“TRUE”表示UE支持“Non-Anchor载波承载寻呼消息”特性，信令中未包含某个指示域则表示UE不支持“Non-Anchor载波承载寻呼消息”特性；或者通过不同类别的UE来隐含指示UE是否支持“Non-Anchor载波承载寻呼消息”；或者通过“寻呼类型”来指示UE是否支持“Non-Anchor载波承载寻呼消息”(比如：寻呼类型一为常规的寻呼，只支持在Anchor载波承载寻呼信息；寻呼类型二为多载波小区的寻呼，支持在Anchor载波和on-Anchor载波承载寻呼信息)等。
需要说明的是，上述装置可以是位于移动管理实体MME，具体的，可以是上述图1所示的网络架构中的MME，但并不限于此。
需要说明的是，上述装置可以应用于NB-IoT系统中，但并不限于此。
本发明实施例还提供了一种MME，包括本实施例中的寻呼消息的发送装置。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
实施例5
本发明优选实施例还提供了一种系统，包括实施例3中的基站，实施例4中的MME和终端。
需要说明的是，上述终端设置为在初始附着或跟踪区更新时，通过非 接入层NAS消息或接入层AS信令将终端的寻呼特性上报给MME或者在无线资源控制RRC建立过程中，通过RRC信令将终端的寻呼特性上报给基站；其中，寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力。
需要说明的是，上述终端还设置为根据终端自身的寻呼特性、终端所在小区能够承载寻呼消息的载波和终端标识确定接收基站发送的寻呼消息的载波。
为了更好地理解本发明实施例3至5，以下结合优选实施例做进一步解释。
本发明优选实施例还提出一种eNodeB获取UE的“Non-Anchor载波承载寻呼消息”寻呼特性的系统，图16是根据本发明优选实施例提供的系统的结构示意图，如图16所示，该优选实施例中的系统包括：UE(相当于上述终端)、eNodeB(相当于上述实施例3中的基站)、MME(相当于上述实施例4中的MME)三个网元设备。其中：
UE包含两个模块：
UE“Non-Anchor载波承载寻呼消息”能力上报模块：当UE在初始附着(Initial Attach)或者TAU时，UE通过NAS消息将UE的“Non-Anchor载波承载寻呼消息”寻呼特性上报给MME；UE在RRC建立过程中，通过RRC信令将UE的“Non-Anchor载波承载寻呼消息”寻呼特性上报给eNodeB；
寻呼接收模块：UE根据自己的“Non-Anchor载波承载寻呼消息”寻呼特性、小区可承载寻呼信息的载波和UE标识等信息来确定接收寻呼的载波，并在寻呼时机在该载波上监控和接收寻呼信息。
eNodeB包括两个模块：
寻呼接收模块(相当于实施例3中的第一获取模块1402)：接收来源于MME的寻呼消息，并从中解析可能携带的UE的“Non-Anchor载波承载寻呼消息”寻呼特性。
UE寻呼能力接收模块(相当于实施例3中的第二获取模块)：接收UE通过RRC信令上报的UE的“Non-Anchor载波承载寻呼消息”寻呼特性。
UE寻呼能力存储模块(相当于实施例3中的保存模块)：存储UE通过RRC信令上报的UE的“Non-Anchor载波承载寻呼消息”寻呼特性。
寻呼发送模块(相当于实施例3中的确定模块1404)：eNodeB根据MME发送的寻呼消息携带的UE“Non-Anchor载波承载寻呼消息”寻呼特性或者eNodeB的UE寻呼能力存储模块里存储的UE“Non-Anchor载波承载寻呼消息”寻呼特性，结合小区可承载寻呼信息的载波和UE标识等信息来确定UE接收寻呼的载波，并在对应载波上发送寻呼消息给UE。
MME包括三个模块：
UE寻呼能力接收模块(相当于实施例4中的获取模块)：接收UE在初始附着(Initial Attach)或者TAU时上报的UE“Non-Anchor载波承载寻呼消息”寻呼特性。
UE寻呼能力存储模块(相当于实施例4中的存储模块)：存储UE在初始附着或者TAU时上报的UE“Non-Anchor载波承载寻呼消息”寻呼特性。
寻呼发送模块(相当于实施例4中的发送模块1504)：当MME发送寻呼消息时，可选地在寻呼信息中携带MME的UE寻呼能力存储模块存储的UE“Non-Anchor载波承载寻呼消息”寻呼特性；当UE处于挂起状态时，MME可以在寻呼信息中不携带UE“Non-Anchor载波承载寻呼消息”寻呼特性。
实施例6
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行实施例1或2中的方法的步骤的程序代码。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只 读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，在本实施例中，处理器根据存储介质中已存储的程序代码执行实施例1或2中的方法的步骤。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
基于本发明实施例提供的上述技术方案，通过从MME发送的寻呼消息或者基站本地保存的信息中获取终端的寻呼特性，使得能够获取该终端的寻呼特性，进而可以根据该寻呼特性确定承载与终端对应的寻呼消息的载波，进而可以将小区内不同终端的寻呼消息通过确定的载波进行分担，进而解决了相关技术中的多载波小区寻呼容量受限的问题，提高了多载波小区的寻呼容量。

Claims (36)

  1. 一种承载寻呼消息载波的确定方法，包括：
    从移动管理实体MME发送的寻呼消息或基站本地存储的信息中获取终端的寻呼特性，其中，所述寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；
    依据所述寻呼特性确定承载与所述终端对应的寻呼消息的载波。
  2. 根据权利要求1所述的方法，其中，依据所述寻呼特性确定承载与所述终端对应的寻呼消息的载波包括：
    在所述寻呼特性为所述终端具有支持非主Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与所述终端对应的所述寻呼消息的载波为主Anchor载波或非主Non-Anchor载波；
    在所述寻呼特性为所述终端不具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定所述承载与所述终端对应的寻呼消息的载波为主Anchor载波。
  3. 根据权利要求2所述的方法，其中，确定承载与所述终端对应的所述寻呼消息的载波为主Anchor载波或非主Non-Anchor载波包括：
    根据预先设置的所述终端所在小区的能够承载寻呼消息的载波和终端标识的对应关系确定承载与所述终端对应的所述寻呼消息的载波为主Anchor载波或非主Non-Anchor载波。
  4. 根据权利要求1所述的方法，其中，从移动管理实体MME发送的寻呼消息中获取终端的寻呼特性之前，所述方法还包括：
    通过S1口信令将用于指示所述终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息发送给所述MME。
  5. 根据权利要求1所述的方法，其中，从基站本地存储的信息 中获取终端的寻呼特性之前，所述方法还包括：
    从所述终端上报的无线资源控制RRC信令获取所述终端的所述寻呼特性；
    将所述终端的所述寻呼特性保存在所述信息中。
  6. 根据权利要求5所述的方法，其中，所述RRC信令包括以下至少之一：
    RRC连接请求消息，RRC连接恢复请求消息，RRC重建立请求消息，RRC连接建立完成消息，RRC连接恢复完成消息，RRC连接重建立完成消息。
  7. 根据权利要求1至6中任一项所述的方法，其中，所述终端的所述寻呼特性通过以下至少之一来指示：
    一个信元，一个信元中的一个比特，寻呼类型，终端类别。
  8. 一种寻呼消息的发送方法，包括：
    向基站发送寻呼消息，其中，所述寻呼消息中携带终端的寻呼特性，所述寻呼特性为所述终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；所述寻呼特性用于所述基站确定承载与所述终端对应的寻呼消息的载波。
  9. 根据权利要求8所述的方法，其中，在向基站发送寻呼消息之前，所述方法还包括：
    确定在向所述基站发送的所述寻呼消息中是否携带所述终端的所述寻呼特性。
  10. 根据权利要求9所述的方法，其中，确定在向所述基站发送的所述寻呼消息中是否携带所述终端的所述寻呼特性包括：
    根据指示信息和所述终端的所述寻呼特性确定所述寻呼消息中是否携带所述终端的所述寻呼特性；其中，所述指示信息为从所述基站获取的用于指示所述终端所在小区是否支持Non-Anchor载波承载 寻呼消息的指示信息；在所述指示信息指示所述终端所在小区支持所述Non-Anchor载波承载寻呼消息和所述终端的所述寻呼特性为所述终端具有支持所述Non-Anchor载波承载寻呼消息的能力的情况下，确定所述寻呼消息中携带所述终端的所述寻呼特性；在所述指示信息指示所述终端所在小区支持所述Non-Anchor载波承载寻呼消息和所述终端的所述寻呼特性为所述终端不具备支持所述Non-Anchor载波承载寻呼消息的能力的情况下，确定所述寻呼消息中携带或者不携带所述终端的所述寻呼特性。
  11. 根据权利要求10所述的方法，其中，
    所述寻呼消息中携带所述终端的所述寻呼特性包括：通过所述寻呼消息中的特定指示域来携带所述终端的寻呼特性；其中，在所述特定指示域的取值为第一值时，所述终端具有支持非主Non-Anchor载波承载寻呼消息的能力，在所述特定指示域的取值为第二值时，所述终端不具有支持非主Non-Anchor载波承载寻呼消息的能力；
    所述寻呼消息中不携带所述终端的所述寻呼特性包括：在所述寻呼消息中不包含所述特定指示域。
  12. 根据权利要求8所述的方法，其中，从向基站发送寻呼消息之前，所述方法还包括：
    在所述终端初始附着或跟踪区更新时，通过所述终端发送的非接入层NAS消息或接入层AS信令获取所述终端的所述寻呼特性，或者从所述终端的签约信息中获取所述终端的所述寻呼特性。
  13. 根据权利要求12所述的方法，其中，所述NAS消息包括以下至少之一：
    附着请求消息、跟踪区更新TAU请求消息。
  14. 根据权利要求12所述的方法，其中，所述AS信令包括以下至少之一：
    空口的终端能力信息，S1口的终端能力信息指示。
  15. 一种承载寻呼消息载波的确定装置，包括：
    第一获取模块，设置为从移动管理实体MME发送的寻呼消息或基站本地存储的信息中获取终端的寻呼特性，其中，所述寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；
    确定模块，设置为依据所述寻呼特性确定承载与所述终端对应的寻呼消息的载波。
  16. 根据权利要求15所述的装置，其中，所述确定模块还设置为在所述寻呼特性为所述终端具有支持非主Non-Anchor载波承载寻呼消息的能力的情况下，确定承载与所述终端对应的所述寻呼消息的载波为主Anchor载波或非主Non-Anchor载波；以及在所述寻呼特性为所述终端不具有支持Non-Anchor载波承载寻呼消息的能力的情况下，确定所述承载与所述终端对应的寻呼消息的载波为主Anchor载波。
  17. 根据权利要求16所述的装置，其中，所述确定模块还设置为根据预先设置的所述终端所在小区的能够承载寻呼消息的载波和终端标识的对应关系确定承载与所述终端对应的所述寻呼消息的载波为主Anchor载波或非主Non-Anchor载波。
  18. 根据权利要求15所述的装置，其中，所述装置还包括：
    发送模块，设置为通过S1口信令将用于指示所述终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息发送给所述MME。
  19. 根据权利要求15所述的装置，其中，所述装置还包括：
    第二获取模块，设置为从所述终端上报的无线资源控制RRC信令获取所述终端的所述寻呼特性；
    保存模块，设置为将所述终端的所述寻呼特性保存在所述信息中。
  20. 根据权利要求19所述的装置，其中，所述RRC信令包括以 下至少之一：
    RRC连接请求消息，RRC连接恢复请求消息，RRC重建立请求消息，RRC连接建立完成消息，RRC连接恢复完成消息，RRC连接重建立完成消息。
  21. 根据权利要求15至20中任一项所述的装置，其中，所述终端的所述寻呼特性通过以下至少之一来指示：
    一个信元，一个信元中的一个比特，寻呼类型，终端类别。
  22. 一种寻呼消息的发送装置，包括：
    发送模块，设置为向基站发送寻呼消息，其中，所述寻呼消息中携带终端的寻呼特性，所述寻呼特性为所述终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力；所述寻呼特性用于所述基站确定承载与所述终端对应的寻呼消息的载波。
  23. 根据权利要求22所述的装置，其中，所述装置还包括：
    确定模块，设置为确定在向所述基站发送所述寻呼消息中是否携带所述终端的所述寻呼特性。
  24. 根据权利要求23所述的装置，其中，所述确定模块还设置为根据指示信息和所述终端的所述寻呼特性确定所述寻呼消息中是否携带所述终端的所述寻呼特性；其中，所述指示信息为从所述基站获取的用于指示所述终端所在小区是否支持Non-Anchor载波承载寻呼消息的指示信息；在所述指示信息指示所述终端所在小区支持所述Non-Anchor载波承载寻呼消息和所述终端的所述寻呼特性为所述终端具有支持所述Non-Anchor载波承载寻呼消息的能力的情况下，确定所述寻呼消息中携带所述终端的所述寻呼特性；在所述指示信息指示所述终端所在小区支持所述Non-Anchor载波承载寻呼消息和所述终端的所述寻呼特性为所述终端不具备支持所述Non-Anchor载波承载寻呼消息的能力的情况下，确定所述寻呼消息中携带或者不携带所 述终端的所述寻呼特性。
  25. 根据权利要求24所述的装置，其中，
    所述寻呼消息中携带所述终端的所述寻呼特性包括：通过所述寻呼消息中的特定指示域来携带所述终端的寻呼特性；其中，在所述特定指示域的取值为第一值时，所述终端具有支持非主Non-Anchor载波承载寻呼消息的能力，在所述特定指示域的取值为第二值时，所述终端不具有支持非主Non-Anchor载波承载寻呼消息的能力；
    所述寻呼消息中不携带所述终端的所述寻呼特性包括：在所述寻呼消息中不包含所述特定指示域。
  26. 根据权利要求22所述的装置，其中，所述装置还包括：
    获取模块，设置为在所述终端初始附着或跟踪区更新时，通过所述终端发送的非接入层NAS消息或接入层AS信令获取所述终端的所述寻呼特性，或者设置为从所述终端的签约信息中获取所述终端的所述寻呼特性。
  27. 根据权利要求26所述的装置，其中，所述NAS消息包括以下至少之一：
    附着请求消息、跟踪区更新TAU请求消息。
  28. 根据权利要求26所述的装置，其中，所述AS信令包括以下至少之一：
    空口的终端能力信息，S1口的终端能力信息指示。
  29. 一种基站，包括：权利要求15至21中任一项所述的装置。
  30. 一种移动管理实体MME，包括：权利要求22至28中任一项所述的装置。
  31. 一种系统，包括权利要求29所述的基站，权利要求30所述的MME和终端；其中，所述终端设置为在初始附着或跟踪区更新时， 通过非接入层NAS消息或接入层AS信令将所述终端的寻呼特性上报给所述MME或者在无线资源控制RRC建立过程中，通过RRC信令将所述终端的寻呼特性上报给所述基站；其中，所述寻呼特性为终端是否具有支持非主Non-Anchor载波承载寻呼消息的能力。
  32. 根据权利要求31所述的系统，其中，所述终端还设置为根据所述终端自身的所述寻呼特性、所述终端所在小区能够承载寻呼消息的载波和所述终端标识确定接收所述基站发送的寻呼消息的载波。
  33. 一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求1至7中任一项所述的方法。
  34. 一种存储介质，所述存储介质包括存储的程序，其中，所述程序运行时执行权利要求8至14中任一项所述的方法。
  35. 一种处理器，所述处理器用于运行程序，其中，所述程序运行时执行权利要求1至7中任一项所述的方法。
  36. 一种处理器，其所述处理器用于运行程序，其中，所述程序运行时执行权利要求8至14中任一项所述的方法。
PCT/CN2017/088102 2016-06-29 2017-06-13 承载寻呼消息载波的确定、寻呼消息的发送方法及装置 WO2018001086A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/314,279 US10917871B2 (en) 2016-06-29 2017-06-13 Method and device for determining carrier for bearing paging message and sending paging message

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610495724.7 2016-06-29
CN201610495724.7A CN107566099B (zh) 2016-06-29 2016-06-29 承载寻呼消息载波的确定、寻呼消息的发送方法及装置

Publications (1)

Publication Number Publication Date
WO2018001086A1 true WO2018001086A1 (zh) 2018-01-04

Family

ID=60785919

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/088102 WO2018001086A1 (zh) 2016-06-29 2017-06-13 承载寻呼消息载波的确定、寻呼消息的发送方法及装置

Country Status (3)

Country Link
US (1) US10917871B2 (zh)
CN (1) CN107566099B (zh)
WO (1) WO2018001086A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2552838B (en) * 2016-08-12 2018-08-08 Tcl Communication Ltd Non-Anchor carrier utilisation

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20220006577A (ko) * 2019-05-09 2022-01-17 광동 오포 모바일 텔레커뮤니케이션즈 코포레이션 리미티드 무선 통신 방법, 네트워크 기기 및 단말 기기
WO2021056508A1 (en) * 2019-09-29 2021-04-01 Nokia Shanghai Bell Co., Ltd. Methods and apparatuses for location area update

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102217396A (zh) * 2008-10-15 2011-10-12 Lg电子株式会社 分配寻呼载波的方法以及移动站
CN102761826A (zh) * 2011-04-26 2012-10-31 中国移动通信集团公司 寻呼消息承载方法及装置、寻呼消息发送方法及装置
CN103428809A (zh) * 2012-05-23 2013-12-04 华为技术有限公司 寻呼窄带终端的方法、网络设备及基站

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2481182B1 (en) * 2009-09-25 2016-01-13 BlackBerry Limited System and method for multi-carrier network operation
US8923180B2 (en) 2013-01-23 2014-12-30 Conversant Intellectual Property Management Incorporated Power saving in wireless network entities
GB2516886A (en) * 2013-08-02 2015-02-11 Nec Corp Communications system
CN105338519A (zh) * 2014-08-07 2016-02-17 北京三星通信技术研究有限公司 一种支持低复杂度ue接入和寻呼的方法
WO2016156227A1 (en) * 2015-04-01 2016-10-06 Nokia Solutions And Networks Oy Evolved packet core (epc) paging via wlan access points
GB2552838B (en) * 2016-08-12 2018-08-08 Tcl Communication Ltd Non-Anchor carrier utilisation

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102217396A (zh) * 2008-10-15 2011-10-12 Lg电子株式会社 分配寻呼载波的方法以及移动站
CN102761826A (zh) * 2011-04-26 2012-10-31 中国移动通信集团公司 寻呼消息承载方法及装置、寻呼消息发送方法及装置
CN103428809A (zh) * 2012-05-23 2013-12-04 华为技术有限公司 寻呼窄带终端的方法、网络设备及基站

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
SEQUANS COMMUNICATIONS: "Paging on a non-anchor carrier", 3GPP TSG-RAN WG2 #95 R2-165553, 26 August 2016 (2016-08-26), XP051127004 *
ZTE: "Considerations on multiple carriers operation for NB-IoT", 3GPP TSG RAN WG1 MEETING #84 RL-160472, 19 February 2016 (2016-02-19), XP051053805 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2552838B (en) * 2016-08-12 2018-08-08 Tcl Communication Ltd Non-Anchor carrier utilisation

Also Published As

Publication number Publication date
US10917871B2 (en) 2021-02-09
US20200187155A1 (en) 2020-06-11
CN107566099B (zh) 2019-08-27
CN107566099A (zh) 2018-01-09

Similar Documents

Publication Publication Date Title
US11632788B2 (en) Data scheduling method, base station, and system
US9775105B2 (en) Optimization on network assisted proximity services discovery management
CN108260121B (zh) 一种数据调度方法、基站及系统
CN108541033B (zh) 处理暂时用户端能力的装置及方法
WO2017121199A1 (zh) 一种信息传输方法、装置、系统和计算机存储介质
US9900836B2 (en) Network node, radio network node, and methods for sending a second secondary cell of a wireless device
WO2013174183A1 (zh) 一种寻呼方法和设备
WO2017133550A1 (zh) 频点选择方法及装置
KR20190102052A (ko) Ran 기반 통지 영역에 관한 정보의 통지를 위한 방법 및 디바이스
WO2018001086A1 (zh) 承载寻呼消息载波的确定、寻呼消息的发送方法及装置
US11190974B2 (en) Device and method for controlling network congestion with RRC inactive
WO2017121281A1 (zh) 一种实现数据传输方式切换的方法、装置和系统
WO2013113240A1 (zh) 一种传输rn信息、寻呼ue的方法及装置
WO2019141194A1 (zh) 更新系统消息的方法及装置
WO2022127777A1 (zh) 一种通信方法及通信装置
US12022428B2 (en) Remote user equipment direct to indirect path switching in sidelink relay
KR102029583B1 (ko) 무선 통신 시스템에서 그룹 기반 초기 접속 방법 및 그 방법을 이용하는 기지국
CN110740453A (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: 17819083

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

Country of ref document: EP

Kind code of ref document: A1