WO2020056595A1 - Transmission de petites données en liaison descendante - Google Patents

Transmission de petites données en liaison descendante Download PDF

Info

Publication number
WO2020056595A1
WO2020056595A1 PCT/CN2018/106285 CN2018106285W WO2020056595A1 WO 2020056595 A1 WO2020056595 A1 WO 2020056595A1 CN 2018106285 W CN2018106285 W CN 2018106285W WO 2020056595 A1 WO2020056595 A1 WO 2020056595A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
paging
access node
response
transport block
Prior art date
Application number
PCT/CN2018/106285
Other languages
English (en)
Inventor
Srinivasan Selvaganapathy
Jussi-Pekka Koskinen
Haitao Li
Rapeepat Ratasuk
Original Assignee
Nokia Shanghai Bell Co., Ltd.
Nokia Solutions And Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co., Ltd., Nokia Solutions And Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co., Ltd.
Priority to PCT/CN2018/106285 priority Critical patent/WO2020056595A1/fr
Priority to CN201880097807.8A priority patent/CN112740778B/zh
Publication of WO2020056595A1 publication Critical patent/WO2020056595A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
    • H04W68/02—Arrangements for increasing efficiency of notification or paging channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal

Definitions

  • Various example embodiments relates to wireless communications.
  • Mobility Manage-ment Entity MME
  • RRC Radio Resource Control
  • Figure 1 illustrates an exemplified wireless communication system
  • FIGS 2, 3, 4A, 4B, 5, 6 and 7 illustrate exemplary processes accord-ing to embodiments.
  • Figure 8 illustrates an apparatus according to embodiments.
  • Embodiments and examples described herein may be implemented in any communications system comprising wireless connection (s) .
  • a radio access ar-chitecture based on long term evolution advanced (LTE Advanced, LTE-A) or new radio (NR, 5G) without restricting the embodiments to such an architecture, however.
  • LTE Advanced, LTE-A long term evolution advanced
  • NR, 5G new radio
  • the embodiments may also be applied to other kinds of communications networks having suitable means by adjusting parameters and procedures appropriately.
  • UMTS universal mobile telecommunications system
  • E-UTRAN long term evolution
  • LTE long term evolution
  • WiMAX wireless local area network
  • PCS personal communications services
  • WCDMA wideband code division multiple access
  • UWB ultra-wideband
  • IMS Internet Protocol multimedia subsystems
  • Figure 1 depicts examples of simplified system architectures only showing some elements and functional entities, all being logical units, whose im-plementation may differ from what is shown.
  • the connections shown in Figure 1 are logical connections; the actual physical connections may be different. It is ap-parent to a person skilled in the art that the system typically comprises also other functions and structures than those shown in Figure 1.
  • Figure 1 shows a part of an exemplifying radio access network.
  • Figure 1 shows user devices 100 and 102 configured to be in a wire-less connection on one or more communication channels in a cell with an access node (such as (e/g) NodeB) 104 providing the cell.
  • the physical link from a user device to a (e/g) NodeB is called uplink or reverse link and the physical link from the (e/g) NodeB to the user device is called downlink or forward link.
  • (e/g) NodeBs or their functionalities may be implemented by using any node, host, server or access point etc. entity suitable for such a usage.
  • a communications system typically comprises more than one (e/g) NodeB in which case the (e/g) NodeBs may also be configured to communi-cate with one another over links, wired or wireless, designed for the purpose. These links may be used for signalling purposes.
  • the (e/g) NodeB is a computing device configured to control the radio resources of communication system it is coupled to.
  • the NodeB may also be referred to as a base station, an access point or any other type of interfacing device.
  • the (e/g) NodeB includes or is coupled to transceivers. From the transceivers of the (e/g) NodeB, a connection is provided to an antenna unit that establishes bi-directional radio links to user devices.
  • the antenna unit may comprise a plurality of antennas or antenna elements.
  • the (e/g) NodeB is further connected to core network 110 (CN or next generation core NGC) .
  • core network 110 CN or next generation core NGC
  • S-GW serving gateway
  • P-GW packet data network gateway
  • MME mobile management entity
  • the user device also called UE, user equipment, user terminal, termi-nal device, etc.
  • UE user equipment
  • user terminal user terminal
  • termi-nal device etc.
  • a relay node An example of such a relay node is a layer 2 relay or a layer 3 relay (self-backhauling relay) towards the base station.
  • the user device typically refers to a portable computing device that in-cludes wireless mobile communication devices operating with or without a sub-scriber identification module (SIM) , including, but not limited to, the following types of devices: a mobile station (mobile phone) , smartphone, personal digital assistant (PDA) , handset, device using a wireless modem (alarm or measurement device, etc. ) , laptop and/or touch screen computer, tablet, game console, note-book, and multimedia device.
  • SIM sub-scriber identification module
  • a mobile station mobile phone
  • smartphone personal digital assistant
  • handset device using a wireless modem (alarm or measurement device, etc. )
  • laptop and/or touch screen computer tablet, game console, note-book, and multimedia device.
  • a user device may also be a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • a user device may also be a device having capability to operate in Internet of Things (IoT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.
  • the user device may be a NarrowBand Internet of Things (NB-IoT) device or en- hanced Machine-Type Communication (eMTC) device.
  • NB-IoT NarrowBand Internet of Things
  • eMTC en- hanced Machine-Type Communication
  • the user device (or in some embodiments a layer 3 relay node) is configured to perform one or more of user equipment functionalities.
  • the user device may also be called a subscriber unit, mobile station, remote terminal, access terminal, user terminal or user equipment (UE) just to mention but a few names or apparatuses.
  • CPS cyber-physical system
  • ICT devices sensors, actuators, processors microcontrollers, etc.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physi-cal systems include mobile robotics and electronics transported by humans or animals.
  • 5G enables using multiple input -multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept) , including macro sites operating in co-operation with smaller stations and employ-ing a variety of radio technologies depending on service needs, use cases and/or spectrum available.
  • MIMO multiple input -multiple output
  • 5G mobile communications supports a wide range of use cas-es and related applications including video streaming, augmented reality, differ-ent ways of data sharing and various forms of machine type applications such as (massive) machine-type communications (mMTC) , including vehicular safety, different sensors and real-time control.
  • mMTC massive machine-type communications
  • 5G is expected to have multiple radio in-terfaces, namely below 6GHz, cmWave and mmWave, and also being integrable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where mac-ro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE.
  • 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz -cmWave, below 6GHz -cmWave - mmWave) .
  • inter-RAT operability such as LTE-5G
  • inter-RI operability inter-radio interface operability, such as below 6GHz -cmWave, below 6GHz -cmWave - mmWave
  • One of the concepts considered to be used in 5G networks is network slicing in which multiple
  • the current architecture in LTE networks is fully distributed in the ra-dio and fully centralized in the core network.
  • the low latency applications and services in 5G require to bring the content close to the radio which leads to local break out and multi-access edge computing (MEC) .
  • MEC multi-access edge computing
  • 5G enables analytics and knowledge generation to occur at the source of the data. This approach requires leveraging resources that may not be continuously connected to a network such as laptops, smartphones, tablets and sensors.
  • MEC provides a distributed compu-ting environment for application and service hosting. It also has the ability to store and process content in close proximity to cellular subscribers for faster re-sponse time.
  • Edge computing covers a wide range of technologies such as wire-less sensor networks, mobile data acquisition, mobile signature analysis, coopera-tive distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (massive connectivity and/or latency critical) , critical communications (autonomous vehicles, traffic safety, real-time analytics, time-critical control, healthcare applications) .
  • technologies such as wire-less sensor networks, mobile data acquisition, mobile signature analysis, coopera-tive distributed peer-to-peer ad hoc networking and processing also classifiable as local cloud/fog computing and grid/mesh computing, dew computing, mobile edge computing, cloudlet, distributed data storage and retrieval, autonomic self-healing networks, remote cloud services, augmented and virtual reality, data caching, Internet of Things (mas
  • the communication system is also able to communicate with other networks, such as a public switched telephone network or the Internet 112, or utilize services provided by them.
  • the communication network may also be able to support the usage of cloud services, for example at least part of core network operations may be carried out as a cloud service (this is depicted in Figure 1 by “cloud” 114) .
  • the communication system may also comprise a central control en-tity, or a like, providing facilities for networks of different operators to cooperate for example in spectrum sharing.
  • Edge cloud may be brought into radio access network (RAN) by utiliz-ing network function virtualization (NVF) and software defined networking (SDN) .
  • RAN radio access network
  • NVF network function virtualization
  • SDN software defined networking
  • Using edge cloud may mean access node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head or base station comprising radio parts. It is also possible that node opera-tions will be distributed among a plurality of servers, nodes or hosts.
  • Application of cloudRAN architecture enables RAN real time functions being carried out at the RAN side (in a distributed unit, DU 104) and non-real time functions being carried out in a centralized manner (in a centralized unit, CU 108) .
  • 5G may also utilize satellite communication to enhance or complement the coverage of 5G service, for example by providing backhauling.
  • Possible use cases are providing service continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or for passengers on board of vehicles, or ensuring service availability for critical communications, and future rail-way/maritime/aeronautical communications.
  • Satellite communication may uti-lize geostationary earth orbit (GEO) satellite systems, but also low earth orbit (LEO) satellite systems, in particular mega-constellations (systems in which hun-dreds of (nano) satellites are deployed) .
  • Each satellite 106 in the mega-constellation may cover several satellite-enabled network entities that create on-ground cells.
  • the on-ground cells may be created through an on-ground relay node 104 or by a gNB located on-ground or in a satellite.
  • the depicted system is only an example of a part of a radio access system and in practice, the system may comprise a plurality of (e/g) NodeBs, the user device may have an access to a plu-rality of radio cells and the system may comprise also other apparatuses, such as physical layer relay nodes or other network elements, etc. At least one of the (e/g) NodeBs or may be a Home (e/g) nodeB. Additionally, in a geographical area of a radio communication system a plurality of different kinds of radio cells as well as a plurality of radio cells may be provided.
  • Radio cells may be macro cells (or umbrella cells) which are large cells, usually having a diameter of up to tens of kilometers, or smaller cells such as micro-, femto-or picocells.
  • the (e/g) NodeBs of Figure 1 may provide any kind of these cells.
  • a cellular radio system may be implemented as a multilayer network including several kinds of cells. Typically, in multilayer networks, one access node provides one kind of a cell or cells, and thus a plurality of (e/g) NodeBs are required to provide such a network structure.
  • a network which is able to use “plug-and-play” (e/g) NodeBs includes, in addition to Home (e/g) NodeBs (H (e/g) nodeBs) , a home node B gateway, or HNB-GW (not shown in Figure 1) .
  • HNB-GW HNB Gateway
  • a HNB Gateway (HNB-GW) which is typically installed within an operator’s network may aggregate traffic from a large number of HNBs back to a core network.
  • a data payload may be transmitted from the Mobility Management Entity (MME) via an access node to a terminal device.
  • MME Mobility Management Entity
  • the terminal device first, needs to be paged with a paging message transmitted by the access node (per request of the MME) . If the terminal device detects an identifier of the terminal device from the decoded paging message, it triggers a Random Access (RA) procedure in order to establish an RRC connection.
  • RA Random Access
  • the Random Ac-cess procedure itself entails multiple steps as the terminal device needs to trans-mit a preamble (i.e., a sequence of known bits or a signature) to the access node and the access node needs to allocate resources for the transmission of a paging response (i.e., a RRC connection request) . Only after the resources have been allo-cated, the terminal device may transmit to the access node the paging response which in turn triggers the RRC connection setup.
  • a preamble i.e., a sequence of known bits or a signature
  • the access node After the RRC connection has been setup successfully (comprising at least transmitting a RRC connection setup message by the access node and subsequently a RRC connection setup acknowl-edgment by the terminal device) , the access node is able to finally to allocate re-sources for the data payload and subsequently transmit the data payload using the allocated resources.
  • the small data payload may be defined as correspond- ing to a payload size which is able to fit into a single downlink transmission or a payload size below a (pre-defined) maximum downlink transport block size.
  • NB-IoT Narrow-band Internet of Things
  • LPWAN Low Power Wide Area Network
  • the NB-IoT focuses spe-cifically on indoor coverage, low cost, long battery life and high connection densi-ty.
  • NB-IoT is based on the LTE standard, but limits the bandwidth to a single nar-row band of 200 kHz. It uses OFDM modulation for downlink communication and SC-FDMA for uplink communications.
  • SC-FDMA SC-FDMA
  • the embodiments to be described below utilize a short paging re-sponse (e.g., 16 bits) and/or combined resource allocation to overcome or at least alleviate the problems described above.
  • the embodiments also reduce overall latency of the procedure.
  • Figure 2 illustrates a process according to an embodiment for trans-mitting a (small) data payload to at least one terminal device as early data trans-mission.
  • the illustrated process may be performed by an access node or specifi-cally the access node 104 of Figure 1. While the process is discussed in the follow-ing in terms of an access node carrying out the process, in other embodiments another network (possibly in communication with an access node) may carry out the illustrated process fully or partly.
  • the at least one terminal device may com-prise one or more NB-IoT-compatible or eMTC-compatible devices. In some em-bodiments, all of the at least one terminal device may be NB-IoT-compatible de-vices or eMTC-compatible devices.
  • the access node causes transmitting, in block 201, a paging message to the at least one terminal device associated with a small data payload to be transmitted.
  • the paging message may comprise, for each of the one or more terminal devices, a paging identifier, a preamble and/or a first transport block size (TBS) .
  • the preamble may be a common preamble for multi-ple paging identifiers of terminal devices.
  • the first transport block size may cor-respond to the paging identifier of the terminal device for each terminal device of the one or more terminal devices.
  • the first transport block size may be associated with the small data payload and thus may be used by the terminal device for de-coding the data payload.
  • the paging message may further comprise a flag for each paging identifier of a terminal device for which early data transmission is sched-uled.
  • the paging message or the paging identifier may (implicitly or indi-rectly) comprise, for each of the one or more terminal devices, an additional (hid-den or implicit) N bit identifier.
  • the N bit identifier may not be directly included in the paging message (i.e., it may not be directly accessible from the paging mes-sage) , but it may be extractable from the paging identifier based on the Interna-tional Mobile Subscriber Identity (IMSI) of the terminal device (or other terminal device identifier known to the terminal device) and optionally an index of the paging identifier (i.e., the position of the paging identifier within the paging mes-sage) which is comprised in the paging message.
  • IMSI Interna-tional Mobile Subscriber Identity
  • the N bit identi-fier may be generated locally by the terminal device (or by the access node) based on the paging identifier, the IMSI of the terminal device and the index of the pag-ing identifier of the terminal device.
  • the N bit identifier may be used for provid-ing additional security for the early data transmission at the terminal device and/or at the access node.
  • the N bit identifier is not directly included in the paging message (i.e., it is inaccessible without the IMSI of the corresponding ter-minal device) , it is not possible for an unwanted terminal device to access this N bit identifier (and transmit it to the access node as a paging response) by just looking into the paging message.
  • N is a positive integer which may, in some em-bodiments, be equal to 16 though in other embodiments it may have another val-ue, preferably satisfying N ⁇ 88.
  • the transport block size of 88 bits corresponds to a RRC connection request (Msg3) transmitted in conventional LTE RRC connec-tion setup procedure.
  • the IMSIs and/or the indices of the at least one terminal device may be maintained in a database comprised in or connected to the access node.
  • the paging message may be a RRC paging message modified by including said additional (hidden) N bit identifier (or specifically additional 16 bit identifi-er) .
  • one or more of the paging identifier, the pre-amble, the first transport block size and the N bit identifier may be provided for a terminal device using means other than the paging message, for example, using another message transmitted by the access node or other network node.
  • the access node receives (and decodes) , in block 202, one or more preambles which were comprised in the paging message.
  • the one or more pre-ambles may be transmitted from terminal device (s) which received and decoded the paging message successfully.
  • the access node receives preambles from each of the one or more terminal devices. However, some of the one or terminal devices may have been unable to receive the paging response and thus no pream-ble transmission is received from said terminal devices.
  • the message received in block 202 may correspond to Msg1 of LTE RRC connection setup procedure.
  • the access node causes transmitting, in block 203, a first resource allocation grant to each of one or more first terminal devices associated with the one or more preambles.
  • the set of one or more first terminal devices may correspond to the set of at least one terminal device or be smaller in number compared to it.
  • the first resource allocation grant defines allocated downlink resources and uplink resources for each terminal de-vice.
  • the resource allocation grant may define allocated uplink re-sources to be used for transmitting a paging response (or a RRC connection re-quest) and allocated downlink resources to be used for transmitting the data pay-load.
  • the allocated uplink resources may correspond to one or more pre-defined transport block sizes for uplink transmission (to be discussed below in detail) .
  • the downlink resources allocated in each first resource allocation grant may be narrowband physical data shared channel (NPDSCH) resources.
  • NPDSCH narrowband physical data shared channel
  • the downlink resources allocated in each first resource allocation grant may be machine-type communication physical downlink control channel (MPDCCH) resources.
  • MPDCCH machine-type communication physical downlink control channel
  • the downlink resources may be allo-cated in the first resource allocation grant for a maximum transport block size required by any of the one or more first terminal devices and/or the uplink re-sources may be allocated in the first resource allocation grant (or in a second re-source allocation grant to be discussed below) for a maximum transport block size of 88 bits.
  • the access node may be configured to cause transmitting in some situations, instead of the first resource allocation grant, a second resource allocation grant (e.g., Msg2 or Random Access Response of LTE RRC connection setup procedure) defining only allocated uplink resources to be used for the paging response.
  • a second resource allocation grant e.g., Msg2 or Random Access Response of LTE RRC connection setup procedure
  • Which resource allocation grant (first or second) is transmitted may depend, e.g., on the paging load in the cell associated with the access node.
  • a second resource allocation grant e.g., Msg2 or Random Access Response of LTE RRC connection setup procedure
  • the access nodes receives, in block 204, one or more paging responses from one or more second terminal devices which is a subset of the one or more first terminal devices (but not necessarily a proper or strict subset thereof) .
  • the paging response may be received on uplink resources allocated in the resource allocation grant.
  • the access node de-codes, in block 205, each paging response based on one or more pre-defined transport block sizes.
  • the one or more pre-defined transport block sizes comprise at least N bits, preferably with N ⁇ 88 as discussed above. In other embodiments, the one or more pre-defined transport block sizes comprise at least N bits with N ⁇ 88 and 88 bits.
  • the N bit transport block size may correspond to the additional N bit identifier extractable from the paging message by the terminal device and which may be used by terminal devices as the paging response (i.e., as an N bit paging response) .
  • N may be, for example, equal to 16.
  • the access node may, for example, compare each re-ceived N bit identifier against one or more N bit identifiers associated with the at least one terminal device (to which the paging response was transmitted) e.
  • the one or more N bit identifiers may be maintained a database comprised in or con-nected to the access node.
  • Each of the one or more N bit identifiers may be gener-ated and stored to the database when the paging message is transmitted to a par-ticular terminal device for the first time.
  • the 88 bit transport block size may cor-respond to the response message or RRC connection request (Msg3) transmitted in conventional LTE RRC connection setup procedure.
  • the access node may attempt decoding for transport block size corresponding to conven-tional Msg3 and to a new shorter Msg3 (i.e., a short paging response) .
  • the access node may use the assigned uplink resource used to transmit the acknowledgement bit to identify the UE.
  • the number of repetitions may be larger for the transmissions of short paging responses (i.e., ones corresponding to N bit transport block size with N ⁇ 88) compared to the conventional 88 bit paging re-sponses.
  • the access node After the decoding, the access node causes transmitting, in block 206, the small data payload on the downlink resources (allocated in the resource allo-cation grant) to each of the one or more second terminal devices.
  • the small data payload on the downlink resources (allocated in the resource allo-cation grant) to each of the one or more second terminal devices.
  • no connection needs to be estab-lished between the access node and the one or more second terminal device for transmitting the small data payload.
  • the access node may decode each paging response as soon as the paging response arrives (i.e., not wait until all paging responses are received until proceeding with the decoding) .
  • the access node may transmit a separate resource allocation grant for each terminal device as soon as the corresponding preamble is received and decoded.
  • Figure 3 illustrates a process according to an embodiment for receiv-ing (small) data payload by a terminal device.
  • the illustrated process may be per-formed by any of the terminal devices 100, 102 of Figure 1.
  • the illustrated pro-cess may correspond to the process carried out by each terminal device in re-sponse to the access node carrying out the process of Figure 2.
  • the terminal de-vice may be a NB-IoT device or an eMTC device.
  • the terminal device initially receives (and de-codes) , in block 301, a paging message from an access node.
  • the paging message may be defined as described in relation to Figure 2, i.e., it may, for example, com-prise at least a paging identifier of the terminal device, a preamble, a first transport block size and an index of the paging identifier.
  • the terminal device causes transmitting, in block 302, the preamble (which was comprised in the paging message) to the access node.
  • the access node In response to receiving (and decoding) , in block 303, a first resource allocation grant, the access node causes transmitting, block 304, a first paging response on the uplink resources to the access node.
  • the first resource allocation grant may be defined as described in relation to Figure 2, i.e., it may define allocated uplink resources and downlink resources.
  • the downlink resources may be allocated in the first re-source allocation grant for a maximum transport block size required by any of the one or more first terminal devices and/or the uplink resources may be allocated in the first resource allocation grant for a maximum transport block size of 88 bits (even though only N bits with N ⁇ 88 are required for the transmission of the short paging response) .
  • the first paging response may also be defined as described in relation to Figure 2, i.e., it may be a short paging response, e.g., hav-ing the size of N or 16 bits.
  • the short paging response may be generated by the terminal device based on the paging response, the index of the paging response and the IMSI of the terminal device.
  • the IMSI of the terminal device may have been provisioned in the SIM (Subscriber Identity Module or Subscriber Identifica-tion Module) card of the terminal device, in the terminal device directly or in the R-UIM (Removable User Identity Module) card.
  • the access node In response to receiving, in block 305, a (small) data payload from the access node on the downlink resources (allo-cated in the resource allocation grant) , the access node decodes, in block 306, the data payload based on the first transport block size. If the terminal device fails to receive any of the first resource allocation grant in block 303 and the small data payload in block 305 (e.g., within one or more pre-defined time limits) , the pro-cess may be cancelled/interrupted.
  • the access node may be configured to select whether to perform the connectionless downlink early data transmission or the normal connected downlink data transmission (e.g., using LTE RRC connec-tion setup procedure) based on certain criteria (e.g. paging load on the cell) .
  • Fig-ures 4A and 4B illustrate a process according to one such embodiment. The illus-trated process may be performed by an access node or specifically the access node 104 of Figure 1.
  • the one or more pre-defined transport block sizes used for decoding paging response comprise a sec-ond transport block size (e.g., 16 bits) and a third transport block size (e.g., 88 bits) larger than the second transport block size.
  • a paging request (e.g., a RRC paging request) comprising a (small) data payload associated with at least one terminal device.
  • the paging re-quest may be received from a core network or specifically from the MME. It should be appreciated that the feature illustrated in block 401 may also be com-bined with the embodiment illustrated in Figure 2.
  • the access node causes transmitting, in block 402, a paging message to each of the at least one terminal device. Thereafter, the access node starts, in block 402, a timer.
  • the timer is a validity timer for the preamble (s) comprised in each paging message.
  • the timer may be restarted ifthe same pre-amble is assigned for another paging message. Therefore, ifthere is heavy paging load in the cell associated with the access node, the timer may be restarted fairly regularly.
  • the access node determines whether the preamble was received before the timer exceeded a pre-defined (time) limit. If the pre-defined limit was not exceed-ed at the time of reception of the preamble in block 405, the access node may cause transmitting, in block 406, the first resource allocation grant to the corre-sponding terminal device (as described in relation to Figure 2) . In some embodi-ments, the access node may, instead of transmitting the first resource allocation message, cause transmitting, in block 406, a second resource allocation message.
  • the second resource allocation grant defines an allocation only for uplink re-sources (to be used for sending the paging response) .
  • the second resource alloca-tion grant may correspond to Msg2 (i.e., Random Access Response, RAR) of LTE RRC connection setup.
  • RAR Random Access Response
  • the decision whether the transmit the first resource allo-cation grant (i.e., use early downlink data transmission with combined allocation) or the second resource allocation grant (i.e., use conventional downlink data transmission) may be based, for example, information provided in the paging re-quest.
  • the access node In response to receiving, in block 407, a paging response from the ter-minal device to which a first or a second resource allocation grant was transmit-ted, the access node decodes, in block 408, based on the second and third transport block sizes.
  • the paging response may be a short paging response corre-sponding to the second transport block size (e.g., 16 bits) or a “conventional” pag-ing response corresponding to the third transport block size (e.g., 88 bits) . There-fore, the access node attempts decoding with both of these transport block sizes.
  • the access node causes transmitting, in block 410, the data payload on said downlink resources.
  • the access node establishes, in blocks 410, 411, a connection to the access node for transmitting the data payload.
  • the access node causes transmitting, in block 410, a connection setup message for configuring the termi-nal device for establishing the connection to the terminal device.
  • the connection setup message may be a LTE RRC connection setup message.
  • the access node In response to re-ceiving a connection setup acknowledgment message (e.g., LTE RRC connection setup complete message) in block 411, the access node causes transmitting, in block 412, the data payload using the established connection.
  • a connection setup acknowledgment message e.g., LTE RRC connection setup complete message
  • the access node may be configured to perform the trans-mitting of the data payload always according to a (RRC) connection setup proce-dure. Namely, the access node causes transmitting, in block 413, a second re-source allocation grant (as defined above) . In response to receiving a paging re-sponse from the terminal device in block 414, the access node decodes, in block 412, the paging response based only on the third transport block size.
  • RRC radio resource control
  • the terminal device always transmits a paging response corre-sponding to the third transport block size (e.g., 88 bits) in response to receiving the second resource allocation grant.
  • Blocks 413, 414 may correspond to blocks 410, 411 and are thus not repeated for brevity.
  • the access node In response to receiving the con-nection setup acknowledgment message in block 417, the access node causes transmitting, in block 415, the data payload using the established connection.
  • Figure 5 illustrates a process according to an embodiment for receiv-ing a (small) data payload by a terminal device.
  • the illustrated process may be performed by any of the terminal devices 100, 102 of Figure 1.
  • the illustrated process may correspond to the process carried out by each terminal device in response to the access node carrying out the process of Figures 4A and 4B.
  • blocks 501, 502 may correspond to blocks 301, 302 of Figure 1 and are thus not repeated here for brevity. Furthermore, if a first resource allocation grant (as defined in relation to above embodiments) is re-ceived in block 503, the terminal device may carry out a process similar to as dis-cussed in relation Figure 3.
  • the terminal device may further be configured to handle second resource allocation grants as defined in relation to Figures 4A and 4B (in blocks 504 to 508) .
  • This functionality may correspond to a conventional LTE RRC connection setup procedure.
  • the terminal device In response to receiving a second resource allocation grant in block 504, the terminal device causes transmitting, in block 505, a (second) pag-ing response to the access node.
  • the transmitted second paging response may specifically be a paging response corresponding to the third transport block size (e.g., 88 bits) .
  • the second paging response may comprise the paging identifier and correspond to a transport block size of 88 bits.
  • the second paging response may correspond to a (RRC) connection request.
  • the terminal device may configure, in block 507, itself for establishing a connection based on the connection setup message and subse-quently transmit, in block 508, a connection setup acknowledgment to the access node.
  • the terminal device decodes, in block 510, the small data payload, e.g., based on the first transport block size received in the paging mes-sage (block 501) .
  • Figure 6 illustrates an alternative process according to embodiments using a signaling diagram between an access node and a terminal device for transmitting a (small) data payload from the access node to the terminal device.
  • Figure 6 shows a simplified process where some of the steps (e.g., receiving and decoding steps) are omitted.
  • the access node in response to receiving a paging re-quest in block 601, the access node allocates, in block 601, a preamble for each terminal device (of only one is shown in Figure 6) from contention-based random access resources or from dedicated resources (other than contention-based ran-dom access resources) . Then, the access node causes transmitting, in message 602, a paging message comprising that allocated preamble for the terminal de-vice.
  • the access node may attempt (blind) decoding of short messages (i.e., message 603) only on uplink allocation of specific preambles. If the preamble for each terminal device is allocated from dedicated preambles, the ac-cess node does not need to perform blind decoding for short message (i.e., mes-sage 603) .
  • Messages 603 to 605 may correspond to performing blocks 202 to 204 of Figure 2 or blocks 402 to 407 of Figure 4A for the access node side and to performing blocks 301 to 304 of Figure 3 or blocks 501 to 503 and 511 of Figure 5 for the terminal device.
  • the first re-source allocation grant (message 504) comprises, in addition to the allocation of uplink and downlink resources, respectively, for the paging response and the small data payload, an allocation of additional uplink resources for an acknowl-edgment and an allocation for a gap in downlink transmission (illustrated as ele- ment 607) .
  • the paging response 605 may be, in the illustrated embodiment, an N bit paging response corresponding to an N bit identifier generated based at least on the IMSI of the terminal device and the paging message.
  • the allocated gap 607 in downlink transmission may be used retrans-mitting the paging response in the case that the decoding of the paging response fails.
  • the access node receives the paging response (mes-sage 605) and tries to decode it, but the decoding is not successful in block 606. Consequently, the access node causes transmitting, in message 608, a downlink control indicator (DCI) to the terminal device within the allocated gap 607.
  • DCI downlink control indicator
  • the downlink control indicator indicates a negative acknowledgment to the terminal device and comprises information on new resource allocation at least for re-transmission of the paging response (and possibly also for the transmission of the small data payload) .
  • the information on new resource allocation may comprise new starting points in frequency and/or time domain for resource allo-cation of the paging response and/or transmission of the small data payload.
  • the terminal device In response to receiving and decoding the downlink control indicator, the terminal device causes retransmitting, in message 609, the paging response (possibly also within the gap 607) . It is assumed in the illustrated scenario that the decoding of this second paging response based on the one or more second transport block sizes (e.g., N or 16 bits and possibly 88 bits) is successful. Obviously, in other em-bodiments multiple retransmissions of the paging response (and thus multiple resource reallocations) may also be possible.
  • the one or more second transport block sizes e.g., N or 16 bits and possibly 88 bits
  • the ac-cess node causes transmitting, in message 610, the small data payload using the downlink resources allocated in the resource allocation grant and/or the down-link control indicator based on the first transport block size (comprised in the paging message 602) .
  • the terminal device causes transmitting, in message 611, an acknowledgment to the access node on the additional uplink resources (allocated in the resource allocation grant 604) in response to the decoding of the small data payload.
  • the access node may receive and decode the acknowledgment. If the decoding of the small data payload by the terminal device fails for any reason, the terminal device may be configured to transmit a negative acknowledgment, instead of the positive acknowledgment, in message 611.
  • Fig-ure 6 the additional features introduced in Fig-ure 6 are not inextricably linked to each other. Some embodiments may, for ex-ample, comprise one or more of the features pertaining to the allocating of the preamble, allocating of the gap in downlink transmission and its utilization for retransmission and the allocation and the transmitting of the acknowledgment.
  • While the above embodiments describe processes for early data transmission utilizing (at least for some terminal devices) joint uplink and down-link allocation with a single resource allocation grant, some other embodiments may be limited only to processes relating to responding to a paging message using a short paging response (e.g., corresponding to an N or 16 bit identifier) .
  • a short paging response e.g., corresponding to an N or 16 bit identifier
  • Such embodiments maintain the benefits discussed above for the short paging re-sponse, that is, the reduced energy consumption compared to transmitting a lega-cy 88 bit paging response (Msg3) and improved security if the IMSI of the termi-nal device is used for generating the short paging response.
  • Figure 7 illustrates such a process according to embodiments using a signaling diagram between an access node and a terminal device.
  • the access node causes transmitting a paging message, message 701, to the terminal device associated with a (small) data payload to be transmitted.
  • the paging message comprises, for the terminal device, at least a paging identifier of the terminal de-vice.
  • the paging message may further comprise one or more of a preamble, a first transport block size and an index of the paging identifier of the terminal device.
  • the terminal device receives (and decodes) , in block 702, the paging message 701. If the paging message comprises a preamble, the terminal device may transmit the preamble to the access node as discussed in relation to above embodiments (not shown in Figure 7) .
  • the access node causes transmitting, in message 703, a first resource allocation grant to the terminal device.
  • the first resource allocation grant may define an allocation at least for uplink resources.
  • the first resource allocation grant may also define an allocation for downlink resources (for transmitting a small data payload) .
  • the terminal device receives and decodes, in block 704, the resource allocation grant 703. Subsequently, the terminal device causes transmitting a first paging response on the uplink resources to the access node.
  • the first paging re-sponse may be generated, by the terminal device, based at least on the paging identifier and may correspond to the transport block size N smaller than 88 bits (e.g., 16 bits) .
  • the first paging response may be generated based on the paging identifier, the index of the paging identifier and the IMSI of the terminal device.
  • the access node receives and decodes, in block 706, one or more pag-ing responses 705 from one or more second terminal devices on the uplink re-sources, each paging response based on the one or more pre-defined transport block sizes for uplink transmission.
  • the paging response may be decoded based on a pre-defined transport block size of N bits, N being a positive integer with N ⁇ 88.
  • the terminal device may transmit a short paging response, instead of an 88 bit paging response corresponding a RRC connection request.
  • the access node may cause transmitting of the small data payload which triggered the transmitting of the paging response.
  • the access node may use downlink resources allocated in the resource allocation grant or if no downlink resources were allocated in the resource allocation grant, the access node may, first, allocate said downlink resource and only then cause transmitting the resource allocation grant.
  • FIG. 6 and 7 While embodiments illustrated in Figures 6 and 7 are shown as com-munication between only a single terminal device and an access node, it should be appreciated that the access node may perform the transmission of any of the illus-trated messages to more than one terminal device at a time, similar to as dis-cussed in relation to embodiments illustrated in Figures 2, 4A and 4B.
  • the actions performed by the access node may be performed fully or partly by another network node or network element or even by multiple network nodes/elements.
  • said actions may be performed, instead of the access node, by a core element or by an edge cloud (element) .
  • the N bit identifier and the transport block size of N may be restricted by N ⁇ M.
  • an apparatus/device configured to support small (and ear-ly) data transmission based on at least partly on what is disclosed above with any of Figures 2, 3, 4A, 4B, 5, 6 and 7, including implementing one or more func-tions/operations of a corresponding terminal device or access node (or network element) described above with an embodiment/example, for example by means of any of Figures 2, 3, 4A, 4B, 5, 6 and 7, comprises not only prior art means, but also means for implementing the one or more functions/operations of a corre-sponding functionality described with an embodiment, for example by means of any of Figures 2, 3, 4A, 4B, 5, 6 and 7.
  • the implementation may comprise separate means for each separate function/operation, or means may be config-ured to perform two or more functions/operations.
  • one or more of the means described above may be im-plemented in hardware (one or more devices) , firmware (one or more devices) , software (one or more modules) , or combinations thereof.
  • the apparatus (es) of embodiments may be implemented within one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , processors, controllers, micro-controllers, microprocessors, logic gates, decoder circuitries, encoder circuitries, other electronic units designed to perform the functions described herein by means of Figures 2, 3, 4A, 4B, 5, 6 and 7, or a combination thereof.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, micro-controllers
  • the implementation can be carried out through modules of at least one chipset (e.g., procedures, functions, and so on) that perform the functions described herein.
  • the software codes may be stored in a memory unit and exe-cuted by processors.
  • the memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively cou-pled to the processor via various means, as is known in the art.
  • the components described herein may be rearranged and/or complemented by addi-tional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise config- urations set forth in the given figures, as will be appreciated by one skilled in the art.
  • Figure 8 provides an access node, a terminal device (e.g., a NB-loT de-vice or an eMTC device) or other network node or network element (apparatus, device) according to some embodiments.
  • Figure 8 may illustrate an access node or other network element (in the following, simply “the access node” for brevity) configured to carry out at least the functions described above in connection with configuring small data transmission to at least one terminal device.
  • Figure 8 may illustrate a terminal device configured to carry out at least the func-tions described above in connection with configuring the terminal device to re-ceive small data transmission and receiving the small data payload.
  • Each access node and terminal device may comprise one or more communication control cir-cuitry 820, such as at least one processor, and at least one memory 830, including one or more algorithms 831, such as a computer program code (software) where-in the at least one memory and the computer program code (software) are con-figured, with the at least one processor, to cause, respectively, the access node or the terminal device to carry out any one of the exemplified functionalities of the access node or the terminal device described above.
  • communication control cir-cuitry 820 such as at least one processor
  • at least one memory 830 including one or more algorithms 831, such as a computer program code (software) where-in the at least one memory and the computer program code (software) are con-figured, with the at least one processor, to cause, respectively, the access node or the terminal device to carry out any one of the exemplified functionalities of the access node or the terminal device described above.
  • algorithms 831 such as a computer program code (software) where-in the at least one
  • the communication control circuitry 821 of the access node 801 comprises at least data transmission circuitry 821 and connec-tion setup circuitry.
  • the data transmission circuitry 821 may be configured to configure at least one terminal device for receiving a data payload as small (and early) data transmission and to transmit said data pay-load and, to this end, to carry out at least some of the functionalities described above by means of any of Figures 2, 4, 6 and 7 using one or more individual cir-cuitries.
  • the connection setup circuitry 822 may be configured to carry out any conventional (RRC) connection setup processes of the access node as described in relation to any of Figures 2, 4, 6 and 7 using one or more individual circuitries.
  • the data transmis-sion circuitry 821 may be configured to configure the terminal device for receiv-ing a data payload as small (and early) data transmission in communication with an access node and, to this end, to carry out at least some of the functionalities described above by means of any of Figures 3, 5, 6 and 7 using one or more indi-vidual circuitries.
  • the connection setup circuitry 822 may be configured to carry out any conventional (RRC) connection setup processes of the terminal device as described in relation to any of Figures 3, 5, 6 and 7 using one or more individual circuitries.
  • the memory 830 may be implemented using any suitable data storage technology, such as semiconductor based memory de-vices, flash memory, magnetic memory devices and systems, optical memory de-vices and systems, fixed memory and removable memory.
  • the access node or the terminal device may fur-ther comprise different interfaces 810 such as one or more communication inter-faces (TX/RX) comprising hardware and/or software for realizing communication connectivity over the medium according to one or more communication proto-cols.
  • the communication interface 810 for the access node may pro-vide the access node with communication capabilities to communicate in the cel-lular communication system and enable communication to one or more user de-vices (terminal devices) and between different network nodes or elements and/or a communication interface to enable communication between different network nodes or elements, for example.
  • the communication interface 810 for the terminal device may provide the terminal device with communication capabilities to communicate in the cellular communication system and enable communi-cation between user devices (terminal devices) and to different network nodes or elements (e.g., to one or more access nodes) .
  • the communication interface may comprise standard well-known components such as an amplifier, filter, frequen-cy-converter, (de) modulator, and encoder/decoder circuitries, controlled by the corresponding controlling units, and one or more antennas.
  • the communication interfaces 810 for the access node may comprise radio interface components providing the access node radio communication capability to provide a cell with at least an unlicensed band.
  • the communication interfaces 810 for the access node may comprise optical interface components providing the access node with optical fiber communication capability.
  • the commu-nication interfaces for the terminal device may comprise radio interface compo-nents providing the terminal device radio communication capability to use NPDSCH and/or eMTC resources.
  • the terminal device may also comprise differ-ent user interfaces.
  • circuitry may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of hardware circuits and software (and/or firmware) , such as (as applicable) : (i) a combination of analog and/or digital hardware circuit (s) with software/firmware and (ii) any portions of hardware processor (s) with software, including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or an access node, to perform various func-tions, and (c) hardware circuit (s) and processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g.
  • circuitry for operation, but the software may not be present when it is not needed for opera-tion.
  • circuitry also covers an implementation of merely a hardware circuit or proces-sor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit for an access node or a terminal device or other computing or network device.
  • the at least one processor, the memory, and the com-puter program code form processing means or comprises one or more computer program code portions for carrying out one or more operations according to any one of the embodiments of Figures 2, 3, 4A, 4B, 5, 6 and 7 or operations thereof.
  • Embodiments as described may also be carried out in the form of a computer process defined by a computer program or portions thereof. Embodi-ments of the methods described in connection with Figures 2, 3, 4A, 4B, 5, 6 and 7 may be carried out by executing at least one portion of a computer program com-prising corresponding instructions.
  • the computer program may be provided as a computer readable medium comprising program instructions stored thereon or as a non-transitory computer readable medium comprising program instructions stored thereon.
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
  • the computer program may be stored on a computer program distribution medi-um readable by a computer or a processor.
  • the computer program medium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distri-bution package, for example.
  • the computer program medium may be a non-transitory medium. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art.

Landscapes

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

Abstract

Selon un aspect, l'invention concerne un nœud d'accès comprenant des moyens pour effectuer les étapes suivantes. Le nœud d'accès provoque la transmission d'un message de radiomessagerie à au moins un dispositif terminal associé à une charge utile de données. Le message de radiomessagerie comprend, pour chaque dispositif terminal, au moins un identificateur de radiomessagerie. Le nœud d'accès provoque également la transmission d'une autorisation d'attribution de ressources à au moins une partie du dispositif terminal. Chaque autorisation d'attribution de ressources définit une attribution au moins pour des ressources de liaison montante. Le nœud d'accès décode, en réponse à la réception d'une ou de plusieurs réponses de radiomessagerie sur les ressources de liaison montante, chaque réponse de radiomessagerie sur la base de la ou des tailles de bloc de transport prédéfinies. Au moins une réponse de radiomessagerie est décodée sur la base d'une taille de bloc de transport prédéfinie de N bits, N étant un entier positif avec N < 88.
PCT/CN2018/106285 2018-09-18 2018-09-18 Transmission de petites données en liaison descendante WO2020056595A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2018/106285 WO2020056595A1 (fr) 2018-09-18 2018-09-18 Transmission de petites données en liaison descendante
CN201880097807.8A CN112740778B (zh) 2018-09-18 2018-09-18 下行链路小数据传输

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/106285 WO2020056595A1 (fr) 2018-09-18 2018-09-18 Transmission de petites données en liaison descendante

Publications (1)

Publication Number Publication Date
WO2020056595A1 true WO2020056595A1 (fr) 2020-03-26

Family

ID=69888092

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/106285 WO2020056595A1 (fr) 2018-09-18 2018-09-18 Transmission de petites données en liaison descendante

Country Status (2)

Country Link
CN (1) CN112740778B (fr)
WO (1) WO2020056595A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114189934B (zh) * 2021-12-07 2024-04-26 中国建设银行股份有限公司 一种重复寻呼确定方法、装置、设备及介质
EP4458074A1 (fr) * 2021-12-30 2024-11-06 Lenovo (Beijing) Limited Gestion de transmission de données dans une sdt dl

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104811279A (zh) * 2014-01-23 2015-07-29 电信科学技术研究院 一种寻呼消息传输方法及装置
US20160338006A1 (en) * 2015-05-15 2016-11-17 Samsung Electronics Co., Ltd. Apparatus and method for performing paging process in wireless communication system
CN108012312A (zh) * 2016-10-28 2018-05-08 华为技术有限公司 被寻呼装置、寻呼装置及方法
CN108282861A (zh) * 2017-01-05 2018-07-13 中兴通讯股份有限公司 一种寻呼信息的传输方法、装置及系统

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
ES2784725T3 (es) * 2015-09-25 2020-09-30 Sony Corp Aparatos y procedimientos de telecomunicaciones

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104811279A (zh) * 2014-01-23 2015-07-29 电信科学技术研究院 一种寻呼消息传输方法及装置
US20160338006A1 (en) * 2015-05-15 2016-11-17 Samsung Electronics Co., Ltd. Apparatus and method for performing paging process in wireless communication system
CN108012312A (zh) * 2016-10-28 2018-05-08 华为技术有限公司 被寻呼装置、寻呼装置及方法
CN108282861A (zh) * 2017-01-05 2018-07-13 中兴通讯股份有限公司 一种寻呼信息的传输方法、装置及系统

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Responding the questions on small data Tx in RRC INACTIVE", 3GPP TSG-RAN WG2 #97 R2-1700891, 17 February 2017 (2017-02-17), XP051223281 *
QUALCOMM INCORPORATED: "Early data transmission", 3GPP TSG-RAN WG1 MEETING #89 R1-1708800, 19 May 2017 (2017-05-19), XP051262675 *

Also Published As

Publication number Publication date
CN112740778A (zh) 2021-04-30
CN112740778B (zh) 2023-06-20

Similar Documents

Publication Publication Date Title
US10716031B2 (en) Network node configured to provide wireless access with enhanced resource allocation
US20220330026A1 (en) Counter measures for attacking messages
US20220322487A1 (en) Low-latency communication with discontinuous transmission
US20180295645A1 (en) Device to device communications
WO2020056595A1 (fr) Transmission de petites données en liaison descendante
WO2020120825A1 (fr) Communications par paquets
CN114026952B (zh) 截断的标识指示符
US11997504B2 (en) Dynamic spectrum sharing reduced overhead operation
US11523402B2 (en) Reconfiguring resources for transmission
WO2020037675A1 (fr) Indication de priorité de données pour autorisation de liaison montante
EP3952588B1 (fr) Détermination de l&#39;occupation d&#39;un canal pour la communication de liaison latérale
US20230199835A1 (en) Channel access procedure
EP3756392B1 (fr) Station de base configurée pour fournir un filtrage de distance
WO2022096129A1 (fr) Indicateur de format de créneau
US11870585B1 (en) Adapting hybrid automatic repeat requests
US11863288B2 (en) Relaying transmissions
US20240313906A1 (en) Hybrid automatic repeat request feedback for groupcast
US20240187914A1 (en) Methods and apparatuses for controlling small data transmission on uplink
US20230397241A1 (en) Delay information
US20220393842A1 (en) Scheduling and signalling communication resources
WO2024114911A1 (fr) Bandes tampons adaptatives pour communication directe de dispositif terminal à dispositif terminal
WO2023016632A1 (fr) Procédé et appareil pour transmissions par l&#39;intermédiaire de canaux radio sans licence
WO2022223498A1 (fr) Procédé de partage de ressources informatiques en bande de base

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18934170

Country of ref document: EP

Kind code of ref document: A1