WO2021243598A1 - Optimisation de mises à jour de politiques ursp sur des dispositifs à deux sim - Google Patents

Optimisation de mises à jour de politiques ursp sur des dispositifs à deux sim Download PDF

Info

Publication number
WO2021243598A1
WO2021243598A1 PCT/CN2020/094115 CN2020094115W WO2021243598A1 WO 2021243598 A1 WO2021243598 A1 WO 2021243598A1 CN 2020094115 W CN2020094115 W CN 2020094115W WO 2021243598 A1 WO2021243598 A1 WO 2021243598A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
nssai
behalf
subscription
ursp
Prior art date
Application number
PCT/CN2020/094115
Other languages
English (en)
Inventor
Chaofeng HUI
Fojian ZHANG
Yuankun ZHU
Hao Zhang
Jing Zhou
Quanling ZHANG
Xuesong Chen
Jian Li
Xiangfeng KANG
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to PCT/CN2020/094115 priority Critical patent/WO2021243598A1/fr
Publication of WO2021243598A1 publication Critical patent/WO2021243598A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing

Definitions

  • the technology discussed below relates generally to wireless communication systems, and more particularly, to updating policies and rules for 5G NR SA devices.
  • Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be accessed by various types of devices adapted to facilitate wireless communications, where multiple devices share the available system resources (e.g., time, frequency, and power) .
  • system resources e.g., time, frequency, and power
  • the third generation partnership project (3GPP) is an organization that develops and maintains telecommunication standards for fourth generation (4G) long-term evolution (LTE) networks.
  • 4G fourth generation
  • LTE long-term evolution
  • NR New Radio
  • 5G NR networks may exhibit a higher degree of flexibility and scalability than LTE, and are envisioned to support very diverse sets of requirements.
  • improvements may be desirable that one or more of the improvements obtained in 5G NR be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
  • improvements are needed to address the complexities and overhead associated with user equipment (UE) configuration.
  • aspects of the disclosure relate to providing improved methods for updating policies that relate to establishment of connections and provisioning of service for a UE. Some aspects relate to UEs that support connections for multiple subscriptions to a network. In one example, a method of wireless communication at a scheduled entity is disclosed.
  • the method includes obtaining a first single network slice selection assistance information (S-NSSAI) for use with a network connection that is established with a core network on behalf of a first network subscription associated with the UE, providing the first S-NSSAI when requesting establishment of a first protocol data unit (PDU) session on behalf of the first network subscription, receiving an updated UE route selection policy (URSP) from the core network, the updated URSP including a second S-NSSAI to be used by the UE, using the updated URSP to refresh or replace a prior URSP maintained for a second network subscription associated with the UE, and providing the second S-NSSAI when requesting establishment of a network connection with the core network on behalf of the second network subscription or when requesting establishment of a PDU session on behalf of the second network subscription.
  • S-NSSAI single network slice selection assistance information
  • a scheduled entity configured for wireless communication.
  • the scheduled entity includes a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor.
  • the processor is configured to obtain a first S-NSSAI for use with a network connection that is established with a core network on behalf of a first network subscription associated with the UE, provide the first S-NSSAI when requesting establishment of a first PDU session on behalf of the first network subscription, receive an updated URSP from the core network, the updated URSP including a second S-NSSAI to be used by the UE, use the updated URSP to refresh or replace a prior URSP maintained for a second network subscription associated with the UE, and provide the second S-NSSAI when requesting establishment of a network connection with the core network on behalf of the second network subscription or when requesting establishment of a PDU session on behalf of the second network subscription.
  • a computer-readable medium may be configured to store information including computer executable code.
  • the code may be executed by a processor and may cause the processor to obtain a first S-NSSAI for use with a network connection that is established with a core network on behalf of a first network subscription associated with the UE, provide the first S-NSSAI when requesting establishment of a first PDU session on behalf of the first network subscription, receive an updated URSP from the core network, the updated URSP including a second S-NSSAI to be used by the UE, use the updated URSP to refresh or replace a prior URSP maintained for a second network subscription associated with the UE, and provide the second S-NSSAI when requesting establishment of a network connection with the core network on behalf of the second network subscription or when requesting establishment of a PDU session on behalf of the second network subscription.
  • a scheduled entity configured for wireless communication.
  • the scheduled entity includes means for establishing network connections, configured to obtain a first S-NSSAI when establishing a first network connection with a core network on behalf of a first network subscription associated with the UE.
  • the scheduled entity may include means for establishing PDU sessions.
  • the means for establishing PDU sessions may provide the first S-NSSAI when establishing a first PDU session on behalf of the first network subscription.
  • the scheduled entity may include means for updating URSP, configured to receive an updated URSP from the core network, the updated URSP including a second S-NSSAI to be used by the UE, and further configured to use the updated URSP to refresh or replace a prior URSP maintained for a second network subscription associated with the UE.
  • the means for establishing network connections may be configured to provide the second S-NSSAI when requesting establishment of a network connection with the core network on behalf of the second network subscription.
  • the means for establishing PDU sessions may be configured to provide the second S-NSSAI when requesting establishment of a PDU session on behalf of the second network subscription.
  • a scheduled entity may send the second S-NSSAI in a request for establishment of a second PDU session on behalf of the first network subscription.
  • the request for establishment of the second PDU session on behalf of the first network subscription may be sent when a network slice used for the first PDU session is unavailable under the updated URSP.
  • the first S-NSSAI is transmitted to an AMF when requesting establishment of the first PDU session on behalf of the first network subscription.
  • the scheduled entity may receive the updated URSP in a message from the AMF.
  • the updated URSP may be triggered by a policy control function of the core network.
  • the scheduled entity may send the second S-NSSAI in a message to the AMF requesting establishment of the network connection with the core network on behalf of the second network subscription.
  • the scheduled entity may send the second S-NSSAI in a message to the AMF to request establishment of a second PDU session on behalf of the first network subscription.
  • a first universal Integrated Circuit Card (UICC) installed in the UE maintains information that identifies the first network subscription
  • a second UICC installed in the UE maintains information that identifies the second network subscription.
  • a first subscriber identity module in the UE may maintain information that identifies the first network subscription.
  • a second subscriber identity module in the UE may maintain information that identifies the second network subscription.
  • FIG. 1 is a schematic illustration of a wireless communication system according to some aspects.
  • FIG. 2 is a conceptual illustration of an example of a radio access network according to some aspects.
  • FIG. 3 is a schematic illustration of an organization of wireless resources in an air interface utilizing orthogonal frequency divisional multiplexing (OFDM) according to some aspects.
  • OFDM orthogonal frequency divisional multiplexing
  • FIG. 4 illustrates certain aspects of a portion of a 5G system architecture that may provide certain network management functions in accordance with certain aspects of the disclosure.
  • FIG. 5 illustrates registration procedures involving a UE operating in a 5G network.
  • FIG. 6 illustrates registration procedures involving a dual subscriber identity module UE, including an optimized URSP update procedure provided in accordance with certain aspects of this disclosure.
  • FIG. 7 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity according to some aspects.
  • FIG. 8 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity according to some aspects.
  • FIG. 9 is a flow chart illustrating an example of a process for generating and communicating a PHR according to some aspects.
  • Implementations may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations.
  • devices incorporating described aspects and features may also necessarily include additional components and features for implementation and practice of claimed and described embodiments.
  • transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, RF-chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders/summers, etc. ) .
  • innovations described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of varying sizes, shapes and constitution.
  • the various concepts presented throughout this disclosure may be implemented across a broad variety of telecommunication systems, network architectures, and communication standards.
  • the wireless communication system 100 includes three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106.
  • the UE 106 may be enabled to carry out data communication with an external data network 110, such as (but not limited to) the Internet.
  • the RAN 104 may implement any suitable wireless communication technology or technologies to provide radio access to the UE 106.
  • the RAN 104 may operate according to 3 rd Generation Partnership Project (3GPP) New Radio (NR) specifications, often referred to as 5G.
  • 3GPP 3 rd Generation Partnership Project
  • NR New Radio
  • the RAN 104 may operate under a hybrid of 5G NR and Evolved Universal Terrestrial Radio Access Network (eUTRAN) standards, often referred to as LTE.
  • eUTRAN Evolved Universal Terrestrial Radio Access Network
  • the 3GPP refers to this hybrid RAN as a next-generation RAN, or NG-RAN.
  • a base station 108 configured for 5G NR may interface with a core network 102 through a backhaul link 120.
  • the base station 108 may perform one or more of the following functions: transfer of user data, radio channel ciphering and deciphering, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity) , inter-cell interference coordination, connection setup and release, load balancing, distribution for non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS) , subscriber and equipment trace, RAN information management (RIM) , paging, positioning, and delivery of warning messages.
  • NAS non-access stratum
  • MBMS multimedia broadcast multicast service
  • RIM RAN information management
  • paging positioning, and delivery of warning messages.
  • many other examples may be utilized within the scope of the present disclosure.
  • a base station is a network element in a radio access network responsible for radio transmission and reception in one or more cells to or from a UE.
  • a base station may variously be referred to by those skilled in the art as a base transceiver station (BTS) , a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , an access point (AP) , a Node B (NB) , an eNode B (eNB) , a gNode B (gNB) , or some other suitable terminology.
  • BTS base transceiver station
  • BSS basic service set
  • ESS extended service set
  • AP access point
  • NB Node B
  • eNB eNode B
  • gNB gNode B
  • the radio access network 104 is further illustrated supporting wireless communication for multiple mobile apparatuses.
  • a mobile apparatus may be referred to as user equipment (UE) in 3GPP standards, but may also be referred to by those skilled in the art as a mobile station (MS) , a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal (AT) , a mobile terminal, a wireless terminal, a remote terminal, a handset, a terminal, a user agent, a mobile client, a client, or some other suitable terminology.
  • a UE may be an apparatus that provides a user with access to network services.
  • a “mobile” apparatus need not necessarily have a capability to move, and may be stationary.
  • the term mobile apparatus or mobile device broadly refers to a diverse array of devices and technologies.
  • UEs may include a number of hardware structural components sized, shaped, and arranged to help in communication; such components can include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. electrically coupled to each other.
  • a mobile apparatus examples include a mobile, a cellular (cell) phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal computer (PC) , a notebook, a netbook, a smartbook, a tablet, a personal digital assistant (PDA) , and a broad array of embedded systems, e.g., corresponding to an “Internet of things” (IoT) .
  • IoT Internet of things
  • a mobile apparatus may additionally be an automotive or other transportation vehicle, a remote sensor or actuator, a robot or robotics device, a satellite radio, a global positioning system (GPS) device, an object tracking device, a drone, a multi-copter, a quad-copter, a remote control device, a consumer and/or wearable device, such as eyewear, a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., MP3 player) , a camera, a game console, etc.
  • GPS global positioning system
  • a mobile apparatus may additionally be a digital home or smart home device such as a home audio, video, and/or multimedia device, an appliance, a vending machine, intelligent lighting, a home security system, a smart meter, etc.
  • a mobile apparatus may additionally be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device controlling electric power (e.g., a smart grid) , lighting, water, etc.; an industrial automation and enterprise device; a logistics controller; agricultural equipment; military defense equipment, vehicles, aircraft, ships, and weaponry, etc.
  • a mobile apparatus may provide for connected medicine or telemedicine support, e.g., health care at a distance.
  • Telehealth devices may include telehealth monitoring devices and telehealth administration devices, whose communication may be given preferential treatment or prioritized access over other types of information, e.g., in terms of prioritized access for transport of critical service data, and/or relevant QoS for transport of critical service data.
  • Wireless communication between a RAN 104 and a UE 106 may be described as utilizing an air interface.
  • Transmissions over the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) may be referred to as downlink (DL) transmission.
  • DL downlink
  • the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108) .
  • Another way to describe this scheme may be to use the term broadcast channel multiplexing.
  • Uplink Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) may be referred to as uplink (UL) transmissions.
  • UL uplink
  • the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE 106) .
  • a scheduling entity e.g., a base station 108 allocates resources for communication among some or all devices and equipment within its service area or cell.
  • the scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, UEs 106, which may be scheduled entities, may utilize resources allocated by the scheduling entity 108.
  • Base stations 108 are not the only entities that may function as scheduling entities. That is, in some examples, a UE may function as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs) .
  • a scheduling entity 108 may broadcast downlink traffic 112 to one or more scheduled entities 106.
  • the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network, including the downlink traffic 112 and, in some examples, uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108.
  • the scheduled entity 106 is a node or device that receives downlink control information 114, including but not limited to scheduling information (e.g., a grant) , synchronization or timing information, or other control information from another entity in the wireless communication network such as the scheduling entity 108.
  • base stations 108 may include a backhaul interface for communication with a backhaul portion 120 of the wireless communication system.
  • the backhaul 120 may provide a link between a base station 108 and the core network 102.
  • a backhaul network may provide interconnection between the respective base stations 108.
  • Various types of backhaul interfaces may be employed, such as a direct physical connection, a virtual network, or the like using any suitable transport network.
  • the core network 102 may be a part of the wireless communication system 100, and may be independent of the radio access technology used in the RAN 104.
  • the core network 102 may be configured according to 5G standards (e.g., 5GC) .
  • the core network 102 may be configured according to a 4G evolved packet core (EPC) , or any other suitable standard or configuration.
  • EPC evolved packet core
  • a UE connected to the RAN 104 may be operated in a standalone mode that may be referred to as a 5G NR SA mode, or 5G SA mode.
  • a UE connected to the RAN 104 may be operated in a non-standalone mode that may be referred to as a 5G NR NSA mode, or 5G NSA mode.
  • FIG. 2 a schematic illustration of a RAN 200 is provided.
  • the RAN 200 may be the same as the RAN 104 described above and illustrated in FIG. 1.
  • the geographic area covered by the RAN 200 may be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) based on an identification broadcasted from one access point or base station.
  • FIG. 2 illustrates macrocells 202, 204, and 206, and a small cell 208, each of which may include one or more sectors (not shown) .
  • a sector is a sub-area of a cell. All sectors within one cell are served by the same base station.
  • a radio link within a sector can be identified by a single logical identification belonging to that sector.
  • the multiple sectors within a cell can be formed by groups of antennas with each antenna responsible for communication with UEs in a portion of the cell.
  • two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206.
  • a base station can have an integrated antenna or can be connected to an antenna or RRH by feeder cables.
  • the cells 202, 204, and 126 may be referred to as macrocells, as the base stations 210, 212, and 214 support cells having a large size.
  • a base station 218 is shown in the small cell 208 (e.g., a microcell, picocell, femtocell, home base station, home Node B, home eNode B, etc. ) which may overlap with one or more macrocells.
  • the cell 208 may be referred to as a small cell, as the base station 218 supports a cell having a relatively small size. Cell sizing can be done according to system design as well as component constraints.
  • the radio access network 200 may include any number of wireless base stations and cells. Further, a relay node may be deployed to extend the size or coverage area of a given cell.
  • the base stations 210, 212, 214, 218 provide wireless access points to a core network for any number of mobile apparatuses. In some examples, the base stations 210, 212, 214, and/or 218 may be the same as the base station/scheduling entity 108 described above and illustrated in FIG. 1.
  • FIG. 2 further includes a quadcopter or drone 220, which may be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station such as the quadcopter 220.
  • a quadcopter or drone 220 may be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary, and the geographic area of the cell may move according to the location of a mobile base station such as the quadcopter 220.
  • the cells may include UEs that may be in communication with one or more sectors of each cell.
  • each base station 210, 212, 214, 218, and 220 may be configured to provide an access point to a core network 102 (see FIG. 1) for all the UEs in the respective cells.
  • UEs 222 and 224 may be in communication with base station 210; UEs 226 and 228 may be in communication with base station 212; UEs 230 and 232 may be in communication with base station 214 by way of RRH 216; UE 234 may be in communication with base station 218; and UE 236 may be in communication with mobile base station 220.
  • the UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and/or 242 may be the same as the UE/scheduled entity 106 described above and illustrated in FIG. 1.
  • a mobile network node e.g., quadcopter 220
  • quadcopter 220 may be configured to function as a UE.
  • the quadcopter 220 may operate within cell 202 by communicating with base station 210.
  • sidelink signals may be used between UEs without necessarily relying on scheduling or control information from a base station.
  • two or more UEs e.g., UEs 226 and 228, may communicate with each other using peer to peer (P2P) or sidelink signals 227 without relaying that communication through a base station (e.g., base station 212) .
  • P2P peer to peer
  • UE 238 is illustrated communicating with UEs 240 and 242.
  • the UE 238 may function as a scheduling entity or a primary sidelink device
  • UEs 240 and 242 may function as a scheduled entity or a non-primary (e.g., secondary) sidelink device.
  • a UE may function as a scheduling entity in a device-to-device (D2D) , peer-to-peer (P2P) , or vehicle-to-vehicle (V2V) network, and/or in a mesh network.
  • D2D device-to-device
  • P2P peer-to-peer
  • V2V vehicle-to-vehicle
  • UEs 240 and 242 may optionally communicate directly with one another in addition to communicating with the scheduling entity 238.
  • a scheduling entity and one or more scheduled entities may communicate utilizing the scheduled resources.
  • the various physical channels between the UE and the radio access network are generally set up, maintained, and released under the control of an access and mobility management function (e.g., the AMF 410 in FIG. 4) that is part of the core network 102 of FIG. 1.
  • the AMF 410 may include a security context management function (SCMF) that manages the security context for both the control plane and the user plane functionality, and a security anchor function (SEAF) that performs authentication.
  • SCMF security context management function
  • SEAF security anchor function
  • a radio access network 200 may utilize DL-based mobility or UL-based mobility to enable mobility and handovers (i.e., the transfer of a UE’s connection from one radio channel to another) .
  • a UE may monitor various parameters of the signal from its serving cell as well as various parameters of neighboring cells. Depending on the quality of these parameters, the UE may maintain communication with one or more of the neighboring cells.
  • the UE may undertake a handoff or handover from the serving cell to the neighboring (target) cell.
  • UE 224 illustrated as a vehicle, although any suitable form of UE may be used
  • the UE 224 may transmit a reporting message to its serving base station 210 indicating this condition.
  • the UE 224 may receive a handover command, and the UE may undergo a handover to the cell 206.
  • UL reference signals from each UE may be utilized by the network to select a serving cell for each UE.
  • the base stations 210, 212, and 214/216 may broadcast unified synchronization signals (e.g., unified Primary Synchronization Signals (PSSs) , unified Secondary Synchronization Signals (SSSs) and unified Physical Broadcast Channels (PBCH) ) .
  • PSSs Primary Synchronization Signals
  • SSSs unified Secondary Synchronization Signals
  • PBCH Physical Broadcast Channels
  • the UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive the carrier frequency and slot timing from the synchronization signals, and in response to deriving timing, transmit an uplink pilot or reference signal.
  • the uplink pilot signal transmitted by a UE may be concurrently received by two or more cells (e.g., base stations 210 and 214/216) within the radio access network 200.
  • Each of the cells may measure a strength of the pilot signal, and the radio access network (e.g., one or more of the base stations 210 and 214/216 and/or a central node within the core network) may determine a serving cell for the UE 224.
  • the radio access network e.g., one or more of the base stations 210 and 214/216 and/or a central node within the core network
  • the network may continue to monitor the uplink pilot signal transmitted by the UE 224.
  • the network 200 may handover the UE 224 from the serving cell to the neighboring cell, with or without informing the UE 224.
  • the synchronization signal transmitted by the base stations 210, 212, and 214/216 may be unified, the synchronization signal may not identify a particular cell, but rather may identify a zone of multiple cells operating on the same frequency and/or with the same timing.
  • the use of zones in 5G networks or other next generation communication networks enables the uplink-based mobility framework and improves the efficiency of both the UE and the network, since the number of mobility messages that need to be exchanged between the UE and the network may be reduced.
  • the air interface in the radio access network 200 may utilize one or more duplexing algorithms.
  • Duplex refers to a point-to-point communication link where both endpoints can communicate with one another in both directions.
  • Full duplex means both endpoints can simultaneously communicate with one another.
  • Half duplex means only one endpoint can send information to the other at a time.
  • a full duplex channel generally relies on physical isolation of a transmitter and receiver, and suitable interference cancellation technologies.
  • Full duplex emulation is frequently implemented for wireless links by utilizing frequency division duplex (FDD) or time division duplex (TDD) .
  • FDD frequency division duplex
  • TDD time division duplex
  • transmissions in different directions operate at different carrier frequencies.
  • TDD transmissions in different directions on a given channel are separated from one another using time division multiplexing. That is, at some times the channel is dedicated for transmissions in one direction, while at other times the channel is dedicated for transmissions in the other direction, where the direction may change very rapidly, e.g., several
  • a frame refers to a duration of 10 ms for wireless transmissions, with each frame consisting of 10 subframes of 1 ms each.
  • FIG. 3 an expanded view of an exemplary DL subframe 302 is illustrated, showing an OFDM resource grid 304.
  • time is in the horizontal direction with units of OFDM symbols; and frequency is in the vertical direction with units of subcarriers or tones.
  • the resource grid 304 may be used to schematically represent time–frequency resources for a given antenna port. That is, in a MIMO implementation with multiple antenna ports available, a corresponding multiple number of resource grids 304 may be available for communication.
  • the resource grid 304 is divided into multiple resource elements (REs) 306.
  • An RE which is 1 subcarrier ⁇ 1 symbol, is the smallest discrete part of the time–frequency grid, and contains a single complex value representing data from a physical channel or signal.
  • each RE may represent one or more bits of information.
  • a block of REs may be referred to as a physical resource block (PRB) or a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain.
  • an RB may include 12 subcarriers, a number independent of the numerology used.
  • an RB may include any suitable number of consecutive OFDM symbols in the time domain.
  • a UE generally utilizes only a subset of the resource grid 304.
  • An RB may be the smallest unit of resources that can be allocated to a UE.
  • the RB 308 is shown as occupying less than the entire bandwidth of the subframe 302, with some subcarriers illustrated above and below the RB 308.
  • the subframe 302 may have a bandwidth corresponding to any number of one or more RBs 308.
  • the RB 308 is shown as occupying less than the entire duration of the subframe 302, although this is merely one possible example.
  • Each 1 ms subframe 302 may consist of one or multiple adjacent slots.
  • one subframe 302 includes four slots 310, as an illustrative example.
  • a slot may be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length.
  • CP cyclic prefix
  • a slot may include 7 or 14 OFDM symbols with a nominal CP.
  • Additional examples may include mini-slots having a shorter duration (e.g., one or two OFDM symbols) . These mini-slots may in some cases be transmitted occupying resources scheduled for ongoing slot transmissions for the same or for different UEs.
  • An expanded view of one of the slots 310 illustrates the slot 310 including a control region 312 and a data region 314.
  • the control region 312 may carry control channels (e.g., PDCCH)
  • the data region 314 may carry data channels (e.g., PDSCH or PUSCH) .
  • a slot may contain all DL, all UL, or at least one DL portion and at least one UL portion.
  • the structure illustrated in FIG. 3 is merely exemplary in nature, and different slot structures may be utilized, and may include one or more of each of the control region (s) and data region (s) .
  • the various REs 306 within a RB 308 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc.
  • Other REs 306 within the RB 308 may also carry pilots or reference signals, including but not limited to a demodulation reference signal (DMRS) a control reference signal (CRS) , or a sounding reference signal (SRS) .
  • DMRS demodulation reference signal
  • CRS control reference signal
  • SRS sounding reference signal
  • pilots or reference signals may provide for a receiving device to perform channel estimation of the corresponding channel, which may enable coherent demodulation/detection of the control and/or data channels within the RB 308.
  • the transmitting device may allocate one or more REs 306 (e.g., within a control region 312) to carry DL control information 114 including one or more DL control channels that generally carry information originating from higher layers, such as a physical broadcast channel (PBCH) , a physical downlink control channel (PDCCH) , etc., to one or more scheduled entities 106.
  • DL REs may be allocated to carry DL physical signals that generally do not carry information originating from higher layers.
  • These DL physical signals may include a primary synchronization signal (PSS) ; a secondary synchronization signal (SSS) ; a demodulation reference signal (DM-RS) ; a phase-tracking reference signal (PT-RS) ; a channel-state information reference signal (CSI-RS) ; etc.
  • PSS primary synchronization signal
  • SSS secondary synchronization signal
  • DM-RS demodulation reference signal
  • PT-RS phase-tracking reference signal
  • CSI-RS channel-state information reference signal
  • the synchronization signals PSS and SSS may be transmitted in an SS block (SSB) that includes 4 consecutive OFDM symbols, numbered via a time index in increasing order from 0 to 3.
  • SSB SS block
  • the SSB may extend over 240 contiguous subcarriers, with the subcarriers being numbered via a frequency index in increasing order from 0 to 239.
  • the present disclosure is not limited to this specific SSB configuration.
  • Nonlimiting examples may utilize greater or fewer than two synchronization signals; may include one or more supplemental channels in addition to the PBCH; may omit a PBCH; and/or may utilize nonconsecutive symbols for an SSB, within the scope of the present disclosure.
  • the PDCCH may carry downlink control information (DCI) for one or more UEs supported by one or more serving cells, including but not limited to power control commands, scheduling information, a grant, and/or an assignment of REs for DL and UL transmissions.
  • DCI downlink control information
  • the transmitting device may utilize one or more REs 306 to carry UL control information 118 originating from higher layers via one or more UL control channels, such as a physical uplink control channel (PUCCH) , a physical random access channel (PRACH) , etc., to the scheduling entity 108.
  • UL REs may carry UL physical signals that generally do not carry information originating from higher layers, such as demodulation reference signals (DM-RS) , phase-tracking reference signals (PT-RS) , sounding reference signals (SRS) , etc.
  • DM-RS demodulation reference signals
  • PT-RS phase-tracking reference signals
  • SRS sounding reference signals
  • control information 118 may include a scheduling request (SR) , i.e., a request for the scheduling entity 108 to schedule uplink transmissions.
  • SR scheduling request
  • the scheduling entity 108 may transmit downlink control information 114 that may schedule resources for uplink packet transmissions.
  • UL control information may also include hybrid automatic repeat request (HARQ) feedback such as an acknowledgment (ACK) or negative acknowledgment (NACK) , channel state information (CSI) , or any other suitable UL control information.
  • HARQ hybrid automatic repeat request
  • ACK acknowledgment
  • NACK negative acknowledgment
  • CSI channel state information
  • HARQ is a technique well-known to those of ordinary skill in the art, wherein the integrity of packet transmissions may be checked at the receiving side for accuracy, e.g., utilizing any suitable integrity checking mechanism, such as a checksum or a cyclic redundancy check (CRC) . If the integrity of the transmission confirmed, an ACK may be transmitted, whereas if not confirmed, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may implement chase combining, incremental redundancy, etc.
  • any suitable integrity checking mechanism such as a checksum or a cyclic redundancy check (CRC) .
  • CRC cyclic redundancy check
  • one or more REs 306 may be allocated for user data or traffic data.
  • traffic may be carried on one or more traffic channels, such as, for a DL transmission, a physical downlink shared channel (PDSCH) ; or for an UL transmission, a physical uplink shared channel (PUSCH) .
  • PDSCH physical downlink shared channel
  • PUSCH physical uplink shared channel
  • the RAN may provide system information (SI) characterizing the cell.
  • This system information may be provided utilizing minimum system information (MSI) , and other system information (OSI) .
  • MSI minimum system information
  • OSI system information
  • the MSI may be periodically broadcast over the cell to provide the most basic information required for initial cell access, and for acquiring any OSI that may be broadcast periodically or sent on-demand.
  • the MSI may be provided over two different downlink channels.
  • the PBCH may carry a master information block (MIB)
  • the PDSCH may carry a system information block type 1 (SIB1) .
  • SIB1 may be referred to as the remaining minimum system information (RMSI) .
  • OSI may include any SI that is not broadcast in the MSI.
  • the PDSCH may carry a plurality of SIBs, not limited to SIB1, discussed above.
  • the OSI may be provided in these SIBs, e.g., SIB2 and above.
  • channels or carriers described above and illustrated in FIGs. 1 and 3 are not necessarily all the channels or carriers that may be utilized between a scheduling entity 108 and scheduled entities 106, and those of ordinary skill in the art will recognize that other channels or carriers may be utilized in addition to those illustrated, such as other traffic, control, and feedback channels.
  • Transport channels carry blocks of information called transport blocks (TB) .
  • TBS transport block size
  • MCS modulation and coding scheme
  • a UE that is subscribed to a network may establish a connection with the network through a registration process.
  • the UE may register with a 5G NR core network using information maintained by a universal subscriber identity module (USIM) application provided on a universal Integrated Circuit Card (UICC) .
  • USIM universal subscriber identity module
  • UICC universal Integrated Circuit Card
  • SIM subscriber identity module
  • the SIM maintains information associated with or provided by a network operator, including information that identifies the UE, a subscription to the network, an international mobile subscriber identity (IMSI) , security authentication and ciphering information, and a list of the services accessible by the UE.
  • IMSI international mobile subscriber identity
  • a UE may be assigned or acquire multiple network subscriptions.
  • the UE may hold subscriptions to two or more different network.
  • the UE may hold multiple subscriptions to a single network, where the UE is provisioned with multiple SIMs and where each SIM identifies the UE as a subscriber of the network.
  • each SIM identifies a different subscription associated with the UE or user of the UE.
  • the UE may establish connections with one or more subscribed networks based on subscription information maintained by one or more SIMs.
  • a 5G NR RAN may support logical networking based on network slices.
  • Each network slice may be implemented as a logical network that provides specific network capabilities and network characteristics customized to support the requirements of one or more applications provided by a network operator for the benefit of one or more users or UEs.
  • Each network slice may have a defined quality of service and specific network capabilities and network characteristics.
  • a network slice instance may include the required resources needed to provide a deployed network slice access to a set of functions that may be provided through the core network. Resources may include computing, storage and networking resources.
  • Each network slice instance may be associated with and/or identified by a network slice identifier (NSI ID) .
  • NSI ID network slice identifier
  • Network slices may be managed using network slice selection assistance information (NSSAI) .
  • NSSAI network slice selection assistance information
  • the NSSAI is a collection of single network slice selection assistance information (S-NSSAI) , each of which identifies a network slice and may include a Slice/Service type (SST) , which refers to the expected Network Slice behavior with respect to features and services.
  • SST Slice/Service type
  • Each S-NSSAI may include an optional slice differentiator (SD) that may distinguish between multiple network slices that have the same SST.
  • SD slice differentiator
  • the NSSAI may be a configured NSSAI, a requested NSSAI or an allowed NSSAI. Based on the operational or deployment needs of the network operator, a network slice instance can be associated with one or more S-NSSAIs, and an S-NSSAI can be associated with one or more Network Slice instances.
  • FIG. 4 illustrates certain aspects of a portion of a 5G system architecture 400 that provide certain network management functions, including network slice management services and/or network slice related functions.
  • the 5G system architecture 400 includes a network slice selection function (NSSF 402) , a policy control function (PCF 406) an application function (AF 408) , an AMF 410 and a session management function (SMF 412) .
  • a requested and/or allowed NSSAI may be exchanged between the UE 414 and the RAN 416 in one or more messages.
  • the RAN 416 may associate certain network slices and network slice instances for the UE 414 based on a requested NSSAI signaled by the UE 414.
  • the RAN 416 may select an AMF 410 to handle requests from the UE 414.
  • the AMF 410 handles connection or mobility management requests and forwards session management requirements to the SMF 412.
  • the AMF 410 may determine which SMF 412 is best suited to handle a connection request by querying a Network Repository Function
  • the SMF 412 may be configured to establish, modify and/or release protocol data unit (PDU) sessions through signaling exchanged between the UE 414 and the SMF 412.
  • PDU protocol data unit
  • the establishment of a PDU Session in a network slice to a data network (DN 420) permits data transmission within the network slice, and the association between the UE 414 and the DN 420 provides a PDU connectivity service supported by a user plane function (UPF 418) that provides packet processing for service-based architectures (SBAs) .
  • UPF 418 user plane function
  • a PDU session request may include an S-NSSAI and a data network name (DNN) .
  • a UE 414 that is registered in a Public Land Mobile Network (PLMN) and that has obtained an allowed NSSAI, indicates its corresponding S-NSSAI in a PDU Session Establishment procedure, in accordance with a UE Route Selection Policy (URSP) .
  • the URSP is used by the UE 414 to determine routing for outgoing traffic.
  • the DNN identifies the DN 420 for the PDU session.
  • a set of network slices associated with the UE 414 through the URSP can be changed at any time while the UE 414 is registered with a network. Changes to the URSP may be initiated by the network.
  • the network may modify the URSP for a UE 414 based on local policies, changes in local policies, subscription changes, unavailability of the network slice and/or UE mobility operational reasons. Updating the URSP may affect or change the set of network slices to which the UE 414 is registered or associated. Updates to the URSP may be provided in a registration process initiated by a message sent from the PCF 406 to the UE 414.
  • a new allowed NSSAI may be provided to the UE 414 during a registration procedure or after a notification of the change of the network slices has been sent to the UE 414.
  • the UE 414 may use a network slice selection policy (NSSP) included in URSP rules to determine whether ongoing traffic can be routed over existing PDU sessions associated with other network slices or establish one or more new PDU sessions.
  • NSSP network slice selection policy
  • the UE 414 may change the set of S-NSSAIs being used by initiating a registration procedure.
  • FIG. 5 is an example of message flow 500 that illustrates registration procedures involving a UE 502 that is operating in a 5G NR network.
  • the network may be configured for operation as a 5G SA network.
  • the UE 502 may have been previously configured with a URSP rule through an exchange of messages 510 with an AMF 504.
  • the preconfigured URSP rule may be saved in a memory or USIM of the UE 502.
  • the UE 502 may provide a requested NSSAI list in a registration request message, where the requested NSSAI list may be derived from the preconfigured USRP rule and local configuration information of the UE 502.
  • the UE 502 may provide a requested NSSAI list that includes NSSAIs that do not conflict with the preconfigured USRP rule or the local configuration information of the UE 502.
  • the registration accept message provided in response by the AMF 504 may identify allowed/configured/rejected NSSAIs.
  • the URSP rule may associate the UE 502 with S-NSSAI_A.
  • the UE 502 may send the S_NSSAI_A with a DNN in a request 512 to establish a PDU session with a data network.
  • the data network is identified by the DNN as the Internet.
  • the request 512 may be sent to the AMF 504, which may respond positively with a PDU Session establishment accept message 514.
  • an associated PCF 506 may trigger and/or initiate a URSP update.
  • the URSP update may be triggered based on local policies, after a network slice becoming unavailable, and/or after the UE 502 has moved to a new registration area.
  • the URSP update may be triggered after a subscription change, and/or for UE mobility operational reasons.
  • the PCF 506 may notify the AMF 504 of the updated URSP in a message 518 transmitted using a communication service (Namf) defined to support certain functions of the AMF 504.
  • the AMF 504 may operate as a conduit through which 5GC Network Functions (NFs) communicate with the UE 502 accessible through the network.
  • NFs 5GC Network Functions
  • a NF can use Namf to obtain information from the AMF 504 regarding capabilities, reachability, and/or current location of the UE 502.
  • the AMF 504 may respond to notification of the updated URSP by transmitting updated URSP information in a policy container 520 to the UE 502 using a downlink NAS transport.
  • the updated URSP may define a different S-NSSAI (e.g., S_NSSAI_B) for the UE 502.
  • the UE 502 may respond by transmitting an updated URSP configuration in a policy container 522 using an uplink NAS transport.
  • the UE 502 may release or keep previously-established PDU sessions. In some instances, a previously-established PDU session may be maintained when the associated network slice remains available in the updated URSP. In some instances, the UE 502 may send the S_NSSAI_B with a DNN in a request 524 to establish a PDU session through a different network slice. In the illustrated example, UE 502 includes S_NSSAI_B with a DNN corresponding to the Internet in the request 524. The request 524 may be sent to the AMF 504, which may respond positively with a PDU Session establishment accept message 526.
  • a dual-SIM UE may be operating in a 5G network, where both SIMs are available to the UE when operating as a 5G SA device.
  • the UE executes a registration process for each SIM and, where necessary, executes one or more PDU session establishment requests for each SIM when the associated PCF triggers the URSP update.
  • Certain aspects of this disclosure provide an optimized URSP update procedure that can reduce the network control plane signaling load associated with URSP updates.
  • the URSP update procedure can enable faster PDU session setup associated with a second SIM after a first SIM has performed the optimized URSP update procedure.
  • FIG. 6 is an example of message flow 600 that illustrates registration involving a dual-SIM UE 602 using an optimized URSP update procedure that is conducted in accordance with certain aspects of this disclosure.
  • the network may be configured for operation as a 5G SA network.
  • the UE 602 may be capable of maintaining network connections for two subscriptions, which may be identified herein as the SIM1 608 1 subscription and the SIM2 608 2 subscription.
  • an action taken by the UE 602 on behalf of one of the subscriptions 608 1 , 608 2 may be referred to herein as an action taken by the corresponding subscription 608 1 , 608 2 .
  • Actions taken by the UE 602 on behalf of one of the subscriptions 608 1 , 608 2 include transmissions on behalf of the corresponding subscription 608 1 , 608 2 . Additionally, and for the purposes of this disclosure, an action affecting the UE 602 when operating on behalf of one of the subscriptions 608 1 , 608 2 may be referred to herein as an action affecting the corresponding subscription 608 1 , 608 2 . Actions affecting the UE 602 when operating on behalf of one of the subscriptions 608 1 , 608 2 include reception of messages directed to the corresponding subscription 608 1 , 608 2 .
  • the SIM1 608 1 and SIM2 608 2 subscriptions may have been previously configured with a URSP rule.
  • the SIM1 608 1 subscription may have been previously configured with the URSP rule through an exchange of messages 610 with an AMF 604.
  • the preconfigured URSP rule may be saved in a memory of the UE 602 or in the USIM corresponding to the SIM1 608 1 subscription.
  • the SIM1 608 1 subscription may provide a requested NSSAI list in a registration request message, where the requested NSSAI list may be derived from the preconfigured USRP rule and local configuration information of the UE 602.
  • the SIM1 608 1 subscription may provide a requested NSSAI list that includes NSSAIs that do not conflict with the preconfigured USRP rule or the local configuration information of the UE 602.
  • the registration accept message provided in response by the AMF 604 may identify allowed/configured/rejected NSSAIs.
  • the URSP rule may associate the SIM1 608 1 subscription with an S-NSSAI (here, S_NSSAI_A) .
  • the UE 602 on behalf of the SIM1 608 1 subscription, may provide the S_NSSAI_A with a DNN in a request 612 to establish a PDU session, with a data network.
  • the data network is identified by the DNN as the Internet.
  • the request 612 may be sent to the AMF 604, which may respond positively with a PDU Session establishment accept message 614.
  • an associated PCF 606 may trigger and/or initiate a URSP update.
  • the URSP update may be triggered based on local policies, and/or after a network slice becoming unavailable.
  • the URSP update may be triggered after a subscription change, and/or for UE mobility operational reasons.
  • the PCF 606 may notify the AMF 604 of the updated URSP in a message 618.
  • the AMF 604 may respond to notification of the updated URSP by transmitting updated URSP information in a policy container 620 to the UE 602 for the SIM1 608 1 subscription using a downlink NAS transport.
  • the updated URSP may define a different S-NSSAI (e.g., S_NSSAI_B) for the SIM1 608 1 subscription.
  • the UE 602 may respond on behalf of the SIM1 608 1 subscription by transmitting an updated URSP configuration in a policy container 622 using an uplink NAS transport.
  • the SIM1 608 1 subscription may update its URSP information 628.
  • the SIM1 608 1 subscription may release or keep previously-established PDU sessions.
  • a previously-established PDU session may be maintained when the associated network slice remains available in the updated URSP.
  • the UE 602 may send S_NSSAI_B with a DNN in a request 624 to establish a PDU session through a different network slice for the SIM1 608 1 subscription.
  • a new PDU session may be established.
  • the request 624 includes S_NSSAI_B with a DNN corresponding to the Internet.
  • the request 624 may be sent to the AMF 604, which may respond positively with a PDU Session establishment accept message 626.
  • the updated, saved URSP information 628 for the SIM1 608 1 subscription may be shared with the SIM2 608 2 subscription.
  • the UE 602 may store, update or otherwise refresh 630 the URSP information 632 maintained for the SIM2 608 2 subscription using the URSP information 628 maintained for the SIM1 608 1 subscription.
  • the UE 602 may then use the refreshed or updated URSP information 632 to register the SIM2 608 2 subscription with the AMF 604 and/or to establish one or more PDU sessions for the SIM2 608 2 subscription.
  • the SIM2 608 2 subscription be may registered with the AMF 604 through an exchange of messages 634 between the UE 602 and the AMF 604.
  • the UE 602 may send S_NSSAI_B with a DNN in a request 636 to establish a PDU session for the SIM2 608 2 subscription.
  • the S_NSSAI_B may be sent with a DNN corresponding to the Internet in a request 636 sent to the AMF 604.
  • the AMF 604 may respond positively with a PDU Session establishment accept message 638.
  • FIG. 7 is a block diagram illustrating an example of a hardware implementation for a scheduling entity 700 employing a processing system 714.
  • the scheduling entity 700 may be a user equipment (UE) as illustrated in any one or more of FIGs. 1, 2, 4, 5 and/or 6.
  • the scheduling entity 700 may be a base station as illustrated in any one or more of FIGs. 1 and/or 2.
  • the scheduling entity 700 may be implemented with a processing system 714 that includes one or more processors 704.
  • processors 704 include microprocessors, microcontrollers, digital signal processors (DSPs) , field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • DSPs digital signal processors
  • FPGAs field programmable gate arrays
  • PLDs programmable logic devices
  • state machines gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure.
  • the scheduling entity 700 may be configured to perform any one or more of the functions described herein. That is, the processor 704, as utilized in a scheduling entity 700, may be used to implement any one or more of the processes described below.
  • the processor 704 may in some instances be implemented via a baseband or modem chip and in other implementations, the processor 704 may itself comprise a number of devices distinct and different from a baseband or modem chip (e.g., in such scenarios is may work in concert to achieve embodiments discussed herein) . And as mentioned above, various hardware arrangements and components outside of a baseband modem processor can be used in implementations, including RF-chains, power amplifiers, modulators, buffers, interleavers, adders/summers, etc.
  • the processing system 714 may be implemented with a bus architecture, represented generally by the bus 702.
  • the bus 702 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 714 and the overall design constraints.
  • the bus 702 communicatively couples together various circuits including one or more processors (represented generally by the processor 704) , a memory 705, and computer-readable media (represented generally by the computer-readable medium 706) .
  • the bus 702 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further.
  • a bus interface 708 provides an interface between the bus 702 and a transceiver 710.
  • the transceiver 710 provides a communication interface or means for communicating with various other apparatus over a transmission medium.
  • a user interface 712 e.g., keypad, display, speaker, microphone, joystick
  • a user interface 712 is optional, and may be omitted in some examples, such as a base station.
  • the processor 704 is responsible for managing the bus 702 and general processing, including the execution of software stored on the computer-readable medium 706.
  • the software when executed by the processor 704, causes the processing system 714 to perform the various functions described below for any particular apparatus.
  • the computer-readable medium 706 and the memory 705 may also be used for storing data that is manipulated by the processor 704 when executing software.
  • One or more processors 704 in the processing system may execute software.
  • Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • the software may reside on a computer-readable medium 706.
  • the computer-readable medium 706 may be a non-transitory computer-readable medium.
  • a non-transitory computer-readable medium includes, by way of example, a magnetic storage device (e.g., hard disk, floppy disk, magnetic strip) , an optical disk (e.g., a compact disc (CD) or a digital versatile disc (DVD) ) , a smart card, a flash memory device (e.g., a card, a stick, or a key drive) , a random access memory (RAM) , a read only memory (ROM) , a programmable ROM (PROM) , an erasable PROM (EPROM) , an electrically erasable PROM (EEPROM) , a register, a removable disk, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer.
  • a magnetic storage device e.g., hard disk, floppy disk, magnetic strip
  • an optical disk e.g.
  • the computer-readable medium may also include, by way of example, a carrier wave, a transmission line, and any other suitable medium for transmitting software and/or instructions that may be accessed and read by a computer.
  • the computer-readable medium 706 may reside in the processing system 714, external to the processing system 714, or distributed across multiple entities including the processing system 714.
  • the computer-readable medium 706 may be embodied in a computer program product.
  • a computer program product may include a computer-readable medium in packaging materials.
  • the processor 704 may include circuitry configured for various functions.
  • the processor 704 may include resource assignment and scheduling circuitry 742, configured to generate, schedule, and modify a resource assignment or grant of time–frequency resources (e.g., a set of one or more resource elements) .
  • the resource assignment and scheduling circuitry 742 may schedule time–frequency resources within a plurality of time division duplex (TDD) and/or frequency division duplex (FDD) subframes, slots, and/or mini-slots to carry user data traffic and/or control information to and/or from multiple UEs.
  • TDD time division duplex
  • FDD frequency division duplex
  • the resource assignment and scheduling circuitry 742 may be configured to allocate/schedule downlink resources for the transmission of one or more messages.
  • the resource assignment and scheduling circuitry 742 may further be configured to allocate/schedule uplink resources for a UE to communicate information to the scheduling entity 700.
  • the uplink resources may be a dynamically scheduled via an uplink grant, semi-statically scheduled, or semi-persistently scheduled.
  • the resource assignment and scheduling circuitry 742 may further be configured to execute resource assignment and scheduling software 752 stored in the computer-readable medium 706 to implement one or more of the functions described herein.
  • the processor 704 may further include communication and processing circuitry 744 configured to communicate with a UE.
  • the communication and processing circuitry 744 may include one or more hardware components that provide the physical structure that performs processes related to wireless communication (e.g., signal reception and/or signal transmission) and signal processing (e.g., processing a received signal and/or processing a signal for transmission) .
  • the communication and processing circuitry 744 may be configured to generate and transmit one or more messages via the transceiver 710.
  • the communication and processing circuitry 744 may be configured to receive and process messages via the transceiver 710.
  • the communication and processing circuitry 744 may further be configured to execute communication and processing software 754 stored on the computer-readable medium 706 to implement one or more functions described herein.
  • the processor 704 may further include one or more core network functions.
  • the processor 704 may further include PCF and/or AMF circuitry 746 configured to manage requests from a UE.
  • the requests may relate to establishing network connections and establishing PDU sessions.
  • PCF circuitry may be configured to update and/or trigger updates of URSPs 715 for one or more UEs.
  • the URSPs 715 may be maintained in the memory 705.
  • the PCF and/or AMF circuitry 746 may further be configured to execute PCF and/or AMF software 756 stored on the computer-readable medium 706 to implement one or more functions described herein.
  • the scheduling entity 700 has a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor.
  • the scheduling entity 700 provide a first S-NSSAI for use with a first network connection that is established with a UE on behalf of a first network subscription associated with the UE.
  • the first S-NSSAI may be received with requests for establishment of a PDU sessions through the first network connection.
  • the processor may receive an updated URSP from the core network, the updated URSP including a second S-NSSAI to be used by the UE.
  • the UE may be configured to use the updated URSP to refresh or replace a prior URSP maintained for a second network subscription associated with the UE, and to provide the second S-NSSAI when requesting establishment of a second network connection with the core network on behalf of the second network subscription or when requesting establishment of a second PDU session through the second network connection.
  • FIG. 8 is a conceptual diagram illustrating an example of a hardware implementation for an exemplary scheduled entity 800 employing a processing system 814.
  • an element, or any portion of an element, or any combination of elements may be implemented with a processing system 814 that includes one or more processors 804.
  • the scheduled entity 800 may be a user equipment (UE) as illustrated in any one or more of FIGs. 1, 2, 4, 5 and/or 6.
  • UE user equipment
  • the processing system 814 may be substantially the same as the processing system 714 illustrated in FIG. 7, including a bus interface 808, a bus 802, memory 805, a processor 804, and a computer-readable medium 806.
  • the scheduled entity 800 may include a user interface 812 and a transceiver 810 substantially similar to those described above in FIG. 7. That is, the processor 804, as utilized in a scheduled entity 800, may be used to implement any one or more of the processes described herein.
  • the processing system 814 may be coupled to one or more UICCs 816.
  • Each UICC 816 may include a USIM application.
  • the USIM application may maintain and/or provide subscription-related information and/or subscriber-related information.
  • the USIM application may maintain cryptographic keys shared with a home network of the subscriber.
  • the processor 804 may include communication and processing circuitry 842, configured to communicate with one or more base stations.
  • the communication and processing circuitry 842 may include one or more hardware components that provide the physical structure that performs processes related to wireless communication (e.g., signal reception and/or signal transmission) and signal processing (e.g., processing a received signal and/or processing a signal for transmission) .
  • the communication and processing circuitry 842 may be configured to receive and process one or more scheduling transmissions from the one or more base stations via the transceiver 810.
  • the communication and processing circuitry 842 may be configured to identify uplink resources that may be utilized to transmit a PHR to a base station.
  • the communication and processing circuitry 842 may further be configured to transmit the PHR utilizing the uplink resources.
  • the communication and processing circuitry 842 may further be configured to execute communication and processing software 852 stored on the computer-readable medium 806 to implement one or more functions described herein.
  • the processor 804 may further include connection establishment circuitry 844, configured to establish network connections with networks on behalf of one or more network subscription associated with the UE.
  • the connection establishment circuitry 844 may be further configured to execute connection establishment software 854 stored on the computer-readable medium 806 to implement one or more functions described herein.
  • the processor 804 may further include PDU session establishment circuitry 846, configured to establish PDU sessions for one or more network subscription associated with the UE.
  • the PDU session establishment circuitry 846 may be further configured to execute PDU session establishment software 856 stored on the computer-readable medium 806 to implement one or more functions described herein.
  • the processor 804 may further include URSP update circuitry 848, configured to receive and propagate changes to URSP 815 and/or URSP rules defined by the URSP 815 for use with one or more network subscription associated with the UE.
  • the URSP update circuitry 848 may be further configured to execute URSP update software 858 stored on the computer-readable medium 806 to implement one or more functions described herein.
  • the scheduled entity 800 has a processor, a transceiver communicatively coupled to the processor, and a memory communicatively coupled to the processor.
  • the processor may be configured to obtain a first S-NSSAI for use with a network connection that is established with a core network on behalf of a first network subscription associated with the UE provide the first S-NSSAI when requesting establishment of a first PDU session on behalf of the first network subscription, receive an updated URSP from the core network, the updated URSP including a second S-NSSAI to be used by the UE, use the updated URSP to refresh or replace a prior URSP maintained for a second network subscription associated with the UE, and provide the second S-NSSAI when requesting establishment of a network connection with the core network on behalf of the second network subscription or when requesting establishment of a PDU session on behalf of the second network subscription.
  • the processor may be configured to send the second S-NSSAI in a request for establishment of a second PDU session on behalf of the first network subscription.
  • the request for establishment of the second PDU session on behalf of the first network subscription may be sent when a network slice used for the first PDU session is unavailable under the updated URSP.
  • the first S-NSSAI is transmitted to an AMF when requesting establishment of the first PDU session on behalf of the first network subscription.
  • the processor may be configured to receive the updated URSP in a message from the AMF.
  • the updated URSP may be triggered by a PCF of the core network.
  • the processor may be configured to send the second S-NSSAI in a message to the AMF requesting establishment of the network connection with the core network on behalf of the second network subscription.
  • the processor may be configured to send the second S-NSSAI in a message to the AMF to request establishment of a second PDU session on behalf of the first network subscription.
  • a first universal Integrated Circuit Card (UICC) installed in the UE maintains information that identifies the first network subscription
  • a second UICC installed in the UE maintains information that identifies the second network subscription.
  • a first SIM in the UE may maintain information that identifies the first network subscription.
  • a second subscriber identity module in the UE may maintain information that identifies the second network subscription.
  • FIG. 9 is a flow chart illustrating an example of a process 900 for generating and communicating a PHR in accordance with some aspects of the present disclosure. As described below, some or all illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some illustrated features may not be required for implementation of all embodiments. In some examples, the process 900 may be carried out by the scheduled entity 800 illustrated in FIG. 8. In some examples, the process 900 may be carried out by any suitable apparatus or means for carrying out the functions or algorithm described below.
  • the scheduled entity 800 may obtain a first S-NSSAI for use with a network connection that is established with a core network on behalf of a first network subscription associated with the UE.
  • the scheduled entity 800 may provide the first S-NSSAI when requesting establishment of a first PDU session on behalf of the first network subscription.
  • the scheduled entity 800 may receive an updated URSP from the core network.
  • the updated URSP may include a second S-NSSAI to be used by the UE.
  • the scheduled entity 800 may use the updated URSP to refresh or replace a prior URSP maintained for a second network subscription associated with the UE.
  • the scheduled entity 800 may provide the second S-NSSAI when requesting establishment of a network connection with the core network on behalf of the second network subscription or when requesting establishment of a PDU session on behalf of the second network subscription.
  • the scheduled entity 800 may send the second S-NSSAI in a request for establishment of a second PDU session on behalf of the first network subscription.
  • the request for establishment of the second PDU session on behalf of the first network subscription may be sent when a network slice used for the first PDU session is unavailable under the updated URSP.
  • the first S-NSSAI is transmitted to an AMF when requesting establishment of the first PDU session on behalf of the first network subscription.
  • the scheduled entity 800 may receive the updated URSP in a message from the AMF.
  • the updated URSP may be triggered by a PCF of the core network.
  • the scheduled entity 800 may send the second S-NSSAI in a message to the AMF requesting establishment of the network connection with the core network on behalf of the second network subscription.
  • the scheduled entity 800 may send the second S-NSSAI in a message to the AMF to request establishment of a second PDU session on behalf of the first network subscription.
  • a first universal Integrated Circuit Card (UICC) installed in the UE maintains information that identifies the first network subscription
  • a second UICC installed in the UE maintains information that identifies the second network subscription.
  • a first SIM in the UE may maintain information that identifies the first network subscription.
  • a second subscriber identity module in the UE may maintain information that identifies the second network subscription.
  • various aspects may be implemented within other systems defined by 3GPP, such as Long-Term Evolution (LTE) , the Evolved Packet System (EPS) , the Universal Mobile Telecommunication System (UMTS) , and/or the Global System for Mobile (GSM) .
  • LTE Long-Term Evolution
  • EPS Evolved Packet System
  • UMTS Universal Mobile Telecommunication System
  • GSM Global System for Mobile
  • Various aspects may also be extended to systems defined by the 3rd Generation Partnership Project 2 (3GPP2) , such as CDMA2000 and/or Evolution-Data Optimized (EV-DO) .
  • 3GPP2 3rd Generation Partnership Project 2
  • EV-DO Evolution-Data Optimized
  • Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Ultra-Wideband (UWB) , Bluetooth, and/or other suitable systems.
  • Wi-Fi IEEE 802.11
  • WiMAX IEEE 8
  • the word “exemplary” is used to mean “serving as an example, instance, or illustration. ” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of the disclosure. Likewise, the term “aspects” does not require that all aspects of the disclosure include the discussed feature, advantage or mode of operation.
  • the term “coupled” is used herein to refer to the direct or indirect coupling between two objects. For example, if object A physically touches object B, and object B touches object C, then objects A and C may still be considered coupled to one another-even if they do not directly physically touch each other. For instance, a first object may be coupled to a second object even though the first object is never directly physically in contact with the second object.
  • circuit and “circuitry” are used broadly, and intended to include both hardware implementations of electrical devices and conductors that, when connected and configured, enable the performance of the functions described in the present disclosure, without limitation as to the type of electronic circuits, as well as software implementations of information and instructions that, when executed by a processor, enable the performance of the functions described in the present disclosure.
  • FIGs. 1-14 One or more of the components, steps, features and/or functions illustrated in FIGs. 1-14 may be rearranged and/or combined into a single component, step, feature or function or embodied in several components, steps, or functions. Additional elements, components, steps, and/or functions may also be added without departing from novel features disclosed herein.
  • the apparatus, devices, and/or components illustrated in FIGs. 1, 2, 4, 7, and/or 8 may be configured to perform one or more of the methods, features, or steps escribed herein.
  • the novel algorithms described herein may also be efficiently implemented in software and/or embedded in hardware.
  • “at least one of: a, b, or c” is intended to cover: a; b; c; a and b; a and c; b and c; and a, b and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des aspects de la présente invention concernent la mise à jour de politiques et de règles pour des dispositifs SA 5G NR. Un procédé comprend : l'obtention de premières informations d'assistance de sélection de tranche de réseau unique (S-NSSAI) à utiliser avec une première connexion de réseau établie pour le compte d'un abonnement à un premier réseau associé à un équipement d'utilisateur (UE), la fourniture des premières S-NSSAI lors de la demande d'établissement d'une première session d'unité de données de protocole (PDU) par le biais de la première connexion de réseau, la réception d'une politique de sélection de routage d'UE (URSP) mise à jour, l'URSP mise à jour comprenant des secondes S-NSSAI à utiliser par l'UE, l'utilisation de la URSP mise à jour pour rafraîchir ou remplacer une URSP précédente conservée pour un abonnement à un second réseau associé à l'UE, et la fourniture des secondes S-NSSAI lors de la demande d'établissement d'une seconde connexion de réseau pour le compte de l'abonnement au second réseau ou lors de la demande d'établissement d'une seconde session PDU pour le compte de l'abonnement au second réseau.
PCT/CN2020/094115 2020-06-03 2020-06-03 Optimisation de mises à jour de politiques ursp sur des dispositifs à deux sim WO2021243598A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/094115 WO2021243598A1 (fr) 2020-06-03 2020-06-03 Optimisation de mises à jour de politiques ursp sur des dispositifs à deux sim

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/094115 WO2021243598A1 (fr) 2020-06-03 2020-06-03 Optimisation de mises à jour de politiques ursp sur des dispositifs à deux sim

Publications (1)

Publication Number Publication Date
WO2021243598A1 true WO2021243598A1 (fr) 2021-12-09

Family

ID=78831595

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/094115 WO2021243598A1 (fr) 2020-06-03 2020-06-03 Optimisation de mises à jour de politiques ursp sur des dispositifs à deux sim

Country Status (1)

Country Link
WO (1) WO2021243598A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4255019A1 (fr) * 2022-03-29 2023-10-04 Apple Inc. Amélioration de politique d'équipement utilisateur, ue, pour politique de sélection de route d'ue, ursp, dans un système de paquets évolué, eps.
WO2023191465A1 (fr) * 2022-03-29 2023-10-05 Samsung Electronics Co., Ltd. Procédés et appareil pour la configuration d'une politique de sélection d'itinéraire

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019032972A1 (fr) * 2017-08-11 2019-02-14 Idac Holdings, Inc. Orientation et commutation de trafic entre de multiples réseaux d'accès
CN110225563A (zh) * 2019-01-31 2019-09-10 华为技术有限公司 网络注册的方法及设备
US20190342761A1 (en) * 2018-04-09 2019-11-07 Huawei Technologies Co., Ltd. Communication Method, Apparatus, and System

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019032972A1 (fr) * 2017-08-11 2019-02-14 Idac Holdings, Inc. Orientation et commutation de trafic entre de multiples réseaux d'accès
US20190342761A1 (en) * 2018-04-09 2019-11-07 Huawei Technologies Co., Ltd. Communication Method, Apparatus, and System
CN110225563A (zh) * 2019-01-31 2019-09-10 华为技术有限公司 网络注册的方法及设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
SPREADTRUM: "User preference has higher priority than NSSP in URSP when UE selects the S- NSSAI for PDU Session Establishment.", 3GPP DRAFT; S2-183415, 3RD GENERATION PARTNERSHIP PROJECT (3GPP); F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, 9 April 2018 (2018-04-09), Sanya, China; 20180416 - 20180420, XP051437461 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4255019A1 (fr) * 2022-03-29 2023-10-04 Apple Inc. Amélioration de politique d'équipement utilisateur, ue, pour politique de sélection de route d'ue, ursp, dans un système de paquets évolué, eps.
WO2023191465A1 (fr) * 2022-03-29 2023-10-05 Samsung Electronics Co., Ltd. Procédés et appareil pour la configuration d'une politique de sélection d'itinéraire

Similar Documents

Publication Publication Date Title
US11985557B2 (en) Signaling for conditional primary secondary cell addition/change configuration
US20230180072A1 (en) Ue enhancement prioritizing 5g nr cell selection
US11552753B2 (en) Enablement of simultaneous beam update across component carriers
US11937135B2 (en) Signaling of delta configuration for handover
US11812512B2 (en) Detecting a change to relay device protocol data unit session configuration
US11611985B2 (en) Grant of resources for downlink and uplink communication via one or more relay user equipment
US20210337381A1 (en) Peer-to-peer link security setup for relay connection to mobile network
WO2021243598A1 (fr) Optimisation de mises à jour de politiques ursp sur des dispositifs à deux sim
US11825373B2 (en) Reference measurement timing selection for wireless communication mobility
WO2021237613A1 (fr) Procédure d'accès aléatoire non autonome accéléré pour la 5g
US12035299B2 (en) Scheduling communication for multiple subscriber identity modules over a single communication link
WO2022205035A1 (fr) Mesure et gestion améliorées de brouillage entre liaisons
US20240015527A1 (en) Receive spatial configuration indication for communication between wireless devices
WO2022047693A1 (fr) Radiomessagerie de dispositifs multiples à l'aide d'une occasion de radiomessagerie commune
US20230247701A1 (en) Coordination of multiple connections with a user equipment using multiple subscriptions
WO2022041036A1 (fr) Mise à jour de flux de trafic à l'aide d'un message de temps de cycle de réception discontinue
WO2021232215A1 (fr) Système et procédé pour retenir un service lte dans une cellule lors du rejet d'une demande de service non autonome
WO2023010271A1 (fr) Préférence de connectivité de réseau d'équipement utilisateur
US11805477B2 (en) Method to reduce recovery time from out-of-service event in dual receive (DR) or dual sim dual access (DSDA) capable user equipment
US20230171590A1 (en) Capability information for a user equipment
US20220007347A1 (en) Shared common beam update across multiple component carriers
WO2023087251A1 (fr) Communication sans fil utilisant des services de multiples tranches de réseau
US20230413136A1 (en) Secondary cell group activation state configuration in multiple secondary cell group configurations
WO2024092591A1 (fr) Localisation de période de commutation pour commutation de transmission
WO2024039961A1 (fr) Multiples réseaux d'accès avec une agrégation non intégrée

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20939402

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20939402

Country of ref document: EP

Kind code of ref document: A1