Sidelink procedures and structures for transmission and reception of dependent and independent physical sidelink shared channels

Abstract

Certain embodiments of the present disclosure include apparatus and methods for transmitting and receiving sidelink procedures and structures for dependent and independent PSSCH in a wireless communication system.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit under 35 USC §119(e) of U.S. Provisional Application No. 62 / 791,572, filed on January 11, 2019, which is hereby incorporated by reference in its entirety. Background Art

[0003] Various embodiments may generally relate to the field of wireless communications. Summary of the invention

[0004] Certain embodiments of the present disclosure include apparatus and methods for transmitting and receiving sidelink procedures and structures for dependent and independent physical sidelink shared channels (PSSCH).

[0005] Some embodiments relate to a method of operating a system. The method includes selecting, by a user equipment (UE) based on a scheduling decision, a rate matching (RM) mode for transmitting symbols in a physical sidelink shared channel (PSSCH); and transmitting, by the UE, symbols based on the RM mode.

[0006] Some embodiments relate to a method of operating a system, wherein the PSSCH is formatted based on a quality of service (QoS) attribute level including one or more of priority, reliability, delay, communication range, or a combination thereof.

[0007] Some embodiments relate to a method of operating a system wherein the PSSCH is formatted based on sidelink control information (SCI) or sidelink feedback control information (SFCI), the sidelink feedback control information comprising hybrid automatic repeat request (HARQ) feedback.

[0008] Some embodiments relate to a method of operating a system, wherein transmitting symbols further comprises transmitting based on a sub-channelization process, wherein the sub-channelization process comprises a sub-channel comprising M consecutive PSCCH resources, wherein M may be a value greater than or equal to 1.

[0009] Some embodiments relate to a method of operating a system, the method also comprising configuring, by a UE, a subchannel size associated with a subchannel to utilize a subcarrier spacing (SCS) and a frequency spectrum within a carrier bandwidth.

[0010] Some embodiments relate to a method of operating a system, the method also comprising deriving, by a UE, a subchannel size from a plurality of subchannels and a plurality of physical resource blocks (PRBs) in a vehicle-to-everything (V2X) resource pool.

[0011] Some embodiments relate to a method of operating a system wherein the subchannel size is equal to or greater than the number of M consecutive PSCCH resources.

[0012] Some embodiments relate to a non-transitory computer-readable medium having instructions stored thereon, which when executed by a computing system causes the computing system to perform operations. The operations include selecting a rate matching (RM) mode based on a scheduling decision for transmitting symbols in a physical sidelink shared channel (PSSCH); and transmitting symbols based on the RM mode.

[0013] Some embodiments relate to a non-transitory computer-readable medium, wherein the PSSCH is formatted based on a quality of service (QoS) attribute level including one or more of priority, reliability, delay, communication range, or a combination thereof.

[0014] Some embodiments relate to a non-transitory computer-readable medium, wherein the PSSCH is formatted based on sidelink control information (SCI) or sidelink feedback control information (SFCI), the sidelink feedback control information comprising hybrid automatic repeat request (HARQ) feedback.

[0015] Some embodiments relate to a non-transitory computer-readable medium, wherein the operations further comprise transmitting symbols based on a sub-channelization process, wherein the sub-channelization process comprises a sub-channel comprising M consecutive PSCCH resources, wherein M may be a value greater than or equal to 1.

[0016] Some embodiments relate to a non-transitory computer-readable medium, wherein the operations further comprise configuring a subchannel size associated with the subchannel to utilize a frequency spectrum within a subcarrier spacing (SCS) and a carrier bandwidth.

[0017] Some embodiments relate to a non-transitory computer-readable medium, wherein the operations further comprise deriving a subchannel size from a plurality of subchannels and a plurality of physical resource blocks (PRBs) in a vehicle-to-everything (V2X) resource pool.

[0018] Some embodiments relate to a non-transitory computer-readable medium, wherein the subchannel size is equal to or greater than the number of M consecutive PSCCH resources.

[0019] Some embodiments relate to a system including a processor and a radio frequency integrated circuit. The processor is configured to select a rate matching (RM) mode based on a scheduling decision for transmitting symbols in a physical side link shared channel (PSSCH). The radio frequency integrated circuit is configured to transmit symbols based on the RM mode.

[0020] Some embodiments are directed to a system wherein the PSSCH is formatted based on a quality of service (QoS) attribute level including one or more of priority, reliability, delay, communication range, or a combination thereof.

[0021] Some embodiments are directed to a system wherein the PSSCH is formatted based on sidelink control information (SCI) or sidelink feedback control information (SFCI) including hybrid automatic repeat request (HARQ) feedback.

[0022] Some embodiments relate to a system wherein the RFIC is further configured to transmit symbols based on a sub-channelization process, wherein the sub-channelization process includes a sub-channel containing M consecutive PSCCH resources, wherein M can be a value greater than or equal to 1.

[0023] Some embodiments relate to a system wherein the processor is further configured to configure a subchannel size associated with a subchannel to utilize a frequency spectrum within a subcarrier spacing (SCS) and a carrier bandwidth.

[0024] Some embodiments relate to a system wherein the processor is further configured to derive the subchannel size from a plurality of subchannels and a plurality of physical resource blocks (PRBs) in a vehicle-to-everything (V2X) resource pool. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 Structures resulting in different polymerizations according to embodiments are shown.

[0026] Figure 2 An example of PSCCH and PSSCH resource configuration according to an implementation scheme is shown.

[0027] Figure 3 An exemplary RM mode 0 is shown according to an embodiment.

[0028] Figure 4 An exemplary RM mode 1 according to an embodiment is shown.

[0029] Figure 5 An exemplary RM mode 2 according to an embodiment is shown.

[0030] Figure 6 An exemplary RM mode 3 according to an embodiment is shown.

[0031] Figure 7 An example of PSCCH transmission according to an embodiment is shown.

[0032] Figure 8 Short and long PSCCH according to an embodiment are shown.

[0033] Fig. 9 Gap symbols and AGC / transient symbols are shown according to an implementation.

[0034] Fig.10An exemplary HARQ feedback timeline for different PSCCH / PSFCHs carrying HARQ feedback allocation options is shown according to an embodiment.

[0035] Fig.11 An exemplary system architecture according to an embodiment is shown.

[0036] Fig.12 Another exemplary system architecture according to an embodiment is shown.

[0037] Fig.13 Another exemplary system architecture according to an embodiment is shown.

[0038] Fig.14 A block diagram of exemplary infrastructure equipment is shown, according to an embodiment.

[0039] Fig.15 A block diagram of an exemplary platform according to an embodiment is shown.

[0040] Fig.16 A block diagram of a baseband circuit and a front-end module according to an embodiment is shown.

[0041] Fig.17 A block diagram illustrating exemplary protocol functionality that may be implemented in a wireless communication device according to an embodiment.

[0042] Fig.18 A block diagram of an exemplary computer system that can be used to implement various embodiments is shown.

[0043] Fig.19 A method of operating a system according to an embodiment is shown.

[0044] Features and advantages of the embodiments will become more apparent from the detailed description set forth below when taken in conjunction with the accompanying drawings, wherein like reference characters identify corresponding elements throughout. In the accompanying drawings, like reference numerals generally indicate identical, functionally similar, and / or structurally similar elements. The drawing in which an element first appears is indicated by the leftmost digit in the corresponding reference numeral. DETAILED DESCRIPTION

[0045] abbreviation

[0046] For the purposes of this document, the following abbreviations may be applied to the examples and implementations discussed herein but are not intended to be limiting.

[0047] 3GPP Third Generation Partnership Project

[0048] 4G Fourth Generation

[0049] 5G Fifth Generation

[0050] 5GC 5G Core Network

[0051] ACK

[0052] AF Application Function

[0053] AM Confirmation Mode

[0054] AMBR Aggregate Maximum Bit Rate

[0055] AMF Access and Mobility Management Function

[0056] AN Access Network

[0057] ANR Automatic Neighbor Relation

[0058] AP application protocol, antenna port, access point

[0059] API Application Programming Interface

[0060] APN Access Point Name

[0061] ARP Assignment Retention Priority

[0062] ARQ Automatic Repeat Request

[0063] AS Access Layer

[0064] ASN.1 Abstract Syntax Notation

[0065] AUSF authentication server function

[0066] AWGN Additive White Gaussian Noise

[0067] BCH Broadcast Channel

[0068] BER Bit Error Rate

[0069] BFD Beam Fault Detection

[0070] BLER Block Error Rate

[0071] BPSK Binary Phase Shift Keying

[0072] BRAS Broadband Remote Access Server

[0073] BSS Business Support System

[0074] BS Base Station

[0075] BSR Buffer Status Report

[0076] BW Bandwidth

[0077] BWP Bandwidth Part

[0078] C-RNTI Cell Radio Network Temporary Identifier

[0079] CA Carrier Aggregation, Certification Authority

[0080] CAPEX Capital Expenditure

[0081] CBRA Contention-based random access

[0082] CC component carrier, country code, encryption checksum

[0083] CCA Clear Channel Assessment

[0084] CCE Control Channel Element

[0085] CCCH Common Control Channel

[0086] CE Coverage Enhancement

[0087] CDM Content Delivery Network

[0088] CDMA Code Division Multiple Access

[0089] CFRA Contention-free random access

[0090] CG Cell Group

[0091] CI Cell ID

[0092] CID Cell ID (eg, positioning method)

[0093] CIM Common Information Model

[0094] CIR Carrier to Interference Ratio

[0095] CK Cryptographic Key

[0096] CM Connection Management, Conditionally Mandatory

[0097] CMAS Commercial Mobile Alert Service

[0098] CMD command

[0099] CMS Cloud Management System

[0100] CO Conditional optional

[0101] CoMP Coordinated Multipoint

[0102] CORESET Control Resource Set

[0103] COTS Commercial Off-the-Shelf

[0104] CP Control Plane, Cyclic Prefix, Attachment Point

[0105] CPD Connection Point Descriptor

[0106] CPE user terminal equipment

[0107] CPICH Common Pilot Channel

[0108] CQI Channel Quality Indicator

[0109] CPU CSI processing unit, central processing unit

[0110] C / R Command / Response field bit

[0111] CRAN Cloud Radio Access Network, Cloud RAN

[0112] CRB Common Resource Block

[0113] CRC Cyclic Redundancy Check

[0114] CRI Channel State Information Resource Indicator, CSI-RS Resource Indicator

[0115] C-RNTI Cell RNTI

[0116] CS Circuit Switched

[0117] CSAR Cloud Service Archive

[0118] CSI Channel State Information

[0119] CSI-IM CSI interference measurement

[0120] CSI-RS CSI reference signal

[0121] CSI-RSRP CSI reference signal received power

[0122] CSI-RSRQ CSI reference signal reception quality

[0123] CSI-SINR CSI signal to interference plus noise ratio

[0124] CSMA Carrier Sense Multiple Access

[0125] CSMA / CA CSMA with collision avoidance

[0126] CSS Common Search Space, Cell Specific Search Space

[0127] CTS Clear to Send

[0128] CW codeword

[0129] CWS Contention Window Size

[0130] D2D Device to Device

[0131] DC Dual Connection, Direct Current

[0132] DCI Downlink Control Information

[0133] DF deployment preferences

[0134] DL Downlink

[0135] DMTF Distributed Management Task Force

[0136] DPDK Data Plane Development Kit

[0137] DM-RS, DMRS Demodulation Reference Signal

[0138] DN Data Network

[0139] DRB Data Radio Bearer

[0140] DRS Discovery Reference Signal

[0141] DRX Discontinuous Reception

[0142] DSL Domain Specific Language Digital Subscriber Line

[0143] DSLAM DSL Access Multiplexer

[0144] DwPTS Downlink Pilot Time Slot

[0145] E-LAN ​​Ethernet Local Area Network

[0146] E2E End-to-End

[0147] ECCA Extended Clear Channel Assessment, Extended CCA

[0148] ECCE Enhanced Control Channel Element, Enhanced CCE

[0149] ED Energy Detection

[0150] EDGE Enhanced Data Rates for GSM Evolution (GSM Evolution)

[0151] EGMF exposes governance management functions

[0152] EGPRS Enhanced GPRS

[0153] EIR Equipment Identity Register

[0154] eLAA Enhanced License Assisted Access, enhanced LAA

[0155] EM Component Manager

[0156] eMBB Enhanced Mobile Broadband

[0157] EMS Component Management System

[0158] eNB Evolved Node B, E-UTRAN Node B

[0159] EN-DC E-UTRA-NR Dual Connectivity

[0160] EPC Evolved Packet Core

[0161] EPDCCH Enhanced PDCCH, Enhanced Physical Downlink Control Channel

[0162] EPRE Energy per resource element

[0163] EPS Evolved Packet System

[0164] EREG Enhanced REG, enhanced resource element group

[0165] ETSI European Telecommunications Standards Institute

[0166] ETWS Earthquake and Tsunami Warning System

[0167] eUICC embedded UICC, embedded universal integrated circuit card

[0168] E-UTRA Evolved UTRA

[0169] E-UTRAN Evolved UTRAN

[0170] EV2X Enhanced V2X

[0171] F1AP F1 Application Protocol

[0172] F1-C F1 control plane interface

[0173] F1-U F1 User Plane Interface

[0174] FACCH Fast Associated Control Channel

[0175] FACCH / F Fast Associated Control Channel / Full Rate

[0176] FACCH / H Fast Associated Control Channel / Half Rate

[0177] FACH Forward Access Channel

[0178] FAUSCH Fast Uplink Signalling Channel

[0179] FB Function Block

[0180] FBI Feedback

[0181] FCC Federal Communications Commission

[0182] FCCH Frequency Correction Channel

[0183] FDD Frequency Division Duplex

[0184] FDM Frequency Division Multiplexing

[0185] FDMA Frequency Division Multiple Access

[0186] FE Front End

[0187] FEC Forward Error Correction

[0188] FFS for further study

[0189] FFT Fast Fourier Transform

[0190] feLAA Further Enhanced License Assisted Access, further enhanced LAA

[0191] FN Frame Number

[0192] FPGA Field Programmable Gate Array

[0193] FR Frequency Range

[0194] G-RNTI GERAN Radio Network Temporary Identity

[0195] GERAN GSM EDGE RAN, GSM EDGE Radio Access Network

[0196] GGSN Gateway GPRS Support Node

[0197] GLONASS GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Chinese: Global Navigation Satellite System)

[0198] gNB Next Generation Node B

[0199] gNB-CU gNB centralized unit, next generation Node B centralized unit

[0200] gNB-DU gNB distributed unit, next generation Node B distributed unit

[0201] GNSS Global Navigation Satellite System

[0202] GPRS General Packet Radio Service

[0203] GSM Global System for Mobile Communications, Mobile Experts Group

[0204] GTP GPRS Tunneling Protocol

[0205] GTP-U GPRS Tunneling Protocol for the User Plane

[0206] GTS Go to sleep signal (related to WUS)

[0207] GUMMEI Globally Unique MME Identifier

[0208] GUTI Globally Unique Temporary UE Identifier

[0209] HARQ Hybrid ARQ, Hybrid Automatic Repeat Request

[0210] HANDO,HO switch

[0211] HFN Superframe Number

[0212] HHO Hard Handover

[0213] HLR Home Location Register

[0214] HN Home Network

[0215] HO Switchover

[0216] HPLMN Home Public Land Mobile Network

[0217] HSDPA High Speed ​​Downlink Packet Access

[0218] HSN Hopping Sequence Number

[0219] HSPA High Speed ​​Packet Access

[0220] HSS Home Subscriber Server

[0221] HSUPA High Speed ​​Uplink Packet Access

[0222] HTTP Hypertext Transfer Protocol

[0223] HTTPS Hypertext Transfer Protocol Secure (https is http / 1.1 over SSL, i.e., port 443)

[0224] I-Block Information Block

[0225] ICCID Integrated Circuit Card Identifier

[0226] ICIC Inter-cell Interference Coordination

[0227] ID

[0228] IDFT Inverse Discrete Fourier Transform

[0229] IE Information Elements

[0230] IBE In-Band Emission

[0231] IEEE Institute of Electrical and Electronics Engineers

[0232] IEI Information Element Identifier

[0233] IEIDL Information Element Identifier Data Length

[0234] IETF Internet Engineering Task Force

[0235] IF infrastructure

[0236] IM Interference Measurement, Intermodulation, IP Multimedia

[0237] IMC IMS credentials

[0238] IMEI International Mobile Equipment Identity

[0239] IMGI International Mobile Group Identity

[0240] IMPI IP Multimedia Privacy Identity

[0241] IMPU IP Multimedia Public Identity

[0242] IMS IP Multimedia Subsystem

[0243] IMSI International Mobile Subscriber Identity

[0244] IoT

[0245] IP Internet Protocol

[0246] IPsec IP security, Internet Protocol security

[0247] IP-CAN IP connection access network

[0248] IP-M IP Multicast

[0249] IPv4 Internet Protocol version 4

[0250] IPv6 Internet Protocol version 6

[0251] IR

[0252] IS Synchronization

[0253] IRP Integration Reference Point

[0254] ISDN Integrated Services Digital Network

[0255] ISIM IM Service Identity Module

[0256] ISO International Organization for Standardization

[0257] ISP Internet Service Provider

[0258] IWF interworking function

[0259] I-WLAN Intercommunication WLAN

[0260] K is the constraint length of the convolutional code, USIM individual key

[0261] kB kilobyte (1000 bytes)

[0262] kbps kilobits per second

[0263] Kc Cryptographic key

[0264] Ki Individual user authentication key

[0265] KPI Key Performance Indicator

[0266] KQI Key Quality Indicator

[0267] KSI Key Set Identifier

[0268] ksps kilosymbols per second

[0269] KVM Kernel Virtual Machine

[0270] L1 Layer 1 (physical layer)

[0271] L1-RSRP Layer 1 reference signal received power

[0272] L2 Layer 2 (Data Link Layer)

[0273] L3 Layer 3 (Network Layer)

[0274] LAA License Assisted Access

[0275] LAN Local Area Network

[0276] LBT Listen before you speak

[0277] LCM Lifecycle Management

[0278] LCR Low Chip Rate

[0279] LCS Location Services

[0280] LCID Logical Channel ID

[0281] LI layer indicator

[0282] LLC Logical Link Control, Low Layer Compatibility

[0283] LPLMN Local PLMN

[0284] LPP LTE Positioning Protocol

[0285] LSB Least Significant Bit

[0286] LTE Long Term Evolution

[0287] LWA LTE-WLAN Aggregation

[0288] LWIP LTE / WLAN radio level integration with IPsec tunneling

[0289] LTE Long Term Evolution

[0290] M2M Machine to Machine

[0291] MAC Medium Access Control (Protocol Layer Context)

[0292] MAC Message Authentication Code (Security / Cryptography Context)

[0293] MAC-A MAC for authentication and key agreement (TSG T WG3 context)

[0294] MAC-I MAC for data integrity of signalling messages (TSG T WG3 context)

[0295] MANO Management and Orchestration

[0296] MBMS Multimedia Broadcast Multicast Service

[0297] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0298] MCC Mobile Country Code

[0299] MCG Master Cell Group

[0300] MCOT Maximum Channel Occupancy Time

[0301] MCS Modulation and Coding Scheme

[0302] MDAF Management Data Analysis Function

[0303] MDAS Management Data Analysis Service

[0304] Minimization of MDT-driven testing

[0305] ME Mobile Devices

[0306] MeNB Master eNB

[0307] MER message error rate

[0308] MGL Measurement Gap Length

[0309] MGRP measurement gap repetition period

[0310] MIB Master Information Block, Management Information Base

[0311] MIMO Multiple Input Multiple Output

[0312] MLC Mobile Location Center

[0313] MM Mobility Management

[0314] MME Mobility Management Entity

[0315] MN Master Node

[0316] MO measurement object, mobile station calling

[0317] MPBCH MTC Physical Broadcast Channel

[0318] MPDCCH MTC Physical Downlink Control Channel

[0319] MPDSCH MTC Physical Downlink Shared Channel

[0320] MPRACH MTC Physical Random Access Channel

[0321] MPUSCH MTC Physical Uplink Shared Channel

[0322] MPLS Multi-Protocol Label Switching

[0323] MS Mobile Station

[0324] MSB Most Significant Bit

[0325] MSC Mobile Switching Center

[0326] MSI minimum system information, MCH scheduling information

[0327] MSID Mobile Station Identifier

[0328] MSIN Mobile Station Identification Number

[0329] MSISDN Mobile Subscriber ISDN Number

[0330] MT mobile station called, mobile terminal

[0331] MTC Machine Type Communication

[0332] mMTC Massive MTC, Massive Machine Type Communication

[0333] MU-MIMO Multi-User MIMO

[0334] MWUS MTC wake-up signal, MTC WUS

[0335] NACK Negative Acknowledgement

[0336] NAI Network Access Identifier

[0337] NAS Non-Access Stratum, Non-Access Stratum

[0338] NCT Network Connection Topology

[0339] NEC network capabilities exposed

[0340] NE-DC NR-E-UTRA dual connectivity

[0341] NEF Network Exposure Function

[0342] NF Network Function

[0343] NFP Network Forwarding Path

[0344] NFPD Network Forwarding Path Descriptor

[0345] NFV Network Function Virtualization

[0346] NFVI NFV Infrastructure

[0347] NFVO NFV Orchestrator

[0348] NG Next generation, next generation

[0349] NGEN-DC NG-RAN E-UTRA-NR Dual Connectivity

[0350] NM Network Manager

[0351] NMS Network Management System

[0352] N-PoP Network Point of Presence

[0353] NMIB, N-MIB Narrowband MIB

[0354] NPBCH Narrowband Physical Broadcast Channel

[0355] NPDCCH Narrowband Physical Downlink Control Channel

[0356] NPDSCH Narrowband Physical Downlink Shared Channel

[0357] NPRACH Narrowband Physical Random Access Channel

[0358] NPUSCH Narrowband Physical Uplink Shared Channel

[0359] NPSS Narrowband Primary Synchronization Signal

[0360] NSSS Narrowband Secondary Synchronization Signal

[0361] NR New Radio, Neighbor Relations

[0362] NRF NF Repository Functionality

[0363] NRS Narrowband Reference Signal

[0364] NS Network Services

[0365] NSA Non-standalone operation mode

[0366] NSD Network Service Descriptor

[0367] NSR Network Service Record

[0368] NSSAI Network Slice Selection Assistance Information

[0369] S-NNSAI Single NSSAI

[0370] NSSF network slice selection function

[0371] NW Network

[0372] NWUS Narrowband wake-up signal, narrowband WUS

[0373] NZP Non Zero Power

[0374] O&M Operation and Maintenance

[0375] ODU2 Optical Channel Data Unit - Type 2

[0376] OFDM Orthogonal Frequency Division Multiplexing

[0377] OFDMA Orthogonal Frequency Division Multiple Access

[0378] OOB Out of Band

[0379] OOS Out of Sync

[0380] OPEX Operating Expenditure

[0381] OSI Other System Information

[0382] OSS Operation Support System

[0383] OTA

[0384] PAPR Peak to Average Power Ratio

[0385] PAR Peak to Average Ratio

[0386] PBCH Physical Broadcast Channel

[0387] PC Power Control, Personal Computer

[0388] PCC Primary Component Carrier, Primary CC

[0389] PCell Primary Cell

[0390] PCI Physical Cell ID, Physical Cell Identity

[0391] PCEF Policy and Charging Enforcement Function

[0392] PCF Policy Control Function

[0393] PCRF Policy Control and Charging Rules Function

[0394] PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol Layer

[0395] PDCCH Physical Downlink Control Channel

[0396] PDCP Packet Data Convergence Protocol

[0397] PDN Packet Data Network, Public Data Network

[0398] PDSCH Physical Downlink Shared Channel

[0399] PDU Protocol Data Unit

[0400] PEI Persistent Equipment Identifier

[0401] PFD Packet Flow Description

[0402] P-GW PDN Gateway

[0403] PHICH Physical Hybrid ARQ Indicator Channel

[0404] PHY Physical Layer

[0405] PLMN Public Land Mobile Network

[0406] PIN Personal Identification Number

[0407] PM performance measurement

[0408] PMI Precoding matrix indicator

[0409] PNF Physical Network Function

[0410] PNFD Physical Network Functional Descriptor

[0411] PNFR Physical Network Function Record

[0412] POC PTT over Cellular

[0413] PP,PTP Point to Point

[0414] PPP Point-to-Point Protocol

[0415] PRACH Physical RACH

[0416] PRB Physical Resource Block

[0417] PRG Physical Resource Group

[0418] ProSe Proximity-based Services

[0419] PRS Positioning Reference Signal

[0420] PRR Packet Receive Radio

[0421] PS Packet Service

[0422] PSBCH Physical Sidelink Broadcast Channel

[0423] PSDCH Physical Sidelink Downlink Channel

[0424] PSCCH Physical Sidelink Control Channel

[0425] PSSCH Physical Sidelink Shared Channel

[0426] PSCell Primary SCell

[0427] PSS Primary Synchronization Signal

[0428] PSTN Public Switched Telephone Network

[0429] PT-RS Phase Tracking Reference Signal

[0430] PTT Push to Talk

[0431] PUCCH Physical Uplink Control Channel

[0432] PUSCH Physical Uplink Shared Channel

[0433] QAM Quadrature Amplitude Modulation

[0434] QCI QoS Class Identifier

[0435] QCL Quasi-Co-sited

[0436] QFI QoS flow ID, QoS flow identifier

[0437] QoS Quality of Service

[0438] QPSK Quadrature (Quaternary) Phase Shift Keying

[0439] QZSS Quasi-Zenith Satellite System

[0440] RA-RNTI Random Access RNTI

[0441] RAB Radio Access Bearer, Random Access Burst

[0442] RACH Random Access Channel

[0443] RADIUS Remote Authentication Dial-In User Service

[0444] RAN Radio Access Network

[0445] RAND random number (for authentication)

[0446] RAR Random Access Response

[0447] RAT Radio Access Technology

[0448] RAU Routing Area Update

[0449] RB Resource Block, Radio Bearer

[0450] RBG Resource Block Group

[0451] REG Resource Element Group

[0452] Rel Release

[0453] REQ Request

[0454] RF

[0455] RI Rank Indicator

[0456] RIV Resource Indicator Value

[0457] RL Radio Link

[0458] RLC Radio Link Control, Radio Link Control Layer

[0459] RLC AM RLC Acknowledgement Mode

[0460] RLC UM RLC Unacknowledged Mode

[0461] RLF Radio Link Failure

[0462] RLM Radio Link Monitoring

[0463] RLM-RS Reference signal for RLM

[0464] RM Registration Management

[0465] RMC Reference Measurement Channel

[0466] RMSI Remaining MSI, Remaining Minimum System Information

[0467] RN Relay Node

[0468] RNC Radio Network Controller

[0469] RNL Radio Network Layer

[0470] RNTI Radio Network Temporary Identifier

[0471] ROHC Robust Header Compression

[0472] RRC Radio Resource Control, Radio Resource Control Layer

[0473] RRM Radio Resource Management

[0474] RS reference signal

[0475] RSRP Reference Signal Received Power

[0476] RSRQ Reference Signal Received Quality

[0477] RSSI Received Signal Strength Indicator

[0478] RSU Road Side Unit

[0479] RSTD Reference Signal Time Difference

[0480] RTP Real Time Protocol

[0481] RTS Ready to Send

[0482] RTT Round Trip Time

[0483] Rx receive, receive, receiver

[0484] S1AP S1 Application Protocol

[0485] S1-MME is used for S1 control plane

[0486] S1-U S1 for user plane

[0487] S-GW Service Gateway

[0488] S-RNTI SRNC Radio Network Temporary Identifier

[0489] S-TMSI SAE temporary mobile station identifier

[0490] SA Standalone Operation Mode

[0491] SAE system architecture evolution

[0492] SAP Service Access Point

[0493] SAPD Service Access Point Descriptor

[0494] SAPI Service Access Point Identifier

[0495] SCC Secondary Component Carrier, Secondary CC

[0496] SCell Secondary Cell

[0497] SC-FDMA Single Carrier Frequency Division Multiple Access

[0498] SCG Secondary Cell Group

[0499] SCM Security Context Management

[0500] SCS Subcarrier Spacing

[0501] SCTP Stream Control Transmission Protocol

[0502] SDAP Service Data Adaptation Protocol, Service Data Adaptation Protocol Layer

[0503] SDL Supplemental Downlink

[0504] SDNF Structured Data Storage Network Function

[0505] SDP Service Discovery Protocol (Bluetooth related)

[0506] SDSF structured data storage function

[0507] SDU Service Data Unit

[0508] SEAF Security Anchoring Function

[0509] SeNB Assisted eNB

[0510] SEPP Security Edge Protection Proxy

[0511] SFI Slot Format Indicator

[0512] SFTD Space Frequency Time Diversity, SFN and Frame Timing Difference

[0513] SFN System Frame Number

[0514] SgNB

[0515] SGSN Serving GPRS Support Node

[0516] S-GW Service Gateway

[0517] SI System Information

[0518] SI-RNTI System Information RNTI

[0519] SIB System Information Block

[0520] SIM Subscriber Identity Module

[0521] SIP Session Initiation Protocol

[0522] SiP System in Package

[0523] SL Side Link

[0524] SLA Service Level Agreement

[0525] SM Session Management

[0526] SMF session management functions

[0527] SMS Short Message Service

[0528] SMSF SMS Function

[0529] SMTC SSB-based measurement timing configuration

[0530] SN Secondary node, serial number

[0531] SoC System on Chip

[0532] SON Self-Organizing Network

[0533] SpCell Special Cell

[0534] SP-CSI-RNTI Semi-persistent CSI RNTI

[0535] SPS Semi-persistent Scheduling

[0536] SQN Serial Number

[0537] SR Scheduling Request

[0538] SRB Signalling Radio Bearer

[0539] SRS Sounding Reference Signal

[0540] SS Sync Signal

[0541] SSB Synchronization Signal Block, SS / PBCH Block

[0542] SSBRI SS / PBCH block resource indicator, synchronization signal block resource indicator

[0543] SSC Session and Service Continuity

[0544] SS-RSRP Reference signal received power based on synchronization signal

[0545] SS-RSRQ Reference signal reception quality based on synchronization signal

[0546] SS-SINR Signal to Interference and Noise Ratio based on synchronization signal

[0547] SSS Secondary synchronization signal

[0548] SSSG Search Space Group

[0549] SSSIF Search Space Set Indicator

[0550] SST Slice / Service Type

[0551] SU-MIMO Single User MIMO

[0552] SUL Supplementary Uplink

[0553] TA timing advance, tracking area

[0554] TAC Tracking Area Code

[0555] TAG Timing Advance Group

[0556] TAU Tracking Area Updates

[0557] TB Transfer Block

[0558] TBS Transport Block Size

[0559] TBD To be defined

[0560] TCI Transmission Configuration Indicator

[0561] TCP transport communication protocol

[0562] TDD Time Division Duplex

[0563] TDM Time Division Multiplexing

[0564] TDMA Time Division Multiple Access

[0565] TE Terminal Equipment

[0566] TEID Tunnel Endpoint Identifier

[0567] TFT Business Flow Template

[0568] TMSI Temporary Mobile Subscriber Identity

[0569] TNL Transport Network Layer

[0570] TPC Transmit Power Control

[0571] TPMI Transmitted Precoding Matrix Indicator

[0572] TR Technical Report

[0573] TRP,TRxP Transmission Receive Point

[0574] TRS Tracking Reference Signal

[0575] TRx Transceiver

[0576] TS Technical Specification, Technical Standard

[0577] TTI Transmission Time Interval

[0578] Tx transmission, transmission, transmitter

[0579] U-RNTI UTRAN Radio Network Temporary Identity

[0580] UART Universal Asynchronous Receiver and Transmitter

[0581] UCI Uplink Control Information

[0582] UE User Equipment

[0583] UDM Unified Data Management

[0584] UDP User Datagram Protocol

[0585] UDSF Unstructured Data Storage Network Function

[0586] UICC Universal Integrated Circuit Card

[0587] UL Uplink

[0588] UM Unconfirmed Mode

[0589] UML Unified Modeling Language

[0590] UMTS Universal Mobile Telecommunications System

[0591] UP User Plane

[0592] UPF User Plane Function

[0593] URI Uniform Resource Identifier

[0594] URL Uniform Resource Locator

[0595] URLLC Ultra-Reliable Low Latency

[0596] USB Universal Serial Bus

[0597] USIM Universal Subscriber Identity Module

[0598] USS UE-specific search space

[0599] UTRA UMTS Terrestrial Radio Access

[0600] UTRAN Universal Terrestrial Radio Access Network

[0601] UwPTS Uplink Pilot Time Slot

[0602] V2I Vehicle to Infrastructure

[0603] V2P Vehicle to Pedestrian

[0604] V2V Vehicle to Vehicle

[0605] V2X: Vehicle-to-Everything

[0606] VIM Virtualization Infrastructure Manager

[0607] VL Virtual Link

[0608] VLAN virtual LAN, virtual local area network

[0609] VM Virtual Machine

[0610] VNF Virtualized Network Function

[0611] VNFFG VNF forwarding graph

[0612] VNFFGD VNF Forwarding Graph Descriptor

[0613] VNFM VNF Manager

[0614] VoIP Voice over IP, Voice over Internet Protocol

[0615] VPLMN Visited Public Land Mobile Network

[0616] VPN Virtual Private Network

[0617] VRB Virtual Resource Block

[0618] WiMAX Worldwide Interoperability for Microwave Access

[0619] WLAN Wireless Local Area Network

[0620] WMAN Wireless Metropolitan Area Network

[0621] WPAN Wireless Personal Area Network

[0622] X2-C X2 control plane

[0623] X2-U X2 user plane

[0624] XML Extensible Markup Language

[0625] XRES Expected User Response

[0626] XOR

[0627] ZC Zadoff-Chu

[0628] ZP Zero Power

[0629] Discussion of implementation plan

[0630] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the description of various embodiments will not be obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0631] It is expected that NR V2X communication systems will support a variety of use cases and deployment scenarios, including basic safety message exchange, advanced driving applications, and extended sensor sharing. While basic safety applications can largely reuse the Long Term Evolution (LTE)—the well-known 4G mobile communication standard—channel access design based on sensing performed on the transmit / transmitter (TX) side, advanced applications may require a combination of TX-based and receive / receiver (RX)-based sensing channel access schemes to achieve higher data rates and reliability. It is important to note that these new use cases mainly assume sidelink communications of either multicast or unicast type, where knowledge of the intended message recipients can help adapt TX and RX behavior to select the best resources in terms of system capacity and link performance.

[0632] In broadcast systems, there is no accurate characterization of the intended receivers and the corresponding propagation channels, which results in the only approach to collision avoidance being transmitter-based channel sensing for resource selection. Note that this approach was adopted as a solution for Rel. 14 V2V communications in LTE. It is also well known that such approaches do not directly ensure RX channel quality due to multiple challenges such as hidden node interference, in-band emissions, and near-far problems.

[0633] TX-based channel sensing schemes, if directly applied to unicast and multicast operations, targeted to be supported by NR V2X, will substantially limit the achievable link reliability and spectral efficiency due to the same issues of hidden node interference, in-band emissions and near-far effect. It should be noted that due to the pre-association, authorization, discovery procedures, at least from a higher layer perspective, it can be assumed that the intended receiver / receiver group for unicast and multicast is known. Therefore, this type of link may employ more advanced collision avoidance schemes based on a combination of TX-based and RX-based sensing.

[0634] The introduction of unicast links together with broadcast operations in the same spectrum requires consideration of seamless coexistence of both communication types. Therefore, at least the introduction of unicast links into a broadcast system should not significantly degrade the performance of the broadcast system. Additionally, the performance of the unicast system should not be significantly degraded in the case of mixed unicast and broadcast traffic compared to a unicast-only scenario. To ensure such coexistence, a distributed communication mode can be designed to consider different types of links, and a unified channel sensing approach and control signaling design can be employed.

[0635] In order to optimize the operation of the various services mentioned in the same spectrum, the control channel design for the sidelink plays a vital role. In the present invention, the design and procedures of the sidelink control channel (PSCCH) are described using the following components: (1) a common PSCCH structure for handling independent and non-independent PSCCH; (2) the structure and procedures of the PSCCH carrying the sidelink control information (SCI) for scheduling PSSCH; (3) the structure and procedures of the independent PSCCH and PSFCH; (4) enabling the system to support both traffic types without performance degradation. As a result, even a flexible communication system can be used for use cases that have not been considered so far, because all possible traffic types are foreseeable.

[0636] General PSCCH structure

[0637] According to current agreements, the PSCCH may have at least the following characteristics: (1) it may be transmitted before the associated PSSCH in non-overlapping symbols, (2) it may be transmitted in symbols overlapping with the associated PSSCH, (3) it may have at least an OFDM waveform (DFT-s-OFDM has not yet been confirmed), and (4) it may carry at least the SCI that schedules the PSSCH.

[0638] In addition to the agreed properties, the following features are envisioned for PSCCH: (1) controlled monitoring complexity, e.g., monitoring of the configured control resources should incur an expected UE complexity based on the number of channel estimation and blind decoding attempts in a given time interval; (2) variable spectral efficiency (SE) of PSCCH transmission, e.g., in cases of different QoS for unicast / multicast communications or broadcast services, different coverage of PSCCH transmission may be required, so variable SE of PSCCH is beneficial to adapt to different situations; (3) potential variable payload size, same as above, etc.

[0639] Prior disclosures have discussed exemplary embodiments for implementing variable SE for PSCCH transmission. Variable SE for PSCCH can be implemented by aggregating different numbers of basic control channel elements (CCEs), so-called SL-CCEs.

[0640] To overcome such limitations, Figure 1 A structure 102 that results in different polymerizations according to one aspect of the present disclosure is shown. Specifically, Figure 1 Examples of PSCCH formats 104 with different durations or different bandwidths according to embodiments are shown. Having a flexible structure to implement different aggregation levels of PSCCH, it is important to define the procedures for when / how to use them.

[0641] Different PSCCH formats 104 (e.g., aggregation levels of the PSCCH) may be used in different situations. For example, different services and service types (i.e., unicast, groupcast, broadcast) may require different coverage of the PSCCH carrying the SCI. In another example, there may be a standalone PSCCH without an associated PSSCH that requires different coverage than a PSCCH associated with a PSSCH.

[0642] In some embodiments, the PSCCH format 104 may be associated with a given combination of QoS attribute levels, including one or more of priority, reliability, delay, communication range, etc. The association may be configured by RRC configuration or by pre-configuration. The configuration may be UE-specific or universal for a group of UEs or for a carrier, etc. For example, a PSCCH format 104 "0" may be associated with priorities 0 and 1, a PSCCH format 104 "1" may be associated with priorities 2 and 3, etc.

[0643] In some embodiments, the PSCCH format 104 may be associated with a given SCI or SFCI format to be carried. For example, PSCCH format 104 "0" may be associated with an SCI that schedules PSSCH, PSCCH format 104 "1" may be associated with an SFCI that carries HARQ feedback, PSCCH format 104 "2" may be associated with an SFCI that carries CSI reports, and so on. Note that in the case where the SFCI carries HARQ feedback, the PSCCH format 104 may be referred to as PSFCH (Physical Sidelink Feedback Channel).

[0644] Frequency domain dimension analysis

[0645] In LTE, in order to limit the maximum number of PSCCH resources in a carrier and for channel sensing purposes, the subchannelization process was introduced. A subchannel is associated with a single PSCCH resource, and there is a configurable number of subchannels (or subchannel size) in a carrier. In NR, a similar subchannelization concept may be introduced, however, each subchannel may not be associated with a PSCCH resource. A single PSCCH resource may not satisfy all the purposes envisioned for PSCCH usage, such as PSCCH carrying SCI, independent PSCCH for reservation, preemption, feedback, etc.

[0646] Since the channel bandwidth for different combinations of carrier bandwidth and SCS is usually not an integer multiple of any cardinality (see Tables 1 and 2), the sub-channelization problem may not be trivial in NR. For example, when SCS = 30kHz, the number of PRBs is 24 at 10MHz and 51 at 20MHz, i.e., in most cases, N PRB_2X_MHz ≠2*N PRB_X_MHz Therefore, in order to accommodate different available numbers of PRBs in the channel bandwidth and fully utilize them, configurability of sub-channelization will be required.

[0647] Table 1 Transmission bandwidth configuration N of FR1 RB (From TS 38.104)

[0648] Table 1 Transmission bandwidth configuration N of FR1 RB (From TS 38.104)

[0649]

[0650] Table 2: Transmission bandwidth configuration N for FR2 RB (From TS 38.104)

[0651] Table 2: Transmission bandwidth configuration N for FR2 RB (From TS 38.104)

[0652]

[0653] In one embodiment, a subchannel contains M consecutive PSCCH resources, where M can be 1 or 2 or a larger value. Continuous here means a fairly logical domain, because the PSCCH resources themselves may not be configured in all PRBs in the frequency direction, so these PRBs may not even be adjacent. It should be noted that M=2 can be suitable for most cases, where one of the resources can usually be used to carry the PSCCH for SCI, and the other resource can be used to carry independent PSCCHs for reservations, preemption, feedback, etc. However, this may require that each combination of SCS and carrier bandwidth contains at least two sizes of PSCCH. It can be seen that for 30kHz@5MHz and 60kHz@10MHz, the number of PRBs is 11, which may be too small to contain two PSCCH resources with a bandwidth greater than 5PRBs. In this case, exceptions may be introduced, such as a small number of PSCCH resources per subchannel or a small size of PSCCH resources.

[0654] In one embodiment, two different subchannel sizes may be configured to efficiently utilize the spectrum in any combination of SCS and carrier bandwidth. The first subchannel size may be used as the primary size so that the number of resources of the second subchannel size is always equal to or less than the resources of the first size.

[0655] Alternatively, the subchannel size may not be explicitly configured, but derived from the explicitly configured number of subchannels and the number of PRBs in the V2X resource pool. Assume that the number of available PRBs in the V2X resource pool is N PRB , and the number of configured subchannels is N SBC , then the size of the first subchannel can be calculated as floor(N PRB / N SBC ), and the second subchannel size can be calculated as ceil(N PRB / N SBC ). When N SBC *floor(N PRB / N SBC ) is equal to N PRB When , there is only one subchannel size. Subchannels of different sizes may be mapped to the V2X resource pool consecutively, i.e., all subchannels of the first (or second) size, then all subchannels of the second (or first) size. Alternatively, subchannels of different sizes may be interleaved in a uniform manner.

[0656] In another embodiment related to the above sub-channelization option, the UE does not expect the resulting sub-channel size to be less than M PSCCH resources. For example, a sub-channel should contain at least one PSCCH resource.

[0657] Time domain dimension analysis

[0658] Due to limited power, dimensionalization of the control channel in time is advantageous to achieve different reliability. However, if the control is transmitted without PSSCH, system complexity caused by interference and signal power variations within the time slot may be introduced. In this sense, only a limited number of different PSCCH durations in a carrier are possible. For example, a short structure and a long structure may be introduced as described in other parts of this IDF.

[0659] Structure and procedures of PSCCH for carrying SCI and associated with PSSCH

[0660] 1. Rate Matching Assumption

[0661] Once the control resources for PSCCH monitoring are defined, an assumption should be made at the UE whether the symbols carrying PSCCH are used for PSSCH. Figure 2 The reference structure is shown in .

[0662] Figure 2 An example of PSCCH and PSSCH resource configuration according to an implementation scheme is shown. Specifically, Figure 2 It is shown that in the case of two subchannels 202, the sidelink CORESET 204 consists of the 3 first symbols of the time slot 206, each subchannel has two PSCCH resources 208, and the remaining symbols in the time slot are dedicated to PSSCH. It should be noted that as shown in the right part of the figure, there may be PRBs in the PSCCH symbol that are not occupied by PSCCH.

[0663] In one embodiment, a given PSCCH transmission may be associated with a PSSCH rate matching (RM) mode according to one of the following alternative modes described below.

[0664] RM Mode :

[0665] RM Mode 0 : Around all PSCCH resources in a resource pool or sidelink control resource set (CORESET). This mode can also cover the case where there are multiple sidelink CORESETs but only one or some or all CORESETs are rate matched.

[0666] Figure 3 An exemplary RM mode "0" 302 is shown according to an embodiment. Specifically, Figure 3 The case where data scheduled on two subchannels is rate matched around all control resources is shown. The main feature of this option is the presence of control resources in the already occupied data subchannels, which can be used to transmit PSCCH without an associated PSSCH (e.g. carrying HARQ feedback).

[0667] RM Mode 1 : Around the PSCCH carrying the indication.

[0668] Figure 4 An exemplary RM mode "1" 402 according to an embodiment is shown. Specifically, Figure 4 The case where the data scheduled on two subchannels is rate matched only around the PSCCH resources that schedule the PSSCH and the remaining PRBs in the control resource set are also used for PSSCH is shown. Assuming that other PSCCH candidates in these subchannels should not be occupied by independent PSCCHs, this rate matching mode maximizes the throughput of PSSCH.

[0669] RM Mode 2 : Around all PSCCH resources in the subchannel where the PSCCH carries the detected indication.

[0670] Figure 5 An exemplary RM mode "2" 502 according to an embodiment is shown. Specifically, Figure 5 The case where data scheduled on two subchannels is rate matched around two control resources in the subchannel where the PSCCH is detected and transmitted on other PRBs in other subchannels is shown. In this case, additional PSCCH transmissions within these subchannels are still possible, but at the same time, the PSSCH throughput is not penalized by rate matching the entire PSCCH symbol.

[0671] RM Mode 3 : Around the configured PSCCH resource subset in the sidelink COREST / resource pool.

[0672] Figure 6 An exemplary RM mode "3" 602 according to an embodiment is shown. Specifically, Figure 6 It shows the case where the data scheduled on two subchannels is rate matched around some control resources configured for the UE.

[0673] In one embodiment, with respect to the listed RM modes 0 to 3, the SCI of the scheduling PSSCH may carry a field indicating which mode the transmitter uses. For example, a 2-bit field may encode the four listed modes, where the value of the field may be converted to an RM mode index. In the case of supporting a greater or lesser number of modes in a dynamic manner, the bit field may have a larger or smaller size correspondingly.

[0674] The RM mode may be selected by the transmitter in an autonomous manner based on a scheduling decision, or as a function of the channel access procedure, (pre) configuration by the network, association with quality of service attributes (which include priority, reliability, delay, communication range). It may also be controlled by a congestion control function, for example, in the case of light load (congestion metric below a certain threshold) an RM mode that occupies more control channel symbols / PRBs (e.g., RM 1, 2) may be selected, while in the case of higher load (congestion metric above a certain threshold) an RM mode that occupies fewer control channel symbols / PRBs (e.g., RM 0) may be selected.

[0675] 2. Relationship between PSCCH frequency resources and PSSCH frequency resources

[0676] To preserve typical UE implementations, the transmission of PSCCH and PSSCH in overlapping symbols should be continuous, i.e., without gaps. In some RM modes described previously, the UE may need to rate match around some PRBs in the control region, so in these cases it would be beneficial to reserve empty PRBs at the edges of the transmission.

[0677] In one embodiment, the PSSCH resource may be the result of a channel sensing process, and the PSCCH may be determined relative to the starting PRB or center PRB of the PSSCH allocation. Specifically, taking into account the rate matching mode, the PSCCH carrying the SCI may be allocated in the lowest or highest index subchannel so that if the PSSCH is contained in the same symbol as the PSCCH, there is no gap in the total PSCCH and PSSCH transmission.

[0678] Alternatively, the PSCCH resources may be the result of a channel sensing process within a PSCCH region, which may have the restriction of only considering PSCCH candidates within a PSSCH sub-channel.

[0679] In another example, PSCCH resources may always be allocated in the center subchannel (or in a subchannel close to the center when the number of selected subchannels is even).

[0680] 3. Relationship with independent PSCCH

[0681] In the case where an independent PSCCH plays the role of a so-called reserved signal, there may be another structure defined as a scheduled PSSCH. In one embodiment, the PSCCH associated with the PSSCH may consist of two different self-decodable parts, PSCCH-1 and PSCCH-2. The first part (PSCCH-1) carries information for decoding the second part (PSCCH-2) and points to PSSCH resources in the current time slot and / or in future time slots including repeat / retransmission resources. The second part includes at least the information required to decode the PSSCH. In one embodiment, the first part PSCCH-1 may be sent in the previous time slot, or in the same time slot defined within the PSSCH transmission bandwidth.

[0682] Figure 7 An example of a PSCCH transmission 700 according to an embodiment is shown. Specifically, Figure 7 A case where PSCCH-1 and PSCCH-2 may occupy consecutive resources of the same subchannel is shown. The transmission of the first part in other time slots than the second part and the PSSCH may be determined based on loading conditions, service type, QoS, etc. For example, in the case of a lightly loaded network and / or when the PSSCH transmission 700 is relatively short and urgent, if possible, the first PSCCH part may be sent a few time slots before the second PSCCH part and the associated PSSCH, so that other UEs exclude resources to be used for data in the resource selection process.

[0683] Independent PSCCH and PSFCH

[0684] In NR V2X, it is necessary to transmit PSCCH independently without an associated PSSCH. Examples of such transmissions may be one or more of the following: (1) SFCI (Sidelink Feedback Control Information) transmission. Note that there may be multiple SFCI formats carrying different types of information, so some or all of them may be transmitted using the PSCCH format and some of them may be transmitted using a dedicated PSFCH format; (2) Reservation signal. Depending on the specific channel access scheme adopted in NR, an independent PSCCH signal may be introduced that carries reservation information, i.e., indicates which resources the UE selects for transmission in a given time window; (3) Preemption signal. Depending on the specific channel access scheme, a special signal may be introduced to clear the indicated resources to make way for urgent or high priority transmissions; (4) Resource request / grant or resource assistance information. In unicast operation, it is possible to optimize performance using sensing information from both the TX side and the RX side. Independent PSCCH transmissions may be used to exchange sensing information.

[0685] 1. Physical structure of independent PSCCH

[0686] In one embodiment, at least two versions of independent PSCCH transmissions may be introduced, namely long 804 PSCCH and short 802 PSCCH.

[0687] Figure 8 A short 802 PSCCH and a long 804 PSCCH are shown according to an implementation.

[0688] "Long" 804 PSCCH : This PSCCH format may occupy all sidelink symbols available in a slot, except for necessary handover / retuning gaps and potentially specific AGC training symbols. The bandwidth of this PSCCH format may span 1 to 2 PRBs. It shall be modulated by QPSK.

[0689] "Short" 802 PSCCH : This PSCCH format may occupy L symbols which are less than the total number of available sidelink symbols in a slot. In one example, L may be 1 or 2 or 3 symbols. The bandwidth of this PSCCH format may span from 2 to about 8 PRBs in order to keep the spectral efficiency consistent with the long PSCCH format. The position within the slot may be the beginning or the end L symbols. It shall be modulated by QPSK.

[0690] Both presented PSCCH formats may be supported and configured in a carrier. Hence, short 802 PSCCH and long 804 PSCCH may be monitored in the same / overlapping resource sets or in different resource sets.

[0691] In some embodiments, a short 802 independent PSCCH (or PSFCH) may be transmitted at the end of a timeslot. In this case, the PSCCH carrying the SCI transmitted at the beginning of the timeslot may convey an indication of the rate matching behavior around the PSCCH region / candidate at the end of the timeslot. This indication is required on the data receiver side in order to perform correct receive processing with the actual rate matching assumption and avoid blind detection of rate matching situations. On the transmitter side, the decision to transmit in symbols overlapping the PSCCH / PSFCH region at the end of the timeslot may be a function of the communication type, quality of service parameters, and the channel sensing process.

[0692] HARQ feedback transmission may not be required every time, especially when considering broadcast, multicast type operations. In this case, a semi-static configuration that provides separate resources for FB transmission may be too wasteful in terms of spectrum resources. In order to avoid the constant control overhead of such methods, the data source may perform a channel sensing process to identify whether control resources for FB transmission are available for PSSCH in a given time-frequency resource (i.e., a subchannel of a time slot). This can be done by monitoring the PSCCH and / or reservation signals of other transmitters and detecting whether FB transmission has been declared / requested. Decisions about FB resource occupancy can also be a function of radio measurements and service indicator quality (such as priority, reliability, delay, communication range, etc.) of both the data source UE and the opponent UE that plan the FB transmission.

[0693] 2. Impact of transient cycle, AGC stability, retuning / switching

[0694] The introduction of an independent front-loaded PSCCH and in some cases a front-loaded PSCCH associated with a PSSCH may require consideration of transition symbols between the PSCCH region / transmission and another part of the timeslot. There are three main reasons: (1) AGC (about 10-15 μs); (2) TX-RX switching (13 μs); (3) TX transitions due to power changes, allocation changes, frequency changes. In the current RAN4 assumptions, 10 μs may be required. It is typically absorbed by the gap portion, each signal portion in the transition, or a signal portion in the transition. In one embodiment, when a short 802 PSCCH region is configured in a carrier, it starts and ends with a gap symbol and an AGC / transient symbol, where the gap symbol and the AGC / transient symbol can be the same symbol or different symbols.

[0695] Fig. 9 The gap symbol and AGC / transient symbol according to the implementation scheme are shown. Specifically, Fig. 9The upper left portion of shows symbols #0 and #4 (denoted as "XS", where "X" represents either of the AGC / gap / transient purposes and "S" represents the symbol) used for both gap and AGC training. It should be noted that in many cases, no specific gap / AGC / transient symbol is required after the short PSCCH due to the following assumptions: (1) If AGC is not performed after the PSCCH, there may be a marginal performance difference since no RX clipping is expected because, due to the process, no signal appears after the PSCCH region and there is no corresponding association in the PSCCH region. In other words, the AGC settings trained in the PSCCH region may be well suited to processing the PSSCH region in many cases; (2) TX-RX switching may not be required in the case of independent PSCCH transmissions because, due to half-duplex in the PSCCH region, there is no opportunity to receive anything afterwards without processing the PSCCH. However, if a TX-RX switching gap is provided, reception of a PSSCH known from a previous slot may be performed. In addition, sidelink measurements can also be performed; (3) The transient period can be absorbed equally by PSCCH and PSSCH (5 μs per channel), making the impact small in the case of 15kHz and 30kHz SCS. However, this may not be the case in 60kHz SCS, where the transient period is comparable to the symbol duration.

[0696] Based on the above considerations, in another example, when a short 802 PSCCH region is configured in a carrier, it starts with a gap symbol and an AGC / transient symbol, where the gap symbol and the AGC / transient symbol can be the same symbol or different symbols, such as Fig. 9 shown in the upper right portion of .

[0697] In another special case, when a separate short 802PSCCH (or a special PSFCH channel) is configured at the end of a time slot, an "XS" symbol may be inserted before the short 802PSCCH, for example, for feedback purposes. Fig. 9 As shown in the lower left portion of , symbol #11 is the “XS” symbol before the ending 2-symbol short 802 PSCCH.

[0698] 3. The process of transmitting and receiving independent PSCCH

[0699] An example of an independent PSCCH transmission is HARQ feedback. In NR, it is agreed that both ACK status and NACK status can be reported in unicast mode. It is agreed to further consider that NACK status is reported only in groupcast mode.

[0700] The feedback transmission process needs to consider the processing time at both the data receiver (PSCCH+PSSCH processing) and the data transmitter (feedback processing). It may affect the design and resource allocation / timeline of the control channel for HARQ feedback reporting.

[0701] The processing time at the data receiver side can be expressed as NS1, which should take into account the PSCCH and associated PSSCH processing and can be measured in the number of symbols after the end of PSSCH. The processing time at the data transmitter side can be expressed as NS2, which should take into account the PSCCH / PSFCH carrying SFCI processing plus the preparation time of a new TB or ReTX TB for a specific HARQ process.

[0702] Fig.10 An exemplary HARQ feedback timeline for different PSCCH / PSFCHs carrying HARQ feedback allocation options according to an implementation scheme is shown. Specifically, Fig.10 Several examples of unicast sidelink scheduling are shown, and the HARQ timeline is shown as follows.

[0703] Example :

[0704] Example 1 : The PSCCH carrying HARQ feedback may be sent in the same PSCCH region / CORESET as the PSCCH carrying SCI. In this case, if SCI+PSSCH is sent in slot 'n', the PSCCH carrying HARQ FB may be sent in slot 'n+2' to provide processing time. After receiving feedback in slot 'n', a new TB or ReTX TB for this HARQ process may be sent in slot 'n+3' or 'n+4' depending on the processing capability.

[0705] Example 2 : The PSCCH carrying HARQ feedback may be sent in the same PSCCH region / CORESET as the PSCCH carrying the SCI. A HARQ feedback multiplexing mechanism may be applied so that the PSCCH may convey HARQ feedback for more than one HARQ process and TB. The multiplexing may be performed by the data receiver UE based on predefined rules and indications in the SCI that schedules the PSSCH. For example, if the SCI indicates that the feedback resource (e.g., time slot indication) overlaps with previously scheduled feedback, the data receiver UE multiplexes different feedback in a single transmission.

[0706] Example 3: In this embodiment, a similar process as in Embodiments 1 and 2 may be used, except that the HARQ feedback is carried as a long PSCCH format. Since the carried PSCCH lasts for the entire time slot, there is no opportunity to send a new TB or ReTX for this HARQ process in the next time slot, so at least one more time slot should be skipped after the FB transmission opportunity.

[0707] Example 4 : In this embodiment, the PSCCH carrying HARQ feedback (or a dedicated physical channel for feedback such as PSFCH) can be allocated in the end portion of a time slot in resources that do not overlap with the PSCCH carrying the SCI for scheduling the PSSCH. Since there is no time domain overlap with the SCI, there is no need to dedicate a separate time slot only for feedback purposes.

[0708] System and implementation

[0709] Fig.11 An exemplary system architecture according to an embodiment is shown. Specifically, Fig.11 An exemplary architecture of a system 1100 of a network according to various embodiments is shown. The following description is provided for an example system 1100 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0710] like Fig.11As shown, system 1100 includes UE 1100a and UE 1101b (collectively referred to as "multiple UEs 1101" or "UE 1101"). In this example, multiple UEs 1101 are shown as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument panels (ICs), head-up display (HUD) devices, on-board diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine electronic control units (ECUs), electronic / engine electronic control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0711] In some embodiments, any of the UEs 1101 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0712] UE 1101 may be configured to be connected, e.g., communicatively coupled, to RAN 1110. In an embodiment, RAN 1110 may be an NG RAN or 5G RAN, E-UTRAN, or a legacy RAN, such as UTRAN or GERAN. As used herein, the term "NGRAN" or the like may refer to RAN 1110 operating in NR or 5G system 1100, while the term "E-UTRAN" or the like may refer to RAN 1110 operating in LTE or 4G system 1100. Multiple UEs 1101 utilize connections (or channels) 1103 and 1104, respectively, each connection comprising a physical communication interface or layer (discussed in further detail below).

[0713] In this example, connections 1103 and 1104 are shown as air interfaces to achieve communication coupling, and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, multiple UEs 1101 may directly exchange communication data via a ProSe interface 1105. The ProSe interface 1105 may alternatively be referred to as a SL interface 1105, and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0714] 1101b is shown as being configured to access AP 1106 (also referred to as "WLAN node 1106," "WLAN 1106," "WLAN terminal 1106," "WT 1106," etc.) via connection 1107. Connection 1107 may include a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, where AP 1106 would include Wireless Fidelity ( ) router. In this example, AP 1106 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 1101b, RAN 1110, and AP 1106 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 1101b in RRC_CONNECTED state being configured by RAN nodes 1111a-b to utilize radio resources of LTE and WLAN. LWIP operation may involve 1101b using WLAN radio resources (e.g., connection 1107) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 1107. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0715] The RAN 1110 may include one or more AN nodes or RAN nodes 1111a and 1111b (collectively referred to as "multiple RAN nodes 1111" or "RAN node 1111") that enable connections 1103 and 1104. As used herein, the terms "access node", "access point", etc. may describe equipment that provides radio baseband functions for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN node" and the like may refer to a RAN node 1111 (e.g., a gNB) operating in an NR or 5G system 1100, while the terms "E-UTRAN node" and the like may refer to a RAN node 1111 (e.g., an eNB) operating in an LTE or 4G system 1100. According to various embodiments, the RAN node 1111 may be implemented as one or more of dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0716] In some embodiments, all or part of the RAN node 1111 may be implemented as one or more software entities running on a server computer as part of a virtual network that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes 1111; MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes 1111; or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, and the lower portions of the PHY layers are operated by individual RAN nodes 1111. This virtualization framework allows idle processor cores of the RAN node 1111 to execute other virtualized applications. In some specific implementations, separate RAN nodes 1111 may represent separate F1 interfaces ( Fig.11 In these embodiments, the gNB-DU may include one or more remote radio heads or RFEMs (see, e.g., Fig.14), and the gNB-CU may be operated by a server (not shown) located in the RAN 1110 or by a server pool in a manner similar to CRAN / vBBUP. In addition or alternatively, one or more of the RAN nodes 1111 may be a next generation eNB (ng-eNB), which is a next generation eNB that provides E-UTRA user plane and control plane protocol terminals to the UE 1101 and is connected to the 5GC (e.g., NG-eNB) via an NG interface (discussed below). Fig.13 CN 1320) RAN node.

[0717] In a V2X scenario, one or more of the RAN nodes 1111 may be an RSU or act as an RSU. The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device coupled to a radio frequency circuit located on the road side that provides connectivity support to a passing vehicle UE 1101 (vUE 1101). The RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, etc. In addition or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications as well as other cellular communication services. In addition or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

[0718] Any of the multiple RAN nodes 1111 may serve as the endpoint for the air interface protocol and may be the first point of contact for multiple UEs 1101. In some embodiments, any of the multiple RAN nodes 1111 may perform various logical functions of the RAN 1110, including but not limited to the functions of a radio network controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0719] In an embodiment, multiple UEs 1101 may be configured to communicate with each other or with any of multiple RAN nodes 1111 on a multi-carrier communication channel using OFDM communication signals according to various communication techniques, such as but not limited to OFDMA communication techniques (e.g., for downlink communication) or SC-FDMA communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiments is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0720] In some embodiments, a downlink resource grid may be used for downlink transmissions from any of a plurality of RAN nodes 1111 to a plurality of UEs 1101, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is common practice, which makes wireless resource allocation intuitive. Each column and each row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0721] According to various embodiments, multiple UEs 1101 and multiple RAN nodes 1111, 1112 communicate data (e.g., send data and receive data) through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz band.

[0722] To operate in the unlicensed spectrum, the UE 1101 and the RAN nodes 1111, 1112 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the plurality of UEs 1101 and the plurality of RAN nodes 1111, 1112 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0723] LBT is a mechanism by which equipment (e.g., multiple UEs 1101, multiple RAN nodes 1111, 1112, etc.) senses the medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include a CCA that utilizes at least an ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0724] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 802.11 technology. WLANs use a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 1101 or AP 1106, etc.) intends to transmit, the WLAN node may first perform CCA before transmission. In addition, in the case where more than one WLAN node senses the channel as idle and transmits at the same time, a backoff mechanism is used to avoid conflicts. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a conflict occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to the CSMA / CA of WLAN. In some specific implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have a LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS of LAA. In one example, the minimum CWS for LAA transmissions may be 9 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0725] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0726] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL, and may handle activities related to RRC and NAS. Other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require UE 1101 to undergo switching. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0727] The PDSCH carries user data and higher layer signaling to the UE 1101. The PDCCH carries, among other information, information about the transport format and resource allocation related to the PDSCH channel. It may also inform multiple UEs 1101 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to 1101b within a cell) may be performed on any of the RAN nodes 1111 based on channel quality information fed back from any of the UEs 1101. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of the multiple UEs 1101.

[0728] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0729] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0730] The plurality of RAN nodes 1111 may be configured to communicate with each other via the interface 1112. In an embodiment where the system 1100 is an LTE system (eg, when the CN 1120 is Fig.12 1101 in the EPC 1120), the interface 1112 may be an X2 interface 1112. The X2 interface may be defined between two or more RAN nodes 1111 (e.g., two or more eNBs, etc.) connected to the EPC 1120, and / or between two eNBs connected to the EPC 1120. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-sequence delivery of PDCP PDUs from the SeNB to the UE 1101 for user data; information about PDCP PDUs that are not delivered to the UE 1101; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from the source eNB to the target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0731] When system 1100 is a 5G or NR system (e.g., when CN 1120 is Fig.13 In an implementation scheme of the 5GC 1320 in the 5GC 1120, the interface 1112 may be an Xn interface 1112. The Xn interface is defined between two or more RAN nodes 1111 (e.g., two or more gNBs, etc.) connected to the 5GC 1120, between a RAN node 1111 (e.g., a gNB) and an eNB connected to the 5GC 1120, and / or between two eNBs connected to the 5GC 1120. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 1101 in a connected mode (e.g., a CM connection) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 1111. Mobility support may include context transfer from the old (source) service RAN node 1111 to the new (target) service RAN node 1111; and control of the user plane tunnel between the old (source) service RAN node 1111 and the new (target) service RAN node 1111. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and / or IP layer for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0732] RAN 1110 is shown as being communicatively coupled to a core network—in this embodiment, communicatively coupled to a core network (CN) 1120. CN 1120 may include a plurality of network elements 1122 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 1101) connected to CN 1120 via RAN 1110. The components of CN 1120 may be implemented in one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-mentioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 1120 may be referred to as a network slice, and a logical instance of a portion of CN 1120 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

[0733] Generally speaking, the application server 1130 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). The application server 1130 may also be configured to support one or more communication services for the UE 1101 via the EPC 1120 (e.g., VoIP session, PTT session, group communication session, social network service, etc.).

[0734] In an embodiment, CN 1120 may be a 5GC (referred to as "5GC 1120" or the like), and RAN 1110 may be connected to CN 1120 via an NG interface 1113. In an embodiment, NG interface 1113 may be divided into two parts: an NG user plane (NG-U) interface 1114, which carries traffic data between RAN node 1111 and UPF; and an S1 control plane (NG-C) interface 1115, which is a signaling interface between RAN node 1111 and AMF. Fig.13 An implementation of CN 1120 as 5GC 1120 is discussed in more detail.

[0735] In an embodiment, CN 1120 may be a 5G CN (referred to as "5GC 1120", etc.), while in other embodiments, CN 1120 may be an EPC. In the case where CN 1120 is an EPC (referred to as "EPC 1120", etc.), RAN 1110 may be connected to CN 1120 via an S1 interface 1113. In an embodiment, S1 interface 1113 may be divided into two parts: an S1 user plane (S1-U) interface 1114, which carries traffic data between RAN node 1111 and S-GW; and an S1-MME interface 1115, which is a signaling interface between RAN node 1111 and MME. Fig.12 An exemplary architecture in which CN 1120 is EPC 1120 is shown.

[0736] Fig.12 Another exemplary system architecture according to the embodiment is shown. Specifically, Fig.12 FIG. 1 shows an exemplary architecture of a system 1200 including a first CN 1220 according to various embodiments. In this example, the system 1200 may implement the LTE standard, wherein the CN 1220 is associated with Fig.11 In addition, UE 1201 can communicate with Fig.11 1 is the same as or similar to UE 1101, and E-UTRAN 1210 may be Fig.11 The CN 1220 may be a RAN that is the same as or similar to the RAN 1110 of the mobile station, and may include the RAN node 1111 discussed previously. The CN 1220 may include an MME 1221, an S-GW 1222, a P-GW 1223, an HSS 1224, and an SGSN 1225.

[0737] The MME 1221 may be similar in function to the control plane of a traditional SGSN, and may implement MM functions to track the current location of the UE 1201. The MME 1221 may perform various MM procedures to manage mobility aspects in access, such as gateway selection and tracking area list management. MM (also referred to as "EPS MM" or "EMM" in an E-UTRAN system) may refer to all applicable procedures, methods, data stores, etc. for maintaining knowledge of the current location of the UE 1201, providing user identity confidentiality, and / or performing other similar services to users / subscribers. Each UE 1201 and MME 1221 may include an MM or EMM sublayer, and when the attachment procedure is successfully completed, an MM context may be established in the UE 1201 and the MME 1221. The MM context may be a data structure or database object that stores MM-related information of the UE 1201. The MME 1221 may be coupled to the HSS 1224 via an S6a reference point, to the SGSN 1225 via an S3 reference point, and to the S-GW 1222 via an S11 reference point.

[0738] SGSN 1225 may be a node that serves UE 1201 by tracking the location of individual UE 1201 and performing security functions. In addition, SGSN 1225 may perform inter-EPC node signaling for mobility between 2G / 3G and E-UTRAN 3GPP access networks; PDN and S-GW selection as specified by MME 1221; handling of UE 1201 time zone functions as specified by MME 1221; and MME selection for handover to E-UTRAN 3GPP access network. The S3 reference point between MME 1221 and SGSN 1225 may enable user and bearer information exchange for inter-3GPP access network mobility in an idle state and / or an active state.

[0739] The HSS 1224 may include a database for network users, which includes subscription-related information for supporting network entities in handling communication sessions. The EPC 1220 may include one or several HSSs 1224, depending on the number of mobile users, the capacity of the devices, the organization of the network, etc. For example, the HSS 1224 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. The S6a reference point between the HSS 1224 and the MME 1221 may enable the transmission of subscription data and authentication data for authenticating / authorizing user access to the EPC 1220 between the HSS 1224 and the MME 1221.

[0740] The S-GW 1222 may terminate the S1 interface 1113 towards the RAN 1210 (at Fig.12The S-GW 1222 may be a local mobility anchor for inter-RAN node handovers and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and enforcement of certain policies. The S11 reference point between the S-GW 1222 and the MME 1221 may provide a control plane between the MME 1221 and the S-GW 1222. The S-GW 1222 may be coupled to the P-GW 1223 via the S5 reference point.

[0741] P-GW 1223 may terminate the SGi interface toward PDN 1230. P-GW 1223 may communicate with PDN 1230 via IP interface 1125 (see, e.g., Fig.11 ) routes data packets between EPC 1220 and external networks such as a network including application server 1130 (alternatively referred to as "AF"). In an embodiment, P-GW 1223 can communicate via IP communication interface 1125 (see, e.g. Fig.11 ) is communicatively coupled to an application server ( Fig.11 Application server 1130 or Fig.12 The S5 reference point between the P-GW 1223 and the S-GW 1222 may provide user plane tunneling and tunnel management between the P-GW 1223 and the S-GW 1222. The S5 reference point may also be used for S-GW 1222 relocation due to UE 1201 mobility and if the S-GW 1222 needs to connect to a non-co-located P-GW 1223 for required PDN connectivity. The P-GW 1223 may also include nodes for policy implementation and charging data collection, such as a PCEF (not shown). In addition, the SGi reference point between the P-GW 1223 and the packet data network (PDN) 1230 may be an operator-external public, private PDN, or an internal operator packet data network, such as for providing IMS services. The P-GW 1223 may be coupled to the PCRF 1226 via a Gx reference point.

[0742] PCRF 1226 is a policy and charging control element of EPC 1220. In a non-roaming scenario, there may be a single PCRF 1226 in a domestic public land mobile network (HPLMN) associated with an Internet Protocol Connectivity Access Network (IP-CAN) session of UE 1201. In a roaming scenario with local traffic breakout, there may be two PCRFs associated with the IP-CAN session of UE 1201: a domestic PCRF (H-PCRF) in the HPLMN and a visited PCRF (V-PCRF) in a visited public land mobile network (VPLMN). PCRF 1226 may be communicatively coupled to application server 1230 via P-GW 1223. Application server 1230 may signal PCRF 1226 to indicate a new service flow and select appropriate QoS and charging parameters. PCRF 1226 may configure the rule to a PCEF (not shown) with the appropriate TFT and QCI, which initiates QoS and charging specified by application server 1230. The Gx reference point between PCRF 1226 and P-GW 1223 may allow QoS policies and charging rules to be transferred from PCRF 1226 to the PCEF in P-GW 1223. The Rx reference point may reside between PDN 1230 (or “AF 1230”) and PCRF 1226.

[0743] Fig.13 Another exemplary system architecture according to the embodiment is shown. Specifically, Fig.13 The architecture of a system 1300 including a second CN 1320 according to various embodiments is shown. The system 1300 is shown to include: a UE 1301, which may be the same or similar to the previously discussed UE 1101 and UE 1201; a (R) AN 1310, which may be the same or similar to the previously discussed RAN 1110 and RAN 1210, and which may include the previously discussed RAN node 1111; and a DN 1303, which may be, for example, an operator service, Internet access, or a third-party service; and a 5GC 1320. The 5GC 1320 may include an AUSF 1322, an AMF 1321, an SMF 1324, an NEF 1323, a PCF 1326, an NRF 1325, an UDM 1327, an AF 1328, an UPF 1302, and an NSSF 1329.

[0744] The UPF 1302 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with the DN 1303, and a branch point to support multi-host PDU sessions. The UPF 1302 may also perform packet routing and forwarding, perform packet inspection, perform the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 1302 may include an uplink classifier to support routing of traffic flows to the data network. The DN 1303 may represent various network operator services, Internet access, or third-party services. The DN 1303 may include or be similar to the application server 1130 discussed previously. UPF 1302 may interact with SMF 1324 via the N4 reference point between SMF 1324 and UPF 1302.

[0745] AUSF 1322 may store data for authenticating UE 1301 and handle authentication-related functions. AUSF 1322 may facilitate a common authentication framework for various access types. AUSF 1322 may communicate with AMF 1321 via the N12 reference point between AMF 1321 and AUSF 1322; and may communicate with UDM 1327 via the N13 reference point between UDM 1327 and AUSF 1322. In addition, AUSF 1322 may present an interface based on Nausf services.

[0746] AMF 1321 may be responsible for registration management (e.g., responsible for registering UE 1301, etc.), connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization. AMF 1321 may be the termination point of the N11 reference point between AMF 1321 and SMF 1324. AMF 1321 may provide transport for SM messages between UE 1301 and SMF 1324, and act as a transparent proxy for routing SM messages. AMF 1321 may also provide communication between UE 1301 and SMSF ( Fig.131301). The AMF 1321 may provide transport for SMS messages between the (R)AN 1310 and the UE 1301 (not shown). The AMF 1321 may act as a SEAF, which may include interaction with the AUSF 1322 and the UE 1301, receiving intermediate keys established as a result of the UE 1301 authentication process. In the case of using USIM-based authentication, the AMF 1321 may retrieve security material from the AUSF 1322. The AMF 1321 may also include an SCM function that receives keys from the SEA for deriving access network-specific keys. In addition, the AMF 1321 may be a termination point for the RAN CP interface, which may include or be the N2 reference point between the (R)AN 1310 and the AMF 1321; and the AMF 1321 may be a termination point for NAS (N1) signaling, and perform NAS encryption and integrity protection.

[0747] The AMF 1321 may also support NAS signaling with the UE 1301 over the N3 IWF interface. The N3IWF may be used to provide access to untrusted entities. The N3IWF may be the termination point for the N2 interface between the (R)AN 1310 and the AMF 1321 for the control plane, and may be the termination point for the N3 reference point between the (R)AN 1310 and the UPF 1302 for the user plane. Thus, the AMF 1321 may process N2 signaling for PDU sessions and QoS from the SMF 1324 and the AMF 1321, encapsulate / decapsulate packets for IPSec and N3 tunnels, mark N3 user plane packets in the uplink, and perform QoS corresponding to N3 packet markings, taking into account QoS requirements associated with such markings received over N2. The N3IWF may also relay uplink and downlink control plane NAS signaling between the UE 1301 and the AMF 1321 via the N1 reference point between the UE 1301 and the AMF 1321, and relay uplink and downlink user plane packets between the UE 1301 and the UPF 1302. The N3IWF also provides a mechanism for establishing an IPsec tunnel with the UE 1301. The AMF 1321 may present an interface based on the Namf service, and may be an N14 reference point between the two AMFs 1321 and the AMF 1321 and the 5G-EIR ( Fig.13 The termination point of the N17 reference point between the two (not shown).

[0748] UE 1301 may need to register with AMF 1321 in order to receive network services. RM is used to register UE 1301 with the network (e.g., AMF 1321) or deregister the UE, and establish a UE context in the network (e.g., AMF 1321). UE 1301 may operate in the RM-REGISTERED state or the RM-DEREGISTERED state. In the RM-DEREGISTERED state, UE 1301 is not registered with the network, and the UE context in AMF 1321 does not maintain valid location or routing information for UE 1301, so UE 1301 is not accessible by AMF 1321. In the RM-REGISTERED state, UE 1301 is registered with the network, and the UE context in AMF 1321 may maintain valid location or routing information for UE 1301, so UE 1301 is accessible by AMF 1321. In the RM-REGISTERED state, UE 1301 can perform a mobility registration update procedure, perform a periodic registration update procedure triggered by the expiration of a periodic update timer (for example, to notify the network that UE 1301 is still active), and perform a registration update procedure to update UE capability information or renegotiate protocol parameters with the network, etc.

[0749] AMF 1321 may store one or more RM contexts for UE 1301, each RM context being associated with a specific access right of the network. An RM context may be a data structure, a database object, etc., which indicates or stores, among other things, the registration status and periodic update timer for each access type. AMF 1321 may also store a 5GC MM context which may be the same or similar to the (E)MM context discussed previously. In various embodiments, AMF 1321 may store CE mode B restriction parameters for UE 1301 in an associated MM context or RM context. AMF 1321 may also derive values ​​from the UE's usage setting parameters already stored in the UE context (and / or MM / RM context) when necessary.

[0750] The CM may be used to establish and release a signaling connection between the UE 1301 and the AMF 1321 through the N1 interface. The signaling connection is used to implement NAS signaling exchanges between the UE 1301 and the CN 1320, and includes a signaling connection between the UE and the AN (e.g., an RRC connection or a UE-N3IWF connection for non-3GPP access) and an N2 connection of the UE 1301 between the AN (e.g., the RAN 1310) and the AMF 1321. The UE 1301 may operate in one of two CM states (CM-IDLE mode or CM-CONNECTED mode). When the UE 1301 is operating in the CM-IDLE state / mode, the UE 1301 may not have a NAS signaling connection established with the AMF 1321 through the N1 interface, and there may be a (R)AN 1310 signaling connection (e.g., N2 and / or N3 connection) for the UE 1301. When the UE 1301 is operating in the CM-CONNECTED state / mode, the UE 1301 may have a NAS signaling connection established with the AMF 1321 through the N1 interface, and there may be a (R)AN 1310 signaling connection (e.g., N2 and / or N3 connection) for the UE 1301. The establishment of the N2 connection between the (R)AN 1310 and the AMF 1321 may cause the UE 1301 to transition from the CM-IDLE mode to the CM-CONNECTED mode, and when the N2 signaling between the (R)AN 1310 and the AMF 1321 is released, the UE 1301 may transition from the CM-CONNECTED mode to the CM-IDLE mode.

[0751] SMF 1324 may be responsible for SM (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuring traffic steering of UPF to route traffic to the correct destination; terminating the interface towards the policy control function; control portion of policy enforcement and QoS; lawful interception (for SM events and interface with LI system); terminating the SM portion of NAS messages; downlink data notification; initiating AN-specific SM information sent to AN via AMF over N2; and determining the SSC mode of the session. SM may refer to the management of a PDU session, and a PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 1301 and a data network (DN) 1303 identified by a data network name (DNN). The PDU session may be established upon request by UE 1301, modified upon request by UE 1301 and 5GC 1320, and released upon request by UE 1301 and 5GC 1320 using NAS SM signaling exchanged over the N1 reference point between UE 1301 and SMF 1324. Upon request from an application server, 5GC 1320 may trigger a specific application in UE 1301. In response to receiving the trigger message, UE 1301 may deliver the trigger message (or relevant parts / information of the trigger message) to one or more identified applications in UE 1301. The identified application in UE 1301 may establish a PDU session to a specific DNN. SMF 1324 may check whether the UE 1301 request complies with the user subscription information associated with UE 1301. In this regard, SMF 1324 may retrieve and / or request to receive update notifications about SMF 1324 level subscription data from UDM 1327.

[0752] SMF 1324 may include the following roaming functions: handling local execution to apply QoS SLA (VPLMN); charging data collection and charging interface (VPLMN); lawful interception (for SM events and interface with LI system, in VPLMN); and support interaction with external DN to transmit signaling for PDU session authorization / authentication through external DN. In a roaming scenario, an N16 reference point between two SMFs 1324 may be included in the system 1300, which may be located between another SMF 1324 in the visited network and the SMF 1324 in the home network. In addition, SMF 1324 may present an interface based on Nsmf services.

[0753] NEF 1323 may provide a device for securely exposing services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, application functions (e.g., AF 1328), edge computing or fog computing systems, etc. In such embodiments, NEF 1323 may authenticate, authorize and / or restrict AF. NEF 1323 may also convert information exchanged with AF 1328 and information exchanged with internal network functions. For example, NEF 1323 may convert between AF service identifiers and internal 5GC information. NEF 1323 may also receive information from other network functions (NFs) based on the exposure capabilities of other network functions. The information may be stored at NEF 1323 as structured data, or stored at a data storage NF using a standardized interface. The stored information may then be re-exposed to other NFs and AFs by NEF 1323, and / or used for other purposes such as analysis. In addition, NEF 1323 may present an interface based on Nnef services.

[0754] NRF 1325 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information of discovered NF instances to NF instances. NRF 1325 also maintains information of available NF instances and the services they support. As used herein, the term "instantiation" and the like may refer to the creation of an instance, and "instance" may refer to the specific occurrence of an object, which may occur, for example, during the execution of a program code. In addition, NRF 1325 may present an interface based on Nnrf services.

[0755] The PCF 1326 may provide for control plane functions to enforce their policy rules, and may also support a unified policy framework for managing network behavior. The PCF 1326 may also implement a FE to access subscription information related to policy decisions in the UDR of the UDM 1327. The PCF 1326 may communicate with the AMF 1321 via the N15 reference point between the PCF 1326 and the AMF 1321, which may include the PCF 1326 in the visited network and the AMF 1321 in the case of a roaming scenario. The PCF 1326 may communicate with the AF 1328 via the N5 reference point between the PCF 1326 and the AF 1328; and communicate with the SMF 1324 via the N7 reference point between the PCF 1326 and the SMF 1324. The system 1300 and / or the CN 1320 may also include an N24 reference point between the PCF 1326 (in the home network) and the PCF 1326 in the visited network. Additionally, PCF 1326 may present an interface based on Npcf services.

[0756] UDM 1327 may process subscription-related information to support the handling of communication sessions by network entities, and may store subscription data of UE 1301. For example, subscription data may be transmitted between UDM 1327 and AMF 1321 via an N8 reference point between UDM 1327 and AMF. UDM 1327 may include two parts: application FE and UDR ( Fig.13 FE and UDR are not shown). UDR can store subscription data and policy data of UDM 1327 and PCF 1326, and / or structured data for exposure and application data of NEF 1323 (including PFD for application detection, application request information of multiple UEs 1301). Nudr service-based interface can be presented by UDR221 to allow UDM 1327, PCF 1326 and NEF 1323 to access specific sets of stored data, as well as read, update (e.g., add, modify), delete and subscribe to notifications of related data changes in UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, etc. In different transactions, several different front ends may serve the same user. UDM-FE accesses subscription information stored in UDR, and performs authentication credential processing, user identification processing, access authorization, registration / mobility management and subscription management. UDR can interact with SMF 1324 via the N10 reference point between UDM 1327 and SMF 1324. UDM 1327 may also support SMS management, where SMS-FE implements similar application logic discussed previously. In addition, UDM 1327 may present an interface based on Nudm services.

[0757] AF 1328 can provide the influence of applications on traffic routing, provide access to NCE, and interact with the policy framework for policy control. NCE can be a mechanism that allows 5GC 1320 and AF 1328 to provide information to each other via NEF 1323, which can be used for edge computing implementation. In such implementations, network operators and third-party services can be hosted near the UE 1301 access point of the attachment to achieve effective service delivery through reduced end-to-end delay and load on the transmission network. For edge computing implementation, 5GC can select UPF 1302 near UE 1301 and perform traffic steering from UPF 1302 to DN 1303 via the N6 interface. This can be based on UE subscription data, UE location and information provided by AF 1328. In this way, AF 1328 can affect UPF (re) selection and traffic routing. Based on operator deployment, when AF 1328 is considered a trusted entity, the network operator can allow AF 1328 to interact directly with the relevant NF. In addition, AF 1328 can present an interface based on Naf services.

[0758] NSSF 1329 may select a set of network slice instances to serve UE 1301. If necessary, NSSF 1329 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI. NSSF 1329 may also determine a set of AMFs to serve UE 1301, or a list of candidate AMFs 1321, based on appropriate configuration and possibly by querying NRF 1325. The selection of a set of network slice instances for UE 1301 may be triggered by AMF 1321, where UE 1301 registers by interacting with NSSF 1329, which may result in changes to AMF 1321. NSSF 1329 may interact with AMF 1321 via the N22 reference point between AMF 1321 and NSSF 1329; and may communicate with AMF 1321 via the N31 reference point ( Fig.13 The NSSF 1329 may communicate with another NSSF 1329 in the visited network (not shown). In addition, the NSSF 1329 may present an interface based on the Nnssf service.

[0759] As discussed previously, CN 1320 may include SMSF, which may be responsible for SMS subscription checking and verification, and relaying SM messages from other entities, such as SMS-GMSC / IWMSC / SMS routers, to UE 1301 or from the UE to other entities. SMS may also interact with AMF 1321 and UDM 1327 for notification procedures so that UE 1301 is available for SMS transmission (e.g., setting a UE unreachable flag and notifying UDM 1327 when UE 1301 is available for SMS).

[0760] CN 1320 may also include Fig.13 Other elements not shown, such as data storage system / architecture, 5G-EIR, SEPP, etc. The data storage system may include SDSF, UDSF, etc. Any NF can communicate with UDSF ( Fig.13 The N18 reference point between the NF and the NF (not shown) stores or retrieves unstructured data in or from the UDSF (e.g., UE context). Individual NFs may share a UDSF for storing their respective unstructured data, or individual NFs may each have their own UDSF located at or near a single NF. In addition, the UDSF may present an interface based on the Nudsf service ( Fig.13 (not shown). The 5G-EIR may be a NF that checks the status of the PEI to determine whether to blacklist a specific equipment / entity from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on the inter-PLMN control plane interface.

[0761] Additionally, there may be more reference points and / or service-based interfaces between NF services in a NF; however, for clarity, Fig.13 These interfaces and reference points are omitted. In one example, CN 1320 may include an Nx interface, which is an inter-CN interface between an MME (e.g., MME 1221) and AMF 1321 to enable interworking between CN 1320 and CN 1220. Other example interfaces / reference points may include an interface based on N5g-EIR services presented by 5G-EIR, an N27 reference point between an NRF in a visited network and an NRF in a home network; and an N31 reference point between an NSSF in a visited network and an NSSF in a home network.

[0762] Fig.14 A block diagram of an exemplary infrastructure equipment according to an embodiment is shown. Specifically, Fig.14 An example of infrastructure equipment 1400 according to various embodiments is shown. Infrastructure equipment 1400 (or "system 1400") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 1111 and / or AP 1106 shown and described previously), an application server 1130, and / or any other element / device discussed herein. In other examples, system 1400 can be implemented in or by a UE.

[0763] System 1400 includes: application circuit 1405, baseband circuit 1410, one or more radio front end modules (RFEM) 1415, memory circuit 1420, power management integrated circuit (PMIC) 1425, power tee circuit 1430, network controller circuit 1435, network interface connector 1440, satellite positioning circuit 1445 and user interface 1450. In some embodiments, device 1400 may include additional elements, such as, for example, memory / storage, display, camera, sensor, or input / output (I / O) interface. In other embodiments, the following components may be included in more than one device. For example, the circuit may be included separately in more than one device for CRAN, vBBU or other similar implementations.

[0764] Application circuit 1405 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low dropout regulator (LDO), an interrupt controller, a serial interface such as SPI, I 2C or general programmable serial interface module, real-time clock (RTC), timer-counter including interval timer and watchdog timer, general input / output (I / O or IO), memory card controller such as secure digital (SD) multimedia card (MMC) or similar products, universal serial bus (USB) interface, mobile industry processor interface (MIPI) interface and joint test access group (JTAG) test access port. The processor (or core) of application circuit 1405 can be coupled with memory / storage element or can include memory / storage element, and can be configured to execute instructions stored in memory / storage device to enable various applications or operating systems to run on system 1400. In some embodiments, memory / storage element can be on-chip memory circuit, which can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory and / or any other type of memory device technology, such as those discussed herein.

[0765] The processor of application circuit 1405 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, application circuit 1405 may include or may be a dedicated processor / controller for operating according to various embodiments herein. As an example, the processor of application circuit 1405 may include one or more Intel FPGAs. or Processor: Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU) or Processor; ARM-based processors licensed by ARM Holdings, Ltd., such as the ARM Cortex-A series processors provided by Cavium (TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, system 1400 may not utilize application circuit 1405, and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0766] In some implementations, the application circuit 1405 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, and the like. The one or more hardware accelerators may include, for example, computer vision (CV) and / or deep learning (DL) accelerators. For example, the programmable processing device may be one or more field programmable devices (FPDs), such as field programmable gate arrays (FPGAs), and the like; programmable logic devices (PLDs), such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), and the like; ASICs, such as structured ASICs, and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of the application circuit 1405 may include logic blocks or logic architectures, as well as other interconnected resources that may be programmed to perform various functions, such as the processes, methods, functions, and the like of the various embodiments discussed herein. In such an embodiment, the circuitry of application circuit 1405 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic architectures, data, etc. in a look-up table (LUT), etc.

[0767] Baseband circuit 1410 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Fig.16 The various hardware electronic components of baseband circuit 1410 are discussed.

[0768] User interface circuitry 1450 may include one or more user interfaces designed to enable a user to interact with system 1400 or a peripheral component interface designed to enable a peripheral component to interact with system 1400. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touch pad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power interface, etc.

[0769] The radio front end module (RFEM) 1415 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Fig.16 Antenna array 1611), and the RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 1415 that combines both millimeter wave antennas and sub-millimeter waves.

[0770] The memory circuit 1420 may include one or more of the following: a volatile memory including a dynamic random access memory (DRAM) and / or a synchronous dynamic random access memory (SDRAM); and a non-volatile memory (NVM) including a high-speed electrically erasable memory (commonly referred to as a "flash memory"), a phase change random access memory (PRAM), a magnetoresistive random access memory (MRAM), etc., and may be combined with and The memory circuit 1420 may be implemented as one or more of: a solder-in package integrated circuit, a socket memory module, and a plug-in memory card.

[0771] The PMIC 1425 may include a voltage regulator, a surge protector, a power alarm detection circuit, and one or more backup power sources, such as a battery or capacitor. The power alarm detection circuit may detect one or more of a power outage (undervoltage) and a surge (overvoltage) condition. The power tee circuit 1430 may provide electrical power extracted from a network cable to provide power and data connections for the infrastructure equipment 1400 using a single cable.

[0772] The network controller circuit 1435 may provide a connection to the network using a standard network interface protocol such as Ethernet, Ethernet based on a GRE tunnel, Ethernet based on a multi-protocol label switching (MPLS), or some other suitable protocol. A physical connection may be used to provide a network connection to / from the infrastructure equipment 1400 via a network interface connector 1440, which may be an electrical connection (commonly referred to as a "copper interconnect"), an optical connection, or a wireless connection. The network controller circuit 1435 may include one or more dedicated processors and / or FPGAs for communicating using one or more of the aforementioned protocols. In some specific implementations, the network controller circuit 1435 may include multiple controllers for providing connections to other networks using the same or different protocols.

[0773] The positioning circuit 1445 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a global satellite navigation system (GNSS). Examples of navigation satellite constellations (or GNSS) include the United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo system, China's Beidou Navigation Satellite System, regional navigation systems or GNSS augmentation systems (e.g., using the Indian constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbit Chart and Satellite Integrated Radio Positioning (DORIS), etc. for navigation), etc. The positioning circuit 1445 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 1445 may include a micro technology (micro PNT) IC for positioning, navigation, and timing that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 1445 may also be part of or interact with the baseband circuit 1410 and / or RFEM 1415 to communicate with nodes and components of the positioning network. The positioning circuit 1445 may also provide location data and / or time data to the application circuit 1405, which may use the data to synchronize operations with various infrastructures (e.g., RAN node 1111, etc.), etc.

[0774] Fig.14 The components shown may communicate with each other using interface circuitry that may include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX may be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems may be included, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0775] Fig.15 A block diagram of an exemplary platform according to an embodiment is shown. Specifically, Fig.15An example of a platform 1500 (or "device 1500") according to various embodiments is shown. In an embodiment, the computer platform 1500 may be suitable for use as a UE 1101, 1201, an application server 1130, and / or any other element / device discussed herein. The platform 1500 may include any combination of components shown in the example. The components of the platform 1500 may be implemented as an integrated circuit (IC), part of an IC, a discrete electronic device, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 1500, or as components otherwise incorporated within a chassis of a larger system. Fig.15 The block diagram is intended to show a high-level view of the components of computer platform 1500. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0776] Application circuit 1505 includes circuits such as, but not limited to, one or more processors (or processor cores), cache memory, and LDO, interrupt controller, serial interface (such as SPI), I 2 The processor (or core) of the application circuit 1505 may be coupled to or may include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 1500. In some embodiments, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0777] The processor of the application circuit 1505 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSPs, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, multi-threaded processors, ultra-low voltage processors, embedded processors, some other known processing elements, or any suitable combination thereof. In some embodiments, the application circuit 1505 may include or may be a dedicated processor / controller for operating according to various embodiments herein.

[0778] As an example, the processor of the application circuit 1505 may include a processor based on Architecture Core TM Processors such as Quark TM 、Atom TM , i3, i5, i7 or MCU-class processors, or available from Santa Clara, CA company( The processor of application circuit 1505 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s A5-A9 processors, Snapdragon by Technologies, Inc. TM Processor, Texas Instruments, Open Multimedia Applications Platform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 1505 can be part of a system on a chip (SoC), in which the application circuit 1505 and other components are formed as a single integrated circuit or a single package, such as Edison TM or Galileo TM SoC board.

[0779] Additionally or alternatively, the application circuit 1505 may include circuits such as, but not limited to, one or more field programmable devices (FPDs) such as FPGAs, etc.; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high capacity PLDs (HCPLDs), etc.; ASICs such as structured ASICs, etc.; programmable SoCs (PSoCs); etc. In such embodiments, the circuits of the application circuit 1505 may include logic blocks or logic structures, and other interconnected resources that can be programmed to perform various functions such as the processes, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuits of the application circuit 1505 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuse, etc.)) for storing logic blocks, logic structures, data, etc. in look-up tables (LUTs), etc.

[0780] Baseband circuit 1510 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits. Fig.16 The various hardware electronic components of baseband circuit 1510 are discussed.

[0781] The RFEM 1515 may include a millimeter wave (mmWave) RFEM and one or more sub-millimeter wave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-millimeter wave RFICs may be physically separated from the mmWave RFEM. The RFIC may include connections to one or more antennas or antenna arrays (see, e.g., below). Fig.16 Antenna array 1611), and the RFEM can be connected to multiple antennas. In an alternative implementation, both millimeter wave and sub-millimeter wave radio functions can be implemented in the same physical RFEM 1515 that combines both millimeter wave antennas and sub-millimeter waves.

[0782] The memory circuit 1520 may include any number and type of memory devices for providing a fixed amount of system memory. For example, the memory circuit 1520 may include one or more of the following: volatile memory, including random access memory (RAM), dynamic RAM (DRAM) and / or synchronous dynamic RAM (SDRAM); and non-volatile memory (NVM), including high-speed electrically erasable memory (commonly referred to as flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuit 1520 may be developed according to a Joint Electron Device Engineering Council (JEDEC) low power double data rate (LPDDR) based design such as LPDDR2, LPDDR3, LPDDR4, etc. The memory circuit 1520 may be implemented as one or more of a solder-in package integrated circuit, a single die package (SDP), a dual die package (DDP), or a quad die package (Q17P), a socketed memory module, a dual in-line memory module (DIMM) including a micro DIMM or a mini DIMM, and / or soldered to a motherboard via a ball grid array (BGA). In a low-power implementation, the memory circuit 1520 may be an on-chip memory or register associated with the application circuit 1505. In order to provide persistent storage of information such as data, applications, operating systems, etc., the memory circuit 1520 may include one or more mass storage devices, which may include, among others, a solid state disk drive (SSDD), a hard disk drive (HDD), a micro HDD, a resistive change memory, a phase change memory, a holographic memory, or a chemical memory. For example, the computer platform 1500 may be combined with a computer system obtained from and Three-dimensional (3D) cross-point (XPOINT) memory.

[0783] Removable memory circuitry 1523 may include devices, circuitry, housings / casings, ports or receptacles, etc., for coupling portable data storage devices to platform 1500. These portable data storage devices may be used for mass storage, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, micro SD cards, xD picture cards, etc.), as well as USB flash drives, optical disks, external HDDs, etc.

[0784] The platform 1500 may further include an interface circuit (not shown) for connecting external devices to the platform 1500. External devices connected to the platform 1500 via the interface circuit include a sensor circuit 1521 and an electromechanical component (EMC) 1522, and a removable memory device coupled to a removable memory circuit 1523.

[0785] Sensor circuitry 1521 comprises a device, module, or subsystem that is intended to detect events or changes in its environment, and to send information about the detected events (sensor data) to some other device, module, subsystem, etc. Examples of such sensors include, among others: an inertial measurement unit (IMU) including an accelerometer, a gyroscope, and / or a magnetometer; a microelectromechanical system (MEMS) or nanoelectromechanical system (NEMS) including a three-axis accelerometer, a three-axis gyroscope, and / or a magnetometer; a level sensor; a flow sensor; a temperature sensor (e.g., a thermistor); a pressure sensor; a barometric pressure sensor; a gravity meter; an altimeter; an image capture device (e.g., a camera or a lensless aperture); a light detection and ranging (LiDAR) sensor; a proximity sensor (e.g., an infrared radiation detector, etc.), a depth sensor, an ambient light sensor, an ultrasonic transceiver; a microphone or other similar audio capture device; etc.

[0786] EMC 1522 includes devices, modules or subsystems that are intended to enable platform 1500 to change its state, position and / or orientation or to move or control mechanisms or (sub) systems. In addition, EMC 1522 can be configured to generate messages / signaling and send messages / signaling to other components of platform 1500 to indicate the current state of EMC 1522. Examples of EMC 1522 include one or more power switches, relays (including electromechanical relays (EMR) and / or solid-state relays (SSR)), actuators (e.g., valve actuators, etc.), audible sound generators, visual warning devices, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks and / or other similar electromechanical components. In an embodiment, platform 1500 is configured to operate one or more EMC 1522 based on one or more capture events and / or instructions or control signals received from service providers and / or various clients.

[0787] In some specific implementations, the interface circuit may connect the platform 1500 to the positioning circuit 1545. The positioning circuit 1545 includes a circuit for receiving and decoding signals transmitted / broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) may include the United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's Beidou navigation satellite system, regional navigation systems or GNSS augmentation systems (e.g., NAVIC, Japan's QZSS, France's DORIS, etc.), etc. The positioning circuit 1545 may include various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, etc. for facilitating OTA communications) to communicate with components of the positioning network such as navigation satellite constellation nodes. In some embodiments, the positioning circuit 1545 may include a micro PNT IC that uses a master timing clock to perform position tracking / estimation without GNSS assistance. The positioning circuit 1545 may also be part of or interact with the baseband circuit 1410 and / or RFEM 1515 to communicate with nodes and components of the positioning network. Positioning circuitry 1545 may also provide position data and / or time data to application circuitry 1505 , which may use the data to synchronize operations with various infrastructure (eg, radio base stations) for use in turn-by-turn navigation applications, and the like.

[0788] In some implementations, the interface circuit may connect the platform 1500 with a near field communication (NFC) circuit 1540. The NFC circuit 1540 is configured to provide contactless short-range communication based on the radio frequency identification (RFID) standard, where magnetic field induction is used to enable communication between the NFC circuit 1540 and an NFC-enabled device (e.g., an "NFC touch point") external to the platform 1500. The NFC circuit 1540 includes an NFC controller coupled to an antenna element and a processor coupled to the NFC controller. The NFC controller may be a chip / IC that provides NFC functionality to the NFC circuit 1540 by executing an NFC controller firmware and an NFC stack. The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to transmit a short-range RF signal. The RF signal may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transfer stored data to the NFC circuit 1540, or initiate data transfer between the NFC circuit 1540 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) proximate to the platform 1500.

[0789] The driver circuit 1546 may include software and hardware elements for controlling specific devices embedded in, attached to, or otherwise communicatively coupled to the platform 1500. The driver circuit 1546 may include various drivers to allow other components of the platform 1500 to interact with or control various input / output (I / O) devices that may be present in or connected to the platform 1500. For example, the driver circuit 1546 may include: a display driver for controlling and allowing access to a display device, a touch screen driver for controlling and allowing access to a touch screen interface of the platform 1500, a sensor driver for obtaining sensor readings of the sensor circuit 1521 and controlling and allowing access to the sensor circuit 1521, an EMC driver for obtaining an actuator position of the EMC 1522 and / or controlling and allowing access to the EMC 1522, a camera driver for controlling and allowing access to an embedded image capture device, and an audio driver for controlling and allowing access to one or more audio devices.

[0790] A power management integrated circuit (PMIC) 1525 (also referred to as “power management circuit 1525”) may manage power provided to various components of the platform 1500. Specifically, the PMIC 1525 may control power selection, voltage scaling, battery charging, or DC-DC conversion relative to the baseband circuit 1510. When the platform 1500 is capable of being powered by a battery 1530, for example, when the device is included in UE 1101, 1201, the PMIC 1525 may be generally included.

[0791] In some embodiments, the PMIC 1525 may control or otherwise be part of various power saving mechanisms of the platform 1500. For example, if the platform 1500 is in the RRC_Connected state, in which the platform is still connected to the RAN node because it expects to receive traffic soon, then after a period of inactivity, the platform may enter a state known as discontinuous reception mode (DRX). During this state, the platform 1500 may be powered off for short time intervals, thereby saving power. If there is no data traffic activity for an extended period of time, the platform 1500 may transition to the RRC_Idle state, in which the platform is disconnected from the network and no operations such as channel quality feedback, handover, etc. are performed. The platform 1500 enters a very low power state and performs paging, in which the platform wakes up again periodically to listen to the network and then powers off again. The platform 1500 may not receive data in this state; to receive data, the platform may transition back to the RRC_Connected state. Additional power saving modes may prevent the device from using the network for longer than the paging interval (ranging from a few seconds to a few hours). During this time, the device cannot connect to the network and may be completely powered off. Any data sent during this time will incur significant latency, and it is assumed that latency is acceptable.

[0792] The battery 1530 can power the platform 1500, but in some examples, the platform 1500 can be mounted in a fixed location and can have a power source coupled to a power grid. The battery 1530 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, the battery 1530 can be a typical lead-acid car battery.

[0793] In some implementations, the battery 1530 may be a "smart battery" that includes or is coupled to a battery management system (BMS) or a battery monitoring integrated circuit. The BMS may be included in the platform 1500 to track the state of charge (SoCh) of the battery 1530. The BMS may be used to monitor other parameters of the battery 1530, such as the state of health (SoH) and state of function (SoF) of the battery 1530 to provide fault prediction. The BMS may transmit information about the battery 1530 to the application circuit 1505 or other components of the platform 1500. The BMS may also include an analog-to-digital (ADC) converter that allows the application circuit 1505 to directly monitor the voltage of the battery 1530 or the current from the battery 1530. The battery parameters may be used to determine actions that the platform 1500 may perform, such as transmission frequency, network operation, sensing frequency, etc.

[0794] A power block or other power source coupled to the grid can be coupled to the BMS to charge the battery 1530. In some examples, the power block can be replaced with a wireless power receiver to obtain power wirelessly, for example, through a loop antenna in the computer platform 1500. In these examples, a wireless battery charging circuit can be included in the BMS. The specific charging circuit selected can depend on the size of the battery 1530 and therefore the current required. Charging can be performed using the aviation fuel standard published by the Aviation Fuel Alliance, the Qi wireless charging standard published by the Wireless Power Alliance, or the Rezence charging standard published by the Wireless Power Alliance.

[0795] The user interface circuit 1550 includes various input / output (I / O) devices present in or connected to the platform 1500, and includes one or more user interfaces designed to implement user interaction with the platform 1500 and / or a peripheral component interface designed to implement interaction with the peripheral components of the platform 1500. The user interface circuit 1550 includes input device circuits and output device circuits. The input device circuit includes any physical or virtual means for accepting input, including, in particular, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touch screen, a microphone, a scanner, a headset, etc. The output device circuit includes any physical or virtual means for displaying information or otherwise conveying information (such as sensor readings, actuator positions, or other similar information). The output device circuitry may include any number and / or combination of audio or visual displays, including, in particular, one or more simple visual outputs / indicators (e.g., binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs, such as display devices or touch screens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where outputs of characters, graphics, multimedia objects, etc. are generated or produced by the operation of platform 1500. The output device circuitry may also include speakers or other audio emitting devices, printers, etc. In some embodiments, sensor circuitry 1521 may be used as an input device circuit (e.g., an image capture device, a motion capture device, etc.) and one or more EMCs may be used as output device circuits (e.g., actuators for providing tactile feedback, etc.). In another example, an NFC circuit may be included to read an electronic tag and / or connect to another NFC-enabled device, the NFC circuitry including an NFC controller and a processing device coupled to an antenna element. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, USB ports, audio jacks, power interfaces, etc.

[0796] Although not shown, the components of platform 1500 may communicate with each other using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCIx, PCIe, a time-triggered protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus / IX may be a proprietary bus / IX, such as used in SoC-based systems. Other bus / IX systems, such as I 2 C interface, SPI interface, point-to-point interface and power bus, etc.

[0797] Fig.16 A block diagram of a baseband circuit and a front-end module according to an embodiment is shown. Specifically, Fig.16 16 shows exemplary components of a baseband circuit 1610 and a radio front end module (RFEM) 1615 according to various embodiments. The baseband circuit 1610 corresponds to Fig.14 The baseband circuit 1410 and Fig.15 The baseband circuit 1510. RFEM 1615 corresponds to Fig.14 RFEM 1415 and Fig.15 RFEM 1515. As shown, RFEM 1615 may include at least a radio frequency (RF) circuit 1606, a front end module (FEM) circuit 1608, and an antenna array 1611 coupled together as shown.

[0798] The baseband circuit 1610 includes circuits and / or control logic components configured to execute various radio / network protocols and radio control functions that enable communication with one or more radio networks via the RF circuit 1606. The radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit 1610 may include a fast Fourier transform (FFT), precoding, or constellation mapping / demapping function. In some embodiments, the encoding / decoding circuit of the baseband circuit 1610 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. The implementation of the modulation / demodulation and encoder / decoder functions is not limited to these examples, and may include other suitable functions in other embodiments. The baseband circuit 1610 is configured to process the baseband signal received from the receiving signal path of the RF circuit 1606 and generate a baseband signal for the transmitting signal path of the RF circuit 1606. The baseband circuit 1610 is configured to communicate with the application circuit 1405 / 1505 (see Fig.14 and Fig.15 ) to generate and process baseband signals and control the operation of RF circuit 1606. Baseband circuit 1610 may handle various radio control functions.

[0799] The aforementioned circuits and / or control logic components of the baseband circuit 1610 may include one or more single-core or multi-core processors. For example, the one or more processors may include a 3G baseband processor 1604A, a 4G / LTE baseband processor 1604B, a 5G / NR baseband processor 1604C, or some other baseband processors 1604D for other existing generations, generations under development, or generations to be developed in the future (e.g., the sixth generation (6G), etc.). In other embodiments, some or all of the functions of the baseband processors 1604A-1604D may include a module stored in the memory 1604G and executed via a central processing unit (CPU) 1604E. In other embodiments, some or all of the functions of the baseband processors 1604A-1604D may be provided as a hardware accelerator (e.g., FPGA, ASIC, etc.) loaded with an appropriate bitstream or logic block stored in a corresponding memory unit. In various embodiments, the memory 1604G may store program code of a real-time OS (RTOS), which, when executed by the CPU 1604E (or other baseband processor), will enable the CPU 1604E (or other baseband processor) to manage resources of the baseband circuit 1610, schedule tasks, etc. Examples of RTOS may include: Operating System Embedded (OSE) provided TM , by Mentor Nucleus RTOS provided TM , by Mentor Versatile Real-TimeExecutive (VRTX) provided by Express Provided by ThreadX TM ,Depend on FreeRTOS and REX OS provided by Open Kernel (OK) OKL4 is provided, or any other suitable RTOS, such as those discussed herein. In addition, the baseband circuit 1610 includes one or more audio digital signal processors (DSPs) 1604F. The audio DSP 1604F includes elements for compression / decompression and echo cancellation, and may include other suitable processing elements in other embodiments.

[0800] In some embodiments, each of processors 1604A-1604E includes a corresponding memory interface to send data to / receive data from memory 1604G. Baseband circuit 1610 may also include one or more interfaces for communicatively coupling to other circuits / devices, such as an interface for sending data to / receiving data from a memory external to baseband circuit 1610; an interface for sending data to / receiving data from a memory external to the baseband circuit; Fig.14 and Fig.15 An application circuit interface for sending data to / receiving data from the application circuit 1405 / 1505; Fig.16 RF circuit 1606 to send data / receive data from the RF circuit RF circuit interface; for receiving data from one or more wireless hardware elements (e.g., near field communication (NFC) components, Low power consumption components, components, etc.) to send data / receive data from these wireless hardware elements; and a power management interface for sending power or control signals to / receiving power or control signals from the PMIC 1525.

[0801] In an alternative embodiment (which can be combined with the above embodiment), the baseband circuit 1610 includes one or more digital baseband systems, which are coupled to each other and to the CPU subsystem, the audio subsystem and the interface subsystem via an interconnection subsystem. The digital baseband subsystem can also be coupled to the digital baseband interface and the mixed signal baseband subsystem via another interconnection subsystem. Each of the interconnection subsystems may include a bus system, a point-to-point connector, a network on chip (NOC) structure and / or some other suitable bus or interconnection technology, such as those discussed herein. The audio subsystem may include a DSP circuit, a buffer memory, a program memory, a voice processing accelerator circuit, a data converter circuit such as an analog-to-digital converter circuit and a digital-to-analog converter circuit, an analog circuit including one or more of an amplifier and a filter, and / or other similar components. In one aspect of the present disclosure, the baseband circuit 1610 may include a protocol processing circuit with one or more control circuit instances (not shown) to provide control functions for the digital baseband circuit and / or the radio frequency circuit (e.g., the radio front end module 1615).

[0802] although Fig.16Not shown, but in some embodiments, the baseband circuit 1610 includes various processing devices (e.g., "multi-protocol baseband processor" or "protocol processing circuit") to operate one or more wireless communication protocols and various processing devices to implement PHY layer functions. In these embodiments, the PHY layer functions include the aforementioned radio control functions. In these embodiments, the protocol processing circuit operates or implements various protocol layers / entities of one or more wireless communication protocols. In a first example, when the baseband circuit 1610 and / or the RF circuit 1606 are part of a millimeter wave communication circuit or some other suitable cellular communication circuit, the protocol processing circuit may operate LTE protocol entities and / or 5G / NR protocol entities. In the first example, the protocol processing circuit will operate MAC, RLC, PDCP, SDAP, RRC, and NAS functions. In a second example, when the baseband circuit 1610 and / or the RF circuit 1606 are part of a Wi-Fi communication system, the protocol processing circuit may operate one or more IEEE-based protocols. In the second example, the protocol processing circuit will operate Wi-Fi MAC and logical link control (LLC) functions. The protocol processing circuitry may include one or more memory structures (e.g., 1604G) for storing program code and data for operating protocol functions, and one or more processing cores for executing program code and performing various operations using data. The baseband circuitry 1610 may also support radio communications for more than one wireless protocol.

[0803] The various hardware elements of the baseband circuit 1610 discussed herein may be implemented as, for example, a solder-in substrate including one or more integrated circuits (ICs), a single packaged IC soldered to a main circuit board, or a multi-chip module containing two or more ICs. In one example, the components of the baseband circuit 1610 may be appropriately combined in a single chip or a single chipset, or disposed on the same circuit board. In another example, some or all of the components of the baseband circuit 1610 and the RF circuit 1606 may be implemented together, such as, for example, a system on a chip (SoC) or a system-level package (SiP). In another example, some or all of the components of the baseband circuit 1610 may be implemented as a separate SoC communicatively coupled to the RF circuit 1606 (or multiple instances of the RF circuit 1606). In yet another example, some or all of the components of the baseband circuit 1610 and the application circuit 1405 / 1505 may be implemented together as a separate SoC mounted to the same circuit board (e.g., a "multi-chip package").

[0804] In some embodiments, baseband circuit 1610 may provide communications compatible with one or more radio technologies. For example, in some embodiments, baseband circuit 1610 may support communications with E-UTRAN or other WMAN, WLAN, WPAN. Embodiments in which baseband circuit 1610 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuits.

[0805] RF circuit 1606 may enable communication with a wireless network through a non-solid medium using modulated electromagnetic radiation. In various embodiments, RF circuit 1606 may include switches, filters, amplifiers, etc. to facilitate communication with a wireless network. RF circuit 1606 may include a receive signal path, which may include circuitry for down-converting an RF signal received from FEM circuit 1608 and providing a baseband signal to baseband circuit 1610. RF circuit 1606 may also include a transmit signal path, which may include circuitry for up-converting a baseband signal provided by baseband circuit 1610 and providing an RF output signal for transmission to FEM circuit 1608.

[0806] In some embodiments, the receive signal path of the RF circuit 1606 may include a mixer circuit 1606A, an amplifier circuit 1606B, and a filter circuit 1606C. In some embodiments, the transmit signal path of the RF circuit 1606 may include a filter circuit 1606C and a mixer circuit 1606A. The RF circuit 1606 may also include a synthesizer circuit 1606D for synthesizing frequencies used by the mixer circuit 1606A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuit 1606A of the receive signal path may be configured to down-convert the RF signal received from the FEM circuit 1608 based on the synthesized frequency provided by the synthesizer circuit 1606D. The amplifier circuit 1606B may be configured to amplify the down-converted signal, and the filter circuit 1606C may be a low pass filter (LPF) or a band pass filter (BPF) configured to remove unwanted signals from the down-converted signal to generate an output baseband signal. The output baseband signal may be provided to baseband circuit 1610 for further processing. In some embodiments, the output baseband signal may be a zero frequency baseband signal, although this is not required. In some embodiments, the mixer circuit 1606A of the receive signal path may include a passive mixer, but the scope of the embodiments is not limited in this regard.

[0807] In some embodiments, mixer circuit 1606A of the transmit signal path may be configured to upconvert an input baseband signal based on a synthesized frequency provided by synthesizer circuit 1606D to generate an RF output signal for FEM circuit 1608. The baseband signal may be provided by baseband circuit 1610 and may be filtered by filter circuit 1606C.

[0808] In some embodiments, the mixer circuit 1606A of the receive signal path and the mixer circuit 1606A of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and up-conversion, respectively. In some embodiments, the mixer circuit 1606A of the receive signal path and the mixer circuit 1606A of the transmit signal path may include two or more mixers and may be arranged for image suppression (e.g., Hartley image suppression). In some embodiments, the mixer circuit 1606A of the receive signal path and the mixer circuit 1606A of the transmit signal path may be arranged for direct down-conversion and direct up-conversion, respectively. In some embodiments, the mixer circuit 1606A of the receive signal path and the mixer circuit 1606A of the transmit signal path may be configured for superheterodyne operation.

[0809] In some embodiments, the output baseband signal and the input baseband signal may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and the input baseband signal may be digital baseband signals. In these alternative embodiments, RF circuit 1606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuits, and baseband circuit 1610 may include a digital baseband interface to communicate with RF circuit 1606.

[0810] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0811] In some embodiments, synthesizer circuit 1606D may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of the embodiments is not limited in this respect, as other types of frequency synthesizers may also be suitable. For example, synthesizer circuit 1606D may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with a frequency divider.

[0812] Synthesizer circuit 1606D may be configured to synthesize an output frequency based on a frequency input and a divider control input for use by mixer circuit 1606A of RF circuit 1606. In some embodiments, synthesizer circuit 1606D may be a fractional-N / N+1 synthesizer.

[0813] In some embodiments, the frequency input may be provided by a voltage controlled oscillator (VCO), although this is not required. The divider control input may be provided by the baseband circuit 1610 or the application circuit 1405 / 1505 according to the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1405 / 1505.

[0814] The synthesizer circuit 1606D of the RF circuit 1606 may include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-mode frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by N or N+1 (e.g., based on a carry) to provide a fractional division ratio. In some example embodiments, the DLL may include a cascaded, tunable, delay element, a phase detector, a charge pump, and a set of D-type flip-flops. In these embodiments, the delay element may be configured to divide the VCO cycle into Nd equal phase groups, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0815] In some embodiments, the synthesizer circuit 1606D can be configured to generate a carrier frequency as an output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and can be used with a quadrature generator and divider circuit to generate multiple signals with multiple different phases relative to each other at the carrier frequency. In some embodiments, the output frequency can be the LO frequency (fLO). In some embodiments, the RF circuit 1606 can include an IQ / polarity converter.

[0816] FEM circuitry 1608 may include a receive signal path that may include circuitry configured to operate on RF signals received from antenna array 1611, amplify the received signals, and provide an amplified version of the received signals to RF circuitry 1606 for further processing. FEM circuitry 1608 may also include a transmit signal path that may include circuitry configured to amplify transmit signals provided by RF circuitry 1606 for transmission by one or more antenna elements in antenna array 1611. In various embodiments, amplification by the transmit or receive signal path may be accomplished only in RF circuitry 1606, only in FEM circuitry 1608, or in both RF circuitry 1606 and FEM circuitry 1608.

[0817] In some embodiments, the FEM circuit 1608 may include a TX / RX switch to switch between transmit mode and receive mode operation. The FEM circuit 1608 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit 1608 may include an LNA to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., provided to the RF circuit 1606). The transmit signal path of the FEM circuit 1608 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by the RF circuit 1606), and one or more filters for generating an RF signal for subsequent transmission by one or more antenna elements of the antenna array 1611.

[0818] The antenna array 1611 includes one or more antenna elements, each of which is configured to convert an electrical signal into a radio wave to travel through the air and convert the received radio wave into an electrical signal. For example, a digital baseband signal provided by the baseband circuit 1610 is converted into an analog RF signal (e.g., a modulated waveform), which is amplified and transmitted via the antenna elements of the antenna array 1611 including one or more antenna elements (not shown). The antenna elements may be omnidirectional, directional, or a combination thereof. The antenna elements may be formed into a variety of arrangements as known and / or discussed herein. The antenna array 1611 may include a microstrip antenna or a printed antenna fabricated on the surface of one or more printed circuit boards. The antenna array 1611 may be formed as a patch of metal foil of various shapes (e.g., a patch antenna) and may be coupled to the RF circuit 1606 and / or the FEM circuit 1608 using a metal transmission line or the like.

[0819] The processor of the application circuit 1405 / 1505 and the processor of the baseband circuit 1610 can be used to execute elements of one or more instances of the protocol stack. For example, the processor of the baseband circuit 1610 can be used alone or in combination to perform layer 3, layer 2, or layer 1 functions, while the processor of the application circuit 1405 / 1505 can utilize data received from these layers (e.g., packet data) and further perform layer 4 functions (e.g., TCP and UDP layers). As mentioned herein, layer 3 may include an RRC layer, which will be described in further detail below. As mentioned herein, layer 2 may include a MAC layer, an RLC layer, and a PDCP layer, which will be described in further detail below. As mentioned herein, layer 1 may include a PHY layer of a UE / RAN node, which will be described in further detail below.

[0820] Fig.17 A block diagram of exemplary protocol functions that can be implemented in a wireless communication device according to an embodiment is shown. Specifically, Fig.17An arrangement 1700 is included to show the interconnection between various protocol layers / entities. Various protocol layers / entities operating in conjunction with 5G / NR system standards and LTE system standards are provided. Fig.17 The following description, but Fig.17 Some or all aspects of the invention may also be applicable to other wireless communication network systems.

[0821] In addition to other higher layer functions not shown, the protocol layers of arrangement 1700 may also include one or more of PHY 1710, MAC 1720, RLC 1730, PDCP 1740, SDAP 1747, RRC 1755, and NAS layer 1757. These protocol layers may include one or more service access points (e.g., Fig.17 Items 1759, 1756, 1750, 1749, 1745, 1735, 1725 and 1715).

[0822] PHY 1710 can transmit and receive physical layer signals 1705, which can be received from or transmitted to one or more other communication devices. Physical layer signals 1705 may include one or more physical channels, such as those discussed herein. PHY 1710 may also perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and switching purposes) and other measurements used by higher layers (e.g., RRC 1755). PHY 1710 may also further perform error detection on transmission channels, forward error correction (FEC) encoding / decoding of transmission channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping to physical channels, and MIMO antenna processing. In an embodiment, an instance of PHY 1710 may process a request from an instance of MAC 1720 and provide an indication thereof via one or more PHY-SAP 1715. According to some embodiments, the request and indication transmitted via PHY-SAP 1715 may include one or more transmission channels.

[0823] An instance of MAC 1720 may process requests from an instance of RLC 1730 and provide indications thereto via one or more MAC-SAPs 1725. These requests and indications transmitted via MAC-SAP 1725 may include one or more logical channels. MAC 1720 may perform mapping between logical channels and transport channels, multiplexing MAC SDUs from one or more logical channels onto TBs to be delivered to PHY 1710 via transport channels, demultiplexing MAC SDUs from TBs delivered from PHY 1710 via transport channels to one or more logical channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via HARQ, and logical channel prioritization.

[0824] An instance of RLC 1730 may process requests from an instance of PDCP 1740 and provide indications thereto via one or more radio link control service access points (RLC-SAPs) 1735. These requests and indications transmitted via RLC-SAPs 1735 may include one or more RLC channels. RLC 1730 may operate in a variety of operating modes, including: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC 1730 may perform transmission of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transmission, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmission. RLC 1730 may also perform resegmentation of RLC data PDUs for AM data transmission, reorder RLC data PDUs for UM and AM data transmission, detect duplicate data for UM and AM data transmission, discard RLC SDUs for UM and AM data transmission, detect protocol errors for AM data transmission, and perform RLC re-establishment.

[0825] An instance of PDCP 1740 may process requests from an instance of RRC 1755 and / or an instance of SDAP 1747 and provide indications thereto via one or more Packet Data Convergence Protocol Service Access Points (PDCP-SAPs) 1745. These requests and indications transmitted via PDCP-SAPs 1745 may include one or more radio bearers. PDCP 1740 may perform header compression and decompression of IP data, maintain PDCP sequence numbers (SNs), perform in-order delivery of upper layer PDUs when lower layers are reestablished, eliminate duplication of lower layers when reestablishing lower layer SDUs for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification on control plane data, control timer-based data discard, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0826] An instance of SDAP 1747 may process requests from one or more higher layer protocol entities and provide indications thereto via one or more SDAP-SAPs 1749. These requests and indications transmitted via SDAP-SAPs 1749 may include one or more QoS flows. SDAP 1747 may map QoS flows to DRBs and vice versa, and may also mark QFIs in DL and UL packets. A single SDAP entity 1747 may be configured for a separate PDU session. In the UL direction, NG-RAN 1110 may control the mapping of QoS flows to DRBs in two different ways (reflective mapping or explicit mapping). For reflective mapping, SDAP 1747 of UE 1101 may monitor the QFI of DL packets for each DRB, and may apply the same mapping to packets flowing in the UL direction. For DRBs, SDAP 1747 of UE 1101 may map UL packets belonging to a QoS flow corresponding to the QoS flow ID and PDU session observed in the DL packets of the DRB. To implement the reflective mapping, the NG-RAN 1310 may mark the DL packets with a QoS flow ID over the Uu interface. The explicit mapping may involve the RRC 1755 configuring the SDAP 1747 with explicit mapping rules of QoS flows to DRBs, which may be stored and followed by the SDAP 1747. In an embodiment, the SDAP 1747 may be used only in NR implementations and may not be used in LTE implementations.

[0827] The RRC 1755 may configure aspects of one or more protocol layers, which may include one or more instances of PHY 1710, MAC 1720, RLC 1730, PDCP 1740, and SDAP 1747, via one or more Management Service Access Points (M-SAPs). In an embodiment, an instance of the RRC 1755 may process requests from one or more NAS entities 1757 and provide instructions thereto via one or more RRC-SAPs 1756. The main services and functions of the RRC 1755 may include broadcasting of system information (e.g., included in a MIB or SIB related to NAS), broadcasting of system information related to the access stratum (AS), paging, establishment, maintenance, and release of an RRC connection between the UE 1101 and the RAN 1110 (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance, and release of point-to-point radio bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting. These MIBs and SIBs may include one or more IEs, each of which may include a separate data field or data structure.

[0828] NAS 1757 may form the highest layer of the control plane between UE 1101 and AMF 1321. NAS 1757 may support the mobility and session management procedures of UE 1101 to establish and maintain an IP connection between UE 1101 and P-GW in the LTE system.

[0829] According to various embodiments, one or more protocol entities of arrangement 1700 may be implemented in UE 1101, RAN node 1111, AMF 1321 in NR implementation or MME 1221 in LTE implementation, UPF 1302 in NR implementation or S-GW 1222 and P-GW 1223 in LTE implementation, etc., for control plane or user plane communication protocol stacks between the aforementioned devices. In such embodiments, one or more protocol entities that may be implemented in one or more of UE 1101, gNB 1111, AMF 1321, etc. may communicate with corresponding peer protocol entities that may be implemented in or on another device (using services of corresponding lower layer protocol entities to perform such communication). In some embodiments, the gNB-CU of gNB1111 may host the gNB's RRC 1755, SDAP 1747, and PDCP1740 that control operations of one or more gNB-DUs, and the gNB-DUs of gNB 1111 may each host the RLC 1730, MAC 1720, and PHY 1710 of gNB 1111.

[0830] In a first example, the control plane protocol stack may include, in order from the highest layer to the lowest layer, NAS 1757, RRC 1755, PDCP 1740, RLC 1730, MAC 1720, and PHY 1710. In this example, an upper layer 1760 may be built on top of NAS 1757, which includes an IP layer 1761, SCTP 1762, and an application layer signaling protocol (AP) 1763.

[0831] In a NR specific implementation, AP 1763 can be an NG application protocol layer (NGAP or NG-AP) 1763 for the NG interface 1113 defined between the NG-RAN node 1111 and the AMF 1321, or AP 1763 can be an Xn application protocol layer (XnAP or Xn-AP) 1763 for the Xn interface 1112 defined between two or more RAN nodes 1111.

[0832] The NG-AP 1763 may support the functionality of the NG interface 1113 and may include an elementary procedure (EP). The NG-AP EP may be an interaction unit between the NG-RAN node 1111 and the AMF 1321. The NG-AP 1763 services may include two groups: UE-associated services (e.g., services related to the UE 1101) and non-UE-associated services (e.g., services related to the entire NG interface instance between the NG-RAN node 1111 and the AMF 1321). These services may include functions including, but not limited to: a paging function for sending a paging request to the NG-RAN node 1111 involved in a specific paging area; a UE context management function for allowing the AMF 1321 to establish, modify and / or release the UE context in the AMF 1321 and the NG-RAN node 1111; a mobility function for the UE 1101 in ECM-CONNECTED mode, for intra-system HO to support mobility within the NG-RAN, and for inter-system HO to support mobility from / to the EPS system; a NAS signaling transport function for transferring or rerouting NAS messages between the UE 1101 and the AMF 1321; a NAS signaling transport function for determining whether the AMF 1321 and the UE 1101 have a NAS message; and 1101; an NG interface management function for setting up an NG interface and monitoring errors through the NG interface; a warning message sending function for providing a means for transmitting a warning message via the NG interface or cancelling an ongoing warning message broadcast; a configuration transmission function for requesting and transmitting RAN configuration information (e.g., SON information, performance measurement (PM) data, etc.) between two RAN nodes 1111 via CN1120; and / or other similar functions.

[0833] The XnAP 1763 may support the functions of the Xn interface 1112 and may include XnAP basic mobility procedures and XnAP global procedures. The XnAP basic mobility procedures may include procedures for handling UE mobility within the NG RAN 1111 (or E-UTRAN 1210), such as handover preparation and cancellation procedures, SN state transfer procedures, UE context retrieval and UE context release procedures, RAN paging procedures, procedures related to dual connectivity, etc. The XnAP global procedures may include procedures unrelated to a specific UE 1101, such as Xn interface setup and reset procedures, NG-RAN update procedures, cell activation procedures, etc.

[0834] In an LTE specific implementation, AP 1763 can be an S1 application protocol layer (S1-AP) 1763 for an S1 interface 1113 defined between an E-UTRAN node 1111 and an MME, or AP 1763 can be an X2 application protocol layer (X2AP or X2-AP) 1763 for an X2 interface 1112 defined between two or more E-UTRAN nodes 1111.

[0835] The S1 application protocol layer (S1-AP) 1763 may support the functions of the S1 interface, and similar to the NG-AP discussed previously, the S1-AP may include an S1-AP EP. The S1-AP EP may be an interaction unit between the E-UTRAN node 1111 and the MME 1221 within the LTE CN 1120. The S1-AP 1763 services may include two groups: UE-associated services and non-UE-associated services. The functions performed by these services include, but are not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM) and configuration transmission.

[0836] The X2AP 1763 may support the functions of the X2 interface 1112 and may include an X2AP basic mobility procedure and an X2AP global procedure. The X2AP basic mobility procedure may include a procedure for handling UE mobility within the E-UTRAN 1120, such as a handover preparation and cancellation procedure, an SN state transfer procedure, a UE context retrieval and a UE context release procedure, a RAN paging procedure, a procedure related to dual connectivity, etc. The X2AP global procedure may include a procedure that is not related to a specific UE 1101, such as an X2 interface setup and reset procedure, a load indication procedure, an error indication procedure, a cell activation procedure, etc.

[0837] The SCTP layer (alternatively referred to as the SCTP / IP layer) 1762 may provide guaranteed delivery of application layer messages (e.g., NGAP or XnAP messages in NR implementations, or S1-AP or X2AP messages in LTE implementations). The SCTP 1762 may ensure reliable delivery of signaling messages between the RAN node 1111 and the AMF 1321 / MME 1221 based in part on the IP protocol supported by the IP 1761. The Internet Protocol layer (IP) 1761 may be used to perform packet addressing and routing functions. In some implementations, the IP layer 1761 may deliver and transmit PDUs using point-to-point transport. In this regard, the RAN node 1111 may include L2 and L1 layer communication links (e.g., wired or wireless) with the MME / AMF to exchange information.

[0838] In a second example, the user plane protocol stack may include SDAP 1747, PDCP 1740, RLC 1730, MAC 1720, and PHY 1710 in order from the highest layer to the lowest layer. The user plane protocol stack may be used for communication between UE 1101, RAN node 1111, and UPF 1302 in NR implementation, or communication between S-GW 1222 and P-GW 1223 in LTE implementation. In this example, the upper layer 1751 may be built on top of SDAP 1747 and may include a user datagram protocol (UDP) and IP security layer (UDP / IP) 1752, a general packet radio service (GPRS) tunneling protocol for a user plane layer (GTP-U) 1753, and a user plane PDU layer (UP PDU) 1763.

[0839] The transport network layer 1754 (also referred to as the "transport layer") may be built on top of the IP transport, and the GTP-U 1753 may be used on top of the UDP / IP layer 1752 (including the UDP layer and the IP layer) to carry the user plane PDU (UP-PDU). The IP layer (also referred to as the "Internet layer") may be used to perform packet addressing and routing functions. The IP layer may assign IP addresses to user data packets, for example, in any of the IPv4, IPv6, or PPP formats.

[0840] GTP-U 1753 may be used to carry user data within the GPRS core network and between the radio access network and the core network. For example, the transmitted user data may be packets in any of the IPv4, IPv6, or PPP formats. UDP / IP 1752 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication of selected data flows. The RAN node 1111 and the S-GW 1222 may utilize the S1-U interface to exchange user plane data via a protocol stack including an L1 layer (e.g., PHY 1710), an L2 layer (e.g., MAC 1720, RLC 1730, PDCP 1740, and / or SDAP 1747), a UDP / IP layer 1752, and GTP-U 1753. S-GW 1222 and P-GW 1223 may utilize an S5 / S8a interface to exchange user plane data via a protocol stack including an L1 layer, an L2 layer, a UDP / IP layer 1752, and a GTP-U 1753. As previously discussed, the NAS protocol may support the mobility and session management procedures of UE 1101 to establish and maintain an IP connection between UE 1101 and P-GW 1223.

[0841] In addition, despite Fig.17Not shown, but an application layer may exist above the AP 1763 and / or transport network layer 1754. The application layer may be a layer where a user of the UE 1101, RAN node 1111, or other network element interacts with a software application, for example, executed by the application circuit 1405 or the application circuit 1505, respectively. The application layer may also provide one or more interfaces for the software application to interact with the communication system (such as the baseband circuit 1610) of the UE 1101 or RAN node 1111. In some implementations, the IP layer and / or the application layer may provide the same or similar functionality as layers 5 to 7 of the open systems interconnection (OSI) model, or portions thereof (e.g., OSI layer 7—application layer, OSI layer 6—presentation layer, and OSI layer 5—session layer).

[0842] Fig.18 A block diagram of an exemplary computer system that can be used to implement various embodiments is shown. Specifically, Fig.18 is a block diagram illustrating components capable of reading instructions from a machine-readable medium or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig.18 A schematic diagram of hardware resources 1800 is shown, including one or more processors (or processor cores) 1810, one or more memory / storage devices 1820, and one or more communication resources 1830, each of which can be communicatively coupled via a bus 1840. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1802 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1800.

[0843] Processor 1810 may include, for example, processor 1812 and processor 1814. Processor 1810 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

[0844] The memory / storage device 1820 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1820 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage, etc.

[0845] The communication resources 1830 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 1804 or one or more databases 1806 via the network 1808. For example, the communication resources 1830 may include a wired communication component (e.g., for coupling via USB), a cellular communication component, an NFC component, (or Low power consumption) components, components and other communication components.

[0846] The instructions 1850 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1810 to perform any one or more of the methods discussed herein. The instructions 1850 may reside in whole or in part in at least one of the processors 1810 (e.g., in a cache memory of the processor), the memory / storage device 1820, or any suitable combination thereof. In addition, any portion of the instructions 1850 may be transmitted to the hardware resources 1800 from any combination of the peripheral device 1804 or the database 1806. Therefore, the memory of the processor 1810, the memory / storage device 1820, the peripheral device 1804, and the database 1806 are examples of computer-readable and machine-readable media.

[0847] Fig.19 A method 1900 of operating a system according to an embodiment of the present disclosure is shown. The method 1900 includes: selecting a rate matching (RM) mode by a user equipment (UE) based on a scheduling decision for transmitting symbols in a physical sidelink shared channel (PSSCH), as shown in block 1902; and transmitting symbols by the UE based on the RM mode, as shown in block 1904.

[0848] In an implementation scheme, Fig.19 The processes or steps in may be performed by one or more of the application circuit 1405 or 1505 , the baseband circuit 1410 or 1510 , or the processor 1814 .

[0849] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following example section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments shown in the example section below.

[0850] Example

[0851] Embodiment 1 may include a method (or a system for performing the method) of unicast, multicast vehicle-to-vehicle (V2V) communication or vehicle-to-everything (V2X) communication in a fifth generation (5G) or new radio (NR) system, the method comprising:

[0852] Independent control channel transmitted by UE;

[0853] A control channel associated with a data channel is transmitted by the UE;

[0854] Transmitting feedback by the second UE in response to the control and / or shared channel; or

[0855] The UE avoids half-duplex conflicts with other UEs in the group;

[0856] Embodiment 2 may include the method of embodiment 1 or some other embodiments herein, wherein the PSCCH format / aggregation level may be associated with a given combination of QoS attribute levels including one or more of priority, reliability, delay, communication range, etc.

[0857] Embodiment 3 may include the method of embodiment 1 or some other embodiments herein, wherein the PSCCH format / AL may be associated with a given SCI or SFCI format to be carried.

[0858] Embodiment 4 may include the method of embodiment 1 or some other embodiments herein, wherein the subchannel contains M consecutive PSCCH resources, where M may be a value of 1 or 2 or greater.

[0859] Embodiment 5 may include the method of embodiment 1 or some other embodiments herein, wherein two different subchannel sizes may be configured to efficiently utilize spectrum in any combination of SCS and carrier bandwidth.

[0860] Embodiment 6 may include the method of embodiment 1 or some other embodiments herein, wherein the subchannel size may not be explicitly configured, but derived from the number of subchannels and the number of PRBs explicitly configured in the V2X resource pool. Assuming that the number of available PRBs in the V2X resource pool is NPRB and the number of configured subchannels is NSBC, the first subchannel size may be calculated as floor(NPRB / NSBC) and the second subchannel size may be calculated as ceil(NPRB / NSBC).

[0861] Embodiment 7 may include the method of embodiment 1 or some other embodiments herein, wherein the UE does not expect the resulting subchannel size to be less than M PSCCH resources.

[0862] Embodiment 8 may include the method of embodiment 1 or some other embodiments herein, wherein a given PSCCH transmission may be associated with a PSSCH rate matching (RM) mode.

[0863] Embodiment 9 may include the method of embodiment 8 or some other embodiments herein, wherein the PSSCH is rate matched around all PSCCH resources in a resource pool or a sidelink control resource set (CORESET).

[0864] Embodiment 10 may include the method of embodiment 8 or some other embodiments herein, wherein the PSSCH is rate matched around a PSCCH candidate carrying an SCI that schedules the PSSCH.

[0865] Embodiment 11 may include the method of embodiment 8 or some other embodiments herein, wherein the PSSCH is rate matched around all PSCCH resources in the subchannel in which the PSCCH carries the detected indication.

[0866] Embodiment 12 may include the method of embodiment 8 or some other embodiments herein, wherein the PSSCH is rate matched around a configured subset of PSCCH resources in the sidelink COREST / resource pool.

[0867] Embodiment 13 may include the method of embodiments 8 to 12 or some other embodiments herein, wherein the SCI scheduling the PSSCH may carry a field indicating which mode the transmitter uses.

[0868] Embodiment 14 may include the methods of embodiments 8 to 12 or some other embodiments herein, wherein the rate matching mode may be selected by the transmitter in an autonomous manner based on a scheduling decision, or is a function of the channel access process, (pre) configuration by the network, and association with quality of service attributes (including priority, reliability, delay, communication range).

[0869] Embodiment 15 may include the method of embodiment 1 or some other embodiments herein, wherein the PSSCH resource may be a result of a channel sensing process and the PSCCH may be determined relative to a starting PRB or a center PRB of a PSSCH allocation.

[0870] Embodiment 16 may include the method of embodiment 1 or some other embodiments herein, wherein a PSCCH associated with a PSSCH may consist of two different self-decodable parts, PSCCH-1 and PSCCH-2. The first part (PSCCH-1) carries information for decoding the second part (PSCCH-2) and points to PSSCH resources in the current time slot and / or in future time slots including repeat / retransmission resources. The second part includes at least the information required to decode the PSSCH.

[0871] Embodiment 17 may include the method of embodiment 1 or some other embodiments herein, wherein the independent PSCCH may be one of at least two different physical formats: a long PSCCH and a short PSCCH.

[0872] Embodiment 18 may include the method of embodiment 17 or some other embodiments herein, wherein the long PSCCH may occupy all side link symbols available in the time slot except for necessary switching / retuning gaps and potential specific AGC training symbols. The bandwidth of this PSCCH format may span 1 to 2 PRBs. It should be modulated by QPSK.

[0873] Embodiment 19 may include the method of embodiment 17 or some other embodiment of this document, wherein the short PSCCH format may occupy L symbols less than the total number of available side link symbols in the time slot. In one example, L may be 1 or 2 or 3 symbols. The bandwidth of this PSCCH format may span 2 to approximately 8 PRBs to keep the spectrum efficiency consistent with the long PSCCH format. The position within the time slot may be the beginning or end of the L symbols. It should be modulated by QPSK.

[0874] Embodiment 20 may include the method of embodiment 17 or some other embodiments herein, wherein a short independent PSCCH (or PSFCH) may be transmitted at the end of a time slot. In this case, the PSCCH carrying the SCI transmitted at the beginning of the time slot may convey an indication of the rate matching behavior around the PSCCH region / candidate at the end of the time slot.

[0875] Embodiment 21 may include the method of embodiment 17 or some other embodiments herein, wherein when a short PSCCH region is configured in a carrier, it starts and ends with a gap symbol and an AGC / transient symbol, wherein the gap symbol and the AGC / transient symbol may be the same symbol or different symbols.

[0876] Embodiment 22 may include an apparatus comprising means for performing one or more elements of the method described in or related to any of Embodiments 1 to 21, or any other method or process described herein.

[0877] Embodiment 23 may include one or more non-transitory computer-readable media, which include instructions that, when one or more processors of an electronic device execute the instructions, cause the electronic device to perform one or more elements of a method described in or related to any one of Embodiments 1 to 21 or any other method or process described herein.

[0878] Embodiment 24 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of a method as described or related to any of Embodiments 1 to 21, or any other method or process described herein.

[0879] Embodiment 25 may include methods, techniques or processes described in or related to any one of Embodiments 1-21, or parts or components thereof.

[0880] Embodiment 26 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or portions thereof, described in or related to any one of Embodiments 1-21.

[0881] Embodiment 27 may include a signal as described or related to any one of Embodiments 1 to 21, or a portion or component thereof.

[0882] Embodiment 28 may include signals in a wireless network as shown and described herein.

[0883] Embodiment 29 may include a method of communicating in a wireless network as shown and described herein.

[0884] Embodiment Z09 may include a system for providing wireless communications as shown and described herein.

[0885] Embodiment 30 may include an apparatus for providing wireless communications as shown and described herein.

[0886] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be acquired from the practice of the various embodiments.

[0887] the term

[0888] For the purposes of this document, the following terms and definitions apply to the examples and implementations discussed herein but are not intended to be limiting.

[0889] As used herein, the term "circuit" refers to, is part of, or includes a hardware component such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and / or a memory (shared, dedicated, or group) configured to provide the described functions, an application specific integrated circuit (ASIC), a field programmable device (FPD) (e.g., a field programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), a digital signal processor (DSP), etc. In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuit" may also refer to a combination of one or more hardware elements and a program code for performing the functions of the program code (or a combination of circuits used in an electrical or electronic system). In these embodiments, the combination of hardware elements and program code may be referred to as a specific type of circuit.

[0890] As used herein, the term "processor circuit" refers to, is part of, or includes a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, and / or transmitting digital data. The term "processor circuit" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional processes). The terms "application circuit" and / or "baseband circuit" may be considered synonymous with "processor circuit" and may be referred to as "processor circuit".

[0891] As used herein, the term "interface circuit" refers to a circuit that enables, is a part of, or includes information exchange between two or more components or devices. The term "interface circuit" may refer to one or more hardware interfaces, such as a bus, an I / O interface, a peripheral component interface, a network interface card, etc.

[0892] As used herein, the term "user equipment" or "UE" refers to a device that has radio communication capabilities and can describe a remote user of network resources in a communication network. In addition, the terms "user equipment" or "UE" may be considered synonymous and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. In addition, the term "user equipment" or "UE" may include any type of wireless / wired device or any computing device that includes a wireless communication interface.

[0893] As used herein, the term "network element" refers to physical or virtualized equipment and / or infrastructure for providing wired or wireless communication network services. The term "network element" may be considered synonymous with and / or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN equipment, RAN node, gateway, server, virtualized VNF, NFVI, etc.

[0894] As used herein, the term "computer system" refers to any type of interconnected electronic devices, computer devices, or components thereof. Additionally, the terms "computer system" and / or "system" may refer to various components of a computer that are communicatively coupled to one another. Furthermore, the terms "computer system" and / or "system" may refer to multiple computer devices and / or multiple computing systems that are communicatively coupled to one another and configured to share computing and / or networking resources.

[0895] As used herein, the terms "appliance", "computer appliance", etc. refer to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide specific computing resources. A "virtual appliance" is a virtual machine image to be implemented by a device equipped with a hypervisor that virtualizes or emulates a computer appliance or is otherwise dedicated to providing specific computing resources.

[0896] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, and / or a physical or virtual component within a specific device, such as a computer device, a mechanical device, a memory space, a processor / CPU time and / or a processor / CPU usage rate, a processor and accelerator load, a hardware time or usage rate, a power supply, an input / output operation, a port or a network socket, a channel / link allocation, throughput, memory usage rate, storage, a network, a database and an application, a unit of work, etc. "Hardware resources" may refer to computing, storage and / or network resources provided by physical hardware elements. "Virtualized resources" may refer to computing, storage and / or network resources provided by a virtualized infrastructure to an application, a device, a system, etc. The term "network resources" or "communication resources" may refer to resources that a computer device / system can access via a communication network. The term "system resources" may refer to any kind of shared entity that provides a service, and may include computing resources and / or network resources. System resources may be considered as a set of coherent functions, network data objects or services that can be accessed through a server, wherein such system resources reside on a single host or multiple hosts and can be clearly identified.

[0897] As used herein, the term "channel" refers to any tangible or intangible transmission medium for transmitting data or data streams. The term "channel" may be synonymous and / or equivalent to "communication channel", "data communication channel", "transmission channel", "data transmission channel", "access channel", "data access channel", "link", "data link", "carrier", "radio frequency carrier" and / or any other similar terms representing a path or medium through which data is transmitted. In addition, the term "link" as used herein refers to a connection between two devices for transmitting and receiving information over a RAT.

[0898] As used herein, the terms "instantiate," "instantiate," and the like refer to the creation of an instance. "Instance" also refers to a specific occurrence of an object, which may occur, for example, during the execution of program code.

[0899] The terms "coupled," "communicatively coupled," and their derivatives are used herein. The term "coupled" may mean that two or more elements are in direct physical or electrical contact with each other, may mean that two or more elements are in indirect contact with each other but still cooperate or interact with each other, and / or may mean that one or more other elements are coupled or connected between the elements said to be coupled to each other. The term "directly coupled" may mean that two or more elements are in direct contact with each other. The term "communicatively coupled" may mean that two or more elements may be in contact with each other by means of communication, including through a wire or other interconnect connection, through a wireless communication channel or link, etc.

[0900] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual contents of an information element, or a data element that contains the contents.

[0901] The term "SMTC" refers to the SSB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

[0902] The term "SSB" refers to SS / PBCH block.

[0903] The term "primary cell" refers to an MCG cell operating on a primary frequency, where the UE either performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0904] The term "primary SCG cell" refers to an SCG cell in which a UE performs random access when reconfiguration is performed using a synchronization procedure for DC operation.

[0905] The term "secondary cell" refers to a cell that provides additional radio resources on top of a special cell for a UE configured with CA.

[0906] The term "secondary cell group" refers to a subset of serving cells including a PSCell for a UE configured with DC and zero or more secondary cells.

[0907] The term "serving cell" refers to a primary cell for a UE in RRC_CONNECTED without CA / DC configured, where there is only one serving cell including the primary cell.

[0908] The term "serving cell" refers to a cell group including a special cell for a UE configured with CA and in RRC_CONNECTED and all secondary cells.

[0909] The term "special cell" refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term "special cell" refers to the Pcell.

Claims

1. A method comprising: The user equipment UE selects a PSSCH RM mode from a plurality of physical side link shared channel PSSCH rate matching RM modes based on scheduling decision and congestion control function; generating sidelink control information SCI, the SCI carrying a field indicating a selected PSSCH RM mode; allocating, by the UE, the SCI in a lowest or highest indexed subchannel of a physical sidelink control channel (PSCCH) transmission, wherein the allocation is based on a selected PSSCH RM mode to obtain no gap between the PSCCH transmission and the PSSCH transmission; as well as The SCI is transmitted by the UE in the PSCCH transmission and symbols are transmitted in the PSSCH transmission based on the selected PSSCH RM mode.

2. The method of claim 1, wherein the PSSCH is formatted based on a quality of service (QoS) attribute level, the QoS attribute level comprising one or more of priority, reliability, delay, communication range, or a combination thereof.

3. The method of claim 1, wherein the plurality of PSSCH RM patterns comprises four patterns.

4. The method of claim 1, wherein transmitting the symbol further comprises transmitting based on a sub-channelization process, wherein the sub-channelization process comprises a sub-channel containing M consecutive PSCCH resources, wherein M is a value greater than or equal to 1.

5. The method of claim 4, further comprising configuring, by the UE, a subchannel size associated with the subchannel to utilize a subcarrier spacing SCS and a spectrum in a carrier bandwidth.

6. The method of claim 5, further comprising deriving, by the UE, the subchannel size from a plurality of subchannels and a plurality of physical resource blocks (PRBs) in a vehicle-to-everything (V2X) resource pool.

7. The method according to claim 5, wherein the subchannel size is equal to or greater than the number of the M consecutive PSCCH resources.

8. A non-transitory computer-readable medium having instructions stored thereon, the instructions, when executed by a user equipment (UE), causing the UE to perform operations comprising: Selecting a PSSCH RM mode from a plurality of physical side link shared channel PSSCH rate matching RM modes based on scheduling decision and congestion control functions; generating sidelink control information SCI, the SCI carrying a field indicating a selected PSSCH RM mode; allocating the SCI in a lowest or highest index subchannel of a physical sidelink control channel (PSCCH) transmission, wherein the allocation is based on a selected PSSCH RM mode to obtain no gap between the PSCCH transmission and the PSSCH transmission; as well as The SCI is transmitted in the PSCCH transmission and symbols are transmitted in the PSSCH transmission based on the selected PSSCH RM mode.

9. The non-transitory computer-readable medium of claim 8, wherein the PSSCH is formatted based on a quality of service (QoS) attribute level, the QoS attribute level comprising one or more of priority, reliability, delay, communication range, or a combination thereof.

10. The non-transitory computer readable medium of claim 8, wherein the plurality of PSSCH RM patterns comprises four patterns.

11. The non-transitory computer-readable medium of claim 8, wherein the operations further comprise transmitting the symbol based on a sub-channelization process, wherein the sub-channelization process comprises a sub-channel containing M consecutive PSCCH resources, wherein M is a value greater than or equal to 1.

12. The non-transitory computer-readable medium of claim 11, wherein the operations further comprise configuring a subchannel size associated with the subchannel to utilize a frequency spectrum within a subcarrier spacing (SCS) and a carrier bandwidth.

13. The non-transitory computer-readable medium of claim 12, wherein the operations further comprise deriving the subchannel size from a plurality of subchannels and a plurality of physical resource blocks (PRBs) in a vehicle-to-everything (V2X) resource pool.

14. The non-transitory computer-readable medium of claim 12, wherein the subchannel size is equal to or greater than the number of the M consecutive PSCCH resources.

15. A system comprising: A processor, the processor being configured to: Selecting a PSSCH RM mode from a plurality of physical side link shared channel PSSCH rate matching RM modes based on scheduling decision and congestion control functions; generating sidelink control information SCI, the SCI carrying a field indicating a selected PSSCH RM mode; allocating the SCI in the lowest or highest index subchannel of a physical sidelink control channel (PSCCH) transmission, wherein the allocation is based on a selected PSSCH RM mode to obtain no gap between the PSCCH transmission and the PSSCH transmission; and a radio frequency integrated circuit, the radio frequency integrated circuit being coupled to the processor, the radio frequency integrated circuit being configured to: The SCI is transmitted in the PSCCH transmission and symbols are transmitted in the PSSCH transmission based on the selected PSSCH RM mode.

16. The system of claim 15, wherein the PSSCH is formatted based on a quality of service (QoS) attribute level, the QoS attribute level comprising one or more of priority, reliability, delay, communication range, or a combination thereof.

17. The system of claim 15, wherein the plurality of PSSCH RM patterns comprises four patterns.

18. The system of claim 15, wherein the RFIC is further configured to transmit the symbol based on a sub-channelization process, wherein the sub-channelization process includes a sub-channel containing M consecutive PSCCH resources, wherein M is a value greater than or equal to 1.

19. The system of claim 18, wherein the processor is further configured to configure a subchannel size associated with the subchannel to utilize a frequency spectrum within a subcarrier spacing (SCS) and a carrier bandwidth.

20. The system of claim 19, wherein the processor is further configured to derive the subchannel size from a plurality of subchannels and a plurality of physical resource blocks (PRBs) in a vehicle-to-everything (V2X) resource pool.

Images