APPARATUS AND METHOD FOR IMPROVING PERFORMANCE AND OPERATION OF MULTI-SIM DEVICES - Patent application

Abstract

A method for managing message services for a Multiple Universal Subscriber Identity Module (MUSIM) user equipment (UE) having at least a first USIM and a second USIM includes calculating a first time opportunity at which a message service associated with the first USIM is used and a second time opportunity at which a message service associated with the second USIM is used; determining a first paging pattern based on the first time opportunity and a second paging pattern based on the second time opportunity; transmitting the first paging pattern and the second paging pattern to a network access node; and receiving a message from the network access node indicating acceptance or rejection of the first paging pattern and acceptance or rejection of the second paging pattern.

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Patent Application No. 63 / 181,303, filed on April 29, 2021 (the "Provisional Application"), the contents of which are incorporated herein by reference.

[0002] The present invention is directed to 5G, the fifth generation mobile network. It is the new global wireless standard after 1G, 2G, 3G, and 4G networks. 5G enables networks designed to connect machines, objects, and devices.

[0003] The present invention more specifically relates to managing message services for a Multi Universal Subscriber Identity Module (MUSIM) User Equipment (UE) having at least a first USIM and a second USIM, the method including the steps of calculating a first time opportunity at which a message service associated with the first USIM is used and a second time opportunity at which a message service associated with the second USIM is used, determining a first paging pattern based on the first time opportunity and a second paging pattern based on the second time opportunity, transmitting the first paging pattern and the second paging pattern to a network access node, and receiving a message from the network access node indicating acceptance or rejection of the first paging pattern and acceptance or rejection of the second paging pattern. Summary of the Invention

[0004] In one embodiment, the present invention manages message services for a Multi Universal Subscriber Identity Module (MUSIM) User Equipment (UE) having at least a first USIM and a second USIM. methodThe method includes the steps of calculating a first time opportunity for a message service associated with a first USIM to be used and a second time opportunity for a message service associated with a second USIM to be used; determining a first paging pattern based on the second time opportunity and a second paging pattern based on the second time opportunity; transmitting the first paging pattern and the second paging pattern to a network access node; and receiving a message from the network access node indicating acceptance or rejection of the first paging pattern and acceptance or rejection of the second paging pattern.

[0005] Determining the first and second paging patterns includes associating a priority-based ranking with a message service associated with each of the first and second universal subscriber identity modules (USIMs) and determining the first and second paging patterns based on the priority-based ranking of the associated message services. Associating the priority-based ranking includes determining an importance of a communication service associated with the message service and assigning a rank to each of the message services based on the importance of the communication service of each of the message services. The priority-based ranking of the message services may be configured by a user or may be pre-configured by a user equipment (UE) manufacturer.

[0006] The Multi Universal Subscriber Identity Module (MUSIM) User Equipment (UE) and at least one of a first Universal Subscriber Identity Module (USIM) and a second USIM; The method comprises:registering with a first network, registering with a second network via the first network, communicating capabilities of a multi-universal subscriber identity module (MUSIM) to the first network, and receiving a message from the first network indicating acceptance by the first network of the communicated capabilities of the MUSIM. moreover The step of associating a priority based ranking with the relevant message services may be time or geographic location dependent or both. Preferably, the first paging pattern and the second paging pattern are based on a policy rule, the policy rule being provided by a Policy Control Function (PCF) module of the first network. Also, the policy rule may be pre-configured or configured by a user.

[0007] N The network access node is an access and mobility management function (AMF) module of the first network. do.

[0008] In one form, the policy rule includes a policy descriptor field, a rule priority field, a traffic descriptor field, a route selection descriptor field, and a route selection verification field. In that regard, the method may include a multi-universal subscriber identity module (MUSIM) device communicating a message to the network including a network assistance message, or determining a third paging pattern if the first paging pattern is rejected by the network access node, and determining a fourth paging pattern if the second paging pattern is rejected by the network access node. The method may further include determining whether the first time opportunity conflicts with the second time opportunity.

[0009] In one embodiment, the present invention provides a method for managing a message service by a first radio access node in a wireless communication system, the method comprising the steps of receiving, from a Multi Universal Subscriber Identity Module (MUSIM) User Equipment (UE) having at least a first USIM and a second USIM, a first message associated with a first network to the first USIM and a second message associated with a second network to the second USIM based on a policy rule, and transmitting a paging message to a second radio access node and a paging service for the UE according to the first message and the second message. and transmitting an acknowledgement message to the UE indicating acceptance or rejection of the first message and the second message. wireless The access node is an Access and Mobility Management (AMF) node, and the second wireless The access node is a policy control function node. In the method, the first message includes a preferred paging pattern for the user equipment (UE) from a first network and the second message includes a preferred paging pattern for the UE from a second network. The method may include transmitting a message to the user equipment (UE) providing configuration for a network assistance message.

[0010] In another embodiment, the present invention provides a wireless communication device including: a processor associated with a first universal subscriber identity module (USIM) and a second USIM, the processor configured to calculate a first time opportunity for a message service associated with the first USIM and a second time opportunity for a message service associated with the second USIM, determine a first paging pattern based on the first time opportunity, and determine a second paging pattern based on the second time opportunity; and a transceiver in communication with the processor, the transceiver configured to transmit the first paging pattern and the second paging pattern to a network access node and receive a message from the network access node indicating acceptance or rejection of the first paging pattern and acceptance or rejection of the second paging pattern. [Brief description of the drawings]

[0011] [Figure 1] FIG. 1 illustrates an example of a mobile communication system in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Diagram 2] FIG. 2 illustrates an example of a user plane and control plane radio protocol stack in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Diagram 3] FIG. 1 illustrates an example of mapping between logical channels and transport channels in the downlink, uplink, and sidelink in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 4] FIG. 1 illustrates an example of mapping between transport channels and physical channels in the downlink, uplink, and sidelink in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Diagram 5] FIG. 1 illustrates an example of a radio protocol stack for NR sidelink communications in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 6]FIG. 1 illustrates an example of physical signals in the downlink, uplink, and sidelink in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 7] FIG. 2 illustrates an example of Radio Resource Control (RRC) states and transitions between different RRC states in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 8] FIG. 2 illustrates an example of a frame structure and physical resources in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 9] FIG. 2 illustrates an example of a component carrier configuration in different carrier aggregation scenarios in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 10] A diagram showing an example of Bandwidth Part configuration and switching in accordance with some aspects of various exemplary embodiments of the present disclosure. [Figure 11] FIG. 1 illustrates an example of a time and frequency structure of a Synchronization Signal and Physical Broadcast Channel (PBCH) block (SSB) in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 12] FIG. 1 illustrates an example of a wireless communication system including two networks and a UE with multi-USIM capability, in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 13] FIG. 2 illustrates an example of components of a multi-USIM UE in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 14] FIG. 2 illustrates an example of components of an Access and Mobility Management Function (AMF), in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 15] FIG. 1 is a logic diagram illustrating an example of communication between a UE and a network in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 16] FIG. 13 is a flow diagram of a method for a UE to perform paging collision avoidance and multi-USIM operation in accordance with certain aspects of various exemplary embodiments of the present disclosure. [Figure 17] A flow diagram of a method in which an AMF performs paging policy management for paging collision avoidance in accordance with certain aspects of various exemplary embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0012] 1 illustrates an example of a mobile communication system 100 according to some aspects of various exemplary embodiments of the present disclosure. The mobile communication system 100 may be operated by a wireless communication system operator, such as a Mobile Network Operator (MNO), a private network operator, a Multi-System Operator (MSO), an Internet of Things (IOT) network operator, etc., and may provide services such as voice, data (e.g., wireless Internet access), messaging, vehicular communication services such as Vehicle to Everything (V2X) communication services, safety services, mission-critical services, and services in residential, commercial, or industrial environments such as IoT, Industrial IOT (IIOT), etc.

[0013] The mobile communication system 100 can enable various types of applications with different requirements in terms of latency, reliability, throughput, etc. Examples of supported applications include enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). eMBB can support stable connections at high peak data rates as well as moderate rates for cell edge users. URLLC can support applications with stringent requirements in terms of latency and reliability and moderate requirements in terms of data rates. Examples of mMTC applications include networks of vast numbers of IoT devices that are sporadically active and transmit small data payloads.

[0014] The mobile communication system 100 may include a radio access network (RAN) portion and a core network portion. In the example shown in FIG. 1, a Next Generation RAN (NG-RAN) 105 and a 5G Core Network (5GC) 110 are shown as examples of a RAN and a core network, respectively. Other examples of a RAN and a core network may be implemented without departing from the scope of the present disclosure. Other examples of a RAN include an Evolved Universal Terrestrial RAN (EUTRAN), a Universal Terrestrial RAN (UTRAN), etc. Other examples of a core network include an Evolved Packet Core (EPC), a UMTS Core Network (UCN), etc. The RAN implements a radio access technology (RAT) and exists between a user equipment (UE) 125 and the core network. Examples of such RATs include New Radio (NR), Long Term Evolution (LTE), also known as Evolved Universal Terrestrial Radio Access (EUTRA), Universal Mobile Telecommunication System (UMTS), etc. The mobile communication system 1 The RAT in the example of 5G-RAN 100 may be NR. The core network exists between the RAN and one or more external networks (e.g., data networks) and is responsible for functions such as mobility management, authentication, session management, bearer setup, and application of different Quality of Service (QoS). The functional layer between the UE 125 and the RAN (e.g., NG-RAN 105) is referred to as the Access Stratum (AS), and the functional layer between the UE 125 and the core network (e.g., 5GC 110) is referred to as the Non-access Stratum (AS). It may also be referred to as Stratum (NAS).

[0015] The UE 125 may include wireless transmission and reception means for communicating with one or more nodes in the RAN, one or more relay nodes, or one or more other UEs, etc. Examples of UEs include, but are not limited to, smartphones, tablets, laptops, computers, wireless transmitting and / or receiving units in vehicles, V2X or vehicle-to-vehicle (V2V) devices, wireless sensors, IoT devices, IIOT devices, etc. Other names may be used for UEs, such as mobile station (MS), terminal equipment, terminal node, client device, mobile device, etc.

[0016] The RAN may include nodes (e.g., base stations) for communicating with UEs. For example, the NG-RAN 105 of the mobile communication system 100 may include nodes for communicating with the UE 125. For example, different names may be used for the RAN nodes depending on the RAT used in the RAN. In a RAN using the UMTS RAT, the RAN nodes may be referred to as NodeBs (NBs). In a RAN using the LTE / EUTRA RATs, the RAN nodes may be referred to as evolved NodeBs (eNBs). In the example of the mobile communication system 100 shown in FIG. 1, the nodes of the NG-RAN 105 may be either evolved NodeBs (gNBs) 115 or next generation evolved NodeBs (ng-eNBs) 120. In this specification, the terms base station, RAN node, gNB, and ng-eNB may be used interchangeably. The gNB 115 terminates NR user plane and control plane protocols for the UE. 125. The ng-eNB 120 may provide E-UTRA user plane and control plane protocol termination for the UE 125. The interface between the gNB 115 and the UE 125 or between the ng-eNB 120 and the UE 125 may be referred to as a Uu interface. The Uu interface may be established using a user plane protocol stack and a control plane protocol stack. For the Uu interface, the direction from the base station (e.g., gNB 115 or ng-eNB 120) to the UE 125 may be referred to as a downlink, and the direction from the UE 125 to the base station (e.g., gNB 115 or ng-eNB 120) may be referred to as an uplink.

[0017] The gNB 115 and the ng-eNB 120 may be interconnected using an Xn interface. The Xn interface may include an Xn User Plane (Xn-U) interface and an Xn Control Plane (Xn-C) interface. The transport network layer of the Xn-U interface may be built on Internet Protocol (IP) transport, and GPRS Tunneling Protocol (GTP) may be used on User Datagram Protocol (UDP) / IP to carry user plane protocol data units (PDUs). Xn-U may provide non-guaranteed delivery of user plane PDUs and may support data forwarding and flow control. The transport network layer of the Xn-C interface may be built on Stream Control Transport Protocol (SCTP) over IP. The application layer signaling protocol may be referred to as Xn Application Protocol (XnAP). The SCTP layer may provide guaranteed delivery of application layer messages. The transport IP layer may include: , point-to-point transmission may be used to deliver signaling PDUs. The Xn-C interface can support Xn interface management, UE mobility management including context transfer and RAN paging, and dual connectivity.

[0018] The gNB 115 and ng-eNB 120 support 5GC over the NG interface. 110. More specifically, it may be connected to the Access and Mobility Management Function (AMF) 130 of the 5GC 110 by an NG-C interface and to the User Plane Function (UPF) 135 of the 5GC 110 by an NG-U interface. The transport network layer of the NG-U interface may be built on IP transport and may carry user plane PDUs between the NG-RAN nodes (e.g., gNB 115 or ng-eNB 120) and the UPF 135 using the GTP protocol over UDP / IP. The NG-U may provide unguaranteed delivery of user plane PDUs between the NG-RAN nodes and the UPF. The transport network layer of the NG-C interface may be built on IP transport. SCTP may be added on top of IP for reliable transmission of signaling messages. The application layer signaling protocol may be referred to as NG Application Protocol (NGAP). The SCTP layer may provide guaranteed delivery of application layer messages. At the transport IP layer, point-to-point transmission may be used to deliver signaling PDUs. The NG-C interface can provide the following functions: NG interface management, UE context management, UE mobility management, forwarding of NAS messages, paging, PDU session management, configuration forwarding, and alert message transmission.

[0019] The gNB 115 or ng-eNB 120 provides the following functions: radio resource management functions such as radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources (e.g., scheduling) to UEs in both uplink and downlink, IP and Ethernet header compression, data encryption and integrity protection, selection of the AMF at the UE attachment when the routing to the AMF cannot be determined based on information provided by the UE, routing of user plane data to the UPF, routing of control plane information to the AMF, connection setup and release, scheduling and transmission of paging messages, scheduling and transmission of system broadcast information (e.g., originating from the AMF), configuration of measurements and measurement reports for mobility and scheduling, transport level packet marking in the uplink, session management, support for network slicing, QoS flow management and mapping to data radio bearers, support for UEs in RRC inactive state, delivery of NAS messages, radio access network sharing, Dual QoS, and QoS-based QoS. The 5G LTE-R may be responsible for one or more of the following: 1) LTE connectivity, 2) close interaction between NR and E-UTRA, and 3) maintaining security and radio configuration for user plane 5G system (5GS) Cellular IoT (CIoT) optimization.

[0020] The AMF 130 provides the following functions: NAS signaling termination, NAS signaling security, AS security control, CN inter-node signaling for mobility between 3GPP access networks, idle mode UE reachability (including control and execution of paging retransmissions), registration area management, support for intra-system and inter-system mobility, access authentication, access authorization including validation of roaming rights, mobility management control (subscription and policy), support for network slicing, Session Management Function (SMF) selection, 5GS CIoT. The optimization may be performed using one or more of the following:

[0021] The UPF 135 may be responsible for one or more of the following functions: anchor point for intra / inter-RAT mobility (if applicable); external PDU session point for interconnection to the data network; packet routing and forwarding; packet inspection and application of the user plane part of policy rules; traffic usage reporting; uplink classifier supporting routing of traffic flows to the data network; branching point to support multi-homed PDU sessions; QoS operations for the user plane, e.g., packet filtering, gating, UL / DL rate enforcement, uplink traffic validation (Service Data Flow (SDF) to QoS Flow mapping); and downlink packet buffering and downlink data notification triggering.

[0022] As shown in FIG. 1, the NG-RAN 105 may support a PC5 interface between two UEs 125 (e.g., UE 125A and UE 125B). In the PC5 interface, the direction of communication between two UEs (e.g., from UE 125A to UE 125B or vice versa) is called the sidelink. Sidelink transmission and reception over the PC5 interface is supported when the UE 125 is within the coverage of the NG-RAN 105 and when the UE 125 is out of the coverage of the NG-RAN 105, regardless of which RRC state the UE 125 is in. Support for V2X services over the PC5 interface is provided by NR sidelink communication and / or V2X sidelink communication.

[0023] PC5-S signaling is used for unicast link establishment using direct communication request / accept messages. The UE self-assigns the source layer-2 ID of the PC5 unicast link, e.g. based on the V2X service type. During the unicast link establishment procedure, the UE sends its own source layer-2 ID of the PC5 unicast link to a peer UE, e.g. the UE that has received the destination ID from the higher layer. The source layer-2 ID and destination layer-2 ID pair can uniquely identify a unicast link. The receiving UE verifies that the destination ID belongs to it and accepts the unicast link establishment request from the sending UE. During the PC5 unicast link establishment procedure, the PC5-RRC procedure on the Access Stratum is invoked for UE sidelink context establishment as well as for AS layer configuration, capability exchange, etc. PC5-RRC signaling allows for the exchange of UE capabilities and AS layer configuration, e.g. sidelink radio bearer configuration, between a pair of UEs with which a PC5 unicast link is established.

[0024] NR sidelink communication can support one of three types of transmission modes (e.g., unicast transmission, groupcast transmission, and broadcast transmission) for a pair of source Layer 2 ID and destination Layer 2 ID in an AS. The unicast transmission mode is characterized by the support of one PC5-RRC connection between peer UEs for the pair, the transmission and reception of control information and user traffic between peer UEs in the sidelink, the support of sidelink HARQ feedback, the support of sidelink transmit power control, the support of RLC acknowledged mode (AM), and the detection of radio link failure for the PC5-RRC connection. The groupcast transmission is characterized by the transmission and reception of user traffic between UEs belonging to a group in the sidelink, and the support of sidelink HARQ feedback. The broadcast transmission is characterized by the transmission and reception of user traffic between UEs in the sidelink.

[0025] NR sidelink communication includes the source Layer-2 ID, destination Layer-2 ID, and PC The source Layer 2 ID is used in the sidelink communication frame. Send out The Destination Layer 2 ID may be a link layer identification that identifies a device or a group of devices. Is a recipient ofThe source Layer-2 ID may be a link layer identification that identifies the device. In some examples, the source Layer-2 ID and the destination Layer-2 ID may be assigned by a management function in the core network. The source Layer-2 ID can identify the source of the data in the NR sidelink communication. The source Layer-2 ID may be 24 bits long and may be split into two bit strings at the MAC layer. One bit string may be the LSB portion (8 bits) of the source Layer-2 ID and may be forwarded to the sender's physical layer. This can identify the source of the intended data in the sidelink control information and can be used for packet filtering at the receiver's physical layer. The second bit string may be the MSB portion (16 bits) of the source Layer-2 ID and may be carried in a Media Access Control (MAC) header. This can be used for packet filtering at the receiver's MAC layer. The destination Layer-2 ID can identify the target of the data in the NR sidelink communication. For NR sidelink communication, the destination Layer-2 ID may be 24 bits long and may be split into two bit strings at the MAC layer. One bit string may be the LSB part (16 bits) of the destination Layer 2 ID and may be forwarded to the sender's physical layer. This may identify the target of the intended data in the sidelink control information and may be used for packet filtering at the receiver's physical layer. The second bit string may be the MSB part (8 bits) of the destination Layer 2 ID and may be carried in the MAC header. This may be used for packet filtering at the receiver's MAC layer. The PC5 link identifier may uniquely identify a PC5 unicast link in the UE for the lifetime of the PC5 unicast link. The PC5 link identifier is used to indicate the PC5 unicast link for which a sidelink Radio Link Failure (RLF) declaration has been made and the PC5-RRC connection has been released.

[0026] 2A and 2B respectively illustrate an example of a user plane and control plane radio protocol stack according to some aspects of various exemplary embodiments of the present disclosure. As shown in FIG. 2A, the user plane protocol stack of the Uu interface (between the UE 125 and the gNB 115) includes Service Data Adaptation Protocol (SDAP) 201 and SDAP 211, Packet Data Convergence Protocol (PDCP) 202 and PDCP 212, Radio Link Control (RLC) 203 and RLC 213, MAC 204 and MAC 214, sublayers of Layer 2, and Physical (PHY) 205 and PHY 215 layers (Layer 1 is also referred to as L1).

[0027] The PHY 205 and PHY 215 provide transport channels 244 to the MAC 204 and MAC 214 sublayers. The MAC 204 and MAC 214 sublayers provide logical channels 243 to the RLC 203 and RLC 213 sublayers. The RLC 203 and RLC 213 sublayers provide RLC channels 242 to the PDCP 202 and PCP 212 sublayers. The PDCP 202 and PDCP 212 sublayers provide radio bearers 241 to the SDAP 201 and SDAP 211 sublayers. The radio bearers may be classified into two groups: Data Radio Bearers (DRBs) for user plane data and Signaling Radio Bearers (SRBs) for control plane data. The SDAP 201 and SDAP 211 sublayers provide QoS flows 240 to the 5GC.

[0028] The main services and functions of the MAC 204 or MAC 214 sublayer are Mapping between channels and transport channels, one or MultipleMultiplexing / demultiplexing of MAC Service Data Units (SDUs) belonging to different logical channels to / from Transport Blocks (TBs) passed to / from the physical layer on transport channels, reporting of scheduling information, error correction with Hybrid Automatic Repeat Request (HARQ) (one HARQ entity per cell in case of Carrier Aggregation (CA)), priority handling between UEs with dynamic scheduling, priority handling between logical channels of one UE with Logical Channel Prioritization (LCP), priority handling between overlapped resources of one UE, and padding. A single MAC entity may support multiple numerologies, transmission timings, and cells. Mapping restrictions in logical channel prioritization that control which numerologies, cells, and transmission timings a logical channel can use.

[0029] The HARQ function can ensure delivery between peer entities at Layer 1. If the physical layer is not configured for downlink / uplink spatial multiplexing, a single HARQ process can support one TB, and if the physical layer is configured for downlink / uplink spatial multiplexing, a single HARQ process can support one or multiple TBs.

[0030] The RLC 203 or RLC 213 sublayer can support three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC configuration may be per logical channel independent of the numerology and / or transmission time, and the Automatic Repeat Request (ARQ) may operate with any of the numerologies and / or transmission times for which the logical channel is configured.

[0031] The main services and functions of the RLC 203 or RLC 213 sublayer depend on the transmission mode (e.g., TM, UM, or AM) and may include transport of higher layer PDUs, sequence numbering independent of the PDCP sequence number (UM and AM), error correction through ARQ (AM only), segmentation (AM and UM) and resegmentation (AM only) of RLC SDUs, reassembly of SDUs (AM and UM), duplicate detection (AM only), discarding of RLC SDUs (AM and UM), RLC re-establishment, and protocol error detection (AM only).

[0032] The automatic repeat request in the RLC 203 or RLC 213 sublayer has the following properties: ARQ retransmits RLC SDUs or RLC SDU segments based on an RLC status report. Polling for RLC status reports may be used if required by RLC, and the RLC receiver may also trigger an RLC status report after detecting a missing RLC SDU or RLC SDU segment.

[0033] The main services and functions of the PDCP 202 or PDCP 212 sublayer include forwarding of data (user plane or control plane), maintenance of the PDCP sequence number (SN), header compression and decompression using the Robust Header Compression (ROHC) protocol, header compression and decompression using the EHC protocol, encryption and decryption, integrity protection and integrity verification, timer-based SDU discard, split bearer routing, duplication, reordering and in-order delivery, out-of-order delivery, and duplicate discarding.

[0034] The main services and functions of the SDAP 201 or SDAP 211 are mapping between QoS flows and data radio bearers, and mapping between downlink packets and uplink packets. This includes the marking of QoS Flow ID (QFI) for both packets. A single protocol entity in the SDAP may be configured for each individual PDU session.

[0035] As shown in FIG. 2B, the control plane protocol stack of the Uu interface (between the UE 125 and the gNB 115) includes the PHY layer (Layer 1), the MAC, RLC and PDCP sublayers of Layer 2, and further the RRC 206 and RRC 216 sublayers, as described above. The main services and functions of the RRC 206 and RRC 216 sublayers on the Uu interface include broadcast of AS and NAS related system information, paging initiated by 5GC or NG-RAN, establishment, maintenance and release of RRC connection between UE and NG-RAN (including adding, modifying and releasing carrier aggregation and adding, modifying and releasing dual connectivity in NR or between E-UTRA and NR), security functions including key management, establishment, configuration, maintenance and release of SRBs and DRBs, mobility functions (including handover and context transfer, UE cell selection and reselection and control of cell selection and reselection, and inter-RAT mobility), QoS management functions, control of UE measurement reports and reports, detection and recovery of radio link failures, and forwarding of NAS messages between NAS and UE. The NAS 207 and NAS 227 layers are control protocols (terminated in the AMF on the network side) that perform functions such as authentication, mobility management, security control, etc.

[0036] Sidelink specific services and functions of the RRC sublayer over the Uu interface include configuration of sidelink resource allocation via system information or dedicated signaling, reporting of UE sidelink information, configuration and reporting of sidelink related measurements, and reporting of UE assistance information of SL traffic patterns.

[0037] 3A, 3B, and 3C respectively show an example of mapping between logical channels and transport channels in the downlink, uplink, and sidelink according to some aspects of various exemplary embodiments of the present disclosure. Different types of data transfer services may be provided by the MAC. Each logical channel type may be defined by what type of information is transferred. The logical channels may be classified into two groups: control channels and traffic channels. The control channels are used only for transferring control plane information. The broadcast control channel (BCCH) is a downlink channel for broadcasting system control information. The paging control channel (PCCH) is a downlink channel that carries paging messages. The common control channel (CCCH) is a channel for transmitting control information between the UE and the network. This channel may be used for UEs that do not have an RRC connection with the network. The dedicated control channel (DCCH) is a point-to-point bidirectional channel that transmits dedicated control information between the UE and the network, and is used by UEs that have an RRC connection. The traffic channel is used only for transferring user plane information. A Dedicated Traffic Channel (DTCH) is a point-to-point channel dedicated to one UE for transferring user information. A DTCH can exist in both uplink and downlink. A Sidelink Control Channel (SCCH) is a sidelink channel for transmitting control information (e.g., PC5-RRC and PC5-S messages) from one UE to other UEs. A Sidelink Traffic Channel (STCH) is a sidelink channel for transmitting user information from one UE to other UEs. A Sidelink Broadcast Control Channel (SBCCH) is a sidelink channel for broadcasting sidelink system information from one UE to other UEs.

[0038] Downlink transport channel types include Broadcast Channel (BC The BCH includes the Downlink Shared Channel (DL-SCH), Downlink Receiver Channel (DRX), Downlink Receiver Channel (DH), Downlink Shared Channel (DL-SCH), and Paging Channel (PCH). The BCH is characterized by a fixed, predefined transport format and the requirement to be broadcast throughout the coverage area of ​​a cell, either as a single message or by beamforming different BCH instances. The DL-SCH is characterized by support for HARQ, support for dynamic link adaptation by varying modulation, coding, and transmit power, the possibility of being broadcast throughout the cell, the possibility of using beamforming, support for both dynamic and semi-static resource allocation, and support for UE discontinuous reception (DRX) to enable UE power saving. 。P The CH is characterized by support for UE Discontinuous Reception (DRX) to enable UE power saving (DRX cycle is indicated to the UE by the network), the requirement to be broadcast throughout the coverage area of ​​a cell either as a single message or by beamforming different BCH instances, and being mapped to physical resources that can also be dynamically used for traffic / other control channels.

[0039] In the downlink, the following connections may exist between logical channels and transport channels: BCCH may be mapped to BCH. BCCH may be mapped to DL-SCH. PCCH may be mapped to PCH. CCCH may be mapped to DL-SCH. DCCH may be mapped to DL-SCH. DTCH may be mapped to DL-SCH.

[0040] Types of uplink transport channels include the uplink shared channel (UL-SCH) and the random access channel (RACH). The UL-SCH is characterized by the possibility of using beamforming, support for dynamic link adaptation by varying transmit power and potentially modulation and coding, support for HARQ, and support for both dynamic and quasi-static resource allocation. The RACH is characterized by limited control information and child region risk.

[0041] In the uplink, the following connections exist between logical channels and transport channels: CCCH may be mapped to UL-SCH, DCCH may be mapped to UL-SCH, DTCH may be mapped to UL-SCH.

[0042] Sidelink transport channel types include the Sidelink Broadcast Channel (SL-BCH) and the Sidelink Shared Channel (SL-SCH). The SL-BCH is characterized by a predefined transport format. The SL-SCH is characterized by supporting unicast, groupcast and broadcast transmissions, supporting both UE autonomous resource selection and scheduled resource allocation by the NG-RAN, supporting both dynamic and semi-static resource allocation when the UE is assigned resources by the NG-RAN, supporting HARQ, and supporting dynamic link adaptation by varying transmit power, modulation and coding.

[0043] In the sidelink, the following connections exist between logical channels and transport channels: SCCH is mapped to SL-SCH, STCH is mapped to SL-SCH, and SBCCH is mapped to SL-BCH.

[0044] 4A, 4B, and 4C show examples of mapping between transport channels and physical channels in the downlink, uplink, and sidelink, respectively, according to some aspects of various exemplary embodiments of the present disclosure. The physical channels in the downlink include a Physical Downlink Shared Channel (PDSCH), ... The PDCCH includes the Downlink Control Channel (PDCCH), the Physical Broadcast Channel (PBCH), and the Downlink Downlink Control Channel (PCH). The PCH and DL-SCH transport channels are mapped to the PDSCH. The BCH transport channel is mapped to the PBCH. No transport channels are mapped to the PDCCH, but Downlink Control Information (DCI) is transmitted via the PDCCH.

[0045] The physical channels in the uplink include the Physical Uplink Shared Channel (PUSCH), the Physical Uplink Control Channel (PUCCH), and the Physical Random Access Channel (PRACH). The UL-SCH transport channel may be mapped to the PUSCH, and the RACH transport channel may be mapped to the PRACH. No transport channel is mapped to the PUCCH, but uplink control information (UCI) is transmitted via the PUCCH.

[0046] The physical channels of the sidelink include the physical sidelink shared channel (PSSCH), the physical sidelink control channel (PSCCH), the physical sidelink feedback channel (PSFCH), and the physical sidelink broadcast channel (PSBCH). The physical sidelink control channel (PSCCH) indicates the resources and other transmission parameters used by the UE for the PSSCH. The physical sidelink shared channel (PSSCH) transmits TBs of the data itself and control information such as HARQ procedures and CSI feedback triggers. At least six OFDM symbols in one slot are used for PSSCH transmission. The physical sidelink feedback channel (PSFCH) can carry HARQ feedback over the sidelink from the UE that is the intended recipient of the PSSCH transmission to the UE that performed the transmission. The PSFCH sequence may be transmitted in one PRB that is repeated across two OFDM symbols near the end of the sidelink resources in the slot. The SL-SCH transport channel is mapped to the PSSCH. The SL-BCH is mapped to the PSBCH. The transport channels are not mapped to the PSFCH, but the sidelink feedback control information (SFCI) is mapped to the PSFCH. The transport channels are not mapped to the PSCCH, but the sidelink control information (SCI) is mapped to the PSCCH.

[0047] 5A, 5B, 5C, and 5D each illustrate an example of a radio protocol stack for NR sidelink communication according to some aspects of various exemplary embodiments of the present disclosure. The AS protocol stack of the user plane in the PC5 interface (i.e., for STCH) consists of SDAP, PDCP, RLC and MAC sublayers, and a physical layer. The user plane protocol stack is shown in FIG. 5A. The AS protocol stack of the SBCCH in the PC5 interface consists of RRC, RLC, MAC sublayers, and a physical layer, as shown below in FIG. 5B. To support the PC5-S protocol, PC5-S is placed above the PDCP, RLC, and MAC sublayers, and a physical layer in the control plane protocol stack for SCCH for PC5-S, as shown in FIG. 5C. The AS protocol stack of the control plane for SCCH for RRC in the PC5 interface consists of RRC, PDCP, RLC and MAC sublayers, and a physical layer. The control plane protocol stack for SCCH for RRC is shown in FIG. 5D.

[0048] Sidelink Radio Bearers (SLRBs) can be classified into two groups: Sidelink Data Radio Bearers (SL DRBs) for user plane data and Sidelink Signalling Radio Bearers (SL SRBs) for control plane data. Separate SL SRBs using different SCCHs are used for PC5-RRC and PC5-S signalling, respectively. It is configured for use as a

[0049] The MAC sublayer can provide the following services and functions over the PC5 interface: radio resource selection, packet filtering, priority handling between uplink and sidelink transmissions for a given UE, and sidelink CSI reporting. Due to the restriction of logical channel prioritization in the MAC, only sidelink logical channels belonging to the same destination are multiplexed into the MAC PDU for each unicast, groupcast, and broadcast transmission associated with the destination. For packet filtering, a SL-SCH MAC header containing both source and destination Layer-2 ID parts is added to the MAC PDU. The logical channel identifier (LCID) contained within the MAC subheader can uniquely identify a logical channel within the combination of source Layer-2 ID and destination Layer-2 ID.

[0050] The services and functions of the RLC sublayer may be supported for the sidelink. Both RLC unacknowledged mode (UM) and acknowledged mode (AM) may be used for unicast transmission, while only UM may be used for groupcast or broadcast transmission. For UM, only one-way transmission of groupcast and broadcast is supported.

[0051] The services and functions of the PDCP sublayer for the Uu interface are supported for the sidelink with some restrictions: out-of-order delivery is supported only for unicast transmission and duplication over the PC5 interface may not be supported.

[0052] The SDAP sublayer can provide the following services and functions over the PC5 interface: mapping between QoS flows and sidelink data radio bearers: There is one SDAP entity per destination for one of unicast, groupcast and broadcast associated with the destination.

[0053] The RRC sublayer can provide the following services and functions over the PC5 interface: forwarding PC5-RRC messages between peer UEs, maintaining and releasing PC5-RRC connections between two UEs, and detecting sidelink radio link failures for PC5-RRC connections based on instructions from MAC or RLC. A PC5-RRC connection is a logical connection between two UEs for a pair of source Layer-2 ID and destination Layer-2 ID that is expected to be established after the corresponding PC5 unicast link is established. There is a one-to-one correspondence between PC5-RRC connections and PC5 unicast links. A UE can have multiple PC5-RRC connections with one or more UEs for different pairs of source Layer-2 ID and destination Layer-2 ID. Separate PC5-RRC procedures and messages are used for the UE to forward UE capabilities and sidelink configurations, including SL-DRB configurations, to the peer UE. Both peer UEs can exchange their UE capabilities and sidelink configurations using separate bidirectional procedures in both directions of the sidelink.

[0054] FIG. 6 illustrates an example of physical signals in the downlink, uplink, and sidelink according to some aspects of various exemplary embodiments of the present disclosure. Demodulation reference signals (DM-RS) are used in the downlink, uplink, and sidelink and are used for channel estimation. DM-RS is a UE-specific reference signal that is transmitted along with a physical channel in the downlink, uplink, or sidelink and is used for channel estimation and coherent detection of the physical channel. Phase tracking reference signals (PT-RS) are used in the downlink, uplink, and sidelink and are used for phase tracking. , and is used to mitigate performance loss due to phase noise. PT-RS is primarily used to estimate and minimize the impact of common phase error (CPE) on system performance. Due to phase noise characteristics, PT-RS signals have low density in the frequency domain and high density in the time domain. PT-RS occurs when the network configures PT-RS to be present, in combination with DM-RS. Positioning reference signals (PRS) may be used in the downlink for positioning using different positioning techniques. PRS is used to measure the delay of downlink transmission by correlating the received signal from the base station with a local replica in the receiver. Channel state information reference signals (CSI-RS) are used in the downlink and sidelink. CSI-RS is used for, among other things, channel state estimation, reference signal received power (RSRP) measurement for mobility and beam management, time / frequency tracking for demodulation. CSI-RS may be configured UE specific, but multiple users may share the same CSI-RS resources. The UE determines the CSI reports and transmits them in the uplink to the base station using the PUCCH or PUSCH. CSI reports may be carried in the sidelink MAC CE. Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) are used for radio frame synchronization. PSS and SSS are used for cell search procedure during initial attach or for mobility purposes. Sounding Reference Signal (SRS) is used in the uplink for uplink channel estimation. Similar to CSI-RS, SRS serves as a QCL reference for other physical channels as it may be configured to be transmitted quasi-colocated with SRS. Sidelink PSS (S-PSS) and Sidelink SSS (S-SSS) are used in the sidelink for sidelink synchronization.

[0055] FIG. 7 illustrates an example of Radio Resource Control (RRC) states and transitions between different RRC states according to some aspects of various exemplary embodiments of the present disclosure. A UE is in one of three RRC states: RRC connected state 710, RRC idle state 720, and RRC inactive state 730. After powering on, the UE is in the RRC idle state 720, and the UE establishes a connection with the network via an RRC connection establishment procedure using initial access to perform data transfer and / or voice calls. Once the RRC connection is established, the UE is in the RRC connected state 710. The UE can transition from the RRC idle state 720 to the RRC connected state 710 or from the RRC connected state 710 to the RRC idle state 720 using an RRC connection establishment / release procedure 740.

[0056] The RRC inactive state 730 is used to reduce the signaling load and latency caused by frequent transitions from the RRC connected state 710 to the RRC idle state 720 when the UE frequently transmits small data. In the RRC inactive state 730, the AS context is stored by both the UE and the gNB. This results in a faster state transition from the RRC inactive state 730 to the RRC connected state 710. The UE transitions from the RRC inactive state 730 to the RRC connected state 710 or from the RRC connected state 710 to the RRC inactive state 730 using an RRC connection resume / deactivation procedure 760. The UE transitions from the RRC inactive state 730 to the RRC idle state 720 using an RRC connection release procedure 750.

[0057] FIG. 8 illustrates an example of a frame structure and physical resources according to some aspects of various exemplary embodiments of the present disclosure. Downlink, uplink or sidelink transmission is performed by a frame having a time length of 10 ms with ten 1 ms subframes. Each subframe includes 1, 2, 4, ... slots, and the number of slots per subframe depends on the subcarrier spacing of the carrier on which the transmission is performed. The time length of a slot can be 14 symbols with a normal cyclic prefix (CP) or 12 symbols with an extended CP, and the number of slots in one subframe is 10 ms. The number of subcarriers varies in time depending on the subcarrier spacing used, such that the number of subcarriers is an integer. Figure 8 shows a resource grid in the time and frequency domain. Each element of the resource grid containing one symbol in time and one subcarrier in frequency is called a Resource Element (RE). A Resource Block (RB) may be defined as 12 consecutive subcarriers in the frequency domain.

[0058] In some examples, with non-slot-based scheduling, the transmission of a packet occurs over a portion of a slot, e.g., 2, 4, or 7 OFDM symbols, also called a minislot. Minislots are used for low-latency applications such as URLLC and operation in unlicensed bands. In some embodiments, minislots may also be used for fast flexible scheduling of services (e.g., preemption of URLLC for eMBB).

[0059] FIG. 9 illustrates an example of component carrier configurations in different carrier aggregation scenarios according to some aspects of various exemplary embodiments of the present disclosure. In carrier aggregation (CA), two or more component carriers (CCs) may be aggregated. A UE can simultaneously receive or transmit on one or more CCs depending on its capabilities. CA is supported for both contiguous and non-contiguous CCs in the same band or different bands as illustrated in FIG. 9. The gNB and the UE can communicate using a serving cell. The serving cell is associated with at least one downlink CC (e.g., may be associated with only one downlink CC or may be associated with a downlink CC and an uplink CC). The serving cell may be a primary cell (PCell) or a secondary cell (CCell). RiC ell(SCell).

[0060] The UE can adjust the timing of its uplink transmission using an uplink timing control procedure. A timing advance (TA) can be used to adjust the uplink frame timing relative to the downlink frame timing. The gNB can determine a desired timing advance setting and provide it to the UE. The UE can use the provided TA to determine its uplink transmit timing relative to the UE's observed downlink receive timing.

[0061] In the RRC connected state, the gNB is responsible for maintaining the timing advance to keep L1 synchronized. Serving cells with uplinks to which the same timing advance applies and using the same timing reference cell are grouped into a Timing Advance Group (TAG). A TAG contains at least one serving cell with a configured uplink. The mapping of serving cells to TAGs is set by RRC. For a primary TAG, the UE uses the PCell as the timing reference cell, except for shared spectrum channel access where in some cases a SCell may also be used as the timing reference cell. For a secondary TAG, the UE can use any of the activated SCells of this TAG as the timing reference cell and does not have to change this unless necessary.

[0062] Timing advance updates may be signaled from the gNB to the UE via a MAC CE command. Such a command may restart a TAG specific timer indicating whether L1 can be synchronized or not; when the timer is running, L1 is considered to be synchronized, otherwise L1 is considered to be unsynchronized (uplink transmissions are only on the PRACH in this case).

[0063] UEs with CA single timing advance capability shall use the same timing advance. A UE may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells that share a common serving cell (multiple serving cells grouped into one TAG). A UE with multiple timing advance capability for CA may simultaneously receive and / or transmit on multiple CCs corresponding to multiple serving cells with different timing advances (multiple serving cells grouped into multiple TAGs). NG-RAN ensures that each TAG contains at least one serving cell. A non-CA capable UE may receive on a single CC and transmit on a single CC corresponding to only a single serving cell (one serving cell in one TAG).

[0064] The multi-carrier property of the physical layer in case of CA may be exposed to the MAC layer, and one HARQ entity may be required per serving cell. If CA is configured, the UE may have one RRC connection with the network. In RRC connection establishment / re-establishment / handover, one serving cell (e.g., PCell) provides NAS mobility information. Depending on the UE capabilities, the SCell is configured to form a set of serving cells together with the PCell. The set of serving cells configured for the UE includes one PCell and one or more SCells. Reconfiguration, addition, and removal of SCells may be performed by RRC.

[0065] In a Dual Connectivity scenario, a UE is configured with multiple cells including a Master Cell Group (MCG) for communicating with a master base station, a Secondary Cell Group (SCG) for communicating with a secondary base station, and two MAC entities, i.e., a MAC entity for the MCG for communicating with the master base station and a MAC entity for the SCG for communicating with the secondary base station.

[0066] FIG. 10 illustrates an example of Bandwidth Part configuration and switching according to some aspects of some exemplary embodiments of the present disclosure. A UE may be configured with one or more Bandwidth Parts (BWPs) 1010 in a given component carrier. In some examples, one of the one or more Bandwidth Parts may be active at the same time. The active Bandwidth Part defines the operating bandwidth of the UE within the operating bandwidth of the cell. For initial access, an initial Bandwidth Part 1020 determined from system information is used until the configuration of the UE in the cell is received. For example, in Bandwidth Adaptation (BA) by BWP switching 1040, the UE's transmission and reception bandwidth is adjusted because it is not as large as the cell's bandwidth. For example, the width can be ordered to be variable (e.g., shrink during low activity periods to save power), the position can be moved in the frequency domain (e.g., to increase scheduling flexibility), and the subcarrier spacing can be ordered to be variable (e.g., to enable different services). The first active BWP 1020 may be an active BWP upon RRC (re)configuration of a PCell or activation of an SCell.

[0067] For a downlink BWP or an uplink BWP in the set of downlink or uplink BWPs, the UE is provided with the following configuration parameters, respectively: subcarrier spacing (SCS), cyclic prefix, number of common RBs and consecutive RBs, index in the set of downlink or uplink BWPs by the respective BWP-Id, a set of BWP common parameters and a set of BWP-specific parameters. The BWP is associated with an OFDM numerology based on the subcarrier spacing and cyclic prefix configured for the BWP. For the serving cell, the UE is provided with a default downlink BWP among the configured downlink BWPs. If the UE is not provided with a default downlink BWP, the default downlink BWP is the initial downlink BWP.

[0068] A downlink BWP is associated with a BWP inactivity timer. If a BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is configured, the UE may perform BWP switching to the default BWP. If a BWP inactivity timer associated with an active downlink BWP expires and a default downlink BWP is not configured, the UE may perform BWP switching to the initial downlink BWP.

[0069] FIG. 11 illustrates an example of a time and frequency structure of a Synchronization Signal and Physical Broadcast Channel (PBCH) block (SSB) according to some aspects of various exemplary embodiments of the present disclosure. The SS / PBCH block (SSB) includes one symbol and 127 subcarriers each (e.g., FIG. 11 The primary and secondary synchronization signals (PSS, SSS) occupy subcarriers 56 to 182 in the OFDM system, and the 1802.11b span three OFDM symbols and 240 subcarriers, as shown in Fig. 11As shown in Figure 1, the half-frame consists of a PBCH with an unused portion in the middle for SSS on one symbol. The time positions where the SSBs can be placed within the half-frame may be determined by the subcarrier spacing, and the period of the half-frame during which the SSBs are transmitted is set by the network. During the half-frame, different SSBs are transmitted in different spatial directions (i.e., using different beams spanning the coverage area of ​​the cell).

[0070] The PBCH is used to carry the Master Information Block (MIB) used by the UE during cell search and initial access procedures. The UE first decodes the PBCH / MIB to receive other system information. The MIB provides the UE with the necessary parameters to acquire System Information Block 1 (SIB1), more specifically, the necessary information to monitor the PDCCH for scheduling the PDSCH carrying SIB1. In addition, the MIB may indicate cell barring status information. The MIB and SIB1 are collectively referred to as Minimum System Information (SI), and SIB1 may be referred to as Remaining Minimum System Information (RMSI). The other System Information Blocks (SIBs) (e.g., SIB2, SIB3, ..., SIB10, and SIBpos) may be referred to as Other SI. Other SI may be broadcast periodically on the DL-SCH, may be broadcast on demand on the DL-SCH (e.g., upon request from a UE in RRC idle, RRC inactive, or RRC connected state), or may be sent in a dedicated manner to RRC connected UEs on the DL-SCH (e.g., upon request, if configured by the network, from a UE in RRC connected state, or if the UE has an active BWP for which a common search space is not configured).

[0071] 12 illustrates a wireless communication system 1200 including two networks in accordance with some aspects of various exemplary embodiments of the present disclosure. A UE 1203 is configured to establish a wireless connection with base stations 1209 and 1211. The UE 1203 communicates with a universal 1204 base station 1205 for communication to networks 1213 and 1215. Ruka Entrant identification The UE 1203 may each include a USIM A 1205, and a USIM B 1207. For example, the UE 1203 may be configured to transmit and receive data to and from a network 1213 via a base station 1209. The UE 1203 may further be configured to transmit and receive data to and from a network 1215 via a base station 1211. The networks 1213, 1215 are connected to the Internet 1220 and may transmit and receive data to and from each other via the Internet 1220.

[0072] The wireless networks 1213 and 1215 may be an example of the mobile communication network of Figure 1. The networks 1213 and 1215 may be an orthogonal frequency division multiplexing (OFDM), frequency The networks 1213, 1215 may use multiple access technologies, including, but not limited to, frequency division multiplexing (FDMA), code division multiplexing (CDMA), time division multiplexing (TDMA), 4G long term evolution (LTE), 5G NR, or other multiple access schemes that may be used in mobile communication networks. The networks 1213, 1215 may use the same or different multiple access technologies.

[0073] In some embodiments, the wireless networks 1213, 1215 may be cellular communication networks (e.g., 3GPP networks) or wireless local area networks (WLANs). The UE 1203 may simultaneously establish simultaneous connections to a 3GPP cellular network and a Wi-Fi network. Although various examples are described herein in the context of a 3GPP wireless network, the examples are not limited to a 3GPP wireless network and may be implemented in any network.

[0074] In the wireless network 1200, the UE 1203 may have multiple USIMs to connect to multiple wireless networks. For example, the UE 1203 may be a dual USIM device capable of connecting to multiple networks (e.g., networks 1213, 1215). Using the dual USIM capability, the UE 1203 can access two networks 1213, 1215 simultaneously.

[0075] The UE 1203 is USIM A and USIM B The UE 1203 may register with the network 1213, 1215 using the information stored in the USIM. Once the UE 1203 completes the registration process, it may establish a connection with the network 1213 and / or 1215. The UE 1203 may make calls (e.g., voice or data services) with third parties using either USIM. The UE 1203 may also receive voice calls or data transmission services from third parties (e.g., UE 125E).

[0076] In some embodiments, the UE 1203 may have dual radio frequency (RF) transceivers, which allow the UE 1203 to simultaneously transmit and receive data with the networks 1213, 1215 on the same or different frequency channels. In some embodiments, the UE 1203 may have a single RF transceiver. If the UE 1203 has a single RF transceiver, the UE may receive and transmit data with the networks 1213, 1215 on the same or different frequency channels. 1215 It is possible to send / receive data at once.

[0077] In some variations, the UE 1203 may be registered with multiple networks and needs to be able to receive pages from multiple networks. For example, the UE may be actively communicating with one network while the other network is paging the UE. The paging management (PM) module 1208 manages detection of paging and collision requests from the networks 1213, 1215. For example, the UE 1203 detects if a paging collision occurs from the networks 1213, 1215 and informs the networks 1213, 1215 of the desired paging pattern of the UE 1203 from the networks 1213, 1215. If the UE 1203 detects a paging collision during registration with the networks 1213, 1215, it can indicate to the networks that it needs network assistance to set up paging from the networks.

[0078] The PM module 1208 can be configured to determine the priority of different services in USIM A and USIM B before registering with the network. The priority of different services may be set by a user or based on a pre-configured logic. The priority of different services may differ according to the time or geographical location of the UE, or some UE local configuration. For example, in some scenarios, a “voice” type of service may be prioritized. PLMN B The MT service is a "voice" type PLMN A Service Since the service has a higher priority than the user, it is always available to the user. Another example of the pre-defined logic is: USIM B The "SMS" type service of USIM A has a higher service priority than the "voice" type service of USIM B and can trigger the UE to respond to paging. USIM B Mobile terminal (MT) services of USIM AIn some other examples, an "SMS" type service on USIM B may have a higher service priority than a "voice" type service on USIM B, thereby presenting the MT service on USIM B of "voice" type to the user even if the user is actively engaged in a "voice" service with USIM A. USIM A UE A has a higher service priority than the “voice” type service with USIM B and can trigger the UE to respond to the paging regardless of the engagement of the “voice” type service with USIM A.

[0079] FIG. 13 illustrates example components of the user equipment 1203 according to some aspects of various exemplary embodiments of the present disclosure. All or some of the blocks and functions of FIG. 13 may be in the user equipment 1203 or may be executed by the user equipment 1203. The antenna 1310 may be used to transmit or receive electromagnetic signals. The antenna 1310 may include one or more antenna elements and may enable different input / output antenna configurations including a Multiple-Input Multiple Output (MIMO) configuration, a Multiple-Input Single-Output (MISO) configuration, and a Single-Input Multiple-Output (SIMO) configuration. In some embodiments, the antenna 1310 may enable a massive MIMO configuration having tens or hundreds of antenna elements. The antenna 1310 may enable other multi-antenna techniques such as beamforming. In some examples, depending on the capabilities of the UE 1203 or the type of the UE 1203 (e.g., a low complexity UE), the UE 1203 may only support a single antenna.

[0080] The transceiver 1320 can communicate bidirectionally over the wireless links described herein via the antenna 1310. For example, the transceiver 1320 may represent a wireless transceiver in a UE and communicate bidirectionally with a wireless transceiver in a base station, or vice versa. The transceiver 1320 can include a modem that modulates packets, provides the modulated packets to the antenna 1310 for transmission, and demodulates packets received from the antenna 1310.

[0081] The memory 1330 may include RAM and ROM. The memory 1330 may store computer-readable computer-executable code 1335 including instructions that, when executed, cause the processor to perform various functions described herein. In some examples, the memory 1330 may include a Basic Input / Output System (BIOS) that may control basic hardware or software operations such as interactions with peripheral components or devices, among others. The memory 1330 includes a PM 1208 that manages paging services from different networks (e.g., networks 1213, 1215), detects occurrences of paging collisions, and determines a desired paging pattern for a UE, as previously described in FIG. 12. In some embodiments, the PM 1208 may be implemented individually or partially in software, firmware, and / or hardware.

[0082] The processor 1340 may include a hardware device having processing capabilities (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). 1340 using the memory controller The memory controller may be configured to operate on the memory. In other examples, the memory controller may be incorporated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1330) to cause the UE 1203 to perform various functions.

[0083] The USIMs 1205, 1207 may be integrated circuit cards configured to enable the UE to access wireless cellular or non-cellular networks. In some embodiments, the USIMs 1205, 1207 may be removable user identity modules or cards. Each USIM may include a CPU, ROM, RAM, EPROM, and I / O circuitry. In some embodiments, the USIMs 1205, 1207 may include storage for user subscription information and phone book contacts. USIMs 1205, 1207 may further store a Home PLMN (HPLMN) code indicating the network operator provider, a Network Identification Number (NIN), and the like.

[0084] Central processing unit (CPU) 1350 may perform basic arithmetic, logic, control, and input / output (I / O) operations specified by computer instructions in memory 1330. User equipment 1203 may include additional peripheral components such as a graphics processing unit (GPU) 1360 and a global positioning system (GPS) 1370. GPU 1360 is dedicated circuitry for rapid manipulation and modification of memory 1330 to accelerate processing performance of user equipment 1203. GPS 1370 may be used to enable location-based services or other services, for example, based on the geographic location of user equipment 1203.

[0085] FIG. 14 illustrates an example of components of an Access and Mobility Management Function (AMF) 1400 according to some aspects of various exemplary embodiments of the present disclosure. All or a subset of the blocks and functions of FIG. 14 may be in the AMF 1400 and may be executed by the AMF equipment 1400. The network interface 1410 may be used to transmit or receive data and control signals to a network (e.g., LTE, 5G network). The network interface 1410 may include an integrated circuit for transmitting and receiving data using a specific data transmission protocol (e.g., Ethernet). The network interface 1410 allows a network protocol stack to be implemented by the AMF 1400 and enables communication between different nodes on the same or different networks via routable protocols.

[0086] The transceiver 1420 can communicate bidirectionally over the interface 1410. For example, the transceiver 1420 can include an RF converter and a base station. Bureau and The transceiver 1420 may include a modem for modulating packets and providing the modulated packets to the interface 1410 for transmission, and for demodulating packets received from the interface 1410.

[0087] The memory 1430 may include RAM and ROM. The memory 1430 may include computer readable computer executable code that includes instructions that, when executed, cause the processor to perform various functions described herein. 1435 In some examples, the memory 1430 may include a Basic Input / Output System (BIOS) that may control basic hardware or software operations such as interaction with peripheral components or devices, among other things.

[0088] A Paging Policy Manager (PPM) 1406 manages paging to different UEs (e.g., UE 1203) as described above in FIG. The PPM 1400 enables the MF 1400 to apply different paging strategies to different traffic or service types associated with the same or different protocol data unit (PDU) sessions. Paging policies are defined for different services based on their handling priorities in different networks. In some embodiments, the PPM 1406 may be implemented individually or in part in software, firmware, and / or hardware.

[0089] The processor 1440 may include a hardware device having processing capabilities (e.g., a general purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). 1440 The AMF 1400 may be configured to operate the memory using a memory controller. In other examples, the memory controller may be incorporated into the processor 1440. The processor 1440 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1430) to cause the AMF 1400 to perform various functions.

[0090] A central processing unit (CPU) 1450 may perform basic arithmetic, logical, control, and input / output (I / O) operations specified by computer instructions in memory 1430 .

[0091] 15 illustrates a logic flow diagram of a method 1500 illustrating communication flow between a multi-USIM (MUSIM) UE and network components according to some aspects of various exemplary embodiments of the present disclosure. The UE determines processing priorities for different services on different USIMs prior to registering with the network. In some embodiments, the processing priorities for different services may depend on the time or geographic location of the UE or some local UE configuration.

[0092] In step 1503, the UE registers with a network associated with PLMN A (or PLMN B). When registering with the network, the UE indicates to the network (AMF) that it has multi-USIM capability.

[0093] In step 1505, the UE calculates a first paging occasion (PO) associated with the first USIM and a second paging occasion associated with the second USIM, and determines whether the first PO collides with the second PO. If the first PO collides with the second PO, a paging collision occurs. If a paging collision is detected during the registration process, the UE indicates in a registration message that it would like to obtain network assistance to avoid the collision.

[0094] In step 1507, the UE ranks the services of the PLMNs based on priority. In some examples, the priority of the services may depend on the importance of the communication service associated with the transmission of each message. The service priority may be configured by a user or based on pre-configured logic. The priority of different services may differ according to time or geographic location of the UE, or some UE local configuration.

[0095] In step 1509, the UE determines a paging pattern that indicates how it wants to be paged from different networks. For example, if the service is considered an emergency service that requires being paged in any case, the UE assigns the first available paging occasion (PO). In some examples, the paging pattern may be determined by the UE upon registration with the network. USIM A and USIM B In advance It is composed of.

[0096] In some examples, the UE may determine the paging pattern based on a policy rule. The UE may determine the paging pattern according to the paging pattern. PLMN A and PLMN B determine a policy rule for processing a paging service for the UE, and then determine a paging pattern according to the policy rule. The policy rule may be provided to the UE by the PCF or may be provided by the UE upon registration with the network. USIM A and USIM B The policy rule may be preconfigured in the policy rule table. The service priority may vary according to the time or geographic location of the UE or some UE local configuration. The policy rule includes at least a rule priority, a traffic descriptor, a route selection descriptor, and a route selection verification criterion, as shown in Table 1. [Table 1]

[0097] The DNN selection field of the exemplary policy rule specified in Table 1 indicates that the traffic of the corresponding service should be routed to the corresponding data network (DNN) via a protocol data unit (PDU) session. The traffic descriptor indicates that the traffic of the service indicated by the traffic descriptor should be forwarded on the PDU session via the selected DNN.

[0098] The procedure for associating applications and services with a PDU session is similar to the URSP rules.

[0099] Each policy rule may contain a list of route selection descriptors, each with a different route selection descriptor priority. When the UE receives a paging request (e.g., from an application or service), the UE evaluates the policy rules by rule priority and determines whether the application matches the traffic descriptor of any of the policy rules. If a valid route selection descriptor is found, the UE determines whether there is an existing PDU session that matches the route selection descriptor. The UE compares the selected route selection descriptor with the existing PDU sessions, and if there is a matching PDU session, the UE associates the application with the existing PDU session, i.e., routes the traffic of the application over this PDU session. If none of the existing sessions match, the UE attempts to establish a new session using the values ​​specified by the selected route selection descriptor.

[0100] If the paging pattern is rejected by a network, the UE defines a new paging pattern. Alternatively, the UE may periodically monitor POs from different networks. For example, the UE first monitors the PO of the paging channel of PLMN A (PLMN A paging pattern is accepted), and then: PLMN B (PL MN B paging pattern is rejected) Monitors the PO for the paging channel.

[0101] In step 1511, the UE requests registration with the network. The UE may register through its home network in both networks.

[0102] In step 1513, the AMF initiates the establishment of a UE policy association with the PCF by an Npcf_UEPolicyControlCreate request. The Npcf_UEPolicyControlCreate request , includes a MUSIM instruction to notify the PCF that MUSIM communication is possible.

[0103] In step 1515, the PCF establishes paging collision avoidance with the AMF.

[0104] In step 1517, the AMF registers the UE and enables the MUSIM capability of the UE.

[0105] FIG. 16 is a flow diagram of a method 1600 illustrating a MUSIM UE performing registration in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0106] In step 1603, the UE registers with a network (e.g., PLMN A, PLMN B). During the registration process, the UE performs a RACH process to initiate communication with the gNB, completes a security process with the gNB, and establishes an RRC connection with the gNB.

[0107] In step 1607, the UE calculates the POs from different networks and detects whether a paging collision occurs.

[0108] In step 1611, if a collision is detected during the registration process, the UE indicates that it desires network assistance to avoid the collision.

[0109] In step 1615, the UE ranks the priority of serving different services of different USIMs. The UE determines a paging policy for serving different services.

[0110] Steps 1619 In the present embodiment, the UE determines the paging patterns for different networks, and the paging patterns are determined based on the priorities of different services.

[0111] In step 1623, the UE informs the network (eg, PLMN A, PLMN B) of the desired paging pattern.

[0112] FIG. 17 is a flow diagram of a method 1700 illustrating an AMF performing registration in accordance with certain aspects of various exemplary embodiments of the present disclosure.

[0113] In step 1703, the AMF receives a UE registration request. The AMF can determine the UE MUSIM capabilities and grant the registration request.

[0114] In step 1707, the AMF receives a UE desired paging pattern from a network (e.g., PLMN A, PLMN B).

[0115] In step 1711, the AMF initiates the establishment of a UE policy association with the PCF. Further, the AMF notifies the PCF that MUSIM communication is possible.

[0116] In step 1715, the AMF indicates acceptance of the paging policy to the UE.

[0117] The exemplary blocks and modules described in this disclosure with respect to various exemplary embodiments may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. Examples of general purpose processors include, but are not limited to, a microprocessor, any conventional processor, controller, microcontroller, or state machine. In some examples, a processor may be implemented using a combination of devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration).

[0118] The functions described in this disclosure may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. Instructions or codes may be stored or transmitted to a computer-readable medium to implement the functions. Other examples for implementing the functions disclosed herein are also within the scope of this disclosure. Implementation of the functions may be via physically co-located or distributed elements (e.g., at various locations), including being distributed such that some of the functions are implemented in different physical locations.

[0119] Computer-readable media includes, but is not limited to, non-transitory computer storage media. Non-transitory storage media may be accessed by general-purpose or special-purpose computers. Examples of non-transitory storage media include, but are not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage, and the like. Non-transitory media may be used to carry or store desired program code means (e.g., instructions and / or data structures) and may be accessed by general-purpose or special-purpose computers or general-purpose or special-purpose processors. In some examples, the software / program code may be transmitted from a remote source (e.g., a website, a server, etc.) using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, microwave, and the like. In such examples, coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, and the like, are within the definition of media. Combinations of the above examples are also within the scope of computer-readable media.

[0120] As used in this disclosure, the use of the term "or" in a list of items indicates an inclusive list. A list of items can begin with a phrase such as "at least one" or "one or more." For example, a list of at least one of A, B, or C includes A or B or C or AB (i.e., A and B) or AC or BC or ABC (i.e., A and B and C). Also, as used in this disclosure, the phrase "based on" preceding a list of conditions should not be interpreted as "based only on" the set of conditions, but rather as "based at least in part on" the set of conditions. For example, a result described as "based on condition A" can be based on both condition A and condition B without departing from the scope of this disclosure.

[0121] As used herein, the terms "comprise", "include" or "contain" may be used interchangeably and have the same meaning, It should be interpreted as inclusive and open ended. The terms "comprise," "include," or "contain" may be used before a list of elements to indicate that at least all of the listed elements in the list are present, but other elements not in the list may also be present. For example, if A contains B and C, then both {B, C} and {B, C, D} are within the scope of A.

[0122] The present disclosure describes exemplary configurations in connection with the accompanying drawings, which do not represent all examples that may be implemented or all configurations within the scope of the present disclosure. The term "exemplary" should not be interpreted as "preferred" or "advantageous compared to other examples," but rather as "an example, instance, or example." By reading this disclosure, including the description of the embodiments and drawings, those skilled in the art will understand that the technology disclosed herein may be implemented using alternative embodiments. Those skilled in the art will understand that the embodiments, or specific features of the embodiments described herein, may be combined to arrive at yet other embodiments for implementing the technology described in the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. 1. A method for managing a message service in a Multi Universal Subscriber Identity Module (MUSIM) User Equipment (UE) having at least a first Universal Subscriber Identity Module (USIM) and a second USIM, comprising: determining at least one of a first paging pattern based on a priority of different message services associated with the first USIM and a second paging pattern based on a priority of different message services associated with the second USIM; transmitting the determined at least one of the first paging pattern and the second paging pattern to a network access node; receiving a message from the network access node indicating acceptance or rejection of the transmitted at least one of the first and second paging patterns; The method includes:

2. The step of determining at least one of the first paging pattern and the second paging pattern includes: associating the priority order based on a priority with the message services associated with each of the first USIM and the second USIM; determining the first paging pattern and the second paging pattern based on the priority based on the priority of the associated message service; The method of claim 1 , comprising:

3. The step of associating the priority order based on the priority includes: determining an importance of a communication service related to said message service; assigning a rank to each of the message services based on the importance of the communication service of each of the message services; Including, The method of claim 2.

4. the priority order based on the priority of the message service is configured by a user. The method of claim 2.

5. the priority order based on the priority of the message service is pre-configured by a user equipment (UE) manufacturer; The method of claim 2.

6. The MUSIM UE includes at least one of the first USIM and the second USIM; The method comprises: registering with a first network; registering with a second network via the first network; conveying MUSIM capabilities to the first network; receiving a message from the first network indicating acceptance by the first network of the conveyed capabilities of the MUSIM; Further comprising: The method of claim 1.

7. and associating the priority based on the priority with the associated message service is dependent on time or geographic location, or both. The method of claim 2.

8. the first paging pattern and the second paging pattern are based on a policy rule, the policy rule being provided by a Policy Control Function (PCF) module of the first network; The method of claim 1.

9. The policy rules may be pre-configured or configured by a user. The method according to claim 8.

10. The network access node is an Access and Mobility Management Function (AMF) module of a first network; The method of claim 1.

11. The policy rule includes a policy descriptor field, a rule priority field, a traffic descriptor field, a route selection descriptor field, and a route selection validation field.

10. The method of claim 9.

12. The method further includes the step of: the MUSIM UE transmitting a message including a network assistance message to a network. The method of claim 1.

13. determining a third paging pattern if the first paging pattern is rejected by the network access node, or determining a fourth paging pattern if the second paging pattern is rejected by the network access node. The method of claim 1.

14. The method according to claim 1, further comprising the step of determining whether a first time opportunity at which a message service associated with the first USIM is used conflicts with a second time opportunity at which a message service associated with the second USIM is used. The method of claim 1.

15. 1. A method for managing a message service in a wireless communication system, comprising: receiving, from a multi-universal subscriber identity module (MUSIM) user equipment (UE) having at least a first universal subscriber identity module (USIM) and a second USIM, at least one of a first paging pattern based on priorities of different message services associated with the first USIM and a second paging pattern based on priorities of different message services associated with the second USIM; transmitting a message to the UE indicating acceptance or rejection of the received at least one of the first and second paging patterns; The method includes:

16. 16. The method of claim 15, wherein the first radio access node is an Access and Mobility Management (AMF) node.

17. and transmitting a message to the UE providing a configuration for a network assistance message. The method of claim 15.

18. 1. A wireless communication device, comprising: a processor associated with a first universal subscriber identity module (USIM) and a second USIM, determining at least one of a first paging pattern based on a priority of different message services associated with the first USIM and a second paging pattern based on a priority of different message services associated with the second USIM; a processor configured to a transceiver in communication with the processor, transmitting the determined at least one of the first paging pattern and the second paging pattern to a network access node; receiving a message from the network access node indicating acceptance or rejection of the transmitted at least one of the first paging pattern and the second paging pattern; A transceiver configured as described above.

4. A wireless communication device comprising:

Images