Communication of user terminals with multiple subscription identities

Abstract

The present invention provides an apparatus and method in a communication system. When one subscription identity of a user equipment is active, the user equipment maintains a primary capability to be used (300), and when more than one subscription identity of the user equipment is active, the user equipment maintains a secondary capability to be used, and transmits (302) to a radio access network node to which the user equipment is connected an indication of which capability is selected from the primary or secondary capabilities to be used based on the radio resource connection state of one or more subscription identities of the user equipment.

Description

Technical Field

[0001] The exemplary and non-limiting embodiments of the present invention generally relate to wireless communication systems. The exemplary and non-limiting embodiments of the present invention particularly relate to apparatus and methods in wireless communication networks. Background Art

[0002] Wireless communication systems are constantly evolving. One aspect that is being developed is user terminals with more than one subscription identity. There may be a user who needs to use more than one subscription in the same terminal. For example, one subscription may be for home and another for work. Communication systems should be prepared to handle these situations in an efficient manner.

[0003] A wireless communication system typically includes wireless user terminals, a radio access network, and a core network. These components of the system exchange messages to establish signaling connections between them to facilitate data transmission from one communication point to another. The exchange of signaling messages between the different components of the system should be as reliable and efficient as possible in terms of the use of communication system resources. Summary of the invention

[0004] A simplified summary of the present invention is given below to provide a basic understanding of some aspects of the present invention. This summary is not an extensive overview of the present invention. It is not intended to identify the key / critical elements of the present invention or to describe the scope of the present invention. Its sole purpose is to present some concepts of the present invention in a simplified form as a prelude to a more detailed description presented later.

[0005] According to one aspect of the present invention, the apparatus of claims 1, 8 and 13 is provided.

[0006] According to one aspect of the present invention, the method of claims 15, 16 and 17 is provided.

[0007] According to an aspect of the invention, a computer program comprising instructions of claims 18, 19 and 20 is provided.

[0008] One or more examples of each embodiment are described in more detail in the following drawings and descriptions. Other features will be apparent from the description and drawings, as well as from the claims. The embodiments and / or examples and features described in this specification that do not fall within the scope of the independent claims, if any, will be interpreted as examples useful for understanding the various embodiments of the invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The following describes various embodiments of the present invention by way of example only, with reference to the accompanying drawings, in which

[0010] Figure 1 and 2 An example of a simplified system architecture for a communication system is shown;

[0011] Figure 3 , 4A 4B are flow charts illustrating various embodiments;

[0012] Figure 5 and 6 is a signaling diagram describing various embodiments;

[0013] Figure 7 , 8 and 9 are flow charts describing various embodiments;

[0014] Fig.10 , 11 12 show simplified examples of apparatus to which some embodiments of the present invention may be applied. DETAILED DESCRIPTION

[0015] The following embodiments are merely examples. Although the specification may refer to "one", "an" or "some" embodiments in multiple locations, this does not necessarily mean that each such reference refers to the same embodiment, or that the feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments. In addition, the words "comprise" and "comprising" should be understood as not limiting the described embodiments to consist only of those features that have been mentioned, and such embodiments may also include features, structures, units, modules, etc. that are not specifically mentioned.

[0016] Some embodiments of the present invention may be applied to user terminals, communication devices, base stations, eNodeBs, gNodeBs, distributed implementations of base stations, network elements of communication systems, corresponding components and / or any communication system or any combination of different communication systems supporting the required functionality.

[0017] The protocols, communication systems, servers and user equipment used, especially in wireless communications, are evolving rapidly. Such developments may require additional changes to the embodiments. Therefore, all words and expressions should be interpreted broadly and they are intended to illustrate rather than limit the embodiments.

[0018] In the following, different exemplary embodiments will be described using a radio access architecture based on advanced long term evolution (LTE-advanced, LTE-a) or new air interface (NR, 5G) as an example of an access architecture to which the embodiments may be applied, however, the embodiments are not limited to such an architecture. By appropriately adjusting the parameters and procedures, these embodiments may also be applied to other types of communication networks with appropriate devices. Some examples of other options for suitable systems are Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Wireless Local Area Network (WLAN or WiFi), Worldwide Interoperability for Microwave Access (WiMAX), Personal Communications Service (PCS), Wideband Code Division Multiple Access (WCDMA), systems using Ultra-Wideband (UWB) technology, sensor networks, Mobile Ad Hoc Networks (MANETs), and Internet Protocol Multimedia Subsystem (IMS), or any combination thereof.

[0019] Figure 1 An example of a simplified system architecture is depicted, showing only some elements and functional entities, which are all logical units and whose implementation may differ from what is shown. Figure 1 The connections shown in are logical connections; the actual physical connections may be different. It is obvious to those skilled in the art that the system typically also includes Figure 1 Other functions and structures than those shown.

[0020] However, the embodiments are not limited to the systems given as examples, but a person skilled in the art may apply the solution to other communication systems having the necessary characteristics.

[0021] Figure 1 The example of FIG. 1 shows a portion of an exemplary radio access network.

[0022] Figure 1 Devices 100 and 102 are shown. Devices 100 and 102 may be, for example, user equipment or user terminals. Devices 100 and 102 are configured to be wirelessly connected to node 104 on one or more communication channels. Node 104 is also connected to core network 106. In one example, node 104 may be an access node, such as an (e / g)NodeB serving a device in a cell. In one example, node 104 may be a non-3GPP access node. The physical link from the device to the (e / g)NodeB is referred to as an uplink or reverse link, and the physical link from the (e / g)NodeB to the device is referred to as a downlink or forward link. It should be understood that (e / g)NodeB or their functions may be implemented using entities such as any node, host, server or access point suitable for such use.

[0023] The communication system typically includes more than one (e / g)NodeB, in which case the (e / g's)NodeBs may also be configured to communicate with each other via wired or wireless links designed for this purpose. These links may be used for signaling purposes. (e / g)NodeB is a computing device configured to control the radio resources of the communication system to which it is coupled. NodeB may also be referred to as a base station, an access point, or any other type of interface device, including a relay station capable of operating in a wireless environment. (e / g)NodeB includes or is coupled to a transceiver. From the transceiver of the (e / g)NodeB, a connection is provided to an antenna unit that establishes a bidirectional radio link to the device. The antenna unit may include multiple antennas or antenna elements. (e / g)NodeB is further connected to a core network 106 (CN or next generation core NGC).

[0024] The device (also referred to as a subscriber unit, user device, user equipment (UE), user terminal, terminal device, etc.) shows a type of device to which resources on the air interface are allocated and assigned, and therefore any features of the device described herein can be implemented with a corresponding device such as a relay node. An example of such a relay node is a layer 3 relay (self-backhaul relay) towards a base station.

[0025] The device generally refers to a device (part of a mobile or non-mobile computing device) including a wireless mobile communication device that operates with or without a Universal Subscriber Identity Module (USIM), including but not limited to the following types of devices: mobile workstations (mobile phones), smart phones, personal digital assistants (PDAs), mobile phones, devices using wireless modems (alarm or measurement devices, etc.), laptops and / or touch screen computers, tablets, game consoles, laptops, and multimedia devices. It should be understood that the device can also be an almost exclusive uplink-only device, an example of which is a camera or video camera that loads images or video clips to a network. The device can also be a device with the ability to operate in an Internet of Things (IoT) network, which is a scenario in which objects are provided with the ability to transmit data on a network without the need for human-to-human or human-to-computer interaction, such as for smart grids and connected vehicles. The device can also use the cloud. In some applications, the device may include a user-portable device with a radio component (such as a watch, headphones, or glasses), and the calculation is performed in the cloud. The device (or in some embodiments, a layer 3 relay node) is configured to perform one or more user device functions.

[0026] Various techniques described herein may also be applied to Cyber-Physical Systems (CPS) (systems of cooperating computing elements that control physical entities). CPS enables the implementation and development of a large number of interconnected information and communication technologies, ICTs, devices (sensors, actuators, processors, microcontrollers, etc.) embedded in physical objects at different locations. Mobile Cyber-Physical Systems are a subcategory of Cyber-Physical Systems where the physical systems involved are inherently mobile. Examples of mobile physical systems include mobile robots and electronic devices transported by humans or animals.

[0027] Furthermore, although the apparatus has been described as a single entity, different units, processors and / or memory units may be implemented ( Figure 1 Not all are shown in the table).

[0028] 5G supports the use of multiple-input multiple-output (MIMO) antennas, more base stations or nodes than LTE (the so-called small cell concept), including macro sites operating in cooperation with smaller sites, and the use of multiple radio technologies depending on service needs, usage and / or available spectrum. 5G mobile communications support a wide range of use cases and related applications, including video streaming, augmented reality, different ways of sharing data and various forms of machine type applications (such as (massive) machine type communications (mMTC), including vehicle safety, different sensors and real-time control. 5G is expected to have multiple radio interfaces, such as below 6 GHz or above 24 GHz, cmWave and mmWave, and can also be integrated with existing traditional radio access technologies such as LTE. At least in the early stages, the integration with LTE can be implemented as a system in which macro coverage is provided by LTE and 5G radio interface access comes from small cells through aggregation to LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6 GHz - cmWave, cmWave and mmWave at 6 or above 24 GHz). One of the concepts considered for use in 5G networks is network slicing, in which multiple independent dedicated virtual subnetworks (network instances) can be created within the same infrastructure to run services with different requirements for latency, reliability, throughput and mobility.

[0029] The current architecture in LTE networks is completely distributed in the air interface (radio) and completely centralized in the core network. Low-latency applications and services in 5G require content to be close to the air interface, which leads to local bursting and multi-access edge computing (MEC). 5G enables analysis and knowledge generation to be performed at the source of data. This approach requires the use of resources that may not be continuously connected to the network, such as laptops, smartphones, tablets, and sensors. MEC provides a distributed computing environment for application and service hosting. It also has the ability to store and process content close to the cellular subscriber to speed up response time. Edge computing covers a wide range of technologies such as wireless sensor networks, mobile data collection, mobile signature analysis, collaborative distributed peer-to-peer self-organizing networks and processing that can also be divided into local cloud / fog computing and grid / grid computing, dew computing, mobile edge computing, cloudlets, distributed data storage and retrieval, autonomous self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and / or latency critical), critical communications (autonomous vehicles, traffic safety, real-time analysis, time-critical control, medical applications).

[0030] The communication system can also communicate with other networks 112, such as a public switched telephone network, or a VoIP network, or the Internet, or a private network, or utilize services provided by them. The communication network can also support the use of cloud services, for example, at least part of the core network operations can be performed as a cloud service (this is in Figure 1 114). The communication system may also include a central control entity or the like, which provides facilities for networks of different operators to cooperate, for example in spectrum sharing.

[0031] Edge cloud technology can be introduced into the radio access network (RAN) by utilizing network function virtualization (NFV) and software defined networking (SDN). Using edge cloud technology can mean performing access node operations at least partially in a server, host or node operably coupled to a remote radio head or a base station including radio components. Node operations may also be distributed among multiple servers, nodes or hosts. The application of cloud RAN architecture enables RAN real-time functions to be performed at or near the remote antenna site (in a distributed unit, DU 108), and non-real-time functions to be performed in a centralized manner (in a centralized unit, CU 110).

[0032] It should also be understood that the work distribution between core network operations and base station operations may be different from that of LTE, or even non-existent. Some other technological advances that can be used are big data and all-IP, which may change the way networks are built and managed. 5G (or new radio, NR) networks are designed to support a multi-layer structure, where MEC servers can be placed between the core and base stations or Node Bs (gNBs). It should be understood that MEC can also be applied to 4G networks.

[0033] 5G can also make use of satellite communications, for example by providing backhaul, to enhance or supplement the coverage of 5G services. Possible use cases are to provide service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or passengers on vehicles, or to ensure service availability for critical communications and future rail / maritime / aeronautical communications. Satellite communications can make use of geostationary orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems where hundreds of (nano) satellites are deployed). Each satellite in a mega-constellation can cover several satellite-enabled network entities creating terrestrial cells. Terrestrial cells can be created by ground relay nodes or by gNBs located on the ground or in satellites.

[0034] It is obvious to a person skilled in the art that the depicted system is only an example of a part of a radio access system, and in practice, the system may include multiple (e / g)NodeBs, which may access multiple radio cells, and the system may also include other devices, such as physical layer relay nodes or other network elements. At least one of the (e / g)nodeBs may be a home (e / g)nodeB. In addition, in the geographical area of ​​the radio communication system, a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided. A radio cell may be a macro cell (or umbrella cell), which is a large cell, typically having a diameter of up to tens of kilometers; or a smaller cell, such as a micro, femto or pico cell. Figure 1 The (e / g)NodeB of a cell can provide any type of these cells. A cellular radio system can be implemented as a multi-layer network including several cells. Typically, in a multi-layer network, one access node provides one or more cells, and therefore multiple (e / g)NodeBs are required to provide such a network structure.

[0035] In order to meet the needs of improving the deployment and performance of communication systems, the concept of "plug-and-play" (e / g) NodeB has been introduced. Generally, a network capable of using "plug-and-play" (e / g) NodeB includes, in addition to a Home (e / g) NodeB (H(e / g) NodeB), a Home NodeB Gateway or HNB-GW ( Figure 1The HNB Gateway (HNB-GW), which is usually installed in the operator's network, aggregates traffic from a large number of HNBs back to the core network.

[0036] Figure 2 An example of a communication system based on 5G network components is shown. A user terminal or user equipment 200 communicates with a data network 112 via a 5G network 202. The user terminal 200 is connected to a radio access network RAN ​​node, such as an (e / g)NodeB 206, which provides the user terminal with a connection to the network 112 via one or more user plane functions 208. The user terminal 200 is also connected to a core access and mobility management function AMF 210, which is the control plane core connector for the (radio) access network and can be seen from this perspective as a 5G version of the mobility management entity MME in LTE. The 5G network also includes a session management function SMF 212, which is responsible for subscriber sessions, such as session establishment, modification and release, and a policy control function 214, which is configured to manage network behavior by providing policy rules to control plane functions.

[0037] Each user terminal (or user equipment, UE) hardware has a unique identifier. The identifier can be expressed as a permanent equipment identifier PEI or an international mobile equipment identifier IMEI.

[0038] A user device wishing to utilize the services of a wireless communication system such as a cellular network needs to have a subscription from an operator of the communication system. Typically, a subscription is bound to a physical Universal Subscriber Identity Module USIM card and the subscription can be identified by a unique subscription permanent identifier SUPI, also denoted International Mobile Subscriber Identity IMSI. SUPI consists of a Mobile Country Code (MCC), a Mobile Network Code (MNC) and a Mobile Subscription Identification Number (MSIN).

[0039] There are also so-called embedded USIMs or electronic SIMs, eSIMs available. An eSIM is a digital USIM that allows the owner to activate a subscription to a communications system without having to use a physical USIM card.

[0040] In most cases, a user device has only one user identity stored in a USIM card inserted into the terminal. However, there are many user devices on the market that have more than one slot for a USIM card or eSIM support and are able to support multiple subscriber identities. These user devices may be denoted as multi-USIM (MUSIM) devices.

[0041] MUSIM user equipment registers with the network using one or more subscription identities stored in the corresponding USIM. The subscription identity is associated with each UE radio protocol stack instance which may be in any of the RRC states RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED.

[0042] MUSIM user equipment is generally divided into two main types according to the simultaneous RRC_states supported on the USIM.

[0043] First, a Dual SIM Dual Standby (DSDS) or Multi-USIM Multi-Standby (MUMS) device has two or more independent subscriber IDs (USIMs) registered and can be in RRC_IDLE mode on all USIMs. However, it can only be in RRC_CONNECTED mode with a single USIM at a given time.

[0044] Second, Dual SIM Dual Active (DSDA) or Multiple USIM Multiple Active (MUMA) MUSIM devices are registered with two or more independent subscriber IDs (USIMs) and can be in RRC_IDLE mode on all USIMs. In addition, the device can keep RRC_CONNECTED mode active on all USIMs.

[0045] Furthermore, the behavior of a MUSIM device with respect to handling multiple USIMs simultaneously may depend on the capabilities of the UE. Three types may be defined as follows:

[0046] Type 1: Single Rx / Single Tx: The UE can only receive traffic from one network and / or transmit traffic to one network at a time.

[0047] Type 2: Dual Rx / Single Tx: The UE is able to receive traffic from two networks simultaneously, but can only transmit to one network at a time.

[0048] Type 3: Dual Rx / Dual Tx: The UE is able to receive and / or transmit to and / or from two networks simultaneously.

[0049] A DSDA MUSIM UE may be in a situation where it is being provided data services from one USIM (USIM-A) and voice services from the other USIM (USIM-B) at the same time.

[0050] In the following, we refer to the UE radio protocol instance associated with USIM-A as UE A, and the UE radio protocol instance of USIM-B as UE B.

[0051] When UE-A establishes an RRC connection, the network may configure different features on the network, such as dual connectivity, carrier aggregation, MIMO, etc., based on the UE capabilities already available to PLMN-A (the public land mobile network to which UE-A is connected).

[0052] When UE-B also moves to connected mode, UE-A needs to inform its network of the change and also needs to reduce the capabilities of UE-A's connected mode operation in PLMN-A. This requires additional signaling exchanges to carry out the reduced capabilities operation. In addition, the scope of the reduced capabilities needs to be controlled and coordinated. When resuming the situation of a single USIM activity, it is also necessary to switch back to this functionality.

[0053] In the following, a reliable signaling mechanism between UE, RAN node and network is proposed.

[0054] In one embodiment, a MUSIM UE supporting DSDA operation or supporting reduced capabilities for efficient MUSIM operation may indicate to the network that it has multiple sets of capabilities: a primary capability that includes all of its radio capabilities and one or more secondary capabilities that are subsets / restrictions of the primary capabilities. In one embodiment, the primary capabilities are used when one subscription identity is active, and the one or more secondary capabilities are used when more than one subscription identity is active.

[0055] In one embodiment, the UE informs the RAN node which capability to use.

[0056] In general, the attributes of the capabilities that may be changed between primary and secondary capabilities may include, for example, various attributes related to the user equipment's processor and memory usage, radio frequency capabilities, and the user equipment's operation at the physical and protocol layers.

[0057] In one embodiment, the attributes of the capabilities may include protocol specific capabilities (capabilities based on Media Access Control / Radio Link Control / Packet Data Convergence Protocol / Service Data Adaptation Protocol). This is because processing power and memory capabilities may also be shared between the two subscriptions. If only one subscription is connected, the UE may be allowed to use the full functionality, while a subset must be abandoned when the other subscription moves to connected. Examples of such parameters may be the maximum supported data rate, the total layer 2 buffer size and the maxNumberROHCContextSessions-parameter.

[0058] In one embodiment, the attributes of the capability may include physical layer capabilities (e.g., receiver, multiple input multiple output (MIMO) and transmit mode (TM), capabilities, feedback, codebook). When more than one RRC connection is active, the UE may not support higher TM or MIMO or other PHY capabilities. If there is only a single RRC connection, the UE may support additional layers of MIMO or transmit mode. As an example, the parameters in question may include, for example, maxNumberRxBeam (maximum number of receive beams), maxNumberRxTxBeamSwitchDL, maxNumberCSI-RS-SSB-BFR, groupBeam-Reporting, channelBW-90mhz, maxNumberMIMO-LayersPDSCH, supportedBandwidthDL (supported bandwidthDL), supportedModulationOrderDL (supported modulation orderDL), supportedSubCarrierSpacingDL (supported subcarrier spacingDL).

[0059] In one embodiment, the attributes of the capability may include radio frequency (RF) capabilities (transmit band combinations and capabilities per band combination). When more than one connection is active, all RRC connections require partial RF. Supported bands, carrier aggregation, or dual connectivity features, such as supported band combinations, will change depending on how many subscription identities have RRC connections. Examples include bandNR, ca-BandwidthClassDL NR, ca-BandwidthClassUL NR, ca-ParametersNR, mrdc-Parameter, supportedBandwidthCombinationSet, channelBWs DL, channelBW UL, etc.

[0060] In one embodiment, the attributes of the capability may include measurement-specific capabilities.A single connection may not require measurement gaps, while multiple connections may require measurement gaps.

[0061] In one embodiment, the attributes of the capability may further include inter-RAT capabilities (e.g., frequency bands supported between RATs). This is similar to RF capabilities and may change based on the number of connections. Examples include bandEUTRA, ca-ParametersEUTRA, ca-BandwidthClassDL EUTRA, and ca-BandwidthClassUL-EUTRA, etc. For example, the current RAT is considered NR and other RATs are considered EUTRA.

[0062] In one embodiment, the attributes of the capability may include feature-specific capabilities. When there is more than one RRC connection active, the UE may not support all features. Examples of specific functionality may include:

[0063] 1. Multimedia Broadcast Multicast Service (MBMS),

[0064] 2. UE receiver characteristics (Minimum Mean Square Error (MMSE) with Interference Rejection Combining (IRC) receiver, MMSE-IRC downlink control channel interference mitigation receiver for UEs with 4 receiver antenna ports, Single-User MIMO Interference Mitigation Advanced Receiver for UEs with 2 receiver antenna ports, Single-User MIMO Interference Mitigation Advanced Receiver for UEs with 4 receiver antenna ports) and

[0065] 3. Sidelink features (sidelink relay UE operation, sidelink remote UE operation, sidelink discovery gap)

[0066] In addition to the radio capabilities, some non-access stratum (NAS) attributes may also change when multiple subscriptions establish an RRC connection. These may include supported codecs, device attributes, and some additional auxiliary information related to the new connection in the other USIM. For example, if one USIM has a voice call, the new voice call may not be accepted. This information may be sent from the UE as a NAS protocol data unit (PDU) and the RAN node may relay it directly to the core network.

[0067] Figure 3 The flowchart of shows an embodiment. The flowchart shows an example of the operation of the device. In one embodiment, the device can be a part of the MUSIM user equipment 200, a MUIM user equipment, or any other device capable of performing the following steps.

[0068] In one embodiment, the user equipment maintains or stores multiple subscription identities in the user equipment. For example, the user equipment may be installed with multiple USIMs.

[0069] In step 300, the user equipment is configured to maintain a primary capability to be used when one subscription identity is active, and to maintain a secondary capability to be used when more than one subscription identity is active.

[0070] In step 302, the user equipment is configured to transmit an indication to a radio access network (RAN) node to which the user equipment is connected as to which capability selected from primary or secondary capabilities to use based on a radio resource connection state of one or more subscription identities.

[0071] In one embodiment, the user equipment is configured to indicate to the network that the user equipment is capable of communicating using more than one capability, receive minimum requirements for secondary capabilities from the network, and create secondary capabilities based on the minimum requirements received from the network.

[0072] In one embodiment, the user equipment is configured to receive at least one radio resource control reconfiguration message from the RAN node depending on the capabilities to be used.

[0073] Figure 4A The flowchart of illustrates an embodiment. The flowchart illustrates an example of the operation of an apparatus. In one embodiment, the apparatus may be a RAN node 206, a part of a RAN node, or any other apparatus capable of performing the following steps.

[0074] In step 400, the apparatus is configured to receive an indication of a primary or secondary capability to be used from a user equipment based on a radio resource connection state of one or more subscription identities of the user equipment.

[0075] In step 402, the apparatus is configured to transmit a radio resource control reconfiguration message to the user equipment according to the capabilities to be used.

[0076] In one embodiment, the apparatus is configured to receive from a user equipment an indication of a change of a capability to be used selected from a primary or secondary capability, based on the capability, request data about the capability to be used from a core network, and prepare and transmit a radio resource control reconfiguration message to the user equipment according to the capability to be used.

[0077] Figure 4B The flowchart of shows an embodiment. The flowchart shows an example of the operation of the device. In one embodiment, the device can be a core access and mobility management function AMF 210, or a part of AMF or any other device capable of performing the following steps.

[0078] In step 410, the apparatus is configured to receive an indication from a user equipment that the user equipment is capable of communicating using more than one capability.

[0079] In step 412, the apparatus is configured to transmit a minimum requirement for secondary capabilities to the user equipment.

[0080] In one embodiment, the apparatus receives information about primary and secondary capabilities of the user equipment from a radio access network node and stores the information.

[0081] In one embodiment, the apparatus transmits information about primary and / or secondary capabilities related to handover or context setup of the user equipment to a RAN node.

[0082] Figure 5 is a signaling diagram illustrating an embodiment. The figure shows signaling between UE 200, RAN node gNB 206 and the network's AMF 210. The flow chart shows an example of establishing a secondary function. In this example, the user equipment includes two USIMs, USIM-A and USIM-B.

[0083] UE 200 has performed RRC setup 500 with a RAN node. The UE transmits a NAS message 502 to the RAN node indicating that it has multiple capabilities. In this example, the indication is in an RRC setup complete message, which includes a NAS registration request with MUSIM assistance information, field Secondarycapabilitypresent = TRUE.

[0084] The RAN node transmits an initial UE registration request 504 to the AMF.

[0085] In response to the request, based on the USIM-a subscription requirements, the AMF may decide whether the UE may be allowed to have a reduced set of capabilities and how much of a reduction in capabilities is acceptable 506. In one embodiment, the AMF derives a minimum required set of secondary capabilities (minimum capabilities) for the UE.

[0086] In one embodiment, the AMF is configured to send a message 508 to the UE notifying the minimum set of requirements. In one embodiment, the message is a NAS message, such as a configuration update command including a minimum capability field. The UE is configured to create a secondary capability 510 based on the message sent by the AMF and transmit an indication 512 to the AMF that the secondary capability has been created. In one embodiment, the UE transmits a NAS configuration update complete message.

[0087] The AMF updates the UE's secondary-capable RAN nodes 514, 516. In one embodiment, for example, the update may be performed using a NGAP message such as an NGAP Initial Context Setup Request.

[0088] When retrieving UE capabilities 518, the RAN node may request the UE to report secondary capabilities 520 via the Boolean IEreportSecondaryCapabilities field in the RRC UECapabilityQuery message. The UE may respond 522 by transmitting a UECapabilityInformation message including primary and secondary capabilities to the RAN node, and indicating its current capabilities selected from either primary or secondary capabilities.

[0089] The RAN node may be configured to reconfigure the UE 524, 526 based on the received current capabilities. In one embodiment, the RAN node will also transmit the received capabilities 528 including the secondary capabilities to the AMF.

[0090] When a handover to another RAN node is to be performed, the AMF may be configured to provide the received secondary capabilities to the new RAN node. This means that the exchange of secondary capabilities only needs to occur once during connection to the network. In one embodiment, the RAN node may also transmit to the new RAN node the secondary capabilities of the handover UE in an Xn HO Request message during handover and an XnInformation Transfer message during RRC recovery (inactive to connected transition).

[0091] Figure 6 is a signaling diagram illustrating an embodiment. The figure shows signaling between a user equipment, a UE, a RAN node and an AMF of the network. The flow chart shows an example of signaling during RRC setup and capability switching between primary and secondary capabilities. Also in this example, the user equipment includes two USIMs, USIM-A and USIM-B.

[0092] The figure shows how a MUSIM DSDA user equipment signals secondary capabilities during a transition from idle to connected and during a capability change depending on another USIM's transition from idle to connected state (or from idle / inactive to connected state).

[0093] In this example, the user equipment is a MUSIM device that supports different capability sets of DSDA. The UE 200 has performed an RRC setup 600 with a RAN node. In this example, the UE may indicate capabilities using an enumeration variable currentCapability during the RRC setup procedure. In the absence of an explicit indication, the RAN node is configured to interpret that the UE has primary capabilities. Figure 6 In the example embodiment of , the UE transmits an enumeration variable “currentCapability=secondary” to the RAN node in the RRC Setup Complete message 602 .

[0094] In response to receiving "currentCapability=secondary" from the UE, the RAN node indicates to the AMF in the NGAP Initial UE message that the secondary capability is available / active at the UE 604. The RAN node may receive the secondary capabilities 606, 608 from the AMF via the NGAP Initial Context Setup Request. In one embodiment, the AMF may include both primary and secondary capabilities in the NGAP Initial Context Setup Request.

[0095] The RAN node will reconfigure the UE based on the current capabilities 610, 612. In one embodiment, the RAN node may send two configurations corresponding to each of the primary and secondary capabilities and indicate to the UE which capability to use if the current capability is the secondary capability.

[0096] In case the capabilities required by the UE change, for example from secondary to primary due to the USIM-B moving from connected state to idle state (or from connected to idle / inactive state) 614, the UE is configured to transmit an RRC assistance information message 616 which indicates to the RAN node that the primary capabilities are activated.

[0097] If the RAN node in this case does not yet have primary capabilities, the RAN node is configured to request primary capabilities 618 from the AMF, for example using an NGAP message NGAP UE Capability Request 618, and receive a response prepared 620 by the AMF in an NGAP UE Capability Response 622 with primary capabilities.

[0098] The RAN node may then reconfigure the UE 624, 626 to take advantage of the increased capabilities.

[0099] In case the capabilities required by the UE change, for example from primary capabilities to secondary capabilities due to the USIM-B moving from idle state back to connected state (or from idle / inactive state back to connected state) 628, the UE is configured to again transmit RRC assistance information 630 to the RAN node indicating that the secondary capabilities are activated.

[0100] In this case, the RAN node may have the secondary capability in memory and may reconfigure the UE to use the secondary capability 632, 634. This naturally also applies to the earlier change 614 if the RAN node has the primary capability in memory.

[0101] Figure 7 The flowchart of illustrates an embodiment. The flowchart illustrates an example of the operation of the device. In one embodiment, the device can be a part of the MUSIM user equipment 200, a MUIM user equipment, or any other device capable of performing the following steps. The flowchart illustrates an example of a user equipment notifying the network of its secondary capabilities.

[0102] In step 700, the user equipment is configured to indicate the presence of secondary capabilities to the network, for example to the AMF of the network. In one embodiment, the UE transmits a registration request or any other NAS or RRC message including information about the secondary capabilities.

[0103] In step 702, the user equipment is configured to receive a NAS message from the AMF, such as a configuration update message, and auxiliary information MinimumCapability on how to create a secondary capability.

[0104] In step 704, the user equipment is configured to create a secondary capability that complies with the MinimumCapability, and then confirms the configuration update command 706 to the AMF with a NAS configuration update complete message.

[0105] In step 708, the user equipment is configured to receive an RRC UE capability query message requesting reporting of secondary capabilities from the RAN node.

[0106] In response to the query, the user equipment is configured to transmit the secondary capability information in a RRC UE CAPABILITY INFORMATION message in step 710. The RAN node may then reconfigure the user equipment using a radio configuration corresponding to the reported secondary capabilities.

[0107] Figure 8 The flowchart of the embodiment shows an embodiment. The flowchart shows an example of the operation of the device. In one embodiment, the device can be a RAN node 206, a part of a RAN node, or any other device capable of performing the following steps. The flowchart illustrates an example of the operation of the RAN node for handling secondary capabilities of a user equipment.

[0108] In step 800, the RAN node receives an RRC Setup Complete message from the user equipment, which tells the RAN node that the current capability of the user equipment is a secondary capability during the transition from the idle state to the connected state (or from the idle / inactive state to the connected state).

[0109] In step 802, the RAN node transmits a message to the AMF, requesting the AMF to send a Secondary Capability: Initial Context Setup Request message in NGAP.

[0110] In step 804, the RAN node receives an NGAP: Initial Context Setup Request message.

[0111] In one embodiment, when the secondary capability is already available at the RAN node, steps 802 and 804 need not be performed.

[0112] In step 806, the RAN node reconfigures the user equipment based on the received secondary capabilities.

[0113] In step 808, the RAN node receives an RRC message from the user equipment, such as an RRC Assistance Information message, indicating that a capability in the user equipment changes to a primary capability, e.g. due to the USIM-B moving from a connected state to an idle state (or from a connected state to an idle / inactive state).

[0114] In step 810, the RAN node is configured to request primary capabilities using an NGAP UE Capability Request message and receive the capabilities in an NGAP UE Capability Response message.

[0115] In one embodiment, in case the primary capabilities are already available at the RAN node, step 810 does not need to be performed.

[0116] In step 812, the RAN node is then configured to reconfigure the user equipment based on the primary capabilities.

[0117] Fig. 9 The flowchart of the embodiment shows an embodiment. The flowchart shows an example of the operation of the device. In one embodiment, the device can be a core access and mobility management function AMF of the network, a part of the AMF or any other device capable of performing the following steps. The flowchart illustrates an example of the operation of the AMF for handling secondary capabilities of the user equipment.

[0118] In step 900, the AMF receives a message indicating that the user equipment has secondary capabilities. In one embodiment, the AMF receives MUSIM assistance information in a NAS message such as a registration request message.

[0119] In step 902, the AMF transmits a message, such as a NAS UE Configuration Update Command message, including a MinimumCapability field for creating secondary capabilities.

[0120] In step 904, the AMF receives a message such as a UE configuration update complete message from the user equipment, indicating that the secondary capability has been created.

[0121] In step 906, the AMF transmits information about the presence of secondary capabilities to the RAN node.

[0122] In step 908, the AMF receives and stores information about the secondary capabilities from the RAN node.

[0123] In step 910, the AMF transmits information about the secondary capabilities of the user equipment to the new RAN node in association with the handover of the user equipment to the new RAN node, or during a transition from an idle to a connected state (or from an idle / inactive to a connected state).

[0124] In one embodiment, for a user equipment, two types of transitions may be considered to change the capabilities to be used (selected from primary or secondary capabilities): a first type of transition from / to (RRC_IDLE or RRC_INACTIVE) to / from RRC_CONNECTED and a second type of transition from / to RRC_IDLE to / from RRC_CONNECTED.

[0125] With the first type of transition, whenever the UE leaves or enters the RRC_CONNECTED state for one of the subscriptions, including when the UE moves to the RRC_INACTIVE state, the change in the capabilities used is notified.

[0126] With the second type of transition, whenever the UE leaves or enters the RRC_IDLE state for one of the subscriptions, the change in the capabilities used is notified, but if the UE switches between the RRC_INACTIVE and RRC_CONNECTED states, the change is not notified.

[0127] In one embodiment, using the first type of transition makes the most efficient use of UE capabilities, which means using full primary capabilities when another subscription is in RRC_INACTIVE state. However, since switching between RRC_CONNECTED and RRC_INACTIVE states will result in switching of the capabilities used, there is more RRC signaling overhead.

[0128] In one embodiment, using the second type of transition will reduce the number of capability switches and corresponding RRC reconfigurations, but at the expense of using reduced secondary capabilities with an RRC_INACTIVE state, even though the full primary capabilities could have been used.

[0129] In one embodiment, the AMF may indicate which type of conversion (first type or second type) the UE will use. In one embodiment, for example, when sending the minimum requirements of the secondary capability to the UE in step 902 above, the AMF may use a Boolean indicator together.

[0130] In one embodiment, the RAN node may also indicate which type of transition to use during the RRC establishment or RRC reconfiguration procedure, for example based on its current RRC signaling load.

[0131] Fig.10An embodiment is shown. The figure shows a simplified example of an apparatus to which an embodiment of the present invention is applied. In some embodiments, the apparatus may be a user equipment, a terminal, or a part of a user equipment in which more than one subscription identity is maintained.

[0132] It should be understood that the device is described here as an example showing some embodiments. It will be apparent to those skilled in the art that the device may also include other functions and / or structures and not all described functions and structures are required. Although the device has been described as one entity, different modules and memories may be implemented in one or more physical or logical entities.

[0133] The apparatus 700 of this example includes a control circuit 1000 configured to control at least a portion of the operation of the apparatus.

[0134] The apparatus may comprise a memory 1002 for storing data. Furthermore, the memory may store software 1004 executable by the control circuit 1000. The memory may be integrated in the control circuit.

[0135] The apparatus may include one or more interface circuits 1006. The interface circuits may be operably connected to the control circuit 1000. The interface circuits 1006 may be a set of transceivers configured to communicate with a RAN node such as an (e / g)NodeB of a wireless communication network. The interface circuits 1006 have the ability to support multiple subscription identities. In one embodiment, the interface may support more than one subscription identity being in the RRC_connected state at the same time. The interface circuits may be connected to an antenna device (not shown). The apparatus may also include a connection to a transmitter instead of a transceiver. The apparatus may also include a user interface.

[0136] In one embodiment, the software 1004 may comprise a computer program including program code means adapted to cause the control circuit 1000 of the apparatus to implement at least some of the above-described embodiments.

[0137] Fig.11 An embodiment is shown. The figure shows a simplified example of such or a network element to which an embodiment of the invention is applied. In some embodiments, the apparatus may be a RAN node, such as a (e / g)NodeB or a part of a RAN node.

[0138] It should be understood that the device is described here as an example showing some embodiments. It will be apparent to those skilled in the art that the device may also include other functions and / or structures and not all described functions and structures are required. Although the device is described as one entity, different modules and memories may be implemented in one or more physical or logical entities.

[0139] The example 206 includes a control circuit 1100 configured to control at least part of the operation of the device.

[0140] The apparatus may comprise a memory 1102 for storing data. Furthermore, the memory may store software 1104 executable by the control circuit 1100. The memory may be integrated in the control circuit.

[0141] The apparatus also includes one or more interface circuits 1106, 1108 configured to connect the apparatus to other devices and network elements of a radio access network. The interface circuit 1106 may be a set of transceivers configured to communicate with a user terminal. The interface circuit 1108 may be a set of transceivers configured to communicate with other network elements such as a core network. The interface may provide a wired or wireless connection.

[0142] In one embodiment, the software 1106 may comprise a computer program including computer program code means adapted to cause the control circuit 1100 of the apparatus to implement at least some of the above-described embodiments.

[0143] In one embodiment, Fig.12 As shown, Fig.11 At least some of the functions of the apparatus may be shared between two physically separate devices to form an operational entity. Thus, it can be seen that the apparatus depicts an operational entity comprising one or more physically separate devices for performing at least some of the processes described. Thus, such a shared architecture is utilized. Fig.11 The apparatus of the present invention may include a remote control unit RCU 1200, such as a host or server computer operatively coupled (e.g., via a wireless or wired network) to a remote distributed unit RDU 1202 located in a base station. In one embodiment, at least some of the described processes may be performed by the RCU 1200. In one embodiment, execution of at least some of the described processes may be shared between the RDU 1202 and the RCU 1200.

[0144] In one embodiment, the RCU 1200 may generate a virtual network through which the RCU 1200 communicates with the RDU 1202. In general, a virtual network may involve the process of combining hardware and software network resources and network functions into a single software-based management entity, a virtual network. Network virtualization may involve platform virtualization, which is often combined with resource virtualization. Network virtualization may be classified as an external virtual network that combines many networks or parts of networks into a server computer or host computer (e.g., to an RCU). External network virtualization is for optimized network sharing. Another type is an internal virtual network, which provides network-like functionality for software containers on a single system. Virtual networks may also be used to test terminal devices.

[0145] In one embodiment, the virtual network can provide a flexible allocation of operations between the RDU and the RCU. In practice, any digital signal processing task can be performed in the RDU or the RCU, and the boundary of the transfer of responsibilities between the RDU and the RCU can be selected according to the implementation.

[0146] There is no absolute chronological order for the steps and related functions described above and in the accompanying drawings, and some steps may be performed simultaneously or in a different order than given. Other functions may also be performed between steps or within steps. Certain steps may also be omitted or replaced with corresponding steps.

[0147] The device or controller capable of performing the above steps may be implemented as an electronic digital computer, a processing system or a circuit, which may include a working memory (random access memory, RAM), a central processing unit (CPU) and a system clock. The CPU may include a set of registers, an arithmetic logic unit and a controller. The processing system, controller or circuit is controlled by a sequence of program instructions transmitted from the RAM to the CPU. The controller may contain a plurality of microinstructions for basic operations. The implementation of the microinstructions may vary depending on the CPU design. The program instructions may be encoded in a programming language, which may be a high-level programming language such as C, Java, etc.; or a low-level programming language such as a machine language; or an assembler. The electronic digital computer may also have an operating system that can provide system services to computer programs written in program instructions.

[0148] As used in this application, the term "circuitry" refers to all of the following: (a) hardware circuit implementations only, such as implementations only in analog and / or digital circuits, and (b) combinations of circuitry and software (and / or firmware), such as (as applicable) the following: (i) a combination of a processor or (ii) portions of a processor / software including a digital signal processor, software, and memory that work together to enable the device to perform various functions; and (c) circuits that require software or firmware to operate, such as a microprocessor or a portion of a microprocessor, even if the software or firmware is not physically present.

[0149] The definition of "circuitry" applies to all uses of the term in this application. As a further example, as used in this application, the term "circuitry" would also cover implementations of only a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and / or firmware. For example, the term "circuitry" would also cover, if applicable to the particular element, a baseband integrated circuit or an application processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.

[0150] The embodiments provide a computer program embodied on a distribution medium comprising program instructions, which when loaded into an electronic device are configured to control the device to execute the above-described embodiments.

[0151] A computer program may be in source code form, object code form, or some intermediate form, and may be stored in some carrier, which may be any entity or device capable of carrying the program. Such carriers include, for example, recording media, computer memories, read-only memories, and software distribution packages. Depending on the processing power required, a computer program may be executed in a single electronic digital computer, or it may be distributed among several computers.

[0152] The device may also be implemented as one or more integrated circuits, such as an application specific integrated circuit ASIC. Other hardware embodiments, such as circuits constructed from separate logic components, are also possible. Mixtures of these different implementations are also possible. When selecting an implementation method, a person skilled in the art will consider, for example, the size and power consumption of the device, the necessary processing power, the production cost, and the requirements set for the production volume.

[0153] In one embodiment, a user equipment comprises at least one processor; and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to cause the apparatus to execute, using the at least one processor, maintaining a primary capability to be used when one subscription identity of the user equipment is active, and maintaining a secondary capability to be used when more than one subscription identity of the user equipment is active, and sending an indication to a radio access network (RAN) node to which the user equipment is connected regarding which capability selected from the primary or secondary capabilities to use based on the radio resource connection state of one or more subscription identities of the user equipment.

[0154] In one embodiment, a radio access network RAN ​​node comprises: at least one processor; and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to perform: receiving an indication of a primary or secondary capability to be used from a user equipment based on a radio resource connection state of one or more subscription identities of the user equipment, and transmitting a radio resource control reconfiguration message to the user equipment according to the capability to be used. .

[0155] In one embodiment, the network element comprises: at least one processor; and at least one memory comprising computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to perform: receiving an indication from a user equipment that the user equipment is capable of communicating using more than one capability, and transmitting a minimum requirement for a secondary capability to the user equipment.

[0156] It is obvious to a person skilled in the art that, as technology advances, the inventive concept can be implemented in various ways.The invention and its embodiments are not limited to the examples described above but may vary within the scope of the claims.

Claims

1. A user equipment, comprising: at least one processor; at least one memory comprising computer program code, the at least one memory and the computer program code being configured to, with the at least one processor, cause the user equipment to: maintaining primary capabilities to be used when one subscription identifier of the user equipment is active, and maintaining secondary capabilities to be used when more than one subscription identifier of the user equipment is active; transmitting, based on a radio resource connection state of one or more subscription identities of the user equipment, to a radio access network RAN ​​node to which the user equipment is connected, an indication of which capability to select from the primary or secondary capabilities for use for the one or more subscription identities; receiving, from the RAN node, at least one radio resource control reconfiguration message for the one or more subscription identities in accordance with the capabilities to be used; indicating to a network element that the user equipment is capable of communicating using more than one capability; receiving minimum requirements for secondary capabilities from the network element; as well as The secondary capabilities are created based on the minimum requirements received from the network element.

2. The user equipment according to claim 1, wherein: The at least one memory and the computer program code are further configured to, with the at least one processor, cause the user device to: The indication is transmitted to the RAN node whenever a capability to be used is changed based on a new radio resource connection state of the one or more subscription identities.

3. The user equipment according to claim 2, wherein: The indication includes an enumeration value indicating which capability to use.

4. The user equipment according to claim 1, wherein: The secondary capability is created based on one or more of the following: processor and memory capabilities of the user equipment, radio frequency capabilities of the user equipment, physical layer capabilities of the user equipment, and protocol layer capabilities of the user equipment.

5. The user equipment according to claim 1, wherein: The minimum requirement is based on a subscription profile of the one or more subscription identities.

6. A method for use in a user equipment, comprising: maintaining primary capabilities to be used when one subscription identifier of the user equipment is active, and maintaining secondary capabilities to be used when more than one subscription identifier of the equipment is active; transmitting, based on a radio resource connection state of one or more subscription identities of the user equipment, to a radio access network RAN ​​node to which the user equipment is connected, an indication of which capability to select from the primary or secondary capabilities for use for the one or more subscription identities; receiving, from the RAN node, at least one radio resource control reconfiguration message for the one or more subscription identities in accordance with the capabilities to be used; indicating to a network element that the user equipment is capable of communicating using more than one capability; receiving minimum requirements for secondary capabilities from the network element; as well as The secondary capabilities are created based on the minimum requirements received from the network element.

7. A computer-readable medium having instructions stored thereon, which, when executed by at least one processor of a user device, cause the user device to: maintaining primary capabilities to be used when one subscription identifier of the user equipment is active, and maintaining secondary capabilities to be used when more than one subscription identifier of the user equipment is active; transmitting, based on a radio resource connection state of one or more subscription identities of the user equipment, to a radio access network RAN ​​node to which the user equipment is connected, an indication of which capability to select from the primary or secondary capabilities for use for the one or more subscription identities; receiving, from the RAN node, at least one radio resource control reconfiguration message for the one or more subscription identities in accordance with the capabilities to be used; indicating to a network element that the user equipment is capable of communicating using more than one capability; receiving minimum requirements for secondary capabilities from the network element; as well as The secondary capabilities are created based on the minimum requirements received from the network element.

Images