WO2023153999A1 - Indication d'aide à la libération pour une transmission de petites données de new radio (nr sdt) - Google Patents

Indication d'aide à la libération pour une transmission de petites données de new radio (nr sdt) Download PDF

Info

Publication number
WO2023153999A1
WO2023153999A1 PCT/SE2023/050123 SE2023050123W WO2023153999A1 WO 2023153999 A1 WO2023153999 A1 WO 2023153999A1 SE 2023050123 W SE2023050123 W SE 2023050123W WO 2023153999 A1 WO2023153999 A1 WO 2023153999A1
Authority
WO
WIPO (PCT)
Prior art keywords
rai
information
rrc
transmitting
network node
Prior art date
Application number
PCT/SE2023/050123
Other languages
English (en)
Inventor
Andreas HÖGLUND
Jan Christoffersson
Luca FELTRIN
Tuomas TIRRONEN
Henrik Enbuske
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2023153999A1 publication Critical patent/WO2023153999A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the present disclosure relates to methods, apparatuses, and systems for enabling release assistance indications (RAIs) in small data transmissions (SDTs).
  • RAIs release assistance indications
  • a Work Item RP -200954 ‘New Work Item on New Radio (NR) small data transmissions in INACTIVE state’ has been approved in the Third Generation Partnership Project (3 GPP) with the focus of optimizing the transmission for (mobile originated, i.e. uplink) small data payloads by reducing the signaling overhead.
  • the Work Item contains the following relevant objectives:
  • Radio Resource Control state as follows:
  • RACH Random Access Channel
  • CCCH Common Control Channel
  • NB-IoT Narrowband Internet of Things
  • LTE Long Term Evolution
  • MTC Machine Type Communication
  • SDT NR Small Data Transmission
  • MBB Mobile Broadband
  • UEs User Equipment
  • Random Access Small Data Transmission means that either legacy 4-step RACH or 2-step RACH procedure is used as a baseline but that a user-plane data payload can be appended (multiplexed with the RRCResumeRequest message) in Msg3 (or MsgA).
  • Configured Grant Small Data Transmission means that the UE is configured via RRC to have periodic CG-SDT occasions which can, contention-free, be used for uplink transmission. In this way Msgl and Msg2 can be omitted, but it is a requirement that the UE has a valid TA and is uplink synchronized to be able to use the resources for transmission.
  • WID work item description
  • a method is performed by a user equipment (UE).
  • the method includes, during an SDT procedure, transmitting to a network node information including an RAI.
  • RAI release assistance indications
  • Certain embodiments provide one or more of the following technical advantages: the disclosed subject matter provides support for RAI in New Radio (NR) without which the performance of SDT is poor, or even has inferior performance in some scenarios compared to legacy operation (i.e., without SDT).
  • NR New Radio
  • the transmitting the information including the RAI includes transmitting a Radio Resource Control (RRC) message including the RAI.
  • the transmitting the information including the RAI includes transmitting UE Assistance Information including the RAI.
  • the transmitting the UE Assistance Information including the RAI includes transmitting UE Assistance Information including the RAI together with an RRC Resume Request message using either a same uplink assignment or a separate uplink assignment.
  • the RAI is indicated by a preferred RRC state field comprised in the UE Assistance Information in a Release Preference Information Element (IE).
  • the transmitting the information including the RAI includes transmitting an RRC message including a Release Preference IE including the RAI.
  • the transmitting the RRC message including the RAI includes transmitting the RRC message including the RAI together with an RRC Resume Request message using either a same uplink assignment or a separate uplink assignment.
  • the Release Preference IE includes a preferred RRC state field that includes the RAI.
  • a plurality of codepoints for the preferred RRC state field are re-mapped to a respective plurality of RAI values when the UE Assistance Information is transmitted during an SDT procedure, and the preferred RRC state field is set to one of the plurality of codepoints for the preferred RRC state field that is re-mapped to a desired one of the plurality of RAI values.
  • the transmitting the information including the RAI includes transmitting information that includes a Release Preference IE including a new field that includes the RAI.
  • the transmitting the information including the RAI includes transmitting an RRC Resume Request message including the RAI.
  • the RAI is indicated via a re-purposed spare bit in the RRC Resume Request message.
  • the RAI is indicated via a Resume Cause field of the RRC Resume Request message.
  • one or more defined values for the Resume Cause field are remapped to one or more RAI values when the RRC Resume Request message is transmitted during an SDT procedure.
  • the transmitting the information including the RAI includes transmitting a Medium Access Control (MAC) Control Element (CE) including the RAI.
  • the MAC CE is a Buffer Status Report (BSR) MAC CE.
  • BSR Buffer Status Report
  • the different subsets of a plurality of indices defined for the BSR MAC CE are mapped to different RAI values, and the BSR MAC CE includes one of the plurality of indices that is mapped to a desired one of the different RAI values.
  • the BSR MAC CE is interpreted using a first table when sent during an SDT procedure and otherwise interpreted using a second table that is different than the first table.
  • the BSR MAC CE includes a Logical Channel Identifier (LCID) or an Enhanced LCID (eLCID) that indicates that the BSR MAC CE includes the RAI.
  • the BSR MAC CE include an LCID or eLCID, that indicates the RAI.
  • the transmitting the information including the RAI includes transmitting a Msg5 or an RRC Setup Complete message including the RAI.
  • the RAI includes information that indicates an expected traffic pattern for the UE on a per radio bearer basis.
  • the transmitting the information including the RAI includes transmitting the information including the RAI to the network node via an NR Uu interface.
  • the UE is an NR UE
  • the network node is a next-generation Node B (gNB).
  • gNB next-generation Node B
  • a UE includes transmitter circuitry and processing circuitry associated with the transmitter circuitry.
  • the processing circuitry is configured to cause the UE to transmit to a network node during an SDT procedure information including an RAI.
  • the method includes receiving, from a UE during an SDT procedure, information including an RAI.
  • the receiving the information including the RAI includes receiving an RRC message including the RAI. In some embodiments, the receiving the information including the RAI includes receiving UE Assistance Information including the RAI. In some embodiments, the receiving the information including the RAI includes receiving an RRC message including a Release Preference IE, the Release Preference IE including the RAI. In some embodiments, the receiving the RRC message including the RAI includes receiving the RRC message including the RAI together with an RRC Resume Request message using either a same uplink assignment or a separate uplink assignment. In some embodiments, the Release Preference IE includes a preferred RRC state field that includes the RAI.
  • the receiving the information including the RAI includes receiving information that includes a Release Preference Information Element, IE, the Release Preference IE including a new field that includes the RAI.
  • IE Release Preference Information Element
  • the receiving the information including the RAI includes receiving UE Assistance Information including the RAI together with an RRC Resume Request message using either a same uplink assignment or a separate uplink assignment.
  • the RAI is indicated by a preferred RRC state field comprised in the UE Assistance Information in a Release Preference IE.
  • a plurality of codepoints for the preferred RRC state field are remapped to a respective plurality of RAI values when the UE Assistance Information is received during an SDT procedure, and the preferred RRC state field is set to one of the plurality of codepoints for the preferred RRC state field that is re-mapped to a desired one of the plurality of RAI values.
  • the receiving the information including the RAI includes receiving an RRC Resume Request message including the RAI.
  • the RAI is indicated via a re-purposed spare bit in the RRC Resume Request message.
  • the RAI is indicated via a Resume Cause field of the RRC Resume Request message.
  • one or more defined values for the Resume Cause field are re-mapped to one or more RAI values when the RRC Resume Request message is transmitted during an SDT procedure.
  • the receiving the information including the RAI includes receiving a MAC CE, including the RAI.
  • the MAC CE is a BSR MAC CE.
  • different subsets of a plurality of indices defined for the BSR MAC CE are mapped to different RAI values, and the BSR MAC CE includes one of the plurality of indices that is mapped to a desired one of the different RAI values.
  • the BSR MAC CE is interpreted using a first table when sent during an SDT procedure and otherwise interpreted using a second table that is different than the first table.
  • the BSR MAC CE includes an LCID, or an eLCID, that indicates that the BSR MAC CE includes the RAI. In some embodiments, the BSR MAC CE includes an LCID, or an eLCID that indicates the RAI. In some embodiments, the receiving the information including the RAI includes receiving a Msg5 or an RRC Setup Complete message including the RAI. In some embodiments, the RAI includes information that indicates an expected traffic pattern for the UE on a per radio bearer basis. In some embodiments, the method further includes performing one or more actions based on the RAI.
  • the receiving the information including the RAI includes receiving the information including the RAI from the UE via an NR Uu interface.
  • the UE is an NR UE and the network node is a gNB.
  • a network node includes receiver circuitry and processing circuitry associated with the receiver circuitry.
  • the processing circuitry is configured to cause the network node to receive, from a UE during an SDT procedure, information including an RAI.
  • a non-transitory computer readable medium having code stored thereon, the code, when executed, causing a processor to perform a method as disclosed herein.
  • FIG 1 shows a Medium Access Control (MAC) Control Element (CE) for a Downlink Channel Quality Report (DCQR) and Access Stratum Release Assistance Indication (AS RAI).
  • MAC Medium Access Control
  • CE Control Element
  • DCQR Downlink Channel Quality Report
  • AS RAI Access Stratum Release Assistance Indication
  • Figure 2 shows an example of a User Equipment (UE) Assistance Information.
  • UE User Equipment
  • Figure 3 shows an example of New Radio (NR) subheaders for fixed size MAC CE including Logical Channel Identifiers (LCIDs) and two reserved bits (R).
  • NR New Radio
  • Figure 4 shows an example variable length MAC CE structure where the UE provides information for “m” Radio Bearers (RBs), and this information includes, for each radio bearer, an indicator bit “S” and two bits used to provide Release Assistance Indication (RAI).
  • RBs Radio Bearers
  • RAI Release Assistance Indication
  • Figure 5 illustrates the operation of a UE and a network node, in accordance with some example embodiments.
  • Figure 6 shows a communication system, in accordance with some example embodiments.
  • Figure 7 shows a UE, in accordance with some example embodiments.
  • Figure 8 shows a network node, in accordance with some example embodiments.
  • Figure 9 shows a block diagram of a host, in accordance with example embodiments.
  • Figure 10 shows a block diagram illustrating a virtualization environment, in accordance with some example embodiments.
  • Figure 11 shows a communication diagram of a host communicating via a network node with a UE, in accordance with some example embodiments.
  • SDT Small Data Transmission
  • UE User Equipment
  • NR New Radio
  • RAI Release assistance indication
  • LTE Long Term Evolution
  • AS Access Stratum
  • BSR Buffer Status Report
  • DL downlink
  • UL uplink
  • CIoT Cellular Internet of Things
  • NAS Non-Access Stratum
  • CN Core Network
  • the gNB would release the UE at first after a RRC inactivity timer expires (i.e., indicating that there is no further data activity).
  • AS RAI is captured in 3GPP Technical Specification (TS) 36.321 V16.6.0 shown in the following excerpts (DCQR is a Downlink Channel Quality Report, AS RAI is Access Stratum Release Assistance Indication):
  • Access Stratum Release Assistance Indication is used to provide the serving eNB with information whether subsequent DL or UL transmission is expected.
  • AS RAI uses the DCQR and AS RAI MAC Control Element. Upper layers trigger AS RAI.
  • AS RAI For EDT and transmission using PUR, if AS RAI is triggered by upper layers but is not included in the resulting MAC PDU with the MAC SDU as a result of logical channel prioritization, AS RAI is cancelled, for other transmissions if AS RAI is not included in the resulting MAC PDU as a result of logical channel prioritization, AS RAI may be cancelled.
  • rai-Activation is configured and a buffer size of zero bytes has been triggered for the BSR and no subsequent DL and UL data transmission is expected, and if rai-ActivationEnh is enabled and applicable as specified in TS 36.331 [8], it is up to UE to send BSR MAC control element or DCQR and AS RAI MAC control element.
  • DCQR and AS RAI MAC control element is identified by a MAC PDU subheader with LCID as specified in Table 6.2.1-2.
  • a MAC PDU shall contain at most one DCQR and AS RAI MAC control element.
  • - R Reserved bit, set to “0”
  • - AS RAI The field corresponds to Access Stratum Release Assistance Indication as shown in Table 6.1.3.19-1.
  • the length of the field is 2 bits;
  • the field corresponds to CQI-NPDCCH-NB as defined in TS 36.331 [8]
  • the field corresponds to DL channel quality report as defined in TS 36.133 [9]
  • the length of the field is 4 bits.
  • Embodiments of the present disclosure provide support for RAI in NR, without which the performance of SDT is poor, or even have inferior performance compared to legacy operation (i.e., without SDT), at least in some scenarios.
  • UE Assistance Information which can be sent to the gNB by the UE.
  • the following IE in the UE assistance information can indicate the preferred Radio Resource Control (RRC) state of the UE:
  • ReleasePreference-rl6 SEQUENCE ⁇ preferredRRC-State-rl6 ENUMERATED ⁇ idle, inactive, connected, outOfC onnected ⁇ ⁇
  • the UE When configured to do so, the UE can signal the network through UEAssistancelnformation'.
  • start timer T346f with the timer value set to the releasePreferenceProhibitTimep 3> initiate transmission of the UEAssistancelnformation message in accordance with 5.7.4.3 to provide the release preference;
  • the UE can indicate that it prefers to be in the RRC IDLE state, and the gNB can use this information to release the UE to RRC IDLE state.
  • SDT is specified in the RRC INACTIVE state, and the UE stays in the RRC INACTIVE Inactive state during the entire SDT procedure, meaning the ReleasePreference IE does not apply.
  • the fields of preferredRRC-State contained in the UE Assistance Information are remapped to RAI values.
  • the actual values (code points) would be kept the same, and the re-mapping is introduced in the field description (additions in bold, underlined text):
  • ReleasePreference-rl6 SEQUENCE ⁇ preferredRRC-State-rl6 ENUMERATED ⁇ idle, inactive, connected, outOfC onnected ⁇ ⁇ indicated if the UE prefers to be released from RRC CONNECTED and transition to RRC INACTIVE.
  • the value connected is indicated if the UE prefers to revert an earlier indication to leave RRC CONNECTED state.
  • the value outOfConnected is indicated if the UE prefers to be released from RRC CONNECTED and has no preferred RRC state to transition to.
  • the value connected can only be indicated if the UE is configured with connectedReporting.
  • the value idle is indicating that ‘No subsequent DL and UL data transmission is expected
  • the i value inactive is indicating that ‘A single subsequent DL transmission is expected’
  • the value connected is indicating that ‘the UE prefers to be moved to RRC CONNECTED’
  • the value outOfConnected is indicating that there is no RAI information.
  • mapping above is only an example.
  • the codepoints of preferredRRC-State may be re-mapped to RAI values in any desired manner, as long as the re-mapping is known to both the UE and the gNB.
  • UEAssistancelnformation is transmitted in an Uplink Dedicated Control Channel (UL-DCCH) through Signaling Radio Bearer 1 (SRB1) which is resumed before Msg3/MsgA transmission; therefore, no particular action is required to enable the transmission of this indication together with RRCResumeRequest or RRCResumeRequestl in the first UL transmission.
  • SRB1 Signaling Radio Bearer 1
  • UEAssistancelnformation including Re leasePreference IE, is transmitted either using the same uplink assignment together with RRCResumeRequest or RRCResmeRequestl or using a separate uplink assignment either implicitly or explicitly provided when using SDT.
  • the ReleasePreference IE contains the preferredRRC-State field for which, when reported during an SDT procedure, has values (codepoints) that are re-mapped to RAI values in a defined manner (see example above).
  • a new RRC message is defined to be used in the first uplink transmission, including full UEAssistancelnformation or at least the ReleasePreference IE.
  • a new version of ReleasePreference IE is defined with a new field indicating the values for a RAI.
  • the cases of no RAI information, no further data is expected in the future, a single DL packet is expected in the future, and a spare or reserved value, correspondingly, are defined as exemplary code points in the following ASN.1 example:
  • ReleasePreference-rXY SEQUENCE ⁇ releaseAssistance-rXY ENUMERATED ⁇ noRAI, noFurtherData, 12ingled, spare 1 ⁇
  • the RAI information is provided to the gNB in the RRCResumeRequest message.
  • the spare bit currently defined in the RRCResumeRequest message could be reused to indicate to the gNB that the UE has no further uplink transmission, nor is it expecting any downlink transmission. For example, this may be done through the following modification (in bold font where strikethrough means deletion and underlining means insertion):
  • RRCResumeRequest SEQUENCE ⁇ rrcResumeRequest RRCResumeRequest-Ies
  • RRCResumeRequest-Ies SEQUENCE ⁇ resumeidentity Shortl-RNTI- Value, resumeMAC-I BIT STRING (SIZE (16)), resumeCause ResumeCause, spare - - BIT STRING (SIZE (1)) rai _ ENUMERATED (true) OPTIONAL
  • resumeCause values are re-interpreted to map to different RAI values when RRCResumeRequest(l) is transmitted during the SDT procedure:
  • ResumeCause ENUMERATED ⁇ emergency, highPriority Access, mt-Access, mo- Signalling, mo-Data, mo-VoiceCall, mo- VideoCall, mo-SMS, rna-Update, mps-Priority Access, mcs-Priority Access, spare 1, spare2, spare3, spared, spare5 ⁇
  • the spare values could be mapped to different RAI values such that:
  • a new RRC message referred to herein as RRCResumeRequestSDT
  • RRCResumeRequestSDT is used for SDT and explicitly includes a new RAI IE which would include the code points for RAI, which may include one or more of the following: “No RAI information”, “No subsequent DL and UL data transmission is expected”, “A single subsequent DL transmission is expected”, and possibly other code points.
  • only two code points for RAI are defined (related to either of the above embodiments), for the cases whether a further DL transmission is expected or not expected.
  • the existing BSR mechanism can be updated to provide information that indicates whether further uplink transmission is expected or not.
  • further configuration enables the UE to indicate zero buffer size in the case the current buffer is empty and there is no more expected uplink transmission.
  • the BSR Medium Access Control Control Element is reused to indicate RAI values.
  • padding the BSR header fields such as R-bits may in this case include the RAI indication.
  • SDT may not support transmitting more than 100 bytes (since small data), and BSR entries could then be repeated to mean the same BSR value but a different RAI value.
  • Legacy BSR looks like follows:
  • Table 2 Reproduction of Table 6.1.3.1-1 from 3GPP TS 38.321: Buffer size levels (in bytes) for 5-bit Buffer Size field
  • the BSR is, in accordance with one exemplary embodiment, re-interpreted according to the following table:
  • the BSR MAC CE could be mapped to a different BSR table when used with SDT.
  • the MAC subheader is used to indicate the RAI value.
  • the NR subheaders for fixed size MAC CE (from 3GPP TS 38.321 V16.7.0) are shown in Figure 3 as an example.
  • the two R-bits are used to indicate RAI.
  • One example is
  • the advantage with this embodiment is that no new MAC CE needs to be defined for RAI and therefore two bytes are saved (one byte for MAC subheader and one byte for a new RAI MAC CE).
  • LCID Logical Channel Identifier
  • 3 (or 1) new LCIDs are defined for Common Control Channel (CCCH) or BSR, each of the LCIDs representing a code point for RAI.
  • the RAI indication is conveyed as a “header only” MAC CE as illustrated in Figure 3, for where only the LCID or enhanced LCID (eLCID) defines the signaling MAC CE and where additional header fields such as R-fields convey the RAI.
  • even more the preamble space is partitioned so that from:
  • a bit indication conveys that: • The UE expects more than n subsequent UL data transmissions with the current transport block size, or alternatively, based on the currently used grant resource.
  • n may be defined in specifications as a threshold number (e.g., per logical channel or per MAC entity, or other), or
  • Buffer content would require more than a Delay Condition ms/slots or other to be transmitted with n subsequent SDT UL transmissions using the current grant/UL resource.
  • the delay condition may be representing a specific logical channel or logical channel group, or similar.
  • bit indication could indicate an expected DL transmission expected within a Delay Condition corresponding to a logical channel/group transmitted on the UL resource.
  • the UE informs the gNB about the expected traffic pattern on a Radio Bearer (RB) basis during the initial configuration or subsequent updates of such configuration.
  • RB Radio Bearer
  • the UE During initial access (i.e., RRC connection establishment procedure), the UE typically sends some assistance information to the gNB in Msg5/RRCSetupComplete.
  • This RRC message can be extended to include a new indication in the following non-limiting way:
  • RRCSetupComplete-Ies SEQUENCE ⁇ selectedPLMN-Identity INTEGER (1 . maxPLMN), registeredAMF RegisteredAMF OPTIONAL, guami-Type ENUMERATED ⁇ native, mapped ⁇ OPTIONAL, s-NSSAI-List SEQUENCE (SIZE (L.maxNrofS-NSSAI)) OF S-NSSAI
  • OPTIONAL dedicatedNAS-Message DedicatedNAS-Message, ng-5G-S-TMSI-Value CHOICE ⁇ ng-5G-S-TMSI NG-5G-S-TMSI, ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9)) ⁇ OPTIONAL,
  • RRCSetupComplete-vl610-Ies : : SEQUENCE ⁇ iab-NodeIndication-rl6 ENUMERATED ⁇ true ⁇ OPTIONAL, idleMeasAvailable-r!6 ENUMERATED ⁇ true ⁇ OPTIONAL, ue-MeasurementsAvailable-r 16 UE-MeasurementsAvailable-rl6 OPTIONAL, mobility Hi story Avail-r 16 ENUMERATED ⁇ true ⁇ OPTIONAL, mobility State-r 16 ENUMERATED ⁇ normal, medium, high, spare ⁇
  • the gNB stores the expected traffic pattern on an RB basis.
  • the gNB checks from which RB this data belongs and, if the stored information is that no further data is expected, the gNB can release this UE immediately; otherwise, the gNB will avoid to do so and wait for the further DL data to arrive.
  • the gNB may even decide to move the UE in RRC CONNECTED state.
  • the gNB could release the UE only if all the RBs involved are associated to the “NoFurtherDataExpected” traffic pattern.
  • the messages used in RRC Reconfiguration and UEAssistancelnformation can be extended to include the same IE, so that the UE has the possibility to update the expected traffic information stored in the gNB.
  • the gNB discards the stored information when a timer, restarted every time the expected traffic pattern information is received, expires.
  • a MAC CE is used instead of an RRC IE.
  • the UE transmits this MAC CE following the same rules explained above.
  • the MAC CE may have the nonlimiting structure illustrated in Figure 4.
  • the UE provides information for “m” Radio Bearer with this variable-length MAC CE. For each RB one octet is used. In each octet the “S” bit indicates if the Radio Bearer is an SRB or DRB. RB Identity (5 bit) provide the RB identity, while the last 2 bits are used to provide the RAI similarly to what described above.
  • FIG. 5 illustrates the operation of a UE 500 and a network node 502 in accordance with one embodiment of the present disclosure.
  • the network node 502 is, in the preferred embodiments, a gNB or a network node that implements at least some of the functionality of a gNB (e.g., a gNB-DU or gNB-CU).
  • the UE 500 transmits, to the network node 502, information comprising RAI (step 504).
  • the network node 502 performs one or more actions responsive to the RAI (step 506).
  • the UE 500 transmits the information that indicates the release assistance indication to the network node 502 as part of UE Assistance Information or as part of a Release Preference IE (which may be part of the UE Assistance Information).
  • the information comparing the RAI is UE Assistance Information or a Release Preference IE comprising a preferredRRC-State field, where, during the SDT procedure, codepoints of the preferredRRC-State field are remapped to RAI values.
  • the RAI is then a value contained in the preferredRRC-State field that is remapped to a corresponding RAI value (e.g., ‘No subsequent DL and UL data transmission is expected’ or ‘a single subsequent DL transmission is expected’ or ‘there is no RAI information’).
  • the RAI is provided as a new version of the Release Preference IE as described above in Section 2.2.
  • the UE 500 transmits the information comprising the RAI (e.g., the UE Assistance Information, or at least the ReleasePreference IE, containing the RAI value) together with an RRC Resume Request (e.g., RRCResumeRequest or RRCResiimeRequestl) in a first UL transmission. Further details regarding embodiments in which the information comprising the RAI is provided in UE Assistance Information or at least the Release Preference IE are described in Sections 2.1 and 2.2 above and are equally applicable here.
  • the information comprising the RAI is provided in a RRC Resume Request message (e.g., via a repurposed spare bit in the RRC Resume Request message or via the ResumeCause field, where, e.g., one or more spare codepoints defined for the ResumeCause field are re-mapped to respective RAI values).
  • the information comprising the RAI is provided via a new RRC message that explicitly includes a new RAI IE. Further details regarding embodiments in which the information comprising the RAI is provided in a RRC Resume Request message are described in Section 2.3 above and are equally applicable here.
  • the information comprising the RAI is provided in a MAC CE such as, e.g., a BSR MAC CE. Further details regarding embodiments in which the information comprising the RAI is provided in a MAC CE are described in Section 2.4 above and are equally applicable here.
  • the information comprising the RAI comprises a Msg5 or RRC Setup Complete message.
  • the RAI comprises information that indicates an expected traffic pattern (e.g., ‘no further data expected’ or ‘single DL transmission expected’ or ‘further data expected on the UL or DL, etc.) for the UE 500 on a radio bearer basis (e.g., per DRB and/or per SRB).
  • the information that indicates the expected traffic pattern on a radio bearer basis is provided in a MAC CE. Further details regarding this embodiment are described above and are equally appliable here.
  • the action(s) performed by the network node 502 responsive to the RAI may be any desired action considering the received RAI.
  • the network node 502 may release the UE 500 if the RAI indicates that no further UL or DL data is expected.
  • the network node 502 may, for example, release the UE 502 after transmission of the single DL data transmission to the UE 500.
  • Other actions are described above and are equally appliable here.
  • Figure 6 shows an example of a communication system 600 in accordance with some embodiments.
  • the communication system 600 includes a telecommunication network 602 that includes an access network 604, such as a Radio Access Network (RAN), and a core network 606, which includes one or more core network nodes 608.
  • the access network 604 includes one or more access network nodes, such as network nodes 610A and 610B (one or more of which may be generally referred to as network nodes 610), or any other similar Third Generation Partnership Project (3GPP) access node or non-3GPP Access Point (AP).
  • network node 610A/610B can perform as network node 502 in Figure 5 and as described above.
  • the network nodes 610 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 612A, 612B, 612C, and 612D (one or more of which may be generally referred to as UEs 612) to the core network 606 over one or more wireless connections.
  • UEs 612 can perform as UE 500 in Figure 5 and as described above.
  • Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors.
  • the communication system 600 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 600 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 612 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 610 and other communication devices.
  • the network nodes 610 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 612 and/or with other network nodes or equipment in the telecommunication network 602 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 602.
  • the core network 606 connects the network nodes 610 to one or more hosts, such as host 616. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 606 includes one more core network nodes (e.g., core network node 608) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 608.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-Concealing Function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 616 may be under the ownership or control of a service provider other than an operator or provider of the access network 604 and/or the telecommunication network 602, and may be operated by the service provider or on behalf of the service provider.
  • the host 616 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 600 of Figure 6 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system 600 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the telecommunication network 602 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunication network 602 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 602. For example, the telecommunication network 602 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and/or massive Machine Type Communication (mMTC)/massive Internet of Things (loT) services to yet further UEs.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB enhanced Mobile Broadband
  • mMTC massive Machine Type Communication
  • LoT massive Internet of Things
  • the UEs 612 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 604 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 604.
  • a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multi-standard mode.
  • RAT Radio Access Technology
  • a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. be configured for Multi -Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).
  • MR-DC Multi -Radio Dual Connectivity
  • E-UTRAN Evolved UMTS Terrestrial RAN
  • EN-DC Dual Connectivity
  • a hub 614 communicates with the access network 604 to facilitate indirect communication between one or more UEs (e.g., UE 612C and/or 612D) and network nodes (e.g., network node 610B).
  • the hub 614 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 614 may be a broadband router enabling access to the core network 606 for the UEs.
  • the hub 614 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 614 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data.
  • the hub 614 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 614 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 614 then provides to the UE either directly, after performing local processing, and/or after adding additional local content.
  • the hub 614 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.
  • the hub 614 may have a constant/persistent or intermittent connection to the network node 610B.
  • the hub 614 may also allow for a different communication scheme and/or schedule between the hub 614 and UEs (e.g., UE 612C and/or 612D), and between the hub 614 and the core network 606.
  • the hub 614 is connected to the core network 606 and/or one or more UEs via a wired connection.
  • the hub 614 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 604 and/or to another UE over a direct connection.
  • M2M Machine-to-Machine
  • UEs may establish a wireless connection with the network nodes 610 while still connected via the hub 614 via a wired or wireless connection.
  • the hub 614 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 610B.
  • the hub 614 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 610B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • a UE refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • VoIP Voice over Internet Protocol
  • PDA Personal Digital Assistant
  • LOE Laptop Embedded Equipment
  • LME Laptop Mounted Equipment
  • CPE Customer Premise Equipment
  • UE 700 can perform as UE 500 in Figure 5 and as described above.
  • a UE may support Device-to-Device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehi cl e-to- Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle- to-Everything (V2X).
  • D2D Device-to-Device
  • DSRC Dedicated Short-Range Communication
  • V2V Vehi cl e-to- Vehicle
  • V2I Vehicle-to-Infrastructure
  • V2X Vehicle- to-Everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent
  • the UE 700 includes processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a power source 708, memory 710, a communication interface 712, and/or any other component, or any combination thereof.
  • processing circuitry 702 that is operatively coupled via a bus 704 to an input/output interface 706, a power source 708, memory 710, a communication interface 712, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in Figure 7. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.
  • the processing circuitry 702 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 710.
  • the processing circuitry 702 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 702 may include multiple Central Processing Units (CPUs).
  • the input/output interface 706 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 700.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • a sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof.
  • An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.
  • USB Universal Serial Bus
  • the power source 708 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used.
  • the power source 708 may further include power circuitry for delivering power from the power source 708 itself, and/or an external power source, to the various parts of the UE 700 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging the power source 708.
  • Power circuitry may perform any formatting, converting, or other modification to the power from the power source 708 to make the power suitable for the respective components of the UE 700 to which power is supplied.
  • the memory 710 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth.
  • the memory 710 includes one or more application programs 714, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 716.
  • the memory 710 may store, for use by the UE 700, any of a variety of various operating systems or combinations of operating systems.
  • the memory 710 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and/or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof.
  • RAID Redundant Array of Independent Disks
  • HD-DVD High Density Digital Versatile Disc
  • HDDS Holographic Digital Data Storage
  • DIMM Dual In-line Memory Module
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’
  • the memory 710 may allow the UE 700 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 710, which may be or comprise a device-readable storage medium.
  • the processing circuitry 702 may be configured to communicate with an access network or other network using the communication interface 712.
  • the communication interface 712 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 722.
  • the communication interface 712 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network).
  • Each transceiver may include a transmitter 718 and/or a receiver 720 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth).
  • the transmitter 718 and receiver 720 may be coupled to one or more antennas (e.g., the antenna 722) and may share circuit components, software, or firmware, or alternatively be implemented separately.
  • communication functions of the communication interface 712 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof.
  • GPS Global Positioning System
  • Communications may be implemented according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol/Internet Protocol (TCP/IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.
  • CDMA Code Division Multiplexing Access
  • WCDMA Wideband CDMA
  • GSM Global System for Mobile communications
  • LTE Long Term Evolution
  • NR Fifth Generation
  • UMTS Worldwide Interoperability for Mobile communications
  • WiMax Ethernet
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • SONET Synchronous Optical Networking
  • ATM Asynchronous Transfer Mode
  • QUIC Quick User Datagram Protocol Internet Connection
  • HTTP Hypertext Transfer Protocol
  • a UE may provide an output of data captured by its sensors, through its communication interface 712, or via a wireless connection to a network node.
  • Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE.
  • the output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).
  • a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection.
  • the states of the actuator, the motor, or the switch may change.
  • the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.
  • a UE when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare.
  • Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or itemtracking device, a sensor for
  • a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node.
  • the UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device.
  • the UE may implement the 3 GPP NB-IoT standard.
  • a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.
  • any number of UEs may be used together with respect to a single use case.
  • a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone.
  • the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed.
  • the first and/or the second UE can also include more than one of the functionalities described above.
  • a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.
  • FIG 8 shows a network node 800 in accordance with some embodiments.
  • network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment in a telecommunication network.
  • network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).
  • APs e.g., radio APs
  • BSs Base Stations
  • eNBs evolved Node Bs
  • gNBs NR Node Bs
  • network node 800 can perform as network node 502 in Figure 5 and as described above.
  • BSs may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto BSs, pico BSs, micro BSs, or macro BSs.
  • a BS may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio BS such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio.
  • RRUs Remote Radio Heads
  • Parts of a distributed radio BS may also be referred to as nodes in a Distributed Antenna System (DAS).
  • DAS Distributed Antenna System
  • network nodes include multiple Transmission Point (multi-TRP) 5G access nodes, Multi -Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).
  • MSR Transmission Point
  • MSR Multi -Standard Radio
  • RNCs Radio Network Controllers
  • BSCs Base Transceiver Stations
  • MCEs Multi-Cell/Multicast Coordination Entities
  • OFM Operation and Maintenance
  • OSS Operations Support System
  • SON Self-Organizing Network
  • the network node 800 includes processing circuitry 802, memory 804, a communication interface 806, and a power source 808.
  • the network node 800 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components.
  • the network node 800 comprises multiple separate components (e.g., BTS and BSC components)
  • one or more of the separate components may be shared among several network nodes.
  • a single RNC may control multiple Node Bs.
  • each unique Node B and RNC pair may in some instances be considered a single separate network node.
  • the network node 800 may be configured to support multiple RATs.
  • the network node 800 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 800, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within the network node 800.
  • the processing circuitry 802 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other network node 800 components, such as the memory 804, to provide network node 800 functionality.
  • the processing circuitry 802 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 802 includes one or more of Radio Frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814. In some embodiments, the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on the same chip or set of chips, boards, or units.
  • SOC System on a Chip
  • the processing circuitry 802 includes one or more of Radio Frequency (RF) transceiver circuitry 812 and baseband processing circuitry 814.
  • RF transceiver circuitry 812 and the baseband processing circuitry 814 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the
  • the memory 804 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable, and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 802.
  • volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)
  • the memory 804 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 802 and utilized by the network node 800.
  • the memory 804 may be used to store any calculations made by the processing circuitry 802 and/or any data received via the communication interface 806.
  • the processing circuitry 802 and the memory 804 are integrated.
  • the communication interface 806 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 806 comprises port(s)/terminal(s) 816 to send and receive data, for example to and from a network over a wired connection.
  • the communication interface 806 also includes radio front-end circuitry 818 that may be coupled to, or in certain embodiments a part of, the antenna 810.
  • the radio front-end circuitry 818 comprises filters 820 and amplifiers 822.
  • the radio front-end circuitry 818 may be connected to the antenna 810 and the processing circuitry 802.
  • the radio front-end circuitry 818 may be configured to condition signals communicated between the antenna 810 and the processing circuitry 802.
  • the radio front-end circuitry 818 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection.
  • the radio front-end circuitry 818 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 820 and/or the amplifiers 822.
  • the radio signal may then be transmitted via the antenna 810.
  • the antenna 810 may collect radio signals which are then converted into digital data by the radio front-end circuitry 818.
  • the digital data may be passed to the processing circuitry 802.
  • the communication interface 806 may comprise different components and/or different combinations of components.
  • the network node 800 does not include separate radio front-end circuitry 818; instead, the processing circuitry 802 includes radio front-end circuitry and is connected to the antenna 810. Similarly, in some embodiments, all or some of the RF transceiver circuitry 812 is part of the communication interface 806. In still other embodiments, the communication interface 806 includes the one or more ports or terminals 816, the radio frontend circuitry 818, and the RF transceiver circuitry 812 as part of a radio unit (not shown), and the communication interface 806 communicates with the baseband processing circuitry 814, which is part of a digital unit (not shown).
  • the antenna 810 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals.
  • the antenna 810 may be coupled to the radio front-end circuitry 818 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly.
  • the antenna 810 is separate from the network node 800 and connectable to the network node 800 through an interface or port.
  • the antenna 810, the communication interface 806, and/or the processing circuitry 802 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node 800. Any information, data, and/or signals may be received from a UE, another network node, and/or any other network equipment. Similarly, the antenna 810, the communication interface 806, and/or the processing circuitry 802 may be configured to perform any transmitting operations described herein as being performed by the network node 800. Any information, data, and/or signals may be transmitted to a UE, another network node, and/or any other network equipment.
  • the power source 808 provides power to the various components of the network node 800 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component).
  • the power source 808 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 800 with power for performing the functionality described herein.
  • the network node 800 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 808.
  • the power source 808 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.
  • Embodiments of the network node 800 may include additional components beyond those shown in Figure 8 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein.
  • the network node 800 may include user interface equipment to allow input of information into the network node 800 and to allow output of information from the network node 800. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 800.
  • FIG 9 is a block diagram of a host 900, which may be an embodiment of the host 616 of Figure 6, in accordance with various aspects described herein.
  • the host 900 may be or comprise various combinations of hardware and/or software including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 900 may provide one or more services to one or more UEs.
  • the host 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a network interface 908, a power source 910, and memory 912.
  • processing circuitry 902 that is operatively coupled via a bus 904 to an input/output interface 906, a network interface 908, a power source 910, and memory 912.
  • Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 7 and 8, such that the descriptions thereof are generally applicable to the corresponding components of the host 900.
  • the memory 912 may include one or more computer programs including one or more host application programs 914 and data 916, which may include user data, e.g. data generated by a UE for the host 900 or data generated by the host 900 for a UE.
  • Embodiments of the host 900 may utilize only a subset or all of the components shown.
  • the host application programs 914 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 900 may select and/or indicate a different host for Over-The-Top (OTT) services for a UE.
  • the host application programs 914 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (DASH or MPEG-DASH), etc.
  • Applications 1002 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.
  • Hardware 1004 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth.
  • Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1006 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 1008 A and 1008B (one or more of which may be generally referred to as VMs 1008), and/or perform any of the functions, features, and/or benefits described in relation with some embodiments described herein.
  • the virtualization layer 1006 may present a virtual operating platform that appears like networking hardware to the VMs 1008.
  • the VMs 1008 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 1006. Different embodiments of the instance of a virtual appliance 1002 may be implemented on one or more of the VMs 1008, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.
  • NFV Network Function Virtualization
  • a VM 1008 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 1008, and that part of the hardware 1004 that executes that VM be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs 1008, forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 1008 on top of the hardware 1004 and corresponds to the application 1002.
  • the hardware 1004 may be implemented in a standalone network node with generic or specific components.
  • the hardware 1004 may implement some functions via virtualization.
  • the hardware 1004 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1010, which, among others, oversees lifecycle management of the applications 1002.
  • the hardware 1004 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a BS.
  • some signaling can be provided with the use of a control system 1012 which may alternatively be used for communication between hardware nodes and radio units.
  • Figure 11 shows a communication diagram of a host 1102 communicating via a network node 1104 with a UE 1106 over a partially wireless connection in accordance with some embodiments.
  • embodiments of the host 1102 include hardware, such as a communication interface, processing circuitry, and memory.
  • the host 1102 also includes software, which is stored in or is accessible by the host 1102 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 1106 connecting via an OTT connection 1150 extending between the UE 1106 and the host 1102.
  • a host application may provide user data which is transmitted using the OTT connection 1150.
  • the network node 1104 includes hardware enabling it to communicate with the host 1102 and the UE 1106 via a connection 1160.
  • the connection 1160 may be direct or pass through a core network (like the core network 606 of Figure 6) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • an intermediate network may be a backbone network or the Internet.
  • the UE 1106 includes hardware and software, which is stored in or accessible by the UE 1106 and executable by the UE’s processing circuitry.
  • the software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1106 with the support of the host 1102.
  • a client application such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via the UE 1106 with the support of the host 1102.
  • an executing host application may communicate with the executing client application via the OTT connection 1150 terminating at the UE 1106 and the host 1102.
  • the UE's client application may receive request data from the host's host application and provide user data in response to the request data.
  • the OTT connection 1150 may transfer both the request data and the user data.
  • the UE 1106 executes a client application which provides user data to the host 1102.
  • the user data may be provided in reaction or response to the data received from the host 1102.
  • the UE 1106 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 1106. Regardless of the specific manner in which the user data was provided, the UE 1106 initiates, in step 1118, transmission of the user data towards the host 1102 via the network node 1104.
  • the network node 1104 receives user data from the UE 1106 and initiates transmission of the received user data towards the host 1102.
  • the host 1102 receives the user data carried in the transmission initiated by the UE 1106.
  • One or more of the various embodiments improve the performance of OTT services provided to the UE 1106 using the OTT connection 1150, in which the wireless connection 1170 forms the last segment. More precisely, the teachings of these embodiments may improve power consumption and thereby provide benefits such as, e.g., extended battery lifetime.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 1150 may be implemented in software and hardware of the host 1102 and/or the UE 1106.
  • sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1150 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 1150 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not directly alter the operation of the network node 1104. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency, and the like by the host 1102.
  • the measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1150 while monitoring propagation times, errors, etc.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • processing circuitry may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.
  • components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components.
  • a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device- readable storage medium, such as in a hardwired manner.
  • the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and/or by end users and a wireless network generally.
  • Embodiment 1 A method performed by a user equipment, UE, (500), the method comprising: during a Small Data Transmission, SDT, procedure, transmitting (504), to a network node (502), information comprising a release assistance indication, RAI.
  • Embodiment 2 The method of embodiment 1, wherein transmitting (504) the information comprising the RAI comprises transmitting (504) a Radio Resource Control, RRC, message comprising the RAI.
  • RRC Radio Resource Control
  • Embodiment 3 The method of embodiment 1 or 2, wherein transmitting (504) the information comprising the RAI comprises transmitting (504) UE Assistance Information comprising the RAI.
  • Embodiment 4 The method of embodiment 3, wherein transmitting (504) UE Assistance Information comprising the RAI comprises transmitting (504) UE Assistance Information comprising the RAI together with an RRC Resume Request message using either a same uplink assignment or a separate uplink assignment.
  • Embodiment 5 The method of embodiment 3 or 4, wherein the RAI is indicated by a preferred RRC state field comprised in the UE Assistance Information (e.g., in a Release Preference IE within the UE Assistance Information).
  • the RAI is indicated by a preferred RRC state field comprised in the UE Assistance Information (e.g., in a Release Preference IE within the UE Assistance Information).
  • Embodiment 6 The method of embodiment 1 or 2, wherein transmitting (504) the information comprising the RAI comprises transmitting (504) an RRC message comprising a Release Preference IE, the Release Preference IE comprising the RAI.
  • Embodiment 7 The method of embodiment 6, wherein transmitting (504) RRC message comprising the RAI comprises transmitting (504) the RRC message comprising the RAI together with an RRC Resume Request message using either a same uplink assignment or a separate uplink assignment.
  • Embodiment 8 The method of embodiment 6 or 7, wherein the Release Preference IE comprises a preferred RRC state field that comprises the RAI.
  • Embodiment 9 The method of embodiment 5 or 8, wherein a plurality of codepoints for the preferred RRC state field are re-mapped to a respective plurality of RAI values when the UE Assistance Information is transmitted during an SDT procedure, and the RRC state field is set to one of the plurality of codepoints for the preferred RRC state field that is re-mapped to a desired one of the plurality of RAI values.
  • Embodiment 10 The method of embodiment 1 or 2, wherein transmitting (504) the information comprising the RAI comprises transmitting (504) information that comprises a Release Preference IE, the Release Preference IE comprising a new field that comprises the RAI.
  • Embodiment 11 The method of embodiment 1, wherein transmitting (504) the information comprising the RAI comprises transmitting (504) a Radio Resource Control, RRC, Resume Request message comprising the RAI.
  • Embodiment 12 The method of embodiment 11, wherein the RAI is indicated via a repurposed spare bit in the RRC Resume Request message.
  • Embodiment 13 The method of embodiment 11, wherein the RAI is indicated via a Resume Cause field of the RRC Resume Request message.
  • Embodiment 14 The method of embodiment 13, wherein one or more defined values for the Resume Cause field are re-mapped to one or more RAI values when the RRC Resume Request message is transmitted during an SDT procedure.
  • Embodiment 15 The method of embodiment 1, wherein transmitting (504) the information comprising the RAI comprises transmitting (504) Medium Access Control, MAC, Control Element, CE, comprising the RAI.
  • Embodiment 16 The method of embodiment 15, wherein the MAC CE is a Buffer Status Report, BSR, MAC CE.
  • Embodiment 17 The method of embodiment 16, wherein different subsets of a plurality of indices defined for the BSR MAC CE are mapped to different RAI values, and the BSR MAC CE comprises one of the plurality of indices that is mapped to a desired one of the different RAI values.
  • Embodiment 18 The method of embodiment 16 or 17, wherein the BSR MAC CE is interpreted using a first table when sent during an SDT procedure and otherwise interpreted using a second table that is different than the first table.
  • Embodiment 19 The method of any of embodiments 15 to 18, wherein the BSR MAC CE comprise a Logical Channel Identifier (LCID) or Enhanced LCID (eLCID) that indicates that the BSR MAC CE comprises RAI.
  • LCID Logical Channel Identifier
  • eLCID Enhanced LCID
  • Embodiment 20 The method of any of embodiments 15 to 18 wherein the BSR MAC CE comprise a Logical Channel Identifier (LCID) or Enhanced LCID (eLCID) that indicates the RAI.
  • LCID Logical Channel Identifier
  • eLCID Enhanced LCID
  • Embodiment 21 The method of embodiment 1, wherein transmitting (504) the information comprising the RAI comprises transmitting (504) Msg5 or RRC Setup Complete message comprising the RAI.
  • Embodiment 22 The method of embodiment 21, wherein the RAI comprises information that indicates an expected traffic pattern for the UE (500) on a per radio bearer basis.
  • Embodiment 23 The method of any of embodiments 1 to 22 wherein transmitting (504) the information comprising the RAI comprises transmitting (504) the information comprising the RAI to the network node (502) via a New Radio, NR, Uu interface.
  • Embodiment 24 The method of any of embodiments 1 to 22, wherein the UE (500) is a New Radio, NR, UE, and the network node (502) is a next-generation Node B, gNB.
  • the UE (500) is a New Radio, NR, UE
  • the network node (502) is a next-generation Node B, gNB.
  • Embodiment 25 The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host via the transmission to the network node.
  • Embodiment 26 A method performed by a network node (502), the method comprising: during a Small Data Transmission, SDT, procedure, receiving (504), from a User Equipment, UE, (500), information comprising a release assistance indication, RAI.
  • Embodiment 27 The method of embodiment 26 wherein receiving (504) the information comprising the RAI comprises receiving (504) a Radio Resource Control, RRC, message comprising the RAI.
  • RRC Radio Resource Control
  • Embodiment 28 The method of embodiment 26 or 27, wherein receiving (504) the information comprising the RAI comprises receiving (504) UE Assistance Information comprising the RAI.
  • Embodiment 29 The method of embodiment 28, wherein receiving (504) UE Assistance Information comprising the RAI comprises receiving (504) UE Assistance Information comprising the RAI together with an RRC Resume Request message using either a same uplink assignment or a separate uplink assignment.
  • Embodiment 30 The method of embodiment 28 or 29, wherein the RAI is indicated by a preferred RRC state field comprised in the UE Assistance Information (e.g., in a Release Preference IE within the UE Assistance Information).
  • the RAI is indicated by a preferred RRC state field comprised in the UE Assistance Information (e.g., in a Release Preference IE within the UE Assistance Information).
  • Embodiment 31 The method of embodiment 26 or 27, wherein receiving (504) the information comprising the RAI comprises receiving (504) an RRC message comprising a Release Preference IE, the Release Preference IE comprising the RAI.
  • Embodiment 32 The method of embodiment 31, wherein receiving (504) RRC message comprising the RAI comprises receiving (504) the RRC message comprising the RAI together with an RRC Resume Request message using either a same uplink assignment or a separate uplink assignment.
  • Embodiment 33 The method of embodiment 31 or 32, wherein the Release Preference IE comprises a preferred RRC state field that comprises the RAI.
  • Embodiment 34 The method of embodiment 30 or 33, wherein a plurality of codepoints for the preferred RRC state field are re-mapped to a respective plurality of RAI values when the UE Assistance Information is received during an SDT procedure, and the RRC state field is set to one of the plurality of codepoints for the preferred RRC state field that is re-mapped to a desired one of the plurality of RAI values.
  • Embodiment 35 The method of embodiment 26 or 27, wherein receiving (504) the information comprising the RAI comprises receiving (504) information that comprises a Release Preference IE, the Release Preference IE comprising a new field that comprises the RAI.
  • Embodiment 36 The method of embodiment 26, wherein receiving (504) the information comprising the RAI comprises receiving (504) a Radio Resource Control, RRC, Resume Request message comprising the RAI.
  • Embodiment 37 The method of embodiment 36, wherein the RAI is indicated via a repurposed spare bit in the RRC Resume Request message.
  • Embodiment 38 The method of embodiment 36, wherein the RAI is indicated via a Resume Cause field of the RRC Resume Request message.
  • Embodiment 39 The method of embodiment 38, wherein one or more defined values for the Resume Cause field are re-mapped to one or more RAI values when the RRC Resume Request message is transmitted during an SDT procedure.
  • Embodiment 40 The method of embodiment 26, wherein receiving (504) the information comprising the RAI comprises receiving (504) Medium Access Control, MAC, Control Element, CE, comprising the RAI.
  • Embodiment 41 The method of embodiment 40, wherein the MAC CE is a Buffer Status Report, BSR, MAC CE.
  • Embodiment 42 The method of embodiment 41, wherein different subsets of a plurality of indices defined for the BSR MAC CE are mapped to different RAI values, and the BSR MAC CE comprises one of the plurality of indices that is mapped to a desired one of the different RAI values.
  • Embodiment 43 The method of embodiment 41 or 42, wherein the BSR MAC CE is interpreted using a first table when sent during an SDT procedure and otherwise interpreted using a second table that is different than the first table.
  • Embodiment 44 The method of any of embodiments 40 to 43, wherein the BSR MAC CE comprise a Logical Channel Identifier (LCID) or Enhanced LCID (eLCID) that indicates that the BSR MAC CE comprises RAI.
  • LCID Logical Channel Identifier
  • eLCID Enhanced LCID
  • Embodiment 45 The method of any of embodiments 40 to 43, wherein the BSR MAC CE comprise a Logical Channel Identifier (LCID) or Enhanced LCID (eLCID) that indicates the RAT
  • LCID Logical Channel Identifier
  • eLCID Enhanced LCID
  • Embodiment 46 The method of embodiment 26, wherein receiving (504) the information comprising the RAI comprises receiving (504) Msg5 or RRC Setup Complete message comprising the RAI.
  • Embodiment 47 The method of embodiment 46, wherein the RAI comprises information that indicates an expected traffic pattern for the UE (500) on a per radio bearer basis.
  • Embodiment 48 The method of any of embodiments 26 to 47 further comprising performing (506) one or more actions based on the RAI.
  • Embodiment 49 The method of any of embodiments 26 to 48, wherein receiving (504) the information comprising the RAI comprises receiving (504) the information comprising the RAI from the UE (500) via a New Radio, NR, Uu interface.
  • Embodiment 50 The method of any of embodiments 26 to 48, wherein the UE (500) is a New Radio, NR, UE, and the network node (502) is a next-generation Node B, gNB.
  • the UE (500) is a New Radio, NR, UE
  • the network node (502) is a next-generation Node B, gNB.
  • Embodiment 51 The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.
  • Embodiment 52 A user equipment comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 53 A network node comprising: processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.
  • Embodiment 55 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to receive the user data from the host.
  • OTT over-the-top
  • Embodiment 56 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.
  • Embodiment 57 The host of the previous two embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 58 A method implemented by a host operating in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the UE performs any of the operations of any of the Group A embodiments to receive the user data from the host.
  • UE user equipment
  • Embodiment 59 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 60 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Embodiment 61 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • OTT over-the-top
  • Embodiment 62 The host of the previous embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.
  • Embodiment 63 The host of the previous two embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 64 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A embodiments to transmit the user data to the host.
  • UE user equipment
  • Embodiment 65 The method of the previous embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.
  • Embodiment 66 The method of the previous embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.
  • Embodiment 67 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • OTT over-the-top
  • Embodiment 68 The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host
  • Embodiment 69 A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • UE user equipment
  • Embodiment 70 The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.
  • Embodiment 71 The method of any of the previous two embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 72 A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.
  • a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the
  • Embodiment 73 The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.
  • Embodiment 74 A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.
  • OTT over-the-top
  • Embodiment 75 The host of the previous two embodiments, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.
  • Embodiment 76 The host of the any of the previous two embodiments, wherein the initiating receipt of the user data comprises requesting the user data.
  • Embodiment 77 A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.
  • Embodiment 78 The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

Landscapes

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

Abstract

Sont divulgués ici des procédés, des appareils, des systèmes et des supports lisibles par ordinateur pour un équipement d'utilisateur (UE) et des nœuds de réseau qui permettent des indications d'aide à la libération (RAI) dans des transmissions de petites données (SDT). Dans certains modes de réalisation, un procédé est mis en œuvre par un UE. Le procédé comprend, pendant une procédure SDT, la transmission d'informations comprenant une RAI à un nœud de réseau. Certains modes de réalisation fournissent un ou plusieurs des avantages techniques suivants : l'objet divulgué fournit un support pour une RAI dans une New Radio (NR) sans lequel la performance de SDT est médiocre, ou présente même des performances inférieures dans certains scénarios par rapport à un fonctionnement patrimonial (c'est-à-dire, sans SDT). L'invention concerne également un procédé correspondant mis en œuvre par un nœud de réseau.
PCT/SE2023/050123 2022-02-14 2023-02-14 Indication d'aide à la libération pour une transmission de petites données de new radio (nr sdt) WO2023153999A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263309982P 2022-02-14 2022-02-14
US63/309,982 2022-02-14

Publications (1)

Publication Number Publication Date
WO2023153999A1 true WO2023153999A1 (fr) 2023-08-17

Family

ID=85462176

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2023/050123 WO2023153999A1 (fr) 2022-02-14 2023-02-14 Indication d'aide à la libération pour une transmission de petites données de new radio (nr sdt)

Country Status (1)

Country Link
WO (1) WO2023153999A1 (fr)

Non-Patent Citations (9)

* Cited by examiner, † Cited by third party
Title
3GPP TECHNICAL SPECIFICATION (TS) 36.321
3GPP TS 36.321
3GPP TS 38.300
3GPP TS 38.321
3GPP TS 38.331
EMAIL DISCUSSION RAPPORTEUR (ZTE CORPORATION): "CP open issues list for SDT (email: [POST116bis-e][511])", vol. RAN WG2, no. e-Meeting, 28 January 2022 (2022-01-28), XP052122631, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_116bis-e/Inbox/R2-2202022.zip R2-2202022_SDT_OpenIssueList_v08_rapp(final).docx> [retrieved on 20220128] *
HUAWEI ET AL: "Control Plane Common aspects for SDT", vol. RAN WG2, no. E-meeting; 20220117 - 20220125, 11 January 2022 (2022-01-11), XP052093942, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_116bis-e/Docs/R2-2200811.zip R2-2200811_control plane common aspects for SDT.docx> [retrieved on 20220111] *
HUAWEI: "(TP to TS 38.473 BL CR) Support of CG based SDT", vol. RAN WG3, no. E-meeting; 20211101 - 20211111, 22 October 2021 (2021-10-22), XP052067998, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_114-e/Docs/R3-215002.zip R3-215002 (TP to TS 38.473 BL CR)Support of CG based SDT.doc> [retrieved on 20211022] *
HUAWEI: "(TPs to RA-SDT BL CRs of TS 38.300, 38.420, 38.470) RACH based SDT without anchor relocation", vol. RAN WG3, no. Electronic meeting; 20220221 - 20220303, 11 February 2022 (2022-02-11), XP052107959, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG3_Iu/TSGR3_115-e/Docs/R3-222170.zip R3-222170 (TPs to RA-SDT BL CRs of TS 38.300, 38.420, 38470) RACH SDT without anchor relocation.docx> [retrieved on 20220211] *

Similar Documents

Publication Publication Date Title
WO2023105073A1 (fr) Commande d&#39;admission inter-nœuds de réseau pour un ue relais de liaison latérale
WO2023014254A1 (fr) Rapport de libération de réseau initiée par un ue
WO2023153999A1 (fr) Indication d&#39;aide à la libération pour une transmission de petites données de new radio (nr sdt)
WO2024027838A9 (fr) Procédé et appareil pour arrêter un rapport de localisation
WO2024027839A9 (fr) Procédé et appareil de configuration de type de rapport d&#39;emplacement
WO2024032571A1 (fr) Procédé et appareil aux fins d&#39;une sélection de fonction de plan d&#39;utilisateur
WO2023185737A1 (fr) Procédé et appareil permettant d&#39;effectuer une authentification/autorisation secondaire pour un dispositif terminal dans un réseau de communication
WO2023143314A1 (fr) Procédé et appareil de configuration de qos dans un réseau de communication
US20240292478A1 (en) Handling of secondary node (sn) configurations during multi-rat dual connectivity (mr-dc) release
WO2023204752A1 (fr) Radiomessagerie pour commande de réseau mt-sdt et signalisation inter-nœuds
WO2024019652A1 (fr) Stockage de configurations qoe et rvqoe dans rrc_idle
WO2024015000A1 (fr) Transmission de petites données à terminaison mobile
WO2023239280A1 (fr) Sélection de réponse ul pour transmission de petites données à terminaison mobile
WO2024068354A1 (fr) Extension de paramètres d&#39;interdiction
WO2024096789A1 (fr) Accès aléatoire pendant cg-sdt
WO2023214919A1 (fr) Procédés pour améliorer des capacités d&#39;économie d&#39;énergie pour un ue après la réception de données dl dans une mt-sdt
WO2024172748A1 (fr) Génération de pdu mac pour de multiples occasions de transmission d&#39;autorisations configurées
WO2023218383A1 (fr) Systèmes et procédés pour permettre une configuration par service pour mt-sdt
WO2024172726A1 (fr) Systèmes et procédés de signalisation de paramètres de différenciation de radiomessagerie
WO2023136759A1 (fr) Envoi et réception d&#39;un rapport
WO2023101580A1 (fr) Systèmes et procédés de taille de tampon assistée par équipement utilisateur en connectivité multiple
WO2023249529A1 (fr) Gestion de problèmes de coexistence dans un dispositif
WO2023203246A1 (fr) Transmission d&#39;informations d&#39;interdiction de cellule à un ue distant par l&#39;intermédiaire d&#39;un ue relais
WO2024099949A1 (fr) Inclusion d&#39;identité de pcell (cellule primaire) dans un rapport ra tout en effectuant une procédure ra vers une cellule scg
WO2024028840A1 (fr) Rapport d&#39;informations d&#39;assistance d&#39;équipement utilisateur pour faciliter des économies d&#39;énergie de réseau d&#39;accès radio

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

Country of ref document: EP

Kind code of ref document: A1