[go: up one dir, main page]

WO2025179521A1 - Procédé de réordonnancement adaptatif pour voix - Google Patents

Procédé de réordonnancement adaptatif pour voix

Info

Publication number
WO2025179521A1
WO2025179521A1 PCT/CN2024/079240 CN2024079240W WO2025179521A1 WO 2025179521 A1 WO2025179521 A1 WO 2025179521A1 CN 2024079240 W CN2024079240 W CN 2024079240W WO 2025179521 A1 WO2025179521 A1 WO 2025179521A1
Authority
WO
WIPO (PCT)
Prior art keywords
packets
voice
packet
status
sid
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/079240
Other languages
English (en)
Inventor
Lijie Zhang
Yong Zhong
Ying Zhang
Tao Xie
Zhiwei Wang
Qiang MIAO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Apple Inc
Original Assignee
Apple Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apple Inc filed Critical Apple Inc
Priority to PCT/CN2024/079240 priority Critical patent/WO2025179521A1/fr
Publication of WO2025179521A1 publication Critical patent/WO2025179521A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers

Definitions

  • Embodiments of the invention relate to wireless communications, including apparatuses, systems, and methods for adaptive reordering of voice packets.
  • Wireless communication systems are rapidly growing in usage.
  • wireless devices such as smart phones and tablet computers have become increasingly sophisticated.
  • many mobile devices now provide access to the internet, email, text messaging, and navigation using the global positioning system (GPS) and are capable of operating sophisticated applications that utilize these functionalities.
  • GPS global positioning system
  • LTE Long Term Evolution
  • 5G NR Fifth Generation New Radio
  • 5G-NR also simply referred to as NR
  • NR provides, as compared to LTE, a higher capacity for a higher density of mobile broadband users, while also supporting device-to-device, ultra-reliable, and massive machine type communications with lower latency and/or lower battery consumption.
  • NR may allow for more flexible UE scheduling as compared to current LTE. Consequently, efforts are being made in ongoing developments of 5G-NR to take advantage of higher throughputs possible at higher frequencies.
  • Embodiments relate to wireless communications, and more particularly to apparatuses, systems, and methods for adaptive reordering of voice packets at a user equipment (UE) .
  • a method comprises receiving, at the UE: voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer; silence insertion descriptor (SID) packets each having a PDCP SN at the PDCP layer; and a network configured reordering timer.
  • the method further comprises determining, at the UE, a voice status of the packets as: an active status when voice packets are received; or a silence status when SID packets are received.
  • the method further comprises detecting, at the UE, an SN packet gap associated with one or more missing packets.
  • the method comprises starting, at the UE, the network configured reordering timer when the SN packet gap is detected and the packet is determined to be a voice packet with the active status, or delivering the packets directly to a higher layer than the PDCP layer without starting the network configured reordering timer when the SN packet gap is detected and the packet is determined to be an SID packet with the silence status.
  • a user equipment comprising one or more processors coupled to a memory.
  • the processors are configured to receive, at the UE: voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer; silence insertion descriptor (SID) packets each having a PDCP SN at the PDCP layer; and a network configured reordering timer.
  • SN PDCP sequence number
  • SID silence insertion descriptor
  • the processors are configured to determine, at the UE, a voice status of the packets as: an active status when voice packets are received; or a silence status when SID packets are received.
  • the processors are configured to detect, at the UE, an SN packet gap associated with one or more missing packets.
  • the processors are configured to start, at the UE, the network configured reordering timer when the SN packet gap is detected and the packet is determined to be a voice packet with the active status, or deliver the packets directly to a higher layer than the PDCP layer without starting the network configured reordering timer when the SN packet gap is detected and the packet is determined to be an SID packet with the silence status.
  • the method comprises receiving, at the UE: voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer; silence insertion descriptor (SID) packets each having a PDCP SN at the PDCP layer; and a network configured reordering timer.
  • the method further comprises determining, at the UE, a voice status of the packets as: an active status when voice packets are received; or a silence status when SID packets are received.
  • the method further comprises detecting, at the UE, an SN packet gap associated with one or more missing packets in the voice packets or the SID packets received at the PDCP layer.
  • the method comprises starting, at the UE, a different second reordering timer that is less than the network configured reordering timer when the SN packet gap is detected, and an active voice status is determined.
  • the method comprises delivering, at the UE, the packets directly to a higher layer than the PDCP layer at the expiration of the different second reordering timer.
  • a user equipment comprising one or more processors coupled to a memory.
  • the processors are configured to receive, at the UE: voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer; silence insertion descriptor (SID) packets each having a PDCP SN at the PDCP layer; and a network configured reordering timer.
  • the processors are configured to determine, at the UE, a voice status of the packets as: an active status when voice packets are received; or a silence status when SID packets are received.
  • the processors are configured to detect, at the UE, an SN packet gap associated with one or more missing packets in the voice packets or the SID packets received at the PDCP layer.
  • the processors are configured to start, at the UE, a different second reordering timer that is less than the network configured reordering timer when the SN packet gap is detected, and an active voice status is determined; and deliver, at the UE, the packets directly to a higher layer than the PDCP layer at the expiration of the different second reordering timer.
  • the method comprises receiving, at the UE: voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer; and a network configured reordering timer.
  • the method further comprises determining, at the UE, a network scheduling scheme for the plurality of packets.
  • the scheduling scheme comprises receiving the plurality of packets at a first interval or the plurality of packets at a second interval. The first interval is greater than the second interval.
  • the method comprises re-calculating the network configured reordering timer for the plurality of voice packets based on the network scheduling scheme.
  • UAVs unmanned aerial vehicles
  • UACs unmanned aerial controllers
  • base stations access points
  • cellular phones tablet computers
  • wearable computing devices portable media players, and any of various other computing devices.
  • FIG. 1A illustrates an example wireless communication system according to some embodiments.
  • FIG. 1 B illustrates an example of a base station and an access point in communication with a user equipment (UE) device, according to some embodiments.
  • UE user equipment
  • FIG. 2 illustrates an example block diagram of a base station, according to some embodiments.
  • FIG. 3 illustrates an example block diagram of a server according to some embodiments.
  • FIG. 4 illustrates an example block diagram of a UE according to some embodiments.
  • FIG. 5 illustrates an example block diagram of cellular communication circuitry, according to some embodiments.
  • FIG. 6 illustrates an example of a baseband processor architecture for a UE, according to some embodiments.
  • FIG. 7 illustrates an example block diagram of an interface of baseband circuitry according to some embodiments.
  • FIG. 8 illustrates an example of a control plane protocol stack in accordance with some embodiments.
  • FIG. 9 illustrates an example of a user plane protocol stack in accordance with some embodiments.
  • FIG. 10 illustrates example components of a core network in accordance with some embodiments.
  • FIG. 11a illustrates an example of an example packet data convergence protocol layer in 3GPP, in accordance with some embodiments.
  • FIG. 11 b illustrates an example reordering scheme, in accordance with some embodiments.
  • FIG. 11c illustrates an example reordering scheme, in accordance with some embodiments.
  • FIG. 11 d illustrates an example reordering scheme, in accordance with some embodiments.
  • FIG. 12 illustrates an example network scheduling scheme, in accordance with some embodiments.
  • FIG. 13 illustrates an example network scheduling scheme, in accordance with some embodiments.
  • FIG. 14 illustrates a flow chart of an example of a method of adaptive reordering of voice packets, according to some embodiments.
  • FIG. 15 illustrates an example reordering scheme, in accordance with some embodiments.
  • FIG. 16 illustrates a flow chart of an example of a method of adaptive reordering of voice packets, according to some embodiments.
  • FIG. 17 illustrates an example reordering scheme, in accordance with some embodiments.
  • FIG. 18 illustrates an example reordering scheme, in accordance with some embodiments.
  • FIG. 19 illustrates an example reordering scheme, in accordance with some embodiments.
  • FIG. 20 illustrates a flow chart of an example of a method of adaptive reordering of voice packets, according to some embodiments.
  • Memory Medium Any of various types of non-transitory memory devices or storage devices.
  • the term “memory medium” is intended to include an installation medium, e.g., a CD-ROM, floppy disks, or tape device; a computer system memory or random-access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash, magnetic media, e.g., a hard drive, or optical storage; registers, or other similar types of memory elements, etc.
  • the memory medium may include other types of non-transitory memory as well or combinations thereof.
  • the memory medium may be located in a first computer system in which the programs are executed or may be located in a second different computer system which connects to the first computer system over a network, such as the Internet. In the latter instance, the second computer system may provide program instructions to the first computer for execution.
  • the term “memory medium” may include two or more memory mediums which may reside in different locations, e.g., in different computer systems that are connected over a network.
  • the memory medium may store program instructions (e.g., embodied as computer programs) that may be executed by one or more processors.
  • Carrier Medium a memory medium as described above, as well as a physical transmission medium, such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
  • a physical transmission medium such as a bus, network, and/or other physical transmission medium that conveys signals such as electrical, electromagnetic, or digital signals.
  • Programmable Hardware Element includes various hardware devices comprising multiple programmable function blocks connected via a programmable interconnect. Examples include FPGAs (Field Programmable Gate Arrays) , PLDs (Programmable Logic Devices) , FPOAs (Field Programmable Object Arrays) , and CPLDs (Complex PLDs) .
  • the programmable function blocks may range from fine grained (combinatorial logic or look up tables) to coarse grained (arithmetic logic units or processor cores) .
  • a programmable hardware element may also be referred to as "reconfigurable logic” .
  • Computer System any of various types of computing or processing systems, including a personal computer system (PC) , mainframe computer system, workstation, network appliance, Internet appliance, personal digital assistant (PDA) , television system, grid computing system, or other device or combinations of devices.
  • PC personal computer system
  • mainframe computer system workstation
  • network appliance Internet appliance
  • PDA personal digital assistant
  • television system grid computing system, or other device or combinations of devices.
  • computer system can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.
  • UE User Equipment
  • UE Device any of various types of computer systems devices which are mobile or portable and which performs wireless communications.
  • UE devices include mobile telephones or smart phones (e.g., iPhone TM , Android TM -based phones) , portable gaming devices (e.g., Nintendo DS TM , PlayStation Portable TM , Gameboy Advance TM , iPhone TM ) , laptops, wearable devices (e.g., smart watch, smart glasses) , PDAs, portable Internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones) , UAV controllers (UACs) , and so forth.
  • UAVs unmanned aerial vehicles
  • UACs UAV controllers
  • Base Station has the full breadth of its ordinary meaning, and at least includes a wireless communication station installed at a fixed location and used to communicate as part of a wireless telephone system or radio system.
  • Processing Element refers to various elements or combinations of elements that are capable of performing a function in a device, such as a user equipment or a cellular network device.
  • Processing elements may include, for example: processors and associated memory, portions or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as an ASIC (Application Specific Integrated Circuit) , programmable hardware elements such as a field programmable gate array (FPGA) , as well any of various combinations of the above.
  • ASIC Application Specific Integrated Circuit
  • FPGA field programmable gate array
  • channel widths may be variable (e.g., depending on device capability, band conditions, etc. ) .
  • LTE may support scalable channel bandwidths from 1.4 MHz to 20MHz.
  • 5G NR can support scalable channel bandwidths from 5 MHz to 100 MHz in Frequency Range 1 (FR1) and up to 400 MHz in FR2.
  • WLAN channels may be 22 MHz wide while Bluetooth channels may be 1 MHz wide.
  • Other protocols and standards may include different definitions of channels.
  • some standards may define and use multiple types of channels, e.g., different channels for uplink or downlink and/or different channels for different uses such as data, control information, etc.
  • band has the full breadth of its ordinary meaning, and at least includes a section of spectrum (e.g., radio frequency spectrum) in which channels are used or set aside for the same purpose.
  • spectrum e.g., radio frequency spectrum
  • Automatically refers to an action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuitry, programmable hardware elements, ASICs, etc. ) , without user input directly specifying or performing the action or operation.
  • a computer system e.g., software executed by the computer system
  • device e.g., circuitry, programmable hardware elements, ASICs, etc.
  • An automatic procedure may be initiated by input provided by the user, but the subsequent actions that are performed “automatically” are not specified by the user, i.e., are not performed “manually” , where the user specifies each action to perform.
  • a user filling out an electronic form by selecting each field and providing input specifying information is filling out the form manually, even though the computer system will update the form in response to the user actions.
  • the form may be automatically filled out by the computer system where the computer system (e.g., software executing on the computer system) analyzes the fields of the form and fills in the form without any user input specifying the answers to the fields.
  • the user may invoke the automatic filling of the form but is not involved in the actual filling of the form (e.g., the user is not manually specifying answers to fields but rather they are being automatically completed) .
  • the present specification provides various examples of operations being automatically performed in response to actions the user has taken.
  • Concurrent refers to parallel execution or performance, where tasks, processes, or programs are performed in an at least partially overlapping manner.
  • concurrency may be implemented using “strong” or strict parallelism, where tasks are performed (at least partially) in parallel on respective computational elements, or using “weak parallelism” , where the tasks are performed in an interleaved manner, e.g., by time multiplexing of execution threads.
  • Various components may be described as “configured to” perform a task or tasks.
  • “configured to” is a broad recitation generally meaning “having structure that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently performing that task (e.g., a set of electrical conductors may be configured to electrically connect a module to another module, even when the two modules are not connected) .
  • “configured to” may be a broad recitation of structure generally meaning “having circuitry that” performs the task or tasks during operation. As such, the component can be configured to perform the task even when the component is not currently on.
  • the circuitry that forms the structure corresponding to “configured to” may include hardware circuits.
  • a network configured reordering timer can be scaled by a UE based on a detected network scheduling scheme, e.g. whether two packets every 40ms or one packet every 20ms.
  • the UE can directly deliver packets to a higher or application layer without starting the reordering timer during a silence status.
  • the UE can start a specific reordering timer for a silence or an active status.
  • the example embodiments are described with regard to a user equipment (UE) and a network (NW) or base station, such as a gNB.
  • UE user equipment
  • NW network
  • gNB network
  • the example embodiments may be utilized with any electronic component that may establish a connection to a network and is configured with the hardware, software, and/or firmware to support gapless RRM measurements. Therefore, the gNB or UE as described herein is used to represent any appropriate type of electronic component.
  • the example embodiments are also described with regard to a fifth generation (5G) New Radio (NR) network that may configure a UE to control the measurement opportunity sharing between L3 measurements and L1 measurements based on a network configurable sharing factor.
  • 5G fifth generation
  • NR New Radio
  • reference to a 5G NR network is merely provided for illustrative purposes.
  • the example embodiments may be utilized with any appropriate type of network.
  • FIGS 1A and 1B Communication Systems
  • FIG. 1A illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system of FIG. 1A is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.
  • the example wireless communication system includes a base station 102A which communicates over a transmission medium with one or more user devices 106A, 106B, etc., through 106N.
  • Each of the user devices may be referred to herein as a “user equipment” (UE) .
  • UE user equipment
  • the user devices 106 are referred to as UEs or UE devices.
  • the base station (BS) 102A may be a base transceiver station (BTS) or cell site (a “cellular base station” ) and may include hardware that enables wireless communication with the UEs 106A through 106N.
  • BTS base transceiver station
  • cellular base station a “cellular base station”
  • the communication area (or coverage area) of the base station may be referred to as a “cell. ”
  • the base station 102A and the UEs 106 may be configured to communicate over the transmission medium using any of various radio access technologies (RATs) , also referred to as wireless communication technologies, or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces) , LTE, LTE-Advanced (LTE-A) , 5G new radio (5G NR) , HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD) , etc.
  • RATs radio access technologies
  • GSM Global System for Mobile communications
  • UMTS associated with, for example, WCDMA or TD-SCDMA air interfaces
  • LTE LTE-Advanced
  • 5G NR 5G new radio
  • 3GPP2 CDMA2000 e.g., 1xRT
  • the base station 102A is implemented in the context of LTE, also referred to as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN, it may alternately be referred to as an 'eNodeB' or ‘eNB’ .
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • eNB Evolved Universal Terrestrial Radio Access Network
  • the base station 102A is implemented in the context of 5G NR, it may alternately be referred to as ‘gNodeB’ or ‘gNB’ .
  • the base station 102A may also be equipped to communicate with a network 100 (e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN) , and/or the Internet, among various possibilities) .
  • a network 100 e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN) , and/or the Internet, among various possibilities
  • PSTN public switched telephone network
  • the base station 102A may facilitate communication between the user devices and/or between the user devices and the network 100.
  • the cellular base station 102A may provide UEs 106 with various telecommunication capabilities, such as voice, SMS and/or data services.
  • Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or a different cellular communication standard may thus be provided as a network of cells, which may provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.
  • each UE 106 may also be capable of receiving signals from (and possibly within communication range of) one or more other cells (which might be provided by base stations 102B-N and/or any other base stations) , which may be referred to as “neighboring cells” .
  • Such cells may also be capable of facilitating communication between user devices and/or between user devices and the network 100.
  • Such cells may include “macro” cells, “micro” cells, “pico” cells, and/or cells which provide any of various other granularities of service area size.
  • base stations 102A-B illustrated in FIG. 1A might be macro cells, while base station 102N might be a micro cell. Other configurations are also possible.
  • base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB” .
  • a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • a gNB cell may include one or more transition and reception points (TRPs) .
  • TRPs transition and reception points
  • a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
  • a UE 106 may be capable of communicating using multiple wireless communication standards.
  • the UE 106 may be configured to communicate using a wireless networking (e.g., Wi-Fi) and/or peer-to-peer wireless communication protocol (e.g., Bluetooth, Wi-Fi peer-to-peer, etc. ) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces) , LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD) , etc. ) .
  • GSM Global System for Mobile communications
  • UMTS associated with, for example, WCDMA or TD-SCDMA air interfaces
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • 5G NR Fifth Generation
  • HSPA High Speed Packet Access
  • the UE 106 may also or alternatively be configured to communicate using one or more global navigational satellite systems (GNSS, e.g., GPS or GLONASS) , one or more mobile television broadcasting standards (e.g., ATSC-M/H or DVB-H) , and/or any other wireless communication protocol, if desired.
  • GNSS global navigational satellite systems
  • mobile television broadcasting standards e.g., ATSC-M/H or DVB-H
  • any other wireless communication protocol if desired.
  • Other combinations of wireless communication standards including more than two wireless communication standards are also possible.
  • FIG. 1 B illustrates user equipment 106 (e.g., one of the devices 106A through 106N) in communication with a base station 102 and an access point 112, according to some embodiments.
  • the UE 106 may be a device with both cellular communication capability and non-cellular communication capability (e.g., Bluetooth, Wi-Fi, and so forth) such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.
  • non-cellular communication capability e.g., Bluetooth, Wi-Fi, and so forth
  • the UE 106 may include a processor that is configured to execute program instructions stored in memory. The UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively, or in addition, the UE 106 may include a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.
  • a programmable hardware element such as an FPGA (field-programmable gate array) that is configured to perform any of the method embodiments described herein, or any portion of any of the method embodiments described herein.
  • the UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies.
  • the UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT /1xEV-DO /HRPD /eHRPD) , LTE/LTE-Advanced, or 5G NR using a single shared radio and/or GSM, LTE, LTE-Advanced, or 5G NR using the single shared radio.
  • the shared radio may couple to a single antenna, or may couple to multiple antennas (e.g., for MIMO) for performing wireless communications.
  • a radio may include any combination of a baseband processor, analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc. ) , or digital processing circuitry (e.g., for digital modulation as well as other digital processing) .
  • the radio may implement one or more receive and transmit chains using the aforementioned hardware.
  • the UE 106 may share one or more parts of a receive and/or transmit chain between multiple wireless communication technologies, such as those discussed above.
  • the UE 106 may include separate transmit and/or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol with which it is configured to communicate.
  • the UE 106 may include one or more radios which are shared between multiple wireless communication protocols, and one or more radios which are used exclusively by a single wireless communication protocol.
  • the UE 106 might include a shared radio for communicating using either LTE or 5G NR (or LTE or 1xRTTor LTE or GSM) , and separate radios for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.
  • FIG. 2 Block Diagram of a Base Station
  • FIG. 2 illustrates an example block diagram of a base station 102, according to some embodiments. It is noted that the base station of FIG. 2 is merely one example of a possible base station. As shown, the base station 102 may include processor (s) 204 which may execute program instructions for the base station 102. The processor (s) 204 may also be coupled to memory management unit (MMU) 240, which may be configured to receive addresses from the processor (s) 204 and translate those addresses to locations in memory (e.g., memory 260 and read only memory (ROM) 250) or to other circuits or devices.
  • MMU memory management unit
  • the base station 102 may include at least one network port 270.
  • the network port 270 may be configured to couple to a telephone network and provide a plurality of devices, such as UE devices 106, access to the telephone network as described above in Figures 1 and 2.
  • the network port 270 may also or alternatively be configured to couple to a cellular network, e.g., a core network of a cellular service provider.
  • the core network may provide mobility related services and/or other services to a plurality of devices, such as UE devices 106.
  • the network port 270 may couple to a telephone network via the core network, and/or the core network may provide a telephone network (e.g., among other UE devices serviced by the cellular service provider) .
  • base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB” .
  • base station 102 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs) .
  • TRPs transition and reception points
  • a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.
  • the base station 102 may include at least one antenna 234, and possibly multiple antennas.
  • the at least one antenna 234 may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices 106 via radio 230.
  • the antenna 234 communicates with the radio 230 via communication chain 232.
  • Communication chain 232 may be a receive chain, a transmit chain or both.
  • the radio 230 may be configured to communicate via various wireless communication standards, including, but not limited to, 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.
  • the base station 102 may be configured to communicate wirelessly using multiple wireless communication standards.
  • the base station 102 may include multiple radios, which may enable the base station 102 to communicate according to multiple wireless communication technologies.
  • the base station 102 may include an LTE radio for performing communication according to LTE as well as a 5G NR radio for performing communication according to 5G NR.
  • the base station 102 may be capable of operating as both an LTE base station and a 5G NR base station.
  • the base station 102 may include a multi-mode radio which is capable of performing communications according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc. ) .
  • multiple wireless communication technologies e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.
  • the BS 102 may include hardware and software components for implementing or supporting implementation of features described herein.
  • the processor 204 of the base station 102 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • the processor 204 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) , or a combination thereof.
  • processor 204 of the BS 102 in conjunction with one or more of the other components 230, 232, 234, 240, 250, 260, 270 may be configured to implement or support implementation of part or all of the features described herein.
  • processor (s) 204 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor (s) 204. Thus, processor (s) 204 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor (s) 204. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 204.
  • circuitry e.g., first circuitry, second circuitry, etc.
  • radio 230 may be comprised of one or more processing elements.
  • one or more processing elements may be included in radio 230.
  • radio 230 may include one or more integrated circuits (ICs) that are configured to perform the functions of radio 230.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of radio 230.
  • the base station or gNB 102, and/or processors 204 thereof can be capable of and configured to send for transmission a network configured reordering timer.
  • the reordering timer may be configured or determined by a network or the base station.
  • FIG. 3 Block Diagram of a Server
  • FIG. 3 illustrates an example block diagram of a server 104, according to some embodiments. It is noted that the server of FIG. 3 is merely one example of a possible server. As shown, the server 104 may include processor (s) 344 which may execute program instructions for the server 104. The processor (s) 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from the processor (s) 344 and translate those addresses to locations in memory (e.g., memory 364 and read only memory (ROM) 354) or to other circuits or devices.
  • MMU memory management unit
  • the server 104 may be configured to provide a plurality of devices, such as base station 102, and UE devices 106 access to network functions, e.g., as further described herein.
  • the server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network.
  • the server 104 may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network.
  • EPC legacy evolved packet core
  • NRC NR core
  • the server 104 may include hardware and software components for implementing or supporting implementation of features described herein.
  • the processor 344 of the server 104 may be configured to implement or support implementation of part or all of the methods described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • the processor 344 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) , or a combination thereof.
  • the processor 344 of the server 104 in conjunction with one or more of the other components 354, 364, and/or 374 may be configured to implement or support implementation of part or all of the features described herein.
  • processor (s) 344 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor (s) 344.
  • processor (s) 344 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor (s) 344.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 344.
  • FIG. 4 Block Diagram of a User Equipment
  • FIG. 4 illustrates an example simplified block diagram of a communication device 106, according to some embodiments. It is noted that the block diagram of the communication device of FIG. 4 is only one example of a possible communication device.
  • communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device) , a tablet, an unmanned aerial vehicle (UAV) , a UAV controller (UAC) and/or a combination of devices, among other devices.
  • the communication device 106 may include a set of components 400 configured to perform core functions.
  • this set of components may be implemented as a system on chip (SOC) , which may include portions for various purposes.
  • SOC system on chip
  • this set of components 400 may be implemented as separate components or groups of components for the various purposes.
  • the set of components 400 may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device 106.
  • the communication device 106 may include various types of memory (e.g., including NAND flash 410) , an input/output interface such as connector I/F 420 (e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc. ) , the display 460, which may be integrated with or external to the communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry 429 (e.g., Bluetooth TM and WLAN circuitry) .
  • communication device 106 may include wired communication circuitry (not shown) , such as a network interface card, e.g., for Ethernet.
  • the cellular communication circuitry 430 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435 and 436 as shown.
  • the short to medium range wireless communication circuitry 429 may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 437 and 438 as shown.
  • the short to medium range wireless communication circuitry 429 may couple (e.g., communicatively; directly or indirectly) to the antennas 435 and 436 in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas 437 and 438.
  • the short to medium range wireless communication circuitry 429 and/or cellular communication circuitry 430 may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.
  • MIMO multiple-input multiple output
  • cellular communication circuitry 430 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly. dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR) .
  • cellular communication circuitry 430 may include a single transmit chain that may be switched between radios dedicated to specific RATs.
  • a first radio may be dedicated to a first RAT, e.g., LTE, and may be in communication with a dedicated receive chain and a transmit chain shared with an additional radio, e.g., a second radio that may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.
  • a first RAT e.g., LTE
  • a second radio may be dedicated to a second RAT, e.g., 5G NR, and may be in communication with a dedicated receive chain and the shared transmit chain.
  • the communication device 106 may also include and/or be configured for use with one or more user interface elements.
  • the user interface elements may include any of various elements, such as display 460 (which may be a touchscreen display) , a keyboard (which may be a discrete keyboard or may be implemented as part of a touchscreen display) , a mouse, a microphone and/or speakers, one or more cameras, one or more buttons, and/or any of various other elements capable of providing information to a user and/or receiving or interpreting user input.
  • the communication device 106 may further include one or more smart cards 445 that include SIM (Subscriber Identity Module) functionality, such as one or more UICC (s) (Universal Integrated Circuit Card (s) ) cards 445.
  • SIM Subscriber Identity Module
  • UICC Universal Integrated Circuit Card
  • SIM entity is intended to include any of various types of SIM implementations or SIM functionality, such as the one or more UICC (s) cards 445, one or more eUICCs, one or more eSIMs, either removable or embedded, etc.
  • the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and/or otherwise implement SIM functionality.
  • each SIM may be a single smart card that may be embedded, e.g., may be soldered onto a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card.
  • the SIM (s) may be one or more removable smart cards (such as UICC cards, which are sometimes referred to as “SIM cards” )
  • the SIMs 410 may be one or more embedded cards (such as embedded UICCs (eUICCs) , which are sometimes referred to as “eSIMs” or “eSIM cards” ) .
  • one or more of the SIM (s) may implement embedded SIM (eSIM) functionality; in such an embodiment, a single one of the SIM (s) may execute multiple SIM applications.
  • Each of the SIMs may include components such as a processor and/or a memory; instructions for performing SIM/eSIM functionality may be stored in the memory and executed by the processor.
  • the UE 106 may include a combination of removable smart cards and fixed/non-removable smart cards (such as one or more eUICC cards that implement eSIM functionality) , as desired.
  • the UE 106 may comprise two embedded SIMs, two removable SIMs, or a combination of one embedded SIMs and one removable SIMs.
  • Various other SIM configurations are also contemplated.
  • the UE 106 may include two or more SIMs.
  • the inclusion of two or more SIMs in the UE 106 may allow the UE 106 to support two different telephone numbers and may allow the UE 106 to communicate on corresponding two or more respective networks.
  • a first SIM may support a first RAT such as LTE
  • a second SIM 410 support a second RAT such as 5G NR.
  • Other implementations and RATs are of course possible.
  • the UE 106 may support Dual SIM Dual Active (DSDA) functionality.
  • DSDA Dual SIM Dual Active
  • the DSDA functionality may allow the UE 106 to be simultaneously connected to two networks (and use two different RATs) at the same time, or to simultaneously maintain two connections supported by two different SIMs using the same or different RATs on the same or different networks.
  • the DSDA functionality may also allow the UE 106 to simultaneously receive voice calls or data traffic on either phone number.
  • the voice call may be a packet switched communication.
  • the voice call may be received using voice over LTE (VoLTE) technology and/or voice over NR (VoNR) technology.
  • the UE 106 may support Dual SIM Dual Standby (DSDS) functionality.
  • the DSDS functionality may allow either of the two SIMs in the UE 106 to be on standby waiting for a voice call and/or data connection. In DSDS, when a call/data is established on one SIM, the other SIM is no longer active.
  • DSDx functionality (either DSDA or DSDS functionality) may be implemented with a single SIM (e.g., a eUICC) that executes multiple SIM applications for different carriers and/or RATs.
  • the SOC 400 may include processor (s) 402, which may execute program instructions for the communication device 106 and display circuitry 404, which may perform graphics processing and provide display signals to the display 460.
  • the processor (s) 402 may also be coupled to memory management unit (MMU) 440, which may be configured to receive addresses from the processor (s) 402 and translate those addresses to locations in memory (e.g., memory 406, read only memory (ROM) 450, NAND flash memory 410) and/or to other circuits or devices, such as the display circuitry 404, short to medium range wireless communication circuitry 429, cellular communication circuitry 430, connector I/F 420, and/or display 460.
  • the MMU 440 may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU 440 may be included as a portion of the processor (s) 402.
  • the communication device 106 may include hardware and software components for implementing the above features for a communication device 106 to communicate a scheduling profile for power savings to a network.
  • the processor 402 of the communication device 106 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • processor 402 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) .
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • the processor 402 of the communication device 106 in conjunction with one or more of the other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460 may be configured to implement part or all of the features described herein.
  • processor 402 may include one or more processing elements.
  • processor 402 may include one or more integrated circuits (ICs) that are configured to perform the functions of processor 402.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processor (s) 402.
  • cellular communication circuitry 430 and short to medium range wireless communication circuitry 429 may each include one or more processing elements.
  • one or more processing elements may be included in cellular communication circuitry 430 and, similarly, one or more processing elements may be included in short to medium range wireless communication circuitry 429.
  • cellular communication circuitry 430 may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry 430.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of cellular communication circuitry 430.
  • the short to medium range wireless communication circuitry 429 may include one or more ICs that are configured to perform the functions of short to medium range wireless communication circuitry 429.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of short to medium range wireless communication circuitry 429.
  • the UE 106 and/or the processors 402 thereof can be configured to and/or capable of receiving voice packets, silence insertion descriptor (SID) packets, or a network configured reordering timer.
  • the UE 106 and/or the processors 402 thereof can be configured to and/or capable of determining a network scheduling scheme for the packets.
  • the UE 106 and/or the processors 402 thereof can be configured to and/or capable of re-calculating the network configured reordering timer.
  • the UE 106 and/or the processors 402 thereof can be configured to and/or capable of determining a voice status of the packets as active or silence.
  • the UE 106 and/or the processors 402 thereof can be configured to and/or capable of detecting a sequence number (SN) gap associated with one or more missing packets.
  • the UE 106 and/or the processors 402 thereof can be configured to and/or capable of starting the reordering timer and/or delivering packets to a higher layer.
  • SN sequence number
  • FIG. 5 Block Diagram of Cellular Communication Circuitry
  • FIG. 5 illustrates an example simplified block diagram of cellular communication circuitry, according to some embodiments. It is noted that the block diagram of the cellular communication circuitry of FIG. 5 is only one example of a possible cellular communication circuit.
  • cellular communication circuitry 530 which may be cellular communication circuitry 430, may be included in a communication device, such as communication device 106 described above.
  • communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device) , a tablet and/or a combination of devices, among other devices.
  • UE user equipment
  • the cellular communication circuitry 530 may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas 435a-b and 436 as shown (in FIG. 4) .
  • cellular communication circuitry 530 may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly. dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR) .
  • cellular communication circuitry 530 may include a modem 510 and a modem 520.
  • Modem 510 may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.
  • a first RAT e.g., such as LTE or LTE-A
  • modem 520 may be configured for communications according to a second RAT, e.g., such as 5G NR.
  • modem 510 may include one or more processors 512 and a memory 516 in communication with processors 512. Modem 510 may be in communication with a radio frequency (RF) front end 530.
  • RF front end 530 may include circuitry for transmitting and receiving radio signals.
  • RF front end 530 may include receive circuitry (RX) 532 and transmit circuitry (TX) 534.
  • receive circuitry 532 may be in communication with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.
  • DL downlink
  • modem 520 may include one or more processors 522 and a memory 526 in communication with processors 522. Modem 520 may be in communication with an RF front end 540.
  • RF front end 540 may include circuitry for transmitting and receiving radio signals.
  • RF front end 540 may include receive circuitry 542 and transmit circuitry 544.
  • receive circuitry 542 may be in communication with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.
  • a switch 570 may couple transmit circuitry 534 to uplink (UL) front end 572.
  • switch 570 may couple transmit circuitry 544 to UL front end 572.
  • UL front end 572 may include circuitry for transmitting radio signals via antenna 336.
  • switch 570 may be switched to a first state that allows modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry 534 and UL front end 572) .
  • switch 570 may be switched to a second state that allows modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry 544 and UL front end 572) .
  • the modem 510 may include hardware and software components for implementing the above features or for time division multiplexing UL data for NSA NR operations, as well as the various other techniques described herein.
  • the processors 512 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • processor 512 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) .
  • processor 512 in conjunction with one or more of the other components 530, 532, 534, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.
  • processors 512 may include one or more processing elements.
  • processors 512 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 512.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processors 512.
  • the processors 522 may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium) .
  • processor 522 may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array) , or as an ASIC (Application Specific Integrated Circuit) .
  • the processor 522 in conjunction with one or more of the other components 540, 542, 544, 550, 570, 572, 335a, 335b, and 336 may be configured to implement part or all of the features described herein.
  • processors 522 may include one or more processing elements.
  • processors 522 may include one or more integrated circuits (ICs) that are configured to perform the functions of processors 522.
  • each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc. ) configured to perform the functions of processors 522.
  • FIG. 6 Block Diagram of a Baseband Processor Architecture for a UE
  • FIG. 6 illustrates example components of a device 600 in accordance with some embodiments. It is noted that the device of FIG. 6 is merely one example of a possible system, and that features of this disclosure may be implemented in any of various UEs, as desired.
  • the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown.
  • the components of the illustrated device 600 may be included in a UE 106 or a RAN node.
  • the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC) .
  • the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .
  • C-RAN Cloud-RAN
  • the application circuitry 602 may include one or more application processors.
  • the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc. ) .
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 600.
  • processors of application circuitry 602 may process IP data packets received from an EPC.
  • the baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 606 and to generate baseband signals for a transmit signal path of the RF circuitry 606.
  • Baseband processing circuity 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
  • the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor (s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G) , sixth generation (6G) , etc. ) .
  • the baseband circuitry 604 e.g., one or more of baseband processors 604A-D
  • baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/demodulation circuitry of the baseband circuitry 604 may include Fast-Fourier Transform (FFT) , precoding, or constellation mapping/demapping functionality.
  • FFT Fast-Fourier Transform
  • encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 604 may include one or more audio digital signal processor (s) (DSP) 604F.
  • the audio DSP (s) 604F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry 604 and the application circuitry 602 may be implemented together such as, for example, on a system on a chip (SOC) .
  • SOC system on a chip
  • the baseband circuitry 604 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN) , a wireless local area network (WLAN) , a wireless personal area network (WPAN) .
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry 606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604.
  • RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.
  • the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
  • the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
  • RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
  • the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
  • the amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 604 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a necessity.
  • mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
  • the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection) .
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 606d may be a fractional N/N+1 synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO) , although that is not a necessity.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 602.
  • Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL) , a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA) .
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO) .
  • the RF circuitry 606 may include an IQ/polar converter.
  • FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
  • FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.
  • the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606) .
  • the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606) , and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610) .
  • PA power amplifier
  • the PMC 612 may manage power provided to the baseband circuitry 604.
  • the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604, in other embodiments the PMC 612 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.
  • the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in a radio resource control_Connected (RRC_Connected) state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.
  • RRC_Connected radio resource control_Connected
  • DRX Discontinuous Reception Mode
  • the device 600 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 600 may not receive data in this state, in order to receive data, it will transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours) . During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 604 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 604 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers) .
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • the baseband circuitry 604 can be used to encode a message for transmission between a UE and a gNB, or decode a message received between a UE and a gNB.
  • the baseband circuitry 604 can be used to decode, at the UE 106, voice packets, SID packets, and a network configured reordering timer. These examples are not intended to be limiting.
  • the baseband circuitry can be used as previously described.
  • FIG. 7 Block Diagram of an Interface of Baseband Circuitry
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments. It is noted that the baseband circuitry of FIG. 7 is merely one example of a possible circuitry, and that features of this disclosure may be implemented in any of various systems, as desired.
  • the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors.
  • Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.
  • the baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604) , an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6) , an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
  • a memory interface 712 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604
  • an application circuitry interface 714 e.g., an interface to send/receive data to/from the application circuitry 602 of FIG.
  • an RF circuitry interface 716 e.g., an interface to send/receive data to/from RF circuitry 606 of FIG.
  • a wireless hardware connectivity interface 718 e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, components (e.g., Low Energy) , components, and other communication components
  • NFC Near Field Communication
  • components e.g., Low Energy
  • components e.g., Low Energy
  • components e.g., Low Energy
  • components e.g., Low Energy
  • components e.g., Low Energy
  • a power management interface 720 e.g., an interface to send/receive power or control signals to/from the PMC 612.
  • FIG. 8 Control Plane Protocol Stack
  • FIG. 8 is an illustration of a control plane protocol stack in accordance with some embodiments.
  • a control plane 800 is shown as a communications protocol stack between the UE 106a (or alternatively, the UE 106b) , the RAN node 611 (or alternatively, the RAN node 612) , and the mobility management entity (MME) 621.
  • MME mobility management entity
  • the PHY layer 801 may transmit or receive information used by the MAC layer 802 over one or more air interfaces.
  • the PHY layer 801 may further perform link adaptation or adaptive modulation and coding (AMC) , power control, cell search (e.g., for initial synchronization and handover purposes) , and other measurements used by higher layers, such as the RRC layer 805.
  • AMC link adaptation or adaptive modulation and coding
  • the PHY layer 801 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing.
  • FEC forward error correction
  • MIMO Multiple Input Multiple Output
  • the MAC layer 802 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ) , and logical channel prioritization.
  • SDUs MAC service data units
  • TB transport blocks
  • HARQ hybrid automatic repeat request
  • the RLC layer 803 may operate in a plurality of modes of operation, including: Transparent Mode (TM) , Unacknowledged Mode (UM) , and Acknowledged Mode (AM) .
  • the RLC layer 803 may execute transfer of upper layer protocol data units (PDUs) , error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers.
  • PDUs protocol data units
  • ARQ automatic repeat request
  • the RLC layer 803 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.
  • the PDCP layer 804 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs) , perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc. ) .
  • security operations e.g., ciphering, deciphering, integrity protection, integrity verification, etc.
  • the main services and functions of the RRC layer 805 may include broadcast of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS) ) , broadcast of system information related to the access stratum (AS) , paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (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 radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting.
  • SIBs may comprise one or more information elements (IEs) , which may each comprise individual data fields or data structures.
  • the UE 601 and the RAN node 611 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 801, the MAC layer 802, the RLC layer 803, the PDCP layer 804, and the RRC layer 805.
  • a Uu interface e.g., an LTE-Uu interface
  • the non-access stratum (NAS) protocols 806 form the highest stratum of the control plane between the UE 601 and the MME 621.
  • the NAS protocols 806 support the mobility of the UE 601 and the session management procedures to establish and maintain IP connectivity between the UE 601 and the P-GW 623.
  • the S1 Application Protocol (S1-AP) layer 815 may support the functions of the S1 interface and comprise Elementary Procedures (EPs) .
  • An EP is a unit of interaction between the RAN node 1010 and the CN 1020.
  • the S1-AP layer services may comprise two groups: UE-associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM) , and configuration transfer.
  • E-RAB E-UTRAN Radio Access Bearer
  • RIM RAN Information Management
  • the Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) 814 may ensure reliable delivery of signaling messages between the RAN node 611 and the MME 621 based, in part, on the IP protocol, supported by the IP layer 813.
  • the L2 layer 812 and the L1 layer 811 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.
  • the RAN node 611 and the MME 621 may utilize an S1-MME interface to exchange control plane data via a protocol stack comprising the L1 layer 811, the L2 layer 812, the IP layer 813, the SCTP layer 814, and the S1-AP layer 815.
  • FIG. 9 User Plane Protocol Stack
  • FIG. 9 is an illustration of an example of a user plane protocol stack in accordance with some embodiments.
  • a user plane 900 is shown as a communications protocol stack between the UE 106A (or alternatively, the UE 106B or 106N) , the RAN node 611 (or alternatively, the RAN node 612) , the S-GW 622, and the P-GW 623.
  • the user plane 900 may utilize at least some of the same protocol layers as the control plane 800.
  • the UE 601 and the RAN node 611 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 801, the MAC layer 802, the RLC layer 803, the PDCP layer 804.
  • a Uu interface e.g., an LTE-Uu interface
  • the General Packet Radio Service (GPRS) Tunneling Protocol for the user plane (GTP-U) layer 904 may be used for carrying user data within the GPRS core network and between the radio access network and the core network.
  • the user data transported can be packets in any of IPv4, IPv6, or PPP formats, for example.
  • the UDP and IP security (UDP/IP) layer 903 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows.
  • the RAN node 611 and the S-GW 622 may utilize an S1-U interface to exchange user plane data via a protocol stack comprising the L1 layer 811, the L2 layer 812, the UDP/IP layer 903, and the GTP-U layer 904.
  • the S-GW 622 and the P-GW 623 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the L1 layer 811, the L2 layer 812, the UDP/IP layer 903, and the GTP-U layer 904.
  • NAS protocols support the mobility of the UE 106 and the session management procedures to establish and maintain IP 913 connectivity between the UE 106 and the P-GW 623.
  • FIG. 10 Core Network
  • FIG. 10 illustrates an example architecture of a system 1000 including a core network (CN) 1020 in accordance with various embodiments.
  • the CN 1020 may be a core network for a 5G System (which may be referred to as a 5GC) .
  • the system 1000 is shown to include a UE 1001, which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously; a (R) AN 102, which may be the same or similar to the BSs 102A or 102N discussed previously; and a data network (DN) 1003, which may be, for example, operator services, Internet access, or 3rd party services; and a CN 1020.
  • a UE 1001 which may be the same or similar to the UEs 106A, 106B, or 106N discussed previously
  • R AN 102
  • DN data network
  • the CN 1020 may include a number of network functions including an Authentication Server Function (AUSF) 1022; an Access and Mobility Management Function (AMF) 1021; a Session Management Function (SMF) 1024; a Network Exposure Function (NEF) 1023; a Policy Control Function (PCF) 1026; a Network Repository Function (NRF) 1025; a Unified Data Management (UDM) 1027; an Application Function (AF) 1028; a User Plane Function (UPF) 1002; and a Network Slice Selection Function (NSSF) 1029.
  • AUSF Authentication Server Function
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • NEF Network Exposure Function
  • PCF Policy Control Function
  • NRF Network Repository Function
  • UDM Unified Data Management
  • AF Application Function
  • UPF User Plane Function
  • NSSF Network Slice Selection Function
  • the UPF 1002 may act as an anchor point for intra-RAT and inter-RAT mobility, an external packet data unit (PDU) session point of interconnect to DN 1003, and a branching point to support multi-homed PDU session.
  • PDU session is a logical connection between the UE and the DN.
  • the UPF 1002 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (user plane (UP) collection) , perform traffic usage reporting, perform quality of service (QoS) handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement) , perform Uplink Traffic verification (e.g., Service Data Flows (SDF) to QoS flow mapping) , transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 1002 may include an uplink classifier to support routing traffic flows to a data network.
  • the DN 1003 may represent various network operator services, Internet access, or third party services. DN 1003 may include, or be similar to, application server 430 discussed previously.
  • the UPF 1002 may interact with the SMF 1024 via an N4 reference point between the SMF 1021 and the UPF 1002.
  • the AUSF 1022 may store data for authentication of UE 1001 and handle authentication-related functionality, The AUSF 1022 may facilitate a common authentication frame work for various access types.
  • the AUSF 1022 may communicate with the AMF 1021 via an N12 reference point between the AMF 1021 and the AUSF 1022; and may communicate with the UDM 1027 via an N13 reference point between the UDM 1027 and the AUSF 1022. Additionally, the AUSF 1022 may exhibit an Nausf service-based interface.
  • the AMF 1021 may be responsible for registration management (e.g., for registering UE 1001, etc. ) , connection management, reachability management, mobility management, and lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 1021 may be a termination point for the an N11 reference point between the AMF 1021 and the SMF 1024.
  • the AMF 1021 may provide transport for SM messages between the UE 1001 and the SMF 1024, and act as a transparent proxy for routing SM messages.
  • AMF 1021 may also provide transport for Short Message Service (SMS) messages between UE 1001 and an SMSF (not shown by FIG. 10) .
  • SMS Short Message Service
  • AMF 1021 may act as a security anchor function (SEAF) , which may include interaction with the AUSF 1022 and the UE 1001, receipt of an intermediate key that was established as a result of the UE 1001 authentication process. Where Universal Subscriber Identity Module (USIM) based authentication is used, the AMF 1021 may retrieve the security material from the AUSF 1022. AMF 1021 may also include a Security Context Management (SCM) function, which receives a key from the SEAF that it uses to derive access-network specific keys.
  • SEAF security anchor function
  • SCM Security Context Management
  • AMF 1021 may be a termination point of a RAN control plane (CP) interface, which may include or be an N2 reference point between the (R) AN 1010 and the AMF 1021; and the AMF 1021 may be a termination point of NAS (N1) signaling and perform NAS ciphering and integrity protection.
  • CP RAN control plane
  • AMF 1021 may also support NAS signaling with a UE 1001 over a non- 3GPP Inter-Working Function (N3IWF) interface.
  • the N3IWF may be used to provide access to untrusted entities.
  • N3IWF may be a termination point for the N2 interface between the (R) AN 1010 and the AMF 1021 for the control plane and may be a termination point for the N3 reference point between the (R) AN 1010 and the UPF 1002 for the user plane.
  • the AMF 1021 may handle N2 signaling from the SMF 1024 and the AMF 1021 for PDU sessions and encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3 user-plane packets in the uplink, and enforce QoS corresponding to N3 packet marking while considering QoS requirements associated with such marking received over N2.
  • N3IWF may also relay uplink and downlink control plane non-access stratum (NAS) signaling between the UE 1001 and AMF 1021 via an N1 reference point between the UE 1001 and the AMF 1021, and relay uplink and downlink user-plane packets between the UE 1001 and UPF 1002.
  • NAS non-access stratum
  • the N3IWF also provides mechanisms for internet protocol security (IPsec) tunnel establishment with the UE 1001.
  • the AMF 1021 may exhibit an Namf service based interface and may be a termination point for an N14 reference point between two AMFs 1021 and an N17 reference point between the AMF 1021 and a 5G Equipment Identity Register (5G-EIR) (not shown by FIG. 10) .
  • 5G-EIR 5G Equipment Identity Register
  • the UE 1001 may need to register with the AMF 1021 in order to receive network services.
  • Registration Management is used to register or deregister the UE 1001 with the network (e.g., AMF 1021) , and establish a UE context in the network (e.g., AMF 1021) .
  • the UF 1001 may operate in an RM-REGISTERED state or an RM-DEREGISTERED state. In the RM-DEREGISTERED state, the UE 1001 is not registered with the network, and the UE context in AMF 1021 holds no valid location or routing information for the UE 1001 so the UE 1001 is not reachable by the AMF 1021.
  • the UE 1001 In the RM REGISTERED state, the UE 1001 is registered with the network, and the UE context in AMF 1021 may hold a valid location or routing information for the UE 1001 so the UE 1001 is reachable by the AMF 1021.
  • the UE 1001 In the RM-REGISTERED state, the UE 1001 may perform mobility registration update procedures, perform periodic registration update procedures triggered by expiration of the periodic update timer (e.g., to notify the network that the UE 1001 is still active) , and perform a Registration Update procedure to update UE capability information or to re-negotiate protocol parameters with the network, among others.
  • the AMF 1021 may store one or more RM contexts for the UE 1001, where each RM context is associated with a specific access to the network.
  • the RM context may be a data structure, database object, etc. that indicates or stores, inter alia, a registration state per access type and the periodic update timer.
  • the AMF 1021 may also store a 5GC mobility management (MM) context that may be the same or similar to the evolved packet services (EPS) Mobility Management (E)MM context discussed previously.
  • EPS evolved packet services
  • E Mobility Management
  • the AMF 1021 may store a CE mode B Restriction parameter of the UE 1001 in an associated MM context or registration management (RM) context.
  • the AMF 1021 may also derive the value, when needed, from the UE's usage setting parameter already stored in the UE context (and/or MM/RM context) .
  • CM Connection Management
  • the signaling connection is used to enable NAS signaling exchange between the UE 1001 and the CN 1020, and comprises both the signaling connection between the UE and the AN (e.g., RRC connection or UE-N3IWF connection for non-3GPP access) and the N2 connection for the UE 1001 between the AN (e.g., AN 1010) and the AMF 1021.
  • the UE 1001 may operate in one of two CM states, CM-IDLE mode or CM-CONNECTED mode.
  • the UE 1001 When the UE 1001 is operating in the CM-IDLE state/mode, the UE 1001 may have no NAS signaling connection established with the AMF 1021 over the N1 interface, and there may be (R) AN 1010 signaling connection (e.g., N2 and/or N3 connections) for the UE 1001. When the UE 1001 is operating in the CM-CONNECTED state/mode, the UE 1001 may have an established NAS signaling connection with the AMF 1021 over the Nl interface, and there may be a (R) AN 1010 signaling connection (e.g., N2 and/or N3 connections) for the UE 1001.
  • R NAS signaling connection
  • Establishment of an N2 connection between the (R) AN 1010 and the AMF 1021 may cause the UE 1001 to transition from CM-IDLE mode to CM-CONNECTED mode, and the UE 1001 may transition from the CM-CONNECTED mode to the CM-IDLE mode when N2 signaling between the (R) AN 1010 and the AMF 1021 is released.
  • the SMF 1024 may be responsible for session management (SM) session establishment, modify and release, including tunnel maintain between UPF and AN node) ; UE IP address allocation and management (including optional authorization) ; selection and control of UP function; configuring traffic steering at UPF to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement and QoS; lawful intercept (for SM events and interface to LI system) ; termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF over N2 to AN; and determining SSC mode of a session.
  • SM session management
  • SM may refer to management of a PDU session
  • a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between a UE 1001 and a data network (DN) 1003 identified by a Data Network Name (DNN) .
  • PDU sessions may be established upon UE 1001 request, modified upon UE 1001 and CN 1020 request, and released upon UE 1001 and CN 1020 request using NAS SM signaling exchanged over the N1 reference point between the UE 1001 and the SMF 1024.
  • the CN 1020 may trigger a specific application in the UE 1001.
  • the UE 1001 may pass the trigger message (or relevant parts/information of the trigger message) to one or more identified applications in the UE 1001.
  • the identified application (s) in the UE 1001 may establish a PDU session to a specific data network name (DNN) .
  • the SMF 1024 may check whether the UE 1001 requests are compliant with user subscription information associated with the UE 1001. In this regard, the SMF 1024 may retrieve and/or request to receive update notifications on SMF 1024 level subscription data from the UDM 1027.
  • the SMF 1024 may include the following roaming functionality: handling local enforcement to apply QoS SLAB virtual Public Land Mobile Network (VPLMN) ; charging data collection and charging interface (VPLMN) ; lawful intercept (in VPLMN for SM events and interface to LI system) ; and support for interaction with external DN for transport of signaling for PDU session authorization/authentication by external DN.
  • An N16 reference point between two SMFs 1024 may be included in the system 1000, which may be between another SMF 1024 in a visited network and the SMF 1024 in the home network in roaming scenarios. Additionally, the SMF 1024 may exhibit the Nsmf service-based interface.
  • the NEF 1023 may provide means for securely exposing the services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, Application Functions (e.g., AF 1028) , edge computing or fog computing systems, etc.
  • the NEF 1023 may authenticate, authorize, and/or throttle the AFS.
  • NEF 1023 may also translate information exchanged with the AF 1028 and information exchanged with internal network functions. For example, the NEF 1023 may translate between an AF-Service-Identifier and an internal SCC information.
  • NEF 1023 may also receive information from other network functions (NFs) based on exposed capabilities of other network functions. This information may be stored at the NEF 1023 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 1023 to other NFs and AFs, and/or used for other purposes such as analytics. Additionally, the NEF 1023 may exhibit a Nnef service-based interface.
  • the NRF 1025 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 1025 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate, " “instantiation, “ and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 1025 may exhibit the Nnrf service based interface.
  • the PCF 1026 may provide policy rules to control plane function (s) to enforce them and may also support unified policy framework to govern network behavior,
  • the PCF 1026 may also implement a front end (FE) to access subscription information relevant for policy decisions in a UDR of the UDM 1027.
  • the PCF 1026 may communicate with the AMF 1021 via an N15 reference point between the PCF 1026 and the AMF 1021, which may include a PCF 1026 in a visited network and the AMF 1021 in case of roaming scenarios.
  • the PCF 1026 may communicate with the AF 1028 via an NS reference point between the PCF 1026 and the AF 1028; and with the SMF 1024 via an N7 reference point between the PCF 1026 and the SMF 1024,
  • the system 1000 and/or CN 1020 may also include an N24 reference point between the PCF 1026 (in the home network) and a PCF 1026 in a visited network, Additionally, the PCF 1026 may exhibit an Npcf service-based interface.
  • the UDM 1027 may handle subscription-related information to support the network entities' handling of communication sessions and may store subscription data of UE 1001. For example, subscription data may be communicated between the UDM 1027 and the AMF 1021 via an NS reference point between the UDM 1027 and the AMF.
  • the UDM 1027 may include two parts, an application FE and a UDR (the FE and UDR are not shown by FIG. 10) .
  • the UDR may store subscription data and policy data for the UDM 1027 and the PCF 1026, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 1001) for the NEF 1023.
  • the Nadr service-based interface may be exhibited by the UDR 221 to allow the UDM 1027, PCF 1026, and NEF 1023 to access a particular set of the stored data, as well as to read, update (e.g., add, modify) , delete, and subscribe to notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDR may interact with the SMF 1024 via an Nl0 reference point between the UDM 1027 and the SMF 1024.
  • UDM 1027 may also support SMS management, wherein an SMS-FE implements the similar application logic as discussed previously. Additionally, the UDM 1027 may exhibit the Nudm service based interface.
  • the AF 1028 may provide application influence on traffic routing, provide access to the NCE, and interact with the policy framework for policy control.
  • the NCE may be a mechanism that allows the CN 1020 and AF 1028 to provide information to each other via NEF 1023, which may be used for edge computing implementations.
  • the network operator and third party services may be hosted close to the UE 1001 access point of attachment to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network.
  • the 5GC may select a UPF 1002 close to the UE 1001 and execute traffic steering from the UPF 502 to ON 1003 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 1028.
  • the AF 1028 may influence UPF (re) selection and traffic routing. Based on operator deployment, when AF 1028 is considered to be a trusted entity, the network operator may permit AF 1028 to interact directly with relevant NFs. Additionally, the AF 1028 may exhibit a Naf service-based interface.
  • the NSSF 1029 may select a set of network slice instances serving the UE 501.
  • the NSSF 1029 may also determine allowed Network Slice Selection Assistance Information (NSSAI) and the mapping to the subscribed single NSSAI (S-NSSAI) is, if needed.
  • the NSSF 1029 may also determine the AMF set to be used to serve the UE 1001, or a list of candidate AMF (s) 1021 based on a suitable configuration and possibly by querying the NRF 1025.
  • the selection of a set of network slice instances for the UE 1001 may be triggered by the AMF 1021 with which the UE 1001 is registered by interacting with the NSSF 1029, which may lead to a change of AMF 1021.
  • the NSSF 1029 may interact with the AMF 1021 via an N22 reference point between AMF 1021 and NSSF 1029; and may communicate with another NSSF 1029 in a visited network via an N31 reference point (not shown by FIG. 10) . Additionally, the NSSF 1029 may exhibit an Nnssf service-based interface.
  • the CN 1020 may include a short message service function (SMSF) , which may be responsible for SMS subscription checking and verification, and relaying SM messages to/from the UE 1001 to/from other entities, such as an SMS-GMSC/IWMSC/SMS-router.
  • SMS may also interact with AMF 1021 and UDM 1027 for a notification procedure that the UE 1001 is available for SMS transfer (e.g., set a UE not reachable flag, and notifying UDM 1027 when UE 1001 is available for SMS) .
  • SMS short message service function
  • the CN 1020 may also include other elements that are not shown by FIG. 10, such as a Data Storage system/architecture, a 5G-EIR, a Security Edge Protection Proxy (SEPP) , and the like.
  • the Data Storage system may include a Structured Data Storage Network Function (SDSF) , air Unstructured Data Storage Function (UDSF) , and/or the like.
  • SDSF Structured Data Storage Network Function
  • UDSF air Unstructured Data Storage Function
  • Any network function (NF) may store and retrieve unstructured data into/from the UDSF (e.g., UE contexts) , via N18 reference point between any NF and the UDSF (not shown by FIG.
  • 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 the individual NFs. Addition-ally, the UDSF may exhibit an Nudsf service-based interface (not shown by FIG. 10) .
  • the 5G-EIR may be an NF that checks the status of permanent equipment identifier (PEI) for determining whether particular equipment/entities are blacklisted from the network; and the SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.
  • PEI permanent equipment identifier
  • SEPP may be a non-transparent proxy that performs topology hiding, message filtering, and policing on inter-PLMN control plane interfaces.
  • the CN 1020 may include an Nx interface, which is an inter-CN interface between a mobility management entity (MME) and the AMF 1021 in order to enable interworking between CN 1020 and a CN in a 4G system.
  • Nx interface is an inter-CN interface between a mobility management entity (MME) and the AMF 1021 in order to enable interworking between CN 1020 and a CN in a 4G system.
  • Other example interfaces/reference points may include an N5G-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network; and an N31 reference point between the NSSF in the visited network and the NSSF in the home network.
  • FIG. 11a Packet Data Convergence Protocol Layer (PDCP) in 3GPP
  • FIG. 11a provides an illustration of an example packet data convergence protocol layer in 3GPP 1100, in accordance with some embodiments.
  • the PDCP layer for 3GPP is specified in TS 38.323 V18.0.0 (January 2024) for 3GPP 5G.
  • the PDCP layer is located in the Radio Protocol Stack in the 5G air interface on top of the radio link control (RLC) layer, as shown in FIGs. 8 and 9.
  • RLC radio link control
  • the PDCP provides its services to the radio resource control (RRC) and user plane upper layers, e.g. the Internet protocol (IP) layer at the UE or to the relay layer at the BS.
  • RRC radio resource control
  • IP Internet protocol
  • the following services are provided by the PDCP to upper layers: the transfer of user plane data; the transfer of control plane data; header compression; ciphering; and integrity protection.
  • PDCP packets are associated with a sequence number.
  • Data entering the PDCP layer is first stored in a transmission buffer.
  • the data is organized using a Sequence Numbering procedure.
  • the PDCP adds a Sequence Number (SN) to each incoming data block. Once the SN is added, the PDCP can use the SN to manage the packets.
  • the SN can be used to determine information such as whether the data that was transmitted at the BS is arriving in order at the UE, whether duplicate packets are received, or whether packets were dropped in the transmission.
  • a packet for transmission can be received at the PDCP layer from higher layers and enter the transmission buffer 1110, where sequence numbering can be performed on the data.
  • a Service Data Unit is a block of data that is passed from one layer to another within the protocol stack. SDUs represent data that higher layers send for transmission across the network.
  • PDCP SDUs are the data units at the PDCP layer, representing data received from higher layers for further processing and transmission over the radio interface.
  • the PDCP entity can add headers 1114 to the PDCP SDUs as they are passed down from higher layers.
  • the headers include information that is used for the operation of the PDCP entity and for the recipient to understand how to process the data.
  • the PDCP entity can apply integrity protection 1118 and encryption (ciphering 1122) to protect the confidentiality and integrity of the data.
  • a PDCP header 1126 can then be added to the PDCP SDU and routed across the radio interface.
  • the PDCP entity Once the PDCP entity has processed and prepared the PDCP SDUs, they can be handed over to the RLC layer for further segmentation, concatenation, and encapsulation before being transmitted over the radio interface.
  • the PDCP entity can be used for reassembling the PDCP SDUs from the incoming data units.
  • the received packet can have its PDCP header removed 1130, followed by deciphering 1134 and integrity verification 1138.
  • the packet can then enter the reception buffer 1142, where packet reordering and duplicate discarding of packets can occur, based, in part, on the sequence numbering applied by the PDCP in the transmission buffer.
  • the packet can then have header decompression 1146 and be communicated to higher layers in the 3GPP protocol stack.
  • FIGs. 11b-d Reordering Scheme
  • FIGs. 11 b-d provide illustrations of example reordering schemes that can occur in the reception buffer of the PDCP entity, in accordance with some embodiments.
  • the Third Generation Partnership Project (3GPP) comprises a reordering scheme to enable in-order delivery of received packets at the PDCP layer to be sent to an upper layer.
  • a lower layer Hybrid Automatic Repeat reQuest/Automatic Repeat reQuest (HARQ/ARQ) transmission can result in one or more out-of-order PDCPSNs. If a PDCP packet is not received, it can result in a gap occurring between PDCP SN.
  • a reordering timer (t-reordering) is configured to operate at the receiving side of the PDCP entity. The duration of the timer is configured by RRC; and can range from 0 milliseconds (ms) to 3000 ms. The reordering timer can be used to detect the loss of PDCP PDUs.
  • SN gap detection can have limits. An SN gap is detected only after one PDCP packet is successfully received. The later a successful packet is received, the longer a re-ordering window can be, as shown in FIGs. 11 b-d. A longer re-ordering window can occur in real-time traffic with an unacknowledged mode (UM) .
  • UM unacknowledged mode
  • a packet transmission failure (e.g. SN1) may have a different length re-ordering window and a different delivery latency.
  • FIG. 11 b is a schematic illustration of an example reordering scheme 1150 in which a number (N) of missing packets (e.g. SN1, SN2 and SN3) is greater than one (N > 1) , according to some examples. While the actual SN gap begins at time t1, the SN gap is not detected by the UE until a successful packet (e.g. SN4) is received at a later time (e.g. t4) . Thus, the reorder timer (t-Reordering timer) starts later, at time t4; resulting in a different (e.g. longer) re-ordering window 1154 for SN1.
  • N number of missing packets
  • the SN gap occurs at time t1 and is detected by the UE at the next time a packet is successfully received, which is at time t2 in this example.
  • the t-Reordering timer starts at time t2;resulting in a different (e.g. smaller) re-ordering window with respect to the example of FIG. 11 b.
  • the SN gap in the example of FIG. 11d occurs at time t1 and is detected by the UE at time t2 after an empty period in which no packet is received, resulting in a longer interval than in the example of FIG. 11 c.
  • the t-Reordering timer starts at time t2 after the longer interval; resulting in a different re-ordering window than the re-ordering windows illustrated in the examples of FIGs. 11 b and 11c.
  • the re-order windows can have a different length, with some being longer or shorter than others.
  • the packets are generated sequentially. During transmission, the transmission of some packets may fail, resulting in the “missing packets” .
  • the sequence numbers (SN) are not consecutive, e.g. N-2/N packets are received, it indicates that one or packets are missing since N packets are expected but not received.
  • FIGs. 12 and 13 Network Scheduling Schemes
  • FIGs. 12 and 13 provide illustrations of example network scheduling schemes, in accordance with some embodiments.
  • FIG. 12 is a schematic illustration of an example reordering scheme with a number (N) of missing packets (e.g. SN2 and SN3) , according to some examples.
  • FIG. 13 is a schematic illustration of an example reordering scheme with a number (N) of missing packets (e.g. SN3) , according to some examples.
  • a network can schedule 2 packets (e.g. SN0 and SN1) to be transmitted every 40ms.
  • NW network
  • CDRX Connected Discontinuous Reception
  • the network can assemble 2 voice packets together in 1 HARQ transmission. If the packets are not received, the resulting SN gaps can be detected by the UE 40ms later when the next packets are received.
  • a network can schedule 1 packet every 20ms.
  • the network can assemble 1 voice packet in 1 HARQ transmission. If a packet is not received, the SN gap can be detected by the UE 20ms later. As shown in the two examples (Cases 1 and 2) , the SN gap caused re-ordering windows can have different duration; and the latency (i.e. the delay in detecting when a packet is not received) of valid packets can be different. Therefore, the different network scheduling schemes can be different, while the t-Reordering timer can be the same; resulting in different length re-ordering windows.
  • the reordering window can be a potential window for potential retransmission, which can start from a first transmission that fails and can end at a timestamp of an expiration of the t-Reordering timer.
  • the reorder timer can be configured by the network, i.e. a network configured reorder timer, based on considerations, such as environment.
  • the UE can detect or monitor the scheduling pattern (e.g. 20 ms or 40 ms) and can scale the network configured reorder timer at the UE.Thus, the UE can determine the scheduling pattern and re-calculate the t-Reordering timer based on the determined network scheduling pattern.
  • the threshold can be selected between 0 and 40ms in one aspect, or 20ms in another aspect.
  • the threshold can be set by the UE’s configuration.
  • the threshold can be configured by the UE, e.g. as 20 ms.
  • the UE can then re-calculate the t-Reordering timer per the determined network scheduling as: t-Reordering + 20ms*N
  • N 1 for Case 1 (i.e. shorter, such as 20 ms) and 2 for Case 2 (i.e. longer, such as 40 ms) .
  • FIG. 14 Flow Chart for a Method of Adaptive Reordering of Voice Packets
  • FIG. 14 illustrates a flow chart of an example of a method of adaptive reordering of voice packets, according to some embodiments.
  • the method 1400 shown in FIG. 14 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices.
  • some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.
  • the method 1400 can comprise receiving 1410, at the UE 106:
  • voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer;
  • a network configured reordering timer.
  • the method 1400 can comprise determining 1420, at the UE 106, a network scheduling scheme for the plurality of packets.
  • the scheduling scheme can comprise receiving the plurality of packets at a first interval or the plurality of packets at a second interval.
  • the first interval can be greater than the second interval.
  • the method 1400 can comprise re-calculating 1430 the network configured reordering timer for the plurality of voice packets based on the network scheduling scheme.
  • determining 1420 the network scheduling scheme can further comprise: recording an arrival time of each voice packet having an SN; calculating an inter SN interval between proximate packets in the voice packets; calculating a difference between a maximum interval and a minimum interval between the arrival time of the proximate packets; and comparing the difference to a threshold (TH) level.
  • the TH can be selected to account for jitter.
  • re-calculating 1430 the network configured reordering timer can further comprise scaling the network configured reorder timer based on the network scheduling scheme.
  • the new timer can be a function of the network configured t-Reordering timer and network scheduling patterns.
  • the network configured t-Reordering timer cam be scaled by its scheduling patterns, and a new timer can be determined after scaling.
  • re-calculating 1430 the network configured reordering timer can further comprise: t-Reordering + 20 milliseconds (ms) *N
  • t-Reordering is the network configured reordering timer
  • N 1 when a single voice packet is received every 20 ms;
  • N 2 for when two voice packets are received every 40 ms.
  • a UE 106 and/or baseband processors 604 can be configured to perform the methods above.
  • FIG. 15 Invalid Re-Ordering for Silence Status
  • FIG. 15 provides an illustration of an example reordering scheme 1500, in accordance with some embodiments.
  • Silence status corresponds to when a user/speaker is not speaking.
  • SID silence insertion descriptor
  • the SID packets are generated at the onset of the silence period and whenever the characteristics of the background noise change.
  • the speech decoder that receives the SID packet can use a comfort noise generation (CNG) algorithm to reproduce the background noise from the information in the packet and possibly information contained in past active voice packets.
  • CNG comfort noise generation
  • the SID packets can be generated during silence status to provide a better listening experience for the listener.
  • the SID packets may be generated every 20 ms and can be relatively small compared to voice packets.
  • the network configured t-Reordering timer may be invalid for voice silence status.
  • the network may configure the t-Reordering timer with 50 ⁇ 100ms.
  • silence status silence insertion descriptor (SID) packets may be received every 160ms/200ms.
  • SID silence insertion descriptor
  • the resulting SN gap may have occurred 160ms/200ms prior to when the missing SID packet is detected (when the next SID packet is received) .
  • the missing SID packet were to be received at a later time, the time is typically within a few tens of milliseconds. Accordingly, if no packet is received between the relatively long period of 160/200ms of the SID packets, the missing SID packet likely may not be received.
  • SID packets are rarely received with their SN number out of order. Accordingly, the re-ordering may be meaningless for voice silence, and may contribute additional latency.
  • packets can be received at the UE every 20 or 40 ms and may be received with their SN number out of order.
  • the voice packets can be released at 160/200ms intervals, which can be relatively long. But a common reorder timer can be 60 ms in length.
  • a UE detects a missing SID packet, e.g. SN1
  • the UE can start the reorder timer, e.g. 60 ms.
  • the missing SID packet SN1 happened at t1, e.g. 160 ms ago before detection by the UE.
  • a missing SID packet SN1 probably will not be received.
  • the reordering timer can be meaningless for the packets received during the silent status because SN gap detection, which occurs the next time a packet is received, is too late and the missing packet happened a long time ago.
  • the UE can re-use the t-Reordering timer.
  • the UE can be configured to not start a t-Reordering timer when SID packets are received and deliver packets directly.
  • the UE may not add further delay with the reordering timer when receiving silent (SID) packets are received.
  • the UE can detect the status of the received packets, i.e. active or silence, or just detect silence status.
  • the UE may not start the reorder timer and deliver the SID packets directly to a higher layer, such as the application layer. For example, the UE can deliver the next packet, e.g. SN2, to the upper layer or the application layer without buffering the packets in Layer 2 during the reordering timer.
  • a user equipment UE 106 can comprise one or more baseband processors 604 coupled to a memory 604G.
  • the processors 604 can be configured to receive, at the UE 106:
  • voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer;
  • SN PDCP sequence number
  • PDCP packet data convergence protocol
  • SID silence insertion descriptor
  • a network configured reordering timer.
  • the UE 106 can further comprise application processors 402 that can be configured to determine, at the UE 106, a voice status of the packets as:
  • the processors 402 can be configured to detect, at the UE 106, an SN packet gap associated with one or more missing packets.
  • the processors 604 can be configured to start, at the UE 106, the network configured reordering timer when the SN packet gap is detected and the packet is determined to be a voice packet with the active status, or deliver the packets directly to a higher layer than the PDCP layer without starting the network configured reordering timer when the SN packet gap is detected and the packet is determined to be an SID packet with the silence status.
  • application processors 402 can further be configured to:determine the status of the packets based on an interval of receiving the voice packets or the SID packets.
  • the SID packets can be received with an interval that is greater than an interval of the voice packets.
  • the voice packets with the active status can be received periodically approximately every 20 or 40 milliseconds (ms) .
  • the SID packets with the silence status can be received periodically approximately every 160 or 200 ms.
  • the processors 604 can further be configured to determine the voice status of the packets based on a size of a voice packet or an SID packet.
  • the size of the SID packet can be less than the size of the voice packet.
  • the size of the voice packets with the active status can be greater than approximately 50 bytes.
  • the size of the SID packets with the silence status can be approximately 10 bytes.
  • the size of the voice packets can be greater than 40 bytes.
  • the size of the SID packets can be less than 15 bytes.
  • FIG. 16 Flow Chart for a Method of Adaptive Reordering of Voice Packets
  • FIG. 16 illustrates a flow chart of an example of a method of adaptive reordering of voice packets, according to some embodiments.
  • the method 1600 shown in FIG. 16 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices.
  • some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.
  • the method 1600 can comprise receiving 1610, at the UE 106:
  • voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer;
  • SN PDCP sequence number
  • PDCP packet data convergence protocol
  • SID silence insertion descriptor
  • a network configured reordering timer.
  • the method 1600 can further comprise determining 1620, at the UE 106, a voice status of the packets as:
  • the method 1600 can further comprise detecting 1630, at the UE 106, an SN packet gap associated with one or more missing packets.
  • the method 1600 can further comprise starting 1640, at the UE 106, the network configured reordering timer when the SN packet gap is detected and the packet is determined to be a voice packet with the active status, or delivering the packets directly to a higher layer than the PDCP layer without starting the network configured reordering timer when the SN packet gap is detected and the packet is determined to be an SID packet with the silence status.
  • determining 1620 the voice status of the packets can further comprise determining the status of the packets based on an interval of receiving the voice packets or the SID packets.
  • the SID packets can be received with an interval that is greater than an interval of the voice packets.
  • the voice packets with the active status can be received periodically approximately every 20 or 40 milliseconds (ms) .
  • the SID packets with the silence status can be received periodically approximately every 160 or 200 ms.
  • determining 1620 the voice status of the packets can further comprise determining the voice status of the packets based on a size of a voice packet or an SID packet.
  • the size of the SID packet can be less than the size of the voice packet.
  • the voice packets with the active status can be greater than or equal to approximately 50 bytes.
  • the SID packets with the silence status can be less than or equal to approximately 10 bytes.
  • a UE 106 and/or processors 402 can be configured to perform the methods above.
  • FIGs. 17 and 18 Racing Condition During Active/Silence Transition
  • packets arrive at the UE with random jitters in their arrival time. Packets may also arrive out of order, as previously discussed.
  • the packets from Layer 2 e.g. the PDCP layer
  • Layer 2 e.g. the PDCP layer
  • a jitter buffer also referred to as a de-jitter buffer
  • FIG. 17 provides an illustration of an example reordering scheme 1700, in accordance with some embodiments.
  • Layer 2 L2 is illustrated to show packets that are received, assigned sequence numbers, and potentially reordered, if necessary, in a reordering window.
  • the packets are then passed to a jitter buffer in a higher layer that is used to absorb the jitter in the arrival time of the packets from Layer 2.
  • the packets may be stuck in L2 during a transition of the received packets from a silence status with SID packets to an active status with voice packets.
  • the voice packets may be configured for Voice over long term evolution (VoLTE) or Voice over 5G (Vo5G) .
  • the L2 can have a relatively long t-Reordering timer during silence status.
  • the UE may still use a long t-Reordering timer since it is assumed, in the SN gap of the missing SN2 packet, that the packets in the L2 layer are still in a silence status (no voice packets arrived to update a jitter buffer length and t-Reordering timer) .
  • the voice packets may be stuck in L2 due to the length of the re- ordering timer that is set to silence status.
  • SN0 and SN1 are noise packets, i.e. SID packets
  • SN2 is a voice packet but is missing due to the wireless environment.
  • the SN3 voice packet is received at L2, after an SN gap when the SN2 voice packet does not arrive at the UE.
  • the t-reordering timer is started with the assumption that SN3 is a SID packet and the UE is set to a silence status, thereby resulting in a large t-reordering timer.
  • the jitter buffer can be in an application or module of a voice application. Since the t-reordering timer is set to a long period, multiple additional voice packets will arrive during the t-reordering timer. So, the jitter buffer cannot receive the SN3 packet during the t-reordering timer.
  • the jitter buffer is not aware of the transition from the silence status to the active status and is still in silence status until the SN3 voice packet and other voice packets arrive with a period of 20 to 40 ms, rather than the 160 to 200 ms of the SID packets. But the packets may arrive late because of the reordering timer, which can be relatively long in the silence status. Meanwhile, the voice packets are buffering in Layer 2. The result can be a long latency period.
  • the jitter buffer did not receive the voice packet SN2. So, the jitter buffer does not switch status from silence status to active status.
  • the reorder timer is long, and the packets may be buffered for a long time, resulting in a long latency period of potentially hundreds of milliseconds. In addition, the packets may be discarded by the jitter buffer due to the long delay at L2.
  • the UE does not start the reorder timer, but delivers the packet directly to the upper layer or application layer (i.e. the jitter buffer) .
  • the purpose of the reorder timer is to allow packets that arrive out of order, with reference to each packet’s SN number, to be received, and re-ordered sequentially at the Layer 2 before sending the packets to a higher layer.
  • the reorder timer is not started and SN3 is a voice packet that is delivered unexpectedly during the silence status, and SN2 is a voice packet that is late, then the SN2 packet will be discarded by Layer 2 because the voice status is now active, not the silence status.
  • the jitter buffer in the upper layer is unaware a transition has occurred and cannot inform Layer 2. This results in the SN2 packet not being reordered. Whether the SN2 packet is not reordered or is dropped, the result is the same.
  • the SN2 packet is not able to be sent to the higher layer from the L2 layer.
  • FIG. 18 provides an illustration of an example reordering scheme 1800, in accordance with some embodiments.
  • the voice packets may be missing during a transition from a silence status to an active state. Once the voice packets are missing during the silence to active status transition, without t-Reordering, the packets are delivered. Once SN gaps occur when packets are not received in L2, the PDCP entity may discard them when the received count is less than the received (RCVD_COUNT ⁇ RX_DELIV) . This can occur since the voice packets may not be re-ordered in L2 if the reorder timer is not started.
  • FIG. 19 Re-Ordering Adaptation During Silence/Active Transition
  • FIG. 19 provides an illustration of an example reordering scheme 1900, in accordance with some embodiments.
  • the reordering scheme illustrated in this example can be used to resolve the issues that can be caused when there is an SN gap during a transition from silence status to active status that can either cause a large latency, as illustrated in FIG. 17, or result in the SN packets not being reordered, as illustrated in FIG. 18.
  • the UE can use one or more application processors 402 or baseband processors 604 to monitor the arriving packets at L2 and determine a current voice status.
  • the size of the packets or the arrival time of the packets in L2 can be used to determine a silence/active status.
  • the arriving packets may be determined to have an active status if the size of the packets are greater than a threshold level (TH) .
  • the arriving packets may be determined to have an active status if an inter-packet-interval of the arriving packets is less than a TH level.
  • the one or more processors can set a silence or active specific t-Reorder timer respectively.
  • the one or more processors can start an active specific t-Reorder timer once a silence to active status transition is detected.
  • the UE can perform voice monitoring of the voice status and determine if there is a silence status or an active status based on a change in packet size. So, the UE, monitoring the packet size, arrival time, and periodicity of packets arriving at Layer 2, can directly determine the silence or active status and can accordingly change to a specific silence or active reordering timer.
  • the UE can start reordering time when it detects a voice packet, i.e. active status, after an SID packet, i.e. silence status.
  • a package size for SID packets in silence status is relatively small, e.g. 0-10 bytes, while a voice package in active status is relatively large, e.g. 50 bytes.
  • a threshold can be set, e.g. 25-30 bytes. Based on interval, an interval for voice packages is relatively small, e.g. 20-40 ms, while an interval for silence is relatively large, e.g. 160 ms.
  • a user equipment (UE) 106 can comprise one or more processors 604 coupled to a memory 406.
  • the processors 604 can be configured to receive, at the UE 106:
  • voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer;
  • SN PDCP sequence number
  • PDCP packet data convergence protocol
  • SID silence insertion descriptor
  • a network configured reordering timer.
  • the processors 604 can be configured to determine, at the UE 103, a voice status of the packets as:
  • the processors 604, 402 can be configured to detect, at the UE 106, an SN packet gap associated with one or more missing packets in the voice packets or the SID packets received at the PDCP layer.
  • the processors 604 can be configured to start, at the UE, a different second reordering timer that is less than the network configured reordering timer when the SN packet gap is detected, and an active voice status is determined.
  • the processors 604 can be configured to deliver, at the UE 106, the packets directly to a higher layer than the PDCP layer at the expiration of the different second reordering timer.
  • the processors 604 can further be configured to determine the voice status of the packets based on an interval of receiving the voice packets or the SID packets.
  • the SID packets can be received with an interval that is greater than an interval of the voice packets.
  • the voice packets with the active status can be received every 20 or 40 milliseconds (ms) .
  • the SID packets with the silence status can be received every 160 or 200 ms.
  • the processors 604 can further be configured to determine a packet as active status when an inter-packet-interval of the packets is smaller than a threshold value.
  • the threshold value for the inter-packet-interval can be 20 to 40 milliseconds (ms) .
  • the processors 604 can further be configured to determine the voice status of the packets based on a size of a voice packet or an SID packet.
  • the size of the SID packet can be less than the size of the voice packet.
  • the voice packets with the active status can be greater than approximately 50 bytes.
  • the SID packets with the silence status can be approximately 10 bytes.
  • the processors are 604 can further be configured to determine a packet as active status when a packet size is greater than a threshold value.
  • the threshold value for the size of the packet can be 25 to 30 bytes.
  • the network configured reorder timer can further comprise a silence specific reorder timer and an active specific reorder timer.
  • the active specific reorder timer can be less than the silence specific reorder timer.
  • the processors 604 can further be configured to start the active specific reorder timer when the SN packet gap is detected, and an active voice status is determined.
  • FIG. 20 Flow Chart for a Method of Adaptive Reordering of Voice Packets
  • FIG. 20 illustrates a flow chart of an example of a method of adaptive reordering of voice packets, according to some embodiments.
  • the method 2000 shown in FIG. 20 may be used in conjunction with any of the systems, methods, or devices illustrated in the Figures, among other devices.
  • some of the method elements shown may be performed concurrently, in a different order than shown, or may be omitted. Additional method elements may also be performed as desired.
  • the method 2000 can comprise receiving 2010, at the UE 106:
  • voice packets of voice data each having a PDCP sequence number (SN) at a packet data convergence protocol (PDCP) layer;
  • SN PDCP sequence number
  • PDCP packet data convergence protocol
  • SID silence insertion descriptor
  • a network configured reordering timer.
  • the method 2000 can comprise determining 2020, at the UE 106, a voice status of the packets as:
  • the method 2000 can comprise detecting 2030, at the UE 106, an SN packet gap associated with one or more missing packets in the voice packets or the SID packets received at the PDCP layer.
  • the method 2000 can comprise starting 2040, at the UE 106, a different second reordering timer that is less than the network configured reordering timer when the SN packet gap is detected, and an active voice status is determined.
  • the method 2000 can comprise delivering 2050, at the UE 106, the packets directly to a higher layer than the PDCP layer at the expiration of the different second reordering timer.
  • determining 2020 the voice status of the packets can further comprise determining the voice status of the packets based on an interval of receiving the voice packets or the SID packets.
  • the SID packets can be received with an interval that is greater than an interval of the voice packets.
  • the voice packets with the active status can be received every 20 or 40 milliseconds (ms) .
  • the SID packets with the silence status can be received every 160 or 200 ms.
  • determining 2020 the voice status of the packets can further comprise determining a packet as active status when an inter-packet-interval of the packets is smaller than a threshold value.
  • the threshold value for the inter-packet-interval can be 20 to 40 milliseconds (ms) .
  • determining 2020 the voice status of the packets can further comprise determining the voice status of the packets based on a size of a voice packet or an SID packet.
  • the size of the SID packet can be less than the size of the voice packet.
  • the voice packets with the active status can be greater than approximately 50 bytes.
  • the SID packets with the silence status can be approximately 10 bytes.
  • determining 2020 the voice status of the packets can further comprise determining a packet as active status when a packet size is greater than a threshold value.
  • the threshold value for the size of the packet can be 25 to 30 bytes.
  • the network configured reorder timer can comprise a silence specific reorder timer and an active specific reorder timer.
  • the active specific reorder timer can be less than the silence specific reorder timer.
  • Starting 2040 the timer can further comprise starting the active specific reorder timer when the SN packet gap is detected, and an active voice status is determined.
  • a UE 106 and/or baseband processors 604 can be configured to perform the methods above.
  • Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer-implemented method, a computer readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices such as ASICs. Still other embodiments may be realized using one or more programmable hardware elements such as FPGAs.
  • a non-transitory computer-readable memory medium may be configured so that it stores program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to perform a method, e.g., any of the method embodiments described herein, or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets.
  • a device e.g., a UE 106 may be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or, any combination of the method embodiments described herein, or, any subset of any of the method embodiments described herein, or, any combination of such subsets) .
  • the device may be realized in any of various forms.
  • Any of the methods described herein for operating a user equipment may be the basis of a corresponding method for operating a base station, by interpreting each message/signal X received by the UE in the downlink as message/signal X transmitted by the base station, and each message/signal Y transmitted in the uplink by the UE as a message/signal Y received by the base station.

Landscapes

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

Abstract

Un procédé de réordonnancement adaptatif de paquets voix consiste à recevoir : des paquets voix de données audio ayant chacun un numéro de séquence (SN) PDCP ; des paquets de descripteur d'insertion de silence (SID) ; et un temporisateur de réordonnancement configuré en réseau. Le procédé consiste à déterminer un état vocal des paquets comme étant : un état actif lorsque des paquets voix sont reçus ; ou un état de silence lorsque des paquets SID sont reçus. Le procédé consiste à détecter un intervalle de paquet SN associé à un ou plusieurs paquets manquants. Le procédé comprend le démarrage du temporisateur de réordonnancement configuré en réseau lorsque l'intervalle de paquet SN est détecté et le paquet est déterminé comme étant un paquet voix à l'état actif, ou la distribution des paquets directement à une couche supérieure à celle de la couche PDCP sans démarrer le temporisateur de réordonnancement configuré en réseau lorsque l'intervalle de paquet SN est détecté et que le paquet est déterminé comme étant un paquet SID à l'état de silence.
PCT/CN2024/079240 2024-02-29 2024-02-29 Procédé de réordonnancement adaptatif pour voix Pending WO2025179521A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/079240 WO2025179521A1 (fr) 2024-02-29 2024-02-29 Procédé de réordonnancement adaptatif pour voix

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/079240 WO2025179521A1 (fr) 2024-02-29 2024-02-29 Procédé de réordonnancement adaptatif pour voix

Publications (1)

Publication Number Publication Date
WO2025179521A1 true WO2025179521A1 (fr) 2025-09-04

Family

ID=96919792

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/079240 Pending WO2025179521A1 (fr) 2024-02-29 2024-02-29 Procédé de réordonnancement adaptatif pour voix

Country Status (1)

Country Link
WO (1) WO2025179521A1 (fr)

Similar Documents

Publication Publication Date Title
US11877355B2 (en) Efficient and reliable data transfer in 5G systems
US10892957B2 (en) Managing physical network function instances in a network service instance
US11743870B2 (en) Interruption and delay for V2X sidelink carrier aggregation
CN111165031B (zh) 在载波聚合或双连接下针对缩短的传输时间间隔的定时提前调节延迟
US11038662B2 (en) Interruption for SCell activation and deactivation with short transmission time interval
EP3841793A1 (fr) Systèmes et procédés d'indication d'une capacité d'ue en lien avec des exigences de retard d'identification de cellule
US11778529B2 (en) Robust header compression indication after path switch during handover
US10862599B2 (en) Systems and methods for applying 4Rx capable UE tests to an 8Rx capable UE
WO2025179521A1 (fr) Procédé de réordonnancement adaptatif pour voix
WO2025208436A1 (fr) Optimisation d'utilisation de chercheur pour mesure ca/cc
WO2025199856A1 (fr) Configuration et procédés d'ue pour mettre en œuvre une mobilité déclenchée par l1/l2 (ltm) inter-cu
WO2025160752A1 (fr) Améliorations de la couverture pour pusch avec format dci 0_3
WO2025231663A1 (fr) Rrm, rlm et bfd dans une adaptation de ssb
WO2025199805A1 (fr) Mesure lte inter-rat sans intervalle de mesure
WO2025231713A1 (fr) Amélioration de l'activation d'une cellule secondaire (scell) à l'aide d'un rapport de mesure précoce (emr)
WO2025091354A1 (fr) Partage d'opportunités de mesure entre la couche 1 et la couche 3
WO2025091347A1 (fr) Sélection de cellule voisine pour mesure l1
WO2025231755A1 (fr) Amélioration de restriction de planification pour commutation de satellite douce sans changement de pci
US20250365589A1 (en) Near Real Time Wireless Network Outage Detection
WO2025231660A1 (fr) Minimisation des tests mobiles (mdt) pour collecte de données d'entraînement d'intelligence artificielle (ai)
WO2025179534A1 (fr) Améliorations d'ai/ml centrées sur l'ue pour ltm
WO2025171543A1 (fr) Améliorations apportées à un retard de commutation d'indicateur de configuration de transmission (tci) unifié avec deux avances temporelles (ta) dans la gamme de fréquences 2 (fr2)
WO2025212779A1 (fr) Maintien d'une session de pdu lors d'un changement inter-système entre des réseaux mobiles 4g et 5g
WO2025212463A1 (fr) Fonctionnalité d'intelligence artificielle/d'apprentissage automatique (ia/ml) postdéploiement et validation de dérive
WO2025212462A1 (fr) Mesure de test de précision de mesure de faisceau pour gestion de faisceau basée sur intelligence artificielle/langage machine (ia/ml)

Legal Events

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

Ref document number: 24926402

Country of ref document: EP

Kind code of ref document: A1