WO2022236484A1 - Sdt失败上报的方法、终端设备和网络设备 - Google Patents
Sdt失败上报的方法、终端设备和网络设备 Download PDFInfo
- Publication number
- WO2022236484A1 WO2022236484A1 PCT/CN2021/092425 CN2021092425W WO2022236484A1 WO 2022236484 A1 WO2022236484 A1 WO 2022236484A1 CN 2021092425 W CN2021092425 W CN 2021092425W WO 2022236484 A1 WO2022236484 A1 WO 2022236484A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- sdt
- failure
- cell
- terminal device
- failure information
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 195
- 230000005540 biological transmission Effects 0.000 claims abstract description 80
- 230000008569 process Effects 0.000 claims description 69
- 230000015654 memory Effects 0.000 claims description 56
- 238000004590 computer program Methods 0.000 claims description 42
- 238000011084 recovery Methods 0.000 claims description 26
- 230000001960 triggered effect Effects 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 10
- 230000008859 change Effects 0.000 claims description 8
- 238000004891 communication Methods 0.000 description 53
- 230000006870 function Effects 0.000 description 27
- 238000010586 diagram Methods 0.000 description 16
- 230000004044 response Effects 0.000 description 9
- 230000011664 signaling Effects 0.000 description 8
- 230000001360 synchronised effect Effects 0.000 description 5
- 230000007774 longterm Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000010295 mobile communication Methods 0.000 description 3
- 238000005457 optimization Methods 0.000 description 3
- 101150039363 SIB2 gene Proteins 0.000 description 2
- 238000013475 authorization Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000010365 information processing Effects 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 102100039292 Cbp/p300-interacting transactivator 1 Human genes 0.000 description 1
- 101000888413 Homo sapiens Cbp/p300-interacting transactivator 1 Proteins 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008054 signal transmission Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
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
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04B—TRANSMISSION
- H04B7/00—Radio transmission systems, i.e. using radiation field
- H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
- H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
- H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
- H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
- H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
- H04B7/06952—Selecting one or more beams from a plurality of beams, e.g. beam training, management or sweeping
- H04B7/06964—Re-selection of one or more beams after beam failure
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
-
- 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
-
- 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
- the embodiment of the present application relates to the communication field, and more specifically, relates to a method for reporting an SDT failure, a terminal device, and a network device.
- the network In order to quickly restore the RRC connection, the network usually keeps the UE with infrequent data transmission in the RRC_INACTIVE state. Before Rel-16, a UE in the RRC_INACTIVE state does not support data transmission. When uplink (MO) or downlink (MT) data arrives, the UE needs to restore the connection and release it to the INACTIVE state after the data transmission is completed. For UEs with small amount of data and low transmission frequency, such a transmission mechanism will cause unnecessary power consumption and signaling overhead.
- MO uplink
- MT downlink
- SDT Small Data Transmission
- pre-configured resources such as CG type1
- CG type1 the uplink based on the random access process (two steps/four steps)
- SDT Small Data Transmission and uplink small data transmission based on pre-configured resources (such as CG type1).
- other related schemes for SDT still need to be further improved.
- the embodiment of the present application provides a method for reporting SDT failure, a terminal device, and a network device, which improve related solutions for SDT failure, and can improve the reliability of data transmission.
- the present application provides a method for reporting SDT failure, including:
- the present application provides a method for reporting SDT failure, including:
- the present application provides a terminal device configured to execute the method in the foregoing first aspect or various implementation manners thereof.
- the terminal device includes a functional module configured to execute the method in the foregoing first aspect or its various implementation manners.
- the terminal device may include a processing unit configured to perform functions related to information processing.
- the processing unit may be a processor.
- the network device may include a sending unit and/or a receiving unit.
- the sending unit is used to perform functions related to sending, and the receiving unit is used to perform functions related to receiving.
- the sending unit may be a transmitter or transmitter, and the receiving unit may be a receiver or receiver.
- the network device is a communication chip, the receiving unit may be an input circuit or interface of the communication chip, and the sending unit may be an output circuit or interface of the communication chip.
- the present application provides a terminal device, including a processor and a memory.
- the memory is used to store a computer program
- the processor is used to call and run the computer program stored in the memory, so as to execute the method in the above first aspect or each implementation manner thereof.
- processors there are one or more processors, and one or more memories.
- the memory may be integrated with the processor, or the memory may be separated from the processor.
- processors there are one or more processors, and one or more memories.
- the present application provides a computer-readable storage medium for storing a computer program, and the computer program enables the computer to execute any one of the above-mentioned first to second aspects or the method in each implementation manner thereof .
- Fig. 1 is an example of a communication system provided by an embodiment of the present application.
- Fig. 8 is a schematic block diagram of a chip provided by an embodiment of the present application.
- the embodiment of the present application is only described by using the communication system 100 as an example, but the embodiment of the present application is not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (Long Term Evolution, LTE) system, LTE Time Division Duplex (Time Division Duplex, TDD), Universal Mobile Communication System (Universal Mobile Telecommunication System, UMTS), Internet of Things (Internet of Things, IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system , 5G communication system (also known as New Radio (NR) communication system), or future communication systems, etc.
- LTE Long Term Evolution
- LTE Time Division Duplex Time Division Duplex
- TDD Universal Mobile Communication System
- Universal Mobile Telecommunication System Universal Mobile Telecommunication System
- UMTS Universal Mobile Communication System
- Internet of Things Internet of Things
- NB-IoT Narrow Band Internet of Things
- eMTC enhanced Machine-Type Communications
- the network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a Long Term Evolution (Long Term Evolution, LTE) system, or a Next Generation Radio Access Network (NG RAN) device, Either a base station (gNB) in the NR system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 can be a relay station, an access point, a vehicle-mounted device, a wearable Devices, hubs, switches, bridges, routers, or network devices in the future evolution of the Public Land Mobile Network (Public Land Mobile Network, PLMN), etc.
- Evolutional Node B, eNB or eNodeB in a Long Term Evolution (Long Term Evolution, LTE) system
- NG RAN Next Generation Radio Access Network
- gNB base station
- CRAN Cloud Radio Access Network
- the network device 120 can be a relay station, an access point, a vehicle-mounted device, a wear
- Figure 1 exemplarily shows a base station, a core network device, and two terminal devices.
- the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminals within the coverage area.
- the device is not limited in the embodiment of this application.
- the communication device may include a network device 120 and a terminal device 110 having a communication function, and the network device 120 and the terminal device 110 may be the devices described above, which will not be repeated here;
- the communication device may also include other devices in the communication system 100, such as network controllers, mobility management entities and other network entities, which are not limited in this embodiment of the present application.
- Radio Resource Control Radio Resource Control
- RRC Radio Resource Control
- RRC_IDLE RRC idle state
- RRC_INACTIVE RRC inactive state
- RRC_CONNECTED RRC connected state
- the process 200 may include:
- the network device After receiving Msg 1 sent by the terminal device, the network device sends Msg 2 to the terminal device, that is, a Random Access Response (Random Access Response, RAR) message.
- the Msg 2 may carry, for example, a time advance (Time Advance, TA), an uplink authorization instruction such as configuration of uplink resources, and a Temporary Cell-Radio Network Temporary Identity (Temporary Cell-Radio Network Temporary Identity, TC-RNTI), etc.
- the terminal device monitors the physical downlink control channel (Physical Downlink Control Channel, PDCCH) within the random access response time window (RAR window), so as to receive the RAR message replied by the network device.
- PDCCH Physical Downlink Control Channel
- the RAR message may be descrambled using a corresponding Random Access Radio Network Temporary Identifier (RA-RNTI). If the terminal device does not receive the RAR message replied by the network device within the RAR time window, it considers that the random access procedure has failed. If the terminal device successfully receives a RAR message, and the preamble index carried in the RAR message is the same as the index of the preamble sent by the terminal device through Msg 1, it is considered that the RAR has been successfully received, and the terminal The device can stop monitoring in the RAR time window.
- RA-RNTI Random Access Radio Network Temporary Identifier
- the UE completes the transmission of the small data packet (that is, the uplink data in S230 and the downlink data in S240 ) without entering the connected state.
- the network will configure a maximum transmission block size (TB size) that the current network allows transmission on SIB2, and the UE judges the amount of data to be transmitted. If it is smaller than the maximum transmission block size broadcast, the UE can initiate EDT transmission ; Conversely, the UE uses the normal connection establishment process and enters the connected state to transmit data.
- TB size maximum transmission block size
- PUR Preconfigured Uplink Resource
- FIG. 3 is a schematic diagram of a PUR transmission air interface process 300 provided by an embodiment of the present application.
- the process 300 may include:
- the terminal device sends an RRC connection recovery request (RRCConnectionResumeRequest) and uplink data (Uplink data) to the network device.
- RRC connection resume request includes but not limited to: resume ID (resumeID), establishment cause (establishment cause) and short resume MAC-I (shortResumeMAC-I).
- RSRP change (increase or decrease) is not greater/less than the set threshold.
- the TAT configuration is sent to the UE through the RRCConnectionRelease message as part of the PUR configuration.
- the RRC instructs the MAC layer or the bottom layer to release the corresponding configuration.
- RRC judges whether pur-Config is included. If it is not included, UE will keep the existing configuration unchanged and TAT will not restart; if it is included, RRC will perform one of the following actions according to the PUR configuration (pur-Config):
- the UE releases the PUR configuration and instructs the lower layers to release the pur-TimeAlignmentTimer.
- the default behavior of the UE after receiving the RRCConnectionRelease message is to maintain the current configuration.
- the method 400 may include:
- the S410 may include:
- the SDT failure condition includes at least one of the following:
- a radio link failure RLF occurs
- the first timer is started when the SDT process is started/triggered, and when the first timer expires, it is considered that the SDT process fails, that is, the terminal device reports SDT failure information to the network device.
- the random access small data transmission (RA-SDT) resources are used to transmit data (or after the RA-SDT process is triggered)
- the random access process fails that is, the random access MSG1/MSG A exceeds
- the indication of the failure of the random access process may come from MCG MAC (upon random access problem indication from MCG MAC).
- the SDT process is a CG-SDT/RA-SDT process, that is, when the SDT uses CG-SDT/RA-SDT resource transmission, when the radio link layer control (Radio Link Control, RLC) retransmission reaches the maximum number of retransmissions , the SDT is considered to have failed; in one implementation, the indication information from the MCG RLC is used to indicate that the maximum number of retransmissions has been reached (upon indication from MCG RLC that the maximum number of retransmissions has been reached). For another example, in the SDT process, if a radio link failure (Radio Link Failure, RLF) occurs, it is considered that the SDT process fails; in one implementation, the radio link can be restored after the RLF occurs.
- RLF Radio Link Failure
- the terminal device when the terminal device receives an RRC rejection (RRCReject) message or an RRC configuration (RRCSetup) message sent by the network side during the execution of the SDT, it considers that the SDT has failed.
- RRC rejection RRCReject
- RRCSetup RRC configuration
- beam recovery can include the following 4 steps:
- Step 0
- the terminal maintains a backup beam pair all the time, and if a beam fails, it will notify the base station of the number of the beam. This step is independent of the 3 other steps below.
- step 1
- the terminal monitors the quality of the control channel, and if it is continuously lower than a certain threshold (hypothetical BLER>0.1) and lasts for a certain period of time, it is considered that a beam failure has occurred.
- a certain threshold hyperthetical BLER>0.1
- the base station After receiving the beam recovery request, the base station switches its own beam to the standby beam notified by the terminal, and sends a response on the standby beam, that is, the beam recovery response (Beam failure recovery response). If the terminal receives the beam recovery response, it means that the recovery of the beam failure has been completed, otherwise it will enter link recovery (link recovery).
- the SDT failure information includes at least one of the following: SDT failure type and failure reason.
- the SDT failure information includes the SDT failure type and/or failure reason.
- CG-SDT can be understood as a process of using CG resources to perform SDT
- RA-SDT can be understood as a process of using RA resources to perform SDT
- the SDT failure type can be understood as a type of failed SDT.
- the CG-SDT, RA-SDT, and even the SDT failure type may also be defined or explained from other angles, which is not specifically limited in this embodiment of the present application.
- the first timer expires, and the first timer is started when the SDT process starts and/or is triggered;
- the radio link layer control RLC fails
- the failure reasons involved in the embodiments of the present application may be the same as the SDT failure conditions mentioned above, that is, when the terminal device determines that the SDT fails based on a certain SDT failure condition, it may determine the corresponding SDT failure condition as the failure cause
- the failure reason involved in the embodiment of the present application may also be different from the SDT failure condition mentioned above, which is not specifically limited in the embodiment of the present application.
- the failure cause may be a subordinate concept of a failure condition.
- the failure condition may be that a radio link failure RLF occurs, and the failure cause may be beam recovery failure.
- the S420 may include:
- the SDT failure information is reported through dedicated information.
- the dedicated information may refer to an information element (IE) dedicated (only) for carrying failure information (FailureInformation).
- IE information element
- the transfer information may be dedicated information of the SDT failure information, or information specially used to carry any kind of failure information, which is not limited in this embodiment of the present application.
- the first serving cell includes at least one of the following cells: a cell accessed through a non-SDT random access procedure, a cell successfully accessed through an RRC connection reestablishment procedure, The cell that the terminal equipment successfully accesses when it re-enters the RRC connected state.
- the first serving cell receives the SDT failure information reported by the terminal device.
- the method 400 may also include:
- the SDT failure information is stored.
- the terminal device before reporting the SDT failure information, stores the SDT failure information; furthermore, after successfully accessing the first serving cell, reports the SDT failure information to the first serving cell.
- the first cell or the second cell receives the SDT failure information reported by the terminal device. Further, when the first serving cell is the second cell, the second cell is further configured to forward the received SDT failure information to the first cell.
- the SDT failure information further includes an identifier of the first cell.
- the identifier of the first cell may be a physical-layer Cell identity (PCI) and/or a cell global identity (Cell Global Identity, CGI) of the first cell.
- PCI physical-layer Cell identity
- CGI cell Global Identity
- the method 400 may also include:
- the network device receives the first indication information reported by the terminal device.
- the first indication information may be carried in an RRC message; for example, an RRC connection establishment request, an RRC reestablishment request or an RRCresume request.
- Receive second indication information where the second indication information is used to instruct the terminal device to report or not to report SDT failure information.
- the method 400 may also include:
- the data volume of the uplink data is less than or equal to the SDT threshold
- CG resources are available on the selected carrier
- the timing advance TA timer is running.
- the signal quality of the serving cell includes but not limited to: Reference Signal Received Power (Reference Signal Receiving Power, RSRP) and/or Reference Signal Received Quality (Reference Signal Receiving Quality, RSRQ).
- RSRP Reference Signal Receiving Power
- RSRQ Reference Signal Received Quality
- the terminal device When uplink data arrives at the upper layer, the terminal device triggers the SDT process, specifically, selects the corresponding SDT type (CG-SDT/RA-SDT) and corresponding resources based on the SDT selection criteria for uplink data transmission. At the same time, the terminal device starts a first timer, which is configured by the network side through an RRC release (RRC release) message when the terminal device enters an inactive state.
- RRC release RRC release
- the data volume of the uplink data is less than or equal to the SDT threshold
- the timing advance TA timer is running.
- the terminal will execute the failure information reporting process, that is, report the SDT failure information.
- the terminal can set the type of failure as SDT failure; further, the terminal can also report the reason for the failure, for example, the RLC exceeds the maximum number of retransmissions.
- the methods for the terminal to report SDT failure information include but are not limited to the following three methods:
- Mode 1 The terminal stores the SDT failure information, initiates non-small data transmission (NON-SDT) random access, and reports the SDT failure information to the successfully accessed serving cell after successful access.
- NON-SDT non-small data transmission
- Mode 2 The terminal stores the SDT failure information, initiates connection re-establishment, and reports the SDT failure information to the successfully accessed serving cell after successful access re-establishment.
- Mode 3 The terminal returns to the idle state, stores the SDT failure information, and reports the SDT failure information to the successfully accessed serving cell when entering the connected state next time.
- the serving cell may be the first cell configured with SDT resources and SDT failure occurs, or may be a new second cell. If the cell successfully accessed by the terminal is the second cell, the second cell may forward the reception to the first cell for subsequent optimization.
- the failure information report may include the ID of the first cell, such as PCI and/or CGI.
- the terminal before the terminal reports the SDT failure information, it can decide whether to report based on the needs of the network, such as telling the network the current failure information/failure report to be reported through the 1-bit indication information; and then determine whether to report based on the network configuration.
- the indication information may be carried in an RRC message; for example, an RRC connection establishment request, an RRC reestablishment request or an RRCresume request.
- the terminal device When uplink data arrives at the upper layer, the terminal device triggers the SDT process, specifically, selects the corresponding SDT type (CG-SDT/RA-SDT) and corresponding resources based on the SDT selection criteria for uplink data transmission. At the same time, the terminal device starts a first timer, which is configured by the network side through an RRC release (RRC release) message when the terminal device enters an inactive state.
- RRC release RRC release
- Mode 1 The terminal stores the SDT failure information, initiates non-small data transmission (NON-SDT) random access, and reports the SDT failure information to the successfully accessed serving cell after successful access.
- NON-SDT non-small data transmission
- Mode 2 The terminal stores the SDT failure information, initiates connection re-establishment, and reports the SDT failure information to the successfully accessed serving cell after successful access re-establishment.
- Mode 3 The terminal returns to the idle state, stores the SDT failure information, and reports the SDT failure information to the successfully accessed serving cell when entering the connected state next time.
- the serving cell may be the first cell configured with SDT resources and SDT failure occurs, or may be a new second cell. If the cell successfully accessed by the terminal is the second cell, the second cell may forward the reception to the first cell for subsequent optimization.
- the failure information report may include the ID of the first cell, such as PCI and/or CGI.
- the terminal before the terminal reports the SDT failure information, it can decide whether to report based on the needs of the network, such as telling the network the current failure information/failure report to be reported through the 1-bit indication information; and then determine whether to report based on the network configuration.
- the indication information may be carried in an RRC message; for example, an RRC connection establishment request, an RRC reestablishment request or an RRCresume request.
- the terminal device When uplink data arrives at the upper layer, the terminal device triggers the SDT process, specifically, selects the corresponding SDT type (CG-SDT/RA-SDT) and corresponding resources based on the SDT selection criteria for uplink data transmission. At the same time, the terminal device starts a first timer, which is configured by the network side through an RRC release (RRC release) message when the terminal device enters an inactive state.
- RRC release RRC release
- CG resources are available on the selected carrier
- the timing advance TA timer is running.
- the methods for the terminal to report SDT failure information include but are not limited to the following three methods:
- Mode 3 The terminal returns to the idle state, stores the SDT failure information, and reports the SDT failure information to the successfully accessed serving cell when entering the connected state next time.
- the serving cell may be the first cell configured with SDT resources and SDT failure occurs, or may be a new second cell. If the cell successfully accessed by the terminal is the second cell, the second cell may forward the reception to the first cell for subsequent optimization.
- the failure information report may include the ID of the first cell, such as PCI and/or CGI.
- the terminal before the terminal reports the SDT failure information, it can decide whether to report based on the needs of the network, such as telling the network the current failure information/failure report to be reported through the 1-bit indication information; and then determine whether to report based on the network configuration.
- the indication information may be carried in an RRC message; for example, an RRC connection establishment request, an RRC reestablishment request or an RRCresume request.
- the sequence numbers of the above-mentioned processes do not mean the order of execution, and the order of execution of the processes should be determined by their functions and internal logic, and should not be used in this application.
- the implementation of the examples constitutes no limitation.
- the terms “downlink” and “uplink” are used to indicate the transmission direction of signals or data, wherein “downlink” is used to indicate that the transmission direction of signals or data is from the station to the user equipment in the cell For the first direction, “uplink” is used to indicate that the signal or data transmission direction is the second direction from the user equipment in the cell to the station, for example, “downlink signal” indicates that the signal transmission direction is the first direction.
- the term "and/or" is only an association relationship describing associated objects, indicating that there may be three relationships. Specifically, A and/or B may mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or" relationship.
- Fig. 5 is a schematic block diagram of a terminal device 500 according to an embodiment of the present application.
- a processing unit 510 configured to determine whether a small data transmission SDT failure occurs
- the reporting unit 520 is configured to report SDT failure information when SDT failure occurs.
- the processing unit 510 is specifically configured to:
- the SDT failure condition includes at least one of the following:
- the first timer expires, and the first timer is started when the SDT process starts and/or is triggered;
- the radio link layer control RLC fails
- a radio link failure RLF occurs
- the SDT failure information includes at least one of the following:
- the SDT failure type includes at least one of the following:
- Random access small data transmission RA-SDT failed.
- the failure reasons include at least one of the following:
- the reporting unit 520 is specifically configured to:
- the reporting unit 520 is also used to:
- the first serving cell is a first cell configured with SDT resources and an SDT failure occurs; or the first serving cell is a second cell other than the first cell.
- the SDT failure information further includes an identifier of the first cell.
- the reporting unit 520 is also used to:
- the reporting unit 520 is also used to:
- Receive second indication information where the second indication information is used to instruct the terminal device to report or not to report SDT failure information.
- the reporting unit 520 is also used to:
- the data volume of the uplink data is less than or equal to the SDT threshold
- the change amount of the signal quality of the serving cell is less than or equal to the quality threshold
- CG resources are available on the selected carrier
- the timing advance TA timer is running.
- the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment.
- the terminal device 500 shown in FIG. 5 may correspond to the corresponding subject in the method 400 of the embodiment of the present application, and the aforementioned and other operations and/or functions of each unit in the terminal device 500 are for realizing the For the sake of brevity, the corresponding processes in each method are not repeated here.
- the network device 600 may include:
- the receiving unit 610 is configured to receive the small data transmission SDT failure information reported by the terminal device.
- the SDT failure information includes at least one of the following:
- the SDT failure type includes at least one of the following:
- Random access small data transmission RA-SDT failed.
- the failure reasons include at least one of the following:
- the first timer expires, and the first timer is started when the SDT process starts and/or is triggered;
- the radio link layer control RLC fails
- the receiving unit 610 is specifically configured to:
- the SDT failure information reported by the terminal device is received through dedicated information.
- the serving cell of the terminal device is a first serving cell
- the first serving cell includes at least one of the following cells: a cell accessed through a non-SDT random access procedure, reestablished through an RRC connection The cell successfully accessed by the process, and the cell successfully accessed when the terminal device re-enters the RRC connection state.
- the first serving cell is a first cell configured with SDT resources and an SDT failure occurs; or the first serving cell is a second cell other than the first cell.
- the serving cell of the terminal device is the second cell
- the receiving unit 610 is further configured to:
- the SDT failure information further includes an identifier of the first cell.
- the receiving unit 610 is also used for:
- the receiving unit 610 is also used for:
- the receiving unit 610 is also used for:
- the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment.
- the network device 600 shown in FIG. 6 may correspond to the corresponding subject in the method 400 of the embodiment of the present application, and the foregoing and other operations and/or functions of each unit in the network device 600 are respectively in order to realize the For the sake of brevity, the corresponding processes in each method are not repeated here.
- the functional modules may be implemented in the form of hardware, may also be implemented by instructions in the form of software, and may also be implemented by a combination of hardware and software modules.
- each step of the method embodiment in the embodiment of the present application can be completed by an integrated logic circuit of the hardware in the processor and/or instructions in the form of software, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as hardware
- the decoding processor is executed, or the combination of hardware and software modules in the decoding processor is used to complete the execution.
- the software module may be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, and registers.
- the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps in the above method embodiments in combination with its hardware.
- processing unit 510 mentioned above may be implemented by a processor, and both the reporting unit 520 and the receiving unit 610 mentioned above may be implemented by a transceiver.
- FIG. 7 is a schematic structural diagram of a communication device 700 according to an embodiment of the present application.
- the communication device 700 may include a processor 710 .
- the processor 710 can invoke and run a computer program from the memory, so as to implement the method in the embodiment of the present application.
- the memory 720 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 710 .
- the processor 710 can invoke and run a computer program from the memory 720, so as to implement the method in the embodiment of the present application.
- the memory 720 may be an independent device independent of the processor 710 , or may be integrated in the processor 710 .
- a chip is also provided in the embodiment of the present application.
- the chip may be an integrated circuit chip, which has signal processing capabilities, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
- the chip can also be called system-on-chip, system-on-chip, system-on-chip or system-on-chip, etc.
- the chip can be applied to various communication devices, so that the communication device installed with the chip can execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
- FIG. 8 is a schematic structural diagram of a chip 800 according to an embodiment of the present application.
- the chip 800 may further include a memory 820 .
- the processor 810 can call and run a computer program from the memory 820, so as to implement the method in the embodiment of the present application.
- the memory 820 may be used to store indication information, and may also be used to store codes, instructions, etc. executed by the processor 810 .
- the memory 820 may be an independent device independent of the processor 810 , or may be integrated in the processor 810 .
- the chip 800 may further include an input interface 830 .
- the processor 810 may control the input interface 830 to communicate with other devices or chips, specifically, may obtain information or data sent by other devices or chips.
- the processor 810 can control the output interface 840 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.
- the chip 800 can be applied to the network device in the embodiment of the present application, and the chip can realize the corresponding process implemented by the network device in the various methods of the embodiment of the present application, and can also realize the various methods of the embodiment of the present application For the sake of brevity, the corresponding process implemented by the terminal device in , will not be repeated here.
- bus system includes not only a data bus, but also a power bus, a control bus, and a status signal bus.
- Processors mentioned above may include, but are not limited to:
- DSP Digital Signal Processor
- ASIC Application Specific Integrated Circuit
- FPGA Field Programmable Gate Array
- the processor may be used to implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present application.
- the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
- the software module may be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or erasable programmable memory, register.
- the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
- the storage mentioned above includes but is not limited to:
- non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash.
- the volatile memory can be Random Access Memory (RAM), which acts as external cache memory.
- RAM Static Random Access Memory
- SRAM Static Random Access Memory
- DRAM Dynamic Random Access Memory
- Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
- SDRAM double data rate synchronous dynamic random access memory
- Double Data Rate SDRAM, DDR SDRAM double data rate synchronous dynamic random access memory
- Enhanced SDRAM, ESDRAM enhanced synchronous dynamic random access memory
- SLDRAM synchronous connection dynamic random access memory
- Direct Rambus RAM Direct Rambus RAM
- Embodiments of the present application also provide a computer-readable storage medium for storing computer programs.
- the computer-readable storage medium stores one or more programs, and the one or more programs include instructions that, when executed by a portable electronic device including a plurality of application programs, enable the portable electronic device to perform the implementation shown in method 400. example method.
- the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application. For brevity, here No longer.
- the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application , for the sake of brevity, it is not repeated here.
- the embodiment of the present application also provides a computer program product, including a computer program.
- the computer program product can be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
- the repeat can be applied to the computer program product in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods of the embodiments of the present application, for It is concise and will not be repeated here.
- the embodiment of the present application also provides a computer program.
- the computer program When the computer program is executed by the computer, the computer can execute the method of the embodiment shown in the method 400 .
- the computer program can be applied to the network device in the embodiment of the present application.
- the computer program When the computer program is run on the computer, the computer executes the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity , which will not be repeated here.
- the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
- the computer program When the computer program is run on the computer, the computer executes each method in the embodiment of the present application to be implemented by the mobile terminal/terminal device For the sake of brevity, the corresponding process will not be repeated here.
- An embodiment of the present application also provides a communication system, which may include the above-mentioned terminal device and network device to form a communication system 100 as shown in FIG. 1 , which is not repeated here for brevity.
- a communication system which may include the above-mentioned terminal device and network device to form a communication system 100 as shown in FIG. 1 , which is not repeated here for brevity.
- system and the like in this document may also be referred to as “network management architecture” or “network system”.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (35)
- 一种SDT失败上报的方法,其特征在于,包括:确定是否发生小数据传输SDT失败;在发生SDT失败的情况下,上报SDT失败信息。
- 根据权利要求1所述的方法,其特征在于,所述确定是否发生小数据传输SDT失败,包括:当满足SDT失败条件时,确定SDT失败。
- 根据权利要求2所述的方法,其特征在于,所述SDT失败条件包括以下中的至少一项:第一定时器超时,所述第一定时器在SDT流程开始和/或触发时启动;随机接入RA失败;配置授权CG资源不可用;无线链路层控制RLC失败;发生无线链路失败RLF;发生小区重选;以及收到无线资源控制拒绝RRCReject或无线资源控制配置RRCSetup消息。
- 根据权利要求1至3中任一项所述的方法,其特征在于,所述SDT失败信息包括以下中的至少一项:SDT失败类型;失败原因。
- 根据权利要求4所述的方法,其特征在于,所述SDT失败类型包括以下中的至少一项:SDT失败;配置授权小数据传输CG-SDT失败;随机接入小数据传输RA-SDT失败。
- 根据权利要求4所述的方法,其特征在于,所述失败原因包括以下中的至少一项:第一定时器超时,所述第一定时器在SDT流程开始和/或触发时启动;随机接入RA失败;配置授权CG资源不可用;无线链路层控制RLC失败;波束恢复失败;发生小区重选;收到无线资源控制拒绝RRCReject或无线资源控制配置RRCSetup消息。
- 根据权利要求1至6中任一项所述的方法,其特征在于,所述上报SDT失败信息,包括:通过RLF报告上报所述SDT失败信息;或通过专用信息上报所述SDT失败信息。
- 根据权利要求1至7中任一项所述的方法,其特征在于,所述上报SDT失败信息,包括:向第一服务小区上报所述SDT失败信息,所述第一服务小区包括以下小区中的至少一项:通过非SDT随机接入流程接入的小区,通过RRC连接重建流程成功接入的小区、终端设备重新进入RRC连接态时成功接入的小区。
- 根据权利要求8所述的方法,其特征在于,所述方法还包括:存储所述SDT失败信息。
- 根据权利要求8所述的方法,其特征在于,所述第一服务小区为配置有SDT资源且发生了SDT失败的第一小区;或所述第一服务小区为除所述第一小区之外的第二小区。
- 根据权利要求10所述的方法,其特征在于,所述SDT失败信息还包括所述第一小区的标识。
- 根据权利要求1至11中任一项所述的方法,其特征在于,所述方法还包括:上报第一指示信息,所述第一指示信息用于指示存在待上报的SDT失败信息。
- 根据权利要求1至12中任一项所述的方法,其特征在于,所述方法还包括:接收第二指示信息,所述第二指示信息用于指示终端设备上报或不上报SDT失败信息。
- 根据权利要求1至13中任一项所述的方法,其特征在于,所述方法还包括:接收高层下发的上行数据;通过随机接入资源和/或配置授权CG资源,发送所述上行数据。
- 根据权利要求14所述的方法,其特征在于,在确定使用CG资源发送所述上行数据的情况下,满足以下条件中的至少一项:所述上行数据的数据量小于或等于SDT门限;服务小区的信号质量的变化量小于或等于质量门限;所选载波上有可用的CG资源;所选波束上有可用的CG资源;以及定时提前TA定时器处于在运行期间。
- 一种SDT失败上报的方法,其特征在于,包括:接收终端设备上报的小数据传输SDT失败信息。
- 根据权利要求16所述的方法,其特征在于,所述SDT失败信息包括以下中的至少一项:SDT失败类型;失败原因。
- 根据权利要求17所述的方法,其特征在于,所述SDT失败类型包括以下中的至少一项:SDT失败;配置授权小数据传输CG-SDT失败;随机接入小数据传输RA-SDT失败。
- 根据权利要求17所述的方法,其特征在于,所述失败原因包括以下中的至少一项:第一定时器超时,所述第一定时器在SDT流程开始和/或触发时启动;随机接入RA失败;配置授权CG资源不可用;无线链路层控制RLC失败;波束恢复失败;发生小区重选;收到无线资源控制拒绝RRCReject或无线资源控制配置RRCSetup消息。
- 根据权利要求16至19中任一项所述的方法,其特征在于,所述接收终端设备上报的小数据传输SDT失败信息,包括:通过RLF报告接收所述终端设备上报的所述SDT失败信息;或通过专用信息接收所述终端设备上报的所述SDT失败信息。
- 根据权利要求16至20中任一项所述的方法,其特征在于,所述方法应用于第一服务小区,所述第一服务小区包括以下小区中的至少一项:通过非SDT随机接入流程接入的小区,通过RRC连接重建流程成功接入的小区、终端设备重新进入RRC连接态时成功接入的小区。
- 根据权利要求21所述的方法,其特征在于,所述第一服务小区为配置有SDT资源且发生了SDT失败的第一小区;或所述第一服务小区为除所述第一小区之外的第二小区。
- 根据权利要求22所述的方法,其特征在于,所述方法应用于所述第二小区,所述方法还包括:向所述第一小区转发所述终端设备上报的所述SDT失败信息。
- 根据权利要求22所述的方法,其特征在于,所述SDT失败信息还包括所述第一小区的标识。
- 根据权利要求16至24中任一项所述的方法,其特征在于,所述方法还包括:接收所述终端设备上报的第一指示信息,所述第一指示信息用于指示存在待上报的SDT失败信息。
- 根据权利要求16至25中任一项所述的方法,其特征在于,所述方法还包括:向所述终端设备发送第二指示信息,所述第二指示信息用于指示终端设备上报或不上报SDT失败信息。
- 根据权利要求16至26中任一项所述的方法,其特征在于,所述方法还包括:通过随机接入资源和/或配置授权CG资源,接收所述终端设备发送的上行数据。
- 一种终端设备,其特征在于,包括:处理单元,用于确定是否发生小数据传输SDT失败;上报单元,用于在发生SDT失败的情况下,上报SDT失败信息。
- 一种网络设备,其特征在于,包括:接收单元,用于接收终端设备上报的小数据传输SDT失败信息。
- 一种终端设备,其特征在于,包括:处理器和存储器,所述存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存储的计算机程序,以执行权利要求1至15中任一项所述的方法。
- 一种网络设备,其特征在于,包括:处理器和存储器,所述存储器用于存储计算机程序,所述处理器用于调用并运行所述存储器中存 储的计算机程序,以执行权利要求16至27中任一项所述的方法。
- 一种芯片,其特征在于,包括:处理器,用于从存储器中调用并运行计算机程序,使得安装有所述芯片的设备执行如权利要求1至15中任一项所述的方法或如权利要求16至27中任一项所述的方法。
- 一种计算机可读存储介质,其特征在于,用于存储计算机程序,所述计算机程序使得计算机执行如权利要求1至15中任一项所述的方法或如权利要求16至27中任一项所述的方法。
- 一种计算机程序产品,其特征在于,包括计算机程序指令,所述计算机程序指令使得计算机执行如权利要求1至15中任一项所述的方法或如权利要求16至27中任一项所述的方法。
- 一种计算机程序,其特征在于,所述计算机程序使得计算机执行如权利要求1至15中任一项所述的方法或如权利要求16至27中任一项所述的方法。
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180089280.6A CN116803193A (zh) | 2021-05-08 | 2021-05-08 | Sdt失败上报的方法、终端设备和网络设备 |
EP21941065.1A EP4333489A4 (en) | 2021-05-08 | 2021-05-08 | SDT ERROR REPORTING PROCEDURE, TERMINAL DEVICE AND NETWORK DEVICE |
PCT/CN2021/092425 WO2022236484A1 (zh) | 2021-05-08 | 2021-05-08 | Sdt失败上报的方法、终端设备和网络设备 |
US18/504,243 US20240080699A1 (en) | 2021-05-08 | 2023-11-08 | Sdt failure reporting method, terminal device, and network device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/CN2021/092425 WO2022236484A1 (zh) | 2021-05-08 | 2021-05-08 | Sdt失败上报的方法、终端设备和网络设备 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US18/504,243 Continuation US20240080699A1 (en) | 2021-05-08 | 2023-11-08 | Sdt failure reporting method, terminal device, and network device |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022236484A1 true WO2022236484A1 (zh) | 2022-11-17 |
Family
ID=84027890
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2021/092425 WO2022236484A1 (zh) | 2021-05-08 | 2021-05-08 | Sdt失败上报的方法、终端设备和网络设备 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20240080699A1 (zh) |
EP (1) | EP4333489A4 (zh) |
CN (1) | CN116803193A (zh) |
WO (1) | WO2022236484A1 (zh) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023125649A1 (zh) * | 2021-12-31 | 2023-07-06 | 夏普株式会社 | 连接建立失败报告方法和用户设备 |
WO2023125375A1 (zh) * | 2021-12-28 | 2023-07-06 | 华为技术有限公司 | 通信方法及装置 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110913428A (zh) * | 2018-09-14 | 2020-03-24 | 电信科学技术研究院有限公司 | 一种信息上报方法、信息获取方法、终端及网络设备 |
WO2021007869A1 (zh) * | 2019-07-18 | 2021-01-21 | Oppo广东移动通信有限公司 | 信息上报方法及相关设备 |
WO2021026932A1 (zh) * | 2019-08-15 | 2021-02-18 | Oppo广东移动通信有限公司 | 无线通信方法、终端设备和网络设备 |
CN112770350A (zh) * | 2019-11-06 | 2021-05-07 | 维沃移动通信有限公司 | 一种失败报告的上报方法及相关设备 |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104105114B (zh) * | 2013-04-03 | 2018-02-23 | 中国移动通信集团公司 | 数据传输方法、装置及终端 |
CN111095973A (zh) * | 2019-12-06 | 2020-05-01 | 北京小米移动软件有限公司 | 通信失败处理方法、通信失败处理装置及存储介质 |
WO2022212706A1 (en) * | 2021-03-31 | 2022-10-06 | Ofinno, Llc | Report for small data transmission |
-
2021
- 2021-05-08 WO PCT/CN2021/092425 patent/WO2022236484A1/zh active Application Filing
- 2021-05-08 EP EP21941065.1A patent/EP4333489A4/en active Pending
- 2021-05-08 CN CN202180089280.6A patent/CN116803193A/zh active Pending
-
2023
- 2023-11-08 US US18/504,243 patent/US20240080699A1/en active Pending
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN110913428A (zh) * | 2018-09-14 | 2020-03-24 | 电信科学技术研究院有限公司 | 一种信息上报方法、信息获取方法、终端及网络设备 |
WO2021007869A1 (zh) * | 2019-07-18 | 2021-01-21 | Oppo广东移动通信有限公司 | 信息上报方法及相关设备 |
WO2021026932A1 (zh) * | 2019-08-15 | 2021-02-18 | Oppo广东移动通信有限公司 | 无线通信方法、终端设备和网络设备 |
CN112770350A (zh) * | 2019-11-06 | 2021-05-07 | 维沃移动通信有限公司 | 一种失败报告的上报方法及相关设备 |
Non-Patent Citations (1)
Title |
---|
See also references of EP4333489A4 * |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2023125375A1 (zh) * | 2021-12-28 | 2023-07-06 | 华为技术有限公司 | 通信方法及装置 |
WO2023125649A1 (zh) * | 2021-12-31 | 2023-07-06 | 夏普株式会社 | 连接建立失败报告方法和用户设备 |
Also Published As
Publication number | Publication date |
---|---|
EP4333489A1 (en) | 2024-03-06 |
EP4333489A4 (en) | 2024-05-29 |
US20240080699A1 (en) | 2024-03-07 |
CN116803193A (zh) | 2023-09-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN109565896B (zh) | 低功率rrc操作方法和装置 | |
JP7088603B2 (ja) | データ伝送方法、端末デバイス及びアクセスネットワークデバイス | |
CN108541034B (zh) | 处理状态的转换的装置及方法 | |
WO2021203310A1 (zh) | 一种数据传输方法及装置、终端设备 | |
JP2021510255A (ja) | ビーム失敗回復方法、装置およびデバイス | |
WO2018112871A1 (zh) | 数据发送/接收装置、方法以及通信系统 | |
US20240080699A1 (en) | Sdt failure reporting method, terminal device, and network device | |
EP4229906A1 (en) | Method and apparatus for multicast and broadcast services | |
TW202010334A (zh) | 一種資料傳輸方法及裝置、終端 | |
WO2021195843A1 (en) | Method and apparatus for data transmission | |
CN115244979A (zh) | 一种数据传输方法及装置、通信设备 | |
WO2022061872A1 (zh) | 一种小数据传输方法及装置、终端设备 | |
US20230180329A1 (en) | Method and apparatus for sidelink communication during fast mcg link recovery procedure | |
WO2020206643A1 (zh) | 一种随机接入方法、设备及存储介质 | |
WO2020024611A1 (zh) | 一种信息传输的方法、设备及计算机存储介质 | |
WO2023028991A1 (en) | Method and apparatus for small data transmission | |
WO2023065303A1 (zh) | 一种控制方法、设备及存储介质 | |
WO2019136598A1 (zh) | 部分带宽定时方法以及装置、通信系统 | |
WO2021197029A1 (zh) | 一种先听后说lbt失败指示方法及装置 | |
WO2022236499A1 (zh) | Cg资源维护方法、终端设备和网络设备 | |
WO2020082394A1 (zh) | 随机接入的方法、终端设备和网络设备 | |
WO2020077600A1 (zh) | 一种触发波束失败恢复的方法及装置、终端 | |
WO2023122889A1 (zh) | 一种通信处理方法及装置、终端设备、接入网设备 | |
WO2023035240A1 (zh) | 一种控制随机接入的方法及装置、终端设备 | |
WO2022252133A1 (zh) | 一种安全激活失败后的恢复方法和装置 |
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: 21941065 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180089280.6 Country of ref document: CN |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2021941065 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021941065 Country of ref document: EP Effective date: 20231201 |