Relationship Indication of Multi-SIM Device

Abstract

A method for indicating and operating multiple user equipments (UEs) in a wireless device is provided. In an embodiment disclosed herein, the wireless device may identify the presence of multiple UEs in the wireless device and determine the relationships among the multiple UEs in the wireless device. Accordingly, the wireless device may provide an indication to a network node (e.g., a base station) to indicate the determined relationships among the multiple UEs. On the other hand, the network node may cause the wireless device to perform one or more actions (e.g., paging, handover, etc.) based on the indicated relationships among the multiple UEs in the wireless device. By being able to identify and indicate the multiple UEs in the wireless device and perform network operations accordingly, it is possible to enhance the convenience, flexibility, mobility, and fundamental economy of the wireless device, thereby contributing to improving the subscriber experience.

Description

[0001] Related Applications

[0002] This application claims the benefit of U.S. Provisional Patent Application Ser. No. 62 / 893,608, filed Aug. 29, 2019, the disclosure of which is hereby incorporated herein by reference in its entirety. Field of Technology

[0003] The technology of the present disclosure generally relates to the operation of wireless devices with multiple subscriber identity modules (SIMs) (multi-SIM) in a wireless communication network. Background Art

[0004] A subscriber identity module (SIM) card is an integrated circuit designed to securely store information for identifying and authenticating a subscriber in a wireless communication network such as a Long-Term Evolution (LTE) network, such as an International Mobile Subscriber Identity (IMSI) and an International Mobile Equipment Identity (IMEI). In this regard, a wireless device (e.g., a smart phone) needs to include at least one SIM card to operate in a wireless communication network.

[0005] Today, it has become increasingly common for wireless devices to include more than one SIM card. Thus, such wireless devices are conveniently referred to as multi-SIM devices. Notably, each SIM card is typically associated with a unique telephone number. In this way, a multi-SIM device can provide greater flexibility for partitioning data, voice, text, and multimedia services across multiple telephone numbers. For example, a wireless device with two SIM cards can be configured to have one telephone number dedicated to business use and another telephone number dedicated to personal use.

[0006] In general, all terms used herein will be interpreted according to their ordinary meaning in the relevant technical field, unless clearly given and / or implied a different meaning from the context in which it is used. Unless otherwise explicitly stated, all references to elements, devices, components, parts, steps, etc. should be interpreted openly as referring to at least one instance of the said element, device, component, part, step, etc. The steps of any method disclosed herein do not necessarily have to be performed in the exact order disclosed, unless the steps are explicitly described as after or before another step and / or in a situation where it is implied that the steps must be after or before another step. In appropriate cases, any feature of any embodiment disclosed herein can be applied to any other embodiment. Similarly, any advantage of any embodiment can be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description. Summary of the Invention

[0007] Embodiments disclosed herein include a method for indicating and operating multiple user equipment (UEs) in a wireless device. In a non - limiting example, each of the multiple UEs corresponds to a respective subscriber identity module (SIM) card. In this regard, the wireless device is also referred to as a multi - SIM device. In the embodiments disclosed herein, the wireless device can identify the presence of multiple UEs in the wireless device and determine the relationship between the multiple UEs in the wireless device. Thus, the wireless device can provide an indication to a network node (e.g., a base station) to indicate the determined relationship between the multiple UEs. On the other hand, the network node can cause the wireless device to perform one or more actions (e.g., paging, handover, etc.) based on the indicated relationship between the multiple UEs in the wireless device. By being able to determine and indicate the multiple UEs in the wireless device and perform network operations accordingly, it is possible to enhance the convenience, flexibility, mobility, and basic economy of the wireless device, thereby contributing to an improved subscriber experience.

[0008] In one embodiment, a method for indicating and operating multiple UEs performed by a wireless device is provided. The method includes sending an indication to a network node to indicate the relationship between a first UE and a second UE, where both the first UE and the second UE are included in the wireless device. The method further includes performing one or more actions based on the indicated relationship.

[0009] In another embodiment, the method further includes detecting a trigger event for indicating the relationship between the first UE and the second UE before sending the indication to the network node.

[0010] In another embodiment, the trigger event includes one or more of the following: receiving a request from the network node; activating a new subscriber identity module (SIM) in the wireless device; establishing a network connection by the wireless device; and performing a network access procedure by the wireless device.

[0011] In another embodiment, sending the indication includes sending UE capability information from the first UE to the network node or from the second UE to the network node, where the UE capability information includes the indication that the first UE is associated with the second UE.

[0012] In another embodiment, sending the indication includes sending the indication during a radio resource control (RRC) connection establishment procedure.

[0013] In another embodiment, sending the indication includes protecting the indication by one or more of the following: encrypting the indication; sending the indication after enabling security with the network node; and sending the indication in a message for enabling the security with the network node.

[0014] In another embodiment, performing one or more actions based on the indicated relationship includes, at the first UE: receiving a paging message in the cell of the second UE; and performing a random access procedure in response to receiving the paging message.

[0015] In another embodiment, the cell of the second UE is the primary cell (PCell) of the second UE.

[0016] In another embodiment, performing one or more actions includes, at the second UE: receiving an indication from the network node to wake up the first UE; and triggering the first UE to wake up when receiving the indication to wake up the first UE.

[0017] In another embodiment, performing one or more actions further includes performing one or more actions at the first UE to wake up.

[0018] In another embodiment, performing one or more actions includes, at the first UE: receiving a handover indication from the network node to hand over to a specific cell; and applying the handover indication to both the first UE and the second UE such that both the first UE and the second UE hand over to the specific cell.

[0019] In another embodiment, performing one or more actions includes receiving, at the first UE, a second indication indicating whether the handover indication is applicable to the second UE.

[0020] In another embodiment, performing one or more actions includes performing a procedure by which the first UE and the second UE select the same cell to camp on.

[0021] In another embodiment, performing the procedure includes, at the first UE: obtaining information about the second UE; and performing cell selection based on the information about the second UE.

[0022] In another embodiment, performing one or more actions includes, at the first UE: performing measurements at the first UE; and sharing the measurements with the second UE.

[0023] In one embodiment, a method for a cellular communication system performed by a network node is provided. The method includes receiving an indication indicating a relationship between a first UE and a second UE, both the first UE and the second UE being included in a wireless device. The method further includes performing one or more actions based on the indicated relationship.

[0024] In another embodiment, performing one or more actions includes providing the indication to another network node.

[0025] In another embodiment, performing one or more actions includes sending a paging message to the first UE in the cell of the second UE.

[0026] In another embodiment, performing one or more actions includes sending an indication to the second UE to wake up the first UE.

[0027] In another embodiment, performing one or more actions includes: indicating scheduling resources for the first UE; and indicating scheduling resources for the second UE, wherein the scheduling resources for the first UE are different from the scheduling resources for the second UE.

[0028] In another embodiment, performing one or more actions includes avoiding scheduling the second UE when paging the first UE.

[0029] In another embodiment, performing one or more actions includes at least one of the following: avoiding assigning to the first UE scheduling resources that conflict with the scheduling resources assigned to the second UE; and avoiding assigning to the second UE scheduling resources that conflict with the scheduling resources assigned to the first UE.

[0030] In another embodiment, performing one or more actions includes at least one of the following: providing a handover indication to the first UE to hand over to a specific cell; and providing a second indication indicating whether the handover indication applies to the second UE.

[0031] In another embodiment, receiving an indication includes receiving the indication from the first UE, the second UE, or a combination thereof.

[0032] In another embodiment, receiving an indication includes one or more of the following: receiving UE capability information from the first UE, the UE capability information including the indication associated with the second UE; receiving the indication during a radio resource control (RRC) connection establishment procedure; and receiving the indication in a message for enabling security with the network node.

[0033] In another embodiment, the indication includes an identifier of the second UE.

[0034] In another embodiment, the identifier of the second UE includes one of the following: a cell radio network temporary identifier (C-RNTI); a serving temporary mobile subscriber identity (S-TMSI); an active radio network temporary identifier (I-RNTI); a resume identifier; a globally unique temporary identifier (GUTI); and a new identifier for indicating the association between the second UE and other UEs.

[0035] In another embodiment, receiving the indication includes receiving, from the second UE, the indication indicating the relationship between the first UE and the second UE.

[0036] In another embodiment, the indication includes an identifier of the first UE.

[0037] In another embodiment, the identifier of the first UE includes one of the following: C-RNTI; S-TMSI; I-RNTI; a recovery identifier; GUTI; and a new identifier for indicating an association between the second UE and other UEs.

[0038] In another embodiment, receiving the indication includes receiving, from another network node, the indication indicating the relationship between the first UE and the second UE.

[0039] In one embodiment, a wireless device is provided. The wireless device includes a processing circuit configured to perform any one of the steps performed by the UE in any one of the claims performed by the wireless device. The wireless device further includes a power supply circuit configured to supply power to the wireless device.

[0040] In one embodiment, a network node is provided. The network node includes a control system configured to perform any one of the steps performed by the network node in any one of the claims performed by the network node.

[0041] In one embodiment, a method performed by a core network node for enabling a wireless device to indicate and operate multiple UEs is provided. The method includes providing an indication that a first UE and a second UE in the wireless device are associated to a network node.

[0042] In another embodiment, the method further includes obtaining information indicating that the first UE and the second UE are associated from at least one of the following: Unified Data Management (UDM) and Access and Mobility Management Function (AMF). BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The drawings incorporated in and forming a part of this specification illustrate several aspects of the present disclosure and, together with the description, are used to explain the principles of the present disclosure.

[0044] Figure 1 An example of a cellular communication system is shown in which embodiments of the present disclosure may be implemented;

[0045] Figure 2A wireless communication system is shown that represents a fifth-generation (5G) network architecture composed of core network functions (NFs), where the interaction between any two NFs is represented by point-to-point reference points / interfaces;

[0046] Figure 3 A 5G network architecture is shown that uses service-based interfaces between NFs in the control plane instead of Figure 2 the point-to-point reference points / interfaces used in the 5G network architecture;

[0047] Figure 4 It is a schematic diagram of an exemplary wireless communication network, in which a wireless device and a network node can be configured to identify and operate multiple subscriber devices (UEs) in the wireless device according to embodiments of the present disclosure;

[0048] Figure 5 It is a flowchart showing a method performed by a wireless device in Figure 4 for identifying and operating multiple UEs in the wireless device;

[0049] Figure 6A It is a flowchart showing a method performed by a network node in Figure 4 for enabling a wireless device to identify and operate multiple UEs;

[0050] Figure 6B It is a flowchart showing a method performed by a core network (CN) for enabling a wireless device to identify and operate multiple UEs;

[0051] Figure 7 It is a signal flow diagram showing exemplary signaling between a wireless device and a network node in Figure 4 according to embodiments of the present disclosure;

[0052] Figure 8 It is a signal flow diagram showing exemplary signaling between a wireless device and a network node in Figure 4 according to another embodiment of the present disclosure;

[0053] Figure 9 It is a signal flow diagram showing exemplary signaling between a wireless device and a network node in Figure 4 according to another embodiment of the present disclosure;

[0054] Figure 10 It is a signal flow diagram showing exemplary signaling between a wireless device and a network node in Figure 4 according to another embodiment of the present disclosure;

[0055] Figure 11 It is a signal flow diagram showing exemplary signaling between a wireless device and a network node in Figure 4Signal flow diagram of exemplary signaling between a wireless device and a network node therein;

[0056] Figure 12 is a signal flow diagram showing exemplary signaling between a wireless device and a network node according to another embodiment of the present disclosure; Figure 4 Signal flow diagram of exemplary signaling between a wireless device and a network node therein;

[0057] Figure 13 is a signal flow diagram showing exemplary signaling between a wireless device and a network node according to another embodiment of the present disclosure; Figure 4 Signal flow diagram of exemplary signaling between a wireless device and a network node therein;

[0058] Figure 14 is a signal flow diagram showing exemplary signaling between a wireless device and a network node according to another embodiment of the present disclosure; Figure 4 Signal flow diagram of exemplary signaling between a wireless device and a network node therein;

[0059] Figure 15 is a signal flow diagram showing exemplary signaling between a wireless device and a network node according to another embodiment of the present disclosure; Figure 4 Signal flow diagram of exemplary signaling between a wireless device and a network node therein;

[0060] Figure 16 is a signal flow diagram showing exemplary signaling between a wireless device and a network node according to another embodiment of the present disclosure; Figure 4 Signal flow diagram of exemplary signaling between a wireless device and a network node therein;

[0061] Figure 17 is a schematic block diagram of a network node according to some embodiments of the present disclosure;

[0062] Figure 18 is a schematic block diagram showing a virtualized embodiment of a network node according to some embodiments of the present disclosure;

[0063] Figure 19 is a schematic block diagram of a network node according to some other embodiments of the present disclosure; Figure 17 ;

[0064] Figure 20 is a schematic block diagram of a UE according to some embodiments of the present disclosure;

[0065] Figure 21 is a schematic block diagram of a UE according to some other embodiments of the present disclosure; Figure 20 ;

[0066] Figure 22 is a communication system according to an embodiment of the present disclosure;

[0067] Figure 23 is a communication system according to an embodiment of the present disclosure;

[0068] Figure 24is a flowchart showing a method implemented in a communication system according to an embodiment of the present disclosure;

[0069] Figure 25 is a flowchart showing a method implemented in a communication system according to an embodiment of the present disclosure;

[0070] Figure 26 is a flowchart showing a method implemented in a communication system according to an embodiment of the present disclosure; and

[0071] Figure 27 is a flowchart showing a method implemented in a communication system according to an embodiment of the present disclosure. Detailed implementation

[0072] The embodiments described below represent information that enables those skilled in the art to practice the embodiments and show the best mode of practicing the embodiments. When reading the following description with reference to the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize the applications of these concepts that are not specifically addressed herein. It should be understood that these concepts and applications fall within the scope of the present disclosure.

[0073] Radio node: As used herein, a "radio node" is a radio access node or a wireless device.

[0074] Radio access node: As used herein, a "radio access node" or "radio network node" is any node in the radio access network of a cellular communication network that operates to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to, base stations (e.g., NR base stations (gNBs) in a 3rd Generation Partnership Project (3GPP) 5th Generation (5G) New Radio (NR) network or enhanced or evolved Node Bs (eNBs) in a 3GPP Long Term Evolution (LTE) network), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, home eNBs, or the like), and relay nodes.

[0075] Core network node: As used herein, a "core network node" is any type of node in the core network or any node that implements core network functions. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (PGW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), etc. Some other examples of core network nodes include nodes that implement Access and Mobility Functions (AMF), UPF, Session Management Function (SMF), Authentication Server Function (AUSF), Network Slice Selection Function (NSSF), Network Exposure Function (NEF), Network Function (NF) Repository Function (NRF), Policy Control Function (PCF), Unified Data Management (UDM), etc.

[0076] Wireless device: As used herein, a "wireless device" is any type of device that has access to (i.e., is served by) a cellular communication network by wirelessly transmitting and / or receiving signals to / from one or more radio access nodes. Some examples of wireless devices include, but are not limited to, user equipment devices (UEs) and machine type communication (MTC) devices in a 3GPP network.

[0077] Network node: As used herein, a "network node" is any node that is part of the core network or radio access network of a cellular communication network / system.

[0078] Note that the description given herein focuses on 3GPP cellular communication systems, and as such, 3GPP terminology or terminology similar to 3GPP terminology is often used. However, the concepts disclosed herein are not limited to 3GPP systems.

[0079] Note that in the description herein, reference may be made to the term "cell"; however, especially with respect to 5G NR concepts, beams may be used instead of cells, and thus it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0080] Methods for multi-SIM devices will be described herein. In some descriptions, dual-SIM UEs, i.e., UEs having two SIMs, may be described; however, embodiments may apply to devices having more than two SIMs.

[0081] It should be noted that herein it will be described how a device having multiple SIMs can be considered as a device hosting multiple UEs. From a network perspective, the device can be considered as multiple UEs - one UE per SIM.

[0082] In this regard, Figure 1FIG. 0 shows an example of a cellular communication system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communication system 100 is a 5G system (5GS) including an NR radio access network (RAN) or an LTE RAN (i.e., an E-UTRA RAN) or an evolved packet system (EPS) including an LTE RAN. In this example, the RAN includes base stations 102-1 and 102-2 that are referred to as eNBs in LTE (when connected to an evolved packet core (EPC)) and as gNBs in 5G NR (e.g., an LTE RAN node connected to a 5GC, which is referred to as an eNB), and the base stations 102-1 and 102-2 control corresponding (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are generally referred to herein as base stations 102 and are individually referred to as base stations 102. Similarly, the (macro) cells 104-1 and 104-2 are generally referred to herein as (macro) cells 104 and are individually referred to as (macro) cells 104. The RAN may also include a plurality of low-power nodes 106-1 to 106-4 that control corresponding small cells 108-1 to 108-4. The low-power nodes 106-1 to 106-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs) or the like. It is noted that although not shown, one or more of the small cells 108-1 to 108-4 may alternatively be provided by the base stations 102. The low-power nodes 106-1 to 106-4 are generally referred to herein as low-power nodes 106 and are individually referred to as low-power nodes 106. Similarly, the small cells 108-1 to 108-4 are generally referred to herein as small cells 108 and are individually referred to as small cells 108. The cellular communication system 100 further includes a core network 110, which is referred to as a 5G core (5GC) in 5GS. The base stations 102 (and optionally the low-power nodes 106) are connected to the core system 110.

[0083] The base stations 102 and the low-power nodes 106 provide services to wireless devices 112-1 to 112-5 in the corresponding cells 104 and 108. The wireless devices 112-1 to 112-5 are generally referred to herein as wireless devices 112 and are individually referred to as wireless devices 112. The wireless devices 112 are sometimes also referred to herein as UEs.

[0084] Figure 2 FIG. 7 shows a wireless communication system represented as a 5G network architecture composed of core network functions (NFs), where the interaction between any two NFs is represented by a point-to-point reference point / interface. Figure 2 can be regarded as Figure 1 a particular implementation of the system 100.

[0085] From the access side, Figure 2The 5G network architecture shown in the figure includes multiple UEs connected to the RAN or access network (AN) and the AMF. Typically, the (R)AN includes base stations, such as eNB or gNB, etc. From the perspective of the core network side, Figure 2 The 5G core NFs shown in the figure include NSSF, AUSF, UDM, AMF, SMF, PCF, and AF.

[0086] The reference points of the 5G network architecture are used to develop detailed call flows in the standardization of the specification. The N1 reference point is defined to carry the signaling between the UE and the AMF. The reference points used for the connection between the AN and the AMF and between the AN and the UPF are defined as N2 and N3 respectively. There is a reference point N11 between the AMF and the SMF, which means that the SMF is at least partially controlled by the AMF. N4 is used by the SMF and the UPF, so that the UPF can be set using the control signals generated by the SMF, and the UPF can report its status to the SMF. N9 is the reference point for the connection between different UPFs, and N14 is the reference point for the connection between different AMFs respectively. Since the PCF applies policies to the AMF and the SMP respectively, N15 and N7 are defined. The AMF needs N12 to perform the authentication of the UE. Since the AMF and the SMF need the subscription data of the UE, N8 and N10 are defined.

[0087] The 5G core network aims to separate the user plane and the control plane. The user plane carries user traffic, while the control plane carries the signaling in the network. In Figure 2 the figure, the UPF is in the user plane, and all other NFs (i.e., AMF, SMF, PCF, AF, AUSF, and UDM) are in the control plane. Separating the user plane and the control plane ensures that the resources of each plane are scaled independently. It also allows the UPF to be deployed in a distributed manner separately from the control plane functions. In this architecture, for some applications that require low latency, the UPF can be deployed very close to the UE to shorten the round-trip time (RTT) between the UE and the data network.

[0088] The core 5G network architecture consists of modular functions. For example, the AMF and the SMF are independent functions in the control plane. The separated AMF and SMF allow independent evolution and scaling. Other control plane functions such as the PCF and the AUSF can be separated as Figure 2 shown in the figure. The modular function design enables the 5G core network to flexibly support various services.

[0089] Each NF directly interacts with another NF. It is possible to use an intermediate function to route messages from one NF to another NF. In the control plane, the set of interactions between two NFs is defined as a service, enabling its reuse. This service can support modularity. The user plane supports interactions such as forwarding operations between different UPFs.

[0090] Figure 3 Shows a 5G network architecture that uses service-based interfaces between NFs in the control plane instead of Figure 2 the point-to-point reference points / interfaces used in the 5G network architecture described above. However, the NFs referred to above Figure 2 correspond to the NFs shown in Figure 3 . The (one or more) services provided by an NF to other authorized NFs can be exposed to the authorized NFs through service-based interfaces. In Figure 3 , the service-based interfaces are indicated by the letter "N" followed by the name of the NF (e.g., Namf for the service-based interface of the AMF and Nsmf for the service-based interface of the SMF, etc.). Figure 3 The NEF and NF NRF in Figure 2 are not shown in the Figure 2 discussed above. However, it should be clarified that all the NFs depicted in Figure 3 can interact with the NEF and NRF in Figure 2 as needed, although not explicitly indicated in

[0091] Figure 2 and Figure 3 . Some characteristics of the NFs shown in

[0092] The NF can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform (e.g., cloud infrastructure).

[0093] Embodiments disclosed herein include a method for indicating and operating multiple UEs in a wireless device. In a non-limiting example, each of the multiple UEs corresponds to a respective SIM card. In this regard, the wireless device is also referred to as a multi-SIM device. In the embodiments disclosed herein, the wireless device can identify the presence of multiple UEs in the wireless device and determine the relationships between the multiple UEs in the wireless device. Accordingly, the wireless device can provide an indication to a network node (e.g., a base station) to indicate the determined relationships between the multiple UEs. On the other hand, the network node can cause the wireless device to perform one or more actions (e.g., paging, handover, etc.) based on the indicated relationships between the multiple UEs in the wireless device. By being able to determine and indicate the multiple UEs in the wireless device and perform network operations accordingly, it is possible to enhance the convenience, flexibility, mobility, and basic economy of the wireless device, thereby contributing to an improved subscriber experience.

[0094] Now, a description of some example embodiments of the present disclosure is provided. In this regard, Figure 4 is a schematic diagram of an exemplary wireless communication network, in which a wireless device 400 including a first UE 402A and a second UE 402B and a network node 404 can be configured to identify and operate the multiple UEs 402A and 402B in the wireless device 400 according to embodiments of the present disclosure.

[0095] In one embodiment, a wireless device (e.g., wireless device 112) indicates to a network node (e.g., base station 106) (interchangeably referred to as "the network") the relationship between a first UE (referred to herein as UE1) and a second UE (referred to herein as UE2) in the wireless device. The indication can be an indication of the identity of the second UE indicated by the first UE, as Figure 4 shown.

[0096] In some versions of this embodiment, UE1 can be made to indicate the relationship with UE2, and UE2 can be made to indicate the relationship with UE1.

[0097] The indication indicated by UE1 can be an identity associated with UE2. Alternatively, the indication is an identity associated with both UEs, i.e., UE1 and UE2 have an identity associated with both UEs.

[0098] Figure 5 is shown by Figure 4Flowchart of a method performed by a wireless device 400 in for identifying and operating multiple UEs 402A and 402B in the wireless device 400. In this regard, the wireless device 400 may detect a trigger event for indicating a relationship between a first UE 402A and a second UE 402B, where both the first UE 402A and the second UE 402B are provided within the wireless device 400 (block 500). The wireless device 400 sends an indication to a network node 404 to indicate the relationship between the first UE 402A and the second UE 402B (block 502). Subsequently, the wireless device 400 performs one or more actions (e.g., multi-SIM actions) based on the relationship between the first UE 402A and the second UE 402B (block 504).

[0099] Figure 6A is a flowchart showing a method performed by Figure 4 the network node 404 in for enabling the wireless device 400 to identify and operate based on multiple UEs 402A and 402B. In this regard, the network node 404 receives an indication from the wireless device 400 indicating the relationship between the first UE 402A and the second UE 402B in the wireless device 400 (block 600). The network node 404 then performs one or more actions based on the indicated relationship (block 602).

[0100] Figure 6B is a flowchart showing a method performed by a core network (CN) such as the core network 110 for enabling the wireless device 400 to identify and operate multiple UEs 402A and 402B. In this regard, the CN may provide an indication associated with the first UE 402A and the second UE 402B in the wireless device 400 to the network node 404 (block 604).

[0101] The wireless device 400 may report the relationship indication in one or more of the following ways.

[0102] In one non-limiting example, as Figure 7 shown in , the UE may indicate the relationship indication together with or within the UE capabilities. This may be a new field within the UECapabilityInformation message (e.g., step 702).

[0103] In another non-limiting example, the UE may indicate the relationship indication in a message sent in response to a request sent from the network (e.g., step 700).

[0104] The network may configure the UE to send a relationship indication to the network based on certain triggers. For example, the trigger for a message may not be an explicit request from the network, but rather the network indicates that the UE should send a message that may carry a relationship indication, and the UE may do so in response to certain triggers.

[0105] One example trigger may be that the UE in the wireless device has triggered certain actions, such as establishing a connection to the network (the "connection" may be, for example, a connection at the core network / NAS (Non-Access Stratum) level or a connection to the radio access network / AS (Access Stratum) level).

[0106] Another example is that the UE may send an update in response to a new SIM being activated in the device. This has the advantage that the UE does not send an indication unless there are actually two SIMs in the device.

[0107] As Figure 8 shown, the network may indicate in the RRC reconfiguration message 800 that the UE should send relationship information in the UE Assistance Information message 802, and the UE will do so in response to certain triggers.

[0108] The UE may send a relationship indication during the procedure used by the UE to access the network. This may be, for example, during the RRC connection establishment procedure, the RRC connection resume procedure, the RRC connection re-establishment procedure, etc.

[0109] The relationship indication may be sent, for example, in the message (RRC Setup Complete, RRC Resume Complete, RRC Re-establishment Complete) used to complete the above procedures, or in the message (RRC Setup Request, RRC Resume Request, RRC Re-establishment Request) used to request the above procedures.

[0110] Whether the UE should include such information in the message related to the access procedure may be indicated by the network in a message (e.g., RRC Setup) by, for example, a flag indicating that the network requests such information.

[0111] It is worth noting that the relationship information may be considered sensitive information and may therefore only be sent after the connection is secure (e.g., encryption has been enabled).

[0112] For the method by which the network requests the UE to send a relationship indication, the network may request such information only after security has been enabled.

[0113] Another method is to request information during the procedure for enabling security, for example, request information in the SecurityModeCommand message. As Figure 9 shown in Figure 9 , the UE can receive the SecurityModeCommand message 900 from the network node 404. The UE responds with the relationship indication together with the SecurityModeComplete message 902 or responds to the SecurityModeCommand message 900 in another message.

[0114] During mobility in the RRC_CONNECTED state, the source RAN node includes the relationship indication in the handover preparation procedure and includes it in the relevant source RAN to target RAN message (e.g., NGAP HANDOVER REQUIRED or XnAP HANDOVER REQUEST message). The relationship indication can be included in the source RAN targeting a RAN transparent container.

[0115] In one embodiment, the core network node can indicate the relationship between two UEs. In this regard, the CN (e.g., AMF) includes the relationship indication to the RAN in the relevant procedure. In one example, such a procedure is the New Generation Application Protocol (NGAP) initial context setup procedure for the first UE, where the AMF includes the relationship indication to the second UE in the NGAP INITIAL UECONTEXT SETUP REQUEST message sent from the AMF to the RAN. Another example procedure is the NGAP downlink non-access stratum (NAS) transport procedure to the first UE, where when sending a NAS message (e.g., registration acceptance) to the first UE during the registration procedure, the AMF includes the relationship indication to the second UE in the NGAP DOWNLINK NAS TRANSPORT message sent to the RAN.

[0116] The CN node (e.g., AMF) that assigns the relationship indication may know the relationship between two or more UEs in the same radio device 400 (e.g., by means of subscription information available in a database, such as UDM), and when the subscription information changes, provide it to the AMF during or later during the initial registration / registration procedure of one of the UEs in the radio device 400.

[0117] The subscription data stored in the UDM may include information indicating the existence of multiple UEs in a single radio device (e.g., the subscription information may include multiple related identifiers, such as the listed Subscription Permanent Identifiers (SUPI)). When registering one of the UEs with the network and thus registering the associated identifier (e.g., during the initial registration process), the UDM may provide the AMF with a list of all identifiers or a subset of the identifiers associated with that subscription, and thus provide other UEs within the same radio device.

[0118] If the second UE on the radio device has already been registered with the network, the AMF (e.g., when registering the first UE) may receive an indication from the UDM of which identifier the second (already registered) UE is associated with. The AMF uses this identifier as a key to determine the relationship indication (e.g., 5G S-TMSI) assigned to the second (already registered) UE. The AMF includes in the relevant message sent from the CN (e.g., AMF to RAN) during the relevant process related to the first UE the relationship indication that has been assigned to the second UE by the CN (e.g., AMF).

[0119] If the second UE registers with the network after the first UE, the database (e.g., UDM) may update the AMF that manages the first (registered) UE providing the identifier of the second UE. The AMF uses this identifier as a key to determine the relationship indication (e.g., 5G S-TMSI) assigned to the second (already registered) UE. In this case, the AMF may update the RAN with the relationship indication of the second UE (e.g., the NGAP UE context modification process of the first UE context in the RAN).

[0120] If the second UE has already been registered with the network but is registered in a second AMF different from the first AMF to which the first UE is currently registered, in addition to the identifier of the second UE (e.g., SUPI), the UDM may also include an identifier (e.g., during the process of providing updated subscription information to the first AMF) indicating the identifier of the second AMF to the first AMF (e.g., the Global Unique AMF Identifier (GUAMI) of the second AMF). The first AMF may use the identifier of the second AMF to retrieve information about the relationship indication from the second AMF using a new process / service on the interface between the relevant CN nodes (e.g., on the N14 reference point / interface between the first AMF and the second AMF). In this case, the first AMF may update the RAN by using the relationship indication (e.g., updating the first UE context in the RAN through the NGAP UE context modification process).

[0121] In another embodiment, the second UE may include in the NAS signaling an indication of the relationship of the first UE, e.g., an indication to the network of the registration of the first UE in the radio device to the network. This relationship indication may be included, for example, in any initial NAS message (registration request or service request). In cases where it is considered to provide this information in a secure manner and no NAS security context is available yet in the second UE, the relationship indication may be provided after NAS security has been enabled in the UE (e.g., in the security mode complete message). The relationship indication may be, for example, the 5G globally unique temporary identifier (GUTI) of the second UE. In this embodiment, the relationship indication may be used to address the situation where the subscriptions of the UEs are associated with different operators that do not share a common database (e.g., UDM).

[0122] To be able to transmit the relationship indication of the UE with subscriptions of different operators, the UE may be configured and authorized by the network to:

[0123] • Share the relationship indication between protocol entities that communicate with their corresponding network entities (operated by the corresponding operator);

[0124] • Stop sharing the relationship indication between protocol entities.

[0125] The CN (e.g., AMF) in which the second AMF is registered stores the relationship indication indicating the relationship with the first UE in the second UE. Subsequently, the AMF provides the relationship information to the RAN that manages the second UE, where the relationship information may be stored in the context of the second UE.

[0126] As an example, the relationship information may be provided from the CN (e.g., AMF) to the RAN during the association process of the UE (see 3GPP TS 38.413 v15.3.0), which involves:

[0127] • UE context management in the RAN (e.g., initial UE context setup);

[0128] • Transmission of NAS messages; and

[0129] • UE mobility management process.

[0130] In some embodiments, it is assumed that both UEs are in the same AMF. Additionally, in some embodiments, the S-TMSI of one UE is established when the other UE is connected.

[0131] In some embodiments, the AMF indicates to the RAN where the first UE changes state the existence of a second UE related to the first UE (e.g., S-TMSI).

[0132] In some embodiments, if the UEs are in different AMFs, there may be an indication from AMF1 to AMF2.

[0133] In some embodiments, the indication of the associated UE is sent from the CN, e.g., if a CN type of id (S-TMSI) is used.

[0134] In some embodiments, the indication of the associated UE is sent by the UE to the AMF via NAS signaling and then sent to the RAN.

[0135] In a non-limiting example, the first UE 402A may be linked to the second UE 402B based on one or more different identifiers.

[0136] In one example, the first UE 402A may be linked to the second UE 402B based on the Cell Radio Network Temporary Identifier (C-RNTI). In this regard, UE1 indicates the C-RNTI of UE2. It is noted that this may only work when both UEs are in the CONNECTED mode, as the C-RNTI is an identifier that the UE may not save when in the CONNECTED mode.

[0137] Another candidate indication that can be used to indicate the relationship between UEs is the C-RNTI. It may be made such that UE1 indicates the S-TMSI of UE2. This has the following benefit: the S-TMSI is an identifier that is not released when the UE exits the CONNECTED mode. Then, this identifier can also work for UEs in the IDLE mode.

[0138] In another example, the first UE 402A may be linked to the second UE 402B based on the Inactive Radio Network Temporary Identifier (I-RNTI).

[0139] In this regard, another candidate indication that can be used to indicate the relationship between UEs is the I-RNTI. It may be made such that UE1 indicates the I-RNTI of UE2. The I-RNTI is an identifier that is assigned to the UE for use when the UE is in RRC_INACTIVE and is used by the UE and then indicated to the RAN when returning to the CONNECTED mode so that the RAN can identify the UE (e.g., so that the RAN can retrieve the context of the UE).

[0140] In another example, the first UE 402A may be linked to the second UE 402B based on the resume ID. When the UE is in the IDLE mode, the resume ID is given to the UE for use, and when the UE returns to the CONNECTED mode, the UE indicates the resume ID to the RAN so that the RAN can retrieve the context of the UE.

[0141] In another example, the first UE 402A may be linked to the second UE 402B based on the GUTI.

[0142] In this regard, another candidate indicator that can be used to indicate the relationship between UEs is the GUTI. The UE1 may be made to indicate the GUTI of the UE2. This has the advantage that when the UE exits the CONNECTED mode, the GUTI is an identifier that is not released. Then, this identifier can also function for the UE in the IDLE mode. In addition, this identifier enables identification across PLMNs and CN entities.

[0143] In another example, the first UE 402A may be linked to the second UE 402B based on a new identifier, which may be generated by the wireless device 400 and indicated to the network by both the UE1 and the UE2. In this regard, if the network detects two UEs indicating the same identifier, the network knows that these UEs are related. This has the benefit that the identifier does not need to be changed regardless of the states of the UE1 and the UE2.

[0144] A set of embodiments regarding different uses of the knowledge of the relationship between UEs is described below. These embodiments may be used separately, or any two or more of them may be used together.

[0145] In one embodiment, a network node that wants to page the UE1 (which the network node knows is associated with the UE2) pages the UE1 in the same cell as the cell associated with the UE2. For example, if the network knows that the UE2 is connected to cell A, the network will page the UE1 in cell A. Based on the prior art, the network may page the UE1 in the cell where the network last observed the UE1, and if the UE does not respond to the paging, the network may attempt to page the UE in a wider set of cells (e.g., the cells around cell A), and also if this does not work, the network may page the UE in an even wider set of cells (e.g., all the cells in the tracking area of cell A).

[0146] When the network mentioned above pages the UE1 in the same location as the UE2, this location may mean the cell that serves as the primary cell (PCell) of the UE2.

[0147] In this regard, Figure 10Shows an example process in which a network node 404 (e.g., a base station 106 or a CN node (e.g., an AMF)) pages UE1 in the cell of UE2 (e.g., the PCell of UE2). Optional steps are indicated by dashed lines or dashed boxes. As shown, the network node 404 obtains an indication associated with UE1 and UE2 (e.g., in the same radio device), which is in accordance with any of the embodiments disclosed herein in which the network node 404 obtains such an indication (block 1000). For example, when the network node 404 desires to page UE1, the network node 404 determines the cell of UE2 (e.g., the PCell of UE2) (block 1002). Then, the network node 404 pages UE1 in the cell of UE2, for example, by sending a paging message to UE1 in the cell of E2 (block 1004). Then, UE1 responds to the paging message by, for example, performing a random access procedure in the cell of UE2 (block 1006).

[0148] The network may combine information about the mobility patterns and other observable characteristics of UEs to optimize the management of UEs (e.g., optimize RRM). One example is populating a cell candidate list for paging based on the mobility of two UEs. This requires considering special conditions such as frequency priorities that can be assigned independently and differently, based on subscription information and / or the use of different slices configured on different frequencies (e.g.,).

[0149] This embodiment may need to be used in conjunction with the features described below, where UE1 resides on the same cell as UE2.

[0150] In another embodiment, the network node 404 indicates to UE2 that UE1 needs to wake up. When UE2 receives such an indication, UE2 triggers UE1 to change its state to wake up. Here, waking up may mean that the UE starts monitoring one or more channels.

[0151] In a non-limiting example, UE1 changes its internal discontinuous reception (DRX) state based on an indication received by UE2. Here, changing the DRX state may mean that the UE transitions from an inactive time to an active time. To achieve this, a timer may be started in UE1, and if the timer is running, UE1 may consider itself to be in an active time.

[0152] Figure 11An example of this embodiment is shown. Optional steps are indicated by dashed lines or dashed boxes. As shown, network node 404 (e.g., base station 106 or core network node) obtains an indication associated with UE1 and UE2 (e.g., in the same wireless device), according to any of the embodiments disclosed herein in which network node 404 obtains such an indication (block 1100). Network node 404 decides to wake up UE1 (block 1102) and sends an indication to UE2 to wake up UE1 (block 1104). In response, UE2 triggers the wake-up of UE1. For example, UE2 sends (e.g., via one or more higher layers) a trigger to wake up (block 1106). In response, UE1 performs one or more actions to wake up (e.g., starts monitoring one or more downlink channels, such as PDCCH) (block 1108).

[0153] As Figure 12 shown, network node 404 avoids scheduling UE1 and UE2 on the same resources (block 1202). This has the benefit that wireless device 400 will not be requested to transmit with UE1 and UE2 simultaneously. Alternatively, for the downlink, UE1 does not have to receive using UE1 and UE2 simultaneously.

[0154] As Figure 13 shown, when paging UE1 (block 1304), UE is not scheduled (block 1302).

[0155] As Figure 14 shown, network node 404 avoids the assigned resources (e.g., SRS transmission) of the first UE conflicting with the resources assigned to the second UE (block 1402).

[0156] As Figure 15 shown, wireless device 400 receives a mobility command (e.g., handover command) for UE1 (block 1502) and applies it to UE1 and UE2. For example, if UE1 is instructed to hand over to cell X, wireless device 400 performs a handover to cell X for both UE1 and UE2 (block 1504).

[0157] Network node 404 may indicate to the UE whether the handover command also applies to another UE (e.g., indicate to UE1 that the handover command for that UE also applies to another UE2) (block 1506). This indication may be sent in the handover command itself. Alternatively, the UE may be configured to generally apply this behavior until further notice, etc.

[0158] As Figure 16As shown, a first UE and a second UE (UE1 and UE2) within a wireless device reside on the same cell (block 1600). This can be achieved through a process in UE1 that performs cell (re)selection based on information about UE2 (block 1604). For example, when (e.g., IDLE or INACTIVE in NR), UE1 can select the cell that UE2 has already selected. Then, UE1 and UE2 will end up selecting the same cell to reside on. Alternatively, within the wireless device 400, there can be an entity that performs cell (re)selection for UE1 and UE2 (instead of UE1 performing cell reselection based on information about UE2 as described above).

[0159] In the case where UE2 is in the connected mode and UE1 is in the mode of performing cell (re)selection, UE1 can select the cell to which UE2 is connected. In the case where UE2 is connected to multiple cells (e.g., in carrier aggregation or multi / dual connectivity), UE1 can select one of the cells to which UE2 is connected. UE1 can select the cell that is the PCell of UE2.

[0160] In one embodiment, the network node 404 can indicate to UE2 which cell UE1 should select during cell (re)selection. This can be beneficial if UE2 is in the connected mode and using a cell that for some reason is not suitable / optimal for UE1 to reside on.

[0161] The network node 404 can control whether UE1 should select the same cell as the cell associated with UE2 (or one of the cells associated with UE2) by sending an indication to the wireless device 400. This indication can be sent to UE2, and UE2 will trigger UE1 to apply its behavior of selecting the same cell as the cell associated with UE2. Another method is for the network to indicate through an indication in the system information that this behavior should be applied to the UE. If UE2 is indicating such an indication, then UE2 will indicate to UE1 to apply this behavior. Another method is for the network to directly indicate to UE1 to apply this behavior, which can be done when the UE is in the connected mode, or it can be indicated in a message for indicating the UE to enter the mode of applying cell (re)selection, such as in a message for moving the UE to the IDLE mode or INACTIVE state.

[0162] In one embodiment, UE1 and UE2 share measurements. This means that the measurement results completed by the device for UE1 are also considered by UE2. For example, if UE1 and UE2 are both measuring neighboring cells to perform cell reselection, they can reside on the same cell, and thus if the measurements are performed jointly for the two UEs, separate measurements for UE1 and UE2 can be avoided, which can save power.

[0163] In another example, the wireless device 400 may perform measurements for the purpose of reporting the measurements to the network node 404. In the case where UE1 and UE2 are within the same wireless device, only one of the UEs may perform the measurements (or, put another way, the wireless device performs the measurements only once and the results are shared among the UEs within the wireless device). Note that the reporting may be configured differently for different UEs within the wireless device. For example, based on the configuration from the network for UE1 and UE2, there may be different times to trigger the criteria for the two different devices.

[0164] In one embodiment, the reporting of the measurements may be sent by only one UE and may be indicated to also apply to another UE. For example, if both UE1 and UE2 are configured to perform measurements on a specific frequency or perform measurements on a specific cell, the measurement report may be sent by UE1, but UE2 refrains from sending a measurement report. This has the benefit that the wireless device does not send duplicate information.

[0165] In some embodiments, it is not allowed for UE1 and UE2 to be connected to the same cell, for example in a non-public network (NPN).

[0166] The purpose of the NPN is to create a network for non-public purposes. Thus, U1 and UE2 will have different subscriptions and credentials. The NPN scenario may include a shared network. In the case of an integrated NPN, the UE may have a subscription with a different PLMN.

[0167] Another scenario is having a non-integrated NPN. There may be shared cells and each UE will register with its network and camp on the shared cells. Otherwise, the cells may be dedicated and the UEs will camp on different cells, and this may be similar to the case of having different prioritized frequencies. It seems that all of the above written content will also apply here.

[0168] Figure 17Schematic block diagram of a network node 1700 according to some embodiments of the present disclosure. The network node 1700 can be, for example, a radio access node (such as base station 102 or 106) or a core network node (such as a network node implementing core network functions such as, for example, AMF). As shown, the network node 1700 includes a control system 1702, and the control system 1702 includes one or more processors 1704 (such as, for example, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or the like), a memory 1706, and a network interface 1708. The one or more processors 1704 are also referred to herein as processing circuitry. Further, if the network node 1700 is a radio access node, the network node 1700 includes one or more radio units 1710, and each radio unit 1710 includes one or more transmitters 1712 and one or more receivers 1714 coupled to one or more antennas 1716. The radio unit 1710 can be referred to as or be part of radio interface circuitry. In some embodiments, the (one or more) radio units 1710 are external to the control system 1702 and are connected to the control system 1702 via, for example, a wired connection (such as, for example, an optical cable). However, in some other embodiments, the (one or more) radio units 1710 and potentially also the (one or more) antennas 1716 are integrated with the control system 1702. The one or more processors 1704 operate to provide one or more functions of the network node 1700 as described herein. In some embodiments, the (one or more) functions are implemented in software, such as, for example, stored in the memory 1706 and executed by the one or more processors 1704.

[0169] Figure 18FIG. 0 is a schematic block diagram showing a virtualized implementation of a network node 1700 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of network nodes. As used herein, a “virtualized” network node is an implementation of network node 1700 in which at least a portion of the functionality of network node 1700 (e.g., via one or more virtual machines executing on one or more physical processing nodes in the network) is implemented as one or more virtual components. As shown, in this example, network node 1700 includes one or more processing nodes 1800 coupled to or included as part of network 1802. Each processing node 1800 includes one or more processors 1804 (e.g., CPU, ASIC, FPGA, and / or the like), memory 1806, and a network interface 1808. Additionally, if network node 1700 is a radio access node, network node 1700 may further include a control system 1702 and / or one or more radio units 1710, as described above.

[0170] In this example, the functionality 1810 of network node 1700 described herein is distributed across control system 1702 and one or more processing nodes 1800 in any desired manner or is implemented at one or more processing nodes 1800 and control system 1702 and / or radio unit(s) 1710. In some particular embodiments, some or all of the functionality 1810 of network node 1700 described herein is implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments hosted by one or more processing nodes 1800.

[0171] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, causes the at least one processor to implement the functionality of network node 1700 according to any of the embodiments described herein or a node (e.g., processing node 1800) that implements one or more of the functionality 1810 of network node 1700 in a virtual environment. In some embodiments, a carrier including the aforementioned computer program product is provided. The carrier is one of the following: an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as memory).

[0172] Figure 19is a schematic block diagram of a network node 1700 according to some other embodiments of the present disclosure. The network node 1700 includes one or more modules 1900, each of which is implemented in software. The (one or more) modules 1900 provide the functionality of the network node 1700 described herein. This discussion is equally applicable to Figure 18 the processing node 1800, where the module 1900 can be implemented at one of the processing nodes 1800, or distributed across multiple processing nodes 1800, and / or distributed across the (one or more) processing nodes 1800 and the control system 1702.

[0173] Figure 20 is a schematic block diagram of a UE 2000 according to some embodiments of the present disclosure. It is noted that the UE 2000 can be a wireless device that can be regarded as having multiple UEs (e.g., a dual-SIM or multi-SIM UE). Alternatively, the UE 2000 can be, for example, the UE1 or UE2 described in the above embodiments. As shown, the UE 2000 includes one or more processors 2002 (e.g., a CPU, an ASIC, an FPGA, and / or the like), a memory 2004, and one or more transceivers 2006, each of which includes one or more transmitters 2008 and one or more receivers 2010 coupled to one or more antennas 2012. As will be understood by those skilled in the art, the (one or more) transceivers 2006 include radio front-end circuitry connected to the (one or more) antennas 2012, and the radio front-end circuitry is configured to condition the signals transmitted between the (one or more) antennas 2012 and the (one or more) processors 2002. The processor 2002 is also referred to as a processing circuit herein. The transceiver 2006 is also referred to as a radio circuit herein. In some embodiments, the functionality of the UE 2000 described above can be implemented fully or partially in software, such as software stored in the memory 2004 and executed by the (one or more) processors 2002. Note that the UE 2000 can include Figure 20 additional components not shown in

[0174] In some embodiments, a computer program comprising instructions is provided, which when executed by at least one processor, cause the at least one processor to implement the functionality of the UE 2000 according to any of the embodiments described herein. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of the following: an electronic signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0175] Figure 21 is a schematic block diagram of a UE 2000 according to some other embodiments of the present disclosure. The UE 2000 includes one or more modules 2100, and each module 2100 is implemented in software. The (one or more) modules 2100 provide the functionality of the UE 2000 described herein.

[0176] Referring Figure 22 , according to an embodiment, a communication system includes a telecommunication network 2200, such as a 3GPP-type cellular network, which includes an access network 2202 (such as a RAN) and a core network 2204. The access network 2202 includes a plurality of base stations 2206A, 2206B, 2206C (such as Node B, eNB, gNB, or other types of wireless access points (APs)) that each define a corresponding coverage area 2208A, 2208B, 2208C. Each base station 2206A, 2206B, 2206C can be connected to the core network 2204 through a wired or wireless connection 2210. A first UE 2212 located in the coverage area 2208C is configured to wirelessly connect to or be paged by the corresponding base station 2206C. A second UE 2214 in the coverage area 2208A can wirelessly connect to the corresponding base station 2206A. Although multiple UEs 2212, 2214 are shown in this example, the disclosed embodiments are equally applicable to cases where there is a single UE in the coverage area or where a single UE is connected to the corresponding base station 2206.

[0177] The telecommunications network 2200 is itself connected to a host computer 2216, which may be embodied in the hardware and / or software of a stand-alone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 2216 may be under the ownership or control of a service provider, or may be operated by or on behalf of a service provider. The connections 2218 and 2220 between the telecommunications network 2200 and the host computer 2216 may extend directly from the core network 2204 to the host computer 2216 or may be via an optional intermediate network 2222. The intermediate network 2222 may be one of a public, private, or managed network or a combination of more than one of a public, private, or managed network; the intermediate network 2222 (if any) may be a backbone network or the Internet; in particular, the intermediate network 2222 may include two or more subnets (not shown).

[0178] Figure 22 The communication system as a whole implements the connectivity between the connected UEs 2212, 2214 and the host computer 2216. The connectivity may be described as an over-the-top (OTT) connection 2224. The host computer 2216 and the connected UEs 2212, 2214 are configured to communicate data and / or signaling via the OTT connection 2224 using the access network 2202, the core network 2204, any intermediate network 2222, and possibly additional infrastructure (not shown) as intermediaries. The OTT connection 2224 may be transparent in the sense that the participating communication devices through which the OTT connection 2224 passes do not know the routes of the uplink and downlink communications. For example, the base station 2206 may not or need not be informed about the past route of an incoming downlink communication having data originating from the host computer 2216 to be forwarded (e.g., handed over) to the connected UE 2212. Similarly, the base station 2206 need not know the future route of an outgoing uplink communication originating from the UE 2212 towards the host computer 2216.

[0179] According to an embodiment, reference will now be made to Figure 23Describe example implementations of the UE, the base station, and the host computer discussed in the previous paragraphs. In the communication system 2300, the host computer 2302 includes hardware 2304, which includes a communication interface 2306 configured to establish and maintain a wired or wireless connection to an interface of different communication devices of the communication system 2300. The host computer 2302 further includes a processing circuit 2308, which may have storage and / or processing capabilities. In particular, the processing circuit 2308 may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) suitable for executing instructions. The host computer 2302 further includes software 2310, which is stored in or accessible by the host computer 2302 and executable by the processing circuit 2308. The software 2310 includes a host application 2312. The host application 2312 may be operable to provide services to a remote user, such as the UE 2314, which is connected via an OTT connection 2316 terminated at the UE 2314 and the host computer 2302. When providing services to the remote user, the host application 2312 may provide user data transmitted using the OTT connection 2316.

[0180] The communication system 2300 further includes a base station 2318, which is provided in a telecommunication system and includes hardware 2320 that enables it to communicate with the host computer 2302 and the UE 2314. The hardware 2320 may include a communication interface 2322 for establishing and maintaining a wired or wireless connection to an interface of different communication devices of the communication system 2300, and a radio interface 2324 for establishing and maintaining at least a wireless connection 2326 to the UE 2314 located in a coverage area (not shown) served by the base station 2318. The communication interface 2322 may be configured to facilitate a connection 2328 to the host computer 2302. The connection 2328 may be direct or it may go through the core network of the telecommunication system (not shown) and / or through one or more intermediate networks external to the telecommunication system. In the illustrated embodiment, the hardware 2320 of the base station 2318 further includes a processing circuit 2330, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) suitable for executing instructions. The base station 2318 further has software 2332 stored internally or accessible via an external connection. Figure 23 in which is not shown). Figure 23 in which is not shown).

[0181] The communication system 2300 further includes the UE 2314 already mentioned. The hardware 2334 of the UE 2314 may include a radio interface 2336 configured to establish and maintain a wireless connection 2326 with a base station serving the coverage area where the UE 2314 is currently located. The hardware 2334 of the UE 2314 further includes processing circuitry 2338, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) suitable for executing instructions. The UE 2314 further includes software 2340, which is stored in or accessible by the UE 2314 and executable by the processing circuitry 2338. The software 2340 includes a client application 2342. The client application 2342 may be operable to provide services to a human or non-human user via the UE 2314 with the support of the host computer 2302. In the host computer 2302, the executed host application 2312 may communicate with the executed client application 2342 via an OTT connection 2316 terminated at the UE 2314 and the host computer 2302. When providing services to the user, the client application 2342 may receive request data from the host application 2312 and provide user data in response to the request data. The OTT connection 2316 may transmit both the request data and the user data. The client application 2342 may interact with the user to generate the user data it provides.

[0182] Note Figure 23 The host computer 2302, the base station 2318, and the UE 2314 shown in Figure 22 may be similar or identical to one of the host computer 2016, base stations 2206A, 2206B, 2206C, and one of the UEs 2212, 2214, respectively. That is, the internal workings of these entities may be as shown in Figure 23 and, independently, the surrounding network topology may be Figure 20 the surrounding network topology of

[0183] In Figure 23 the OTT connection 2316 has been abstractly drawn to show the communication between the host computer 2302 and the UE 2314 via the base station 2318 without explicitly mentioning any intermediate devices and the exact routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide the routing from the UE 2314 or from the service provider operating the host computer 2302 or from both. Although the OTT connection 2316 is active, the network infrastructure may further make decisions by which it dynamically changes the routing (e.g., based on load balancing considerations or network reconfiguration).

[0184] The wireless connection 2326 between the UE 2314 and the base station 2318 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 2314 using the OTT connection 2316, in which the wireless connection 2326 forms the final segment.

[0185] A measurement process can be provided for the purpose of monitoring data rate, latency, and other factors improved by one or more embodiments. There can further be optional network functionality for reconfiguring the OTT connection 2316 between the host computer 2302 and the UE 2314 in response to changes in the measurement results. The measurement process and / or network functionality for reconfiguring the OTT connection 2316 can be implemented in the software 2310 and hardware 2304 of the host computer 2302 or in the software 2340 and hardware 2334 of the UE 2314 or both. In some embodiments, sensors (not shown) can be deployed in or associated with the communication devices through which the OTT connection 2316 passes; the sensors can participate in the measurement process by supplying values of the monitored quantities exemplified above or other physical quantities from which the software 2310, 2340 can calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 2316 can include message format, retransmission settings, preferred routing, etc.; the reconfiguration need not affect the base station 2318, and it may be unknown or imperceptible to the base station 2318. Such processes and functionality can be known and practiced in the art. In certain embodiments, the measurement can involve dedicated UE signaling that facilitates the measurement of throughput, propagation time, latency, etc. of the host computer 2302. The measurement can be implemented because the software 2310 and 2340 cause the use of the OTT connection 2316 to transmit messages, particularly empty or "dummy" messages, when they monitor propagation time, error, etc.

[0186] Figure 24 is a flowchart showing a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which can be those referred to Figure 22 and 23 described. For the sake of simplicity of this disclosure, only the Figure 24Reference to the accompanying drawings. In step 2400, the host computer provides user data. In sub-step 2402 of step 2400, which may be optional, the host computer provides user data by executing a host application. In step 2404, the host computer initiates the transmission of the user data to be carried to the UE. In step 2406, which may be optional, according to the teachings of the embodiments described throughout this disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 2408, which may also be optional, the UE executes a client application associated with the host application executed by the host computer.

[0187] Figure 25 is a flowchart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be those referred to in the accompanying drawings Figure 22 and 23 described. To simplify this disclosure, only the reference to the accompanying drawings Figure 25 will be included in this section. In step 2500 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 2502, the host computer initiates the transmission of the user data to be carried to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may be relayed via the base station. In step 2504, which may be optional, the UE receives the user data carried in the transmission.

[0188] Figure 26 is a flowchart showing a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be those referred to in the reference Figure 22 and 23 described. To simplify this disclosure, only the reference to the Figure 26Accompanying drawing references. In step 2600 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 2602, the UE provides user data. In sub-step 2604 of step 2600 (which may be optional), the UE provides user data by executing a client application. In sub-step 2606 of step 2602 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates, in sub-step 2608 (which may be optional), the transmission of the user data to the host computer. In step 2610 of the method, the host computer receives the user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0189] Figure 27 is a flowchart showing a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be those referred to Figure 22 and 23 described. To simplify this disclosure, only the accompanying drawing references to Figure 27 will be included in this section. In step 2700 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 2702 (which may be optional), the base station initiates the transmission of the received user data to the host computer. In step 2704 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0190] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include a plurality of these functional units. These functional units may be implemented via a processing circuit that may include one or more microprocessors or microcontrollers and other digital hardware, which may include a digital signal processor (DSP), dedicated digital logic, etc. The processing circuit may be configured to execute program code stored in a memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunication and / or data communication protocols and instructions for executing one or more of the techniques described herein. In some implementations, the processing circuit may be used to cause the corresponding functional unit to perform the corresponding function in accordance with one or more embodiments of this disclosure.

[0191] Although the processes in the figures may show a specific order of operations performed by certain embodiments of the present disclosure, it should be understood that such an order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0192] Some exemplary embodiments of the present disclosure are as follows.

[0193] Group A Embodiments

[0194] Embodiment 1: A method performed by a wireless device that is perceived by a cellular communication system as a plurality of UEs (UE1, UE2, and optionally one or more additional UEs), the method including sending an indication to a network node that the UE1 is associated with the UE2 for the UE1.

[0195] Embodiment 2: The method according to Embodiment 1, wherein sending the indication includes sending UE capability information including the indication that the UE1 is associated with the UE2 to the network node for the UE1.

[0196] Embodiment 3: The method according to Embodiment 1, wherein sending the indication includes sending the indication in response to a request from the network node.

[0197] Embodiment 4: The method according to Embodiment 1, wherein sending the indication includes sending the indication to the network node in response to a triggering event.

[0198] Embodiment 5: The method according to Embodiment 1, wherein sending the indication includes sending the indication to the network node during an access procedure.

[0199] Embodiment 6: The method according to Embodiment 1, wherein sending the indication includes sending the indication to the network node in a security-related message (e.g., a SecurityModeComplete message).

[0200] Embodiment 7: The method according to any one of Embodiments 1 to 6, wherein the indication includes an identifier of the UE2.

[0201] Embodiment 8: The method according to Embodiment 7, wherein the identifier of the UE2 includes the C-RNTI of UE2, the S-TMSI of UE2, the I-RNTI of UE2, the recovery ID of UE2, the GUIT of UE2, or a new identifier of UE2 for the purpose of indicating the association between UE2 and one or more other UEs.

[0202] Example 9: A method performed by a wireless device that is perceived by a cellular communication system as multiple UEs (UE1, UE2, and optionally one or more additional UEs), the method including receiving a paging message for UE1 in the cell of UE2.

[0203] Example 10: The method according to Example 9, further including performing one or more actions (e.g., performing a random access procedure in the cell of UE2) in response to the paging message.

[0204] Example 11: The method according to Example 9 or 10, wherein the cell of UE2 is the PCell of UE2.

[0205] Example 12: A method performed by a wireless device that is perceived by a cellular communication system as multiple UEs (UE1, UE2, and optionally one or more additional UEs), the method including: receiving, for UE2, an indication from a network node to wake up UE1; and performing one or more actions to trigger the wake-up of UE1 upon receiving the indication to wake up UE1.

[0206] Example 13: A method performed by a wireless device that is perceived by a cellular communication system as multiple UEs (UE1, UE2, and optionally one or more additional UEs), the method including: receiving, for UE1, an indication from a network node to cause UE1 to switch to a specific cell; and in response to receiving the indication to cause UE1 to switch to the specific cell, performing one or more actions to cause both UE1 and UE2 to switch to the specific cell.

[0207] Example 14: The method according to Example 13, further including receiving a second indication indicating whether the indication to cause UE1 to switch to the specific cell also applies to UE2.

[0208] Example 15: A method performed by a wireless device that is perceived by a cellular communication system as multiple UEs (UE1, UE2, and optionally one or more additional UEs), the method including performing a procedure by which UE1 and UE2 select the same cell to camp on.

[0209] Example 16: The method according to Example 15, wherein performing the procedure includes: obtaining information about UE2 at UE1; and performing cell selection at UE2 based on the information about UE2 such that UE1 and UE2 camp on the same cell.

[0210] Example 17: The method according to Example 15, wherein performing the process includes: performing cell selection for both the UE1 and the UE2 at a single entity within the wireless device, such that the UE1 and the UE2 camp on the same cell.

[0211] Example 18: A method performed by a wireless device, the wireless device being perceived by a cellular communication system as a plurality of UEs (UE1, UE2, and optionally one or more additional UEs), the method including performing measurements for the UE1 and sharing the measurements with the UE2.

[0212] Example 19: The method according to any one of the preceding embodiments, further including: providing user data; and forwarding the user data to a host computer via a transmission to a base station.

[0213] Group B Embodiments

[0214] Example 20: A method performed by a base station, including: receiving an indication associated with a first UE (UE1) and a second UE (UE2); and using the indication to perform one or more actions.

[0215] Example 21: The method according to Example 20, wherein the one or more actions include providing the indication to another network node.

[0216] Example 22: The method according to Example 20 or 21, wherein the one or more actions include paging the UE1 in the cell of the UE2 (e.g., the PCell of the UE2).

[0217] Example 23: The method according to any one of Examples 20 to 22, wherein the one or more actions include sending an indication to the UE2 to wake up the UE1.

[0218] Example 24: The method according to any one of Examples 20 to 23, wherein the one or more actions include avoiding scheduling the UE1 and the UE2 on the same resources (e.g., on the same time and frequency resources).

[0219] Example 25: The method according to any one of Examples 20 to 24, wherein the one or more actions include scheduling the UE1 and the UE2 on different resources (e.g., on different time and frequency resources).

[0220] Example 26: The method according to any one of Examples 20 to 25, wherein the one or more actions include avoiding scheduling the UE2 when paging the UE1.

[0221] Example 27: The method according to any one of Examples 20 to 26, wherein the one or more actions include sending to UE1: an indication to cause UE1 to switch to a specific cell, and a second indication that the indication to cause UE1 to switch to the specific cell also applies to UE2.

[0222] Example 28: The method according to any one of Examples 20 to 27, wherein receiving the indication associated with the first UE (UE1) and the second UE (UE2) includes receiving, from the first UE (UE1), the indication associated with the first UE (UE1) and the second UE (UE2).

[0223] Example 29: The method according to Example 28, wherein the indication includes an identifier of UE2.

[0224] Example 30: The method according to Example 29, wherein the identifier of UE2 includes the C-RNTI of UE2, the S-TMSI of UE2, the I-RNTI of UE2, the recovery ID of UE2, the GUIT of UE2, or a new identifier of UE2 for indicating the association between UE2 and one or more other UEs.

[0225] Example 31: The method according to any one of Examples 20 to 27, wherein receiving the indication associated with the first UE (UE1) and the second UE (UE2) includes receiving, from the second UE (UE2), the indication associated with the first UE (UE1) and the second UE (UE2).

[0226] Example 32: The method according to Example 31, wherein the indication includes an identifier of UE1.

[0227] Example 33: The method according to Example 32, wherein the identifier of UE1 includes the C-RNTI of UE1, the S-TMSI of UE1, the I-RNTI of UE1, the recovery ID of UE1, the GUIT of UE1, or a new identifier of UE1 for indicating the association between UE1 and one or more other UEs.

[0228] Example 34: The method according to any one of Examples 20 to 27, wherein receiving the indication associated with the first UE (UE1) and the second UE (UE2) includes receiving, from another network node (e.g., a core network node), the indication associated with the first UE (UE1) and the second UE (UE2).

[0229] Example 35: The method according to any one of the foregoing examples further comprises: obtaining user data; and forwarding the user data to a host computer or a wireless device.

[0230] Group C examples

[0231] Example 36: A method performed by a core network node, comprising providing an indication associated with a first UE (UE1) and a second UE (UE2) to a radio access node.

[0232] Example 37: The method according to Example 36 further comprises obtaining information (e.g., an indication that the first UE (UE1) and the second UE (UE2) are associated) indicating that the first UE (UE1) and the second UE (UE2) are associated from another network node (e.g., a UDM or an AMF).

[0233] Group D examples

[0234] Example 38: A wireless device comprising: a processing circuit configured to perform any one of the steps according to any one of Group A examples; and a power supply circuit configured to supply power to the wireless device.

[0235] Example 39: A base station comprising: a processing circuit configured to perform any one of the steps according to any one of Group B examples; and a power supply circuit configured to supply power to the base station.

[0236] Example 40: A user equipment UE, the UE comprising:

[0237] - an antenna configured to transmit and receive wireless signals;

[0238] - a radio front-end circuit connected to the antenna and to a processing circuit and configured to condition signals transmitted between the antenna and the processing circuit;

[0239] - the processing circuit configured to perform any one of the steps according to any one of Group A examples;

[0240] - an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit;

[0241] - an output interface connected to the processing circuit and configured to output information that has been processed by the processing circuit from the UE; and

[0242] - A battery, the battery being connected to the processing circuit and configured to supply power to the UE.

[0243] Example 41: A communication system including a host computer, comprising:

[0244] - A processing circuit, the processing circuit being configured to provide user data; and

[0245] - A communication interface, the communication interface being configured to forward the user data to a cellular network for transmission to a user equipment UE;

[0246] - Wherein the cellular network includes a base station having a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any one of the steps described in any one of Group B embodiments.

[0247] Example 42: The communication system according to the foregoing embodiment further includes a base station.

[0248] Example 43: The communication system according to the previous 2 embodiments further includes the UE, wherein the UE is configured to communicate with the base station.

[0249] Example 44: The communication system according to the previous 3 embodiments, wherein:

[0250] - The processing circuit of the host computer is configured to execute a host application to provide the user data; and

[0251] - The UE includes a processing circuit, the processing circuit being configured to execute a client application associated with the host application.

[0252] Example 45: A method implemented in a communication system including a host computer, a base station, and a user equipment UE, the method comprising:

[0253] - At the host computer, providing user data; and

[0254] - At the host computer, initiating a transmission of the user data to the UE via a cellular network including the base station, wherein the base station performs any one of the steps described in any one of Group B embodiments.

[0255] Example 46: The method according to the foregoing embodiment further includes transmitting the user data at the base station.

[0256] Example 47: The method according to the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, and the method further includes executing a client application associated with the host application at the UE.

[0257] Example 48: A user equipment UE configured to communicate with a base station, the UE including a radio interface and a processing circuit, the processing circuit being configured to perform the methods described in the previous 3 examples.

[0258] Example 49: A communication system including a host computer, comprising:

[0259] - A processing circuit configured to provide user data; and

[0260] - A communication interface configured to forward the user data to a cellular network for transmission to a user equipment UE;

[0261] - Wherein the UE includes a radio interface and a processing circuit, and the components of the UE are configured to perform any of the steps described in any one of Group A of the examples.

[0262] Example 50: The communication system according to the previous example, wherein the cellular network further includes a base station configured to communicate with the UE.

[0263] Example 51: The communication system according to the previous 2 examples, wherein:

[0264] - The processing circuit of the host computer is configured to execute a host application to provide the user data; and

[0265] - The processing circuit of the UE is configured to execute a client application associated with the host application.

[0266] Example 52: A method implemented in a communication system including a host computer, a base station, and a user equipment UE, the method comprising:

[0267] - At the host computer, providing user data; and

[0268] - At the host computer, initiating a transmission of the user data via a cellular network including the base station to the UE, wherein the UE performs any of the steps described in any one of Group A of the examples.

[0269] Example 53: The method according to the previous example, further comprising receiving the user data at the UE from the base station.

[0270] Example 54: A communication system including a host computer, comprising:

[0271] - A communication interface configured to receive user data sourced from a transmission from a user equipment UE to a base station;

[0272] - Wherein the UE includes a radio interface and a processing circuit, and the processing circuit of the UE is configured to perform any one of the steps described in any one of Group A of embodiments.

[0273] Embodiment 55: The communication system according to the foregoing embodiments further includes the UE.

[0274] Embodiment 46: The communication system according to the previous 2 embodiments further includes the base station, wherein the base station includes a radio interface configured to communicate with the UE and a communication interface configured to forward the user data carried by the transmission from the UE to the base station to the host computer.

[0275] Embodiment 57: The communication system according to the previous 3 embodiments, wherein:

[0276] - The processing circuit of the host computer is configured to execute a host application; and

[0277] - The processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing the user data.

[0278] Embodiment 58: The communication system according to the previous 4 embodiments, wherein:

[0279] - The processing circuit of the host computer is configured to execute a host application, thereby providing request data; and

[0280] - The processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.

[0281] Embodiment 59: A method implemented in a communication system including a host computer, a base station, and a user equipment UE, the method including: at the host computer, receiving user data transmitted from the UE to the base station, wherein the UE performs any one of the steps described in any one of Group A of embodiments.

[0282] Embodiment 60: The method according to the foregoing embodiments further includes providing the user data from the UE to the base station.

[0283] Embodiment 61: The method according to the previous 2 embodiments further includes:

[0284] - At the UE, executing a client application to provide the user data to be transmitted; and

[0285] - At the host computer, executing a host application associated with the client application.

[0286] Example 62: The method according to the previous three examples further comprises:

[0287] - at the UE, executing a client application; and

[0288] - at the UE, receiving input data for the client application, the input data being provided at the host computer by executing a host application associated with the client application;

[0289] - wherein the client application provides the user data to be transmitted in response to the input data.

[0290] Example 63: A communication system comprising a host computer, the host computer comprising a communication interface configured to receive user data sourced from a transmission from a user equipment UE to a base station, wherein the base station comprises a radio interface and a processing circuit, the processing circuit of the base station being configured to perform any one of the steps of any one of Group B of the examples.

[0291] Example 64: The communication system according to the previous examples further comprises the base station.

[0292] Example 65: The communication system according to the previous two examples further comprises the UE, wherein the UE is configured to communicate with the base station.

[0293] Example 66: The communication system according to the previous three examples, wherein:

[0294] - the processing circuit of the host computer is configured to execute a host application; and

[0295] - the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

[0296] Example 67: A method implemented in a communication system comprising a host computer, a base station and a user equipment UE, the method comprising: at the host computer, receiving from the base station user data sourced from a transmission that the base station has received from the UE, wherein the UE performs any one of the steps of any one of Group A of the examples.

[0297] Example 68: The method according to the previous examples further comprises receiving the user data at the base station from the UE.

[0298] Example 69: The method according to the previous two examples further comprises initiating at the base station the transmission of the received user data to the host computer.

[0299] At least some of the following abbreviations may be used in this disclosure. If there are inconsistencies between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

[0300] • 3GPP Third Generation Partnership Project

[0301] • 5G Fifth Generation

[0302] • 5GC Fifth Generation Core

[0303] • 5GS Fifth Generation System

[0304] • AF Application Function

[0305] • AMF Access and Mobility Management Function

[0306] • AN Access Network

[0307] • AP Access Point

[0308] • ASIC Application Specific Integrated Circuit

[0309] • AUSF Authentication Server Function

[0310] • CN Core Network

[0311] • CPU Central Processing Unit

[0312] • C-RNTI Cell Radio Network Temporary Identifier

[0313] • DN Data Network

[0314] • DRX Discontinuous Reception

[0315] • DSP Digital Signal Processor

[0316] • eNB Enhanced or Evolved Node B

[0317] • EPC Evolved Packet Core

[0318] • EPS Evolved Packet System

[0319] • E-UTRA Evolved Universal Terrestrial Radio Access

[0320] • FPGA Field Programmable Gate Array

[0321] • gNB New Radio Base Station

[0322] • gNB-DU New Radio Base Station Distributed Unit

[0323] • GUAMI Global Unique AMF Identifier

[0324] • Global Unique Temporary Identifier (GUTI)

[0325] • Home Subscriber Server (HSS)

[0326] • International Mobile Equipment Identity (IMEI)

[0327] • International Mobile Subscriber Identity (IMSI)

[0328] • Internet Protocol (IP)

[0329] • Inactive Radio Network Temporary Identifier (I-RNTI)

[0330] • Long Term Evolution (LTE)

[0331] • Mobility Management Entity (MME)

[0332] • Machine Type Communication (MTC)

[0333] • Non-Access Stratum (NAS)

[0334] • Network Exposure Function (NEF)

[0335] • Network Function (NF)

[0336] • Next Generation Application Protocol (NGAP)

[0337] • Non-Public Network (NPN)

[0338] • New Radio (NR)

[0339] • Network Function Repository Function (NRF)

[0340] • Network Slice Selection Function (NSSF)

[0341] • Over The Top (OTT)

[0342] • Primary Cell (PCELL)

[0343] • Policy Control Function (PCF)

[0344] • Packet Data Network Gateway (P-GW)

[0345] • Quality of Service (QoS)

[0346] • Random Access Memory (RAM)

[0347] • Radio Access Network (RAN)

[0348] • Read Only Memory (ROM)

[0349] • Remote Radio Head (RRH)

[0350] •RTT Round Trip Time

[0351] •SCEF Service Capability Exposure Function

[0352] •SIM Subscriber Identity Module

[0353] •SMF Session Management Function

[0354] •S-TMSI Service Temporary Mobile Subscriber Identity

[0355] •SUPI Subscription Permanent Identifier

[0356] •UDM Unified Data Management

[0357] •UE User Equipment

[0358] •UPF User Plane Function

[0359] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method for indicating and operating multiple user equipment UEs performed by a wireless device (400), comprising: Determine the relationship between a first UE (402A) and a second UE (402B), where both the first UE (402A) and the second UE (402B) are included in the wireless device; Send an indication to a network node (404) to indicate the relationship, where the relationship includes an identifier defining the association between the first UE (402A) and the second UE (402B) in the wireless device (400); and Perform (504) one or more actions based on the indicated relationship, where the first UE is associated with a first cell, and the second UE is associated with a second cell, the second cell being different from the first cell, and where performing (504) one or more actions based on the indicated relationship includes, at the first UE (402A): Receive (1004) a paging message in the second cell of the second UE (402B); and Perform (1006) a random access procedure in response to receiving (1004) the paging message.

2. The method according to claim 1, further comprising detecting a trigger event for indicating the relationship between the first UE (402A) and the second UE (402B) before sending the indication to the network node (404).

3. The method according to claim 2, wherein, The triggering event includes one or more of the following: Receive a request from the network node (404); Activate a new subscriber identity module SIM in the wireless device (400); Establish a network connection by the wireless device (400); And Perform a network access procedure by the wireless device (400).

4. The method according to any one of claims 1 to 3, wherein, Sending the indication includes sending (702) UE capability information from the first UE (402A) to the network node (404) or from the second UE (402B) to the network node (404), the UE capability information including the indication that the first UE (402A) is associated with the second UE (402B).

5. The method according to any one of claims 1 to 3, wherein, Sending the indication includes sending (802) the indication during a radio resource control RRC connection establishment procedure.

6. The method according to any one of claims 1 to 3, wherein, Sending the indication includes protecting the indication by one or more of the following: Encrypting the indication; Sending the indication after enabling security with the network node (404); and Sending the indication in a message for enabling the security with the network node (404).

7. The method according to claim 1, wherein, The second cell of the second UE (402B) is the primary cell PCell of the second UE (402B).

8. The method according to any one of claims 1 to 3, wherein, Performing (504) one or more actions includes, at the second UE (402B): Receive (1104) an indication from the network node (404) to wake up the first UE (402A); and Trigger (1106) the first UE (402A) to wake up when receiving (1104) the indication to wake up the first UE (402A).

9. The method according to claim 8, wherein, Performing (504) one or more actions further includes performing (1108) one or more actions to wake up at the first UE (402A).

10. The method according to any one of claims 1 to 3, wherein, Performing (504) one or more actions includes, at the first UE (402A): Receive (1502) a handover indication from the network node (404) to hand over to a specific cell; and Apply the handover indication (1504) to both the first UE (402A) and the second UE (402B) such that both the first UE (402A) and the second UE (402B) hand over to the specific cell.

11. The method according to claim 10, further comprising receiving (1506) at the first UE (402A) a second indication indicating whether the handover indication is applicable to the second UE (402B).

12. The method according to any one of claims 1 to 3, wherein Performing (504) one or more actions includes performing (1600) a procedure by which the first UE (402A) and the second UE (402B) select the same cell to camp on.

13. The method according to claim 12, wherein Performing (1600) the procedure includes, at the first UE (402A): Obtaining (1602) information about the second UE (402B); and Performing (1604) cell selection based on the information about the second UE (402B).

14. The method according to any one of claims 1 to 3, wherein Performing (504) one or more actions includes, at the first UE (402A): Performing measurements at the first UE (402A); and Sharing the measurements with the second UE (402B).

15. A method for a cellular communication system (100) performed by a network node (404), comprising: Receiving an indication indicating the relationship between a first UE (402A) and a second UE (402B), both the first UE (402A) and the second UE (402B) being included in a wireless device (400), wherein the relationship includes an identifier defining an association between the first UE (402A) and the second UE (402B) in the wireless device; and Performing one or more actions based on the indicated relationship, wherein the relationship is determined by the wireless device, wherein the first UE is associated with a first cell and the second UE is associated with a second cell, the second cell being different from the first cell, and wherein performing one or more actions based on the indicated relationship includes: Transmitting a paging message to the first UE in the second cell of the second UE; and Performing a random access procedure with the first UE in response to transmitting the paging message.

16. The method according to claim 15, wherein Performing one or more actions includes providing the indication to another network node.

17. The method according to any one of claims 15 and 16, wherein Performing one or more actions includes sending (1104) an indication to the second UE (402B) to wake up the first UE (402A).

18. The method according to any one of claims 15 and 16, wherein Performing one or more actions includes: Indicating (1204) scheduling resources for the first UE (402A); and Indicating (1206) scheduling resources for the second UE (402B), wherein the scheduling resources for the first UE (402A) are different from the scheduling resources for the second UE (402B).

19. The method according to any one of claims 15 and 16, wherein Performing one or more actions includes avoiding (1302) scheduling the second UE (402B) when paging the first UE (402A).

20. The method according to any one of claims 15 and 16, wherein Performing one or more actions includes at least one of the following: Avoiding (1402) assigning scheduling resources to the first UE (402A) that conflict with the scheduling resources assigned to the second UE (402B); and Avoiding (1402) assigning scheduling resources to the second UE (402B) that conflict with the scheduling resources assigned to the first UE (402A).

21. The method according to any one of claims 15 and 16, wherein Performing one or more actions includes at least one of the following: Providing (1502) a handover indication to the first UE (402A) to hand over to a specific cell; and Providing (1506) a second indication indicating whether the handover indication applies to the second UE (402B).

22. The method according to any one of claims 15 and 16, wherein, Receiving an indication includes receiving the indication from the first UE (402A), the second UE (402B), or a combination thereof.

23. The method according to claim 22, wherein, Receiving an indication includes one or more of the following: Receiving (702) UE capability information from the first UE (402A), the UE capability information including the indication associated with the second UE (402B); Receiving (802) the indication during a radio resource control (RRC) connection establishment procedure; and Receiving (902) the indication in a message for enabling security with the network node.

24. The method according to claim 23, wherein, The indication includes an identifier of the second UE (402B).

25. The method according to claim 24, wherein, The identifier of the second UE (402B) includes one of the following: Cell Radio Network Temporary Identifier (C-RNTI); Service Temporary Mobile Subscriber Identity (S-TMSI); Inactive Radio Network Temporary Identifier (I-RNTI); Recovery identifier; Globally Unique Temporary Identifier (GUTI); And A new identifier for indicating an association between the second UE and other UEs.

26. The method according to claim 22, wherein, Receiving an indication includes receiving from the second UE (402B) the indication indicating the relationship between the first UE (402A) and the second UE (402B), wherein the indication includes an identifier of the first UE (402A).

27. The method according to claim 26, wherein, The identifier of the first UE (402A) includes one of the following: Cell Radio Network Temporary Identifier (C-RNTI); Service Temporary Mobile Subscriber Identity (S-TMSI); Inactive Radio Network Temporary Identifier (I-RNTI); Recovery identifier; Globally Unique Temporary Identifier (GUTI); And A new identifier for indicating an association between the first UE and other UEs.

28. The method according to any one of claims 15 and 16, wherein, Receiving an indication includes receiving from another network node the indication indicating the relationship between the first UE (402A) and the second UE (402B).

29. A wireless device (2000), comprising: A processing circuit (2002), the processing circuit (2002) being configured to perform the steps performed by the wireless device in any one of claims 1 to 14; And A power circuit configured to power the wireless device (400).

30. A network node (1700), comprising a control system (1702), the control system (1702) being configured to perform the steps performed by the network node (404) in any one of claims 15 to 28.

31. A method for enabling a wireless device (400) to indicate and operate multiple user equipment UEs, performed by a core network node, including providing (606) an indication associated with a first UE (402A) and a second UE (402B) in the wireless device (400) to a network node (404), where the relationship between the first UE and the second UE includes an identifier defining the association between the first UE (402A) and the second UE (402B) in the wireless device, and the relationship is determined by the wireless device, where the first UE is associated with a first cell, and the second UE is associated with a second cell, the second cell being different from the first cell, and where, The method further includes enabling the wireless device to perform one or more actions based on the indicated relationship, at the first UE (402A): Receiving a paging message in the second cell of the second UE (402B); and Performing a random access procedure in response to receiving the paging message.

32. The method according to claim 31, further including obtaining (604) information indicating the association between the first UE (402A) and the second UE (402B) from at least one of the following: Unified Data Management UDM and Access and Mobility Management Function AMF.

Images