Patent Application
20240349246
The present invention relates to a communication system. The invention has particular but not exclusive relevance to winless communication systems and devices thereof operating according to the 3rd Generation Partnership Project (3GPP) standards or equivalents or derivatives thereof (including LTE-Advanced and Next Generation or 5G networks). The invention has particular although not exclusive relevance to paging of communication devices.
The latest developments of the 3GPP standards are referred to as the Long Term Evolution (LTE) of Evolved Packet Core (EPC) network- and Evolved UMTS Terrestrial Radio Access Network (E-UTRAN), also commonly referred as ‘4G’. In addition, the term ‘5G’ and ‘new radio’ (NR) refer to an evolving communication technology that is expected to support a variety of applications and services. Various details of 5G networks are described in, for example, the ‘NGMN 5G White Paper’ V1.0 by the Next Generation Mobile Networks (NGMN) Alliance, which document is available from https://www.ngmn.org/5g-white-paper.html. 3GPP intends to support 5G by way of the so-called 3GPP Next Generation (NextGen) radio access network (RAN) and the 3GPP NextGen core network.
Under the 3GPP standards, a NodeB (or an eNB in LTE, gNB in 5G is the base station via which communication devices (user equipment or ‘UE’) connect to a core network and communicate to other communication devices or remote servers. For simplicity, the present application will use the term base station to refer to any such base stations and use the term mobile device, user device, or UE to refer to any such communication device. The core network. (i.e. the EPC in case, of LTE) hosts functionality for subscriber management, mobility management, charging, security, and call/session management (amongst others), and provides connection for communication devices to external networks, such as the Internet.
Communication devices might be, for example, mobile communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop/tablet computers, web browser, e-book readers and/or the like. Such mobile (or even generally stationary) devices are typically operated by a user. However, 3GPP standards also make it possible to connect so-called ‘Internet of Things’ (IoT) devices (e.g. Narrow-Band IoT (NB-IoT) devices) to the network, which typically comprise automated equipment, such as various measuring equipment, telemetry equipment, monitoring systems, tracking and tracing devices, in-vehicle safety systems, vehicle maintenance system, road sensors, digital billboards, point of sale (POS) terminals, remote control systems, and the like. Effectively, the Internet of Things is a network of devices (or “things”) equipped with appropriate electronics, software, sensors, network connectivity, and/or the like, which enables these devices to collect and exchange data with each other and with other communication devices. It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) communication devices or Machine-to-Machine (M2M) communication devices.
For simplicity, the present application refers to mobile devices in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and/or generally stationary) that can connect to a communications network for sending/receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory.
Communication between mobile devices and heat stations is controlled using a Radio Resource Control (RRC) protocol as defined in 3GPP TS 36.331. V14.1.0. RRC handles the control plane signalling of Layer 3 between mobile telephones and the radio access network, and includes, amongst other things, functions for broadcasting system information, paging, connection establishment and release, radio bearer establishment, reconfiguration and release, mobility procedures, and power control. In accordance with the current version of the RRC protocol, at any given time, a mobile device may operate either in an ‘RRC idle mode’ (in which no data communication takes place) or an ‘RRC connected mode’ (in which data communication may take place between the mobile device and its serving base station).
As mobile devices operating in the RRC connected erode move around in the area covered by the communication system, they are handed over from one cell (i.e. operated by a base station) to another cell (operated by the same or a different base station), depending on signal conditions and other requirements, such as requested quality of service, the type of service used, overall system load, and the like. Handover requires extensive signalling between the mobile device and the base stations (old and new) and also between the base stations and the core network as well.
On the other hand, whilst in the RRC idle mode, mobile devices are programmed to select a ‘serving’ cell, having a good quality signal, to camp on so that when new data is to be transmitted to/from these mobile devices, they can benefit from favourable signal conditions. In the event that an idle mobile device detects a new cell with better signal quality than the current serving cell, e.g. due to the mobile device changing its location, the mobile device can perform a so-called cell reselection procedure. However, an idle mode mobile device does not inform the network about the selected new cell as long as this cell is within the same ‘trucking area’ (i.e. a larger geographic area comprising a pre-defined set of cells), because the radio network transmits system information and UE specific paging messages within the whole tracking area thus making it possible to initiate communication to/from the mobile device regardless of the current cell it camps on.
In order to benefit from the lowest energy consumption and to free up valuable system resources, the mobile devices return to the RRC idle mode whenever possible and perform cell re selections (instead of handovers) as long as they remain within the same tracking area. The base station controls the transition between the various operating modes for each mobile device within its cell(s). Since the setting up and termination of an RRC connection between the base station and the mobile device requires exchanging of signalling messages and hence utilises valuable system resources, and also takes some time to complete, the transition from connected to idle mode is allowed under specific circumstances as defined in 3GPP TS 36.331. For example, the serving base station might instruct a mobile device to enter the RRC idle mode only after it has confirmed that there is no more data to be transmitted to/from, the particular mobile device (e.g. both uplink (UL) and downlink (DL) buffers are empty).
When it registers its current location (e.g. cell) with the cow network, each mobile device also has an associated ‘S1’ connection between its serving base station and the core network. The S1 connection is either in a so-called ‘ECM-IDLE’ mode (when the mobile device is in RRC idle mode) or in an ‘ECM-CONNECTED’ mode (when the mobile device is in RRC connected mode). The S1 connection is used for transferring data (control and user data) between the mobile device and the core network. (and beyond) and it is maintained as long as the mobile device remains in the RRC connected mode. On the other hand, when a mobile device enters the RRC idle mode, its associated S1 connection is also terminated (or suspended) until the mobile device has more data to send or receive in which case a new S1 connection is established to the current serving base station (or the suspended S1 connection is re-activated).
When the network has data to send to an RRC idle mobile device, it triggers an appropriate paging procedure in the last known area (tracking/paging area) of the mobile device, which causes the base stations within that area to broadcast appropriate paging messages in their cells requesting that particular mobile device to enter the RRC connected state. When a previously idle mobile telephone has data to send again (or it has been paged for receiving downlink data), in order to be allocated communication resources it initiates a so called RRC connection establishment procedure by sending an appropriately formatted RRC connection request message to the base station (following a so-called Random Access Procedure which ensures that the lower layers, and in particular the Media. Access Control (MAC) layer, are set up k r communication with the base station).
For the latent developments of the 3GPP standards, the so-called Next Generation (NG) or 5G networks, ills envisaged that mobile devices may also operate in a new RRC state, or new radio state, referred to as an ‘RRC inactive’ state (e.g. in 5G), or a ‘light-connected’ (LC) state/mode (e.g. in LTE/4G). When a mobile device is in the LC state, the core network maintains both its control-plane and user-plane connection even after the mobile device has no more data to send or receive (and Bence it is normally configured to enter the RRC idle mode). In other words, even though in the LC slate/mode the mobile device is seen as operating in idle mode from the radio access network's (base station's) point of view, it may still be seen as being connected from the core network's point of view (even though there is no active RRC connection (i.e. SRB/DRB) between the base station and the LC or inactive state LIE), one of the benefits of (his new LC state/mode is that mobile devices (IoT devices in particular) that have small and infrequent data transmissions do not need to perform the entire RRC connection establishment procedure every time they have data to send (or receive). Instead, an LC slate/mode capable mobile device can be configured to resume its existing RRC, connection with the current serving base station whenever needed and then return to a more power efficient mode of operation until it has data to send/receive again.
The mobile device can resume its RRC connection by sending to its current base station information (e.g. a resume ID) identifying the connection to be resumed. This beneficially avoids the base station and the mobile device having to go through authentication and radio bearer establishment. In order to facilitate such lightweight connection and simplified resumption or the connection between the mobile device and its serving base station, the concept of a so-called anchor base station is being considered by 3GPP. Effectively, the anchor base station is a base station responsible for storing UE Access Stratum (AS) context, caching the mobile device's user data (UE context) and for providing the user data to other base stations as needed while terminating S1. For example, the anchor base station may be the first (or previous) base station that the mobile device registered with in a particular tracking area (or other pre defined area). Thus, when the mobile device attempts to resume its RRC connection via a different haw station (within the same area), the new base station can contact the anchor base station and retrieve the UE context along with the cached user data based on information provided by the mobile device (e.g. resume ID and/or the like). Since in the LC state/mode the S1 connection is maintained, beneficially, the new base station can avoid having to contact the core network and/or establish a new S1 connection for the mobile device (although the new base station might need to switch the S1 connection from the anchor/previous base station to the new base station). This procedure may be referred to as anchor relocation and it involves switching an S1 terminating point from an Anchor base station to a new Serving base station whilst transferring the UE context. The anchor base station concept is illustrated in
The current agreement in 3GPP is that the base station maintains the S1 connection while the mobile device is lightly connected and the these station is responsible for RAN paging (within an appropriate paging/tracking area configured by the base station) when it receives the downlink data from core network. The LC state/mode mobile device notifies the network when it moves out of its configured RAN based paging area, in which case the network can decide whether to keep the mobile device in LC mode or suspend the mobile, device (e.g. request it to enter RRC idle mode).
However, the inventors have realised that since the mobile device does not maintain its connection with the network while it is in inactive state or LC mode, this may cause a number of issues that the currently proposed systems cannot handle. Such issues include, although they are not limited to:
Accordingly, preferred example embodiments of the present invention aim to provide methods and apparatus which address or at least partially deal with one or more of the above issues whilst still allowing mobile devices to maintain a light/RRC inactive connection with the network.
Although for efficiency of understanding for those of skill in the art, the invention will be described in detail in the context of a 3GPP system UMTS. LTE, NR), the principles of the invention can be applied to other systems in which communication devices or User Equipment WE) access a core network using a radio access technology.
In one aspect, the invention provides a method performed by a base station of a communications network, the method comprising: sending, to a communication device, a message indicating that it paging area for the communication device is to be updated at the communication device; and broadcasting system information comprising information identifying a change to the paging area.
In another, aspect, the invention provides a method performed by a base station of a communications network, the method comprising: receiving, from a communication device, a message to request update of a routing area; and sending, to a communication device, responsive to the request message, a message comprising information identifying a change to the muting area.
In another aspect, the invention provides a method performed by a base station of a communications network, the method comprising: receiving, from another base station, a request message to request removal of a base station to base station interface between base stations operating cells of a paging area; and sending, to the another base station, responsive to the request message, a response message, comprising information identifying a change to the paging area; wherein at least one of the request message, and the response message, includes information identifying at least one communication device that will be impacted by the removal.
In another aspect, the invention provides a method performed by a communication device of a communications network, the method comprising: receiving, from a base station, a message indicating that a paging area for the communication device is to be updated at the communication device; and receiving system, information broadcast comprising information identifying a change to the paging area.
In another aspect, the invention provides a method performed by a communication device of a communications network, the method comprising: transmitting, to a base station, a request message to request update of a muting area, receiving, from the base station, responsive to the request message, a message comprising information identifying a change to the routing area.
In another aspect, the invention provides a method performed by a base station of a communications network, the method comprising: determining that a communication device is to be moved to an inactive or light connected (LC) mode/state; and sending, to the communication device, a message indicating that the communication device is to move to the inactive or light connected (LC) mode/state; wherein, the message includes information identifying at least one cell that forms a paging area for the communication device.
In another aspect, the invention provides a method performed by a base station acting as an anchor base station for a communication device of a communications network, the method comprising: determining that a paging attempt for the communication device has failed, and sending, to a core network entity, responsive to said determining, a message to request the core network entity to page the communication device; wherein the request message includes information identifying at least one cell recommended for paging.
In another aspect, the invention provides a method performed by a core network entity of a communications network, the method comprising: receiving, from a base station acting as an anchor base station for a communication device, responsive to the base station determining that a paging attempt for the communication device has failed, a request message to request the core network entity to page the communication device; wherein the request message includes information identifying at least one cell recommended for paging.
Aspects of the invention extend to corresponding systems, apparatus, and computer program products such as computer readable storage media having instructions stored thereon which are operable to program a programmable processor to carry out a method as described in the aspects and possibilities set out above or recited in the claims and/or to program a suitably adapted computer to provide the apparatus recited in any of the claims.
Each feature disclosed in this specification (which term includes the claims) and/or shown in the drawings may be incorporated in the invention independently of (or in combination with) any other disclosed and/or illustrated features. In particular but without limitation the features of any of the claims dependent from a particular in dependent claim may be introduced into that independent claim in any combination or individually.
Example embodiments of the invention will now be described, by way of example, with reference to the accompanying drawings in which:
Although not shown in
Communication devices 3 can connect to an appropriate cell (depending on their location and possibly on ether factors, e.g. signal conditions, subscription data, capability, and/or the like) by establishing a radio resource control (RRC) connection with the appropriate base station 5 operating that cell. As can be seen, the first mobile device 3 is located in an area where it can be saved by the cells operated by the base stations 5a or 5b. Thus, when operating in RRC, idle mode (not sending/receiving data, the mobile device 3 camps on the cell having the best signal quality, and when in RRC active mode, the mobile device 3 communicates data via that cell (using e.g. the ‘Uu’ air interface).
When the mobile device 3 first registers with the network (via one of the base stations 5, its serving base station 5 also establishes an associated S1 connection for relaying communications (user and control data) between the serving base station 5 and the core network 7.
The base stations 5 are connected to the core network 7 via an S1 interface for NG-C/NG-U interface in case of 5G) and to each other via an X2 interface (Xn interface in 5G). The core network 7 includes, amongst others, an access and mobility management function (AMF) 9 (or a mobility management entity. MME), and a user-plane function 10 for providing a connection between the base stations 5 and external networks 15 (such as the Internet) and/or servers hosted outside the core network 7.
The AMF/MME 9 is the network node responsible for keeping track of the locations of the mobile communication devices within the communications network 1 especially when a UE is RRC_IDLE mode. In particular, the AMF/MME 9 stores an identifier of the mobile communication devices' last known cell (or tracking area) so that they can be notified when there is an incoming (voice or data) call for them and that a communication path is set up via the base station 5 currently serving the particular mobile communication device.
In the following examples, the mobile device 3 connects to the network periodically (e.g, whenever one of its applications needs to communicate with the network) for sending data to a remote endpoint (e.g. a server or another communication device). The mobile device 3 is configured to operate in a light connected (LC) mode in which the network maintains an associated S1 connection even when the mobile device 3 is operating in an inactive mode from the RAN's point of view. Therefore, between its periodic re-connections, the mobile device 3 effectively enters an idle (or ‘suspended’) mode and thus avoids performing handovers as long as it remains within an area configured by its anchor base station 5a.
The base station 5 serving the mobile device 3 is responsible for configuring an appropriate RAN based paging area for the mobile device 3 (e.g. by providing a list of cells and/or paging area IDs to the mobile device 3). The RAN based paging area may be configured to comprise one or more cells from the same or different base stations 5. For example, the RAN based paging area may be a tracking area, however, the RAN based paging area is UE specific and serving tease station 5 may change the cells included in the RAN based paging area (when appropriate).
As illustrated by a dashed line, the mobile device 3 previously connected to the base station 5a (via Cell A) and thus the base station 5a (acting as the anchor base station for the mobile device 3) maintains an associated OF context and terminates S1. However, it will also be appreciated that the anchor base station may be a different base station, e.g. the base station 5b currently serving the mobile device 3. In the present example, the anchor base station 5a configures the mobile device 3 with a RAN paging area that includes one or more cells in the vicinity of the anchor base station 5a. For example, the (UE specific) RAN paging area may include the anchor base station's own cell(s) and the cells operated by the base stations 5b and 5c.
As illustrated by a continuous line, the mobile device 3 is now reachable via the base station 5b (e.g. via a ‘Cell B’ operated by that base station 5b)—for example, due to a change in signal conditions in Cell A and/or movement of the mobile device 3. In this example, the mobile device 3 currently has no active connections with the radio access network (the base stations 5), thus it is configured to perform cell reselection (without informing the network) when it moves between cells operated by the base stations 5a, 5b, and 5c. However, if the mobile device 3 moves to an area (e.g. a cell operated by base station 5d or 5c) that is not included in its RAN paging area, the mobile device 3 initiates a location update procedure in order to inform the network about its current location (in which case the mobile device 3 may be configured with a new RAN paging area).
As explained above, in LC state/mode the mobile device 3 is still seen as connected (ECM-CONNECTED) from the core network's 7 (AMF/MME 9) point of view even after the mobile device 3 has, in effect, entered an idle/inactive mode from the perspective of the base stations (and hence the mobile device 3 does not have an active data connection with its base station 5). Accordingly, when there is downlink data to send, the MME 9 does not initiate paging for the mobile device 3 in the LC state/mode (e.g. throughout an associated tracking/paging area) because the MME 9 assumes that the mobile device 3 still has an active connection with its serving base station 5 (in this example, the anchor base station 5a). Thus, the MME 9 starts sending the downlink data to the anchor base station 5a. In response to the downlink data, the anchor base station 5a starts appropriate procedures for (RAN based) paging of the mobile device 3 within the paging area appropriate for that mobile device 3.
The RAN based paging indicates to the mobile device 3 that it needs to resume its RRC connection (re-connect) via an appropriate base station for receiving downlink data. Until the mobile device 3 resumes its connection, the anchor base station 5a stores the downlink data from the AMF/MME 9 (in case of control-planes signalling or data) or from the UPF 10 (in case of user-plane data) in its cache (memory).
The base station 5a decides which cells to page when it receives the downlink data. If necessary, the anchor base station 5b may send appropriate X2/Xn paging signalling to its neighbour base station(s) in order to reach the mobile device 3 via other than its own cell(s). Thus, in this example, the anchor base station 5a performs RAN based paging in its own cell(s) and in the cells operated by the base stations 5b and Se which are included in the (UE specific) RAN paging area for the mobile device 3. In response to receiving an appropriate paging message, the mobile device 3 is operable to resume its RRC connection via one of the base stations 5a, 5b, and 5c (depending on which cell the mobile device 3 is currently camping on) for receiving the downlink data.
In this example, the RAN paging area of the mobile device 3 changes whilst the mobile device 3 is in the LC mode. Specifically, the cell(s) operated by the base station 5c (e.g. Cell C) are being removed from the RAN paging area for the mobile device 3. This may be necessary, for example, when the X2/Xn connection between the anchor base station 5a and the base elation 5c is being removed or reconfigured, or when the base station 5c is no longer able to serve the mobile device 3 (e.g. due to a cell recon figuration, change in cell load, failure of a neighbour base station, and/or the like). In some cases, especially when the base station 5c comprises a ‘home’ base station (home eNB), the base station 5c may be turned off and no longer available.
However, the nodes of this system are beneficially configured to address such scenarios that necessitate a change in the associated RAN paging area for the mobile devices.
In more detail, the base stations 5 are configured to inform each other (via the X2/Xn interface) about events that may cause a change in the RAN paging area employed by other base stations. For example, such event may include a cell (or base station) becoming unavailable, a base station being powered off, an X2/Xn connection being reconfigured or removed, and/or the like.
When necessary (e.g, when being notified/triggered by a neighbour base station), each anchor base station 5 (in this example, base station 5a for UE1) is able to notify the affected mobile device(s) 3 about the change in its RAN paging area (e.g. removal of one or more cells from the currently configured RAN paging area). For example, the base stations 5 may notify the change in the paging area by transmitting updated system information and/or carry out an appropriate RAN muting area update procedure with the mobile devices 3.
Beneficially, the mobile devices 3 can be kept updated about which cells they are allowed to camp on (which cells to include in their RAN paging area) and which cells they are not allowed to camp on (which cells to exclude from their RAN paging area). The decision by an anchor base station in terms of how to configure a UE specific RAN paging area may depend on one or more of: UE history information; a handover (HO) restriction area, a service level agreement relating to the UE; UE communication pattern history; and/or the like. It will be appreciated this information may change over time, it, is possible that that the base station 5 may determine an initial UE specific RAN paging area, and then, after a period of time, the base station 5 may decide to modify the number of cells in the UE specific RAN paging area and to trigger the signalling to inform the mobile device 3 of this change.
In summary, in this network it is possible to provide better service continuity and more efficient resource usage at user equipment (mobile devices and/or IoT devices), (home) base stations, and the AMF/MME when the associated RAN paging area changes for the user equipment (which may be operating in LC state/mode).
The controller 37 is configured to control overall operation of the mobile device 3 by, in this example, program instructions or software instructions stored within the memory 39. As shown, these software instructions include, among other things, an operating system 41, a communications control module 43, a paging module 45, an RRC module 46, and a NAS module 49.
The communications control module 43 is operable to control the communication between the mobile device. 3 and its serving base station 5 (and other communication devices connected to the serving base station 5, such as other user equipment, core network nodes, etc.).
The paging module 45 is responsible (or maintaining a (RAN based) paging area (e.g. in the form of a list of cells) in which the mobile device 3 can be paged, and to control the transceiver 31 to monitor for paging messages addressed to the mobile device 3. The paging module 45 is also responsible to notify the other modules (e.g. the RRC module 46 and the NAS module 49, as appropriate) when the mobile device 3 is about to leave (or when it has left) the currently configured RAN paging area (for example, in order to perform an appropriate location update procedure).
The RRC module 46 is operable to generate, send and receive signalling messages formatted according to the RRC standard. For example, such messages are exchanged between the mobile device 3 and its serving base station 5. The RRC messages may include, for example, messages relating to configuring a (RAN based) paging area for the mobile device 3.
The NAS module 49 is operable to generate, send and receive signalling messages formatted according to the NAS standard. For example, such messages am exchanged between the mobile device 3 and the MME 9 (via the serving base station 5, using the RRC module 46). The NAS messages may include, for example, messages relating to registering and/or updating a tracking area (or cell) where the mobile device 3 is currently located.
The communications control module 63 is operable to control the communication between the base station 5 and the mobile device 3 (user equipment) and other network entities that are connected to the base station 5. The communications control module 63 also controls the separate flows of downlink user traffic (via associated data radio bearers) and control data to be transmitted to the communication devices associated with this base station 5. Control data may include, for example, control data for managing operation of the mobile device 3 (e.g. NAS, RRC, paging, system in formation, and/or the like).
The paging area control module 65 is responsible for maintaining, for each UE for which the base station 5 acts as an anchor, an appropriate (RAN based) paging area. The paging area control module 65 is also responsible for controlling the transceiver 51 to perform paging, of mobile devices 3, when appropriate (e.g, when there is downlink, data to send to a particular mobile device 3 that is not in RRC connected mode).
The RRC module 66 is operable to generate, send and receive signalling messages formatted according to the RRC standard. For example, such messages are exchanged between the base station 5 and the mobile device 3 (and other user equipment within the cell of the base station 5). The RRC messages may include, for example, messages relating to configuring a (RAN based) paging area for the mobile device 3.
The X2 module 67 is operable to generate, send and receive signalling messages (X2/Xn messages) formatted according to the X2AP (or XnAP) standard. The X2/Xn messages may include, for example, messages relating to paging a mobile device 3, data forwarding, transferring/fetching of UE context (and other information relating to the mobile device 3) between neighbouring base stations.
The S1AP module 68 is operable to generate, send and receive signalling messages formatted according to the S1AP (or NG-C) standard. For example, such messages are exchanged between the base station 5 and the AMF/MME 9. The S1AP (or NG-C) messages may include, for example, messages relating to registering the location and/or operating state of user equipment in a cell of the base station 5, requesting paging for a particular mobile device 3, and/or associated responses.
The communications control module 83 is operable to control the communication between the access and mobility management function 9 and the base stations 5, the mobile devices 3, and other network entities that are connected to the access and mobility management function 9.
The UE location registration module 85 is responsible for keeping track of current location and state (e.g. idle or connected) of user equipment connected to the access and mobility management function 9.
The S1AP module 88 is operable to generate, send and receive signalling messages formatted according to the S1AP (or NG-C) standard. For example, such messages are exchanged between the access and mobility management function 9 and connected base stations 5. The S1AP (or NG-C) messages may include, for example, messages relating to registering the location and/or operating state of user equipment in a cell of the base station 5, requesting paging for a particular mobile device 3, and/or associated responses.
The NAS module 89 is operable to generate, send and receive signalling messages formatted according to the NAS standard. For example, such messages am exchanged between the access and mobility management function 9 and the mobile device 3 (via a base station 5, using the S1AP module 88). The NAS messages may include, for example, messages relating to registering and/or updating a tracking area (or cell) where the mobile device 3 is currently located.
In the above description, the mobile device 3, the base station 5, and the access and mobility management function 9 are described for ease of understanding as having a number of discrete modules (such as the communications control modules and the RRC modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the invention, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.
A more detailed description will now be given (with reference to
Initially, the mobile device 3 operates in (RRC) connected state, in which it is able to send uplink (UL) data to the UPS 10 (via the serving base station 5a) and to receive downlink (DL) data. However, in step S501, the serving (anchor) base station 5a decides to move the mobile device 3 to inactive (or LC) state, whilst maintaining the associated (S1 or NG-C/NG-U) connections towards the core network 7 (as generally shown in step S503).
It will be appreciated that the base station 5a may decide to move the mobile device 3 to the inactive (LC) state, when one or more predetermined condition is met. For example, the base station 5a may decide to move the mobile device 3 to the inactive (LC) state after the mobile device 3 has no more data to send or receive (e.g, when the downlink data buffer at the base station 5a is empty and/or when all uplink data requested for sending by the mobile device 3 has been successfully received). The base station 5a may move the mobile device 3 to the inactive (or LC) state, for example, after expiry of a timer (e.g. an inactivity timer) and/or upon request by the mobile device 3a (either explicitly or by an implicit indication, such as an indication of LC-capability).
In order to prepare the mobile device 3 for the inactive state (and to facilitate subsequent resuming of the mobile device's connection), the base station 5a stores/updates (in its memory 59) the UE context associated with the mobile device 3 (including e.g. uplink/downlink data counters, a resume ID, security parameters, in formation identifying any associated S1/NO-C/NG-U bearer, information identifying a paging area, and/or the like).
Next, the base station 5a (using its RRC module 66) generates and sends, in step S505, an appropriately formatted signalling message (e.g. an RRC Connection Release message and/or the like) configuring the mobile device 3 to move to the inactive state (e.g. upon receipt of the message or after expiry of a timer) and/or suspend (release) the radio connection. The base station's 5a message includes at least one of, information identifying a release cause (e.g. ‘RRC-inactive’ and/or the like, which may be included in an appropriately formatted information element); a resume ID; and in formation identifying a paging area associated with the mobile device 3 (for example, a list of all cells/cell IDs that are included in the RAN based paging area, preferably with their respective tracking area codes/identifiers). It will be appreciated that the inclusion of tracking area code (TAC) may beneficially enable a mobile network operator to increase the number of unique base station/cell identifiers within a given PLMN. Further, a resume_ID in combination with a TAC can be made unique within the whole PLMN with reduced resume ID length (i.e. a Resume ID having fewer bits/smaller sine can be employed whilst still being able to differentiate among a relatively large number of (inactive) mobile devices across a particular PLMN).
In step S507, the mobile device 3 changes its operation to the inactive state (light-connected stale/mode) in accordance with the base station's 5a message, and stores the received information identifying the paging area (e.g. list of cells/cell fps and associated tracking area identifiers t. The mobile device 3 also stores the access stratum (AS) context, suspends all signalling radio bearers (SRBs) and data radio bearers (DRBs), and enters to light-connected t inactive state (until it has data to send or it receives signalling (paging) that it has downlink data).
Beneficially, therefore, the base station 5a is able to inform the mobile device 3 about the applicable RAN paging area as part of the procedure in which the base station 5a instructs to mobile device to change its operating state (e.g. from RRC connected to RRC inactive or light-connected state/mode). This ensures that the base station 5a and the mobile device 3 use the same list of cells for the relevant procedures (e.g, paging, location update, random access, etc.).
Therefore, in the example shown in
It will also be appreciated that, using an appropriately formatted RRC Connection Release message, the anchor base station 5a is able to notify a respective RAN paging area to any other mobile devices (e.g. UE4) that might be affected by the change in the cell(s) of the base station 5c.
In this example, the mobile device 3 is initially in inactive state (e.g. following the procedure described above with reference to
In response to an appropriate trigger, of the anchor base station 5a is configured to notify the mobile device 3 (or a set of mobile devices) about a change in their associated RAN paging area (for example, the addition/removal of one or more cells). The trigger may include, for example, one or more of: an update of the applicable paging area and/or a cell thereof; removal/addition of an X2/Xn connection (e.g. the connection to base station 5c); an expiry of a timer measuring a validity period of a previously configured paging area; receipt of downlink data for a mobile device; a change in network (cell) configuration/load, and/or the like.
In more detail, the controller 57 of the anchor base station 5a is configured to initiate RAN based paging for the mobile device 3 (or a set of mobile devices) within the paging area that is appropriate for that mobile device 3 (within a respective paging area for each mobile device, if more than one). RAN based paging typically involves transmitting paging signalling via the air (Uu) interface, via the X2/Xn interface, or both. Therefore, as generally shown in step S601, the anchor base station 5a generates and sends appropriate paging signals (over the Uu air interface) in order to prepare the mobile device 3 to receive information about its updated RAN paging area. This paging message therefore indicates to the mobile device 3 that its associated RAN paging area is being reconfigured (rather than indicating downlink data from the core network 7).
Since the anchor base station 5a does not know whether the mobile device 3 is located in Cell A. or in another cell (of the current paging area), the anchor base station 5a also sends, in step S604, appropriate X2/Xn paging signalling to its neighbour base station(s) 5 in order to attempt to reach the mobile device 3 via neighbour cells (comprised in the current paging area for that mobile device 3).
Beneficially, the anchor base station 5a also includes in the X2/Xn message (e.g. a RAN Routing Area Update Request and/or the like) to its neighbour base station 5b in formation identifying one or more mobile device 3 (e.g. a list of UEs) that are being affected by the paging, area change. (and hence identifying the UEs that need to be paged by the neighbour base station 5b); information identifying one or more cells/base stations that are to be added (if any); and information identifying one or more cells/base stations that am to be removed (if any). Preferably, the information identifying mobile devices may comprise an appropriately formatted information element (e.g. a ‘UE-ID list’ information element) and the information identifying cells/base stations to be aided and/or removed may comprise another information element (e.g. an ‘eNB/gNB add list’ information element and/or an ‘eNB/gNB delete list’ in formation element). Although not shown in
As generally shown in step S605, the neighbour base station 5b generates and sends appropriate paging signals (over the Uu air interface) in its own cell (in this example, Cell B), as described above with reference to step S601. In step S607, the base station 5b confirms receipt of the X2/Xn message from the anchor base station 5a (step S603) by generating and sending an appropriate X2/Xn response (e.g. a RAN Routing Area Update Response and/or the like). It will be appreciated that step S607 might precede step S605, if appropriate.
After transmitting the paging signals in their respective cells, the anchor base station 5a and the neighbour base station 5b proceed to transmit information identifying the change in the RAN paging area of the mobile device(s) 3 that has been paged. In this example, as generally shown in step S608, the base stations 5a and 5b are configured to transmit information identifying cells/base stations to be removed (and/or added) via system information broadcast (SIB).
For example, the base stations 5a and 5b may transmit an appropriately formatted SIB message (e.g. a dedicated. SIB message) including an information element (IE) indicating a list of cells (with their associated tracking area identifier, if applicable) to be deleted from the RAN paging area. The SIB message may be transmitted as part of a system information broadcast or unicast on demand transmission. It will be appreciated that cells to be deleted from the RAN paging area may be notified in a way analogous to the currant method of notifying blacklisted cells (e.g. using SIB4).
Beneficially, by exchanging appropriate information (e.g. using RAN Routing Area update Request on X2/Xn), the neighbour base stations any also able to take action (paging and SIB broadcast/unicast on-demand) in order to notify, in their own cell, any mobile device 3 being affected by the paging area change.
It will be appreciated that paging (steps S601 and S605) may not be necessary to notify the mobile device 3 of a paging area change. Instead, the mobile device 3 may be configured to monitor SIB transmission periodically while operating in the inactive state. This may be achieved, for example, by using an appropriate counter (e.g. changing the counter whenever the paging area changes, thereby prompting the mobile devices 3 to obtain updated paging area information from the SIB). For example, the so-called ‘systemInfoValueTagS1’ (defined in 3GPP TS36.331) may be used/adapted for notifying paging area changes for inactive state/mode mobile devices.
In this example, it is not necessary to perform paging in order to notify mobile devices of a, paging area change. Beneficially, in this example, information relating to the associated paging area (e.g. a change thereof) may be notified periodically, for example, as part of a procedure to update a RAN routing area (and/or the like).
In more detail, a RAN routing area update procedure may be initiated by the mobile device 3, periodically (e.g. upon expiry of a timer), when it needs to perform a cell update. It will be appreciated that this is similar to the legacy trucking area update (TAU) procedure, although in this case the serving base station is configured to update the RAN paging area for the mobile device 3, as pan of the RAN routing area update procedure.
In this case, therefore, the base stations 5 are configured to send, periodically, when requested by mobile devices 3 in their cells, information relating to the RAN routing area/cell in which the mobile device 3 is currently located. For example, the base stations 5 may be configured to send such information upon a periodic location update (and/or the like) initiated by the mobile devices 3. In this example, the mobile devices 3 are configured to generate and send appropriate signalling messages (e.g. a ‘RAN Routing Area Update Request’) to their base station 5. In order to do so, the mobile devices 3 may be configured with an appropriate timer, and request (periodic) RAN routing area updates upon expiry of the timer. It will be appreciated that this is step may be analogous to the legacy timer based TAU.
Turning now to
Steps S701 and S702 are similar to steps S603 and S607 described above with reference to
Therefore, in step S701, the anchor base station 5a generates and sends, to its neighbour base station 5b, an appropriately formatted X2/Xn message (e.g., a RAN Routing Area Update Request) and includes in this message information identifying one or more mobile device 3 (e.g. a list of UEs) that are being affected by the paging area change and information identifying one or more cells/base stations that are to be removed. If appropriate, the anchor base station 5a may also include information identifying one or move cells/base stations that are to be added. In this case, the in formation identifying one or more mobile device 3 (e.g. a list of UEs) indicates to the neighbour base station 5b which UEs need to be notified by the neighbour base station 5b (if located in the associated Cell B).
The base station stores the received information in its memory 59, and confirms receipt of the X2/Xn message from the anchor base station 5a, by generating and sending, in step S702, an appropriate X2/Xn response (e.g. a RAN Routing Area Update Response and/or the like).
In this example, the mobile device 3 is currently operating in inactive state (LC state) within its currently configured RAN paging area (for example, camping on Cell A or Cell B).
If the mobile device 3 is now camping on Cell B, it generates and sends, as shown in step S703, an appropriate signalling message to the Mace station 5b operating that cell, sending cell update. The base station 5b (now acting as a serving base station for the mobile device 3) proceeds to check (based on information stored in its memory 59) whether there is any change in the RAN paging area and whether that particular mobile is affected (included in the list of UEs from the anchor base station 5a). Beneficially, therefore, the serving base station 5b is able to include in its response, in step S704, the information received from the anchor base station 5a (in step S701) identifying one or more cells/base stations to be removed from the RAN paging area of the mobile device 3 of that mobile device 3 is affected). It will be appreciated that the serving base station 5b may be configured to obtain updated RAN paging area information from the anchor base station 5a (e.g., in a similar manner as in steps S701 and S702), before it responds (in step S704) to the RAN routing area update request from the mobile device 3. It will be appreciated that the updated RAN paging area information may be included in a RAN routing area update accept message (and/or the like), for example, as part of an appropriately formatted ‘Modified RAN Routing Area Information’ IE (and/or any other suitable IE).
Beneficially, by exchanging appropriate information (e.g. using RAN Routing Area Update Request on X2/Xn), the neighbour base stations are able to take action in order to notify, in a subsequent RAN routing area update procedure, any mobile device 3 being affected by the paging area change.
On the other hand, if the mobile device 3 is still camping on a cell operated by the anchor base station 5a (e.g. Cell A), the anchor base station 5a is able to provide the updated RAN paging area information to the mobile device 3, when it performs an appropriate (periodic) RAN routing area update. This is generally shown in steps S705 and S706 (which correspond to steps S703 and S704.
In this example, therefore, it is possible to notify the mobile device 3 about an update of its applicable RAN paging area, regardless of which cell the mobile device 3 camps on (and without requiring paging of the mobile device 3).
In this example, the base stations 5 are configured to identify mobile devices 3 (e.g. for which they ad as an anchor base station) that may be impacted by a change relating to that base station (or another base station connected to it). For example, in the scenario shown in
In more detail, when (a cell of) the base station 5c becomes unavailable for RAN based paging (e.g. due to being turned off and/or the like), the base station 5s generates and sends, in step S801, an appropriately formatted (X2/Xn) signalling message informing the other base station 5a about a set of one or more mobile devices 3 that might be affected by this change (e.g. a list of UEs for which the base station 5c is currently acting as the anchor base station). In this example, the have station 5c requests to remove the X2/Xn connection it has with the base station 5a. Therefore, preferably, the message comprises an ‘Xn Removal Request’ (or an ‘X2 Removal Request’) and includes an appropriately formatted IE comprising information (e.g. a list) identifying each (at least one) mobile device 3 that might be affected.
In response to this message, each neighbour base station tin this example, base station 5a) generates and sends, as shown in step S802, an appropriately formatted (X2/Xn) response informing the base station 5c about a set of one or more mobile devices 3 that might be affected by this change (e.g. UEs for which that particular base station 5a is currently acting as the anchor base station). In this example, the message comprises an ‘Xn Removal Response’ (or an ‘X2 Removal Response’) and also includes an appropriately formatted IC identifying (listing) the affected mobile devices 3 (for which that base station 5a is the anchor base station).
It will be appreciated that the list of impacted UEs may comprise a list of associated UE Ins suitable to identify a particular (inactive) mobile device 3, such as, for example. ResumeIDs and/or S-TMSIs (and may also be accompanied by TAC-ID List in order to ensure uniqueness).
The contents of exemplary IEs that may be used are shown in Table 1 (for the X2 Removal Request) and Table 2 (for the X2 Removal Response).
Although not spawn in
It will be appreciated that the respective lists of impacted UEs appearing in the X2 removal request (step S801) and the corresponding response (step S802) are likely to be different as the lists indicate impacted UEs from the perspective of the particular base station sending the message.
In this example, the mobile device 3 does not respond to the paging by the anchor base station 5a in the RAN based paging, area. Therefore, as generally shown in step S901, the anchor base station 5a determines that the RAN based paging has been un successful (failed). For example, the anchor base station 5a may be configured to determine that the RAN based paging has failed if the mobile device 3 does not respond to paging messages (in any cell of the RAN paging area) within a predetermined time interval, which may be indicated by expiry of an associated timer (e.g. a paging timer).
Therefore, when it determines failure of the RAN based paging, the anchor base station 5a proceeds to requesting assistance from the core network 7 (i.e. from the AMF/MME 9). Specifically, the anchor base station 5a generates and sends, in step S903, and appropriately formatted signalling message (such as a ‘CN-Paging Assistance’ message and/or the like) requesting the AMF/MMI 9 to initiate CN based paging procedures for the mobile device 3. The anchor base station 5a includes in this request message information identifying the mobile device 3 to be paged and information identifying one or more cells in which paging is recommended.
It will be appreciated that the cells in which paging is recommended may comprise at least a cell in which the anchor base station 5a was unable to perform RAN based paging (such us any cell operated by the base station 5c for which the associated X2/Xn connection has been removed, although it may comprise any other cell in which the mobile device 3 is likely to be located.
Optionally, the information identifying one or more coils in which paging is recommended may also include, for each cell, information identifying a respective tracking area associated with that cell. The information identifying one or more cells may comprise a list of recommended cells, for example an appropriately formatted in formation element (a ‘Recommended Cells for Paging’ IE and/or the like). Further details of the exemplary CN-Paging Assistance request and the contents of some of the information included in this request are shown in Table 3 below.
In order to assist the anchor base station 5a, the AMF/MME 9 proceeds to initiating core network based paging procedures for the mobile device 3, based on the in formation (e.g. recommended cell list) included in the base station's request. Therefore, the AMP/MME 9 generates (using its S1AP module 88) and sends, in step S905, an appropriately formatted paging request to the base stations 5 operating cells that are included in the recommended cell list (and/or any further cells, if appropriate). It will be appreciated that the AMF/MME 9 may also perform, either concurrently or subsequently, core network based paging procedures for the mobile device 3 over the last known tracking area for the mobile device 3.
Although not shown in
In this example, therefore, even if RAN based paging fails, e.g. due to the mobile device 3 being unable to obtain the updated paging area information, the anchor base station 5a is beneficially able to request the AMF/MME 9 to carry out a core network based paging (e.g. over a wider (tracking) area and/or over cells other than the ones currently included in the RAN paging area). Moreover, since the anchor base station 5a is aware of which cells are affected by the removal of an X2/Xn connection, it is able to assist, the AMF/MME 9 to conduct an optimised paging (e.g. in a smaller area than a tracking area) when RAN-based paging fails.
This message is sent by the base station and is used to request the AMF/MME to page a UE when RAN-based paging fails.
Detailed embodiments have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above embodiments whilst still benefiting from the inventions embodied therein. By way of illustration only a number of these alternatives and modifications will now be described.
It will be appreciated that embodiments of the invention may be particularly beneficial for Internet of Things (or machine-type) data transmission (e.g. transmission of data acquired during measurement events and the like). However, it will be appreciated that the embodiments are also beneficially for transmission of any form of data depending on the application in which the communication device is being used. For example, the above embodiments may be applicable for transmitting data such as user data, backup data, synchronisation data, diagnostic data, monitoring data, usage statistics, error data and/or the like.
For simplicity, the base station 5a is described to be the anchor base station for each mobile device (UE1 to UE4) in
In
In step S503 of
In step S50 of
In the above description, the list of cells (cell IDs) that belong to a particular RAN based paging area includes the respective tracking area codes/identifiers for each cell. It will be appreciated that this allows the mobile device and the erase station to uniquely identify cells across multiple tracking areas (in which the same cell IDS might be reused). However, it will be appreciated that a RAN based paging area may also be defined using a list of cell IDs only (i.e. without tracking area codes/identifiers).
It will be appreciated that the anchor base station may be configured to consider neighbour topology and/or (state of) X2/Xn connections with its neighbour base stations when determining which cells to remove form the paging area (i.e. which cells to include in the deleteCellList). For example, neighbour base station may be configured to exchange information with each other about changes in their con figuration (also including changes in their X2/Xn connection to other haw stations) which might require removal of a cell from the RAN paging area.
Specifically, whenever the anchor base station decides to change the RAN paging area (fir a particular UE in lightly connected/RRC_INACTIVE state), it may follow one of the three options (denoted ‘OPT 1’, ‘OPT 2’, and ‘OPT 3’) illustrated in
It will be appreciated that the RAN paging area may also be referred to as a RAN muting area or a RAN notification area. In some case, the RAN paging area may be a tracking area, although in most cases the RAN paging area comprises fewer cells than a tracking area.
In the above example embodiments, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (i.e. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) can be used for managing operating states and/or notification areas for IoT devices in accordance with the above embodiments. The above example embodiments are also applicable to ‘non-mobile’ or generally stationary user equipment.
In the above description, the mobile device, the base station, and the MME are described for ease of understanding as having a number of discrete functional components or modules. Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the invention, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities.
In the above example embodiments, a number of software modules were described. As those skilled in the art, will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the base station, to the mobility management entity, to the mobile/IoT device, or to other user equipment as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of (his software may be performed using one or more dedicated hardware circuits. However, the use of software module; is preferred as it facilitates the updating of the base station, the mobility management entity, or the mobile device in order to update their functionalities.
It will be appreciated that the controllers referred to in the description of the mobile/IoT device, the base station, and the mobility management entity (i.e. with reference to
In one example described above, a method performed by a base station of a communications network comprises: sending, to a communication device, a message indicating that a paging area for the communication device is to be updated at the communication device; and broadcasting system information comprising information identifying a change to the paging area.
When the base station operates as an anchor base station for the communication device, the method may further comprise sending to another base station or multiple base stations (e.g. that operates a cell of the paging area) a message comprising information identifying a change to the paging area. When the base station operate a cell of the paging area, the method further may comprise receiving front another base station (e.g. an anchor base station) a message comprising information identifying a change to the paging area. The method may further comprise of sending a message to the anchor base station responsive to the message comprising information identifying a change to the paging area (e.g. after sending the message comprising information identifying, a change to the paging area).
The change to the paging area may comprise removal of at least one base station (and/or an associated cell) from the paging area, in which case the system information may comprise a list of at least one base station (and/or an associated cell) to be deleted from the paging area.
In another example described above, a method performed by a base station of a communications network comprises: receiving, from a communication device, a request message to request update of a routing area; and sending, to a communication device, responsive to the request message, a message comprising information identifying a change to the outing area.
When the base station operates as an anchor base station for the communication device, the method may further comprise sending to another base station or multiple base stations (e.g. that operates a cell of the paging area) a message comprising information identifying a change to the routing area. When the base station operates a cell of the routing area, the method may further comprise receiving from another base station (e.g. an anchor base station) a message comprising information identifying a change to the routing area. In this case, the method may further comprise of sending a message to the anchor base station responsive to the message comprising information identifying a change to the touting area.
In another example described above, a method performed by a base station of a communications network comprises: receiving, from another base station, a request message to request removal of a base station to base station interface between base stations crating cells of a paging area; and sending, to the another base station, responsive to the request message, a response message comprising information identifying a change to the paging area; wherein at least one of the request message, and the response message, includes information identifying at least one communication device that will be impacted by the removal, in this example, both the request message and the response message may include respective information identifying at least one communication device that will be impacted by the removal.
In another example described above, a method performed by a communication device of a communications network comprises: receiving, from a base station, a message indicating that a paging area for the communication device is to be updated at the communication device; and receiving system information broadcast comprising in formation identifying a change to the paging area.
The change to the paging area may comprise removal of at least one base station (anchor an associated cell or cells) from the paging area, in which case the system in formation may comprise a list of at least one base station (and/or an associated cell or cells) to be deleted from the paging area.
In another example described above, a method performed by a communication device of a communications network comprises: transmitting, to a base station, a request message to request update of a routing area; receiving, from the base station, responsive to the request message, a message comprising information identifying a change to the routing area.
In another example described above, a method performed by a base station of a communications network comprises: determining that a communication device is to be moved to an inactive or light connected (LC, mode/state; and sending, to the communication device, a message indicating that the communication device is to move to the inactive or light connected (LC) mode/state; wherein, the message includes in formation identifying at least one cell that forms a paging area for the communication device. In this example, the message may comprise a radio resource control (RRC) connection release message. The RRC, connection release message may include in formation identifying a release cause (e.g. release cause=rrc-inactive). The in formation identifying at least one cell may comprise a cell list (e.g. a RANPagingArea-CellList), for example, a list of cells together with respective associated trucking area codes (TAC).
The base station may operate as an anchor base station for the communication device whilst the communication device is in the light connected (LC) mode/state.
In another example described above, a method is performed by a base station acting as an anchor base station for a communication device of a communications network. The method comprises: determining that a paging attempt for the communication device has failed; and sending, to a core network entity, responsive to said determining, a request message to request the core network entity to page the communication device; wherein the request message includes information identifying at least one cell recommended for paging.
In another example described above, a method performed by a core network entity of a communications network comprises: receiving, from a base station acting as an anchor base station for a communication device, responsive to the base station determining that a paging attempt for the communication device has failed, a request message to request the core network entity to page the communication device; wherein the request message includes information identifying at least one cell recommended for paging. In this example, the method may further comprise paging the communication device based on the information identifying at least one cell recommended for paging e.g. based on the RAN Paging Area list assigned to a communication device whilst in the light connected (LC) mode/state.
Whilst specific hardware apparatus having a specific physical structure (e.g, controllers and transceiver circuitry) have been disclosed for performing the various procedures described herein, each step of the methods disclosed in the description and/or forming part of the claims, may be implemented by any suitable means for performing that step. In accordance with this each method aspect of the invention has a corresponding apparatus aspect comprising respective means for performing each stop of that method aspect.
Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.
This application is based upon and claims the benefit of priority from United Kingdom patent application No. 1701965.6, filed on Feb. 3, 2017, the disclosure of which is incorporated herein in its entirety by reference.
| Number | Date | Country | Kind |
|---|---|---|---|
| 1701865.6 | Feb 2017 | GB | national |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16483316 | Aug 2019 | US |
| Child | 18645772 | US |
