WO2022021049A1 - Sélection de tranche de réseau basée sur la direction de liaison d'application - Google Patents

Sélection de tranche de réseau basée sur la direction de liaison d'application Download PDF

Info

Publication number
WO2022021049A1
WO2022021049A1 PCT/CN2020/105083 CN2020105083W WO2022021049A1 WO 2022021049 A1 WO2022021049 A1 WO 2022021049A1 CN 2020105083 W CN2020105083 W CN 2020105083W WO 2022021049 A1 WO2022021049 A1 WO 2022021049A1
Authority
WO
WIPO (PCT)
Prior art keywords
network slice
application link
network
data packet
application
Prior art date
Application number
PCT/CN2020/105083
Other languages
English (en)
Inventor
Nan Zhang
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/105083 priority Critical patent/WO2022021049A1/fr
Publication of WO2022021049A1 publication Critical patent/WO2022021049A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/18—Selecting a network or a communication service
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Definitions

  • 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 capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) .
  • a wireless multiple-access communications system may include a number of base stations (BSs) , each simultaneously supporting communications for multiple communication devices, which may be otherwise known as user equipment (UE) .
  • BSs base stations
  • UE user equipment
  • NR next generation new radio
  • LTE long term evolution
  • NR next generation new radio
  • 5G 5 th Generation
  • LTE long term evolution
  • NR next generation new radio
  • NR is designed to provide a lower latency, a higher bandwidth or a higher throughput, and a higher reliability than LTE.
  • NR is designed to operate over a wide array of spectrum bands, for example, from low-frequency bands below about 1 gigahertz (GHz) and mid-frequency bands from about 1 GHz to about 6 GHz, to high-frequency bands such as millimeter wave (mmWave) bands.
  • GHz gigahertz
  • mmWave millimeter wave
  • NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed and shared spectrum. Spectrum sharing enables operators to opportunistically aggregate spectrums to dynamically support high-bandwidth services. Spectrum sharing can extend the benefit of NR technologies to operating entities that may not have access to a licensed spectrum.
  • a method of wireless communication includes receiving an indication of establishment of an application link between the UE and a 5G network for transmitting a data packet. Further, the method includes selecting a network slice for transmitting the data packet based at least in part on a direction of the application link for transmitting the data packet. The method further comprises establishing or selecting a packet data unit (PDU) session over the selected network slice for the transmission of the data packet.
  • PDU packet data unit
  • an apparatus comprising a transceiver configured to receive an indication of establishment of an application link between the UE and a 5G network for transmitting a data packet.
  • the apparatus also comprises a processor configured to select a network slice for transmission of the data packet based at least in part on a direction of the application link for transmitting the data packet. Further, the processor is configured to establish or select a packet data unit (PDU) session over the selected network slice for the transmission of the data packet.
  • PDU packet data unit
  • a non-transitory computer-readable medium having program code recorded thereon is disclosed.
  • the program code can include code for causing the user equipment (UE) to receive an indication of establishment of an application link between the UE and a 5G network for transmitting a data packet.
  • the program code includes code for causing the UE to select a network slice for transmission of the data packet based at least in part on a direction of the application link for transmitting the data packet.
  • the program code comprises code for causing the UE to establish or select a packet data unit (PDU) session over the selected network slice for the transmission of the data packet.
  • PDU packet data unit
  • an apparatus includes means for receiving an indication of establishment of an application link between the UE and a 5G network for transmitting a data packet.
  • the apparatus comprises means for selecting a network slice for transmission of the data packet based at least in part on a direction of the application link for transmitting the data packet.
  • the apparatus comprises means for establishing or selecting a packet data unit (PDU) session over the selected network slice for the transmission of the data packet.
  • PDU packet data unit
  • the network slice is selected based at least in part on a UE route selection policy (URSP) including an application link direction rule for selecting the network slice based on the direction of the application link.
  • URSP UE route selection policy
  • the network slice includes an ultra-reliable low-latency communication (uRLLC) network slice, an enhanced mobile broadband (eMBB) network slice or massive machine type communication (mMTC) network slice.
  • direction of the application link includes an uplink (UL) direction.
  • the network slice can be an ultra-reliable low-latency communication (uRLLC) network slice.
  • the direction of the application link includes a downlink (DL) direction.
  • the network slice can be an enhanced mobile broadband (eMBB) network slice.
  • indication is received from a remote server of an application linked to the UE via the application link. In some aspects, the indication is received from the 5G network or the UE. In some aspects, the data packet can be tagged with an application link direction tag based on the direction of the application link, and the network slice can be selected based at least in part on the application link direction tag.
  • FIG. 1 illustrates a wireless communication network according to some embodiments of the present disclosure.
  • FIG. 2 illustrates a wireless communication network implementing selection of network slicing instances according to some embodiments of the present disclosure.
  • FIG. 3 is signaling diagram illustrating a communication method with selection of network slicing instances according to some embodiments of the present disclosure.
  • FIG. 4 is a block diagram of a user equipment (UE) according to some embodiments of the present disclosure.
  • FIG. 5 is a block diagram of an exemplary base station (BS) according to some embodiments of the present disclosure.
  • FIG. 6 is a flow diagram of a communication method according to some embodiments of the present disclosure.
  • This application relates to wireless communication systems, and more particularly to the selection of network slicing instances based on the direction of an application link.
  • the techniques and apparatus may be used for wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single-carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, 5 th Generation (5G) or new radio (NR) networks, as well as other communications networks.
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal FDMA
  • SC-FDMA single-carrier FDMA
  • LTE Long Term Evolution
  • GSM Global System for Mobile Communications
  • 5G 5 th Generation
  • NR new radio
  • An OFDMA network may implement a radio technology such as evolved UTRA (E-UTRA) , Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and the like.
  • E-UTRA evolved UTRA
  • IEEE Institute of Electrical and Electronics Engineers
  • GSM Global System for Mobile communications
  • LTE long term evolution
  • UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided from an organization named “3rd Generation Partnership Project” (3GPP)
  • cdma2000 is described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • 3GPP 3rd Generation Partnership Project
  • 3GPP long term evolution LTE
  • LTE long term evolution
  • the 3GPP may define specifications for the next generation of mobile networks, mobile systems, and mobile devices.
  • the present disclosure is concerned with the evolution of wireless technologies from LTE, 4G, 5G, NR, and beyond with shared access to wireless spectrum between networks using a collection of new and different radio access technologies or radio air interfaces.
  • the improved latency, reliability, bandwidth, and/or throughput in NR enable various types of network deployments and/or services such as enhanced mobile broadband (eMBB) , ultra-reliable, low-latency communication (uRLLC) , and/or massive machine-type communications (mMTCs) or Internet of Things (IoT) services.
  • eMBB enhanced mobile broadband
  • uRLLC ultra-reliable, low-latency communication
  • mMTCs massive machine-type communications
  • IoT Internet of Things
  • the different types of services may have different traffic requirements (e.g., latency, bandwidth, reliability, and/or throughput) .
  • the 5G core network can apply network slicing to create isolated virtual networks over which different traffic streams or flows (e.g., from the different services) can be communicated.
  • Different network slices may have different traffic characteristics (e.g., latency, bandwidth, reliability, and/or throughput) tailored to the specific needs of the services being served.
  • a network may include a network slice for eMBB services requiring a high bandwidth, a network slice for URLLC services requiring a low latency, and a network slice for IoT services with small data transfer, but a large number of registered devices.
  • 5G networks contemplate diverse deployments, diverse spectrum, and diverse services and devices that may be implemented using an OFDM-based unified, air interface.
  • further enhancements to LTE and LTE-A are considered in addition to development of the new radio technology for 5G NR networks.
  • the 5G NR will be capable of scaling to provide coverage (1) to a massive Internet of things (IoTs) with an ultra-high density (e.g., ⁇ 1M nodes/km 2 ) , ultra-low complexity (e.g., ⁇ 10s of bits/sec) , ultra-low energy (e.g., ⁇ 10+ years of battery life) , and deep coverage with the capability to reach challenging locations; (2) including mission-critical control with strong security to safeguard sensitive personal, financial, or classified information, ultra-high reliability (e.g., ⁇ 99.9999%reliability) , ultra-low latency (e.g., ⁇ 1 ms) , and users with wide ranges of mobility or lack thereof; and (3) with enhanced mobile broadband including extreme high capacity (e.g., ⁇ 10 Tbps/km 2 ) , extreme data rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates) , and deep awareness with advanced discovery and optimizations.
  • IoTs Internet of things
  • the 5G NR may be implemented to use optimized OFDM-based waveforms with scalable numerology and transmission time interval (TTI) ; having a common, flexible framework to efficiently multiplex services and features with a dynamic, low-latency time division duplex (TDD) /frequency division duplex (FDD) design; and with advanced wireless technologies, such as massive multiple input, multiple output (MIMO) , robust millimeter wave (mmWave) transmissions, advanced channel coding, and device-centric mobility.
  • TTI transmission time interval
  • MIMO massive multiple input, multiple output
  • mmWave millimeter wave
  • Scalability of the numerology in 5G NR with scaling of subcarrier spacing, may efficiently address operating diverse services across diverse spectrum and diverse deployments.
  • subcarrier spacing may occur with 15 kHz, for example over 5, 10, 20 MHz, and the like bandwidth (BW) .
  • BW bandwidth
  • subcarrier spacing may occur with 30 kHz over 80/100 MHz BW.
  • the subcarrier spacing may occur with 60 kHz over a 160 MHz BW.
  • subcarrier spacing may occur with 120 kHz over a 500 MHz BW.
  • the scalable numerology of the 5G NR facilitates scalable TTI for diverse latency and quality of service (QoS) requirements. For example, shorter TTI may be used for low latency and high reliability, while longer TTI may be used for higher spectral efficiency.
  • QoS quality of service
  • 5G NR also contemplates a self-contained integrated subframe design with uplink/downlink scheduling information, data, and acknowledgement in the same subframe.
  • the self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink/downlink that may be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet the current traffic needs.
  • an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways.
  • an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein.
  • such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein.
  • a method may be implemented as part of a system, device, apparatus, and/or as instructions stored on a computer readable medium for execution on a processor or computer.
  • an aspect may comprise at least one element of a claim.
  • a UE can receive service from a data network via a packet data unit (PDU) session that may belong to a single specific network slice, or an instance thereof. That is, the PDU session can be a logical connection between the UE and the data network and may associate the UE to the data network that provides the service to the UE.
  • PDU packet data unit
  • a network slice can be a collection of logical network functions (NFs) that support the communication service requirements of a particular network service.
  • NFs logical network functions
  • the network slice can be an ultra-reliable low-latency communication (uRLLC) network slice, an enhanced mobile broadband (eMBB) network slice or a massive machine type communication (mMTC) network slice, as described in the 3GPP standard document TS 28.531, titled “3 rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Provisioning (Release 15) , ” version 15.2.0, March, 2019, which is incorporated herein by reference in its entirety.
  • the NFs may provide the functions of a router, a switch, a gateway, a firewall, a load balancer, a storage, a server, etc.
  • the NFs can be implemented as network elements on dedicated hardware, software executing on dedicated hardware, and/or virtualized functions instantiated on appropriate platforms (e.g., in a cloud infrastructure) .
  • the network may be a NR network and may include NFs such as but not limited to a policy control function (PCF) .
  • PCF policy control function
  • a UE’s selection of PDU sessions for communicating to a network can be controlled by a UE access selection and PDU session selection related policy control that may allow the network and/or the PCF to configure the UE with a UE route selection policy (URSP) that may be related to applications and PDU sessions.
  • the URSP can include information matching certain user data packet traffic (e.g., applications) to PDU session connectivity parameters.
  • an application can be defined in the URSP rule by “traffic descriptor” parameters including but not limited to a data network name (DNN) , an application identifier (ID) , IP 3 tuples (e.g., IP address or IPv6 network prefix, port number, protocol ID of the protocol above IP) , and/or non-IP descriptors (e.g., descriptor (s) for destination information of non-IP traffic) .
  • the URSP may also include policy components such as the network slice selection policy (NSSP) that may include rules configured to allow the UE to associate the matching application with single network slice assistance information (S-NSSAI) descriptor that can identify a network slice across the data network and the UE.
  • NSSP network slice selection policy
  • S-NSSAI single network slice assistance information
  • an NSSP rule may associate or match an application to specific DNN or specific network slice (or an instance thereof) .
  • the URSP may also include other sets of rules, each rule mapped to a different PDU session as described in the 3GPP document TS 23.503, titled “3 rd Generation Partnership Project; Technical Specification Group Service and System Aspects; Policy and Charging Control Framework for the 5G System; Stage 2 (Release 15) , ” version 15.5.0, March 25, 2019, which is incorporated herein by reference in its entirety.
  • the URSP can be used by the UE for various purposes, such as but not limited to, determining whether a new PDU session may be established or an existing one may be used for an application started by the UE if an application can use an already established PDU session.
  • the matching of an application to a specific network slice or a specific network slicing instance may not be based on a direction of a network link for the application. That is, NSSP rule may not be configured to route an application to different network slicing instances based on the direction of the application link direction. For example, once an application is matched with a network slicing instance (e.g., one of eMBB, uRLLC or mMTC) , the same network slicing instance may be used for both uplink (UL) and downlink (DL) directions of the application. Such routing, however, may not be efficient, because in some cases, a more efficient approach may be to use different network slicing instances for the UL and DL transmissions.
  • a network slicing instance e.g., one of eMBB, uRLLC or mMTC
  • the application may include cloud augmented reality/virtual reality (AR/VR) streaming, cloud gaming, video live streaming (e.g., 4K streaming) , etc., where the DL transmission may be better served by a network slicing instance that may be particularly configured to have high bandwidth (e.g., eMBB network slice) and the UL transmission may be better served by a network slicing instance that may be particularly configured to have robust reliability and low latency (e.g., uRLLC network slice) .
  • AR/VR cloud augmented reality/virtual reality
  • cloud gaming e.g., 4K streaming
  • 4K streaming video live streaming
  • some embodiments of the present application describe mechanisms for allowing a UE to select network slicing instances based on the direction of an application link (e.g., downlink or uplink) linking the UE to a data network.
  • the matching of an application or data packet traffic to a specific network slice or a specific network slicing instance may be based on a direction of a network link linking the UE to the network.
  • NSSP rule may be configured to route an application to different network slicing instances based on the direction of the application or data packet traffic link.
  • the NSSP rule traffic descriptor may include application link direction (e.g., UL or DL) as one of the parameters, such that the NSSP can allow the UE to match an application with a network slice or network slicing instance based on a direction of the application link. That is, the UE may be allowed by a NSSP rule to select a first network slice for a first link direction and a second network slice for the opposite direction, and the UE may establish (e.g., concurrently) separate PDU sessions with different application link directions over the two network slices.
  • application link direction e.g., UL or DL
  • the NSSP rule descriptor may include at least the parameters DNN , application ID, application link direction (UL or DL) , IP 3 tuple, Non-IP description, and UE may be configured to select an eMBB network slicing instance to establish a PDU session in a DL direction and an uRLLC network slicing instance to establish a PDU session in an UL direction.
  • separating UL and DL direction traffic to separate network slicing instances may allow one to meet the requirements of an application traffic in that particular direction, because the different network slices may have different traffic characteristics (e.g., latency, bandwidth, reliability, and/or throughput) tailored to the specific needs of the application or data packet traffic direction being served. That is, application or data packet traffic in different application link directions can be routed to a network slice that may be configured to better serve that type of traffic more efficiently than other types of network slices.
  • traffic characteristics e.g., latency, bandwidth, reliability, and/or throughput
  • aspects of the present disclosure allow UEs to select network slicing instances based on the service requirements or needs of a particular direction of an application or data packet traffic (e.g., eMBB for high bandwidth downloads, uRLLC for low latency for uploads, mMTC for small data uplink transfers, etc. ) , which allows the UEs to better realize the capabilities of new radio networks such as but not limited to improved latency, reliability, bandwidth, and/or throughput.
  • eMBB for high bandwidth downloads
  • uRLLC low latency for uploads
  • mMTC small data uplink transfers
  • FIG. 1 illustrates a wireless communication network 100 according to some embodiments of the present disclosure.
  • the network 100 may be a 5G network.
  • the network 100 includes a number of base stations (BSs) 105 (individually labeled as 105a, 105b, 105c, 105d, 105e, and 105f) and other network entities.
  • a BS 105 may be a station that communicates with UEs 115 and may also be referred to as an evolved node B (eNB) , a next generation eNB (gNB) , an access point, and the like.
  • eNB evolved node B
  • gNB next generation eNB
  • Each BS 105 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to this particular geographic coverage area of a BS 105 and/or a BS subsystem serving the coverage area, depending on the context in which the term is used.
  • a BS 105 may provide communication coverage for a macro cell or a small cell, such as a pico cell or a femto cell, and/or other types of cell.
  • a macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a small cell such as a pico cell, would generally cover a relatively smaller geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider.
  • a small cell such as a femto cell, would also generally cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG) , UEs for users in the home, and the like) .
  • a BS for a macro cell may be referred to as a macro BS.
  • a BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS or a home BS. In the example shown in FIG.
  • the BSs 105d and 105e may be regular macro BSs, while the BSs 105a-105c may be macro BSs enabled with one of three dimension (3D) , full dimension (FD) , or massive MIMO.
  • the BSs 105a-105c may take advantage of their higher dimension MIMO capabilities to exploit 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity.
  • the BS 105f may be a small cell BS which may be a home node or portable access point.
  • a BS 105 may support one or multiple (e.g., two, three, four, and the like) cells.
  • the network 100 may support synchronous or asynchronous operation.
  • the BSs may have similar frame timing, and transmissions from different BSs may be approximately aligned in time.
  • the BSs may have different frame timing, and transmissions from different BSs may not be aligned in time.
  • the UEs 115 are dispersed throughout the wireless network 100, and each UE 115 may be stationary or mobile.
  • a UE 115 may also be referred to as a terminal, a mobile station, a subscriber unit, a station, or the like.
  • a UE 115 may be a cellular phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a wireless local loop (WLL) station, or the like.
  • PDA personal digital assistant
  • WLL wireless local loop
  • a UE 115 may be a device that includes a Universal Integrated Circuit Card (UICC) .
  • a UE may be a device that does not include a UICC.
  • UICC Universal Integrated Circuit Card
  • the UEs 115 that do not include UICCs may also be referred to as IoT devices or internet of everything (IoE) devices.
  • the UEs 115a-115d are examples of mobile smart phone-type devices accessing network 100.
  • a UE 115 may also be a machine specifically configured for connected communication, including machine type communication (MTC) , enhanced MTC (eMTC) , narrowband IoT (NB-IoT) and the like.
  • MTC machine type communication
  • eMTC enhanced MTC
  • NB-IoT narrowband IoT
  • the UEs 115e-115k are examples of various machines configured for communication that access the network 100.
  • a UE 115 may be able to communicate with any type of the BSs, whether macro BS, small cell, or the like. In FIG.
  • a lightning bolt (e.g., communication links) indicates wireless transmissions between a UE 115 and a serving BS 105, which is a BS designated to serve the UE 115 on the downlink and/or uplink, or desired transmission between BSs, and backhaul transmissions between BSs.
  • the BSs 105a-105c may serve the UEs 115a and 115b using 3D beamforming and coordinated spatial techniques, such as coordinated multipoint (CoMP) or multi-connectivity.
  • the macro BS 105d may perform backhaul communications with the BSs 105a-105c, as well as small cell, the BS 105f.
  • the macro BS 105d may also transmits multicast services which are subscribed to and received by the UEs 115c and 115d.
  • Such multicast services may include mobile television or stream video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.
  • the BSs 105 may also communicate with a core network.
  • the core network may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions.
  • IP Internet Protocol
  • At least some of the BSs 105 (e.g., which may be an example of a gNB or an access node controller (ANC) ) may interface with the core network through backhaul links (e.g., NG-C, NG-U, etc. ) and may perform radio configuration and scheduling for communication with the UEs 115.
  • the BSs 105 may communicate, either directly or indirectly (e.g., through core network) , with each other over backhaul links (e.g., X1, X2, etc. ) , which may be wired or wireless communication links.
  • the network 100 may also support mission critical communications with ultra-reliable and redundant links for mission critical devices, such as the UE 115e, which may be a drone. Redundant communication links with the UE 115e may include links from the macro BSs 105d and 105e, as well as links from the small cell BS 105f.
  • UE 115f e.g., a thermometer
  • UE 115g e.g., smart meter
  • UE 115h e.g., wearable device
  • the network 100 may also provide additional network efficiency through dynamic, low-latency TDD/FDD communications, such as in a vehicle-to-vehicle (V2V) .
  • V2V vehicle-to-vehicle
  • the network 100 utilizes OFDM-based waveforms for communications.
  • An OFDM-based system may partition the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, bins, or the like. Each subcarrier may be modulated with data.
  • the subcarrier spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system BW.
  • the system BW may also be partitioned into subbands. In other instances, the subcarrier spacing and/or the duration of TTIs may be scalable.
  • the BSs 105 can assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RB) ) for downlink (DL) and uplink (UL) transmissions in the network 100.
  • DL refers to the transmission direction from a BS 105 to a UE 115
  • UL refers to the transmission direction from a UE 115 to a BS 105.
  • the communication can be in the form of radio frames.
  • a radio frame may be divided into a plurality of subframes or slots, for example, about 10. Each slot may be further divided into mini-slots. In a FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands.
  • each subframe includes a UL subframe in a UL frequency band and a DL subframe in a DL frequency band.
  • UL and DL transmissions occur at different time periods using the same frequency band.
  • a subset of the subframes (e.g., DL subframes) in a radio frame may be used for DL transmissions and another subset of the subframes (e.g., UL subframes) in the radio frame may be used for UL transmissions.
  • each DL or UL subframe may have pre-defined regions for transmissions of reference signals, control information, and data.
  • Reference signals are predetermined signals that facilitate the communications between the BSs 105 and the UEs 115.
  • a reference signal can have a particular pilot pattern or structure, where pilot tones may span across an operational BW or frequency band, each positioned at a pre-defined time and a pre-defined frequency.
  • a BS 105 may transmit cell specific reference signals (CRSs) and/or channel state information –reference signals (CSI-RSs) to enable a UE 115 to estimate a DL channel.
  • CRSs cell specific reference signals
  • CSI-RSs channel state information –reference signals
  • a UE 115 may transmit sounding reference signals (SRSs) to enable a BS 105 to estimate a UL channel.
  • Control information may include resource assignments and protocol controls.
  • Data may include protocol data and/or operational data.
  • the BSs 105 and the UEs 115 may communicate using self-contained subframes.
  • a self-contained subframe may include a portion for DL communication and a portion for UL communication.
  • a self-contained subframe can be DL-centric or UL-centric.
  • a DL-centric subframe may include a longer duration for DL communication than for UL communication.
  • a UL-centric subframe may include a longer duration for UL communication than for UL communication.
  • the network 100 may be an NR network deployed over a licensed spectrum.
  • the BSs 105 can transmit synchronization signals (e.g., including a PSS and an SSS) in the network 100 to facilitate synchronization.
  • the BSs 105 can broadcast system information associated with the network 100 (e.g., including a MIB, RMSI, and other system information (OSI) ) to facilitate initial network access.
  • the BSs 105 may broadcast the PSS, the SSS, and/or the MIB in the form of SSBs over a PBCH and may broadcast the RMSI and/or the OSI over a physical downlink shared channel (PDSCH) .
  • PDSCH physical downlink shared channel
  • a UE 115 attempting to access the network 100 may perform an initial cell search by detecting a PSS from a BS 105.
  • the PSS may enable synchronization of period timing and may indicate a physical layer identity value.
  • the UE 115 may then receive a SSS.
  • the SSS may enable radio frame synchronization, and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell.
  • the PSS and the SSS may be located in a central portion of a carrier or any suitable frequencies within the carrier.
  • the UE 115 may receive a MIB.
  • the MIB may include system information for initial network access and scheduling information for RMSI and/or OSI.
  • the UE 115 may receive RMSI and/or OSI.
  • the RMSI and/or OSI may include radio resource control (RRC) information related to random access channel (RACH) procedures, paging, control resource set (CORESET) for physical downlink control channel (PDCCH) monitoring, physical uplink control channel (PUCCH) , physical uplink shared channel (PUSCH) , power control, and SRS.
  • RRC radio resource control
  • the UE 115 can perform a random access procedure to establish a connection with the BS 105.
  • the UE 115 may transmit a random access preamble and the BS 105 may respond with a random access response.
  • the UE 115 may transmit a connection request to the BS 105 and the BS 105 may respond with a connection response (e.g., contention resolution message) .
  • the UE 115 and the BS 105 can enter a normal operation stage, where operational data may be exchanged.
  • the BS 105 may schedule the UE 115 for UL and/or DL communications.
  • the BS 105 may transmit UL and/or DL scheduling grants to the UE 115 via a PDCCH.
  • the BS 105 may transmit a DL communication signal to the UE 115 via a PDSCH according to a DL scheduling grant.
  • the UE 115 may transmit a UL communication signal to the BS 105 via a PUSCH and/or PUCCH according to a UL scheduling grant.
  • the network 100 may implement network slicing to create multiple isolated virtual networks or independent logical network slices to support a variety of application services in the network 100.
  • some UEs 115 e.g., the UEs115a-115d
  • eMBB enhanced mobile broadband
  • some UEs 115 e.g., the UEs 115e-115h
  • some other UEs 115 e.g., the UEs 115i-115k
  • some UEs 115 may require different types of services (e.g., including eMBB services and URLLC services) simultaneously in the network 100.
  • Each service may have a set of specific traffic requirements (e.g., latency, bandwidth, throughput, and/or reliability) .
  • the network 100 may serve services having different traffic requirements over different network slices. Network slicing provides the flexibility and adaptability for the network 100 to tailor each network slice according to the specific needs of the services being served. Network slicing mechanisms are described in greater detail below in FIG. 2.
  • FIG. 2 illustrates a wireless communication network 200 implementing network slicing according to some embodiments of the present disclosure.
  • the network 200 may be substantially similar to the network 100.
  • the network 200 includes a core network 204, a radio access network (RAN) 202, and a plurality of UEs 215.
  • the UEs 215 may be substantially similar to the UEs 115.
  • the core network 204 is logically partitioned into a plurality of network slices 210.
  • the RAN 202 may include BSs similar to the BSs 105 that serve the UEs 215 by connecting the UEs 215 to the network slices 210.
  • FIG. 2 illustrates three network slices 210a, 210b, and 210c and a UE 215.
  • the network 200 may include any suitable number of network slices (e.g., about 2, 4, 5, or more) and may serve any suitable number of UEs 215 (e.g., up to millions) . Further, in some examples, the network slicing may also be applied to the RAN 202 in addition to the core network 204.
  • a network slice 210 is a collection of logical network functions (NFs) that support the communication service requirements of a particular network service.
  • the NFs may provide the functions of a router, a switch, a gateway, a firewall, a load balancer, a storage, and/or a server.
  • the NFs can be implemented as network elements on dedicated hardware, software executing on dedicated hardware, and/or virtualized functions instantiated on appropriate platforms (e.g., in a cloud infrastructure) .
  • the core network 204 may be a 5G core network and may include NFs such as an authentication server function (AUSF) , an access and mobility management function (AMF) , a session management function (SMF) , a policy control function (PCF) , a user plane function (UPF) , an application functions (AFs) , a unified data repository (UDR) , an unstructured data storage network function (UDSF) , a network exposure function (NEF) , an NF repository function (NRF) , a unified data management function (UDM) , and/or a network slice selection function (NSSF) .
  • a network slice 210 may include instances of one or more of the 5G core NFs.
  • Different network slices 210 may include different subsets of the 5G core NFs.
  • each network slice 210 may be configured to include NFs that are required to serve a particular type of service.
  • the network slices 210 are isolated from each other so that one network slice 210 may not impact the performance and/or the functions of another network slice 210.
  • a network slice 210 may be configured to function as a virtual network to serve a particular type of network traffic.
  • the network slice 210a may be a eMBB network slice
  • the network slice 210b may be a URLLC network slice
  • the network slice 210c may be an IoT or mMTC network slice as described in the 3GPP standard document TS 28.531, titled “3 rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Provisioning (Release 15) , ” version 15.2.0, March, 2019, which is incorporated herein by reference in its entirety.
  • the eMBB network slice 210a may be configured to serve services with a high bandwidth requirement.
  • the URLLC network slice 210b may be configured to serve services that require a low latency and/or a high reliability.
  • the IoT or mMTC network slice 210c may be configured to serve services with small data transfer (e.g., a few bytes to tens of bytes) , but may require a large capacity to register and serve a large number of devices (e.g., up to millions of devices) .
  • the network slices 210 may be defined by operators.
  • an entity may serve multiple instances of a service over different network slices 210, where different instances may provide the service at different bandwidth and/or latency levels.
  • an operator may configure two eMBB network slices 210, where one eMBB network slice 210 may have higher bandwidth and/or a lower latency than the other eMBB network slice 210 for serving high-valued customers.
  • a UE 215 may be served by one or more network slices 210 at a time.
  • the UE 215 may be a smart phone-typed device requiring high-bandwidth services and thus may be served by the eMBB network slice 210a.
  • the UE 215 may be a self-driving car requiring V2V and/or V2X communication services that are sensitive to network latency and/or reliability and thus may be served by the URLLC network slice 210b.
  • the UE 215d may be a machine-type device (e.g., smart meter or instrument) requiring services for data logging or reading and/or control command communications with a small data size and thus may be served by the IoT network slice 210c.
  • a UE 215 may require different services with different traffic flow requirements at the same time.
  • the UE 215 may be performing a file transfer while a V2V, V2X, and/or gaming application is ongoing.
  • the file transfer may require a high bandwidth, while the V2V, V2X, and/or gaming may be sensitive to network latency.
  • the UE 215 may be served by the eMBB network slice 210a for the high-bandwidth file transfer and the URLLC network slice 210b for the low-latency V2V, V2X, or gaming application.
  • a UE 215 may receive a service in the network 200 via a PDU session 230 or 240.
  • Each PDU session 230 or 240 may belong to a single specific network slice 210 or a single specific network slice 210 instance.
  • the PDU session 230 or 240 may associate the UE 215 to a data network that provides the service to the UE 215.
  • the PDU session 230 or 240 is a logical connection between the UE 215 and the data network.
  • the PDU session 230 or 240 may be established based on a request from the UE 215.
  • the core network 204 may allocate entities that can serve the traffic requirement (e.g., latency and/or bandwidth) of the PDU session 230 or 240.
  • the core network 204 may assign a slice identifier (ID) to the PDU session 230 or 240.
  • ID slice identifier
  • the data transmission for a service can take place after the PDU session 230 or 240 is established in a network slice 210.
  • the PDU session 230 or 240 may include one or more PDU streams 232 (e.g., a PDU stream 232a, a PDU stream 232b, ..., a PDU stream 232n) or one or more PDU streams 242 (e.g., a PDU stream 242a, a PDU stream 242b, ..., a PDU stream 242n) .
  • Each PDU stream 232 or 242 may provide a certain QoS.
  • the UE 215 served by the eMBB network slice 210 may have a file communicated over one PDU stream 232a and an ongoing voice call over another PDU stream 242b, where the PDU streams 232a and 242b may provide different QoSs.
  • the PDU sessions or streams can be application link direction specific.
  • the UE 215 may download massive data such as VR streaming data using a DL PDU session 232 over eMBB network slice 210a while uploading low latency data using an UL PDU session 242 via uRLLC network slice 210b.
  • the selection of a network slice based on the direction of an application or or data packet traffic link and establishment of PDU sessions in the network slice to service the application or data packet traffic is further discussed below with reference to FIG. 3.
  • FIG. 3 is signaling diagram illustrating a communication method with selection of network slicing instances according to some embodiments of the present disclosure.
  • the method 300 may be implemented by a UE 302, such as the UEs 115 and/or 215, in a network, such as the network 100 and/or 200 that can include a BS (e.g., such as BS 205) and the core network (e.g., core network 204) which may include an access and mobility management function (AMF) .
  • the BS and the AMF may generally be referred to as the network side.
  • Steps of the method 300 can be executed by computing devices (e.g., a processor, processing circuit, and/or other suitable component) of the BS, the UE, and an AMF component.
  • computing devices e.g., a processor, processing circuit, and/or other suitable component
  • the method 300 includes a number of enumerated steps, but embodiments of the method 300 may include additional steps before, after, and in between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.
  • the UE 302 may start an application executing thereon that is configured to generate data for transmission to the network 304 in an UL direction and receive data transmitted from the network 304 in the DL direction.
  • the application may be hosted on a remote server that may be in communication with the UE 302 and may be executing on the remote server and/or the UE 302.
  • the application may have different service requirements for different application link directions.
  • the application may have the service requirements of a URLLC application (e.g., V2V, V2X, gaming, or remote healthcare related) in one direction (e.g., UL direction) and the service requirements of a eMBB application (e.g., file transfer and/or streaming) or a IoT application (e.g., industrial automation related) in the other direction (e.g., DL direction) .
  • a URLLC application e.g., V2V, V2X, gaming, or remote healthcare related
  • eMBB application e.g., file transfer and/or streaming
  • IoT application e.g., industrial automation related
  • the application may have different network slicing instances requirements based on the direction of the application link.
  • the application can be an application with a low-latency and/or high-reliability requirement for UL transmissions and high-bandwidth requirement for DL transmissions, examples of such applications including video streaming applications, video streaming applications, AR/VR/extended reality (XR) applications, etc.
  • the UE can be a smartphone requiring eMBB network slicing instances to satisfy downlink (DL) high-bandwidth requirements and uRLLC network slicing instances to satisfy uplink (UL) low-latency and/or high-reliability requirements simultaneously or nearly simultaneously for proper execution of the application.
  • eMBB and uRLLC network slicing instances are given here as non-limiting examples and that proper execution of the application may require any two different network slicing instances for the UL and DL directions of data transmissions.
  • the UE 302 can be an industrial sensor executing an application requiring IoT or mMTC network slicing instances for UL transmissions and uRLLC network slicing instances for DL transmissions.
  • the UE 302 may identify or select a suitable network slice or network slicing instance for the application based on the direction of the application link.
  • the network slice can be selected based at least in part on a URSP that includes an application link direction rule for selecting the network slice based on the direction of the application link.
  • the URSP may include NSSP rules that can be configured to allow the UE 302 to associate the application with a single network slice assistance information (S-NSSAI) descriptor that can identify a network slice for the application or data packet traffic to the network 304.
  • S-NSSAI single network slice assistance information
  • the UE 302 may identify or select a suitable network slice or network slicing instance based on the NSSP rule that is configured to associate or match the application to the network slice (or an instance thereof) .
  • the NSSP rule may include a traffic descriptor specifying the transmission or link direction of the application (e.g., UL or DL) .
  • the UE 302 may select or identify the network slice to serve the application or data packet traffic. For example, as discussed above, if the service requirements of the application in one direction include low-latency and/or high-reliability requirement, then the UE 302 may identify uRLLC network slice as a network slice for serving the application traffic in that direction.
  • the UE 302 may select or identify a different network slice for serving the application or data packet traffic in the opposite direction if the service requirements of the application in the opposite direction are different. For instance, the UE 302 may identify eMBB network slice as a network slice for serving the application or data packet traffic in the opposite direction if the service requirements of the application in the opposite direction include high-bandwidth requirements.
  • the UE 302 may tag the data packet to be transmitted over the application link with an application link direction tag corresponding to the direction of the application link and select the network slice or network slicing instance based at least in part on the application link direction tag. For example, if the application link direction is UL or DL, the UE may tag the data packet with an application link direction tag indicating that the data packet is to be transmitted via an UL or DL directed application link, respectively.
  • the UE 302 may then refer to the application link direction tag of the data packet and establish or select the PDU session over the network slice or network slicing instance that corresponds to the application link direction tag.
  • an application link may be established between UE 302 and a NR network to service an application (e.g., video gaming, AR/VR streaming, etc. ) that may have data transmission service requirements of low-latency and/or high-reliability in the UL direction and high bandwidth in the DL direction.
  • the UE may tag such data packet with a tag indicating that given direction.
  • the UE may select a network slice based at least in part on the direction tag of the data packet.
  • the UE 302 may select an uRLLC network slice when the direction tag of the data packet indicates UL direction and an eMBB network slice when the direction tag of the data packet indicates DL direction.
  • the UE 302 may then establish or select a PDU session over the selected network slice or a network slicing instance that corresponds to the direction of the data packet tag for transmitting the data packet. For example, if the data packet is tagged with a tag indicating UL direction, then the UE 302 may establish or select a PDU session over the uRLLC network slice to route the data packet from the application to the NR network. As another example, if the data packet is tagged with a tag indicating DL direction, then the UE 302 may establish or select a PDU session over the eMBB network slice to route the data packet from the NR network to the application.
  • the UE 302 may establish a PDU session over the network slice or network slicing instance identified at step 320.
  • the UE 302 may transmit an RRC connection setup completion message to the BS of the network 304.
  • the RRC connection setup completion message may include a non-access stratum (NAS) registration request, which can include requested-NSSAI.
  • the requested-NSSAI may indicate a network slice requested by the UE, for example, the application link direction specific network slice identified by the UE at step 320.
  • the UE 302 may request the network 304 for a network slice.
  • the network 304 e.g., the AMF of the core network of the network 304
  • the UE 302 may then establish a PDU session in the application link direction over the allowed network slice for communicating the application or data packet traffic in that direction.
  • the UE 302 may establish a first PDU session in an UL direction over a first network slice and a second PDU session in a DL direction over a second network slice to communicate application or data packet traffic from and to the UE, respectively, where the first network slice and the second network slice can be different and identified at step 320 based on the application link direction specific requirements of the application.
  • the UE 302 and the network 304 may transmit and/or receive application data traffic over the established PDU sessions.
  • FIG. 4 is a block diagram of an exemplary UE 400 according to embodiments of the present disclosure.
  • the UE 400 may be a UE 115 or 215 as discussed above in FIG. 1 or FIG. 2, respectively.
  • the UE 400 may include a processor 402, a memory 404, a network slice selection (NSS) module 408, a transceiver 410 including a modem subsystem 412 and a radio frequency (RF) unit 414, and one or more antennas 416.
  • NSS network slice selection
  • RF radio frequency
  • the processor 402 may include a central processing unit (CPU) , a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
  • the processor 402 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the memory 404 may include a cache memory (e.g., a cache memory of the processor 402) , random access memory (RAM) , magnetoresistive RAM (MRAM) , read-only memory (ROM) , programmable read-only memory (PROM) , erasable programmable read only memory (EPROM) , electrically erasable programmable read only memory (EEPROM) , flash memory, solid state memory device, hard disk drives, other forms of volatile and non-volatile memory, or a combination of different types of memory.
  • the memory 404 includes a non-transitory computer-readable medium.
  • the memory 404 may store, or have recorded thereon, instructions 406.
  • the instructions 406 may include instructions that, when executed by the processor 402, cause the processor 402 to perform the operations described herein with reference to the UEs 115 and/or 215 in connection with embodiments of the present disclosure, for example, aspects of FIGS. 2, 3 and 6. Instructions 406 may also be referred to as program code.
  • the program code may be for causing a wireless communication device to perform these operations, for example by causing one or more processors (such as processor 402) to control or command the wireless communication device to do so.
  • the terms “instructions” and “code” should be interpreted broadly to include any type of computer-readable statement (s) .
  • instructions and code may refer to one or more programs, routines, sub-routines, functions, procedures, etc. “Instructions” and “code” may include a single computer-readable statement or many computer-readable statements.
  • the NSS module 408 may be implemented via hardware, software, or combinations thereof.
  • NSS module 408 may be implemented as a processor, circuit, and/or instructions 406 stored in the memory 404 and executed by the processor 402.
  • the NSS module 408 can be integrated within the modem subsystem 412.
  • the NSS module 408 can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 412.
  • the NSS module 408 may be used for various aspects of the present disclosure, for example, aspects of FIGS. 2, 3 and 6.
  • the NSS module may be configured to select or identify a network slice for transmission of an application or data packet traffic based at least in part on the application link direction of the data packet or traffic.
  • the transceiver 410 may include the modem subsystem 412 and the RF unit 414.
  • the transceiver 410 can be configured to communicate bi-directionally with other devices, such as the BSs 105.
  • the modem subsystem 412 may be configured to modulate and/or encode the data from the memory 404 according to a modulation and coding scheme (MCS) , e.g., a low-density parity check (LDPC) coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.
  • MCS modulation and coding scheme
  • LDPC low-density parity check
  • the RF unit 414 may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.
  • the RF unit 414 may be further configured to perform analog beamforming in conjunction with the digital beamforming. Although shown as integrated together in transceiver 410, the modem subsystem 412 and the RF unit 414 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.
  • the RF unit 414 may provide the modulated and/or processed data, e.g. data packets (or, more generally, data messages that may contain one or more data packets and other information) , to the antennas 416 for transmission to one or more other devices.
  • the antennas 416 may further receive data messages transmitted from other devices.
  • the antennas 416 may provide the received data messages for processing and/or demodulation at the transceiver 410.
  • the antennas 416 may include multiple antennas of similar or different designs in order to sustain multiple transmission links.
  • the RF unit 414 may configure the antennas 416.
  • the UE 400 can include multiple transceivers 410 implementing different RATs (e.g., NR and LTE) .
  • the UE 400 can include a single transceiver 410 implementing multiple RATs (e.g., NR and LTE) .
  • the transceiver 410 can include various components, where different combinations of components can implement RATs.
  • FIG. 5 is a block diagram of an exemplary BS 500 according to embodiments of the present disclosure.
  • the BS 500 may be a BS 105 in the network 100 as discussed above in FIG. 1.
  • the BS 500 may include a processor 502, a memory 504, a network slice selection (NSS) module 508, a transceiver 510 including a modem subsystem 512 and a RF unit 514, and one or more antennas 516.
  • NSS network slice selection
  • the processor 502 may have various features as a specific-type processor. For example, these may include a CPU, a DSP, an ASIC, a controller, a FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.
  • the processor 502 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the memory 504 may include a cache memory (e.g., a cache memory of the processor 502) , RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, a solid state memory device, one or more hard disk drives, memristor-based arrays, other forms of volatile and non-volatile memory, or a combination of different types of memory.
  • the memory 504 may include a non-transitory computer-readable medium.
  • the memory 504 may store instructions 506.
  • the instructions 506 may include instructions that, when executed by the processor 502, cause the processor 502 to perform operations described herein, for example, aspects of FIG. 3. Instructions 506 may also be referred to as code, which may be interpreted broadly to include any type of computer-readable statement (s) as discussed above with respect to FIG. 3.
  • the NSS module 508 may be implemented via hardware, software, or combinations thereof.
  • the NSS module 508 may be implemented as a processor, circuit, and/or instructions 506 stored in the memory 504 and executed by the processor 502.
  • the NSS module 508 can be integrated within the modem subsystem 512.
  • the NSS module 508 can be implemented by a combination of software components (e.g., executed by a DSP or a general processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 512.
  • the NSS module 508 is configured to provide to the UE allowed NSSAI indicating permission of request by the UE for an application link direction specific network slice to serve the application traffic in the provided direction.
  • the transceiver 510 may include the modem subsystem 512 and the RF unit 514.
  • the transceiver 510 can be configured to communicate bi-directionally with other devices, such as the UEs 115 and/or another core network element.
  • the modem subsystem 512 may be configured to modulate and/or encode data according to a MCS, e.g., a LDPC coding scheme, a turbo coding scheme, a convolutional coding scheme, a digital beamforming scheme, etc.
  • the RF unit 514 may be configured to process (e.g., perform analog to digital conversion or digital to analog conversion, etc.
  • the RF unit 514 may be further configured to perform analog beamforming in conjunction with the digital beamforming. Although shown as integrated together in transceiver 510, the modem subsystem 512 and/or the RF unit 514 may be separate devices that are coupled together at the BS 105 to enable the BS 105 to communicate with other devices.
  • the RF unit 514 may provide the modulated and/or processed data, e.g. data packets (or, more generally, data messages that may contain one or more data packets and other information) , to the antennas 516 for transmission to one or more other devices. This may include, for example, transmission of information to complete attachment to a network and communication with a camped UE 115 or 500 according to embodiments of the present disclosure.
  • the antennas 516 may further receive data messages transmitted from other devices and provide the received data messages for processing and/or demodulation at the transceiver 510.
  • the antennas 516 may include multiple antennas of similar or different designs in order to sustain multiple transmission links.
  • the BS 500 can include multiple transceivers 510 implementing different RATs (e.g., NR and LTE) .
  • the BS 500 can include a single transceiver 510 implementing multiple RATs (e.g., NR and LTE) .
  • the transceiver 510 can include various components, where different combinations of components can implement RATs.
  • FIG. 6 is signaling diagram illustrating a communication method 600 with network slice information-based packet prioritization according to some embodiments of the present disclosure.
  • the method 600 may be implemented between a UE (e.g., the UE 115, UE 215, or UE 400) and a network (e.g., including a core network similar to the core network 204 and/or one or more BSs similar to the BS 105, and/or the BS 500) .
  • the method 600 may employ similar mechanisms as in the method 300 described above with respect to FIG. 3. Steps of the method 600 can be executed by computing devices (e.g., a processor, processing circuit, and/or other suitable component) of the UE.
  • computing devices e.g., a processor, processing circuit, and/or other suitable component
  • the UE may utilize one or more components, such as the processor 402, the memory 404, the NSS module 408, the transceiver 410, the modem 412, and the one or more antennas 416, to execute the steps of method 600.
  • the method 600 includes a number of enumerated steps, but embodiments of the method 600 may include additional steps before, after, and in between the enumerated steps. In some embodiments, one or more of the enumerated steps may be omitted or performed in a different order.
  • the UE may receive an indication of establishment of an application link between the UE and a 5G or NR network for transmitting a data packet.
  • the indication may be received from a remote server of an application linked to the UE via the application link. That is, the application may be executing on remote server in communication with the UE and the indication of the establishment of the application link between the UE and the NR network may be received from the remote server.
  • the indication may be received from the 5G or NR network or the UE.
  • the UE may tag the data packet with an application link direction tag based on a direction of the application link.
  • the application link for transmitting the data packet may be in the UL direction or DL direction and the data packet may be tagged with an UL or DL application link direction tag, respectively.
  • the UE may select or identify a network slice for transmission of the data packet based at least in part on the application link direction of the data packet.
  • the network slice can be selected based at least in part on a UE route selection policy (URSP) including an application link direction rule for selecting the network slice based on the direction of the application link.
  • URSP UE route selection policy
  • the network slice includes an ultra-reliable low-latency communication (uRLLC) network slice, an enhanced mobile broadband (eMBB) network slice or massive machine type communication (mMTC) network slice.
  • uRLLC ultra-reliable low-latency communication
  • eMBB enhanced mobile broadband
  • mMTC massive machine type communication
  • application link direction may be in the UL direction and the network slice can be an ultra-reliable low-latency communication (uRLLC) network slice.
  • the direction of the application link includes a downlink (DL) direction and the network slice is an enhanced mobile broadband (eMBB) network slice.
  • the selection or identification of the network slice can be based at least in part on the application link direction tag of the data packet.
  • the UE may establish or select a packet data unit (PDU) session over the selected network slice for the transmission of the data packet. That is, the UE may establish a new PDU session or utilize an existing one that matches the selected network slice or network slicing instance. In some cases, the UE may establish a pair of PDU sessions for transmitting data for the same application, one in the UL direction over a first network slice and another in the DL direction in a second network slice that can be different from the first network slice.
  • the first network slice can be an uRLLC network slice while the second network slice is an eMBB network slice.
  • Information and signals may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • “or” as used in a list of items indicates an inclusive list such that, for example, a list of [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .

Landscapes

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

Abstract

L'invention concerne des systèmes et des procédés de communication sans fil se rapportant à l'établissement, pour un équipement utilisateur, de sessions d'unités de données par paquets sur une tranche de réseau sélectionnée sur la base d'une direction de liaison d'application. Un UE peut recevoir une indication d'établissement d'une liaison d'application entre l'UE et un réseau 5G pour la transmission d'un paquet de données. En outre, l'UE peut sélectionner ou identifier une tranche de réseau pour transmettre le paquet de données sur la base, au moins en partie, d'une direction de la liaison d'application pour la transmission du paquet de données. De plus, l'UE peut établir ou sélectionner une session d'unité de données par paquets (PDU) sur la tranche de réseau sélectionnée pour la transmission du paquet de données.
PCT/CN2020/105083 2020-07-28 2020-07-28 Sélection de tranche de réseau basée sur la direction de liaison d'application WO2022021049A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/105083 WO2022021049A1 (fr) 2020-07-28 2020-07-28 Sélection de tranche de réseau basée sur la direction de liaison d'application

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/105083 WO2022021049A1 (fr) 2020-07-28 2020-07-28 Sélection de tranche de réseau basée sur la direction de liaison d'application

Publications (1)

Publication Number Publication Date
WO2022021049A1 true WO2022021049A1 (fr) 2022-02-03

Family

ID=80038026

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/105083 WO2022021049A1 (fr) 2020-07-28 2020-07-28 Sélection de tranche de réseau basée sur la direction de liaison d'application

Country Status (1)

Country Link
WO (1) WO2022021049A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018129325A1 (fr) * 2017-01-06 2018-07-12 Idac Holdings, Inc. Communications à multiplexage de données urllc et embb
US20190280802A1 (en) * 2016-11-02 2019-09-12 Idac Holdings, Inc. Shared Data Channel Design
CN110267276A (zh) * 2019-05-10 2019-09-20 中国联合网络通信集团有限公司 网络切片部署方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190280802A1 (en) * 2016-11-02 2019-09-12 Idac Holdings, Inc. Shared Data Channel Design
WO2018129325A1 (fr) * 2017-01-06 2018-07-12 Idac Holdings, Inc. Communications à multiplexage de données urllc et embb
CN110267276A (zh) * 2019-05-10 2019-09-20 中国联合网络通信集团有限公司 网络切片部署方法及装置

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
TENCENT: "Discussion on Asymmetric Traffic for Cloud Gaming and pCR to TR 22.842", 3GPP TSG-SA WG1 MEETING #85 S1-190069, 22 February 2019 (2019-02-22), XP051609352 *
TENCENT: "Discussion on Asymmetric Traffic for Cloud Gaming and pCR to TR 22.842", 3GPP TSG-SA WG1 MEETING #85 S1-190265, 22 February 2019 (2019-02-22), XP051609525 *
TENCENT: "Discussion on Asymmetric Traffic for Cloud Gaming and pCR to TR 22.842", 3GPP TSG-SA WG1 MEETING #85 S1-190453, 22 February 2019 (2019-02-22), XP051609648 *

Similar Documents

Publication Publication Date Title
KR102401887B1 (ko) 다운링크 스트리밍에서 트래픽 핸들링에 대한 네트워크 보조를 제공하기 위한 시스템 및 장치
US11632694B2 (en) Network slice availability check and indication
US11356940B2 (en) Mobility enhancement with network slicing
US12107793B2 (en) Physical downlink control channel (PDCCH) monitoring with overlapping resources
WO2021087180A1 (fr) Découverte de capacité d'une plateforme informatique de périphérie
US20210105724A1 (en) User equipment (ue) capability signaling for maximum power support
WO2021021423A1 (fr) Vérification et indication de disponibilité de tranche de réseau
US11706833B2 (en) On-demand ultra-reliable, low-latency communication (URLLC)
US20210266831A1 (en) Update of physical downlink control channel (pdcch) parameters
US20240129911A1 (en) Enhanced initial access with multi-beam operations
US20240155641A1 (en) Signaling for dynamic waveform switching
WO2022021049A1 (fr) Sélection de tranche de réseau basée sur la direction de liaison d'application
WO2022041124A1 (fr) Procédés et système de réglage de connectivité multimode d'un équipement utilisateur en fonction d'un type de tranche de réseau
CN114208272B (zh) 网络切片可用性检查和指示
US20240340823A1 (en) Sidelink synchronization signal block repetition in wideband communications
WO2023212888A1 (fr) Rapport de mesures de signal de référence pour une gestion prédictive de faisceau
US20230370232A1 (en) Multiplexing physical sidelink feedback channels in sidelink communication
US20230189159A1 (en) Power control parameter configurations for physical uplink shared channels in the presence of spatial division multiplexing
WO2023211594A1 (fr) Chevauchement de groupes de ressources dans une communication de liaison latérale

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: 20947005

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: 20947005

Country of ref document: EP

Kind code of ref document: A1