Patent Description:
To meet the demand due to ever-increasing wireless data traffic after the commercialization of the 4th generation (<NUM>) communication system, there have been efforts to develop an advanced 5th generation (<NUM>) system or pre-<NUM> communication system. For this reason, the <NUM> or pre-<NUM> communication system is also called a beyond 4th-generation (<NUM>) network communication system or post long term evolution (LTE) system. Implementation of the <NUM> communication system using ultra-frequency millimeter wave (mmWave) bands, e.g., <NUM> giga hertz (GHz) bands, is considered to attain higher data transfer rates. To reduce propagation loss of radio waves and increase a transmission range in the ultra-frequency bands, beamforming, massive multiple-input multiple-output (MIMO), Full Dimensional MIMO (FD-MIMO), array antenna, analog beamforming, and large-scale antenna techniques are under discussion. To improve system networks, technologies for advanced small cells, cloud Radio Access Networks (RANs), ultra-dense networks, device to device (D2D) communication, wireless backhaul, moving networks, cooperative communication, Coordinated Multi-Points (CoMP), reception-end interference cancellation and the like are also being developed in the <NUM> communication system. In addition, in the <NUM> system, an advanced coding modulation (ACM), e.g., hybrid frequency-shift keying (FSK) and quadrature amplitude modulation (QAM) (FQAM), sliding window superposition coding (SWSC), and an advanced access technology, e.g., filter bank multi carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA), are being developed.

In the meantime, the Internet is evolving from a human-centered connectivity network where humans generate and consume information into an Internet of Things (IoT) network where distributed entities such as things transmit, receive and process information without human intervention. Internet of Everything (IoE) technologies combined with IoT, such as big data processing technologies through connection with a cloud server, for example, have also emerged. To implement IoT, various technologies, such as a sensing technology, a wired/wireless communication and network infrastructure, a service interfacing technology, and a security technology are required, and recently, even technologies for sensor network, Machine to Machine (M2M), Machine Type Communication (MTC) for connection between things are being studied. Such an IoT environment may provide intelligent Internet Technology (IT) services that generate a new value to human life by collecting and analyzing data generated among connected things. IoT may be applied to a variety of areas, such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart home appliances and advanced medical services through convergence and combination between existing Information Technologies (IT) and various industrial applications.

In this regard, various attempts to apply the <NUM> communication system to the IoT network are being made. For example, technologies regarding a sensor network, M2M, MTC, etc., are implemented by the <NUM> communication technologies, such as beamforming, MIMO, array antenna schemes, etc. Even application of a cloud Radio Access Network (cloud RAN) as the aforementioned big data processing technology may be viewed as an example of convergence of <NUM> and IoT technologies.

<CIT> discloses methods and devices for enabling improved performance for page decodes on a SIM of a multi-SIIVI wireless communication device in which a shared radio frequency (RF) resource is used to read system information for a different SIIVI. After determining that a first SIM is using the shared RF resource to decode SIBs, the wireless device may receive information about an upcoming page decode time for monitoring a paging channel associated with the second SIM. The wireless device may obtain system information block (SIB) scheduling information associated with the first SIM, and may create a RF resource release gap during the system information read period based on the SIB scheduling information and the upcoming page decode time. Control of the RF resource may be released from the modem stack associated within the first SIM, and gained by a modem stack associated with the second SIIVI during the RF resource release gap. <NPL>, diiscloses that standard paging requests contain an ID that elects a single user as recipient of the paging request in order to service the paging request.

The present disclosure relates to methods and apparatus for paging a user equipment (UE) with a paging request including information indicating the UE to service the paging request.

System performance and user experience are greatly impacted in at least two areas. Firstly, support for multi-USIM is handled in an implementation-specific manner without any support from the 3GPP standard specifications, resulting in a variety of implementations and UE behaviours. Secondly, a multi-USIM device implementation typically uses common radio and baseband components that are shared among the multiple USIMs. For example, while actively communicating with the first system/network associated with USIM A, the UE needs to occasionally check the other system/network associated with USIM B, e.g. to monitor the paging channel, perform signal measurements, or read the system information, and determine if it needs to respond to a paging request from the other system.

Embodiments of the disclosure aim to address issues associated with paging requests received by MUSIM devices. In particular, embodiments aim to focus on paging procedures that may happen with respect to a Public Land Mobile Network (PLMN) different from the one the UE is active at in that moment. Current state-of-the-art specifications force the UE to process an incoming page even if it is being active on a different PLMN.

According to the present disclosure there is provided an apparatus and method as set forth in the appended claims. Other features of the disclosure will be apparent from the dependent claims, and the description which follows The claimed invention corresponds to <FIG>, <FIG>, <FIG> and to the related text in the description. The remaining figures and the text of the description are intended to better explain the invention.

According to a first aspect of the present disclosure, there is provided a method of operating a Multi-USIM User Equipment, UE, wherein if the UE is active on a first network and receives a paging request from a second network, the UE determines if the paging request includes an indication that it must service the paging request, and then the UE services the paging request.

In an embodiment, if the result of the determination is that the paging request does not include the indication, the UE determines if there are performance reasons not to accept the paging request and if there are no such reasons, the UE services the paging request.

In an embodiment, if the UE determines that there are performance reasons not to accept the paging request, the UE then determines if the paging cause is prioritised and if it is prioritised, the UE services the paging request.

In an embodiment, if the UE determines that the paging cause is prioritised, the UE services the paging request.

In an embodiment, if the UE determines that the paging cause is not prioritised, then the UE drops the paging request.

In an embodiment, the UE additionally informs the second network that it will not service the paging request.

In an embodiment, if the UE is active with the first network as a result of a previous paging request which included an indication that it must service the paging request, then any subsequent requests from the second network are dropped.

According to a second aspect of the present disclosure, there is provided a multi-USIM UE operable to perform the method of the first aspect.

According to a third aspect of the present disclosure, there is provided method of transmitting a paging request from a telecommunication network to a Multi-USIM User Equipment, UE, wherein the paging request includes a paging cause which indicates to the UE that it must service the paging request.

According to a fourth aspect of the present disclosure, there is provided Network apparatus arranged to perform the method of the third aspect.

Although a few preferred embodiments of the present disclosure have been shown and described, it will be appreciated by those skilled in the art that various changes and modifications might be made without departing from the scope of the invention, as defined in the appended claims.

<FIG> shows a Multi-USIM UE <NUM>, having two USIMs <NUM>, <NUM>. The UE <NUM> is configured such that USIM <NUM> is associated with network <NUM> and USIM <NUM> is associated with network <NUM>.

The UE is located in a position where service is possible from either or both networks <NUM>, <NUM> and is operable according to one or more of the embodiments described herein.

A problem addressed by embodiments of this disclosure is the need for a multi-USIM UE to be able to ignore paging requests on a different PLMN to the one where it is actively operating, whenever suitable. Prior art standard specifications force the UE to service the page request, and only if it is determined that the service priority that the incoming page refers to is lower than the service currently being handled can the incoming page be dropped. Hence, it is currently not possible for the network to indicate to the UE that a paging message may be dropped or ignored (i.e., not 'heeded') without the need for the page to be first serviced by the UE. Embodiments of the disclosure optimize the overall network performance when multi-USIM UEs are present by increasing the efficiency of the system's ability to handle paging messages in multi-USIM devices.

A particular problem in the prior art is that multi-USIM UEs may be busy processing service requests on a different USIM and PLMN. Embodiments of the present disclosure provide a new message type ('HEED') as paging cause that indicates to the UE whether it's possible for the paging request to be ignored or not. Once the page message is received by the UE - which is a dual receiver, so it can indeed receive the page message - if the paging cause message is <HEED> then the UE must service the request, but if it is <not HEED> then it may directly drop the page request (if appropriate for any reason), and then notify the network that nothing is being done with regard to the paging request.

This arrangement is not known in the prior art, which merely discloses that the page needs to be serviced by the UE and only after a priority assessment has been performed may the page be dropped, with the network noticing only after a timer repeatedly expires, since no notification is sent explicitly by the UE to the Access and Mobility Management Function (AMF). Such unresponsive behaviour resembles the UE being out of coverage: the UE electively determines that it is unable to respond in order to prevent the need for communication, especially transmission, to one or more PLMNs.

Page causes are currently part of the paging messages in UTRAN (<NUM>, section <NUM>. <NUM>), and codes representing the different causes are transmitted along with the message to indicate such a cause. New Radio (NR) does not include a paging cause code. Hence, a <HEED> message is encoded as a page cause, where the only purpose is to indicate to the UE the reason for the paging message.

Embodiments of the disclosure comprise the following steps:.

In addition, a further optimization may be achieved by the sending of a 'NOTHING DOING' message to the network (via the AMF), indicating that the page was ignored. This allows the network to know that the UE is not 'out of coverage' but rather in a 'suspended' state where it is actively ignoring the incoming page and so the network should not 'waste' network resources by avoiding:.

<FIG> shows an updated service request procedure triggered by the network. Various entities are shown, including UE <NUM>, RAN <NUM>, AMF <NUM>, SMF <NUM> and UPF <NUM>. The message exchanges shown here effectively replace those shown in Figure <NUM>. <NUM>-<NUM> in clause <NUM>. <NUM> of <NPL>. A key difference is that in this embodiment, the UE <NUM> applies a new methodology to check whether to drop the page based on the newly defined HEED message, which is part of the paging message itself specifying the paging cause. In particular, the following new or updated steps (compared to the figures referenced above) are performed within the network-triggered service request procedure:.

There now follows details of embodiments of the present disclosure, which utilize a HEED indication as paging cause to determine that a service request must be serviced. The embodiments differentiate themselves in the exact processing that takes place at the UE <NUM> after receiving such a request.

A first embodiment represents the case where the UE <NUM> is busy on a first network, PLMN1, processing a service request that was not marked as <HEED> and the page dropping mechanism follows the standardized procedure known in the prior art i.e. the UE <NUM> does not provide notification of page dropping to the network and the paging process continues after a timer at the AMF <NUM> expires. <FIG> shows a flow chart representing this embodiment.

At <NUM>, UE <NUM> receives a page from a second network PLMN2. If, at <NUM>, the UE <NUM> is idle on the first network PLMN1, then flow continues to the service request procedure <NUM>. However, if the UE is not idle on PLMN1 i.e. it is active, then a check is made at <NUM> if the page cause is <HEED>. If it is, then flow continues to <NUM>, since the UE is forced to react. However, if the page cause is <NOT HEED>, then at <NUM> a check is made to determine if there are any performance reasons not to accept the page. If there are none, flow continues to <NUM>. If, however, there are, then at <NUM> a check is made to determine if the page cause is prioritised. If it is, then flow continues to <NUM>. If not, the page is dropped at <NUM> and the prior art process is continued as set out above.

<FIG> represents a different scenario, where the UE <NUM> is busy on PLMN1 processing a service request that was not marked as <HEED>, and the page dropping mechanism follows a different path, namely the previously mentioned additional is enabled, whereby a NOTHING DOING message is sent by the UE <NUM> to the AMF <NUM> indicating to the network that the page has been dropped. This saves transmission resources in the network by preventing the rest of the prior art paging process from continuing.

At <NUM>, UE <NUM> receives a page from a second network PLMN2. If, at <NUM>, the UE <NUM> is idle on the first network PLMN1, then flow continues to the service request procedure <NUM>. However, if the UE is not idle on PLMN1 i.e. it is active, then a check is made at <NUM> if the page cause is <HEED>. If it is, then flow continues to <NUM>, since the UE is forced to react. However, if the page cause is <NOT HEED>, then at <NUM> a check is made to determine if there are any performance reasons not to accept the page. If there are none, flow continues to <NUM>. If, however, there are, then at <NUM> a check is made to determine if the page cause is prioritised. If it is, then flow continues to <NUM>. If not, the page is dropped at <NUM> and the NOTHING DOING message is sent to the AMF to indicate that the page in question has been dropped.

<FIG> represents a case where the UE <NUM> is busy on PLMN1, <NUM>, processing a service request that was marked as <HEED> and a paging request arrives, <NUM>, from PLMN2 (with or without a cause). In this case no further checks are needed and the page is dropped, <NUM>. A NOTHING DOING message is sent by the UE to the AMF indicating to the network that the page has been dropped.

<FIG> represents a case where the UE <NUM> is busy on PLMN1, <NUM>, processing a service request that was marked as <HEED> and a paging request arrives, <NUM>, from PLMN2 (with or without a cause). In this case no further checks are needed, and the page is dropped <NUM>. The page dropping mechanism follows the procedure known in the prior art and referred to previously.

Further, the HEED cause may be provided to the MUSIM UE <NUM> by PLMN1 (of say SIM-<NUM>) when a highest priority service data or signalling (for example emergency or mission critical service) is pending to be delivered to the UE <NUM>. The UE <NUM> will immediately respond with an initial NAS message unless the UE is also executing a similar highest priority service on PLMN2 (of say SIM-<NUM>) i.e. the same category of service. In such a collision case, where there is no obvious solution, the UE <NUM> may make a choice whether to respond to paging message with HEED cause indication. Such a decision may be implementation specific and does not need to be a standardisation issue.

In embodiments of the disclosure, the trigger from the UE <NUM> in response to a paging message is illustrated as a Service request procedure, however this can be any initial direct transfer message as shown in, for instance, prior art specification 3GPP TS <NUM> "example registration procedure" or "detach procedure".

Embodiments of the disclosure provide an improved UE able to better handle paging requests due to the adaptation provided herein. Network resources are better utilised by preventing unnecessary interactions between network entities.

<FIG> is a block diagram illustrating a base station according to an exemplary embodiment of the present disclosure.

Referring to the <FIG>, the base station <NUM> may include a processor <NUM>, a transceiver <NUM> and a memory <NUM>. However, all of the illustrated components are not essential. The base station <NUM> may be implemented by more or less components than those illustrated in <FIG>. In addition, the processor <NUM> and the transceiver <NUM> and the memory <NUM> may be implemented as a single chip according to another embodiment.

The processor <NUM> may include one or more processors or other processing devices that control the proposed function, process, and/or method. Operation of the base station <NUM> may be implemented by the processor <NUM>.

The memory <NUM> may store the control information or the data included in a signal obtained by the base station <NUM>. The memory <NUM> may be connected to the processor <NUM> and store at least one instruction or a protocol or a parameter for the proposed function, process, and/or method. The memory <NUM> may include read-only memory (ROM) and/or random access memory (RAM) and/or hard disk and/or CD-ROM and/or DVD and/or other storage devices.

<FIG> illustrates a user equipment (UE) according to embodiments of the present disclosure.

The multi-USIM UE described above corresponds to the UE <NUM>.

Referring to the <FIG>, the UE <NUM> includes a processor <NUM>, a transceiver <NUM> and a memory <NUM>. The UE <NUM> may be implemented by more or less components than those illustrated in <FIG>. In addition, the processor <NUM> and the transceiver <NUM> and the memory <NUM> may be implemented as a single chip according to another embodiment.

The processor <NUM> may include one or more processors or other processing devices that control the proposed function, process, and/or method. Operation of the UE <NUM> is implemented by the processor <NUM>.

The transceiver <NUM> is connected to the processor <NUM> and transmit and/or receive a signal. In addition, the transceiver <NUM> receives the signal through a wireless channel and outputs the signal to the processor <NUM>. The transceiver <NUM> transmits a signal output from the processor <NUM> through the wireless channel.

The memory <NUM> may store the control information or the data included in a signal obtained by the UE <NUM>. The memory <NUM> may be connected to the processor <NUM> and store at least one instruction or a protocol or a parameter for the proposed function, process, and/or method. The memory <NUM> may include read-only memory (ROM) and/or random access memory (RAM) and/or hard disk and/or CD-ROM and/or DVD and/or other storage devices.

<FIG> schematically illustrates a core network entity according to embodiments of the present disclosure.

The AMF described above corresponds to the core network entity <NUM>.

Referring to the <FIG>, the core network entity <NUM> includes a processor <NUM>, a transceiver <NUM> and a memory <NUM>. The core network entity <NUM> may be implemented by more or less components than those illustrated in <FIG>. In addition, the processor <NUM> and the transceiver <NUM> and the memory <NUM> may be implemented as a single chip according to another embodiment.

The transceiver <NUM> may provide an interface for performing communication with other devices in a network. That is, the transceiver <NUM> may convert a bitstream transmitted from the core network entity <NUM> to other devices to a physical signal and covert a physical signal received from other devices to a bitstream. That is, the transceiver <NUM> transmits and receives a signal. The transceiver <NUM> may be referred to as modem, transmitter, receiver, communication unit and communication module. The transceiver <NUM> may enable the core network entity <NUM> to communicate with other devices or system through backhaul connection or other connection method.

The memory <NUM> may store a basic program, an application program, configuration information for an operation of the core network entity <NUM>. The memory <NUM> may include volatile memory, non-volatile memory and a combination of the volatile memory and the non-volatile memory. The memory <NUM> may provide data according to a request from the processor <NUM>.

The processor <NUM> may control overall operations of the core network entity <NUM>. For example, the processor <NUM> may transmit and receive a signal through the transceiver <NUM>. The processor <NUM> includes at least one processor. The processor <NUM> controls the core network entity <NUM> to perform operations according to embodiments of the present disclosure.

According to an embodiment of the present disclosure, a method of an User Equipment (UE) in a wireless communication system is provided. The method may comprise: receiving a paging request from a second network when the UE is active on a first network; determining if the received paging request includes information indicating the UE to service the received paging request; and servicing the received paging request based on the information included in the paging request.

In an embodiment, the method may further comprise: determining if performance reasons not to accept the paging request exist, in case that the paging request does not include the information; and servicing the paging request in case that the performance reasons do not exist.

In an embodiment, the method may further comprise: determining if a paging cause is prioritised in case that the performance reasons exist; and servicing the paging request in case that the paging cause is prioritised.

In an embodiment, the method may further comprise dropping the paging request in case that the paging cause is not prioritised.

In an embodiment, the method may further comprise informing the second network that the UE will not service the paging request in case that the paging request is dropped.

In an embodiment, if the UE is active with the first network as a result of a previous paging request indicating the UE to service the previous paging request, any subsequent requests from the second network are dropped.

According to an embodiment of the present disclosure, an User Equipment (UE) in a wireless communication system is provided. The UE may comprise: a transceiver; and at least one processor coupled with the transceiver and configured to: receive, via the transceiver, a paging request from a second network when the UE is active on a first network; determine if the received paging request includes information indicating the UE to service the received paging request; and service the received paging request based on the information included in the paging request.

In an embodiment, the at least one processor is further configured to: determine if performance reasons not to accept the paging request exist, in case that the paging request does not include the information; and service the paging request in case that the performance reasons do not exist.

In an embodiment, the at least one processor is further configured to: determine if a paging cause is prioritised in case that the performance reasons exist; and service the paging request in case that the paging cause is prioritised.

In an embodiment, the at least one processor is further configured to drop the paging request in case that the paging cause is not prioritised.

In an embodiment, the at least one processor is further configured to inform the second network that the UE will not service the paging request in case that the paging request is dropped.

In an embodiment, if the UE is active with the first network as a result of a previous paging request including an indication that the UE must service the paging request, then any subsequent requests from the second network are dropped.

According to an embodiment of the present disclosure, a method of an Access and Mobility Management Function (AMF) in a wireless communication system is provided. The method may comprise transmitting a paging request including a paging cause indicating an User Equipment (UE) to service the transmitted paging request.

In an embodiment, the method may further comprise receiving, from the UE, a message including information that the transmitted paging request is not serviced by the UE.

According to an embodiment of the present disclosure, an Access and Mobility Management Function (AMF) in a wireless communication system is provided. The AMF may comprise a transceiver; and at least one processor configure to transmit a paging request including a paging cause which indicates to an User Equipment (UE) that the UE must service the paging request.

Claim 1:
A method performed by a user equipment, UE, in a wireless communication system, the method characterized by:
receiving, from an access mobility management function, AMF, entity, a paging request associated with a second network, wherein the UE is in an active state on a first network, and
wherein the paging request includes one of first information indicating the UE to service the paging request and second information indicating that the UE is allowed to ignore the paging request in case that performance reasons not to accept the paging request exist;
in case that the paging request includes the second information, determining whether the performance reasons exist; and
in case that the performance reasons do not exist, transmitting, to the AMF entity, a service request message, in response to the paging request including the second information.