[go: up one dir, main page]

WO2022000327A1 - Amélioration de découpage de réseau - Google Patents

Amélioration de découpage de réseau Download PDF

Info

Publication number
WO2022000327A1
WO2022000327A1 PCT/CN2020/099508 CN2020099508W WO2022000327A1 WO 2022000327 A1 WO2022000327 A1 WO 2022000327A1 CN 2020099508 W CN2020099508 W CN 2020099508W WO 2022000327 A1 WO2022000327 A1 WO 2022000327A1
Authority
WO
WIPO (PCT)
Prior art keywords
vendor
application
network
sequence
field
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2020/099508
Other languages
English (en)
Inventor
Nan Zhang
Chaofeng HUI
Yongjun XU
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qualcomm Inc
Original Assignee
Qualcomm Inc
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 Inc filed Critical Qualcomm Inc
Priority to PCT/CN2020/099508 priority Critical patent/WO2022000327A1/fr
Publication of WO2022000327A1 publication Critical patent/WO2022000327A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2475—Traffic characterised by specific attributes, e.g. priority or QoS for supporting traffic characterised by the type of applications

Definitions

  • aspects of the present disclosure relate to wireless communications, and more particularly, to network slicing enhancements.
  • Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, etc. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc. ) .
  • available system resources e.g., bandwidth, transmit power, etc.
  • multiple-access systems examples include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) systems, LTE Advanced (LTE-A) systems, code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems, to name a few.
  • 3GPP 3rd Generation Partnership Project
  • LTE Long Term Evolution
  • LTE-A LTE Advanced
  • CDMA code division multiple access
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • OFDMA orthogonal frequency division multiple access
  • SC-FDMA single-carrier frequency division multiple access
  • TD-SCDMA time division synchronous code division multiple access
  • a wireless multiple-access communication system may include a number of base stations (BSs) , which are each capable of simultaneously supporting communication for multiple communication devices, otherwise known as user equipments (UEs) .
  • BSs base stations
  • UEs user equipments
  • a set of one or more base stations may define an eNodeB (eNB) .
  • eNB eNodeB
  • a wireless multiple access communication system may include a number of distributed units (DUs) (e.g., edge units (EUs) , edge nodes (ENs) , radio heads (RHs) , smart radio heads (SRHs) , transmission reception points (TRPs) , etc.
  • DUs distributed units
  • EUs edge units
  • ENs edge nodes
  • RHs radio heads
  • SSRHs smart radio heads
  • TRPs transmission reception points
  • CUs central units
  • CNs central nodes
  • ANCs access node controllers
  • a set of one or more DUs, in communication with a CU may define an access node (e.g., which may be referred to as a BS, 5G NB, next generation NodeB (gNB or gNodeB) , transmission reception point (TRP) , etc. ) .
  • BS central nodes
  • 5G NB next generation NodeB
  • TRP transmission reception point
  • a BS or DU may communicate with a set of UEs on downlink channels (e.g., for transmissions from a BS or DU to a UE) and uplink channels (e.g., for transmissions from a UE to BS or DU) .
  • downlink channels e.g., for transmissions from a BS or DU to a UE
  • uplink channels e.g., for transmissions from a UE to BS or DU
  • NR e.g., new radio or 5G
  • LTE long term evolution
  • NR is a set of enhancements to the LTE mobile standard promulgated by 3GPP.
  • NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, making use of new spectrum, and better integrating with other open standards using OFDMA with a cyclic prefix (CP) on the downlink (DL) and on the uplink (UL) .
  • OFDMA orthogonal frequency division multiple access
  • CP cyclic prefix
  • DL downlink
  • UL uplink
  • NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.
  • MIMO multiple-input multiple-output
  • wireless networks such as NR and LTE networks
  • Edge computing devices may support dynamic distribution of processing of data and/or content between the edge computing devices and a wireless device, such as a UE.
  • Certain aspects provide a method for wireless communications performed by a network entity.
  • the method generally includes determining a network slicing instance, encoding an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance, and transmitting the sequence of traffic descriptor bits to a UE.
  • ID application identification
  • Certain aspects provide a method for wireless communications performed by a user equipment (UE) .
  • the method generally includes receiving, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application ID field, decoding the application ID field, determining a vendor ID based on the decoding, and determining an application corresponding to at least one of the vendor ID or the network slicing instance.
  • the network entity generally includes means for determining a network slicing instance, means for encoding an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance, and means for transmitting the sequence of traffic descriptor bits to a user equipment (UE) .
  • ID application identification
  • UE user equipment
  • the UE generally includes means for receiving, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field, means for decoding the application ID field, means for determining a vendor ID based on the decoding, and means for determining an application corresponding to at least one of the vendor ID or the network slicing instance.
  • ID application identification
  • the UE generally includes means for receiving, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field, means for decoding the application ID field, means for determining a vendor ID based on the decoding, and means for determining an application corresponding to at least one of the vendor ID or the network slicing instance.
  • ID application identification
  • the network entity generally includes a processing system configured to determine a network slicing instance and encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance, and a transmitter configured to transmit the sequence of traffic descriptor bits to a user equipment (UE) .
  • a processing system configured to determine a network slicing instance and encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance
  • UE user equipment
  • the UE generally includes a receiver configured to receive, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field and a processing system configure to decode the application ID field, determine a vendor ID based on the decoding, and determine an application corresponding to at least one of the vendor ID or the network slicing instance.
  • ID application identification
  • the apparatus generally includes a processing system configured to determine a network slicing instance and encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance, and an interface configured to output the sequence of traffic descriptor bits for transmission to a user equipment (UE) .
  • ID application identification
  • UE user equipment
  • the apparatus generally includes an interface configured to obtain, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field and a processing system configure to decode the application ID field, determine a vendor ID based on the decoding, and determine an application corresponding to at least one of the vendor ID or the network slicing instance.
  • ID application identification
  • the computer-readable medium generally includes codes executable to determine a network slicing instance, encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance, and transmit the sequence of traffic descriptor bits to a user equipment (UE) .
  • ID application identification
  • UE user equipment
  • the computer-readable medium generally includes codes executable to receive, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field, decode the application ID field, determine a vendor ID based on the decoding, an determine an application corresponding to at least one of the vendor ID or the network slicing instance.
  • ID application identification
  • the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims.
  • the following description and the appended drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.
  • FIG. 1 is a block diagram conceptually illustrating an example telecommunications system, in accordance with certain aspects of the present disclosure.
  • FIG. 2 is a block diagram conceptually illustrating a design of an example base station (BS) and user equipment (UE) , in accordance with certain aspects of the present disclosure.
  • BS base station
  • UE user equipment
  • FIG. 3 illustrates an example data traffic component type identifier, in accordance with certain aspects of the present disclosure.
  • FIG. 4 illustrates example operations for wireless communications by a network entity, in accordance with some aspects of the present disclosure.
  • FIG. 5 illustrates example operations for wireless communications by a UE, in accordance with some aspects of the present disclosure.
  • FIG. 6 illustrates an example call flow diagram for network slicing enhancement, in accordance with some aspects of the present disclosure.
  • FIG. 7 illustrates example bundle IDs, in accordance with some aspects of the present disclosure.
  • aspects of the present disclosure relate to wireless communications, and more particularly, to network slicing enhancements with encoded vendor identifiers.
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , cdma2000, etc.
  • UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA.
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • An OFDMA network may implement a radio technology such as NR (e.g.
  • E-UTRA Evolved UTRA
  • UMB Ultra Mobile Broadband
  • IEEE 802.11 Wi-Fi
  • IEEE 802.16 WiMAX
  • IEEE 802.20 Flash-OFDMA
  • UTRA and E-UTRA are part of Universal Mobile Telecommunication System (UMTS) .
  • New Radio is an emerging wireless communications technology under development in conjunction with the 5G Technology Forum (5GTF) .
  • 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are releases of UMTS that use E-UTRA.
  • UTRA, E-UTRA, UMTS, LTE, LTE-A and GSM are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • cdma2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • the techniques described herein may be used for the wireless networks and radio technologies mentioned above as well as other wireless networks and radio technologies. For clarity, while aspects may be described herein using terminology commonly associated with 3G and/or 4G wireless technologies, aspects of the present disclosure can be applied in other generation-based communication systems, such as 5G and later, including NR technologies.
  • New radio (NR) access may support various wireless communication services, such as enhanced mobile broadband (eMBB) targeting wide bandwidth (e.g., 80 MHz or beyond) , millimeter wave (mmW) targeting high carrier frequency (e.g., 25 GHz or beyond) , massive machine type communications MTC (mMTC) targeting non-backward compatible MTC techniques, and/or mission critical targeting ultra-reliable low-latency communications (URLLC) .
  • eMBB enhanced mobile broadband
  • mmW millimeter wave
  • mMTC massive machine type communications MTC
  • URLLC ultra-reliable low-latency communications
  • These services may include latency and reliability requirements.
  • These services may also have different transmission time intervals (TTI) to meet respective quality of service (QoS) requirements.
  • TTI transmission time intervals
  • QoS quality of service
  • these services may co-exist in the same subframe.
  • FIG. 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be performed.
  • a BS 110 may be configured to perform operations 400 of FIG. 4, while a UE 120 may be configured to perform operations 500 of FIG. 5, to achieve network slicing enhancements with application identifiers encoded with a vendor identification (ID) .
  • ID vendor identification
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal FDMA
  • SC-FDMA Single-Carrier FDMA
  • a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA) , cdma2000, etc.
  • UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR) .
  • cdma2000 covers IS-2000, IS-95 and IS-856 standards.
  • a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM) .
  • GSM Global System for Mobile Communications
  • An OFDMA network may implement a radio technology such as Evolved UTRA (E-UTRA) , IEEE 802.11, IEEE 802.16, IEEE 802.20, etc.
  • E-UTRA, and GSM are part of Universal Mobile Telecommunication System (UMTS) .
  • Long Term Evolution (LTE) is an upcoming release of UMTS that uses E-UTRA.
  • UTRA, E-UTRA, GSM, UMTS and LTE are described in documents from an organization named “3rd Generation Partnership Project” (3GPP) .
  • cdma2000 is described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) .
  • SC-FDMA Single carrier frequency division multiple access
  • SC-FDMA Single carrier frequency division multiple access
  • SC-FDMA signal has lower peak-to-average power ratio (PAPR) because of its inherent single carrier structure.
  • PAPR peak-to-average power ratio
  • SC-FDMA has drawn great attention, especially in the uplink communications where lower PAPR greatly benefits the mobile terminal in terms of transmit power efficiency. It is currently a working assumption for uplink multiple access scheme in 3GPP Long Term Evolution (LTE) , or Evolved UTRA.
  • LTE Long Term Evolution
  • FIG. 1 shows a wireless communication network 100 in which aspects of the present disclosure may be practiced.
  • evolved Node Bs 110 may cache content and transmit the cached content to user equipments (UEs) 120 as described herein.
  • UEs user equipments
  • Wireless communication network 100 may be an LTE network.
  • the wireless network 100 may include a number of evolved Node Bs (eNBs) 110 and other network entities.
  • eNB evolved Node Bs
  • An eNB may be a station that communicates with the UEs and may also be referred to as a base station, an access point, etc.
  • a Node B is another example of a station that communicates with the UEs.
  • Each eNB 110 may provide communication coverage for a particular geographic area.
  • the term “cell” can refer to a coverage area of an eNB and/or an eNB subsystem serving this coverage area, depending on the context in which the term is used.
  • An eNB may provide communication coverage for a macro cell, a pico cell, a femto cell, and/or other types of cell.
  • a macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription.
  • a pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription.
  • a femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having association with the femto cell (e.g., UEs in a Closed Subscriber Group (CSG) , UEs for users in the home, etc. ) .
  • CSG Closed Subscriber Group
  • An eNB for a macro cell may be referred to as a macro eNB.
  • An eNB for a pico cell may be referred to as a pico eNB.
  • An eNB for a femto cell may be referred to as a femto eNB or a home eNB.
  • the eNBs 110a, 110b and 110c may be macro eNBs for the macro cells 102a, 102b and 102c, respectively.
  • the eNB 110x may be a pico eNB for a pico cell 102x.
  • the eNBs 110y and 110z may be femto eNBs for the femto cells 102y and 102z, respectively.
  • An eNB may support one or multiple (e.g., three) cells.
  • the wireless network 100 may also include relay stations.
  • a relay station is a station that receives a transmission of data and/or other information from an upstream station (e.g., an eNB or a UE) and sends a transmission of the data and/or other information to a downstream station (e.g., a UE or an eNB) .
  • a relay station may also be a UE that relays transmissions for other UEs.
  • a relay station 110r may communicate with the eNB 110a and a UE 120r in order to facilitate communication between the eNB 110a and the UE 120r.
  • a relay station may also be referred to as a relay eNB, a relay, etc.
  • the wireless network 100 may be a heterogeneous network that includes eNBs of different types, e.g., macro eNBs, pico eNBs, femto eNBs, relays, etc. These different types of eNBs may have different transmit power levels, different coverage areas, and different impact on interference in the wireless network 100.
  • macro eNBs may have a high transmit power level (e.g., 20 Watts) whereas pico eNBs, femto eNBs and relays may have a lower transmit power level (e.g., 1 Watt) .
  • the wireless network 100 may support synchronous or asynchronous operation.
  • the eNBs may have similar frame timing, and transmissions from different eNBs may be approximately aligned in time.
  • the eNBs may have different frame timing, and transmissions from different eNBs may not be aligned in time.
  • the techniques described herein may be used for both synchronous and asynchronous operation.
  • a network controller 130 may couple to a set of eNBs and provide coordination and control for these eNBs.
  • the network controller 130 may communicate with the eNBs 110 via a backhaul.
  • the eNBs 110 may also communicate with one another, e.g., directly or indirectly via wireless or wireline backhaul.
  • the UEs 120 may be dispersed throughout the wireless network 100, and each UE may be stationary or mobile.
  • a UE may also be referred to as a terminal, a mobile station, a subscriber unit, a station, etc.
  • a UE may be a cellular phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, etc.
  • PDA personal digital assistant
  • a UE may be able to communicate with macro eNBs, pico eNBs, femto eNBs, relays, etc.
  • a solid line with double arrows indicates desired transmissions between a UE and a serving eNB, which is an eNB designated to serve the UE on the downlink and/or uplink.
  • a dashed line with double arrows indicates interfering transmissions between a UE and an eNB.
  • LTE utilizes orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink.
  • OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, which are also commonly referred to as tones, bins, etc.
  • K orthogonal subcarriers
  • Each subcarrier may be modulated with data.
  • modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM.
  • the spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth.
  • the spacing of the subcarriers may be 15 kHz and the minimum resource allocation (called a ‘resource block’ ) may be 12 subcarriers (or 180 kHz) . Consequently, the nominal FFT size may be equal to 128, 256, 512, 1024 or 2048 for system bandwidth of 1.25, 2.5, 5, 10 or 20 megahertz (MHz) , respectively.
  • the system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.8 MHz (i.e., 6 resource blocks) , and there may be 1, 2, 4, 8 or 16 subbands for system bandwidth of 1.25, 2.5, 5, 10 or 20 MHz, respectively.
  • the wireless network 100 may also include UEs 120 capable of communicating with a core network via one or more radio access networks (RANs) that implement one or more radio access technologies (RATs) .
  • RANs radio access networks
  • RATs radio access technologies
  • the wireless network 100 may include co-located access points (APs) and/or base stations that provide communication through a first RAN implementing a first RAT and a second RAN implementing a second RAT.
  • the first RAN may be a wide area wireless access network (WWAN) and the second RAN may be a wireless local area network (WLAN) .
  • WWAN wide area wireless access network
  • WLAN wireless local area network
  • WWAN may include, but not be limited to, for example, radio access technologies (RATs) such as LTE, UMTS, cdma2000, GSM, and the like.
  • RATs radio access technologies
  • WLAN may include, but not be limited to, for example, RATs such as Wi-Fi or IEEE 802.11 based technologies, and the like.
  • the wireless network 100 may include co-located Wi-Fi access points (APs) and femto eNBs that provide communication through Wi-Fi and cellular radio links.
  • APs Wi-Fi access points
  • femto eNBs that provide communication through Wi-Fi and cellular radio links.
  • co-located generally means “in close proximity to, ” and applies to Wi-Fi APs or femto eNBs within the same device enclosure or within separate devices that are in close proximity to each other.
  • the term “femtoAP” may refer to a co-located Wi-Fi AP and femto eNB.
  • FIG. 2 is a block diagram of an example embodiment of a base station 110 (also known as an access point (AP) ) and a UE 120 in which aspects of the present disclosure may be practiced.
  • a base station 110 also known as an access point (AP)
  • UE 120 in which aspects of the present disclosure may be practiced.
  • the various processors of BS 110 may be configured to perform (or cause UE 120 to perform) operations 400 of FIG. 4 and/or the various processors of UE 120 may be configured to perform operations 500 of FIG. 5.
  • traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.
  • TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.
  • the coded data for each data stream may be multiplexed with pilot data using OFDM techniques.
  • the pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response.
  • the multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QSPK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols.
  • a particular modulation scheme e.g., BPSK, QSPK, M-PSK, or M-QAM
  • the data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230.
  • TX MIMO processor 220 may further process the modulation symbols (e.g., for OFDM) .
  • TX MIMO processor 220 then provides N T modulation symbol streams to N T transmitters (TMTR) 222a through 222t.
  • TMTR TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.
  • Each receiver 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel.
  • N T modulated signals from transmitters 222a through 222t are then transmitted from N T antennas 224a through 224t, respectively.
  • the transmitted modulated signals are received by N R antennas 252a through 252r, and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254a through 254r.
  • Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.
  • An RX data processor 260 then receives and processes the N R received symbol streams from N R receivers 254 based on a particular receiver processing technique to provide N T “detected” symbol streams.
  • the RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream.
  • the processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at base station 110.
  • a processor 270 periodically determines which pre-coding matrix to use. Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.
  • the reverse link message may comprise various types of information regarding the communication link and/or the received data stream.
  • the reverse link message is then processed by a TX data processor 238, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254a through 254r, and transmitted back to base station 110.
  • the modulated signals from UE 120 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by a RX data processor 242 to extract the reserve link message transmitted by the UE 120.
  • Processor 230 determines which pre-coding matrix to use for determining the beamforming weights and then processes the extracted message.
  • the controllers/processors 230 and 270 may direct the operation at the base station 110 and the UE 120, respectively.
  • the processor 230, TX data processor 214, and/or other processors and modules at the base station 110 may perform or direct processes for the techniques described herein.
  • the processor 270, RX data processor 260, and/or other processors and modules at the UE 120 may perform or direct processes for the techniques described herein.
  • the processor 230, TX data processor 214, and/or other processors and modules at the base station 110 may perform or direct operations 400 of FIG. 4, and/or other processors and modules at the UE 120 may perform or direct operations 500 of FIG. 5.
  • aspects of the present disclosure relate to wireless communications, and more particularly, to network slicing enhancements with application identifiers encoded with a vendor identification (ID) .
  • a user equipment UE may be able to forward such requests to a network entity to receive an encoded vendor identification (ID) to provide for improved indexing of applications on the UE.
  • ID vendor identification
  • the HLOS when applications that do not require special treatment (as identified by their application ID) request a wireless network connection, the HLOS sends an Internet Connection setup request to the modem to establish a default Internet PDU session.
  • the requesting application as well as other conventional applications, share this default Internet PDU session.
  • URSP applications may require special treatment, such as special connection capabilities provided on a special network slice.
  • a URSP application may refer to any application with data traffic that may be sent according to one or more URSP rules, for example, specifying a route selection descriptor (RSD) .
  • RSD route selection descriptor
  • a network slice generally refers to a set of resources that effectively establish a logical network that runs on a shared physical infrastructure, capable of providing a negotiated service quality. The technology enabling network slicing is typically transparent to users (e.g., business customers/subscribers) .
  • a PDU Session Establishment is the procedure allowing data transmission to a data network (DN) in a Network Slice.
  • a PDU Session is associated with a single Network Slice Selection Assistance Information (S-NSSAI) and a data network name (DNN) .
  • S-NSSAI Network Slice Selection Assistance Information
  • DNN data network name
  • NSSP Network Slice Selection Policy
  • OS App Id field is a fundamental component for a UE to index application to a particular network slicing instance.
  • FIG. 3 which is an example data traffic component type identifier
  • the “OS App Id Type” may be an octet of bits (as defined by current wireless standards) to provide a UE with information to search and match an application, running in an OS, corresponding to the application ID.
  • certain aspects provide for enhanced network slicing.
  • certain aspects provide for encoding/decoding application identifiers encoded with a vendor identification (ID) that corresponds to an application and/or a network slicing instance.
  • ID vendor identification
  • the application ID may be related to an application vendor and/or a mobile operator.
  • application may have a unique ID, which may include the name of the vendor and/or mobile operator encoded in a substring of the application ID.
  • a UE may use the substring to index applications to, for example, route to a network slicing instance.
  • FIG. 4 illustrates example operations 400 for wireless communications by a network entity.
  • operations 400 may be performed, by a network entity (e.g., such as a BS 110 in the wireless communication network 100 of FIG. 1 or FIG. 2) to enhance network slicing.
  • a network entity e.g., such as a BS 110 in the wireless communication network 100 of FIG. 1 or FIG. 2 to enhance network slicing.
  • Operations 400 begin, at 402, by determining a network slicing instance.
  • the network entity encodes an application ID field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance.
  • the network entity transmits the sequence of traffic descriptor bits to a UE.
  • FIG. 5 illustrates example operations 500 for wireless communications by UE that may be considered complementary to operations 400 of FIG. 4.
  • operations 500 may be performed by a UE (e.g., the UE 120 of FIG. 1 or FIG. 2) to participate in enhanced network slicing with a network entity (e.g., a BS 110 performing operations 400 of FIG. 4) .
  • a UE e.g., the UE 120 of FIG. 1 or FIG. 2
  • a network entity e.g., a BS 110 performing operations 400 of FIG.
  • Operations 500 begin, at 502, by receiving, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application ID field.
  • the UE decodes the application ID field.
  • the UE determines a vendor ID based on the decoding.
  • the UE determines an application corresponding to at least one of the vendor ID or the network slicing instance.
  • FIGs. 4 and 5 may be understood with reference to the call flow diagram 600 of FIG. 6.
  • a network entity e.g., a base station of the operator network
  • FIG. 6 may perform operations 400 of FIG. 4, while the UE may perform operations 500 of FIG. 5.
  • the UE may determine that an application has requested a slicing instance. For example, an application on the UE may indicate that the application desires an ultra-reliable low latency connection (uRLLC) network slicing service.
  • uRLLC ultra-reliable low latency connection
  • the UE may transmit the request to a remote server (e.g., operated by a vendor for the requesting application) , and the remote server may forward the request to the network (operator) .
  • the request received by the network may include public land mobile network (PLMN) information and/or information regarding the application.
  • PLMN public land mobile network
  • the request may be transmitted via a default data service (DDS) of the UE.
  • DDS default data service
  • the network may generate a vendor ID.
  • the network may encode, within a sequence of traffic descriptor bits, an application ID field related to the application with the vendor ID.
  • the network may store a plurality of different vendor IDs.
  • the network may generate the application ID field based on a vendor of the application and/or a mobile operator for the application.
  • the network may be configured to generate the application ID field and encode the vendor ID without receiving the request from the UE.
  • an application vendor may submit a vendor name as an ASCII string to the network.
  • the network may then transmit the sequence of traffic descriptor bits to the remote server, which may forward the sequence of traffic descriptor bits to the UE to configure the UE to update a UE route selection policy (USRP) .
  • USRP UE route selection policy
  • the UE may update a USRP based on the reception of the vendor ID.
  • the UE may match the vendor ID to the application ID of the application. If the matching is successful, the UE may, route the application to the network slicing instance (e.g., the uRLLC network slicing instance) .
  • the UE may perform the matching by using an ASCII string provided by the vendor, as described above, to match the application ID to the vendor ID.
  • the table shown in FIG. 7 illustrates how a vendor ID may be provided a s a middle string in a bundle ID.
  • An application ID e.g., a Bundle ID shown in FIG. 7 is typically the result of application vendor and mobile operator. This type of cooperation may allow, for example, subscribed (VIP) users of an application vendor to use their application free of data service charges (or free up to a threshold usage) .
  • VIP subscribed
  • an operating system e.g., Apple iOS or Android OS
  • the unique ID typically contains the vendor name (a generic name “vendor” is used in the example) .
  • a UE may, thus, use this substring vendor in the bundle ID to index applications to a NW slicing instance.
  • Embodiment 1 A method for wireless communications by a network entity, comprising: determining a network slicing instance; encoding an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance; and transmitting the sequence of traffic descriptor bits to a user equipment (UE) .
  • ID application identification
  • UE user equipment
  • Embodiment 2 The method of Embodiment 1, further comprising storing a plurality of different vendor IDs including the vendor ID.
  • Embodiment 3 The method of any of Embodiments 1 through 2, wherein the vendor ID corresponds to a vendor providing the application.
  • Embodiment 4 The method of any of Embodiments 1 through 3, wherein further comprising generating the application ID field based on at least one of an application vendor or a mobile operator.
  • Embodiment 5 The method of any of Embodiments 1 through 4, wherein the sequence of traffic descriptor bits configures the UE to update a UE route selection policy (USRP) .
  • USRP UE route selection policy
  • Embodiment 6 A method for wireless communications by a user equipment (UE) , comprising: receiving, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field; decoding the application ID field; determining a vendor ID based on the decoding; and determining an application corresponding to at least one of the vendor ID or the network slicing instance.
  • ID application identification
  • Embodiment 7 The method of Embodiment 6, wherein the vendor ID is one of a plurality of different vendor IDs stored by the network entity.
  • Embodiment 8 The method of any of Embodiments 6 through 7, wherein the vendor ID corresponds to a vendor providing the application.
  • Embodiment 9 The method of any of Embodiments 6 through 8, wherein the application ID field is generated based on at least one of an application vendor or a mobile operator.
  • Embodiment 10 The method of any of Embodiments 6 through 9, further comprising updating a UE route selection policy (USRP) based on the sequence of traffic descriptor bits.
  • USRP UE route selection policy
  • Embodiment 11 A network entity, comprising: means for determining a network slicing instance; means for encoding an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance; and means for transmitting the sequence of traffic descriptor bits to a user equipment (UE) .
  • ID application identification
  • UE user equipment
  • Embodiment 12 The network entity of Embodiment 11, further comprising means for storing a plurality of different vendor IDs including the vendor ID.
  • Embodiment 13 The network entity of any of Embodiments 11 through 12, wherein the vendor ID corresponds to a vendor providing the application.
  • Embodiment 14 The network entity of any of Embodiments 11 through 13, further comprising means for generating the application ID field based on at least one of an application vendor or a mobile operator.
  • Embodiment 15 The network entity of any of Embodiments 11 through 14, wherein the sequence of traffic descriptor bits configures the UE to update a UE route selection policy (USRP) .
  • USRP UE route selection policy
  • Embodiment 16 A user equipment (UE) , comprising: means for receiving, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field; means for decoding the application ID field; means for determining a vendor ID based on the decoding; and means for determining an application corresponding to at least one of the vendor ID or the network slicing instance.
  • ID application identification
  • Embodiment 17 The UE of Embodiment 16, wherein the vendor ID is one of a plurality of different vendor IDs stored by the network entity.
  • Embodiment 18 The UE of any of Embodiments 16 through 17, wherein the vendor ID corresponds to a vendor providing the application.
  • Embodiment 19 The UE of any of Embodiments 16 through 18, wherein the application ID field is generated based on at least one of an application vendor or a mobile operator.
  • Embodiment 20 The UE of any of Embodiments 16 through 19, further comprising means for updating a UE route selection policy (USRP) based on the sequence of traffic descriptor bits.
  • USRP UE route selection policy
  • Embodiment 21 A network entity, comprising: a processing system configured to: determine a network slicing instance; and encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance; and a transmitter configured to transmit the sequence of traffic descriptor bits to a user equipment (UE) .
  • a processing system configured to: determine a network slicing instance; and encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance
  • a transmitter configured to transmit the sequence of traffic descriptor bits to a user equipment (UE) .
  • UE user equipment
  • Embodiment 22 The network entity of Embodiment 21, wherein the processing system is further configured to store a plurality of different vendor IDs including the vendor ID.
  • Embodiment 23 The network entity of any of Embodiments 21 through 22, wherein the vendor ID corresponds to a vendor providing the application.
  • Embodiment 24 The network entity of any of Embodiments 21 through 23, wherein the processing system is further configure to generate the application ID field based on at least one of an application vendor or a mobile operator.
  • Embodiment 25 The network entity of any of Embodiments 21 through 24, wherein the sequence of traffic descriptor bits configures the UE to update a UE route selection policy (USRP) .
  • USRP UE route selection policy
  • Embodiment 26 A user equipment (UE) , comprising: a receiver configured to receive, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field; and a processing system configure to: decode the application ID field; determine a vendor ID based on the decoding; and determine an application corresponding to at least one of the vendor ID or the network slicing instance.
  • UE user equipment
  • Embodiment 27 The UE of Embodiment 26, wherein the vendor ID is one of a plurality of different vendor IDs stored by the network entity.
  • Embodiment 28 The UE of any of Embodiments 26 through 27, wherein the vendor ID corresponds to a vendor providing the application.
  • Embodiment 29 The UE of any of Embodiments 26 through 28, wherein the application ID field is generated based on at least one of an application vendor or a mobile operator.
  • Embodiment 30 The UE of any of Embodiments 26 through 29, wherein the processing system is further configured to update a UE route selection policy (USRP) based on the sequence of traffic descriptor bits.
  • USRP UE route selection policy
  • Embodiment 31 An apparatus for wireless communications performed by a network entity, comprising: a processing system configured to: determine a network slicing instance; and encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance; and an interface configured to output the sequence of traffic descriptor bits for transmission to a user equipment (UE) .
  • a processing system configured to: determine a network slicing instance; and encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance; and an interface configured to output the sequence of traffic descriptor bits for transmission to a user equipment (UE) .
  • ID application identification
  • Embodiment 32 An apparatus for wireless communications performed by user equipment (UE) , comprising: an interface configured to obtain, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field; and a processing system configure to decode the application ID field; determine a vendor ID based on the decoding; and determine an application corresponding to at least one of the vendor ID or the network slicing instance.
  • UE user equipment
  • Embodiment 33 A computer-readable medium for wireless communications performed by a network entity, comprising codes executable to: determine a network slicing instance; encode an application identification (ID) field within a sequence of traffic descriptor bits with a vendor ID corresponding to at least one of an application or the network slicing instance; and transmit the sequence of traffic descriptor bits to a user equipment (UE) .
  • ID application identification
  • UE user equipment
  • Embodiment 34 A computer-readable medium for wireless communications performed by a user equipment (UE) , comprising codes executable to: receive, from a network entity in a network slicing instance, a sequence of traffic descriptor bits comprising an application identification (ID) field; decode the application ID field; determine a vendor ID based on the decoding; and determine an application corresponding to at least one of the vendor ID or the network slicing instance.
  • UE user equipment
  • the methods disclosed herein comprise one or more steps or actions for achieving the methods.
  • the method steps and/or actions may be interchanged with one another without departing from the scope of the claims.
  • the order and/or use of specific steps and/or actions may be modified without departing from the scope of the claims.
  • a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members.
  • “at least one of: a, b, or c” is intended to cover a, b, c, a-b, a-c, b-c, and a-b-c, as well as any combination with multiples of the same element (e.g., a-a, a-a-a, a-a-b, a-a-c, a-b-b, a-c-c, b-b, b-b-b, b-b-c, c-c, and c-c-c or any other ordering of a, b, and c) .
  • determining encompasses a wide variety of actions. For example, “determining” may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” may include receiving (e.g., receiving information) , accessing (e.g., accessing data in a memory) and the like. Also, “determining” may include resolving, selecting, choosing, establishing and the like.
  • the various operations of methods described above may be performed by any suitable means capable of performing the corresponding functions.
  • the means may include various hardware and/or software component (s) and/or module (s) , including, but not limited to a circuit, an application specific integrated circuit (ASIC) , or processor.
  • ASIC application specific integrated circuit
  • processors 258, 264 and 266, and/or controller/processor 280 of the UE 120a and/or processors 220, 230, 238, and/or controller/processor 240 of the BS 110a shown in FIG. 2 may be configured to perform operations 400 of FIG. 4 and operations 500 of FIG. 5.
  • Means for receiving may include a transceiver, a receiver or at least one antenna and at least one receive processor illustrated in FIG. 2.
  • Means for transmitting, means for sending or means for outputting may include, a transceiver, a transmitter or at least one antenna and at least one transmit processor illustrated in FIG. 2.
  • Means for determining, means for encoding, means for storing, means for generating, means for decoding, and means for updating may include a processing system, which may include one or more processors, such as processors 258, 264 and 266, and/or controller/processor 280 of the UE 120a and/or processors 220, 230, 238, and/or controller/processor 240 of the BS 110a shown in FIG. 2.
  • a device may have an interface to output a frame for transmission (a means for outputting) .
  • a processor may output a frame, via a bus interface, to a radio frequency (RF) front end for transmission.
  • RF radio frequency
  • a device may have an interface to obtain a frame received from another device (a means for obtaining) .
  • a processor may obtain (or receive) a frame, via a bus interface, from an RF front end for reception.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • PLD programmable logic device
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any commercially available 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, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • an example hardware configuration may comprise a processing system in a wireless node.
  • the processing system may be implemented with a bus architecture.
  • the bus may include any number of interconnecting buses and bridges depending on the specific application of the processing system and the overall design constraints.
  • the bus may link together various circuits including a processor, machine-readable media, and a bus interface.
  • the bus interface may be used to connect a network adapter, among other things, to the processing system via the bus.
  • the network adapter may be used to implement the signal processing functions of the PHY layer.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • a user interface e.g., keypad, display, mouse, joystick, etc.
  • the bus may also link various other circuits such as timing sources, peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further.
  • the processor may be implemented with one or more general-purpose and/or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuitry that can execute software. Those skilled in the art will recognize how best to implement the described functionality for the processing system depending on the particular application and the overall design constraints imposed on the overall system.
  • the functions may be stored or transmitted over as one or more instructions or code on a computer readable medium.
  • Software shall be construed broadly to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.
  • Computer-readable media include both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • the processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage media.
  • a computer-readable storage medium may be coupled to a processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor.
  • the machine-readable media may include a transmission line, a carrier wave modulated by data, and/or a computer readable storage medium with instructions stored thereon separate from the wireless node, all of which may be accessed by the processor through the bus interface.
  • the machine-readable media, or any portion thereof may be integrated into the processor, such as the case may be with cache and/or general register files.
  • machine-readable storage media may include, by way of example, RAM (Random Access Memory) , flash memory, ROM (Read Only Memory) , PROM (Programmable Read-Only Memory) , EPROM (Erasable Programmable Read-Only Memory) , EEPROM (Electrically Erasable Programmable Read-Only Memory) , registers, magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
  • RAM Random Access Memory
  • ROM Read Only Memory
  • PROM Programmable Read-Only Memory
  • EPROM Erasable Programmable Read-Only Memory
  • EEPROM Electrical Erasable Programmable Read-Only Memory
  • registers magnetic disks, optical disks, hard drives, or any other suitable storage medium, or any combination thereof.
  • the machine-readable media may be embodied in a computer-program product.
  • a software module may comprise a single instruction, or many instructions, and may be distributed over several different code segments, among different programs, and across multiple storage media.
  • the computer-readable media may comprise a number of software modules.
  • the software modules include instructions that, when executed by an apparatus such as a processor, cause the processing system to perform various functions.
  • the software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices.
  • a software module may be loaded into RAM from a hard drive when a triggering event occurs.
  • the processor may load some of the instructions into cache to increase access speed.
  • One or more cache lines may then be loaded into a general register file for execution by the processor.
  • any connection is properly termed a computer-readable medium.
  • the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared (IR) , radio, and microwave
  • the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium.
  • Disk and disc include compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers.
  • computer-readable media may comprise non-transitory computer-readable media (e.g., tangible media) .
  • computer-readable media may comprise transitory computer-readable media (e.g., a signal) . Combinations of the above should also be included within the scope of computer-readable media.
  • certain aspects may comprise a computer program product for performing the operations presented herein.
  • a computer program product may comprise a computer-readable medium having instructions stored (and/or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein. For example, instructions for performing the operations described herein and illustrated in FIGs. 4 and 5.
  • modules and/or other appropriate means for performing the methods and techniques described herein can be downloaded and/or otherwise obtained by a user terminal and/or base station as applicable.
  • a user terminal and/or base station can be coupled to a server to facilitate the transfer of means for performing the methods described herein.
  • various methods described herein can be provided via storage means (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc. ) , such that a user terminal and/or base station can obtain the various methods upon coupling or providing the storage means to the device.
  • storage means e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or floppy disk, etc.
  • CD compact disc
  • floppy disk etc.
  • any other suitable technique for providing the methods and techniques described herein to a device can be utilized.

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 divulgation portent sur les communications sans fil, et plus particulièrement, des améliorations de découpage de réseau au moyen d'identifiants d'application codés avec une identification de vendeur (ID). Par exemple, en gérant des demandes d'une application, un équipement utilisateur (UE) peut permettre de transmettre de telles demandes à une entité de réseau pour recevoir une identification (ID) de vendeur codée pour fournir une indexation améliorée d'applications sur l'UE.
PCT/CN2020/099508 2020-06-30 2020-06-30 Amélioration de découpage de réseau Ceased WO2022000327A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/099508 WO2022000327A1 (fr) 2020-06-30 2020-06-30 Amélioration de découpage de réseau

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/099508 WO2022000327A1 (fr) 2020-06-30 2020-06-30 Amélioration de découpage de réseau

Publications (1)

Publication Number Publication Date
WO2022000327A1 true WO2022000327A1 (fr) 2022-01-06

Family

ID=79317321

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/099508 Ceased WO2022000327A1 (fr) 2020-06-30 2020-06-30 Amélioration de découpage de réseau

Country Status (1)

Country Link
WO (1) WO2022000327A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109743766A (zh) * 2018-02-13 2019-05-10 华为技术有限公司 一种数据路由选择的方法及装置
CN110224857A (zh) * 2013-04-11 2019-09-10 高通股份有限公司 用于应用业务配对的方法、设备和服务器
WO2019194633A1 (fr) * 2018-04-05 2019-10-10 삼성전자 주식회사 Dispositif et procédé de gestion de politique d'un équipement utilisateur dans un système de communication sans fil
WO2020030180A1 (fr) * 2018-08-10 2020-02-13 Mediatek Inc. Mise en correspondance améliorée de règles d'une politique de sélection d'itinéraire d'ue (ursp)

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110224857A (zh) * 2013-04-11 2019-09-10 高通股份有限公司 用于应用业务配对的方法、设备和服务器
CN109743766A (zh) * 2018-02-13 2019-05-10 华为技术有限公司 一种数据路由选择的方法及装置
WO2019194633A1 (fr) * 2018-04-05 2019-10-10 삼성전자 주식회사 Dispositif et procédé de gestion de politique d'un équipement utilisateur dans un système de communication sans fil
WO2020030180A1 (fr) * 2018-08-10 2020-02-13 Mediatek Inc. Mise en correspondance améliorée de règles d'une politique de sélection d'itinéraire d'ue (ursp)

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
APPLE: "Deprecating OS Id and OS App Id from URSP and ATSSS rules", 3GPP DRAFT; S2-1911904, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. Reno, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051824201 *
MOTOROLA MOBILITY, LENOVO, NOKIA, NOKIA SHANGHAI BELL, INTEL, SAMSUNG, VODAFONE, ERICSSON: "3GPP OS Id", 3GPP DRAFT; C1-196296 WAS C1-194967 WAS C1-194469 3GPP OS ID TS 24.501 REL 16-V00, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Portoroz (Slovenia); 20191007 - 20191011, 30 September 2019 (2019-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051787917 *
NOKIA, NOKIA SHANGHAI BELL: "A new approach for registering and retrieving OS/App IDs", 3GPP DRAFT; C1-203736, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG1, no. Electronic meeting; 20200602 - 20200610, 26 May 2020 (2020-05-26), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051891284 *

Similar Documents

Publication Publication Date Title
US10939280B2 (en) Optimization of user equipment radio capability signaling
US11356404B2 (en) Domain name system (DNS) override for edge computing
US20210282084A1 (en) Slice-aware plmn selection
KR102691103B1 (ko) 디바이스-대-디바이스 송신 및 수신을 위한 주파수 결정
US20210099945A1 (en) Reduced overhead network slice selection assistance information (nssai) signaling
US20220312368A1 (en) Service priority information for multi-sim user equipment paging
EP4176565B1 (fr) Clé de sécurité de couche 1 (l1) et couche 2 (l2) à base de mobilité
US12369024B2 (en) Restricted access and use control for user equipment with reduced capabilities
US12317213B2 (en) Delaying UE radio capability ID (URCID) update for EPLMN
WO2022081342A1 (fr) Partage dynamique de spectre dans un dispositif à multiples modules d'identité d'abonné
WO2022056659A1 (fr) Négociation de nssai applicable à un équipement utilisateur
EP4173228B1 (fr) Mise en évidence de découpage de réseau
WO2022011665A1 (fr) Découpage en tranches de réseau nssp/ursp et mise à jour de configuration locale d'ue
WO2022000327A1 (fr) Amélioration de découpage de réseau
US20230141754A1 (en) Ensuring compatibility between network slice operating frequencies and user equipment (ue) radio capabilities
CN118339883A (zh) 无线电网络节点、用户设备和其中执行的方法

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

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

Country of ref document: EP

Kind code of ref document: A1