WO2022241682A1 - Method, device and computer program product for wireless communication - Google Patents

Method, device and computer program product for wireless communication Download PDF

Info

Publication number
WO2022241682A1
WO2022241682A1 PCT/CN2021/094686 CN2021094686W WO2022241682A1 WO 2022241682 A1 WO2022241682 A1 WO 2022241682A1 CN 2021094686 W CN2021094686 W CN 2021094686W WO 2022241682 A1 WO2022241682 A1 WO 2022241682A1
Authority
WO
WIPO (PCT)
Prior art keywords
wireless communication
sdt
communication node
notification message
message
Prior art date
Application number
PCT/CN2021/094686
Other languages
English (en)
French (fr)
Inventor
Zijiang Ma
Yin Gao
Yingjun Zhou
Original Assignee
Zte Corporation
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 Zte Corporation filed Critical Zte Corporation
Priority to EP21930625.5A priority Critical patent/EP4115696A4/de
Priority to CN202180016370.2A priority patent/CN115643825A/zh
Priority to PCT/CN2021/094686 priority patent/WO2022241682A1/en
Publication of WO2022241682A1 publication Critical patent/WO2022241682A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This document is directed generally to wireless communications.
  • UEs In New Radio (NR) of 5G communication, UEs (user equipments) can enter an RRC_INACTIVE state/mode to reduce power consumption. Typically, in the RRC_INACTIVE state, a UE cannot transmit data. Thus, the UE has to resume connections (i.e., switch back to the RRC_CONNECTED state) for the downlink (e.g., mobile termination (MT) ) and uplink (e.g., mobile originated (MO) ) data.
  • MT mobile termination
  • MO mobile originated
  • Signaling overhead caused by small data transmission of UEs in the RRC_INACTIVE state can be a severe problem when there are a lot of UEs in a NR system. Signaling overhead may influent not only performance and efficiency of the network, but also battery performance of the UEs.
  • a UE is allowed to stay in the RRC_INACTIVE state and send uplink (UL) user data or receive downlink (DL) user data when the UL or DL user data is SDT (small data transmission) data.
  • UL uplink
  • DL downlink
  • the present disclosure provides a method for keeping a UE in an RRC_INACTIVE state performing SDT.
  • the present disclosure relates to methods, devices, and computer program products for wireless communication for SDT.
  • the wireless communication method includes: transmitting, by a first wireless communication node to a second wireless communication node, a first message comprising a first indicator to instruct the second wireless communication node handling small data transmission, SDT, in which the first indicator indicates one or more SDT bearers are resumed.
  • the wireless communication method includes receiving, by a second wireless communication node from a first wireless communication node, a first message comprising a first indicator to handle small data transmission, SDT, in which the first indicator indicates one or more SDT bearers are resumed.
  • the wireless communication node includes a communication unit and a processor.
  • the processor is configured to: transmit, to a second wireless communication node, a first message comprising a first indicator to instruct the second wireless communication node handling small data transmission, SDT, wherein the first indicator indicates one or more SDT bearers are resumed.
  • the wireless communication node includes a communication unit and a processor.
  • the processor is configured to receive, from a first wireless communication node, a first message comprising a first indicator to handle small data transmission, SDT, wherein the first indicator indicates one or more SDT bearers are resumed.
  • the first wireless communication node is configured to transmit a second message comprising a second indicator to instruct the second wireless communication node stopping handling SDT, wherein the second indicator indicates the one or more SDT bearers are suspended.
  • At least one of the first message and the second message is a bearer context modification request message or a bearer context setup request message.
  • the first wireless communication node is configured to receive an SDT notification message from the second wireless communication node and resume the one or more SDT bearers according to the SDT notification message.
  • the first wireless communication node is configured to keep one or more non-SDT bearers suspended according to the SDT notification message.
  • the first wireless communication node is configured to keep a Radio Resource Control, RRC, state of a wireless communication terminal in an inactive state according to the SDT notification message.
  • RRC Radio Resource Control
  • the SDT notification message is an uplink data notification message or a downlink data notification message with an SDT data indicator.
  • the first wireless communication node is configured to receive an SDT inactivity notification message and suspend the one or more SDT bearers according to the SDT inactivity notification message.
  • the first wireless communication node is configured to keep an RRC state of a wireless communication terminal in an inactive state according to the SDT inactivity notification message.
  • the SDT inactivity notification message is a bearer context inactivity notification message with inactivity monitoring results.
  • the second wireless communication node is configured to receive a second message comprising a second indicator to suspend the one or more SDT bearer.
  • the second wireless communication node is configured to transmit an SDT notification message to the first wireless communication node to inform the first wireless communication node resuming the one or more SDT bearers.
  • the second wireless communication node is configured to transmit the SDT notification message to the first wireless communication node to request the first wireless communication node to keep one or more non-SDT bearers suspended.
  • the first wireless communication node is configured to keep a Radio Resource Control, RRC, state of a wireless communication terminal in an inactive state according to the SDT notification message.
  • RRC Radio Resource Control
  • the second wireless communication node is configured to transmit an SDT inactivity notification message to the first wireless communication node to request the first wireless communication node suspend the one or more SDT bearers.
  • the second wireless communication node is configured to transmit the SDT inactivity notification message to the first wireless communication node to request the first wireless communication node to keep an RRC state of a wireless communication terminal in an inactive state.
  • the present disclosure relates to a computer program product including a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement a wireless communication method recited in any one of foregoing methods.
  • the present disclosure is not limited to the exemplary embodiments and applications described and illustrated herein. Additionally, the specific order and/or hierarchy of steps in the methods disclosed herein are merely exemplary approaches. Based upon design preferences, the specific order or hierarchy of steps of the disclosed methods or processes can be re-arranged while remaining within the scope of the present disclosure. Thus, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or acts in a sample order, and the present disclosure is not limited to the specific order or hierarchy presented unless expressly stated otherwise.
  • FIGs. 1A and 1B show a schematic diagram of a procedure to perform SDT according to an embodiment of the present disclosure.
  • FIG. 2 shows an example of a schematic diagram of a wireless communication node according to an embodiment of the present disclosure.
  • FIG. 3 shows an example of a schematic diagram of another wireless communication node according to another embodiment of the present disclosure.
  • FIG. 4 shows a flowchart of a wireless communication method according to an embodiment of the present disclosure.
  • FIG. 5 shows a flowchart of another wireless communication method according to an embodiment of the present disclosure.
  • an indicator can be introduced in one or more messages from a gNB-CU-CP (gNodeB-Control unit-Control plane) to a gNB-CU-CP (gNodeB-Control unit-User plane) , to indicate whether one or more SDT bearers (also referred to as SDT bearer contexts) are suspended or resumed.
  • the indicator may be a Suspend indicator or a Resume indicator in a new information element (IE) , such as “SDT Bearer Context Status Change” IE.
  • IE new information element
  • the SDT Bearer Context Status Change IE may be illustrated as the table shown below.
  • the indicator may be contained in a message related to a bearer context. In an embodiment, the indicator may be contained in at least one of the Bearer context setup request message or the Bearer context modification request message provided from a gNB-CU-CP to a gNB-CU-UP.
  • the gNB-CU-UP may handle SDT user data.
  • the SDT Bearer Context Status Change IE is set as “suspend” (i.e., a Suspend indicator) and is contained in the Bearer context setup request message or the Bearer context modification request message, the gNB-CU-UP may stop handling the SDT user data.
  • an indicator may be introduced in one or more messages provided from the gNB-CU-UP to the gNB-CU-CP, to indicate that the coming user data is SDT data.
  • the one or more messages can be at least one of the UL Data Notification message or the DL Data Notification message.
  • another new IE such as SDT data IE, can be taken as the indicator.
  • the gNB-CU-CP may resume the one or more SDT bearers if they are suspended, not resume the other bearers, and keep radio resource control (RRC) of a corresponding UE in an RRC_INACTIVE state.
  • RRC radio resource control
  • the gNB-CU-CP may resume all the bearers and/or change the corresponding UE to an RRC_CONNECTED state.
  • bearers of the UE including one or more SDT bearers and non-SDT bearers are setup and suspended, and the UE is in the RRC_INACTIVE state.
  • the gNB-CU-UP sends a UL Data Notification message or a DL Data Notification message including the SDT data IE to the gNB-CU-CP in response to the gNB-CU-UP receiving UL or DL SDT user data.
  • the gNB-CU-UP sends a Bearer Context Inactivity Notification message to the gNB-CU-CP, in which the Bearer Context Inactivity Notification message includes an SDT bearer monitoring result indicating that the SDT bearers are active.
  • the gNB-CU-CP determines to keep the UE in the RRC_INACTIVE state, resume the one or more SDT bearers, and keep suspending non-SDT bearers according the UL Data Notification message or the DL Data Notification message including the SDT data IE from the gNB-CU-UP.
  • the gNB-CU-CP sends a Bearer context modification request message including the SDT Bearer Context Status Change IE with a Resume indicator to the gNB-CU-UP, to indicate the one or more SDT bearers are resumed.
  • the gNB-CU-UP sends a Bearer context modification response message to the gNB-CU-CP.
  • the gNB-CU-UP handles UL or DL SDT data. In some embodiments, this operation may be omitted if no UL or DL SDT data is received.
  • the gNB-CU-UP monitors the UL or DL SDT data. If the gNB-CU-UP determines that no further UL or DL SDT data is expected or transmitted for a period of time, the gNB-CU-UP sends a Bearer context inactivity notification message with inactivity monitoring results to the gNB-CU-CP.
  • the gNB-CU-UP if the gNB-CU-UP receives non-SDT user data, the gNB-CU-UP sends a UL Data Notification message or a DL Data Notification message without the the SDT data IE to the gNB-CU-CP, so that the gNB-CU-CP can change the RRC state of the UE to an RRC_CONNECTED mode and resume all the bearers, including SDT bearer (s) and non-SDT bearer (s) .
  • the gNB-CU-CP keeps the UE in the RRC_INACTIVE mode and suspends the one or more SDT bearers.
  • the gNB-CU-CP sends an F1AP message (e.g., a UE CONTEXT RELEASE COMMAND message) with an RRCRelease message to a gNodeB-data unit (gNB-DU) serving the UE.
  • the gNB-DU forwards the RRCRelease message to the UE.
  • the gNB-CU-CP sends a Bearer context modification request message including an SDT Bearer Context Status Change IE with a Suspend indicator to the gNB-CU-UP.
  • the gNB-CU-UP sends a Bearer context modification response message to the gNB-CU-CP.
  • operations 8 and 9 and operations 10 and 11 may be performed simultaneously or the execution times thereof may at least partially overlap. In some embodiments, operations 8 and 9 may be performed before or after operations 10 and 11.
  • bearers of the UE including one or more SDT bearers and non-SDT bearers are setup and suspended, and the UE is in the RRC_INACTIVE state.
  • the gNB-CU-CP receives a UL Data Notification message or a DL Data Notification message including the SDT data IE from the gNB-CU-UP.
  • the gNB-CU-CP determines to keep the UE in the RRC_INACTIVE state and to resume one or more SDT bearers according the UL Data Notification message or the DL Data Notification message including the SDT data IE from the gNB-CU-UP.
  • the gNB-CU-CP sends a Bearer context modification request message including the SDT Bearer Context Status Change IE with a Resume indicator to the gNB-CU-UP, to indicate the one or more SDT bearers are resumed.
  • the gNB-CU-CP receives a Bearer context modification response message from the gNB-CU-UP.
  • the gNB-CU-CP receives a Bearer context inactivity notification message with inactivity monitoring results from the gNB-CU-UP.
  • the gNB-CU-CP receives a UL Data Notification message or a DL Data Notification message from the gNB-CU-UP, and changes the RRC state of the UE to an RRC_CONNECTED mode and resumes all the bearers, including SDT bearer (s) and non-SDT bearer (s) according to the UL Data Notification message or the DL Data Notification message.
  • the gNB-CU-CP keeps the UE in the RRC_INACTIVE mode and suspends the one or more SDT bearers.
  • the gNB-CU-CP sends an F1AP message (e.g., a UE CONTEXT RELEASE COMMAND message) with an RRCRelease message for the UE to the gNB-DU serving the UE.
  • F1AP message e.g., a UE CONTEXT RELEASE COMMAND message
  • the gNB-CU-CP sends a Bearer context modification request message including an SDT Bearer Context Status Change IE with a Suspend indicator to the gNB-CU-UP, and receives a Bearer context modification response message from the gNB-CU-UP.
  • operations 7 and 8 may be performed simultaneously or the execution time thereof may at least partially overlap. In some embodiments, operation 7 may be performed before or after operation 8.
  • bearers of the UE including one or more SDT bearers and non-SDT bearers are setup and suspended, and the UE is in the RRC_INACTIVE state.
  • the gNB-CU-UP sends a UL Data Notification message or a DL Data Notification message including the SDT data IE to the gNB-CU-CP in response to the gNB-CU-UP receiving UL or DL SDT user data.
  • the gNB-CU-UP receives a Bearer context modification request message including the SDT Bearer Context Status Change IE with a Resume indicator from the gNB-CU-CP, to indicate that the one or more SDT bearers are resumed.
  • the gNB-CU-UP sends a Bearer context modification response message to the gNB-CU-CP.
  • the gNB-CU-UP handles UL or DL SDT data. In some embodiments, this operation may be omitted if no UL and/or DL SDT data is received.
  • the gNB-CU-UP monitors the UL or DL SDT data. If the gNB-CU-UP determines that no further UL and/or DL SDT data is expected or transmitted for a period of time, the gNB-CU-UP sends a Bearer context inactivity notification message with inactivity monitoring results to the gNB-CU-CP.
  • the gNB-CU-UP if the gNB-CU-UP receives non-SDT user data, the gNB-CU-UP sends a UL Data Notification message or a DL Data Notification message without the SDT data IE to the gNB-CU-CP, so that the gNB-CU-CP may change the RRC state of the UE to an RRC_CONNECTED mode and resume all the bearers including SDT bearer (s) and non-SDT bearer (s) .
  • the gNB-CU-UP receives a Bearer context modification request message including an SDT Bearer Context Status Change IE with a Suspend indicator from the gNB-CU-UP.
  • the gNB-CU-UP sends a Bearer context modification response message to the gNB-CU-CP.
  • an IE e.g., the SDT Bearer Context Status Change IE with a value of “resume” or “suspend”
  • the Bearer context modification request message and/or the Bearer context setup request message is included in the Bearer context modification request message and/or the Bearer context setup request message.
  • an IE (e.g., the SDT data IE) is included in the UL Data Notification message and/or the DL Data Notification message.
  • the gNB-CU-CP may decide to keep the UE in the RRC_INACTIVE state/mode, and to resume the SDT bearer (s) .
  • the gNB-CU-CP may resume the SDT bearer (s) , keep suspending non-SDT bearer (s) , and handle SDT data.
  • FIG. 2 relates to a schematic diagram of a wireless communication node 40 (e.g., a network device) according to an embodiment of the present disclosure.
  • the wireless communication node 40 may be a satellite, a base station (BS) (e.g., a gNB or a gNB-CU-CP) , a network entity, a Mobility Management Entity (MME) , Serving Gateway (S-GW) , Packet Data Network (PDN) Gateway (P-GW) , a radio access network (RAN) , a next generation RAN (NG-RAN) , a data network, a core network or a Radio Network Controller (RNC) , and is not limited herein.
  • BS base station
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • RAN radio access network
  • NG-RAN next generation RAN
  • RNC Radio Network Controller
  • the wireless communication node 40 may include (perform) at least one network function such as an access and mobility management function (AMF) , a session management function (SMF) , a user place function (UPF) , a policy control function (PCF) , an application function (AF) , etc.
  • the wireless communication node 40 may include a processor 400 such as a microprocessor or ASIC, a storage unit 410 and a communication unit 420.
  • the storage unit 410 may be any data storage device that stores a program code 412, which is accessed and executed by the processor 400. Examples of the storage unit 412 include but are not limited to a SIM, ROM, flash memory, RAM, hard-disk, and optical data storage device.
  • the communication unit 420 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 400.
  • the communication unit 420 transmits and receives the signals via at least one antenna 422.
  • the storage unit 410 and the program code 412 may be omitted.
  • the processor 400 may include a storage unit with stored program code.
  • the processor 400 may implement any steps described in exemplified embodiments on the wireless communication node 40, e.g., via executing the program code 412.
  • the communication unit 420 may be a transceiver.
  • the communication unit 420 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals, messages, or information to and from a wireless node (e.g., a gNB-CU-UP or a gNB-DU) .
  • a wireless node e.g., a gNB-CU-UP or a gNB-DU
  • the wireless communication node 40 may be used to perform the operations of the gNB-CU-CP described above.
  • the processor 400 and the communication unit 420 collaboratively perform the operations described above. For example, the processor 400 performs operations and transmit or receive signals through the communication unit 420.
  • FIG. 3 relates to a schematic diagram of a wireless communication node 50 (e.g., a network device) according to an embodiment of the present disclosure.
  • the wireless communication node 50 may be a satellite, a base station (BS) (e.g., a gNB or a gNB-CU-UP) , a network entity, a Mobility Management Entity (MME) , Serving Gateway (S-GW) , Packet Data Network (PDN) Gateway (P-GW) , a radio access network (RAN) , a next generation RAN (NG-RAN) , a data network, a core network or a Radio Network Controller (RNC) , and is not limited herein.
  • BS base station
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • PDN Packet Data Network Gateway
  • RAN radio access network
  • NG-RAN next generation RAN
  • RNC Radio Network Controller
  • the wireless communication node 50 may include (perform) at least one network function such as an access and mobility management function (AMF) , a session management function (SMF) , a user place function (UPF) , a policy control function (PCF) , an application function (AF) , etc.
  • the wireless communication node 50 may include a processor 500 such as a microprocessor or ASIC, a storage unit 510 and a communication unit 520.
  • the storage unit 510 may be any data storage device that stores a program code 512, which is accessed and executed by the processor 500. Examples of the storage unit 512 include but are not limited to a SIM, ROM, flash memory, RAM, hard-disk, and optical data storage device.
  • the communication unit 520 may be a transceiver and is used to transmit and receive signals (e.g., messages or packets) according to processing results of the processor 500.
  • the communication unit 520 transmits and receives the signals via at least one antenna 522.
  • the storage unit 510 and the program code 512 may be omitted.
  • the processor 500 may include a storage unit with stored program code.
  • the processor 500 may implement any steps described in exemplified embodiments on the wireless communication node 50, e.g., via executing the program code 512.
  • the communication unit 520 may be a transceiver.
  • the communication unit 520 may as an alternative or in addition be combining a transmitting unit and a receiving unit configured to transmit and to receive, respectively, signals, messages, or information to and from a wireless node (e.g., a gNB-CU-CP or a gNB-DU) .
  • a wireless node e.g., a gNB-CU-CP or a gNB-DU
  • the wireless communication node 50 may be used to perform the operations of the gNB-CU-UP described above.
  • the processor 500 and the communication unit 520 collaboratively perform the operations described above. For example, the processor 500 performs operations and transmit or receive signals through the communication unit 520.
  • a wireless communication method is also provided according to an embodiment of the present disclosure.
  • the wireless communication method may be performed by using a wireless communication node (e.g., a gNB-CU-CP) .
  • the wireless communication terminal may be implemented by using the wireless communication terminal 40 described above, but is not limited thereto.
  • the wireless communication method includes: transmitting, by a first wireless communication node to a second wireless communication node, a first message comprising a first indicator to instruct the second wireless communication node handling small data transmission, SDT, in which the first indicator indicates one or more SDT bearers are resumed.
  • the first wireless communication node may be the gNB-CU-CP described above, and the second wireless communication node may be the gNB-CU-UP described above.
  • the first message may be the Bearer context setup request message or the Bearer context modification request message described above, and the first indicator may be the Resume indicator described above.
  • the first wireless communication node is configured to transmit a second message comprising a second indicator to instruct the second wireless communication node stopping handling SDT, wherein the second indicator indicates the one or more SDT bearers are suspended.
  • the second message may be the Bearer context setup request message or the Bearer context modification request message described above, and the second indicator may be the Suspend indicator described above.
  • the first wireless communication node is configured to receive an SDT notification message from the second wireless communication node and resume the one or more SDT bearers according to the SDT notification message.
  • the SDT notification message is the UL Data Notification message or the DL Data Notification message with the SDT data indicator.
  • the first wireless communication node is configured to keep one or more non-SDT bearers suspended according to the SDT notification message.
  • the first wireless communication node is configured to keep a Radio Resource Control, RRC, state of a wireless communication terminal (e.g., the UE described above) in an inactive state (e.g., an RRC_INACTIVE mode) according to the SDT notification message.
  • RRC Radio Resource Control
  • the first wireless communication node is configured to receive an SDT inactivity notification message and suspend the one or more SDT bearers according to the SDT inactivity notification message.
  • the SDT inactivity notification message is the Bearer context inactivity notification message with inactivity monitoring results described above.
  • the first wireless communication node is configured to keep an RRC state of a wireless communication terminal (e.g., the UE described above) in an inactive state (e.g., an RRC_INACTIVE mode) according to the SDT inactivity notification message.
  • a wireless communication terminal e.g., the UE described above
  • an inactive state e.g., an RRC_INACTIVE mode
  • the wireless communication method may be performed by using a wireless communication node (e.g., a gNB-CU-UP) .
  • the wireless communication node may be implemented by using the wireless communication node 50 described above, but is not limited thereto.
  • the wireless communication method includes: receiving, by a second wireless communication node from a first wireless communication node, a first message comprising a first indicator to handle small data transmission, SDT, in which the first indicator indicates one or more SDT bearers are resumed.
  • the first wireless communication node may be the gNB-CU-CP described above, and the second wireless communication node may be the gNB-CU-UP described above.
  • the first message may be the Bearer context setup request message or the Bearer context modification request message described above, and the first indicator may be the Resume indicator described above.
  • any reference to an element herein using a designation such as “first, “ “second, “ and so forth does not generally limit the quantity or order of those elements. Rather, these designations can be used herein as a convenient means of distinguishing between two or more elements or instances of an element. Thus, a reference to first and second elements does not mean that only two elements can be employed, or that the first element must precede the second element in some manner.
  • any one of the various illustrative logical blocks, units, processors, means, circuits, methods and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two) , firmware, various forms of program or design code incorporating instructions (which can be referred to herein, for convenience, as "software” or a “software unit” ) , or any combination of these techniques.
  • a processor, device, component, circuit, structure, machine, unit, etc. can be configured to perform one or more of the functions described herein.
  • IC integrated circuit
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the logical blocks, units, and circuits can further include antennas and/or transceivers to communicate with various components within the network or within the device.
  • a general purpose processor can be a microprocessor, but in the alternative, the processor can be any conventional processor, controller, or state machine.
  • a processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration to perform the functions described herein. If implemented in software, the functions can be stored as one or more instructions or code on a computer-readable medium. Thus, the steps of a method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium.
  • Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program or code from one place to another.
  • a storage media can be any available media that can be accessed by a computer.
  • such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer.
  • unit refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. Additionally, for purpose of discussion, the various units are described as discrete units; however, as would be apparent to one of ordinary skill in the art, two or more units may be combined to form a single unit that performs the associated functions according embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • memory or other storage may be employed in embodiments of the present disclosure.
  • any suitable distribution of functionality between different functional units, processing logic elements or domains may be used without detracting from the present disclosure.
  • functionality illustrated to be performed by separate processing logic elements, or controllers may be performed by the same processing logic element, or controller.
  • references to specific functional units are only references to a suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
PCT/CN2021/094686 2021-05-19 2021-05-19 Method, device and computer program product for wireless communication WO2022241682A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21930625.5A EP4115696A4 (de) 2021-05-19 2021-05-19 Verfahren, vorrichtung und computerprogrammprodukt zur drahtlosen kommunikation
CN202180016370.2A CN115643825A (zh) 2021-05-19 2021-05-19 用于无线通信的方法、设备和计算机程序产品
PCT/CN2021/094686 WO2022241682A1 (en) 2021-05-19 2021-05-19 Method, device and computer program product for wireless communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/094686 WO2022241682A1 (en) 2021-05-19 2021-05-19 Method, device and computer program product for wireless communication

Publications (1)

Publication Number Publication Date
WO2022241682A1 true WO2022241682A1 (en) 2022-11-24

Family

ID=84140083

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/094686 WO2022241682A1 (en) 2021-05-19 2021-05-19 Method, device and computer program product for wireless communication

Country Status (3)

Country Link
EP (1) EP4115696A4 (de)
CN (1) CN115643825A (de)
WO (1) WO2022241682A1 (de)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110249703A (zh) 2017-02-03 2019-09-17 瑞典爱立信有限公司 无上下文取得的无线电资源控制恢复
CN111373837A (zh) 2018-09-19 2020-07-03 三星电子株式会社 用于在无线通信系统中发送和接收数据的方法和装置
WO2020166817A1 (en) 2019-02-12 2020-08-20 Lg Electronics Inc. Early data transmission in cu-du split
WO2020171369A1 (en) 2019-02-19 2020-08-27 Lg Electronics Inc. Uplink data fast transmission in cu-du split

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110249703A (zh) 2017-02-03 2019-09-17 瑞典爱立信有限公司 无上下文取得的无线电资源控制恢复
CN111373837A (zh) 2018-09-19 2020-07-03 三星电子株式会社 用于在无线通信系统中发送和接收数据的方法和装置
WO2020166817A1 (en) 2019-02-12 2020-08-20 Lg Electronics Inc. Early data transmission in cu-du split
WO2020171369A1 (en) 2019-02-19 2020-08-27 Lg Electronics Inc. Uplink data fast transmission in cu-du split

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NOKIA, NOKIA SHANGHAI BELL: "SDT control plane aspects", 3GPP DRAFT; R2-2103497, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Electronic; 20210412 - 20210420, 1 April 2021 (2021-04-01), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051992108 *
See also references of EP4115696A4
ZTE: "Discussion on SDT with/without UE context relocation", 3GPP DRAFT; R3-210187, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20210125 - 20210204, 15 January 2021 (2021-01-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051974920 *

Also Published As

Publication number Publication date
EP4115696A1 (de) 2023-01-11
EP4115696A4 (de) 2023-09-27
CN115643825A (zh) 2023-01-24

Similar Documents

Publication Publication Date Title
CN109548109B (zh) 一种ue和网络状态不匹配的处理方法及装置、存储介质
CN114900547B (zh) 一种通信方法及装置
US20230337317A1 (en) Method for small data transmission
EP2957135B1 (de) Verfahren und netzwerkknoten zur einstellung eines mobilen kommunikationsendgeräts in einem ruhemodus
JP2018537909A (ja) ユーザ機器、ネットワークノード、及び無線通信方法
US20240031253A1 (en) Method for radio access network visible quality of experience measurement of dual connectivity
EP4082294A1 (de) Verfahren und vorrichtungen zur signalverarbeitung
US20230020986A1 (en) Method, device and computer program product for wireless communication
EP3169090B1 (de) Vorrichtungen und verfahren zur reduzierung von funkruf für mobilstation (ms) mit erweitertem diskontinuierlichem empfang (edrx) zum empfang von an mobiltelefone gerichteten (mt) kurznachrichten (sm)
WO2020073875A1 (zh) 信号传输方法及装置
WO2022241682A1 (en) Method, device and computer program product for wireless communication
WO2022213337A1 (en) Method, device and computer program product for wireless communication
CN110121216B (zh) 会话恢复方法及装置、计算机存储介质
US20230397291A1 (en) Method for small data transmission
WO2023178475A1 (en) Method for extended drx
WO2022227046A1 (en) Method, device and computer program product for wireless communication
WO2022135436A1 (zh) 辅小区组状态信息的通知方法、装置及网络侧设备
WO2023060570A1 (en) Method, device and computer program product for wireless communication
WO2024082150A1 (en) Method, device and computer program product for wireless communication
WO2024011425A1 (en) Method, device and computer program product for wireless communication
US20240179785A1 (en) Method, device and computer program product for wireless communication
EP4190043A1 (de) Planung und übertragung eines systems
CN115136661A (zh) 一种通信方法及装置
CN115707052A (zh) 基于双连接配置的通信方法及相关设备

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2021930625

Country of ref document: EP

Effective date: 20220923

NENP Non-entry into the national phase

Ref country code: DE