WO2018126406A1 - Traitement de données à terminaison mobile dans un état inactif - Google Patents

Traitement de données à terminaison mobile dans un état inactif Download PDF

Info

Publication number
WO2018126406A1
WO2018126406A1 PCT/CN2017/070314 CN2017070314W WO2018126406A1 WO 2018126406 A1 WO2018126406 A1 WO 2018126406A1 CN 2017070314 W CN2017070314 W CN 2017070314W WO 2018126406 A1 WO2018126406 A1 WO 2018126406A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
control channel
identifier
downlink control
paging
Prior art date
Application number
PCT/CN2017/070314
Other languages
English (en)
Inventor
Yanji Zhang
Yuantao Zhang
Original Assignee
Nokia Technologies Oy
Nokia Technologies (Beijing) Co., Ltd.
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 Technologies Oy, Nokia Technologies (Beijing) Co., Ltd. filed Critical Nokia Technologies Oy
Priority to PCT/CN2017/070314 priority Critical patent/WO2018126406A1/fr
Publication of WO2018126406A1 publication Critical patent/WO2018126406A1/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

Definitions

  • Various communication systems may benefit from the appropriate handling of data that is to be transmitted to a terminal device.
  • certain wireless communication systems may benefit from mobile terminated handling when a user equipment is in inactive state.
  • N-RAT New Radio Access Technology
  • An objective may be the following: “Target a single technical framework addressing all usage scenarios, requirements and deployment scenarios defined in TR38.913 including, Enhanced mobile broadband, Massive machine-type-communications, Ultra reliable and low latency communications” .
  • the new radio access technology may enable a diverse and wide range of services delivered with high throughput, connecting numerous of devices or terminals, and providing immediate feedback on demand.
  • a radio access network (RAN) controlled “inactive state” may need to be provided.
  • the core network (CN) and RAN connection may be maintained.
  • a user equipment (UE) and at least one next generation Node B (gNB) may keep the Access Stratum (AS) context information.
  • a UE location can be known at the RAN based area level where that area may be a single cell or more than one cell.
  • New Radio (NR) may target to support uplink (UL) autonomous/grant-free/contention based” at least for massive machine-type-communications (mMTC) and ultra reliable and low latency communications (URLLC) .
  • mMTC massive machine-type-communications
  • URLLC ultra reliable and low latency communications
  • a method can include determining a user equipment’s location. The method can also include sending mobile terminated data from a paging occasion to the user equipment at the determined location scheduled by a downlink control channel while the user equipment is in inactive mode.
  • a method can include detecting, by a user equipment, a downlink control channel addressed by a stored identifier at a paging occasion. The method can also include decoding, by the user equipment, downlink data from the downlink control channel at the paging occasion or at a subsequent paging occasion while in inactive state.
  • An apparatus can include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to determine a user equipment’s location.
  • the at least one memory and the computer program code can also be configured to, with the at least one processor, cause the apparatus at least to send mobile terminated data from a paging occasion to the user equipment at the determined location scheduled by a downlink control channel while the user equipment is in inactive mode.
  • An apparatus in certain embodiments, can include at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus at least to detect, by a user equipment, a downlink control channel addressed by a stored identifier at a paging occasion.
  • the at least one memory and the computer program code can also be configured to, with the at least one processor, cause the apparatus at least to decode, by the user equipment, downlink data from the downlink control channel at the paging occasion or at a subsequent paging occasion while in inactive state.
  • an apparatus can include means for determining a user equipment’s location.
  • the apparatus can also include means for sending mobile terminated data from a paging occasion to the user equipment at the determined location scheduled by a downlink control channel while the user equipment is in inactive mode.
  • an apparatus can include means for detecting, by a user equipment, a downlink control channel addressed by a stored identifier at a paging occasion.
  • the apparatus can also include means for decoding, by the user equipment, downlink data from the downlink control channel at the paging occasion or at a subsequent paging occasion while in inactive state.
  • a computer program product can, in various embodiments, encode instructions for performing a process.
  • the process can be any of the methods described above.
  • the process can be any of the methods described above.
  • Figure 1 illustrates an example of an LTE based control channel structure, according to certain embodiments.
  • FIG. 2 illustrates direct mobile terminated data transmission, according to certain embodiments.
  • Figure 3 illustrates a downlink control channel order for mobile terminated data transmission, according to certain embodiments.
  • Figure 4 illustrates a flow chart of user equipment behavior for receiving mobile terminated data, according to certain embodiments.
  • FIG. 5 illustrates mobile terminated data notification and transmission, according to certain embodiments.
  • Figure 6 illustrates a flow chart of user equipment behavior for receiving mobile terminated data, according to certain embodiments.
  • Figure 7 illustrates a method according to certain embodiments.
  • Figure 8 illustrates a system according to certain embodiments.
  • Data transmission in inactive state may need to be supported without transition to connection state.
  • One potential solution is to send uplink (UL) data without radio resource control (RRC) signaling.
  • RRC radio resource control
  • the “autonomous/grant-free/contention based” UL transmission is a candidate scheme for the direct data transmission in the new state.
  • the paging procedure is initiated for an RRC_IDLE user equipment (UE) when there is a mobile terminated (MT) packet for the UE.
  • UE user equipment
  • MT mobile terminated
  • the UE After receiving the paging message, the UE will not be able to receive the downlink (DL) data until it transitions to RRC connected state by triggering a service request procedure. Therefore there will be a delay for data reception due to the signaling procedure. This delay can be because of the paging and service request which can contain several signaling interactions over interface Uu and the interface between a radio access network (RAN) and a core network (CN) .
  • RAN radio access network
  • CN core network
  • the RAN may be aware whenever the UE moves from one “RAN-based notification area” to another.
  • the RAN based notification area can be UE-specific and configurable by the gNB via dedicated signaling.
  • a RAN notification area can cover a single cell or multiple cells.
  • a RAN initiated notification procedure can be used to reach the UE in such a case.
  • Certain embodiments provide methods and systems to transmit MT data for UE in inactive state for NR considering the different RAN deployment.
  • the UE sends hybrid automatic repeat request (HARQ) feedback for DL data from physical uplink control channel (PUCCH) if there is no physical uplink shared channel (PUSCH) scheduled.
  • PUCCH physical uplink control channel
  • PUSCH physical uplink shared channel
  • PUCCH is located in the either extreme ends of the uplink frequency domain in alternating fashion between the two slots within a subframe. Exactly how many resource elements are allocated to the PUCCH is determined by the network and the configuration is broadcasted to UE via system information block 2 (SIB2) . Those PUCCH allocations could be considered as common uplink resource shared by the UEs served by the cell.
  • SIB2 system information block 2
  • certain embodiments define another dedicated uplink control channel resource which is applied for the UEs which are in inactive state.
  • Such dedicated uplink control channel resource may be one specific resource unit, which is broadcasted by gNB and shared by all UEs in inactive state, or within the resource pool for contention based or grant free UL transmission preconfigured for the UE.
  • the LTE light connection procedure may be applied as baseline for NR inactive state.
  • a LTE light connected UE can follow nearly all IDLE mode procedures, except extended discontinuous reception (eDRX) and power save mode (PSM) .
  • the UE can apply paging occasion calculations for monitoring the DL paging message. Therefore, a NR UE in inactive state may also be able to monitor the downlink control channel at each paging occasion (PO) derived from the paging cycle.
  • PO paging occasion
  • a RAN notification area can cover a single cell or multiple cells belonging to same gNB.
  • the UE can update the UE’s location to the RAN whenever the UE reselects a new gNB, the UE’s location is always known to gNB.
  • the MT data could be sent to UE directly scheduled by downlink control channel. If a UE detects downlink control channel addressed by the stored C-RNTI at a PO, it will decode the DL data from downlink data channel at the same subframe.
  • gNB may indicate a need of state transition from inactive to connected state in the DL message.
  • the indication could be carried either in the downlink control information (DCI) within downlink control channel or in the user data in downlink data channel, for example a medium access control (MAC) control element (CE) for example.
  • DCI downlink control information
  • MAC medium access control
  • CE control element
  • the UE could send acknowledgement /negative acknowledgement (A/N) feedback for received DL data via the common uplink control channel.
  • A/N acknowledgement /negative acknowledgement
  • the UE can send A/N feedback for the received DL data via a dedicated uplink control channel.
  • the sequence used by the UE for transmitting A/N in the dedicated UL control channel can be determined by the lowest resource block (RB) index of this control channel and the lowest control channel element (CCE) index carrying the corresponding scheduling DCI.
  • the UE can start the normal state transition procedure by corresponding RRC signaling after sending the UL feedback.
  • the gNB may send an order from the downlink control channel prior to the DL data transmission by a DCI format. Similarly the gNB may request a state transition from inactive to connected state in the same DCI.
  • the UE After detecting the DCI from downlink control channel addressed by the C-RNTI, if the state transition is not required, the UE can transmit the UE’s own identifier allocated when the UE moved from connected state to inactive state. Within the response from gNB, a timing advance (TA) value may be included, by which UE could reach UL synchronization with gNB. The UE can continue monitoring the DL data scheduled by downlink control channel, and can send A/N for the received data via the common uplink control channel. If the state transition is required, the UE can start the state transition procedure and receive the DL data after entering the connected state.
  • TA timing advance
  • a RAN notification area can cover multiple cells belonging to different gNBs. As the UE performs mobility within that area without notifying the network, the serving gNB may not know the exact location of the UE within the RAN based notification area.
  • the gNB can initiate a paging procedure.
  • the UE can detect a downlink control channel addressed by P-RNTI or a separate P-RNTI for those UEs working in inactive state.
  • the paging message may have following information: a flag to indicate whether the state transition is required; and a preamble and/or a contention based (CB) or grant free resource for CB or grant free transmission followed.
  • CB contention based
  • the UE can start the CB UL transmission from the CB or grant free resources indicated by paging message if the indication of the CB or grant free resources is present, otherwise the UE can randomly select from preconfigured resources.
  • the UE will send corresponding RRC message, and the DL data is sent after UE transits to connected. Otherwise, the UE can send the UE’s identifier allocated when it left connected state for inactive state.
  • the gNB can send feedback if the gNB derives and verifies the UE context by the identifier.
  • the feedback may contain the relative parameters, for example the new allocated C-RNTI, the TA optionally depending on different situations.
  • the UE can start monitoring a downlink control channel addressed by the C-RNTI for downlink data, and can send A/N for the received data via uplink control channel from the common resource.
  • certain embodiments provide various methods and systems to transmit MT data for a UE in inactive state for NR, considering the different RAN deployments that are possible.
  • Separate uplink control channel resource can be allocated dedicatedly to the UE working in inactive state, which could be reserved from the preconfigured contention based UL resource.
  • the dedicated uplink control channel resource could be configured to UE together with contention based UL resource configuration.
  • the UE can send UL A/N feedback corresponding to the received DL data transmission from the common uplink control channel if the UE keeps UL synchronization with gNB. Otherwise the UE can send the A/N feedback from the dedicated uplink control channel.
  • Figure 1 illustrates an example of an LTE based control channel structure, according to certain embodiments. More particularly, Figure 1 illustrates common UL control channel for UL when a UE is synchronized (sync) , and dedicated UL control channel for UL when a UE is not synchronized (async) .
  • the common control region may use a different structure, such as containing one or more dedicated orthogonal frequency division multiplexed (OFDM) symbols in the whole frequency domain and/or including a specific pool of sequences.
  • the dedicated physical uplink control channel (PUCCH) region can be in different resources than those for the common PUCCH region.
  • Figure 2 illustrates direct mobile terminated data transmission, according to certain embodiments.
  • the gNB can schedule the MT data received from a gateway (GW) by downlink control channel.
  • the gNB may also indicate the request for state transition in the DCI carried in downlink control channel, or by MAC CE carried in the downlink data channel multiplexed with the user data.
  • the TA timer can be running, and thus the UE can be maintaining UL synchronization with gNB.
  • the UE can send the A/N feedback for the received DL data from the common uplink control channel.
  • the UE can send the feedback from a dedicated uplink control channel.
  • the UE can initiate the state transition procedure.
  • the gNB may indicate a DL data from the downlink control channel, and the state transition may be required at the same time.
  • Figure 3 illustrates a downlink control channel order for mobile terminated data transmission, according to certain embodiments.
  • the approach of Figure 3 may be suitable for case 1.
  • the gNB can inform the UE about the MT data by downlink control channel.
  • the gNB may also indicate a request for state transition in the DCI carried in downlink control channel.
  • the UE can send the UE’s UE identifier allocated when moving to inactive state. Then, at 3, the gNB can send the feedback for the received UL data, which may contains the TA value. At 4, the UE can start monitoring the downlink control channel for the DL data. As with the previous example, the downlink control channel can be addressed by C-RNTI and downlink data channel scrambled by C-RNTI. At 5, the UE can send the A/N feedback for the received data from the common uplink control channel.
  • the UE can initiate the state transition procedure. Then, at 3A, the UE can start the normal DL data reception and UL feedback transmission after entering into connected state.
  • Figure 4 illustrates a flow chart of user equipment behavior for receiving mobile terminated data, according to certain embodiments.
  • Figure 4 illustrates an approach that may be suitable for case 1.
  • the user equipment can monitor a downlink control channel addressed by C-RNTI at a PO derived from a paging cycle.
  • the user equipment can check DCI at 415. If the DCI indicates a direct data transmission followed via a downlink data channel, then at 420 the user equipment can receive the DL data from the DL data channel scheduled by the DCI.
  • the UE can check whether a timing advance (TA) timer is running. If so, then at 430 the UE can send UL A/N feedback using a common uplink control channel resource. Otherwise, at 435, the UE can send UL A/N feedback using a dedicated uplink control channel resource.
  • the gNB can request a state transition, for example from inactive state to connected state. Then, at 445, the user equipment can trigger the state transition procedure to connected. The process can end at 450.
  • TA timing advance
  • the DCI indicates mobile terminated (MT) data
  • the UE can monitor a downlink control channel addressed by C-RNTI and decode the DL data from the downlink data channel scheduled by downlink control channel. Then, at 470, the UE can send UL A/N feedback using a common uplink control channel resource.
  • the UE can trigger the state transition procedure to connected state.
  • the UE can then, at 480, receive DL data and send UL feedback in connected state.
  • Figure 5 illustrates mobile terminated data notification and transmission, according to certain embodiments.
  • the signal flow illustrated in Figure 5 may be applicable to case 2.
  • the serving gNB may not initially know the exact location of the UE within the RAN based notification area and may need to page the UE to get the UE’s location when MT data arrives for the UE.
  • a gNB can notify a UE about MT data by downlink control channel addressed by P-RNTI, (aseparate P-RNTI may be applied for the UEs in inactive state) .
  • the paging message scheduled may indicate a request for state transition.
  • the paging message scheduled may also indicate the contention based (CB) or grant free resource (for example, preamble and/or time/frequency domain resource) for subsequent UL data transmission. If such information is absent, the UE can select a CB or grant free resource from a preconfigured resource pool.
  • CB contention based
  • grant free resource for example, preamble and/or time/frequency domain resource
  • the UE can send the UE’s UE identifier allocated when moving to inactive state. Then, at 3, the gNB can send feedback for the received UL data, which may contains the TA value. Then, at 4, the UE can start monitoring the downlink control channel for the DL data. Furthermore, at 5, the UE can send the A/N feedback for the received data from the common uplink control channel.
  • the UE can initiate the state transition procedure. Then, at 3A, the UE can start the normal DL data reception and UL feedback transmission after entering in connected state.
  • Figure 6 illustrates a flow chart of user equipment behavior for receiving mobile terminated data, according to certain embodiments.
  • Figure 6 illustrates an approach that may be suitable for case 2.
  • the UE can monitor a downlink control channel addressed by P-RNTI for a PO derived from a paging cycle. Then, at 615, the UE can decode a paging message scheduled by the downlink control channel. At 620, the UE can determine whether a contention based (CB) or grant free resource is indicated in the paging message. If so, then the UE can apply, at 625, the CB or grant free resource indicated by the gNB. Otherwise, at 630, the UE can select a CB or grant free resource from a preconfigured resource pool.
  • CB contention based
  • the UE can determine whether the gNB has requested that the UE undergo a state transition. If not, then the UE can send a UE identifier at 640. The UE can then, at 645, monitor the downlink control channel addressed by C-RNTI corresponding to the UE and can decode the DL from the downlink data channel scheduled by downlink control channel. At 650, the UE can send UL A/N feedback using a common uplink control channel resource. The process can then end at 655.
  • the UE can trigger a state transition procedure to connected state. Then, at 665, the UE can receive DL data and send UL feedback in connected state.
  • Figure 7 illustrates a method according to certain embodiments.
  • the method illustrated in Figure 7 can broadly relate to any of the previously discussed methods, including those illustrated in Figures 4 and 6 and can be variously implemented, such as by the signal flows illustrated in Figures 2, 3, and 5.
  • the method can utilize a physical uplink channel having the characteristics illustrated in Figure 1.
  • the method can include, at 710, determining a user equipment’s location. This can be performed by an access node, such as an evolved Node B, a gNB, a base station, or the like.
  • the method can also include, at 720, sending mobile terminated data from a paging occasion to the user equipment at the determined location scheduled by a downlink control channel while the user equipment is in inactive mode.
  • the method can further include, at 730, including an indication for the user equipment to transition from inactive mode to connected mode.
  • This indication can be provided with the mobile terminated data or optionally, this can be done before or after the mobile terminated data is provided. In case this is done before the mobile terminated data is provided.
  • the indication can be carried in the downlink control channel, with the mobile terminated data, and/or in a paging message.
  • the method can further include, at 731, including an indication of physical resources for a user equipment identifier transmission. The indication can be carried in the downlink control channel or in the paging message.
  • the method can additionally include, at 740, receiving an identifier from the user equipment. This can be a RNTI associated with the user equipment.
  • the method can also include, at 750, sending a timing advance value to the user equipment in response.
  • the timing advance value can be configured to permit the user equipment to reach uplink synchronization, prior to the sending of the mobile terminated data.
  • the method can include, at 760, initiating a paging procedure to the user equipment to determine the user equipment’s location, prior to sending the mobile terminated data. This can be done, for example, in case 2 or other cases in which the gNB does not already know the location of the user equipment.
  • an uplink control channel resource can be allocated specifically for devices in inactive mode. This dedicated resource can be separate from the resources for connected mode devices.
  • the above-described steps can, as mentioned, be performed by a device such as a gNB.
  • the method can also include steps performed by a terminal device, such as a user equipment, which may be a machine-type communication device.
  • the method can, for example, include at 715, detecting, by a user equipment, a downlink control channel addressed by a stored identifier at a paging occasion.
  • the method can also include, at 725, decoding, by the user equipment, downlink data from the downlink control channel while in inactive state.
  • the downlink data can be at the same paging occasion or at a subsequent paging occasion.
  • the downlink data can be provided in a portion of a downlink control channel that is identified by downlink control information.
  • the method can also include, at 735, sending, by the user equipment, acknowledgement feedback for the downlink data via a common uplink control channel or a dedicated uplink control channel.
  • the selection of how to send feedback can depend on whether the information from the gNB identifies the resource (s) for feedback and/or whether the UE is in uplink synchronization with the gNB.
  • the gNB can receive the feedback at 770.
  • the method can additionally include, at 745, transmitting, by the user equipment, an identifier allocated to the user equipment when the user equipment transitioned to inactive state.
  • the identifier can be transmitted in response to the detected downlink control channel addressed by the stored identifier. This can be the same identifier received at 740.
  • the method can also include, at 755, receiving a response from an access node, the response including a timing advance value configured to enable uplink synchronization between the user equipment and the access node. This can be the same TA value sent at 750.
  • the decoding and/or the sending the acknowledgment feedback can follow the uplink synchronization.
  • the stored identifier can be at least one of a cell radio network temporary identifier, a paging radio network temporary identifier of the user equipment, or a paging radio network temporary identifier of one or more devices in inactive state.
  • Figure 8 illustrates a system according to certain embodiments of the invention. It should be understood that each block of the flowchart of Figure 7 may be implemented by various means or their combinations, such as hardware, software, firmware, one or more processors and/or circuitry.
  • a system may include several devices, such as, for example, network element 810 and user equipment (UE) or user device 820.
  • the system may include more than one UE 820 and more than one network element 810, although only one of each is shown for the purposes of illustration.
  • a network element can be an access point, a base station, an eNode B (eNB) , a gNB, or any other network element.
  • eNB eNode B
  • Each of these devices may include at least one processor or control unit or module, respectively indicated as 814 and 824.
  • At least one memory may be provided in each device, and indicated as 815 and 825, respectively.
  • the memory may include computer program instructions or computer code contained therein, for example for carrying out the embodiments described above.
  • One or more transceiver 816 and 826 may be provided, and each device may also include an antenna, respectively illustrated as 817 and 827. Although only one antenna each is shown, many antennas and multiple antenna elements may be provided to each of the devices. Other configurations of these devices, for example, may be provided.
  • network element 810 and UE 820 may be additionally configured for wired communication, in addition to wireless communication, and in such a case antennas 817 and 827 may illustrate any form of communication hardware, without being limited to merely an antenna.
  • Transceivers 816 and 826 may each, independently, be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.
  • the transmitter and/or receiver (as far as radio parts are concerned) may also be implemented as a remote radio head which is not located in the device itself, but in a mast, for example.
  • the operations and functionalities may be performed in different entities, such as nodes, hosts or servers, in a flexible manner. In other words, division of labor may vary case by case.
  • One possible use is to make a network element to deliver local content.
  • One or more functionalities may also be implemented as a virtual application that is provided as software that can run on a server.
  • a user device or user equipment 820 may be a mobile station (MS) such as a mobile phone or smart phone or multimedia device, a computer, such as a tablet, provided with wireless communication capabilities, personal data or digital assistant (PDA) provided with wireless communication capabilities, vehicle, portable media player, digital camera, pocket video camera, navigation unit provided with wireless communication capabilities or any combinations thereof.
  • MS mobile station
  • PDA personal data or digital assistant
  • the user device or user equipment 820 may be a sensor or smart meter, or other device that may usually be configured for a single location.
  • an apparatus such as a node or user device, may include means for carrying out embodiments described above in relation to Figures 1 through 7.
  • Processors 814 and 824 may be embodied by any computational or data processing device, such as a central processing unit (CPU) , digital signal processor (DSP) , application specific integrated circuit (ASIC) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , digitally enhanced circuits, or comparable device or a combination thereof.
  • the processors may be implemented as a single controller, or a plurality of controllers or processors. Additionally, the processors may be implemented as a pool of processors in a local configuration, in a cloud configuration, or in a combination thereof.
  • the term circuitry may refer to one or more electric or electronic circuits.
  • processor may refer to circuitry, such as logic circuitry, that responds to and processes instructions that drive a computer.
  • the implementation may include modules or units of at least one chip set (e.g., procedures, functions, and so on) .
  • Memories 815 and 825 may independently be any suitable storage device, such as a non-transitory computer-readable medium.
  • a hard disk drive (HDD) random access memory (RAM) , flash memory, or other suitable memory may be used.
  • the memories may be combined on a single integrated circuit as the processor, or may be separate therefrom.
  • the computer program instructions may be stored in the memory and which may be processed by the processors can be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.
  • the memory or data storage entity is typically internal but may also be external or a combination thereof, such as in the case when additional memory capacity is obtained from a service provider.
  • the memory may be fixed or removable.
  • a non-transitory computer-readable medium may be encoded with computer instructions or one or more computer program (such as added or updated software routine, applet or macro) that, when executed in hardware, may perform a process such as one of the processes described herein.
  • Computer programs may be coded by a programming language, which may be a high-level programming language, such as objective-C, C, C++, C#, Java, etc., or a low-level programming language, such as a machine language, or assembler. Alternatively, certain embodiments of the invention may be performed entirely in hardware.
  • Figure 8 illustrates a system including a network element 810 and a UE 820
  • embodiments of the invention may be applicable to other configurations, and configurations involving additional elements, as illustrated and discussed herein.
  • multiple user equipment devices and multiple network elements may be present, or other nodes providing similar functionality, such as nodes that combine the functionality of a user equipment and an access point, such as a relay node.
  • Certain embodiments may have various benefits and/or advantages. For example, certain embodiments may provide solutions for fast MT data reception/transmission considering different RAN deployments. Moreover, certain embodiments may reduce latency for MT data transmission and may reduce signaling overhead. In addition, with the dedicated uplink control channel in inactive state, the interference among the UEs which have different UL synchronization status could be avoided to improve the uplink performance.

Landscapes

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

Abstract

Divers systèmes de communication peuvent bénéficier de la gestion appropriée de données qui doivent être transmises à un dispositif terminal. Par exemple, certains systèmes de communication sans fil peuvent bénéficier d'une gestion à terminaison mobile lorsqu'un équipement d'utilisateur est dans un état inactif. Un procédé peut consister à déterminer l'emplacement d'un équipement utilisateur. Le procédé peut également consister à envoyer des données à terminaison mobile d'une occasion de radiomessagerie à l'équipement utilisateur à l'emplacement déterminé planifiées par un canal de commande de liaison descendante tandis que l'équipement utilisateur est en mode inactif.
PCT/CN2017/070314 2017-01-05 2017-01-05 Traitement de données à terminaison mobile dans un état inactif WO2018126406A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/070314 WO2018126406A1 (fr) 2017-01-05 2017-01-05 Traitement de données à terminaison mobile dans un état inactif

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/070314 WO2018126406A1 (fr) 2017-01-05 2017-01-05 Traitement de données à terminaison mobile dans un état inactif

Publications (1)

Publication Number Publication Date
WO2018126406A1 true WO2018126406A1 (fr) 2018-07-12

Family

ID=62788884

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/070314 WO2018126406A1 (fr) 2017-01-05 2017-01-05 Traitement de données à terminaison mobile dans un état inactif

Country Status (1)

Country Link
WO (1) WO2018126406A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011101026A1 (fr) * 2010-02-17 2011-08-25 Nokia Siemens Networks Oy Minimisation des tests de couverture dans un réseau de communication mobile
WO2012058797A1 (fr) * 2010-11-02 2012-05-10 华为技术有限公司 Procédé, dispositif et terminal mobile pour la transmission de données
WO2013038391A1 (fr) * 2011-09-16 2013-03-21 Telefonaktiebolaget L M Ericsson (Publ) Procédé d'accès système optimisé
EP2830338A1 (fr) * 2012-03-23 2015-01-28 NEC Corporation Serveur d'abonnés, serveur de surveillance, terminal mobile, procédé correspondant, et support lisible par un ordinateur
CN104717725A (zh) * 2013-12-12 2015-06-17 展讯通信（上海）有限公司 一种lte系统非连续接收模式下的同步方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011101026A1 (fr) * 2010-02-17 2011-08-25 Nokia Siemens Networks Oy Minimisation des tests de couverture dans un réseau de communication mobile
WO2012058797A1 (fr) * 2010-11-02 2012-05-10 华为技术有限公司 Procédé, dispositif et terminal mobile pour la transmission de données
WO2013038391A1 (fr) * 2011-09-16 2013-03-21 Telefonaktiebolaget L M Ericsson (Publ) Procédé d'accès système optimisé
EP2830338A1 (fr) * 2012-03-23 2015-01-28 NEC Corporation Serveur d'abonnés, serveur de surveillance, terminal mobile, procédé correspondant, et support lisible par un ordinateur
CN104717725A (zh) * 2013-12-12 2015-06-17 展讯通信（上海）有限公司 一种lte系统非连续接收模式下的同步方法

Similar Documents

Publication Publication Date Title
US11751245B2 (en) Method and wireless communication system for handling timer operation
US11889565B2 (en) Method and system for handling random access response in wireless communication system
US11523433B2 (en) System and method of handling bandwidth part inactivity timer
US11818080B2 (en) Random access with bandwidth part switch
EP3536110B1 (fr) Procédure d'accès aléatoire en deux étapes
KR102304205B1 (ko) Mtc를 위한 반복된 전송의 조기 종료
CN106028464B (zh) 高效率分布式设备对设备(d2d)信道接入
CN111247845A (zh) NB-IoT中用于在预配置的UL资源中进行传送的定时提前验证
US20210235506A1 (en) Information processing method and apparatus
KR20220089705A (ko) 정보 지시 방법 및 장치
CN109587766B (zh) 按需系统信息请求响应、接收方法及装置、基站
US11672014B2 (en) Transmission of a short contention resolution identifier
EP2897388B1 (fr) Support de puissance efficace de transmission de paquets de petites tailles
CN113424594A (zh) 一种信息发送方法及装置
JP2023543071A (ja) 端末装置、ネットワーク装置及び通信の方法
KR20230135677A (ko) 무선 통신 시스템에서 스몰 데이터 전송을 처리하기 위한 방법 및 장치
WO2018126406A1 (fr) Traitement de données à terminaison mobile dans un état inactif
US20240008090A1 (en) Uplink control information (uci) multiplexed in uplink message with uplink message repetition
JP2024518669A (ja) Ｓｄｔを用いるオンデマンドｓｉｂの配信
JP2022115997A (ja) 帯域幅部切替えによるランダムアクセス
US20160080971A1 (en) Multicast paging message for indicating proprietary protocol support

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

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

Country of ref document: EP

Kind code of ref document: A1